Configuring the discovery profile

If you want to change the discovery level, update the discovery profile for the IBM® WebSphere® sensor.

To change the default the discovery level for this sensor, complete the following steps:

  1. In the Discovery Profiles window, click New.
  2. In the Create New Profile window, type the profile name, description, and click OK.
  3. In the list of sensors, click the WebSphereCellSensor, and click New.
  4. In the Create Configuration window, type the name and description for your configuration of the WebSphereCellSensor, and select the Enable Configuration check box.
  5. In the Configuration section of the Create Configuration window, to change the discovery level value, select one of the following choices:
    • To enable medium discovery, double-click the value for mediumDiscoveryLevel and change from false to true
    • To enable deep discovery, double-click the value for deepDiscoveryLevel and change from false to true

    If deepDiscoveryLevel is set to true, it runs a deep discovery regardless if shallow and medium discoveries are set to true or false.

  6. Optional: To configure the sensor to discover only servers that are running, click discoverStoppedServers. Then double-click the Value field in the row, and type false.
  7. Click OK to return to the Discovery Profiles window.
  8. Ensure the WebSphereVersionSensor and WebSphereNodeSensor are selected along with the new WebSphereCellSensor configuration you created.
  9. In the Discovery Profiles window, click Save.
  10. Choose this discovery profile when running a discovery.

Sensor properties

shallowDiscoveryLevel, mediumDiscoveryLevel, deepDiscoveryLevel

The WebSphere sensor has three discovery levels, shallow, medium, and deep. By default the shallow discovery level is enabled. To modify the discovery level value, select one of the following choices:

  • To enable medium discovery, double-click the value of mediumDiscoveryLevel and change false to true.
  • To enable deep discovery, double-click the value of deepDiscoveryLevel and change from false to true.

If the deepDiscoveryLevel is set to true, it runs a deep discovery regardless of whether shallow and medium discoveries are set to true or false.

  • The following list contains the information that is captured at each discovery level.
    • Shallow discovery discovers the following components:
      • Application descriptor files
      • Cell, node, server names
      • Cell, node, server type
      • Host system
      • JVM runtime version for every running server
      • Product name and version
      • Root directory
    • Medium discovery discovers the following components:
      • Clusters
      • Configuration files
      • Connections
      • Deployed connector modules
      • Deployed EJB modules
      • Deployed Java EE applications
      • Deployed web modules
      • Efixes
      • EJB containers
      • End points
      • JVM settings
      • Ports
      • Process definition
      • Process monitoring policy
      • Process pools
      • Security, SSL settings, and user registries
      • Virtual hosts
      • Web containers
    • Deep discovery discovers the following components:
      • Cell, node, server, cluster JDBC providers, JDBC data sources, and JDBC dependencies
      • Custom properties
      • Deployment descriptors for Java EE applications and modules
      • JMS providers and JMS destinations
      • Shared libraries
      • Variables
      • Web services
      • Dynamic cache service settings for servers and dynamic clusters
traceSpecification

Sets the trace specification string for enabling trace logging of the WebSphere client code called by the WebSphere sensor. sample value - Admin=all=enabled

Caution: The preceding value generates verbose trace logging. Not setting any value prevents trace logging.

traceOutputFile

Allows you to specify the full path name of the output file to be used for logging trace output. Leave this property blank if tracing is not required.

Agile Service Manager user must have permission to create the output file.

ffdcLogDirectory

Enables FFDC logs of the WebSphere client code called by the WebSphere sensor for troubleshooting purposes. FFDC logs capture the failure path through the WebSphere client code in a subdirectory named ffdc in the directory specified in this property.

Not setting a value ensures that FFDC is not enabled. The directory must exist and the Agile Service Manager user must have write access.