Creation of a Second Batch Engine

The Loyalty Batch Component uses a CCF (Common Core Facility) service of key-based routing to register a key string, servername:procnum. The CCF ensures that the key is unique across all MT servers of that component. Each LoyEngineBatch MT server process iterates through the server key map table records until it successfully registers the first available key. This unique process number is the base of the Loyalty engine's internal load balancing/scheduling algorithm.

Every component name in a Siebel enterprise is unique. A cloned component can't be given the same name as LoyEngineBatch. When the cloned LoyEngineBatch component is trying to register a key, the CCF service doesn't restrict it, even though the key exists and is used by another component. So, a cloned LoyEngineBatch component assumes the same key values provided in the server key map. As you can see, cloning is a powerful tool to duplicate the Loyalty Batch Engine's processing power.

By providing different values for the LOYEngineQueueObjects parameter, you can make the cloned component process specified object records. For example, giving a value of LOYEngineQueueObjects = Bucket:500 for the cloned LoyEngineBatch component will make it process only bucket objects.

Because keys in server key maps are used to distribute the load, care should be exercised while specifying the keys, so that the distribution of the bucket objects remains fairly uniform across different keys.

Grouping cloned Loyalty Batch components under a user-defined Server Component Group will help distribute the load across available Siebel servers