We're currently running WebSphere Application Server 3.5.4 on a couple of AIX application servers, with the corresponding WAS database repository on a separate AIX database server, under UDB v7.2. We're now in the process of looking at a high-availability solution for our database servers. One alternative is to build an HACMP cluster on AIX for our UDB database servers, and put the WAS database in that environment. Another alternative is to move the WAS database to OS/390, into our 4-way DB2 data-sharing environment, accessible by sysplex distributor via DB2 Connect. When we mentioned the OS/390 alternative to some IBM WebSphere folks who visited us yesterday to do technical review of our architecture, they looked at us as if we had been smoking crack! Although this is a supported configuration (WAS DB support on OS/390 became available as of WAS 3.5.3), they told us that they were not aware of any of their customers who may have been doing us, and overall seemed somewhat uncomfortable about our considering this alternative. They admitted that it probably would work, but they gave us the impression that they thought we shouldn't pursue it, that we should keep the WAS database on the same platform (AIX) as the WAS software, albeit on a different physical box. I'm not sure if I really understand their concern, or what risk we would really be looking at, since this does appear to be a supported configuration. Does anybody want to give any opinions about running the WAS software on one platform, and putting the WAS database repository on a different platform? Is anybody else doing it? Are there any obvious pros/cons about doing it? As usual, any information or opinions will be appreciated. Bill Gallagher, DBA Phoenix Life Insurance Enfield, CT ===== To unsubscribe, send 'unsubscribe' to [EMAIL PROTECTED] For other info (and scripts), see http://people.mn.mediaone.net/scottrmcleod
