1. Marketing Installation and Administration Guide
  2. Initial Setup and Configuration

Initial Setup and Configuration

The initial setup and configuration tasks for the Siebel CRM integration with Oracle Unity are as follows:

  1. Install Siebel CRM (Siebel CRM 21.10 Update or later).

    For more information, see Siebel Installation Guide.

  2. Perform the tasks described for configuring incremental indexing for third-party search engines, as described in Siebel Search Administration Guide. These tasks include the following:

    1. Enable the Search Processing (alias Search) and Disconnected Mobile Synchronization (alias MobileSync) component groups. See also the note about the Transaction Processor component later in this topic.

    2. Set the Enable Incremental Indexing system preference to True. If the system preference is not already defined, then add it.

    3. Add a job template, add a job, and submit the job.

      Use the settings described in Siebel Search Administration Guide.

  3. Set the Enable Transaction Logging system preference to True, as described in Siebel Remote and Replication Manager Administration Guide. This setting is required to support incremental data loading.

  4. Set up the driver parameters for the Siebel - Unity Data Export engine, as follows:

    1. Navigate to the Administration - Data Export screen, then the Data Export Administration view.

    2. In the Export Engine list, select the Siebel Unity - Data Export engine.

    3. In the Driver Parameters list, confirm the default value for each parameter or modify the value, as appropriate for your deployment.

      The driver parameters are listed in Driver Parameters for the Siebel - Unity Data Export Engine.

Caution: When the Enable Incremental Indexing system preference is set to True, the Transaction Processor component (alias TxnProc) runs automatically. In this case, for Siebel Remote deployments, you must stop TxnProc before you run the Database Extract component (alias DbXtract) for the first time. After DbXtract has completed, then you can restart TxnProc. If you do not follow these steps, then some transactions might not be routed to remote clients. For more information about running DbXtract, see Siebel Remote and Replication Manager Administration Guide.