Vous êtes sur la page 1sur 117

PS1 INSTALLATION on Linux Server :

Index :
1. BI Apps 11.1.1.7.1 Installation Life Cycle
2. Downloading Required Softwares
3. Linux Box Kernel Parameters Setup
4. Java Installation
5. Oracle 11.2.0.3 Database Server Installation and Setup
6. Schema Creation for OBIEE and ODI using RCU
7. OBIEE 11.1.1.7.0 Installation
8. Weblogic Server Upgradation from 10.3.5 to 10.3.6
9. ODI 11.1.1.7.0 Installation
10.
OBIA Schema Creation using RCU
11.
OBIA 11.1.1.7.1 Installation
12.
OFMW Platform Patches
13.
Configuring OBIApps
14.
Installing ODI Studio and Load Plan Generator Plugin
15.
Applying Post-Installation Patches
16.
Performing Post-Installation System Set-Up Tasks
17.
Data Loads and Debugging
18.
Basic Validation of Data

1. BI Apps 11.1.1.7.1 Installation Life Cycle:

Install Oracle
Database
11.2.0.3

Perform Post-Installation System


Set-ups
Apply Post-Installation
Patches

Run OBIEE
RCU

Configure OBIApps

Install OBIEE
11.1.1.7.0
Install ODI 11.1.1.7.0 (JAVA EE
Components & Client too)

Install SOA 11.1.1.7.0


(Optional for IDSP)

2.

Apply OFMW
Patches

Run OBIA
RCU

Install OBIApps
11.1.1.7.1

Download Required Softwares for PS1 Installation :

3.

Linux Box Kernel Parameters Setup:


3.1. The following lines should be appended to the /etc/security/limits.conf file
Ex:oracleuser add the user details as mentioned below
oracle
oracle
oracle
oracle
oracle

soft nproc 2047


hard nproc 16384
soft nofile 4096
hard nofile 65536
soft stack 10240

3.2. Add the following line to the "/etc/pam.d/login" file, if it does not already
exist.
session

required

pam_limits.so

3.3. Disable secure linux by editing the "/etc/selinux/config" file, making sure
the SELINUX flag is set as follows, then reboot the server.
SELINUX=disabled

3.4. The following lines should be appended to the "/etc/sysctl.conf" file


[Depends upon the Linux Versions] as of Redhat release 5 or greater
fs.suid_dumpable = 1
fs.aio-max-nr = 1048576
fs.file-max = 6815744
kernel.shmall = 2097152
kernel.shmmax = 536870912
kernel.shmmni = 4096
# semaphores: semmsl, semmns, semopm, semmni
kernel.sem = 250 32000 100 128
net.ipv4.ip_local_port_range = 9000 65500
net.core.rmem_default=4194304
net.core.rmem_max=4194304
net.core.wmem_default=262144
net.core.wmem_max=1048586
3.5. The current values can be tested using the following command.
/sbin/sysctl -a | grep <param-name>
3.6. Verify the privileges and change permissions according to the user
chown -R oracle:oinstall /u01
chmod -R 775 /u01
3.7. To test Rpms List:
rpm -qa |grep binutils-2.*
rpm -qa |grep compat-libstdc++-33*
rpm -qa |grep compat-libstdc++-33*.i386.rpm
rpm -qa |grep elfutils-libelf*
rpm -qa |grep gcc-4.*
rpm -qa |grep gcc-c++-4.*
rpm -qa |grep glibc-2.*
rpm -qa |grep glibc-common-2.*
rpm -qa |grep glibc-devel-2.*
rpm -qa |grep glibc-headers-2.*
rpm -qa |grep ksh*
rpm -qa |grep libaio-0.*
rpm -qa |grep libaio-devel-0.*
rpm -qa |grep libgomp-4.*
rpm -qa |grep libgcc-4.*
rpm -qa |grep libstdc++-4.*
rpm -qa |grep libstdc++-devel-4.*
rpm -qa |grep make-3.*
rpm -qa |grep sysstat-7.*
rpm -qa |grep unixODBC-2.*
rpm -qa |grep unixODBC-devel-2.*
rpm -qa |grep numactl-devel-*
3.8. Add the below lines in .bashrc and .bash_profile for invoking Oracle and
Informatca server binaries.
# Oracle Settings
TMP=/tmp; export TMP
TMPDIR=$TMP; export TMPDIR
ORACLE_BASE=/u01/app/oracle; export ORACLE_BASE
ORACLE_HOME=$ORACLE_BASE/product/11.2.0/client_1;
ORACLE_HOME
PATH=/usr/sbin:$PATH; export PATH
PATH=$ORACLE_HOME/bin:$PATH; export PATH

export

LD_LIBRARY_PATH=$LD_LIBRARY_PATH:$ORACLE_HOME/lib:/lib:/usr/lib;
export LD_LIBRARY_PATH
CLASSPATH=$ORACLE_HOME/jlib:$ORACLE_HOME/rdbms/jlib; export
CLASSPATH
TNS_ADMIN=$ORACLE_HOME/network/admin;
export TNS_ADMIN
4.

Java installation:
jdk 1.7.0_25 was installed. (Requirement is : jdk 1.7+ version)

5.

Oracle 11.2.0.3 Database Installation and Setup:

6.

Schema Creation for OBIEE and ODI using RCU :

To install Repository Creation Utility (RCU) after you have downloaded the
installation files, unzip them in the same place.

Go to shell prompt and type in:


cd /home/oracle/Softwares/OBIEE/rcuHome/bin/
ls
You will find a rcu batch file. Run it using :
./rcu

This launches the Oracle Repository Creation Utility (RCU) screen.

Create Repository : This enables to create or drop a Repository.

Database Connection Details: Give the specific details like Host Name, Port,
Service Name, User Name, Password and click Next. Note: The role is sysdba.

Provide the Database details as follows :

After clicking Next you will see :

Select Components: Create a New Prefix: The default name is DEV. You can
change it if you want. (We have given: PS1)
Check the Repository Components, Oracle Data Integrator and Oracle
Business Intelligence boxes.

Note down the MDS, ODI, and BIPLATFORM Schema names. (As in our
installation it is PS1_MDS, PS1_BIPLATFORM, PS1_ODI_REPO).
Click Next.

Schema Password : Provide the Schema Passwords: Select the option Same
Schema Password for all Schemas.
Click Next.

Custom Variables: Provide the Supervisor Password and the Work Repository
Password in this page as follows:

You will See a Map Tablespaces page.


Click Next.

Click OK to create the Tablespaces.

Summary: You will see the Summary details for the RCU created.

Click on Create to create the above Table spaces.

Click on OK and then Click on Next.

Completion Summary screen

Click on Close. This is the end of the OBIEE and ODI RCU creation.

7.

OBIEE 11.1.1.7.0 Installation :


To install Oracle BI EE 11g, after you have downloaded the installation files,
unzip them.
Go to shell prompt and type in:
cd /home/oracle/Softwares/OBIEE/bishiphome/Disk1/
ls
You will find a runInstaller file. Run it using the command :
./runInstaller
This launches the Oracle Universal Installer (OUI) as follows:

Welcome: Click Next.

Install Software Updates: Select Skip Software Updates option and then Click
Next.

Select Installation Type: Select Enterprise Install and Click Next.

Prerequisite Check: These are some basic checks that the installer performs
like checking for the Operating System Version, the Service Pack, the
available memory and the disk space.
After the Check is completed, Click Next.

Create New BI System: You can enter any name here like weblogic or
admin or administrator. Enter a Password, and make sure you remember

it, since you will need this to log into the Console, BI EE, Enterprise Manager,
etc.

Enter the details and Click Next.

Specify Installation Location: The Middleware Home is going to be a new


concept for people who have not installed Oracle products before. With this
release, Oracle BI EE integrates more tightly with the Oracle way of installing
products. Every product needs to be installed into an Oracle Home. If you
dont have an Oracle Home, you need to specify a new one. One thing that

you will notice, which is different from other Oracle product installations, is
that you do not get to specify a name for the Oracle Home. A system
generated name is going to be assigned to this location that you specify as
the Oracle Home. For the most part you do not need to concern yourself with
its implications.
We have created a local user u01 and created a directory OBIEE11g
under it. Hence the Oracle Middleware location as /u01/OBIEE11g.
Domain
Home
Location
:
/u01/OBIEE11g/user_projects/domains/bifoundation_domain
Oracle Instance Location : /u01/OBIEE11g/instances/instance1
Oracle Instance Name : instance1
Click on Next.

Configure Components: Select all products on offer here which will install
everything. Click Next.

BIPLATFORM Schema : Fill-in the details as follows:


Connect String: hostname:port:servicename (for example, in our installation
it was 172.16.31.22:1521:odiorcl.fcs-inc.local
BIPLATFORM Schema Username: Enter the BIPLATFORM schema username
(same as during RCU installation).
BIPLATFORM Schema Password: Give the Schema password used earlier
during RCU Installation.

Click Next.

MDS Schema : The above screen will display the Connect String, MDS
Schema Username and MDS Schema Password. The Password is same as
used in the creation of the BIPLATFORM Schema (if you had chosen the Same
Schema Password option earlier during RCU Installation) or else if you have
chose for different Schema Password then give the same.
Click Next.

Configure Ports: Click on Auto Port Configuration. Click Next.

Security Updates: This is optional. Click on Next.


An alert will prompt: Click on Yes and then click on Next.

Summary: This page will give you the Installation Details and Configured
Components.
Save this page(optional/recommended).
Click Install. Now the Installation process starts.

Installation Progress: Once the Installation Progress is completed, it


automatically starts the Configuration Progress which will take some time
(around 40 minutes).

Configuration Progress: Once the Configuration Progress is completed


successfully, you will notice the progress bar at 100%. Every configuration
step shows a status of Success (given by the Tick symbol, as shown above).
Click Next.

Complete: On this last screen, you will see details pertinent to your
installation. Save this summary(Optional/Recommended).
Click Finish.
The Oracle Business Intelligence Home Page will open automatically. No need
to restart the services for the first time. We can see SampleLite was installed
successfully.
This ends the OBIEE 11g Installation.

8. Weblogic Server Upgradation from 10.3.5 to 10.3.6:


Oracle BI Applications requires WebLogic Server 10.3.6. If you installed Oracle BI
EE in Enterprise Install mode, then WebLogic Server 10.3.5 was automatically
installed. You must now upgrade to WebLogic Server 10.3.6. The WebLogic
Upgrade Installer allows you to upgrade to WebLogic Server 10.3.6. The Upgrade
Installer is available on My Oracle Support (https://support.oracle.com). For
instructions on downloading the Upgrade Installer and upgrading to WebLogic
10.3.6, see Oracle Fusion Middleware Getting Started With Installation for Oracle
WebLogic Server 11g Release 1 (10.3.6) > Obtaining the Installation Program >
Upgrade Installer.
8.1

Before You Begin:


Before you begin upgrading your existing WebLogic Server version to
WebLogic 10.3.6.0:
Shut down all WebLogic processes you want to upgrade such as:
o Node Manager
o Admin Server
o All Managed Servers

Download a new version of JDK 1.7+.


Note: A plus sign '+' after the version number indicates that this and its
subsequent versions are supported.

Download this patch set for


(p13529623_1036_Generic.zip)

Oracle

WebLogic

10.3.6.0:

Patch

13529623

/home/oracle/Softwares/weblogic_10.3.6/ p13529623_1036_Generic.zip

Unzip the file in a temporary location and confirm the extracted contains this file:
wls1036_upgrade_generic.jar

8.2

Installing and Verifying the JDK Version


In order to meet the MTRs for the requisite JDK, if you need to install a new JDK you
should install it to a different location. Otherwise you should completely uninstall
the existing JDK and replace it with the newer version.
To install and verify the level of an existing JDK, type in the following in the shell
prompt:
$java version

8.3

Running OUI to Upgrade an Existing WebLogic Server to 10.3.6


This section describes running the Oracle Universal Installer (OUI) to upgrade an
existing WebLogic Server to 10.3.6.
1. Locate this patchset from the temporary location where you downloaded it
in Section 8.1, "Before You Begin":
wls1036_upgrade_generic.jar
2. Open a Linux Terminal and run this command from the shell prompt:
$java -jar wls1036_upgrade_generic.jar
Upon execution, the installer starts preparing the OUI install program.

3. On Choose Middleware Home Directory, select the existing Middleware home


you wish to upgrade.
4. Click the Next button.

5. On Register for Security Updates, the Email address and/or the My Oracle
Support Password fields as applicable.
6. Click the Next button.

7. On Choose Products and Components, verify the components.


Note: The OUI installer automatically selects the Oracle Coherence
component. You can choose to select or deselect this component,
keeping in mind that this server type has not yet been verified with
Oracle JD Edwards EnterpriseOne.
8. Click the Next button.

9. On Choose Product Installation Directories, verify the directory locations for


the previously selected products and components.
Note: A new version of Oracle Coherence_3.7 will be installed.
10. Click the Next button.
OUI begins copying the files and performs the upgrade.

11. On Installation Complete, click the check box for Run Quickstart to
continue with the upgrade of the Oracle WebLogic domains.
12. Click the Done button to complete the installation and exit OUI.
The Quickstart configuration screen appears.

13. On the QuickStart links panel, select this link:


Upgrade domains to version 10.3.6.
An Upgrade Wizard is launched.

14. On the Welcome panel of the Upgrade Wizard, review and complete the tasks
listed in the Prerequisites section of the above screen.
15. When the Prerequisite tasks are complete, click the Next button.

16. On Select WebLogic Version, select this radio button: 9.0 or higher
17. Click the Next button.
18. On
Select
a
Domain
to
Upgrade,
drill
down
through
the Oracle\Middleware\user_projects\domains directory structure and select
the Oracle JD Edwards domain. For example: E1_Apps
19. Click the Next button.

20. On Inspect Domain, review the upgrade configuration selections.


21. Click the Next button.

22. On Select Upgrade Options, select this check box:


Back up current domain (recommended)
Caution: The wizard advises you that if you choose the check box
or Add log files to backup zip, the resultant zip file can be
extremely large.

23. On Domain Backup, review the message.


24. Click the Next button.
25. On Select Directory for Domain Backup, you can accept or change location
and filename of the backup zip file.
26. The wizard shows the progress of the domain backup.
27. When the backup is complete, click the Next button.

28. On Finalize Domain Upgrade, review the message.


29. Click the Next button to begin the Upgrade.

30. On Upgrade Complete, click the Done button to exit OUI.


Note: As a result of this domain upgrade, you do not need to
individually upgrade any Managed Server.
31. Start the WebLogic NodeManager.
32. Start the WebLogic Administration Console.
33. Start the existing Managed Server such as the Oracle JD Edwards
EnterpriseOne HTML server.
34. Test and verify the upgrade.

9.

ODI 11.1.1.7.0 Installation :

Hardware and System Configuration Requirements for Oracle Data Integrator


:

Disk Space: 5GB or more.


Available Memory: 2GB or more.
Database Requirements for Oracle Data Integrator:
Master Repository: 60MB of Storage Space
Work Repository: 80MB of Storage Space

Download the ODI software from the below location :


http://www.oracle.com/technetwork/middleware/bi-enterpriseedition/downloads/bus-intelligence-applications-1942275.html

https://edelivery.oracle.com/EPD?Download/get_form?
egroup_aru_number=16339887

Unzip the softwares into a single folder and go to Disk1 and type in the shell
prompt :
ls
You will see a runInstaller file. Run this file using the command:
./runInstaller

Welcome: This launches the Welcome Screen automatically.

Click Next.

Install Software Update: Select Skip Software Updates and Click Next.

Select Installation Type: We have selected all the 2 types of Installations..


Click Next.

Prerequisite Checks: The above screen checks for the prerequisites like the
OS certification details, kernel parameters, the physical memory, etc. and
after completion returns a screen with progress shown as follows:

Click Next.

Installation Location: Specify the Oracle Middleware Home as created during


OBIEE 11g installation. The Oracle Home will be created under the Oracle
Middleware Home Location with the given name.
Click Next.

Application Server: By default the WebLogic Server is selected. Click Next.

Repository Configuration: We selected Configure Repositories. Click Next.

Master Repository: These fields are automatically filled in accordance with


those created during RCU creation for ODI. Click Next.

Supervisor Details: Provide a password for the ODI Username and note it
down for future reference.
Click Next.

Work Repository Details: Select the Work Repository Details (for our
installation it is WORKREP).
Click Next.

Specify Agent Details: Give the Agent Name: odiagent


Specify the Agent Port: any number in the range 1024-65535 and should not
be used by any other process.
Click Next.

Installation Summary: Save the Response file (Optional/Recommended).


Click Install.

Installation Progress: The Installation Progress follows as shown above.

Configuration Progress: This starts automatically after the Installation


Progress is completed. When the ODI Configuration is 100%, Click on Next.

Installation Completed: The Installation and the Configuration details are


shown as above. Save them for future reference. Click on Finish.
The ODI 11g Installation has ended.

10.

OBIA Schema Creation Using RCU:

Download the ODI software from the below location :


http://www.oracle.com/technetwork/middleware/bi-enterpriseedition/downloads/bus-intelligence-applications-1942275.html

https://edelivery.oracle.com/EPD?Download/get_form?
egroup_aru_number=16339887

Unzip the Software into a folder and go into the shell prompt and type :
cd home/oracle/Softwares/OBIAPS1_11.1.7.1/OBIAPS1_RCU/bin
ls
You will find a rcu file. Run it using the command:
./rcu
As shown below in the screen :

The Repository Creation Utility window launches automatically.

Welcome: Click Next.

Create Repository: Select the Create option and Click Next.

Database Connection Details: Specify the Database Connection details as


used earlier during RCU creation for OBIEE and ODI 11g. They are the same
details. Click Next.

Click OK.

Select Components: We have used the same prefix PS1 as was used during
the RCU Creation for OBIEE and ODI 11g. Check all the boxes. And note down
the Schema names and Click Next.

Click OK.

Schema Passwords: We have used the Same Password Option. You can
choose different password even. Click Next.

Custom Variables: Here we need to enter the value/ the path where the given
Components are installed.

Click Next.

Map Tablespaces: Click Next.

Click OK to create Tablespaces.

Click OK.

Summary: This screen shows the summary of the Database Connection


details.
Click Create.

Click Ok. The RCU is created for OBIApps 11g.


Completion Summary: Detailed Summary of the RCU created and location of
the logfile are provided in this page. Click Close.
This ends the RCU Creation for OBIApps 11g.

11. OBIApps 11.1.1.7.1 Installation:


Download the ODI software from the below location :
http://www.oracle.com/technetwork/middleware/bi-enterpriseedition/downloads/bus-intelligence-applications-1942275.html

https://edelivery.oracle.com/EPD?Download/get_form?
egroup_aru_number=16339887

Unzip the downloaded software.


Through the Shell Prompt goto the bishiphome folder and then navigate to
Disk1 under bishiphome folder as follows:
cd
/home/oracle/Softwares/OBIAPS1_11.1.1.7.1/OBIAPS1/biappsshiphome/Disk1
ls
You will see a runInstaller file. Run it using the Command:
./runInstaller
The Oracle Business Analytics Applications Suite launches automatically.

Click Next.

Prerequisite Checks: Checks like the OS certification , the kernel parameters,


the physical memory, etc. are done. Once these checks are completed you
get a screen as below:

The above Screen shows 100% prerequisite check successful. Click Next.

Installation Location: The same path as given earlier is provided here by


default. Accordingly the Oracle home will be created under the Oracle
Middleware Home location with the given name.
Click Next.

Summary: Software only Installation is done here and hence the Summary is
shown. Save the details for future reference. Click Install to begin the
OBIApps 11g Installation process.

Installation Progress: The above Screen shows the Installation screen. Once it
gets completed we see the Screen below:

Click Next.

12.

Complete: Click Save for future referencing of the Installation details.


Click Finish.
This ends the OBIApps 11.1.1.7.1 Installation.

OFMW Platform Patches:

You must apply Fusion Middleware Platform Patches. The Patches are
available for download as part of the Oracle Business Intelligence
Applications 11.1.1.7.1 media pack. You will run a script to apply the patches.
The
script
is
a
Perl
Script
and
is
available
in
<BI_Oracle_Home>/biapps/tools/bin/APPLY_PATCHES.pl. (In our installation
the
Perl
file
is
in
/u01/OBIEE11g/Oracle_BI1/biapps/tools/bin/APPLY_PATCHES.pl).
The Perl you will run to apply the patches requires a parameter input file
(apply_patches_import.txt). In this procedure, before you run the Perl script,
you will update the parameter input file to reflect the appropriate directory
paths.
To apply Platform Patches:
1. If Oracle BI EE was installed in Enterprise Install mode, then shut down WebLogic
Administration Server, Managed Server, and Node Manager. Shutdown BI
processes using Oracle Process Manager and Notification Server (OPMN). If you
installed Oracle BI EE in Software Only mode, then skip this step.
2. Download "Oracle Fusion Middleware Platform Patches for Oracle Business
Analytics Applications Suite" from the Oracle Business Intelligence Applications
11.1.1.7.1 media pack on Oracle Software Delivery Cloud, as follows:
Download the following three parts from the Oracle Business Intelligence
Applications 11.1.1.7.1 Media Pack and unzip them into the same directory
location:
o Oracle Fusion Middleware Platform Patches for Oracle Business Intelligence
Applications (Part 1 of 2) - V38107-01_1of2.zip
o Oracle Fusion Middleware Platform Patches for Oracle Business Intelligence
Applications (Part 2 of 2) - V38107-01_2of2.zip

o Oracle Fusion Middleware Platform Patches for Oracle Business Intelligence


Applications for <OS> - V38105-01.zip (for Linux X86-64-bit).
3. Extract the ZIP file or files into a Patch Home directory, as follows:
Extract the contents of the three downloaded zip files containing the patches into
the same directory, for example, here we have downloaded the files into
/home/oracle/Softwares/OFM_Pathces_for_OBIA.
Note:
The
directory
structure
of
the
extracted
contents
is
not
patches4fa/dist/ps6rc3. The patches are contained in folders: biappsshiphome, odi,
soa, weblogic and oracle_common. You do not have to unzip the individual patches.
4. Update the parameter input file (apply_patches_import.txt) to reflect the paths as
specified in the text file:
o Create a writable directory where logs and temporary patch files will be
stored.
In
the
apply_patches_import.txt
file,
you
will
set
the WORKDIR=variable to point to the path for this directory.
o Open
apply_patches_import.txt,
which
<BI_Oracle_Home>/biapps/tools/bin directory.

is

located

in

the

o Specify the following directory paths:


Directory

Path

Path for PS1 Installation

JAVA_HOME

Path of the JDK you /usr/local/java/jdk1.7.0_25


installed
for
your
platform.

INVENTORY_LOC

Path
of
Oracle\Inventory
directory.

ORACLE_HOME

Path of the Oracle Home /u01/OBIEE11g/Oracle_BI1


for BI directory.

MW_HOME

Path
of
the
Middleware
directory.

the /u01/app/oraInventory

Oracle /u01/OBIEE11g
Home

COMMON_ORACLE_H Path
of
the /u01/OBIEE11g/oracle_common
OME
oracle_common
directory, which is under
the Middleware Home
directory.
WL_HOME

Path
of
the
Oracle /u01/OBIEE11g/wlserver_10.3
WebLogic Server Home
directory.

SOA_HOME

Path of SOA

ODI_HOME

Path of Oracle
Integrator.

WORKDIR

Path
of
a
writable /u01/OBIEE11g/tmp/work
directory where logs and
temporary patch files are
stored.

PATCH_ROOT_DIR

Path
of
directory.

/u01/OBIEE11g/Oracle_SOA1

the

Data /u01/OBIEE11g/Oracle_ODI1

patch /
home/oracle/Softwares/OFM_Pathces_fo
r_OBIA

5. Run the following command to apply the patch:


$ perl APPLY_PATCHES.pl <PARAM_INPUT_FILE_PATH>

For example:
perl
<BI_Oracle_Home>/biapps/tools/bin/APPLY_PATCHES.pl
perl<BI_Oracle_Home>/biapps/tools/bin/apply_patches_import.txt
Note: This script can be run from any location if Perl is set in the path variable. If
Perl is not set in the path variable, run the script from the following location:
<ORACLE_HOME>/perl/bin>
Confirm that all patches have been applied successfully by reviewing the following
log files in the directory specified by WORDIR:
a. final_patching_report.log (summary of patch application)
b. biappshiphome_generic_patches.log
c. biappshiphome_<OS specific>_patches.log
d. odi_generic_patches.log
e. oracle_common_generic_patches.log
f. soa_generic_patches.log (Note: if SOA is not installed, then patch log will
indicate that patch application has failed - this is expected).
g. weblogic_patching.log
6. If Oracle BI EE was installed in Enterprise Install Mode, then start WLS Admin
Server, Managed Server and Node Manager. Start the BI processes using OPMN.
If you installed Oracle BI EE in Software Only mode, then skip this step.

13.

Configuring Oracle BI Applications:

You run the configApps.bat or configApps.sh file to extend the BI Domain to deploy
Oracle BI Applications and to configure the components.
During this phase, the following key configurations occur:

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. For our
PS1_Installation we have the file in /u01/OBIEE11g/OracleBI1/bin/configApps.sh
To configure components by running the configApps.bat or configApps.sh file:
1. Before running the configApps process, ensure that WLS Admin Server, Node
Manager, and BI Services are running.
2. Start the configuration utility from the bin directory in the BI_Oracle_Home (default
folder name is Oracle_BI1), based on the operating system:
UNIX commands:
cd / u01/OBIEE11g/OracleBI1/bin/
./configApps.sh

3. On the Welcome screen, click Next.

4. On the Prerequisite Checks screen, after the prerequisite checks conclude with no
errors, click Next.
If an error message appears, fix the error and then click Retry to run the
prerequisite check again (recommended). Repeat this until all prerequisite checks
conclude with no errors. To stop the configuration process while you fix a
prerequisite error, click Abort. To ignore an error or warning message, and
continue with the configuration process, click Continue (not recommended).
Note: The configuration might not function normally if you continue without
resolving the issue that caused an error or warning message during the
prerequisite checks.

5. On the Extend BI Domain screen, specify the following:


Field

Description

Host Name The host name of the computer on which the WebLogic Server domain
exists. This field is read-only.
Port

Specify the port number over which the WebLogic Server domain
communicates. The default is 7001.

User Name Specify the user name for logging into the WebLogic Server.
User
Password
Click Next.

Specify the password for logging into the WebLogic Server.

6. The Specify Installation Location screen displays the following information.


Field

Description

Middleware Specify the path to the directory for an existing Oracle Middleware Home
Home
where Oracle BI EE has been installed.
The value in this field is read-only.
Oracle
Home

The Oracle Home for BI, which is the location where Oracle BI EE, Oracle BI
Applications, and Operational Planning Applications files are installed.
The value in this field is read-only.

WebLogic
Server
Home

The directory name for the WebLogic Server.


The value in this field is read-only and is the host name you specified in
the Middleware Home field.

Domain
Home

The home directory for the domain associated with the Oracle Business
Intelligence system. The value in this field is read-only.

Instance
Home

The path to the Oracle Instance directory.


The installer installs component configuration files and runtime processes
in the Oracle Instance directory. Runtime components write to this directory
only. The directory that you identify for the Oracle Instance can be located
anywhere on your system, and does not need to be inside the Oracle
Middleware Home.
The value in this field is read-only.

Instance
Name

The name of the Oracle Business Intelligence instance. By default, the


location is based on the value in the Instance Home field. This directory is
commonly referred to as ORACLE_INSTANCE.
The value in this field is read-only.

Click Next.

7. On the Configure Components screen, to deploy Oracle BI Applications, select:

BI Application Components

8. On the RPD Encryption Password screen, specify the following:

Field

Description

RPD Password

Specify the password used to encrypt the RPD.

Confirm RPD Password

Confirm the password used to encrypt the RPD.

Click Next

9. On the BI Applications Administrator User screen, specify the following:


Field

Description

Username

Specify a user name for the Oracle BI Applications Administrator.


Note: Do not enter "Administrator" or "Supervisor" in upper case, lower
case, or mixed case letters. These user names are reserved.

Password

Specify a password for the Oracle BI Applications Administrator.

Confirm
Password

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.
Click Next.

10. On the MDS Schema screen, specify the following:


Field

Description

Database Type

The type of database that hosts the MDS schema. The only
supported database type is Oracle.

Connect String

The connect string used to access the MDS schema.

MDS
Schema The schema name for the MDS schema.
Username

MDS
Schema The password for the MDS schema.
Password

Note: The values for user name and password must match the values you entered
when you ran the Fusion Middleware RCU in Section 3.2.2, "Running Fusion
Middleware RCU."
Click Next.

11. On the BI Applications Components Repository Schema screen, specify the


following:
Field

Description

Database Type

Select the type of database that hosts the


Applications Components Repository schema.
supported database type is Oracle.

Connect String

Specify the connect string used to access the Oracle BI


Applications Components Repository schema.
Use the format:
host:port:service_name

Oracle BI
The only

BIA
Components Specify the schema name for the Oracle BI Applications
Repository
Schema Components Repository schema.
Username
BIA
Components Specify the password for the Oracle BI Applications Components
Repository
Schema Repository schema.
Password
Click Next.

12. On the Business Analytics Warehouse Schema screen, specify the following:
Field

Description

Database Type

Specify the type of database that hosts the Business Analytics


Warehouse schema. The only supported database type is
Oracle.

Connect String

Specify the connect string used to access the Business


Analytics Warehouse schema.
Use the format:
host:port:service_name

Business
Warehouse
Username

Analytics Specify the schema


Schema Warehouse schema.

Business
Warehouse
Password

Analytics Specify the password for the Business Analytics Warehouse


Schema schema.

Click Next.

name

for

the

Business

Analytics

13. On the BI Applications ODI Repository Schema screen, specify the following:
Field

Description

Database Type

Specify the type of database that hosts the ODI Repository


schema. The only supported database type is Oracle.

Connect String

Specify the connect string used to access the ODI Repository


schema.
Use the format:
host:port:service_name

ODI
Repository Specify the schema name for the ODI Repository schema.
Schema Username
ODI
Repository Specify the password for the ODI Repository schema.
Schema Password
Click Next.

14. On the Configure Ports screen, specify the following:


Field

Description

Auto
Port Select this option if you want Oracle Business Analytics Applications
Configuration
Suite installer to configure the ports for you.
Specify
Ports
Using
Configuration
File

Select this option to use a configuration file to configure the ports.


Optionally, click Browse to specify a configuration file location.
Click View/Edit File to view or edit the file.
A sample configuration file named staticport.ini is provided. The file is
stored in the Disk1\stage\Response directory of the Business Analytics
Applications Suite installer. You can edit this file to specify the
configuration settings for your environment.

15. On the Summary screen, click Save to save the settings for this configuration in a
response file (optional), and then click Configure to start the configuration process.
16. In the Configuration Progress screen, you can monitor the progress of the software
configuration and respond to errors, if any occur.
If a configuration task fails, an error message appears. To retry the task,
click Retry. To continue with the next task, click Continue (not recommended). To
stop the installation and configuration process entirely, click Abort.
After the configuration concludes without any errors, click Next.

17. On the Complete screen, click Save to save the settings for this installation in a
response file (optional), and then click Finish to exit the Oracle Business
Intelligence Configuration Assistant.

14.

Installing ODI Studio and Load Plan Generator Plug-In:

ODI Studio with the Oracle BI Applications Load Plan Generator Plug-in is typically
installed on developer machines. The supported operating systems for ODI Studio is
Linux 32-bit.
ODI Studio is a desktop client that enables you to design and manage the ODI
Repository.
To install ODI Studio and the Load Plan Generator Plug-in, perform the following
procedures in the order they appear:

Section 14.1, "Installing ODI Studio"

Section 14.2, "Generating Security Files for ODI Studio"

Section 14.3, "Installing Oracle BI Applications Load Plan Generator Plug-In"

14.1
Installing ODI Studio
You install ODI Studio using the ODI installer.
Note: On the Select Installation Type screen, you must select Developer
Installation as the installation type and both options under Developer Installation, that
is, ODI Studio (with local agent) and ODI SDK.
For instructions on installing ODI Studio, see Oracle Fusion Middleware Installation Guide
for Oracle Data Integrator.
14.2 Generating Security Files for ODI Studio
The ODI Repository is configured for external authentication against WebLogic Server's
embedded LDAP server. System administrators must generate the appropriate security
files for authentication as specified below, and provide these to developers who have
installed ODI Studio on their machines.

Note: You must perform these steps even if ODI Studio has been installed on the
machine where Oracle Home for BI resides.
To generate security files for ODI Studio:
1. Execute the wlst.sh script:
ORACLE_HOME/common/bin/wlst.sh
<MW_Home>/Oracle_BI1/bifoundation/install/createJPSArtifactsODI.py embedded
--ADMIN_USER_NAME
<Administrator>
--DOMAIN_HOSTNAME
<Hostname>
--DOMAIN_PORT
7001
--DOMAIN_HOME_PATH
<MW
Home>/user_projects/domains/bifoundation_domain
In our PS1_Installation the above is :
/u01/OBIEE11g/Oracle_BI1/common/bin/wlst.sh
/u01/OBIEE11g/Oracle_BI1/bifoundation/install/createJPSArtifactsODI.py embedded
ADMIN_USER_NAME
weblogicDOMAIN_HOSTNAME
FCSHYDSR0022
DOMAIN_PORT 7001DOMAIN_HOME_PATH
/u01/OBIEE11g/user_projects/domains/bifoundation_domain
Where ADMIN_USER_NAME is the WebLogic Server administrator user i.e . by
default taken as weblogic
The JPS configuration file and credential wallet are created at location:
<MW_Home>/user_projects/domains/bifoundation_domain/odi-clientconfig/embedded
i.e,
/u01/OBIEE11g/user_projects/domains/bifoundation_domain/odi-clientconfig/embedded
2. Copy cwallet.sso and jps-config-jse.xml from:
<MW_Home>/user_projects/domains/bifoundation_domain/odi-clientconfig/embedded
i.e.,
/u01/OBIEE11g/user_projects/domains/bifoundation_domain/odi-clientconfig/embedded
To:
<ODI_Home>/oracledi/client/odi/bin
i.e., /u01/OBIEE11g/Oracle_ODI1/oracledi/client/odi/bin
3. Edit <ODI_Home>/oracledi/client/odi/bin/odi.conf
i.e., /u01/OBIEE11g/Oracle_ODI1/oracledi/client/odi/bin
by updating the JPS configuration file name as follows:
AddVMOption -Doracle.security.jps.config=./jps-config-jse.xml
If you do not successfully complete these steps, you will receive the following error
message: "ODI-10188: Error while login from OPSS../jps-config.xml (No such file or
directory)."
14.3 Installing Oracle BI Applications Load Plan Generator Plug-In
The Oracle BI Applications Load Plan Generator Plug-in is delivered as a ZIP file
containing a set of jar files and a Readme file with instructions on how and where to
deploy the jar files. System administrators must provide the ZIP file to developers as
needed. The ZIP file is installed in the Oracle Home for BI directory, at
<BI_Oracle_Home>/clients/biappsclients/odi/OBIA_LPG_Plugin.zip
i.e., /u01/OBIEE11g/Oracle_BI1/clients/biappsclients/odi/OBIA_LPG_Plugin.zip_FILES.zip
Follow the instructions in the Readme file to extract the ZIP file and deploy the jar files as
follows:

Installing "Oracle BI Load Plan Generator" plug-in:


===================================================
1. Close ODI Studio client, if already running.
2.
Copy
lpggui.jar
and
OBIALoadPlanGenerator
folder
to
<ODI_Home>/oraledi/client/ide/extensions/ folder
i.e.,
to
/u01/OBIEE11g/Oracle_ODI1/oracledi/client/ide/extensions/OBIALoadPlanGenerator/
3. Restart the ODI Studio client.
4. Access "Oracle BI Load Plan Generator" plug-in from the "ODI" menu in ODI
Studio.
15. Applying Post-Installation Patches:
This section contains information about the post-installation patches that you must apply.
To apply the post-installation Patches:
1. Apply the ATGLite Patch, as described in Section 15.1, "Applying the ATGLite
Patch".
2. Apply the client-side Patch 16629917 to ODI Studio, as described in Section 15.2,
"Applying Patch 16629917 to ODI Studio".
3. Apply the client-side Patch 16492220 to BI Clients, as described in Section15.3,
"Applying Patch 16492220 to BI Clients".
The patches are available in the directory in which you extracted the Fusion Middleware
Patches, in the PATCH_ROOT_DIR, i.e, /home/oracle/Softwares/OFM_Pathces_for_OBIA/
15.1 To apply the ATGLite Patch:
1. Stop all the services related to Business Intelligence components.
Note: Use Fusion Middleware Control to stop Oracle BI EE components. For more
information, see 'Using Fusion Middleware Control to Start and Stop Oracle
Business Intelligence System Components and Java Components" in Oracle
Business Intelligence Suite Enterprise Edition System Administrator's Guide.
Use ./opmnctl stopall to stop all the Oracle BI EE components.
2. Update the BIACOMP schema:
Oracle recommends that you perform the steps below by starting a fresh Xterm,
such as Xterm1, because the ORACLE_HOME used is the Oracle RDBMS client.
a. Identify the client install of Oracle RDBMS. Set the environment to execute
SQLPlus from this client installation. The most common variables are
ORACLE_HOME, PATH LD_LIBRARY_PATH, TWO_TASK and ORACLE_SID.
Verify that you can connect to the BIACOMP schema database as
sqlplus system/<password>
i.e, sqlplus system/password
sqlplus <BIACOMP_user>/<password>
i.e., PS1_BIACOMP/Admin123
b. Execute the following:
sqlplus <schema_BIACOMP>/<password_DW>@<db>
@<BI ORACLE_HOME>/sdf/DW/ATGPF/sql/fndtbs_11170_upg.sql

i.e,
sqlplus
PS1_BIACOMP/Admin123@sysdba@/u01/OBIEE11g/Oracle_BI1/sdf/DW/ATGPF/
sql/ fndtbs_11170_upg.sql

3. Apply seed data updates:


Note: This step applies to Linux and UNIX installations only.
Oracle recommends that you perform the steps below by starting a fresh Xterm,
such as Xterm1, because the ORACLE_HOME used is the ORACLE_HOME for BI.
a. Identify the BI_ORACLE_HOME.
This is the directory under MW_HOME that holds Oracle BI EE and Oracle BI
Applications code. For example:
/u01/OBIEE11g/Oracle_BI1
b. Set ORACLE_HOME to BI_ORACLE_HOME as follows:
export ORACLE_HOME= /u01/OBIEE11g/Oracle_BI1
c. Execute the post script using following command. You must specify the
arguments in the same order as they appear:
cd <patch_dir>/16239380/custom/linux
sh
post
apply
16239380
<database
host>:<database
port>:<database_sid>
<BIACOMP schema> <BIACOMP password>
i.e,
cd
/home/oracle/Softwares/OFM_Pathces_for_OBIA/biappsshiphome/generic/162
39380/custom/linux
sh post apply 16239380 FCSHYDSR0022:1521:odiorcl.fcs-inc.local
PS1_BIACOMP Admin123
4. Start the WebLogic Server using Fusion Middleware Control, and restart BI Services
using ./opmnctl startall command.
If you receive the following error, ignore it:
1) SEVERE: java.io.FileNotFoundException:
/
slot/XXXXXXX/oracle/ora6464/mw_home_standalone/patches/XXXXXXXX/custom/sc
ripts/./config/jps-config.xml
(No such file or directory)
2) INFO: MDS-00013: no metadata found for metadata object
"/META-INF/connections.xml"
15.2 Applying Patch 16629917 to ODI Studio:
Patch
16629917
is
available
in
PATCH_ROOT_DIR/odi/generic.

PATCH_ROOT_DIR/odi/generic

or

We have this patch in /home/oracle/Softwares/OFM_Pathces_for_OBIA/odi/generic/


p16629917_111170_Generic.zip
Unzip the patch zip file into the PATCH_TOP folder as follows:
$ unzip -d PATCH_TOP p16629917_111170_Generic.zip
Go
through
the
Readme
file
present
inside
/home/oracle/Softwares/OFM_Pathces_for_OBIA/odi/generic/PATCH_TOP/16629917/Readm
e.txt
And follow accordingly.

15.3 Applying Patch 16492220 to BI Clients:


Patch 16492220 is available in PATCH_ROOT_DIR/biappsshiphome/generic
PATCH_ROOT_DIR/biappsshiphome/generic.
WE
have
this
patch
/home/oracle/Softwares/OFM_Pathces_for_OBIA/biappsshiphome/generic/16492220

or
in

Note: If BI Clients have not been installed then provide the biee_client_install_x64.exe
executable file in the patch to developers to install the BI Clients. Run
biee_client_install_x64.exe obtained on unzip of the patch zip file. Select "Install a new
instance".

16.

Performing Post-Installation System Set-Up Tasks:

16.1 Setting the Business Analytics Warehouse Connection in ODI


a. Log into ODI Studio using the BI Applications Administrator credentials.
Username/Password:Administrator1/Admin123
Master Repository Username/Password:PS1_BIA_ODIREPO/Admin123
Work Repository:BIAPPS_WORKREP
b. In the navigation pane, go to Topology, and expand Technologies, and then
expand File.
c. Create New Physical Schema by right clicking on BIAPPS_DW_FILE and give the
src files connection.

d. Create New Physical Schema by right clicking on FILE_EBSR12 and give the src files
connection.

16.2 Registering Source Systems, warehouse and Propagating Connection Details to ODI
Create New Physical Schema by right clicking on EBSR12 and give the connection.

Create New Physical Schema by right clicking on BIAPP_DW and give the connection.

Create New Physical Schema by right clicking on BIAPPS_BIACOMP and give the
connection.

Configuring Agent:

Configuring Context:

Configuring Logical Architecture:

17.

Data Loads:

We can give the same source connections and warehouse connections and generate the
load plan from Configuration Manager as well.
Login to BIACM by using the below link:
http://fcshydsr0022:9704/biacm
Username/Password:Administrator1/Admin123

Click on Define Business Intelligence Application Instance under System Setups.


Right side we can see Source Systems,Target warehouse,Environment Configuration.
By using the Add button we can add a new source details

Under Manage Business Intelligence Applications select the module which we need to
run

We can see the selected module in the next tab.

Under Load Plans Administration we can create New Load Plans by clicking on the +
button on the top.

After creation of load plan we need to click on generate load plan by clicking on generate
symbol on the top.

After generation of load plan we need to execute the load plan and status can be seen
form ODI Studio.

We need to host the BIAPPS RPD and Catalog in the server for getting the reports.

Change the RPD Connection pool for Oracle BI Application Configuration and for Oracle
Data Warehouse including Init block connection pools.

Once the load is done we can see the reports from the below mentioned URL:
http://fcshydsr0022:9704/analytics
Username/Password : weblogic/Welcome123