Most of them who have worked with ODI 10.x will know how good the agent was. Creating, starting, stopping and converting it into service was very easy in older versions.
With ODI using Weblogic to create agent services in the new version, things have become tricky.
If you have skipped master repository creation step while installing, the agent name that you give while installing ODI never shows up automatically in the 'Physical Architecture' tab in Topology, though you can see a batch file created with name 'agent_AGENT_NAME.bat' in the 'C:\oracle\product\11.1.1\Oracle_ODI_1\oracledi\agent\bin' folder and running this batch file directly will give you nothing but an error. You have to modify and run the odiparams.bat file before running the agent file.
Modifying the odiparams.bat file : File is located in the path mentioned above. Search for the below lines
REM #
REM # Repository Connection Information
REM #
set ODI_MASTER_DRIVER=oracle.jdbc.OracleDriver
set ODI_MASTER_URL=jdbc:oracle:thin:@localhost:1521:XE
set ODI_MASTER_USER=MASTER
set ODI_MASTER_ENCODED_PASS=a7yXZz0C1gPf2GxKzUNPxEJMp
REM #
REM # User credentials for agent startup program
REM #
set ODI_SUPERVISOR=SUPERVISOR
set ODI_SUPERVISOR_ENCODED_PASS=a7yabVOzj7C5oY503v.Ei6xKy
REM #
REM # User credentials for ODI tools
REM #
set ODI_USER=%ODI_SUPERVISOR%
set ODI_ENCODED_PASS=%ODI_SUPERVISOR_ENCODED_PASS%
REM #
REM # Work Repository Name
REM #
set ODI_SECU_WORK_REP=WORK
The text highlighted in yellow needs to be changed as per your Master Rep and Work rep details (just like the good old days)
This time you wont find the 'agent encode' command working, use the 'encode.bat' file to encode the passwords eg. encode The_password
Add the agent using Topology manager and relate it to a context.
This will start the agent successfully. But the moment you close the command prompt window or try to exit, it will terminate the batch script and your agent will fail.
To create a service of ODI agent in the newer versions refer to the following link
With ODI using Weblogic to create agent services in the new version, things have become tricky.
If you have skipped master repository creation step while installing, the agent name that you give while installing ODI never shows up automatically in the 'Physical Architecture' tab in Topology, though you can see a batch file created with name 'agent_AGENT_NAME.bat' in the 'C:\oracle\product\11.1.1\Oracle_ODI_1\oracledi\agent\bin' folder and running this batch file directly will give you nothing but an error. You have to modify and run the odiparams.bat file before running the agent file.
Modifying the odiparams.bat file : File is located in the path mentioned above. Search for the below lines
REM #
REM # Repository Connection Information
REM #
set ODI_MASTER_DRIVER=oracle.jdbc.OracleDriver
set ODI_MASTER_URL=jdbc:oracle:thin:@localhost:1521:XE
set ODI_MASTER_USER=MASTER
set ODI_MASTER_ENCODED_PASS=a7yXZz0C1gPf2GxKzUNPxEJMp
REM #
REM # User credentials for agent startup program
REM #
set ODI_SUPERVISOR=SUPERVISOR
set ODI_SUPERVISOR_ENCODED_PASS=a7yabVOzj7C5oY503v.Ei6xKy
REM #
REM # User credentials for ODI tools
REM #
set ODI_USER=%ODI_SUPERVISOR%
set ODI_ENCODED_PASS=%ODI_SUPERVISOR_ENCODED_PASS%
REM #
REM # Work Repository Name
REM #
set ODI_SECU_WORK_REP=WORK
The text highlighted in yellow needs to be changed as per your Master Rep and Work rep details (just like the good old days)
This time you wont find the 'agent encode' command working, use the 'encode.bat' file to encode the passwords eg. encode The_password
Add the agent using Topology manager and relate it to a context.
This will start the agent successfully. But the moment you close the command prompt window or try to exit, it will terminate the batch script and your agent will fail.
To create a service of ODI agent in the newer versions refer to the following link
https://blogs.oracle.com/dataintegration/entry/running_odi_11gr1_standalone_a
I tried this on my laptop and it worked till the time I didn't shut down my machine. Since then the service has not started once, though I feel redoing the steps mentioned above will solve the problem. I wont be doing that since its not necessary when we can use OPMN to create agent services. Read the next blog post to find out ...
I tried this on my laptop and it worked till the time I didn't shut down my machine. Since then the service has not started once, though I feel redoing the steps mentioned above will solve the problem. I wont be doing that since its not necessary when we can use OPMN to create agent services. Read the next blog post to find out ...
No comments:
Post a Comment