Deploying a Process That Calls a Web Service

Calling a Service on a Virtualization Binding

If your process calls the service on a virtualization binding, the promoted reference in the composite application (representing the service call) must be wired to the appropriate service virtualization binding of the application that provides the service.

You can perform this wiring by using the Wiring Configuration page of the DAA Deployment Wizard wizard. For more information see Using Pageflow Processes and Business Services.

Alternatively, you can export the project to a Distributed Application Archive (DAA), then use the Administrator interface in the BPM runtime to perform the wiring and deploy the application. See the Administrator interface documentation for your BPM runtime environment for more information.

Calling a Service on a SOAP Binding

If your process calls the service on a SOAP binding, when you deploy the project, you must bind the system participant to the appropriate resource instance(s) in the BPM runtime:

• The system participant logically identifies the web service to be called.
• Resource instances define the actual runtime connection to the target web service.

You can perform this binding using the Property Configuration page of the DAA Deployment Wizard wizard. For more information see the following references:

• SOAP over JMS Binding Details (Provider)
  Note: A binding is made for each system participant, so if multiple tasks or events use the same system participant to call the same web service, they will all use the same service endpoint.
• SOAP Over JMS Binding Details (Consumer)

Alternatively, you can export the project to a Distributed Application Archive (DAA), then use the Administrator interface in the BPM runtime to perform the binding and deploy the application. See the Administrator interface documentation for your BPM runtime environment for more information.