PQ91014: UDDI INSTALL SCRIPT FOR CLOUDSCAPE ( SETUPUDDI.JACL ) FAILS WEBSPHERE APPLICATION SERVER V5 | |||||||||||||||||||||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||||||||||||||||||||
![]() APAR status Closed as program error. Error description Customer encoutering error with the UUDI install of CloudScape. Customer issue > There is a problem in the WebSphere directory structure related to the cloudscape libraries. The UDDI install script for cloudscape (setupuddi.jacl) creates a cloudscape datasource with a classpath of /$WAS_LIBS_DIR/db2j.jar. $WAS_LIBS_DIR equates to $WAS_INSTALL_ROOT/lib which, on our system, equates to There is no db2j.jar in this directory. There is a symbolic in the /TESTAPPS/WebSphere390/V500/AppServ52/lib/ cloudscape/lib for db2j.jar which points to /usr/lpp/Product/WebSphere/WASWS/lib/cloudscape /lib/db2j.jar. However, there is nothing in /usr/lpp/Product/WebSphere/WASWS/lib/cloudscape/lib (/usr/lpp/Product/WebSphere/WASWS/ is the smpe install root) The actual file is located in /usr/lpp/Product/WebSphere/WASWS/lib. It appears the actual problem is that there is no symbolic link in the /TESTAPPS/WebSphere390/V500/AppServ52/lib directory.Local fix Workaround by copying db2j.jar from the Cloudscape 5.0 directory , Cloudscape 5.0 is the default. Or they can workaround by making the link from $WAS_HOME/lib/db2j.jar back to to /usr/lpp/Product/WebSphere/WASWS/lib/db2j.jar. which is what the post-install action should have done.Problem summary **************************************************************** * USERS AFFECTED: All users of WebSphere Application Server * * V5.0 for z/OS * **************************************************************** * PROBLEM DESCRIPTION: The Cloudscape files db2j.jar and * * db2jtools.jar are missing from the * * $WAS_HOME/lib directory under certain * * installation scenarios. * **************************************************************** * RECOMMENDATION: * **************************************************************** The Cloudscape files db2j.jar and db2jtools.jar are missing from the $WAS_HOME/lib directory in certain installation scenarios. The problem scenarios are those in which WebSphere for z/OS V5.0 was installed at a service level prior to W502000, and then a W502000 or more recent service level of WebSphere for z/OS V5.0 was applied to the pre-existing 5.0 installation. One problem caused by this mistake can occur when using Cloudscape as the database for UDDI, since the resulting setup requires these Cloudscape jars in the $WAS_HOME/lib directory. After setting up UDDI using Cloudscape you might see the following error when subsequently starting up the server: CONM1006E: The data source class name "com.ibm.db2j.jdbc.DB2jConnectionPoolDataSource" could not be found for data source (UDDI.Datasource).Problem conclusion For each of the files db2j.jar and db2jtools.jar, create a link from the runtime $WAS_HOME/lib directory back to the copy of the respective file in the SMP/E install directory (this is only done, however, if it is detected that the user has not already created a copy or link of the given file in the $WAS_HOME/lib directory outside of the WAS install process). APAR PQ91014 is associated with SERVICE LEVEL W502014 of WebSphere Application Server V5.0 for z/OS.Temporary fix Comments
APAR is sysrouted FROM one or more of the following: APAR is sysrouted TO one or more of the following: Modules/Macros
Publications Referenced
|
Document Information |
Current web document: swg1PQ91014.html
Product categories: Software > Application Servers >
Distributed Application & Web Servers > WebSphere Application
Server for z/OS
Operating system(s):
Software version: 500
Software edition:
Reference #: PQ91014
IBM Group: Software Group
Modified date: Sep 3, 2004
(C) Copyright IBM Corporation 2000, 2009. All Rights Reserved.