This topic contains details of the general properties that you can configure for a UDDI node.
To view this administrative console page, click UDDI > UDDI Nodes > UDDI_node_id.
By clicking on a node in the UDDI node ID column the UDDI node detail page is displayed. The UDDI node detail page displays a set of General Properties for the UDDI node, some of which may be editable depending on the state of the node. There are also links to Additional Properties (Value sets, Tiers and UDDI Publishers) and links to Policy Groups where you can view and change UDDI node policy.
Unless you installed the UDDI node as a default UDDI node (as defined in UDDI registry terminology), there are some important general properties that set before you can initialize the UDDI node. These properties are marked as being required (indicated by the presence of a '*' next to the input field). You may set the values as many times as you wish before initialization. However, after you initialize the UDDI node, these properties will become read only for the lifetime of that UDDI node. It is very important to set these properties correctly. You can set other general properties of the UDDI node before, and after, initialization.
After you set the general properties to appropriate values, click OK to save your changes and exit the page, or Apply to save your changes and remain on the same page. At this point the changes are stored.
If the UDDI node is in the Not Initialized state, indicated on the UDDI node detail page by the presence of an Initialize button (above the General Properties section), you can initialize UDDI node by clicking Initialize. This operation can take a while to complete. It is important to save any changes you made to the general properties by clicking Apply or OK, before you click Initialize.
Unique identifier that is given to a UDDI node in a UDDI registry. The node ID must be a valid UDDI key. The value will also be the domain key for the UDDI node.
The value for the node ID will also be the domain key for this UDDI node.
| Required | Yes |
| Data type | String |
| Default | uddi:cell_name:node_name:server_name:node_id |
Specifies the description of this UDDI node.
| Required | Yes |
| Data type | String |
| Default | WebSphere UDDI registry default node |
Specifies the root key space of the registry. Registries intending to become affiliate registries might want to specify a root key space in a partition below the root key generator of the parent root registry, for example, uddi:thisregistry.com:keygenerator.
| Required | Yes |
| Data type | String |
| Default | uddi:cell_name:node_name:server_name:keyspace_id:keygenerator |
Specifies the URL prefix that is applied to generated discoveryURLs in businessEntity elements, so they can be returned on HTTP GET requests. This property applies to UDDI version 2 API requests only. Set this prefix to a valid URL for your configuration, and do not change it unless absolutely necessary.
The format is http://hostname:port/uddisoap/, where uddisoap is the context root of the UDDI version 2 SOAP servlet.
Although this field is not required, you should set it so that the required and valid URL is generated in response to version 2 GET requests. After you have set the prefix you should not alter it unless a subsequent configuration change renders it invalid; if you change the prefix, discoveryURLs generated using the earlier prefix will no longer work.
| Required | No |
| Data type | String |
| Default | http://localhost:9080/uddisoap |
Specifies the host name root used by the UDDI node to model API services in its own node business entity. This value must be the fully qualified domain name, or IP address, of the network host.
The UDDI node provides Web services that implement each of the UDDI API sets that it supports. The host name is used to generate access point URLs in the bindingTemplate elements for each of the services. The access point URL is generated by prefixing the host name value with a protocol, such as http, and suffixing it with the corresponding host port number. The access point URL must resolve to a valid URL.
| Data type | String |
| Default | localhost |
Port number used to access UDDI node services with HTTP. This port number must match the WebSphere Application Server port for HTTP requests.
| Data type | Integer |
| Default | 9080 |
Port number used to access UDDI node services with HTTPS. This port number must match the WebSphere Application Server port for HTTPS requests.
| Data type | Integer |
| Default | 9443 |
Specifies the maximum size of result set which the registry will process for an inquiry API request.
If the result set exceeds this value, an E_resultSetTooLarge error is returned to the user. If you set this value too low, and users use imprecise search criteria, the likelihood of receiving an E_resultSetTooLarge error is increased. Setting the value higher allows larger result sets but can cause increased response times.
| Data type | Integer |
| Default | 500 |
| Range | 0 to 1024 |
Specifies, for inquiry API requests, the maximum number of results returned in each response. Do not set this value higher than the value for Maximum inquiry results.
If the result set contains more results than this value, the response will include only a subset of those results. The user can retrieve the remaining results using the listDescription feature as described in the UDDI specification. If you set this value too low, the user has to make more requests to retrieve the remainder of the result set.
| Data type | Integer |
| Default | 500 |
| Range | 0 to 1024 |
Specifies the maximum number of names that can be supplied in an inquiry API request. To avoid slowing UDDI node response times, set this value no higher than 8.
Higher values allow more complex requests to be processed by the UDDI node, however complex requests can significantly slow the response times of the UDDI node.
| Data type | Integer |
| Default | 5 |
| Range | 1 to 64 |
Specifies the maximum number of keys that can be supplied in an inquiry API request. To avoid slowing UDDI node response times, set this value no higher than 5.
This value limits the number of references that can be specified in categoryBag, identifierBag, tModelBag and discoveryURLs.
Higher values allow the UDDI node to process more complex requests, however complex requests can significantly slow the response times of the UDDI node. In exceptional cases, the UDDI node may reject complex requests with excessive numbers of keys even if the value of maxSearchKeys is not exceeded.
| Data type | Integer |
| Default | 5 |
| Range | 1 to 64 |
Specifies whether tModel:keyGenerator requests must be digitally signed.
| Data type | Boolean (check box) |
| Default | False (cleared) |
Specifies whether an approval manager is used to check publication tier limits. If you set this value to false, the number of UDDI entities that can be published is unlimited.
| Data type | Boolean (check box) |
| Default | True (selected) |
Specifies whether authInfo contents in UDDI API requests are used to validate users when WebSphere Application Server security is off. If you set this value to true, the UDDI node will use the authInfo element in the request, otherwise the default user name is used.
| Data type | Boolean (check box) |
| Default | True (selected) |
Period, in minutes, after which an authentication token is invalidated and a new authentication token is required.
Set this value high enough to allow the registry to operate successfully, but be aware that high values can increase the risk of illegal use of authentication tokens.
| Data type | Integer |
| Default | 30 |
| Range | 1 to 10080 minutes (10080 minutes = 1 week) |
Specifies whether UDDI publishers are automatically registered and assigned to the default tier. Automatically registered UDDI publishers are given default entitlements.
| Data type | Boolean (check box) |
| Default | True (selected) |
User name used for publish operations when WebSphere Application Server security is disabled and Use authInfo credentials if provided is set to false.
| Data type | String |
| Default | UNAUTHENTICATED |
Specifies, for UDDI version 1 and version 2 requests, the default language code to be used for xml:lang, when not otherwise specified.
| Data type | String |
| Default | en |