Siebel Field Service Guide > Scheduling Using Siebel Scheduler >

Setting Up Server Key Mappings

Service regions are self-contained so that they can run on separate CPUs and even separate servers. You use server key mappings to specify the location and routing of requests to these service regions. Server key mappings also assign the service regions to different processes and determine whether the servers process them in parallel or serially. There are server key mappings for the ABS and for the Optimizer.

When a user clicks the Book Appointment button, the request is sent to the enterprise server. The enterprise server then reviews the mapping of the service regions and routes the request to the appropriate Siebel Server that stores that service region.

In the Server Key Mappings view, you assign servers to processes and associated service regions.

This task is a step in Process of Administering Schedules Using Siebel Scheduler.

To set up a server key mapping

1. Navigate to the Administration - Scheduling screen, then the Server Key Mappings view.
2. Create a new server key mapping record, and complete the fields as appropriate.

   Some fields are described in the following table.

   Field	Comments
   Server	Type the name of a Siebel Server.
   Process #	Type the number of a process that runs on the server. This number groups service regions into the same process. CAUTION:  If you specify multiple processes on a server, then you must set the Maximum MT Servers server component parameter to the same number of processes so that multiple processes are spawned. If you do not, then only the first process is created and not all regions are loaded. It is recommended that you set the Minimum MT Servers server component parameter to the number of needed processes and the Maximum MT Servers parameter to a value greater than or equal to the Minimum MT Servers parameter. For more information about these parameters, see Siebel Performance Tuning Guide and Setting Parameters for Server Component Tasks.
   Leaf Service Region	Select the name of a service region from the Pick Service Region dialog box.
   Component	Select the name of a component, either ABS or Optimizer, from the Pick Component dialog box. NOTE:  If the Server Key Mappings - Optimizer Component is not available for selection in the Component field, then the server installation is incomplete. To correct this problem, use the Synchronize button in the Synchronize view in the Enterprises view of the Administration - Server Configuration screen. For more information about the complete procedure, see Siebel System Administration Guide.

3. Restart the relevant server component (for example, the Appointment Booking Engine or Optimizer) for the changes to take effect.

   You must also restart the relevant server if you add or remove a key value.

Multiple Processor Support

If the underlying operating system can support multiple processors on 1 computer, then Siebel Scheduler can take advantage of the processors by running different service regions for the ABS and Optimizer on different processors. You must set different process numbers in a server key mapping. A server with a single processor can run multiple processes, but this setup can adversely affect performance. Service regions in different processes are run in parallel, while service regions in the same process are run serially.

NOTE:  The number of processes running on a server computer is not related to the number of processors in that computer.

Because the ABS and Optimizer are different modules, they are already running as separate processes, even though the process number is the same. A module for 1 service region can run in only 1 process at a time.

For example, consider a 4-processor computer with only 2 processors in use. Table 13 shows an example of the key mapping when 1 service region runs with both the ABS and Optimizer. Process refers to the number of processes for that component, not the processor number on the server.

NOTE:  You cannot run 1 module for a service region as 2 processes.

Table 14 shows an example of the key mapping when 2 service regions run on a 4-processor computer. In this example, you can use all 4 processors. Process refers to the number of processes for that component, not the processor number on the server.

If there are more than 2 service regions on a 4-processor computer, then you can run the modules as different processes. Table 15 shows an example of the key mapping for the best use of the processors on a server when the West Coast Region is very large and the Central Region and East Coast Region are smaller. Process refers to the number of processes for that component, not the processor number on the server.

The West Coast Region requires more computation and uses 2 processors. The East Coast Region and Central Region run in the same processes and on the same 2 processors.

Each server component is multithreaded and can load schedules for multiple service regions. Multiple threads can share these schedules. Each request to the Optimizer runs on a new thread.

A request identifies the required schedule for 1 service region and locks the schedule. Requests for schedules for other service regions can continue while requests for the same schedule are queued. Because the response time for the ABS is fast, high latency for the returned booking times does not result because the processing time between ABS transactions is usually several minutes.