Input variables for JMX polling Wizards

Home  Previous  Next

Here is a recapitulative table with the input variables required to connect to the various JMX application servers.

JMX Application Server

Input Variables

JBoss by Redhat

Connection Information

Host: Name of host server where the JBoss application server is installed
Port: JBoss port number (1099 by default for JBoss 3.2.x, 4.x, 5.x, and 6.x; 9999 for JBoss 7.x). Can be modified

 

Additional Information for JBoss 3.2.x, 4.x, and 5.x

Initial context factory: org.jnp.interfaces.NamingContextFactory by default. Can be modified
URL package prefixes: org.jboss.naming:org.jnp.interfaces (by default). Can be modified

 

Connection Account

Principle: Username
Credentials: Password
Path to Java on the local server: java bin path
Connection timeout period: 120 seconds (by default). Can be modified.

JOnAS

Connection Information

Host: Name of host server where the JOnAs application server is installed
Port: Port number. (By default: 1091). This is linked to the protocol used. Can be modified

 

Additional Information

Server name: Name given to the JOnAS application server
Initial context factory: com.sun.jndi.rmi.registry.RegistryContextFactory (by default). Can be modified
Protocol: JRMP or IIOP
URL package prefixes: org.objectweb.jonas.naming (by default) Can be modified

 

Connection Account

Principle: Username
Credentials: Password
Path to Java on the local server: java bin path
Connection timeout period: 120 seconds (by default). Can be modified.

BEA WebLogic

Connection Information

Host: Name of host server where the WebLogic application server is installed
Port: Port number. (By default: 7001). Can be modified

 

Additional Information

Initial context factory: weblogic.jndi.WLInitialContextFactory (by default) Can be modified

 

For WebLogic 9.x and higher

JNDI: weblogic.management.mbeanservers.domainruntime (by default). Can be modified

 

For WebLogic 8.x

JNDI name: weblogic.management.adminhome (by default). Can be modified

 

Connection Account

Principle: Username
Credentials: Password
Path to Java on the local server: java bin path
Connection timeout period: 120 seconds (by default). Can be modified.

IBM WebSphere

Connection Information

Host: Name of host server where the WebSphere application server is installed
SOAP port: Enter port number. The first profile created on WebSphere is by default given the number 8880 and every profile created on WebSphere is allotted a new SOAP port number by increasing the count from 8880. This can be modified.

 

To connect to the WebSphere AS, it is essential to connect to certain credential files: ClientKeyFile.jks and ClientTrustFile.jks. These files are profile-specific and are created and stored by WebSphere under %IBM_HOME%\profile\profilename\etc.

Depending on the security of your environment, either give the path to these files to where the WebSphere AS resides, or, copy them from there to your local file-system.

 

Additional Information

TrustStoreFile path: Enter the path to the file ClientTrustFile.jks.
TrustStore password: Enter the password created on WebSphere for your profile (default WebAS)
KeyStoreFile path: Enter the path to the file ClientKeyFile.jks
KeyStore password: Enter the password created on WebSphere for your profile (default WebAS)
Server name: Name of the WebSphere application server.
Node name: Enter node name allotted to your profile. By default WebSphere assigns a unique node name to each profile created.

 

Connection Account

Principle: Username
Credentials: Password
Path to Java on the local server: java bin path
Connection timeout period: 120 seconds (by default). Can be modified.

Generic JMX applications

Connection Information

Host: Name of host server where the generic JMX application server is installed
Port: Enter port number

 

Generic environment additional information

Server name: Name of generic server
Protocol: RMI or IIOP

 

Connection Account

Principle: Username
Credentials: Password
Path to Java on the local server: java bin path
Connection timeout period: 120 seconds (by default). Can be modified.

 

The application server should be started with the option:

Dcom.sun.management.jmxremote.port=portNumber

Using this option starts a dedicated JMX agent for this particular application. The Monitoring Studio generic JMX client needs to use this port number to establish a connection.

 


See Also

Java MBean Polling (JMX)

JBoss

JOnAS

Numeric Value extraction

String Search

SW_JMX

WebLogic

WebSphere