j2ee agent

28
Deploy and configure the Enterprise Manager Plugin on the existing WebLogic domain, ODI-DOMAIN. You should have created the WebLogic server domain ODI-DOMAIN, deployed and configured ODI JEE agent with this domain. Now you need to deply and configure the Enterprise Manager plugin on this existing WebLogic server domain, ODI-DOMAIN. 1 . Open the Command Prompt window. Change directory to: <WLS-HOME>\ common\bin (for example: C:\oracle\Middleware\Oracle_ODI1\ common\bin). Execute config command. The Configuration Wizard starts. 2. In the Welcome screen, select: Extend an existing WebLogic domain. Click Next. In the screen that follows, select the domain ODI-DOMAIN, as shown on the screenshot. Click Next.

Upload: chowdary

Post on 10-Jul-2016

248 views

Category:

Documents


8 download

DESCRIPTION

ODI Agents

TRANSCRIPT

Page 1: J2EE Agent

Deploy and configure the Enterprise Manager Plugin on the existing WebLogic domain, ODI-DOMAIN.

You should have created the WebLogic server domain ODI-DOMAIN, deployed and configured ODI JEE agent with this domain. Now you need to deply and configure the Enterprise Manager plugin on this existing WebLogic server domain, ODI-DOMAIN.

1 . Open the Command Prompt window. Change directory to: <WLS-HOME>\common\bin (for example: C:\oracle\Middleware\Oracle_ODI1\common\bin). Execute config command. The Configuration Wizard starts.

  2. In the Welcome screen, select: Extend an existing WebLogic domain. Click Next. In the

screen that follows, select the domain ODI-DOMAIN, as shown on the screenshot. Click Next.

Page 2: J2EE Agent
Page 3: J2EE Agent

3 . In the screen that follows, 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. Click Next. In the screen that follows, click OK to replace the existing component odi_server1, that was created earlier.

4 . In the next screen, accept the default application location. Click Next.

Page 4: J2EE Agent

5 . 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. Verify that the test was successful (if not, correct any connectivity settings). Click Next.

Database Connection (Master Repository) Parameter Value Vendor Oracle Driver Oracle’s driver (Thin) for Instance connections Master Schema Owner snpm1 Master Schema Password oracle1 Work Schema Owner snpw1Work Schema Password oracle1DBMS/Service orcl Host Name localhost Port 1521

Page 5: J2EE Agent

6 . In the next screen, select Managed Servers, Clusters and Machines. Click Next. Verify that

Page 6: J2EE Agent

Listen port is set to 8001 for managed server odi_server1. Click Next. In the Configure Clusters screen, click Next.

Page 7: J2EE Agent

7 . In the Configure Machines screen, click Next. The Assign Servers to Machines screen will already have the odi_server1 assigned to localODImachine. Click Next. Review the Configuration Summary, and then click Extend. When the domain is created, click Done.

Page 8: J2EE Agent
Page 9: J2EE Agent

Connecting to the WebLogic server and managed server odi_server1. Now that you have created and extended the WebLogic domain with the Enterprise Manager, you need to connect to WebLogic server and managed server odi_serevr1.

1. 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.

Page 10: J2EE Agent

  2 . To start managed server odi_server_1, change directory to WLS Home - C:\Oracle\Middleware\

user_projects\domains\ODI-DOMAIN\bin , and use the execute command:StartManagedWeblogic odi_server1. For Username, enter weblogic . For the password, enter welcome1 . Verify that your managed server is started in RUNNING mode.

Note: You created the credential store for ODI Supervisor and for the domain ODI-DOMAIN in the OBE: Deploying and Configuring the ODI Agent as Java EE Application.Note: All commands are case-sensitive! You can copy commands from the text file provided HERE.

Page 11: J2EE Agent

3 . If not started, start ODI Designer and connect to ODI Work repository (WORKREP1). For user SUPERVISOR, eneter password: SUNOPSIS. Open Topology Navigator, open Physical architecture and then open ODI JEE agent OracleDIAgent. Click Test icon to test connectivity of your ODI Java EE agent. Click OK. Close OracleDIAgent tab.

Page 12: J2EE Agent

Use Enterprise Manager to Administer ODI

Page 13: J2EE Agent

With Enterprise manager, explore your ODI environment and resources.

1. Start the browser and enter URL: http://localhost:7001/em . Log in to Enterprise Manager. For the user, enter weblogic . For the password, enter welcome1 . On the screen that follows, click Continue.

  2. With Enterprise Manager, a process and resources can be monitored and managed. You can

explore the deployed application by clicking on each link. You can see running processes, workload, log file information, and more. Drill down into ODI objects by expanding ODI > odiconsole > MASTER REPOSITORY in the left panel, as shown in the following screen.

Note: Your information may differ from the information provided on these screens.

Page 14: J2EE Agent

 

3 . Click MASTER REPOSITORY to view more details. Click the OracleDIAgent to see the Java EE agent information.

Page 15: J2EE Agent

4 . Click the localagent node to see details for the standalone agent.

Page 16: J2EE Agent

 

5 . Expand the Application Deployment node, and then click oraclediagent . View the WebLogic server application deployment information.

Page 17: J2EE Agent

Use ODI Console to Explore ODI Environment With ODI Console, explore your ODI environment.

1 . Start the browser and enter URL: http://localhost:8001/odiconsole to start the Oracle Data Integrator Console. To log in Work reposotory, enter SUPERVISOR for the user ID, and enter SUNOPSIS for the password. Expand the Design Time tab and then expand Projects, Models , and Topology as shown on the screenshot below.

Note: Your projects may differ from the information provided on these screens.

Page 18: J2EE Agent

2 . Select the Procedure-CRT-TBL project, and then click the View icon.

Page 19: J2EE Agent

3 . Click the First Folder link. Click the Procedures tab. Scroll-down, and then select procedure PRD-create-populate-table.

Page 20: J2EE Agent
Page 21: J2EE Agent

4 . Scroll-down and view details for this procedure.

5 . Expand: Runtime > Sessions > All Sessions. Select session PRD-create-populate table- 1001,

and then click View icon . Scroll-down and view execution information for selected session. Similarly, expand Topology > Agents > Physical Agents. View information for your agents. You may wish to continue exploration of your ODI environment.

Page 22: J2EE Agent

Note: To view information for each selected node, click icon.

Page 23: J2EE Agent
Page 24: J2EE Agent

6 . To stop managed WebLogic server odi_server1 and then WebLogic server, change directory to WLS Home - C:\Oracle\Middleware\user_projects\domains\ODI-DOMAIN\bin, and then execute the following command: stopManagedWebLogic odi_server1. For Username, enter weblogic . For the password, enter welcome1 .

To stop WebLogic server, execute the command: stopWebLogic.

Page 25: J2EE Agent