Group Subscription Registry Configuration

Min. notification interval Minimal interval between notifications provided to a subscriber Sender Pool size Number of stubs ready for notification Transformer Cache Size Number of cached XSLT transformations

2.7. Node

On the Node tab, you can configure UDDI node properties. Figure 42. Registry Configuration - Node Default key generator The Default Key generator tModel allows the Registry to generate keys in the form domain:string instead of only in the form uuid. For example, uddi:mycompany.com:myservice:61c08bf0-be41-11d8-aa33- b8a03c50a862 instead of only 61c08bf0-be41-11d8-aa33-b8a03c50a862. Enter the key of the tModel that is the key generator. For example, if you enter uddi:mycompany.com:myservice:keyGenerator, keys will be generated with the prefix uddi:mycompany.com:myservice:. For more information, please see Section 5.2, Publisher-Assigned Keys in the Users Guide. Operator name The name of the operator of the UDDI node. The default entry for this field is configured during installation. Page 349

2.7. Node

Operational business key The key of the Operational business entity. This entity holds miscellaneous registry settings such as the validation service configuration. Operational business key v2 The key of the Operational business entity in UDDI v2 format. Web UI URL The URL of the Registry Control. tModel deletion If this box is checked then deleted tModels are deleted permanently. Otherwise, tModels are marked as deprecated. Deprecated tModels are visible by direct get tModel call, but do not appear in any search results.

3. Configuration in Database

Oracle Service Registry uses many configuration files. They are stored in REGISTRY_HOME\app\uddi\conf and REGISTRY_HOME\work\uddi\bsc.jar\conf directories. Some of them may be changed during setup or with web interfaces. Each such configuration file is an XML file containing tag config with some information about how the configuration file is used. These attributes are generally recognized: Table 2. Attributes of config tag Default value Optional Meaning Attribute no configuration name name false yes true when the file is local to the cluster node local false yes when true the file is stored in the database on Oracle Service Registry start updateDB true yes when false configuration history is not logged history 2000 yes delay before changes in memory are written to file in milliseconds savingPeriod The most important attribute is name which is the identifier by which Oracle Service Registry tries to find the configuration. Some configuration files have attribute local set to true. That means that the configuration is only used by this Oracle Service Registry and other Registries in the cluster will not share it. Other nodes will have their own independent versions. These cluster nodes are distinguished by the Node ID which is specified inside nodeid.xml. If its value is empty, a unique