There are a couple of enhancements added in outbound Web
Services invocation support in Oracle Data Integrator (ODI) 12.2.1. You can now
configure the Web Service end point URLs in the Topology definition instead of
hard coding it in the ODI Tools parameters. Logical Schema of such topology
configuration can be then used directly in the OdiInvokeWebService tool parameters. Now ODI also allows you to
invoke a WebService that is protected by OWSM policies and register those OWSM
policies as part of Physical Schema definition.
To register the Web Services definition a new technology,
“SOAP Web Service”, is added in the Topology where you create the Data Server
for the Web Service and register its WSDL URL.
The Services, Ports, user credentials, OWSM policies for the
endpoint service from the WSDL are configured as the Physical Schemas.
You can then create a Logical schema for it and bind it with
Physical Schema through Context mapping. Such logical schema and context can be
specified in the OdiInvokeWebService
tool instead of hard coding Web Service URL and other parameters.
To learn more about the Topology
Configurations for Web Services, there is an Oracle by Example tutorial
available providing step by step instructions on using the feature: http://www.oracle.com/webfolder/technetwork/tutorials/obe/fmw/odi/odi_12c/odi12c_newfeatures/ascii_files.html#section3s1
Additionally the new features introduced in Oracle Data
Integrator 12.2.1 are also documented in our New
Features white paper.