Skip to Content
avatar image
Former Member

Promote 4.0 to 4.1 and change computer name

Approach: Install 4.1 BO on new environment, using Promotion Management to promote all report include Dashboard, WEBI, Crystal Report, Qaaws, Universe, User Groups etc. Output of Promote as LCMBIAR file. Repeat this into Production, Development and Disaster server. VMWare is being used.

Scenario: Because shortage of time, I have an idea. Finish install BO 4.1 into Production server and promote all report into LCMBIAR file. Duplicate a copy of Production VMWare and change computer name of duplicate version. After computer name changed, follow instruction from SAP Note 1592215 to update BI4.1.

Is my idea gonna work???

Add comment
10|10000 characters needed characters exceeded

  • Follow
  • Get RSS Feed

3 Answers

  • Best Answer
    Jan 08, 2015 at 01:35 PM

    Why cannot you do inplace upgrade?

    It is much faster and you don't have to do anything.

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Jan 08, 2015 at 02:20 PM

    Hi,

    I feel that its perfectly fine to use the approach,as it will save time and effort too.

    Ensure that during this process PROD is not hampered.

    You can use a different network to isolate you activity and once the Hostname, Cluster name are changed and SIA is recreated include the system to the Landscape network.

    Make sure during this process all necessary backups (CMS and Filestore) are in place.

    -Guru

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Jan 12, 2015 at 10:32 AM

    Hello,

    It would be interesting to know how the SIA and system name change behaves with BO.

    It is slightly risky to clone the VM especially if in use for a production level system. The ill effects of saving time may result in unexpected behavior.

    The best approach in this case would be to install BusinessObjects on a new VM.
    Take a backup of the CMS database and Filestore of the old VM.
    Restore this backup to the new installation.
    Recreate NEW SIA on the restored repository.

    KBA 1275068 discusses this approach in detail.

    -Sid

    Add comment
    10|10000 characters needed characters exceeded