Context Id

. This Id is used in the URL to login to the Process Server, deploy contributions, and access services. For example, a tenant administrator would login to the Process Console at the following URL:

Console URL

. The URL that is used to invoke the tenant's Process Console.

Central URL

. The URL that is used to invoke the tenant's Process Central.

SOAP services URL

. The URL to which a SOAP request is sent.

REST services URL

. The URL to which a REST request is sent.

Tenant Name

. This descriptive name is for system administrator use.

Activity Execution Limit

. Set a value for the maximum number of activities that can execute In order to avoid infinite loops and resource draining processes. The default value is approximately 10,000. When this maximum is reached, the process is suspended. Suspended processes must be resumed manually. The processes count is reset to zero when it is reset. You can get around this limitation by using an agent to run your process.

Process Logging Level

. By default, Process Server generates an execution log for running processes. You can view or download an execution log for a running or completed process. An execution log provides start and end times for activity execution and helps you troubleshoot faulted processes. The logging levels are:

Execution (default)—All execution statements are logged, except for
Will Not Execute
statements. Using this setting can greatly decrease the size of the log file.
Execution with Data—All execution statements are logged, except for
Will Not Execute
statements, but including variable, expression, and partner link data. Using this setting can increase the size of the log file.
Execution with Service Data—All execution and fault information, as well as some WSIO activty information. For execution information, information such as deadpath states, terminations, ready-to-execute and the like. For WSIO, this includes invokes, picks, and receives. WSIO information related to data assignment and changes is excluded.
None—You can disable logging to enhance engine performance.
Full—All execution statements are logged, including the
Will Not Execute
statements for deadpath activities. For example, all fault handling statements that are not executed are logged.

Process Retention (seconds)

. Specify how many second to keep completed and faulted processes are retained before they are deleted.

Message TTL (seconds)

. Specifies the amount of time between the time a message reaches the Process Server and the time when it is about to get dispatched to the target process. Default is 24 hours.

/active-bpel/services/
/active-bpel/public/rt/
/active-bpel/rt/
/active-bpel/public/soap/
/active-bpel/soap/
/active-bpel/odata/repository/v4/OdataRepository/Execute
/active-bpel/tf/
/activebpel-cert/services/
/activebpel-cert/rt/
/activebpel-cert/soap/
/activebpel-cert/odata/repository/v4/OdataRepository/Execute
/process-engine/rt/
/process-engine/public/rt/
/process-engine/services/
/process-engine/public/soap/
/process-engine/soap/

Message with attachments size limit

. Sets the maximum size of the payload for a multi-part message that has attachments.

Tenant Description

. These details are for system administrator use.

Admin Group

: Security Roles:

abTenantAdmin
(Required for the group and each user in the group)
abTaskClient (Required for each user in the group for access to Process Central)
Not needed:
abDeployer
or
abServiceConsumer
abDeveloper
(Allows remote debugging from Process Developer. Alternately, tenant admins can perform debugging in the Process Console.)

Login access to the tenant context and control over tenant context (described in Tenant Administration for Tenant Administrators/Deployers)
Deploy contributions into the tenant context from Process Developer
Access Process Server Web Services

Service Consumer Groups

: Security Roles:

abServiceConsumer
(Required for the group and each user in the group)
abTaskClient
(Required for each user in the group for access to Process Central)

Tenant Data

. This data is not currently used.