|
![]() |
Complete the Context tab to indicate whether stateful or stateless processing applies to this package, and to identify an access group for listeners and requestors.
Field |
Description |
||||||||||||||||||
Processing Mode |
Select Select the default value Choose this value carefully. Using requestor session pooling may improve performance if a high volume of uniform requests arrive, even when authentication is required. See Concepts — How requestor pooling for services works. |
||||||||||||||||||
Service Access Group |
Process Commander uses this access group, even for services that require authentication, to locate the service rule. The service rules and service activities to be executed must be accessible to requestors operating with this access group.
Click the pencil icon ( |
||||||||||||||||||
Requires authentication ? |
Select if the service request requires authentication. When selected, the system expects Process Commander Operator ID and password values in the arriving request message. When selected, authentication occurs only for the first request for stateful services that use pooling and don't destroy the requestor. Later service requests that include the Session ID in the request message continue with the same previously authenticated requestor session.
The location and name of the Operator ID and password values vary, depending on the service type:
|
||||||||||||||||||
Suppress Show-HTML? |
Select to cause the system to skip over any activity step that calls the Show-HTML method in the service activities that execute through service rules that reference this service package instance. This feature lets you reuse or share an activity that supports both interactive users and services. |
||||||||||||||||||
Integration Viewer |
After you save this form, click to view a tree of the components that comprise the package. See About the Integration viewer. |