Free 30 Day Trial
Find the root-cause of your cloud, hybrid-cloud
or on-prem performance issues
|
||
|
Managing the IBM WebSphere Application – 4/5.x Server
After installation of the eG Agent, please follow the following steps to configure eG to monitor WebSphere Application from the eG Manager.
Now, if you proceed to log out of the administrative interface, a list of unconfigured tests (see Figure 1) will appear prompting you to configure tests for the WebSphere Server.
Figure 1 : A page displaying WebSphere tests to be configured
Click on, say, Ws Beans test to move to the page that facilitates test configuration (see Figure 2). This test reports the performance metrics that determines the functioning of the EJB groups.
Figure 2 : Specifying the test parameters for a WebSphere application
Here, select the WebSphere server for which the test is to be configured, click on the Configure button, and provide the following information:
serverhostname - Specify the node name of the server instance being monitored. To know the node name that is to be specified against the serverhostname parameter, do the following:
Expand the Servers node in the tree structure in the left pane of the console, and click on the Application Servers link within (see Figure 3).
Figure 3 : The WebSphere Administrative Console displaying the list of application server instances
servername – Specify the name of the WebSphere server instance to be monitored. To know the instances of a WebSphere server currently available, do the following:
Then, login to the administrative console and expand the Servers node in the left pane of the console. Next, click on the Application Servers sub-node under the Servers node (see Figure 4).
ndmanager - The ndmanager parameter is applicable only under the following circumstances:
In the case of situation (a), in the ndmanager text box, provide the host name of the node manager that manages the application servers in the cluster. To know the name of the node manager, do the following:
Using the tree-structure in the left pane of the Administrative Console that appears (see Figure 5), drill down to the Deployment Manager node within System Administration.
Figure 6 will then appear. Here, select the SOAP_CONNECTOR_ADDRESS link.
The fully qualified domain name displayed against Host in Figure 7 should be specified as the host name of the NODE MANAGER in the ndmanager text box of Figure 2.
In the case of situation (b), enter the SERVERHOSTNAME itself as the NDMANAGER.
If both conditions (a) and (b) do not apply, then specify none here.
connectorport – The connectorport parameter is applicable only under the following circumstances:
If the WebSphere server being monitored is one of many instances of the server running on the same host
In case of situation (a), the connectorport parameter will take the port number using which the node manager communicates with the WebSphere servers in the cluster. The connector port can be a SOAP port or an RMI port. To know the port number, do the following:
From the Node manager’s host, open the <WEBSPHERE_INSTALL_DIR>\DeploymentManager\properties\wsadmin.properties file (see Figure 8).
In case of situation (b), do the following to know the connectorport.
Expand the Servers node in the tree-structure in the left pane of the console, and click on the Application Servers link. A list of application server instances will then appear in the right pane (see Figure 9).
Click on the server instance being monitored. Doing so invokes Figure 10 that displays the Configuration of the chosen server instance.
Figure 10 : The Configuration of the server instance being monitored
Scroll down the Configuration to view the End Points link (see Figure 11). Once you locate the End Points link, click on it.
Figure 12 will then appear. Click on the SOAP_CONNECTOR_ADDRESS link in Figure 12.
The Port displayed in Figure 13 that appears should be used as the connectorport in situation (b).
Figure 13 : Viewing the CONNECTORPORT of the server instance being monitored
If both (a) and (b) do not apply, specify none against connectorport.
DETAILED DIAGNOSIS - To make diagnosis more efficient and accurate, the eG Enterprise embeds an optional detailed diagnostic capability. With this capability, the eG agents can be configured to run detailed, more elaborate tests as and when specific problems are detected. To enable the detailed diagnosis capability of this test for a particular server, choose the On option. To disable the capability, click on the Off option.
The option to selectively enable/disable the detailed diagnosis capability will be available only if the following conditions are fulfilled:
So, click on Processes test and proceed to configure it.
Note:
For Processes Test configuring procedure, refer to Configuring and Monitoring Mail Servers document.
Remember that the process pattern has to be specified in the following format:
PROCESSNAME:PROCESSPATTERN
For example, the process pattern can be specified as below:
WebSphere:*/opt/WebSphere/AppServer/java/jre/bin/exe/java*-Xmx128m*-Xminf0.15*-Xmaxf0.25*–X*