IT Operations Management (ITOM)
cancel

How to Configure and Monitor TIBCO using OMi Management Pack for TIBCO

How to Configure and Monitor TIBCO using OMi Management Pack for TIBCO

Divya_Bharathi

A typical TIBCO eco-system could consist of 1000s of multi-level heterogeneous systems installed with different versions of TIBCO products like Enterprise Messaging Server, ActiveMatrix Business Works, Rendezvous, Hawk and Administrator Runtime. OMi MP for TIBCO monitoring provides a unified management of your entire TIBCO infrastructure to help ensure the health, performance and availability of your business systems by collecting operational events and providing a clear understanding of problem severity. OMi MP for TIBCO uses the TIBCO Hawk Java Application Programming Interface (API) for data collection.

This blog is not targeted on the setup of TIBCO products. Instead, I want to show you a step-by-step guide on how to configure, scale up/down TIBCO environment for monitoring using the OMi Management Pack for TIBCO and how to get monitoring results into Operations Manager i.

Prerequisites

Ensure you have a running OMi 10.1x, downloaded the OMi Management Pack for TIBCO from the HPE Live Network and installed.

  • TIBCO MP supports RV Domain Transport and EMS Domain Transport types.
    For RV Domain Transport à Hawk, RV and JDK (1.6 and above) library jars should be available.
    For the EMS Domain Transport à  Hawk, RV, EMS and JDK (1.6 and above) library jars should be available.
  • TIBCO Hawk libraries provided should be the highest version in the TIBCO ecosystem.
  • TIBCO EMS Server, BW Applications and Rendezvous microagents should be enabled for data collection.

3 steps for Monitoring TIBCO
3Steps.jpg

Scenarios for Deploying “TIBCO Configuration” Aspect

  1. Inside TIBCO Domain: One of the machine in a TIBCO Domain is installed with HP OA and TIBCO MP solution is deployed on it.
    1.jpg
  2. Outside TIBCO Domain: We can choose a proxy node where HP OA is installed, which is outside/not-part of the TIBCO Domain. TIBCO MP solution is deployed on the proxy node and monitoring of TIBCO Domain happens remotely.
    2.jpg
  3. Scale out: TIBCO MP solution can be deployed on a machine with HP OA installed on a node which is either inside/outside TIBCO Domain. This scenario is useful in monitoring more than 1000 applications/systems. “TIBCO Configuration” Aspect can be configured on one managed node to monitor x number of hawk agents and the remaining hawk agents can be monitored from the other node. This also enhances the performance of TIBCO MP monitoring.
    3.jpg

Example Configuration for Deploying “TIBCO Configuration” Aspect in a “Scale Out” mechanism

Step 1: Edit the policy template “TIBCO_Configuration” from the policy group “MP for TIBCO” to provide inputs for the TIBCO component details as shown below.
4.png

<global> block parameters are the details provided only once and will be used globally by TIBCO MP Collector to connect to all the domains which are configured in each <config> blocks. The global parameters inputs are mandatory and requires input directory paths for JAVA_PATH, JAVA_TOOLS_DIR, HAWK_DIR, RV_DIR and EMS_DIR.
HAWK_DOMAIN_ID holds the TIBCO hawk domain name and this will be considered as the instance parameter.
If TIBCO hawk domain is of EMS domain transport type provide inputs for EMS_URL and EMS_AUTH_ENABLED. If EMS server is SSL enabled provide EMS_URL like “ssl://hostname:port” and provide other SSL_* parameters. If EMS server is enabled in fault tolerance mode provide EMS_URL like “tcp://hostname1:port,tcp://hostname2:port” where hostname1 is the primary EMS server and hostname2 is the secondary EMS server.
If TIBCO hawk domain is of RV domain transport type provide inputs for HAWK_SERVICE, HAWK_NETWORK and HAWK_DAEMON and needs to comment the EMS related fields.

For filling the Scale out parameters, let us consider an example TIBCO domain of EMS domain transport type by name “EMSDOMAIN” running on host “IWFVM00499.hpeswlab.net” and around 10 machines by name “Node1, Node2 … Node10” added to the domain. On each of those 10 machines, consider 50 BW applications by name “App1, App2 … App50” are deployed and running.

If you don’t want to monitor a set of machines which are not critical, you can exclude those machines using parameter “EXCLUDE_HAWKAGENTS” as highlighted in the example below.

If you don’t want to monitor particular applications hosted on a machine which are not that critical, you can do so by listing the microagent names for those applications using parameter “EXCLUDE_MICROAGENTS” as highlighted in the example below.

You can include multiple <config> blocks to provide inputs for multiple TIBCO hawk domains. Save and Close the “TIBCO_Configuration” policy template after entering all the inputs. The policy version increases by 0.1.

<props>
<global>
JAVA_PATH=C:/tibco/tibcojre64/1.8.0/bin/java
JAVA_TOOLS_DIR=C:/tibco/tibcojre64/1.8.0/lib
HAWK_DIR=C:/tibco/hawk/5.2
RV_DIR=C:/tibco/tibrv/8.4
EMS_DIR=C:/tibco/ems/8.2
</global>

<config>
#Hawk domain name
HAWK_DOMAIN_ID=EMSDOMAIN
#List of hawkagents to be excluded from discovery and collection. If there are multiple hawkagents they should be separated by ","
EXCLUDE_HAWKAGENTS=Node9,Node10
#List of hawkagents to be included from discovery and collection. If there are multiple hawkagents they should be separated by ","
#INCLUDE_HAWKAGENTS=all
#List of microagents to be excluded from discovery and collection. If there are multiple microagents they should be separated by ","
EXCLUDE_MICROAGENTS= COM.TIBCO.ADAPTER.bwengine.EMSDOMAIN.Stocks_Buy.simpleRV, COM.TIBCO.ADAPTER.bwengine.EMSDOMAIN.Stocks_Display.simpleRV
#List of microagents to be included from discovery and collection. If there are multiple microagents they should be separated by ","
#INCLUDE_MICROAGENTS=all

#If RV is set as domain transport and non-default values are set for HAWK_SERVICE, HAWK_NETWORK and HAWK_DAEMON uncomment the below three lines and set proper values
#HAWK_SERVICE=7475
#HAWK_NETWORK=;
#HAWK_DAEMON=tcp:7474

#If EMS is used as domain transport mention the ems url and uncomment the below line
EMS_URL=tcp://IWFVM00499.hpeswlab.net:7222
EMS_AUTH_ENABLED=TRUE
#In case SSL is enabled while using EMS as transport uncomment the below necessary lines and fill proper values
#SSL_TRACE=TRUE|FALSE
#SSL_VENDOR=
#SSL_VERIFY_HOST=TRUE|FALSE
#In case of multiple trusted certificates, they should be separated by ","
#SSL_TRUSTED=
#SSL_VERIFY_HOSTNAME=TRUE|FALSE
#SSL_EXPECTED_HOSTNAME=
#SSL_IDENTITY=
#SSL_PRIVATE_KEY=
#For list of supported CIPHERS refer to EMS User Guide -> "Using the SSL Protocol" -> "Configuring SSL in EMS Clients"
#SSL_CIPHERS=
</config>
………
<props>

Step 2: Edit the “TIBCO Configuration” Aspect to include the required version of the “TIBCO_Configuration” policy template as show below. Now Aspect version increases by 0.1.
5.png

Step 3: Assign and Deploy the updated “TIBCO_Configuration” Aspect on the managed node to discover the TIBCO Components. You need to provide the required parameters “HAWK_DOMAIN_ID” by entering the TIBCO hawk domain name. If the TIBCO Domain is of EMS domain transport type with authentication enabled, you need to provide inputs for “EMS_USERNAME” and “EMS_PASSWORD”. If it is SSL enabled provide input for “EMS_SSL_PASSWORD”. If there are multiple TIBCO hawk domains configured in the “TIBCO_Configuration” policy template, then you need to add those names as shown below.
6.png

Result:  Once the TIBCO Configuration aspect is deployed on a managed node, it discovers the running TIBCO components in your eco-system. You can visualize the entire TIBCO product suite along with the system infrastructure of your enterprise in a single topology view. It also automatically discovers any additional systems or applications when added to your TIBCO environment. A sample shown below.
7.png

OMi MP for TIBCO monitoring provides a unified view of your entire TIBCO infrastructure to help ensure the health, performance and availability of your business systems. Hope these steps mentioned will ease you in configuring your TIBCO environment. When you can create an automatic assignment rule for the TIBCO Management Template, OMi will take care of automatically assigning the Management Template and Aspects to the discovered TIBCO CIs as they appear on the network. It will save you from having to deploy the assignments manually whenever any new TIBCO CIs are discovered.

 Try OMi now! OMi 10.10 comes pre-loaded with a number of Management Packs that you can try out without the hassle of getting management pack software or an evaluation license.

Read more:

HPE Operations Bridge
HPE Live Network: Operations Bridge Evolution

HPE Live Network: Operations Manager i

HPE Live Network: OMi Management Pack development kit

HPE Live Network: HPE  SPI to MP Evolution Tool

  • operations bridge
About the Author

Divya_Bharathi

Comments
N/A

Thanks for putting this document.

Couple of question

- Is there any document for TIBCOMP error?

- Any KM doc, WhitePaper to troubleshoot Tibco Discovery from Tibco MP?

Let me know.

Member

I am missing this kind of guides for deployment, great work

//Add this to "OnDomLoad" event