Siebel Deployment Planning Guide > Siebel Architecture Overview >

About the Siebel Application Interface

The Siebel Application Interface serves as the Web server for Siebel CRM applications. The Siebel Application Interface identifies requests for Siebel application data 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 Siebel Application Interface helps complete the composition of the Web page for forwarding to the client.

You can install and deploy multiple Siebel languages on a single Siebel Application Interface instance. The Siebel Server and the Siebel Application Interface do not have to be operated in the same language. However, the Siebel Server, the Siebel Application Interface, and all other server components must use the same character set. You install and configure the Application Interface as a separate module, located in the DMZ. (The DMZ or demilitarized zone is located behind an external firewall but outside of an internal firewall.)

The Siebel Application Interface and Siebel Gateway work together to provide Siebel Server load balancing. When a user requests a new application connection, Siebel Application Interface sends a request to Siebel Gateway, which returns a connect string for the least-loaded Application Object Manager from among the Siebel Servers supporting that component. The user session will use this Application Object Manager.

NOTE:  As of Siebel CRM version 17.5, application containers for Siebel Application Interface instances on multiple nodes can be load balanced using Apache HTTP Server (httpd) and Apache Tomcat Connector (mod_jk). For more information, see Components Involved in Service Failures.

For information about installing and configuring the Siebel Application Interface and about deploying Siebel languages, see the Siebel Installation Guide for the operating system you are using and Siebel Global Deployment Guide.