Importing Metadata and Working with Data Sources 4-37
Figure 4–6 Connection Pool Dialog for Standby Connection Pool
To create the primary connection pool for the standby database configuration: 1.
In the Administration Tool, in the Physical layer, right-click the database object for the standby database configuration and select New Object, then select
Connection Pool.
2.
Provide a name for the connection pool, and ensure that the call interface is appropriate for the primary database type.
3. Provide the Data source name for the primary database.
4.
Enter a user name and password for the primary database.
5. Click OK.
Figure 4–7 shows the Connection Pool dialog for the primary connection pool.
4-38 Metadata Repository Builders Guide for Oracle Business Intelligence Enterprise Edition
Figure 4–7 Connection Pool Dialog for Primary Connection Pool
Updating Write-Back Scripts in a Standby Database Configuration
If you use scripts that write to the database, such as scripts for aggregate persistence, you must update the scripts to explicitly refer to the primary connection pool.
Information written through the primary connection will be automatically transferred to the standby database through the regularly scheduled replication between the
primary and secondary databases, and will become available through the standby connection pool.
The following example shows a writeback script for aggregate persistence that explicitly specifies the primary connection pool:
create aggregates sc_rev_qty_yr_cat for DimSnowflakeSales.SalesFacts Revenue, QtySold at levels DimSnowflakeSales.Time.Year,
DimSnowflakeSales.Product.Category using connection pool StandbyDemo.Primary Connection in StandbyDemo.My_Schema
Setting Up Usage Tracking in a Standby Database Configuration
The Oracle BI Server supports the collection of usage tracking data. When usage tracking is enabled, the Oracle BI Server collects usage tracking data for each query
and writes statistics to a usage tracking log file or inserts them directly to a database table.
If you want to enable usage tracking on a standby database configuration using direct insertion, you must create the table used to store the usage tracking data typically S_
NQ_ACCT on the primary database. Then, import the table into the physical layer of the repository using the Administration Tool.
You must ensure that the database object for the usage tracking table is configured with both the standby connection pool and the primary connection pool. Then, ensure
that the CONNECTION_POOL parameter for usage tracking points to the primary database. For example, in NQSConfig.ini:
Importing Metadata and Working with Data Sources 4-39
CONNECTION_POOL = StandbyDatabaseConfiguration.Primary Connection;
See Managing Usage Tracking in Oracle Fusion Middleware System Administrators Guide for Oracle Business Intelligence Enterprise Edition for full information about usage
tracking, including how to create tables for usage tracking data and how to set parameters for usage tracking.
Setting Up Event Polling in a Standby Database Configuration
You can use an Oracle BI Server event polling table event table as a way to notify the Oracle BI Server that one or more physical tables have been updated. The event table
is a physical table that resides on a database accessible to the Oracle BI Server. It is normally exposed only in the Physical layer of the Administration Tool, where it is
identified in the Physical Table dialog as an Oracle BI Server event table.
The Oracle BI Server requires write access to the event polling table. Because of this, if you are using event polling in a standby database configuration, you must ensure that
the database object for the event table only references the primary connection pool.
See Cache Event Processing with an Event Polling Table in Oracle Fusion Middleware System Administrators Guide for Oracle Business Intelligence Enterprise Edition for full
information about event polling, including how to set up, activate, and populate event tables.
Setting Up Oracle BI Scheduler in a Standby Database Configuration
Oracle BI Scheduler is an extensible application and server that manages and schedules jobs, both scripted and unscripted. To use Oracle BI Scheduler in a standby
database configuration, you must ensure that the database object for Oracle BI Scheduler only references the primary connection pool.
See Configuration Tasks for Oracle BI Scheduler in Oracle Fusion Middleware Scheduling Jobs Guide for Oracle Business Intelligence Enterprise Edition for full
information about setting up and using Oracle BI Scheduler.
4-40 Metadata Repository Builders Guide for Oracle Business Intelligence Enterprise Edition
5
Working with ADF Business Component Data Sources 5-1
5
Working with ADF Business Component Data Sources
Oracle Business Intelligence supports connecting to ADF Business Components as data sources. This enables Oracle Business Intelligence users to query data from any
application that is built using the ADF Framework. For example, because Oracle CRM applications are developed using the ADF Framework, Oracle Business Intelligence
users can report on CRM data using an ADF Business Component data source that implements the required ADF Application Programming Interface API.
By using the ADF components as a data source to the Oracle BI Server, users can quickly integrate operational reporting with any application that is built on top of the
ADF Framework.
This chapter contains the following topics:
■
What Are ADF Business Components?
■
What Happens During Import?
■
About Specifying a SQL Bypass Database
■
Setting Up ADF Business Component Data Sources
■
Importing Metadata from ADF Business Component Data Sources
■
Enabling the Ability to Pass Custom Parameters to the ADF Application
■
Propagating Labels and Tooltips from ADF Business Component Data Sources
What Are ADF Business Components?
Oracle Application Development Framework Oracle ADF is an object-relational framework that can be used to create J2EE business services and expose underlying
database objects. This framework provides an abstraction layer that enables application developers to build applications quickly and efficiently.
When you use Oracle ADF to build service-oriented Java EE applications, you implement your core business logic as one or more business services. These back-end
services provide clients with a way to query, insert, update, and delete business data as required, while enforcing appropriate business rules. ADF Business Components
are prebuilt application objects that provide a ready-to-use implementation of Java EE design patterns and best practices.
The ADF model is represented through the ADF Business Component constructs called Entity Objects and View Objects, usually constructed and defined during design
time:
5-2 Metadata Repository Builders Guide for Oracle Business Intelligence Enterprise Edition
■
Entity Objects: ADF framework components that represent a row in a database
table and simplify modifying its data. Importantly, it enables you to encapsulate domain business logic for those rows to ensure your business policies and rules
are consistently validated.
■
View Objects: ADF framework components that encapsulate a SQL query and
simplify working with its results. In addition to read-only view objects, there are entity-based view objects that support updatable rows. The view object queries just
the data needed for the client-facing task at hand, then cooperates with one or more entity objects in your business domain layer to automatically validate and
save changes made to its view rows. Like the read-only view object, an entity-based view object encapsulates a SQL query, can be linked into
masterdetail hierarchies using view links, and can be used in the data model of your application modules.
Applications built using ADF obtain their data by querying the defined View Objects using the ADF APIs.
The ADF model also includes an application module, which is the transactional component that UI clients use to work with application data. It defines an updatable
data model along with top-level procedures and functions called service methods related to a logical unit of work related to an end-user task.
The application module serves as a container for multiple View Objects and Entity Objects, and also contains configuration related to the JDBC data source.
About Operational Reporting with ADF Business Components
You can use Oracle Business Intelligence integration with ADF Business Components to generate reports on data within your applications. For example, you can generate
reports based on expense report data entered into an Expense Application.
To do this, you would first import the Expense Application metadata into the Oracle BI repository using the Administration Tool, then map the data from the Physical layer
to the Business Model and Mapping layer and Presentation layer. After you restart the Oracle BI Server and reload the metadata into Oracle BI Presentation Services, you can
log in to Oracle BI Answers and drag and drop the columns to generate a report on the Expense Application data. For example, you can select columns to view a report of
your expenses grouped by category.
What Happens During Import?
On import, the required physical tables and complex joins are automatically created. The instances ViewObject and ViewLink are imported into Oracle Business
Intelligence. During query execution, the definitions retrieved from these instances are used to create the CompositeVO in ADF.
These complex joins are dummy joins and are not executed in Oracle Business Intelligence. Instead, they denote ViewLink instances that connect pairs of View
Objects in the ADF model. The physical table and complex join names correspond to the fully qualified ViewObject and ViewLink instance names, respectively. This
convention allows arbitrary nesting of ApplicationModules in the ADF model.
Note that the External Expression field in the Complex Join dialog for ADF data sources shows an arbitrary expression that has no meaning. This field is reserved for a
future release.
The name of the automatically generated joins follow a naming convention similar to ViewObjectName1_ViewObjectName2 for example, AppModuleAM.AP_VO1_
Working with ADF Business Component Data Sources 5-3
AppModuleAM_BU_VO1. The ViewLink instance name appears in the ViewLink Name
field of the Complex Join dialog. The complex joins are only created automatically if a ViewLink instance is available.
They are not created for ViewLink definitions. Joins using ViewLink definitions must be created manually. To do this, specify the ViewLink definition name in the
ViewLink Name
field of the Complex Join dialog. Alternatively, Oracle Business Intelligence joins between VOs in different
ApplicationModules are created upon import from ADF if custom properties are defined on the ApplicationModule. Note the following:
■
The property name format is BI_VIEW_LINK_property_name
■
The property value format is source_VO_instance_name, ViewLink_definition_name, destination_VO_instance_name
Be sure to use the fully qualified VO instance names for the source and destination VOs, as well as the fully qualified package name for the ViewLink definition.
About Specifying a SQL Bypass Database
The Oracle BI Server can automatically create composite View Objects at run time, so that an ad-hoc BI query can reference multiple View Objects in the ADF layer. For
improved performance, a SQL bypass query is generated that incorporates the projection columns, filters, and joins required by the BI query.
The SQL Bypass feature directly queries the database so that aggregations and other transformations are pushed down where possible, reducing the amount of data
streamed and worked on in Oracle Business Intelligence. When using a SQL Bypass database, the Oracle BI Server gets the VO query from the ADF Business Component
data source and then wraps it with the aggregations in the Logical SQL query. The query, including the aggregations, is then executed in the database. Because the
database computes the aggregation and less rows are streamed back to Oracle Business Intelligence, using a SQL Bypass database can result in significant
performance gains.
Multiple View Objects are modeled as separate BI physical tables and are connected with dummy complex joins. These joins only represent the ViewLinks in the ADF
model and are not executed by the Oracle BI Server.
You can specify the name of the SQL Bypass database in the connection pool for the ADF Business Component data source. The SQL Bypass database must be a physical
database in the Physical layer of the repository. The database object for the SQL Bypass database must have a valid connection pool, with connection information that
points to the same database that is being used by the JDBC Data source defined in the Oracle WebLogic Server that runs the ADF application.
The SQL Bypass database does not need to have any tables under it. After a valid database name is supplied, the SQL Bypass feature is enabled for all queries against
that ADF database.
Setting Up ADF Business Component Data Sources
This section explains how to configure your ADF Business Components for use with Oracle Business Intelligence.
See System Requirements and Certification
for information about supported versions.
5-4 Metadata Repository Builders Guide for Oracle Business Intelligence Enterprise Edition
This section contains the following topics:
■
Creating a WebLogic Domain
■
Deploying OBIEEBroker as a Shared Library in Oracle WebLogic Server
■
Deploying the Application EAR File to Oracle WebLogic Server from JDeveloper
■
Setting Up a JDBC Data Source in the WebLogic Server
■
Setting the Logging Level for the Deployed Application in Oracle WebLogic Server
Creating a WebLogic Domain
Create a WebLogic Domain for your ADF Business Components that supports WebLogic Server, Oracle Application Core Webapp, and Oracle JRF.
To create a WebLogic domain that supports the required components: 1.
Start the WebLogic Configuration Wizard. For example, on Windows, run MW_ HOME\wlserver_10.3\common\bin\config.cmd.
2. Select Create a new WebLogic domain and click Next.
