Siebel Loyalty Administration Guide > Getting Started with Siebel Loyalty > Setting Up Server Components for Siebel Loyalty >

Setting Up the Real-Time Server Component


To set up the real-time component, you must configure several parameters. In addition, you can choose whether to run this component in synchronous or asynchronous mode.

NOTE:  If your company has multiple Siebel Business Applications installed, then these parameter settings only affect Siebel Loyalty, and not any of the other applications.

Setting Parameters of the Real-Time Component

To configure parameters for the Loyalty Engine real-time component, perform the steps in the following procedure.

To set parameters for the Loyalty Engine real-time component

  1. Navigate to Administration - Server Configuration, Enterprises, then the Component Definitions view.
  2. Query for the eLoyalty Processing Engine - Realtime component.
  3. In the Component Parameters view, specify values for the parameters shown in the following table.
    Parameter
    Value

    Maximum Tasks

    This parameter determines the maximum number of tasks the component can run. Set its value based on the number of users who use real-time processing through the user interface.

    Minimum MT Servers

    Maximum MT Servers

    Set the value of both of these parameters to one.

    For more information about these parameters, see Siebel System Administration Guide.

Configuring the Processing Mode of the Real-Time Component

When the user clicks the Process button, the real-time component can process the request in one of the following modes:

  • Synchronous. The client waits for transaction processing to be completed before control is returned to the client. The user cannot do anything until the processing is completed. When control is returned to the user, the record reflects changes such as change in status or number of points.
  • Asynchronous. The client submits a transaction and control returns to the client immediately. The user can continue working, but the user must requery the transaction to see whether the processing is completed (by looking at the Status) and to check the results.

The decision about which mode to use depends on the load in the deployment. There is typically a satisfactory response time in synchronous mode with a few hundred users and a light to medium load. You must use asynchronous mode if there are thousands of users all using real time processing, which is not common.

In a typical deployment, real-time processing is not used heavily, so Siebel Loyalty runs in synchronous mode by default. The following procedure describes how to configure the processing mode.

To configure the processing mode

  • Use Siebel Tools to change the user property ComponentRequestMode defined in the business service LOY Processing Engine.

    Acceptable values for this user property are Sync and Async.

Siebel Loyalty Administration Guide Copyright © 2013, Oracle and/or its affiliates. All rights reserved. Legal Notices.