Use this Knowledge Script to start or stop the Java server that the AppManager managed object uses to communicate with WebSphere Application Server. This Java server must be running in order for WebSphere Application Server Knowledge Scripts to work properly.
Typically, you do not need to manually start or stop the Java server. The Java server starts automatically when you discover WebSphere Application Server.
If you encounter problems with WebSphere Application Server Knowledge Scripts collecting performance data, use this Knowledge Script to stop and restart the Java server.
When you discover WebSphere Application Server, you specify the port that the Java server uses to communicate with the managed object. You can use this Knowledge Script to update the communication port on the Java server without rediscovering WebSphere Application Server. To change the listening port for the Java server, you must stop and restart the Java server to apply your changes.
WebSphere Application Server
The default interval for this script is Run Once.
Set the following parameters as needed:
|
Description |
How to Set It |
|---|---|
|
Event? (y/n) |
Set to y to raise an event if the Java server cannot be started or stopped. The default is y. |
|
Event severity when agent cannot be started or stopped |
Set the event severity level, from 1 to 40, to indicate the importance of the event. The default is 10. |
|
Start agent? (y/n) |
Set to y to start the agent, or n to stop the agent. The default is y. |
|
TCP port |
Specify the TCP port to be used by the Java server when listening for requests. The same port should normally be specified for all computers on which the Java server runs. However, this is strictly required only if you intend to run the RequestMetrics Knowledge Script. The default TCP port is 4000. |