Application Layer Services Tier

Global Service Manager (GSM)—Tracks system configuration information and monitors registered services in the system. A system can have several GSMs. A GSM can be replicated so that all GSMs have the same comprehensive information about the services registered in the system.

Local Service Manager (LSM)—Created for every instance of a Reporting and Analysis service, including GSM. When system servers start, they register their services and configuration information with GSM, which supplies and maintains references to all other registered services.

Service Broker—Supports GSM and LSM by routing client requests and managing load balancing for services. A system can have multiple Service Brokers.

Job Service—Executes scripts that create reports, which can be prompted by users with permissions or by Event Service. Report output is returned to initiating users or published to the repository. Job Services can be created and configured for every executable.

Event Service—Manages subscriptions to system resources. Tracks user subscriptions, job parameters, events and exceptions, and prompts Job Service to execute scheduled jobs. Event Service is configured to distribute content through e-mail and FTP sites, and to notify users with subscriptions about changing resources. Event Service can be replicated allowing systems to have more than one.

Repository Service—Stores Oracle system data in supported relational database tables, known collectively as the repository. Repository Service is replicable. If replicated, it must be co-located with Publisher Service.

Usage Service—Records the number and nature of processes addressed by entire system. It can track execution of generic files in repository, Production Reporting jobs, database log ins, and modifications of events. Administrators can review usage statistics such as the number of log ins, what the most used files are, what the most selected MIME types are, and what happens to system output. Systems can have multiple Usage Services.

Logging Service—Centralized service for recording system messages to log files. A system can have only one Logging Service.

Session Manager Service—Monitors and maintains the number of simultaneous system users. Monitors all current sessions and terminates sessions that are idle for more than a specified time period. While Session Manager is replicable, each instance independently manages a set of sessions.

Publisher Service—Handles repository communication for other Reporting and Analysis services and some Web application requests; forwards repository requests to Repository Service and passes replies back to initiating services. Publisher Service is replicable. If replicated, it must be co-located with Repository Service.

Authentication Service—Checks user credentials at log in time and determines whether they can connect; determines group memberships, which, along with roles, affects what content and other system artifacts (resources) users can view and modify. Authentication Service is replicable and does not need to be co-located with other services.

Authorization Service—Provides security at the level of resources and actions; manages roles and their associations with operations, users, groups, and other roles. A system must have at least one Authorization Service.

Analytic Bridge Service (also known as Extended Access for Hyperion Interactive Reporting)—Enables users to jointly analyze multidimensional and relational sources in one document. It retrieves flattened OLAP results from Web Analysis documents, Production Reporting job output, or Financial Reporting batch reports in the Reporting and Analysis repository and imports data into Interactive Reporting (BQY) documents as Results sections.

Oracle's Hyperion® Impact Management Services—Reporting and Analysis Framework services that harvest, update, and publish new Interactive Reporting content from old Interactive Reporting repository resources. These services must be used in conjunction with Interactive Reporting services. These services perform automatic load balancing and fault tolerance when multiple instances are running:

Search Services—Reporting and Analysis Framework services that enable users to search for and retrieve documents, reports, and dashboards from any repository in EPM Workspace.

Interactive Reporting Log Service—Acts as the helper service to all instances of Interactive Reporting Services. Each instance of Interactive Reporting Services posts the log messages to Interactive Reporting Log Services. Interactive Reporting Log Service collects these messages and forwards them to the Logging Service in the Reporting and Analysis Framework Services tier with appropriates loggers created for each instance of Interactive Reporting Services.

Interactive Reporting Intelligence Service—Opens Interactive Reporting documents and delivers interactive HTML content. When actions involving Interactive Reporting documents are requested, this service fulfills the requests by opening and query processing the documents and delivering HTML for display.

Interactive Reporting Job Service—Similar to Interactive Reporting Intelligence Service, which handles only the requests for Interactive Reporting jobs. When a job is scheduled to run, this service receives the job request with job scripts. Then, the Interactive Reporting document associated with the job is opened and the scripts are executed. Finally, the job results are stored in the target directory.

Interactive Reporting Data Access Service—Provides access to relational and multidimensional databases, and carries out database queries for the Interactive Reporting Intelligence Service and Interactive Reporting jobs. Each Interactive Reporting Data Access Service supports connectivity to multiple data sources, using the connection information in one or moreInteractive Reporting database connection files, so that one Interactive Reporting Data Access Service can process a document whose sections require multiple data sources. Interactive Reporting Data Access Service maintains a connection pool for database connections.

Oracle Financial Reporting Service—Generates and formats dynamic report or book results, including specified calculations. Oracle Financial Reporting Services can handle numerous simultaneous requests for report execution from multiple clients because each request is run on its own execution thread. Oracle Financial Reporting Services caches data source connections, so multiple requests by the same user do not require a reconnection. Financial Reporting servers are replicable—the number necessary depends on the number of concurrent users who want to simultaneously execute reports through the clients. Multiple Financial Reporting servers can be configured to report against one repository.

Oracle Financial Reporting Communication Service—Provides a Java RMI Registry to which other Financial Reporting services are bound.

Oracle Financial Reporting Print Service—Enables Financial Reporting content to be compiled as PDF output. Runs only on supported Windows platforms, but is replicable to provide scalability for PDF generation.

Oracle Financial Reporting Scheduler Service—Responds to Financial Reporting scheduled batch requests. At the specified time, Oracle Financial Reporting Scheduler Service prompts the other Financial Reporting services to fulfill the request.