Lightweight Console

By default, the console monitors and can communicate with every agent in a given TIBCO Hawk domain. If, however, you are building an application that needs to interact with only a single agent, you can initialize the console in such a way that limits its communication to just that agent. This results in a lightweight console instance that uses fewer resources.

Creating a Lightweight Console

Instantiating a lightweight console involves constructing a TIBHawkConsole object with a fully qualified hawkDomain parameter. A fully qualified hawkDomain narrows down the domain to a single agent and contains the three parts that uniquely identify an agent, in a dot-separated format:

   <hawkDomain>.<agentDNS>.<agentName>
<hawkDomain> is what would be used as the hawkDomain parameter of the TIBHawkConsole constructor if you were instantiating a console that communicates with all agents. If an agent is configured without a hawkDomain specification, it uses the value "default".
<agentDNS> should match the agentDNS (also called agent domain) parameter with which the agent was configured. If the agent was not configured with an agentDNS, it uses the value "none".
<agentName> must match the agent name. If not set, this defaults to the hostname the agent is running on. See The AgentInstance Class for more information

Using the Dot and Underscore Characters

None of the three elements may contain the dot '.' character. The dot is used as a separator in a fully qualified hawkDomain. If any of the three components require a dot (agentDNS typically does), replace all occurrences with the underscore '_' character. The agent automatically performs this translation on its end.

For example, if an agent is configured with the following values:

hawkDomain = testDomain
agentDNS = myfirm.com (note the dot in the name)
agentName = host1

the fully qualified hawk domain is:

   testDomain.myfirm_com.host1