odi 12c standalone agent - · pdf filestarted oracle database services and components...
TRANSCRIPT
2/1/2016 ODI 12c Standalone Agent
http://www.oracle.com/webfolder/technetwork/tutorials/obe/fmw/odi/odi_12c/odi12c_agent/odi12c_agent.html 1/25
ODI 12c Standalone Agent
Purpose
This tutorial walks you through the steps that are needed to use Oracle Data Integrator Studio(ODI Studio) graphical tools to create a standalone agent (that is, no WLS is installed) to support(among other things) scheduling of procedures. Once created and configured, the agent runswithout the Studio GUI.
Time to Complete
Approximately 40 minutes.
Introduction
A common task that is performed using ODI is to set up and install an ODI Agent. After the ODIscenarios are created, they can be scheduled and orchestrated using an ODI Agent, which is alightweight Java process that orchestrates the execution of ODI scenarios. This tutorial walks youthrough the steps that are needed to set up and install the ODI Agent.
This is the third in a series of four OBEs in the Oracle Data Integrator 12c: Getting Started(https://apex.oracle.com/pls/apex/f?p=44785:24:15503233161396::::P24_CONTENT_ID,P24_PREV_PAGE:7952,24) series.
Scenario
Linda works as a database administrator for Example Enterprise Corp (http://www.example.com). InExample Enterprise, Linda is responsible for performing database management and integrationtasks on various resources within the organization. In particular, Linda is responsible for dataloading, transformation, and validation. To begin working on her projects, Linda created the newMaster repository and Work repository. Linda also created the project and the procedure to create arelational table and populate it with data. Now Linda needs to set up and install an ODI Agent as aservice. This agent will be used in the next OBE to schedule a later run of the procedure. Agents areused for many other tasks in addition to scheduling.
Hardware and Software Requirements
Before You Begin.
2/1/2016 ODI 12c Standalone Agent
http://www.oracle.com/webfolder/technetwork/tutorials/obe/fmw/odi/odi_12c/odi12c_agent/odi12c_agent.html 2/25
The following is a list of software requirements:
A supported operating system (the OS shown here is 64bit Oracle Enterprise Linux release 6.7(Santiago), other versions such as Windows are supported as well)
Oracle Database (the version shown here is Enterprise Edition 12.1.0.2.0, other versions aresupported as well)
Oracle Data Integrator (ODI) 12c (the version shown here is 12.2.1) installer executed twice toinstall the following components:
first as ODI Standalone to install ODI Standalone Agent
second as ODI Enterprise to install ODI Studio
Ideally these two ODIs are on two different hosts, but it could be on the same host, as long as theyare in different Middleware Home directories.
The following is a list of OPTIONAL software:
Oracle SQL Developer 12c (included with Database 12c install)
Note: This OBE presumes that WebLogic Server (WLS) is not present in the Middleware home forODI Standalone, but is present in the Middleware home for ODI Enterprise. If you do have WLSinstalled and licensed, and want to only install ODI once, then see alternate OBE here(https://apex.oracle.com/pls/apex/f?p=44785:24:12669762339885::NO:24:P24_CONTENT_ID%2CP24_PREV_PAGE:8290%2C16).
Prerequisites
Before starting this tutorial, you should have:
Started Oracle Database services and components such as the Listener.
A Database user with DBA role privileges such as the SYS or SYSTEM account.
Installed the HR schema included in the Oracle Database. The Sample Schemas Installation Guideis part of the Oracle Database documentation set, and is also available online at:http://otn.oracle.com (http://otn.oracle.com).
Already installed and configured ODI Master and Work repositories (instructions on how to do thisare contained in the first (https://apex.oracle.com/pls/apex/f?p=44785:24:15503233161396::NO:24:P24_CONTENT_ID,P24_PREV_PAGE:7946,16) of fourOBEs in the Getting Started series).
Already created an ODI project and mapping for a flat file to a relational table (instructions on howto do this are contained in the second (https://apex.oracle.com/pls/apex/f?p=44785:24:15503233161396::NO:24:P24_CONTENT_ID,P24_PREV_PAGE:7947,16) of fourOBEs in the Getting Started series).
1. Creating the Domain for the Standalone Agent
2/1/2016 ODI 12c Standalone Agent
http://www.oracle.com/webfolder/technetwork/tutorials/obe/fmw/odi/odi_12c/odi12c_agent/odi12c_agent.html 3/25
The agent in this OBE runs in a domain that is very similar to (but not dependent on) WebLogicServer (WLS) domains. The GUI Configuration Wizard uses templates to determine whichcomponents are needed to support the function of the agent. There are three possible kinds ofagents:
completely standalone agent (no WLS installed. This OBE uses this kind of agent.)
standalone collocated agent (WLS is installed, but is not being used. The agent is started as itsown binary.)
JEE agent (WLS installed and used. The domain, admin server, managed servers, nodemanagers, and so on are started in the normal WLS way. The agent is one of many possible JEEapps running in the domain. )
To create the standalone agent requires ODI Studio running (so that you can configure the agent),and a Standalone ODI deployment that has no user interface. When you see OS prompts below, bemindful of whether they are my_ent_host (Enterprise) where the Studio GUI is, or my_std_host(Standalone) where the database is. To create the domain using CAM, perform the following steps:
1.1 Basic Configuration
To create a domain for the agent, start the Fusion Middleware (FMW) Configuration Wizard on the host with ODI Standaloneinstalled. This is the Common Administration Model (CAM), though you may not see that term used anywhere. It bears a strikingresemblance to the WebLogic Server (WLS) domain configurator.
OS Prompt
[myuser@my_std_host ~]$ cd $ODI_HOME/common/bin
[myuser@my_std_host bin]$ pwd
/u01/app/oracle/Middleware/Oracle_Home/odi/common/bin
[myuser@my_std_host bin]$ ll
total 20
rwxrx 1 oracle oinstall 483 Feb 6 09:14 clonedunpack.sh
rwxrx 1 oracle oinstall 471 Dec 19 2012 config.sh
rwxrx 1 oracle oinstall 467 Dec 19 2012 pack.sh
rwxrx 1 oracle oinstall 471 Dec 19 2012 unpack.sh
rwxrx 1 oracle oinstall 1748 Dec 19 2012 wlst.sh
[myuser@my_std_host bin]$ ./config.sh
Note that there are other different versions of config.sh in other FMW directories, but this is the one you want for creating anODI agent. The splash screen displays briefly.
2/1/2016 ODI 12c Standalone Agent
http://www.oracle.com/webfolder/technetwork/tutorials/obe/fmw/odi/odi_12c/odi12c_agent/odi12c_agent.html 4/25
For most of the nonAdvanced configuration, the defaults are adequate. On the Configuration Type panel, leave the defaults.
If you do not yet have a WLS domain, then the first one created will be called base_domain by default. You can rename it to
something such as odi_agent or mydomain99 , just make sure that it remains in
$FMW_HOME/user_projects/domains/ . If you already have a domain named base_domain , then you
cannot "create" another one, you would have to rename it to base_domain2 or something else, or you could Update anexisting domain. The particulars about updating an existing domain are outside the scope of this OBE, and are covered in the WLScurriculum.
2/1/2016 ODI 12c Standalone Agent
http://www.oracle.com/webfolder/technetwork/tutorials/obe/fmw/odi/odi_12c/odi12c_agent/odi12c_agent.html 5/25
Click Next to continue.
On the Templates panel, select Oracle Data Integrator Standalone Agent. It is “standalone” in the sense that it does not useWLS.
2/1/2016 ODI 12c Standalone Agent
http://www.oracle.com/webfolder/technetwork/tutorials/obe/fmw/odi/odi_12c/odi12c_agent/odi12c_agent.html 6/25
Click Next to continue.
On the JDK Selection panel, leave the defaults.
2/1/2016 ODI 12c Standalone Agent
http://www.oracle.com/webfolder/technetwork/tutorials/obe/fmw/odi/odi_12c/odi12c_agent/odi12c_agent.html 7/25
Click Next to continue.
On the Database Configuration Type panel, change the Service to the database service (not database instance), such asorcl.us.oracle.com . Change the Host Name to localhost , change the Schema Password to the password
for DEV_STB that you picked when you ran RCU.
2/1/2016 ODI 12c Standalone Agent
http://www.oracle.com/webfolder/technetwork/tutorials/obe/fmw/odi/odi_12c/odi12c_agent/odi12c_agent.html 8/25
Click Get RCU Configuration to continue, staying on this panel.
2/1/2016 ODI 12c Standalone Agent
http://www.oracle.com/webfolder/technetwork/tutorials/obe/fmw/odi/odi_12c/odi12c_agent/odi12c_agent.html 9/25
The Connection Result Log should end with Successfully Done. Click Next to continue.
On the JDBC Component Schema panel, leave the defaults.
2/1/2016 ODI 12c Standalone Agent
http://www.oracle.com/webfolder/technetwork/tutorials/obe/fmw/odi/odi_12c/odi12c_agent/odi12c_agent.html 10/25
Click Next to continue.
On the JDBC Component Schema Test panel, leave the defaults.
2/1/2016 ODI 12c Standalone Agent
http://www.oracle.com/webfolder/technetwork/tutorials/obe/fmw/odi/odi_12c/odi12c_agent/odi12c_agent.html 11/25
The Connection Result Log should end with Test Successful! Click Next to continue.
In summary, you have completed the first half, the basic part of the configuration. You mustcontinue with the second half, the advanced configuration.
1.2 Advanced Configuration
On the System Components panel, leave the defaults.
2/1/2016 ODI 12c Standalone Agent
http://www.oracle.com/webfolder/technetwork/tutorials/obe/fmw/odi/odi_12c/odi12c_agent/odi12c_agent.html 12/25
Click Next to continue.
On the ODI Server Configuration panel, make a note of the Port (you will need that number later), and change the SupervisorPassword to the password you picked when you ran RCU.
2/1/2016 ODI 12c Standalone Agent
http://www.oracle.com/webfolder/technetwork/tutorials/obe/fmw/odi/odi_12c/odi12c_agent/odi12c_agent.html 13/25
Click Next to continue.
On the Node Manager panel, you have to put in something for credentials, but it does not need to match anything else.
2/1/2016 ODI 12c Standalone Agent
http://www.oracle.com/webfolder/technetwork/tutorials/obe/fmw/odi/odi_12c/odi12c_agent/odi12c_agent.html 14/25
Click Next to continue.
On the Configuration Summary panel, leave the defaults.
2/1/2016 ODI 12c Standalone Agent
http://www.oracle.com/webfolder/technetwork/tutorials/obe/fmw/odi/odi_12c/odi12c_agent/odi12c_agent.html 15/25
Click Create to make the domain and continue.
On the Configuration Progress panel, there is nothing to do. Just make sure that it ends with the progress bar at 100%, and withthe message, “Domain Created Successfully!”
2/1/2016 ODI 12c Standalone Agent
http://www.oracle.com/webfolder/technetwork/tutorials/obe/fmw/odi/odi_12c/odi12c_agent/odi12c_agent.html 16/25
Click Next to continue.
On the Configuration Success panel, there is nothing to do.
2/1/2016 ODI 12c Standalone Agent
http://www.oracle.com/webfolder/technetwork/tutorials/obe/fmw/odi/odi_12c/odi12c_agent/odi12c_agent.html 17/25
Click Finish to end the Configuration Wizard and return to the OS prompt.
In summary, you completed both halves of the domain configuration. This created severaldirectories with configuration files and scripts.
The physical agent is a background OS process that communicates with ODI via TCP/IP ports. Tocreate the standalone agent requires ODI Studio running (so that you can configure the agent), anda Standalone ODI deployment that has no user interface. When you see OS prompts below, bemindful of whether they are my_ent_host (Enterprise) where the Studio GUI is, or my_std_host(Standalone) where the database is.
To create, start, and test the physical agent, perform the following steps:
2.1 Creating a Physical Agent
2. Creating a Physical Agent
2/1/2016 ODI 12c Standalone Agent
http://www.oracle.com/webfolder/technetwork/tutorials/obe/fmw/odi/odi_12c/odi12c_agent/odi12c_agent.html 18/25
Start ODI Studio by running odi.sh on the host with ODI Enterprise installed.
OS Prompt
[myuser@my_ent_host ~]$ cd $ODI_HOME/studio
[myuser@my_ent_host studio]$ pwd
/u01/app/oracle/Middleware/Oracle_Home/odi/studio
[myuser@my_ent_host studio]$ ./odi.sh
Oracle Fusion Data Integrator Studio 12c
Copyright (c) 1997, 2015, Oracle and/or its affiliates. All rights reserved.
The splash screen and progress bar displays briefly.
On the Designer or Topology tab, click Connect To Repository...
On the Enter Wallet Password dialog box, enter the password you chose when you installed ODI.
2/1/2016 ODI 12c Standalone Agent
http://www.oracle.com/webfolder/technetwork/tutorials/obe/fmw/odi/odi_12c/odi12c_agent/odi12c_agent.html 19/25
Click OK to continue.
On the Oracle Data Integrator Login dialog box, enter the Supervisor's password you chose when you installed ODI. It may be prepopulated for you.
Click OK to continue.
On the Topology tab, expand Physical Architecture, then expand Agents. Rightclick Agents and select New Agent.
An unnamed Agent panel opens on the right.
On the Agent panel, on the Definition tab, in Name, enter the name that matches the agent you created with the earlier domainwizard: OracleDIAgent1 .
In Port, enter the port that matches the agent you created with the earlier domain wizard: 20910 .
Verify that Host is correct. If you are doing everything on one host with different Middleware Home directories, then you can uselocalhost for host (likely you install ODI twice on the same host only for testing proofofconcept.) More likely in a productionenvironment you have two different hosts: one with ODI Standalone (that is the host that goes here), and the other host with Studio
2/1/2016 ODI 12c Standalone Agent
http://www.oracle.com/webfolder/technetwork/tutorials/obe/fmw/odi/odi_12c/odi12c_agent/odi12c_agent.html 20/25
(which is not the host for here).
Save your work by clicking , but do not close the panel. Leave the panel open.
You should now see the new agent display on the left under Topology > Physical Architecture > Agents.
In summary, you created the physical agent configuration for within ODI. This points to theexecutables created in the previous CAM steps.
2.2 Starting the Background Process
On the host with ODI Standalone installed, change to the directory of the domain that contains the binary files. Start the agent usingthe agent name from the domain. Leave that window running (perhaps minimized or sent to the back of the desktop.)
OS Prompt
2/1/2016 ODI 12c Standalone Agent
http://www.oracle.com/webfolder/technetwork/tutorials/obe/fmw/odi/odi_12c/odi12c_agent/odi12c_agent.html 21/25
[myuser@my_std_host ~]$ cd $FMW_HOME/user_projects/domains/base_domain/bin
[myuser@my_std_host bin]$ pwd
/u01/app/oracle/Middleware/Oracle_Home/user_projects/domains/base_domain/bin
[myuser@my_std_host bin]$ ls
agent.sh restartsession.sh startComponent.sh stopComponent.sh
agentstop.sh setODIDomainEnv.sh startloadplan.sh stoploadplan.sh
odi_credtool.sh setStartupEnv.sh startNodeManager.sh stopsession.sh
restartloadplan.sh startcmd.sh startscen.sh
[myuser@my_std_host bin]$ ./agent.sh NAME=OracleDIAgent1 PORT=20910
Note that this looks like a subset of a WebLogic Server (WLS) install. It is not a WLS install, but does use many of the samecomponents. The very first time you run this, you will get LOTS of output as Java initializes. Subsequent run times the messages willbe fewer.
OS Prompt
/u01/app/oracle/Middleware/Oracle_Home/odi/agent/internal/bin/commODIEnv.sh: line 111:
/u01/app/oracle/Middleware/Oracle_Home/odi/agent/../../wlserver/modules/com.oracle.weblogic.security.encryption_1.0.0.0.jar: Permission denied
/u01/app/oracle/Middleware/Oracle_Home/odi/agent/internal/bin/commODIEnv.sh: line 114:
/u01/app/oracle/Middleware/Oracle_Home/odi/agent/../../oracle_common/modules/com.oracle.webservices.orasaajapi_12.1.2.jar: Permission denied
/u01/app/oracle/Middleware/Oracle_Home/odi/agent/internal/bin/commODIEnv.sh: line 117:
/u01/app/oracle/Middleware/Oracle_Home/odi/agent/../../wlserver/server/lib/wlthint3client.jar: Permission denied
20130802 20:54:24.897 NOTIFICATION New data source:
[DEV_ODI_REPO/*******@jdbc:oracle:thin:@localhost:1521/ORCL.US.ORACLE.COM]
20130802 20:54:27.058 NOTIFICATION ODI1128 Agent OracleDIAgent1 is starting.
Container: STANDALONE. Agent Version: 12.1.2 11/07/2013. Port: 20910. JMX Port: 21910.
Allowing : 127.0.0.1,10.216.4.175,127.0.0.1
20130802 20:54:33.457 NOTIFICATION New data source:
[DEV_ODI_REPO/*******@jdbc:oracle:thin:@(description=(address=(host=localhost)(protocol=tcp)(port=1521))(connect_data=(service_name=ORCL.US.ORACLE.COM)(server=dedicated)))]
20130802 20:54:34.186 NOTIFICATION ODI1111 Agent OracleDIAgent1 started. Agent version: 12.1.2 11/07/2013. Port: 20910. JMX Port: 21910.
20130802 20:54:34.187 NOTIFICATION ODI1136 Starting Schedulers on Agent OracleDIAgent1.
20130802 20:54:35.678 NOTIFICATION ODI1137 Scheduler started for work repository workrep on Agent OracleDIAgent1.
You want to see at the bottom that the scheduler has started for the correct work repository.
In summary, you have started the external process associated with the ODI physical agent.
2.3 Testing the Physical Agent
2/1/2016 ODI 12c Standalone Agent
http://www.oracle.com/webfolder/technetwork/tutorials/obe/fmw/odi/odi_12c/odi12c_agent/odi12c_agent.html 22/25
You should have left the OracleDIAgent1 Agent panel open from step 2.1.4.
Click Test to test the agent now that the process is running outside of ODI.
The ODI Information dialog box should say, “Agent Test Successful.”
Click OK to continue. You may now close the OracleDIAgent1 tab.
In summary, you have configured and started a physical agent.
Most components in ODI have a physical and logical side to them. You already created the physicalagent with ports and names, the logical agent is much simpler and shorter.
3. Creating a Logical Agent
2/1/2016 ODI 12c Standalone Agent
http://www.oracle.com/webfolder/technetwork/tutorials/obe/fmw/odi/odi_12c/odi12c_agent/odi12c_agent.html 23/25
To create a logical agent that corresponds with the previous physical agent, perform the followingsteps:
3.1 Creating a Logical Agent
On the Topology tab, expand Logical Architecture, then expand Agents. Rightclick Agents and select New LogicalAgent.
An unnamed Logical Agent panel displays on the right.
On the Logical Agent panel, on the Definition tab, in Name, enter MyAgent . In the Physical Agents pulldown, selectOracleDIAgent1.
Save your work by clicking .
You should now see the new agent display on the left under Topology > Logical Architecture > Agents.
2/1/2016 ODI 12c Standalone Agent
http://www.oracle.com/webfolder/technetwork/tutorials/obe/fmw/odi/odi_12c/odi12c_agent/odi12c_agent.html 24/25
You can close all the open tabs on the right.
In summary, you created a logical agent to match the previous physical agent.
In this tutorial, you should have learned how to:
Use CAM to create a domain from a template for a standalone collocated agent
Use ODI Studio to create a physical agent
Start the physical agent background process from the OS prompt
Use ODI Studio to create a logical agent that corresponds to the physical agent
Resources
The following are conceptual or procedural Help topics relevant to the topic of this tutorial:
Online documentation, viewlets, samples, and OLN URLs on OTN:
Current version: here (http://docs.oracle.com/middleware/1221/odi/index.html)
Older versions: here (http://www.oracle.com/technetwork/middleware/dataintegrator/documentation/index.html)
The following specific courses:
D82167GC10 (http://placeholder) Oracle Data Integrator 12c: Integration and Administration (replaces D64974GC20 Oracle Data Integrator 11g: Integration and Administration Ed2)
D82171GC10 (http://placeholder) Oracle Data Integrator 12c: New Features
External Web sites for related information:
www.oracle.com/goto/odi (http://www.oracle.com/goto/odi)
Want to Learn More?
2/1/2016 ODI 12c Standalone Agent
http://www.oracle.com/webfolder/technetwork/tutorials/obe/fmw/odi/odi_12c/odi12c_agent/odi12c_agent.html 25/25
Copyright © 2015, Oracle and/or its affiliates. All rights reserved.
OTN Community Forums(https://forums.oracle.com/community/developer/english/business_intelligence/system_management_and_integration/data_integrator)
To learn more about Oracle Data Integrator 12c, refer to additional OBEs in the Oracle LearningLibrary (http://www.oracle.com/goto/oll), or on the ODI Studio Start Page.
Credits
Lead Curriculum Developer: Elio Bonazzi
Other Contributors: Viktor Tchemodanov, Alex Kotopoulis, Julien Testut
About Oracle (http://www.oracle.com/corporate/index.html) Contact Us (http://www.oracle.com/us/corporate/contact/index.html)Legal Notices (http://www.oracle.com/us/legal/index.html) Terms of Use (http://www.oracle.com/us/legal/terms/index.html)Your Privacy Rights (http://www.oracle.com/us/legal/privacy/index.html)