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".
This task is part of a parent task Installing and setting up a UDDI Registry. You should complete this task at the appropriate step in the parent task.
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.
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: If you are migrating from an earlier version of the UDDI Registry, and your UDDI20 DB2 database already exists, you should skip this step unless you want to replace the existing database with a new UDDI20 DB2 database. If you do choose to replace an existing database all of your existing UDDI data will be lost. Important: If you do choose to replace the existing UDDI20 database, then there must not be any applications or users accessing the database at the time that you run the UDDI DB2 setup wizard.
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.
Note: If you
have a copy of the file SetupDB2UDDI.jar in your application server directory,
then the application of the base and Network Deployment PTFs will not update
SetupDB2UDDI.jar in your application server directory. You must apply the
PTF for Network Deployment to your DeploymentManager file structure to update
the SetupDB2UDDI.jar located there (in the /UDDIReg/scripts subdirectory),
and then manually copy this jar file to any application server you may wish
to run it on.
If you are planning to use a remote DB2 system on another host 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.
The UDDI DB2 setup wizard used in this task prompts you to provide the DB2 userid and password under which the UDDI Registry database is created and subsequently accessed. Before starting this task, ensure that you have created an appropriate DB2 userid and password. This same userid and password must be used throughout the following steps where the DB2 userid and password is requested.
On Windows this should be a userid and password with administrative privileges. On Unix platforms, you should supply the userid and password of the DB2 instance in which you wish the database to be created.
To create the database you use the UDDI DB2 setup wizard which is supplied as a jar file called SetupDB2UDDI.jar in the UDDIReg/scripts subdirectory, by following these steps::
<AppServer-install-dir>\bin\setupcmdline.bat
For example, C:\Progra~1\WebSphere\AppServer\bin\setupcmdline.bat
. <AppServer-install-dir>/bin/setupCmdLine.sh
source /<AppServer-install-dir>/bin/setupCmdLine.sh
set path=%WAS_PATH%;%path%
export PATH=$WAS_PATH:$PATH
java -jar SetupDB2UDDI.jar
java -jar SetupDB2UDDI.jar -console
Note: The above commands will fail unless your DB2 installation has the correct fix packs applied as listed on the prerequisite page found at http://www-3.ibm.com/software/webservers/appserv/doc/latest/prereq.html
. /home/db2inst1/sqllib/db2profile
On Windows:
startserver server1
On Unix platforms:
. /startServer.sh server1
wsadmin -f appserversetupuddi.jacl uddi-ear-location servername nodename WebSphere-lib-subdirectory dbname db2userid db2pwd db2ziplocation > setupuddi.log
where
For example, on Windows:
C:/Progra~1/WebSphere/AppServer/installableApps/uddi.ear
and on Unix platforms
/opt/WebSphere/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.