In our first blog, we provided an overview of the HANA Enterprise Cloud (HEC) and introduced the services that are available for customers that ensure a smooth transition to the HEC. The second blog detailed the technical assessment available to customers to help them develop a technical landscape and put together a plan for migration to HEC. In the third installment of this series, we will dive into the Onboarding and Migration Services provided by SAP for customers looking to move their existing applications to the HEC.
The Onboarding & Migration service is really where the “rubber meets the road” for a customer’s migration to HEC because this is when the customer systems are migrated to the HEC. Careful planning in terms of downtime, upgrade execution and OS/DB migration is required to ensure a smooth transition and minimal impacts to the end user community. The service involves tight collaboration among multiple teams, including customer, SAP Services, the operations teams from the HEC, and the HEC Center of Excellence (CoE) in order to be successful.
One point of note—the Onboarding and Migration service is needed to migrate existing systems. If the targeted applications for HEC are “greenfield” or new installations then no Onboarding & Migration services are required. The installation of these systems are included in the HEC monthly fees.
Instead of an FAQ style approach like last blog, we’ll take customer example to give you an idea of what a typical migration will look like in this one.
The customer is going to migrate an existing BW system and consists of the following technical landscape:
Therefore, the project approach will need to account for a stack split to separate out the Java stack from ABAP stack before upgrading to 7.31. The SAP Services team and project have agreed to a traditional 5 cycle approach for OS/DB migration as shown in the following graphic:
The customer and SAP Services work closely together to create a detailed migration plan and once this is agreed up the project starts.
The phase of the project can be termed landscape preparation. The following items are addressed here:
In the execution phase of the project, 5 cycles are conducted. The timing of this phase varies depending on the customers testing and validation requirements.
Finally, the productive system is validated and turned back to the end user community.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
13 | |
10 | |
10 | |
7 | |
6 | |
5 | |
5 | |
5 | |
4 | |
4 |