In this post, I will be discussing how to install ODI for OBIA 126.96.36.199.2. Essentially, this means that we will be installing ODI with everything (including ODI Studio) except for the standalone agent. Furthermore, we will not be configuring an ODI repository at this time as a later part of the OBIA installation process will create one for us.
For those of you who have been following along this series, you will see many similarities between this and my blog entry about the OBIEE install. In fact, I heavily leveraged (i.e. essentially duplicated) that earlier blog entry to create this one. So, if you're reading this page and thinking to yourself that all of this sounds awfully familiar, it's because, well, it is. And while I'd like to claim this is because I'm an amazing writer with even more amazingly clever blogging skills, the real credit here is due to Oracle who has spent an enormous amount of time and money developing a common foundation/methodology for their products. When you consider that a product acquired from nQuire via Siebel (OBIEE) and originally intended to run on Windows, and a product acquired by Sunopsis (ODI) can basically be installed the same way with only slightly different parameter files - you can start to understand the scope of what Oracle has done.
General Assumptions and Conventions Used
I will assume that readers of this blog have read the prior blog entries in this series before continuing. Specifically, I will assume that the two ODI zip files (V75874-01_1of2.zip, V75874-01_2of2.zip) have been downloaded from eDelivery and placed in /u01/sw/odi, and Java and WebLogic have already been installed. Please note that while the previous two blog entries have dealt with installing the OBIEE RCU and OBIEE itself (in software-only mode), installing them first is not a pre-requisite. You can install ODI first if you so choose. However, both ODI and OBIEE must be present before continuing on with the remainder of the OBIA installation.
From a high level, the approach outlined by this blog will accomplish the following:
Unzip the two ODI zip files to a temporary working directory ($TMP/odiinst)
Configure a response file to automate the ODI 188.8.131.52 installation (/u01/sw/scripts/odi11119Install.rsp)
Install ODI in the Middleware Home that was created in a previous blog entry ($MW_HOME)
Remove the temporary working directory
Please note that $TMP and $MW_HOME are environment variables that were established in an earlier blog entry in this series.
Unzipping the installation files
The first step is to unzip the ODI installation zip files to a temporary location. The temporary location we will use is $TMP/odiinst. Please issue the following commands from the terminal in order to create this temporary directory and unzip the files there:
$ umask 027
$ mkdir -p $TMP/odiinst
$ cd /u01/sw/odi
$ unzip -q '*.zip' -d $TMP/odiinst
Configuring a response file
In order to install ODI from the command line, you will need a response file (just like with OBIEE).
I have generated a response file called odi11119Install.rsp and have posted it on my GitHub account. I generated this response file from one of my ODI 184.108.40.206 installations. For the purposes of this blog series, we will download this file and store it in /u01/sw/scripts.
This particular response file has already been altered to suite the installation detailed by this blog series. If you want to choose different installation paths or enter different values, the response file does contain documentation to help you do that. However, please note that this blog series will assume that the file is used as is.
Just like with the OBIEE response file, there's not much you would want to change in this response file. Most of the variables need to remain as is in order for subsequent portions of the OBIA installation to work correctly. However, if you wanted to use different paths, you should look at changing the following parameters in the file: MW_HOME, APPSERVER_LOCATION (both of which should be set to the same path) and ORACLE_HOME which will point to the spot where the ODI binaries are installed (and is usually $MW_HOME/Oracle_BI1). Here are the parameter settings I used:
Here is a screenshot of the relevant portion of the response file:
Again, it is important to note that this response file will not install the standalone agent. For OBIA we want the J2EE-managed agent, because ODI will be managed from our WebLogic domain.
Furthermore, this response file also installs ODI Studio (i.e. the ODI GUI) and the ODI SDK (which is required if you elect to install ODI Studio). ODI Studio is not required to be installed on this application server, however you will need it to be installed on some machine in order to finish basic configuration (and to do ODI development, maintenance, etc. post-install). Personally, I like to install ODI Studio on the server. It doesn't take up too much space (a few gigs) and it can be very handy to have it there if you are trying to troubleshoot issues in the future. This blog series will assume that ODI Studio (and the SDK) is installed by this process. If you don't want to do this though, you can simply set the ODI_SDK and ODI_STUDIO parameters in the response file to FALSE. As is shown by the following screenshot, they are currently set to true:
Running the installer
Now that the installation files have been unzipped and the response file created/downloaded, we are now able to launch the installer. In order to do so, please issue the following commands from the terminal: