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

Elements in Siebel Remote Architecture

Figure 1 illustrates major elements in the Siebel Remote architecture.

Figure 1.  Siebel Remote Hardware Architecture

Siebel database. A computer on which the Siebel database resides. Tables in this database store information about your organizational structure, job responsibilities, sales personnel, sales territories, accounts, sales opportunities, and product lines. Other enterprise-wide databases may also reside on this server.

Siebel File System. A directory structure that contains the Siebel Encyclopedia items, correspondence templates, file attachments, and other files for client access and download. The Siebel Remote server must have network connectivity to the Siebel File System, which may be located on a Siebel Server, Siebel database server, or other server on the network. For more information on the Siebel File System, see Siebel File System.

Database access. The combination of hardware and software that enables a Siebel Remote server to access the Siebel database server. This connectivity is typically established using an ODBC driver and the database vendor's specific connectivity package. Due to the volume of data exchanged between the Siebel Remote server and the database server, this access needs to be provided over a 100 MB or faster network connection, such as Fast Ethernet or FDDI.

Siebel Remote server. A Siebel Server that runs the Siebel Remote components and manages synchronization sessions with Mobile Web Clients. Each Siebel Remote server manages a distinct group of mobile users who are assigned to that specific server. Other Siebel Server components, such as Assignment Manager and Enterprise Integration Manager, may run on the same Siebel Server.

To maintain a high level of integrity and availability, the Siebel Remote server provides an interim storage area for data required to synchronize mobile databases with the Siebel database server. To make sure of the integrity and availability of this data, administrators should implement a redundant disk configuration for the Siebel Remote server. Using redundant disk configuration will reduce the likelihood of losing data on the Remote server caused by malfunctioning hardware. However, if it does occur, a reextract of all Mobile Web Clients registered on the affected Remote server will be necessary.

Siebel Remote Client. Siebel Remote client software installed on the Siebel Mobile Web Client. During synchronization, it communicates directly with the Synchronization Manager component on the Siebel Server to synchronize the mobile node with its parent.

Components of Siebel Remote client are (a) Local Database and File System, and (b) Local Database Initialization Program.

Modem, LAN, WAN, or VPN. The combination of hardware and software that enables a Mobile Web Client to communicate with the Siebel Remote server. Mobile Web Clients must communicate with the Siebel Remote server using the TCP/IP protocol.

Client. A computer running the Siebel applications client software. The Mobile Web Client is used for Siebel Remote.

Siebel Mobile Web Client. A computer (typically a laptop used by field professionals) that normally runs Siebel applications as a stand-alone unit, using a local database and local file system. The local database and file system contain specific data and files that are initially drawn from the enterprise database and Siebel File System. The Mobile Web Client must connect to a Siebel Remote Server periodically to synchronize both the local database and local file system with their Enterprise counterparts. The connection is made using a modem across public telephone lines, LAN, WAN, or VPN.

The Siebel applications that run on a Mobile Web Client run inside a standard Web browser. However, layers of the Siebel eBusiness Applications architecture, including the local database and file system, reside on the user's personal computer and execute business logic locally. This architectural configuration requires installation of Siebel software on each Mobile Web Client computer.

The software that is installed for a Mobile Web Client is the same as the software that is installed for a Dedicated Web Client. However, the installation program requires more input for installation of a Dedicated Web Client than a Mobile Web Client. A Dedicated Web Client is capable of functioning as a Mobile Web Client (using a local database and local Siebel File System) if all setup steps for Mobile Web Clients are followed, including registering the user as a Mobile Web Client and extracting a local database. A Mobile Web Client can function as a Dedicated Web Client (using the enterprise database and Siebel File System) if appropriate modifications are made to its configuration (CFG) file.

Siebel Mobile Web Clients include a lightweight HTTP listener that listens on a dynamic port for HTTP requests from the local machine. Any requests from other machines on the network are ignored. Therefore, minimal security risk exists when the application is used on the network.