Thank you for your feedback.
Form temporarily unavailable. Please try again or contact to submit your comments.
  • London
  • Kingston
  • Jakarta
  • Istanbul
  • Helsinki
  • Geneva
  • Store

Create an empty pattern

Create an empty pattern

Create a new pattern and define its basic attributes.

Before you begin

Role required: admin or sm_admin

Make sure that the application for which you want to create a new pattern, has a corresponding configuration item (CI) type.


  1. Navigate to Service Mapping > Administration > Discovery Patterns.
  2. Click New.
  3. Define the basic pattern attributes as described below:
    Field Description
    Name Enter the pattern name. This name must be unique to this pattern. It is recommended that you use self-explanatory names like Apache on Unix pattern.
    CI type Select the CI type which you want this pattern to discover. If the CI type you require is not in the list, create it as described in Create a CI type for Service Mapping.
    Pattern type Select Discovery.
  4. Click Manage Pattern.
    The Pattern Designer window opens.

    Pattern Designer window
  5. Define advanced attributes as follows:
    Field Description
    Description Enter a free text description to help identify the pattern later.
    Operating system Select the operating system that the selected CI runs:
    • All - if the CI runs more than one operating system.
    • Windows
    • Unix - Select this option for any of the following: Linux, Solaris, HP-UX, AIX
    • IBM Z/OS
    If the required operating system does not match any of the above, add it:
    1. Click the plus sign+.
    2. Select the Proprietary check box.
    3. Type the name of the operating system.
    Run order Select the order in which this pattern always runs:
    • Before
    • After

    Then select the other applicable pattern. In most cases this field is not relevant. It is only relevant if a particular pattern can be confused with another pattern.

    For example, Both IIS and MS Exchange applications have an HTTP entry point; however MS Exchange uses some of the components of IIS. Therefore, if the IIS pattern ran first, discovery might incorrectly identify MS Exchange as IIS. To prevent this, in the Run Order field in the MS Exchange pattern definition, select Before and IIS.

  6. Click Save.

What to do next

Define the identification section