Setting up Actuate Information Console

You install Information Console in either of two ways:

n	As a separate web application. This method enables native load-balancing for iServer clusters, redundancy to support constant report services over the web, and secure networks using firewalls and proxy severs as described in Using Actuate Information Console security.

n	Automatically on the same host with iServer. This method provides reports locally on each iServer machine.

For enterprise architectures, installing Information Console on several web servers is recommended.

To deploy a report to the web, you need:

n	An Actuate Information Console installation.

n	An application server or JSP or servlet engine such as Actuate embedded servlet engine or IBM WebSphere.

n	One or more Actuate designer tools and Actuate BIRT iServer System with Actuate Management Console.

n	Actuate BIRT iServer administrator privileges.

n

Permission to read, write, and modify operating system directories as necessary. For example, the directory Java uses to hold temporary files is defined by the java.io.tmpdir property and is by default the value of the TMP system variable in the Windows environment and /var/tmp in the UNIX and Linux environments. Read and write permission must be provided to the application server running Information Console for this directory.

This section discusses deployment concerns that may affect your Information Console installation and how you wish to deploy reports to the web. For more information about installing Information Console, see Installing BIRT iServer for Windows or Installing BIRT iServer for Linux and UNIX.

(c) Copyright Actuate Corporation 2011