Prior to 220.127.116.11 FDMEE was known as ERPi and while it worked together with Oracle Data Integrator (ODI) they were seperate installs.
ODI's installer is good but I woudln't call friendly or great. The agent configuration in ODI for example is not part of the install and it also comes in two forms. The first one being the standalone, that was
easy less difficult to setup but lacked many features. The second being the J2EE agent (preferred) which included an optional web based console and allowed for centralized configuration with the rest most of the EPM products in WebLogic. The J2EE agent required execution of commands using the WebLogic scripting tool and a somewhat manual deployment of the application to WebLogic that was quite unforgiving in single machine installs and downright mean in distributed deployments. On top of that once you got it configured if you wanted to run it as a service you would have to use OPMN or a third party service manager.
Once ODI was working ERPi could be configured. EPRi preferred the use of a specific type of ODI repository (execution) that should only hold scenarios. ERPi also required
some a lot of manual configuration in the ODI topology.
With 18.104.22.168 things have gotten better (assuming FDMEE is installed, manual install ODI is still the same.) FDMEE really streamlines the process, in addition to installing the FDMEE interface it creates ODI repositories, installs the agent, sets it up as s service and configures it all to work together out of the box. The only thing missing is the install of the ODI Studio.
* The steps below assume ODI studio is being installed on a single server environment or on the same server as FDMEE in a distributed environment.
Install ODI Studio
I have always started the ODI install from command line since executing the setup without runtime parameters requires additional environment variables that I rarely set. To do so locate the ODI setup located in X:\Install Path\odi\Disk1. If you do so from windows explorer you can launch a command window from that directory by right clicking on the white space while holding down the Shift button.
Once in the command window the setup can be launched. The jreLoc parameter will set the location of the Java Runtime Environment. Since its being installed on a server where EPM is already installed you can use the JDK that ships with EPM.
Once setup is launched the Welcome screen will appear.
After the Welcome screen is Install Software Updates. Generally I select the Skip Software Updates radio button and continue.
After software updates ODI will prompt for the products to be installed. Since this is being installed on a server with FDMEE the agent and many componets of ODI are already installed and configured so only ODI Studio is needed with the ODI SDK being optional.
After selecting the installation components ODI will continue to the Prerequisite Check screen.
Next on the Specify Install Location screen ODI will ask where to create a Oracle Home or where the existing Oracle home is located.
Locate the existing ODI Oracle Home created by FDMEE in the Middleware directory.
ODI will then prompt to upgrade the existing ODI Oracle Home.
Since FDMEE has already created a exising repository skip the repository configuraion on the Repository Configuraion screen.
On the Specify Security Updates screen the user has the option to be notified of security issues.
The last screen before beginning the installation of ODI Studio is the Installation Summary.
Its likely errors and/or warnings will be encountered during installation. In the next section below I have listed the errors we enountered during my most recent installation. Once the install has completed the Configuration Progress screen will allow the process to continue.
Once completed an Installation Completed summary screen will finish the ODI install process.
Once completed it should be possible to launch ODI Studio from the start menu.
Next up is Configuring ODI Studio with FDMEE which I will cover in my next post.
Warnings and Errors
It is not uncommon to encounter warnings or errors during the ODI install. When doing this installation I encountered the following:
- The install touches a component that is patched by an interim patches.
- File not found: oracle.opss.client
- File not found: oracle.odi.scheduler.manual
- File not found: oracle.sysman.plugin.ai.odi
- File not found: oracle.sysman.plugin.ai.main.oms.mw
- File not found: oracle.fmwconfig
Below I have included the screenshots for reference.