Siebel System Administration Guide > Configuring Siebel Servers > Advanced Configuration Tasks >

Reconfiguring Siebel Server Component Definitions

Component reconfiguration is a process that allows existing component tasks to continue running until they finish, while starting new processes with reconfigured component parameter values. Each component can be reconfigured, but this task is primarily done for multithreaded components. This topic is part of Advanced Configuration Tasks.

Component reconfiguration is particularly useful for scenarios such as site migration. In this scenario, component reconfiguration allows you to maintain the existing component configuration, which remains available until the migration is complete and a new component configuration becomes available.

When a component reconfiguration is committed, this action signifies to every Siebel Server in the Siebel Enterprise Server that a new component definition is available and that new tasks should not start for that component. Existing tasks, however, continue to run until completion. The connected Siebel Servers then start new multithreaded processes for the component, using the new parameter values that were read from the Siebel Gateway Name Server. On each Siebel Server, the number of new multithreaded processes is governed by the parameter Minimum MT Servers (alias MinMTServers).

Previous component tasks that are not affected by the component reconfiguration can continue to run for some time. Therefore, the multithreaded processes hosting the tasks continue to run and the tasks occupy slots in shared memory. Because old and new multithreaded processes for the component are both running, there might be an increase in the number of multithreaded processes running on the Siebel Server computers.

Therefore, it is recommended that you run component definition reconfiguration at times when the server component workload is low, that is, when the component's existing tasks or sessions are few in number. Doing so allows the existing tasks or sessions on the old multithreaded processes to end, so that the total numbers of multithreaded processes and tasks do not exceed configured limits or exhaust system resources. When all of its tasks have ended, a multithreaded process eventually ends.

For each Siebel Server, initial sizing would have been performed, as described in Siebel Performance Tuning Guide. The total number of multithreaded processes for the component cannot exceed what is specified using the parameter Maximum MT Servers (alias MaxMTServers) and the total number of tasks cannot exceed what is specified using the parameter Maximum Tasks (alias MaxTasks).

NOTE:  Parameters set at the individual component level are not affected by component definition reconfiguration unless the parameter override is deleted on that parameter.

Before reconfiguring Siebel Server components, make sure that:

• All of the Siebel Servers running the server component designated for reconfiguration are running. This check makes sure that the server component instances receive the reconfigured parameter values.
• Any external resources that are accessed by current tasks running on the existing component configuration remain available.

  Examples of external resources include the SRF and configuration files that are defined in the component configuration.

• Any external resources that are defined in the new component configuration are available.
• Any previous component reconfiguration process has already completed. If it has not, then you might have to wait before you can reconfigure again.

  If existing multithreaded processes are still running along with reconfigured multithreaded processes, then the following error message might appear: Unable to complete reconfiguration due to insufficient process resources. Starting another reconfiguration process at this time would require more reconfigured multithreaded processes on all applicable Siebel Servers, which might exceed the limits that you configured during sizing and tuning.

To reconfigure Siebel Server components

1. Navigate to the Administration - Server Configuration screen, then the Enterprises view.
2. Select the Component Definitions view tab.
3. In the Component Definitions list, select the component definition that you want to reconfigure.
4. Click Menu, and then Start Reconfiguration.

   The Definition State field changes to Reconfiguring.

5. In the lower Component Definitions list, change the Value field of parameters that you want to reconfigure for the component.

   You can also change the values of fixed parameters, but you cannot change whether parameters are fixed.

6. After parameter values have been reconfigured, commit the new configuration by clicking Menu, and then Commit Reconfiguration.

   The new parameter values are merged at the enterprise level. To cancel the reconfiguration before it has been committed, click Menu, and then Cancel Reconfiguration.

Related Topics

Reconfiguring Component Definition Commands

Related Books

Siebel Performance Tuning Guide