Siebel Interactive Designer Administration Guide > Interactive Designer and Interactive Selling Applications >

Interactive Designer Application Architecture

In eAdvisor and browser-based eConfigurator applications, the engine runs on the browser rather than on the server, providing users with quick response time. Because trips to the server are reduced, there is no network latency.

Application data is stored in the Siebel database and Siebel File System. Unlike in server-based applications, in eAdvisor and browser-based eConfigurator applications, files needed for the application are statically published after the application data model and the user interface are developed. In some deployments, you will need to take the additional step of moving your application files to a Web server where the browser can find them. The data accessed from the Siebel business components is also statically published. You can use the Siebel Application Integration functions to dynamically access data in the business components. For more information about integrating your data, see Referencing Other Siebel Data and Siebel Interactive Designer API Reference.

Figure 1 illustrates eAdvisor and browser-based eConfigurator application architecture.

Figure 1. Siebel eAdvisor and Browser-Based eConfigurator Application Architecture

Click for full size image

Figure 1 shows two types of deployment:


 Siebel Interactive Designer Administration Guide 
 Published: 18 April 2003