Bookshelf Home | Contents | Index | Search | PDF | ![]() ![]() ![]() ![]() |
Siebel Server Administration Guide > Using the Siebel Server Manager GUI > Component Group and Server Component Administration >
Administering Component Groups and Server Components
Administering component groups and Siebel Server components involves the following steps:
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 component after the database connection has been reestablished.
Use the Server Components view to change component states. To change component states using the command-line interface, see Component Definition Commands.
To start an assigned component
- Navigate to the Siebel Servers screen.
- Click the Server Components view tab.
- In the Server Components list, select the assigned component you want to start.
- 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
- Navigate to the Siebel Servers screen.
- Click the Server Components view tab.
- In the Server Components list, select the assigned component you want to make available.
- Click Online.
After the component is enabled, its Component State field changes to Online.
Figure 12 shows an example of successfully enabling the File System Manager component.
To disable an assigned component
- Navigate to the Siebel Servers screen.
- Click the Server Components view tab.
- In the Server Components list, select the assigned component you want to disable.
- 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.
To shut down an assigned component
- Navigate to the Siebel Servers screen.
- Click the Server Components view tab.
- In the Server Components list, select the assigned component you want to shut down.
- 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
- Navigate to the Siebel Servers screen.
- Click the Server Components view tab.
- In the Server Components list, select the unavailable component you want to recover.
- Click Shutdown.
After the component shuts down, its Component State field changes to Shutdown.
- 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.
Configuring Automatic Restart
Automatic restart is an optional feature that allows Siebel Server components to automatically attempt a restart if it exits with error. For a user-defined number of times after the error, the Siebel Server will try to restart the component. This feature greatly reduces the administration of Siebel Server components. By default, this feature is disabled for all components.
You can configure automatic restart using the following parameters:
- Auto Restart
- Minimum Up Time
- Number of Restarts
The Minimum Up Time and Number of Restarts parameters combine to determine the number of restart attempts in a time interval allowed for a component (NumRestart * MinUpTime). If a component instance cannot be restarted after this time interval, no new restart will be attempted (therefore, the component instance will not be running). For descriptions of these parameters, see Parameters.
Typically, you should set these parameters at the component level, but depending on your system configuration, you may want to set these parameters at the Siebel Enterprise Server or Siebel Server levels. For information on configuring parameters, see Parameter Administration.
Configuring Database Reconnect
Database reconnect is an optional feature that enables Siebel Server components to automatically attempt a database connection following a database or network failure. At regular intervals after the failure, Siebel Server components will try to reconnect to the database and resume any tasks that were rolled back due to the failure. This feature greatly reduces the administration of Siebel Server components.
Without database reconnect, a database or network failure will cause the Siebel Server component to shut down and all running tasks to crash. You will then need to manually restart all components that were shutdown and rerun all tasks that crashed.
Database reconnect is enabled for all background mode and batch mode Siebel Server components, with exception to the Enterprise Integration Manager and Database Extract Siebel Server components. This feature is disabled for all interactive mode Siebel Server components (such as Synchronization Manager and all Object Manager components).
You can configure database reconnect using the following parameters:
- Number of Retries
- Retry Interval
- Retry Up Time
For descriptions of these parameters, see Parameters. You should set these parameters at the same level as the automatic restart parameters (this will typically be the component level). For information on automatic restart, see Configuring Automatic Restart. For information on configuring parameters, see Parameter Administration.
Administering Component Groups
A component group may be in one of several states. The run state is dependent on the enable state; only component groups that have an Online enable state when the Siebel Server was started can have a run state of Online or Running:
- Online. Every component within the component group is enabled to run tasks.
- Running. Every component within the component group is enabled, and at least one component within the component group is running a task.
- Shutdown. Every component within the component group is shut down. Tasks cannot run for any components within the component group.
- Part shutdown. At least one component within the component group is shut down or shutting down.
- Offline. Every component within the component group is offline.
- Part offline. At least one component within the component group is offline or unavailable.
- Starting up. At least one component within the component group is starting up.
You will need to enable a component group by setting its run state to Online before tasks can be started for components within the component group. To change the component group run state, use the Server Component Groups view as shown in Figure 15.
To enable an assigned component group
- Navigate to the Siebel Servers screen.
- Click the Server Component Groups view tab.
- In the Siebel Servers list, select the Siebel Server on which the component group is assigned.
- In the Server Component groups list, select the component group you want to enable.
- Click Online.
After the component group is enabled, its Run State field changes to Online.
To disable an assigned component group
- Navigate to the Siebel Servers screen.
- Click the Server Component Groups view tab.
- In the Siebel Servers list, select the Siebel Server on which the component group is assigned.
- In the Server Component groups list, select the component group you want to disable.
- Click Offline.
After the component group is disabled, its Run State field changes to Offline.
To start an assigned component group
- Navigate to the Siebel Servers screen.
- Click the Server Component Groups view tab.
- In the Siebel Servers list, select the Siebel Server on which the component group is assigned.
- In the Server Component groups list, select the component group you want to start.
- Click Startup.
When the component group starts, its Run State field changes to Starting Up. After the component group is started, its Run State field changes to Online.
To shut down an assigned component group
- Navigate to the Siebel Servers screen.
- Click the Server Component Groups view tab.
- In the Siebel Servers list, select the Siebel Server on which the component group is assigned.
- In the Server Component groups list, select the component group you want to shut down.
- Click Shutdown.
After the component group shuts down, its Run State field changes to Disabled.
NOTE: To make a shutdown persistent across Siebel Server restarts for a component group, first disable the component group before shutting it down.
Monitoring Component Group Status
Use the Component Groups views to monitor the status of component groups.
To monitor Siebel Server status for component groups
- Navigate to the Component Groups screen.
- Click the Component Group Servers view tab.
- In the Enterprise Component Groups list, select the component group you want to monitor.
- In the Component Group Servers list, check the State field for the Siebel Server (or servers) on which the component group is running.
To monitor component status for component groups
- Navigate to the Component Groups screen.
- Click the Component Group Components view tab.
- In the Enterprise Component Groups list, select the component group that contains the components you want to monitor.
- In the Component Group Components list, check the Run State field of the components in the component group.
To monitor task status for component groups
- Navigate to the Component Groups screen.
- Click the Component Group Tasks view tab.
- In the Enterprise Component Groups list, select the component group for which you want to monitor task status.
- In the Component Group Tasks list, check the Status field of all running tasks in the component group.
Bookshelf Home | Contents | Index | Search | PDF | ![]() ![]() ![]() ![]() |
Siebel Server Administration Guide Published: 23 June 2003 |