Troubleshooting Web Services issues

Web services logging

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

 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
Class:com.bmc.atrium.ws.classes.atrium_classes
Method:getClass
File:atrium_classes.java Line:1644
+ Operation exited normally
+ Artifacts follow:
-------------------------------------------------------------------------
<typ:GetClassOutput xmlns:typ="http://atrium.bmc.com/2009/01/classes/types">
<classInfo>
<properties>
<regular>
<isAbstract>NO</isAbstract>
<exposure>USED_VISIBLE</exposure>
<hiddenPerms/>
<visiblePerms>-1098;-1099;-1090;-1091;</visiblePerms>
<categorizationSubclass>false</categorizationSubclass>
<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>
<isFinal>false</isFinal>
<isSingleton>false</isSingleton>
<author/>
<auditInfo>
<auditType>NONE</auditType>
<qualifierString/>
</auditInfo>
</regular>
</properties>
<indexList/>
<customCharacList/>
<superclassNameId>
<namespaceName>BMC.CORE</namespaceName>
<className>BMC_System</className>
</superclassNameId>
<classId>BMC_COMPUTERSYSTEM</classId>
<classType>REGULAR</classType>
<formName>BMC.CORE:BMC_ComputerSystem</formName>
</classInfo>
<status/>
<extensions>
<clas:ClassDeprecationInfo xmlns:clas="http://atrium.bmc.com/2009/08/extensions/classes">
<classId>BMC_COMPUTERSYSTEM</classId>
<isDeprecated>false</isDeprecated>
<mappedClass xsi:nil="true" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/>
</clas:ClassDeprecationInfo>
</extensions>
</typ:GetClassOutput>
==================================================================

Web Services installation issues

This topic describes installation issues related to Web Services Infrastructure, BMC Atrium Core Web Services, and Web Services Registry.

BMC Atrium Core Web Services is inaccessible on the network

If BMC Atrium Core Web Services is inaccessible on the network, check the \etc\hosts file.

The computer should not resolve its name with the loopback IP address. An entry line like the following could be the cause:

127.0.0.1 ashiko-vm1-rhel5.labs.bmc.com ashiko-vm1-rhel5 localhost.localdomain localhost

To resolve this issue, remove the host name and reboot the computer.

Web Services Registry installation fails

If you are installing all BMC Atrium Core features on a single computer and the installation of Web Services Registry fails,verify that you have the recommended amount of RAM, 6 GB, on that computer.

Web services not restarting after a computer reboot on UNIX

On UNIX, processes related to web services are not started automatically after a computer restart.

1. Make sure that the $ATRIUMCORE_HOME environment variable is defined when BMC Atrium Core components are installed.
2. Start the Tomcat server by using the startup.sh script which islocated at TomcatServerInstallation/bin.

Web services startup issue

If you have installed web applications that use the BMC Atrium CMDB Java APIs on a single application server, you might not be able to run the BMC Atrium Core web services successfully. For example, if you are running the BMC Atrium Console and the BMC Atrium CMDB web service on the same instance of Apache Tomcat, you might encounter this issue. 

Two web applications that use the same java classes to load native object libraries cannot coexist on an application server, unless the native object libraries are pre-loaded from a common location. To resolve this issue, deploy the BMC Atrium CMDB web service and the mid tier on separate application server instances.