Previous Topic: OverviewNext Topic: iConsole Registry Values


iConsole Architecture

The iConsole front-end Web server and application server are provided as separate components to allow maximum flexibility when deploying the iConsole. For example, you may prefer to install the front-end Web server on your existing corporate Web server while installing the application server on an existing CA DataMinder server. For installation instructions.

Each front-end Web server can only connect to a single, specific application server, but it is possible to connect multiple front-end Web servers to a single application server. For example, this may be preferable if your iConsole users are based in various offices around the world; this configuration enables each user to connect to a local front-end Web server, with each front-end Web server connected to a central application server.

You can also have multiple application servers, each serving different front-end Web servers but all connected to the same CMS. Larger organizations may choose this configuration for load-sharing purposes.

Finally, each application server has a default parent CMS, but can be configured to connect to multiple CMSs if required.

iconsole example deployment

iConsole example deployment

1 CMS. This services all search requests submitted by the application server. All search SPs are stored in the CMS database; all XML search definition files are stored in the CMS file system.

2 iConsole application server. This submits iConsole event searches and audit updates to the CMS and returns search results to the front-end web server. Each application server is parented to a single CMS. If required, multiple application servers can connect to a single CMS.

3a, 3b iConsole front-end Web servers. These generate the HTML content for the various screens in the iConsole. In this example, two front-end Web servers each serve separate groups of iConsole users (for example users based in New York and Paris), but connect to a single shared application server.

4a, 4b Browser-based iConsoles. Reviewers and administrators use the iConsole to search for and retrieve events stored on the CMS and to update audit details for these events. The iConsole URL incorporates the name or address of the front-end Web server host. In this example, the New York iConsoles (4a) connect to front-end Web server 3a, while the Paris iConsoles (4b) connect to front-end Web server 3b.

More information:

Connect iConsoles to Multiple CMSs

Deployment Procedure