This documentation supports the 20.02 version of BMC CMDB.

To view an earlier version, select the version from the Product version menu.

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.


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 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 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 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 CMDB installer configures the correct values for the properties. The following table describes the CMDBWS properties

 
CMDBWS properties

Property

Description

bmc.atrium.arserver.hostname

The hostname of the Remedy AR System server/CMDB to be accessed by the Web services.

bmc.atrium.arserver.port

The port number of the Remedy AR System server/CMDB to be accessed by the Web services.

bmc.atrium.arserver.rpcqueue

The default RPC queue number to be used in accessing the CMDB. This is a global configuration. Client applications cannot set their own values for this property. The default queue number is 0.

bmc.atrium.arserver.defaultlocale

The default locale to be used by Remedy AR System server/CMDB for its human readable status or fault messages. This value can be specified by a client in each operation exposed by the core Web services, but if that value is not passed in at that time, the value specified here is used as the default. Messages specific to CMDBWS are not localized as they are in Atrium Web services, so this setting has no effect on those but rather only on messages from the AR and CMDB. The default locale is en.

bmc.atrium.arserver.defaulttimezone

The default timezone to be used in accessing the Remedy AR System server/CMDB. The default value is 0.

bmc.atrium.arserver.defaulttimeout.normal

The normal timeout value to be used in accessing the Remedy AR System server/CMDB. This is a global configuration. Client applications cannot set their own values for this property. The default value is 0.

bmc.atrium.arserver.defaulttimeout.long

The long timeout value to be used in accessing the Remedy AR System server/CMDB. This is a global configuration. Client applications cannot set their own values for this property. The default value is 0.

bmc.atrium.arserver.defaulttimeout.xlong

The extra long timeout value to be used in accessing the Remedy AR System server/CMDB. This is a global configuration. Client applications cannot set their own values for this property. The default value is 0.

bmc.cmdbws.log.level

The level at which the CMDBWS should log itself. Log messages are written to standard out, meaning that those messages should be included in the console window of Tomcat or one of its standard out logs. Possible values are INFO, ERROR, WARN, DEBUG, and TRACE. The default log level is WARN.


Was this page helpful? Yes No Submitting... Thank you

Comments