WAS v8.5 > Administer applications and their environment > Administer web services - UDDI registry > Administer the UDDI registry

Set up and deploying a new UDDI registry

A UDDI registry node consists of the UDDI registry application (an enterprise application supplied as part of WebSphere Application Server), a store of data (using a relational database management system) referred to as the UDDI database, and a means to connect the application to the data (a data source and related elements). To set up a new UDDI registry, you create the UDDI database and data source, and deploy the supplied application.

Start WAS, and create a server to host the UDDI registry. Use the starting and stopping quick reference information for information about starting WAS using either commands or the dmgr console. The subtopics describe how to create the UDDI database (which can be local or remote) and data source, and how to deploy the UDDI registry application.

We can create either a default UDDI node or a customized UDDI node. The main difference between the two nodes is the number of mandatory UDDI registry properties, such as the UDDI node ID and description, and the prefix to use for generated discovery URLs.

Default UDDI node

The mandatory properties are automatically set to default values and we cannot change them. A default UDDI node is a suitable option for initial evaluation of the UDDI registry, and for development and test purposes.

Customized UDDI node

You must set the mandatory properties. After these properties are set, we cannot change them for this configuration. With a customized UDDI node, we have more control over the database management system used for the UDDI database, and the properties used to set up the UDDI database. With a customized UDDI node, you create the UDDI database and data source to our own specifications before deploying the UDDI registry application. A customized node is a suitable option for production purposes. To move from a default UDDI node to a customized UDDI node, see Change the UDDI registry application environment after deployment.

• To set up a UDDI registry quickly for test or development purposes, follow the instructions in Set up a default UDDI node with a default data source. The database, data source, and UDDI registry application are created or deployed by a single script. The database type is embedded Apache Derby.
• To create a default UDDI registry with a database other than embedded Apache Derby, or to use an embedded Apache Derby database but create the data source manually, follow the instructions in Set up a default UDDI node.

• To create a customized UDDI registry, follow the instructions in Set up a customized UDDI node.

Subtopics

• Set up a default UDDI node with a default data source
  You can create a UDDI node with predetermined property values and an embedded Apache Derby database. We can do this to set up a UDDI registry quickly for test or development purposes.
• Set up a default UDDI node
  We can create a UDDI node with predetermined property values. This UDDI node is suitable for initial evaluation of the UDDI registry and for development and test purposes.
• Set up a customized UDDI node
  We can set up a UDDI node with our own properties, including the mandatory node properties. This type of UDDI node is suitable for production purposes.
• Use the UDDI registry installation verification test (IVT)
  We can use an installation verification test (IVT) to verify that we have successfully deployed a UDDI registry.
• Change the UDDI registry application environment after deployment
  We can change the environment of the UDDI registry application after you deploy it. For example, we can evaluate a UDDI registry using one database, then put it into production using a different database.

Related

Start and stop quick reference

+

Search Tips   |   Advanced Search