Upgrade Guide › Upgrading from 14.1 › Upgrade CA Business Intelligence 3.2 to 3.3

Upgrade CA Business Intelligence 3.2 to 3.3

(Applicable only if CA DataMinder integration with BusinessObjects Enterprise is enabled.)

For the current CA DataMinder release, your reports server must be running BusinessObjects XI 3.1 SP5. In previous releases, CA DataMinder required BusinessObjects XI 3.1 SP4. The simplest way to upgrade from SP4 to SP5 is to install CA Business Intelligence 3.3 on top of your existing CA Business Intelligence 3.2.

Note: CA Business Intelligence is a wrapper that includes a BusinessObjects Enterprise installation. You install CA Business Intelligence on your reports server.

MySQL and Tomcat Are Not Upgraded Automatically

If you do install CA Business Intelligence 3.3 on top of version 3.2, be aware that the upgrade only applies to the BusinessObjects SP level. Existing versions of MySQL and the Tomcat web server are not upgraded. After installing CA Business Intelligence 3.3, you must therefore verify that your reports server is running:

• A supported version of Tomcat (6 or later).
• A supported DBMS for the repository database. We do not recommend using MySQL in a production environment.

Note: Full CA Business Intelligence requirements are in the Reports Integration Guide.

How to Migrate the Repository Database to a New DBMS

(Optional) Follow these guidelines if you want to migrate your existing repository database to a recommended DBMS (for example, from MySQL to SQL Server).

1. Set up the target repository database and a database user account.

   For example, if you want to migrate the repository database to SQL Server, create a new BOUSER database login using SQL Server authentication. Then create a new BOREPOS database owned by the BOUSER login.

2. On the reports server, create a new 32-bit system ODBC data source that links to the target repository database as the new database user (BOUSER). You specify this database link as the target database in the migration.
3. Back up BusinessObjects Enterprise for both the source repository database and the <boe< file store locations.

   Note: 'Copying’ data between system database deletes the contents of the source repository database.

4. Follow instructions in the SAP BusinessObjects Enterprise Administrator's Guide for copying data between CMS system databases. Find these instructions in the following section:

   Managing and Configuring Servers, Configuring Server Settings, Copying Data From One CMS System Database To Another