Deployment Planning Guide > Siebel Architecture Overview >

About Siebel Web Clients and Web Server Extension

There are several types of Siebel Web Clients:

Siebel Web Client

    • Installed software. No additional application software required on the client. Requires only a Web browser.
    • Application connection. Through a Web server to the Siebel Enterprise Server. Applications run on Siebel Server and forward pages to the client.
    • Database connection. Through the Siebel Server to the remote Siebel Database. No Siebel Database or database client installed on the client.

      Siebel Web Client runs in a standard browser on the end user's client computer. ActiveX controls and JavaScript routines are downloaded to the browser automatically when it runs Siebel applications in Siebel high interactivity mode. The browser connects through a Web server to the Siebel Server, which executes business logic and accesses data from the Siebel Database. Only the user interface layer of the Siebel eBusiness Applications architecture resides on the user computer.

      Wireless Client. Siebel Wireless is a modified Siebel Web Client that runs on a mobile device. Users can view, edit, and create records in the Siebel Database through a wireless connection between a mobile device and a Web server. An internet-enabled mobile phone, personal digital assistant or other device communicates using wireless application protocol (WAP) to a wireless gateway server. The wireless gateway server translates HTTP messages to WAP. The Siebel interface is rendered on the mobile device using wireless mark-up language (WML). Specific XML- and HTTP-based wireless browsers are also supported. For a list of Siebel eBusiness Applications that support wireless access, see the Siebel Wireless Administration Guide. For a list of supported wireless browsers, see System Requirements and Supported Platforms on Siebel SupportWeb.

Siebel Mobile Web Client

    • Installed software. Windows-based software containing Siebel applications and related services is installed on each client.
    • Application connection. Applications run on each client. Applications display in a Web browser.
    • Database connection. A Siebel Database and Siebel File System are installed on each client. Applications access the client's local database.

      Users periodically synchronize the client's local database and Siebel File System with a remote Siebel Enterprise Server's Siebel Database and Siebel File System. Users synchronize data using Siebel Remote. Siebel Remote allows users to connect directly to the remote Siebel Database, and Siebel File System without going through the Enterprise Web servers or Siebel Servers.

      The Mobile Web Client runs in a standard browser on the end user's client computer, such as a laptop.

      Siebel Handheld Client. The Siebel Handheld Client is a streamlined version of the Siebel Mobile Web Client. It includes only the functionality required by end users' field technicians. The Siebel Handheld Client supports the same data relationships, the same configuration in Siebel Tools, and much of the same functionality as the Siebel Mobile Web Client. Siebel Handheld runs on devices that support the Windows CE operating system.

Siebel Web Server Extension (SWSE)

The Siebel Web Server Extension (SWSE) is a plug-in for third-party Web servers. It identifies requests for Siebel information coming from Web clients and flags these requests for routing to a Siebel Server. When information is sent from the Siebel Server back to the Web client, the SWSE helps complete the composition of the Web page for forwarding to the client.

Included in the SWSE is the Siebel load balancing module. This module provides round-robin load balancing for Application Object Managers running on Siebel Servers.

All language packs installed on Siebel Servers must also be installed on your Web servers. However, you do not need to install all language packs on all Web servers. If you do not install all languages on all Web servers, you must provide a means for routing user requests to Web servers that have the correct language support.

Deployment Planning Guide