Siebel Remote and Replication Manager Administration Guide > About Siebel Remote > Siebel Remote Architecture >

Overview of the Siebel Remote Architecture

Figure 2 illustrates major components of the Siebel Remote architecture.

Figure 2. Siebel Remote Architecture

Explanation of Callouts

The Siebel Remote architecture includes the following components:

1. Server Database. A database that stores information about the organizational structure of your company, job responsibilities, sales personnel, sales territories, accounts, sales opportunities, contacts, product lines, and so on. It stores data for users who use a stationary client or a remote client. It contains the following items:
   • Metadata for a Siebel application
   • Tables that store user data for a Siebel application
   • A master transaction log table that stores changes made since the last database extraction
2. Siebel File System. A directory structure that includes the following items:
   • Siebel Encyclopedia items
   • Correspondence templates
   • File attachments
   • Other files that support client access and download

     The Siebel Server must possess network connectivity to the Siebel File System, which might be located on a Siebel Server, on another server on the network, or used with the Database Configuration Utilities. For more information, see Siebel File System.

3. Database Configuration Utilities. A set of files. To install these files on a Siebel Server, you use the Siebel Enterprise Server installer. To create this connectivity, you usually use an ODBC driver and the specific connectivity package for the database vendor. Due to the volume of data that Siebel Remote exchanges between the Siebel Server and the Database Configuration Utilities, you must provide this access over a 100 MB or faster network connection, such as Fast Ethernet or FDDI. For more information, see Installing the Server Database Configuration Utilities on the Regional Node.
4. Siebel Server. A Siebel Server that runs the server components that Siebel Remote uses and manages synchronization sessions with the remote client. For more information, see Siebel Server Usage.
5. Modem, LAN, WAN, or VPN. The combination of hardware and software that allows a remote client to communicate with the Siebel Server. The remote client uses the TCP/IP networking protocol to communicate with the Siebel Server. You can use the following types of networks:
   • Local Area Network (LAN)
   • Wide Area Network (WAN)
   • Virtual Private Network (VPN)
   • A modem that uses dial-up networking
6. Software on remote client. Software for the remote client. For more information, see Siebel Remote Client Software.
7. Remote client. A computer that normally runs a Siebel application as a stand-alone application, using a local database and a local file system. For more information, see Mobile Web Client.
8. SRF (Siebel Repository File). Contains the object definitions of the Siebel application and database schema. You install it when you install a Siebel Server. For more information about:
   • Options of where to place the SRF, see Modifying the Configuration File.
   • How to use a customized SRF, see Upgrading a Regional Node.

About the Siebel Enterprise and the Siebel Enterprise Server

A Siebel Enterprise is a system that includes all users on all Siebel Servers in an environment that includes multiple Siebel Servers. The Siebel Enterprise Server is a logical grouping of Siebel Servers that supports a group of users who access a common server database in a multiple server environment. You can configure, manage, and monitor the Siebel Enterprise Server as a single logical group, which allows you to start, stop, monitor, or set parameters for a group of Siebel Servers in a Siebel Enterprise Server. For an example of a Siebel Enterprise, see Figure 8. For more information, see Siebel System Administration Guide.