Agents Administration - Tests
 

Configuration of WsORBSumTest

The WsORBSumTest reports statistics pertaining to the ORBs (Object Request Brokers) on a WebSphere server. The default parameters associated with this test are as follows:

  • The TEST PERIOD list box helps the user to decide how often this test needs to be executed. 

  • In the HOST text box, the host name of the server for which the test is to be configured has to be specified.

  • The port number to which the server is listening to has to be mentioned in the PORT text box.

  • The WEBSERVERPORT text box indicates the port number through which the WebSphere applications can be accessed.

  • Select Yes if SSL (Secured Socket Layer) is to be used to connect to the WebSphere server, and No if it is not. 

  • In the SERVERHOSTNAME text box, specify the node name of the server instance being monitored. To know the node name, do the following:

    • Login to the WebSphere Administrative Console.

    • Expand the Servers node in the tree structure in the left pane of the console, and click on the Application Servers link within.

    • A list of application server instances and their corresponding node names will then appear in the right pane of the console. From this list, you can figure out the node name that corresponds to the application server instance being monitored, and specify that name against the SERVERHOSTNAME parameter.

  • The NDMANAGER parameter is applicable only under the following circumstances:

    1. If the WebSphere server being monitored belongs to a cluster, or,
    2. If the WebSphere server being monitored is one of many instances of the server running on the same host

    In the case of situation (1), 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:

    • Login to the Administrative Console of the node manager using the URL http://{IPoftheWebSphereAppServer'sNodeManager}:{Adminport}/admin/.

    • Using the tree-structure in the left pane of the Administrative Console that appears, drill down to the Deployment Manager node within System Administration.

    • Select the Configuration tab that appears in the right pane, and scroll down to the End Points link in the Additional Properties section.

    • Once you locate the End Points link, click on it, and in the page that appears, click on the SOAP_CONNECTOR_ADDRESS link.

    • In the subsequent page, a fully qualified domain name will be displayed against Host. This is the name that should be specified as the host name of the node manager in the NDMANAGER text box.

    In case of situation (2), enter the SERVERHOSTNAME itself as the NDMANAGER.

    If both conditions (1) and (2) do not apply, then specify 'none' here.

  • The CONNECTORPORT parameter is applicable only under the following circumstances:

    1. If the WebSphere server being monitored belongs to a cluster, or,
    2. If the WebSphere server being monitored is one of many instances of the server running on the same host

    In case of situation (1), 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.

    • Two entries that read as follows will be present in the wsadmin.properties file:

      com.ibm.ws.scripting.port={port_number}

      #com.ibm.ws.scripting.port={port_number}

      Both the entries will have port numbers against them. However, the uncommented entry (the entry without the #) is the one that denotes an active port. Therefore, specify the corresponding port number as the CONNECTORPORT.

    In case of situation (2), do the following to know the CONNECTORPORT:

    • Login to the WebSphere Administrative Console.

    • 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.

    • Click on the server instance being monitored. Doing so invokes the Configuration of the chosen server instance.

    • Scroll down the Configuration to view the End Points link. Once you locate the End Points link, click on it.

    • Next, click on the SOAP_CONNECTOR_ADDRESS link in the End Point Names that are displayed.

    • The Port displayed in the page that appears next should be used as the CONNECTORPORT in situation (2).

    If both (1) and (2) do not apply, specify 'none' against CONNECTORPORT.

  • If security has been enabled for the WebSphere server being monitored, then provide a valid USER name and PASSWORD, and confirm the password by retyping it in the CONFIRM PASSWORD text box. If the WebSphere server does not require any authentication, then the USER, PASSWORD, and CONFIRM PASSWORD text boxes should contain the default value 'none'.

  • By default, the ENCRYPTPASS flag is set to YES, indicating that the PASSWORD of the WebSphere server is encrypted by default. To disable password encryption, select the NO option.

  • In the SERVERNAME text box, specify the name of the WebSphere server instance to be monitored. To know the instances of a WebSphere server currently available, first, connect to the WebSphere Administrative console using the URL: http://{IP of the WebSphere server:Port number of the WebSphere server}\admin. 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. A list of server instance Names and their corresponding Node values will then be displayed in the right pane. One of the displayed server instances can be specified as the value of the SERVERNAME parameter.

  • In the TIMEOUT, specify the maximum duration (in seconds) for which the test will wait for a response from the application server. The default TIMEOUT period is 60 seconds.

  • If multiple components of the same component type are awaiting configuration, then an APPLY TO OTHER COMPONENTS check box will appear in this page. Clicking on this check box will allow you to apply the configuration to all/selected components of that type.

  • Once the necessary values have been provided, clicking on the UPDATE button will register the changes made.

When changing the configuration for specific servers, a “*” beside the text box corresponding to the parameter signifies that these values have to be manually configured by the user. The parameter values that require to be configured will typically be prefixed with a “$” or contain a series of “*”. A value of "none" in the parameter value indicates that the corresponding parameter value can be changed if required.