Bi Publisher Best Practices 2159564

1
Copyright 2013, Oracle and/or its affiliates. All rights reserved.
CON9330
Oracle BI Publisher Best
Practices: Be a Reporting
Super Star
Kevin McDermott
Senior Principal Technical Support Engineer
Nicholas Mann
Senior Consultant , Peleton Group
THE FOLLOWING IS INTENDED TO OUTLINE OUR GENERAL

PRODUCT DIRECTION. IT IS INTENDED FOR INFORMATION
PURPOSES ONLY, AND MAY NOT BE INCORPORATED INTO ANY
CONTRACT. IT IS NOT A COMMITMENT TO DELIVER ANY
MATERIAL, CODE, OR FUNCTIONALITY, AND SHOULD NOT BE
RELIED UPON IN MAKING PURCHASING DECISIONS. THE
DEVELOPMENT, RELEASE, AND TIMING OF ANY FEATURES OR
FUNCTIONALITY DESCRIBED FOR ORACLE'S PRODUCTS
REMAINS AT THE SOLE DISCRETION OF ORACLE.
Program Agenda
Oracle BI Publisher Enterprise Overview
Deployment & System Requirements
Report Design Best Practices
Data Modeling & Template Design Guidelines
BI Publisher & OBIEE Integration Best Practices

Q&A
Oracle Business Intelligence Publisher

Eliminates multiple-point solutions, Lowers TCO
Checks
Invoices
One Environment
Author
Generate
Deliver
Benefits
Destinations
Reports
Eliminate complexity
Simplify report
development & maintenance

Reduce costs
5
Labels
XML / EFT / EDI

Provides an end-to-end solution, from data to documents to delivery
Interactive
PDF
Email
HTML
XSL
Layout Template Types
Excel
Printer
PPT
Flash
Layout Editor
MS Word
MS Excel
Adobe
Flex
XSL
Layout Design Tools
Fax
RTF
CSV
XML
Repository
EDI
OBI EE Semantic Layer
EFT
e-Commerce

Enterprise class reporting application for all your document needs
Program Agenda

Q&A
Installation & System Requirements
Installation requirements
Oracle Fusion Middleware Installation Guide for Oracle Business
Intelligence 11g Release 1 (11.1.1)

JDK requirements
Refer to the certification matrix for supported JDK versions for specific
operating systems. There is one for 11.1.1.3-11.1.1.6 and one for 11.1.1.7.
http://www.oracle.com/technetwork/middleware/ias/downloads/fusion-
certification-100350.html
Sizing Guidelines
How Many servers?
Concurrent Use Case
Bursting Use Case
Users viewing reports online
Bursting reports
Scheduled Jobs running at the
Factors to consider
same time
Factors to consider
Time window
Number of users viewing Small,
% of Small, Medium, Large reports
Medium, Large, XLarge reports

Number of CPUs /server
10
Total Number of reports
Number of CPUs/Server
Sizing Guidelines
My Oracle Support Note 948841.1
11
Enterprise Deployment Options

Oracle BI Publisher
Single Instance Architecture

Oracle Fusion Middleware
High Availability Guide 11g
Release 1 (11.1.1)
High Availability for Oracle Business
Intelligence Publisher
12

Oracle BI Publisher 11g
High Availability Architecture
High Availability Guide 11g
Release 1 (11.1.1)
High Availability for Oracle Business
Intelligence Publisher
Oracle BI Publisher supports an active-active
high availability configuration. Each node acts
as an independent server that shares a common
repository and the scheduler database with the
other Oracle BI Publisher nodes.
13

Oracle BI 11g
High Availability Architecture

Oracle Fusion Middleware High
Availability Guide 11g Release 1
(11.1.1)
Configuring High Availability for Oracle
Business Intelligence and EPM
14
Oracle BI Publisher 11g Scheduler

Client
Web server
Client
Web server
Web server/JMS Provider

(Web Logic, Active MQ)
FAX Q.
Fax
Printer Q.
Printer
BI Publisher
BI Publisher
Job Q
Email Q.
Email
Report Q
FTP Q.
BIP System Topic
WebDav Q.
JMS Resources
File Q.
Repository
File system
BI Publisher Reports Repository
15
Scheduler database
Program Agenda

Q&A
16

Report Architecture
Separate data logic, layout & translation benefits
greater flexibility and reuse
fewer reports and better report maintenance
optimize data extraction and document generation process
Data Logic
Layout
Translation
17
BI Publisher
Report output
Data Generation
Data Sources
Data Source Types
File (XML)
SQL Query
MDX Query
LDAP Query (11g only)
Excel Spreadsheet (11g only)
Endeca Query (11g only)
CSV (11g only)
View Object (11g only)
HTTP (XML Feed)
Web Service
Oracle BI Analysis
Oracle BI Discoverer (10g only)
Data Template (10g only)

18
Data Generation
Connection Types
JDBC Vs JNDI (SQL Type)
Both types of connection use
the same JDBC driver

With JNDI you can take advantage
of connection pooling
Better performance
BI Publisher
Connection already established to the source

Best practice for reports with many parameters
with SQL type LOVs attached to them

Better RDBMS resource management
19
WebLogic
Server
Data Generation
Scalable Mode
Enable for large reports
Slower performance, but
prevents out-of-memory
errors
Use with scheduled
reports
20
Data Generation
Enabling Scalable Mode for Data Engine (10g)
Set scalable mode property to
on in Data Template
<properties>
<property name="scalable_mode" value="on" />
</properties
21
Data Model Design

Objectives
Optimize data extraction
Simplify layout design for report developers
Reduce document generation time
22
Data Model Design

Data Extraction
Leverage back-end system
resources (whenever possible)

Join data
Filter & group data
Perform expensive calculations &
Select
t."OFFICE_DSC" as "Office"
sum(f."REVENUE") as Sales Sum"
From
"BISAMPLE"."SAMP_REVENUE_F f
"BISAMPLE"."SAMP_OFFICES_D t
Where
t."OFFICE_KEY"=f."OFFICE_KEY"
group by
t."OFFICE_DSC"
data transformations
Sort data
23
20 Vs 20,000 records
Data Model Design

Data Extraction
Parameters & LOVs
Cache LOVS for better performance
For large LOVs, pass NULL to the
parameter when users select All &

modify WHERE clause in Data Set
query to use the NVL function.
For example:
Where
order_id=nvl(:p_ordid,
order_id)
24
Data Model Design

Data Extraction
Event triggers
Before Data Triggers
Generate dynamic SQL
Populate TEMP tables
Set user context
After Data Triggers

Insert rows to a target table
Send notifications
Clean or delete TEMP tables
25
Select EMPLOYEE_ID,
DEPARTMENT_ID,
FIRST_NAME,
LAST_NAME,
EMAIL,
PHONE_NUMBER,
HIRE_DATE,
JOB_ID,
SALARY
from employees
where &p_where_clause
Event Driven Jobs (11g Only)

Enable users to set up flexible, conditional execution of scheduled jobs.
Data Model Designer creates
Data Model with schedule trigger

Triggers can be created and
shared from a single data model
Users create scheduled jobs and
determine window of time to
check for condition
Reports execute when condition
is true or are skipped
26
VALUE: Users can schedule

reports to execute based on
an event or condition over a
window of time.
Data Model Design

Best Practices for Faster Document Generation
Structure data to match how data is
27
displayed in the report

Use short XML tag names they reduce
the size of XML data file
Use display names
to simplify template design
Create global & group-level aggregate functions for
best performance, create them in data model instead of
report layout
Pre-sort data (preferably at the source)
Note: Grouping data in data model automatically sorts data
by the grouping element
Bursting
It also requires that data in the XML is sorted (or grouped)
by the split-by key.
Template Design Guidelines

Objectives
Choose the right type of template
Follow BI Publisher (XPT) template design best practices
Do not overcomplicate RTF templates
28
Document Formatting and Layout

What Template Type should I use? (1 of 2)
29
BI Publisher
Template 11g
Web based Layout Editor no client installation required

Best for Management Report WYSIWIG experience
Support Interactive Output
Wide range of output (PDF, HTML, Excel, PPT, RTF, MHTML)
RTF
Templates
Easy to create w/ BI Publisher Template Builder Add-in to Word

Greatest flexibility and functionality for highly formatted reports
RTF marked up with XSL code or BI Publisher simplified XSL
Wide range of output (PDF, HTML, Excel, PPT, RTF, MHTML)
PDF
Forms
PDF forms with XML elements mapped to form fields.

Great to use with government forms
PDF output only
Create in Acrobat Professional

What Template Type should I use? (2 of 2)
30
Excel Templates
Excel w/ data mapped to named cells & Excel and XSL formatting
Great for formatted, true Excel output and burst over sheets
Excel XLS output only
e-Text Templates
Text output only for electronic communication

Great for character delimited or fixed position docs (EFT & EDI)
RTF with table of statements to place fields and separators
Flash Templates
SWF files with BI Publisher data for sophisticated interactivity

Create in Adobe Flex Builder
XSL Style Sheets
Allows for third party tools and legacy solutions
Excel Analyzer
Templates
Not recommended (deprecated)

Excel output only. Can refresh data w/ parameters.
BI Publisher Template Best Practices

Design Consideration
Use Layout Grids to position
components similar to tables in RTF

Templates
Layout Grids can be nested
Layout Grid Cell can be joined

The minimum height of rows
can be fixed
DO NOT put LARGE tables or pivot
tables into Layout Grids (Performance!)
31
BI Publisher Template Best Practices

Design Consideration
The Interactive Viewer is one of BI Publishers most
promising new features

Interactivity works best for flat tables or simple
nested master-detail data sets

Unrelated queries or groups can not interact
Disable interactions for unrelated queries in the
Configure Events Dialog
32
BAD: Country on two branches
GOOD: Country in common parent
Data
G1
Country
Revenue
G2
Country
Cost
Data
G1
Country
G2
Revenue
G3
Cost
RTF Template Best Practices

Use Word Tables
Use tables to control precisely where field data will be placed in the
report
33

Use Form Fields
Keep the template clean
Supported by the Template Builder
Field Browser
Can be colored or hidden to help
understand the structure
Caveat: Word header & footer dont
allow form fields
34

Dont overcomplicate your template
Keep it easy to understand, debug and maintain
In general better to have different business documents in
different templates
Try to limit the logic in templates to simple if or loop statements
Use sub templates to simplify documents if necessary
Many calculations are better performed in the data model
35

Performance Considerations: XPATH Concepts
BI Publisher uses XPATH to access data elements
DEPARTMENT_NAME is inserted in the template as
<?DEPARTMENT_NAME?>
<?DEPARTMENT_NAME?> is translated to the XPATH
.//DEPARTMENT_NAME
.//DEPARTMENT_NAME searches for
DEPARTMENT_NAME in the complete sub-tree starting

from current context
36

Performance Considerations: XPATH Tuning
Use the full relative path for large datasets
Instead of <?for-each: DEPT?>
use <?for-each:/DEPT_SALS/DEPT?>
Instead of <?DEPARTMENT_NAME?>
use <?./DEPARTMENT_NAME?>
For large documents that dont fit into memory
the search requires disk access

For small documents the search time is
negligible
37

Performance Considerations: XPATH Tuning & Tables
XPATH Tuning
Start with the outer loops and outer most data access
Reducing full tree searches will provide bigger improvements than optimizing
access in a small subset of the data

Fixing the XPATH in a single for-each loop may be all the performance tuning
you need to do
Tables
LARGE tables that span hundreds of pages consume considerable server
resources. If possible group the data and create a table inside each grouping.
Do not nest LARGE tables into tables.
38

Performance Considerations: Grouping
Better to Sort data in the data model
Group By <?for-each-group?>
will force the XSL engine to sort data

Checking Data already sorted option in the Table Wizard will not re-sort
data (good thing)
39
Template Best Practices

Summary
Dont overcomplicate your templates
Use tables (layout grids) to place data fields precisely
Use form fields and word styles for clarity
Use sub templates for re-use and encapsulate complex code
Optimize your data structure for interactivity if necessary
Performance optimization
Optimize the XPATH
Focus optimization on outer loops
Sort in the data base and use group-adjacent in the template
40
Program Agenda

Q&A
41
BI Publisher & OBI EE Integration

Best Practices
Nicho Mann
949.290.8553 | p
nmann@pelotongroup.com
Peloton Overview
43
Agenda
BI Publisher and OBI EE Comparison
BI Publisher and OBI EE Integration Best Practices
Customer Success Story
44
BI Publisher and Oracle Business Intelligence

Comparison
45
BI Publisher (BIP)
Oracle Business Intelligence (OBI)
Pixel-Perfect Reporting
Interactive Dashboards and Analyses
Reporting Focused
Analytics Focused
Layer of abstraction via the Data Model
Layer of abstraction via the Repository (RPD)
Sophisticated delivery capabilities
Actionable Intelligence
User-friendly interface
Ad-hoc capabilities
BI Publisher and Oracle Business Intelligence

Comparison
BI Publisher (BIP)
Oracle Business Intelligence (OBI)
Pixel-Perfect Reporting
Interactive Dashboards and Analyses
Reporting Focused
Analytics Focused
Layer of abstraction via the Data Model
Layer of abstraction via the Repository (RPD)
Sophisticated delivery capabilities
Actionable Intelligence
User-friendly interface
Ad-hoc capabilities
BI Publisher + OBIEE =
Integrated, Scalable Reporting & Analytics Enterprise
Application
46
BI Publisher Architecture
Sources
DW
OLAP
Cube
Flat File
47
BIP Data
Model
BI Publisher
Oracle Business Intelligence Architecture

Sources
DW
OLAP
Cube
OBI RPD
Flat File
48
OBI EE
Dashboards
BI Publisher & OBIEE Integration Architecture

Sources
DW
BIP Data
Model
OLAP
Cube
OBI EE
Dashboards
Flat File
BI Server RPD
49
BI Publisher
Reports
BI Publisher & OBI EE Integration Benefits

Flexibility
OBI RPD
OBI Reports
BIP Reports
Multiple Data Sources
Create Calculations
Apply Functions
Change Column Names
Use/Create Aggregates
Custom Formulas
Integration of BI Publisher & OBI EE allows for
flexible solutions
Solution is scalable as a result of flexibility in
accepting multiple data sources
50
BIP Data Model
BI Publisher & OBI EE Integration Interactive

Dashboards & Pixel-Perfect Reports
OBI Dashboards
Interactive Analyses
Action Links & Guided
Navigation
Drillable Reports
Extensive Visualizations
BI Publisher Reports
Pixel-Perfect Reports
User-Friendly Interface
Leverage Existing OBI Reports
51
Agenda
52

Keep It Simple
Source Relational and OLAP data sources into OBI
MDX and SQL will be dynamically generated by OBI
Utilize a single OBI model instead of several data models
53

Keep It Simple
Push Logic As Far Back As Possible
Data Source > RPD > Data Model > BIP Report
Faster Calculations
Less Maintenance
Increased Query Performance
Keep Datasets Under Control

Be mindful of the amount of data being requested
Use filters to limit data sets and increase performance
54

Keep It Simple
Using an existing OBI model means:

Less coding
Decrease turnaround time of requests
Easier for developers to leverage
Less training for end users
Higher adoption by business users
55

Maintain Consistency
Utilize OBI Subject Areas when possible

Cuts down on the number of data models
Maintains logic in fewer locations
Keep the number of BIP data models to a minimum

Create data models that can be used across a range of
reports
56

Leverage Existing OBI EE Implementation
Utilize Existing Applications

Cut down costs
Higher adoption
Increased scalability
Seamless Integration
57
Agenda
58
BI Publisher Success Story

Overview
Infinity Pharmaceuticals In late stage trials beginning to prepare for
the transition to commercial

Purchased Oracle BI Foundation Suite to improve reporting and
analytical capabilities
Partnered with Peloton to implement a scalable, integrated solution to
meet the needs of the growing organization
59

Challenges
Difficult to access key information

No consistent tool for financial reporting
Limited transparency to Financial Investment Plans (FIPs)
for department heads

Challenging to quickly and easily access variance reports
for functional heads
60

Solution - Overview
Established New Data
Warehouse
Built Essbase Studio Cube
Model
Implemented Sophisticated
Reporting Solution:
OBI EE
Hyperion Smart View
BI Publisher
61

Solution BI Publisher
Integrated BI Publisher with
OBI EE
Created POC leveraged existing
OBI EE reports
Developed BI Publisher Data
Models using logical SQL
Quickly generated pixel-perfect
financial reports
62

Solution BI Publisher
Leveraged OBI EE dashboards
with BI Publisher reports

Guided navigation and action
links for sophisticated analysis

BI Publisher reports for exporting
purposes
Cut down on development,
system integration, & adoption
time
63
Solution Options
What if I only have Oracle Business Intelligence?

Easily integrate BI Publisher
Get more from your development dollars by leveraging your OBI EE implementation
What if I only have BI Publisher?
Consider the roadmap of your organization from an analytics perspective
OBI EE offers much more structure for data sources and integrates well with BI Publisher
What if I have neither?
OBI EE is a great starting platform because of its flexibility
Scalability is critical to any organization OBI EE is a highly scalable, enterprise application
64
A Charitable Donation to Support Childrens

Health
65
Q&A
&
66
Stay Connected with BI Publisher
http://www.oracle.com/technetwork/middleware/bi-publisher/overview/index.html
67
Graphic Section Divider
68
Appendix
69
Resources
Certification matrix (11.1.1.x)
System Requirements and Supported Platforms for Oracle Business Intelligence Suite Enterprise Edition 11gR1 (11.1.1.3.0-11.1.1.6.0)
http://www.oracle.com/technetwork/middleware/bi-enterprise-edition/bi-11gr1certmatrix-166168.html
System Requirements and Supported Platforms for Oracle Business Intelligence Suite Enterprise Edition 11gR1 (11.1.1.7.0)
http://www.oracle.com/technetwork/middleware/bi/bi-11gr1certmatrix-ps6-1928219.xls
High availability white paper

http://www.oracle.com/technetwork/middleware/bi-publisher/bip-cluster-deployment-366859.pdf
Sizing Spreadsheet for BI Publisher Enterprise 10g and 11g
My Oracle Support Note - 948841.1

Sub-templates white paper
http://www.oracle.com/technetwork/middleware/bi-publisher/overview/bip-subtemplate-1-132933.pdf
QUARTZ Scheduling - http://www.quartz-scheduler.org/

CPU Ratings - http://www.spec.org/cpu2006/results/cpu2006.html#SPECint_rate
70
Install Requirements
Oracle Business Intelligence 11g

Installation Guide for Oracle Business
Intelligence
11g Release 1 (11.1.1)
Part Number E10539-02
System Requirements
Disk Space: 20GB or more
Available Memory (RAM): 4GB or more
Temp Space: 950MB or more
Swap Space: 3GB or more
CPU: dual-core Pentium, 1.5GHz or greater
Database Requirements
Disk space requirements for the database containing the Oracle Business
Intelligence Scheduler database tables.
500MB on Oracle and Microsoft SQL Server databases for standalone and Business
Intelligence applications and deployments.
500MB on IBM DB2 databases for standalone deployments.
71

Recommended Configuration
JVM settings & JDK version
64 bit JVM/JDK (on a 64 bit OS)
JDK version 1.6 (update 2) or higher
Memory (RAM for the JVM)

8 GB on 64 bit JVM is recommended for large, high volume use
2 GB on 32 bit OS suitable for small to mid volume deployments
(2gb limitation for JDK on win OS)

Storage
Repository: Varies. 30 GB Hard disk space (must be shared for cluster)
Temp Space: 20 GB (for document processing) not shared
72

BI Publisher (10g)
High availability
Improve availability of the
system
Load balancing
Increase throughput
For more details on clustering BI
Publisher standalone, please refer to
our White Paper on High Availability.
The link is available in the Appendix.
73

BI Publisher Scheduler Configuration (v10g only)
Enable clustering
Client
BIP
servers
cluster
Scheduler
database
74
Server Configuration Options

Administration > Server Configuration
Scalable threshold (in bytes)
Cache expiration (in min)
Cache size limit (# of datasets)
Maximum cached reports

Database Fetch Size
75
Default values
Server Configuration Options

Administration > Runtime Configuration > Properties
Bursting (10g only)
Enable multithreading Default: False*
Thread count Default: 2*
FO processing
76
Use BI Publishers XSLT processor

Default: True
Enable scalable feature of XSLT processor

Default: False*
Pages cached during processing

Default: 50
Enable multithreading Default: False*
FO Parsing Buffer Size Default: 1000000*
Enable XSLT runtime optimization

Default: True
Report-level Properties
Edit Report > Properties > Formatting
77
Viewing Reports Online
Report Editor
For long running reports

Take advantage of scheduling
and disable Run Report Online.
78
Report Viewer
Viewing Reports Online
Report Editor
Enable Data Caching
Saves XML data for reuse up to the Cache
Expiration threshold
Improved performance with
different template/output format
Not recommended for real-time data
Enable Document Caching
Better performance
Consumes more Temp storage space
User Level (11g only)
Disable for better performance if data can be
shared across users
Cache Duration (11g only)
79
Data Model Design Guidelines

Element Naming
Avoid re-using the same name for element names; it can cause
confusion in template design.

For example, CITY under SHIPPING_ADDRESS and BILLING_ADDRESS.
But in many cases you are better off using different names e.g. S_CITY
and B_CITY
For reports that generate large data sets using 2 or 3 character names
for elements can have a large impact on performance and size.

Ex: a1, a2,
80

NULL Elements & XML Attributes
Avoid generating empty tags in the XML
Aggregation over fields that contain empty tags will fail with a not a
number exception
Missing fields do not cause an issue with XSL for example a print
statement will just return an empty string

Avoid XML attributes
They are supported in both RTF & Excel templates but they add an extra
layer of complexity; they are not supported in the BI Publisher Layout

Editor
81

OBIEE Data Source
If possible use SQL/JDBC
against BI Server instead of

using an Answers Request as
a data source
Tip: Copy the SQL in an
Answers Request and paste

into the Query Builder text
area
82

Sub Templates: Introduction
What is a sub template?
A document that contains layout and or code that can be defined once
and used multiple times

Multiple functions (called templates in XSL) or text segments can be
defined in a single sub template file
Sub template types
XSL sub templates for code re-use or separation
RTF sub templates for layout re-use
Caveat: Use of RTF sub templates makes it harder to understand the
template structure
83

Sub Templates: Use Cases
RTF sub templates
Re-use common layouts such as terms and conditions
Internationalized address block
XSL sub templates

Transformations for complex chart requirements
Dynamically apply formatting to a portion of data
(e.g. sub scripting / super scripting / chemical formula)

Print formatted XHTML data convert to FO using sub template (as used in
Oracle Contracts) (11.1.1.6 supports HTML in data)
Starting w/ 11.1.1.3 we recommend using Style Templates for Header / Footer instead of RTF Sub Template
84

Use Word Styles
Achieve consistency in the template and
between templates
In 11g use Style Templates to control the
template styles
85
86
87

Bi Publisher Best Practices 2159564

Încărcat de

Informații document

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

Bi Publisher Best Practices 2159564

Încărcat de

Drepturi de autor:

Formate disponibile

1

Copyright 2013, Oracle and/or its affiliates. All rights reserved.

THE FOLLOWING IS INTENDED TO OUTLINE OUR GENERAL

Copyright 2013, Oracle and/or its affiliates. All rights reserved.

BI Publisher & OBIEE Integration Best Practices

Copyright 2013, Oracle and/or its affiliates. All rights reserved.

Oracle Business Intelligence Publisher

development & maintenance

Copyright 2013, Oracle and/or its affiliates. All rights reserved.

XML / EFT / EDI

Oracle Business Intelligence Publisher

Layout Template Types

Layout Design Tools

Copyright 2013, Oracle and/or its affiliates. All rights reserved.

Oracle Business Intelligence Publisher

Copyright 2013, Oracle and/or its affiliates. All rights reserved.

BI Publisher & OBIEE Integration Best Practices

Copyright 2013, Oracle and/or its affiliates. All rights reserved.

Installation & System Requirements

Intelligence 11g Release 1 (11.1.1)

Copyright 2013, Oracle and/or its affiliates. All rights reserved.

Concurrent Use Case

Bursting Use Case

Users viewing reports online

Scheduled Jobs running at the

Number of users viewing Small,

% of Small, Medium, Large reports

Medium, Large, XLarge reports

Total Number of reports

Copyright 2013, Oracle and/or its affiliates. All rights reserved.

Copyright 2013, Oracle and/or its affiliates. All rights reserved.

Enterprise Deployment Options

Single Instance Architecture

Copyright 2013, Oracle and/or its affiliates. All rights reserved.

Enterprise Deployment Options

Copyright 2013, Oracle and/or its affiliates. All rights reserved.

Enterprise Deployment Options

High Availability Architecture

Business Intelligence and EPM

Copyright 2013, Oracle and/or its affiliates. All rights reserved.

Oracle BI Publisher 11g Scheduler

Web server/JMS Provider

BIP System Topic

BI Publisher Reports Repository

Copyright 2013, Oracle and/or its affiliates. All rights reserved.

BI Publisher & OBIEE Integration Best Practices

Copyright 2013, Oracle and/or its affiliates. All rights reserved.

Oracle Business Intelligence Publisher

Copyright 2013, Oracle and/or its affiliates. All rights reserved.

Data Template (10g only)

Copyright 2013, Oracle and/or its affiliates. All rights reserved.

the same JDBC driver

Connection already established to the source

with SQL type LOVs attached to them

Copyright 2013, Oracle and/or its affiliates. All rights reserved.

Copyright 2013, Oracle and/or its affiliates. All rights reserved.

Copyright 2013, Oracle and/or its affiliates. All rights reserved.

Data Model Design

Copyright 2013, Oracle and/or its affiliates. All rights reserved.

Data Model Design

resources (whenever possible)

Copyright 2013, Oracle and/or its affiliates. All rights reserved.

Data Model Design

parameter when users select All &