Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

TIBCO FTL

Note: Support for secure connections to TIBCO FTL was added in version 5.2. Previous versions of RTView do not support secure connections to TIBCO FTL.

The Data Server connects to TIBCO FTL using the TIBCO FTL API. The TIBCO FTL Server can be configured to run with transport encryption and additionally with username/password authentication. If transport encryption is enabled, follow the instructions in the TIBCO FTL Administration Guide to create a trust file (certificate), which by default is named ftl-trust.pem. Copy this file into your projects/rtview-server directory and import it into your JVM keystore with a command such as:

keytool -alias ftl -file ftl-trust.pem -import -keystore $JAVA_HOME/jre/lib/security/cacerts -storepass changeit

In the TIBCO FTL Add Connection dialog in the RTView Configuration Application , use an https URL to connect to TIBCO FTL Servers with transport encryption enabled. If the TIBCO FTL server is configured with authentication, fill in the Username and Password fields.

TIBCO ActiveMatrix

The Data Server connects to TIBCO ActiveMatrix either using TIBCO Hawk and via TIBCO Enterprise Monitor messages. See the TIBCO Hawk section for information about securing TIBCO Hawk connections. The EMS Server can be configured to require a user name and password which the user enters in the RTView Configuration Application ActiveMatrix 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 must implement a subclass of the GmsRtViewJmsDsSSLHandler to return a Map of the required SSL parameters per connection. This is described in the RTView Core documentation under RTView Data Sources→JMS Data Source → Application Options - JMS → JMS Connections Tab → JMS SSL Parameters.

  • No labels