Oracle BI Publisher Component Characteristics

Configuring High Availability for Oracle Business Intelligence and EPM 15-75 Figure 15–11 Oracle BI Publisher Single Instance Architecture

15.2.1.1 Oracle BI Publisher Component Characteristics

Oracle BI Publisher is a Java EE application that uses a servlet based architecture. JMS is used for scheduled jobs execution; Fusion ESS integrates with BI Publisher by means of web services.

15.2.1.1.1 State Information During the execution of Oracle BI Publisher reports, the

session information is stored in memory. BI Publisher is not a stateless application due to the complexity of migrating report execution across servers.

15.2.1.1.2 Runtime Processes Oracle BI Publisher is a Java EE component deployed on

Oracle WebLogic Server. ■ Oracle BI Publisher artifact processing, which includes creating, deleting, and editing these artifacts: – Reports – Data models APPHOST1 Network WEBHOST1 OHS Firewall Firewall Firewall WLS_BIPI WebLogic Server Admin Server BI Publisher Repository BI Publisher Reports, Definitions, and Layouts BI Publisher Configuration Folder Data Sources Scheduled Jobs Information Oracle RAC Database 15-76 Oracle Fusion Middleware High Availability Guide – Layout templates – Scheduler jobs – Configuration ■ Execution of scheduler reports ■ Execution of online reports

15.2.1.1.3 Process Lifecycle Oracle BI Publisher depends entirely on the Oracle

infrastructure. Use the WebLogic Server Administration Console to deploy, start, stop, and monitor Oracle BI Publisher.

15.2.1.1.4 Request Flow JMS is used as a backbone to the Oracle BI Publisher batch

report processing system. JMS is used as a messaging board in a transactional fashion. Every report is divided into these stages of execution: 1. Data retrieval 2. Data formatting 3. Report delivery Each of these stages appears as a job request in the JMS queue. If a node goes down, the other nodes continue to service the queue. However, if a report job is in one of these stages of execution—data retrieval, data formatting, or report delivery—the job is marked as failed and you must resubmit it manually.

15.2.1.1.5 External Dependencies Oracle BI Publisher depends on:

■ Database repository: for scheduled jobs information. ■ Storage of Oracle BI Publisher artifacts: These artifacts include reports, definitions, and layouts. The storage is done in two different ways: – In Oracle Business Intelligence Enterprise Edition mode: Oracle BI Publisher uses Oracle BI Presentation Catalog via a short-lived connection over Web services. – In standalone mode: Oracle BI Publisher uses a shared file system such as SAN or NAS. ■ DBMS for report data: Oracle BI Publisher queries the DBMS to retrieve the report data that needs to be processed. ■ Web services: for data retrieval.

15.2.1.1.6 Configuration Artifacts Oracle BI Publisher is a standard Java EE application.

15.2.1.1.7 Deployment Artifacts Oracle BI Publisher does not have any special

deployment artifacts.

15.2.1.1.8 Log Files Oracle BI Publisher is a Java EE application deployed on Oracle

WebLogic Server. All log messages are logged in the server log file of the Oracle WebLogic Server that the application is deployed on. The default location of the server log is: WEBLOGIC_SERVER_HOME user_projectsdomainsdomainNameserversserverNamelogs serverName -diagnostic.log Configuring High Availability for Oracle Business Intelligence and EPM 15-77

15.2.2 Oracle BI Publisher High Availability Concepts