BO 4.3 Upgrade or do Migration

server administration BI4.3
21

The AD groups will be pulled over if you follow the steps detailed in the Pattern Book.

22

Here’s what I do with my clients:

  1. Configure AD Authentication in the new system and import 1 group for testing to make sure that it’s working correctly.

  2. After verifying that AD Authentication is working, delete the group used for testing. This will also delete all of the users in the group. If you don’t do this, you’ll end up with duplicate users with different identifiers (SI_ID, SI_CUID).

  3. Import the AD groups from the old system.

Doing it this way, you don’t have duplicates and all of your security should migrate successfully as well. If you manually add the AD groups instead of promoting them, you’ll have to rebuild your security as well.

-Dell

2 Likes
23

What about RESTful. I cannot get this working for HTTPS. And all the SAP documents are no help, most of them have links that go nowhere.

Any configuration help I would be greatful.

24

Thank you for this discussion, very helpful. We will be migrating our 4.2 environment to 4.3 shortly. Initially it would have been 4.2 SP2 P800 but given discussion of SP2 we may look for SP3 P100.

We have been directed to move to a Windows environment of AWS and we plan to use SQLServer for RDS for our CMS and Audit repository databases. Our server team asked which instance type of RDS is supported/recommended by SAP. We haven’t found any such documentation and SAP Support gave a non-answer and directed us to the 4.3 PAM

Has anyone worked an installation of BusObj in an AWS environment? Any RDS instance type suggestions? Our existing db server for the CMS is 2 CPUs and 8 GB RAM and I was thinking an instance type db.m6i.large as similar.

Also, any suggestions and pitfalls to watch for would be helpful.

@hilfy , thank you for your insights.

tia
patw

25

Hi Hilfy,

Awesome post, everything well explained. I have question regarding the delta migration, how do you these queries e.g. only changed/new users, or only changed/new connections etc.? Is it enough to add to the export queries the SI_UPDATE_TS?

Thank you.

26

Hi Matthew,

Yes, that’s exactly what you do. You need to use this format for the date to get it to work right.

YYYY.MM.dd.HH.mm.ss

-Dell

27

I’m curious how your upgrade turned out. SAP BusinessObjects is supported for all the major cloud vendors. Did you go with AWS?

28

Hi Hilfy,

Thanks a lot for your detailed explanation but I have some questions about the process.
We have a PROD environment in BOXI 3.1 in a Windows 2008 server. We would like to update to 4.2 and windows server 2019.
We have mounted a new server on Windows Server 2019 but now the questions are:

  • Should we use the PMW or just installing the BOXI 4.2 in this server and use the option “Expand and existing SAP BO platform deployment (Requires a remotely installed CMS)” in the installation wizard?
  • If using the PMW, which DB will be used for?
  • If using the “Expand…” option, will be compatible with 3.1?

Thanks a lot in advance

29

You cannot use the Expand option for the BI 4.2 install as it is not compatible with BO 3.1. You will break your BO 3.1 system.

I can’t remember if you can use the Promotion Management Wizard or if you have to use the Upgrade Management Tool to upgrade from BO 3.1 to BI 4.2. Consult the upgrade documentation.

30

We have used Report conversion tool for Deski → Webi conv and for the rest the UMT.
the servers were not mounted, just firewalls allowed communication,