Siebel Server Administration Guide

Siebel Server Administration

    Server Manager = Set of UI Views used to manage Siebel Enterprise
        Used to:

•             Enable, disable, start/stop components
•             Assign components to specific SSs
•             Stop, Pause, Resume server tasks
•             Monitor status of Components + Tasks (i.e. EIM job)

        Set parameters for Servers + Components (tasks)
        When invoked:
            connects to Siebel GW Server + knows exactly which each Siebel Server in Enterprise is “doing” + which are available for new connections.
            Then connects to each Siebel Server w/in Enterprise
        Consists of:
            Component Groups; Components; Enterprise Configuration; Enterprise Operations; Servers; Tasks
        Two ways to use:
            UI
            Command Line
                I.e. invoke batch jobs, background components
                    (i.e. Workflow Monitor or Batch Jobs via Enterprise scheduler)
    Server Component = type of program performs a specific job; one or more instances (i.e. multi-threaded)
        EIM à Importing + Exporting data in batch mode
        Assignment Manager à Assigned work (data) based on business rules
    Component Group (CG) = logical groupings of related server components
        I.e. Workflow Management CG
        Components are defined at the ES level in Groups; Component Groups are then assigned to one or more Siebel Servers.
    Component Definitions

•         Parameters for a component on a specific server.
•         User can customize existing components or create customer components

        Example:

•             Modify Component Definition so that same parameter values are in effect each time task executes

                (i.e. WF Policies at Dept of Ed had custom start-up parameters)
            Create EIM component specific to your client

•     Task à Instance of a component executing; Can be run concurrently
•     Parameters à used on startup of a task; Start Reconfiguration command allows component parameters to be changed with stopping/starting the Siebel Server

        Dynamic

•             New values apply to subsequent started tasks unless overridden at lower level
•             Effective Immediately

        Static

•             New values do not apply to subsequently started tasks
•             Not effective immediately (i.e. Max Tasks for Server Request manager.. need to re-start)

        Parameter Hierarchy: (highest) EnterpriseàServeràComponent DefinitionàServer ComponentàTasks (lowest)
    Server Component Modes
        (1) Batch Components à task runs until completion and then stops;
            Examples:
                EIM, Generate New Database, Generate Triggers, Database Extract
            Synchronizing Batch tasks:
                Required post-installation task; sends list of components definitions to GW Server for later use
                Also needs to be performed whenever batch component definitions are updated or new component definitions are created
            Starting
                started manually via UI or
                started manually Command Line.
        (2) Background Components à task runs continuously until the component is shut down (repetitively, defined by sleep time).
            Examples:
                Transaction Processor, Transaction Router
            Started
                Started manually via Command Line or
                Started automatic upon server startup.
                    If Default tasks > 0
                Shutdown by shutting down Siebel Server or Server Admin with “shutdown”
        (3) Interactive Components à Runs in response to client requests (no need to manually start).
            Examples:
                Synchronization Manager/Object Manager
            Stops when client disconnects/task completed
    Component States

•         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 the Siebel Server + new tasks can also start
•         Offlineà Currently running tasks will continue to run, but new tasks cannot be started
•         Shutdownà No processes are running + no new
•         Unavailableà Multi-threaded components that should be running are not, run time error is being encountered
•             Should look at log files

*Can disable components to save resources on a given siebel server, can disable across enterpise too*

    Monitoring Tasks
        States:

•             Starting up…
•             Running….
•             Paused…
•             Shutting Down…
•             Completed…
•             Exited with Error…
•             Killed… à could not shut down cleanly, forced to stop…
•            Task information log

        0 = Fatal
        1 = Errors
        2 = warnings
        3 = Informational
        4 = Details

at 12/04/2011