![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |
TIBCO Rendezvous and TIBCO EMS are two independent products that need to be installed separately. Additional configurations need to be performed manually based on whether they are installed before or after installing TIBCO Hawk, and whether any of them share the same TIBCO_HOME installation folder.If you are using or planning to use a single TIBCO_HOME for all TIBCO Rendezvous, TIBCO EMS, and TIBCO Hawk components, read this section. Otherwise, you might skip to the section Different TIBCO_HOME Locations for Various TIBCO Products.You can use an existing transport (TIBCO Rendezvous or TIBCO EMS) either from a previous installation of TIBCO Hawk or independent installations of these TIBCO products in the same TIBCO_HOME where Hawk is installed. Update all the TRA configuration files (for example, tibhawkagent.tra), script files (such as, starthawkconsole and starthma), Hawk Console configuration files with the correct locations of EMS_HOME and RV_HOME and the execution environment.If you install TIBCO Rendezvous or TIBCO Enterprise Message Service in the same TIBCO_HOME after TIBCO Hawk, ensure the following to set the correct runtime environment for the TIBCO Hawk components.
• Edit and modify TRA configuration files (all the files with the extension ".tra" in CONFIG_FOLDER/bin) to set the correct installation location of TIBCO Rendezvous and TIBCO Enterprise Message Service. That is, set the correct values for tibco.env.EMS_HOME and tibco.env.RV_HOME environment variables in all the TRA configuration files.On Unix or Linux, edit and modify the starthma.sh file with the correct RV_HOME location if TIBCO Rendezvous is installed after TIBCO Hawk.
•
− RV_HOME/lib/tibrvj.jar
− EMS_HOME/lib/tibrvjms.jar
− EMS_HOME/lib/tibjms.jar
− EMS_HOME/lib/tibcrypt.jar
− EMS_HOME/lib/jms-2.0.jar (in case of EMS 8.x)
• To configure Hawk WebConsole runtime environment, assuming TIBCO Hawk is installed with default supplied Tomcat web server, edit and modify HAWK_HOME/webconsole/startwebconsole.bat and HAWK_HOME/webconsole/tomcat/bin/setenv.bat (.bat file on Windows, and .sh on Unix/Linux) to set RV_HOME and EMS_HOME correctly.
If you are not using EMS as transport, then it is recommended that you remove the EMS_HOME entries from startwebconsole.bat and setenv.bat (the .bat file on Windows, and the .sh file on UNIX/Linux) files, to avoid any issues with Hawk WebConsole start.
If you are using or planning on using a different TIBCO_HOME for all TIBCO Rendezvous, TIBCO Enterprise Message Service, and TIBCO Hawk components, read this section. Otherwise, skip to the next section.Since TIBCO_HOME for Hawk is different from that of TIBCO Rendezvous and TIBCO Enterprise Message Service, ensure that appropriate installation locations are updated as follows:
• Edit and modify the TRA configuration files (all the files with extension ".tra" in CONFIG_FOLDER/bin) to set the correct installation location of TIBCO Rendezvous and TIBCO Enterprise Message Service. That is, set the correct values for tibco.env.EMS_HOME and tibco.env.RV_HOME environment variables in all the TRA configuration files.On Unix/Linux, if TIBCO Rendezvous is installed at different TIBCO_HOME, then edit and modify the starthma.sh file with the correct RV_HOME location.
•
− RV_HOME/lib/tibrvj.jar
− EMS_HOME/lib/tibrvjms.jar
− EMS_HOME/lib/tibjms.jar
− EMS_HOME/lib/tibcrypt.jar
− EMS_HOME/lib/jms-2.0.jar (in case of EMS 8.x)
• To configure Hawk WebConsole runtime environment, assuming TIBCO Hawk is installed with default supplied Tomcat web server, edit and modify HAWK_HOME/webconsole/startwebconsole.bat and HAWK_HOME/webconsole/tomcat/bin/setenv.bat (the .bat file on Windows, and the .sh file on UNIX/Linux) to set RV_HOME and EMS_HOME correctly.
If you are not using EMS as transport, then it is recommended that you remove the EMS_HOME entries from startwebconsole.bat and setenv.bat (the .bat file on Windows, and the .sh file on UNIX/Linux) files, to avoid any issues with Hawk WebConsole start.
Configure the -rvd_session parameter in the configuration files to enable the TIBCO Rendezvous as transport.TIBCO Hawk connects to the TIBCO Rendezvous daemon by creating a session. In the configuration files, ensure that the -tcp_session and -ems_transport parameters are commented out, and then configure the -rvd_session parameter. TIBCO Rendezvous transport creation calls accept three parameters that govern the behavior of the transport: service, network and daemon.
• service instructs the Rendezvous daemon to use this service whenever it conveys messages on this transport. You can specify the port number as the service to be used, for example, "7474".
• network instructs the Rendezvous daemon to use a particular network for all communications involving this transport. The network parameter consists of up to three parts, separated by semicolons: network, multicast groups, and send address.
• daemon instructs the transport creation function about how and where to find the Rendezvous daemon and establish communication. For remote daemons, specify two parts (introducing the remote host name as the first part), for example, tcp:7474:For more information about architecture of the TCP Transport for TIBCO Hawk, refer to the TIBCO Hawk Concepts Guide.
CONFIG_FOLDER\bin\hawktcpdaemon.cfg Perform the following configuration for setting up TCP Transport for TIBCO Hawk for Hawk components:
• Configure the -tcp_session parameter with details to join the TCP transport cluster. CONFIG_FOLDER\bin\hawkagent.cfg
• In case of connection to TIBCO Hawk Microagent (HMA), also uncomment the -ami_rvd_session parameter (in addition to -M AMIService and -ami_tcp_session parameters) for connection using the Hawk TCP-RV Bridge for the TCP Transport for TIBCO Hawk. For TIBCO Hawk Microagent to use the TCP Transport for TIBCO Hawk no configuration is required in hawkhma.cfg.For more information about -tcp_session, -ami_rvd_session, and -ami_tcp_session parameters for Hawk Agent, see Hawk Agent Configurations. CONFIG_FOLDER\bin\DomainTransportConfig.yml
• - domainName - Specify the Hawk domain name same as specified in the Hawk Cluster Manager (hawktcpdaemon.cfg).
• transport - Specify the value as tibtcp for TCP Transport for TIBCO Hawk.
• tcpSelfUrl - Specify the socket address of the Hawk Console for joining the cluster.
• tcpDaemonUrl - Specify the socket address of the Cluster Manager acting as the seed node for the cluster. This socket address is same as <cluster_manager_IP>:<port> specified for the -tcp_session parameter in the Hawk Cluster Manager (hawktcpdaemon.cfg). CONFIG_FOLDER\hawkteaagent\config\hawk-domain-transport-cfg.xml
• <hk:HawkDomainName> - Specify the Hawk domain name same as specified in the Hawk Cluster Manager (hawktcpdaemon.cfg).
• <hk:selfUrl> - Specify the socket address of the Hawk Admin Agent for joining the cluster.
• <hk:daemonUrl> - Specify the socket address of the Cluster Manager acting as the seed node for the cluster. This socket address is same as <cluster_manager_IP>:<port> specified for the -tcp_session parameter in the Hawk Cluster Manager (hawktcpdaemon.cfg). CONFIG_FOLDER\hawk\tibco\cfgmgmt\hawk\bin\hawkevent.cfg
• Specify the Hawk domain name same as specified in the Hawk Cluster Manager (hawktcpdaemon.cfg).
• Uncomment the -ami_tcp_session parameter for connecting to the Hawk Agent.For more information about -tcp_session and -ami_tcp_session parameters for Hawk Event Service, see Hawk Event Service Configurations. CONFIG_FOLDER\bin\hawkdisplay.cfg HAWK_HOME\webconsole\tomcat\webapps\hawkwebconsole\WEB-INF\conf\DomainTransportCfg.xml Uncomment the DomainTransport section with TCP Transport for TIBCO Hawk details and comment the DomainTransport sections for other transports. Specify the following parameters for the TCP Transport for TIBCO Hawk:
• <hk:HawkDomainName> - Specify the Hawk domain name same as specified in the Hawk Cluster Manager (hawktcpdaemon.cfg).
• <hk:selfUrl> - Specify the socket address of the Hawk WebConsole for joining the cluster.
• <hk:daemonUrl> - Specify the socket address of the Cluster Manager acting as the seed node for the cluster. This socket address is same as <cluster_manager_IP>:<port> specified for the -tcp_session parameter in the Hawk Cluster Manager (hawktcpdaemon.cfg).For instructions to modify the password which was specified during installation, see Handling Passwords for TIBCO EMS Transport.and also specify the additional options as outlined in TIBCO Enterprise Message Service (EMS) Transport Using SSL.In addition to specifying the -ems_transport options, the following parameters in the EMS server configuration file, tibemsd.conf, should be considered:
• ft_active—the name of the active server.
• ft_reconnect_timeout—the amount of time a backup server waits for clients to reconnect.
• store—the directory to store TIBCO EMS data.
•
• entrust61—Use this option when you want to use the Entrust libraries.
• ibm—On non-IBM platforms, this option can be used only if the IBM version of JCE is installed.
• -ssl_ciphers <suite-name>—When specifying this option to specify the cipher suites that can be used, use the ^ qualifier instead of a - qualifier. For more information about specifying cipher suites, refer to the TIBCO Enterprise Message Service documentation.
• -ssl_no_verify_host—If this option is present, it this indicates that the TIBCO Hawk component should not verify the server. Conversely, if this option is not included in the configuration file, it indicates that TIBCO Hawk component should verify the server.
• -ssl_trusted—The option specifies the file name of the server certificates. This option can be repeated if more than one certificate file is used.
• -ssl_no_verify_hostname—This option specifies that the client should not verify the name in the CN field of the server certificate. Conversely, if this option is not included in the configuration file, it indicates that TIBCO Hawk component should verify the name in the CN field of the server certificate.
• -ssl_expected_hostname—The name that is expected in the name of the CN field of the server certificates is specified by this option. The value of this option is used when the -ssl_no_verify_hostname option absent from the configuration file.
If the -ssl_no_verify_host is not specified, the option -ssl_trusted has to be used. Along with the option -ssl_trusted, specify either -ssl_no_verify_hostname or -ssl_expected_hostname.
• -ssl_identity—This option specifies the digital certificate of the TIBCO Hawk components.
• -ssl_private_key—This option indicates the private key of the TIBCO Hawk component. If the key is included in the digital certificate in -ssl_identity, then you may comment this parameter.
• -ssl_password—The password to decrypt the identity file of the Hawk component.
On AIX platform, TIBCO HMA process must be started as root user and should not rely on the setuid feature. On other non-Windows platforms, pseudo access may be sufficient, but root privileges are recommended to start TIBCO HMA process.
![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |