Installation Guide › Server Installation › Standalone Report Server

Standalone Report Server

If you do not need high availability for the Report Server, use the following procedure for a standalone installation.

Prerequisites

If you are planning to use RHEL 6 for the Business Objects installation, these prerequisites exist:

• Minimum patch requirements for RHEL 6: compat-libstdc++-33-3.2.3-69.el6.i686 (compatibility standard C++ library from GCC 3.3.4); glibc-2.12-1 (RedHat advisory RHBA-2007:0619-3); libXext.i386; libncurses.so.5, libXext-devel-1.1-3.el6.i686, libXext-devel-1.1-3.el6.x86_64

  Note: Install both X86_64 & i636 patches for the above. We recommend using yum install package_name.

  The hostname cannot have special characters such as '-' (a hyphen). It can be only alpha-numeric.

• Oracle Client 32Bit (or you can use Instant Client. To download OracleLinuxClient.zip)
• Open your Oracle server Enterprise Management Console or SQL console and create Tablespaces for CMS ("BO_CMS_TS") and Auditing ("BO_AUDIT_TS"). Also create 2 users, one for CMS ("BO_CMS_USER") and other for Auditing ("BO_AUDIT_USER") and give them dba privileges on respective Tablespaces.
• locale en_US.utf8 (to be default locale for BO installation)
• export LANG=en_US.utf8

Follow these steps:

1. Create a UNIX group (for example: bobje) to be used as a CA Business Intelligence User

   # groupadd -g 400 bobje
   

2. Create a folder to be used as home folder for CA Business Intelligence User

   # mkdir /home/bobje
   

3. Create a UNIX user (for example: bobje) to be used by the CA Business Intelligence installer for administrators

   # useradd -d /home/bobje -g bobje bobje
   

4. Set the password for the user created in step 3.

   # passwd bobje
   

5. Change the ownership of the home directory as follows:

   # chown -R bobje:bobje /home/bobje
   

6. Download and copy the CABI3.2 to /home/bobje (or home folder created in step #2)
7. Extract the installer GZ file as follows:

   gunzip cabi-3_2_0_6-linux.tar.gz
   

8. Extract the TAR file as follows:

   tar -xvf cabi-3_2_0_6-linux.tar
   

9. Give necessary permissions on CABI install folder and Installer media

   copy OracleLinuxClient.zip to /tmp
   

10. Extract zip file and all other zip files in it
11. Rename the folder "instantclient_11_2" to "oracle" and move "oracle" folder to /opt/.
12. Go to /opt/oracle and create softlinks as below

    ln -s libclntsh.so.11.1 libclntsh.so
    ln -s libocci.so.11.1 libocci.so
    

13. Create a file "tnsnames.ora" with following content. Remember to replace parameters (specified between < and >) according to your setup

     <your Oracle SID> =
       (DESCRIPTION =
      (ADDRESS = (PROTOCOL = TCP)(HOST = <Oracle Hostname>)(PORT = 1521))
      (CONNECT_DATA =
     (SERVER = DEDICATED)
     (SERVICE_NAME = <your Oracle Service/SID name>)
    

14. Edit .bash_profile of both "root" (/root/.bash_profile) and "bobje" (/home/bobje/.bash_profile) (or CA Business object user created in step #3) and add the following.

    Note: If /home/bobje/.bash_profile does not exist for bobje user, create one and change owner to bobje using command "chown bobje:bobje /home/bobje/.bash_profile"

    export ORACLE_HOME=/opt/oracle
    export PATH=$PATH:$ORACLE_HOME
    export TNS_ADMIN=/opt/oracle
    export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/opt/oracle
    

15. Go to the user home folder (/home/bobje).
16. Run the Cabi installer.

    cabiinstall.sh
    

    Note: CABI installation is console installation. Provide the necessary details in the screen, keeping note of the passwords, ports and usernames provided during the installation

    See the following section for a few important parameters to be given during installation.

Non-Root Credentials

The BusinessObjects Enterprise installation program needs to run as a non-root user. The installer is running as the 'root' user, enter credentials for a valid non-root user.

• User Name: bobje
• Group Name: bobje
• Select 1 - New (Install a new Enterprise system)" for Installation Type
• Select 1 - Use an existing database (Oracle/DB2/Sybase/MySQL)" for CMS Repository
• Select 2 - Oracle for Database Type
• Provide CMS user details for the CMS Database
• Provide Audit user details for the Audit Database
• Select Yes to initialize the database
• Select 1 - Install Tomcat, deploy web applications"

  Note: In case of any database error during install, check the latest "/opt/CA/SharedComponents/CommonReporting3/setup/logs/dbcheck" for details. All installation logs exist here: "/opt/CA/SharedComponents/CommonReporting3/setup/logs/"

To install Business Objects SP4 (optional)

Business Objects SP4 is the patch installer on Business Objects 3.2. To install this release, use the following procedures to install CABI 3.2 and then SP4.

To run the stand-alone patch utility on UNIX, follow these steps:

1. Download and unzip the patch.
2. Navigate to the patch location.
3. Run the following command:

   ./biekpatch
   

4. Provide necessary details to complete the installation.

Install verification

After installation, you should be able to access the CMS console (http://<hostname>:8080/CmcApp)

Starting and Stopping the server

1. To start the server, SSH to the Business Objects system:

   # cd /opt/CA/SharedComponents/CommonReporting3/bobje/setup
   # source env.sh
   # cd ..
   # ./startservers
   # ./tomcatstartup.sh
   

2. To stop the server, SSH to Business Objects system:

   # cd /opt/CA/SharedComponents/CommonReporting3/bobje/setup
   # source env.sh
   # cd ..
   # ./stopservers
   # ./tomcatshutdown.sh
   

To Check the Installed Business Objects Server Version:

1. Log in to CMS Console.
2. On the Home page, click Settings under the Manage section.
3. Check the Product Version is 12.4.0.966 (If CABI 12SP4)

Post Installation for the Identity Management Server

1. Update Registry Entries as follows:

   For reports, such as JDBC/XML, set the registry key to use the Crystal Enterprise/Report Application Server

   For the Identity Management Server to change data sources for reports in the Report Server, run the mergeConnection script.

2. On UNIX and Linux, check for Windows control characters in the mergeconnections script.

   If you downloaded the software using FTP in binary mode, these characters do not appear in this script. If you used another download method, use the dos2unix command to remove these characters.

3. Copy the mergeconnections_3.0.cf script from the system with the Identity Management Admin toolkit to the Report Server. On the system with the toolkit, the default location for this script is as follows:

   /opt/CA/IdentityManager/IAM_Suite/Identity_Manager/tools/ReportServerTools
   

4. On the Report Server system, place the script in this location:

   installation-directory/bobje/enterprise120/generic
   

5. Source in the environment variables for BusinessObjects Enterprise, as follows:

   source installation-directory//bobje/setup/env.sh
   

6. Run the following script:

   ./configpatch.sh mergeconnections_3.0.cf
   

7. Select 1 as the option when prompted.

   Note: On Linux systems, set the environment variable as follows before you run the script:

   export _POSIX2_VERSION=199209
   

8. Restart crystal processing servers as follows:
9. Log in as the non root user you used to install the Report Server.
10. Issue these commands:

    cd /opt/CA/SharedComponents/CommonReporting3/bobje
    ./stopservers
    ./startservers
    

11. Copy the JDBC JAR files.

Follow these steps:

1. Navigate to the jdbcdrivers folder where the Identity Management Admin toolkit is installed. The default location is as follows:

   Windows: C:\Program Files\CA\Identity Manager\IAM Suite\Identity Manager\tools\lib\jdbcdrivers
   UNIX: /opt/CA/IdentityManager/IAM_Suite/Identity_Manager/tools/lib/jdbcdrivers
   

2. Copy ojdbc14.jar (for Oracle) or sqljdbc.jar (for SQL Server) to the following location:

   Windows: CA\SC\CommonReporting3\common\4.0\java\lib
   UNIX: /opt/CA/SharedComponents/CommonReporting3/bobje/java/lib
   

3. Open the CRConfig.xml file, found in the following location:

   Windows: CA\SC\CommonReporting3\common\4.0\java
   UNIX: /opt/CA/SharedComponents/CommonReporting3/bobje/java
   

4. Add the location of the JDBC JAR files to the Classpath. For example:

   Windows: <Classpath>report_server_home\common\4.0\java\lib\sqljdbc.jar; report_server_home\ common\4.0\java\lib\ojdbc14.jar …</Classpath>
   UNIX: <Classpath>${BOBJEDIR}/java/lib/sqljdbc.jar:${BOBJEDIR}/java/lib/ojdbc14.jar:…</Classpath>
   

5. Save the file.
6. Restart the Report Server as follows:

   For Windows, perform the following steps:

   1. Go to Start, Program Files, BusinessObjects XI 3.1, BusinessObjects Enterprise, Central Configuration Manager.The Central Configuration Manager opens.
   2. Select all services and click Restart.

   For UNIX, do the following:

   cd /opt/CA/SharedComponents/CommonReporting3/bobje ./stopservers ./startservers
   

Run the Registry Script

For the Identity Management Server to change data sources for reports in the Report Server, run the mergeConnection script.

Note: On a 64-bit system, omit this procedure. The Report Server is a 32-bit application, so you use the 32-bit side of the registry. On a 64-bit system, open REGEDT32 directly from SysWOW64, and create the MergeConnectionProperties key with the Type REG_SZ and value Yes. Create the key in this location:

@HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Business Objects\Suite 12.0\Crystal Reports\DatabaseOptions

On Windows, perform the following steps:

1. Copy the mergeConnection script from the system with the Identity Management Server Admin toolkit to the Report Server. On the system with the toolkit, the default location for this script is as follows:

   C:\Program Files\CA\Identity Manager\IAM Suite\tools\ReportServerTools

2. Run the mergeconnections_3.0.reg script and respond to the prompts that appear.
3. Click Start, Program Files, CA, Report Server, Central Configuration Manager.
4. Start all services, including Tomcat and the BO Server service.

On UNIX and Linux, perform the following steps:

1. Check for Windows control characters in the mergeconnections script.

   If you downloaded the software using FTP in binary mode, these characters do not appear in this script. If you used another download method, use the dos2unix command to remove these characters.

2. Copy the mergeconnections_3.0.cf script from the system with the CA IdentityMinderIdentity Management Server Admin toolkit to the Report Server. On the system with the toolkit, the default location for this script is as follows:

   /opt/ca/IdentityManager/IAM_Suite/Identity Manager/tools/ReportServerTools

   On the Report Server system, place the script in this location:

   installation-directory/bobje/enterprise120/generic
   

3. Source in the environment variables for BusinessObjects Enterprise, as follows:

   source installation-directory//bobje/setup/env.sh
   

4. Run the following script, as follows:

   ./configpatch.sh mergeconnections_3.0.cf
   

   Select 1 as the option when prompted.

   Note: On Linux systems, set the environment variable as follows before you run the script:

   export _POSIX2_VERSION=199209
   

5. Restart crystal processing servers as follows:
   1. Log in as the non root user you used to install the Report Server.
   2. Issue these commands:

      cd /opt/CA/SharedComponents/CommonReporting3/bobje
      ./stopservers
      ./startservers
      

Follow these steps:

1. Install and startup a X-server on your client operating system. (You can download X-Win32 from http://www.starnet.com/products/xwin32/download.php)
2. Log on to Linux by BOE installation account and run bash as below:

    bash$ export DISPLAY=$YOURXWin32ClientMACHINENAME:0.0
    bash$ echo &DISPLAY
    bash$ cd $INSTALLDIR/bobje/setup/
    bash$ source env.sh
    bash$ regedit
   

   where $INSTALLDIR is where BOE is installed.

3. Switch to X-win32 client machine and there will be a prompt Registry Editor if the configuration is successful in step 2.
4. Create a registry category under HKEY_LOCAL_MACHINE: HKEY_LOCAL_MACHINE\Software\Business Objects\Suite 12.0\Crystal Reports\DatabaseOptions
5. Add a key named MergeConnectionProperties under DatabaseOptions category and set the String value to Yes.
6. Add a key also named MergeConnectionProperties under HKEY_CURRENT_USER\Software\Business Objects\Suite 12.0\Crystal Reports\DatabaseOptions category and set String value Yes as it's Data.
7. Refresh or schedule report in Infoview and now it works.

Copy the JDBC JAR Files

1. Navigate to the jdbcdrivers folder where the Identity Management Server Admin toolkit is installed. The default location is as follows:
   • Windows: C:\Program Files\CA\Identity Manager\IAM Suite\tools\lib\jdbcdrivers
   • UNIX: /opt/ca/IdentityManager/IAM_Suite/Identity Manager/tools/lib/jdbcdrivers
2. Copy ojdbc14.jar (for Oracle) or sqljdbc.jar (for SQL Server) to the following location:
   • Windows: CA\SC\CommonReporting3\common\4.0\java\lib
   • UNIX: /opt/CA/SharedComponents/CommonReporting3/bobje/java/lib

   The ojdbc14.jar and the sqljdbc.jar files are in the following location:

   • Windows: CA\IdentityManager\IAM_Suite\IdentityManager\tools\ReportServerTools
   • UNIX: /opt/CA/IdentityManager/IAM_Suite/IdentityManager/tools/ReportServerTools
3. Open the CRConfig.xml file, found in the following location:
   • Windows: CA\SC\CommonReporting3\common\4.0\java
   • UNIX: /opt/CA/SharedComponents/CommonReporting3/bobje/java
4. Add the location of the JDBC JAR files to the Classpath. For example:
   • Windows: <Classpath>report_server_home\common\4.0\java\lib\sqljdbc.jar; report_server_home\ common\4.0\java\lib\ojdbc14.jar …</Classpath>
   • UNIX: <Classpath>${BOBJEDIR}/java/lib/sqljdbc.jar:${BOBJEDIR}/java/lib/ojdbc14.jar:…</Classpath>
5. Save the file.
6. Restart the Report Server as follows:
   • For Windows, do the following:
     1. Go to Start, Program Files, BusinessObjects XI 3.1, BusinessObjects Enterprise, Central Configuration Manager.

        The Central Configuration Manager opens.

     2. Select all services and click Restart.
   • For UNIX, do the following:

     cd /opt/CA/SharedComponents/CommonReporting3/bobje
     ./stopservers
     ./startservers  
     

Deploy Default Reports

The Identity Management Server comes with default reports you can use for reporting. BIConfig is a utility that uses a specific XML format to install these default reports for CA IdentityMinderIdentity Management Server.

If you are upgrading from a previous version of the Report Server, first remove the CA Identity Manager Reports folder using the Central Management Console. The existing reports do not work. You can then deploy default reports for the new Report Server.

Important! This process updates all default reports. If you customized any default reports, be sure to back them up before performing the update.

1. Gather the following information about the Report Server:
   • Hostname
   • Administrator name
   • Administrator password
   • Snapshot database type
2. Copy all content from the Reports installer-root-directory/disk1/cabi/biconfig folder to the im_admin_tools_dir/ReportServerTools folder.
3. Set the JAVA_HOME variable to the 32-bit version of the JDK1.5 you installed.
4. Run one of the following commands:
   • For a Microsoft SQL Snapshot Database:

     biconfig -h "hostname" -u "administrator_name" -p "administrator_password" -f "ms-sql-biar.xml"
     

   • For an Oracle Snapshot Database:

     biconfig -h "hostname" -u "administrator_name" -p "administrator_password" -f "oracle-biar.xml"
     

   Note: In a UNIX operating environment, be sure that biconfig.sh has execute permissions.

5. View the biconfig.log file found in the location where you ran the command in Step 4.
6. Verify that the default reports installed successfully. Inspect the end of the log file for status; a successful install appears as follows:

   ReportingDeployUtility - Reporting utility program terminated and return code = 0
   

To Secure the Business Objects Report Server with SSL

The Identity Management Server and Report Server communicate over a non-secure connection. Secure Sockets Layer (SSL) connection can be used to secure the connection between Report Server and The Identity Management Server.

An SSL connection ensures that the communication is encrypted when data is accessed from the Report Server. Before configuring the SSL, verify that the BO (Business Objects) Server has HTTPS enabled. To secure the connection with SSL, self-signed certificate or the certificate from the Certified Authority (CA) can be used.

To configure an SSL certificate using self-signed certificate, perform the following steps:

1. Export the certificate from the keystore used in the BO Server, using any tool which generates a certificate.
2. Copy the certificate to a directory where the Identity Management Server is installed.
3. Import the Certificate in to the Java trust store (cacerts). Also, verify that the certificate is imported in to the java version which is currently used by CA IdentityMinderIdentity Management Server.
4. Restart the Application Server for the changes to take effect.
5. In The User Console, go to System, Reporting, Report Server Connection. Select the Secure Connection option.
6. Click Test Connection to verify the connectivity.

The following procedure is an example on how to export and import a certificate using the Keytool utility.

1. In the Business Objects Report Server, open the command prompt and enter the following command to export the certificate from the keystore:

   Windows:

   ..\jvm\bin\keytool -export -alias testcert -file certificate.cer -keystore c:\cert\.keystore  -storepass <keystore password>
   

   Linux or Solaris:

   ../jvm/bin/keytool -export -alias testcert -file certificate.cer -keystore /root/.keystore  -storepass <keystore password>
   

2. Copy the certificate to a directory where the Identity Management Server is installed.
3. In the Identity Management Server, open the command prompt and enter the following command to import the certificate into the keystore:

   Windows:

   ..\jvm\bin\Keytool -import - trustcacerts -file c:\cert\certificater.cer -alias testcert -keystore JAVA_HOME\jre\lib\security\cacerts -storepass password 
   

   Linux or Solaris:

   ../jvm/bin/Keytool -import - trustcacerts -file /root/certificater.cer -alias testcert -keystore JAVA_HOME/jre/lib/security/cacerts -storepass password
   

   The certificate is successfully installed.

Note: We recommend that you refer to the vendor-specific documentation to configure SSL on the Report Server. The Report Server supports Tomcat and IIS servers.

Uninstallation

To uninstall BusinessObjects Enterprise, run the uninstallBOBJE.sh script. The uninstallBOBJE.sh script is installed to the bobje directory of your installation.

This script stops all BusinessObjects Enterprise servers and processes, and then deletes the files copied from the product CD during your original installation of BusinessObjects Enterprise. Installing BusinessObjects Enterprise creates a number of additional files on your system. The uninstallBOBJE.sh script will not remove the files created during the installation process, or files created by the system or by users after installation. The files that remain include log files created by BusinessObjects Enterprise. These log files can be useful in diagnosing problems with previous installations.

To remove all BusinessObjects Enterprise files, perform an rm -rf command on the bobje directory.

Note: If you performed the “system” installation type, you will also need to delete the run control scripts from the appropriate /etc/rc# directories

Additional Information

Description: MergeConnectionProperties registry key

To be able to change server or database information at runtime for reports that are based on command objects. A registry key named "HKEY_CURRENT_USER\Software\Business Objects\Suite 11.0\Crystal Reports\DatabaseOptions\MergeConnectionProperties (Yes/No)" was introduced to allow the option of merging old connection properties to new connection properties; however, the problem continues, because the provider is not included in the query definition.

For reports,such as JDBC/XML, users must set the registry key to 'Yes" use the Crystal Enterprise/Report Application Server.

• ojdbc.jar or ojdbc14.jar
• Ojdbc6.jar is for java 1.6 since it supports the new JDBC 4.0 specification (it has a dependency on JDK 1.6).
• Whereas CABI 3.3 runs with JDK 1.5. We have to copy ojdbc14.jar to work with the reports.

Debugging/Logs

If the CMS does not start, check the /var/log/messages file for the information. This is equivalent to event viewer in windows.