How to install CA Business Intelligence (CABI) 3.3 SP2 (also referred to as Business Objects Enterprise (BOE) 3.1 SP7) to an existing CABI r3 SP5 (CABI 3.3) install?

book

Article ID: 18174

calendar_today

Updated On:

Products

SUPPORT AUTOMATION- SERVER CA Service Desk Manager - Unified Self Service KNOWLEDGE TOOLS CA Service Management - Asset Portfolio Management CA Service Management - Service Desk Manager

Issue/Introduction

Introduction:

Apply CABI 3.3 SP2 (BOE 3.1 SP7) to an existing CABI 3.3 (BOE 3.1 SP5 or 12.5.0.XXXX) install

You can check if 3.1 SP5 is installed by performing the following:

  • Login to the Central Management Console with an Administrator account.
  • Click on SETTINGS under the MANAGE section.
  • The Product Version should be listed as '12.5.0.XXXX'

    <Please see attached file for image>

    Figure 1

Instructions:

  1. Using a FTP client, download 3.1 SP7 from: ftp://ftp.ca.com/caproducts/CABI/CABI-3.x/boeXIR3_SP7/Windows/cabi-windows-boeXIR3_SP7.zip
  2. Extract 3.1 SP7 on the CABI/BOXI server
  3. Take a backup of the following files to another location:

    SC\CommonReporting3\Tomcat55\webapps\OpenDocument\WEB-INF\web.xml
    SC\CommonReporting3\Tomcat55\conf\server.xml
    SC\CommonReporting3\Tomcat55\conf\web.xml
    SC\CommonReporting3\BusinessObjects Enterprise 12.0\win32_x86\dataAccess\connectionServer\odbc\odbc.prm
  4. Review the README.TXT file for patch information. Run the following from the directory SP7 was extracted to: BIEKPATCH.EXE
  5. Click OK on the Language Screen

    <Please see attached file for image>

    Figure 2

    NOTE - it might take a few moments for the patch installer to initialize
  6. Click on NEXT

    <Please see attached file for image>

    Figure 3
  7. Accept the License Agreement and click on NEXT

    <Please see attached file for image>

    Figure 4
  8. Enter the CABI CMS Administrator Password and click on NEXT

    <Please see attached file for image>

    Figure 5
  9. Select 'Yes, automatically redeploy the web applications' and click on NEXT

    <Please see attached file for image>

    Figure 6
  10. If Apache Tomcat 5.5 is still being used as the CABI web server and is detected, it will automatically be upgraded to Apache Tomcat 7.0.27. Click NEXT to proceed.

    <Please see attached file for image>

    Figure 7
  11. Click on NEXT to begin the CABI SP7 install. Be aware that the SP7 install will take some time to complete.

    <Please see attached file for image>

    Figure 8

    <Please see attached file for image>

    Figure 9

    <Please see attached file for image>

    Figure 10
  12. Once the SP7 install is complete, click on the FINISH button to exit the SP7 install.

    <Please see attached file for image>

    Figure 11
  13. To confirm that the SP7 install was successful, login to the Central Management Console with an Administrator account. Click on SETTINGS under the MANAGE section. The Product Version should be listed as '12.7.0.1983'

    <Please see attached file for image>

    Figure 12

    NOTE: If you encounter an error message "Error: Server sdmrep:6400 not found or server may be down (FWM 01003) null" when logging in to the Central Management Console and the Server Intelligence Agent service does not start, please refer to the TEC1946678.
  14. Compare the following two (2) files that were backed up earlier

    A.
    Backed up version of 'SC\CommonReporting3\Tomcat55\webapps\OpenDocument\WEB-INF\web.xml '

    WITH

    Current version of 'SC\CommonReporting3\Tomcat7\webapps\OpenDocument\WEB-INF\web.xml '

    There should not be many differences apart from the TrustedAuthentication enablement and Authentication visibility. Merge those items only from the old file to the current file (SC\CommonReporting3\Tomcat7\webapps\OpenDocument\WEB-INF\web.xml)

    B. Backed up version of 'SC\CommonReporting3\BusinessObjects Enterprise 12.0\win32_x86\dataAccess\connectionServer\odbc\odbc.prm '

    WITH

    Current version of 'SC\CommonReporting3\BusinessObjects Enterprise 12.0\win32_x86\dataAccess\connectionServer\odbc\odbc.prm'

    There should not be many differences except for Date Parameters. Merge those items only from the old ODBC.prm file to the current file (SC\CommonReporting3\BusinessObjects Enterprise 12.0\win32_x86\dataAccess\connectionServer\odbc\odbc.prm)
  15. Compare the other two backed up files

    A. Backed up version of 'SC\CommonReporting3\Tomcat55\conf\server.xml'

    WITH

    Current version of 'SC\CommonReporting3\Tomcat7\conf\server.xml '
    Merge only the PORT or HTTPS type of differences.

    Do NOT just restore Tomcat55 files on top of Tomcat7 files or else Tomcat will fail to start.

    B. Backed up version of 'SC\CommonReporting3\Tomcat55\conf\web.xml'

    WITH

    Current version of 'SC\CommonReporting3\Tomcat7\conf\web.xml'
    Merge only security constraints or similar settings that were customized in this file.

    Do NOT just restore Tomcat55 files on top of Tomcat7 files or else Tomcat will fail to start.

    Note: A merge tool like WinMerge or Notepad++ could be used to easily identify the above differences.

 

Additional Information:

TEC566603: How to install CA Business Intelligence (CABI) 3.2 Service Pack 5 (SP5)
TEC592444: How to install CABI r3 SP6 (also referred to as CABI r3.3 SP1)
TEC1946678: After the BOXI SP7 installation, BOXI does not start

Environment

Release:
Component: SDBOXI

Attachments

1558702372239000018174_sktwi1f5rjvs16ptg.gif get_app
1558702370433000018174_sktwi1f5rjvs16ptf.gif get_app
1558702368525000018174_sktwi1f5rjvs16pte.gif get_app
1558702366586000018174_sktwi1f5rjvs16ptd.gif get_app
1558702364748000018174_sktwi1f5rjvs16ptc.gif get_app
1558702362681000018174_sktwi1f5rjvs16ptb.gif get_app
1558702360740000018174_sktwi1f5rjvs16pta.gif get_app
1558702359038000018174_sktwi1f5rjvs16pt9.gif get_app
1558702357120000018174_sktwi1f5rjvs16pt8.gif get_app
1558702355268000018174_sktwi1f5rjvs16pt7.gif get_app
1558702353405000018174_sktwi1f5rjvs16pt6.gif get_app
1558702351307000018174_sktwi1f5rjvs16pt5.gif get_app