This topic applies only to the IBM Business Automation Workflow Advanced configuration.

Pure dynamic invocation

Edit online
Draft comment:
This topic only applies to BAW, and is located in the BAW repository. Last updated on 2025-03-13 12:15
Pure dynamic invocation calls a service without needing an import in the mediation module.

No additional information is required apart from the details in the message. An example is where the intended service is identified by a name, which is looked up at run time. Pure dynamic invocation assumes a specific set of configuration parameters.

Web services and SCA URLs are supported, but other types are not because of their need for additional configuration that is provided by an import binding.

The default for pure dynamic invocation using a Web Service binding is SOAP 1.1, using HTTP or JMS as specified in the target URL. Pure dynamic invocation is also supported for SOAP 1.2 when using HTTP by specifying an appropriate value for the bindingType field of the EPR. Pure dynamic invocation using SOAP 1.2 and JMS is not supported.

The default for pure dynamic invocation using a Web Service binding is SOAP 1.1, using HTTP or JMS as specified by the target URL. Pure dynamic invocation is also supported for SOAP 1.2 with HTTP.
  • For pure dynamic invocation using SOAP 1.1 and HTTP or JMS, the binding type should either be unset or it should be set to one of the following values:
    • Using the SCA Endpoint Reference API:
      • EndpointReference.BINDING_TYPE_WEB_SERVICE
      • EndpointReference.BINDING_TYPE_WEB_SERVICE_SOAP_1_1
    • Using the SMO structure
      • Target@bindingType=WS
      • Target@bindingType=WS1.1
  • For pure dynamic invocation using SOAP 1.2 and HTTP, the EndpointReference binding type should be set to:
    • EndpointReference.BINDING_TYPE_WEB_SERVICE_SOAP_1_2 using the SCA Endpoint Reference API
    • Target@bindingType=WS1.2 using the SMO structure
Figure 1. Pure dynamic invocation

This image shows a mediation flow component including an endpoint lookup. The mediation flow component is connected to three service providers.

An example of when pure dynamic invocation could be used is with a search engine. Figure 1 shows how a call can be made to the mediation flow component. An Endpoint Lookup mediation primitive is used to retrieve all endpoints from a public WSRR. A public WSRR allows companies to register themselves with service providers on an ongoing basis. This indicates that the endpoint is constantly changing, and so a pure dynamic environment is required. The advantage of pure dynamic invocation, is that the mediation module does not need to be changed in order to respond to new service providers.