Siebel Smart Answer Administration Guide > Configuration and Implementation of Siebel Smart Answer > Smart Answer Setup >

Using Master and Slave Server Setup Configuration 

Use master and slave configurations to balance loads for large volumes of inbound requests, that is, more than 50,000 requests a day.

This configuration suits a multiple server scenario, where one server functions as the master and other servers function as slaves. Server Request Broker load balances incoming messages among master and slave servers. Performance is optimized as all feedback is sent to the master server.

The master server records Smart Answer feedback and synchronizes the knowledge base to the slave servers. One or more slave servers connect periodically to the master server to copy the most recent knowledge base. The master server is the only server that can learn. The slave servers only connect and receive information from the master.

Only use this server setup configuration for load balancing, where large volumes of incoming requests of the knowledge base are expected.

Setup Scenario

You must have at least three servers to run a master and slave configuration. The components to this setup are as follows:

• One server running Communications Manager. For more information on how to set up Communications Manager, see Siebel Communications Server Administration Guide.
• One server running Smart Answer Master.
• One server running Smart Answer Slave.

Server Parameters

The master server parameters are listed in Table 3.

The slave server parameters are listed in Table 4.

Rules and Assumptions

The following rules and assumptions apply when you use a master and server configuration:

• If a categorization or feedback request is made when the master server is saving the file to disk or loading the KB, the Smart Answer engine does not respond until the save operation is completed.
• If a categorization or feedback request is made when the slave server is reading the new KB, the request is held until the slave server has completed the operation.
• If a master attempts to write a record while a slave is reading the KB, the master waits ten second intervals until the slave server is available.
• If the slave attempts to read while the master is writing the KB, the slave returns without having performed the operation.

Overview of Master and Slave Server Setup

This topic provides an overview of a master and slave server installation of three servers, ServerA, ServerB, and ServerC.

1. Install Siebel Server with Siebel Gateway Name Server. On ServerB and ServerC, install Siebel Server pointing to same gateway as ServerA.
2. Follow the instructions for each server as shown in the following table:

   Server	Instructions
   ServerA	Enable Communications Inbound Manager. Do not enable Smart Answer.
   ServerB	Enable Smart Answer with Master
   ServerC	Enable Smart Answer with Slave.

3. To configure the master server, that is, ServerB, perform the following steps:
   1. Navigate to the Administration - Server Configuration screen > Servers view.
   2. Select ServerB from the list of servers, click on the Components tab, then query for the Smart Answer Manager component.
   3. Select the Smart Answer Manager component, then click on the Parameters tab for the component. Query for the Categorization Manager Type parameter.
   4. Enter Master as the current value.
   5. Query for the KB Update Interval and set the value to 0.
   6. Query for the KB Write Interval and set the value to the value of your choice.

      For more information about slave server parameters, see Table 3.

4. To configure the slave server, that is, ServerC, perform the following steps:
   1. Navigate to the Administration - Server Configuration screen > Servers view.
   2. Select ServerC from the list of servers, click on the Components tab, then query for the Smart Answer Manager component.
   3. Select the Smart Answer Manager component, then click on the Parameters tab for the component. Query for the Categorization Manager Type parameter.
   4. Enter Slave as the current value.
   5. Query for the KB Update Interval and set the value to the value of your choice.
   6. Query for the KB Write Interval and set the value to 0.

      For more information about slave server parameters, see Table 4.