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

Create a pattern

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

Create a pattern

Create a pattern and define its basic attributes.

Before you begin

Role required: admin, discovery_admin, or sm_admin

Make sure that the application for which you want to create a pattern, has a corresponding configuration item (CI) type and a CI classification. If the CI type you require is not in the list, create it as described in Create a CI type for Service Mapping and Discovery.

If your ServiceNow instance uses domain separation and you have access to the global domain, select the domain to which the business service belongs from the domain picker (). It must be a domain without any child domains.

About this task

Patterns can be of infrastructure and application type. Infrastructure patterns are used only by Discovery for creating lists of devices. Application patterns serve both Service Mapping and Discovery that use the same application patterns for their purposes.


  1. Navigate to Pattern Designer > Discovery Patterns.
  2. Click New.
  3. Define the basic pattern attributes on the Basic tab:
    Field Description
    Name Enter the pattern name. This name must be unique to this pattern. Use self-explanatory names such as Apache on Unix pattern.
    Pattern type
    • Select Application for an application pattern. It can be used both for top-down discovery performed by Service Mapping and horizontal discovery performed by Discovery.
    • Select Infrastructure for an infrastructure pattern used for the horizontal host discovery performed by Discovery.
    CI type Select the CI type which you want this pattern to discover.
  4. Click Submit.
  5. Click the pattern you created in the list.
  6. Define advanced attributes:
    • For an infrastructure pattern, click Edit for Discovery.
    • For an application pattern used for horizontal discovery by Discovery, click Edit for Discovery.
    • For an application pattern used for top-down discovery by Service Mapping, click Edit for Mapping.
    Field Description
    Description Provide a description for this pattern.
    Operating system [Application patterns only] 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 operating systems: Linux, Solaris, HP-UX, AIX
    • IBM Z/OS
    If the required operating system does not match any options, add it.
    Run Order [Application patterns only] For an application pattern used by Service Mapping, 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 error, in the Run Order field in the MS Exchange pattern definition, select Before and IIS.

  7. Define a set of identification steps for every incoming connection of a configuration item (CI).
    1. Under Identification Section, click the plus icon to create a new identification set of steps.
    2. Configure the following parameters:
      Field Value
      Name Unique name for the identification section.
      Entry Point Types [Application patterns only]

      Select all relevant entry point types. Every CI has incoming connections that are referred to in Pattern Designer as entry points. You base your CI identification process on the CI entry points creating steps and defining step operations and variables for every entry point separately.

      For application patterns used by Discovery, enter either TCP or All.

      Find Process Strategy [Application patterns only] Select the appropriate strategy for finding the process that populates the Process variable in the Temporary Variables table.
      • LISTENING_PORT: The entry point is the listening port.
      • TARGET_PORT_AND_IP: The entry point port communicates with another server.
      • NONE: The process variable is not populated.

      Typically, the port type of the entry point determines the strategy.

      Order For an application pattern used by Service Mapping, select a number that determines the order in which Service Mapping uses identification sections. The section with the lowest order number is used first.
    3. Click Create New.
    4. Define pattern variables for this section. For more information, see Pattern variables.
    5. Define discovery steps as described in Define discovery steps.
    6. Click Save.
    7. Click the Back to pattern link in the upper-right.

      The Back to pattern link
  8. If necessary, create more identification sections.
  9. If necessary, change the order of your identification sections by using arrow buttons:
    Changing order of the identification sections.
  10. When creating an application pattern, make sure you define both modes: for Discovery and for Service Mapping.

What to do next