Before you begin
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.
Why and when to perform this task
The diagram following shows an example Network Deployment configuration
on which the examples in this Information Center are based:
In this configuration, several nodes are federated to the Deployment Manager (dmgr) on myhome.headoffice.xyz.com, from which UDDI is deployed to the host myriad.headoffice.xyz.com.
These instructions assume that the installation has been performed into a clean environment. If you are installing into an existing deployment manager cell skip to step 6.
Steps for this task
For example:
jar -x uddi.ear
(This uses the jar command in the <DeploymentManager-install-dir>\java\bin subdirectory of the deployment manager, so you might need to fully qualify the path to the jar command.)
This will allow you to see the permissions which have been granted to the UDDI Registry application, and to make any changes that are necessary. Please note that if you make any errors in changing this file, then the UDDI Registry application might either fail to start, or will encounter errors when trying to execute UDDI requests.
For example:
jar -cf uddi.ear .
Note: NOTE the space and the dot after uddi.ear)
(This uses the jar command in the <DeploymentManager-install-dir>\java\bin subdirectory of the deployment manager, so you might need to fully qualify the path to the jar command.)
On Unix and Linux platforms run the db2profile script before issuing the startServer.sh server1 command. This script is located within the DB2 instance's home directory under SQLLIB and you can invoke it by typing:
". /home/db2inst1/sqllib/db2profile"
Note: In the above example, notice that the '.' is followed by a single space character.
Note: On Unix and Linux platforms the DB2 user must have a db2profile at $HOME/sqllib/db2profile.
What to do next
Advanced use of setupuddi.jacl
A number of symbols are defined at the top of the setupuddi.jacl script. These allow you to control the amount of logging that is performed, and to install multiple instances of the UDDI Registry within the same cell.
The symbols that you can edit are as follows:
Continue with Configuring the UDDI Registry.