Why and when to perform this task
A UDDI Registry node consists of the UDDI Registry application
(a WebSphere Application Server J2EE application), 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 datasource
and related elements). The 'Setting up' sub-topics describe how to create
the database (which can be local or remote) and datasource, and how to deploy
the UDDI Registry application.
You can create either a
default UDDI
node or a
customized UDDI node. The main difference between default
and customized, in the context of these set up tasks, refers to a number of
mandatory UDDI Registry properties such as the UDDI node ID and description,
and the prefix to be used for generated discovery URLs.
- default UDDI node
- the mandatory properties are automatically set to default values and cannot
be changed. 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, but once set they cannot be changed
for this configuration. With a customized UDDI node you 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 datasource to your 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 node,
see Changing the UDDI Registry application environment after deployment.