This documentation supports the 21.05 version of BMC Helix CMDB.To view an earlier version, select the version from the Product version menu

About the UDDI for BMC Helix CMDB web services

In BMC Helix CMDB, the UDDI Registry Server is based on the Apache jUDDI Registry Server. The BMC Helix CMDB UDDI Registry Server supports multiple Action Request System users as registry consumers. 

UDDI Registry Server functionality and supported features

  • The local user (root publisher) of the server is local to the Universal Description, Discovery and Integration (UDDI) server, not external, and has administrator publishing privileges.
  • One specific AR System user for the AR System server that is linked to the BMC Helix CMDB Core UDDI Registry Server can be designated as having administrator publishing privileges using that account's Action Request System credentials.

Note

The BMC Helix CMDB installer uses the Action Request System administrator used for installation operations as this user, but you can change it to another Action Request System user.

  • All AR administrators for the AR System server that are linked to the BMC Helix CMDB UDDI Registry Server have access with administrator publishing privileges using their AR credentials. 
  • All other AR users for the AR System server that are linked to the BMC Helix CMDB UDDI Registry Server can have access to perform queries using their AR credentials. 

For more information, see Modifying-the-administrator-username-and-password-used-by-web-services.


New features in the UDDI Registry Server

  1. UDDI is upgraded from version 3.0.4 to version 3.3.7.
  2. Previously, UDDI depended on a configuration file called juddiv3.properties for any configuration parameter. This approach was changed by Apache for any 3.2.X or later versions, and they started using an XML file named juddiv3.xml. As a result, if there are any test cases which specifically check for the configuration file, then those test cases must refer to the XML file instead of the properties file.
  3. Previously there was no limit on the number of web services that could be published. In version 3.3.7, UDDI Registry server has started checking the number of web services being published, and there is a limit of 100 web services that can be published. 
  4. Additionally, a new feature called replication is added in jUDDI, which is  a mechanism for maintaining data ownership and data synchronization across multiple UDDI nodes. The configuration file name is root_replicationConfiguration.xml. But because in BMC Helix CMDB, the UDDI Registry server has only one node, this feature is not enabled.





 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*