About the Siebel Server

The Siebel Server is the middle-tier platform that supports both back-end and interactive processes for every Siebel client. These processes are components within the Siebel Server architecture and support functions like the following:

Mobile Web Client synchronization
Operation of business logic for Siebel Web clients, as well as connectivity and access to the Siebel database and Siebel File System
Integration with legacy or third-party data
Automatic assignment of new accounts, opportunities, service requests, and other records
Workflow management

The Siebel Server supports both multiprocess and multithreaded components, and can operate components in background, batch, and interactive modes. Many of the Siebel Server components can operate on multiple Siebel Servers simultaneously to support an increased number of users or larger batch workloads. For more information about Siebel Server components, see "About Siebel Server Components".

Note:

Make sure that your server hardware and software meet minimum standards. For more information, see the Certifications tab on My Oracle Support.

About the Siebel Server System Service

The Siebel Server runs as a system service that monitors and controls the state of every Siebel Server component operating on that Siebel Server. Each Siebel Server is an instantiation of the Siebel Server system service within the current Siebel Enterprise Server.

The Siebel Server runs as a Windows service in a Windows environment and a daemon process in a UNIX environment. The system process associated with the Siebel Server is siebsvc.exe on Windows and siebsvc on UNIX. Each running Siebel Server has a corresponding Siebel Server system process. For information about administering the Siebel Server system service, see "Administering the Siebel Server System Service".

During startup, the Siebel Server system service performs the following sequential steps:

Retrieves configuration information from the Siebel Gateway Name Server. For information about the Siebel Gateway Name Server, see "About the Siebel Gateway Name Server".
Creates a shared memory file located in the admin subdirectory of the Siebel Server root directory on Windows and the sys subdirectory on UNIX. By default, this file has the following name:

Enterprise_Server_Name.Siebel_Server_Name.shm

The total shared memory consists of a fixed amount for the Siebel Server itself, a block for each server component running on the server, and a block for each task.

Prior to creating the SHM file, the shared memory for the Siebel application executables is built up in the RAM of the computer by using the information retrieved from the Siebel Gateway Name Server. This process can use significant amounts of memory. After the creation of the SHM file, the Siebel Server system service releases this memory. The Siebel Server system service deletes this file when it shuts down.

Note:

If the Siebel Server system service is improperly shut down, then the SHM file might not be deleted by the Siebel Server system service. In this case, delete (or rename) this file before restarting the Siebel Server system service. If this file is not visible, then it might be a hidden file.

Siebel Connection Broker (alias SCBroker) server component opens a TCP port to accept inbound Application Object Manager requests. If there are multiple instances of SCBroker on this Siebel Server, then all of the instances listen on the same port.
Opens TCP ports dynamically for non-Application Object Manager components as necessary, such as Workflow Process Manager.
Forks single-threaded and multithreaded processes for background mode components enabled on the Siebel Server. The previously created ports are inherited to these processes. For more information about these processes, see "About Server Component Processes (Shells)".
When server component processes start, each process updates the shared memory table with component availability and status information. SCBroker and SRBroker use this information for load balancing and routing purposes.
Archives log files by moving the current log directory to the logarchive directory.

Note:
If the log or logarchive directory is locked or inaccessible, then a log archive is not created.

About Siebel Server Manager

The Siebel Server Manager is the native management and administration interface for the Siebel Server and Siebel Enterprise Server. The Siebel Server Manager allows you to configure the parameters governing the operation of each component, and determine on which Siebel Servers a given component can operate.

Use the Siebel Server Manager to do the following:

Start, stop, pause, and resume Siebel Servers, components, and tasks.
Monitor the status and collect statistics across the Siebel Enterprise Server, Siebel Servers, components, and tasks.
Manage the configuration of the Siebel Enterprise Server, Siebel Servers, components, and tasks.

You can operate the Server Manager by using one of two interfaces:

The graphical user interface, or GUI, by using the server administration views in the Siebel application client.

Use the Server Manager GUI for most administrative duties because it includes greater user interface functionality (including the ability to search for and sort various fields within views) and a more intuitive view into the operation of Siebel Servers than does the command-line interface.
The command-line interface, or the srvrmgr program.

Use the command-line interface for batch-mode processing, because it can run from batch scripts by invoking script files with administration commands that must be run on a regular basis.

The Server Manager (both the GUI and the command-line interface) connects to the Siebel Gateway Name Server, which contains availability and connectivity information for the Siebel Servers within the Siebel Enterprise Server. The Server Manager then connects with each of the Siebel Servers and starts a Server Manager component task.

Note the following behavior:

If you access the GUI, then Server Manager creates a task on every running Siebel Server.
If you access the command-line interface without specifying a specific Siebel Server, then Server Manager creates a task on every running Siebel Server.
If you start the command-line interface while specifying a specific Siebel Server, by using the /s or -s flag, then Server Manager creates a task on that specific Siebel Server alone, and all of the commands are targeted to that Siebel Server at the server level.

On each Siebel Server, the Server Manager task:

Handles administration commands from the Server Manager
Executes requested functions
Returns each operation's results to the Server Manager

Note:
Each session of Server Manager creates a separate Server Manager task. Therefore, you create a new Server Manager task each time that you access the server administration screens.