Introducing the all-new TIBCO Community site!

For current users, please click "Sign In" to reset your password and access the enhanced features. If you're a first-time visitor, we extend a warm welcome—click "Sign Up" to become a part of the TIBCO Community!

If you're seeking alternative community sites, explore ibi, Jaspersoft, and Spotfire.

Jump to content

Hawk agent with EMS transport fails to connect to HMA bw appnode agent

Recommended Posts


I'm trying to configure hawk agent to use EMS as primary transport to connect to hma bw 6 (using bw642) appnode agent.

My understanding isRendezvous is stil required to connect to the hma agent.

Without using EMS is working fine, using only Rendezvous inhawkagent.cfg :

-rvd_session 7474 ; tcp:7474

Appspace setup is :





























I can see the agent from hawk webconsole (agent is in online status) and I can invokeagent methods.

I have problems when I change thehawkagent.cfg file to useEMS as primary transport.

Here what I changed in thehawkagent.cfg file

# -rvd_session 7474 ; tcp:7474

-ems_transport tcp://localhost:7222 admin admin123

-M AMIService

-ami_rvd_session 7474 ; tcp:7474

My understanding is with EMS transport I need to set these AMIService parameters

Hawk agent starts successfully but I cant connect to the appnode agent.

Agent is in offline status in web console.

I tried to changeami_rvd_session parameters but it didn't work.

Is required additional configuration


Link to comment
Share on other sites


I found the issue.

It was an issue of webconsole configuration.

I had to update the fileDomainTransportCfg.xml in webconsoletomcatwebappshawkwebconsoleWEB-INFconf


I enabled the ems transport and commented RV transport section.

Note : Use the sameHawkDomainName used in hawkagent.cfg.

I know it may bestraightforward for most users but I think can be helpful for beginners :)

Link to comment
Share on other sites

  • Create New...