Set up a customized UDDI node


 

+

Search Tips   |   Advanced Search

We can set up a customized UDDI node with property values that you choose. After the node is initialized, we cannot change the mandatory node properties, for example, the node ID.

If we deploy the UDDI registry application into a cluster, and you want to use an Apache Derby database, use the network version of the Apache Derby database. Embedded Apache Derby is not supported for cluster configurations.

New feature: In WAS ND v7.0, Microsoft SQL Server 2005 is supported as a database for the UDDI registry

 

  1. Review the database considerations for production use of the UDDI registry to decide which database system to use

  2. Create a database schema to hold the UDDI registry using one of the following...

    Do not use the default node options where specified.

    If we are creating the UDDI node in a cluster, it is assumed that a single database is used for all members of the cluster.

  3. Set up a data source for the UDDI registry application to use to access the database.

  4. Deploy the UDDI registry application, as described in Deploy the UDDI registry application.

  5. [AIX] [HP-UX] [Linux] [Solaris]

    For a DB2 database, 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, we can run the db2profile script manually, but do this every time that you restart the node agent or server. Enter the following command (there is a single space character after the period in this command):

    . /home/db2inst1/sqllib/db2profile
    

  6. Click Applications > Application Types > WebSphere enterprise applications to display the installed applications. Start the UDDI registry application by selecting the check box next to the application name and clicking Start. Alternatively, if the appserver is not already running, start the appserver. This action automatically starts the UDDI registry application. The UDDI node is now active.

    If we restart the UDDI application or the appserver, the UDDI node always reactivates, even if the node was previously deactivated.

 

Next steps

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


Create a DB2 distributed database for the UDDI registry
Create a DB2 for z/OS database for the UDDI registry
Create an Apache Derby database for the UDDI registry
Create a Microsoft SQL Server 2005 database for the UDDI registry
Create an Oracle database for the UDDI registry
Create a data source for the UDDI registry
Deploy the UDDI registry application
Initializing the UDDI registry node

 

Related tasks


Set up a default UDDI node
Set up and deploying a new UDDI registry

 

Related information


UDDI node settings