Re: RE: design question, how to handle this project

Ashish,

What I would consider:

1.      Create a ?connection registration? database which hold the URL, driver,
userid, password, properties, etc for each of your AS400 participants.
2.      Create a ?query operations? database which holds JDBC requests plus a
reference to which connection it uses.
3.      At application startup or init time, start your connection pools as
defined in #1
4.      When a query is run, lookup the actual SQL out of the registered
operations and run it.
5.      Place the code on a single server which has TCP access to your 30 AS400?
s.

This functionality is provided in our free WOW version if you are interested
(email to info@xxxxxxxxxxxxxxxxx) .   The application would operate like
this:

http://www.planetjavainc.com/wow60/runApp?id=374

In this example, I have 2 systems being accessed and one operation per
system because I don?t have 30 AS400?s, you would simply expand this to 30
or whatever your requirements are:

In the internal control section, it shows parts of the connection
registration database  #1 and also the dynamic operations.

Advantages:
1.      Single code base and server provide all functionality, minimal
dependencies on other smaller 400?s
2.      JDBC provides standard access.  Other DBs such as Oracle or SQL Server
could be used as well.
3.      Application is dynamic and data driven.  Operations and connections 
could
be added dynamically.
4.      Operations can be tailored to each ?version? of databases as required.

Thanks,  Paul Holm

Business: 760-432-0600   Home: 760-432-6550
Cell:  760-415-8830
PlanetJ - Makers of WOW  (AKA... WebSphere on Steroids)