Troubleshooting Guide › Troubleshooting the Reporting Service › How to Troubleshoot the Reporting Service › Troubleshoot the Distribution Server

Troubleshoot the Distribution Server

On the Distribution Server, the Message Queue receives information that the Report Agents send from the endpoints. Message-driven Java beans (MDBs) then read the data in the Message Queue and write the data to the central database.

To troubleshoot the Distribution Server

1. (UNIX) Start the Tibco EMS Administration Tool, as follows:
   1. Navigate to the following directory:

      /opt/CA/AccessControlServer/MessageQueue/tibco/ems/5.1/bin
      

   2. Run the following command:

      ./tibemsadmin
      

2. (Windows) Start the Tibco EMS Administration Tool, as follows:
   1. Navigate to the following directory:

      C:\Program Files\CA\AccessControlServer\MessageQueue\tibco\ems\5.1\bin
      

   2. Run the following command:

      tibemsadmin.exe
      

3. Connect to the current environment, using one of the following commands:
   • If the Distribution Server listens for the Report Agent on port 7222 (the default port), use the following command:

     connect
     

   • If the Distribution Server listens for the Report Agent in SSL mode on port 7243, use the following command:

     connect SSL://7243
     

4. Enter your username and password.

   Note: The default username is admin, and by default the password is the communication password that you specified when you installed CA Access Control Enterprise Management or the Distribution Server.

   You are connected to the Message Queue on the Distribution Server.

5. Enter the following command:

   show queues
   

   A list of the queues on the Distribution Server appears.

6. Open a command prompt window on an endpoint.
7. (UNIX) Set the library path environment variable, as follows:
   1. su to root.
   2. Set the library path environment variable to ACSharedDir/lib. By default, ACSharedDir is the following directory:

      /opt/CA/AccessControlShared
      

   3. Export the library path environment variable.
8. (UNIX) Navigate to the following directory:

   ACSharedDir/bin
   

9. Run the Report Agent on the endpoint. Do one of the following:
   • (Windows) Run the following command:

     ReportAgent -report snapshot
     

   • (UNIX) Run the following command:

     ./ReportAgent -report snapshot
     

   The Report Agent sends a snapshot of the CA Access Control database and any local PMDBs to the report queue on the Distribution Server.

10. Observe the queue named queue/snapshots in the tibemsadmin utility as the Report Agent runs.

    If the queue grows and does not shrink, JBoss may not be running. You must troubleshoot JBoss.