1-34 Upgrade Guide for Oracle Business Intelligence
Figure 1–7 BI Publisher 11g Report and Data Model
Note the following:
■
A single data model can be used by multiple reports
■
The parameters from the data model can be customized at the report level
■
Multiple bursting definitions can be created for a data model and then selected at the report level
In 10g, a sub template resided in a location outside the BI Publisher repository. In 11g, sub templates are maintained as objects within the catalog. For more information, see
Section 1.4.3.8, Sub Template Management in Catalog. A style template is a specialized template introduced in 11g to simplify the
maintenance of styles across multiple reports, similar to a stylesheet. For more information, see
Section 1.4.3.7, Consistent Look and Feel Using Style Templates.
1.4.1.5 Enhanced Catalog Object Security
In 10g granting access to catalog objects was performed in the Administration Roles and Permissions
page. To grant a user role access to run a report, the Administrator simply mapped the folder in which the report resided to the role in the Roles and
Permissions page. Any user with that role would then have permission to view any report within the folder.
Planning to Upgrade from Oracle BI 10g to BI 11g 1-35
In 11g, the granting of permissions is performed within the catalog using the Permissions
task. A new set of permissions are available to more granularly define what users can do. The permissions are:
■
Read
■
Write
■
Delete
■
Run Report Online
■
Schedule Report
■
View Report Output It is important to note that for a report consumer to successfully run a report, his role
must have the read permission granted for every object that is referenced by the report. For example, in 10g, to run the Employee Salary Report, a user required only
access to the folder in which the report resided. In 11g, now that the data model is a separate object, a user also requires read permissions on the data model object. If the
report references additional objects, such as a Style Template or Sub Template, then read permissions must also be granted for these objects.
Also note that in 11g, all roles that must access the data source, even just for viewing reports, must be granted access to that data source. This requires assigning roles to
data sources in the BI Publisher Administration page. For more information, see About Access to Data Sources in the Oracle Fusion Middleware Administrators Guide
for Oracle Business Intelligence Publisher.
1.4.2 BI Publisher: Other Upgrade Considerations
Other upgrade considerations are described in the following sections:
■
Section 1.4.2.1, Support for BI Publisher File-Based Catalog or Oracle BI Presentation Catalog
■
Section 1.4.2.2, Discoverer Workbooks Not Supported as a Data Set Type
■
Section 1.4.2.3, Compatibility Between 10g and 11g Reports
■
Section 1.4.2.4, Upgraded Data Models Might Not Be Editable
■
Section 1.4.2.5, Upgraded Data Templates Might Cause Validation Errors in 11g
■
Section 1.4.2.6, Applications Using 10g Web Services for Integration Will Require Changes to Application Code
■
Section 1.4.2.7, Differences Between 10g and 11g Sub Template Implementation
1.4.2.1 Support for BI Publisher File-Based Catalog or Oracle BI Presentation Catalog
Release 11g supports the following catalog types:
■
Oracle BI Publisher - File System, for standalone implementations
■
Oracle BI Presentation Catalog, for integrated implementations The 10g option, XML DB repository type, is not an option in 11g.
1.4.2.2 Discoverer Workbooks Not Supported as a Data Set Type
If the 10g implementation includes reports that use Discoverer workbooks as data sources, these reports cannot run in 11g. A workaround to continue to use the
