WebSphere Application Server Network Deployment, Version 6.0.x     Operating Systems: AIX, HP-UX, Linux, Solaris, Windows

Setting up a customized UDDI node

Why and when to perform this task

Use this task to set up a UDDI node with property values that are chosen by you. You will not be able to change the mandatory node properties, such as node ID, after the initialization of the node. Such a node is suitable for production purposes.
Note: If you are deploying the UDDI Registry application into a cluster, and you want to use Cloudscape for your database, you must use the network version of Cloudscape. Embedded Cloudscape is not supported for cluster configurations.

Steps for this task

  1. Review the information in Database considerations for production use of the UDDI Registry to help you decide which database system to use, then create a database schema to hold the UDDI Registry by completing one of the following tasks, ensuring that you do NOT use the default node options where specified:
    Note: If you are creating the UDDI node in a cluster, it is assumed that a single database will be used for all members of the cluster.
  2. Set up a datasource for the UDDI Registry application to use to access the database, as described in Creating a datasource for the UDDI Registry.
  3. Deploy the UDDI Registry application, as described in Deploying the UDDI Registry application.
  4. [Linux][UNIX]If you are using DB2, stop the server if it is running. Edit the user profile for the DB2 user that will start the node agent or server. Modify the user profile to run the db2profile script which is located in the root directory of the DB2 userid (for example /home/db2inst1/sqllib/db2profile). Alternatively you can run the db2profile script manually by entering the following command, however you will need to do this every time you restart the node agent or server :
    . /home/db2inst1/sqllib/db2profile
    Note: In the above example, notice that the '.' is followed by a single space character.
  5. Click Applications > Enterprise Applications to display the installed applications. Start the UDDI Registry application by selecting the check box next to it and clicking Start. Alternatively start the application server if it is not already running; this will automatically start the UDDI Registry application. The UDDI node is now active.
    Note: Restarting the UDDI application, or the application server, will always result in the reactivation of the UDDI node, even if the node was previously deactivated.

What to do next

As you have chosen a user customized UDDI node, you will need to set the properties for the UDDI node using UDDI administration, and initialize the node before it is ready to accept UDDI requests. See Initializing the UDDI Registry node for details.




Sub-topics
Creating a DB2 database for the UDDI Registry
Creating a Cloudscape database for the UDDI Registry
Creating an Oracle database for the UDDI Registry
Creating a datasource for the UDDI Registry
Deploying the UDDI Registry application
Initializing the UDDI Registry node

Related tasks
Setting up a default UDDI node

Related information
UDDI node settings

Task topic    

Terms of Use | Feedback

Last updated: Mar 17, 2005 4:28:29 AM CST
http://publib.boulder.ibm.com/infocenter/ws60help/index.jsp?topic=/com.ibm.websphere.nd.doc/info/ae/ae/twsu_user_install.html

© Copyright IBM Corporation 2002, 2005. All Rights Reserved.
This information center is powered by Eclipse technology. (http://www.eclipse.org)