OBIA INSTALLATION GUIDE

Prerequisites:

 Before installation of the Oracle BI Applications Oracle Business Intelligence Enterprise Edition
(OBIEE) should be installed on a Windows machine. Instance of OBIEE should be a complete
installation.
 System Requirements:

Software Version:

 DAC and informatica powercenter should be colocated.

 Informatica must be installed before installing DAC.
 Informatica PowerCenter Client Tools and the DAC Client must be co-located on the
same machine.
 PowerCenter Services and the DAC Server must be co-located on the same machine.
 The DAC Client can only be installed on Windows.
 The correct version of the JDK is installed by the DAC installer (Supporting Version).

Note:

DAC produces parameter files that are used by Informatica. If an execution plan fails in DAC
and you want to debug the workflow by running it directly from Informatica, then the parameter
file produced by DAC should be visible to Informatica. This is one reason for the requirement to
co-locate the DAC and Informatica components as stated above.

 The DAC Client uses the Informatica pmrep and pmcmd command line programs when
communicating with Informatica PowerCenter. The installation of PowerCenter Client
Tools provides the pmrep executable file. The installation of PowerCenter Services
provides the pmcmd executable file. The DAC installer performs post-install
configuration tasks related to the pmrep and pmcmd executable files.
  Hardware Requirements:

 Operating System:

 Create Databases.
 Install Database Connectivity Software
 Create ODBC Database Connections
 Set Environment Variables
 How to Install the Java JDK
 Download Hibernate Libraries

Create Databases:

Before you install Oracle Business Intelligence Applications and Informatica

PowerCenter, use your target database tool to create database instances to hold the
following:

 The DAC metadata repository.

 The Informatica repository.
 The PowerCenter domain configuration.
 The Oracle Business Analytics Warehouse.

NOTE: The Informatica and DAC repositories are not supported on DB2-390 or Teradata databases. If
your source or Oracle Business Analytics Warehouse database is DB2-390, or your Oracle Business
Analytics Warehouse database is Teradata, you need to use a DB2-UDB, MS SQL Server, or Oracle
database for both the DAC repository
and the Informatica repository.

You can store both the DAC metadata repository and the Oracle Business Analytics
Warehouse in separate databases, or in the same database.

Note: Make sure that the Oracle Business Analytics Warehouse instance is granted
the SSE_ROLE.

How to Create the SSE Role:

To create the SSE Role for the Oracle Business Analytics Warehouse database:

 Create a database role named SSE_ROLE (SSEROLE for DB2 390 databases). Assign this role to
the database user. For instructions on creating roles, see the documentation provided with your
database.

Note the following:

For an Oracle database, when you create the SSE_ROLE role, you need to grant the
following privileges:

- CONNECT
- RESOURCE

For an Oracle database, if the DAC repository and the Informatica repository are stored in a different
database to the data warehouse database, the SSE_ROLE must have the following additional privileges:

- READ
- WRITE
- UPDATE
- DELETE
- GRANT

If you are using a Teradata database, you do not need to create the SSE role. If you are using a DB2 390
database, you can use an alternative SSE role name to SSEROLE if required. To specify a different role
name, modify the 'set GRANTEE="SSEROLE"' line in the OracleBI\dwrep\createwtables.bat file.

Install Database Connectivity Software:

NOTE: You must install and configure the appropriate database native connectivity client
software on the machines that will host the Informatica PowerCenter Services and
DAC Server, and DAC Client.

 For Oracle databases, set the NLS_LANG environment variable on the machines where the
Oracle client was installed.

NOTE:

You need to set the NLS_LANG environment variable on each machine that has the Oracle client
installed.

To set the NLS_LANG environment variable for Oracle databases:

1. Determine the NLS_LANG value.

a. In the data warehouse database, run the command

SELECT * FROM V$NLS_PARAMETERS

b. Make a note of the NLS_LANG value, which is in the format

[NLS_LANGUAGE]_[NLS_TERRITORY].[NLS_CHARACTERSET].

For example: American_America.UTF8

2. For Windows:
a. Navigate to Control Panel > System and click the Advanced tab. Click
Environment Variables.

b. In System variables section, click New.

c. In the Variable Name field, enter NLS_LANG.

d. In the Variable Value field, enter the NLS_LANG value that was returned in
Step 1.

The format for the NLS_LANG value should be

[NLS_LANGUAGE]_[NLS_ TERRITORY].[NLS_CHARACTERSET].

For example: American_America.UTF8.

Note: The NLS_LANG character set should reflect the setting of the operating system character set of
the client. For example, if the database character set is AL32UTF8 and the client is running on a
Windows operating system, then you should not set AL32UTF8 as the client character set in the
NLS_LANG parameter because there are no UTF-8 WIN32 clients. Instead, the NLS_LANG setting
should reflect the code page of the client.
For example, on an English Windows client, the code page is 1252. An appropriate setting for
NLS_LANG is AMERICAN_AMERICA.WE8MSWIN1252.

Setting NLS_LANG correctly allows proper conversion from the client operating system character set to
the database character set. When these settings are the same, Oracle assumes that the data being sent or
received is encoded in the same character set as the database character set, so character set validation or
conversion may not be performed. This can lead to corrupt data if the client code page and the database
character set are different and conversions are necessary.

3. For UNIX and Linux, set the variable as shown below:

setenv NLS_LANG <NLS_LANG>

For example: setenv NLS_LANG American_America.UTF8.

NOTE: If your data is 7-bit or 8-bit ASCII and the Integration Service is running on UNIX or Linux, then set
NLS_LANG <NLS_LANGUAGE>_<NLS_TERRITORY>.WE8ISO8859P1

Setting the DB2CODEPAGE Environment Variable for DB2 Databases: Follow this procedure to set the
DB2CODEPAGE environment variable for DB2 databases on machines that have the DB2 client installed.

To set the DB2CODEPAGE environment variable for DB2 databases:

1. Determine the DB2CODEPAGE value.

a. Connect to the Source database, using the following command:

SELECT CODEPAGE FROM SYSCAT.DATATYPES WHERE TYPENAME = 'VARCHAR'

b. Make a note of the result.

For example: 1208

2. For Windows:
a. Navigate to Control Panel > System and click the Advanced tab. Click
Environment Variables.

b. In System variables section, click New.

c. In the Variable Name field, DB2CODEPAGE.
d. In the Variable Value field, enter the value that was returned in Step 1.

3. For UNIX or Linux, set the variable as shown below:

setenv DB2CODEPAGE <DB2CODEPAGE value>

For example: setenv 1208.

Create ODBC Database Connections:

The DAC Client uses an ODBC connection to create and alter tables in the Oracle Business Analytics Warehouse.
Create an ODBC connection to the Oracle Business Analytics Warehouse database on the machine that hosts the
DAC Client:
NOTE:
If your source system is Siebel CRM, you must create an ODBC connection to the OLTP (source) database on
the machine where you will install Oracle Business Intelligence Applications software. This ODBC connection will
be used by the ddlimp utility.

For the ODBC connections to - Oracle databases, you must use the Oracle Merant ODBC Driver that is installed
with the Oracle Business Intelligence Applications installer. For all other databases, you should use ODBC drivers
supplied by your database vendor.

To create ODBC connections for DB2 databases:

1. Using the DB2 Client Configuration Assistant, create a database connection to the Oracle
Business Analytics Warehouse database on the machine that will host the DAC Client. If your
source system is Siebel CRM, also create an ODBC connection to the transactional database on
the machine where you will run the Oracle Business Intelligence Applications installer.

Note: If you use the DB2 Client Configuration Assistant to create database connections, you can omit step 2,
because the DB2 Client Configuration Assistant automatically creates System DSNs (default behavior).

2. If necessary, on Windows, in the System DSN tab of the ODBC Data Source Administrator, create
an ODBC connection to the Oracle Business Analytics Warehouse (and, if your source system is
Siebel CRM, to the transactional database) using an ODBC driver.

3. Test the connections to make sure they work.

To create ODBC connections for Oracle databases:

Note: You must use the Oracle Merant ODBC driver to create the ODBC connections. The Oracle Merant ODBC
driver is installed by the Oracle Business Intelligence Applications installer. Therefore, you will need to create the
ODBC connections after you have run the Oracle Business Intelligence Applications installer and have installed
the DAC Client.

1. On the machine that will host the DAC Client, use the System DSN tab of the ODBC Data Source
Administrator to create an ODBC connection to the Oracle Business Analytics Warehouse
database using the Oracle Merant ODBC driver that is supplied with Oracle Business Intelligence
Applications.

For example, you might create a database connection called Connect_to_OLAP.

2. (If your source system is Siebel CRM) In Windows, in the System DSN tab of the ODBC Data
Source Administrator, create an ODBC connection to the Siebel transactional database using the
Oracle Merant Closed driver.

3. Test the connections to make sure they work.

To create ODBC connections for SQL Server databases:

 1. In Windows, in the System DSN tab of the ODBC Data Source Administrator,create the
following:

a. An ODBC connection to the Oracle Business Analytics Warehouse database on

the machine that will host the DAC Client.

b. (If your source system is Siebel CRM) an ODBC connection to the transactional database
on the machine where you will run the Oracle Business Intelligence Applications
installer.

NOTE: Select SQL Server as the ODBC driver.

2. Test the connections to make sure they work

Note: When you use the ODBC Data Source Administrator to create a database
connection, make sure that you select the SQL Server authentication option using a
login ID and password entered by the user.

To create ODBC connections for Teradata databases:

1. On the Windows machine that will host the DAC Client, in the System DSN tab of the ODBC Data
Source Administrator, create an ODBC connection to the Oracle Business Analytics Warehouse
Teradata database.

2. Set the following parameters:

Field=Enter
Date Format=AAA
Session Mode=ANSI
No Scan=Yes

3. For Unicode environments, in the Teradata ODBC Driver Advanced Options

dialog, set the Character Set parameter to UTF8.

How to Install the Java JDK:

NOTE: The DAC Client and DAC Server require Java JDK. Install Java JDK on the machines that will host the
DAC Client and DAC Server. On Windows, you must install JDK with no spaces in the directory path.

This step can be optional or mandatory, depending on where you want to install the DAC server and the
DAC client. Java SDK must be installed on the machines where the DAC server or DAC client are installed. If a
machine has the Oracle Business Intelligence infrastructure installed, the Java SDK will already be installed on that
machine.

1. Download and install the Java JDK for your operating system(s) from a website that provides
Java JDK downloads (for example, the Sun or IBM web site). You must download and install
the Java JDK for either 32 bit or 64 bit depending on your operating system.
NOTE:

On Windows, make sure that there are no spaces in the JDK directory path. If there are spaces in the
directory path, the DAC will not start (the \OracleBI\DAC\startclient.bat file will fail).

Download Hibernate Libraries:

To run the DAC Client or DAC Server, you need to have libraries from an open source software product
called Hibernate. Hibernate libraries are not installed as part of Oracle Business Intelligence Applications
7.9.x., but have to be downloaded from the Hibernate Web site.

Oracle recommends that you download Hibernate Core Package Version 3.2.x GA or later. Newer
versions of Hibernate Core Package 3.2 are now generally available (for example, Hibernate Core
Package Version 3.2.5 GA). DAC is supported on the libraries of these versions also. You can download
Hibernate Core Package from (http://www.hibernate.org.)

Oracle BI Application Installer:

When you run the Oracle Business Intelligence Applications Installation Wizard, the Oracle Business
Intelligence Applications files are installed into the existing Oracle Business Intelligence infrastructure
directory (for example, <DRIVE>:\OracleBI\).

Note: If you have a previous version of Oracle Business Intelligence Applications installed, you must
uninstall this version before you run the installer for Oracle Business Intelligence Applications Version
7.9.5. If you do not uninstall the old version, some Version 7.9.5directories will not be correctly installed.
(Make a back-up of your RPD, presentation catalog, and DAC and dwrep directories before you uninstall
the old version.)

To install Oracle Business Intelligence Applications on Windows:

 Access the installation files on the installation CD-ROM, and then run the program
setup.exe to display the Welcome page.
Note: To run the installer in console (or text) mode, run the command setup.exe -console. You
do not see following dialogue screens in console installation mode. Instead, you enter input as
plain text in the terminal window when prompted.

 Click Next to display the Oracle Business Intelligence infrastructure and Java SDK
directory location page.
  Enter or browse for the location for the Oracle Business Intelligence infrastructure (for
example, <DRIVE>:\OracleBI\), the Oracle Business Intelligence infrastructure data (for
example, <DRIVE> :\ OracleBIData\), and the Java SDK (for example,
<DRIVE>:\jdk1.5).

 Click Next to display the Select Oracle Business Intelligence Applications page.

 At the Select Oracle Business Intelligence Applications page, select the applications that
you want to install, then click Next.

To determine the applications you should install for the Oracle Business
Intelligence Applications licenses you have purchased, see the spreadsheet
entitled '2-Installer Options' in the Oracle Business Intelligence Applications
Fusion Edition Licensing and Packaging Guide. This guide is part of the Oracle
Business Intelligence Media Pack.

Once you have installed applications, you can deploy them for one or more source
systems selectively when you create the DAC metadata repository in a later step

 If you selected more than one application on the Select Oracle Business Intelligence
Applications page, click Next at the informational page.
  At the summary page, review the summary information and click Next to start the
installation.

The installer installs the Oracle Business Intelligence Applications directories and
files in the Oracle Business Intelligence infrastructure installation (for example,
<DRIVE>:\OracleBI\), and installs the Oracle BI Repository file and Presentation
Catalog.

Note: Even when the progress bar on the installer reports 100%
Complete, you must wait until the Finish button is displayed.

 Click Finish.

Tip: Look in the <DRIVE>:\OracleBI\Document\version_apps.txt

file in the Oracle Business Intelligence infrastructure directory to
check that you have installed the correct version of Oracle Business
Intelligence Applications.

When the installation is complete, verify that the following directories or files are
installed:

 The dwrep\DAC_metadata folder.

 The dwrep folder.
 The Oracle Business Intelligence Applications repository file named
 EnterpriseBusinessAnalytics.rpd in the OracleBI\server\Repository folder.
 The Presentation Catalog in the OracleBIData\web\catalog folder. The Presentation
Catalog is provided as a zipped file named EnterpriseBusinessAnalytics.zip and will need
to be unzipped before it can be used.

- Language files (for the languages available for Oracle BI Applications) in

OracleBIData\web\res folder.
- Seed Data folder containing localization files.
- Upgrade folder containing repository files from previous versions of Oracle BI
Application and Siebel Analytics Application releases.

Notes

 The credentials required to log into the EnterpriseBusinessAnalytics.rpd file using

the Oracle Business Intelligence Administration Tool are:

- Username: Administrator
- Password: SADMIN

 You should change the default password. Use the Oracle Business Intelligence Administration
Tool to do so.