Siebel Security Hardening Guide > Securing Siebel Business Applications >

About Disabling Siebel Components

Most of the components required to run Siebel Business Applications are common to all Siebel Business Applications. However, the components that are required in a specific Siebel environment vary according to factors such as the following:

• Whether the Siebel application runs in high-interactivity or standard-interactivity mode
• Whether wireless or handheld clients are supported
• The features provided by the Siebel application, for example, Siebel Sales uses a number of components that are not required by applications such as Oracle's Siebel Marketing or Oracle's Siebel Employee Relationship Management application

During the Siebel Server configuration process, you specify the components and component groups you want to enable for a Siebel Server. It is not necessary to run all components on all Siebel Servers in an Enterprise. Verify that only the components or component groups you require on each Siebel Server are enabled; disable or unassign component groups that are not required.

The following are some examples of Siebel Server components that do not have to be enabled on all Siebel Servers in an Enterprise:

• SvrTblCleanup. The SvrTblCleanup component deletes completed and expired Server Request records for all Siebel Servers in a Siebel Enterprise from the S_SRM_REQUEST table. Enable this component on only one Siebel Server in a Siebel Enterprise.
• SCBroker. Disable the SCBroker component on Siebel Servers that host only batch mode components, for example, Workflow components.
• SRProc. Disable the Server Request Processor (alias SRProc) component on Siebel Servers that run only Application Object Manager components and that do not run batch mode components.

Components can be disabled using the Siebel Administration - Server screens or the srvrmgr command-line interface. For information on enabling and disabling components, see Siebel System Administration Guide.