![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |
5.
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.
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.
Sub-directories tibco/cfgmgmt are appended to the path.
11.
− TCP (default): Connects to a Cluster Manager.
− RV: Connects to a TIBCO Rendezvous service.
− EMS: Connects to a TIBCO EMS server.
13. If you select TCP as the transport:
− 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.
− 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.
− 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.
− 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.
− 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:
− 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.
− 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.
− 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.
− 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:
− 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.
− 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.
− 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.
− 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.
− 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.
− 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.
2.
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. 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.
4.
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.
b. For example, update ENV_NAME as follows:
c. Update features to be installed. Set the Hawk component features that you want to install to true and the Admin Agent feature to false. See Understanding Installation Profiles for more details.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.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.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.
1. Edit the same .silent file which was used for Hawk components installation. See Installing the Hawk Components and Admin Agent.
2. Using a text editor, open the copied file and update the install location, ENV_NAME, and features to install as follows:
a. For example, update ENV_NAME as follows:
b. Update features to install. Set the following feature to true to install the Admin Agent component. See Understanding Installation Profiles for more details.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.
![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |