Use the Discovery_WebSphereAppSrvUNIX Knowledge Script to discover instances of WebSphere Application Server. When you run the discovery Knowledge Script, the agent must be running under the root account and the PMI monitoring level must be set to Extended.
NOTE:If a discovered WebSphere Application Server object includes a colon (:) in the name, the Operator Console replaces the colon with a backslash (\). For example, if the object name is Object: ws/WSSecureMap, the object name is displayed as Object\ ws/WSSecureMap.
Use this script to discover any or all of the application servers running on a computer. However, if multiple application servers (associated with either a single WebSphere Application Server installation, or multiple coexisting installations) are to be discovered on a single computer, they must all be discovered simultaneously, with a single execution of the discovery script. This is because each time discovery is run, the discovered resources are replaced, so that if one instance is discovered, and then a second instance is discovered, the resources associated with the instance discovered first will be lost.
This Knowledge Script takes the URL of the Performance servlet Web application as a parameter. This URL is relative to the computer being discovered, so the default URL, which points to localhost, will probably work on most single-host WebSphere Application Server deployments. However, in multi-node WebSphere Application Server deployments, the Performance servlet normally runs on a single server in the domain. In such cases, you will need to change the value of this parameter to point to the proper location.
You can run discovery against multiple computers at once by running the discovery script on a server group. However, all application servers being discovered concurrently must be members of the same WebSphere Application Server domain, with the same Performance servlet URL providing performance data for each of the servers. If you run the discovery script against more than one server, make sure you change the URL from localhost to the appropriate hostname, or each server attempts to contact the Performance servlet on the local computer.
If you must use a proxy server to access the Performance servlet URL, you need to specify the proxy server host name or IP address, and the proxy server port number. If the proxy server requires a login and password, supply them here. If no proxy lies between the agent computer and the Performance servlet, leave all four proxy fields blank.
NOTE:
If you specify a proxy server, the Performance servlet URL that you specify should not include a hostname of localhost, because localhost will be interpreted by the proxy server, causing the proxy server to attempt to connect to itself. When using a proxy server, the Performance servlet URL must specify the actual hostname of the computer being discovered.
The proxy server you specify will be used when accessing the optional servlet URL specified in the HealthCheck Knowledge Script, as well as when accessing the Performance servlet. You cannot specify a separate proxy, or no proxy, for the HealthCheck servlet.
As part of the discovery process, this Knowledge Script:
Starts a Java server on the discovered host that the AppManager managed object uses to communicate with WebSphere Application Server.
Specifies the port that the Java server uses to communicate with the managed object.
If you encounter problems with WebSphere Application Server Knowledge Scripts collecting performance data, use the NetIQAgent Knowledge Script to stop and restart the Java server.
If you run the RequestMetrics Knowledge Script, ensure that the same port number is specified for all the computers you discover. If you do not intend to use the RequestMetrics Knowledge Script, this restriction does not apply. However, you still must supply a valid (otherwise unused) TCP port number.
Set the Values tab parameters as needed.
|
Description |
How to Set It |
|---|---|
|
Raise event if discovery succeeds? (y/n) |
Set to Yes to raise an event when WebSphere resource discovery succeeds. The default is n. |
|
Event severity when discovery succeeds |
Specify the event severity, from 1 to 40, to indicate the importance of an event in which WebSphere resource discovery succeeds. The default is 25. |
|
Event severity when discovery fails |
Specify the event severity, from 1 to 40, to indicate the importance of an event in which WebSphere resource discovery fails. The default is 5. |
|
Event severity for partial discovery |
Specify the event severity, from 1 to 40, to indicate the importance of an event in which WebSphere resource discovery partially succeeds. The default is 15. |
|
Perfservlet URLs (semicolon-separated) |
Specify one or more URLs of the Performance servlet Web application, separated by semicolons. For the discovery process to succeed, the Performance servlet must be running and able to provide performance data for application servers running on the target host. The default is http://localhost:9080/wasPerfTool/servlet/perfservlet. |
|
Directories to search for WebSphere home directory (semicolon-separated) |
Specify the list of directories to search for the WebSphere Application Server home directory. Separate multiple directory entries with semicolons. The default is /opt/IBM/WebSphere/AppServer. |
|
TCP port for accepting requests |
Specify the TCP port that the Java server uses to communicate with the AppManager managed object. The same port must be specified for all computers on which the agent runs in order for the RequestMetrics Knowledge Script to function properly. The default TCP port is 4000. |
|
Proxy host |
Specify the host name or IP address of the computer on which the Web proxy server is running. If you do not use a proxy server, leave this field blank. |
|
Proxy port |
Specify the port number to use when connecting to the proxy server. If you specify a proxy host, you must specify a port as well. If you are not using a proxy server, leave this field blank. |
|
Proxy login |
Specify the username to use when logging into the proxy server. If the proxy server does not require authorization, or if you are not using a proxy server, leave this field blank. |
|
Proxy password |
Specify the password associated with the proxy login. If the proxy server does not require authentication, or if the login being used does not have an associated password, or if you are not using a proxy server, leave this field blank. |
|
Full path of the NetIQAgent JRE directory |
Specify the full path to the NetIQ UNIX agent 32-bit Java Runtime Environment (JRE) directory. For more information about JRE requirements, see Section 2.1, System Requirements. The default is a null string. NOTE:This path should terminate with the jre directory and not the bin directory. For example, /usr/java/jdk1.8_20/jre. IMPORTANT:If you do not specify a NetIQAgent JRE directory, Discovery will, by default, search the paths provided for parameter Directories to search for WebSphere home directory. If the first discovered JRE is a 64-bit instance, the Java portions of this product will not work. |