Set Up ADF Data Sources
These topics explain how to configure your ADF Business Components.
This section contains the following topics:
Create a WebLogic Domain for ADF Business Components
To configure your ADF Business Components for use with Oracle Analytics Server, you need to create a WebLogic Domain for your ADF Business Components that supports WebLogic Server, Oracle Application Core (Webapp), and Oracle JRF.
You can start and stop the Oracle WebLogic Server for this domain using command-line scripts in the domain directory. For example, on Windows, use the following:
-
BI_DOMAIN\bin\startWebLogic.cmd
-
BI_DOMAIN\bin\stopWebLogic.cmd
Deploy OBIEEBroker as a Shared Library in Oracle WebLogic Server
To configure your ADF Business Components for use with Oracle Analytics, you need to install OBIEEBroker, making its physical file or directory known to Oracle WebLogic Server, and start it.
This process deploys the OBIEEBroker library as a shared library in Oracle WebLogic Server.
After the library has been installed and started, other deployed modules can reference the library. The OBIEEBroker shared library is installed by default.
Deploy the Application EAR File to Oracle WebLogic Server from JDeveloper
To configure your ADF Business Components for use with Oracle Analytics Server, you need to deploy the application EAR file to Oracle WebLogic Server from JDeveloper.
Before beginning this procedure, ensure that the following conditions are true:
-
You've an ADF Model project that contains
ApplicationModules
and view objects that are exposed to Oracle Analytics Server. -
You've deployed
OBIEEBroker
as a shared library in Oracle WebLogic Server. See Deploy OBIEEBroker as a Shared Library in Oracle WebLogic Server. -
Oracle WebLogic Server is running.
-
Start JDeveloper, on Windows, run
MW_HOME\jdeveloper\jdev\bin\jdev.exe
. -
Select File, then select Open to open the project that contains your ADF Business Components in JDeveloper. If prompted, allow JDeveloper to migrate the project to the latest version.
-
Create a new Application Module configuration, as follows:
-
In the Model project, double-click the application module, then click the Configurations tab for that application module.
-
Create a new configuration with the following characteristics:
-
Select JDBC DataSource for Connection Type.
-
Keep the default DataSource Name, for example,
java:comp/env/jdbc/ApplicationDBDS
.
When you set up the JDBC data source in Oracle WebLogic Server in a later step, you use part of this DataSource Name as the JNDI name required by Oracle WebLogic Server. The JNDI name is the DataSource Name without the
java:comp/env
context prefix, for example,jdbc/ApplicationDBDS
. -
-
-
Create a Business Component Archive deployment profile, as follows:
-
In the Projects window, right-click the Model project and choose New.
-
Select Deployment Profiles under General in the left pane, then choose Business Components Archive in the right pane and click OK.
-
Provide a name for the deployment profile, for example, MyApplication_Archive, and click OK.
-
On the Deployment page, click OK.
-
-
In the Projects window, right-click the Model project and select Deployyour_deployment_profile_name from Deploy, or use the deployment wizard by selecting Deploy to File.
After the project has been deployed, two jar files are created in the deploy directory for the Model project, for example,
MyApplication_Archive_Common.jar
andMyApplication_Archive_MiddleTier.jar.
-
Create a new web project for the application, as follows:
-
Right-click the global application and select New Project.
-
Select Projects from the left pane, then select Web Project from the right pane.
-
Provide a project name, for example, OBIEEBroker.
-
Click Next until you reach the Web Project Profile page.
-
Modify the Java EE Context Root to a name that better represents your application, for example, MyApplication.
This value determines the URL that you use to connect to the application from Oracle Analytics Server, for example,
http://localhost:7001/MyApplication/obieebroker
.
-
-
Edit the Profile Dependencies of the WAR deployment, as follows:
-
Right-click the Web Project you just created, for example, OBIEEBroker, and select Project Properties.
-
From the left pane, select Deployment. Then, open the WAR File deployment profile on the right pane.
-
Select Profile Dependencies from the left pane, and then, on the right pane, select the Common and Middle Tier deployment profiles of your Model project.
-
-
Expand the Web Project and open
web.xml
. Then, go to the source view of the file. -
In the
web.xml
source, replace the content within the<web-app>
element with the following:<context-param> <description>This holds the Principals (CSV) that a valid end user should have (at least one) in order to query the ADF layer from BI.</description> <param-name>oracle.bi.integration.approle.whitelist</param-name> <param-value>Application_Roles_List</param-value> </context-param> <filter> <filter-name>ServletADFFilter</filter-name> <filter-class>oracle.adf.share.http.ServletADFFilter</filter-class> </filter> <filter-mapping> <filter-name>ServletADFFilter</filter-name> <servlet-name>OBIEEBroker</servlet-name> <dispatcher>FORWARD</dispatcher> <dispatcher>REQUEST</dispatcher> </filter-mapping> <servlet> <servlet-name>OBIEEBroker</servlet-name> <servlet-class>oracle.bi.integration.adf.v11g.obieebroker.OBIEEBroker </servlet-class> </servlet> <servlet-mapping> <servlet-name>OBIEEBroker</servlet-name> <url-pattern>/obieebroker</url-pattern> </servlet-mapping>
Following this step ensures that the OBIEEBroker servlet is used to access your application from Oracle Analytics Server.
For application_roles_list, provide a list of application roles in CSV form. For example:
<param-value>FBI_TRANSACTION_ANALYSIS_GENERIC_DUTY, OBIA_ANALYSIS_GENERIC_DUTY, OBIA_EXTRACT_TRANSFORM_LOAD_DUTY, FUSION_APPS_BI_APPID</param-value>
If you provide a list of application roles, a user's application role is checked before access is allowed to the application. This runtime check requires the following grant to be present in the
domain_name/config/fmwconfig/system-jazn-data.xml
file for the WebLogic domain:<grant> <grantee> <codesource> <url>file:${domain.home}/servers/${weblogic.Name}/tmp/ _WL_user/oracle.bi.integration.adf/-</url> </codesource> </grantee> <permissions> <permission> <class>oracle.security.jps.JpsPermission</class> <name>IdentityAssertion</name> <actions>execute</actions> </permission> <permission> <class>oracle.security.jps.JpsPermission</class> <name>AppSecurityContext.setApplicationID.obi</name> </permission> </permissions> </grant>
If you don't want application roles to be checked by the OBIEEBroker servlet, use DISABLE_WHITELIST_ROLE_CHECK as the value for the <context-param> in web.xml. For example:
<param-value>DISABLE_BI_WHITELIST_ROLE_CHECK</param-value>
-
Create an EAR deployment profile for the application, as follows:
-
Right-click the global application and select Application Properties.
-
From the left pane, select Deployment, then click New on the right pane to create a new deployment profile.
-
For Archive Type, select EAR File. Then, provide a name for the deployment profile, for example, MyApplication.
The deployment profile name is used as the name displayed in the list of deployments in Oracle WebLogic Server.
-
From the left pane, select Application Assembly. Then, on the right pane, select the webapp deployment profile of your Web Project.
Following this step ensures that the WAR file from your Web Project is included in the EAR file.
-
-
Under Application Resources, select Descriptors, select META-INF , and then select
weblogic-application.xml
. -
On the left, select the Libraries tab.
-
Create two new Shared Library References, as follows:
-
Create the first Shared Library Reference with the following characteristics:
-
Library Name:
oracle.bi.integration.adf
-
Implementation Version:
11.1.1.2.0
-
-
Create the second Shared Library Reference with the following characteristics:
-
Library Name:
oracle.applcore.model
-
Implementation Version:
11.1.1.0.0
-
These two Shared Library References create the following entries in the
weblogic-application.xml
file for the application:<library-ref> <library-name>oracle.bi.integration.adf</library-name> <implementation-version>11.1.1.2.0</implementation-version> </library-ref> <library-ref> <library-name>oracle.applcore.model</library-name> <implementation-version>11.1.1.0.0</implementation-version> </library-ref>
-
-
Right-click and select Deploy EAR_deployment_profile_name to deploy the EAR file to Oracle WebLogic Server by the global application.
-
From the dialog that appears, select Deploy to Application Server, and then follow the instructions in the wizard.
-
To verify that the application has been deployed, log in to the WebLogic Server Administration Console and click Deployments under Your Deployed Resources. Verify that your application appears in the list, for example,
obieebroker_app_name
.
Set Up a JDBC Data Source in the WebLogic Server
You must configure the ADF Business Components that you plan to use with Oracle Analytics Server.
To configure your ADF Business Components for use with Oracle Analytics Server, you must set up a JDBC data source in Oracle WebLogic Server for your application.
- Ensure that Oracle WebLogic Server is running. If it isn't running, start it. For example, on Windows, run
BI_DOMAIN\bin\startWebLogic.cmd
. - Open the WebLogic Server Administration Console. For example, if your Oracle WebLogic Server is running locally on port 7001, go to
http://localhost:7001/console
. - Log in to the WebLogic Server Administration Console with the credentials you created when you set up your WebLogic domain.
- On the Home Page, select JDBC, then select Data Sources.
- Click New.
- Provide information for your data source. For Name and JNDI Name, provide the DataSource Name you specified in the Application Module configuration for the application, without the
java:comp/env
context prefix, for example,jdbc/ApplicationDBDS
. In addition, make sure to select the target on which you want to deploy the data source before exiting the wizard. - Click Finish when you're done providing JDBC data source settings.
Set the Logging Level for the Deployed Application in Oracle WebLogic Server
The server_name-diagnostic.log
file for the server where your application is deployed contains information about your deployed application.
You can find this file in the server-specific directory within your domain. For example, on Windows, the log file for the AdminServer is located in:
BI_DOMAIN\servers\AdminServer\logs
.
Log levels include:
-
SEVERE
-
WARNING
-
INFO
-
CONFIG
-
FINE
-
FINER
-
FINEST