For example, the default configuration of ClaimCenter schedules the ActivityEsc batch process to run every 30 minutes. Exclude running such batch processes periodically during your nightly batch processing window. Instead, wait until the end of the batch window to run them, For example, schedule the ActivityEsc to run every 30 minutes except during your nightly batch window. Alternatively, run such batch processes at prescribed places in your chain of nightly batch process. Disabling the ClaimCenter Scheduler You can choose to use your own mechanism for running ClaimCenter system processes. For example, you can use the ClaimCenter API or command-line utilities to run the processes, and you can use your own scheduling application to trigger their execution. If you do this, you might choose to disable the internal ClaimCenter sched- uler. To disable the internal scheduler, set the SchedulerEnabled configuration parameter to false : <param name="SchedulerEnabled" value="false" /> Using Events and Messaging with Batch Processes You can use the event/messaging system to launch external processes upon completion of a batch process, including a distributed work queue writer. For example, you could write records to a file or database table as the batch process handles each transaction. After the batch process has handled all transactions, the data can be submitted to a downstream system. To coordinate this activity, use the ProcessHistory entity. As a batch process starts, ClaimCenter fires a ProcessHistoryAdded event. As the status of the process changes, ClaimCenter fires a ProcessHistoryChanged event. When ClaimCenter catches a ProcessHistoryChanged event, the processHistory.CompletionTime property contains the datestamp in a datetime object. For more information about events and messaging, see “Messaging and Events” on page 139 in the Integration Guide .
ClaimCenter 6.0.8 System Administration Guide Chapter 11, Batch Processes and Work Queues 147 Troubleshooting Batch Processes and Work Queues This section discusses topics that are helpful in troubleshooting the management of batch processes. Tuning Your Batch Process Schedule To improve the performance of the batch operations, stagger the schedule so processes do not run at the same time. See “Scheduling Batch Processes and Distributed Work Queues” on page 143. You can also run these processes manually from the command-line. Running Batch Processes from the Command Line You can use the maintenance_tools command-line tool to run any of the batch processes. Run the following command: maintenance_tools –password password –startprocess process_name For example, to recalculate database statistics, you would run the following: maintenance_tools –password password –startprocess dbstatistics Monitoring Batch Processes To check the status of a batch process, run the following command: maintenance_tools -password password –processstatus process_name You can also terminate a running process with the following command: maintenance_tools -password password –terminateprocess
You've reached the end of your free preview.
Want to read all 180 pages?
- Spring '20
- Data Management, batch processing, configuration file, Configuration files, INI file, ClaimCenter