A common task that is performed by using ODI is to set up and install ODI Agent as a service.After the ODI scenarios are created, they can be scheduled and orchestrated by using an ODI Agent, which is a lightweight Java process that orchestrates the execution of ODI scenarios. In this practice, you create and execute an ODI Agent, which will be used in subsequent practices for orchestration of the execution of ODI objects. First you run encode <password> to generate an encrypted password.
You copy/paste that string into the odiparams.bat file that contains ODI agent parameters.
You then switch to ODI, and define a physical agent named localagent. Next, you define a logical agent also named localagent, mapping it to the same-named physical agent. You specify
the Global context as the context in which to make this particular mapping of logical to physical agents.
In the command window, you execute agent.bat to start the agent that you named localagent.
In ODI, you test connection to your newly created agent.
The directions on the following pages will take you through these activities:
1. Run encode oracle1 to generate an encrypted password string
2. Edit odiparams.bat, inserting the encrypted password
3. In ODI, define a physical agent named localagent
4. In ODI, define a logical agent named localagent, mapping it to the physical agent named localagent for the Global context
5. Execute agent.bat, to start an agent named localagent.
6. Verify connection to the newly created agent localagent in ODI
Your Tasks:
1. Before executing the agent.bat file to create the ODI Agent, you must run the encode password command to generate an encrypted password and paste it into the odiparams.bat parameter file. To do so, perform the following steps:
MS Windows and text editor
Navigate to the ODI_HOME directory, where ODI is installed and open the agent\bin subdirectory:
(C:\Oracle\Middleware\Oracle_ODI1\oracledi\agen t\bin). Navigate to the odiparams.bat file, right-click this file, and select Edit to open it with a text editor. Leave this editor
open. You will run a batch file from a Command window and return to this text editor to copy the results into the odiparams.bat file.
Explanation: You need to edit the odiparams.bat file to set the repository connection information for the ODI Agent to use. The password information is stored as an encrypted string. You will generate the encrypted string in a Command window.
(C:\Oracle\Middleware\Oracle_ODI1\oracledi\agen t\bin). Navigate to the odiparams.bat file, right-click this file, and select Edit to open it with a text editor. Leave this editor
open. You will run a batch file from a Command window and return to this text editor to copy the results into the odiparams.bat file.
Explanation: You need to edit the odiparams.bat file to set the repository connection information for the ODI Agent to use. The password information is stored as an encrypted string. You will generate the encrypted string in a Command window.
Command Prompt
Leave the text editor open, and open the Command window
(Start -> Run -> cmd). Change the directory to the
ODI_HOME\agent\bin directory:
C:\Oracle\Middleware\Oracle_ODI1\oracledi\agent\bin
(Start -> Run -> cmd). Change the directory to the
ODI_HOME\agent\bin directory:
C:\Oracle\Middleware\Oracle_ODI1\oracledi\agent\bin
To generate the encrypted password string, you will be using
the agent command, encode <password>. Because your
password is the word “oracle1”, enter and execute the following command in the Command window:
encode oracle1 Keep the Command window open, as you will be returning to it after editing the odiparams.bat file.
the agent command, encode <password>. Because your
password is the word “oracle1”, enter and execute the following command in the Command window:
encode oracle1 Keep the Command window open, as you will be returning to it after editing the odiparams.bat file.
Command Prompt and text editor
Copy the generated, encrypted password from the Command
window (from the Command window’s pull-down menu, select Edit > Mark, then highlight the password with your mouse) and insert it into the odiparams.bat file as the value for the ODI_MASTER_ENCODED_PASS parameter. Verify and, if necessary, edit settings for other parameters from the following table, save the odiparams.bat file, and then close it. The agent’s connectivity is now set up.
Parameter Value
ODI_MASTER_DRIVER oracle.jdbc.OracleDriver
ODI_MASTER_URL jdbc:oracle:thin:@localhost:1521:orcl
ODI_MASTER_USER DEV_ODI_REPO
ODI_MASTER_ENCODE
D_PASS
Insert your encoded password.
ODI_SECU_WORK_REP WORKREP
ODI_SUPRVISOR_ECO
DED_PASS
Leave the default value.
ODI_USER Leave the default value.
ODI_ENCODED_PASS Leave the default value.
ODI_JAVA_HOME C:\jdk1.6.0_18
Note DEV_ODI_REPO is an RDBMS schema/user (Oracle 11g) for the Master repository. It was precreated for this and subsequent practices.
Work Repository name is WORKREP.
Because each time that you encode the password, it receives
different values, your encoded password will differ from the one provided in the screen.
Do not change the default value of the ODI_USER and
ODI_ENCODED_PASS parameters. Those parameters were precoded during ODI installation.
window (from the Command window’s pull-down menu, select Edit > Mark, then highlight the password with your mouse) and insert it into the odiparams.bat file as the value for the ODI_MASTER_ENCODED_PASS parameter. Verify and, if necessary, edit settings for other parameters from the following table, save the odiparams.bat file, and then close it. The agent’s connectivity is now set up.
Parameter Value
ODI_MASTER_DRIVER oracle.jdbc.OracleDriver
ODI_MASTER_URL jdbc:oracle:thin:@localhost:1521:orcl
ODI_MASTER_USER DEV_ODI_REPO
ODI_MASTER_ENCODE
D_PASS
Insert your encoded password.
ODI_SECU_WORK_REP WORKREP
ODI_SUPRVISOR_ECO
DED_PASS
Leave the default value.
ODI_USER Leave the default value.
ODI_ENCODED_PASS Leave the default value.
ODI_JAVA_HOME C:\jdk1.6.0_18
Note DEV_ODI_REPO is an RDBMS schema/user (Oracle 11g) for the Master repository. It was precreated for this and subsequent practices.
Work Repository name is WORKREP.
Because each time that you encode the password, it receives
different values, your encoded password will differ from the one provided in the screen.
Do not change the default value of the ODI_USER and
ODI_ENCODED_PASS parameters. Those parameters were precoded during ODI installation.
a.
b.
c.
d.
2. Now that you have generated an encoded password and pasted it into the odiparams.bat file, you need to create the ODI physical and logical agent definitions. To create these ODI agent definitions, perform the following steps:
a. MS Windows ODI Login
If it is not started, start Oracle Data Integrator. Click “Connect To Repository”. Select DEV_ODI_REPO from the Login Name drop-down list. Click OK.
b. Topology navigator Click Topology Navigator tab. In Topology Navigator, select the Physical Architecture panel. Right-click the Agents node.Select New Agent.
c. Agent: localagent Fill in the following fields:
Name: localagent
Host: Network name or IP address of the machine the agent has been launched on. Verify that this parameter is set to localhost.
Port: Listening port used by the agent. By default, this port is 20910. Leave the default value.
Web Application Context: Name of the Web application corresponding to the Java EE agent deployed on an application server. For standalone agents, this field should be
set to oraclediagent.Set Maximum number of sessions supported by this agent to 250. Click the Save button.
d. Topology Navigator Local Agent: New
Now you have to insert a logical agent in Logical Architecture, and map it to the newly created Physical agent. Click the Logical Architecture tab. Right-click Agents and select New Logical Agent. On the screen that follows, set the Name to “localagent.”
Set Physical Agents to localagent. From the file menu, click Save, and then close the Logical Agent tab.
a.
b.
c.
d.
3. Now that you have created the agent and defined the ODI physical and logical agents, you can start the agent directly from the command line.
Command Prompt
Switch back to the Command window you left open at the ODI_HOME\agent\bin directory
(C:\Oracle\Middleware\Oracle_ODI1\oracledi\agent\bin). Execute the agent.bat file by using the following
command:
agent -NAME=localagent
Services The agent is now starting. Verify that ODI Agent is successfully
started. Minimize the window Command Prompt – agent-
NAME=localagent.
Note: This command window should remain open during all labs.
Oracle Data
Integrator
In ODI, click the Test icon to verify connection of the agent
localagent.You successfully created and connect to ODI agent. Close thelocalagent tab
. Also, close the Messages -Log tab . 
a.
b.
c.
d.
b.
c.
d.
2. Now that you have generated an encoded password and pasted it into the odiparams.bat file, you need to create the ODI physical and logical agent definitions. To create these ODI agent definitions, perform the following steps:
a. MS Windows ODI Login
If it is not started, start Oracle Data Integrator. Click “Connect To Repository”. Select DEV_ODI_REPO from the Login Name drop-down list. Click OK.
b. Topology navigator Click Topology Navigator tab. In Topology Navigator, select the Physical Architecture panel. Right-click the Agents node.Select New Agent.
c. Agent: localagent Fill in the following fields:
Name: localagent
Host: Network name or IP address of the machine the agent has been launched on. Verify that this parameter is set to localhost.
Port: Listening port used by the agent. By default, this port is 20910. Leave the default value.
Web Application Context: Name of the Web application corresponding to the Java EE agent deployed on an application server. For standalone agents, this field should be
set to oraclediagent.Set Maximum number of sessions supported by this agent to 250. Click the Save button.
d. Topology Navigator Local Agent: New
Now you have to insert a logical agent in Logical Architecture, and map it to the newly created Physical agent. Click the Logical Architecture tab. Right-click Agents and select New Logical Agent. On the screen that follows, set the Name to “localagent.”
Set Physical Agents to localagent. From the file menu, click Save, and then close the Logical Agent tab.
a.
b.
c.
d.
3. Now that you have created the agent and defined the ODI physical and logical agents, you can start the agent directly from the command line.
Command Prompt
Switch back to the Command window you left open at the ODI_HOME\agent\bin directory
(C:\Oracle\Middleware\Oracle_ODI1\oracledi\agent\bin). Execute the agent.bat file by using the following
command:
agent -NAME=localagent
Services The agent is now starting. Verify that ODI Agent is successfully
started. Minimize the window Command Prompt – agent-
NAME=localagent.
Note: This command window should remain open during all labs.
Oracle Data
Integrator
In ODI, click the Test icon to verify connection of the agent
localagent.You successfully created and connect to ODI agent. Close thelocalagent tab
. Also, close the Messages -Log tab . a.
b.
c.
d.
No comments:
Post a Comment