Discovery of the IBM WebSphere Application Server Target

2 Discovery of the IBM WebSphere Application Server Target

How to add a IBM WebSphere Application Server target in Enterprise Manager.

This section describes how to add a IBM WebSphere Application Server target to Enterprise Manager.

Discovering Targets

After successfully deploying the plug-in, follow these steps to add the plug-in target to Enterprise Manager for central monitoring and management:

Log in to Enterprise Manager.
Go to Setup, select Add Target, and then select Add Targets Manually.
Select Target Type as IBM WebSphere Application Server, select a Monitoring Agent and then click Add Manually.
In the Add IBM WebSphere Application Server page, enter the following properties:
- Target Name: Unique target name across all targets, such as IBM_WebSphere Application Server_Hostname. This is the display name in Enterprise Manager. It represents this SQL Server target across all user interfaces within Enterprise Manager.
- IBM WebSphere Application Server Monitoring Credentials
  - IBM WebSphere Application Server Username: The username used to connect via JMX to WebSphere. This is optional and should only be used if you are using authentication.
  - IBM WebSphere Application Server Password:The password for the account used to connect via JMX to WebSphere Application Server. This is optional and should only be used if you are using authentication.
    
    Note:
    If you wish to use SSL, it must be specified in the ssl.client.props and sas.client.props files. The plug-in will connect using those settings.
- Properties
  - Service URL: This is the JMX Service URL to connect to WebSphere Application Server via JMX.
    Example: service:jmx:rmi//<hostname>:<port>/jndi/JMXConnectorYour port will be specified as the BOOTSTRAP_PORT in your WebSphere Application Server console.

Adding Targets with EMCLI

How to add IBM WebSphere Application Server targets with Enterprise Manager CLI.

To add IBM WebSphere Application Server targets with EMCLI, use the add_target verb, as in the following example:

emcli.bat add_target    
        -name=”WebSphere Application Server Target”    
        -type=”oracle_websphere”    
        -host=”HostTargetName”   
        -properties=”serviceURL+service:jmx:rmi//<hostname>:<port>/jndi/JMXConnector”
        -subseparator=properties=”+”

You will need to specify the following options:

Target name: *-name*
It must begin with an alphabetic character contain only alphanumeric characters, multibyte characters, a space, -, _, ., :, /, (, ) and have a maximum length of 256 characters.
Target type: *-type*
Always use "oracle_websphere" (including the quotes).
Host name: *-host*
Network name of the machine running the Management Agent that is collecting data for this target instance.
Target instance Properties: *-properties*
Name-value pair list of properties for the target instance. The available property names are as follows.
```
serviceURL
JMXUsername
JMXPassword
```
Properties separator delimiter: *-separator=properties*
Specify a string delimiter to use between name-value pairs for the value of the -properties option. The default separator delimiter is “;”.
Properties subseparator delimiter: *-subseparator=properties*

Specify a string delimiter to use between name and value in each name-value pair for the value of the -properties option. The default subseparator delimiter is “:”.

Verifying and Validating the Plug-in

How to verify and validate the IBM WebSphere Application Server plug-in for Enterprise Manager.

After waiting a few minutes for the plug-in to start collecting data, use the following steps to verify and validate that Enterprise Manager is properly monitoring the plug-in target:

Click the WebSphere Application Server target link from the All Targets page.
Verify no metric collection errors are reported by clicking Monitoring and then Metric Collection Errors from the Target menu.
Ensure that reports can be seen, and no errors are reported by clicking Information Publisher Reports in the Target menu and viewing reports for the WebSphere Application Server target type.
Ensure that configuration data can be seen by clicking Configuration and then Last Collected in the Target menu. If configuration data does not immediately appear, click Refresh in the Latest Configuration page.