CABI 3.

3 SP2 Release Notes

CABI 3.3 SP2 is a patch release which is equal to SAP BOXI 3.1 SP7 patch release.
The CABI 3.3 SP2 windows release contains below salient features

Option of CMS data automigration from default MySQL to SQL Anywhere

Tomcat 7 as default application server
JDK 1.7 by default

CABI 3.3 SP2 patch can be installed on

1. Windows machine with CABI 3.3 with or without FP52 and/or 3.3 SP1
2. Windows machine with CABI 3.2 with either of the following patch combinations applied

FP32 + SP4 + SP5

FP32 + SP4 + SP5 + FP52
FP32 + SP4 + SP5 + FP52 + 3.3 SP1
FP32 + SP5
FP32 + SP5 + FP52
FP32 + SP5 + FP52 + 3.3 SP1
SP4 + SP5
SP4 + SP5 + FP52
SP4 + SP5 + FP52 + 3.3 SP1
SP4 + 3.3 SP1
SP5 + FP52 + 3.3 SP1

3. Any machine with CABI version 12.5.0.xxxx or above

Note: To check the version, please login into CMC as Administrator, click settings and check
product version.

Installation instructions
1.
2.
3.
4.
5.

Login into windows machine as Administrator.

Download and unzip the CABI 3.3 SP2 patch installer to a temporary folder.
Make sure the Server Intelligence Agent service and the Application Server are running.
Open command prompt and go to the temporary folder.
In the command prompt run the following command to install CABI 3.3 SP2 patch
Installing with GUI
biekpatch.exe l c:\installation.log
Note: 1. -l flag and its value are optional.
1

2. This command is also applicable to any supported external application server (eg:
weblogic, websphere, tomcat..)
3. Please type the commands in command prompt, dont copy/paste from this.
If you want to migrate default MySQL CMS data to SQLAnywhere database then you
need to use cmsmigrate flag with biekpatch.exe. It is recommended not to use this flag
if cms database is not the default MySQL.
When you trigger this patch build on upgradable CABI machine with default MySQL as
CMS database using cmsmigrate flag, you will be prompted for existing MySQL CMS
database details and new SQLAnywhere CMS database details.
Fill the existing MySQL CMS database details and click Next.
Note: Selecting or unselecting of Already selected My SQL as auditing database has no
impact, because automigration of Audit data is not supported.

Fill the SQLAnywhere CMS database details and select Select SQL Anywhere as auditing
database option if you want auditing to be enabled, irrespective of whether you had
auditing enabled with MySQL database or not.

 Click Next and complete the remaining upgrade process.

After installation, if you find SIA service is in stopped state perform the following.
o Install Microsoft Visual C++ 2010 x86 Redistributable (vcredist_x86.exe) which
you can find under softwares folder inside the installer
o Start the SIA from CCM
o Run the cafdeploy command from cafdeploy folder inside the installer
cafdeploy.exe [s <web application server type>] [-a <websphere/weblogic
password>] p <CABI administrator password> [-l <log file>]
Eg: cafdeploy.exe s tomcat7 p myadminpassword
Note: 1. If the existing CMS database is not default MySQL then it is not recommended to use
cmsmigrate flag.
3. There is no option to skip the auto migration process if you used cmsmigrate flag.
4. The automigration process only points CABI audit to a new SQLAnywhere audit
database. In case if you want to migrate the Audit data, follow the Migrating Audit database
From MySQL to SQL Anywhere.pdf document which can be found at docs folder inside the
installer before Post installation steps.
After the upgrade process is complete with cmsmigrate flag, update the following
entries in C:\Program Files (x86)\CA\SC\CommonReporting3\biek.properties file (or in a
similar location).
3

CMSDBUser=<SQLAnywhere Username>
Replace the BOXIMysql=1 with BOXISQLAnywhere=1
(Optional) Post Installation Steps:
After successful upgrade with default MySQL CMS database with cmsmigrate flag, MySQL
database will be retained. Follow below steps to remove the MySQL database and corresponding entries
from your windows machine.
Caution: This process also removes the Audit database (if any), so migrate the audit data before
proceeding.
Follow the steps:
1. Login to CABI server windows machine as an administrator
2. Open Central Configuration Manager (CCM) and stop the Server Intelligence Agent (SIA) service
3. After the SIA has stopped completely, open SIA properties and go to the Dependency tab

4. Select BOE120MySQL (or similar) service and click on Remove

5. Click Add to add SQLAnywhere service as dependency
4

6. Select BOE120SQLAW (or similar) and click Add and then click OK
7. Go to services.msc and stop the BOE120MySQL (or similar) service
8. Open command prompt and run the following command to remove BOE120MySQL service
sc delete BOE120MySQL
9. Go to C:\Program Files (x86)\CA\SC\CommonReporting3 (or similar) location and delete MySQL5
folder
10. Open the odbcad32.exe file (32-bit ODBC Data Sources) that is located at
C:\Windows\SysWOW64 on 64-bit windows system and at C:\Windows\System32 on 32-bit
windows system

11. Go to the System DSN tab

12. Delete Business Objects Audit Server and Business Objects CMS data sources
Silent installation with default tomcat
biekpatch.exe cp <cmspassword> l c:\installation.log
Silent installation with external application server
biekpatch.exe cp <cmspassword> ap <appserverpassword> -l c:\installation.log
Note: If the cms password is empty or null, still we need to specify the cp flag with .
6. CABI 3.3 SP2 patch installs Apache Tomcat 7.0.27 as its application server if the existing CABI is
running with default Apache Tomcat server. It also upgrades the JDK version to 1.7.0_40 (32bit).
7. After successful installation, change the Apache Tomcat 6.0.24 Startup Type to Manual either
from services.msc or from CCM, if you installed on top of CABI 3.3 full installation with or
without FP52 with default tomcat.

If the completion message indicates any error code then there is some problem with
installation. See below for error codes.
Exit Code

Message

---------

-----------------------------------------------------------------------

Operation completed successfully: Either the patching completed

successfully or the patch was not required (i.e., the patch level of
the installation was at or above the patch level of the patch you
were attempting to install).

3010

The requested operation is successful. Changes will not be effective

until the system is rebooted: The patching completed successfully,
but a reboot is required to finish the patching process.

16001

A file I/O error has occurred: An error occurred reading either

patch.properties or patch_list.txt. The files may be missing or
6

corrupt, or an incorrect patch_dir was supplied.

16003

Invalid path: An invalid path was passed to the biekpatch utility.

16005

Invalid arguments: Invalid arguments were passed to the biekpatch utility.

16022

Additional patches are required to install this patch: The patch

you are attempting to install depends on additional patches that
have not yet been installed.

16023

Unknown patch. Invalid patch_list.txt or patch.properties out of date:

A patch listed in the patch_list.txt file could not be found in
the patch.properties file.

Validation
Through web browser

Log into the Central Management Console via a web browser as administrator.
Select "Settings"
Product version should be 12.7.0.1983
If you used cmsmigrate flag in valid landscape, before starting this upgrade process
you would see MySQL value as 5.0.46-enterprise for Database Name entry. After
upgrade you can find the SQLAnywhere value as boe120sqlaw_<SQLAnywhere
Username>;boe120;sql anywhere;12.00.0001 for the same Database Name entry.

Go to the INSTALLDIR\CommonReporting3\BusinessObjects Enterprise 12.0\win32_x86

Right click on busobj.exe file and click properties
Go to Details tab, the Product version should be 12.7.0.1983

In windows

Uninstalling CABI 3.3 SP2 patch

1. Login into the windows machine as Administrator.
2. Open command prompt and go to C:\Program Files (x86)\CA\SC\CommonReporting3\Uninstall
CA Business Intelligence 3.3/3.2 (or similar).
3. Run the following command.
biekpatch.exe u SP7 l c:\uninstallation.log

Note: If you trigger this process on Windows 2012/Windows 2012 R2 machine then you will get bunch
of message boxes as shown below. You can ignore/close these.

Certification Matrix
Operating System

CABI Version

Database

App Server

Installation type

Win2k12-EN

3.3

DEFAULT

DEFAULT

GUI

Win2k12-EN

3.3

DEFAULT

DEFAULT

SILENT

Win2k8R2-EN

3.3+FP 5.2

Oracle

WebLogic

GUI

Win2k8R2-EN

3.3+FP 5.2

Oracle

WebLogic

SILENT

Win2k8SP2-EN

3.3+SP5+SP6

External Mysql

DEFAULT

GUI

Win2k8SP2-EN

3.3+SP5+SP6

External Mysql

DEFAULT

SILENT

Win2k3SP2-EN

3.2+SP5

DEFAULT

DEFAULT

GUI

Win2k3SP2-EN

3.2+SP5

DEFAULT

DEFAULT

SILENT

Win2k8R2-PT

3.3

DEFAULT

DEFAULT

GUI

Win2k8R2-PT

3.3

DEFAULT

DEFAULT

SILENT

Win2k8R2-IT

3.3

DEFAULT

DEFAULT

GUI

Win2k8R2-IT

3.3

DEFAULT

DEFAULT

SILENT

Win2k8R2-KO

3.3

DEFAULT

DEFAULT

GUI

Win2k8R2-KO

3.3

DEFAULT

DEFAULT

SILENT

Win2k8R2-ES

3.3+FP 5.2

Oracle

WebLogic

GUI

Win2k8R2-ES

3.3+FP 5.2

Oracle

WebLogic

SILENT

Win2k8R2-FR

3.2+SP5

DEFAULT

DEFAULT

GUI

Win2k8R2-FR

3.2+SP5

DEFAULT

DEFAULT

SILENT

Win2k8R2-DE

3.2+SP5+SP6

External Mysql

DEFAULT

GUI

Win2k8R2-DE

3.2+SP5+SP6

External Mysql

DEFAULT

SILENT

Win2k8R2-CN

3.2+SP5+SP6

External Mysql

DEFAULT

GUI

Win2k8R2-CN

3.2+SP5+SP6

External Mysql

DEFAULT

SILENT

Win2k8R2-JA

3.2+SP5

DEFAULT

DEFAULT

GUI

Win2k8R2-JA

3.2+SP5

DEFAULT

DEFAULT

SILENT

Important Notes:

After installation of CABI 3.3 SP2 build with previous applied patch is other than CABI 3.3
SP1, CAF content (and any other custom content) will not work because the application
server got changed to Tomcat 7. To overcome the issue, redeploy those content
manually using wdeploy commands.
Eg: wdeploy tomcat7 DAPP=CAFName deploy

During the installation of CABI 3.3 SP2 patch using GUI installation process on top of
CABI 3.3 full installation with or without FP52 with default tomcat application server,
9

Install Tomcat 7 and Re-Deploy Web Applications screen will show Tomcat as Tomcat
5.5. You can ignore this message and can proceed further.

If you are using external application server as CABI application server, it will get stop
during the installation. Start the server after installation is done.

If you are installing on Portuguese environment with default tomcat, deploy all the web
applications to tomcat7 after installation using wdeploy utility.

If you are using external application server then redeploy the all web applications to
that server after installation using wdeploy utility.

After installation of CABI 3.3 SP2 on top of CABI 3.3 full installation with or without FP52
if Apache Tomcat 7.0.27 is stopped and Apache Tomcat 6.0.24 is running in Central
Configuration Manager then
o Stop Apache Tomcat 6.0.24
o Start Apache Tomcat 7.0.27

After the uninstallation of CABI 3.3 SP2 if the earlier version of tomcat is not running,
restart the machine.

If the CABI 3.3 SP2 is installed on top of CABI 3.3 SP1 patch, when uninstalled all the web
applications will be undeployed from tomcat 7. Use wdeploy utility to redeploy all the
applications again.

10