BOBJ Pre-Upgrade Assessment Guide
The following Blog covers specifically BOBJ BI 3.1 to BOBJ BI 4.0/4.1 upgrades. The overall steps still apply to most other BOBJ BI upgrade scenarios.
Prior to embarking on a BOBJ BI upgrade project, each customer must do a little homework before launching the initiative. A full assessment of the current environment must be conducted and documented. This includes a full inventory of all the objects and functionality currently being used in your current environment. This means collecting information regarding which tools are currently used, all the connections, universes, and metadata.
- Are you using Crystal Reports, webIntelligence, deskI, dashboards, info spaces, etc?
- How many instances are currently scheduled?
- Are you using any of the following functions and how many? Categories, folders, groups, forums, etc
- How many users do you have? Concurrent, named?
- How many of these users are inactive?
- What source systems are connected to BOBJ? Do you have a SAP BW source system? A mix of systems?
- What does the system landscape currently look like? How many nodes, load balancing, operating systems, etc?
In addition to taking a full inventory of what needs to be migrated after the upgrade. You should also consider what future capabilities you want to be able to use or explore in the future after the upgrade. Do you want to turn off unused features and allocate the extra resources to your main tools? Will you want to ensure all tools are available after the upgrade?
- Design Studio
- OLAP Analysis
- Mobility Features
After performing this valuable assessment, the next step is to develop an upgrade plan. Based on the results, your post-upgrade plan should have a set of steps for how to handle each tool's content. Therefore, your plan will be divided into migration of webI content, Crystal Reports content, Analysis content and Universe objects. Each of these areas should include plans for migration, conversion, testing, and promotion of objects.
Further, if you have a complex landscape with several source systems connected to BOBJ, you may want to consider further sub-dividing each tool along with each of the source systems. This is due to the differences that exist sometimes depending on the source system. Migrating a SAP BW connection from 3.1 to 4.1 is quite different from migrating a SQL based universe.
Organizing the migration of objects this way leads to timesavings and the possibility of processing the migration in parallel steps. It also leads to fewer errors by permitting each member of the team to focus on their objects.
With an ATCG Pre-Upgrade Assessment, you receive a full inventory of your landscapes metrics, a plan and a roadmap. After the assessment, you can choose to complete your upgrade with your in-house team, ATCG's team or a combination of both. We recommend going with a hybrid team so you can benefit from our expert knowledge and enjoy the cost savings.
Upgrade and/or migrate today by contacting ATCG Solutions. Don't forget to download our FREE guide!
Check out some of our other related links on the topic of SAP BOBJ BI upgrades and migration.