Introduction to Dynamic Service Creation
You can use the Dynamic Service Creation to check in a third-party WSDL, validate the WSDL, and generate all the service definitions and service configurations that are required for a new service that can be used to access a third-party Web service.
You can use these dynamically created services in business processes. The application as a Web services consumer supports either a default configuration with HTTP transport, or a manual configuration with either HTTP or HTTPS transport.
The following figure illustrates the Dynamic Service Creation process:
Transport Options
- A legacy configuration that calls services and adapters at the API level, and is restricted to use of HTTP for transport.
- A transport-independent implementation that restricts the role
of dynamic services to generate the SOAP message from the checked-in
WSDL file allowing use of either HTTP or HTTPS adapter.
This option requires manual configuration in the Graphical Process Modeler (GPM) of the SOA Inbound and SOA Outbound message processing services, (optionally) the SOA Inbound and SOA Outbound Security services, and the adapters used for transport.
As a comparison, the GPM configuration of the two transport options could appear as follows. This is an example with the default HTTP transport configuration:
The following is an example of a GPM configuration for a transport-independent (HTTP/HTTPS) configuration:
For more information about the Dynamic Service Creation process, refer to the Dynamic Services documentation.