JMX connector settings

Use this page to view the configuration for a Java™ Management Extensions (JMX) connector, which makes connections between server processes.

To view this administrative console page, click one of the following paths:

The Simple Object Access Protocol (SOAP) connector, the Remote Method Invocation (RMI) connector, the JMX Remote application programming interface (JSR 160) Remote Method Invocation (JSR160RMI) connector, or the Inter-Process Communications (IPC) connector connect to a controller (server). WebSphere® Application Server for z/OS® internally routes MBean requests from a controller to its servant regions as appropriate.

Type

Specifies the type of the JMX connector.

Data type Enumeration
Default SOAPConnector
Range
SOAPConnector
For JMX connections using Simple Object Access Protocol (SOAP).
RMIConnector
For JMX connections using Remote Method Invocation (RMI).
JSR160RMIConnector
For JMX connections using JMX Remote application programming interface (JSR 160) Remote Method Invocation (JSR160RMI).
IPCConnector
For JMX connections using Inter-Process Communications (IPC).
Avoid trouble: [jun2010] IPC_CONNECTOR_ADDRESS is a special end point. The end point must be defined as 'localhost'. Editing a hostname definition from 'localhost' to any other <hostname> is not permitted if you plan to use this same server as a template to create another server in another node and which is to have an end point definition different than <hostname>. [jun2010]
jun2010
gotcha



Related tasks
Administering nodes and resources
Related reference
Java Management Extensions connector properties
Reference topic    

Terms of Use | Feedback

Last updated: Oct 22, 2010 12:21:29 AM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=compass&product=was-nd-zos&topic=uxml_rconnector_inst
File name: uagt_rconnector_inst.html