discover_was
Discovers an IBM Websphere target in Oracle Enterprise Manager. Targets include an IBM Webshpere cell or an IBM Websphere JEE server (for example,websphere_cell or websphere_jeeserver).
For additional information on how to use the discover_was EM CLI verb, refer to Oracle Enterprise Manager Command Line Interface documentation available on the Oracle Technology Network.
Format
emcli discover_was -host -port -version -key_file -dir -agent [-username] [-password] [-debug] [ ] indicates that the parameter is optional.
Options
-
host
Fully qualified name of the host where the WebSphere Application Server is running.
-
version
Websphere Application Server version. Versions 6.0, 6.1, 7.0, 8.0 or 8.5 are allowed.
-
port
SOAP connector port of the server.
-
key_file
The absolute path of the Monitoring Agent Trust file. This option is required if the port is SSL enabled.
-
dir
The absolute path of the directory where Deployment Manager is installed. For remote discovery, specify the path of the directory on the Agent Host where the required jar files have been copied.
-
agent
Monitoring Agent.
-
username
Websphere host username if security is enabled
-
password
Websphere host password if security is enabled.
-
debug
Runs the verb in verbose mode for debugging purposes.
Examples
Example 1
The following example discovers targets in an IBM Websphere cell.
emcli discover_was -host=host1.example.com -version=8.5 -port=1234 -key_file=/path/to/monitoring/agent/trust/store/file -dir=/to/websphere/server/install/home -agent=host1.example.com:12345 -username=was -password=was123
Example 2
The following example discovers a standalone IBM Websphere application server.
emcli discover_was -host=host1.example.com -version=8.5 -port=1234 -key_file=/path/to/monitoring/agent/trust/store/file -dir=/path/to/websphere/server/install/home -agent=host1.example.com:12345 -username=was -password=was123