Installing the Hawk Components and Hawk Admin Agent

1. Download the package.
2. Extract the contents of the package to a temporary directory.
3. Navigate to the temporary directory.
4. Run TIBCO Universal Installer. You can do so in one of the following ways:

Double-click the TIBCOUniveralsalInstaller icon.

On the command prompt, provide the absolute path of the installer file without specifying any options. The installer defaults to GUI mode.

5. Click the Next button on the Welcome dialog box.
6. Read through the license text when the License Agreement dialog box appears. Select the “I accept the terms of the license agreement” radio button and click the Next button.

The TIBCO Installation Home dialog box is displayed.

7. In the TIBCO Installation Home dialog box, select one of the following options to specify the installation environment. See Installation Environment for more details.
— Create a new TIBCO_HOME   to install the product into a new installation environment, specify the Directory. The directory into which the product is installed. Type a path or click Browse to specify the path or accept the default location.
— Use an existing TIBCO_HOME   to install the product into an existing installation environment, select the environment from the drop-down list. The Directory field are populated automatically and cannot be edited.
8. Click the Next button. The Installation Profile Selection dialog box displays.
9. Select the TIBCO Hawk 6.2 Components installation profile to install all the Hawk components. Or select the Customize Installation check box to explicitly select the Hawk installation components.

Optionally, hold your Ctrl key down and click TIBCO Hawk Admin Agent to select it too. If you choose not to install the Admin Agent at this time you can always install it at a later time by re-running this installer. Click Next. See the Understanding Installation Profiles for more details.

10. Choose a folder to be used as the TIBCO configuration destination for the installation environment. The configuration directory is used to store product configuration information. The folder must not already exist as a configuration destination for another installation environment.

Note 

Sub-directories tibco/cfgmgmt are appended to the path.
11. Select whether you want to use the JVM bundled with the installer or you want to use a JVM previously installed on your machine. If you opt for the latter, browse to the Java location on your machine using the Browse button, then click Next.
12. Select the transport to be used with the Hawk Event Service.
— TCP (default): Connects to a Cluster Manager.

For details, see TCP Transport for TIBCO Hawk.

— RV: Connects to a TIBCO Rendezvous service.

For details, see TIBCO Rendezvous Transport.

— EMS: Connects to a TIBCO EMS server.

For details, see TIBCO Enterprise Message Service (EMS) Transport.

13. If you select TCP as the transport:

Configure the TCP transport for Hawk Event Service:

— Hawk Domain: The default domain of the Hawk Event Service is used.
— Self IP Address:Port: The IP address of the instance running the Hawk Event Service. The default is localhost:2582.
— Cluster Manager IP Address:Port: The IP address of the instance running Hawk Cluster Manager. The default is localhost:2561.

Configure the AMI TCP Session for the Hawk Event Service:

— Self IP Address:Port: The IP address of the instance running the Hawk Event Service. The default is localhost:2575.
— Agent IP Address:Port: The IP address of the instance running Hawk Agent. The default is localhost:2571.

Configure the TCP transport for the Cluster Manager:

— Hawk Domain: The default domain of the Cluster Manager is used.
— Self IP Address:Port: The IP address of the instance running the Cluster Manager daemon. The default is localhost:2561.
— Cluster Manager IP Address:Port: The IP address of the instance running Hawk Cluster Manager. The default is localhost:2561.

Note 

Multiple agents, consoles, or cluster managers running on the same instance must bind separate ports.

Configure the TCP transport for Hawk Agent:

— Hawk Domain: The default domain of the Hawk Agent is used.
— Self IP Address:Port: The IP address of the instance running the Hawk Agent. The default is localhost:2551.
— Cluster Manager IP Address:Port: The IP address of the instance running Hawk Cluster Manager. The default is localhost:2561.

Configure the AMI TCP Session for the Hawk Agent.

— AMI TCP Session Self IP Address:Port: Configures the Hawk agent with a TCP session to be used to communicate with applications implementing the TIBCO Hawk Application Management Interface.

If this parameter is not specified when using TCP Transport for TIBCO Hawk, the default value of localhost:2571 is used.

— Set AMI RVD Session: Configures the agent with a RVD session to be used to communicate with applications implementing the TIBCO Hawk Application Management Interface.

Note 

If you set Set AMI RVD Session to true, make sure that the respective .tra file has the RV_HOME path.

14. If you select RV as the transport:

Configure the Rendezvous transport for Hawk Event Service:

— Hawk Domain: The default domain of the Hawk Event Service is used.
— Service: Specify the host and port number of the TIBCO Rendezvous daemon. The default is 7474.
— Network: The network used for all communications between Hawk and the TIBCO Rendezvous daemon.
— Daemon: The remote host and port used to connect to the TIBCO Rendezvous daemon. The default is tcp:7474.

Configure AMI Rendezvous Session for Hawk Event Service:

— Service: Specify the host and port number of the TIBCO Rendezvous daemon. The default is 7474.
— Network: The network used for all communications between Hawk and the TIBCO Rendezvous daemon.
— Daemon: The remote host and port used to connect to the TIBCO Rendezvous daemon. The default is tcp:7474.

Configure the Rendezvous transport for the Hawk agent:

— Hawk Domain: The default domain of the Hawk agent is used.
— Service: Specify the host and port number of the Rendezvous daemon. The default is 7474.
— Network: The network used for all communications between Hawk and the Rendezvous daemon consisting of network, multicast groups, and send address.
— Daemon: The remote host and port used to connect to the Rendezvous daemon. The default is tcp:7474.

Configure AMI RVD Session for Hawk Agent.

— Service: Specify the host and port number of the Rendezvous daemon. The default is 7474.
— Network: The network used for all communications between Hawk and the Rendezvous daemon consisting of network, multicast groups, and send address.
— Daemon: The remote host and port used to connect to the Rendezvous daemon. The default is tcp:7474.

 

15. If you select EMS as the transport:

Configure the EMS transport for Hawk Event Service.

— Hawk Domain: The default domain of the Hawk Event Service is used.
— Server URL: The location of the EMS server. For example: tcp://server1:7222.
— Username: The user name of the EMS server. For example: admin.
— Password: The password for the EMS server. For example: #!NhAD1NBC.

Configure the AMI RVD Session for the Hawk Event Service.

— Service: Specify the host and port number of the Rendezvous daemon. The default is 7474.
— Network: The network used for all communications between Hawk and the Rendezvous daemon consisting of network, multicast groups, and send address.
— Daemon: The remote host and port used to connect to the Rendezvous daemon. The default is tcp:7474.

Configure the EMS transport for the Hawk agent:

— Hawk Domain: The default domain of the Hawk agent is used.
— Server URL: The location of the EMS server. For example: tcp://server1:7222.
— Username: The user name of the EMS server. For example: admin.
— Password: The password for the EMS server. For example: #!NhAD1NBC.

Configure the AMI RVD Session for the Hawk Agent.

— Service: Specify the host and port number of the Rendezvous daemon. The default is 7474.
— Network: The network used for all communications between Hawk and the Rendezvous daemon consisting of network, multicast groups, and send address.
— Daemon: The remote host and port used to connect to the Rendezvous daemon. The default is tcp:7474.

Configure the TCP transport for the Cluster Manager.

— Self IP Address:Port: The IP address of the instance running the Cluster Manager daemon. The default is localhost:2561.
— Cluster Manager IP Address:Port: The IP address of the instance running Hawk Cluster Manager. The default is localhost:2561.

Note 

Multiple agents, consoles, and cluster managers running on the same instance need to bind to separate ports.

16. Download the Oracle Elliptic Curve Cryptography Library LGPL assembly.
— Oracle Elliptic Curve Cryptography Library assembly from TIBCO: Download the assembly from the TIBCO website.
— Provide the location for the assembly previously downloaded from TIBCO: You can manually download the assembly by clicking the TIB_product_tibco_sunec_11.0.3.012_<OS>.html file listed with the software on the download site. For example, on Windows, click: TIB_product_tibco_sunec_11.0.3.012_win_x86_64.html
— Oracle Elliptic Curve Cryptography Library Assembly Path: Specify the folder where the assembly was downloaded.
17. Verify the list of product features selected for install in the Pre-Install Summary dialog box and click Install.
18. Review the information listed in the Post-Install Summary dialog box and click Finish.