Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved


Chapter 1 TIBCO Hawk Installation : Installation Modes

Installation Modes
TIBCO Universal Installer provides the following three modes of installation for TIBCO Hawk. When installing TIBCO Hawk you also have the option to install the Admin Agent, which exposes TIBCO Hawk to TIBCO Enterprise Administrator, along with the installation of TIBCO Hawk Components.
GUI Mode
GUI mode performs the installation in an interactive graphical interface. The installer prompts you for values specific to your environment.
Installing the Hawk Components and Hawk Admin Agent
1.
2.
3.
4.
a.
b.
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.
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.
Sub-directories tibco/cfgmgmt are appended to the path.
11.
12.
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:
a.
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.
b.
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.
c.
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.
d.
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.
e.
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.
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:
a.
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.
b.
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.
c.
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.
d.
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:
a.
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.
b.
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.
c.
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.
d.
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.
e.
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.
16.
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.
Installing the Admin Agent after Installing the TIBCO Hawk Components
1.
a.
b.
2.
Click the Next button on the Welcome dialog box.
3.
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.
4.
In the TIBCO Installation Home dialog box, click the Use an existing TIBCO_HOME option and select the existing installation environment where Hawk is installed and click Next.
5.
Select the TIBCO Hawk Admin Agent installation profile to install the TIBCO Enterprise Administrator Agent Runtime component. Click Next. See the Understanding Installation Profiles for more details.
6.
7.
Verify the list of product features selected for install in the Pre-Install Summary dialog box and click the Install.
8.
Review the information listed in the Post-Install Summary dialog box and click Finish.
Console Mode
Console mode allows you to install the software from a command window or terminal emulator. The installer prompts you for values.
To install this product in console mode:
1.
2.
3.
4.
TIBCOUniversalInstaller-x86-64.exe -console
To install from a UNIX terminal window, type:
TIBCOUniversalInstaller-<platform>.bin -is:javaconsole -console
5.
The installation process is the similar to the installation in GUI Mode.
Silent Mode
In silent mode, the Universal Installer does not prompt for any inputs during installation. Instead, the inputs are read from a configuration file that can be provided as a command-line parameter. If no value is specified, the installer uses the default TIBCOUniversalInstaller_hawk_<version>.silent file.
The TIBCOUniversalInstaller_hawk_<version>.silent file is packaged in the directory that contains the Universal Installer. Edit the file with information for your environment before launching the silent installation. The file includes comments that describe the installation properties you can set.
While you can use the TIBCOUniversalInstaller_hawk_<version>.silent file, it is recommended to copy the file to a different name and use that file for the silent install. If errors occur during installation, they are listed in the installation log file located in the User_Home/.TIBCO directory.
 
Installing the Hawk Components and Admin Agent
1.
2.
3.
4.
Make a copy of the TIBCOUniversalInstaller_hawk_<version>.silent file and rename the original file.
5.
Using a text editor, open the copied file and update the install location, ENV_NAME, and features that need to be installed as follows.
a.
 
<entry key="installationRoot">C:\tibco</entry>
b.
Update ENV_NAME. TIBCO Hawk must use the same ENV_NAME that <Family> uses.
For example, update ENV_NAME as follows:
 
<entry key="createNewEnvironment">false</entry>
<entry key="environmentName">TIBCO_HAWK_HOME</entry>
c.
The following elements can be set to true or false in the .silent file for installing your choice of components, to simulate the TIBCO Hawk custom installation.
 
<entry key="feature_Agent, SDK, Examples_hawk">true</entry>
<entry key="feature_Event Service_hawk">true</entry>
<entry key="feature_Console_hawk">true</entry>
<entry key="feature_Admin Agent Runtime_hawk">true</entry>
<entry key="feature_Cluster Manager_hawk">true</entry>
d.
<entry key="feature_Admin Agent Runtime_hawk">true</entry>
If you choose not to install the Admin Agent at this time, set the above property to false. You can always install the Admin Agent at a later time by setting the property to true and rerunning the installation.
e.
<!-- Hawk Cluster Manager Self IP Address -->
<entry key="hawk.self.ip.address">localhost:2561</entry>
<!-- Hawk Cluster Manager Cluster IP Address -->
<entry key="hawk.cluster.ip.address">localhost:2561</entry>
<!-- Domain -->
<entry key="cluster.hawk.domain">default</entry>
f.
<!-- Hawk Agent transport. The choices are: TCP, RV, or EMS -->
<entry key="hawk.agent.transport.name">TCP</entry>
 
<!-- Configuration for Hawk Agent if TCP selected-->
<!-- Self IP address -->
<entry key="hawk.agent.tcp.self.address">localhost:2551</entry>
 
<!-- Cluster IP address -->
<entry key="hawk.agent.tcp.cluster.address">localhost:2561</entry>
 
<!-- Domain -->
<entry key="hawk.agent.tcp.hawk.domain">default</entry>
 
<!-- AMI settings for TCP -->
<entry key="hawk.agent.ami.tcp.port">localhost:2571</entry>
<entry key="hawk.agent.ami.rvd.session">false</entry>
 
<!-- Configuration for Hawk Agent if RV is selected -->
<!-- Service name for RV -->
<!-- entry key="hawk.agent.rv.service.name">7474</entry -->
 
<!-- Network for RV -->
<!-- entry key="hawk.agent.network.name"></entry-->
 
<!-- Daemon for RV -->
<!-- entry key="hawk.agent.daemon.name">tcp:7474</entry -->
 
<!-- AMI settings for RV -->
<!-- entry key="hawk.agent.ami.service.name">7474</entry -->
<!-- entry key="hawk.agent.ami.network.name"></entry-->
<!-- entry key="hawk.agent.ami.daemon.name">tcp:7474</entry -->
 
<!-- Domain -->
<!--entry key="hawk.agent.rv.hawk.domain">default</entry-->
 
<!--configuration for Hawk Agent if EMS selected-->
 
<!-- Server URL for EMS -->
<!-- <entry key="hawk.agent.ems.serverurl"></entry-->
 
<!-- User name for EMS -->
<!-- entry key="hawk.agent.ems.username"></entry-->
<!--entry key="hawk.agent.ems.password"></entry-->
 
<!-- AMI Settings for EMS -->
<!--
<entry key="hawk.agent.ami.ems.service.name">7474</entry>
<entry key="hawk.agent.ami.ems.network.name"></entry>
<entry key="hawk.agent.ami.ems.daemon.name">tcp:7474</entry> -->
 
<!-- Domain -->
<!--entry key="hawk.agent.ems.hawk.domain">default</entry-->
g.
<!-- Hawk Event Service transport. The choices are: TCP, RV, or EMS -->
<entry key="hawk.event.transport.name">TCP</entry>
 
<!--Configuration for Hawk Event if TCP selected-->
<!-- Self IP addresss -->
<entry key="hawk.event.tcp.self.address">localhost:2551</entry>
 
<!-- Cluster IP address -->
<entry key="hawk.event.tcp.cluster.address">localhost:2561</entry>
 
<!-- AMI settings for TCP -->
<entry key="hawk.event.ami.self.address">localhost:2582</entry>
<entry key="hawk.event.ami.agent.address">localhost:2561</entry>
 
<!-- Domain -->
<entry key="hawk.event.tcp.hawk.domain">default</entry>
 
<!--Configuration for Hawk Event if RV selected-->
 
<!-- Hawk Event service name if RV is selected -->
<!--entry key="hawk.event.rv.service.name">7474</entry-->
 
<!-- Hawk Event network name if RV is selected -->
<!--entry key="hawk.event.network.name"></entry-->
 
<!-- Hawk Event daemon name if RV is selected -->
<!--entry key="hawk.event.daemon.name">tcp:7474</entry-->
 
<!-- Domain -->
<!--entry key="hawk.event.rv.hawk.domain">default</entry> -->
 
<!-- AMI Settings for Event Service if RV is selected -->
<!--
<entry key="hawk.event.ami.rv.service.name">7474</entry>
<entry key="hawk.event.ami.rv.network.name"></entry>
<entry key="hawk.event.ami.rv.daemon.name">tcp:7474</entry> -->
 
<!-- Configuration for Hawk Event Service if EMS selected -->
<!-- Server URL for Hawk Event Service -->
<!-- <entry key="hawk.event.ems.serverurl"></entry-->
 
<!-- User name for Hawk Event Service if EMS is selected -->
<!--entry key="hawk.event.ems.username"></entry-->
 
<!-- Password for Hawk Event Service if EMS is selected -->
<!--entry key="hawk.event.ems.password"></entry-->
 
<!-- Domain -->
<!--entry key="hawk.event.ems.hawk.domain">default</entry> -->
 
<!-- AMI Settings for Event Service if EMS is selected
<entry key="hawk.event.ami.ems.service.name">7474</entry>
<entry key="hawk.event.ami.ems.network.name"></entry>
<entry key="hawk.event.ami.ems.daemon.name">tcp:7474</entry> -->
6.
 
TIBCOUniversalInstaller.cmd -silent -V responseFile="TIBCOUniversalInstaller_hawk_<version>.silent"
 
TIBCOUniversalInstaller.bin -silent -V responseFile=" TIBCOUniversalInstaller_hawk_<version>.silent "
Provide a complete (absolute) path of TIBCOUniversalInstaller_hawk_<version>.silent to execute Universal Installer from some other folder.
A line similar to the following is written to the installer log file when installation completes:
 
... Install, com.tibco.installer.util.TIBCOInstaller, dbg.Debug, Executing Event:::OnEndInstall
Installing Admin Agent After Installing the Hawk Components
1.
Edit the same .silent file which was used for Hawk components installation. See Installing the Hawk Components and Admin Agent.
2.
a.
Update ENV_NAME. Admin Agent must use the same ENV_NAME that TIBCO Hawk uses.
For example, update ENV_NAME as follows:
 
<entry key="createNewEnvironment">false</entry>
<entry key="environmentName">TIBCO-HAWK_HOME</entry>
b.
Update features to install. Set the following feature to true to install the Admin Agent component. See Understanding Installation Profiles for more details.
 
<entry key="feature_Admin Agent Runtime_hawk">true</entry>
3.
 
TIBCOUniversalInstaller.cmd -silent -V responseFile="TIBCOUniversalInstaller_hawk_<version>.silent"
 
TIBCOUniversalInstaller.bin -silent -V responseFile=" TIBCOUniversalInstaller_hawk_<version>_silent "
Provide a complete (absolute) path of TIBCOUniversalInstaller_hawk_<version>.silent to execute Universal Installer from some other folder.
A line similar to the following is written to the installer log file when installation completes:
 
... Install, com.tibco.installer.util.TIBCOInstaller, dbg.Debug, Executing Event:::OnEndInstall
 

Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved