|
Prerequisites
Monitoring WebSphere application servers requires the presence of certain files on the RSM depending on the version of the WebSphere server.
For WebSphere 5.x
| • | Monitoring Studio Express requires the IBM 32-bit SDK v5.0 to be installed on the same server as the RSM. |
| • | Connection to the WebSphere application server requires the presence of certain credential files on the RSM: DummyClientKeyFile.jks and DummyClientTrustFile.jks |
These files are created and stored by WebSphere under %IBM_HOME%\AppServer\etc. It is vital to copy both files to the local file-system of the server where the RSM is running.
For WebSphere 6.x
| • | Connection to the WebSphere application server requires the presence of certain credential files on the RSM: DummyClientKeyFile.jks and DummyClientTrustFile.jks |
These files are profile-specific and are created and stored by WebSphere under %IBM_HOME%\profile\profilename\etc. It is vital to copy both files to the local file-system of the server where the RSM is running.
To create an instance of Studio - JMX Polling (WebSphere)
| 1. | Go to the Configure tab, click on the element on which you wish to use the tool. |
 If the element was created using Element Profile then add the new application class through the same route.
| 2. | On the Element Properties page, scroll to the Application Class section, click on Add. |
| 3. | On the Add Applications page, select Miscellaneous from the drop down category list and click Next. |
 All application classes belonging to the BMC Performance Manager Express Monitoring Studio package are listed under Miscellaneous.
| 4. | On the Available Application Classes page, select Studio - JMX Polling (WebSphere) and select the number of instances you wish to create, click Next. You can create up to 10 instances at this stage, or create just 1 now and add others later. |
| 5. | You arrive at the Properties and Credentials page. Enter the information required for setting up the JMX Polling (WebSphere) instance and click Add. |
Information required for monitoring
|
|
|
Descriptive Label
|
Label describing the application class/monitoring tool
|
Collection Interval
|
Frequency of collection (monitoring/polling). Unit: Minutes (Default 5 minutes)
|
Credentials
Principle
Credentials
Credentials
|
Login used to connect to the application server
Password associated with the above login
Shared credentials used for authentication
|
Hostname
|
Hostname or IP address of the server on which the WebSphere application server is running (Appears by default)
|
WebSphere Environment
|
Select the version of the WebSphere application server.
|
SOAP Port
|
Enter the port number. (8880 by default)
For WebSphere v6.x, the first profile created on WebSphere is by default 8880 and every profile created on WebSphere is allotted a new SOAP port number by increasing the count from 8880. This can be modified. WebSphere v5.x is not "profile-specific".
|
TrustStoreFile Path
|
Enter the complete path to the file DummyClientTrustFile.jks which is on the RSM server.
WebSphere 5.x: The above-mentioned file is to be copied from %IBM_HOME%\AppServer\etc and stored on the RSM server in order to connect to the WebSphere application server.
WebSphere 6.x: The above-mentioned file is profile-specific and is created and stored by WebSphere under %IBM_HOME%\profile\profilename\etc. This is to be copied to the RSM server in order to enable connection to the WebSphere application server.
|
TrustStore Password
|
Enter the SSL Trust password. Default:WebAS (case-sensitive). It is profile-specific on WebSphere 6.x.
|
KeyStoreFile Path
|
Enter the complete path to the file DummyClientKeyFile.jks which is on the RSM server.
WebSphere 5.x: The above-mentioned file is to be copied from %IBM_HOME%\AppServer\etc and stored on the RSM server in order to connect to the WebSphere application server.
WebSphere 6.x: The above-mentioned file is profile-specific and is created and stored by WebSphere under %IBM_HOME%\profile\profilename\etc. This is to be copied to the RSM server in order to enable connection to the WebSphere application server.
|
KeyStore Password
|
Enter the SSL Key password. Default:WebAS (case-sensitive). It is profile-specific on WebSphere 6.x.
|
Debug Mode
|
"Yes" enables the debug mode, while "No" disables it. The debug output produced is stored on the RSM server in a file located at: %RSM_HOME%/RSM(xx)/SEN_MS/sen_ms_debug_jmx_(servertype)_hostname.log.
File name example: sen_hw_debug_jmx_WebSphere6x_hostname.log.
Do not leave the debug mode enabled for too long as the debug file may grow indefinitely.
|
| 6. | Enter the information and click Next and you arrive at the Properties and Credentials page asking for the Input Properties of the new instance. Enter the required input: |
Input Properties
|
|
|
Descriptive Label
|
Enter a label to describe this new WebSphere polling instance.
|
Domain Name
|
Enter the domain name under which the attribute to be monitored is present.
|
Key Property
|
Enter the unique key property name under which the attribute to be monitored is present.
|
Attribute Name
|
Enter the name of the attribute whose value you wish to collect.
|
To obtain the above properties from the JMX application, you can use the Sentry JMX Browser.
| 7. | After entering the input properties, either click Next to arrive at the thresholds setting page, or, add a string search or a numeric value extraction for this JMX polling query instance. The string search and numeric value extraction instances can also be set later on this instance. |
| 8. | On clicking Next the input properties are displayed grayed-out. This page allows you to verify, edit or delete the newly-created instances and/or add another instance for the same element. If the information is correct, go on to the next step. |
| 9. | You are at the Thresholds, Properties and Credentials page. Set/modify thresholds and alert conditions:
By default, the Execution Status parameter is enabled to raise an Alarm if the connection to the application server fails.
You can modify this setting if it does not suit your requirements. Thresholds and alerts can be set for each parameter. Check the Warning and/or Alarm boxes next to the parameters to activate alerts as per your specific requirements. See details of parameters and alert conditions in the Reference Guide. |
Thresholds can be set or modified at any time by clicking on the element > Configure > ”application class name” > Edit Thresholds, Properties and Credentials.
| 10. | Click on Finish. Changes have been Saved message pops up, and an icon appears in the left pane of the window displaying the newly-created instance. You can also see the new instance of the class under Application Classes. |
You have successfully remotely executed a JMX Polling on a WebSphere application server and can now monitor it.
Editing or Deleting an instance
To edit or delete the instance, follow the regular procedure as for all Performance Managers on the Portal, or see Editing or Deleting an Instance.
|
