Deploying a Process That Exposes a Web Service

When you deploy the project, you must bind the system participant to the appropriate HTTP Connector resource instance in the BPM runtime.

• The system participant defines the web service endpoint.
• The HTTP Connector resource instance is used by BPM to provide external client applications with a runtime connection to the 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 HTTP Binding Details (Provider)
• SOAP over JMS Binding Details (Provider)

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.

A client application (which can be another process) hosted in the BPM runtime can now call the exposed web service operation on its virtualization binding or, if necessary, on its SOAP binding.

An external client application will need to access the exposed web service on its SOAP binding, using a concrete WSDL.

You can generate a concrete WSDL for the application from the Administrator interface in the BPM runtime.

Copyright © Cloud Software Group, Inc. All rights reserved.