MustGather documents for ClearCase Remote Client (CCRC) version 7.1

• General Change Management Server Collector: Gathers information for general issues relating to CM Server. This includes CM Server configuration, IBM Installation Manager, and information related to the embedded IBM WebSphere Application Server.
• Server Configuration Collector: Gathers only CM Server configuration information.
• Server Processes Trace Collector: Enables process tracing on the CM Server. You are prompted to recreate the server issue found. Then continue to use the data collection tool to disable trace settings and gather information.

RATIONAL_HOME refers to the location where Rational products are installed.

• On Windows: C:\Program Files\IBM\RationalSDLC

• On the UNIX system and Linux: /opt/IBM/RationalSDLC


• On Windows:  C:\Program Files\IBM\RationalSDLC\common

• On the UNIX system and Linux: /opt/IBM/RationalSDLC/common

/opt/rational

/opt/rational/common

1. Check that the system requirements are met. For more information, see tech note 1302974.

2. Verify that IBM HTTP Server (IHS) is running by accessing the following URL:

http://<server_name>

If the service is running, the following welcome message appears:

Rational Web Platform: If you see this page, it means that Rational Web Platform was installed and is running on this system.


http://<server_name>/TeamWeb/services/Team

If the service is running, the following welcome message appears:
Hi there, this is a Web service!

4. Verify that the RPC services are running. See the topic Checking RPC Servers in the ClearCase Information Center.


http:// <server_name>/TeamAdminWeb


In the login prompt, specify the CM Server host name and the SOAP port number 12880. If the CM Server is hosted on your own IBM WebSphere Application Server, the SOAP port is 8880. Click Connect to log in to the utility.

Click Site Administration > Configuration, select the CM Server Options tab, and enter the values suggested by the Support Engineer for the CCRC tracing subsystem and CCRC trace level fields. Then click OK.

3. Stop the CM Server and service. See the topic "Starting, stopping, and restarting CM Server" in the ClearCase Information Center.

Attention: Performing this step will also stop the ClearQuest Web server and CM API operations if these are hosted on the same computer.

• <RATIONAL_COMMON>\CM\profiles\cmprofile\logs
  
  The contents of this directory must include the ffdc directory. This directory contains the First Failure Data Capture logs.
• <RATIONAL_COMMON>\eWAS\logs
• <RATIONAL_COMMON>\IHS\logs

If instructed by a ClearCase Support Engineer, gather the CM Server MBean configuration data. See the section Gathering diagnostic logging and information for CM Server below .

Sometimes you need to gather diagnostic information for the CM Server as well as the CCRC client and server components. The next sections describe how to prepare CM Server diagnostic information.

Collecting MBean attribute information

You can configure CM Server using a different variables called MBean attributes. If you experience problems with CCRC or CM Server, verify that these attributes are set correctly. Incorrect attribute values can cause problems.

Use the following instructions to send IBM Support a summary of your custom MBean configuration settings:

1. Locate the following directories:

• On Windows 7.1.0.x:
  
  <RATIONAL_COMMON>\CM\profiles\cmprofile\config\cells\
  <host>CMProfileNode01Cell\
  nodes\<host>CMProfileNode01Cell\servers\server1\stp
  

• On Windows 7.1.1.x:
  
  <RATIONAL_COMMON>\CM\profiles\cmprofile\config\cells\
  dfltCell\nodes\dfltNode\servers\server1\stp
  

• On the UNIX system and Linux:
  
  <RATIONAL_COMMON>/CM/profiles/cmprofile/config/cells/
  dfltCell/nodes/dfltNode/servers/server1/stp
  

Attention: If the directory stp does not exist, then you have not established any custom MBean attributes and thus cannot gather this data.

2. The files described in step 1 store the current MBean attributes configured for CM Server. Collect all of the files in this directory.

Further information on MBean configuration

You can find more information about MBEAN configuration in the following documents:

• The Setting available MBean attributes topic in the ClearCase Information Center.
• Technote 1384772 - Change Management Server MBean Attributes -- Information Center Corrections.
• Technote 1384746 - Preserve the CM Server configuration before customizing the MBean attributes or upgrading from or reinstalling ClearCase and ClearQuest version 7.1.0.x

Increasing CM Server logging levels

This section describes how to increase the logging level detail. By changing the logging level, you increase the trace output and diagnostic information in the CM Server logs. This section also describes how to verify that the file count and file size of the logs are sufficient to reproduce a problem during a trace.

Because increasing the diagnostic details can affect system performance, limit this activity to short time intervals. Remember to restore logging to the original settings when such details are not needed.


http://<server_name>:<port>/ibm/console


The default port for CM Server is 12060. The default port for CM Server hosted on your own IBM WebSphere Application Server is 9060.