TIBCO Hawk 5.1 : Introducing the new WebConsole

TIBCO Hawk is the main tool developed by TIBCO to do monitoring tasks, but in the last years its evolution had been a little confused. We have had the last version of the 4.x series, the 4.9 version for so long, that many people thought the idea of the company was to declare the producto as a “feature complete” (that means, no more features updates only bugfixes will be released). The adquisition of other tools like TIBCO Spotfire, the partnership with RTView could lead us to think that the time of the TIBCO Hawk was been passed away, but we could not be more wrong. Continue reading

How to change the TIBCO Hawk WebConsole Port

In previous post we talked about this new WebConsole introducing by the last version series of TIBCO Hawk, the 5.x series. You can see more information about it here. One of the most important things is that the webconsole is deployed using the 8080 as a default port. This post is so common that is almost imposible to be free in your server when you want to deploy or start the WebConsole. For example, this port is the default of the Tomcat web-server, the JBoss/WildFly application server, even is the default port of the TIBCO Administrator (the older one) so it’s an important thing to know how to change it.

Continue reading

Configuring TIBCO Hawk to keep running the TIBCO Enterprise Administrator

Usually in this blog we talk a lot about development techniques, trips or tricks, but we don’t pay so much attention to the administration tasks. In this topic we are going to change that because we are going to explain how to use the main TIBCO tool for monitoring and administrative tasks, TIBCO Hawk.

As we said earlier, TIBCO Hawk is the main tool by TIBCO to reach the following goals:

  • Monitoring your platform performance
  • Extract statistics about your performance
  • Executing administrative tasks based on the data of their micro-agents.

In this topic we are not going to discuss conceptual aspects about the TIBCO Hawk architecture. We are only going to say that it is a distributed architecture based on agents and a network (preferred Rendezvous network but EMS also supported). All different agents (one agent for  TIBCO software: There is an agent for TIBCO AMX BusinessWorks, another for TIBCO BusinessEvents and so on) use this network to comunicate with each other and to send the data available for all including the Hawk console.

Continue reading