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

Domain separation in Application Portfolio Management

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

Domain separation in Application Portfolio Management

This is an overview of domain separation as it pertains to Application Portfolio Management. Domain separation enables you to separate data, processes, and administrative tasks into logical groupings called domains. You can then control several aspects of this separation, including which users can see and access data.


Support: Data only

Domain separation in this application is supported at the Data only level, meaning it supports the data security model of separating visibility of data from one domain to another. To learn more, see Application support for domain separation.

How domain separation works in Application Portfolio Management

While domain separation in APM is at the "Data only" level, there are a few factors to help you in your use of domain separation:
  • Data can be domain separated.
  • The domain column is present for base system application tables and APM tables.
  • Domains are created and domain-specific configuration is managed by instance owner.
  • Tenant domains can manage their own application data.

  • Application properties are tied to the domain.
  • Business logic and processes can be domain-separated by instance owner. Business rules and policies can be created in specific domains by tenants.
  • Business logic and processes can be administered by tenant domain.