Using the OdiInvokeWebService Tool

Working with Web Services in Oracle Data Integrator 15-7 ■ XML Charset -RESPONSE_XML_ENCODING: The name of the character encoding to write into the XML file. ■ Java Charset -RESPONSE_FILE_CHARSET: The name of the character encoding used when writing the file. Refer to Section A.5.22, OdiInvokeWebService for more information on these parameters.

15.4.3 Web Service Invocation in Integration Flows

Calling a Web Service using the OdiInvokeWebService tool To call a Web Service:

1. Create an OdiInvokeWebService tool step in a package, or right-click a datastore

and select Test Web Service in the contextual menu. 2. Fill in the location of the WSDL. You can use either: ■ A URL for a WSDL that has been deployed to a server for example: http:host:8080servicesWSCustomer?wsdl ■ A local file location for example: c:DataServicesWSCustomer.wsdl

3. Choose a Port, if more than one is available.

4. Choose an Operation from the list on the left.

5. In the SOAP Editor, enter the web service payload. The OdiInvokeWebService tool

supports two web service request formats: the XML body of the SOAP request only or the full-formed SOAP envelope, including the SOAP header and body.

6. Optional Click Remove blank optional elements to delete optional request

parameters which have not been specified. Some Web Services treat blank elements as invalid.

7. Click Invoke Web Service to immediately invoke the Web Service. The response is

shown in right pane of the SOAP Editor. 8. If you are creating an OdiInvokeWebService tool step, define the response file parameters. Note: The result file parameters are only taken into account at run-time. No result file is generated when clicking Invoke Web Service . Note: Input format request and output format response are independant. Oracle Data Integrator recognizes the input message format automatically and writes the response according to the RESPONSE_FILE_FORMAT default is XML. However, in the Advanced editor the request file format determines the response file format. If you test the invocation using a XML payload message, the response will be XML payload. If you test using a full-formed SOAP message, the response will be a full-formed SOAP message. How to generate a web service request file with Oracle Data Integrator is covered in Generating the Request File . 15-8 Oracle Fusion Middleware Developers Guide for Oracle Data Integrator

9. From the File menu, select Save.

Processing the Response File When using the OdiInvokeWebService tool to call a web service, the response is written to an XML file. Processing this XML file can be done with Oracle Data Integrator, using the following guidelines:

1. Invoke the web service once and use the Export Response XSD option to export

the XML schema. 2. Create an XML model for the response file, based on this XML schema file and reverse-engineer the XSD to have your model structure. 3. You can now process the information from your responses using regular Oracle Data Integrator interfaces sourcing for the XML technology. Refer to the Connectivity and Modules Guide for Oracle Data Integrator for more information on XML file processing. Oracle Data Integrator provides the OdiXMLConcat and OdiXMLSplit tools for processing the web service response. Refer to the XML section of the Appendix A.4, ODI Tools per Category for details on how to use these tools. Generating the Request File There are several ways to create a request file: ■ Create the request directly in the SOAP Editor on the Advanced tab of the OdiInvokeWebService tool. The possible format is XML. ■ Use the XML driver, similarly to what is performed for processing the response file. If generating a request file using the XML driver, the request is not a full SOAP but a simplified XML format. Use the SOAP editor for generating a template request. ■ Use an external request file that has been previously generated with ODI. The possible formats are XML and SOAP. ■ Create a SOAP request. To generate a SOAP request, you have to use a third-party tool such as, for example, the HTTP Analyzer provided by JDeveloper. See Using the HTTP Analyzer in the Oracle SOA Suite Developers Guide for more information. To call a web service with a SOAP request, perform the standard procedure as described in Calling a Web Service using the OdiInvokeWebService tool and perform the following steps for creating the web service request in SOAP format: 1. Create the SOAP request in the third-party tool. 2. Copy the SOAP request and paste the entire SOAP message into the Source tab of the SOAP Editor in ODI Studio. 3. Optionally, edit the request. Note: Each XML file is defined as a model in Oracle Data Integrator. When using XML file processing for the request or response file, model will be created for each request or response file. It is recommended to use model folders to arrange them. See Section 17.2, Organizing Models with Folders for more information. Working with Web Services in Oracle Data Integrator 15-9 Note that the web service response will be in SOAP format. Using the Binding Mechanism for Requests It is possible to use the Binding mechanism when using a web service call in a Procedure. With this method, it is possible to call a web service for each row returned by a query, parameterizing the request based on the row’s values. Refer to Binding Source and Target Data for more information. 15-10 Oracle Fusion Middleware Developers Guide for Oracle Data Integrator 16 Working with Oracle Data Quality Products 16-1 16 Working with Oracle Data Quality Products This chapter describes how to work with Data Quality Products in Oracle Data Integrator. This chapter includes the following sections: ■ Section 16.1, Introduction to Oracle Data Quality Products ■ Section 16.2, The Data Quality Process

16.1 Introduction to Oracle Data Quality Products

Oracle Data Profiling and Oracle Data Quality for Data Integrator also referred to as Oracle Data Quality Products extend the inline Data Quality features of Oracle Data Integrator to provide more advanced data governance capabilities. A complete Data Quality system includes data profiling, integrity and quality: ■ Profiling makes possible data investigation and quality assessment. It allows business users to get a clear picture of their data quality challenges, to monitor and track the quality of their data over time. Profiling is handled by Oracle Data Profiling . It allows business users to assess the quality of their data through metrics, to discover or infer rules based on this data, and finally to monitor over time the evolution of the data quality. ■ Integrity control is essential in ensuring the overall consistency of the data in your information systems applications. Application data is not always valid for the constraints and declarative rules imposed by the information system. You may, for instance, find orders with no customer, or order lines with no product, and so forth. Oracle Data Integrator provides built-in working environment to detect these constraint violation and store them for recycling or reporting purposes. Static and Flow checks in Oracle Data Integrator are integrity checks. ■ Quality includes integrity and extends to more complex quality processing. A rule-based engine apply data quality standards as part of an integration process to cleanse, standardize, enrich, match and de-duplicate any type of data, including names and addresses. Oracle Data Quality for Data Integrator places data quality as well as name and address cleansing at the heart of the enterprise integration strategy.

16.2 The Data Quality Process

The data quality process described in this section uses Oracle Data Quality products to profile and cleanse data extracted from systems using Oracle Data Integrator. The