Troubleshooting Sentinel Communication Issues

  • 3451902
  • 25-Mar-2008
  • 26-Apr-2012

Environment


Solaris 9
Microsoft Windows 2000 Server
Microsoft Windows Server 2003 Enterprise Edition
Microsoft SQL 2005
Microsoft SQL 2000
Sentinel 5.1.xx Sentinel Database Manager
Sentinel 6.0.xx

Situation

Slow quick queries and other reporting issues within SCC

Resolution

Verify all the connections made to Sonic with the Sonic Management Console.

This is a java utility, so you may have to export the display if on Unix.

If you launch the ESEC_HOME\3rdparty\SonicMQ\MQxx\bin\startmc.sh or .bat file depending on OS, on the Sentinel Communication server (eSecurity Communincation) then authenticate with the following:

Connection Name:ESEC
Domain Name:esecDomain
Connection URL:tcp://localhost:10012 (if running local or exporting the display)
User Name:esecadm (on Unix or root) Administrator (Windows or user used to install Sentinel)
Password:respective users password

Once logged in select the Manage tab -> In the pane on the left Double Click on Containers -> Double click on esecContainer -> Double click on esecBroker -> click on Connections and then check or screenshot for support all the connections sorted by Identity (click on Identity column).

Look to see if you have old connections or incorrect hosts that are running that are causing the slow down.

If you have sonic issues then it would explain some of the reporting issues.



A connection can also be made with the list_broker_connections script. The script requires the Sonic server's name/IP and port for parameters and otherwise uses the Sentinel default parameters to connect:

cd $ESEC_HOME/bin
./list_broker_connections.sh hostnameOrIPAddressForSonic 10012

The output can be redirected to a file for later review or to be conveniently sent to a colleague.

Feedback service temporarily unavailable. For content questions or problems, please contact Support.