The Process Engine Web Service is a standards-based Web services implementation, deployed as a Web application on the supported FileNet® P8 Content Engine application server. It is specifically compliant with:
Additionally, the following UDDI and SOAP versions are supported:
The Process Engine Web Service uses the framework provided by Systinet Server for Java™. (See IBM FileNet P8 Platform Hardware and Software Requirements for version information. To download this guide from the IBM support page, see Accessing IBM FileNet Documentation.) Systinet Server is a Web services platform providing development tools, a runtime server, and management services. Systinet Server 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 management tools enable you to deploy, configure and administer Web services.
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. See Creating the WS-Security Header for more information.
The Process Engine Web Service (ProcessEngineWS) provides a subset of the Process Engine runtime 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 Engine runtime class and method. See Operations and Messages for this information.
The Process Engine Web Service must access a Process 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 Process Engine connection point in the SOAP header.
Note: The following configuration changes are recommended after installation: