Process Engine Web Service

The Process Engine Web Service is a standards-based Web services implementation. It is deployed as a Web application on the supported application server.

The Process Engine Web Service is compliant with:

WS-I Basic Profile 1.0
WS-Security

Additionally, the following SOAP version is supported:

SOAP 1.1 over HTTP

The Process Engine Web Service uses the framework that is provided by IBM® Axis2. For version information, see the IBM FileNet P8 system requirements web page. Axis2 is a Web services platform that provides development tools, a runtime server, and management services. Axis2 runtime services isolate common services from business applications. The runtime server processes SOAP messages and provides a runtime container for web services. The SOAP message processor converts SOAP messages into application invocations, mapping XML types to Java™ types. The runtime service container hosts and manages the deployed applications.

The Web service operations are stateless. The caller is required to pass in user criteria as part of the SOAP WS-Security header for the operation. For more information, see Creating the WS-Security Header.

The Process Engine Web Service (ProcessEngineWS) provides a subset of the Process Java API, and (per WS-I Basic Profile 1.0) uses document/literal SOAP messaging. The reference documentation for the Process Engine Web Service links each operation to the associated Process Java API class and method.

The Process Engine Web Service must access a Content Platform Engine connection point to create and maintain a session. The default connection point for the Process Engine Web Service is PEWSConnectionPoint. See Using Multiple Regions for instructions in specifying a connection point in the SOAP header.

Note: The following configuration changes are recommended after installation:

Although the Process Engine Web Service is enabled by default, SSL is not. IBM highly recommends that you use SSL for Web services in a deployed environment. Refer to Setting up Content Platform Engine and client transport SSL security for instructions.
(For the .NET framework only.) When you apply a load against your application, deadlocks might occur (HTTP 503 errors), resulting in inflated response times and numerous errors. In this case, update the configuration of the framework per Microsoft Knowledge Base Article 821268.