JMX connector properties

We can specify or set a property in the console, wsadmin.sh, Application Server commands, the scripts that run from a command-line interface, or a custom Java administrative client program that you write. We can also set SOAP connector properties in the soap.client.props file and IPC connector properties in the ipc.client.props file.

A JMX connector can be a Remote Method Invocation (RMI) connector, a SOAP connector, a JMX Remote API (JSR 160) Remote Method Invocation (JSR160RMI) connector, or an Inter-Process Communications (IPC) connector.

Deprecated feature: You should eventually convert all of your RMI connectors to JSR160RMI connectors because support for the RMI connector is deprecated.depfeat

For specific information on how to code the JMX connector properties for wsadmin.sh, the Application Server commands, or scripts, see the particular tool or command. Read the APIs documentation to learn how to code the JMX connector properties for a custom Java administrative client program.

The JMX connectors that servers create use JMX connector properties that are accessible in the console. The wsadmin tool and the Java administrative client use JMX connector properties in the soap.client.props, ipc.client.props, and sas.client.prop files.

For the console, this topic specifies the coding of the particular setting or property. Coding of properties in the soap.client.props file and the ipc.client.props file that are specific to JMX connectors is specified. These SOAP properties begin with com.ibm.SOAP and the IPC properties begin with com.ibm.IPC. Other properties in the soap.client.props file and the ipc.client.props file containing information that can be set elsewhere in the application server are not documented here. The coding for the com.ibm.ssl.contextProvider property, which can be set only in the soap.client.props file and the ipc.client.props file, is specified.

(dist)(zos) Each profile has property files at the following locations:

These property files allow you to set different properties, including security and timeout properties. These properties are the default for all the administrative connections that use either the SOAP JMX connector or the IPC JMX connector between processes that run in a particular profile. For instance, the wsadmin program running under a particular profile uses the property values from these files for the SOAP connector behavior and the IPC connector behavior unless the properties are overridden by some other programmatic means.

To view the JMX connector custom properties console page that goes with this topic, click Servers > Server Types > WebSphere application servers > server_name > Administration > Administration services > JMX connectors > connector_type > Custom properties.


SOAP connector properties

This section discusses the following JMX connector properties that pertain to SOAP connectors:

Configuration URL:

Specify the configuration Universal Resource Locator (URL) property if you want a program to read SOAP properties from this file. We can set the property by using one of the following options:

SSL security:

Enable SSL security between the application server and the SOAP client. Set the property by using one of the following options:

Security context provider:

This property indicates the SSL implementation to use between the application server and the SOAP client.

Set the property using the soap.client.props file.

Information Value
Property com.ibm.ssl.contextProvider
Data type String
Valid Values

    IBMJSSE2

Default IBMJSSE2

SOAP request timeout:

The value that you choose depends on a number of factors, such as the size and the number of the applications that are installed on the server, the speed of the machine, and the usage of the machine.

The program default value for the request timeout is 600 seconds. However, other components that connect to the SOAP client can override the default. Components that use the soap.client.props file have a default value of 180 seconds.

Set the property by using one of the following options:

SSL alias:

This property specifies the alias to use for an SSL configuration for client connections. The value of the alias is what you want it to be.

Set the property in the soap.client.props file.

Information Value
Property com.ibm.ssl.alias
Data type String
Default DefaultSSLSettings


IPC connector properties

This section discusses the following JMX connector properties that pertain to IPC connectors:

Configuration URL:

Specify the configuration URL property if you want a program to read IPC properties from this file. We can set the property by using one of the following options:

IPC request timeout:

The value that you choose depends on a number of factors, such as the size and the number of the applications that are installed on the server, the speed of the machine, and the usage of the machine.

The program default value for the request timeout is 600 seconds. However, other components that connect to the IPC client can override the default. Components that use the ipc.client.props file have a default value of 180 seconds.

Set the property by using one of the following options:

SSL security:

Enable SSL security between Application Server and the IPC client. Set the property by using one of the following options:

Security context provider:

This property indicates the SSL implementation to use between the application server and the IPC client.

Set the property using the ipc.client.props file.

Information Value
Property com.ibm.ssl.contextProvider
Data type String
Valid Values

    IBMJSSE2

Default IBMJSSE2

SSL alias:

The alias to use for an SSL configuration for client connections. The value of the alias is what you want it to be.

Set the property in the ipc.client.props file.

Information Value
Property com.ibm.ssl.alias
Data type String
Default DefaultSSLSettings


SOAP, RMI, JSR160RMI, and IPC connector properties

This section discusses JMX connector properties that pertain to the following SOAP connectors, RMI connectors, JSR160RMI connectors, and IPC connectors:

Connector type:

A connector type of SOAP, RMI, JSR160RMI, or IPC depends on whether the application server connects to a SOAP server, an RMI server, a JSR160RMI server, or an IPC server. We can set the property by using one of the following options:

Disable a connector:

We can enable or disable any of the JMX connectors from the console.

Host:

The host name or the IP address of the server to which the application server connects. The server can be a SOAP server, an RMI server, a JSR160RMI server, or an IPC server. We can set the property by using one of the following options:

Password:

The password that the application server uses to access the SOAP server, the RMI server, the JSR160RMI server, or the IPC server. We can set the property by using one of the following options:

Port:

The port number of the server to which the application server connects. The server can be a SOAP server, an RMI server, a JSR160RMI server, or an IPC server. We can set the property by using one of the following options:

User name:

The user name that the application server uses to access the SOAP server, an RMI server, a JSR160RMI server, or an IPC server. We can set the property by using one of the following options:


RMI connector properties

This section discusses the following JMX connector properties that pertain to RMI connectors:

Disable the JSR 160 RMI connector:

Support for JMX Remote API (JSR 160) is enabled by default so that you automatically receive specification-compliant JMX function. To disable the function for a particular server, set the property by using one of the following options:


Related concepts

  • Additional APIs


    Related tasks

  • Administer nodes and resources
  • Configure security

  • JMX connectors
  • Administrative properties for


    Related information:

  • SOAP connector and Inter-Process Communications connector properties files