Siebel Loyalty Administration Guide > Getting Started with Siebel Loyalty >

Creating a Second Realtime Engine Component for Siebel Loyalty

If you have a heavy load of realtime transactions, you can create a second Loyalty realtime engine on a second Siebel Server, in order to spread the load and improve performance.

The following steps show how to create a second realtime engine component and create a second Process button in the interface to call this new realtime engine component, so you can confirm that the new engine is being called.

In an actual business situation, you would create the second realtime engine and configure the application so that the load balancing occurs in the background, determining which engine to call.

Creating a New Realtime Engine Component

First create the new realtime engine component.

To create a new realtime engine component

  1. Navigate to Administration - Server Configuration > Enterprises view.
  2. Click the Component Definitions view tab.
  3. In the Component Definitions list, query for eLoyalty Processing Engine - Realtime.
  4. Add a new record to the Components Definition list and complete the necessary fields, described in the following table.


    eLoyalty Processing Engine - Realtime2



    Component Type

    Workflow Process Manager (Batch)

    Component Group

    Siebel Loyalty Engine

    Run Mode



    Second Loyalty Realtime engine

    CAUTION:  The Component Type for the existing real time engine definition is "Business Service Manager (Batch)". For the new record you do not select this, instead select the Workflow Process Manager (Batch). When you save the record the Component Type is changed to the "Business Service manager (Batch)".

  5. Next check the component parameters for this new record against the original, and change the parameters as necessary to match the original.
  6. Click Enable.
  7. Stop and restart the Siebel and gateway servers, so that the new component appears.
  8. Disable duplicate server components:
    1. Navigate to Administration - Server Configuration> Servers.
    2. Select the first Siebel server and query in the Components list for *Loy*.
    3. Select eLoyalty Processing Engine - Realtime 2 component and click Disable.
    4. Select the second Siebel server, select the eLoyalty Processing Engine - Realtime component and click Disable.

      Now one realtime engine is on each Siebel servers.

  9. Register the new component as unkeyed:
    1. Navigate to Administration - Data > List of Values view.

      This record should have the display value and language independent code set to LoyEngineRealtime.

    3. Create a new record with the same details except that the display value and language independent code are LoyEngineRealtime2.

      This record refers to the new component, enabling the cache to be refreshed for the new second real time engine when a promotion is activated.

  10. Synchronize the servers:
    1. Navigate to Administration - Server Configuration > Enterprises view.
    2. Click the Synchronize view tab.
    3. Click Synchronize.

      This allows the enterprise to know where all the batch components are located.

  11. Stop and restart the Siebel and gateway servers and gateway and restart.

Adding a New Process Button to Call the New Realtime Engine

Now you must use Siebel Tools to create a new Process button in the interface to call this new realtime engine component.

You should do this only if you have experience using Siebel Tools.

To add a new process button to call the new realtime engine

  1. In Siebel Tools, create a new workflow to call the new realtime engine:
    1. Locate the workflow LOY Engine - Process Object.
    2. Copy this and name the copy LOY Engine - Process Object 2.
    3. Click the workflow step.
    4. In the workflow, select the step Invoke Submit Object.
    5. Select the workflow step I/O argument Component.
    6. Change the Value/Search Specification from LoyEngineRealtime to LoyEngineRealtime2.

      NOTE:  If you cannot make this change directly, you can do the following: export the new workflow, delete it from Tools, open the xml file and locate LoyEngineRealtime, change occurrences to LoyEngineRealtime2, and import the new workflow.

    7. Click Deploy.
  2. In your Siebel application, activate the workflow:
    1. Navigate to Administration - Business Processes> Workflow Deployment.
    2. Query in the Active Workflow Processes list for LOY Engine - Process Object*.

      Only one record should appear, the original workflow.

    3. Query in the Repository Workflow Processes list for LOY Engine - Process Object*.
    4. Select the workflow LOY Engine - Process Object 2 and click Activate.
  3. Create new named methods:
    1. In Siebel Tools locate the LOY Transaction List Applet.

      This applet has a control called ButtonProcessObject which invokes the method ProcessTxn.

    2. The LOY Transaction business component, which the applet is based on, create the following user properties:
      • Named Method 11. ProcessTxn2, INVOKE, LOY Transaction, WriteRecord
      • Named Method 12. ProcessTxn2, INVOKESVC, LOY Transaction, Workflow Process Manager, RunProcess, ProcessName, LOY Engine - Process Object 2, LOYObjectId, [Id], LOYWorkflow, LOY Engine - Process Transaction, LOYObjectStatusLIC, [Status LIC], LOYRequiredStatusLIC, Acceptable, LOYStatusLOV, LOY_TXN_STATUS_CD
      • Named Method 13. ProcessTxn2, INVOKE, LOY Transaction, RefreshBusComp
      • Named Method 14. ProcessTxn2, INVOKE, LOY Member, RefreshRecord
      • Named Method 15. ProcessTxn2, INVOKE, LOY Member Attribute, RefreshBusComp
      • Named Method 16. ProcessTxn2, INVOKE, LOY Promotion Bucket, RefreshBusComp
  4. Create the new button:
    1. In Siebel Tools, in the applet LOY Transaction List Applet, copy the control ButtonProcessObject.
    2. Change the caption to ProcessTransactions.
    3. Change the Method Invoked to ProcessTxn2.
    4. Add the new button to the Edit List Template.
  5. Create the modified application:
    1. Compile the .srf.
    2. Stop the services.
    3. Copy the .srf.
    4. Start the services.
  6. Test the modified application.

    The Process button should call LoyEngineRealtime and the Process Transactions button should call LoyEngineRealtime2. You can increase the logging on these components to verify that the correct ones are called.
