Configure ODI Master and Work Repository for deployment from DEV to SIT to UAT and finally to PROD

Create one single master repository and configure the topology in following way
- Create the physical architecture which has all your DEV/SIT/UAT/PROD servers configured. This will contain your actual data servers, schema, agents etc/
- Create the logical architecture which contain only one set of logical schema which will be use to point to different physical architecture based on the context.
- Now create diferent context say - DEV, SIT, UAT and PROD and point the logical schema to appropriate physical schema in the context mapping screen. 

ii) Create different work repository for each phase
- One schema for DEV which a development work repository and where all the design and development happens.
- Another schema for UAT which is a execution work repository where the scenarios are pushed after being successfully tested from DEV work repository
- A execution work repository in your production database which has the final tested, tried scenario from the UAT and ready for deployment into production

To deploy either we create a package to automate the workflow where scenario are generated from the UAT/DEV boxes and deployed on the PROD execution work repository using ODI tool like ODIImportObject, ODI Generatel scenarios etc.

Other way is to export the generate the scenario in DEV, export the scenario from Designer screen or command line into XML format and then import the scenario to different work repostory using command line or ODI GUI. For command line ODI has provided import/export JAVA API which you can find in the ODI Tool Reference Guide.

Configuring ODI for integrating with Hyperion Financial Management Application

Using Single-machine architecture; machine will be hosting ODI and hosting HFM and EPM foundation (Workspace and shared services). I have created a FM application named SAMPLE that is based on the “Simple Demo” information that can be found in “Hyperion\products\Financial Management\Sample Apps\Simple Demo\” of the HFM installation.

The machine is windows based as that is a pre-requisite for HFM and also the HFM client that has to be installed on the ODI machine.
The EPM version installed is 11.1.1.3
We need to perform some work around solutions for integrating ODI 11g with EPMA 11.1.1.3.

Step: 1) Go to directory C:\oracle\Middleware\Oracle_ODI1\oracledi\agent\lib Copy the HFMDriver.dll file and pest it to directory 
C:\oracle\Middleware\Oracle_ODI1\oracledi\agent\drivers

Step: 2) If you will use the “Local Agent” you will need to add the driver location to the windows environment variable (Path).
C:\oracle\Middleware\Oracle_ODI1\oracledi\agent\drivers

Once you have added the location make sure you restart all the ODI components to pick up the driver or you will continue to receive the error message.