Invoking ODI Scenario using Web Services Invoking ODI ... · Invoking ODI Scenario using Web...

Invoking ODI Scenario using Web Services

25-Aug-15 Korada V Pavan Kumar

Invoking ODI Scenario using Web Service

Overview: This Document explains the step by step process of using the ODI Package tool (Invoke web

service) OdiInvokeWebService to invoke ODI scenarios, load plans as well as get the status from it

Introduction: The Oracle Data Integrator Public Web Services feature allows you to run a scenario from a web

service The OdiInvokeWebService tool invokes a web service using the HTTP or HTTPS protocol and is

able to write the returned response to an XML file, which can be an XML payload or a full-formed SOAP message including a SOAP header and body. The OdiInvokeWebService tool invokes a specific operation on a port of a web service whose description file (WSDL) URL is provided. If this operation requires a SOAP request, it is provided either in a request file or in the tool command. The response of the web service request is written to an XML file that can be used in Oracle Data Integrator.

Note: If the web service operation is one-way and does not return any response, no response file is generated.

Assumptions: Assuming that the resource having the below skills

Should have knowledge on ODI Should have knowledge in ODI Topology for connecting to the source and

target systems. Should have knowledge in creating an interface in ODI. Should have knowledge in creating a package in ODI



Creating an Interface and Generating a Scenario Here is the step by step approach with a brief description along with the respective Screenshots.

For Invoking a Scenario, we need to have a scenario and which can be generated from an interface/package.

Step 1: Create a new project [Project Name: DEMO] Step 2: Import the Necessary knowledge Modules into project

Step 3: Import the respective source and target tables into models

Source: EMP; Target: TRAINING_TARGET



Step 4: Create an interface by right click on the interface tab

Step 5: Provide the necessary details like interface name, Context, etc... As shown in below.

Step 6: Drag and Drop the source and target tables into the work bench of ODI, perform the mapping of the columns and perform any transformations like Filter, expression or Lookup (if Needed) as shown in below.



Step 7: Provide the necessary KM and properties in the flow tab of mapping

Step 8: Save the interface. Step 9: Right click on the interface and click “Generate Scenario” for generating a scenario for this interface.



Step 10: Provide the Name of the scenario and Version number

Now the Interface has been created and also the scenario has been generated for this particular interface



Invoking ODI Scenario using Web Service

Below is the step by step approach for invoking a scenario using an ODI WebService Step1: Pre requisite Check ***Note: Please ensure that you have started the localagent. To verify this, use below URL in your browser. If you see wsdl screen then we are good to go...

http://localhost:20910/oraclediagent/OdiInvoke?wsdl

Step 2: Create a new package [DEMO]

http://localhost:20910/oraclediagent/OdiInvoke?wsdl



Step 3: Drag and drop the ODI invoke webservice event from the internet panel into ODI Package workbench.

Step 4: Click on the advanced tab as shown below.



Step 5: Copy the URL in the WSDL location as shown in below and click the Globe symbol which is highlighted below

Step 6: Once you click on that symbol, you will be able to see the advanced tab as shown in below.

The operations displaying above are the list of operations available in the WSDL



Step 7: Move to respective step as per your requirement. In this demo we will move to InvokeStartScen Step as we need to start a scenario using

the webservice.

Step 8: Click on the Editor tab for providing necessary details as shown below.



Step 9: As our interface/scenario doesn’t contain any variables, we can go ahead and delete the variables section as shown in below.

Step 10: Providing the necessary details like ODI username, Password, Work repository name in the credentials section

As we need to execute the scenario, providing the details related to scenario like scenario name, version, context, session name etc… under the Request section as shown in below.



Step 11: Click on the globe symbol (Invoke web service) high lightened below to get the scenario executed and also for viewing the response of the scenario.

Step 12: Once it is done we could able to see the session number as shown in below under the response tab section.



Step 13: In the similar way we can also see that the scenario/ interface has been executed as per the operator log shown below.

Step 14: we can also save this package and execute as a package for invoking the interface/scenario as a package execution as shown below.

We can able to see both the package and also the interface/scenario executed in the operator as shown below.



Step 15: In addition to this, if required we can store the response file (Session number) In a xml file as shown below. Providing the XML response file storage path

Checking the response file generated in the specified path



Opening and checking the data in the response file and comparing it with the execution session number as shown in below.

In this way, we can invoke a scenario using the ODI web service and also we can capture the response into an xml file (if required) for auditing or for downstream applications.

Invoking ODI Scenario using Web Services Invoking ODI ... · Invoking ODI Scenario using Web...

Documents

Transcript of Invoking ODI Scenario using Web Services Invoking ODI ... · Invoking ODI Scenario using Web...