Performing a manual side-by-side migration

Migrating to BIRT iHub : Performing a side-by-side migration : 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 Backup the existing BIRT iServer Release 11 system to safeguard against failure, including all metadata, data, and necessary configuration files.

For information on how to back up the iHub or iServer system and Encyclopedia volume schemas and related data and configuration files, refer to Chapter 10, “Backing up an Encyclopedia volume,” later in this book.

2 Shut down the BIRT iHub system by performing the following tasks:

1 Log on to Configuration Console. In the Simple view, choose Stop system. Log out of Configuration Console.

2 In Windows Services, stop Actuate BIRT iHub service, then stop Actuate PostgreSQL for BIRT iHub service.

3 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. For example, in a default iServer Release 11 Service Pack 4 installation, copy these files from the following location:

C:\Actuate\iServer\data\config\11SP4

to:

C:\Actuate\iHub\data\config\iHub2

4 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.

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 = 'C:/Actuate/iServer/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 = 'C:/Actuate/iHub/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 = 'C:/Actuate/iServer/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 = 'C:/Actuate/iHub/data/encyc/postgresql/data'

5 Exit the editor, saving the file to disk.

5 Update the AC_DATA_HOME entry in the BIRT iHub acpmdconfig.xml file to use the value in the BIRT iServer acpmdconfig.xml file. For example, perform the following tasks:

1 In a BIRT iServer Release 11 Service Pack 4 installation, navigate to the following location:

C:\Program Files (x86)\Actuate11SP4\iServer\etc

2 In a text editor, open the acpmdconfig.xml file, and copy the following setting:

<AC_DATA_HOME>
C:\Actuate\iServer\data

</AC_DATA_HOME>

3 In the iHub installation, navigate to the following location:

C:\Program Files (x86)\Actuate\iHub2\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>
...
<AC_DATA_HOME>C:\Actuate\iServer\data</AC_DATA_HOME>
...

6 If the BIRT iServer Release 11 system uses the out-of-the-box (OOTB) PostgreSQL RDBMS, start the Actuate PostgreSQL for BIRT iHub service.

7 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 tasks described in “How to upgrade the Encyclopedia volume schema when migrating from an installation earlier than Release 11 Service Pack 4,” later in this chapter.

8 Restart BIRT iHub system by performing the following tasks:

1 In Windows Services, start Actuate BIRT iHub service.

2 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 In Windows System Properties—Environment Variables, add the paths to the Ant and Java executable programs to the Path system variable. For example, add the following notation to the Path variable:

%ANT_HOME%\bin;%JAVA_HOME%\bin

With the ANT_HOME system variable set to the following path:

C:\Program Files (x86)\Actuate\iHub2\tools\apache-ant-1.8.2

And the JAVA_HOME system variable set to the following path:

C:\Program Files (x86)\Common Files\Actuate\22.0\JDK160

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 Windows installation, the path is:

C:\Program Files (x86)\Actuate\iHub2\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

Use forward slashes in the Windows path specifications in this property file. For example, in a default installation, edit the settings to point the following locations:

AC_SERVER_HOME=C:/Program Files (x86)/Actuate/iHub2

AC_DATA_HOME=C:/Actuate/iServer/data

AC_CONFIG_HOME=C:/Actuate/iHub/data/config/iHub2

Exit the editor, saving the file to disk.

2 Open a command prompt, navigate to the location of the BIRT iHub upgrade files, and run the following command to execute the a11Upgrade.xml Ant script:

ant -f a11Upgrade.xml