Learn about high-level tasks users having different roles perform in Service Mapping.

In Service Mapping, users collaborate to map, review, and monitor organization application services.
Note: For a complete list of Service Mapping roles, see Components installed with Service Mapping.
A typical Service Mapping workflow has the following stages:
  1. The administrator performs basic obligatory configurations to set up Service Mapping.
  2. The administrator maps organization application services in bulk. In addition, the administrator may map some application services individually.
  3. The administrator fixes application service errors in bulk.
  4. The administrator reviews the results of the initial mapping and fixes errors in individual application services.
  5. The administrator sends fixed application services to the application service owner for review.
  6. The application service owner checks that the application service maps are complete and all major components comprising it are correctly represented. If necessary, the owner leaves comments, referred to as reject messages, on application service maps for the Service Mapping administrator to implement. See Review application service maps.
  7. The administrator fine-tunes application service maps with feedback from the application service owner, and then resends them to the owner for review.
  8. If the revised application service maps are satisfactory, the application service owner approves them. If not, the owner requests further fixes, which the administrator must address. See Review application service maps.
  9. The administrator completes defining the application services by configuring access to them, as well as some advanced attributes like criticality.
  10. After application service definition is complete, the Service Mapping user can view application service maps.
Figure 1. Service Mapping flow

Service Mapping flow

In addition to these tasks, there may be a need to customize patterns that Service Mapping uses to discover devices and applications forming application services. Users must have the pd_admin role to customize patterns. In the base system, the sm_admin role contains the pd_role. Customizing patterns requires basic knowledge of programming.