Input variables for JMX polling Wizards

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). Can be modified

Additional information

▪	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 home path

JOnAS

Connection Information

▪	Host: Name of host server where the JOnAs application server is installed

▪	Port: Port number. (By default: 1099). 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

▪	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 home path

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

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

For WebLogic 8.x

▪	Server name: Name given to WebLogic application server

Connection Account

▪	Principle: Username

▪	Credentials: Password

▪	Path to Java on the local server: java home path

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.

▪	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 home path

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: Name of protocol

The Monitoring Studio generic client connects to the JMX agent using the protocol RMI or IIOP. If you use the protocol RMI the default server name is “jmxrmi” and if you use the IIOP protocol then the default server name is “jmxiiop”.

Connection Account

▪	Principle: Username

▪	Credentials: Password

▪	Path to Java on the local server: java home path

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.