WebSphere Application Server Version 6.1 Feature Pack for Web Services
             Operating Systems: AIX, HP-UX, i5/OS, Linux, Solaris, Windows, z/OS

             Personalize the table of contents and search results

Setting up a customized UDDI node

You set up a UDDI node with your own property values so that it is suitable for production configurations.

About this task

Use this task to set up a UDDI node with property values that you choose. You cannot 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 deploy 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.

Procedure

  1. See the information in Database considerations for production use of the UDDI registry to decide which database system to use, then create a database schema to hold the UDDI registry by completing one of the following tasks. 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 is used for all members of the cluster.
  2. Set up a data source for the UDDI registry application to use to access the database, as described in Creating a data source for the UDDI registry.
  3. Deploy the UDDI registry application, as described in Deploying the UDDI registry application.
  4. [AIX] [HP-UX] [Linux] [Solaris] If you are using DB2, stop the server if it is running. Edit the user profile for the DB2 user that starts the node agent or server. Modify the user profile to run the db2profile script, which is located in the root directory of the DB2 user ID, for example, /home/db2inst1/sqllib/db2profile. Alternatively, you can run the db2profile script manually, but you must do this every time that you restart the node agent or server. Enter the following command:
    . /home/db2inst1/sqllib/db2profile
    Note: There is a single space character after the period in this command.
  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, if the application server is not already running, start the application server. This action automatically starts the UDDI registry application. The UDDI node is now active.
    Note: Restarting the UDDI application, or the application server, always reactivates the UDDI node, even if the node was previously deactivated.

What to do next

Because you chose a user-customized UDDI node, you 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.




In this information ...


Related information

IBM Redbooks, demos, education, and more


Use IBM Suggests to retrieve related content from ibm.com and beyond, identified for your convenience.

This feature requires Internet access.

IBM Suggests
Task topic    

Terms of Use | Feedback

Last updated: Nov 25, 2008 2:35:59 AM CST
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/index.jsp?topic=/com.ibm.websphere.wsfep.multiplatform.doc/info/ae/ae/twsu_user_install.html