Reports Integration Guide › Deployment › CA Business Intelligence › CA Business Intelligence Requirements

CA Business Intelligence Requirements

Note the following requirements before you install CA Business Intelligence.

BusinessObjects Enterprise

For the current CA Data Protection release, your reports server must be running BusinessObjects XI 3.1 SP5.

InfoView Browser

InfoView is the BusinessObjects web portal. You can launch InfoView from the iConsole or you can browse to InfoView directly.

In BusinessObjects XI 3.1 SP5, InfoView is supported in:

• Mozilla Firefox
• Microsoft Internet Explorer 8 and 9 (in Compatibility View only)

CA Business Intelligence

Compatibility with CA products is provided through CA Business Intelligence. CA Business Intelligence is a wrapper that includes a BusinessObjects Enterprise installation.

The current CA Data Protection release supports CA Business Intelligence 3.3. When you install CA Business Intelligence 3.3 on your reports server, BusinessObjects XI 3.1 SP5 and its InfoView web portal also get installed.

CA Business Intelligence version details are in version.txt. Find this file in:

• The \Disk1\cabi\biek subfolder on your CA Business Intelligence distribution media.
• The \CommonReporting3 subfolder below the CA Business Intelligence installation folder.

For full details, see the CA Business Intelligence Implementation Guide, included in your CA Business Intelligence distribution image.

Reports Server host computer

Note the following requirements for your reports server.

Operating System

CA Data Protection integration with CA Business Intelligence has been tested on Windows Server. For complete information on the platforms, operating systems, database products, and the supported versions, see the CA Data Protection 15.0 Compatibility Matrix.

Note: The current CA Data Protection release does not support integration with a CA Business Intelligence deployment hosted on a non-Windows system.

RAM

2GB RAM.

Note: Although CA Business Intelligence is supported on systems with 2GB RAM, we recommend a minimum of 3GB.

BusinessObjects Repository Database

CA Business Intelligence 3.3 supports the BusinessObjects repository database on the following platforms:

• Microsoft SQL Server:

  SQL Server 2008, SQL Server 2008 R2

  See further SQL Server requirements below.

• Oracle 10.2, 11.1, and 11.2.

  See further Oracle requirements below.

• IBM DB2/UDB 9.1, 9.5, or 9.7
• Sybase Adaptive Server Enterprise 15, 15.5, 15.7
• Sybase SQL Anywhere 12.0.1

  This DBMS is embedded in CA Business Intelligence 3.3. However, we do not recommend SQL Anywhere for use in production systems. See below for details.

• MySQL 5.0

  This DBMS is embedded in CA Business Intelligence 3.2. We strongly recommend upgrading to MySQL 5.1.

Note: CA Data Protection integration with CA Business Intelligence has been tested using SQL Anywhere 12.0.1.

BusinessObjects Audit Database

The audit database is supported on the same platforms as the repository database, with one exception. Sybase Adaptive Server Enterprise 15.7 is not supported.

We Do Not Recommend SQL Anywhere

If you install a SQL Anywhere database when you install CABI 3.3, the installer automatically creates ODBC connections to SQL Anywhere and configures BOXI to use those ODBC connections. Howerver, we do not recommend SQL Anywhere for heavily used production systems.

We do recommend a SQL Server database. We also recommend Oracle and DB2, but SQL Server offers a simpler backup and recovery process.

Note: We do not recommend SQL Server Express because of its sleep mode.

SQL Server

Before installing CA Business Intelligence, you must:

• Create an empty database for BusinessObjects to use.
• Create a SQL Server login to be the owner of the new database.
• Install the relevant SQL Server client tools on the host server.

  These client tools are available from your database vendor and include the drivers (that is, the OLE DB Providers) that the universe uses to access the CA Data Protection central management server. These drivers are essential. Without them, CA Data Protection cannot apply row level security (RLs) to report results.

• (On 64-bit systems only) Specify a 32-bit ODBC System DSN to connect to SQL Server. Find odbcad32.exe in the \Windows\SysWOW64 directory.

Oracle

Before installing CA Business Intelligence, you must:

• Install the relevant Oracle client tools.

  These client tools are available from your database vendor and include the drivers (that is, the OLE DB Providers) that the universe uses to access the CA Data Protection CMS. These drivers are essential. Without them, CA Data Protection cannot apply row level security (RLs) to report results.

• Specify a 32-bit ODBC System DSN to connect to Oracle.

  (On 64-bit systems only) The 32-bit ODBC driver is available to download as part of Oracle 32-bit Oracle Data Access Components on the Oracle web site. After installing the driver, you can create the 32-bit ODBC System DSN using the Data Sources (ODBC) applet in Administrative Tools.

• Add the CA Data Protection CMS to tnsnames.ora.

  (On 64-bit systems only) An Oracle CA Data Protection CMS must use a 32-bit ODBC System DNS to connect to your BusinessObjects CMS. To allow the CA Data Protection CMS to connect using 32-bit Oracle client software, the tnsnames.ora file must include an entry for the CA Data Protection CMS database. You must also specify the location of tnsnames.ora in the registry.

  See the reference below for details.

BusinessObjects Administrator Credentials

The installer creates a default BusinessObjects administrator account (name: administrator). This account is used to import CA Data Protection report templates and to access BusinessObjects InfoView.

You must supply the password for this account when you install CA Business Intelligence.

Apache Tomcat application server

The CA Business Intelligence installer includes an embedded version of Apache Tomcat. If you use this version of Tomcat as your application server, the CA Business Intelligence installer requires the following information:

Connection port

Tomcat connects to this port.

The default port is 8080.

Redirect port

Tomcat redirects requests to this port.

The default port is 8443.

Shutdown port

Tomcat issues SHUTDOWN commands to this port.

The default port is 8005.

More information:

Add a CA Data Protection CMS Entry to Tnsnames.ora