Technology Blogs by Members
Explore a vibrant mix of technical expertise, industry insights, and tech buzz in member blogs covering SAP products, technology, and events. Get in the mix!
cancel
Showing results for 
Search instead for 
Did you mean: 
CdnConnection
Active Contributor

Doing a Full install from BI 4.0.6+ to BI 4.1.6 and Retaining FULL content & Settings

Major Benefits:

  • Save an average of 5-8Gig per SP/FP applied to your original install
  • Installing NEW features of BI 4.1.6 with any corruption to your BI4 install
  • Consistent built of all DLL and library files, no mixed versions of DLL’s
  • Opportunity to cleaning up OS build and optimize base server Pre BI 4.1.6
  • Upgrade from Windows 200x to 2012 with FULL content retention
  • Move your install from Drive C: long name to any Drive with shorter path
    • D:\SAP BusinessObjects\
  • NO need for Promotion Manager to move any objects
  • NO need to re-configure any BI4 Server, all settings fully retained
  • No Size &/or Objects limit for FRS restore (restored up to 50Gig)

High-Level Steps:

  • The CMS database MUST be the correct version prior to connecting to BI 4.1.6
  • Do complete back-up of existing BI 4.0.6+ Server, including
    • CMS and Audit database
    • BOBJ Administrator password should be complicated
    • Reset / Validate Cluster Key password
    • D:\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\Data\Polestar
    • D:\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\Data\TrendingDB
    • D:\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\FileStore
    • Any other special customization done
    • Originally running on Windows 2003 Ent 64bit
  • Upgrade the current BI 4.0.6+ environment to BI 4.1.6
  • Upgrade any additional options being used such as:
    • BI 4.1.6 Explorer
    • Analysis 1.4 w/ SP13 BIP Add-In
    • Design Studio v1.5 Add-In
    • Lumira v1.0.27 BIP Add-In
  • All other options should be installed after BI 4.1.6 Cluster has been reinitialized

Our Restore Example:

Server Name:          PS01

CMS Name:             PS01

Administrator:         <Confirm password is complex>

Cluster Key:            Confirmed password

CMS_DB:                XI4_CMS (MS SQL Server 2012)

Audit_DB:               XI4_AUDIT (MS SQL Server 2012)

ORG BI4 ver:           BI 4.0 w/ SP2

  • Upgraded to BI 4.0 w/SP4
  • Upgraded to BI 4.0 w/SP6
  • Upgraded to BI 4.1
  • Upgraded to BI 4.1 Patch 02
  • Upgraded to BI 4.1 w/SP4
  • Upgraded to BI 4.1 w/SP6

New Windows 2012 RC2 64bit Install

FACT: You will save disk space when doing NEW full install

  • Using real world experience from supporting 50+ BI 4.x installs. With every patch upgrade BI4 Platform install directory increases in size.
  • The current clean-up processes after a patch is very poor, older files are NOT removed.
  • Clean move from Windows 2003/2008 to Windows 2012 with full retention
  • In install example, customer started with NEW Bi 4.0 w/SP2 install
    • Upgraded to BI 4.0 w/SP4 (Added ~ 7Gigs of overhead)
    • Upgraded to BI 4.0 w/SP6 (Added ~ 7Gigs of overhead)
    • Upgraded to BI 4.1 (Added ~ 7Gigs of overhead)
    • Upgraded to BI 4.1 Patch 02 (Added ~ 7Gigs of overhead)
    • Upgraded to BI 4.1 w/SP4 (Added ~ 7Gigs of overhead)
    • Upgraded to BI 4.1 w/SP6 (Added ~ 7Gigs of overhead)
    • Approx. added 40+ Gigs of overhead to your install

FACT: Move from Windows 200x to 2012 with full retention

This is an excellent opportunity to move your BI 4.1.6 install from Windows 200x to Window 2012 as long as the server name stay the same.

FACT: Repointing a newer BI 4.1.6 to an older Repository BI 4.xx is NOT valid

Starting with BI 4.x the CMS database now has full version signature.  You can’t take an older BI 4.0.6 CMS database and connect it to a BI 4.1.6 install, this will corrupt you install.




Step 1: Back-up Current BI 4.0.6 Environment

Complete Back-Up Process includes:

  • BOBJ Servers Image back-up by IT
  • CMS and Audit database
  • D:\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\Data\Polestar
  • D:\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\Data\TrendingDB
  • D:\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\FileStore
  • Any other special customization done

Step 2: In-Place Upgrade to BI 4.1 W/SP6

In-Place Upgrade involves:

  • NOTE: Confirm Administrator password is complex; otherwise you will have issues with SIA when doing FULL Install.  See NOTE – 2188271
  • We need to upgrade the current BI 4.x install to BI 4.1.6 in order to have the CMS database updated. 
    • Upgrade all the CMS Server in parallel
    • Next upgrade ALL the Applications servers within the cluster

Update - SAP Explorer to BI 4.1 w/ SP6 (Optional if installed)

Update – Analysis Add-On for BIP ver 1.4 w/ SP13 (Optional if installed)

Update – Design Studio 1.5 for BIP Add-On (Optional if installed)


Update – LUMIRA BI Platform add-on ver 1.27 (Optional if installed)


Step 3: Back-up In-Place Upgraded BI 4.1.6 Environment

Complete Back-Up Process includes:

  • BOBJ Servers Image back-up by IT
  • CMS and Audit database
  • D:\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\Data\Polestar
  • D:\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\Data\TrendingDB
  • D:\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\FileStore
  • Any other special customization done
  • Take NOTE of:
    • System DNS named and configuration
    • 64-bit Database drivers
    • Any other 3rd party software configuration
  • We will need the BI 4.1.6 signature upgraded CMS database & FRS as a SET to attached to NEW install.

Step 4: Doing NEW FULL-Build Install of BI 4.1 w/SP6

  • Get IT to do NEW installed Windows 2012 RC2 Server with same name as previous BOBJ server, in our example its “PS01”.  If running a BI4 Cluster, you will need IT do NEW installs of Windows 2012 with same name as previous server (SERVER_xx).

  • Install 64-ODBC Drivers required and configure properly. In our example it 64-bit MS SQL 2012 Native Client / Admin tool.
  • Configure the System ODBC-64bit with same names as original BOBJ server.  In our example XI4_CMS / XI4_AUDIT
  • Integrate other options, such as:
    • Joint NT Domain controller using proper NT Service Account
    • Integrate SAN / NAS as required
    • Install SUN JRE / JRK as required, set-up proper parameters
    • Install HTTP / JAVA Application as required
    • Install latest Windows Security updates, including .NET 4.5
    • Other miscellaneous application &/or configuration
  • Have IT take fully IMAGE / SNAPSHOT of system prior starting BI 4.1.6 NEW Install. Taking a full back-up of the NT Server PRE_BOBJ will come in handy in the future.

Install BI 4.1.6 w/SP6 NEW install

Install BI 4.1.6 w/SP6 Explorer Add-On (Optional😞


Install Analysis 1.4 w/SP13 – Add-On for BIP (Optional😞

Install Design Studio 1.5 w/SP00 – Add-On for BIP (Optional😞

Install Lumira Server v 1.0.27 for BIP (Optional😞

Validate NEW BI 4.1.6 CLUSTER Install with SAME Add-On’s

For a BI 4.1.6 Cluster, continue install of other servers

  • Install other CMS Servers within Cluster
  • Next install all other Application servers within Cluster
  • NEW base BI 4.1.6 Cluster is fully ready and on-line

Step 5: Doing Server Restore of ORIGINAL System:

Complete Restore Process includes:

  • STOP Tomcat & SIA
  • Restore CMS Database and Audit Database
    • In our sample it’s XI4_CMS & XI4_AUDIT
    • D:\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\Data\Polestar
    • D:\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\Data\TrendingDB
    • D:\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\FileStore
    • Any other special customization done

Server Restore Process Step-by-Step:

For more details on FULL restore, please refer to SCN post

How to Restore BI4 from FRS & CMS Backup

  • Continue installing any NEW add-on options as required to fully working cluster
4 Comments
Labels in this area