Installing Oracle Business

Intelligence

1. Use the RCU(Repository Creation Utility) to create a obiee repository

2. Before installing Oracle Business Intelligence, use RCU to create the
Metadata Services (MDS) and Business Intelligence Platform
(BIPLATFORM) schemas in the database.
3. To create the BIPLATFORM and MDS schemas with RCU on Oracle
databases, you must possess the DBA privilege and be logged in as
SYSDBA (for example, as user SYS). Although you can use another
database user that has been granted the SYSDBA role, this is not
recommended.
4. RCU comes as a zip file and it would have to be extracted to a
location. Then go to the BIN directory and run the rcu.bat or
simply ./rcu in case of unix. This will open the RCU Create Repository
Screen.
C:\OBIEE-SIEBEL\rcuHome\BIN>rcu.bat

5. In the Welcome screen, click Next. The Create Repository screen

opens.
6. In the Create Repository screen, select Create and then click Next.
The Database Connection Details screen opens.
7. In the Database Connection Details screen, select the type of
database on the system. This is the database in which you create
the Oracle Business Intelligence schemas. Provide the necessary
credentials for RCU to connect to the database. Click Next. The
Checking Prerequisites screen opens. After the checks conclude with
no errors, click OK to dismiss the screen and proceed to the Select
Components screen.
8. In the Select Components screen, near the top of the screen, select
Create a new Prefix. The default prefix is DEV. You can provide
another prefix, if preferred. Oracle Business Intelligence 11g
Installer automatically creates schema names in the format
prefix_schemaname. For example, if you provide the prefix BI, RCU
creates a schema named BI_BIPLATFORM.

9. Note: Make a note of the schema names and the prefix values from
this screen. You need them to configure the products later in the
installation process. If you forget the schema names and want to
find them in the database, Click the plus sign (+) next to the
Business Intelligence component group.
10. Then, click Business Intelligence Platform so that a check
appears next to it. This action automatically selects the Metadata
Services (MDS) schema (under the AS Common Schemas group),
which is also required by Oracle Business Intelligence. If you have
another MDS schema installed to use with Oracle Business
Intelligence, clear the Metadata Services (MDS) box and ignore
the warning message that appears in the Messages box.
 11. Do not select the Oracle AS Repository Components
option, as this configures RCU to install many other schemas that
are not required by Oracle Business Intelligence.
12. Click Next. The Checking Prerequisites screen opens. After the
checking is complete with no errors, click OK to dismiss the screen
and proceed to the Schema Passwords screen.

In the Schema Passwords screen, select Use same password for all
schemas, and provide and confirm a password for the schemas. for
example the password is 'obiee' the schema names would be by default
dev_biplatform and dev_mds.
13. Click Next to proceed to the Map Tablespaces screen.
14. In the Map Tablespaces screen, confirm the schema names.
Click Next to create the tablespaces for the schemas. After the
tablespaces are created with no errors, click OK to dismiss the
screen and proceed to the Summary screen.
15. In the Summary screen, click Create. The Create screen
opens and RCU creates the schemas. After the schemas are created
with no errors, the Completion Summary screen opens. In the
Completion Summary screen, click Close.
16. The machine on which the OBIEE servers are going to
run may not be having Oracle Database installed. If the
oracle database in running on a different server, then ensure
that the OCI connectivity is available between the box where
OBIEE servers are going to run and the Oracle database
server. For this, Oracle Client has to be installed in the box
where OBIEE servers are going to run and the tnsnames.ora
file has to be configured properly.

Starting Oracle Business Intelligence 11g

Installer
1. Invoke the runInstaller (UNIX or Linux) or setup.exe (Windows)
program. Find these programs in the bishiphome/Disk1 directory of
the expanded installation files. Follow the prompts of the installation
program. If the Prerequisite Checks step finds missing software,
install that software and run the installation program again.
2. If the Prerequisite Checks step finds incorrect kernel parameters,
correct the parameters and run the installation program again.
3. For example, you may need to add the following lines to
the /etc/security/limits.conf configuration file on Linux
operating systems.

username soft nofile 10000

username hard nofile 10000
 4. Before you start the Oracle Business Intelligence 11g Installer,
ensure that the ORACLE_HOME environment variable is not set.

5. Open a command window, and do one of the following: If you

downloaded and extracted the Oracle Business Intelligence .zip files,
access the bi_installer_loc/Disk1 directory If you have the Oracle
Business Intelligence 11g Installer DVD, insert the DVD into your
computer and access the Disk1 directory.
6. Run the following command depending on your operating system:

For UNIX:
./runInstaller.sh

7. Note: Running Oracle Business Intelligence 11g Installer as the root

user is not supported For Windows: bishiphome\Disk1\setup.exe.

Note: Install Oracle Business Intelligence with the Run as Administrator

option enabled
8. Simple install: Installs Oracle Business Intelligence components
with the default settings on a single computer in the minimum
number of steps. The Simple Install type is intended for installing
standalone instances of Oracle Business Intelligence. You cannot
scale out, add components to, or use the Configuration Assistant on
instances of Oracle Business Intelligence that were installed with the
Simple Install type.
9. Unlike the Enterprise Install type, the Simple Install type does not
install a Managed Server. Furthermore, with Simple Install type,
components that typically exist in the Managed Server (logically
speaking) are provided in the Administration Server instead.
10. Enterprise install for new installations: Installs a new
Oracle Business Intelligence system for a hosted deployment on one
or more computers
11. Enterprise install to scale out existing installations:
Scales out an existing enterprise installation of Oracle Business
Intelligence 11g.
12. Software only install: Installs software binary files in a
Middleware home for later configuration, such as in an empty Oracle
WebLogic Server domain, IBM WebSphere cell or in a Middleware
home that was previously created by another Oracle Fusion
Middleware product installation (for example, Oracle SOA Suite).
This is useful if your goal is to have multiple domains or products
share a common Middleware home. This install type is required to
install Oracle Business Intelligence with your own JDK.
13. For example for the user weblogic, give the password as say
weblogic1. Specify Installation Location Specify the Oracle
Middleware home location. Optionally, change the following
settings:

Domain home location

Oracle instance location
Oracle instance name

14. Click Next to continue.

Run the Oracle Business Intelligence Administration tool

1. If you have installed Oracle Business Intelligence on Microsoft

Windows, choose the Administration tool from the Start menu
options for Oracle Business Intelligence.
2. If you have installed Oracle Business Intelligence on another
operating system, download and install the Oracle Business
Intelligence Developer Client Tools on a Microsoft Windows
computer. Download the Oracle Business Intelligence Developer
Client Tools installer from the Oracle Business Intelligence download
Web page (http://www.oracle.com/technetwork/middleware/bi-
enterprise-edition/downloads/biee-111150-393613.html).
3. Move a copy of the Oracle ATG Web Commerce Business Intelligence
data model repository file to a directory in which you can open and
edit it with the administration tool. The repository file is provided in
the Oracle ATG Web Commerce installation directory at the following
location.

<ATG10dir>\ARF\DW\OracleBI\OracleBIServerComponent\repository\ATG.r
pd.

4. If you are deploying the data model for Oracle ATG Web Knowledge
Manager analyses, configure the repository file at the following
location. Only use this repository file for Knowledge Manager
reporting and use it instead of the primary Oracle ATG Web
Commerce repository file described above.

<ATG10dir>/Service10.1.2/Service/DW/OracleBI/OracleBIServerCo
mponent/repository/
ATG.rpd

5. Open the repository file in the Oracle Business Intelligence

Administration tool. Enter the default password 'Admin123'

6. Open the properties dialog box for the physical layer of the model.
Select View > Physical if it is not already selected. Select the
physical layer (labeled ATGDW) and choose Edit > Properties.
7. Open the Connection Pool tab and double-click the ATGDW
Connection Pool connection to edit it. Enter the connection
information for your data warehouse database.
8. Fill up the Database details in the datasource field something like
below:

(DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (PROTOCOL = TCP)

(HOST = LOCALHOST)(PORT = 1521))) (CONNECT_DATA =
(SERVICE_NAME = ORCL)))
9. Click OK on all open dialog boxes. Save the model and check its consistency when
prompted. Close the repository file. You will need this file when you deploy business
intelligence content

10.
 Deploying to the Oracle Business
Intelligence Server

1. When you install Oracle Business Intelligence, the Oracle Business

Intelligence installer automatically installs the SampleAppLite.rpd
file with a default repository password of Admin123.
2. Install the Oracle Business Intelligence data model repository file
and analysis definitions on the Oracle Business Intelligence server.
3. Before you perform this procedure, make sure that you have
installed Oracle Business Intelligence, you have the administrator
user name and password, and that you have prepared the data
model repository file.
4. To deploy the data model and business intelligence content to the
Oracle Business Intelligence server:
a. Get the file containing the Oracle ATG Web Commerce
Business Intelligence analysis definitions file from the Oracle
ATG Web Commerce installation directory at the following
location.

<ATG11dir>/ARF/DW/OracleBI/OracleBIPresentationServicesComponent/ca
talog/ATG.zip

b. If you are deploying analyses for Oracle ATG Web Knowledge

Manager, get the file from the following location. Only use this
file for Knowledge Manager reporting and use it instead of the
primary Oracle ATG Web Commerce analysis definition file
described above.

<ATG10dir>/Service10.1.2/Service/DW/OracleBI/OracleBIPresentationServi
cesComponent/
catalog/ATG.zip

c. Unzip the analysis definitions file at the following location on

the Oracle Business Intelligence server. A Folder by name ATG
would be created under the below folder.

<OBIserver>/instances/instance1/bifoundation/OracleBIPresentati
onServicesComponent/coreapplication_obips1/catalog

d. Log into the Oracle Enterprise Manager Fusion Middleware

Control. This application is available on the Oracle Business
Intelligence server at the following URL:

http://server-name:port/em
 http://localhost:7001/em

5. Choose Farm_bifoundation_domain > Business Intelligence >

coreapplication in the navigation panel on the left.

6. Click Lock and Edit Configuration.

7. Click Choose File in the Upload BI Server Repository section of the
coreapplication configuration screen.

8. Browse to the data model repository file that you prepared with the
connection information for your data warehouse database.
9. Enter the password for the data model repository file in the
Repository Password and Confirm Password fields.
10. Enter the path to the directory that holds the business
intelligence content catalog files in the Catalog Location field in the
BI Presentation Catalog section. This is the directory that you
unzipped in a previous step.

11. Click Apply, Activate Changes, and Restart to apply recent

changes. Restart the system on the overview tab.

12. Now logon to the OBIEE home page with the following URL:

localhost:9704/analytics

13. Logon with userID as weblogic and password as weblogic1.

 14. Click on the Catalog Menu on the top RHS menu.

15. Select the ATG folder and open it. You will find many OOTB
reports. The reports can be run now, if we have data populated in
the dw schema.

16. If the data has not been populated, check up whether Logger
components are running and the log files are getting generated for
every activity done on the system.
Note: Dont confuse these log files with the application log files like
debug.log, info.log etc.,
17. Now ensure that your ATG servers are running and also the
DW components are running properly. you can check up that the
data is getting populated in the dw schema and data loader server
instances are running.

UNIX Specific requirements

On all UNIX operating systems, the minimum Open File Limit should be
4096. You can see how many files are open with the following command:

/usr/sbin/lsof | wc -l

To check your open file limits, use the commands below.

For C-shell:

limit descriptors

For Bash:
ulimit -n

To change the open file limits, login as root and edit the
/etc/security/limits.conf
file. Look for the following two lines:
* soft nofile 2048
* hard nofile 2048

Change the values from 2048 to 4096, then reboot the machine

Enabling Unicode Support

Your operating system configuration can influence the behavior of

characters supported by Oracle Fusion Middleware products.
On UNIX operating systems, Oracle highly recommends that you enable
Unicode support by setting the LANG and LC_ALL environment variables to
a locale with the UTF-8 character set. This enables the operating system
to process any character in Unicode. Oracle SOA Suite technologies, for
example, are based on Unicode.
If the operating system is configured to use a non-UTF-8 encoding, Oracle
SOA Suite components may function in an unexpected way. For example,
a non-ASCII file name can make the file inaccessible and cause an error.
Oracle does not support problems caused by operating system
constraints.

Installing as a Non-Default User on UNIX Operating Systems

On UNIX operating systems, the installation of Fusion Middleware products

is owned and controlled as a known user (for example, "oracle"). The file
permissions associated with this installation are configured to ensure the
highest level of security possible, which by default are 700 (meaning all
files are owned and accessible by the owner only).

Changing the default permissions settings will reduce the security of the
installation and possibly your system. Therefore, making such a change is
not recommended. If access to particular files or executables is required
by other users, the UNIX sudo command (or other similar command)
should be considered in lieu of changing file permissions.

Linux OS Requirements
Platfo OS Version Required packages Required
rm Kernel
Version
X86 Oracle binutils-2.15.92.0.2-13 2.6.9
Linux 4 compat-libstdc++-296-2.96-
(UL7+) 132.7.2
 Red Hat compat-db-4.1.25-9
Linux 4 control-center-2.8.0-12
(UL7+) gcc-3.4.3-22.1
gcc-c++-3.4.3-22.1
glibc-common-2.3.4-2.9
gnome-libs-1:1.4.1.2.90-44.1
libaio-0.3.1051
libaio-devel-0.3.1052
libstdc++-3.4.3-22.1
libstdc++-devel-3.4.3-22.1
make-1:3.80-5
openmotif-2.2.32
openmotif21-2.1.30-
11.RHEL4.4
pdksh-5.2.14-30
setarch-1.6-1
sysstat-5.0.5-1
xscreensaver-4.18-5.rhel4.2
x86 Oracle binutils-2.16.91.0.5-23.4 2.6.18
Linux 5 compat-libstdc++-296-2.96-
(UL3+) 132.7.2
Red Hat compat-db-4.1.25-9
Linux 5 control-center-2.8.0-12
(UL3+) gcc-4.1.0-28.4
gcc-c++-4.1.0-28.4
glibc-common-2.3.4-2.9
libaio-0.3.1062
libaio-devel-0.3.1062
libstdc++-4.1.0-28.4
libstdc++-devel-4.1.0-28.4
make-3.80-202.2
openmotif-2.2.31
openmotif22-2.2.31
setarch-1.6-1
sysstat-5.0.5-1
x86-64 Oracle binutils-2.15.92.0.2 2.6.9
Linux 4 compat-libstdc++-33-3.2.3
(UL7+) for x86_64
Red Hat compat-libstdc++-33-3.2.3
Linux 4 for i386
(UL7+) elfutils-libelf-0.97
elfutils-libelf-devel-0.97
gcc-3.4.5
 gcc-c++-3.4.5
glibc-2.3.4-2.19 for x86_64
glibc-2.3.4-2.19 for i686
glibc-common-2.3.4
glic-devel-2.3.4 for x86_64
glic-devel-2.3.4 for i386
libaio-0.3.105 for x86_64
libaio-0.3.105 for i386
libaio-devel-0.3.105
libgcc-3.4.5 for x86_64
libgcc-3.4.5 for i386
libstdc++-3.4.5 for x86_64
libstdc++-3.4.5 for i386
libstdc++-devel-3.4.5 for
x86_64
libstdc++-devel-3.4.5 for
i386
make-3.80
openmotif-2.2.33
openmotif21-2.1.30-
11.RHEL4.41
sysstat-5.0.5
x86-64 Oracle binutils-2.17.50.0.6 2.6.18
Linux 5 compat-libstdc++-33-3.2.3
(UL3+) for x86-64
Red Hat compat-libstdc++-33-3.2.3
Linux 5 for i386
(UL3+) elfutils-libelf-0.125
elfutils-libelf-devel-0.125
gcc-4.1.1
gcc-c++-4.1.1
glibc-2.5-12 for x86_64
glibc-2.5-12 for i686
glibc-common-2.5
glibc-devel-2.5 for x86-64
glibc-devel-2.5-12 for i386
libaio-0.3.106 for x86_64
libaio-0.3.106 for i386
libaio-devel-0.3.106
libgcc-4.1.1 for x86_64
libgcc-4.1.1 for i386
libstdc++-4.1.1 for x86_64
libstdc++-4.1.1 for i386
 libstdc++-devel-4.1.1
make-3.81
openmotif-2.2.33
openmotif22-2.2.33
redhat-lsb-3.1-12.3.EL.0.2
sysstat-7.0.0
xorg-x11-utils5
x86-64 Oracle binutils-2.20.51.0.2-5.28.el6 2.6.32-100.
Linux 6 compat-libcap1-1.10-1 28.5.el6
(UL1+) compat-libstdc++-33-3.2.3-
Red Hat 69.el6 for x86_64
Linux 6 compat-libstdc++-33-3.2.3-
(UL1+) 69.el6 for i686
gcc-4.4.4-13.el6
gcc-c++-4.4.4-13.el6
glibc-2.12-1.7.el6 for x86_64
glibc-2.12-1.7.el6 for i686
glibc-devel-2.12-1.7.el6 for
i686
libaio-0.3.107-10.el6
libaio-devel-0.3.107-10.el6
libgcc-4.4.4-13.el6
libstdc++-4.4.4-13.el6 for
x86_64
libstdc++-4.4.4-13.el6 for
i686
libstdc++-devel-4.4.4-13.el6
libXext for i686
libXtst for i686
openmotif-2.2.3 for x86_642
openmotif22-2.2.3 for
x86_642
redhat-lsb-core-4.0-7.el6 for
x86_64
sysstat-9.0.4-11.el6
uln-internal-setup-1.0.1-
1.el6.noarch.rpm