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 UDDI node policy may be viewed and changed.
Unless the UDDI node has been installed as a default UDDI node (as defined in UDDI Registry terminology) there are some important general properties that need to be set before the UDDI node can be initialized. These properties are all 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, once the UDDI node has been initialized, these properties will become read only for the lifetime of that UDDI node. It is very important to set these properties correctly. Other general properties of the UDDI node may be set before, and after, initialization.
Once the general properties have been set to appropriate values, you can click OK (which saves your changes and exits the page), or Apply (which saves your changes and leaves you on the same page). At this point the changes will have been 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), the UDDI node can be initialized by clicking the Initialize button. This operation may take a while to complete. It is important to remember to save any changes you have made to the general properties by clicking Apply or OK before the Initialize button is pressed. The other UDDI settings that a UDDI administrator can manage are shown to the right of the screen and are described in the following topics:
This topic contains details of the value sets settings that you can configure for a UDDI node.
This topic contains details of the UDDI publisher tiers that you can configure for a UDDI node.
This topic contains details of the publishers that have been registered with the UDDI node.
This topic contains links to the detailed settings information for every policy group that you can configure for a UDDI node.
Runtime tab
The unique identifier given to a UDDI node in a UDDI registry. This must be a valid UDDI key.
The value for the node ID will also be the domain key for this UDDI node.
| Required | Yes |
| Data type | String |
| Default | A valid domain key for this UDDI node |
The user supplied description of this UDDI node.
| Required | Yes |
| Data type | String |
The root key space of the registry.
Registries intending to become affiliate registries may 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:default:keygenerator |
The URL prefix for the GET servlet.
The URL prefix applied to generated discoveryURLs in businessEntity elements so they can be returned on HTTP GET requests. The format is 'http://hostname:port/uddisoap/', where 'uddisoap' is the UDDI version 2 SOAP servlet's context root. This property applies to UDDI version 2 API requests only.
| Required | Yes |
| Data type | String |
| Default | http://localhost:9080/uddisoap |
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. Setting the value higher allows larger result sets but may cause increased response times.
CAUTION:
If this value is set too low users will get an E_resultSetTooLarge error message, whereas setting to too high might cause increased response times. If the value is set too low and users use imprecise search criteria the likelihood of receiving the E_resultSetTooLarge is increased.
| Data type | Integer |
| Default | 500 |
| Range | 0 to 1024 |
For inquiry API requests, this value controls the maximum number of results returned in each response. If the number of results in the result set is greater than this value, the response will only include a subset of results. The user can retrieve remaining results using the listDescription feature as described in the UDDI specification. Setting this value too low will require the user to make more requests to retrieve the remainder of the result set.
CAUTION:
This value can not be higher than the value set for "Maximum inquiry results". Setting this value too low increases the number of requests needed to achieve the full result set.
| Data type | Integer |
| Default | 500 |
| Range | 0 to 1024 |
The maximum number of names that can be supplied in an inquiry API request. Increasing this value can significantly slow response times of the UDDI node.
This can be used to control the complexity of requests that this UDDI node will allow. The recommendation is to not set this value above 8.
| Data type | Integer |
| Default | 5 |
| Range | 1 to 64 |
The maximum number of keys that can be supplied in an inquiry API request. This limits the number of references that can be specified in categoryBag, identifierBag, tModelBag and discoveryURLs. Increasing this value can significantly increase response times for the UDDI node.
This can be used to control the complexity of requests that this UDDI node will allow. The recommended setting for this is 5 or less.
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 |
Whether tModel:keyGenerator requests must be digitally signed.
Whether an approval manager is used to check publication tier limits.
If set to false, the number of UDDI entities that can be published is unlimited.
Specifies if authInfo contents in UDDI API requests are used to validate users when WebSphere global security is off. If this setting is true, the UDDI node will use the request's authInfo element, otherwise the default user name is used.
| Data type | Integer |
| Default | True |
The period after which authentication tokens are invalidated (in minutes), and a new authToken is required.
CAUTION:
The setting should be sufficient to ensure operational success. Longer settings can increase the risk of illegal authToken use.
| Data type | Integer |
| Default | 30 |
| Range | 1 to 10080 (minutes - 1 week) |
Specifies if UDDI publishers are automatically registered, and assigned to the default tier.
Automatically registered UDDI publishers are given default entitlements.
The user name used for publish operations when WebSphere security is disabled.
| Data type | String |
| Default | UNAUTHENTICATED |
Applies only to 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 |
Related information
Administrative console buttons
Administrative console page features