When using the WebSphere Application Server – Configure plug-in, you can run the WebSphere Configuration Discovery step against a cell, node, server, or cluster. By default, the step discovers configuration data for all child objects of the parent object that you specify. For example, if you run the WebSphere Configuration Discovery step against a node, configuration data for all of the servers that are contained by the node is also discovered. If you run the step against a cell, the step discovers all nodes, servers, and clusters that belong to the cell.

Starting with version 33 of the plug-in, you can further limit the scope of WebSphere configuration discovery. If you limit the scope of WebSphere configuration discovery, the configuration data returned by the step is more granular, and the step might run faster.

To limit the discovery scope, complete the following steps:

1. In the process editor in IBM UrbanCode Deploy, edit the WebSphere Configuration Discovery step.
2. Select Show Hidden Properties.
3. For Limit Discovery Scope, select one of the following values:
   

   None

   Discovery scope is not limited. For example, when running discovery on a node, the node configuration data and configuration data for all servers that belong to the node is returned. This is the default value of the Limit Discovery Scope field.

   Cell

   Limits discovery to the cell scope. Configuration data for the cell is returned. Configuration data for nodes, servers, and clusters is not returned.

   Cell and Clusters

   Limits discovery to the cell scope, but also includes all clusters that belong to the cell. Configuration data for the cell and all of the clusters in the cell is returned. Configuration data for nodes and servers is not returned.

   Node

   Limits discovery to the node scope. Configuration data for the node is returned. Configuration data for the cell, servers, and clusters is not returned.