Workspace Component Characteristics Oracle EPM Workspace Component Architecture

Configuring High Availability for Oracle Business Intelligence and EPM 15-27 ----- PROVIDER_SERVICES_WEB_APP 2 | ----- PROVIDER_SERVICES_WEB_APP 2 server2:port_y The LOGICAL_WEB_APP component information specifies the Provider Services cluster URL, which is unique.

15.1.6.1.2 Cluster-Wide Configuration Changes Provider Services reads the

essbase.properties file only during startup. If the Provider Services administrator changes this file, the administrator must restart the Provider Services cluster so that all Provider Services instances in the cluster are synchronized with configuration settings.

15.1.6.1.3 OPMN Essbase Cluster Support To support Essbase clusters, clients

communicate with Provider Services to fetch the active Essbase node in the cluster. API clients CAPIJAPI must specify an Provider Services URL which contains the OPMN Essbase cluster name to obtain the active Essbase host instance details. Provider Services then retrieves the active Essbase node details from the Hyperion Registry. The remainder of this section describes the behavior for Provider Services and CJAPI client use cases.

15.1.6.1.4 Essbase Database Clustering by Provider Services Provider Services supports

high availability of Essbase databases with active-active clustering. Clustering Essbase cubes databases enables load balancing and failover support. Provider Services manages a series of active, duplicate databases that respond to user requests. Users connect to the database by specifying an Essbase cluster; the database that is accessed must be transparent to users. Provider Services facilitates the routing of connections between databases in a cluster, based on availability and precedence rules using the round-robin technique. The Essbase cluster supports read-only operations on the Essbase database. Write-back operations such as data load and outline editing are not supported.

15.1.6.2 Protection from Failures and Expected Behaviors

Provider Services supports sticky sessions: After a user session is established with a Provider Services instance, the same Provider Services instance handles all subsequent requests from the client until the user disconnects. When a Provider Services instance fails indicated by an invalid session error, the user must disconnect the existing invalid session and log on again. The failover to the new Provider Services instance is transparent, so that the user can connect to the same APS URL the dispatcher’s URL that was used earlier. A dispatcher could be, for example, Oracle HTTP Server, which acts as a gateway, delivering requests to the Provider Services instances that are part of the cluster.

15.1.7 Oracle EPM Workspace Component Architecture

Oracle Enterprise Performance Management EPM Workspace, Fusion Edition Workspace is the Web user interface that is used to access all Oracle Hyperion and non-Oracle Hyperion content. Oracle Hyperion content includes Reporting and Analysis Framework and Oracles Hyperion financial applications.

15.1.7.1 Workspace Component Characteristics

Figure 15–5 shows the Workspace single instance architecture. 15-28 Oracle Fusion Middleware High Availability Guide Figure 15–5 Workspace Single Instance Architecture This figure shows the Workspace single instance architecture. EPM Workspace consists of a single J2EE Web application, which is typically fronted by an HTTP proxy such as Oracle HTTP Server. The HTTP proxy serves static content and proxies other products integrated into EPM Workspace. Content aggregation typically occurs on the client-side. EPM Workspace does not aggregate content within its own process; that is, EPM Workspace does not function as a portal.

15.1.7.1.1 State Information EPM Workspace sessions are regular J2EE sessions that are

held in memory only. EPM Workspace is stateful in its session use and the sessions are not serializable to any DB.

15.1.7.1.2 Runtime Processes EPM Workspace has a normal J2EE runtime. Users

typically connect to EPM Workspace, log on to the system, and access another product, such as Oracle Hyperion Financial Reporting. There are no background threads or other forms of server-side services or jobs. All processing is handled in the context of the HTTP request. EPM Workspace uses a set of servlets, implemented directly or as JSPs, and servlet filters. There are no EJBs or JMS usage. Database access is through a standard JNDI lookup of a JDBC data source. Configuring High Availability for Oracle Business Intelligence and EPM 15-29

15.1.7.1.3 Process Lifecycle EPM Workspace is managed as a standard J2EE Web

application deployed to the WebLogic application server. It is managed, started, and terminated by its application server.

15.1.7.1.4 Request Flow Requests are made to EPM Workspace by means of the HTTP

proxy, which is the only means for end-users to access EPM Workspace. EPM Workspace does not make requests against other Web applications or databases other than its repository database and the EPM Registry database.

15.1.7.1.5 External Dependencies EPM Workspace relies upon its repository database

and the Hyperion Registry; both are in the same schema. Most EPM products rely on EPM Workspace to provide initial authentication and a containing user interface.

15.1.7.1.6 Configuration Artifacts The entire EPM Workspace configuration is stored in

the Hyperion Registry. Individual user preferences are stored in the EPM Workspace repository.

15.1.7.1.7 Deployment Artifacts EPM Workspace has no deployment artifacts other than

the JDBC data source.

15.1.7.1.8 Log Files Go to the logsworkspace subdirectory in the managed server

domain home to view workspace.log and Framework.log.

15.1.8 Oracle EPM Workspace High Availability Concepts