Use the dispatch service to create dispatch configurations that throttle requests made to Process Server.

The requests could be HTTP/S messages, message events, or other Transport Layer Security (TLS) requests. You can queue requests, dispatch requests in batches, and control the maximum number of requests that run concurrently.

For example, you have a frequently used process that quickly dispatches asynchronous requests to Process Server. At run time, if thousands of these requests execute simultaneously, the result can overwhelm the server and the service being invoked. Use the dispatch service to send requests in batches and to ensure that only a few requests are processed at the same time.

You can use the dispatch service for services that run on the Secure Agent. You cannot use the dispatch service for services that run on the cloud server.

Create a dispatch configuration for a service. At run time,

Application Integration

chooses the dispatch configuration in the following order of preference:

Service Name
System Default

For example, the service

processA_event1

has the following dispatch configurations that apply to it:

processA_event1
(Service Name)
SystemDefault

When Process Server executes

processA_event1

, the

processA_event1

dispatch configuration applies.

The dispatch service applies to all requests except for subprocess invokes that contain boundary events. For example, if a subprocess step contains a message event, the dispatch service will not apply to the subprocess.

However, if you use a service call step to add a subprocess, the dispatch applies to all subprocess configurations, including subprocesses with boundary events.