ODI Training
ODI Training
ODI Training
Hands-On Workshop
Version 2.2
Copyright 2007
Table of Contents
LAB 1: SOFTWARE INSTALLATION AND SETUP ................................................ 4
Download the Software (Pre-Requisite).......................................................................... 4
Install Oracle Data Integrator........................................................................................ 4
Install Oracle XE ........................................................................................................... 7
Setup the ODI Metadata Repositories............................................................................. 8
DATA INTEGRATION SCENARIO: PERMIT PROCESSING .............................. 19
LAB 2: CAPTURING METADATA........................................................................... 22
Configure Data Servers in the ODI Topology Manager................................................ 22
Define Data Models in the ODI Designer..................................................................... 27
LAB 3: SIMPLE DATA INTEGRATION .................................................................. 34
Create an Integration Project in the ODI Designer ...................................................... 34
Import the Knowledge Modules .................................................................................... 35
Create the Interface to Load the Applicant Data........................................................... 36
Define Basic Transformations ...................................................................................... 38
Define a Filter.............................................................................................................. 39
Execute the Interface.................................................................................................... 40
Monitor the Execution .................................................................................................. 41
LAB 4: HETEROGENEOUS DATA INTEGRATION AND VALIDATION .......... 45
Create the Interface to Load the Permit Data ............................................................... 45
Integrate Heterogeneous Sources ................................................................................. 47
Create Data Validation Rules....................................................................................... 50
Execute the Interface.................................................................................................... 53
Monitor the Execution .................................................................................................. 53
LAB 5: CHANGE DATA CAPTURE ......................................................................... 56
Import the Journalization Knowledge Module .............................................................. 56
Enable Journalization .................................................................................................. 56
Using Journalized Data in an Interface ........................................................................ 58
LAB 6: ORCHESTRATE INTERFACES INTO PACKAGES ................................. 61
Create the Permit Integration Package......................................................................... 61
Archive the Input File................................................................................................... 63
Execute the Package..................................................................................................... 65
LAB 7: SETUP AGENT .............................................................................................. 66
Setup ODI Parameters for Agent .................................................................................. 66
Create a Physical Agent ............................................................................................... 67
Create a Logical Agent................................................................................................. 69
Execute the Agent (use command line) ......................................................................... 70
LAB 8: CREATE AND SCHEDULE AN ODI SCENARIO ...................................... 71
Create an ODI Scenario............................................................................................... 71
Schedule a New Scenario within Oracle Data Integrator.............................................. 72
APPENDIX A: IMPORTING THE ODI REPOSITORY SCHEMAS...................... 77
APPENDIX B: RESETTING THE PERMIT APPLICATION SCENARIO............ 78
Confidential
Page 2 of 79
Confidential
Page 3 of 79
Confidential
Page 4 of 79
Confidential
Page 5 of 79
Confidential
Page 6 of 79
Install Oracle XE
The Oracle Database 10g Express Edition (Oracle XE) is an entry-level, small-footprint
database based on the Oracle Database 10g Release 2 code base that's free to develop, deploy,
and distribute; fast to download; and simple to administer.
For this workshop, we will use Oracle XE as the database engine for ODI. To install Oracle
XE, perform the following steps:
1. Double-click the OracleXE.exe that was downloaded earlier to launch the installer.
2. Click Next.
3. Review and Accept the Licensing Agreement. Click Next.
4. Accept the Default Destination Location (c:\OracleXE). Click Next.
5. Enter a password for the SYS and SYSTEM accounts. Recommended to just use
oracle for the purposes of this workshop. Click Next.
6. From the Summary Screen, click Install.
7. From the InstallShield Wizard Complete window, check the Launch the Database
homepage. Then click Finish.
8. You should see the Oracle XE Database Login page from your browser. Do not close
the browser at this point.
Confidential
Page 7 of 79
The Master Repository is where all the information on the topology of resources,
security and version management of projects and data models is stored. Only one
master repository is required for typical Oracle Data Integrator installations.
The Work Repository is where the information on data models, projects, and their use
is stored. A work repository can be linked with only one master repository for version
management purposes.
These repositories are stored in a relational database accessible in client/server mode from the
different Oracle Data Integrator modules. For this workshop, we will use the Oracle XE
database to store these repositories.
Note: For this workshop, you may skip the creation of the master and work repositories
by running a script that will import the repository schemas into Oracle XE. If you wish
to do so, please refer to Appendix A: Importing the ODI Repository Schemas.
Confidential
Page 8 of 79
2. From the Database Home Page, select the Administration module, and from the menu
select Database Users > Create User.
3. From the Create Data User page, create a user called master and set the passwords to
master. Check the DBA role under User Privileges.
Confidential
Page 9 of 79
4. From the Manage Database Users page, click the Create button to create another user
called workrep1 and set the passwords to workrep1. Again, check the DBA role under
User Privileges.
5. Verify that the master and workrep1 users have been created as shown:
Confidential
Page 10 of 79
Confidential
Page 11 of 79
8. Click the OK and OK again on the wizard to start the repository creation.
9. The Command Window will display log messages during the creation of the repository.
After successful repository creation, you should see the following:
Confidential
Page 12 of 79
For the Oracle Data Integrator Connection use the default username
SUPERVISOR and password SUNOPSIS. This is the default admin user for the
master repository.
For the Database Connection use information you entered earlier for the master
repository connection (Username/Password: master).
Click Test to make sure the connection is valid and Click OK.
Confidential
Page 13 of 79
4. Back in the Security Repository Connection, use the ODI Master Repository and
login with the user SUPERVISOR and password SUNOPSIS. This will launch the
Oracle Data Integrator Topology Manager connected to your Master Repository in the
Oracle XE database.
Confidential
Page 14 of 79
3. On the Data Server Definition tab, enter the name WORKREP1 and select Oracle
from the Technology list. Under the connection, enter the username workrep1 and
password workrep1.
4. Click on the JDBC tab, enter oracle.jdbc.driver.OracleDriver for the JDBC Driver
and enter jdbc:oracle:thin:@localhost:1521:XE for the JDBC URL. You can also
use the browse button to select the values.
5. Click Test to make sure the connection is valid and Click OK. When prompted for an
Agent, select Local (No Agent).
6. Click OK.
7. The Work Repository dialog box will appear. For the ID, enter 0 and for the name,
enter WORKREP1 and click OK.
Confidential
Page 15 of 79
Confidential
Page 16 of 79
1. For the Oracle Data Integrator Connection use Login Name WORKREP1 with
Confidential
Page 17 of 79
You are now ready to use the Work Repository called WORKREP1 for the other sections of
this Workshop.
Confidential
Page 18 of 79
-------------------------------------------------------------------------------------------
-------
Lo
ad
Permit Request
Flat File
Integration
BGCHECK
Transformation
ad
Lo
CDC
Background
Check
Data
Data Validation
Permit Application
RDBMS
In this workshop, you will focus on building out this data integration scenario. You will use
the Oracle Data Integrator to do the following:
1. Capture the metadata information of these systems into ODIs metadata repository:
Permit Request flat-file
Permit Application RDBMS
Background Check RDBMS
2. Filter, transform and load applicant data into the Permit Application.
3. Merge permit requests with the background check data.
4. Create data validation rules and capture validation errors.
Confidential
Page 19 of 79
5. Use change-data-capture (CDC) to process changed data from the background check
system
6. Arrange these tasks in a data integration package with error notifications and file archival
after successful completion.
Before continuing, please perform the following tasks:
1. Open up the ODIWorkshop-MyFiles.zip file from the workshop DVD.
2. Unzip the file to your C:\ drive. This will create a directory called C:\MyFiles. This
includes the Permit Request flat file (permit_batch.csv in the CSV subdirectory) and
database scripts that will be utilized during the workshop.
3. Start a command prompt window. Go to Windows Start > Run and enter cmd.
4. From the command prompt, navigate to c:\MyFiles and enter the following commands:
sqlplus system/oracle
(Note: replace oracle with the password you specified during installation of
OracleXE.)
This script creates the Permit Application and Background Check RDBMS schemas.
6. From the Command Prompt, enter the following:
LoadBGData
Confidential
Page 20 of 79
Confidential
Page 21 of 79
3. To define technologies, click the Physical Architecture tab (the 1st tab) from the
Topology Manager as shown:
Confidential
Page 22 of 79
Lets first capture the Permit Applications Oracle database that will be used as the target.
4. From the list of Technologies, right-click on the Oracle technology and select Insert
Data Server.
5. From the Data Server Definition Tab, enter the name PERMIT_APP. On the connection,
enter the username PERMIT_APP and password PERMIT_APP.
Confidential
Page 23 of 79
6. Click on the JDBC tab. For the Driver, click the browse button
and select the
Oracle JDBC Driver from the list. This should populate the text box with
oracle.jdbc.driver.OracleDriver.
7. For the URL, enter jdbc:oracle:thin:@localhost:1521:XE.
8. Click OK.
9. In the Physical Schema dialog box, select PERMIT_APP for the Directory (Schema)
and PERMIT_APP_WORK for the Directory (Work Schema) as shown:
The Schema is where the actual tables are located, while the Work Schema is where ODI
will create temporary objects such as staging and integration tables.
Confidential
Page 24 of 79
10. Click on the Context tab. Click the new context button and type in
PERMIT_APP_TARGET as the Logical Schema.
BGCHECK
BGCHECK
BGCHECK
oracle.jdbc.driver.OracleDriver
jdbc:oracle:thin:@localhost:1521:XE
BGCHECK
BGCHECK_WORK
BGCHECK_SRC
Important Note: The BGCHECK schema actually resides on the same database instance as
the PERMIT_APP. For this workshop, we are simulating that the BGCHECK is a totally
separate database server, which is why we are configuring it as a separate data server. In
real-life scenarios, if your database schemas belong to the same instance, the best practice is
to just use the same data server for these schemas.
Next, lets configure the Permit File source:
13. From the list of Technologies, right-click on the File and select Insert Data Server
Confidential
Page 25 of 79
14. From the Data Server Definition Tab, enter the name PERMIT_FILE.
15. Click on the JDBC tab. For the driver, click the
icon and select Sunopsis File JDBC
Driver. For the URL, enter jdbc:snps:dbfile, as shown below:
Confidential
Page 26 of 79
18. Click on the Context tab. Click the new context button and type in PERMIT_SRC as the
Logical Schema.
3. Enter PERMIT_APP_MODEL for the model name. Select Oracle as the Technology
and PERMIT_APP_TARGET as the Logical Schema.
Confidential
Page 27 of 79
4. Click the Reverse tab and select the context called Global.
5. Click the Selective Reverse tab and check the check boxes for Selective Reverse and
Objects to Reverse. Youll see the APPLICANTS, PERMITS and PERMIT_TYPES
tables from the list. Click the Reverse button to start the Reverse-Engineering Process.
Confidential
Page 28 of 79
6. You should now see the APPLICANTS, PERMITS and PERMIT_TYPES under your
data models with their corresponding columns and constraints.
Confidential
Page 29 of 79
2. Enter BGCHECK_MODEL for the model name. Select Oracle as the Technology and
BGCHECK_SRC as the Logical Schema.
3. Repeat the Reverse-Engineering process done earlier to capture the BGCHECK table.
2. Enter PERMIT_SRC_MODEL for the model name. Select File as the Technology and
PERMIT_SRC as the Logical Schema.
Confidential
Page 30 of 79
Note: If you do not see the PERMIT_SRC in the Logical Schema combo box (just see
FILE_GENERIC_SRC), check the Topology again that you put the PERMIT_SRC in the File
technology
3. Click the Reverse tab and select the context called Global.
4. Click OK. (For Files, we do not perform Selective Reverse since each file is reverseengineered individually.)
5. From the Models window, right-click on PERMIT_SRC_MODEL and select Insert
Data Store.
Confidential
Page 31 of 79
6. Enter PERMIT_CSV for the name and click the Browse icon to locate the
permit_batch.csv file.
7. Click the Files tab and select Delimited for the File Format, 1 for the Heading and
comma (,) for the Other Field Separator:
Confidential
Page 32 of 79
8. Click the Columns tab and click the Reverse button to generate the column names based
on the file header as shown:
9. Click OK.
You have successfully captured the sources and target metadata for the data integration
scenarios in the next labs.
Confidential
Page 33 of 79
Confidential
Page 34 of 79
5. You will now see an Integration Project 1 project in your project list. Click the + sign
on the left to expand and you will see a default folder called First Folder. Double-Click
the First Folder and rename this to Permit Integration as shown:
3. From the Import Knowledge Modules File Import Directory, enter or browse for the
following path:
Confidential
Page 35 of 79
c:\oracle\product\10.1.3.4\oracledi\impexp
(Replace with your ODI installation home directory if you used a different one.)
4. From the list of files(s) to import, select LKM File to SQL, as shown.
5. Repeat the same steps for the other knowledge modules listed above. You should see the
imported knowledge modules as shown:
Confidential
Page 36 of 79
5. Drag the PERMIT_CSV data store from the PERMIT_SRC_MODEL and drop it on
the Source section.
6. Drag the APPLICANTS data store from the PERMIT_APP_MODEL and drop it on the
Target section.
Confidential
Page 37 of 79
7. You will be asked if you want to perform an automatic mapping. Select Yes.
8. The mapping is based on exact field names so all the fields except the APPLICANT_ID
will be automatically mapped.
(Note that you will see a warning for the Phone and SSN mappings, indicating that the
target column is smaller than the source column. This can be ignored.)
9. To manually map the APPLICANT_ID, click the empty mapping field of the
APPLICANT_ID column from the Target Data Store. This will bring up the
APPLICANT_IDs mapping implementation below (which is empty). Drag the Appl_Id
column from the PERMIT_CSV source node to the mapping implementation text area as
shown:
Page 38 of 79
1. Click the mapping field of the APPLICANTS FIRST column from the Target Data
Store. This will bring up the mapping implementation below, which shows the
MAPPING as PER.First.
2. ODI is based on an E-L-T architecture that utilizes the database engines transformation
capabilities. For this transformation, we will use Oracles INITCAP function. To do this,
we need to specify to execute the transformation in the Staging Area rather than the
source. Select the option Execute on Staging Area below the mapping implementation.
3. Enter the mapping implementation as: INITCAP(PER.First) as shown below.
Optionally, you can click on the
icon on the right to launch the expression editor and
select the INITCAP function under the list of String functions.
4. Repeat the same transformation for the last name column (APPLICANTS.LAST).
Define a Filter
Now lets add a filter to get the permits with permit ID greater than 4008000.
1. From the sources window, drag the Permit_ID column outside the PERMIT_CSV node
to create a filter.
2. Click on the filter icon to show the filter implementation expression below and enter the
expression PER.Permit_ID > 4008000.
Confidential
Page 39 of 79
Notice that only the source and target nodes are show. There is no separate
transformation engine. All the transformation and filtering is done at the target
database where the data is processed and loaded using a set-based operation rather
than processing it row-by-row in a separate engine. This approach yields much
higher performance and shows the benefits of the E-L-T Architecture.
2. Click on the source node and the target node to see the available options provided by the
knowledge modules.
Confidential
Page 40 of 79
Notice that all we had to for this interface was drag the source to the target and specify
the transformations and filters, which are all part of the integration rules. The
knowledge modules take care of all the underlying technical details such as creating the
staging and error tables, committing, cleaning up temporary objects, and performing
flow controls, among others. These are the benefits of Declarative Design.
You can also use the Start Menu: Oracle > Oracle Data Integrator > Operator.
2. Drill down on All Executions and find the Load Application Data session. Click and
expand the second Load Application Data step. You will see the loading, integration and
control steps implemented by the knowledge modules executed by ODI.
Confidential
Page 41 of 79
3. On the left hand window, scroll to the right to view the various statistics for each step.
Youll see that 18000 rows have been staged and 10000 rows have been inserted into the
target table.
4. Double-click Step 7: Integration Load Applicant Data - Insert flow into I$ table.
This is the step that integrates the source data in the staging area.
5. Click on the Description tab and examine the SQL generated with the transformations
and filters that you defined.
Confidential
Page 42 of 79
6. Lastly, go back to ODI Designer, click on the Diagram tab for the Load Applicant Data
interface and right click the Target Data Store - APPLICANTS header as shown:
Confidential
Page 43 of 79
Confidential
Page 44 of 79
Confidential
Page 45 of 79
6. Drag the PERMIT_CSV data store from the PERMIT_SRC_MODEL and drop it on
the Source section.
7. Drag the PERMITS data store from the PERMIT_APP_MODEL and drop it on the
Target section.
8. You will be asked if you want to perform an automatic mapping. Select Yes.
9. Like earlier, manually map the Appl_Id column from the PERMIT_CSV source to the
APPLICANT_ID target column.
10. Add the TO_DATE conversion function to the PER.Application_Date and
PER.Request_Date target columns to convert the string data into a date.
Make sure you specify to execute this transformation in the Staging Area.
11. For the LOAD_DATE column, use the Oracle SYSDATE function to record the current
date.
Confidential
Page 46 of 79
12. Like earlier, create a filter for Permit_ID using the expression PER.Permit_ID >
4008000.
13. You should now have something like:
2. Switch back to the models tab and drag the BGCHECK data store from the
BGCHECK_MODEL and drop it on the Source section.
Confidential
Page 47 of 79
3. Drag the SSN column from PERMIT_CSV to the SSN column in BGCHECK to create
the join.
4. Map the BGCHECKs RESULT column from the source to the PERMITs
BACKGROUND_CHECK column in the target.
5. Map the BGCHECKs REASON column from the source to the PERMITs
BACKGROUND_CHECK_MSG column in the target.
6. We need to only accept background check data only for the current year. Create a filter
on the BGCHECKs DATE_CHECKED column using the expression:
BGCHECK.DATE_CHECKED > TO_DATE('01-JAN-07')
We also need to lookup the correct permit type codes from the Permit Applications
PERMIT_TYPES table because the permit data file only contains the permit type name. To
do this, we need to include the PERMIT_TYPES table as a source.
Confidential
Page 48 of 79
7. Drag the PERMIT_TYPES data store from the PERMIT_APP_MODEL and drop it on
the Source section.
8. You will be asked if you want to perform an automatic mapping. Select Yes. This will
automatically create the mapping for the PERMIT_TYPE_CODE.
9. Drag the Permit_Type column from PERMIT_CSV to the PERMIT_TYPE_NAME
column in PERMIT_TYPES to create the join.
10. You should now have the following:
Note:
- Because Technology File does not support all functions like RDBMS, make sure that
you set the Execute on for the following fields on Staging Area instead of
Source: APPLICATION_DATE; REQUEST_DATE; APPLICANT_ID; LOAD_DATE
- Make sure that you have used TO_DATE for APPLICATION_DATE, REQUEST_DATE
- You should use: PERMIT_ID = TO_CHAR(PER.Permit_ID) if you receive an mis-datatype
error
11. Click on the Flow tab and observe how and where the transformations and merges take
place:
Notice that the joins are done in the staging area. The sources get staged first and
then joined in the staging area for best performance.
Confidential
Page 49 of 79
Notice that the filter for BGCHECK occurs on the source since BGCHECK is a
relational source that can perform filtering logic. It will be more optimal to perform
filtering on the source when possible to minimize the data coming in. Since the
PERMIT_CSV is a file, it does not have an engine to perform filtering and so it
utilizes the staging area for applying the filters.
We will now add 2 additional constraints that will contain our validation rules. Lets create a
rule for making sure that each permit application has a valid reason.
Confidential
Page 50 of 79
Name:
Type:
Where:
Message:
Reason is Required
Oracle Data Integrator Constraint
PERMITS.REQUEST_REASON IS NOT NULL
Optionally, use the Expression Editor
to build the expression.
Hint: Use the Test Query icon
to validate your expression.
There has to be a reason
Note you can also create "NOT NULL" rules at the column level by checking the
"mandatory" check box. The advantage of utilizing conditions as shown above is that error
messages can be customized.
4. Click Ok.
Now lets create a rule to make sure only valid and completed background check results are
accepted.
5. Right-click the Constraints folder and select Insert Condition.
6. Enter the following information:
Name:
Type:
Where:
Message:
Confidential
Page 51 of 79
7. Click Ok.
8. Go back to the Load Permit Data Interface and click the Controls tab. Verify that your
validation rules are listed under constraints and that they are enabled.
Confidential
Page 52 of 79
4. Optional: Try to locate the step that contains the SQL logic for integrating the 3 data
sources.
5. Go back to ODI Designer. From the Models tab on the left, right-click on the PERMITS
data store from the PERMIT_APP_MODEL and select View Data.
Confidential
Page 53 of 79
7. To view the captured errors, right-click on the PERMITS data store from the
PERMIT_APP_MODEL and select Controls > Errors.
8. You should see the errors that have been captured and the corresponding error messages
as shown below:
Confidential
Page 54 of 79
You have successfully implemented an ODI interface that performs heterogonous data
integration and validation.
Confidential
Page 55 of 79
Enable Journalization
To enable journalization on the BGCHECK data store, perform the following steps:
1. Go to the Models tab and double-Click the BGCHECK_MODEL and click on the
Journalization tab.
2. For the Journalizing JKM, select JKM Oracle Simple.Integration Project 1
Confidential
Page 56 of 79
3. Expand the BGCHECK_MODEL, right-click on the BGCHECK data store and select
Change Data Capture > Add to CDC.
4. Next, right-click on the BGCHECK data store and select Change Data Capture >
Subscriber > Subscribe.
5. When asked to Select your Subscriber(s), enter SUNOPSIS and click the
the ODI subscriber to the list as shown. Click OK.
icon to add
6. Click OK in the execution dialog box. You will be informed that the session has started.
Click OK again.
7. Right-click on the BGCHECK data store and select Change Data Capture > Start
Confidential
Page 57 of 79
Journal.
8. When asked to Select your Subscriber(s), select SUNOPSIS from the list and click OK.
9. Click OK in the execution dialog box. You will be informed that the session has started.
Click OK again.
10. Go to the ODI Operator and verify that the 2 jobs for BGCHECK completed successfully.
Optionally, examine the steps under each job. These are the journalization setup work
performed by the Journalizing Knowledge Module (JKM).
Confidential
Page 58 of 79
3. Notice the BGCHECK table contains several rows that have already been processed
earlier. This is because the interface is not set up to use the journalized data.
4. To use the journalized data in the interface, click on the BGCHECK source node header.
From the source configuration below the diagram, mark the Journalized Data only
option as shown below.
5. Notice that a new filter has been created on the BGCHECK source. Click the filter icon to
see the filter expression.
6. Try right clicking on the BGCHECK source node again and select Data. There are no
new rows to process.
7. Lets try adding some new rows. Start a command prompt and enter the following
command:
sqlplus BGDEMO/BGDEMO
8. At the SQL Prompt, enter the following:
Confidential
Page 59 of 79
@c:\myfiles\newBGData.sql
9. This will insert 10 new background check results into the background check table.
10. Go back to Load Permit Data interface in ODI Designer and view the BGCHECK source
data again. This time you will see 10 new rows waiting to be processed.
11. Execute the interface and verify through the ODI Operator that only10 new rows have
been added and not the entire data set.
Confidential
Page 60 of 79
4. Click the Diagram tab. You can drag and drop interfaces that you want to orchestrate as
part of the package in this diagram.
5. Drag the Load Applicant Data interface into the diagram.
6. Drag the Load Permit Data interface into the diagram.
7. Click the OK connector icon
8. Drag the mouse from the Load Applicant Data step to the Load Permit Data step to
create the connection between the 2. This will make Load Permit Data run after Load
Applicant Data completes successfully.
Confidential
Page 61 of 79
13. Drag the mouse from the Load Applicant Data step to the Error Notification step to
create an exception path. This will make the Error Notification step run if the Load
Applicant Data throws an exception.
14. Create the same exception path for Load Permit Data.
Confidential
Page 62 of 79
Confidential
Page 63 of 79
from Load
Name:
Filename:
Target File:
Archive File
C:\myfiles\CSV\permit_batch.csv
C:\myfiles\archive\permit_batch_#CurrentTimestamp.csv
Note: #CurrentTimestamp will get the value from the variable at
runtime to append it to the file name.
Confidential
Page 64 of 79
Confidential
Page 65 of 79
When the password is generated, copy the generated encrypted password for later usage
Note that, the ODI_ENCODED_PASS is set to the encoded password for SUNOPSIS by
default; this does not need to be modified unless the SUPERVISOR password has been
changed.
2. Open the odiparams.bat with any text editor, and edit the following parameters:
set
set
set
set
set
set
set
ODI_SECU_DRIVER=oracle.jdbc.driver.OracleDriver
ODI_SECU_URL=jdbc:oracle:thin:@localhost:1521:xe
ODI_SECU_USER=master
ODI_SECU_ENCODED_PASS=<your encrypted password>
ODI_SECU_WORK_REP=WORKREP1
ODI_USER=SUPERVISOR
ODI_ENCODED_PASS=LELKIELGLJMDLKMGHEHJDBGBGFDGGH
Note: You can copy values from Designer Connection Dialog, except the encrypted passwords
3. Save this file
With this information, the agent could be executed directly from the command line or
installed as the service to run in the background
Confidential
Page 66 of 79
Localagent
Localhost
20910
4. Launch the agent: Start menu > Programs > Oracle > Oracle Data Integrator > Agent
The following screen should apprear
Confidential
Page 67 of 79
Confidential
Page 68 of 79
Confidential
Localagent
Localagent
Page 69 of 79
4. Click OK
The Physical and Logical Agent are now setup successfully. The ODI Agent can now be used
to execute ODI objects
4. Check the numbers of scheduled executions is equal to your scheduled scenarios. If you
do not run the lab 8 below, the number should be zero (0).
You have now successfully completed the lab, which walked through the steps that are needed
to setup the ODI Agent. The lab also walked through the steps to execute an ODI object on
the newly setup ODI Agent.
Confidential
Page 70 of 79
4. Name the scenario Run Permit Integration and set the version to 001
Confidential
Page 71 of 79
The scenario has now been successfully created, you can now execute the scenario directly,
use the scenario within a package or schedule the package within ODI.
To schedule a scenario an Agent must be setup. To setup an ODI Agent, see the lab 7 Setup
an ODI Agent
Confidential
Page 72 of 79
Confidential
Page 73 of 79
5. Select tab Execution Cycle to set the execution frequency and contraints when failure
Set Repetition:
Many times: Interval between Repetitions
Constraints:
Number of Attempts on Failure
Stop Executive After
: 1 minutes
: 10
: 5 minutes
Confidential
Page 74 of 79
10. Click OK
11. Click Scheduling Information. The following screen appears
Confidential
Page 75 of 79
You have now successfully scheduled a scenario with an agent scheduler, and the scenario
was executed by the agent successfully.
Congratulations! You have completed the Oracle Data Integrator Hands-On Workshop
for Public Sector. For more learning material on ODI go to:
http://www.oracle.com/technology/products/oracle-data-integrator/index.html
Confidential
Page 76 of 79
This command drops and recreates a new version of the ODI Master and Work Repositories.
Confidential
Page 77 of 79
2. Make sure journalization is disabled for the Load Permit Data interface.
a. Open the Load Permit Data interface from the Projects and go to the diagram.
b. Click on the BGCHECK source node header. From the source configuration
below the diagram, unmark the Journalized Data only option as shown below.
Confidential
Page 78 of 79
3. Start a command prompt window. Go to Windows Start > Run and enter cmd.
4. From the command prompt, navigate to c:\MyFiles and enter the following commands:
resetPermitScenario.cmd
This command truncates the Permit Application target tables, removes the new data inserted
into the Background Check database during the CDC lab, clears the ODI Error tables and
moves the Permit Request File back to its original location.
Confidential
Page 79 of 79