Database to database communications over LAN

[Jensen, Kim Bjørn]

I have solved the same problem, I think, by using two databases. One as a front end, performing basic validations and data collection, for the web-pages to communicate with, and one being the main database holding data and doing calculations.
The two databases are connected by DB LINKs and processing of data, done by packaged pl/sql procedures and functions, is run by the built-in scheduler with short intervals, like a queueing system.
Both DB Links and the scheduler are in 10g stable technologies and works OK - though database stops and restarts require specific focus on the scheduler which not in all cases restart as expected.

It was fairly easy to get the solution up and running, but the downside is on follow-up in production. It required quite an effort and to minimize hands on controls I had to build a very basic admin-tool which took quite a lot of programming - much more than setting up the required functionality in the first place.

Like John Penney, I would recommend using a queueing tool, if possible, because so much of the administration of the application in production is handled.


Sincerely,
Kim Bjørn Jensen
Principal Consultant
Tel: (+47) 23 21 18 37  Mob: (+47) 911 15 313

P Please consider the environment before printing this e-mail

LINDORFF - Confidence in Commerce and Credit
Box 4, NO-3833 Bø i Telemark, Norway
Visiting address: Hellandtunet, Kyrkjevegen, Bø i Telemark
Tel: (+47) 35 06 15 00 Fax: (+47) 35 06 15 01
www.lindorff.no<blocked::http://www.lindorff.no/> / www.lindorff.com<blocked::http://www.lindorff.com/>

** This message including any attachments may
contain confidential and/or priveleged information
intended only for the person or entity to which it is
addressed. If you are not the intended recipient
you should delete this message. Any printing, copying,
distribution or other use of this message is strictly
prohibited. If you have received this message in
error, please notify the sender immediately by telephone,
fax or e-mail and delete all copies of this message and
any attachments from your system. Thank you.

From: powerh-l-bounces+kim-bjorn.jensen=lindorff.com at lists.sowder.com [mailto:powerh-l-bounces+kim-bjorn.jensen=lindorff.com at lists.sowder.com] On Behalf Of cfinley
Sent: 13. august 2009 23:48
To: 'Penney, John'; powerh-l at lists.sowder.com
Subject: RE: Database to database communications over LAN

I would think that Websphere MQ  would be the best choice and require the least amount of programming.  By that I mean, the problem with sockets in any solution is that it is up to the developer to take care of error correction, outages, etc.  Websphere MQ has much of that built in.  Moreover there are multiple API's you can use to write the application including COBOL.  Also, there are many free and low cost commercial tools that can help you with troubleshooting and debugging.

There are several choice available to you to create such a solution.  One that comes to mind is that Oracle side would use a combination of stored procedures, triggers and perhaps transactions. The VMS side will require some sort of simple server application to manage the communications with the Oracle host and the making of the changes to the RDB database.

If this sounds appealing, please contact me directly and I will brainstorm some implementation ideas with you.


Charles Finley

(619) 795-0720

________________________________
From: powerh-l-bounces+cfinley=xformix.com at lists.sowder.com [mailto:powerh-l-bounces+cfinley=xformix.com at lists.sowder.com] On Behalf Of Penney, John
Sent: Thursday, August 13, 2009 2:20 PM
To: powerh-l at lists.sowder.com
Subject: Database to database communications over LAN

Hello Powerhouse-l:

I need some ideas and this was one of the Forums that came immediately to mind.

Conceptually we have an application running in JSP, HTML, Oracle 10g,etc. that has to send information across the LAN to a native OpenVMS Server running Oracle Rdb and of course PowerHouse. I won't reveal the version numbers to save people falling off their chairs.

On VMS in Real Time we need to have a method of receiving the transmitted data stream, posting ENTRY-FIND-CHANGE transactions to the Rdb and sending back an acknowledgement that we were (or were not) successful.

We're talking 20 - 30 tables with about 1,300 online users at this point. Order Entry is my main concern. Record maintenance of existing customers is low volume.

Already Considered:

Batch processing is not a solution. Too time consuming and potential for Network performance issues. Maybe even locking problems on VMS side?

I thought about using MBXs but how you can access MBXs through a LAN I am unaware of how-to.

Using one central Oracle 10g database for both sides of the house - politically sensitive issue - plus the data migration from Database A to B is probably not feasible.

Socket solution-  in the mix.

MQ messaging- in the mix.

Anybody have any experience conceptually with any of my issues I'd appreciate a post.

Thanks for all your help in the past ladies and gents.

Cheers!

John M Penney
(360)789-8159 cellular


-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.sowder.com/pipermail/powerh-l/attachments/20090814/06e2132e/attachment.htm