Domain separation and Service Mapping

  • Release version: Washingtondc
  • Updated February 1, 2024
  • 2 minutes to read
    • Summarize
    Summarized using AI
    This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.

    Summary of Domain Separation and Service Mapping

    Domain separation in Service Mapping allows for the logical grouping of data, processes, and administrative tasks into domains, enhancing control over user access and visibility. This capability is essential for service providers managing multiple tenants, ensuring that data is appropriately segregated for application service use cases.

    Show full answer Show less

    Key Features

    • Data Control: Ensures that all data is directed to the correct domain, which is crucial for effective service management.
    • Leaf Domains: Actions in Service Mapping are performed within relevant leaf domains, which are the lowest child domains without further subdivisions.
    • Automated Service Suggestions: Supports domain separation; connections can only be created between items within the same domain.
    • Service Definitions: When transferring services between instances, they are assigned to the user's domain.

    Key Outcomes

    By implementing domain separation, customers can expect improved data integrity and streamlined processes across multiple tenants. Users will only interact with data pertinent to their domain, promoting a secure and organized environment for service mapping operations. It is recommended to verify domain content after installing Service Mapping Plus to ensure proper configuration.

    Domain separation is supported in Service Mapping. Domain separation enables you to separate data, processes, and administrative tasks into logical groupings called domains. You can control several aspects of this separation, including which users can see and access data.

    Support level: Basic

    • Business logic: Ensure that data goes into the proper domain for the application’s service provider use cases.
    • The application supports domain separation at run time. The domain separation includes separation from the user interface, cache keys, reporting, rollups, and aggregations.
    • The owner of the instance must set up the application to function across multiple tenants.

    Sample use case: When a service provider (SP) uses chat to respond to a tenant-customer’s message, the customer must be able to see the SP's response.

    For more information on support levels, see Application support for domain separation.

    How domain separation works in Service Mapping

    In domain-separated environments, switch into relevant leaf domains to access actions related to mapping performed by Service Mapping. A leaf domain is a child domain of the lowest level, meaning it does not have any child domains itself.

    Domain separation is handled in a slightly different way than simply configuring separate domains. Notice that you must select or specify the relevant leaf domain to perform the following mapping actions in domain-separated environments:
    • When creating an application service, the application service is assigned to the user's domain.
    • When manually adding a CI to an application service, you can choose only CIs that belong to the service domain.
    • When manually adding connections to CIs to an application service, users must belong to the same domain as the application service.
    • When transferring service definitions between instances, imported application services and service groups are assigned to the user's domain.

    Domain separation and Automated Service Suggestions

    Automated Service Suggestions supports domain separation. This means that:
    • The source and target process must reside in the same domain to create a connection.
    • The user can view only the data in the current domain.
    Note:
    After installing Service Mapping Plus with domain separation support, verify that all content is in the appropriate domain. For a detailed explanation of the required steps, see the Service mapping plus for domain separated instance [KB1303398] article in the Now Support Knowledge Base.

    Automated Service Suggestions supports domain separation starting with version 1.9.0. No support is currently offered for on-premise instances. Reach out to product management for further information.

    For more context, refer to Discovery patterns used by ITOM Visibility topic and MID Server configuration for Service Mapping. The following topics provide operational information on how to use Service Mapping in deployments with domain separation: