Siebel System Administration Guide > Siebel Enterprise Server Architecture > About the Siebel Server >
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:
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
NOTE: If the
logarchive directory is locked or inaccessible, then a log archive is not created.