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:

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

  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.
  5. 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.

Figure 11. Starting an Assigned Component

Click for full size image

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.
  4. Click Online.
  5. 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.

Figure 12. Enabling an Assigned Component

Click for full size image

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.
  5. 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 13. Disabling an Assigned Component

Click for full size image

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.
  5. 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.

Figure 14. Shutting Down an Assigned Component

Click for full size image

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.
  5. After the component shuts down, its Component State field changes to Shutdown.

  6. Click Startup.
  7. 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:

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:

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:

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.

Figure 15. Administering Server Component Groups

Click for full size image

To enable an assigned component group

  1. Navigate to the Siebel Servers screen.
  2. Click the Server Component Groups view tab.
  3. In the Siebel Servers list, select the Siebel Server on which the component group is assigned.
  4. In the Server Component groups list, select the component group you want to enable.
  5. Click Online.
  6. After the component group is enabled, its Run State field changes to Online.

To disable an assigned component group

  1. Navigate to the Siebel Servers screen.
  2. Click the Server Component Groups view tab.
  3. In the Siebel Servers list, select the Siebel Server on which the component group is assigned.
  4. In the Server Component groups list, select the component group you want to disable.
  5. Click Offline.
  6. After the component group is disabled, its Run State field changes to Offline.

To start an assigned component group

  1. Navigate to the Siebel Servers screen.
  2. Click the Server Component Groups view tab.
  3. In the Siebel Servers list, select the Siebel Server on which the component group is assigned.
  4. In the Server Component groups list, select the component group you want to start.
  5. Click Startup.
  6. 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

  1. Navigate to the Siebel Servers screen.
  2. Click the Server Component Groups view tab.
  3. In the Siebel Servers list, select the Siebel Server on which the component group is assigned.
  4. In the Server Component groups list, select the component group you want to shut down.
  5. Click Shutdown.
  6. 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

  1. Navigate to the Component Groups screen.
  2. Click the Component Group Servers view tab.
  3. In the Enterprise Component Groups list, select the component group you want to monitor.
  4. 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

  1. Navigate to the Component Groups screen.
  2. Click the Component Group Components view tab.
  3. In the Enterprise Component Groups list, select the component group that contains the components you want to monitor.
  4. 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

  1. Navigate to the Component Groups screen.
  2. Click the Component Group Tasks view tab.
  3. In the Enterprise Component Groups list, select the component group for which you want to monitor task status.
  4. In the Component Group Tasks list, check the Status field of all running tasks in the component group.

 Siebel Server Administration Guide, Version 7.5, Rev. C 
 Published: 18 April 2003