ESB Hawk Rules

ESB Hawk rules

Monitoring Archives

04/08/23 2EWMS_PC\ESB\Manuals\ESB Hawk rules.ppt

Monitoring the ESB

• EMS plug-in

• Define sets of Monitoring Archives

• Global settings

• Build a set of hawk rule bases

• Build MARs

• Deploy MARs

• TEC Console

• HAWK codes


EMS plug-in

• To be able to monitor EMS components you need to use an additional EMS plugin for Hawk. This consists of the following files:- tibjmsadmin.jar- tibjmsadmin.hma

• Because of environment specific settings in the hawk micro agents for EMS we changed the set-up at the KLM site. 1. On top of the tibjmsadmin.jar we use the custom jar-file

“AFKL_EMSHawkPlugin.jar”2. To make sure that the correct version of tibjmsadmin.jar is used

the file “hawkagent_[DOMAIN_NAME].tra” is updated• “/appl/tibco/tra/domain/[DOMAIN_NAME]/plugin” is added to

tibco.class.path.extended

• Because of connection issues with a FT EMS server we use 2 hma files for each FT EMS server


Define sets of Monitoring Archives [MAR]

• We defined the following MAR files c.q. Monitoring areas- Infra- CLEver / Logging - Project “INCRA / GenDec”

• Infra contains HRBs for monitoring Administrator and EMS server for BW

• CLEver contains rulebases for monitoring the businessworks engines and EMS queues used

• INCRA / GenDec contains rulebases for monitoring the adapters, businessworks engines and EMS queues used


Global settings

• Environments have environment c.q. domain specific settings

• We want the hawk rulebases independent of these domain specific settings

• The hawk agent is able to use global settings from a file

• We use the following file for loading the domain specific settings into hawk- /appl/tibco/tra/domain/[DOMAIN_NAME]/ domain.settings


Build a set of hawk rule bases [HRB]

• Build a custom HRB

• Replace the custom settings by global settings

• Add the global settings to “domain.settings” on the machine for your domain

• Reload the environment vars on your machine(s)- Monitoring Management

- Hawk Console- Microagents

- RuleBaseEngine- updateExternalVariables

• Test your HRB

• Update files “domain.settings” and reload the environment settings on all machine for all your domains

• Check-in HRB to SVN


Build MARs

• Put your HRBs that you want to go in one MAR together in one directory in SVN (e.g. for Infra)- [SVN_HOME]\trunk\operations\monitoring\hawk\rulebases\

MAR\Infra\HRB\

• Use mar utilty to build your MAR

• Check in MAR file in SVN- [SVN_HOME]\trunk\operations\monitoring\hawk\rulebases\

MAR\


Deploy MARs

• Use Administrator- Monitoring Management

- Monitoring Console - Domain

• Click “Add” select your MAR file

• Select target machines per HRB

• Deploy


TEC Console


HAWK codes for Administrator

HAWK0000: Administrator is running on ${Internal.Agent Name}.

HAWK0001: Administrator not running on ${Internal.Agent Name} - it will be restarted automatically.

XM60 HAWK0002: Administrator could not be restarted automatically on ${Internal.Agent Name} - please take manual action.

XM60 HAWK0003: Multiple instances of Administrator running on ${Internal.Agent Name} - please investigate.


HAWK codes for EMS server for BW

HAWK0010: EMS server for BW is running on ${Internal.Agent Name}.

HAWK0011: EMS server for BW not running on ${Internal.Agent Name} - it will be restarted automatically.

XM60 HAWK0012: EMS server for BW could not be restarted automatically on ${Internal.Agent Name} - please take manual action.

XM60 HAWK0013: Multiple instances of EMS server for BW running on ${Internal.Agent Name} - please investigate.


HAWK codes for CLEver BackendServices

HAWK0100: CLEver BackendServices running on ${Internal.Agent Name}.

HAWK0101: CLEver BackendServices not running on ${Internal.Agent Name} - it will be restarted automatically.

XM12 HAWK0102: CLEver BackendServices could not be restarted automatically on ${Internal.Agent Name} - please take manual action.

XM12 HAWK0103: Multiple instances of CLEver BackendServices running on ${Internal.Agent Name} - please investigate.

XM12 HAWK0104: ${pendingMessageCount} messages on queue ${name} waiting to be processed by CLEverBackendServices.


HAWK codes for CLEver FrontendServices

HAWK0120: CLEver FrontendServices running on ${Internal.Agent Name}.

HAWK0121: CLEver FrontendServices not running on ${Internal.Agent Name} - it will be restarted automatically.

XM12 HAWK0122: CLEver FrontendServices could not be restarted automatically on ${Internal.Agent Name} - please take manual action.

XM12 HAWK0123: Multiple instances of CLEver FrontendServices running on ${Internal.Agent Name} - please investigate.


HAWK codes for ADR00001

HAWK0200: ADR00001-IMS-Adapter running on ${Internal.Agent Name}.

HAWK0201: ADR00001-IMS-Adapter is not running on ${Internal.Agent Name} - it will be restarted automatically.

XM12 HAWK0202: ADR00001-IMS-Adapter could not be restarted automatically on ${Internal.Agent Name} - please take manual action.

XM12 HAWK0203: Multiple instances of ADR00001-IMS-Adapter are running on ${Internal.Agent Name} - please investigate.

XM12 HAWK0204: ${pendingMessageCount} messages on queue ${name} waiting to be processed by IMSAdapter.


HAWK codes for ESB00001

HAWK0210: ESB00001 is running on ${Internal.Agent Name}.

HAWK0211: ESB00001 is not running on ${Internal.Agent Name} - it will be restarted automatically.

XM12 HAWK0212: ESB00001 could not be restarted automatically on ${Internal.Agent Name} - please take manual action.

XM12 HAWK0213: Multiple instances of ESB00001 are running on ${Internal.Agent Name} - please investigate.


HAWK codes for ESO00001

HAWK0220: ESO00001 is running on ${Internal.Agent Name}.

HAWK0221: ESO00001 is not running on ${Internal.Agent Name} - it will be restarted automatically.

XM12 HAWK0222: ESO00001 could not be restarted automatically on ${Internal.Agent Name} - please take manual action.

XM12 HAWK0223: Multiple instances of ESO00001 are running on ${Internal.Agent Name} - please investigate.

Documents

ESB Hawk Rules