7.4 Managing Batch Control Utility

The Batch Control Utility enables you to manage and record the beginning and ending of a Behavior Detection batch process. It also enables you to access the currently running batch.

You control the process through a job scheduling tool such as Maestro or Unicenter Autosys. This utility consists of a Java file that resides in the directory <OFSAAI Installed Directory>/database/db_tools/lib and UNIX script files that reside in <OFSAAI Installed Directory>/database/db_tools/bin:

• start_mantas_batch.sh starts the batch process.
• end_mantas_batch.sh ends the batch process.
• get_mantas_batch.sh obtains the name of the currently running batch.

The utility also uses common parameters in the configuration file <OFSAAI Installed Directory>/database/db_tools/mantas_cfg/install.cfg.

This section covers the following topics:

• Batches in Behavior Detection
• Directory Structure
• Logs
• Using the Batch Control Utility

Note:

To calculate the age in business days versus calendar days, verify that the age.alerts.useBusinessDays setting in the <OFSAAI Installed Directory>/database/db_tools/ mantas_cfg/install.cfg file has a value of Y (yes).

Batches in Behavior Detection

Except for the Alert Viewer subsystem, batches govern all other activity in the Behavior Detection system. A batch provides a method of identifying a set of processing. This includes all activities associated with data management and Behavior Detection.

Deployment of a system can be with a single batch or with multiple batches. You can use multiple batches to permit intra-day processing to generate results several times per day, or to separate processing based on servicing multiple time zones.

Behavior Detection provides two types of batches:

• End-of-day: Represent processing at the completion of a business day for a set of data. Some processes are only appropriate for end-of-day batches. For example, daily activity summary derivations and calculating alert ages are activities that occur only in end-of-day batches. Multiple end-of-day batches per day can run if the Behavior Detection installation supports multiple time zones , such as New York and Singapore.
• Intra-day: Used when loading data between end-of-day batches to obtain more frequent detection results. For example, running a batch of trading-compliance scenarios at 10:00 A.M. can identify behaviors relevant to the opening of the market without waiting for the end of the day to be able to act.

Directory Structure

The following table provides the directory structure for the Batch Control Utility, in <OFSAAI Installed Directory>/database/db_tools/:

Table 7-6 Batch Control Utility Directory Structure

Directory	Contents
lib/	Required class files in .jar format.
mantas_cfg/	Configuration files , such as install.cfg and categories.cfg, in which you can configure properties and logging attributes.
logs/	File batch_control.logthat the utility generates during execution.
bin/	Executable files, including the start_mantas_batch.sh, end_mantas_batch.sh, and get_mantas_batch.shshell scripts.

Logs

As the Batch Control Utility manages batch processing, it generates a date-stamped log in the <OFSAAI Installed Directory>/database/db_tools/logs/batch_control.log file. The log file contains relevant information such as status of various batch control processes, results, and error records.

You can modify the current logging configuration for the Alert Purge Utility in the <OFSAAI Installed Directory>/database/db_tools/log4j2.xml files. For more information about logging in these configuration files, refer to Managing Common Resources for Batch Processing Utilities, and Appendix A - Logging.