TIBCO BW AutoNaming delay

Document ID : KB000019748
Last Modified Date : 14/02/2018
Show Technical Document Details

Description:

When using the TIBCO BW auto-naming feature, the agent actually derives its name from the Enterprise Manager. This means that it must first connect to the Enterprise Manager before it can be renamed. One problem with this is that you have duplication of metrics as the agent first connects with the agent name "AgentName" which contributes to the overall amount of historical metrics in the Enterprise Manager.

Solution:

You can manually specify the name of the agent in the IntroscopeAgent.profile or Tibco .tra file of each process, in the same section where you enable the agent using a JVM property:


 	-Dintroscope.agent.agentName=

So, a full example would be:


 	java.extended.properties=-javaagent:C:\tibco\wily\Agent.jar -Dcom.wily.introscope.agentProfile=C:\tibco\wily\core\config\introscopeAgent.profile 	-Dintroscope.agent.agentName= 

The same property can be used for any Java instrumentation, not just TIBCO.

Since you are specifying the agent name, you should disable agent auto-naming in IntroscopeAgent.profile:


 	introscope.agent.agentAutoNamingEnabled=false 

If you would like to keep the automatic feature enabled, please reduce the auto renaming values as shown so that there is less delay in obtaining the correct agent name once the agent has connected to the Enterprise Manager


 	introscope.agent.agentAutoNamingMaximumConnectionDelayInSeconds=10
   introscope.agent.agentAutoRenamingIntervalInMinutes=1

This will reduce the waiting time for seeing the agent in the Investigator and obtaining the correct agent name from 12 minutes to 1 minute 10 seconds.

This is also your best option if you are enabling the agent in bwengine.tra instead of the individual .tra file for each process.