Bookshelf v7.5: About Batch Mode

About Batch Mode

CAUTION: Before enabling batch mode for your implementation, you should familiarize yourself with Siebel Server Administration Guide. In particular, you should read the chapters about the Siebel Enterprise Server architecture, using the Siebel Server Manager GUI, and using the Siebel Server Manager command-line interface.

When you run a process in batch mode, any visibility limitation against your targeted data set is ignored. It is recommended that you allow only a small group of people to access the Siebel Server Manager to run your data quality tasks and require a login with an administrator ID, such as sadmin.

You can run data matching and data cleansing in batch mode. Batch mode lets you match and cleanse a large number of records at one time. You can run batch mode jobs as stand-alone tasks (see Running Data Quality Batch Mode Requests from the Command Line) or schedule them on a recurring basis (see Predefined Batch Request Parameters).

Batch data cleansing. Use data cleansing to standardize the structure of data in customer profiles. In batch mode, the application standardizes and corrects a group of accounts, contacts, prospects, or business addresses.

Batch data matching (deduplication). Use data matching to identify possible duplicate-record matches for account, contact, and prospect records. In batch mode, the application identifies potentially duplicate records and presents them to the data administrator for resolution.

Running data matching and data cleansing in batch mode requires the use of a separate server component called Data Quality Manager. Although you can run real-time data quality features in any interactive Siebel object manager, you should run batch mode data quality features using the Data Quality Manager server component. You use a native management console called Siebel Server Manager to manage, submit, and monitor your data quality tasks. For more information about the Siebel Server Manager, see Siebel Server Administration Guide.

In most implementations, you should run batch-mode key generation before you run real-time data matching. The Siebel Data Quality Matching Server requires generated keys in the key tables first before you can run real-time data matching. The Siebel Data Quality Universal Connector also has a similar requirement, but the key generation is done within the deduplication task.

CAUTION: Do not put Visual Basic (VB) logic in business components that are used for batch mode tasks. These tasks execute in the background and may not trigger logic that activates user interface features, such as pop-up windows.