My Blog

Installing BI Apps 11.1.1.8.1: Part 2 – Install & Configure BI Apps

by Paul Cannon on 23rd May 2014 55 comments

This is the second part of my example walk-through of performing an installation of the newly released Oracle BI Applications 11.1.1.8.1.

I’m performing a completely fresh installation on our Exalytics/Exadata servers using an E-Business Suite 12.1.3 database as the data source.

In part 1 I went through the pre-requisites required before BI Apps can be installed, including installing OBIEE, ODI and creating the warehouse and repositories using the RCU.

Part 2 below will cover installing and configuring BI Apps

Part 3 will demonstrate a simple example of load data into the warehouse and viewing it in OBIEE.

Before beginning the pre-requisites in Part 1 must have been performed – they install the OBIEE platform onto which BI Apps will be installed as well as setup ODI and the database warehouse & repository schemas.

Carrying on then, we are now at the point of starting the BI Apps installation.

Install Oracle BI Applications

From the files downloaded in Part 1, unzip “Oracle Business Intelligence Applications (11.1.1.8.1).zip” into a temporary directory. From within here go to the biappsshiphome directory and run:

./runInstaller -jreLoc <OBIEE_HOME>/Oracle_BI1/jdk

biapps2_01

Skip past the welcome screen when it appears:biapps2_02

Confirm all the pre-requisite checks pass:

biapps2_03

The Oracle Home Directory must be the same directory under which OBIEE is installed – I seen this screen default to the next number up (Oracle_BI2) sometimes in previous installations  of BI Apps, so double check it and change it back to the original OBIEE directory if necessary.  If you don’t change this the installer just hangs, no messages, no files being copied, it just sits there indefinitely!

biapps2_04

Next Confirm you’ve selected oracle home correctly:

biapps2_05

Let the installation proceed:

biapps2_06

And wait for it to finish.biapps2_07

This has installed the BI Apps software into the OBIEE 11g home directory, but as yet it is not configured or ready to use.

Apply Fusion Middleware Platform Patches.

There are a number of patches to various Fusion Middleware components that need to be applied before we can proceed. These patches are all supplied as part of the BI Apps media pack within three zip files.

Before beginning ensure OBIEE, ODI and Weblogic is stopped – including the node manager.

Download and unzip to a temporary directory three patch files:

Oracle Fusion Middleware Platform Patches for Oracle Business Intelligence Applications (Part 1 of 2).zip
Oracle Fusion Middleware Platform Patches for Oracle Business Intelligence Applications (Part 2 of 2) .zip
Oracle Fusion Middleware Platform Patches for Oracle Business Intelligence Applications for Microsoft Windows x86 (64bit).zip

Your temporary patch directory should contain 5 sub-directories, biappsshiphome, odi, oracle_common, soa & weblogic

These directories contain more zip files – these will be unzipped by the script that performs the patch installation.

Now the patch script can be run. This uses perl and needs to be run from a command window (in Windows open with the Run as Administrator option)

Change directory to the <OBIEE_HOME>Oracle_BI1biappstoolsbin directory.

The APPLY_PATCHES.pl script uses a parameter file, apply_patches_import.txt, to control its process and this is located in the same directory.

You need to edit this file in a text editor and amend all of the paths specified. The original file looks like this:

# Required - Java home
JAVA_HOME=/scratch/aime/work/mw_home/Oracle_BI1/jdk
# Required - Inventory Location
INVENTORY_LOC=/scratch/aime/oraInventory
ORACLE_HOME=/scratch/aime/work/mw_home/Oracle_BI1
MW_HOME=/scratch/aime/work/mw_home
COMMON_ORACLE_HOME=/scratch/aime/work/mw_home/oracle_common
WL_HOME=/scratch/aime/work/mw_home/wlserver_10.3
SOA_HOME=/scratch/aime/work/mw_home/Oracle_SOA1
ODI_HOME=/scratch/aime/work/mw_home/Oracle_ODI1
# Required - An existing writable directory to create logs and temp patch files
WORKDIR=/scratch/aime/tmp/work
# Required - Path of patch directory till the release patch-set folder which is inside patches4fa/dist
# i;e the patch-set folder for a particular release to apply patch from
# eg; /scratch/aime/tmp/ps1/biappsshiphome/patches4fa/dist/ps6rc3
PATCH_ROOT_DIR=/scratch/aime/tmp/patches4fa/dist/ps6rc3

My amended file is:

JAVA_HOME=/u01/app/biapps/Oracle_BI1/jdk
INVENTORY_LOC=/home/oracle/oraInventory
ORACLE_HOME=/u01/app/biapps/Oracle_BI1
MW_HOME=/u01/app/biapps
COMMON_ORACLE_HOME=/u01/app/biapps/oracle_common
WL_HOME=/u01/app/biapps/wlserver_10.3
SOA_HOME=/u01/app/biapps/Oracle_SOA1
ODI_HOME=/u01/app/biapps/Oracle_ODI1
WORKDIR=/home/oracle/temp
PATCH_ROOT_DIR=/home/oracle/Downloads/patches

Essentially do the following:

Replace /scratch/aime/work/mw_home with your <OBIEE_HOME> directorySet INVENTORY_LOC to your oracle inventory directory
Set WORKDIR to a temporary directory
Set PATCH_ROOT_DIR to the directory where you unzipped the patch files above

The command is:  perl APPLY_PATCHES.pl <PARAM_INPUT_FILE_PATH>

Replacing <PARAM_INPUT_FILE_PATH> with the full path to the above parameter file. E.g.:

cd /u01/app/biapps/Oracle_BI1/biapps/tools/bin
perl APPLY_PATCHES.pl /u01/app/biapps/Oracle_BI1/biapps/tools/bin/apply_patches_import.txt

Upon completion a patching report called final_patching_report.log  will be created in the WORKDIR directory specified above

----------START OF PATCHING REPORT------------------
Current PLATFORM Detected :linuxx8664

* BIAPPSSHIPHOME Patching Report ..........
Patch Succeded: fsmlitedb_rel8pmlr2_17937188.zip
Patch Succeded: p17463314_111170_Generic.zip
Patch Succeded: p16913445_111170_Generic.zip
Patch Succeded: fsmlite_rel8pmlr2_18529692.zip
Patch Succeded: fsclite_rel8pmlr2_17937189.zip
Patch Succeded: p17463403_111170_Generic.zip
Patch Succeded: p17300045_111170_Generic.zip
Patch Succeded: p16997936_111170_Generic.zip
Patch Succeded: atglite_rel8mlr12_17657541.zip
Patch Succeded: atglite_rel8mlr11_database_17533000.zip
Patch Succeded: BIFNDNEPM_11_1_1_7_0OBIEEBP_LINUX_X64_130816_0640_17314326.zip
Patch Succeded: BISERVER_11_1_1_7_0OBIEEBP_LINUX_X64_130919_2217_17463395.zip
Patch Succeded: BIFNDN_11_1_1_7_0OBIEEBP_LINUX_X64_131008_1224_5_17463376.zip
Patch Succeded: p16569379_111170_Linux-x86-64.zip

* Oracle Common Patching Report ..........
Patch Succeded: idmpatch-1310a-ps6-17447428-owsmrel8.zip
Patch Succeded: SOACOMMON_REL8B7_17549390.zip
Patch Succeded: EM_p14670290_111170_Generic.zip
Patch Succeded: Webservices_Patch-2-PS6REL8_bug-17629596.zip
Patch Succeded: J2EE_Patch-3-PS6RC3_bug-17237952.zip
Patch Succeded: p16080773_111170_Generic.zip
Patch Succeded: WebCenter_BP8REL8_2_17483105.zip
Patch Succeded: p16433036_111170_Generic.zip
Patch Succeded: p16830801_111170_Generic.zip
Patch Succeded: appstrace_17363039.zip
Patch Succeded: T2P_FW_REL8_Patch2_17353546.zip
Patch Succeded: p16433147_111170_Generic.zip
Patch Succeded: idmpatch-1311a-ps6-17665823-opss.zip
Patch Succeded: JDEVADF_REL8MLR9-RT_17611288.zip
Patch Succeded: fmw_diagnostics_17714493.zip
Patch Succeded: idmpatch-1309a-ps6-17440204-urapi.zip

* SOA Patching Report ..........
* ODI Patching Report ..........

Patch Succeded: p18204886_111170_Generic.zip

* Weblogic Patching Report ..........
Successfully installed Patch ID: 2GH7
Successfully installed Patch ID: W3Q6
Successfully installed Patch ID: RJNF
Successfully installed Patch ID: FKGW
Successfully installed Patch ID: JEJW
Successfully installed Patch ID: LJVB
Successfully installed Patch ID: IHFB
Successfully installed Patch ID: 6AEJ
Successfully installed Patch ID: EAS7
Successfully installed Patch ID: TN4A
Successfully installed Patch ID: KPFJ
----------END OF PATCHING REPORT------------------

If any of the patches fail you can see individual patch logs in the WORKDIR directory which may help resolve any issues.

Updating ATGLite & FSM

ATGLite and FSM are two components of the BI Apps toolset are upgraded by the patch set in the previous set but which may also contain database objects in the BI Apps repository which also needs updating.

This updating is performed by calling the biappsrepositoryutil.jar file twice with a long list of parameters.

biappsrepositoryutil.jar exists in the <OBIEE_HOME>/Oracle_BI1/biapps/tools/lib directory.

It requires the following parameters:

  • upgradeATG or upgradeFSM:  the tasks being performed.
  • bi.oracle.home:  the location of the Oracle_BI1 directory
  • work.dir: a temporary working directory
  • biacomp.user:  the BI Apps repository schema created in the RCU, e.g. BIAPPS_BIACOMP
  • biacomp.password: the password to the BI APPs repository
  • db.conn.sid.url: the connection string for the database in host:port:sid format
  • atg.db.seed.url or fsm.db.seed.url: the connection string for the database in host:port/service_name format
  • db.sys.user: A db user with sysdba privileges, e.g. sys
  • db.sys.password: the password to the db sysdba user.

Change directory to the <OBIEE_HOME>/Oracle_BI1/biapps/tools/lib directory.

Run this first for the ATG update:

/u01/app/biapps/Oracle_BI1/jdk/bin/java -jar biappsrepositoryutil.jar upgradeATG bi.oracle.home=/u01/app/biapps/Oracle_BI1 work.dir=/home/oracle/temp biacomp.user=BIAPPS_BIACOMP biacomp.password=welcome1 db.conn.sid.url=dbserver:1521:ora12c atg.db.seed.url=dbserver:1521/ora12c.local.com db.sys.user=sys db.sys.password=welcome1

Then run it for the FSM update:

/u01/app/biapps/Oracle_BI1/jdk/bin/java -jar biappsrepositoryutil.jar upgradeFSM bi.oracle.home=/u01/app/biapps/Oracle_BI1 work.dir=/home/oracle/temp biacomp.user=BIAPPS_BIACOMP biacomp.password=welcome1 db.conn.sid.url= dbserver:1521:ora12c  fsm.db.seed.url=dbserver:1521/ora12c.local.com db.sys.user=sys db.sys.password=welcome1

Both commands generate a log of steps which should end with ‘Completed component upgrade’:

biapps2_08

Weblogic and OBIEE can now be restarted by running your normal start script (biapps.sh if you used the one from part 1 of this blog).

You can see the impact of the patching by logging into OBIEE with the Weblogic admin user and clicking in the Administration link at the top of the page. In the Administration screen you can see that the version of OBIEE has changed from the 11.1.1.7.0 that was originally installed to 11.1.1.7.131017:

biapps2_09

 

Configure BI Applications.

At this point the BI Apps and ODI software has been installed but not yet deployed to the weblogic server.  So the next step is run the configuration wizard to perform the deployments.

In summary the following components are about to be deployed:

  • Oracle BI Applications Configuration Manager
  • Functional Setup Manager
  • ODI
  • Java EE Agent
  • ODI Console
  • Load Plan Generator

Also an Administrator user for BI Apps will be created and the ODI repository will be configured.

To start the configuration wizard locate and run the following command:

<OBIEE_HOME>/Oracle_BI1/bin/configApps.sh

Skip past the welcome screen:

biapps2_11

Confirm the prerequisite checks pass ok:

biapps2_12

Enter the password for the Weblogic admin user (the other fields should be default filled):

biapps2_13

The next screen shows you the home location details, but you can’t change anything:

biapps2_14

Select ‘BI Application Components’ to install:

biapps2_15

You now need to specify a password for the OBIEE repository – a new RPD file will be installed by this process.

biapps2_16

Next you need to create a new admin user for BI Apps. This will be the main admin user for both BI Apps and ODI:

biapps2_17

Now you need to provide the location and user-id/password for the OBIEE MDS schema – created by the RCU when OBIEE was installed.

biapps2_18

Next comes the BI Apps repository schema – BIAPPS_BIACOMP, created by the BI Apps RCU:

biapps2_19

Then it needs the connection details for the data warehouse schema, BIAPPS_DW:

biapps2_20

And finally the ODI Repository schema, BIAPPS_ODI_REPO:

biapps2_21

Next you can specify the ports, but again I’m keeping defaults – 9704 for BIACM and 15001 for the ODI Console:

biapps2_22

Then confirm the details are correct before starting the configuration:

biapps2_23

Let the configuration progress…

biapps2_24

Take a note of the installation details (URLs etc) and save them before closing the Configuration tool.

biapps2_25

 

Copying Source Files

The source ETL files used by BI Apps are located under the OBIEE home directory as part of the installation, however they must now be moved to somewhere outside the OBIEE home otherwise they risk being upgraded automatically in the future if patches are applied and thereby overwriting any custom ETL developments.

The new location must be somewhere on the same OBIEE server where the ODI agent can access them, but outside of the OBIEE (or Weblogic) home directories. Also avoid locating them somewhere with a long directory path.

In this example I’ve chosen /u01/app/etl

biapps2_26

 

Install ODI Studio

To install on client pc, unzip the same zip files for the full ODI install on the server and run the setup.exe with the –jreLoc parameter (install java JDK on your client pc first) from the Disk1 sub-directory.

setup.exe -jreLoc C:Progra~1Javajdk1.7.0_51

Skip past the welcome screen:

biapps_91

Choose to Skip software updates:

biapps_92

In the Installation Type screen just select ODI Studio:

biapps_93

Confirm the prerequisites pass ok:

biapps_94

Take a note of the install location in the following screen:

biapps_95

Again choose to skip the Repository Configuration – in this case because it’s already been done.

biapps_96

Choose whether to receive email updates, I chose not to:

biapps_97

Confirm what is about to be installed:

biapps_98

Let the installation progress:

biapps_99

Check the configuration happens ok:

biapps_100

Close the installer once it’s compete.

biapps_101

Do not launch studio yet.

The next step is to synchronize the security between Studio and the Weblogic server. This needs to be performed for all client Studio installations and the Studio installed on the server (if you intend to use it).

Firstly Copy the files cwallet.sso and jps-config-jse.xml from:

 <OBIEE_Home>/user_projects/domains/bifoundation_domain/odi-client-config/embedded

On the server to:

<ODI_Home>/oracledi/client/odi/bin

biapps2_30

For the client studio installation FTP these two files from the OBIEE server to this directory on the client machine.

Note: these files will need to be regenerated and copied whenever the bi apps administrator password, or any ODI users passwords, are changed in weblogic.To regenerate these files run:

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

Now edit the file <ODI_Home>/oracledi/client/odi/bin/odi.conf

vi /u01/app/biapps/Oracle_ODI1/oracledi/client/odi/bin/odi.conf

Locate the line:

 AddVMOption -Doracle.security.jps.config=./jps-config.xml

And change it to:

 AddVMOption -Doracle.security.jps.config=./jps-config-jse.xml

Here’s my odi.conf file:

IncludeConfFile ../../ide/bin/ide.conf
AddVMOption -XX:MaxPermSize=256M
AddVMOption -Doracle.core.ojdl.logging.config.file=ODI-logging-config.xml
AddVMOption -Dorg.apache.commons.logging.Log=org.apache.commons.logging.impl.Jdk14Logger
AddVMOption -Djava.util.logging.config.class=oracle.core.ojdl.logging.LoggingConfiguration
AddJavaLibFile ../../../../oracledi.sdk/lib/ojdl.jar
AddJavaLibFile ../../../../oracledi.sdk/lib/dms.jar
AddJavaLibFile ../../jdev/extensions/oracle.odi.navigator/lib/log4j-1.2.8.jar
AddJavaLibFile ../../jdev/extensions/oracle.odi.navigator/lib/odi_hfm.jar
AddJavaLibFile ../../jdev/extensions/oracle.odi.navigator/lib/odihapp_common.jar
AddJavaLibFile ../../jdev/extensions/oracle.odi.navigator/lib/ess_es_server.jar
AddJavaLibFile ../../jdev/extensions/oracle.odi.navigator/lib/ess_japi.jar
AddJavaLibFile ../../jdev/extensions/oracle.odi.navigator/lib/odihapp_essbase.jar
AddJavaLibFile ../../jdev/extensions/oracle.odi.navigator/lib/odihapp_planning.jar
AddVMOption -Dnative.canonicalization=false
AddVMOption -Doracle.security.jps.config=./jps-config.xml
AddVMOption -Doracle.odi.studio.ess=false
AddVMOption -Dide.AssertCheckingDisabled=true
AddVMOption -Dide.AssertTracingDisabled=true
AddVMOption -DLOG_FILE=studio.log
AddVMOption -Dsun.java2d.noddraw=true
SetJavaHome /u01/app/biapps/Oracle_BI1/jdk

 

Load Plan Generator Plug-in

The Load Plan Generator is used by the BIACM to control the creation of load plans, however it possible to use it directly in ODI, indeed there are times when it’s best to run it ODI – the logging is far better when investigating issues.

The load plan generator plug-in for ODI is supplied in a zip file and can be found in

 <OBIEE_HOME>/Oracle_BI1/clients/biappsclients/odi/OBIA_LPG_Plugin.zip

Copy this file to the <ODI_Home>/oracledi/client/ide/extensions folder in all studio installations and un-zip it:

biapps2_31

Again repeat this for client studio installations.

Now in Studio the ‘Oracle BI Load Plan Generator’ menu option appears under the ODI menu:

biapps2_32

 

Setup repository connection in ODI Studio.

Each Studio client installation will need a connection setup to the BI Apps ODI repository.

Launch the ODI studio. If you are running from the server this can run from:

 <OBIEE_HOME>/Oracle_ODI1/oracledi/client/odi.sh

From a client pc, launch it from:

<Install_Home>Oracle_ODI_1oraclediclientodi.exe or odi64.exe

Once ODI has started click ‘Connect To Repository’:

biapps2_33

Click the add (green cross) icon on the login screen:

biapps2_34

Now fill in the details of the repository, using the biapps user-id created above during the BI Apps configuration and the BIAPPS_BIA_ODIREPO repository.

To make like easier you should select the work repository now as well (BIAPPS_WORKREP was setup by the BI Apps configuration above) and set it as the default connection. Click Test to ensure all is ok before saving.

biapps2_35

Now back in the login screen connect with the biapps user-id:

biapps2_36

Changing the ETL Location

Earlier on we moved the ETL directories out from under the <OBIEE_HOME>/ directory to somewhere else (/u01/app in my case). We now need to tell ODI where we’ve moved it to, otherwise it will continue to edit & run the ETL from the original location.

In Studio select the Topology tab then expand Technologies -> File then BIAPPS_DW_FILE:

biapps2_38

This will by default be pointing at the /etl directory under the OBIEE home directory. This needs changing to the new directory you copied the ETL files to above.

Double click on BIAPPS_DW_FILE./u01/app/biapps/Oracle_BI1…

biapps2_39

Then change the Directory (Schema) and Directory (Work Schema) to point to the new ETL location, including the /data_files/src_files/BIA_11 directory, in my case:

/u01/app/etl/data_files/src_files/BIA_11

Then click save (the disk icon in the menu bar)

Now exit from ODI Studio.

 

Change the Weblogic start/stop script

The script you use to start & stop Weblogic now needs to be amended to include the odi_server1 service which has now been added.

If you are using the script I used in Part 1 on this blog then do then edit this file (biapps.sh) and perform the following:

After the line:

BIEE_SERVER=bi_server1

Add the line:

ODI_SERVER=odi_server1

Then locate the line:

echo  password=$BIEE_PASSWD >>$ORACLE_FMW/user_projects/domains/$BIEE_DOMAIN/servers/$BIEE_SERVER/security/boot.properties

and add the following two lines after it:

echo  username=$BIEE_USER >$ORACLE_FMW/user_projects/domains/$BIEE_DOMAIN/servers/$ODI_SERVER/security/boot.properties
echo  password=$BIEE_PASSWD >>$ORACLE_FMW/user_projects/domains/$BIEE_DOMAIN/servers/$ODI_SERVER/security/boot.properties

Next locate the section:

echo "********************************************************************************"
echo "OBIEE start sequence completed on $(date)"
echo "********************************************************************************"

and just above this add the section:

echo "********************************************************************************"
echo "Starting Managed Server $ODI_SERVER on $(date)"
echo "********************************************************************************"
$BIEE_PATH/startManagedWebLogic.sh $ODI_SERVER http://$BIEE_MANAGER_URL &
wait_for "Server started in RUNNING mode"

Finally locate the section:

echo "********************************************************************************"
echo "Stopping Node Manager on $(date)"
echo "********************************************************************************"

and just above it add the following section:

echo "********************************************************************************"
echo "Stopping Managed Server $ODI_SERVER on $(date)"
echo "********************************************************************************"
$BIEE_PATH/stopManagedWebLogic.sh $ODI_SERVER t3://$BIEE_MANAGER_URL $BIEE_USER $BIEE_PASSWD

Save and test it by performing a full stop and start:

./biapps.sh stop

./biapps.sh start

If you are not using my script you will need to create the boot.properties file under:

<OBIEE_HOME>/ user_projects/domains/bifoundation_domain/servers/odi_server1/security

for your own script to work. This can be copied from:

<OBIEE_HOME>/user_projects/domains/bifoundation_domain/servers/bi_server1/security/boot.properties

as the details are the same.

To confirm everything has started correctly login to the Weblogic console (http://servername:7001/console) and check the servers page:

biapps2_37

Registering Source Systems and Propagating Connection Details to ODI

We now need to setup the connection details for the source data systems – in my case I’m using the Vision demo in an E-Business suite 12.1.3 database.

Open a browser and enter the following URL:

http://./biacm

e.g. http://biapps_server.local.com:9704/biacm

biapps2_40

Login with the biapps user created earlier.

In the navigation pane click on ‘Define Business Intelligence Applications Instance’ under ‘System Setups’.

Click the Add (green cross) icon in the Source Systems tab:

biapps2_41

In this screen you specify which Product you are using as your data source and it’s version. I’m using E-Business Suite 12.1.3 so that’s what I’ve selected.

The source instance name and description are what the connections will be called in BI Apps, so anything appropriate will do.

The data source number is used in the warehouse to identify where data records come from, useful if you have more than one source. Enter a 1 in this field as it’s the first. If you add additional data sources later on these will increment to 2, 3 and so on.

biapps2_42

Click next.

You now need to enter the connection details to the source system

Firstly in the middle ‘context details’ section select ‘Global’ as the context. This is the default context used in the ODI ETL.

In the Connection details section give the connection a name and fill out the driver, url, username and password fields appropriately. For an E-Business suite connection it should connect with the APPS user.

Click the Test button to ensure all is ok:

biapps2_43

Next in the Connection details section click on the “Technology: File System” tab.

In here you need to specify the location of the data files for BI Apps. These are located under the /etl directory created above, under data_files/src_files, then the directory applicable to the source system, in my case EBS_12_1_3

Enter a name for the server, its host name and then the full path to this directory.

Then click “Save and Close”

biapps2_44

 

 

Enabling offerings for Deployment

The next step is to switch on the BI Apps modules that you are deploying, which of course will depend on which modules have been purchased and which are applicable to the data source(s) you are using for this installation.

In the Task pane click on Manage Business Intelligence Applications:

biapps2_45

Scroll down the list and select all the Functional Areas you require.

As you check each one you will get a window informing you of shared functional areas that are also required and therefore also selected:

biapps2_46

You can expand the modules and individually include/exclude selected functional areas. Here I have drilled into Financial Analysis and de-selected Federal Financials:

biapps2_47

Once you have selected all the required Module and Functional Areas click save.

Now click on the Business Intelligence Application Offerings and Associated Sources tab:

biapps2_48

This is where you map each functional area to a data source. By default all functional areas will map to all sources. I have only created one source (E-Business Suite), so that is all that appears, but in reality you may have multiple sources each used for different functional areas, so you must disable those combinations which don’t apply.

Click save.

Set preferred Currency Names

In the Task pane click on manage Preferred Currencies:

biapps2_49

In this screen you can change the Preferred Currency Name for each Currency Code used by BI Apps.  As you click on each currency you can see which Functional Areas it is used by in the bottom window (e.g. contract currency is only used by Project Analytics). The currency names are displayed on the dashboard in the Account dialogPreferences settings window for each user.

To change a Currency Name click on it, then click the edit icon. Click save when done.

 

Set Languages for Data load into the warehouse

In the tasks pane now Click on ‘Manage Warehouse Languages’.

In here you can install all required languages for this BI Apps installation. Not quite sure why there’s not a British English (it’s our language after all…), so I’ll settle for keeping American English.

biapps2_50

If you install more than one language you can set the default base language by highlighting the required language then clicking ‘Set Base Language’  icon in the toolbar above.

Click save when done.

 

Enabling Initialization Blocks

Initialization blocks are small pieces of code which run upon either server startup or user login startup to set variables which control the user experience. Apart from the Fusion Apps modules, these are disabled by default, so needs to be enabled for the required modules.

Start by copying the sample config.txt template file from

<ORACLE_HOME>/Oracle_BI1/biapps/biarpdutil/bin

to

 <ORACLE_HOME>/Oracle_BI1/biapps/biarpdutil/lib

And rename it with a capital C – Config.txt

biapps2_51

Now copy the Oracle BI repository file for BI Applications from

<OBIEE_HOME>/instances/instance1/bifoundation/OracleBIServerComponent/coreapplication_obis1/repository

To:

<BI_ORACLE_HOME>/biapps/biarpdutil/lib

This will be called OracleBIApps_BI000x.rpd   the x may vary, but is usually a 2 if BI Apps has been installed on a clean new installation of OBIEE. Whatever it is, take the file with the latest x-number.

biapps2_52

Next execute the bi-init.sh script file.  This initialises various environment variables for the OBIEE instance.

This file is located in:

<OBIEE_HOME>/ instances/instance1/bifoundation/OracleBIApplication/coreapplication/setup

As it set variables under Linux make sure you run it with a .-space command, e.g.:

biapps2_53

In addition to the OBIEE enbironment variables you also need to add the following directory to the PATH variable:

<OBIEE_HOME>>/Oracle_BE1/bifoundation/server/bin
export PATH=$PATH:/u01/app/biapps/Oracle_BI1/bifoundation/server/bin

biapps2_54

Next edit the Config.txt file that you copied above as follows:

RPD File Name <RPD file name>
RPD Password <RPD password>
RPD Database List <Comma separated list of database names in RPD physical layer for which the initialization block has to be enabled>

The RPD file will be the RPD file you copied just above, it’s password was created earlier on in the BI Apps configuration (screen ‘Step 6 of 15’)

Note: The values in the RPD Database List must include all initialization blocks related to the source system that need to be enabled. “Oracle BI Server” must be included as a value in the RPD Database List if an initialization block that needs to be refreshed from the Oracle BI EE Server is to be enabled.

The full list is:

RPD Database List
<
Oracle Data Warehouse,
Oracle BI Application Configuration,
Oracle DB InitBlock Initialization,
Oracle EBS OLTP,
PeopleSoft OLTP,
Siebel OLTP,
Oracle BI Server,
oracle.apps.crm.model.analytics.applicationModule.CrmAnalyticsAM_CrmAnalyticsAMLocal,
oracle.apps.fscm.model.analytics.applicationModule.FscmTopModelAM_FscmTopModelAMLocal,
oracle.apps.hcm.model.analytics.applicationModule.HcmTopModelAnalyticsGlobalAM_HcmTopModelGlobalAMLocal,
CRM_OLTP
>

I changed my list to the following:

<
Oracle Data Warehouse,
Oracle BI Application Configuration,
Oracle DB InitBlock Initialization,
Oracle EBS OLTP,
Oracle BI Server
>

My final file looked like this:

RPD File Name<OracleBIApps_BI0002.rpd>
RPD Password<Admin123>
RPD Database List<Oracle Data Warehouse,Oracle BI Application Configuration,Oracle DB InitBlock Initialization,Oracle EBS OLTP,Oracle BI Server>

Next run the ManageInitBlock.jar utility, located in <OBIEE_HOME>/Oracle_BI1/biapps/biarpdutil/lib, using the following command:

<OBIEE_HOME>/Oracle_BI1/jdk/bin/java -classpath ManageInitBlock.jar oracle.apps.biarpdutil.ManageInitBlock >log.txt

This takes a little while to run.

This created a new RPD file called Output_RPD.rpd with all relevant initialization blocks enabled. There is a log file, log.txt, which lists all the changes made to the RPD.

Rename this file to OracleBIApps.rpd and copy it back to the OBIEE repository directory. It won’t be used by OBIEE yet, but it will be ready for the next steps.

biapps2_55

 

The OBIEE Administration Tool & Editing the RPD

The next three steps all involve the OBIEE repository file OracleBIApps.rpd,  created by the previous step.

This file can only be edited using the OBIEE Administration Tool, which is a windows-only utility and must be installed first. This is part of the Oracle Business Intelligence client tools; however you need to ensure you install the correct version.  Right at the start of the BI Apps installation we installed OBIEE 11.1.1.7.0 and we have the client zip file for that. However later on OBIEE was patched to 11.1.1.7.131017 and we do not have a client zip for this version.

Instead the client installer can be downloaded from OBIEE itself.  Launch a browser and login to OBIEE (http://servername:9704/analytics) with the Weblogic admin user-id.

If you already have the client tools installed you can check the version with the about screen in the Administration tool:

biapps2_56

In the ‘Home’ page in the left hand pane there is a section called ‘Get Started…’ and under here a drop-down option called ‘Download BI Desktop Tools’. Under here choose the Oracle BI Client Installer (either 32 or 64 bit depending on your client windows version):

biapps2_57

Save the file, biee_client_install_???.exe, to your pc (it’ll probably end up in your downloads folder) then run it. If this is on a server version of windows you may need to use the ‘run as administrator’ option by right clicking on the file.

Click past the splash screen:

biapps2_58

Then the welcome screen:

biapps2_59

Choose a location to install the software – the default is “C:Program FilesOracle Business Intelligence Enterprise Edition Plus Client Tools”, but this is a bit long-winded and you will need to access this directory in a dos command window later on, so I usually shorten it to C:Program FilesOBIEE_Client

biapps2_60

Decide where you want to create the product icons:

biapps2_61

Then start the installation:

biapps2_62

This will only take a few minutes:

biapps2_63

When you close the installer it will automatically open the window ODBC Data Source Administrator:

biapps2_64

The reason for this is to setup an ODBC link using the Oracle BI Server driver to the OBIEE server to enable on-line editing of the repository. This is something I generally discourage – off-line editing and keeping versioned copies of the RPD file is a much safer way of maintaining the repository – especially with very large complex repositories like the BI Apps one. I therefore usually cancel out of the ODBC Admin tool without creating the data source.

You now need to copy (ftp) the repository OracleBIApps.rpd file from the BI Apps server to your client pc.

From above this repository file is stored in:

<OBIEE_HOME>/instances/instance1/bifoundation/OracleBIServerComponent/coreapplication_obis1/repository

Now launch the Administration Tool from the start menu:

biapps2_65

Once open, use File -> Open Offline to open the RPD file. The password when it prompts for it is the one you entered during the BI Apps configuration above (screen “Step 6 of 15”).

It will take a short while to open, it is very large – the new version for 11.1.1.8.1 now contains the mappings for Fusion Apps, so it’s almost twice the size as the previous version. Later on I’ll cover trimming out the unneeded mappings to reduce its size.

biapps2_66

Once opened it’s ready for the next steps.

 

Enable Document Currency.

The first issue to address is the “Document” Currency (aka Entered Currency). This is disabled by default, but is usually required (if not by the users, it make testing easier) .To enable it you need to amend some filters in the RPD file.

The filters are stored by Security Groups and there is one per functional area:

  • OBIA_CRM_CURRENCY_PREFERENCES
  • OBIA_FINANCIAL_CURRENCY_PREFERENCES
  • OBIA_HCM_CURRENCY_PREFERENCES
  • OBIA_MARKETING_CURRENCY_PREFERENCES
  • OBIA_MFG_CURRENCY_PRFERENCES
  • OBIA_PARTNER_CURRENCY_PREFERENCES
  • OBIA_PROCUREMENT_CURRENCY_PREFERENCES
  • OBIA_PROJECT_CURRENCY_PREFERENCES
  • OBIA_SALES_CURRENCY_PREFERENCES
  • OBIA_SCM_CURRENCY_PREFERENCES

From in the open repository, select ‘Manage’ -> ‘Identity’ from the menu.

In the list of Application Roles locate each of the above roles one at a time:

biapps2_67

Double click on the role:

biapps2_68

Then click on Permissions:

biapps2_69

Copy the contents of the Data Filter field into a text editor (re-format across multiple lines to make it easy to read):

biapps2_70

You need to remove the last condition:

AND
"Core"."Fact - Preference List"."Currency Preference Code" <>  'Document Currency'

biapps2_71

Then paste it back into the data filter field (you need to edit back into a single line before pasting)

Click ok to save and then repeat for all of the other currency roles.

 

Trimming the RPD

The RPD contains all of the modules available in BI Apps, which may be more than have been purchased on a deployment. Whilst these can be left in (on the basis that they won’t be used) it is best to remove them to minimise the OBIEE start-up time and memory requirements for the RPD. It will also make it easier to maintain going forwards.

Additionally the size of the RPD is too big to deploy using the Enterprise Manager. This means that if you are using all the modules you will have to manually deploy the RPD after each change rather than using the Enterprise Manager upload & restart features.

The RPD can be trimmed immediately upon install or later on after further customisations have been performed. The latter is a more complex task as you will need to merge in the customisations, so it’s best to do it during the installation.

To do this the RPD needs to be copied down to the client pc where Administrator is installed. We can start with the OracleBIApps.rpd edited above.

This step needs to be run in a command window. There is a batch file called bi-init.bat file installed with the BI Client installation which sets the necessary environment variables before we begin.

This will be found in the <client home>oraclebiorahomebifoundationserverbin  directory, in my case:

C:Program FilesOBIEE_Clientoraclebiorahomebifoundationserverbin

if you are running this on a windows server where OBIEE was installed run bi-init.cmd from the <obiee_home>instancesinstanceXbifoundationOracleBIApplicationcoreapplicationsetup directory.

Note this doesn’t appear to do much, but it alters the path and environment variables ready for the next commands.

biapps2_72

Now run the ExtractProjects.exe command from the same directory.

ExtractProjects -B input_rpd  -O output_rpd -I "project_name"

Repeating the  -I “project_name” parameter for each project that has been purchased.

To see a full list of the projects included in this release see the ‘Supported Source Applications’ tab of the certification spread sheet downloaded at the start of the install process in part 1 of this blog. The ‘Oracle BI Application’ column lists the projects:

biapps2_73

However this spread sheet does not contain the actual project names, for this look in the RPD in the ‘Manage’ -> ‘Projects’ window:

biapps2_74

In this case I just want the Financial,HR, Procurement & Spend and Supply Chain & Order Management analytics projects, which are called:

  • Financial Analytics Fusion Edition
  • Human Resources Analytics Fusion Edition
  • Procurement and Spend Analytics Fusion Edition
  • Supply Chain and Order Management Analytics Fusion Edition

I also want to retain the usage training module.

So the ExtractProjects command I need is:

ExtractProjects -B OracleBIApps.rpd  -O OracleBIApps_trimmed.rpd -I "Financial Analytics Fusion Edition" -I "Human Resources Analytics Fusion Edition" -I "Procurement and Spend Analytics Fusion Edition" -I "Supply Chain and Order Management Analytics Fusion Edition" -I "Usage Tracking"

Change directory to where the RPD file is before running.

You will be prompted for the Repository password.

biapps2_75

The new RPD is considerably smaller than the original:

biapps2_76

If you then open the new RPD in the Administration Tool you see it opens a lot faster and contains less content:

biapps2_77

All that remains is to deploy this RPD to OBIEE. First rename the file back to OracleBIApps.rpd (deleting or renaming the original one).

Now open a browser and enter the URL for the enterprise manager: http://servername:7001/em and login with as Weblogic admin user.

In the left hand pane expand “Business Intelligence” and click on coreapplication:

biapps2_78

Now click on the Deployment tab and Repository Sub-tab. Then click ‘Lock and Edit Configuration’ and wait for the confirmation screen to appear.

biapps2_79

Click the Browse button in the ‘Upload BI Server Repository’ section and navigate to and select the new OracleBIApps.rpd file.  Wait a few seconds for the new file to be upload – this has completed when the Browse button disappears and an ‘Update…’ button appears in its place:

biapps2_80

Now enter the repository password twice then click the Apply button.  Note that the Default RPD file name as incremented to OracleBIApps_BI0003.  Now click ‘Activate Changes’

biapps2_81

Once the changes have been activated the OBIEE services need to be restarted. Click on the link to ‘Restart to apply recent changes’.

Now in the overview screen click the ‘Restart’ button:

biapps2_82

Let the Restart commence and wait for it to complete.

You can login to OBIEE now and see the available dashboards and reports (use the Weblogic admin user again). We haven’t loaded any data yet, so the reports will not display anything, but you can see the full set of dashboards that have been installed:

biapps2_83

 

That’s it! BI Apps is now installed and ready for use.  In Part 3 I’ll run through the steps to perform a basic data load from my E-Business Suite source system and give access to the reports in OBIEE.

Paul CannonInstalling BI Apps 11.1.1.8.1: Part 2 – Install & Configure BI Apps

55 comments

Join the conversation
  • Kevin Russell - 20th June 2014 reply

    More excellent work.
    I was going through the standard installation document and had nearly got to the end of the material covered in this blog (part 2) when I stumbled across your excellent article.
    Helped me finish the last actions.

    Now things start to get interesting.
    As with previous versions of OBIA the standard documentation is awful.

    How is Part 3 coming along?
    I hope you have more ‘luck’ than I am going around in circles trying to work out what some of these functional steps actually mean.

    Help!

    Paul Cannon - 20th June 2014 reply

    Kevin,

    glad my blogs helped!…thanks for the reminder about part 3, I’d written it but forgotten to publish it!…it’s there now: http://blog.3sixty-analytics.com/?p=1417

    Cheers,

    Paul

    Kevin Russell - 14th July 2015 reply

    Here I am again over a year later.
    My OBIA work was put on the back burner big time – shame I didn’t recheck an hour or so after my last post!
    Have been working with e-DBA on and off since with some of your colleagues (some now EX) – small world.
    Part 3 here we come (if somewhat belatedly on my part!)

  • Nilay - 16th July 2014 reply

    Configuration for BIAPPS 11.1.1.8.1 successful but biacm and ODI agent are not running. Log files say biacm configuration failed . Any inputs would be very much appreciable . Thanks!

  • Amyn - 20th July 2014 reply

    Hi Paul
    Thanks for excellent compilation of the the whole end to end process. Its truly a life saver. I was able to bring up the BI environment on our test servers with help of these articles.
    I hope you’ll have time to answer this question I have.
    I was at the point in installation where I ran appsConfig.sh (on x86 Solaris) on putty/Xming… all inputs were provided as per your document and it started configuring when xming crashed… unfortunately I was VPN to the server when my wifi crashed…immediately xming crashed and putty hung…I had to kill it…
    now I do not know upto what point it went thru… I tried restarting the appsConfig.sh, it opened the installer screen where I had to enter weblogic port 7001 (default) … pressing next errored out with message “BIAPPS is already configured, choose other”… do you know how I can restart this configuration?
    Thanks for your help.

    Paul Cannon - 25th July 2014 reply

    Amyn,

    sorry, but I think this is case of delete it and start the install again -it’s the only way to be 100% that the installation is complete.

    Paul

    Chinna - 9th December 2014 reply

    Hi Paul,

    you said delete and install again, you mean we need to uninstall everything and install from scratch
    or
    we can able to delete particular configuration and install again.

    Thanks,
    Chinna

  • famy - 25th July 2014 reply

    Paul,
    That was excellent article.
    Could you tell me, if we need to open the rpd’s and update the variables to point it to EBS / apps schema at any stage ? If so which are the variables which needs to be modified ? If not, why are we not, as we do similar activity in 7964 version of biapps

    Can you please help ?

    Rgds,
    Famy

    Paul Cannon - 25th July 2014 reply

    Famy,

    you don’t need to open the RPD and update the variables to point to the EBS/apps schema – this is entirely optional. The RPD is setup with the connection pool variables to connect to the BI Apps data warehouse based on the details entered during the install, and this is the only ‘compulsory’ setting. There are some components in the RPD which can access EBS directly and if you want to use these then yes you do need to set the variables appropriately – the variables are ORA_EBS_OLTP_DSN and ORA_EBS_OLTP_USER. You need to enter the password directly the connection pools.

    hope that helps,

    Paul.

  • Amyn - 2nd August 2014 reply

    Thanks Paul
    I did clean up and reinstalled…. it worked.

    pradeep - 9th April 2015 reply

    Hi Amyn,
    Please let me know which folder you have deleted.

  • Naeem Akhtar Khan - 14th August 2014 reply

    Very helpful.

    Please add in “Install ODI Studio” portion that client machine you used/preferred is windows. I can see that you are executing .exe which make sense but may be confusing to someone.

    Also BI Admin tools and Catalog Manager can only be installed on Windows so better to give little awareness about this too.

    Regards
    Naeem Akhtar Khan

  • Prem - 14th August 2014 reply

    Excellent Work and very helpful…..

  • Eduardo Montes - 18th August 2014 reply

    Hi Paul

    Excelent blog.
    I have one problem, when I tried to define the repositoru connection with ODI, I have somo issues.
    When I tied to use thin client. I have an error message as if I were using oci8
    I was able to connect trough toad with direct connection.

    I read oracle coumentation and they said that the odi client has to be patched.

    Any advice?

    Paul Cannon - 21st August 2014 reply

    Eduardo,

    Sorry, I’ve not come across this issue. my advice would be to following the patching instructions!

    Paul.

    ALi - 19th December 2014 reply

    hi Eduardo
    are you able to resolve this issue? I am facing same thing on Deploying ODI step, can you please help me if you were able to resolve this issue. thanks

  • Sampath - 20th August 2014 reply

    Hi, for OBIA 11.1.1.8.1, Is it possible to install OBIEE and ODI on different servers? if not is there any oracle doucment stating that this is a limitation or any other reason behind it. i need to provide deployment architecture for OBIA 11.1.1.8.1, please help me.

    Thanks,
    Awaiting your replt.

    Paul Cannon - 21st August 2014 reply

    ODI needs to be installed in the same Middleware home as OBIEE – the installation guide points this out – this is due to the BI ACM, which is part of the OBIEE installation that interfaces directly with ODI. That said there’s no reason why additional OBIEE installations cannot be clustered on other servers – license permitting of course.

    Regards,

    Paul

  • Sandy - 8th September 2014 reply

    Hi ,
    I could complete installation successfully till ATG upgrade. But while running FSM upgrade in the same way, receiving below error
    (/u01/app/devobiapp/Oracle_BI1/biapps/admin/provisioning/update/11.1.1.7.2/from11.1.1.7.0/sdf/fsm/fsm-pre-seeddata-load.sql) does not exist at expected location.
    Sep 08 2014 08:01:19 SEVERE : Seed Data Task exited with error code 255
    I am seeing fsm-pre-seeddata-load.sql file does not exist under fsm where as same kind of pre-seeddata-lod file exists under ATG. How can wee fix this issue?

    Regards,
    Sandy

    Douglas Ochieng - 7th April 2015 reply

    Please check your final_patching_report.log

    * BIAPPSSHIPHOME Patching Report ……….
    Patch Failed: fsmlitedb_rel8pmlr2_17937188.zip

    please make sure your all your BIAPPSSHIPHOME Patching
    are Succeded:

  • Ashraf - 8th September 2014 reply

    Dear Paul

    Excellent blog..I have installed and configured OBIA 11.1.1.7.1 ,everything was running as expected ,then i created virtual host to implement HA <

    After that OBI server is not coming up ..

    All other services and bi server and odi server are up and running..

    In NQSConfig.INI I could see it is using /u01/MW_Home/instances/instance1/bifoundation/OracleBIServerComponent/coreapplication_obis1/repository/OracleBIApps_BI0002.rpd.

    I am not able to open this rpd from my obi client installed in my laptop ..However I can see /u01a/MW_Home/OBIA_HOME/Oracle_BI1/biapps/admin/provisioning/OracleBIServerComponent/OracleBIApps.rpd which i can open with my bi client ..

    Shall i point my repositry to the above rpd and restart the server … ??

    Please find the below logs in the nqserver.log file

    Regards
    Ashraf TP

    [2014-09-08T14:11:20.000+03:00] [OracleBIServerComponent] [ERROR:1] [] [] [ecid: 0001yzTId4U4epw6wFfd6G0001lg000000] [tid: 52] [15045] All physical tables in logical table source 'Fact – CRM – Service Request Last 6 Months'.'Fact_W_SRVREQ_F_Open_Date' must be join connected.

  • Attila Bognar - 10th September 2014 reply

    Hi,

    Thanks for this really detailed and useful guideline. I’m in the process to install OBIA 11.1.1.8.1 Win 7 64 bit machine. I’m stuck at the point of “Configure BI Applications.”. At Step 3 of 9 after adding the BI Domain parameters I got the error message: INST-08064: Specified domain cannot be used to configure a BI System. Unfortunately I have not found any reference to this error, where and what to check. The BI system at overall working fine (http://localhost:9704/analytics). Is there a log file or so, where I can see what is not OK with my BI Domain?

    Would appreciate any help.

    Regards,
    Ates

    azhar - 20th November 2014 reply

    Hi, I am facing the same issue….did you find any solution

  • Niranjan - 12th November 2014 reply

    Thank you so much for sharing this document, this is very useful for us to learn and implement the BIAPPs with ODI

  • Karthik - 14th November 2014 reply

    Hi,

    I have been trying to install BIAPPs 11.1.1.8.1 on a Linux server, taking help from your blog. and it has been really worth a read to go through your steps.
    I completed all installation steps up to Configuring the BIAPPS using configApps.sh
    However due to some network failures it so happened that the configure step failed and I had to resolve some network issues before restarting the same step. But this time at the point where I entered ->>
    “Enter the password for the Weblogic admin user”
    it does not proceed further showing up an error stating that “Specify an BI domain which does not already have BIapps configured on it”
    I understand why the error is showing up but not sure how on earth I can resolve this.. Please Help!!!

  • Venkatesh - 18th November 2014 reply

    Hi Paul,

    we have followed the steps mentioned your blog and completed till Patching the environment (APPLY_PATCHES.pl). while running ConfigApps.sh we are getting the error (“patch_rpd.py failed with status 1”) and we found that OracleBIApps.rpd.temp is missing in the instance location.

    Need your inputs and suggestions to resolve this issue.

    Regards,
    Venkatesh

  • Ather Ali Shaikh - 3rd December 2014 reply

    It is an excellent article to install OBI Apps with the latest version. I am facing a problem at \”/Oracle_BI1/jdk/bin/java -classpath ManageInitBlock.jar oracle.apps.biarpdutil.ManageInitBlock >log.txt\” task, It creates a xRPD.xml file and at 937MB of file size reaches it fails. the log files says
    Error Message:
    biserverxmlgen: failed
    Exiting Program

    I am not sure, what could be the issue because there is no specific error message written in the log file. I do not have any issue with the sapce it 54GB available here.
    Any idea what could be the reason.

    Thanks,

  • Chinna - 9th December 2014 reply

    BIAPPS Configurations:

    Midst of configApps.bat process was failed so i closed the configApps window.
    I am trying to re-run the ./configApps.bat but at stage Extend BI Domain, i got an error

    INST-07525: Specified domain cannot be used to configure BIAPPS system.

    Hav u ever know how to uninstall and reinstall biapps configurations.

  • Vinoth Selvam - 15th December 2014 reply

    During the setup, I got an error that ATG repository version(11.1.1.7.0) is older than minimum required repository version (11.1.1.7.2)
    So I started to apply the patch,

    Below is the apply_patches_import.txt file and it’s configuration,
    I have placed all the patch files in PATCH_ROOT_DIR

    JAVA_HOME=C:appOBIAOracle_BI1jdk
    INVENTORY_LOC=C:Program FilesOracleInventory
    ORACLE_HOME=C:appOBIAOracle_BI1
    MW_HOME=C:appOBIA
    COMMON_ORACLE_HOME=C:appOBIAoracle_common
    WL_HOME=C:appOBIAwlserver_10.3
    ODI_HOME=C:appOBIAOracle_ODI1
    WINDOWS_UNZIP_TOOL_EXE=C:Program Files (x86)7-Zip7z.exe
    WORKDIR=C:Oracle BIbiappsshiphomegenericworkdir
    PATCH_ROOT_DIR=C:Oracle BIbiappsshiphomegeneric

    Below is the script to run the patch file,
    >perl APPLY_PATCHES.pl apply_patches_import.txt

    I’m expecting the patch files to get succeeded, but nothing happens and nor it throws an error message.
    Find the logs below,

    ———-START OF PATCHING REPORT——————

    Current PLATFORM Detected :nt
    * BIAPPSSHIPHOME Patching Report ……….
    * Oracle Common Patching Report ……….
    * SOA Patching Report ……….
    Not applying SOA Patches since SOA Home (SOA_HOME) value is not specified
    * ODI Patching Report ……….
    * Weblogic Patching Report ……….

    ———-END OF PATCHING REPORT——————

    Any help on this would be greatly appreciated,

  • ALi - 18th December 2014 reply

    Hi Paul
    This is great guideline for beginners like me. I am trying to install this on RHEL 6, while running ConfigApp.sh its getting failed on Deploying ODI. log file is not writing any exception or error which can lead me to any resolution. Please help how this can debug and resolved. Thanks

  • shashikant - 2nd January 2015 reply

    Hi Paul,

    Its really helpful for us.
    I am also installing BIAPPS 11.1.1.8. on windows server 20008. all the installation is successful.

    when I am trying to apply platform patches I m getting following error and because of that my installation get fails:

    ———-START OF PATCHING REPORT——————

    Current PLATFORM Detected :nt

    * BIAPPSSHIPHOME Patching Report ……….
    Patch Failed: p17463403_111170_Generic.zip
    Patch Failed: fsmlitedb_rel8pmlr2_17937188.zip
    Patch Failed: p17463314_111170_Generic.zip
    Patch Failed: p17300045_111170_Generic.zip
    Patch Failed: p16997936_111170_Generic.zip
    Patch Failed: p16913445_111170_Generic.zip
    Patch Failed: fsmlite_rel8pmlr2_18529692.zip
    Patch Failed: fsclite_rel8pmlr2_17937189.zip
    Patch Failed: atglite_rel8mlr12_17657541.zip
    Patch Failed: atglite_rel8mlr11_database_17533000.zip
    Patch Failed: BISERVER_11_1_1_7_0OBIEEBP_WINDOWS_X64_130919_2217_17463395.zip
    Patch Failed: BIFNDNEPM_11_1_1_7_0OBIEEBP_WINDOWS_X64_130816_0640_17314326.zip
    Patch Failed: BIFNDN_11_1_1_7_0OBIEEBP_WINDOWS_X64_131008_1223_5_17463376.zip
    Patch Failed: p16569379_111170_MSWIN-x86-64.zip

    * Oracle Common Patching Report ……….
    Patch Failed: EM_p14670290_111170_Generic.zip
    Patch Failed: WebCenter_BP8REL8_2_17483105.zip
    Patch Failed: p16433036_111170_Generic.zip
    Patch Failed: JDEVADF_REL8MLR9-RT_17611288.zip
    Patch Failed: fmw_diagnostics_17714493.zip
    Patch Failed: idmpatch-1309a-ps6-17440204-urapi.zip
    Patch Failed: idmpatch-1310a-ps6-17447428-owsmrel8.zip
    Patch Failed: SOACOMMON_REL8B7_17549390.zip
    Patch Failed: J2EE_Patch-3-PS6RC3_bug-17237952.zip
    Patch Failed: p16080773_111170_Generic.zip
    Patch Failed: Webservices_Patch-2-PS6REL8_bug-17629596.zip
    Patch Failed: p16830801_111170_Generic.zip
    Patch Failed: appstrace_17363039.zip
    Patch Failed: T2P_FW_REL8_Patch2_17353546.zip
    Patch Failed: p16433147_111170_Generic.zip
    Patch Failed: idmpatch-1311a-ps6-17665823-opss.zip

    * SOA Patching Report ……….
    Not applying SOA Patches since SOA Home (SOA_HOME) value is not specified

    * ODI Patching Report ……….
    Patch Failed: p18204886_111170_Generic.zip

    * Weblogic Patching Report ……….

    ———-END OF PATCHING REPORT——————

    Could you please guide me for the same.

    Thanks

    kirangowda - 26th May 2016 reply

    Hi ShashiKanth,
    Did u get the resolution for ur issue ?
    Even I am getting the same error.
    Please do the needful

  • Allan - 28th January 2015 reply

    Great guide, much easier to follow than the offical one!

    Have a problem with the OBIA LPG Plugin. On both the Linux server ODI Studio, and the Windows clients, the Oracle BI Load Plan Generator option appears under the ODI menu, but they are greyed out. Others are also having this issue, as someone has posted same on the Oracle Community forum:-
    https://community.oracle.com/thread/3647747

    No soluiton offered yet. Any idea?

    Thanks
    Allan

  • Amir - 9th March 2015 reply

    Hi Paul,
    I am installing OBIA 11.1.1.8.1. While running the configApps.sh, the configuration assistant failed on step “Configuring Data Warehousing Integration” step. I see the following error message in the bi_server1 log file:

    #### <> <RuntimeException thrown by rmi server: javax.management.remote.rmi.RMIConnectionImpl.invoke(Ljavax.management.ObjectName;Ljava.lang.String;Ljava.rmi.MarshalledObject;[Ljava.lang.String;Ljavax.security.auth.Subject;)
    javax.management.RuntimeMBeanException: javax.management.RuntimeMBeanException: The connection FS_RTF_APP_biacm_conn was not registered. Could not remove the connection.
    javax.management.RuntimeMBeanException: javax.management.RuntimeMBeanException: The connection FS_RTF_APP_biacm_conn was not registered. Could not remove the connection
    at weblogic.rjvm.ResponseImpl.unmarshalReturn(ResponseImpl.java:237)
    at weblogic.rmi.internal.BasicRemoteRef.invoke(BasicRemoteRef.java:223)

    Any idea what might be causing it?
    Thanks,
    Amir

  • J.A. - 11th March 2015 reply

    Paul,
    One amendment to this blog post. In section “Apply Fusion Middleware Platform Patches” you listed
    “Oracle Fusion Middleware Platform Patches for Oracle Business Intelligence Applications for Microsoft Windows x86 (64bit).zip”
    as part of the Fusion Middleware Patches. But given that this is a Linux Install, it should actually be:
    “Oracle Fusion Middleware Platform Patches for Oracle Business Intelligence Applications for Linux x86-64.zip” (Part Number: V44897-01)

    BTW, just noticed that yesterday OBIA 11.1.1.9.1 came out available in eDelivery 🙂

    regards
    Jorge A.
    Instead.

  • chalk ink - 1st July 2015 reply

    bookmarked!!, I love your web site!

  • Manasa - 19th August 2015 reply

    Hi,
    I am stuck at the last step of configuration.it fails at the 0% itself.And the error shows that error in applying configTemplate.Can you please provide a solution soon.

  • Sayan Majumdar - 2nd September 2015 reply

    Hi Paul,

    Could you please guide me to get the hardware requirement ( which should contain HDD space, RAM and CPU for each software ) for having OBIEE, ODI , Endeca and DBIM12c on exalytics. We are having Exalytics x5-4 box.

    And software versions are :

    OBIEE 11.1.1.7.1
    DBIM : 12.1.0.2
    Endeca : 3

  • ahmed ibrahim - 21st September 2015 reply

    hi pls why pic error
    and link for part 3 not working pls i need it

  • Alex Kamwi - 1st October 2015 reply

    Great blog to follow indeed!!
    I have a problem updating the ATG lite and FSM when I run the command for upgrading the ATG I get the following error.
    Any help please will be much appreciated

    Nov 27 2015 11:36:32 SEVERE : ATG schema upgrade failed with follwoing msg
    java.lang.RuntimeException: Exception in running the /u01/oracle/Middleware/Oracle_BI1/biapps/admin/provisioning/update/11.1.1.7.2/from11.1.1.7.0/schema/oracle/atg/upgrade.sql
    at oracle.as.biapps.upgrade.atg.ATGSchemaUpgradeTask.execute(ATGSchemaUpgradeTask.java:49)
    at oracle.as.biapps.upgrade.atg.ATGSchemaUpgradeTask.execute(ATGSchemaUpgradeTask.java:15)
    at oracle.as.biapps.upgrade.AbstractUpgradeCommand.executeTask(AbstractUpgradeCommand.java:78)
    at oracle.as.biapps.upgrade.AbstractUpgradeCommand.executeUpgradeTasks(AbstractUpgradeCommand.java:68)
    at oracle.as.biapps.upgrade.AbstractUpgradeCommand.upgrade(AbstractUpgradeCommand.java:28)
    at oracle.as.biapps.upgrade.AbstractUpgradeCommand.execute(AbstractUpgradeCommand.java:21)
    at oracle.as.biapps.upgrade.BIAppsRepositoryUtil.main(BIAppsRepositoryUtil.java:47)

    Nov 27 2015 11:36:32 INFO : Building JDBCEngine parameters: dbType = Oracle, dbUser = sys as sysdba,connectString = obiee.silnam.com.na:1521:orcl
    Nov 27 2015 11:36:32 INFO : Calling JDBCEngine constructor
    Nov 27 2015 11:36:32 INFO : Connecting to database: user:sys as sysdba, connectString:jdbc:oracle:thin:sys as sysdba/*****@obiee.silnam.com.na:1521:orcl
    Nov 27 2015 11:36:32 INFO : oracle.jdbc.driver.OraclePreparedStatementWrapper@5c29ea31
    Nov 27 2015 11:36:32 INFO : Building JDBCEngine parameters: dbType = Oracle, dbUser = sys as sysdba,connectString = obiee.silnam.com.na:1521:orcl
    Nov 27 2015 11:36:32 INFO : Calling JDBCEngine constructor
    Nov 27 2015 11:36:32 INFO : Connecting to database: user:sys as sysdba, connectString:jdbc:oracle:thin:sys as sysdba/*****@obiee.silnam.com.na:1521:orcl
    Nov 27 2015 11:36:33 SEVERE : Fatal exception encountered while executing RepositoryUtil
    java.lang.RuntimeException: java.lang.RuntimeException: Exception in running the /u01/oracle/Middleware/Oracle_BI1/biapps/admin/provisioning/update/11.1.1.7.2/from11.1.1.7.0/schema/oracle/atg/upgrade.sql
    at oracle.as.biapps.upgrade.atg.ATGSchemaUpgradeTask.execute(ATGSchemaUpgradeTask.java:61)
    at oracle.as.biapps.upgrade.atg.ATGSchemaUpgradeTask.execute(ATGSchemaUpgradeTask.java:15)
    at oracle.as.biapps.upgrade.AbstractUpgradeCommand.executeTask(AbstractUpgradeCommand.java:78)
    at oracle.as.biapps.upgrade.AbstractUpgradeCommand.executeUpgradeTasks(AbstractUpgradeCommand.java:68)
    at oracle.as.biapps.upgrade.AbstractUpgradeCommand.upgrade(AbstractUpgradeCommand.java:28)
    at oracle.as.biapps.upgrade.AbstractUpgradeCommand.execute(AbstractUpgradeCommand.java:21)
    at oracle.as.biapps.upgrade.BIAppsRepositoryUtil.main(BIAppsRepositoryUtil.java:47)
    Caused by: java.lang.RuntimeException: Exception in running the /u01/oracle/Middleware/Oracle_BI1/biapps/admin/provisioning/update/11.1.1.7.2/from11.1.1.7.0/schema/oracle/atg/upgrade.sql
    at oracle.as.biapps.upgrade.atg.ATGSchemaUpgradeTask.execute(ATGSchemaUpgradeTask.java:49)
    … 6 more

  • Shawn - 22nd October 2015 reply

    Encounter the following error when performing the ATG upgrade on LINUX 64. Please advise on recommended solution.

    -bash-4.1$ java -jar biappsrepositoryutil.jar upgradeATG bi.oracle.home=/OBIA-Share/home/middleware/Oracle_BI1/ work.dir=scratch/workfolder biacomp.user=DEV_BIACOMP biacomp.password=********* db.conn.sid.url=XXXXXXXX:orcl atg.db.seed.url=XXXXXXXX/orcl db.sys.user=sys db.sys.password=******

    Oct 21, 2015 9:46:56 PM oracle.biapps.common.config.PropertyUtils parsePropsFromCommandLine
    INFO: About to parse command line into Properties
    Oct 21, 2015 9:46:56 PM oracle.biapps.common.config.PropertyUtils parsePropsFromCommandLine
    INFO: Found bi.oracle.home on the command line
    Oct 21, 2015 9:46:56 PM oracle.biapps.common.config.PropertyUtils parsePropsFromCommandLine
    INFO: Found work.dir on the command line
    Oct 21, 2015 9:46:56 PM oracle.biapps.common.config.PropertyUtils parsePropsFromCommandLine
    INFO: Found biacomp.user on the command line
    Oct 21, 2015 9:46:56 PM oracle.biapps.common.config.PropertyUtils parsePropsFromCommandLine
    INFO: Found biacomp.password on the command line
    Oct 21, 2015 9:46:56 PM oracle.biapps.common.config.PropertyUtils parsePropsFromCommandLine
    INFO: Found db.conn.sid.url on the command line
    Oct 21, 2015 9:46:56 PM oracle.biapps.common.config.PropertyUtils parsePropsFromCommandLine
    INFO: Found atg.db.seed.url on the command line
    Oct 21, 2015 9:46:56 PM oracle.biapps.common.config.PropertyUtils parsePropsFromCommandLine
    INFO: Found db.sys.user on the command line
    Oct 21, 2015 9:46:56 PM oracle.biapps.common.config.PropertyUtils parsePropsFromCommandLine
    INFO: Found db.sys.password on the command line
    Oct 21 2015 21:46:56 INFO : Logging to /OBIA-Share/home/middleware/Oracle_BI1/biapps/tools/lib/scratch/workfolder/upgradeATG2015-10-21_09_46_56PM.log
    Logging to /OBIA-Share/home/middleware/Oracle_BI1/biapps/tools/lib/scratch/workfolder/upgradeATG2015-10-21_09_46_56PM.log
    Oct 21 2015 21:46:56 INFO : Set logging level to: INFO
    Oct 21 2015 21:46:56 INFO : Command line was: upgradeATG bi.oracle.home=/OBIA-Share/home/middleware/Oracle_BI1/ work.dir=scratch/workfolder biacomp.user=DEV_BIACOMP biacomp.password=****** db.conn.sid.url=XXXXXXXXXXX:orcl atg.db.seed.url=XXXXXXXXXXXX/orcl db.sys.user=sys db.sys.password=******
    Oct 21 2015 21:46:56 INFO : About build a Comamnd object for ATG
    Oct 21 2015 21:46:56 INFO : About to configure context for the command :class oracle.as.biapps.upgrade.atg.UpgradeCommandATG
    Oct 21 2015 21:46:56 INFO : About to build upgrade context
    Oct 21 2015 21:46:56 INFO : Using command-line properties gatherer
    Oct 21 2015 21:46:56 INFO : Config property target.upgrade.version is now set to default value: 11.1.1.7.0
    Oct 21 2015 21:46:56 INFO : Loading Version History file
    Oct 21 2015 21:46:57 INFO : Default Value Provider property target.upgrade.version is now set to default value: 11.1.1.7.2
    Oct 21 2015 21:46:57 INFO : neverAskUser is set to true for property atg.repo.user so not asking user.
    Oct 21 2015 21:46:57 INFO : neverAskUser is set to true for property atg.repo.password so not asking user.
    Oct 21 2015 21:46:57 INFO : Config property current.version is now set to default value: 11.1.1.7.0
    Oct 21 2015 21:46:57 INFO : Setting property with key target.upgrade.version to value 11.1.1.7.2
    Oct 21 2015 21:46:57 INFO : Setting property with key atg.db.seed.url to value XXXXXXX/orcl
    Oct 21 2015 21:46:57 INFO : Setting property with key biacomp.password to value *********
    Oct 21 2015 21:46:57 INFO : Setting property with key biacomp.user to value DEV_BIACOMP
    Oct 21 2015 21:46:57 INFO : Setting property with key component.type to value ATG
    Oct 21 2015 21:46:57 INFO : Setting property with key db.sys.password to value *********
    Oct 21 2015 21:46:57 INFO : Setting property with key db.sys.user to value sys
    Oct 21 2015 21:46:57 INFO : Setting property with key current.version to value 11.1.1.7.0
    Oct 21 2015 21:46:57 INFO : Setting property with key db.conn.sid.url to value XXXXXXXXX:orcl
    Oct 21 2015 21:46:57 INFO : Setting property with key work.dir to value scratch/workfolder
    Oct 21 2015 21:46:57 INFO : Setting property with key bi.oracle.home to value /OBIA-Share/home/middleware/Oracle_BI1/
    Oct 21 2015 21:46:57 INFO : Successfully parsed command line arguments:
    Oct 21 2015 21:46:57 INFO : Successfully parsed command line arguments:
    Oct 21 2015 21:46:57 INFO : About to upgrade component – ATG
    Oct 21 2015 21:46:57 INFO : Building JDBCEngine parameters: dbType = Oracle, dbUser = sys as sysdba,connectString = XXXXXXXXX:orcl
    Oct 21 2015 21:46:57 INFO : Calling JDBCEngine constructor
    Oct 21 2015 21:46:57 INFO : Connecting to database: user:sys as sysdba, connectString:jdbc:oracle:thin:sys as sysdba/*****@XXXXXXXX:orcl
    Oct 21 2015 21:46:58 SEVERE : Schema Version registry entry is missing for the component ATG. Therefor using the current version provided by user.
    Oct 21 2015 21:46:58 SEVERE : Fatal exception encountered while executing RepositoryUtil
    java.lang.RuntimeException: Schema Version registry entry is missing in DB for the component : ATG, ownerName: DEV_BIACOMP
    at oracle.as.biapps.upgrade.UpgradeContext.isUpgradedNeeded(UpgradeContext.java:210)
    at oracle.as.biapps.upgrade.AbstractUpgradeCommand.upgrade(AbstractUpgradeCommand.java:27)
    at oracle.as.biapps.upgrade.AbstractUpgradeCommand.execute(AbstractUpgradeCommand.java:21)
    at oracle.as.biapps.upgrade.BIAppsRepositoryUtil.main(BIAppsRepositoryUtil.java:47)

    Samad - 25th November 2015 reply

    try using the generic patches version, if you are using software version for Linux x86-64

    i.e. pb4biapps_11.1.1.10.1_generic.zip

    Sameer Sawant - 8th December 2015 reply

    Hi Shawn, Were you able to resolve the issue. I am also getting the same error while performing ATG update during installation of BI Apps 11.1.1.10. Any help would be appreciated.
    Thanks,
    Sameer Sawant

    suresh - 19th February 2016 reply

    Hi Shawn
    I am also getting the same error during the update of ATGLITE & FSM in Solaris Sparc 11 64 bit

    Feb 19 2016 04:23:13 SEVERE : Schema Version registry entry is missing for the component ATG. Therefor using the current version provided by user.
    Feb 19 2016 04:23:13 SEVERE : Fatal exception encountered while executing RepositoryUtil
    java.lang.RuntimeException: Schema Version registry entry is missing in DB for the component : ATG, ownerName: BIAPPS_BIACOMP
    at oracle.as.biapps.upgrade.UpgradeContext.isUpgradedNeeded(UpgradeContext.java:210)
    at oracle.as.biapps.upgrade.AbstractUpgradeCommand.upgrade(AbstractUpgradeCommand.java:27)
    at oracle.as.biapps.upgrade.AbstractUpgradeCommand.execute(AbstractUpgradeCommand.java:21)
    at oracle.as.biapps.upgrade.BIAppsRepositoryUtil.main(BIAppsRepositoryUtil.java:47)

    For FSM:

    Feb 19, 2016 5:08:03 AM oracle.biapps.common.config.PropertyUtils parsePropsFromCommandLine
    INFO: About to parse command line into Properties
    Exception in thread “main” java.lang.RuntimeException: Expecting args in the form of key=value but got db.conn.sid.url=
    at oracle.biapps.common.config.PropertyUtils.parts(PropertyUtils.java:310)
    at oracle.biapps.common.config.PropertyUtils.key(PropertyUtils.java:322)
    at oracle.biapps.common.config.PropertyUtils.parsePropsFromCommandLine(PropertyUtils.java:281)
    at oracle.as.biapps.upgrade.BIAppsRepositoryUtil.main(BIAppsRepositoryUtil.java:36)

  • Mohan reddy - 12th November 2015 reply

    Hi Paul,

    Thanks in Advance..

    Its really helpful for me, I am also installing BIAPPS11.1.1.8.0 on windows 2007.
    All software Installation is successful(OBIEE11.1.19.1,ODI11g,OBIA11.1.1.8.0).
    when i am trying to configure the ConfigApps.sh i am getting below error

    Error:-
    INST-08067:BIACM repository version 0 is older than minimum required repository version 11.1..1.8.0

    Could you please help me on this..

    Thanks & Regards,
    Mohan

  • Mohan reddy - 12th November 2015 reply

    Oracle Business Intelligence Product Version 11.1.1.9.0 (Build 150417.0810 64-bit)
    Administration Page Help
    Physical Presentation Catalog Path D:\OBIAPPS11g\instances\instance1\bifoundation\OracleBIPresentationServicesComponent\coreapplication_obips1\catalog\SampleAppLite\root
    Oracle BI Server Data Source coreapplication_OH2008265472
    Available Paging Memory (MB) 3357
    Available Virtual Address Space (MB) 8388116
    Replication Disabled
    Maintenance Mode is currently off.

  • mahmoud - 17th November 2015 reply

    Thanks a lot for your effort and I want to ask you the file I should copy “OracleBIApps_BI000x.rpd ”
    I found it as “essbase_OracleBIApps_BI000x.rpd” Is that the file should I copy? please feed me back

    Paul Cannon - 20th November 2015 reply

    Hi Mahmoud,

    I guess so, yes. Maybe the RPD has this slightly different name in later releases – I’ve not seen this yet. Best option is to open this rpd in the admin tool and compare it’s contents with the screenshot in the blog above – it should be similar (although the content may differ is you chose different modules to install).

    Paul.

  • Tabita - 12th February 2016 reply

    Hi Paul
    Thank you for the great work, I followed all your docs (Part 1,2 & 3), my BI is up and running. However, I could not trim the RPD, it says projects I chose are not in the base repository, I opened the repository offline, I could see them. I put that on hold.
    I am now trying to enable the SSL, it did not go well, am not able to use https. Now when I logon to analytics, with http, it throwing an error “Unable to Sign In

    An error occurred during authentication. Try again later or contact your system administrator.”… Please help me with these issues.

  • John - 25th August 2016 reply

    Hello,
    Is it possible to share the Financials rpd you have extracted for OeBS R12?

    Paul Cannon - 26th August 2016 reply

    Sorry John, can’t do that…two reasons, firstly it’s Oracle licensed software and secondly it not based on the OeBS R12, it’s based on the data warehouse that’s populated from OeBS as part of BI Apps. Without the warehouse and the ETL Mappings it wouldn’t be much good to you.

    Paul.

  • Jiten Patel - 14th November 2016 reply

    i had faced one issue with scroll page and below was the work around :

    “Scroll page with fixed heading does not work

    Bug 18233060 is supposed to be fixed in a future version of OBIEE.

    For 11.1.1.7.150120, Patch 21429687 was provided .

    Workaround:
    1.On IE11, use scroll bar to scroll down.
    2.Use other browser like Firefox or Google Chrome”

  • Geovanny - 17th November 2016 reply

    Hi Paul, excelent blog.
    one Question, is it possible using the OBIA to create reports to EPM solution of oracle, like Hyperion Planning or Financial Management being that Essbase the datasource.
    Thank you.

    Paul Cannon - 18th November 2016 reply

    Hi Geovanny,

    yes it is. by using OBIEE directly (rather than via the OBIA ETL/DW) you can import new database sources into the RPD, including Essbase sources. OBIEE will then go directly to Essbase rather than via the DW for it’s data. its quite normal to supplement the OBIA DW with data from other sources in this way.

    Paul.

  • oracle procurement - 20th May 2017 reply

    very interesting article I feel very enthusiastic while reading and the information
    provided in this article is so useful for me. Content in this article guides in clarifying some of my doubts.
    oracle fusion procurement training

Join the conversation