Table of Contents

Search

  1. Preface
  2. The Application Integration Console
  3. Process Server Configuration
  4. Deployed Assets
  5. Process Schedules
  6. Processes
  7. Process Server Health
  8. Process Metrics
  9. Connections
  10. Guides
  11. Logs

Monitor

Monitor

Dispatch Service Configuration

Dispatch Service Configuration

Configure the following properties to create a custom dispatch configuration:
Property
Description
Name
The name of a service definition or a process group.
To view a service definition name, go to
Processes
Select Process Version Number
My Role
Service column
.
For example, in the following
My Role
section of the
Deployed Process Version Details
page, the service name is
0BQGwyKeJVBie6UGrJHaqI/Print_Hello_World-1
:
If you enter a service definition name, the dispatch configuration governs all instances of the service, regardless of the process that contains the service.
If you enter a process group name, the dispatch configuration governs all processes within the group.
You cannot change the name of a saved dispatch configuration. To edit the name, delete the dispatch configuration and then create a new one.
Max Concurrent
The maximum number of requests that Process Server can hold in the concurrent pool.
Default: 15.
Max In-Memory
The maximum number of requests that Process Server can hold in the in-memory queue.
If you enable persistence, the dispatch service rejects requests that cross the
Max Queued
value.
If you do not enable persistence, the dispatch service rejects requests that cross the
Max In-Memory
value.
Default: 300.
Max Queued
The maximum number of requests to in the persistent queue.
If you enable persistence, the dispatch queue service requests that cross the
Max Queued
value.
If you do not enable persistence, the dispatch service rejects requests that cross the
Max In-Memory
value.
Default: 300.
Timeout (seconds)
The maximum amount of time, in seconds, that a single request can take to execute within the dispatch service.
If a request takes longer that the timeout value to execute, it moves out of the dispatch service and the next pending request executes.
If a request times out of the dispatch service, Process Server continues to execute outside of the dispatch configuration. As a result, you might see different values on the
Processes
list and the
Server Configuration
Queues
Dispatch Queue
list.
Default: 300 seconds.
Persistent
Select
Persistent
to save pending requests to the persistent queue. If you do not select
Persistent
, pending requests are saved only in the in-memory queue and are lost if the Secure Agent restarts.
If you select
Persistent
and the Secure Agent restarts, the dispatch configuration continues to execute queued requests.
Default: Not selected.
For information about how you can use these properties to throttle requests, see the Sample Dispatch Configurations .