Products | Versions |
---|---|
TIBCO iProcess Engine (Oracle) | - |
Not Applicable | - |
Resolution:
Description:
===========
Can I use EMS as a transport to monitor the TIBCO iProcess Engine Microagents?
Environment:
===========
o iPE 11
o All Operating Systems
Symptoms:
=========
n.a.
Cause:
======
n.a.
Resolution:
========
EMS may be used as the primary transport for Hawk if you are planning to monitor iProcess via the TIBCO Hawk Console or TIBCO Administrator. If iProcess Server Manager is to be used, then the primary transport must be Rendezvous.
This is subject to the proviso that iProcess must be configured such that the Rendezvous Service, Network and Daemon must be set with the same Rendezvous settings as set in the primary AMI session section of the hawk configuration.
eg if the Hawk agent uses 7475 ; 7474 as its Rendezvous settings for HMA and Primary AMI Session
Then on the iProcess Engine machine:
cd SWDIR\util
swadm set_attribute 0 ALL 0 RV_SERVICE 7475
swadm set_attribute 0 ALL 0 RV_NETWORK ;
swadm set_attribute 0 ALL 0 RV_DAEMON 7474
Restart the iProcess Sentinels after the Hawk Agent and the Microagents will be available.