07ess server administration

8/10/2019 07ESS Server Administration

1/36

Module 7: Server Administration


2/36

2 of 36Module 7: Server Administration

Module Objectives

After completing this module you will be able to:

Use Server Manager to administer your Siebel Enterprise

Why you need to know

Server Manager enables you to perform server administration

duties required for your Siebel application


3/36


Server Manager

Is the native management console that allows you to manage

the Siebel Enterprise Server, individual Siebel Servers, and

Siebel Server components and component groups


4/36


Server Manager Continued

Is used for a variety of administration duties, including:

Enable, disable, start up, and shut down components

Assign components to execute on specific Siebel Servers

Stop, pause, and resume server tasks

Monitor status for components and tasks

Set parameters for servers and components

Backup of the Siebel Gateway Name Server data file, siebns.dat

Contains configuration information from the Enterprise and Siebel

Servers


5/36


Administering the Siebel Enterprise

Server Manager connects to the Siebel Gateway

Gathers all connectivity information for each Siebel Server within

the Siebel Enterprise

Server Manager then connects to each Siebel Server within the

Enterprise

Displays servers for each enterprise supported by the SiebelGateway

Starts a Server Manager task on

each Siebel Server


6/36


Using Server Manager

There are two ways to use Server Manager

From the Siebel

application

interface

From thecommand line


7/367 of 36Module 7: Server Administration

Server Components

A component is a type of program that performs a specific job

One or more instances can execute as a task on the Siebel

Server

The standard Siebel application comes with many server

components, for example:

Enterprise Integration Manager For importing and exporting data

Assignment Manager

For assigning work based on business rules

Generate Database Triggers

For monitoring the database for user-defined conditions



Component Groups

Component Groups consist of related server components

Select Server Administration > Enterprise Configuration to

enable or disable component groups

Click the menubutton

enable or disablecomponent group



Component Groups Continued

Example: The Workflow Management component group

consists of five server components

Component

group must be

enabled

to utilize any

of the server

components



Component Definitions

Use to customize existing components or create custom

components, for example: Modify component definition so that same parameter values are

in effect each time the task executes

Create EIM component definition called Import Accounts to only

import accounts

Select Server Administration > Enterprise Configuration >Component Definitions

Parameters for the Call

Center Object Manager

component



Tasks

When a component executes, it is called a task

A task is an instantiation of a component and runs in computer

memory

In most cases, the same component may be instantiated many

times

Example: Multiple Batch Assignment tasks can run concurrently onthe Siebel Server

Tasks can run

simultaneously



At startup, a task reads parameters and executes according to

their values

Parameters

Component

parameters for Batch

Assignment



Parameters: Named Subsystems

Are groupings of defined enterprise parameters used by some

server components, such as the Application Object Manager

Named Subsystems

for Application Object

Manager

List of parameters for

the selected Named

Subsystem



Parameters: Named Subsystems Continued

Can be parameters that have a context dependency, for

example: ServerDataSrc is a named subsystem that specifies the data

source connection for the Application Object Manager component

Specifies the server database

connectionon SQL Server and DB2,this is the ODBC data source name



Parameters: Dynamic and Static

Dynamic

New values will apply to subsequent started tasks unless values

are overridden at a lower level

Static

New values will not apply to subsequent started tasks until Siebel

Server System Service is stopped and restarted

Dynamic parameters

are effective

immediately on the

Siebel Server

Static parameters are

not effective immediately

on the Siebel Server



Parameters are set at any of these levels

Parameters set at the enterpriselevel are inherited for the entireenterprise

Parameters set at the tasklevel override the same parametersset at a higher level

Setting Parameters

Server

Enterprise

Component Definition

Named Subsystem

Task

Server Component

Lowest level

Highest level



Server Component Modes

A server component executes in one of three modes

Batch

Background

Interactive



Batch Components

The task runs until completion, and then it stops

Started manually via:

Graphical user interface

Command-line interface

Examples:

Subset of Enterprise Application

Integration component group

Subset of Remote component

group

Subset of Workflow Management

component group



Synchronizing Batch Components

A required post-installation task for executing batch

components on the Siebel Server

Sends the list of component definitions to the Siebel Gateway for

later use

Select Server Administration > Enterprise Configuration >

Batch Component Admin Click the Synchronize button

Synchronized components



Background Components

The task runs continuously until the component is shut down

Runs repetitively, defined by a sleep time Started:

Manually via UI

Select Server Administration > Servers> Server Components

Manually via command line

Automatically upon server startup

Examples:

Subset of Remote

component group

Subset of Workflow

Management component

group



Interactive Components

The task runs in response to client requests

No need to manually start

The task stops when the client disconnects

Examples

Subset of System Management

component group

Subset of Remote componentgroup

Subset of Siebel Call Center

component group



Component States

A server component may be in one of five states

State Description

Online Tasks are currently not running for the assigned component, but

new tasks can be started.

Running Tasks are currently running for the assigned component on theSiebel Server, and new tasks are allowed to start.

Offline Currently running tasks continue to run, but new tasks cannot be

started for the component.

Shutdown No processes are running for the component, and new tasks

cannot be started.Unavailable Multi-threaded components that should be running are not,

indicating a run-time error.



Managing a Component

Select Server Administration > Servers > Server Components

to change a server component state

Select the component and click the appropriate action



Starting a Batch Task

Select Server Administration > Enterprise Operations >

Component Requests

2. Modify parameters

1. Create new request

and select component

3. Submit request


25/36


Starting a Background Task

Via the UI

Tasks with the parameter Default Tasks > 0 will start automaticallyupon Siebel Server startup

Using the command line

Example: Start a Workflow Monitor Agent task

ParametersComponent alias Siebel Server

Example: Transaction Router will

automatically start on the server


26/36


Monitoring a Task

A task updates its state during execution

Can be in one of the following states

State Description

Starting up Indicates that the task has been started

Running Indicates that the task is executing normally

Paused Indicates that the task has been temporarily placed in a

suspended state

Shutting Down Indicates that the task has been instructed to stop, or the

component or server is being shut down

Completed Indicates that the task ran to completion and exited normallyExited with Error Indicates that the task encountered an error during its

processing and exited

Killed Indicates that the process was not able to shut down cleanly,

and had to be forced to shut down


27/36


Viewing Task Information

Each task creates a log of its execution when logging has been

enabled

View log via UI by drilling down on task number

to view Task

Information Log

Drill down on

task number


28/36


Viewing Task Information Continued

View log file on the Siebel Server

Note

the task

number

View the file in log directory


29/36


Event Logging

Uses logging levels to determine the amount of information that

is written to the log file

Level Description

0 Fatal1 Errors

2 Warnings

3 Informational

4 Details

5 Diagnostic


30/36


Configuring Siebel Server Event Logging

Use the Server Event Configuration view to set the log level of

Siebel Server event typesSelect the Siebel Server for which

you want to configure an event

Select the event type you want to

configure and enter the value inthe log level field


31/36


Configuring Component Event Logging

Use the Component Event Configuration view to set the log

level of component event types

Select the component for which

you want to configure an event

Select the event type you want to

configure and enter the value inthe log level field


32/36


Siebns.dat

Is a data file that stores Siebel Gateway Name Server

information

Provides the persistent backing of Siebel Server configuration

information, including:

Definitions and assignments of component groups and components

Operational parameters

Connectivity information

Specifies the Siebel Server configuration at startup

Stores Enterprise and Siebel Server configuration changes


33/36


Backing Up the Enterprise Configuration

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

1) Enter the command: backup namesrvr

2) Locate backup at C:\sea750\gtwysrvr\ADMIN


34/36


Restoring the Enterprise Configuration

Restore a previous Enterprise configuration with the steps:

1) Shutdown the Siebel Gateway Name Server and the Siebel

Server

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

3) Start up the Siebel Gateway Name Server and the Siebel Server


35/36


Summary

This module showed you how to:

Use Server Manager to administer your Siebel Enterprise


36/36

Lab

In the lab you will:

Enable and synchronize server components

Use command line Server Manager

Restore the Siebel Enterprise configuration to a previous

Enterprise configuration

Run a server task Set logging levels

Create a new component definition

07ess server administration

Documents