Installing multiple BIRT iHub modules on Linux
This section describes how to install BIRT iHub with Visualization Platform and System Console on Linux at the same time, on the same machine. To install a single BIRT iHub module, see Installing individual BIRT iHub modules on Linux.
Perform the procedures in this section only if you do not have BIRT iHub already installed on your system. If you purchased BIRT iHub Release 3 or Release 3 Fix 1 and installed the files that you downloaded, you can upgrade to BIRT iHub Release 3.1 by following the instructions in Upgrading to Visualization Platform 3.1 and Upgrading to System Console 3.1.
System Console creates a default cluster automatically. If you install System Console and BIRT iHub on the same machine at the same time using the procedure described in this section, System Console automatically adds the machine on which you installed these modules as a node and adds the default volume to the default cluster. If you install System Console individually either on the same machine as BIRT iHub or on a separate machine, you must add a node and a volume to the default cluster after installing System Console. For information on installing System Console and BIRT iHub individually, see Installing individual BIRT iHub modules on Linux. For more information on clustering, see Chapter 5 “Managing Clusters,” in the System Administration Guide.
When installing more than one BIRT iHub module at the same time, the administrator performs the following tasks:
*Downloads the BIRT iHub installation package, iHub3.tar.gz, from the software download site.
*Downloads the tar.gz and tar.gz.MD5 file pair or pairs for each module the administrator is installing from the download site. By default, the install script installs System Console and BIRT iHub with Visualization Platform. Installing these modules requires that the administrator download the following file pairs from the download site:
*SystemConsole.tar.gz and SystemConsole.tar.gz.MD5
*ActuateBIRTiHub.tar.gz and ActuateBIRTiHub.tar.gz.MD5
*Creates a new folder and unbundles the iHub3.tar.gz file into the folder.
*Reviews the software license agreement.
*Updates the installation properties file.
*Runs the install script, install.sh.
How to install multiple BIRT iHub modules on Linux
1 Download iHub3.tar.gz from the software distribution site.
2 Download the tar.gz and tar.gz.MD5 file pair for each BIRT module you are installing from the modules folder at the software distribution site to one folder.
3 Create a new folder into which to extract the files that iHub3.tar.gz contains, such as /opt/actuate.
4 Unbundle iHub3.tar.gz into /opt/actuate. Unbundling iHub3.tar.gz creates the installation directory, /opt/actuate/iHub3.
5 Navigate to /opt/actuate/iHub3/License.
6 Open and read the file, license.txt. You must agree to the license terms to install BIRT iHub modules. In step 8.5, you indicate whether you accept the license terms or whether you want the install program to prompt you for whether you accept the terms.
7 Navigate to /opt/actuate/iHub3.
8 Using a text editor, open the acinstall.properties file. Using the example shown in Listing 2‑1, perform the following tasks:
1 For ac.login, specify the machine and account name for the machine onto which you are installing the BIRT iHub modules. For ac.password, specify the account name password.
For ac.package, accept the default value of a,b to install System Console and BIRT iHub with Visualization Platform.
2 Modify the ac.homedir property to specify the installation directory path if you do not run the install script, install.sh, from the installation directory.
3 Leave ac.downloadonly set to false.
4 For ac.source, specify the path to the folder containing the tar.gz and tar.gz.MD5 file pairs that you downloaded in step 2. For example, if you downloaded these file pairs to /opt/actuate
/BIRT_component_archive_files, specify this path for ac.source.
5 For ac.acceptlicense, accept the default value of prompt for the install script to prompt you for whether you accept the software license terms when you run the script. Alternatively, specify y for yes, to accept the software license terms.
6 Uncomment ac.ihub_cluster_schema_name and ac.ihub_postgres_port, setting these two properties to the cluster schema name and PostgreSQL RDBMS port, if necessary.
7 Save and close the file.
Listing 2‑1 acinstall.properties
#Tue, 11 Jun 2013 16:19:16 -0700
ac.login=//URUP/actuate
ac.password=password
ac.package=a,b
# Please use forward slashes for the home fully qualified path
# on Windows OS, for example ac.homedir=D:/iHub/distribution
ac.homedir=.
ac.downloadonly=false
 
# Please use forward slashes for the source network path on
# Windows OS, for example ‘source’=//fs/installDir/iHub
# /distribution
#ac.source=.
ac.source=/opt/actuate/BIRT_component_archive_files
 
# The license agreement (license.txt) file is located in the
# ./License directory
# The default value of the ac.acceptlicense parameter is set to
# 'prompt', which requires the user to read the license
# agreement before accepting it
# Before starting a network/silent install, read the
# license.txt file and change the value of the ac.acceptlicense
# parameter to 'y' to confirm that you agree to the terms of
# the license agreement
# ac.acceptlicense=prompt
ac.acceptlicense=y
 
#Advanced Settings
#ac.ihub_cluster_schema_name=
#ac.ihub_postgres_port=
9 Execute the install.sh script using the following command:
sh ./install.sh
When you run the BIRT iHub installation script, you see the message “Unable to locate tools.jar.” You can safely ignore this message.
The script displays messages similar to those shown in Listing 2‑2.
Listing 2‑2 Executing the install script
Install will start now...
[echo] Downloading from given file system location
[echo] Verifying Checksum...
[echo] Completed verification
[echo] Extracting package System Console
[echo] Installing System Console. This may take a few minutes...
[echo] Downloading from given file system location
[echo] Verifying Checksum...
[echo] Completed verification
[echo] Extracting package Actuate BIRT iHub
[echo] Installing Actuate BIRT iHub. This may take a few minutes...
[echo] Using default PostgreSQL database port number 8433
[echo] Using default schema name
[echo] To access Information Console, use URL: http://localhost:8700/iportal
[echo] To access System Console, use URL: http://localhost:8500/sysconsole
[echo] Setup Completed
 
INSTALL SUCCEEDED
Total time: 3 minutes 34 seconds
installation complete