Monitoring IBM WebSphere Application Server

On the Real-Time Monitoring tab, in the Monitor group, click System. The Data Source wizard opens.

Click the Select from predefinded Data Sources option button.

Click Next. The System selection page opens.

Expand the Application Server folder and the IBM WebSphere Application Server folder.

Click the IBM WebSphere <version> (JMX MBean Server) node and then click Next. The Connection parameters page opens.

In the Hostname field, specify the host on which WebSphere is running.

In the User and Password fields, specify a user with administrator permissions for the above specified host.

Optional: In the Alias field, specify an alias for the monitored server.

Click Server Configuration... The JMX Connection Configuration window opens.

Specify the Java Home directory and the Application Server install directory. Use a UNC path (for example, \\<server name>\c$\IBM\WebSphere\AppServer\java).

Note: If you cannot specify a UNC path, copy the application server installation directory to your local machine and specify a local path.

Specify additional JVM parameters based on WebSphere security settings.

JVM vendor Security settings	IBM	SUN
Disabled administrative security	Without additional JVM parameters	Without additional JVM parameters
Enabled administrative security Inbound CSIv2 Transport Layer = TCP/IP	Additional JVM parameter: -Dcom.ibm.CORBA.ConfigURL (already predefined)	Additional JVM parameter: -Dcom.ibm.CORBA.ConfigURL (predefined)
Enabled administrative security Inbound CSIv2 Transport Layer = SSL-supported	Additional JVM parameters: -Dcom.ibm.CORBA.ConfigURL (predefined) -Dcom.ibm.SSL.ConfigURL	Does not work
Enabled administrative security Inbound CSIv2Transport Layer = SSL-required	Additional JVM parameters: -Dcom.ibm.CORBA.ConfigURL (already predefined) -Dcom.ibm.SSL.ConfigURL	Does not work

Note: If your WebSphere server has enabled administrative security and the inbound CSIv2 transport layer is SSL-supported (or SSL-required), copy the application server installation directory to your local machine. Specify Additional JVM parameters according to the table above. The Additional JVM parameters field holds the predefined parameter -Dcom.ibm.CORBA.ConfigURL.

The value for the -Dcom.ibm.CORBA.ConfigURL parameter must be the URL path to the file sas.client.props. The default sas.client.props file is located in the folder %INSTALL_DIR%/Include/jmx-config/WebSphere%MAJOR_VERSION%. For example: For WebSphere 7, the URL path is C:\Program%20Files%20(x86)\Silk\Silk%20Performer%2010.0\Include\jmx-config\WebSphere7. If your server has specific settings, you can use the sas.client.props file from the properties folder of the WebSphere profile. For Example: file:/C:\Program%20Files%20(x86)\IBM\WebSphere\AppServer1\profiles\AppSrv01\properties\sas.client.props

Pay attention to the following two variables and their values in your sas.client.props file: com.ibm.CSI.performTransportAssocSSLTLSRequired=false and com.ibm.CSI.performTransportAssocSSLTLSSupported=true

The value for the -Dcom.ibm.SSL.ConfigURL parameter must be the URL path to the file ssl.client.props, which is found in the properties folder of the WebSphere profile. For example: file:/C:\Program%20Files%20 (x86)\IBM\WebSphere\AppServer1\profiles\AppSrv01\properties\ssl.client.props.

Pay attention to the variable user.root in the file ssl.client.props. It must contain the valid path to the profile folder with the etc directory that contains the key- and trust-files. Blanks in the URL path to the files sas.client.props and ssl.client.props must be replaced with %20.

Click OK.

Click Next. The JMX Data Source Browser opens.

Choose MBeans for those measures that you want to include in the initial monitor view. Select the type of measures (Average, Sum, or Incremental) and click Add.

Click Close. The Select displayed measures page opens.

Check the checkboxes for those measures that you want to include in the initial monitor view.

Click Finish.