This topic lists the parameters in the General Configuration section.

Table 1. Server Properties

Field Name

Description

Shutdown Port

The TCP/IP port where the tc Runtime instance listens for a shutdown command. The connection must be initiated from the same server computer that is running this instance of tc Runtime.

Valid values are -1, 1, 2, ... up to 65535.

When the -1 default setting is specified, no shutdown port is enabled. This means that the only way that the server instance can be shut down is by a local kill statement to the server process.

Shutdown Command

The command to issue via a TCP/IP connection to the Shutdown Port to shut down tc Runtime.

JMX Listener

The JMX Listener section configures the component of the tc Runtime instance that listens for Java Management Extensions (JMX) connections from management tools, such as the vRealize Hyperic agent. By default, tc Runtime enables JMX connectivity.

Table 2. JMX Listener Properties

Field Name

Description

Enabled

Specifies whether the tc Runtime instance's pre-configured JMX listener is enabled.

The vRealize Hyperic agent uses JMX to connect to tc Runtime. If you disable the JMX listener, you cannot configure tc Runtime instances or groups from the vRealize Hyperic user interface, unless you configure JMX for tc Runtime through some other mechanism.

Port

Specifies the port on which tc Runtime listens for JMX/RMI connections. Specify a port number that is not in use by another process.

IP Address

Specifies the IP address on which tc Runtime listens for JMX/RMI connections. If the IP address is the same as the tc Runtime instance, you can enter 127.0.0.1.

Protocols

Specifies a comma-separated list of enabled SSL/TLS protocols. If you do not enter a value for this property, the default protocols are enabled.

Authenticate

Specifies if tc Runtime authenticates users that connect to the server using the JMX port.

If you enable this field, tc Runtime looks up the user and password in the files specified by the Access File and Password File fields. If tc Runtime finds the username and password in the files, the user is authenticated and allowed JMX access. If you disable this property, all users may access tc Runtime via JMX.

You configure the JMX user and password in vRealize Hyperic on server instances on the Inventory > Configuration Propertiespage.

The default JMX user and password is configured by default when you install tc Server. If you change the name or password of the user in the access and password files, you must also change the configured user/password in the vRealize Hyperic user interface.

Access File

Specifies the full path name of the tc Runtime file that contains the list of users allowed to access tc Runtime using JMX. This file resides on the computer that hosts the tc Runtime instance, not the computer that hosts the vRealize Hyperic server.

The access file contains one line per user. Each line contains a username and permission level:

  • readwrite - The user can view and modify the tc Runtime configuration.

    The default name for the access file is jmxremote.access.

    The default location is the CATALINA_BASE/conf directory of the tc Runtime instance.

    Each tc Runtime instance is configured by default with an admin user with readwrite permission.

  • readonly - The user can only view tc Runtime configuration .

Password File

Specifies the full pathname of the tc Runtime file that contains passwords for the users listed in the access file.

The password file contains one line for each user listed in the access file; each line contains a username and password. The default name for the password file is jmxremote.password.

The default location is the CATALINA_BASE/conf directory of the tc Runtime instance. The password for the pre-configured admin user is springsource.

Use SSL

Specifies whether to use secure sockets layer (SSL) for users' JMX connections to tc Runtime.

To use SSL, you must first set up a digital certificate on the computer that hosts the tc Runtime instance and then configure the SSL settings on this page. You can use the command-line utility keytool to manage digital certificates.

Client Authentication

Specifies whether client authentication is required when using SSL.

If you enable this property, tc Runtime authenticates JMX/SSL clients using certificate authentication rather than file-based authentication. This means that tc Runtime must find the client's certificate in its truststore or it will deny the client JMX access. This implies that only clients with known SSL certificates are allowed access to tc Runtime.

Use JDK Client Factory

Specifies whether the vRealize Hyperic agent uses the required client libraries from the JDK. The required libraries are used to pass SSL-specific properties (such as the trust store and password) to the tc Runtime instance. If you disable this property, you must manually set up the vRealize Hyperic agent's CLASSPATH to find these client libraries.

Cipher Suites

Specifies a comma-separated list of enabled SSL/TLS cipher suites. A cipher suite is a combination of cryptographic parameters that define the security algorithms and key sizes used for authentication, key agreement, encryption, and integrity protection.

If you do not enter a value for this property, the default cipher suites are enabled.

Truststore File

Specifies the full pathname of the truststore file used by SSL.

A truststore is a special kind of keystore file that is used when making decisions about what to trust. If you receive some data from an entity that you already trust, and if you can verify that the entity is the one it claims to be, you can assume that the data came from that entity. This means that the key of a truststore file typically contains an entity's identity and a public key, as opposed to a private key contained in a more restricted keystore file.

Truststore Pass

Specifies the password used to access the truststore file.

Keystore File

Specifies the full pathname of the keystore file.

A keystore is a database of key material. Key material is used for a variety of purposes, including authentication and data integrity. There are various types of keystores available, including "PKCS12" and Sun's "JKS." Typically, the key of a keystore consists of an entity's identity and its private key.

Keystore Pass

Specifies the password used to access the keystore file.