...
Secure with Username and Password
Allows This region allows you to secure the JMX ports for RTView processes, which would then require using a specific username/password to gain access. If this option is enabled, you must specify the path to the password file containing all valid user names and passwords.
...
The RTView Manager application also connects to the JMX Ports of the RTVeiw processes in order to monitor them. If you are using the RTView Manager in RTViewCentral and the JMX ports have been secured with username and password, you must fill in the Username and Password Credentials that the RTView Manager should use to connect. If you are using the RTView Manager in a deliverable other than RTViewCentral, you will need to fill in the user name and password in the connection to this RTViewDataServer in the RTView Manager Configuration Application.
...
The Security page tab has the following fields:
SSL Credentials | Truststore | Enter the directory path to the truststore file and click the associated SET PASSWORD button to define the password required to access the file. | ||
Keystore | Enter the directory path to the keystore file and click the associated SET PASSWORD button to define the password required to access the file. | |||
Secure with SSL | Enabling this toggle locks the JMX ports for the RTView processes (DataServer and Historian, for example). You must specify the path to the Truststore and Keystore files (and their associated passwords) in the SSL Credentials region (see above) when selecting this toggle. | |||
This option also locks the JMX ports used when the start_server, stop_server, and status_server scripts are run. Though not required, you can enter the path to the truststore and keystore files in the associated Client Truststore and Client Keystore fields (as well as their passwords) to avoid having to enter the keystore and truststore names and passwords on the command line when using the start_server, stop_server, and status_server scripts. | ||||
SSL Credentials for RTView Scripts | The start_server, stop_server, and status_server scripts connect to the RTView processes using JMX. You can either save the Client Truststore and Client Keystore properties here for use by the scripts or you can pass them in on the command line each time you execute those scripts. | |||
Secure RTView JMX Ports with Username and Password | Secure with User Name and Password | Locks Enabling this option secures the JMX ports for the RTView DataServer and Historian processes, which would then require using a specific username/password to gain access. Selecting If this option also means that RTView Manager connections to the RTView processes will require a username/password,is enabled, you must specify the path to the password file containing all valid user names and passwords. | ||
Password File – enter the path to the password file containing the login and password credentials required to access the RTView DataServer and Historian, which you can enter in the associated Username and Password Credentials regionprocesses. | ||||
Username and Password Credentials – Enter RTView Manager’s username/password combination so that RTView Manager can successfully connect to RTView Central. | Use for Scripts – Toggle on this option to allow the start_server, stop_server and status_server scripts to use the username and password entered here. | |||
Field Name Description
Secure with SSL Toggle on this option to secure RTView JMX ports with SSL
Secures the JMX Ports of the RTView processes with SSL. This requires a truststore and keystore. If this is enabled, fill in the Truststore and Keystore fields below for use by the RTView Processes to secure the JMX ports. RTView Manager connections to these processes must also be configured with Truststore and Keystore information.
SSL Credentials for Securing RTView JMX Ports
Enter the location and passwords for Truststore and Keystores containing SSL certificates, then SET PASWORD. These are required for Securing RTView JMX Ports with SSL.
SSL Credentials for RTView Scripts
The start_server, stop_server and status_server scripts connect to the RTView processes using JMX. You can either save the Client Truststore and Client Keystore properties here for use by the scripts or you can pass them in on the command line each time you execute those scripts.
For example, start_server.sh -sslkeystore:clientkeystore.jks -sslkeystorepass:clientkeystorepass -ssltruststore:clienttruststore.jks -ssltruststorepass:clienttruststorepass.
Secure with Username and Password Toggle on this option to secure RTView JMX ports with a username and password.
...
If you are using RTView Manager in RTViewCentral and the JMX ports have been secured with username and password, you must fill in the Username and Password Credentials that the RTView Manager should use to connect. | |||
Use for Scripts – Toggle on this option to allow the start_server, stop_server, and status_server scripts to use the username and password entered | |||
...
in the Username and Password Credentials region rather than having to specify the username and password on the command line each time you run the start_server, stop_server, and status_server scripts. For example, start_server.sh -jmxuser:userName -jmxpass:myPassword. |