Informatica ActiveVOS
- Informatica ActiveVOS 9.2.4.6
- All Products
Property
| Description
|
---|---|
Name
| The name of a service definition.
To view a service definition name, go to
.
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.
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 is 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 exceed the
Max Queued value.
If you do not enable persistence, the dispatch service rejects requests that exceed the
Max In-Memory value.
Default is 300.
|
Max Queued
| The maximum number of requests in the persistent queue.
If you enable persistence, the dispatch queue service rejects requests that exceed the
Max Queued value.
If you do not enable persistence, the dispatch service rejects requests that exceed the
Max In-Memory value.
Default is 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
list.
Default is 300 seconds.
|
Persistent
| Select the
Persistent option to save pending requests to the persistent queue. If you select this option and the Secure Agent restarts, the dispatch configuration continues to execute queued requests.
If you do not select the
Persistent option, pending requests are saved only in the in-memory queue and are lost if the Secure Agent restarts.
|