How the Dispatcher failover mechanism works

Supports multiple Dispatcher installations See the diagram about managing dispatcher requests using filters. The Dispatcher has the following services: Scheduler: Manages the distribution of Dispatcher requests across modules. Module: Manages translator execution. Dispatcher Client: Extracts and loads data to Teamcenter. Multiple Dispatcher installations can support the same translators, for example, AsyncService, to handle failover. All Dispatcher services support the -ping argument with every startup script to check if the services are running. Failover for Dispatcher Client Each Dispatcher Client queries Teamcenter for specific translator type requests based on filter configurations. For more information, see Manage Dispatcher requests using filters. The same request is not processed by multiple Dispatcher Clients. If the Dispatcher Client goes down, other Dispatcher Installations keep processing the requests for a given type of translator. Dispatcher Client supports retries if there are issues with the pool manager or TcServer. Failover for Scheduler Scheduler has its own database to manage all the requests currently being processed. If the Scheduler goes down, these requests are reprocessed when the scheduler is available. You can clean the Scheduler cache directory and run the Dispatcher utility for the requests that need to be resubmitted. Requests can be resubmitted by using dispatcher_util from the TC_ROOT\bin directory. This changes the state of the request to INITIAL and the next available Dispatcher installation processes the request. Failover for Module When a module goes down, the scheduler reroutes the requests being processed to the next available module. In the diagram about managing dispatcher requests using filters, when Module1 or Machine1 fails, Scheduler1 directs the translation requests to Module2 or Machine2 running in the same Dispatcher instance. Similarly, when Module2 or Machine2 fails, Scheduler1 directs the translation requests to Module1 or Machine1 running in the same Dispatcher instance. Dispatcher Metrics The Dispatcher writes a history log with a record of all the Dispatcher request state changes and the time of the state change. You can parse this log file to get the required metrics data.