The simplest way to deploy a service endpoint as a Web Service is to select one of the standard SOAP bindings:
You only need to select the binding style and a service name. The SOAP binding elements for the selected style are generated based on the Port Type and Policies associated with the
element in the PDD.
After deployment, Process Server handles the receipt and reply of messages designated for the service endpoint. The messages are formatted and processed by Process Server based on the binding.
Services are deployed to the engine's internal web service provider. Web services are supported by the Metro SOAP stack. (Metro was developed by Sun as a core component of the Glassfish project.)
Both SOAP 1.1 and SOAP 1.2 endpoints are deployed for JAX-WS compliant services (Document Literal and RPC Literal). Legacy bindings such as RPC Encoded are deployed as SOAP 1.1 only.
When a request is received, the URL determines the target service and SOAP version. The last segment of the path corresponds to the service name specified in the PDD:
For SOAP 1.1 the URL is:
For SOAP 1.2 the URL is:
The WSDL for a deployed web service endpoint is accessible at:
A listing of all deployed web services hosted within the Process Server engine is found at the following URL:
In the Process Console, select the Service Definitions link.
The WSDL that is published for the service includes standard WS-Policy attachments for policy assertions including WS-Addressing and WS-Security.