Installing the UDDI Registry into a deployment manager cell

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:A pictorial image showing the DMGR Server communicating with server1 on which the UDDI database is installed

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

  1. Install the WebSphere Application Server for Network Deployment package, and select Deployment Manager and UDDI Registry options (under Web Services).
  2. Install one or more base application servers which will form the cell of servers. One of these should be the application server in which you plan to run an instance of the UDDI Registry. You can run more than one instance of the UDDI Registry within a cell of servers: the UDDI Registry application name is suffixed with the target node and server names to make it unique within the cell (See also "Advanced use of setupuddi.jacl"), but you can only run one UDDI instance within each application server.
  3. Ensure that the target application server is stopped.
  4. Run startManager (startManager.sh on Unix and Linux platforms) on the deployment manager node to start the deployment manager.
  5. Run addNode (addNode.sh on Unix and Linux platforms) on each of the base application server(s) to add it as a node into the cell. (How to run addNode is described elsewhere in the Information Center - see addNode command). For example: addnode myhome- where myhome is the IP name of your deployment manager host.
  6. Copy the uddiejbclient.jar file and the EJB javadoc directory tree from the UDDIReg/ejb subdirectory of the deployment manager install tree onto any machine(s) where you will be creating EJB clients to access the UDDI Registry.
  7. If you have any global configuration properties that are common to any UDDI Registries that you install into this cell, you can edit the uddi.properties file in the properties subdirectory of the deployment manager install tree to set them up. (See the section on Configuring global UDDI properties for more details about the global configuration properties).
  8. If required, edit the security permissions for the UDDI Registry application. You should only do so if you have a thorough understanding of Java 2 security issues, and the way in which security permissions are used by WebSphere.
    The permissions for the UDDI Registry application are set within the was.policy file, which is part of the uddi.ear. To see and change the contents of this file you should:
    1. On the deployment manager, copy the uddi.ear file from the installableApps subdirectory of the deployment manager install tree into a temporary directory.
    2. Un-jar the uddi.ear file (that is unpack uddi.ear using the 'jar -x' command).

      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.)

    3. You will find the was.policy file under the META-INF subdirectory that is created.

      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.

    4. Re-jar the uddi.ear file using the jar command.

      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.)

    5. Copy the new uddi.ear back to the installableApps directory.
  9. Note that if the target application server is running, this step will stop and restart it. If you are planning to use Cloudscape for the database in which the UDDI Registry will be held, please read the section "Setting up the UDDI Registry to use Cloudscape within a deployment manager cell" and then return to this point. If however, you plan to use DB2, then please refer to the section "Setting up the UDDI Registry to use DB2 within a deployment manager cell" and then return to this point.
  10. Ensure that the UDDI Registry is configured appropriately for your installation, as described in the section on Configuring the UDDI Registry.
  11. Start, or stop and restart, the target application server. This should also start the UDDI Registry application. If not, use the administrative console on the deployment manager to do so.

    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.

  12. Your UDDI application is now ready to use. Go to the User Console section within this Information Center or any of the API sections.

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.


Related tasks
Installing and setting up a UDDI Registry



Searchable topic ID:   twsu_install_dmc
Last updated: Jun 21, 2007 8:07:48 PM CDT    WebSphere Business Integration Server Foundation, Version 5.0.2
http://publib.boulder.ibm.com/infocenter/wasinfo/index.jsp?topic=/com.ibm.wasee.doc/info/ee/ae/twsu_install_dmc.html

Library | Support | Terms of Use | Feedback