WAS v8.5 > Reference > Developer detailed usage information

Liberty profile: JMX REST connector settings

This topic provides a list of keys and description that we can use as system properties when connecting to a Liberty profile with JMX REST connectors.

These keys are constants in the com.ibm.ws.jmx.connector.client.rest.ConnectorSettings interface, and each constant requires an integer value to specify an amount of time in milliseconds except for the DISABLE_HOSTNAME_VERIFICATION, which accepts the boolean value only.

The com.ibm.ws.jmx.connector.client.rest.ConnectorSettings interface is a management interface. For more information about the management interface, see the Java™ API document for the Liberty profile. The Java API document for each Liberty profile API is detailed in the Programming Interfaces (APIs) section of the information center, and is also available as a JAR file under the /dev/ibm-api/javadoc directory of the server image.

DISABLE_HOSTNAME_VERIFICATION

Boolean setting that disables hostname verification on the client connections when enabled. This can be useful for environments where the hostname used does not match the one specified in the server certificate. The key for constant DISABLE_HOSTNAME_VERIFICATION is the String com.ibm.ws.jmx.connector.client.disableURLHostnameVerification.

MAX_SERVER_WAIT_TIME

Amount of time the client waits for the server to become available before the JMX connection fails and a new connection must be created. The key for constant MAX_SERVER_WAIT_TIME is the String com.ibm.ws.jmx.connector.client.rest.maxServerWaitTime. If the connection is restored, any previous notification listeners are registered again. To disable this behavior, set the value to zero.

NOTIFICATION_DELIVERY_INTERVAL

Maximum amount of time the server waits for new notifications before responding to a request for notifications from the client. The key for constant NOTIFICATION_DELIVERY_INTERVAL is the String com.ibm.ws.jmx.connector.client.rest.notificationDeliveryInterval. A larger value results in better notification delivery times because less time is spent establishing new connections. Normally it is not necessary to adjust this value.

NOTIFICATION_INBOX_EXPIRY

Amount of time the server waits before discarding notification registrations if the client has not checked for new notifications. The key for constant NOTIFICATION_INBOX_EXPIRY is the String com.ibm.ws.jmx.connector.client.rest.notificationInboxExpiry. Normally it is not necessary to adjust this value.

NOTIFICATION_READ_TIMEOUT

Read timeout for notification fetching. Because the server might wait up to NOTIFICATION_DELIVERY_INTERVAL before responding, this value must be somewhat larger, though normally it is not necessary to adjust this value. The key for constant NOTIFICATION_READ_TIMEOUT is the String com.ibm.ws.jmx.connector.client.rest.notificationReadTimeout.

READ_TIMEOUT

Read timeout for all client communications with the server, except notification fetching. Adjust this value if the client throws read timeout exceptions because of a slow connection or client or server process. The key for constant READ_TIMEOUT is the String com.ibm.ws.jmx.connector.client.rest.readTimeout.

SERVER_STATUS_POLLING_INTERVAL

Amount of time the client waits between checks the server is available again when MAX_SERVER_WAIT_TIME is non-zero. Normally it is not necessary to adjust this value. The key for constant SERVER_STATUS_POLLING_INTERVAL is the String com.ibm.ws.jmx.connector.client.rest.serverStatusPollingInterval.

We can enable those JMX REST connector options using the system properties. Take the MAX_SERVER_WAIT_TIME option as an example, we can use one of the following options:


Parent topic: Configuring secure JMX connection to the Liberty profile


|