In this lab, you perform the steps needed to deploy and configure the ODI Java EE Agent,Enterprise Manager11g, and ODI Console plug-in to an existing WLS domain. You use Enterprise Manager 11g and ODI Console to access your ODI objects.
1. Deploy and configure the ODI Java EE agent, Enterprise Manager, and ODI Console with the existing WebLogic domain.
2. Connect to the WebLogic Server and managed server, odi_server1.
3. Use Enterprise Manager to administer ODI.
4. Use ODI Console to explore the ODI environment.
Your Tasks:
1. Deploy and configure the ODI Java EE agent and Enterprise Manager on the existing WebLogic domain, ODI-DOMAIN.
Note: This domain was precreated for this practice.
a. In Topology Navigator, open Physical architecture and then create a new ODI Agent.Name this agent OracleDIAgent. Set the port to 8002 and Host to localhost. Verify
that the Web application context is set to oraclediagent, as shown below. Save your new physical agent.
Note: The agent name is case-sensitive! Use the exact name OracleDIAgent, as shown in the following screen.
b. In the Logical architecture, create a new logical agent with the same name as your new physical agent, OracleDIAgent. Link this logical agent to the physical agent OracleDIAgent in all three contexts, as shown below.
c. Extend the WebLogic server domain ODI-DOMAIN with the ODI agent application.
d. To deploy and configure domains with WLS, you start the config.bat file from the ODI Home Install directory – C:\Oracle\Middleware\Oracle_ODI1\common\bin. Start the command shell and change directory to
C:\Oracle\Middleware\Oracle_ODI1\common\bin. Execute the command config, which starts the Configuration Wizard.
e. Select Extend an Existing WebLogic Domain, and then click Next.
f.Select the WebLogic domain directory ODI-DOMAIN, as shown below. Click Next.
g. In the screen that follows, select Oracle Data Integrator – Agent – 11.1.1.1 (Oracle JRF will then also be selected; leave this option selected). Select the Oracle Enterprise Manger Plugin For ODI – 11.1.1.0, which will also include the Oracle Enterprise Manager – 11.1.1.0. Also select Oracle Data Integrator-Console-11.1.1.0.
Click Next. In the screen that follows, click OK to replace the existing component.
h. In the next screen, accept the default application location. Click Next.
i. The wizard will set up the ODI repository connection within the domain server. During the wizard configuration, the repository connection information must be supplied. Click the check boxes next to ODI Master schema, and next to ODI Work schema. Configure the JDBC component schema as shown in the following table. Click Next.
j. Verify that the test was successful (if not, correct any connectivity settings). Click Next.
k. In the next screen, select Managed Servers, Clusters and Machines. Click Next.
l. Set Listen port to 8002 for managed server odi_server1. Click Next.
m. In the Configure Clusters screen, click Next.
n. In the Configure Machines screen, click Next.
o. The Assign Servers to Machines screen will already have the odi_server1 assigned to localODImachine. Click Next.
p. Review the Configuration Summary, and then click Extend. When the domain is created, click Done.
2. Connect to the WebLogic server and managed server odi_server1.
a. In the command shell, change directory to the directory of the WLS Home -C:\Oracle\Middleware\user_projects\domains\ODI-DOMAIN\bin. Execute the startweblogic command.
b. Security must be set up for the JAVA EE application to have access to the ODI repository. The entry will be created within the credential store, which will allow the JAVA EE Agent to authenticate itself to be able to use the required resources. This
user should be a user that is already set up in the ODI Security. In this practice, we use user SUPERVISOR. To do this, you execute Web Logic Scripting Tool (WLST), connect to our running Admin server and add the credential store. To start WLST, in
the new command window, change directory to the WLS_HOME common bin -C:\Oracle\Middleware\oracle_common\common\bin, and then execute the command wlst.
c. To connect to the running Admin server, execute the following command: connect('weblogic','welcome1','t3://localhost:7002')
d. Execute the following command to add the correct credential store for ODI Supervisor:createCred(map="oracle.odi.credmap", key="SUPERVISOR",user="SUPERVISOR", password="SUNOPSIS", desc="ODI SUPERVISOR Credential").Also execute the command to add the correct credential store for the domain ODIDOMAIN:
createCred(map="oracle.odi.credmap", key="ODI-DOMAIN",
user="weblogic", password="welcome1", desc="ODI-DOMAIN
Credential").To exit WLST, execute the command exit().
Note: All commands are case-sensitive! You can copy commands from the text file
19-2.txt provided in the c:\LABS\text folder.
Note: During run time, the JAVA EE Agent will access this credential store authentication.
1. Deploy and configure the ODI Java EE agent, Enterprise Manager, and ODI Console with the existing WebLogic domain.
2. Connect to the WebLogic Server and managed server, odi_server1.
3. Use Enterprise Manager to administer ODI.
4. Use ODI Console to explore the ODI environment.
Your Tasks:
1. Deploy and configure the ODI Java EE agent and Enterprise Manager on the existing WebLogic domain, ODI-DOMAIN.
Note: This domain was precreated for this practice.
a. In Topology Navigator, open Physical architecture and then create a new ODI Agent.Name this agent OracleDIAgent. Set the port to 8002 and Host to localhost. Verify
that the Web application context is set to oraclediagent, as shown below. Save your new physical agent.
Note: The agent name is case-sensitive! Use the exact name OracleDIAgent, as shown in the following screen.
b. In the Logical architecture, create a new logical agent with the same name as your new physical agent, OracleDIAgent. Link this logical agent to the physical agent OracleDIAgent in all three contexts, as shown below.
c. Extend the WebLogic server domain ODI-DOMAIN with the ODI agent application.
d. To deploy and configure domains with WLS, you start the config.bat file from the ODI Home Install directory – C:\Oracle\Middleware\Oracle_ODI1\common\bin. Start the command shell and change directory to
C:\Oracle\Middleware\Oracle_ODI1\common\bin. Execute the command config, which starts the Configuration Wizard.
e. Select Extend an Existing WebLogic Domain, and then click Next.
f.Select the WebLogic domain directory ODI-DOMAIN, as shown below. Click Next.g. In the screen that follows, select Oracle Data Integrator – Agent – 11.1.1.1 (Oracle JRF will then also be selected; leave this option selected). Select the Oracle Enterprise Manger Plugin For ODI – 11.1.1.0, which will also include the Oracle Enterprise Manager – 11.1.1.0. Also select Oracle Data Integrator-Console-11.1.1.0.
Click Next. In the screen that follows, click OK to replace the existing component.
h. In the next screen, accept the default application location. Click Next.
i. The wizard will set up the ODI repository connection within the domain server. During the wizard configuration, the repository connection information must be supplied. Click the check boxes next to ODI Master schema, and next to ODI Work schema. Configure the JDBC component schema as shown in the following table. Click Next.
j. Verify that the test was successful (if not, correct any connectivity settings). Click Next.
k. In the next screen, select Managed Servers, Clusters and Machines. Click Next.
l. Set Listen port to 8002 for managed server odi_server1. Click Next.
m. In the Configure Clusters screen, click Next.
n. In the Configure Machines screen, click Next.
o. The Assign Servers to Machines screen will already have the odi_server1 assigned to localODImachine. Click Next.
p. Review the Configuration Summary, and then click Extend. When the domain is created, click Done.
2. Connect to the WebLogic server and managed server odi_server1.
a. In the command shell, change directory to the directory of the WLS Home -C:\Oracle\Middleware\user_projects\domains\ODI-DOMAIN\bin. Execute the startweblogic command.
b. Security must be set up for the JAVA EE application to have access to the ODI repository. The entry will be created within the credential store, which will allow the JAVA EE Agent to authenticate itself to be able to use the required resources. This
user should be a user that is already set up in the ODI Security. In this practice, we use user SUPERVISOR. To do this, you execute Web Logic Scripting Tool (WLST), connect to our running Admin server and add the credential store. To start WLST, in
the new command window, change directory to the WLS_HOME common bin -C:\Oracle\Middleware\oracle_common\common\bin, and then execute the command wlst.
c. To connect to the running Admin server, execute the following command: connect('weblogic','welcome1','t3://localhost:7002')
d. Execute the following command to add the correct credential store for ODI Supervisor:createCred(map="oracle.odi.credmap", key="SUPERVISOR",user="SUPERVISOR", password="SUNOPSIS", desc="ODI SUPERVISOR Credential").Also execute the command to add the correct credential store for the domain ODIDOMAIN:
createCred(map="oracle.odi.credmap", key="ODI-DOMAIN",
user="weblogic", password="welcome1", desc="ODI-DOMAIN
Credential").To exit WLST, execute the command exit().
Note: All commands are case-sensitive! You can copy commands from the text file
19-2.txt provided in the c:\LABS\text folder.
Note: During run time, the JAVA EE Agent will access this credential store authentication.
No comments:
Post a Comment