PQ42108: WAS 3.5 SHOULD WORK WITH SYBASE V12 AS DOCUMENT STATES. HOWEVER FAIL TO INSTALL WAS 3.5 WITH REMOTE SYBASE.


APAR

APAR status
Closed as fixed if next.

Error description
Customer fail to install WAS 3.5 with remote Sybase 12. In WAS 3
.5 documentation, and its topology, remote DB repository is vali
d.
Local fix
Partial workaround: First, install WAS 3.5 with a local DB, i.e.
IDB. Then install Sybase 12 on the remote machine. Then modify t
he admin.config file from WAS 3.5 machine, change the dbUrl, dbD
river, classpath, set install.initial.config=true. Then restart
WAS again.WAS can start but it will not configurate everything u
nder Default_Server.  Customer may have to cut and paste the XML
 file from the install with IDB, to the XML file with Sybase.
Problem summary
in the next release of WAS, if any.
Note:  Install problems can't be corrected via a PTF.
Problem conclusion
Temporary fix
Comments
APAR information
APAR numberPQ42108
Reported component nameWAS ADVANCED SU
Reported component ID5648C8402
Reported release350
StatusCLOSED FIN
PENoPE
HIPERNoHIPER
Submitted date2000-09-29
Closed date2000-10-25
Last modified date2000-10-25

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:APAR is sysrouted FROM one or more of the following:


Modules/Macros
INSTALL
APAR is sysrouted TO one or more of the following:Modules/Macros

Fix information

Applicable component levels
R350 PSNUP











Document Information

Product categories: Software, Application Servers, Distributed Application & Web Servers, WebSphere Application Server, General
Software version: 350
Reference #: PQ42108
IBM Group: Software Group
Modified date: 2000-10-25