Siebel 8.
0 Essentials
Server Management
1 of 25
Module 10: Server Management
Module Objectives
To monitor the state of the enterprise, and individual servers and components within that enterprise To Perform administrative tasks on the enterprise, such as: Managing components Backing up and restoring the enterprise Setting logging options Submitting jobs
Server Management
3 of 25
Server Administration
After components have been enabled and their parameters
have been defined, the following administration tasks are performed:
Monitor the system Change component parameters or component states, preferably without shutting down the server Back up the system after making these changes Submit batch jobs for processing
These tasks are done in the Administration Server
Management screen
A command-line interface is also available Useful for using scripts to interact with the enterprise
Server Management
4 of 25
Server Groups
Add servers to a Server Group using the command-line tool:
change attribute groupname=<group name> for server <server name> Connect to all servers in the group simultaneously: srvrmgr /g <gateway> /e enterprise /z <group name> /u <user> /p <password> Performing groupwide manipulations such as changing parameters: change parameter NotifyHandler=newHandler
Changes the parameter for all servers in the server group
Server Management
5 of 25
Monitor the Enterprise
Enterprise can be monitored from the Administration Server
Management screen
Provides status icons for servers, components, jobs, tasks,
sessions, and the enterprise
Server Management
6 of 25
Monitor Sessions
Session Monitor is used to monitor users logged in and their
current activity
Sessions are tasks running the associated Object Manager
This is done from Administration Server Management > Sessions
Server Management
7 of 25
Manage Component States
Use the Administration Server Management > Servers screen to
Manage components across the entire enterprise from the Manage components on a particular server from the
Components may be paused, resumed, started
up, or shut down
Server Management
8 of 25
Component States
Running: When the component is available and at least one
component task is currently running Online: When the component is available but no component tasks are currently running Unavailable: When the component is unavailable and no component tasks are running Paused: When the component is online but is not accepting new tasks Shutting Down: When the server is shutting down; currentlyrunning tasks will execute to completion, but no new tasks can be run Shutdown: When the server component is shut down
Server Management
9 of 25
Change Component Parameters
Change component parameters by changing the Value or Value
on Restart Examine the Effective setting to see when the parameter change will become effective
Server Management
10 of 25
Reconfigure Component Definitions
Modifies component parameters without shutting down the
server(s)
Useful during site migrations or application updates Useful when changing multiple parameters and changes should all be performed at once For example, when changing both a user name and a password parameter, changing one at a time would lead to authentication issues
During reconfiguration:
Tasks started before and during reconfiguration continue to run with the old parameters Tasks started after the reconfiguration is committed run with the new parameters
Server Management
11 of 25
Reconfigure Component Definitions
Navigate to the Administration
Server Configuration > Enterprises screen Start Reconfiguration:
Opens existing component parameters for modification
Commit Reconfiguration: Commits the updated
Component Definition All tasks started after the commit run with the new parameters
Cancel Reconfiguration: Cancels the current reconfiguration; component definition remains unaltered
Server Management
12 of 25
Back Up the Enterprise
It is suggested to have a back up of the enterprise after
making any configuration changes such as modifying component parameters
Creates a backup copy of [Link] [Link] stores information about components, parameters, and servers May also be used for backup or migration purposes However, do not try to manually duplicate this file File is in use as long as Siebel Gateway Name Server is
running
Server Management
13 of 25
Restore the Enterprise
Restore a previous enterprise configuration with these steps:
1. Shut down the Siebel Gateway Name Server and the Siebel Server 2. Replace the existing [Link] file with a working backup 3. Start the Siebel Gateway Name Server and the Siebel Server
Server Management
14 of 25
Server Event Logging
Server events can be monitored by setting log levels Navigate to Administration - Server Configuration > Servers >
Server Event Configuration
Set the log level for each Siebel Server event of interest
Server Management
15 of 25
Log Levels
There are six available logging levels for server events: 0: Fatal 1: Errors 2: Warnings 3: Informational 4: Details 5: Diagnostic
Higher log levels generate larger log files which may affect system
performance, hence it is recommended practice to only use these levels when troubleshooting
Server Management
16 of 25
Component Event Logging
Use the Component Event Configuration view to set the log
level of component event types
Server Management
17 of 25
Examine Logs
Each task creates a log of its execution
Server Management
18 of 25
Examine Log Files
View the log file on the Siebel Server
Server Management
19 of 25
System Alerts
System alerts collect information about the failure of tasks or
unavailability of components, and send email alerts to administrators Examples:
A component fails to restart Critical system throughput thresholds are achieved
Create additional alerts to notify additional individuals or to
handle different types of alerts
Server Management
20 of 25
Using System Alerts
To configure a component to use these system alerts:
Navigate to Administration Server Configuration > Servers > Components Select the component to be configured Specify the notification handler for that component It is one of the system alert profiles previously created
Server Management
21 of 25
Submit Batch Jobs
Navigate to Administration Server Management > Jobs Create a new job or copy an existing job
Job templates as well as components are listed for new jobs
Server Management
22 of 25
Submit Batch Jobs
Specify job parameters Optionally, you can schedule the job to repeat at regular
intervals or to run on a preferred server if it is available Submit the job
Server Management
23 of 25
Manage Batch Jobs
Cancel, pause (hold), or resume jobs from the Administration
Server Management > Jobs screen
Monitor the progress of the job from the Administration Server
Management > Tasks screen
Server Management
24 of 25
Module Highlights
Monitor the state of the enterprise, servers, components, tasks,
jobs, and sessions from the Administration - Server Management screen Managing different types of component states Change component parameters
May require reconfiguring component definitions
Back up the enterprise after changing configurations
Set logging options and system alerts to monitor the system
Submit and manage batch jobs
Server Management
25 of 25
