Cognizant_configure Domain Hawk Agent

7/27/2019 Cognizant_configure Domain Hawk Agent

1/26

Page 1 of36

5.1 CONFIGURE DOMAIN HAWK AGENT

Inthisstep, Domain Hawk agent is configured to use EMS server as itstransport and also

to communicatewith Hawk event service.

a) Open the /tra/domain//hawkagent.cfg file in a

text editor

b) Underems_transport property, specifythe EMS server connectiondetailsas,shownbelow.

-ems_transport tcp://:port #!encryptedpassword

c) In order to communicate with Hawk event service, add the ami_rvd_session

that matches with that of Hawk event services ami_rvd_session. (Steps to

configure the Hawk event service with the same parameters is mentioned in a

latersection)

Forexample,-ami_rvd_session 8500 127.0.0.1 tcp:8500

d) Save the changes.

Note: The encrypted password can be generated by running the Hawk utility

program tibhawkpassword locatedin yourhawk/bindirectory:

tibhawkpassword-encrypt password

where password is the current password

5.2 RENAME DEFAULT HAWK AGENT

In this step, Hawk agent that comes with standalone installation is renamed so that the

two Hawk agents (one that comes with standalone Hawk installation and another one

that comes with TIBCO Admindomain)can be distinguishedin the HawkDisplay.

a) Open the /hawk/bin/hawkagent.cfgfile in a text editor

b) Change the agent name as mentionedbelow.

-agent_name _default

c) Underthe ems_transport, specifythe EMS server connectiondetails




2/26

Page 1010 of

5.3 MONITOR AND MANAGE EMS SERVER FROM HAWK

To use TIBCO Hawk to manage the TIBCO Enterprise Message Service server, load the

HawkController or HawkListenerclasses provided into the TIBCO Hawk agent. Once the

classes are loaded, methods for managing the EMS server are available in the

TIBCO Hawk display. In this implementation, the HawkController classes have been

loaded.

Installing the classes is different for UNIX and Windowsplatforms. Given below are the

steps for installing the classes in UNIX. Please refer to Hawk documentation for

theprocedure on Windows.

a) Locate the tibjmsadmin.hma file in the TIBCO EMS installation directoryunder the /ems/samples/admin/hawk subdirectory and copy it toTIBCO TRA Hawkpluginsdirectory.

Usually, TIBCO TRA Hawk plugins directory is located in

/tra/domain//plugin

b) Locate tibjmsadmin.jar in the ems/clients/java subdirectory, and copy it intothe TIBCO TRA Hawkpluginsdirectory.

c) Open the /tra/domain//hawkagent.cfg file in a

text editor and specify the -hma_plugin_dir option to include the directory where

yourTIBCO Hawkpluginsare located.

-hma_plugin_dir"/tra/domain//plugin"

Save changes to hawkagent.cfg

d) Navigate to plugins directory and open the tibjmsadmin.hma file in a text

editor

e) Specify the TIBCO Hawkmicroagentclassyou wish to use in the

element. In this implementation,

com.tibco.tibjms.admin.hawk.HawkControllerhas been used.

f) Specify the username and password and serverURL to use to connect to the

TIBCO EMS server in the appropriate elements For example:

-useradmin

-passwordMyPassword

-servertcp://:


3/26

Page 1111 of

-timeout


4/26

Page 1212 of

5

You should use specify thepredefined admin useror a user that is a member of

the $admingroup.

Save changes to tibjmsadmin.hma.

Note: To use an encrypted password, specifyencryptedPassword instead of

-password. As the value for -encryptedPassword, supply the output you obtainby

running the Hawk utility program tibhawkpassword located in your hawk/bin

directory:

tibhawkpassword-encrypt password

where password is the current password

5.4 MONITORING EVENT SERVICE FROM HAWK

The TIBCO Hawk Event Service is a process that records TIBCO Hawkalertsand changes

in agent status. When communicationwith an agent is lost,the Event Servicecan invoke

a user-providedscript.Alertsand notificationscan be recorded to log files or a database.

Typically, the TIBCO Hawk Event Service is installed on a minimal number of computers

in the network.

Inthis step, Hawk event serviceis configured to use EMS server as its transport and also

to communicatewith Hawk agent service.

a) Open the /hawk/bin/hawkevent.cfgfile in a text editor

b) Underthe ems_transport, specifythe EMS server connectiondetails.


c) Also specify the TIBCO Rendezvous session used by the TIBCO Hawk event

service for AMI communications.

Forexample,

-ami_rvd_session 8500 127.0.0.1 tcp:8500


5.5 RESTART HAWK SERVICES

Save all the above changes and restart the following servicesso that the changes will be

effective.


5/26

Page 1313 of

a) Hawk agent servicethat comes with standalone installation

b) Domain Hawk agent service

c) Hawk event service

5.6 CONFIGURE HAWK DISPLAY FOR EMS TRANSPORT (ON WINDOWS)

Inthisparticularimplementation,Hawk Display runningon Windows is configured to use

EMS transport.

Open the Hawk Configuration window from menu and configurethe following.

a) Ensure that Hawk Domain name matches with that of domainname mentioned in

the Domain Hawkagentshawkagent.cfg

b) In the Transport tab, select the Primary Transport as EMS and provide the EMS

server connection details. This should be the same EMS server that was

configured in Step5.1

c) Click Ok


6/26

Page 1414 of

d) Click No on the dialogsthat askfor restartingthe Hawk relatedservices.

Now open the Hawk Display from menu to verify that all the changes are done

successfully.

6. RULEBASES

6.1 PRE-REQUISITES

The many new Hawk rulebases,command procedures, etc. need to be separate from the

core TIBCO and Hawk products. This will allow TIBCO Hawk to be upgraded

independently from the custom components and vice-versa. Given below are the pre-

requisites for the rulebases.

6.1.1 FOLDER STRUCTURE

Create the following folder structure under TIBCO domain root (i.e.

/tra/domain/)

----Accelerator

-flags (Location of .enabledand .running files)

-scripts(Location of custom command procedures)

6.1.2 COMMAND PROCEDURES

The BW and ADB Adapter rulebases use Command Procedures to perform some actions.

To track the status of BW process engine or ADB adapter .enabledand .running files will

be created and deletedin the flagsfolder,using these Command Procedures.

UNIX shell script files namely CreateEmptyFile.sh and RemoveFile.sh will be used

forcreating and deleting the appropriate files. If running on Windows the equivalent

batch scripts need to be prepared. At any point of time, Hawk rulebase will identify the

status of BW process engine or ADB adapter based on the availability of one orboth of

these

files and takes the necessary action.

CreateEmptyFile.sh RemoveFile.sh

Copy the CreateEmptyFile.sh and RemoveFile.sh scripts to tibco_root>/tra / domain/

/Accelerator/scripts folder.

Aftercopying the files, change the permissions of CreateEmptyFile.shand RemoveFile.sh

to 777 so that these can be invokedfrom the rulebases.


7/26

Page 1515 of

6.1.3 VARIABLES CONFIGURATION FILE

TIBCO Hawk has the capability to use external variables within the Hawk rulebases.

There are some fields that will be used in all rulebases. Some of the fields will be

common, others will not. These include certain directory locations, log file locations,

and several e-mail relatedvalues.

The

/tra/domain//Accelerator/scripts/HawkAC_variables.dat will

hold all of the variables. All of the values will be configured for

each machine/environment in thisfile. Every agent can read only one configuration file.

Standard Variablesto include:

MAIL_SERVER: This is the mail server used for sendingemails.

MAIL_FROM: The email address defined in this variable will be used as fromaddress on any email sent from Hawk

MAIL_CC: Any email recipient defined in this variable will be CCed on any Hawkalertsent.

MAIL_SUBJECT:The prefix used in the subject of email is definedin thisvariable.

MAIL_TO: Any email recipient defined in this variable will be emailed on anyemail sent from Hawk.

DOMAIN_NAME: This shouldbe set to the name of the TIBCO Administrationdomain

CONFIG_ROOT: This is the location of all of the scripts and config files for Hawk.The variablesfile shouldalreadybe set to the correctvalue.

FLAG_ROOT: This is the location of the Hawkenableflags. The variables fileshouldalreadybe set to the correctvalue.

TRA_ROOT: This is the root location of the TIBCO domain.The variablesfile shouldalreadybe set to the correctvalue.

Note: Apart from above variables, rulebase specific variables also can be

added. Please keep in mind that if any changes are done in the

HawkAC_variables.dat, Domain Hawk agent serviceneed to be restarted to make the

changes effective. The recommendation would be to add the variables for all

rulebases at once, to avoid restartingthe Hawk agent service for several times.

The HawkAC_variable.dat file need to be placed in the / tra/domain/

/Accelerator/scriptsdirectory

HawkAC_variable.da

t


8/26

Page 1616 of

The TRA hawkagent.cfg configuration file must be modified to include the variables

file. The variables line must be uncommented, and the name and location of

the variablesfile appended to theparameter.

-variables

/tra/domain//Accelerator/scripts/HawkAC_variable.dat

Save the changes.

RestartDomain Hawk agent service.

6.2 RULEBASE: BUSINESSWORKS PROCESS ENGINE

This section will discuss on the Hawk Rulebase to monitor and manage the

TIBCO BusinessWorks Process engines.

The naming convention followed for this kind of rulebase is BWEngine-

Deployment- Component.hrb. Here Deployment is the Enterprise Archive name and

Component is theprocess archivename in the BWproject.

6.2.1 REQUIREMENTS

If the engine is started or stopped from the TIBCO Administrator, then Hawk

rulebase should not start the engine. If the engine is stopped abruptly due to

some reason, then the rulebaseshouldattempt to start the engine for once.

Ateach step, appropriatealertsand/oremailsshouldbe sent from the rulebase.

6.2.2 IMPLEMENTATION DETAILS

Given below are the implementation details for CISCommon BW process engine. The

rulebasename is "BWEngine-CISCommon-CISCommonProcesses.hrb"

BWEngine-CISComm

on-CISCommonProces

Given below is the sequence diagram which describes the high level implementation of

thisrulebase.


9/26

Page 1717 of

FIGURE 2 BW PROCESS ENGINE RULEBASE FLOW


10/26

Page 1818 of

The rules include:

Check for the .running file: This rule will test to see the CISCommon-

CISCommonProcesses.running file exists in flags directory. If the file exists,

then the no_error post condition is set. Ifthe file does not exist,then the error

post condition is set. The rule will checkfor the .runningfile every 2 seconds. This

post condition is used later in the rulebase to help Hawk determine if the

BW Process Engine has successfullystartedpreviously.

Check for the .enabled file: This rule will test to see the CISCommon-

CISCommonProcesses.enabled file exists in flags directory. If the file exists,then the enabled post condition is set. If the file does not exist, then the

disabledpost condition is set. The rule will check for the .enabled file every 5

seconds. This post condition is used later in the rulebase to decide whetherthe

rulebaseneed to take some action or not

This rule checks to see if the BW Process Engine is running, also using the

TRA.getComponentStatus Hawk microagent. This test is performed every six

seconds. This rule has several steps depending on if the service is running. The

rulewill:


11/26

Page 1919 of

o Check to see if the BW Process Engine has a state of INITIALIZING. If it

does, the BW Process Engine isbeing started via the TIBCO Administrator.

The rule will run the CreateEmptyFile.sh script with

appropriate parameters such that CISCommon-

CISCommonProcesses.enabled file is created and there by enabledpost

conditionis set.

o Check to see if the BW Process Engine has a state of RUNNING. Ifit does,

the BW Process Engine has successfully started. The rule will send an

informational notification and email that it is running, and run the

CreateEmptyFile.sh script with appropriate parameters such thatCISCommon-CISCommonProcesses.running file is created and there by

no_errorpost conditionis set.

o Check to see if the BW Process Engine has a state of STOPPING and

enabled post condition exists. This signifies that BW Process Engine

isbeing stopped via TIBCO Administrator. The rule will run

the RemoveFile.sh script with appropriate parameters to remove the

CISCommon-CISCommonProcesses.enabled file to ensure that disabled

post condition is set. This will prevent Hawk from attemptingto restart the

BW Process Engine.

o Check to see if the BW Process Engine has a state of STOPPED. Thissignifies that BW Process Engine is no longer running. It couldbe stopped

via TIBCO Administrator or due to some error. The rule will run the

RemoveFile.sh script with appropriate parameters to remove the

CISCommon-CISCommonProcesses.running file to ensure that error

post conditionis set.

o Check to see if the BW Process Engine has a state of STOPPED and

enabledpost condition is set. This signifies that BW Process Engine got


12/26

Page 2020 of

terminated abruptly due to some error. The rule will send a low alert

stating the BW Process Engine is not running, and will attempt to start the

engine. The rule will also run RemoveFile.sh script with appropriate

parameters to remove the CISCommon-CISCommonProcesses.running

file to ensure that error post condition is set. After90 seconds, ifthe BW

process is not started, a highalert will be sent stating that the BW Process

Engine is still down. The BW Process Engine will be disabledto prevent the

rule from attempting to start it again. The rule will also run

the RemoveFile.sh script with appropriate parameters to remove the

CISCommon-CISCommonProcesses.enabled file to ensure that disabled

post condition is set, preventing Hawk from attempting to restart the BW

Process Engine.

o Check to see if the BW Process Engine has a state of STOPPED and

disabled post condition is set. The rule will send a low alert that the

Hawkrulebase will not attempt to start the BW Process Engine.

6.2.3 LOAD THE RULEBASE

Before sending the rulebase (from the rulebase editor) to the selected machine,please

keep in mindthe following items.

This rulebaseneed to be appliedonly afterverifying that a BW Process Enginehas been started successfullyonce in TIBCO Administrator.

Apply the rulebase only when the BW process engine is down. After applyingthe rulebasestart the BW Process Engine from TIBCO Administrator.

Before redeploying a new Enterprise Archive for a BW process engine that isbeing monitoredby this rulebase,please STOP the BW Process engine manually

in TIBCO Administratorand ensure that it is not running. Ifthe BWprocess engine

is not stopped before redeployment, the engine will get killed and the rulebase

will try to start the engineagain.

6.2.4 MIGRATION ACROSS ENVIRONMENTS

Since this rulebase depends on the variables defined in HawkAC_variables.dat,

please ensure that the values for these variables are correctly defined as perthe

respectiveenvironmentconfiguration.

Same rulebase can be moved from one environment to another environment

withoutany changes.

6.2.5 TEMPLATE RULEBASE

Given below is the template rulebase that has been implemented with the requirements

mentionedin section6.2.1


13/26

Page 2020 of

BWEngine-Deployme

ntName-ComponentIn

Following changes have to be done,prior to using thisrulebase for a BW Process Engine.

DeploymentName need to be replaced with the EAR name defined in the BW

Project

ComponentInstanceNameneed to be replacedwith Process Archivename defined

under the EAR.

AuthorName need to be replacedwith the author of the rulebase HostName(IPAddress) need to be replacedwith a correspondingvalue

DateTime need to be replacedwith the current date time BWEngineDesc needs to be replaced with appropriate description of the BW

Process Engine.

Finally, the rulebase file name need to be changed with actual values ofDeploymentNameand ComponentInstanceName

6.3 RULEBASE: FILE ADAPTER

This section will discuss on the HawkRulebase to monitor and manage the TIBCO File

Adapter.

The naming convention followed for this kind of rulebase is FileAdapter-

Deployment- Component.hrb. Here Deployment is the Enterprise Archive name and

Componentis the File Adapterarchivename in the BWproject.

6.3.1 REQUIREMENTS

If the File Adapter is started or stopped from the TIBCO Administrator, then the

Hawk rulebase should send alerts and email notifications. If the File adapter

is stopped abruptly due to some reason, then also the rulebase should send

alerts and emails.


Given below are the implementation details for a Payment File Adapter. The rulebase

name is "FileAdapter-Finance-FinancePaymentFileAdapter.hrb"


14/26

Page 2121 of

FileAdapter-Finance-

FinancePaymentFileA

The rulewill:

Check for the existence of the Payment File Adaptermicroagent. Ifthe numberof

microagents becomes zero, sends a high alert along with an email

mentioning that Payment File Adapter is down. If the number of the

microagents becomes one, a notification and email will be sent saying that

Payment File Adapter is up and running.The rule will check the microagentcount

for every 5 seconds.


This rulebasecan be sent to the machineat anypoint of time. Basedon the current state

of the File Adapter,an alertand email willbe sent.






withoutany changes.


15/26

Page 2222 of




FileAdapter-Deploym

entName-Component

Following changes have to be done,prior to using thisrulebase for a FileAdapter.


Project

ComponentI

nstanceName need to be replaced with FileA

dapterA

rchive namedefinedunder the EAR.

AuthorName need to be replacedwith the author of the rulebase HostName(IPAddress) need to be replacedwith a correspondingvalue DateTime need to be replacedwith the current date time FileAdpaterMicroagentNameproperty needs to be defined with appropriate value

in the HawkAC_variables.dat file. In general as there will be more than one file

adapter in the properties file, it is recommended to add a prefix to thisproperty

name.

FileAdapterDesc needs to be replaced with appropriate description of the file

adapter.


6.4 RULEBASE: ADB ADAPTER

This section will discuss on the HawkRulebase to monitor and manage the TIBCO ADB

Adapter.

The naming convention followed for this kind of rulebase is ADBAdapter-Deployment-

Component.hrb. HereDeploymentis the Enterprise Archive name and Component is the

ADB Adapterarchivename in the BWproject.

6.4.1 REQUIREMENTS


16/26

Page 2323 of

Ifthe ADB Adapter is started or stopped from the TIBCO Administrator, then Hawk

rulebase shouldnot start the adapter. Ifthe ADB Adapter is stopped abruptlydue

to some reason, then the rulebaseshouldattempt to start the adapterfor once.

Ateach step, appropriatealertsand/oremailsshouldbe sent from the rulebase.


The implementation details for a LIMS ADB Adapter are similar to that of BW Process

Engine defined in section 6.2.2. The rulebase name is "ADBAdapter-WaterQuality-

LIMS.hrb"

ADBAdapter-WaterQ

uality-LIMS.hrb


Loadingrulesare same as that of BW Process Engine definedin section6.2.3


Migrationrulesare same as that of BW Process Engine definedin section 6.2.4




ADBAdapter-Deploy

mentName-Componen

Following changes have to be done,prior to using thisrulebase for an ADB adapter.


Project

ComponentInstanceName need to be replaced with ADB Adapter Archive namedefinedunder the EAR.

AuthorName need to be replacedwith the author of the rulebase HostName(IPAddress) need to be replacedwith a correspondingvalue DateTime need to be replacedwith the current date time


17/26

Page 2424 of

ADBAdapterDesc needs to be replaced with appropriate description of the ADBadapter.


6.5 RULEBASE: EMS SERVER

This section will discuss on the HawkRulebase to monitor and manage the TIBCO EMS

server.

The namingconventionfollowed for thisrulebaseis EMSServer-Status.hrb.

6.5.1 REQUIREMENTS

Ifthe EMS server is not running, rulebase should send an alert and email and try

starting the EMS server. If the EMS server could not be started successfully then

an appropriatealertand email shouldbe sent.

Ifthe EMS server is up and running,a notificationand email shouldbe sent.


Given below are the implementation details for an EMS server. The rulebase name is

"EMSServer-Status.hrb"

EMSServer-Status.hr

b

For every 10 seconds, the rule will check whether the EMS server is running or not.

If the EMS server is not running, a low alert and email will be sent and rulebase

will attempt to start the EMS server. If the EMS server is brought back successfully

then notification and email will be sent. Ifthe EMS server couldnot be brought back, an

alert and email willbe sent.


This rulebasecan be sent to the machineat anypoint of time. Basedon the current state

of the EMS server, alert and email will be sent. In case the EMS server is not running,

rulebase will attempt to start it.


18/26

Page 2525 of






withoutany changes.

6.6 RULEBASE: EMS QUEUESThis section will discuss on the HawkRulebase to monitor and manage the TIBCO EMS

queues.

The naming convention followed for this rulebase is EMSQueueTopic-Deployment.hrb.

HereDeploymentis the EnterpriseArchivename.

6.6.1 REQUIREMENTS

For a queue, if the pending message count exceeds the limit (even though the

corresponding BW Process Engine is up and running) an alert and email should be

sent. Here the limit is defined based on the message load and the monitoring

interval.

At any point of time, if the pending message count exceeded the limit an alert

and email shouldbe sent. This check need to be repeated for every subsequent

one hour and up to 12 hrs.


Given below are the implementation details for an EMS queue in Contact project. The

rulebasename is "EMSQueueTopic-Contact.hrb"

EMSQueueTopic-Con

tact.hrb

The rulewill:


19/26

Page 2626 of

Check for the .enabled file: This rule will test to see the Contact-

ContactProcess.enabled file exists in flags directory. If the file exists, then the

enabledpost condition is set. If the file does not exist, then the not_enabled

post conditionis set. The rule will checkfor the .enabledfile every 5 seconds. This

post condition is used later in the rulebase to decide whether the rulebase need

to take some action or not.

Check for the .running file: This rule will test to see the Contact-

ContactProcess.running file exists in flags directory. If the file exists, then

runningpost condition is set. If the file does not exist, then the not_running

post condition is set. The rule will checkfor the .runningfile every 4 seconds. This

post conditionis used laterin the rulebase.

Get the pending message count: This rulegets the queueproperties for every 60

seconds. Itverifieswhether thepending message count is greater than 1 and BW

Process Engine is running (both enabled and running post conditions exist). Ifthis

condition is satisfiedthen an alertand email willbe sent statingthat there are

n

pending messages in the queue. Once the condition is satisfied then for every

subsequent one hour (and up to 12 hrs) this checkwill be performed and if the

conditionexistsat that instance of timean alertand email willbe sent.


This rulebase can be sent to the machine at anypoint of time. It will check the current

state of the queue, and accordinglyan alertand email willbe sent.


20/26

Page 2727 of



please ensure that the values for these variables are correctly defined as per

the respectiveenvironmentconfiguration.

Same rulebasecan be moved from one environment to anotherenvironment without

any changes.




EMSQueueTopic-Depl

oymentName(Q).hrb

Following changes have to be done, prior to using this rulebase for monitoring an EMS

queue.

DeploymentName need to be replaced with the EAR name defined in the

corresponding BW Project


under the EAR.

AuthorName need to be replacedwith the author of the rulebase HostName(IPAddress) need to be replacedwith a correspondingvalue DateTime need to be replacedwith the current date time QueueNameproperty needs to be defined with appropriate value of queue name

in the HawkAC_variables.dat file. In general as there will be more than one

queue in the properties file, it is recommended to add a prefix to thisproperty

name.

ProcessNameproperty needs to be defined with appropriate value of BW process

name in the HawkAC_variables.dat file. In general as there will be more than

one process name in the properties file, it is recommended to add a prefix to this

property name.

ProjectNameproperty needs to be defined with appropriate value of BW project


one project name in the properties file, it is recommended to add aprefix to this

property name.


21/26

Page 2828 of

MaxPendingMessages is the maximum number of messages in the queue and if

the messages exceed this limit an alert and email will be sent. This needs to be

replacedwith appropriatenumber based on the requirement.

Finally, the rulebase file name need to be changed with actual value ofDeploymentName

6.7 RULEBASE: EMS DURABLE TOPICS

This section will discuss on the HawkRulebase to monitor and manage the TIBCO EMS

durabletopics.

The naming convention followed for this rulebase is EMSQueueTopic-Deployment.hrb.

HereDeploymentis the EnterpriseArchivename.

6.7.1 REQUIREMENTS

For a durable topic, ifthependingmessage count exceeds the limit (even though

the corresponding BW Process Engine is up and running) an alert and email

should be sent. Here the limit is defined based on the message load and the

monitoring interval.

At any point of time, if the pending message count exceeded the limit an alert

and email shouldbe sent. This check need to be repeated for every subsequent

one hour and up to 12 hrs.

Also if the durable count for this topic does not match with the expected durable

count, an alert and email shouldbe sent. This check need to be repeated forevery subsequent one hour and up to 12 hrs.


Given below are the implementationdetails for an EMS durabletopic in WAAproject.The

rulebasename is "EMSQueueTopic-WAA.hrb"

EMSQueueTopic-WA

A.hrb

The rulewill:


22/26

Page 2929 of

Check for the .enabled file: This rule will test to see the WAA-WAA.enabled file

exists in flags directory. If the file exists, then the enabledpost condition is

set. If the file does not exist, then the not_enabledpost condition is set. The

rule will check for the .enabled file every 5 seconds. This post condition is used

later in the rulebase to decide whether the rulebase need to take some action ornot.

Check for the .running file: This rule will test to see the WAA-WAA.running file

exists in flags directory. Ifthe file exists, then runningpost condition is set. If

the file does not exist, then the not_runningpost condition is set. The rule will

checkfor the .runningfile every 4 seconds. This post condition is used later in the

rulebase.

This rule checks for the pending message count and the durable count for this

topic.This test is performed every 30 seconds. The rulewill:


23/26

Page 3030 of

o Get the durable count: This test verifies whether the durable count is

equal to 2 or not. Ifthe durable count is not equal to 2, an alert and email

will be sent. Once the condition is satisfied then for every subsequent one

hour (and up to 12 hrs) this checkwill be performed and if the condition

existsat that instance of timean alertand email willbe sent.

o Get the pending message count: This test verifies whether the pending

message count is greater than 5 and the BW Process Engine is running

(both enabled and running post conditions exist). If this condition is

satisfied then an alert and email will be sent stating that there are

npending messages in the queue. Once the condition is satisfied then

for every subsequent one hour (and up to 12 hrs) this check will be

performed and if the condition exists at that instance of time an alert

and email willbe sent.

6.7.3 LOAD THE RUL

EBA

SE

This rulebase can be sent to the machine at anypoint of time. It will check the current

state of the topic,and accordinglyan alertand email willbe sent.



24/26

Page 3131 of


please ensure that the values for these variables are correctly defined as per

the respectiveenvironmentconfiguration.

Same rulebasecan be moved from one environment to anotherenvironment without

any changes.




EMSQueueTopic-Depl

oymentName(T).hrb

Following changes have to be done, prior to using this rulebase for monitoring an EMSdurabletopic.

DeploymentName need to be replaced with the EAR name defined in the

corresponding BW Project


under the EAR.

AuthorName need to be replacedwith the author of the rulebase HostName(IPAddress) need to be replacedwith a correspondingvalue DateTime need to be replacedwith the current date time TopicNameproperty needs to be defined with appropriate value of topic name in

the HawkAC_variables.dat file. Ingeneral as there will be more than one queue

in the propertiesfile, it is recommended to add aprefix to thisproperty name.

ProcessNameproperty needs to be defined with appropriate value of BW process


one process name in the properties file, it is recommended to add a prefix to this

property name.

P

rojectNameproperty needs to be defined with appropriate value of BW projectname in the HawkAC_variables.dat file. In general as there will be more than

one project name in the properties file, it is recommended to add aprefix to this

property name.

DurSubCount is the durable subscriber count for this topic. If the durable count

doesnt match with this number then an alert and email will be sent. This needs

to be replacedwith appropriatenumber based on the requirement.


25/26

Page 3232 of

MaxPendingMessages is the maximum number of messages in the queue and if

the messages exceed this limit an alert and email will be sent. This needs to be

replacedwith appropriatenumber based on the requirement.

Finally, the rulebasefile name need to be changed with actualDeploymentName

6.8 RULEBASE: CLIENT CONNECTIONS TO THE EMS SERVER

This section will discuss on the HawkRulebase to monitor the unauthorized client

connectionsestablishedto TIBCO EMS server.

The naming convention followed for this rulebase is EMSServer-

UnauthorizedConnections.hrb.

6.8.1 REQUIREMENTS

This rulebaseshouldmonitorthe connectionsestablishedto the EMS server and if

a connection has been established from a unknown machine (that is not part of

the allowablemachines),an alertand email shouldbe sent.

The list of allowable machines shouldbe prepared in advance as this list should

be includedin the rulebase.

Note: This rulebase will not prevent the connection from an unauthorized

machine to the EMS server, but will generate alert and email when

such connectionis established.


Given below are the implementation details for monitoring the unauthorized client

connections to EMS server. The rulebase name is "EMSServer-

UnauthorizedConnections.hrb"

EMSServer-Unauthor

izedConnections.hrb

The rule will get the list of EMS server connections for every 60 seconds and verifies the

host name of the machines that are connected. If there is at least one machine that is

not in the list of allowablemachines,then an alertand email willbe sent.



26/26

Cognizant_configure Domain Hawk Agent

Documents

Transcript of Cognizant_configure Domain Hawk Agent