TIBCO Hawk WebConsole Configuration

For Basic Configuration of TIBCO Hawk WebConsole:

Please refer to the basic configuration steps to configure the hawk web console using TIBCO Hawk components for the successful TIBCO Hawk Installation guide.

To start TIBCO Hawk WebConsole on Microsoft Windows:

1. To begin the process, move to the HAWK_HOME\webconsole folder and then double-click on tibhawkh2db.exe to start or run the database.

2. To start the hawk web console process, you need to double-click startwebconsole.bat.

3. As soon as the web hawk console started in your browser's address box, enter a URL of the following format:

http://<hostname>:<port number>/hawkwebconsole where, the default <port_number> is 8080.

For example, http://localhost:8080/hawkwebconsole. Now, enter a valid username and password in the provided login space.

Username - admin, Password - admin

To start Hawk WebConsole on UNIX:

1. To begin the hawk web console on UNIX, try to open the command prompt to head to the HAWK_HOME/webconsole folder.

2. Run the following scripts:

tibhawkh2db

startwebconsole.sh

3. After you start the Hawk WebConsole, in your browser's address box, enter a URL of the following format:

http://<hostname>:<port number>/hawkwebconsole

For example, http://10.97.123.83:8080/hawkwebconsole

In the login space, make sure to enter a valid username and password.

Make use of the following credentials

Username - admin” Password - ”admin"

tibco connection

 

tibco connection

JMS Error: It will occur only if EMS 8.0 or higher version is used ,as JMS 2.0 support start with EMS 8.0 version

Apr 09, 2015 5:34:10 PM org.apache.catalina.startup.ContextConfig processResourceJARs

SEVERE: Failed to processes JAR found at URL [jar:file:/C:/tibco/ems/8.2/lib/jms.jar!/] for static resources to be included in context with name [jar:file:/C:/tibco/ems/8.2/lib/jms.jar!/]

Apr 09, 2015 5:34:10 PM org.apache.catalina.startup.TldConfig tldScanJar

WARNING: Failed to process JAR [jar:file:/C:/tibco/ems/8.2/lib/jms.jar!/] for TLD files

java.io.FileNotFoundException: C:\tibco\ems\8.2\lib\jms.jar (The system cannot find the file specified)

       at java.util.zip.ZipFile.open(Native Method)

       at java.util.zip.ZipFile.<init>(Unknown Source)

 

Resolution: To fix the above issue go to the below location and modify the "setenv.bat" file to include "jms-2.0.jar" instead of "jms.jar"

 

C:\tibco\hawk\5.1\webconsole\tomcat\bin\setenv.bat

 

Note:

  1. You can also modify the hawk web-console default HTTP port by modifying the connector port value in the below file

 

C:\tibco\hawk\5.1\webconsole\tomcat\conf\server.xml

 

  1. You can change the Domain name and RV communication parameters for the TIBCO domain to be monitored in the below file.

 

C:\tibco\hawk\5.1\webconsole\tomcat\webapps\hawkwebconsole\WEB-INF\conf\DomainTransportCfg.xml

 

<!-- RV transport domain-->

<hk:DomainTransport>


<hk:HawkDomainName>default</hk:HawkDomainName>


<hk:Transport>


<hk:RVTransportCfg>


<hk:service>7474</hk:service>


<hk:network></hk:network>


<hk:daemon>tcp:7474</hk:daemon>


</hk:RVTransportCfg>


</hk:Transport>


<hk:SecurityPolicy></hk:SecurityPolicy>


</hk:DomainTransport>

 

 

LOGIN CONSOLE WINDOW

tibco login

 

 

tibco web console

 

tibco web console

By clicking on the particular agent on left window you can get the below view. You can then explore Alerts,Rulebases,Schedules and Microagents options.

 

tibco web console

 

tibco web console deployed

 

tibco web console methods

 

 

  1. For monitoring a remote domain from local machine ensure that port connectivity is open between local and remote machine and specify the correct value for RV parameters in Domain Transport configuration file.

 

C:\tibco\hawk\5.1\webconsole\tomcat\webapps\hawkwebconsole\WEB-INF\conf\DomainTransportCfg.xml

 

<!-- RV transport domain-->

<hk:DomainTransport>


<hk:HawkDomainName>test</hk:HawkDomainName>


<hk:Transport>


<hk:RVTransportCfg>


<hk:service>7474</hk:service>


<hk:network></hk:network>


<hk:daemon>tcp:10.28.184.38:7474</hk:daemon>


</hk:RVTransportCfg>


</hk:Transport>


<hk:SecurityPolicy></hk:SecurityPolicy>


</hk:DomainTransport>

  1. The default log file location and logging level for hawk webconsole can be modified by changing values in following file

 

C:\tibco\hawk\5.1\webconsole\tomcat\webapps\hawkwebconsole\WEB-INF\conf\log4j_webconsole.properties

tibco web console Agent

Modifying/Disabling HawkWebconsole Database :

 

[[email protected] webconsole]$ The Web Console server could not be started. Possible cause: another server is already running at http://10.106.52.45:8082

Root cause: Exception opening port "8082" (port may be in use), cause: "java.net.BindException: Address already in use" [90061-167]

TCP server running at tcp://10.106.52.45:9092 (only local connections)

WRAPPER - start method threw an exception

Exception in thread "main" org.h2.jdbc.JdbcSQLException: Exception opening port "8082" (port may be in use), cause: "java.net.BindException: Address already in use" [90061-167]

at org.h2.message.DbException.getJdbcSQLException(DbException.java:329)


at org.h2.message.DbException.get(DbException.java:158)


at org.h2.util.NetUtils.createServerSocketTry(NetUtils.java:190)


at org.h2.util.NetUtils.createServerSocket(NetUtils.java:156)


at org.h2.server.web.WebServer.start(WebServer.java:331)


at org.h2.tools.Server.start(Server.java:455)


at org.h2.tools.Console.runTool(Console.java:230)


at org.h2.tools.Console.main(Console.java:100)


Caused by: java.net.BindException: Address already in use


at java.net.PlainSocketImpl.socketBind(Native Method)


at java.net.AbstractPlainSocketImpl.bind(Unknown Source)


at java.net.ServerSocket.bind(Unknown Source)


at java.net.ServerSocket.<init>(Unknown Source)


at java.net.ServerSocket.<init>(Unknown Source)


at org.h2.util.NetUtils.createServerSocketTry(NetUtils.java:186)


... 5 more

^C

[1]+ Exit 1                 ./tibhawkh2db

/opt/tibco/hawk/5.1/webconsole/tomcat/webapps/hawkwebconsole/WEB-INF

 

tibco code view

 

No directly start Web console and no need to start the database process