Network Deployment (Distributed operating systems), v8.0 > Administer applications and their environment > Administer web services - UDDI registry > Administer the UDDI registry > Set up and deploying a new UDDI registry
Set up a customized UDDI node
We can set up a UDDI node with your own properties, including the mandatory node properties. This type of UDDI node is suitable for production purposes. We can set up a customized UDDI node with property values that you choose. After the node is initialized, you cannot change the mandatory node properties, for example, the node ID.
If you deploy the UDDI registry application into a cluster, and to use an Apache Derby database, use the network version of the Apache Derby database. Embedded Apache Derby is not supported for cluster configurations.
Procedure
- Review the information in Databases and 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.
- 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 database for the UDDI registry
- Create an Oracle database for the UDDI registry
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. - Set up a data source for the UDDI registry application to use to access the database, as described in Create a data source for the UDDI registry.
- Deploy the UDDI registry application, as described in Deploy the UDDI registry application.
- (AIX)
(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, you 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
- 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 application server is not already running, start the application server. This action automatically starts the UDDI
registry application. The UDDI node is now active.
If you restart the UDDI application or the application server, the UDDI node always reactivates, even if the node was previously deactivated.
What to do next
Because you chose a user-customized UDDI node, set the properties for the UDDI node by using UDDI administration, and initialize the node, before it is ready to accept UDDI requests. See Initialize the UDDI registry node for details.
Related
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 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
Initialize the UDDI registry node
Databases and production use of the UDDI registry
Set up a default UDDI node
Set up and deploying a new UDDI registry
UDDI node settings