About Actuate Information Console architecture
This section describes the general operation, authentication, and structure of Information Console as a web application.
The Actuate Information Console architecture is illustrated in Figure 1-2.
A user submits a request by choosing a link on a web page that specifies an Actuate Information Console URI. As shown in Figure 1-2, the web or application server receives the URI as an HTTP request and passes the request to the servlet or page engine. The engine invokes Actuate Information Console, interprets the URI, and communicates with the Actuate BIRT iServer using the Actuate Information Delivery API (IDAPI). The IDAPI manages the request and returns the results to Actuate Information Console and the servlet or page engine. The web server returns the results to the web browser. Then, the web browser displays the results for the user.
Actuate Information Console manages requests as part of a JSP engine within a web or application server. There is no default user interface for the engine. On a Windows system, Actuate Information Console installation places an Actuate Information Console link on the Start menu.
