CMDBWS and WS-Security

Because CMDBWS does not support any WS-Security features, none of the default WS-Security policies are applied to CMDBWS. Also, you cannot apply the supported WS-Security policies to CMDBWS.


Related topics

Integrating-your-services-with-external-products-by-using-the-CMDB-web-services-API

Any changes made to the policies and keystores as described in other sections affect only CMDB Web Services 7.5.00 and later.

Important

Products that have an existing integration with CMDBWS might not be able to use CMDBWS if you enable SSL using the procedure described in Enabling SSL for transport-level encryption for CMDBWS If, after SSL is applied to the CMDBWS, you encounter any issues with BMC products integrated with BMC Helix CMDB using CMDBWS , you might have to return the CMDBWS to its former configuration without SSL.

CMDBWS is the deprecated Web Services that was released in BMC Helix CMDB 2.1. To support CMDBWS in the Axis2 implementation, the Web application is a modified Axis2-based WAR distribution and contains the CMDBWS Web Service archive prebuilt into it. This Web application should be installed into the same Tomcat instance as the Atrium Web Application. If you need to reinstall or redeploy into that Tomcat instance, the packaged cmdbws.war file is installed in <BMCAtriumCoreInstallationDirectory>/wsc/atriumws91/archives/.

The cmdbws.war file includes the following custom module:

BMCAtriumWSPrerequisiteChecker — This module is globally referenced in the atriumws91.war distribution and affects access to all service endpoints. This module checks that prerequisites are met for BMC Helix CMDB services to run in Tomcat:

  • the CMDB APIs are accessible in a shared lib path in Tomcat
  • the JNI shared native libraries are loadable in Tomcat
  • the Java version is either 1.5 or 1.6,
  • the JRE or JDK is 32-bit.

The installation verifies these prerequisites, so this module is included to check if anything has changed in the Tomcat configuration since installation that would affect these prerequisites. If the prerequisites do not pass, a SOAP:Fault message is sent as a response from the Web Services that describes the failures.

To configure CMDBWS

The Axis2-based implementation of CMDBWS does not share runtime properties with CMDB Web Services, and you do not configure it through Atrium Service Configuration Service. Instead, CMDBWS has its own properties file: <BMCAtriumCoreInstallationDirectory>\wsc\cmdbws directory\cmdbws.properties.

The CMDBWS implementation reads this file each time an operation is called. CMDBWS immediately picks up any property changes in the Web service without restarting the server.

The BMC Helix CMDB installer configures the correct values for the properties. The following table describes the CMDBWS properties

 
CMDBWS properties


 

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