DRM Architectures

Oracle Data Relationship Management (DRM) 11.1.2.2 allows DRM components to be distributed across multiple servers in several configurations to provide isolation and enhanced scalability.  The available architectures include:

• Default - Single Host
• Secondary Engine Hosts
• Secondary UI Web Servers
• Secondary API Adapter Hosts

The default architecture installs all DRM components on a single host; the distributed architectures disperse DRM components across multiple hosts to provide increased resource to individual DRM applications and processes.  This article with provide an overview of the available architectural options; future postings will drill down into the implementation details of the individual designs.

Default Single Host

A default single host installation implements all DRM components on a single server.
Minimum DRM Component Requirements

• DRM Application Server (1)
• DRM Management Console (1)
• DRM Web Server (Requires IIS Server) (1)

Optional DRM Components

• Oracle Hyperion EPM Foundations services must be available to implement DRM External Security
• API Adapter

All client UI connections to the DRM application pass through the host DRM Web Server.
If implemented all DRM API (Web Service) connections pass through the host API Adapter.

Secondary Engine Hosts

A DRM Secondary Engine Host installation implements an additional DRM Application Server component on a second host machine.   This architecture allows individual DRM applications to execute on distributed hosts under the control of a single DRM Management Service.

Minimum DRM Component Requirements

• DRM Application Server (2)
• DRM Management Console (1)
• DRM Web Server (Requires IIS Server) (1)

Optional DRM Components

• Oracle Hyperion EPM Foundations services must be available to implement DRM External Security
• API Adapter

Client UI connections pass through the Primary Host DRM Web Server and are routed to the Application Server where the requested DRM application is attached.
If implemented all DRM API (Web Service) connections pass through the host API Adapter.

Secondary UI Web Servers

A DRM Secondary UI Web Server Host installation implements an additional DRM Web Server component on a second host machine.   This architecture allows individual DRM applications to execute on distributed hosts under the control of a single DRM Management Service.
Minimum DRM Component Requirements

• DRM Application Server (2)
• DRM Management Console (1)
• DRM Web Server (Requires IIS Server) (2)

Optional DRM Components

• Oracle Hyperion EPM Foundations services must be available to implement DRM External Security
• API Adapter

Client UI connections pass through the Primary Host DRM Web Server and are routed to the Application Server where the requested DRM application is attached.
If implemented all DRM API (Web Service) connections pass through the host API Adapter.

Secondary API Adapter Hosts

 A DRM Secondary API Host Server implementation installs the DRM API Adapter component on a second host machine.   This architecture routes custom DRM API application web service clients through the Secondary API Adapter host instead of the Primary (or Secondary) DRM Application host.  The Secondary API Adapter host executes on distributed hosts under the control of a single DRM Management Service.
Minimum DRM Component Requirements

• DRM Application Server (2)
• DRM Management Console (1)
• DRM Web Server (Requires IIS Server) (1)
• Oracle Hyperion EPM Foundations services must be available to implement DRM External Security
• API Adapter (1)

Client API connections pass through the Secondary DRM API Adapter Host and are routed to the Primary Application Server where the requested DRM application is attached.