Performing a manual side-by-side migration
After installing the stand-alone version of BIRT iHub in a path separate from the earlier BIRT iServer Release 11 system, the administrator completes the migration by performing the following tasks:

Backs up the existing BIRT iServer Release 11 system

Shuts down the BIRT iHub system and the embedded OOTB PostgreSQL RDBMS

Performs the manual operations necessary to reconfigure iHub to use the BIRT iServer RDBMS containing the system and Encyclopedia volume metadata and related data stored on disk
This procedure replaces the BIRT iServer Release 11 installation with a new BIRT iHub system. Do not run the iServer Release 11 program files after performing these operations.
The following section describes how to perform these operations.
How to perform a manual side-by-side migration
1 Back up the existing BIRT iServer Release 11 system to safeguard against failure, including all metadata, data, and necessary configuration files.
2 Shut down the BIRT iHub system by performing the following tasks:
1 Navigate to the BIRT iHub AC_SERVER_HOME/bin folder. When installed in a typical side-by-side configuration, the BIRT iHub AC_SERVER_HOME refers to /home/actuate/iHub/AcServer.
2 Execute the shutdown_srvr script:
sh ./shutdown_srvr.sh
3 Shut down the Actuate PostgreSQL for BIRT iHub service by executing the stopPostgreSQL.sh script:
sh ./stopPostgreSQL.sh
4 Copy the BIRT iServer Release 11 acserverconfig.xml and, if migrating from BIRT iServer 11 Service Pack 4, the encryption keys file from the BIRT iServer configuration folder to the BIRT iHub configuration folder by performing the following tasks:
1 Navigate to the BIRT iHub AC_DATA_HOME/config/iHub2 folder. When installed in a typical side-by-side configuration, the BIRT iHub AC_DATA_HOME refers to /home/actuate/iHub/AcServer/data.
2 For example, copy acserverconfig.xml from the iServer AC_DATA_HOME/config/11SP4 folder to the BIRT iHub AC_DATA_HOME/config/iHub2 folder by executing the following command:
cp /home/actuate/AcServer/data/config/11SP4
/acserverconfig.xml .
3 If migrating from a BIRT iServer Release 11 Service Pack 4 installation, copy the keys file from the iServer AC_DATA_HOME/config/11SP4 folder to the BIRT iHub AC_DATA_HOME/config/iHub2 folder by executing the following command:
cp /home/actuate/AcServer/data/config/11SP4/keys .
5 If the BIRT iServer Release 11 system uses the out-of-the-box (OOTB) PostgreSQL RDBMS, give the BIRT iHub system access to the PostgreSQL data in the BIRT iServer Release 11 system by performing the following tasks:
1 Copy the postgresql folder from the iServer AC_DATA_HOME/encyc folder to the iHub AC_DATA_HOME/encyc folder by performing the following tasks:
1 Navigate to the BIRT iHub AC_DATA_HOME/encyc folder.
2 Execute the following command:
cp -r /home/actuate/AcServer/data/encyc/postgresql .
2 From the iHub AC_DATA_HOME/encyc folder, navigate to the following location:
/postgresql/data
3 In a text editor, open the postgresql.conf file and find the second occurrence of log_directory. In a default BIRT iServer Release 11 installation, the log_directory setting points to the following location:
log_directory = '/home/actuate/AcServer/data/postgresql/log'
Edit this setting to point to the location of the iHub AC_DATA_HOME/postgresql/log folder. For example, in a default iHub installation, edit the setting to point to the following location:
log_directory = '/home/actuate/iHub/AcServer/data/postgresql/log'
4 Scroll down until you see the entry for data_dictionary. In a default BIRT iServer Release 11 installation, the data_directory setting points to the following location:
data_directory = '/home/actuate/AcServer/data/encyc/postgresql/data'
Edit this setting to point to the location of the iHub AC_DATA_HOME/encyc/postgresql/data folder. For example, in a default iHub installation, edit the setting to point to the following location:
data_directory = '/home/actuate/iHub/AcServer/data/encyc/postgresql/data'
5 Exit the editor, saving the file to disk.
6 Update the AC_DATA_HOME entry in the BIRT iHub acpmdconfig.xml file to use the value in the BIRT iServer acpmdconfig.xml file by performing the following tasks:
1 In a BIRT iServer Release 11 Service Pack 4 installation, navigate to the following location:
/home/actuate/AcServer/etc
2 In a text editor, open the acpmdconfig.xml file and copy the following setting:
<AC_DATA_HOME>/home/actuate/AcServer/data</AC_DATA_HOME>
3 In the iHub installation, navigate to the following location:
/home/actuate/iHub/AcServer/etc
4 In a text editor, open the acpmdconfig.xml file and replace the default AC_DATA_HOME setting with the value from the BIRT iServer Release 11 acpmdconfig.xml file, as shown in
Listing 4‑1. Exit the editor, saving the file to disk.
Listing 4‑1 acpmdconfig.xml
<PMDConfig>
...
<!--Server information -->
<Server>
...
<AC_DATA_HOME>/home/actuate/AcServer/data</AC_DATA_HOME>
...
7 If the BIRT iServer Release 11 system uses the out-of-the-box (OOTB) PostgreSQL RDBMS, start the Actuate PostgreSQL for BIRT iHub service by performing the following tasks:
1 Navigate to the location of the script that starts the iHub PostgreSQL service. For example, in a default installation, navigate to the following location:
/home/actuate/iHub/AcServer/bin
2 Execute the following command:
sh ./startPostgreSQL.sh
9 Restart BIRT iHub System by performing the following tasks:
1 Navigate to the location of the script that starts the BIRT iHub System. For example, in a default installation, navigate to the following location:
/home/actuate/iHub/AcServer/bin
2 Execute the following command:
sh ./start_srvr.sh
3 Log on to the BIRT iHub Configuration and Management Consoles to verify that the system is functioning properly, the Encyclopedia volume is online, and all migrated partitions and data are accessible.
How to upgrade the Encyclopedia volume schema when migrating from an installation earlier than Release 11 Service Pack 4
If migrating from an installation earlier than Release 11 Service Pack 4, such as Release 11 Service Pack 1, 2, or 3, upgrade the Encyclopedia volume schema by performing the following tasks:
1 Add the paths to the Ant and Java executable programs to the PATH environment variable by performing the following tasks:
1 Create an environment variable named ANT_HOME by executing the following command:
export ANT_HOME=/home/actuate/iHub/AcServer/tools/apache-ant-1.8.2
2 Create an environment variable named JAVA_HOME by executing the following command:
export JAVA_HOME=/home/actuate/iHub/AcServer/jdk160
3 Add the folders containing the Ant and Java executable programs to the PATH variable by executing the following command:
export PATH=$PATH:$ANT_HOME/bin:$JAVA_HOME/bin
2 Verify that the following JAR files are in the BIRT iHub AC_SERVER_HOME/jar folder:

AcCommon.jar

com.actuate.common-server.jar

iserver.jar

JDBCDrivers.jar

ServerAdminTools.jar
3 In the BIRT iHub installation, replace the existing a11Upgrade.xml script with the latest version from the BIRT iHub download page by performing the following tasks:
1 Download the latest version of the a11Upgrade.xml script from the BIRT iHub download page.
2 In the BIRT iHub installation, navigate to the location of the upgrade files:
AC_SERVER_HOME/tools/upgrade/a11
In a default Linux installation, the path is:
/home/actuate/iHub/AcServer/tools/upgrade/a11
3 Delete the existing a11Upgrade.xml script. Copy the latest version from the BIRT iHub download page to this location.
4 In this location, upgrade the Encyclopedia volume schema by performing the following tasks:
1 In a text editor, open the a11Upgrade.properties file and edit these settings to point to the following locations:

AC_SERVER_HOME to the iHub program files

AC_DATA_HOME to the iServer data folder

AC_CONFIG_HOME to the iHub configuration files
For example, in a default installation, edit the settings to point the following locations:
AC_SERVER_HOME=/home/actuate/iHub/AcServer
AC_DATA_HOME=/home/actuate/AcServer/data
AC_CONFIG_HOME=/home/actuate/iHub/AcServer/data/config/iHub2
Exit the editor, saving the file to disk.
2 Execute the following command to run the a11Upgrade.xml Ant script:
ant -f a11Upgrade.xml