In this article we are going to discuss about server configuration activities under following categories :

•Define component definitions •Reconfigure component definitions •Synchronize component •Set server and component event logging •Use component alerts •Create and define job templates •Back up and restore enterprise configuration

1. Define Component Definitions

• Tailor existing components or create custom components using these steps:

2. Reconfigure Component Definitions

• Is accomplished through the Component Definitions applet drop-down menu

• Start Reconfiguration:

Opens existing component parameters for modification

• Commit Reconfiguration:

Commits the updated Component Definition

• Cancel Reconfiguration:

Cancels the current reconfiguration, component definition remains unaltered

3. Synchronize Components

• A required post-installation task for executing components on the Siebel Server

<>Makes enabled components available to the Siebel Enterprise

• Navigate to Administration – Server Configuration > Enterprises

4. Set Server Event Logging

• Use the Server Event Configuration view to set the log level of Siebel Server event types

5. Set Component Event Logging

• Use the Component Event Configuration view to set the log level of component event types

6. Use Component Alerts

• Traps information about the failure of tasks and unavailability of components and sends an email alert to the Administrator

• Examples:

<> A component fails to restart

<> Critical system throughput thresholds are hit

• Additional alerts and parameters can be set up

7. Create and Define Job Templates

• Create and define job templates for repeating jobs that have unchanging parameters

<> Navigate to Administration – Server Configuration > Job Templates

8. Back Up the Enterprise Configuration

• Use Server Manager to back up a working copy of siebns.dat

1. Navigate to Administration – Server Configuration

2. Locate the backup in the Administration directory of the Siebel Server root directory

9. Restore the Enterprise Configuration

• Restore a previous Enterprise configuration with these steps:

1. Shutdown the Siebel Gateway Name Server and the Siebel Server

2. Replace the existing siebns.dat file with a working backup

3. Start the Siebel Gateway Name Server and the Siebel Server

We are expecting feedback/comment from you about this article, which will help us to improve.In next article we will discuss about Server Management Activities

Related posts:

1. EIM tasks log unable to trace the SQL Last week a reader of our blog comes up with...
2. Siebel Recommended Practices – Server Administration I am sharing few best practices for Server Administration, These...
3. Changes / Enhancement in Siebel 8.0 Version Lets discuss new deployment change in Siebel 8.0 version onwards....

Related posts brought to you by Yet Another Related Posts Plugin.

Your Ad Here