Académique Documents
Professionnel Documents
Culture Documents
Table of Contents
1. Overview ............................................................................................................................................... 2 1.1. 1.2. 1.3. 1.4. 1.5. 1.6. 2. What Is Oracle Business Intelligence Applications?...................................................................... 2 What Business Areas Are Supported in Oracle BI Applications? .................................................. 2 Enterprise Resource Planning Analytics........................................................................................ 2 Oracle BI Applications Component Descriptions .......................................................................... 5 What Is the Oracle BI Applications Product Lifecycle? ................................................................. 7 Oracle BI Applications Roadmap ................................................................................................... 9
Installing Prerequisites for Oracle BI Applications .............................................................................. 10 2.1. 2.2. 2.3. 2.4. 2.5. 2.6. 2.7. 2.8. 2.9. Recommendations for Oracle Business Analytics Warehouse Databases.................................. 10 Using Oracle Template Files ........................................................................................................ 10 Hardware Requirements ............................................................................................................. 11 Installing Oracle Database for data warehouse. ......................................................................... 11 Installing Latest version of JDK.................................................................................................... 11 Installing Oracle WebLogic Server .............................................................................................. 11 Running Fusion Middleware RCU ............................................................................................... 12 Installing Oracle Business Intelligence Enterprise Edition 11g ................................................... 18 Installing Oracle Data Integrator (ODI) ....................................................................................... 23
3.
Installing and Configuring Oracle BI Applications ............................................................................... 33 3.1. 3.2. 3.3. 3.4. Creating Database Instances for Schemas and Repositories ...................................................... 33 Creating Schemas Using Business Analytics Applications Suite RCU .......................................... 34 Installing Oracle BI Applications.................................................................................................. 47 Applying Platform Patches .......................................................................................................... 53
1. Overview
1.1. What Is Oracle Business Intelligence Applications?
Oracle BI Applications is a suite of prebuilt business intelligence solutions that deliver role-based intelligence. Oracle BI Applications support prebuilt aggregation and analysis of information from a variety of transactional applications, including Oracle E-Business Suite, Oracle Siebel, PeopleSoft, JD Edwards EnterpriseOne, as well as non-Oracle applications. These transactional applications are referred to source systems, because they provide the underlying data that source analyses.
General Ledger Profitability Accounts Payable Accounts Receivable Fixed Assets Employee Expenses Budgetary Control 1.3.2. Oracle Human Resources Analytics
Absence and Leave Accrual Payroll Recruitment Learning Time and Labor 1.3.3. Oracle Manufacturing Analytics
Planning Manufacturing Execution Quality Production Costing Inventory 1.3.4. Oracle Procurement and Spend Analytics
Spend Analyzer Supplier Performance Sourcing Procurement Performance Employee Expenses 1.3.5. Oracle Project Analytics
Budgets Cost Commitments Billing Funding Contracts Revenue Forecast Resource Management GL Reconciliation Cross Charges
1.3.6. Oracle Supply Chain and Order Management Analytics Oracle Supply Chain and Order Management Analytics includes the following modules:
Order Management Order Fulfillment Inventory and Logistics Costing (for Oracle E-Business Suite only) 1.3.7. Oracle Student Information Analytics
A universal data warehouse design that enables you to integrate data from different source systems. Multiple instance support that enables you to use one data warehouse deployment for multiple source system instances. Conformed dimensions that enables you to view the data from different subject areas.
The Oracle Business Analytics Warehouse is supported only on the Oracle database. 1.4.4. Oracle BI Applications Configuration Manager and Functional Setup Manager Oracle BI Applications Configuration Manager is a web application for setting up and maintaining an Oracle Business Intelligence Applications environment. Oracle BI Applications Configuration Manager works in conjunction with Functional Setup Manager to provide guided Tasks to configure Offerings and Functional Areas. Functional Setup Manager enables you to manage and perform functional configuration tasks for configuring Offerings. You use Functional Setup Manager to deploy the Offering and Functional Areas. Functional Setup Manager generates a list of configuration tasks
for the deployed areas, which you can assign to different functional developers and monitor the implementation status. 1.4.5. Oracle Data Integrator Oracle BI Applications uses Oracle Data Integrator (ODI) as its data integration platform. ODI is a comprehensive, unified ETL tool for building, deploying, and managing complex data warehouses. ODI performs high-volume, high performance batch and real-time loads, as well as data validation. In an Oracle BI Applications environment, ODI works in conjunction with Oracle BI Applications Configuration Manager, which provides a user interface for managing load plans as well as access to ODI Console, the web-based console that enables you to view objects in the ODI repository. 1.4.6. Oracle GoldenGate Oracle BI Applications can optionally leverage Oracle GoldenGate. Oracle GoldenGate is a data replication tool leveraged to create a replicated OLTP schema or schemas, facilitate change data capture, and aid in ETL and transactional system performance. It provides an OLTP mirrored schema on the Oracle Business Analytics Warehouse database instance using replication. This replicated Source-Dependent Schema is then used as a source during ETL Oracle GoldenGate provides less network Input/output (I/O) during ETL because the source data for extract is in the same physical instance/machine as the Oracle Business Analytics Warehouse target tables. It can also shorten the length of time that ETL takes by minimizing the impact to the OLTP database.
1.5.1. Installing Pre-Requisites and Oracle BI Applications Before installing Oracle BI Applications, you will want to review the Oracle BI Applications Installation Guide and ensure that you have completed all of the pre-requisite steps. You install Oracle Business Intelligence Enterprise Edition platform and Oracle Data Integrator. Then, you install Oracle Business Intelligence Applications as described in the Oracle Business Intelligence Applications Installation guide. This guide includes topics and instructions on pre-installation and deployment requirements, installing repositories, and installing Oracle BI Applications. 1.5.2. Configuring Oracle BI Applications After you have installed Oracle Business Intelligence Applications, you perform a functional configurations for each of the applications that you want to use. Oracle BI Applications configuration involves Oracle BI Applications Configuration Manager and Oracle BI Applications Functional Setup Manager. These web applications help you to perform functional configurations, including creating an implementation project, assigning tasks, running the domain ETL, and setting up your functional configuration data. Some of the tasks that you perform include specifying the Initial Extract Date, calendar type, and currency types. These processes are described in the Oracle Business Intelligence Applications Configuration Guide. 1.5.3. Performing a Full Load of Your Transactional Data into Warehouse. After you have configured your load plan and your functional configuration data you perform a full load of your data into the Oracle Business Analytics Warehouse. 1.5.4. Testing Your Oracle BI Applications Deployment and Moving to Production You test your Oracle BI Applications deployment in a pre-production environment with users who are preparing Oracle BI Applications for use by others. During this phase, you continue to customize the deployment based on user feedback and any encountered issues.
1.5.5. Running Regular or Daily ETL with Oracle BI Applications After your Oracle BI Applications deployment is running, you will run periodic ETL on changed data from your transactional database into your Oracle Business Analytics Warehouse. Oracle BI Applications has two ETL modes: full load and incremental load.
Full Load During a full load, all records are extracted from tables that are sources for dimension tables and all records created after an 'Initial Extract Date' from tables that are sources for fact tables. The Initial Extract Date value is a configurable value and is set for each data source in the Oracle BI Applications Configuration Manager.
Incremental Load During an incremental load, Oracle BI Applications extracts records that have changed or were created after a 'Last Extract Date'. This is done by comparing the Last Extract Date value to a Last Updated Date (or LUD) type column in the source table. If the source table does not have such a column, Oracle BI Applications extract all records from that table. 1.5.6. Patching Oracle BI Applications
Patching involves copying a small collection of files over an existing installation. A patch is normally associated with a particular version of an Oracle product and involves updating from one minor version of the same product, or applying an interim patch to resolve a specific issue. to a newer minor version of the same product. An Oracle BI Applications patch can include bug fixes, metadata, and binary file updates. 1.5.7. Administering Oracle BI Applications Administering Oracle BI Applications includes customizing Oracle Business Analytics Warehouse, managing language support, configuring Oracle BI Applications for deployment in additional languages, and managing Oracle GoldenGate and source dependent schemas.
Allocate around 50 to 70 percent of the total available server memory to the database, assuming no other application is running on the same server. At a minimum, separate the data and index tablespaces. Create more tablespaces to separate heavily used tables and their indexes. Oracle recommends using 8k block size for Oracle warehouses. For more information about block size and Oracle databases, see the Oracle Database 11g Documentation Library on Oracle Technology Network. If you are using multiple disk storage systems, stripe the tablespace containers and files across as many disks as possible. Raw devices for tablespaces provide better performance as compared to cooked file systems. RAID-5 is known to give a good balance of performance and availability.
8 GB of free memory for run-time requirements. 35 GB free disk space to run the Business Analytics Applications Suite installer. This disk space will be released after the installer finishes.
If above command doesnt work then make sure java version is working
Follow on screen steps and complete the installation of WebLogic. Provide jdk path if required. Dont configure the WebLogic at this time.
Metadata Services (appears under AS Common Schemas) Make a note of the Metadata Services schema owner name and password. You will need these values when you run the configApps.bat or configApps.sh file to set up Oracle BI Applications.
Caution: Do not select the option to install the Oracle Data Integrator schema. You will install an Oracle BI Applications-specific ODI schema when you run the Business Analytics Applications Suite RCU.
If you are deploying Indirect Spend Planning in addition to Oracle BI Applications, you must select the options to install the following schemas:
SOA Infrastructure User Messaging Service Make a note of these schema owner names and passwords. You will need these values when you run the configApps.bat or configApps.sh file to set up Oracle BI Applications.
To start the setup of RCU open rcu.bat available in the bin directory and follow on screen instructions.
Just select Oracle Business Intelligence and rest of the required things will automatically be selected.
Enter the password for metadata schemas and follow the instructions on the screen to complete the setup.
Oracle BI EE must be deployed on WebLogic. Websphere is not supported for Oracle BI Applications. The BI Domain should not be extended before running the Business Analytics Applications Suite installer. Installing Oracle BI EE using the Simple Install mode is not supported. Installing Oracle BI EE on Windows 32-bit and Linux 32-bit is not supported for Oracle BI Applications. If you are installing Oracle BI EE in Enterprise Install mode, on the Configure Components screen select: o Business Intelligence Enterprise Edition. Business Intelligence Publisher will be automatically selected.
o o
Select software only install if you have already installed WebLogic 10.3.6 or later.
Provide the path where WebLogic is already installed, then next, next and press install
Click Finish
On the ODI installer Welcome screen, ignore the message regarding creation of the ODI Repository. You will create the ODI Repository for Oracle BI Applications later when you run the Business Analytics Applications Suite RCU. On the Select Installation Type screen, select all the components under Java EE Installation that is, Java EE Agent, ODI Console, and Public Web Service. On the Specify Installation Locations screen, enter the Middleware Home where Oracle BI EE is installed. Note: The installation of ODI in other locations is not supported for BI Applications. If you choose to install ODI Studio, then on the Repository Configuration screen, you must select the Skip Repository Configuration option.
The ODI installer is a generic installer. To launch the installer, use one of the following commands:
Platform Command
setup.exe -jreLoc <location of jdk 1.6.0 or higher>
Windows
UNIX Linux
Press next, then skip software updates then again press next.
Provide Middleware home location and press next and again next.
Press Install
Press Next
Press Finish.
Business Analytics Warehouse schema. Oracle BI Applications Components Repository (for Configuration Manager and Functional Setup Manager). ODI Repository for Oracle BI Applications (includes Master and Work repositories). Operational Planning schema (only required if Indirect Spend Planning will be deployed).
In my case, I am using one Oracle database for all components which is already installed. Note the following points:
For this release of Oracle BI Applications, the Business Analytics Warehouse is supported only on Oracle Database. The Oracle BI Applications Components Repository and ODI Repository for BI Applications are supported only on Oracle Database.
The Business Analytics Warehouse, BI Applications Components Repository, and ODI Repository can be installed on different database servers. The ODI Master and Work repositories are installed into the same schema.
Oracle Business Analytics Warehouse Oracle Business Applications Components ODI Repository for Oracle BI Applications Oracle Operational Planning (only required for Indirect Spend Planning deployments)
Before you run the Business Analytics Applications Suite RCU, note the following points:
On Windows machines, make sure that you unzip the rcuHomeBIApps.zip file into a directory that does not have spaces in the directory path. The RCU uses .dmp files to create the required schemas. You must copy the .dmp files for each schema to a directory with global write access on the appropriate database server machines. (RCU writes log files to this directory.) The .dmp files are located in BIA_RCU_HOME/rcu/integration/biapps/schema. To create schemas with RCU on Oracle databases, you must possess the DBA privilege and be logged in as SYSDBA (for example, as user SYS, with the SYSDBA role selected). If you are creating schemas on different databases, then you will need to run RCU multiple times, once for each database connections, because the database connections are different for the different database servers.
To create the Oracle BI Applications and Operational Planning schemas using the Business Analytics Applications Suite RCU: 1. Access the bin directory in the 2. Start RCU, as follows: o UNIX:
./rcu BIA_RCU_HOME.
Windows:
rcu.bat
4. On the Create Repository screen, select Create, and then click Next.
5. On the Database Connection Details screen, specify the connection details for the database in which you want to store the schemas. Note that you must possess the DBA privilege and be logged in as SYSDBA (for example, as user SYS). Specify the following database connection details:
Field Name Action
Database Type Host Name Port Service Name Username Password Role
Select Oracle Database. Other database types are not supported in this release. Specify the fully qualified host name of the machine hosting the database. For example,machine12345.example.com Specify the port number over which the database communicates. The default port number for an Oracle database is 1521. Specify the service name for the database. Typically, the service name is the same as the global database name. Specify the user name for the database. The default user name is SYS. The user must have DBA or SYSDBA privileges. Specify the password for the username specified in the Username field. Select SYSDBA.
6. Click Next to display the Select Components screen. 7. On the Select Components screen, near the top of the dialog, select Create a new Prefix. The default prefix is
DEV.
RCU automatically creates the schema owner (schema name) in the format prefix_schemaname. Select the following options:
Schema Option Default Schema Owner
Oracle Business <prefix>_DW (required for all deployments). Analytics Warehouse Oracle Business <prefix>_BIACOMP (required for all deployments). Applications When you select the BI Applications Components Repository Components (BIACOMP), RCU will create an additional schema, named BIACM_IO. Do not modify or delete this schema. It is required for metadata access by the different Oracle BI Applications components. Oracle Integrator and Repository Operational Planning Data <prefix>_BIA_ODIREPO (required for all deployments). Master Work <prefix>_OPL (required only for Indirect Spend Planning deployments).
9. On the Schema Passwords screen, specify and confirm a password for the schemas, then click Next to proceed to the Custom Variables screen. Note: The RCU uses .dmp files to create the required schemas. Before you perform the action in the Custom Variables screen, you must copy the .dmp files for each schema to a directory with global write access on the appropriate database server host machine. (RCU writes log files to this directory). The .dmp files are located in BIA_RCU_HOME\rcu\integration\biapps\schema.
10. On the Value field in the Custom Variables screen, for each schema enter the directory path of the folder on the database server that contains the .dmp file. Note: Do not include the name of the .dmp file in the directory path. In my case all paths will be same as I am installing all components on the same machine. Click Next to proceed to the Map Tablespaces screen.
11. The Map Tablespaces screen displays the default and temporary tablespaces for the schemas. On this screen, do the following: a. Leave the default values for Default Tablespace and Temp Tablespace for each schema. Dont click next yet.
b. Set the temporary tablespace size for the data warehouse tablespaces according to the values in the table below: - Click Manage Tablespaces. - In the left-side navigation panel, select the appropriate tablespace name. - In the main window, select the tablespace name under the Datafiles heading. - Click the Edit icon to display the Datafile dialog. - In the Edit Datafile dialog, set the temporary tablespace size according to the table below for each tablespace.
Tablespace Value
<prefix>_DW_DATA
Size: 20 GB Maximum Size: Unlimited Leave the remaining default values. Size: 5 GB Maximum Size: Unlimited Leave the remaining default values. Size: 10 GB Maximum Size: Unlimited Leave the remaining default values. Size: 15 GB Maximum Size: Unlimited Leave the remaining default values.
<prefix>_DW_IDX
<prefix>_DW_STG
<prefix>_DW_TEMP
12. Click OK to exit the Edit Datafile dialog. Then, click Next in the Map Tablespaces screen, and click OK in the message dialog to create the tablespaces for the schemas. This might take some time.
13. On the Summary screen, click Create to start the schema creation process. When the schemas are created with no errors, the Completion Summary screen is displayed. 14. On the Completion Summary screen, click Close.
The Business Analytics Applications Suite installer is a generic installer, which requires JDK 1.6.0_29 or higher or JRockit-JDK 1.6.0_29 or higher to be installed. 35 GB free disk space is required to run the Business Analytics Applications Suite installer. This disk space will be released after the installer finishes.
To run the Business Analytics Applications Suite installer: 1. Launch the Business Analytics Applications Suite installer by entering the following in Disk1 Directory. The Business Analytics Applications Suite installer displays the Welcome screen.
Platform Command
Windows
In a command prompt:
setup.exe -jreLoc <Drive:\...\jdk location>
Where jdk location is the directory that contains the bin folder. For example:
setup.exe -jreLoc C:\Progra~1\Java\jdk1.7.0_21
Note: If you are running the installer on a Linux machine that does not have the file /etc/oraInst.loc, the Specify Inventory Location screen will display.
2. Click Next to display the Prerequisite Checks screen. This screen analyzes the host computer to ensure that specific operating system prerequisites have been met. If any of the prerequisite checks fail, then an error message appears in the bottom portion of the screen. Fix the error and click Retry to try again. If you want to ignore the error or warning messages and continue with the installation, click Continue. Click Abort to stop prerequisite checking for all components.
3. Click Next to display the Specify Installation Location screen. 4. In the Specify Installation Location screen, specify the details of the Oracle BI EE installation.
Field Action
Specify the path to the directory for an existing Oracle Middleware home where Oracle BI EE has been installed. If you do not know the location of the directory, click Browse to locate the directory on your system.
Oracle Home Specify the Oracle Home for BI, for example, Oracle_BI1. Do not specify Directory any other Oracle home or choose to create a new one. The Oracle Home for BI directory is where the software binary files for Oracle BI Applications and Operational Planning Applications will be installed.
5. If you are installing on a Windows operating system, make sure that the directory paths are valid and do not contain double backslashes (\\). 6. Click Next to display the Summary screen. 7. In the Summary screen, review the summary information, and click Next to start the installation.
The installer installs the Oracle BI Applications folders and files in the Oracle Home for BI directory. Note: Even when the progress bar on the installer reports 100% complete, you must wait until the Finish button is displayed.
For Windows do below step. Then, with the same text editor application, open the APPLY_PATCHES.pl file in the same directory and modify the following lines within the download_patch routine, from the default:
Then, from the Windows Command prompt type in the following to run the patch installer script:
Once the script completes, check the resulting output which should look similar to this:
* BIAPPSSHIPHOME Patching Report .......... Patch Succeded: fsclite_rel7mlr2_16424872.zip Patch Succeded: BISHIPHOME_11_1_1_7_0_GENERIC_130409_1210_16492220.zip Patch Succeded: atglite_rel7mlr5A_database_16239380.zip Patch Succeded: atglite_rel7mlr5_16480022.zip
Patch Succeded: fsmlitedb_rel7mlr2_16424869.zip Patch Succeded: fsmlite_rel7mlr2_16424870.zip Patch Succeded: BISERVER_11_1_1_7_0_WINDOWS_X64_130326_2045_4_16583998.zip Patch Succeded: BIFNDN_11_1_1_7_0_WINDOWS_X64_130322_1000_5_16462147.zip
* Oracle Common Patching Report .......... Patch Succeded: p16433147_111170_Generic.zip Patch Succeded: p16080773_111170_Generic.zip Patch Succeded: Webservices_Patch-3-PS6RC3_bug-16487786.zip Patch Succeded: p16433036_111170_Generic.zip Patch Succeded: JDEVADF_REL7MLR10-RT_16525527.zip Patch Succeded: WebCenter_BP1REL7RC3_16311963.zip Patch Succeded: fmw_diagnostics_14757820_2.zip Patch Succeded: SOACOMMON_REL7B8_16438735.zip * SOA Patching Report .......... Not applying SOA Patches since SOA Home (SOA_HOME) value is not specified * ODI Patching Report .......... Patch Succeded: p16629917_111170_Generic.zip
Note that no Weblogic patches will be applied in this step, as they only apply to WebLogic Server 10.3.6 (to which you will upgrade later on in this process) and Oracle no longer require these patches to be applied.
On the Create or Scale Out BI System screen, select Create New BI System. For information about the options in this screen, see Section A.4, "Create, Scale Out, or Extend BI System," in Oracle Business Intelligence Suite Enterprise Edition Installation and Upgrade Guide.
On the Configure Components screen, select the following options: o Business Intelligence Enterprise Edition. Business Intelligence Publisher will be automatically selected.
o o
Note: Do not scale out the BI Domain. Screen are on next pages.
Open config.bat
Provide schema details as created earlier in RCU. Make sure tnsnames.ora file present in (:\Oracle\Middleware\Oracle_BI1\network\admin Or TNS_ADMIN is set where tnsnames.ora file is present.
Similarly for second schema and then again press next of autoport configuration.
Skip software updates, Press next, and then press configure. Click finish when done.
Oracle BI Applications Configuration Manager, Functional Setup Manager, ODI Java EE Agent, ODI Console, and Load Plan Generator are deployed into WebLogic Server. Component wiring is performed. A BI Applications Administrator User (with full access to Configuration Manager and access to ODI with the Supervisor role) is created in WebLogic Server embedded LDAP.
The configApps.bat and configApps.sh files are located in <BI_Oracle_Home>/bin. To configure components by running the configApps.bat or configApps.sh file: Start the configuration utility from the bin directory in the name is Oracle_BI1), based on the operating system: UNIX commands:
cd BI_Oracle_Home/bin ./configApps.sh BI_Oracle_Home
(default folder
Windows commands:
cd BI_Oracle_Home\bin configApps.bat
On the Welcome screen, click Next. And next again on pre-req screen.
On the Extend BI Domain screen, specify the following: Field Host Name Port User Name User Password Description The host name of the computer on which the WebLogic Server domain exists. This field is read-only. Specify the port number over which the WebLogic Server domain communicates. The default is 7001. Specify the user name for logging into the WebLogic Server. Specify the password for logging into the WebLogic Server.
Select as below and press next. (If you are interested in ISP and selected ISP in prior installations then choose this option too)
Enter Repository Password and Press next. (Write down the password or remember it for later use)
On the BI Applications Administrator User screen, specify the following: Field Username Password Confirm Password Description Specify a username for the Oracle BI Applications Administrator. Specify a password for the Oracle BI Applications Administrator. Confirm the password.
Note these credentials because this user will be used to perform system setups and is the user that is used for communications between the Oracle BI Applications Configuration Manager and ODI. This user has full access privileges in Configuration Manager and access to ODI with the Supervisor role.
On the MDS Schema screen, specify the following: Field Database Type Connect String MDS Schema Username MDS Schema Password Description The type of database that hosts the MDS schema. The only supported database type is Oracle. The connect string used to access the MDS schema. The schema name for the MDS schema. The password for the MDS schema.
On the BI Applications Components Repository Schema screen, specify the following: Field Database Type Description Select the type of database that hosts the Oracle BI Applications Components Repository schema. The only supported database type is Oracle. Specify the connect string used to access the Oracle BI Applications Components Repository schema. Use the format: host:port:service_name Specify the schema name for the Oracle BI Applications Components Repository schema. Specify the password for the Oracle BI Applications Components Repository schema.
Connect String
BIA Components Repository Schema Username BIA Components Repository Schema Password
On the Business Analytics Warehouse Schema screen, specify the following: Field Database Type Connect String Description Specify the type of database that hosts the Business Analytics Warehouse schema. The only supported database type is Oracle. Specify the connect string used to access the Business Analytics Warehouse schema. Use the format: host:port:service_name Specify the schema name for the Business Analytics Warehouse schema. Specify the password for the Business Analytics Warehouse schema.
Business Analytics Warehouse Schema Username Business Analytics Warehouse Schema Password
On the BI Applications ODI Repository Schema screen, specify the following: Field Database Type Connect String Description Specify the type of database that hosts the ODI Repository schema. The only supported database type is Oracle. Specify the connect string used to access the ODI Repository schema. Use the format: host:port:service_name Specify the schema name for the ODI Repository schema. Specify the password for the ODI Repository schema.
Click Configure