Jump to content

BW applications are not displayed in microagents


chandru TR

Recommended Posts

Hello,

Please check if appnode log to see if you see any error related to RV_HOME path, appnode cannot connect rvd if RV_PATH is not set.

Otherwise please double check the rv used by appnode and Hawk AMI is the same(need to check ami_rvd_session in hawkagent)

Hope this helps.

Thanks,

Tristan

Link to comment
Share on other sites

Hi Tristan,

 

Thanks for your reply. I see RV parameters for node and hawkagent are the same(7474). I dont see any RV related errors in app node logs. microagent is able to detect the bw applications in other cluster member. Both the config files are similar. I have tried almost all possibilities but still having issues. Any other solutions would be of great help.

 

 

 

 

Link to comment
Share on other sites

Hello,1. Please check $TIBCO_HOMEbw6.3domainstestdomainappnodestestAStestANconfig.ini to see if Hawk is enabled like below:========================bw.hawk.hma.rv.service=7474bw.hawk.hma.rv.daemon=tcp:7474bw.hawk.hma.enabled=true

bw.hawk.hma.transport=tibrv========================then check hawkagent.cfg file and see:a. if ami_rvd_session is enabled, it should be:-ami_rvd_session 7474 ; tcp:7474b. if ami_rvd is disable, then make sure rvd_session is using:============================-rvd_session 7474 ; tcp:7474#-ami_rvd_session 7474 ; tcp:7474============================You can upload Hawk.log, hawkagent.cfg, config.ini, appnode log if still have this issue. 2. Of cource you can check rv http interface for 7474 and see if both hawkagent and appnode connected to the same service.Thanks,Tristan

Link to comment
Share on other sites

  • 2 weeks later...
  • 1 year later...

Hello,

If you are using BW5, then please check:

1. if hawk webconsole connects to correct hawkagent, please verify domain name and transport configured for Hawk webconsole which should be consistent with the hawkagent.

2. As long as BW application status is showing correctly on tibco administrator, microagent of BW application should be added to hawkagent already.

3. Please double check .tra file of BW application, and make sure Hawk related parameter below is same as ami_rvd_session in hawkagent.cfg.

Hawk.Daemon=tcp:7474

Hawk.Enabled=true

Hawk.Network=;

Hawk.Service=7475

Please attach following files if issue persists:

- hawkagent.cfg

- .tra file of application

- hawkwebconsole.log

Thanks,

Tristan

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...