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

Troubleshoot pattern-related mapping errors

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

Troubleshoot pattern-related mapping errors

You can troubleshoot mapping errors caused by patterns.

Before you begin

Verify that the mapping error is caused by an inaccurate pattern by checking the discovery message. If the message says "Failed to recognize application", the error is pattern-related.

You need to be familiar with the Pattern Designer module of Service Mapping.

Role required: admin and sm_admin

About this task

If there are configuration items (CIs) that Service Mapping could not map correctly, they appear on your business service map with warning icons The warning icon. Typically, mapping errors happen when Service Mapping fails to connect to a CI or fails to recognize it due to an inaccurate pattern.

You can identify problematic steps in your pattern and fix them without reviewing all steps and operations contained in the pattern. It allows you to troubleshoot pattern-related errors quickly and effectively.

The following video provides an alternative way of troubleshooting pattern-related errors:


  1. Navigate to Service Mapping > Services > Business Services.
  2. Click View map next to the business service that you want to view.
  3. Ensure that the map opens in Edit mode displaying discovery messages and errors.

    Discovery messages appear below the map
  4. Right-click the CI with the warning icon (The warning icon) and select Show discovery log.
    The Discovery Log window opens showing mapping patterns and their details.
  5. Expand the failed pattern which appears above the result marked red.

    A failed pattern appears above the result marked in red.
  6. Expand the failed section and click the failed step.

    A pattern section inside the pattern in the Discovery Log window.

  7. Click Debug.
    The Pattern Designer window opens showing the pattern with its steps in the left pane.
  8. Click the first step and wait for Pattern Designer to run it. Repeat this action for other steps following the order until you reach the faulty step that causes the error.

    In the example below the port number is 8081 instead of 8080 which causes the problem.

    The debug session fails when Pattern Designer tries to run a faulty step.
  9. Click OK.
  10. Fix the pattern attribute that causes the problem.
  11. Click Test.
  12. Verify that Pattern Designer returns a success message.
    In this example, the port number was fixed from 8081 to 8080 which allowed the pattern to run without an error.

    Pattern Designer completes the debug session and displays the success message.
  13. Click Save.
  14. Click Activate.
  15. Return to the business service map which contained the mapping error.
  16. Right-click the CI for which the pattern was fixed and select Resume discovery.
  17. Verify that the CI is discovered and mapped correctly.