TIBCO HAWK

Tibco Hawk “No Valid Data Source Error”

This is one of the common error you might have seen many times ..Here is my observation..

This error means that the Hawk Agent can’t contact the Hawk Microagent plug-in that reports the state of the EMS server. Check that the plug-in is installed correctly and that the user name and password are correct. The user name must be a member of the $admin group.

The Rendezvous daemon must be running on the machine where the Agent is running.

Resolution: – You have not started the Hawk HMA process. This process holds a number of microagents among them the Performance microagent. When you start the Hawkagent also start the Hawkhma process it will work fine and you will not get those ‘NoValidDataSource’ messages.

Error:

NoValidDataSourceError for Rule com.tibco.tibjms.admin.hawk.HawkController:getQueu es(queueRegExp=):60 at RBEngine::Hawk->RuleBase::EMSQueuesPendingMsgCountCheck->Rule::com.tibco.tibjms.admin.hawk.HawkControlle r:getQueu es(queueRegExp=):60->NoValidDataSource::com.tibco.tibco  DataSourceError with com.tibco.tibjms.admin.hawk.HawkController:0: null, Wrapping: COM.TIBCO.hawk.talon.MicroAgentException:

Monitor the log file with as many patterns –HAWK log pattern file entry

You can monitor the log file with as many patterns as you want. Typically the pattern file is a bit like this:

 1 /.*error.*/i

2 /.*warning.*/i

-1 /.*/

 Try setting up the microagent to monitor a simple text file and watch for output as you add lines to it. You will probably find that you have to give the full path name for both the log file and the pattern file. Once you can monitor the text file, reconfigure the agent by supplying the full path name for the log file.

Example to monitor few specific logs in EMS logs

 EMS log pattern file entry

 1 /Slow clock tick/

1 /Invalid listen specification/i

2 /Error/i

-1 /.

What Domain utility Can Do?

 You can use TIBCO Domain Utility to set the following options:

1. Creating Adming Domain (Primary/Secondary)

2. Specify a database backend as the persistent store for domain data.

3. Specify non-default TIBCO Rendezvous properties or configure HTTPS.

4. Synchronize with an LDAP directory server to manage users and groups.

5. Set Local Application Data as the default deployment option

6. Specify a Password Policy

7. Specify ports for a web server

8. Machine Management

9. EMS Server Management

10. Adding Workflow components to Administrator

11. Chaging ports for Administrator (Service, HaWk etc)

Tibco Hawk Rule base to check for memory usage for a particular Queue

12AUG

Rule base to check for memory usage for a particular Queue.

Please follow the screen shots

1.

Select the JMS controller microagent and mention the required Queue name to be monitored.

2.

Select the condition for 80% threshold limit.

Pending message size >= 83886080 (80% of total memory)

3

Then provide the Alert message details and mail alert details.

How to add a TIBCO Hawk Rulebase to an Application?

1. Generate Rulebase according to previous steps.

2. Login to TIBCO administrator using your credentials.

In TIBCO Administrator, click Application Management.

3. Select the application for which the rulebase has been defined, and expand it.

4. In the Configuration Builder pane, click the service or process name for which the rulebase has been defined. A service is named with a .arr suffix. A process is named with a .par suffix.

5. Click the Monitoring tab.

6. In the Rulebases panel, click Add.

7. Click Browse and in the window that appears, navigate to the directory where the rulebase is stored and select the rulebase. Click OK.

8. Click Save.

When you deploy the service, TIBCO Hawk Agent saves the rulebase file in the <install-path>\tibco\tra\domain\<domain-name>\rulebase folder.

When the conditions specified in the rulebase occur, the results display in the Resource Management > Machines View Machine panel.

Monitoring logs using Hawk

Steps as follows :

If you wish to monitor the queues and topics, perform the following :

Locate the tibjmsadmin.hma file in the TIBCO Enterprise Message Service installation directory under the EMS_HOME\samples\admin\hawksubdirectory and copy it into your hawk\admin-plugins directory. 

Location : C:\tibco\ems\samples\admin\hawk\tibjmsadmin.hma

Jar Location : \tibco\ems\clients\java contains the 2 jar files

1. change the username,password,server properties in tibemsadmin.hma and copy it in to hawk\admin-plugins

<classname>com.tibco.tibjms.admin.hawk.HawkController</classname> (dont change the class name it should be HawkController)

<arguments>
<arg>-user</arg>
<arg>admin</arg>
<arg>-password</arg>
<arg>MyPassword</arg>
<arg>-server</arg>
<arg>tcp://server1.yourcompany.com:7222</arg>
<arg>-timeout</arg>
<arg>5</arg>
</arguments>

2. locate jms.jar,tibjmsadmin.jar files and copy them into hawk\admin-plugins folder.

Restart the TIBCO Hawk agent service. See the TIBCO Hawk documentation for more information about restarting the service.

s.