Use this task to create and load the UDDI Registry database using DB2, and to setup and install the UDDI Registry application to use the database.
Before you begin
To decide which database product you should use as your persistence store, see "Choice of database product to be used as the persistence store".
If you plan to use DB2 for the database in
which the UDDI Registry is held, ensure that the correct prerequisite fix
packs have been applied as listed at
http://www-3.ibm.com/software/webservers/appserv/doc/latest/prereq.html
otherwise
the startup of the UDDI DB2 setup wizard will fail.
To install the UDDI Registry onto the z/OS platform, access Unix System Services (USS), using for example telnet or Open Edition MVS, then issue the Unix commands described in this task.
This task uses the UDDI DB2 setup wizard to configure DB2 on the system where you want to run the UDDI Registry. Before starting this task, ensure that DB2 is installed and running on that system.
Why and when to perform this task
The following steps should be carried out on the system on which the target application server is located (referred to below as the 'target system').
Steps for this task
Note: It
is recommended you use the SetupDB2UDDI.jar command from IBM WebSphere Application
Server Version 5.0.1 or later. This is essential for non-English users.
If you are planning to use a remote DB2 system on another z/OShost machine, copy the SetupDB2UDDI.jar file to the remote system and run it on that system to create and load the UDDI Registry database following the instructions within this step and continue with the next step (which states "If using a remote DB2 system on another host machine ....") on the local host.
To create the database you use the UDDI DB2 setup wizard which is supplied as a shell script called SetupDB2UDDI.sh in the UDDIReg/bin subdirectory, by following these steps::
The UDDI DB2 setup wizard supports two modes of operation:
To initiate this mode of operation, issue the following command from an MVS command line prompt:
/install_root/UDDIReg/bin/SetupDB2UDDI.sh DB2_location_name DB2_database_name DB2_tablespace_name create ccsid DB2_storage_group_name volume_name VSAM_catalog_name
This command should be entered all on a single line. It was split here for formatting purposes.
This mode of operation requires you to specify all of the parameters on the shell script. This enables the DB2 database and tablespace to be created. The newly created database will be primed for use by the UDDI Registry.
Note: If you use the create and load mode of operation, you must run the wizard using a USERID that has the authority to create or update DB2 databases, storage groups, ect. Also, that USERID will be used as the SQLID of the resulting DB2 tables.
To initiate this mode of operation, issue the following command from an OMVS command line prompt:
/install_root/UDDIReg/bin/SetupDB2UDDI.sh DB2_location_name DB2_database_name DB2_tablespace_name skip
This command should be entered all on a single line. It was split here for formatting purposes.
This mode of operation does not require you to specify the DB2_storage_group_name volume_name and VSAM_catalog_name parameters on the shell script. This mode uses the existing DB2 database and tablespace and only primes that database for use by the UDDI Registry.
The output from the UDDI DB2 wizard will be placed in a file called setupDB2UDDI.tracelog. Errors that occur will be written to the user's telnet session.
Note: This command must be entered on a single line. It is split here for display purposes.
wsadmin.sh -f appserversetupuddi.jacl uddi-ear-location servername nodename WebSphere-lib-subdirectory dbname db2userid db2pwd db2ziplocation > setupuddi.log
where
/webSphere/V5R1M0/AppServer/installableApps/uddi.ear
Note: If a remote DB2 system is being used the dbname must be the alias created when access to the remote database was set up on the local system.
The appserversetupuddi.jacl completes the following actions:
Note: The setup script, appserversetupuddi.jacl, cannot be used to install the UDDI Registry application into a clustered application server. It is possible to cluster the UDDI Registry application by installing UDDI into an unclustered application server using the setup script, and then clustering that application server.
What to do next
Return to the next step in the parent task Installing and Setting up a UDDI Registry.