Deploying BIRT iHub in a cloud environment
In an Actuate cloud deployment, a stateless iHub image contains only the run‑time environment. The administrator typically transfers the image of the iHub run‑time environment using a compressed archive, such as a TAR file, or virtual image, unbundling the image on the target machine.
In addition, the administrator must install a supported version of the JAVA SE Development Kit (JDK) 1.6 or earlier. If not already installed on the machine, the JDK can be downloaded from the following location:
http://www.oracle.com/technetwork/java/javase/downloads/index.html
Set the JDK_HOME environment variable to point to the location of the JDK.
If you have an earlier version of BIRT iServer installed on your machine, such as Release 10 Service Pack 1, you can continue to run the earlier version, but not simultaneously with the new version if the earlier version uses the same default ports. You must shut down the earlier version during the deployment process. The earlier version must remain shut down when the newly installed iHub is running. Reconfigure the ports for one of the versions to run both versions at the same time.
In an iHub configuration, Actuate recommends storing iHub data in a directory located outside the iHub run-time environment. In a default Linux setup performed using the wizard-based install program, the iHub run‑time environment installs in the following directory:
$HOME/AcServer
The data installs in the following directory:
$HOME/AcServer/data
In a cloud deployment, Actuate recommends installing in an alternative directory. For example, in Linux, install the run-time environment in the following directory:
/home/actuate/Actuate/AcServer
The data installs in the following directory:
/home/actuate/Actuate/AcServer/data
The environment variable AC_SERVER_HOME points to the directory containing the run-time environment. The environment variable AC_DATA_HOME points to the directory containing the iHub data.