You may have already seen the announcement about sunset of the SAP Business Technology Platform (BTP), Neo environment. This blog post covers the technical aspects of migrating SAP Mobile development kit (MDK) applications from SAP BTP Neo to Cloud Foundry environment.
In general, migration from SAP Neo to Cloud Foundry environment involves a landscape migration e.g.,
You will notice some differences during the transition to SAP Mobile Services Cloud Foundry. Yet, these changes are typically more beneficial, providing you with advanced features. It's important for you to familiarize yourself with any functionality that might not be available after migration and also changes in the SAP Mobile Services Cloud Foundry cockpit. Understanding these changes prior to migration will ensure a smooth and efficient transition process.
The steps below will help you migrate your MDK app from SAP BTP Neo to Cloud Foundry environment:
Once you become familiar with some of the changes in SAP mobile service cockpit operations, replicating mobile application configurations between Neo and Cloud Foundry should be straightforward. You can recreate the application manually or export the application configuration on Neo and import the configuration on Cloud Foundry. Due to the differences in mobile services on Neo and Cloud Foundry, only part of application configuration can be imported into Cloud Foundry, and other parts of configuration must be recreated. Please refer below documentations:
Migrate MDK metadata (app definitions)
If you had previously deployed the MDK metadata (app definitions) to the SAP Mobile Services Neo App Update, the same needs to be done for your application configured on SAP Mobile Services Cloud Foundry. To deploy the MDK metadata, you can use below options:
Note: Please follow this blog post on migrating your MDK apps from SAP Web IDE to SAP Business Application Studio and continue enhancing it further.
Reset/Re-onboard MDK client
Before the application is reset to onboard with the new Cloud Foundry Mobile Application, users needs to ensure that there is no unsynchronized data left in their local Offline databases by performing a sync within the application When the application is reset any unsynchronized data will be lost.
The Mobile application URLs of SAP BTP Neo and Cloud Foundry environments are different. In Cloud Foundry, each mobile application has its own unique hostname to connect, as shown on the APIs page of an application. Furthermore, the OAuth specific URLs of Neo and Cloud Foundry are also different. In order to connect to the Mobile application configured on Cloud Foundry environment, a reset and re-onboarding of the MDK client is required.
I hope this post helps you in migrating your MDK application from SAP BTP Neo to Cloud Foundry environment. If you have any question or feedback, please add it in the comment section.
Where can I learn more?
Please familiarize yourself with the multi-cloud environment for SAP BTP on the SAP Help Portal. You can find more information in the Neo sunset FAQ. If you have additional questions, please contact our migration experts.
In general, migration from SAP Neo to Cloud Foundry environment involves a landscape migration e.g.,
- Creating Sub-Accounts, Organizations and Spaces
- SAP Cloud connector setup must be copied to point to the Cloud Foundry account
- Identity provider settings need to be replicated and so on
You will notice some differences during the transition to SAP Mobile Services Cloud Foundry. Yet, these changes are typically more beneficial, providing you with advanced features. It's important for you to familiarize yourself with any functionality that might not be available after migration and also changes in the SAP Mobile Services Cloud Foundry cockpit. Understanding these changes prior to migration will ensure a smooth and efficient transition process.
The steps below will help you migrate your MDK app from SAP BTP Neo to Cloud Foundry environment:
- Migrate Mobile Application Configuration from SAP Mobile Services Neo to Cloud Foundry Environment
- Migrate MDK metadata (app definitions)
- Reset/Re-onboard MDK client
Migrate Mobile Application Configuration from SAP Mobile Services Neo to Cloud Foundry Environment
Once you become familiar with some of the changes in SAP mobile service cockpit operations, replicating mobile application configurations between Neo and Cloud Foundry should be straightforward. You can recreate the application manually or export the application configuration on Neo and import the configuration on Cloud Foundry. Due to the differences in mobile services on Neo and Cloud Foundry, only part of application configuration can be imported into Cloud Foundry, and other parts of configuration must be recreated. Please refer below documentations:
- Before importing the application
- How to import application configuration
- After importing the application
SAP Mobile Services cockpit on Neo and Cloud Foundry Environment
Migrate MDK metadata (app definitions)
If you had previously deployed the MDK metadata (app definitions) to the SAP Mobile Services Neo App Update, the same needs to be done for your application configured on SAP Mobile Services Cloud Foundry. To deploy the MDK metadata, you can use below options:
- SAP Business Application Studio or
- MDK tools or
- Visual Studio Code MDK extension or
- manually upload the bundle zip to app update
Note: Please follow this blog post on migrating your MDK apps from SAP Web IDE to SAP Business Application Studio and continue enhancing it further.
Reset/Re-onboard MDK client
Before the application is reset to onboard with the new Cloud Foundry Mobile Application, users needs to ensure that there is no unsynchronized data left in their local Offline databases by performing a sync within the application When the application is reset any unsynchronized data will be lost.
The Mobile application URLs of SAP BTP Neo and Cloud Foundry environments are different. In Cloud Foundry, each mobile application has its own unique hostname to connect, as shown on the APIs page of an application. Furthermore, the OAuth specific URLs of Neo and Cloud Foundry are also different. In order to connect to the Mobile application configured on Cloud Foundry environment, a reset and re-onboarding of the MDK client is required.
- If you have built your branded MDK client by providing mobile services connection settings in .mdkproject, you need to update the BrandedSettings.json with new connection details and re-built the client
- If there is override functionality is enabled in the client, user can scan the new on-boarding QR code connecting to mobile services on Cloud Foundry environment. The on-boarding QR code can be found in Mobile Services app configuration (under APIs tab) OR in Business Application studio (right click on Application.app and open it in Application editor > QR Code).
SAP Mobile Services on Cloud Foundry Environment
MDK Editor in SAP Business Application Studio
I hope this post helps you in migrating your MDK application from SAP BTP Neo to Cloud Foundry environment. If you have any question or feedback, please add it in the comment section.
Where can I learn more?
Please familiarize yourself with the multi-cloud environment for SAP BTP on the SAP Help Portal. You can find more information in the Neo sunset FAQ. If you have additional questions, please contact our migration experts.
- SAP Managed Tags:
