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
If you intend to run in a single WebSphere Application server, then complete the following task.
When you select the UDDI Registry option, then the installation will place all files that are needed to run a UDDI Registry onto the deployment manager install tree on the machine on which you are installing IBM WebSphere Application Server for Network Deployment.
To be able to run the UDDI Registry in a single application server instance in your network space you must copy these files over to the application server and then deploy the UDDI Registry. You can do this as follows:
Steps for this task
Note: If you set up the UDDI Registry application with a JDBC driver and datasource that reference Cloudscape, but set the persister property in uddi.properties to specify DB2, or vice versa, then some unexpected behavior will result, such as a fatal error on deleting an entity. If this happens, you should check that the above details are not in conflict. This only applies to a UDDI Registry installation on a single appserver.
. /home/db2inst1/sqllib/db2profile
Note: In the above example, it should be noticed 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
Continue with Configuring the UDDI Registry.