Running the WebSphere seed sensor

This topic describes how to run the WebSphere® seed sensor.

To run the WebSphere seed sensor, complete the following steps:
  1. Start the TADDM server.
  2. Open the Discovery Management Console.
  3. Add the IP address of the server where the WebSphere seed file is located to a scope.
  4. In the Access List, add the access credentials of the server where the WebSphere seed file is located.
  5. If security is enabled for the WebSphere server being discovered, add the credential entry for the WebSphere server. If you want to use the entry with a scope restriction, you must include the IP address of your WebSphere server in the discovery scope in addition to the IP address of the host, where the WebSphere seed file is located.

    You also need the client-side SSL certificate when creating the Access List entry. This certificate must be exported from the mainframe security product for example, Resource Access Control Facility (RACF®) and transferred to a tool for maintaining digital certificates. Use this tool for example iKeyman, to generate a JKS or PKCS12 file. This file contains the client-side SSL certificate in a format that can be used by TADDM. The JKS or PKCS12 file must then be used for the SSL settings in the TADDM WebSphere Access List entry for both keystore and truststore certificates.

  6. Complete the following steps:
    1. Configure the IdmlFileUDS sensor using the Discovery Management Console:
      1. In the Discovery Profiles window, click IdmlFileUDS.
      2. Click New.
      3. Type the sensor configuration name and description.
      4. Select Enable Configuration.
      5. Double-click /data/latest/dist/var/dla/zos/was and type the location of the WebSphere XML seed files. This location is the server where the WebSphere seed file is located.
      6. Double-click and type the IP address of the machine on which the seed file is located.
    2. Create a discovery profile that includes the following sensors:
      • Anchor Sensor
      • Sensor name entered in step a. (The modified IdmlFileUDS sensor created previously.)
      • PortSensor
      • PingSensor
      • SessionSensor
      • GenericServerSensor
      • WebSphereIdmlSeedSensor
      • WebSphereCellSensor
      • WebSphereNodeSensor
      • WebSphereSensor (select this sensor instead of WebSphereCellSensor and WebSphereNodeSensor only if com.collation.websphere.performance.setting=false)

      The sensors can require additional sensors to be enabled in the profile by default, enable all additional sensors.

    3. Save the configuration file.
  7. Run the discovery and select the scope to include the server and the discovery profile that you created.