1. Developing and Deploying Siebel CRM
  2. Configuring the Siebel Application Interface

Configuring the Siebel Application Interface

The Siebel Application Interface (SAI) provides the external interface to the Siebel CRM application. This includes user interface channels, such as employees, customers, and partners using browsers to interact with the application, as well as integration with other applications through REST or Web service calls. Normally a development instance requires a single SAI, but as with the Siebel Server, the Application Interface can be enabled on multiple servers to provide load balancing and high availability. For more information, see Siebel Installation Guide for Microsoft Windows or Siebel Installation Guide for UNIX as appropriate.

The key parameters of the SAI are those that are affect client interactivity, such as session timeouts.

Consistent with the Enterprise and Siebel Servers, the SAI, configuration is completed in two parts:

  • Creating or more SAI profiles. For many environments, it is likely that you only need one a single profile, even if you will have Application Interfaces running on multiple machines. You might consider creating multiple profiles for one of the following reasons:

    • Differing authentication. For example, using a different authentication authority for your internal users from that which you will use for your Internet users.

    • Isolation. For example, to place Application Interfaces supporting customer-facing applications on one set of servers and employee-facing applications on another.

  • Deploying the SAI profile as many times as required to support capacity requirements, high availability, isolation, and other technical and functional requirements.