Preparing to run the WebSphere seed sensor

Before running the WebSphere® seed sensor, you must create a seed file.

Before running the WebSphere seed sensor, complete the following steps:

Choose the appropriate method to create the WebSphere seed file:
- To discover WebSphere on a z/OS® system using the Discovery Library Adapter, use the WebSphere Application Server seed utility that generates the seed files automatically from the IdML books created from the z/OS DLA. The utility is provided as a part of the z/OS DLA package.
- To discover WebSphere on a non-mainframe system by manually creating the seed file, use the following file naming conventions when creating the seed file:
  - If you want the file to be included as part of the discovery, the file name must end with a .xml extension.
  - The file name must adhere to the following format:
```
<cellname>_<fqdn>_<port>.xml
```
    An example is c1_0.0.0.0_2809.xml.
  The following example shows the file format:
```
<IDML_WAS_SEED>
  <WAS_ROOT_DIR>/opt/WebSphere/AppServer</WAS_ROOT_DIR>
  <WAS_VERSION>6.0.2.7</WAS_VERSION>
  <SOAP_CONNECTOR_PORT>8880</SOAP_CONNECTOR_PORT>
  <RMI_CONNECTOR_PORT>2809</RMI_CONNECTOR_PORT>
  <JMX_LISTEN_IP_ADDRESS>0.0.0.0</JMX_LISTEN_IP_ADDRESS>
  <HOST_MAPPINGS>
    <HOST_MAPPING>
      <HOST_NAME>wasserver.company.com</HOST_NAME>
      <PRIMARY_IP_ADDRESS>0.0.0.0</PRIMARY_IP_ADDRESS>
      <IP_ADDRESS>0.0.0.0</IP_ADDRESS>
    </HOST_MAPPING>
  </HOST_MAPPINGS>
</IDML_WAS_SEED>
```
  WAS_ROOT_DIR
  
  The directory path where the WebSphere Application Server is installed.
  
  WAS_VERSION
  
  The version of the WebSphere Application Server, which can be found in the product file in the <WebSphere Root Directory>/properties/version directory.
  
  SOAP_CONNECTOR_PORT
  
  The port number is retrieved from the serverindex.xml file for the SOAP_CONNECTOR_ADDRESS endpoint name. For example, <WebSphere Root Directory>/profiles/<app server or dmgr>/conf/cells/<cell name>/nodes/<node name>
  
  If the resource is a deployment manager, use the serverindex.xml file with the following value specified: serverType="DEPLOYMENT_MANAGER".
  
  If the resource is stand-alone component, use the serverindex.xml file with the following value specified: serverType="APPLICATION_SERVER"
  
  RMI_CONNECTOR_PORT
  
  The port number is retrieved from the same serverindex.xml file used to find the soap port, where the endpoint name is BOOTSTRAP_ADDRESS.
  
  JMX_LISTEN_IP_ADDRESS
  
  The IP address that is used to connect through JMX. Typically this address is the same IP address as the WebSphere server.
  
  HOST_MAPPINGS
  
  A list of mappings between the host name and IP address for the WebSphere Application Server or Deployment Manager and each distributed Node Agent.
  
  HOST_MAPPING
  
  One host mapping consisting of a host name, primary IP address, and IP address.
  
  HOST_NAME
  
  The fully qualified domain name.
  
  PRIMARY_IP_ADDRESS
  
  The primary IP address that the host name resolves to.
  
  IP_ADDRESS
  
  The IP address that the host name resolves to, if different from the primary IP address.
Place the .xml files in the $COLLATION_HOME/var/dla/zos/was directory. If the directory does not exist, create the directory. The scope of discovery is controlled by the files in this directory. If discovery of a particular WebSphere server is no longer needed, the file must be removed from this directory or renamed without the .xml extension.
Create a new sensor configuration file when you run the WebSphere seed sensor. Change the location of the XML seed file using the following two tags:

<fileName>

Set this tag to the directory where the WebSphere XML seed files are located.

<scope>

Set this tag to the IP address of the Agile Service Manager server where the WebSphere XML seed files are located.