Siebel Installation Guide for UNIX: Servers, Mobile Web Clients, Tools > Installing the Siebel Server >

Preparing to Run Siebel Server Components After Installing

When you installed your Siebel Server, you specified which server component groups should be enabled. Before you deploy your Siebel Server, you should verify that server components you require are enabled. It is also recommended to disable any server components you do not require.

After installing the Siebel Server, you must synchronize any batch components before you can operate them. You should also do this after upgrading the Siebel Database.

In an upgrade scenario, after you install Siebel Servers and after you upgrade the Siebel Database, the S_SRM_ACTION and S_SRM_ACT_PARAM tables are truncated, with the result that component job definitions are deleted. To help you re-create these definitions, it is recommended that you save component job definitions before you upgrade.

For example, you can export data from the S_SRM_ACTION table using Siebel EIM, then import this data into the same table after upgrading the database and synchronizing batch components. For more information about using Siebel EIM, see the Siebel Enterprise Integration Manager Administration Guide.

For detailed information about enabling or disabling components after installing, synchronizing batch components, creating server component job definitions, using Server Manager, and related topics, see the Siebel System Administration Guide.

Siebel Enterprise Server and Siebel Server parameter settings can be migrated from one Siebel application environment to another by using the configuration upgrade utility (cfgmerge). Other customized application data can be migrated by using the Application Deployment Manager (ADM). For detailed information about using these utilities, see Going Live with Siebel Business Applications.

Siebel Installation Guide for UNIX: Servers, Mobile Web Clients, Tools