...
The Data Server connects to BusinessWorks 5 using TIBCO Hawk. See the TIBCO Hawk section for information about securing those connections. Additional server metrics can optionally be collected via JMX using the RTView Manager. See the TIBCO BusinessWorks 5 documentation for enabling JMX and securing it in your BusinessWorks engine. See the RTView Manager section in this document for information on making secure connections to JMX. For BWSE engines, RTView collects AMX Node data via JMS messages which that are hosted on an EMS Server. The EMS Server can be configured to require a user name and password which the user enters that you enter in the RTView Configuration Application when defining the Connection connection to that Serverserver. Additionally, the EMS Server can be configured to use SSL. In this case, the user you must implement a subclass of the GmsRtViewJmsDsSSLHandler to return a Map map of the required SSL parameters per connection. This is described in the RTView Core documentation under under RTView Data Sources→JMS Data Source→Application Options - JMS→ JMS Connections Tab →JMS SSL Parameters.
TIBCO BusinessWorks 6
The Data Server connects to TIBCO BusinessWorks 6 either using TIBCO Hawk or via the OSGI plugin. See the TIBCO Hawk section for information about securing TIBCO Hawk connections. When using the OSGI plugin, data is sent via socket to the Data Server on port XX72. By default, this socket is not secure, but the data will be sent via secure socket if the Data Server is configured for SSL sockets.
...
The Data Server connects to EMS Servers using TIBCO's TibjmsAdmin api. The EMS Server can be configured to require a user name and password which the user enters that you enter in the RTView Configuration Application EMS Server Connection dialog when defining the connection to that EMS Server. Additionally, the EMS Server can be configured to use SSL. In this case, the user you must implement a subclass of the GmsRtViewTibJmsSSLHandler to return a Map map of the required SSL parameters per connection. This is described in the RTView Core documentation under RTView Data Sources→TIBCO EMS Administration Data Source → Application Options - TIBCO EMS → TIBCO EMS Servers Tab → TIBCO EMS Administration SSL Parameters.
TIBCO Hawk
TIBCO Hawk is used to gather metrics for both TIBCO BusinessWorks 5 (required) and TIBCO BusinessWorks 6. The Data Server connects to TIBCO Hawk via TIBCO's TIBHawkConsole api. The TIBCO Hawk installation may either be configured to run on a Rendezvous transport (rvd) or an EMS Transport. In the case of Rendezvous transports, no secure connection options are supported. In the case of EMS transports, the TIBCO Hawk agent can be configured to require a user name and password which the user enters that you enter in the TIBCO Hawk Add Connection dialog in the RTView Configuration Application TIBCO Hawk Connection dialog when adding a connection to that agent. The EMS transport can also be configured for SSL. In this case, the user you must implement a subclass of the GmsRtViewHawkCustomSSLHandlerto GmsRtViewHawkCustomSSLHandler to return a Map map of the required SSL parameters per connection. This is described in the RTView Core documentation under RTView Data Sources→TIBCO Hawk Data Source → Application Options - TIBCO Hawk→ TIBCO Hawk SSL Parameters.
RTView Manager
The RTView Manager connects to processes via JMX. A process that opens a JMX port can be configured to require a user name and password which the user enters that you enter in the RTView Manager Add Connection dialog in the RTView Configuration Application RTView Manager Connection dialog when defining the connection to that process. A process that opens a JMX port can also be configured to require SSL. To connect to SSL secured JMX, fill in the SSL Credentials section of SECURITY tab in the RTView Configuration Application with the appropriate values for your SSL configuration.
...
The Data Server, Data Collector, Historian and Display Server all open JMX ports for monitoring. By default, these jmx ports are unsecured, but they can be secured either by user name and password or by SSL. See the RTView Manager section in this document for instructions on connecting to secure JMX. To configure the JMX ports of the RTView processes to use SSL and/or username and password, go to the SECURITY tab in the RTView Configuration Application. Note that the start/stop/status_rtv scripts use JMX to communicate with the RTView processes. If you secure the JMX ports on the RTView processes, you will need to save arguments for use by the scripts in the Configuration Application SECURITY tab or pass additional arguments into the start/stop/status_rtv scripts.
To secure with user name and password, you will need a java password file. To secure with SSL, you will need a certificate, truststore, and keystore. These are described in the orace Oracle documentation: https://docs.oracle.com/javase/8/docs/technotes/guides/management/agent.html
...
The Data Server connects to Kafka via JMX. Kafka can be configured to require a user name and password which the user enters that you enter in the Kafka Add Connection dialog in the RTView Configuration Application Kafka Connection dialog when defining the connection to that process. Kafka can also be configured to require SSL. To connect to SSL secured Kafka, fill in the SSL Credentials section of SECURITY tab in the RTView Configuration Application with the appropriate values for your SSL configuration.
...