■ Administering Component Groups
■ Configuring Automatic Restart
■ Configuring Database Reconnect
■ Monitoring Component Group Status
Administering Siebel Server Components
A Siebel Server component may be in one of five component states: Running, Online, Offline, Shutdown, or Unavailable.
The Siebel Server component state is dependent on the assignment state of the component group to which it belongs; only Siebel Server components within assigned component groups when the Siebel Server was started can be Running or Online:
■ Running. Indicates that tasks are currently running for the Siebel Server component on the Siebel Server, and new tasks are allowed to start (up to the value of the Maximum Tasks parameter for the component). When the Siebel Server starts up, all background-mode components for which processes are started by default (components with a Default Tasks parameter set to a nonzero value) will start.
■ Online. Indicates that tasks are currently not running for the Siebel Server component, but new tasks may be started through the Siebel Server Manager (or in response to client requests, for interactive-mode components). When the Siebel Server starts, all components for which processes are not started by default will be online. When a new task is started for the component, the component state changes to Starting Up during the initialization phase and then to Running.
■ Offline. Indicates that new tasks may not be started for the component, though current running tasks can continue running (for background-mode components) or run to completion (for batch-mode and interactive-mode components). You may wish to disable an individual component in order to perform a system maintenance operation outside of the Siebel Server. For example, you may disable the Synchronization Manager component to do a file system reorganization on the docking subdirectory.
To minimize the number of multithreaded processes that will be started on the Siebel Server, you may want to disable components that you do not plan to run. You may also want to disable components due to database licenses. If you have exceeded the maximum licensed connections for your database, then you may want to disable the Siebel Server components that you will not be using. You should only disable components for which you do not plan to run tasks across the entire enterprise. Setting the Min MT Servers parameter to 0 for
multithreaded Siebel Server components renders the server component unable to run tasks.
An offline component may be set to Online (or Started, if there are still tasks running for the offline component) or Shutdown, in which case any running tasks will be stopped as cleanly as possible.
■ Shutdown. Indicates that processes are not running for the component and new tasks may not be started. Each task running when the component shuts down is stopped as soon as possible. All components will be set to Shutdown when the Siebel Server shuts down, with the exception of the Siebel Server Manager component, which remains Online in order to perform administrative
commands executed by the Siebel Server Manager. Background-mode
components that are set to Shutdown but have a Default Tasks parameter set to a nonzero value may be set to Online or Started.
■ Unavailable. Indicates that processes are not running for the component when a Siebel Server process should be running. Multithreaded Siebel Server
components can go into an Unavailable component state when the Min MT Servers parameter is set to a value greater than 0 and no Siebel Server processes are actually running for that component. In this case, the Siebel Server
component may exit with an error and become unavailable because it failed to initialize. Siebel Server components may also go into this state if the database connection is down. In this case, you need to restart the Siebel Server
Use the Server Components view to change component states. To change component states using the command-line interface, see “Component Definition Commands” on page 137.
To start an assigned component
1 Navigate to the Siebel Servers screen.
2 Click the Server Components view tab.
3 In the Server Components list, select the assigned component you want to start.
4 Click Startup.
When the component starts, its Component State field changes to Starting Up. After the component is started, its Component State field changes to Running. Figure 11 shows an example of successfully starting the Call Center Object Manager component.
To enable an assigned component
1 Navigate to the Siebel Servers screen.
2 Click the Server Components view tab.
3 In the Server Components list, select the assigned component you want to make available.
Figure 12 shows an example of successfully enabling the File System Manager component.
To disable an assigned component
1 Navigate to the Siebel Servers screen.
2 Click the Server Components view tab.
3 In the Server Components list, select the assigned component you want to disable.
4 Click Offline.
After the component is disabled, its Component State field changes to Not Online.
Figure 13 shows an example of successfully disabling the Generate New Database component.
Figure 12. Enabling an Assigned Component
To shut down an assigned component
1 Navigate to the Siebel Servers screen.
2 Click the Server Components view tab.
3 In the Server Components list, select the assigned component you want to shut down.
4 Click Shutdown.
After the component shuts down, its Component State field changes to Shutdown.
Figure 14 shows an example of successfully shutting down the Generate New Database component.
To recover a server component from an Unavailable component state
1 Navigate to the Siebel Servers screen.
2 Click the Server Components view tab.
3 In the Server Components list, select the unavailable component you want to recover.
4 Click Shutdown.
After the component shuts down, its Component State field changes to Shutdown.
5 Click Startup.
When the component starts, its Component State field changes to Starting Up. After the component has started, the Component State field changes to Running.