Initializing the UDDI registry node
Use this topic to initialize a UDDI registry node after setup or migration.
We must have a UDDI registry node set up, either as a new node, or to use for migrating a UDDI registry v2 node.
We must set some of the properties of a UDDI registry node before you initialize the node. The UDDI registry node properties are in two categories:
- Mandatory node properties that must be set before the UDDI node can be initialized. We can set these properties as many times as we want before initialization. However, after the UDDI node is initialized, these properties are read-only for the lifetime of that UDDI node. It is very important to set these properties correctly.
- All other properties. We can set these properties before and after initialization.
We can configure these properties and initialize the node using the UDDI administrative console or JMX management interface.
Tasks
- Click UDDI > UDDI Nodes > UDDI_node_id to display the properties page for the UDDI registry node.
- Set the mandatory node properties to suitable, and valid, values. These properties are indicated by the presence of an asterisk (*) next to the input field. The following list summarizes the properties. For more information on each property, see the context help of the administrative console.
- UDDI node ID
- This property must be a text string that begins with uddi: and that is unique to this UDDI node. The default value might be suitable, but ensure that it is unique to the UDDI node before we use it.
- UDDI node description
- This property is a text string that describes the node.
- Root key generator
- This property must be a text string that begins with uddi: and that is unique to this UDDI node. The default value might be suitable, but might contain text, such as keyspace_id, that we must modify to match the system. If we use the default value, ensure that it is unique to this UDDI node.
- Prefix for generated discoveryURLs
- This property must be a valid URL.
- If we are migrating from v2 of the UDDI registry, use the following table to complete the following steps:
- Set any properties from the uddi.properties file that must remain the same as v2.
- Set any properties from the uddi.properties file to keep the same value, for example, dbMaxResultCount.
Version 2 UDDI property (which is set in uddi.property file) Version 3 UDDI property (which is set using the administrative console or UDDI Administrative Interface) Recommended Version 3 UDDI property setting dbMaxResultCount Maximum inquiry response set size We can retain the value from v2, change the value, or use the default. persister No equivalent Not applicable. defaultLanguage Default language code Retain the value from v2 operatorName UDDI node ID You must use a valid value for the UDDI node ID. This value is applied to our v2 data as it is migrated. maxSearchKeys Maximum search keys You can retain the value from v2, change the value, or use the default. getServletURLprefix Prefix for generated discoveryURLs Enter a valid value for our configuration, which is the same as the value used for v2. getServletName No equivalent Not applicable. - Set any other properties, such as policy values, to change from the default settings. For an explanation of policies and properties, see the topic about UDDI node settings. Remember that we can also change these properties later.
- Click Apply to save the changes.
Important: Ensure that the mandatory node properties are set to appropriate values and that we have saved them, because we cannot change them after initialization. If we do not save the changes before proceeding to the initialize step, we will have to delete and recreate the database.
- After saving the changes, initialize the UDDI node by clicking Initialize, at the beginning of the pane.
If we are migrating from v2 of the UDDI registry, the v2 data is migrated now. The initialization might take some time to complete; to track its progress, return to the node collection page and click the refresh icon at the beginning of the Status column. Alternatively, open a second administrative console window, and use the refresh icon in the same way. The UDDI node goes through the following states:
- Initialization pending.
- Initialization in progress.
- Migration in progress. This state occurs only if we are migrating.
- Value set creation in progress.
- Activated.
What to do next
If we migrated the node from a previous version, return to the steps in the procedure to migrate to Version 3 of the UDDI registry, to verify that the migration was successful. If we created a new node, follow the steps in Use the UDDI registry installation verification test (IVT) to verify that we have successfully set up the UDDI node.
Use the UDDI registry installation verification test (IVT) UDDI node settings