This documentation supports the 9.1 to 9.1 Service Pack 3 version and its patches of BMC Atrium Core. The documentation for version 9.1.04 and its patches is available here.

To view the latest version, select the version from the Product version menu.

Web services logging

The BMC Atrium Core web services provide logs that can help you to troubleshoot issues related to web service operations.


The BMC Atrium Core web services use the BMC Atrium CMDB APIs to communicate with the AR System server. Therefore, you can also examine the BMC Atrium CMDB API logs for any errors. For more information about the BMC Atrium CMDB API logging, see Server-side API logging.

BMC Atrium Core web services deployment logs

BMC Atrium Core web services deployment logs are located in the AtriumCoreInstallationDirectory/Logs directory.

BMC Atrium Core web service logs

BMC Atrium CMDB web service logs provide information about troubleshooting TIBCO or other web service issues. The web services log files are located in:

  • AtriumCoreInstallationDirectory/shared/tomcat/logs/ if the Tomcat path is bundled with BMC Atrium Core.
  • TOMCAT_HOME/logs if you are using your own Tomcat installation.

The following code is an example of the output from invoking the GetClass method of the atrium_classes web service.

BMC Atrium WS [ INFO ] Thread:1402 Date:2009-08-20T23:20:44.025+0530
Method:getClass Line:1644
+ Operation exited normally
+ Artifacts follow:
<typ:GetClassOutput xmlns:typ="">
<description>Class that stores configuration items (CIs) relating to collections
of managed system elements. The managed system elements provide computing capabilities
and serve as aggregation points to relate one or more of the following elements:
file systems, operating systems, processors, and memory (volatile storage, nonvolatile,
or storage). The BMC_ComputerSystem class is the primary class that you will use to
model the computers in your organization. You can use the attributes in this class to
identify the purpose of each computer CI in your organization. For example,
the class contains several attributes that represent any network-addressable system,
such as a server, a workstation, or a network device (router, switch, hub, load balancer,
firewall, and so forth), as well as mainframes, printers, and virtual systems.
So CMDB planners might use the PrimaryCapability element to define a vendor-specific
switch used in their network, making it easy to import this data from a vendor
as an industry-standard item in their CMDB. They could also define computer systems
further by placing them in one of its subclasses: BMC_Mainframe, BMC_Printer, or
BMC_VirtualSystem.  The BMC_ComputerSystem class corresponds to the DMTF
CIM_ComputerSystem class.</description>
<clas:ClassDeprecationInfo xmlns:clas="">
<mappedClass xsi:nil="true" xmlns:xsi=""/>
Was this page helpful? Yes No Submitting... Thank you