Process Orchestration

Process Orchestration Web Services can be referenced from the Process Designer UI or invoked from external clients (such as from a Microsoft .NET or Java™ Web Services framework).

At the WSDL level, Process Orchestration Web Services publish the WSDL operations as a document/literal (non-wrapped) SOAP binding.

For invoking other web services, Process Orchestration Web Services supports invoking web services with a SOAP binding of either:

• document/literal (non-wrapped)
• RPC/encoded

The URL for the Process Orchestration Web Service WSDL is formatted as follows:

(For the current workspace:)
    ApplicationEngine_URL/P8BPMWSBroker/wscpCONNECTIONPOINTNAME/wc/workflowName?wsdl

(For a specific workspace:)
    ApplicationEngine_URL/P8BPMWSBroker/wscpCONNECTIONPOINTNAME/wc/workflowName/workspaceID?wsdl

The CCEPOWSBroker servlet uses the bootstrap user credential to process work items. If you want to use different credentials, change the init parameters for the servlet using the application server administration tool. You can also use the set these values via P8BPMWSBroker.properties located in the WEB-INF directory of the ccepowsbroker.war file. These value might not be editable once the WAR file is deployed.

The user credential that you specify will be used to access the workflow system for web services requests, and to persist SIMULATION documents, so ensure that the user has the following permissions:

• Launch a workflow in the workflow system, retrieve workflow definitions, and get XSD files.
• Access any folder that is specified as a Web Services Attachment Folder for the invoke or receive workflow (for persistence attachment).
• Read and write access to the simulation folder, which stores the simulation scenarios.

Procedures for calling Process Orchestration Web Services from Process Designer are found in About Web Services In Workflows.

For more information about the CCEPOWSBroker servlet, see The CCEPOWSBrokerServletURL workflow system property.

For more information about configuring the CCEPOWSBroker servlet, see Configuring the CCEPOWSBroker servlet.