Admin ServiceOptimizer System Configuration Business Functionality Configuring Dispatch
- Andrew Hill (Deactivated)
- f.anwar (Deactivated)
On This Page:
Related Pages:
An Admin ServiceOptimizer Further Detail Core Processes FRU Process and Admin ServiceOptimizer Further Detail Core Processes API Agent rely on Database sp083_system_parameters and Database sp213_scheduler_parameters to configure the dispatch behaviour etc.
They are given below for information only.
Global parameters
| Parameter | Mandatory/ Optional | Description |
|---|---|---|
| M | Specifies how many Dispatch Agent Worker Threads should be used. You will need help from a consultant to set this up. It is critical to the running of the system and incorrect settings can result in performance degradation, system instability or hitting operating system limits. |
| M | Specifies the maximum time (in seconds) allowed between dispatch client requests, before the API Agent disconnects the dispatch client. See also notes below this table. Lowering this value will increase the chances that the API Agent will erroneously consider the dispatch client to be inactive (for instance because of processing and network delays). Therefore the value for this timeout would normally be at least ten seconds (in order to allow for processing and network delays) and often the value would correspond to a duration of several minutes. It is also the case that, if set less than or equal to the client’s SOAP timeout, then this can cause the API Agent to think the system has crashed and hence it restarts itself. Set |
| M | Specifies the maximum time that the API Agent will wait for dispatched jobs (per dispatch client) before returning with return code Lowering this value will increase the network traffic and also the processing load on the dispatch client and API Agent. Therefore the value for this timeout would normally be at least ten seconds and often the value would correspond to a duration of several minutes. |
Per FRU parameters
| Parameter | Mandatory/ Optional | Description |
|---|---|---|
| O | To enable/disable dispatch when changing a Work Item’s status to earmarked. |
| O | The number of Work Items per operative allowed to be earmarked at any one time (was |
| O | Time (in minutes) after the expected end of a Work Item when attempts to dispatch will be abandoned. |
| O | Time (in minutes) after an attempt to unearmark following a change of engineer when attempt to dispatch earmark will be made even if unearmark has not been dispatched. |
| M | Minimum interval between attempts to re-send failed dispatch messages (minutes). |
| M | Time interval (in minutes) between auto-earmarking dispatch scans. |
| O | If Work Item is moved, within same operative, by more than this amount, Dispatch Monitor will Re-Earmark it (percentage, e.g. ‘10%’, or minutes, e.g. ‘10’). |
| O | Dispatch API local time type. Used to specify which time zone should be assumed for the Work Item's times in the dispatch message. |