Thank you for your feedback.
Form temporarily unavailable. Please try again or contact to submit your comments.

Match a condition

Log in to subscribe to topics and get notified when content changes.

Match a condition

As part of creating or modifying a discovery pattern, you can use the Match operation to specify conditions that the discovery process must meet to continue. If these conditions are not met, the discovery process stops.

Before you begin

Navigate to the relevant pattern step:

  1. On the pattern form, select the relevant identification section for Discovery.

    Alternatively, select the relevant identification or connection section for Service Mapping.

  2. Select the relevant pattern step or click Add a step above button to add a step.

Basic knowledge of programming is desirable.

Role required: pd_admin

About this task

While the discovery process always stops if the specified conditions are not met, you can control if the system regards this result as discovery error or not. In some cases you may run a pattern containing the match operation and expect the result not to match conditions. For example, in cloud environments different data centers may have different sets of devices and applications. You run a pattern for a certain application knowing that you do not find it on all data centers.

If you define that the lack of match is not a discovery error, the discovery log shows the message instead of the discovery error. Customize the message to provide useful information about why this result is expected.


  1. Select Match from the Operation list.
  2. In the first condition field, enter the required value.
    You can use an actual string or a variable. You can also use values from temporary tabular variables: from a specific field or a specific column in a table sequentially, starting from the first row. For more information, see Enter values and variables in patterns.

    Defining conditions
  3. Select an operator from the list.
  4. If necessary, enter the required value in the second condition field.
  5. To add more conditions, click the plus icon and define the criteria.
  6. If you create multiple conditions, define if this pattern must meet all or any of them: From the Meet list, select All or Any.
  7. To consider the lack of match as not a discovery error:
    1. Select Expected from the Termination type field.
    2. Enter the text for the discovery message to provide useful information about the expected result.
      You can use variables in the discovery message. For example, you can enter the following text:

      The discovery was stopped due to the following error: $error.

  8. If in Debug mode, test the step by clicking Test and checking that the operation brings the result you expected.


This operation is used in This item
Hierarchy Applications > Business Integration Software
CI Type IBM WMB HTTP Listener
Pattern WMB HTTP Listener On Unix Pattern
Section Identification for HTTP
Step number and Name 1. Check process name to match http lstnr

During discovery of an IBM WMB HTTP Listener, use the Match operation to check the process name.

Defining the Match operation

What to do next