|
Sorry should have changed the subject earlier! Thanks, Sudha Sudha Ramanujan SunGard Futures Systems sramanujan@xxxxxxxxxxxxxxxxxx (312) 577 6179 (312) 577 6101 - Fax -----Original Message----- From: Ramanujan, Sudha Sent: Thursday, February 24, 2005 10:45 AM To: midrange-l@xxxxxxxxxxxx Subject: RE: SQL performance with Local journalling Hi all, I am not sure if this is a question for this user group or for Java-l but I certainly need help. We want to setup WAS for multiple clients on our iSeries (V5R3). Until now, we had TomCat setup and each client having separate instance of TomCat running and their local property files and so to their files library(schema) on iSeries. But now, in WAS, we want to setup one instance and one datasource connection object and now, here is where I don't know how we should be working with users. For all the non-iSeries users, we have been accessing our property file for setups which was unique per instance of TomCat but how will we maintain this in one single instance of WAS. How do you all do this? To explain further, uSer logs in -> how to authenticate to iSeries (especially for non-iSeries users)-> set up their library list? TIA, Sudha Sudha Ramanujan SunGard Futures Systems sramanujan@xxxxxxxxxxxxxxxxxx (312) 577 6179 (312) 577 6101 - Fax -- This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/midrange-l or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.