45 views

Service Mapping incorrectly identifies a service due to run order of the patterns

Issue


Service Mapping identifies a service incorrectly because the service matches the identification settings for two different service definitions. 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.

Cause


The Run order field of a Pattern is not normally set. However, “before” or “after” should be used if there is any similarity or dependency between two patterns. In that case, you need to set the run order to either before or after.

Resolution


  1. Select the order in which this pattern always runs.

    • Before
    • After
  2. Select the other applicable pattern.

    This field is relevant only if a particular pattern might be confused with another pattern.

Article Information

Last Updated:2018-01-25 08:27:15
Published:2017-04-30