Dear Integration Experts,
As we are aware that SAP Neo is going to be sunset on December 31, 2028, and there are many projects which are running on Neo and needs to be migrated to Multicloud environment or Cloud Foundry. I am writing this blog based on my real time experience about migration.
The multi-cloud foundation has become the strategic focus for SAP BTP because of its significant benefits as compared with the Neo environment, including its principles of openness and freedom of choice in terms of support for multiple infrastructure providers, data centers, and a wide range of runtimes and programming languages.
There are two options to perform the migration based on the requirements. One is SAP provided migration package to migrate the interfaces and other related objects. Other option is to use manual export and import to migrate the objects from Neo to Cloud Foundry.
In this blog I will be using SAP provided Migration pack to migrate the objects from Neo environment to Cloud Foundry.
Every migration project should have following stages:
Discover – In the discovery phase we identify the interfaces, security material, certificates, variables, data store, number ranges, credentials, PGP encryption and other objects which we need to migrate. We prepare the list of interfaces, third parties integrated with SAP, SAP and Non-SAP systems integrated, Cloud or on-premises system integration, Cloud connector configuration etc.Plan & Prepare – In Plan & Prepare phase we check the readiness of Neo and Cloud Foundry. In Neo environment we should have all artifacts saved in version as a prerequisite. In draft mode automatic migration will not work. We should communicate with third parties connected about the migration plan and inform them about the endpoint changes required. We prepare the target or Cloud Foundry tenant.Migration – In this step we perform the actual migration process from neo to Cloud foundry. There are certain steps required to prepare for the migration process automatically which I will discuss later.Validation- Once we complete the migration process, we need to validate. We need to raise the ticket to SAP to validate the migration. Also, we can test the simple iflow as a part of pilot and validate the same.
In this blog I will explain step by step process to migrate from Neo to CF environment using SAP provided Migration pack.
Prerequisites:
Provision and setup SAP BTP Integration Suite Cloud Foundry environment.Create and Instances for both plan Integration flow as well as API.Create Service key for both the plan, which we will need for authentication purpose.Assign proper roles to user who is performing migration in Neo as well as in CF tenant.Postman should be installed.Download the compressed file available in SAP note 2937549, This file contains postman collection for migration.
Migration Process:
We perform the migration process by running several Postman requests. To execute these requests, we can use a set of Postman collections predefined by SAP. First, we need to prepare the environment file. In order to create an environment file, we should setup Oauth authentication in Neo and CF.
Configure Oauth Authentication in Neo environment:
Set Up an Oauth in both NEO (for NEO make sure you generate Oauth on “tmn” node ) and CF (For CF make sure the plan selected is “api” )
Login to BTP Cockpit and Neo subaccount. Goto Securityà Oauth, click on Register new client.
Note down the client ID and Secret, this will be used as user id and password in migration.
Using the client ID from the previous step, navigate to Security->Authorizations and assign the user oauth_client_<client id> to the AuthGroup.IntegrationDeveloper and AuthGroup.Administrator roles.
Configure authentication in Cloud Foundry:
Login to Cloud foundry tenant and navigate to the Space, Services->Service Marketplace and search for Process Integration. Click Create. Create a new Instance of plan type api. Then create a service key for the same instance.
Once Service key is created, we can note down the client id, secret, URLs for later use.
Now we are ready to create environment file for migration process.
Next, download the compressed file from SAP Note 2937549 and extract it to a local folder on your computer.
In the extracted folder, open the file CPI MIG Settings.postman_environment and configure the parameters with the hostnames from the previous steps:
Now we need to update following values in the environment file.
sourceHost, targetHost, sourceTokenHost, targetToeknHost, sourceOauthId, sourceOauthSecret, targetOauthId, targetOauthSecret.
Save the file.
Now launch Postman and Import the folder by choosing:
File->New->Import Folder and select the unpacked folder.
Make sure you have the correct environment selected so the proper hostnames and credentials are used.
Now open the first collection in postman CPI MIG010 Connects to Tenants and click on run.
Now run CPI MIG020 for readiness check.
We have multiple Postman collection to migrate objects like credentials, Certificates, Variables, data Store, Packages, Oauth to Client credentials, Number range, Value mapping. Now based on our requirement we run these postman collections to migrate the objects from Neo to CF tenant.
To migrate credentials, we will run CPI MIG 070 User Credentials.
All credentials migrated from Neo to CF. Now we need to update passwords manually in Cloud Foundry.
Run MIG080- OAuth credentials
Run CPI MIG030 for variable migration:
Run CPI MIG060 to migrate Custom public certificates:
Run CPI MIG120 to migrate custom content:
There is a field in environment file “key”: “migratePackages”, if we want to migrate all the custom packages then we can leave this field value empty, else we can specify the package IDs to be migrated.
We migrated successfully 3 packages which contains multiple Integration Flows from Neo to CF.
Once we migrate the Integration Flows to cloud foundry environment, we need to configure them and deploy them manually. After deployment we need to make a note of endpoints and share with the system that call Cloud Integration. We need to update the firewalls or IP address which are whitelisted in Neo environment to Cloud Foundry.
Reference:
https://me.sap.com/notes/3351844
Migrating SAP Cloud Integration to SAP Integration Suite | SAP Help Portal
Thanks & Regards,
Nisha Shrivansh
Dear Integration Experts,As we are aware that SAP Neo is going to be sunset on December 31, 2028, and there are many projects which are running on Neo and needs to be migrated to Multicloud environment or Cloud Foundry. I am writing this blog based on my real time experience about migration.The multi-cloud foundation has become the strategic focus for SAP BTP because of its significant benefits as compared with the Neo environment, including its principles of openness and freedom of choice in terms of support for multiple infrastructure providers, data centers, and a wide range of runtimes and programming languages. There are two options to perform the migration based on the requirements. One is SAP provided migration package to migrate the interfaces and other related objects. Other option is to use manual export and import to migrate the objects from Neo to Cloud Foundry.In this blog I will be using SAP provided Migration pack to migrate the objects from Neo environment to Cloud Foundry.Every migration project should have following stages:Discover – In the discovery phase we identify the interfaces, security material, certificates, variables, data store, number ranges, credentials, PGP encryption and other objects which we need to migrate. We prepare the list of interfaces, third parties integrated with SAP, SAP and Non-SAP systems integrated, Cloud or on-premises system integration, Cloud connector configuration etc.Plan & Prepare – In Plan & Prepare phase we check the readiness of Neo and Cloud Foundry. In Neo environment we should have all artifacts saved in version as a prerequisite. In draft mode automatic migration will not work. We should communicate with third parties connected about the migration plan and inform them about the endpoint changes required. We prepare the target or Cloud Foundry tenant.Migration – In this step we perform the actual migration process from neo to Cloud foundry. There are certain steps required to prepare for the migration process automatically which I will discuss later.Validation- Once we complete the migration process, we need to validate. We need to raise the ticket to SAP to validate the migration. Also, we can test the simple iflow as a part of pilot and validate the same.In this blog I will explain step by step process to migrate from Neo to CF environment using SAP provided Migration pack.Prerequisites:Provision and setup SAP BTP Integration Suite Cloud Foundry environment.Create and Instances for both plan Integration flow as well as API.Create Service key for both the plan, which we will need for authentication purpose.Assign proper roles to user who is performing migration in Neo as well as in CF tenant.Postman should be installed.Download the compressed file available in SAP note 2937549, This file contains postman collection for migration.Migration Process:We perform the migration process by running several Postman requests. To execute these requests, we can use a set of Postman collections predefined by SAP. First, we need to prepare the environment file. In order to create an environment file, we should setup Oauth authentication in Neo and CF.Configure Oauth Authentication in Neo environment:Set Up an Oauth in both NEO (for NEO make sure you generate Oauth on “tmn” node ) and CF (For CF make sure the plan selected is “api” )Login to BTP Cockpit and Neo subaccount. Goto Securityà Oauth, click on Register new client.Note down the client ID and Secret, this will be used as user id and password in migration.Using the client ID from the previous step, navigate to Security->Authorizations and assign the user oauth_client_<client id> to the AuthGroup.IntegrationDeveloper and AuthGroup.Administrator roles. Configure authentication in Cloud Foundry:Login to Cloud foundry tenant and navigate to the Space, Services->Service Marketplace and search for Process Integration. Click Create. Create a new Instance of plan type api. Then create a service key for the same instance.Once Service key is created, we can note down the client id, secret, URLs for later use.Now we are ready to create environment file for migration process.Next, download the compressed file from SAP Note 2937549 and extract it to a local folder on your computer.In the extracted folder, open the file CPI MIG Settings.postman_environment and configure the parameters with the hostnames from the previous steps:Now we need to update following values in the environment file.sourceHost, targetHost, sourceTokenHost, targetToeknHost, sourceOauthId, sourceOauthSecret, targetOauthId, targetOauthSecret.Save the file.Now launch Postman and Import the folder by choosing:File->New->Import Folder and select the unpacked folder. Make sure you have the correct environment selected so the proper hostnames and credentials are used.Now open the first collection in postman CPI MIG010 Connects to Tenants and click on run.Now run CPI MIG020 for readiness check.We have multiple Postman collection to migrate objects like credentials, Certificates, Variables, data Store, Packages, Oauth to Client credentials, Number range, Value mapping. Now based on our requirement we run these postman collections to migrate the objects from Neo to CF tenant.To migrate credentials, we will run CPI MIG 070 User Credentials.All credentials migrated from Neo to CF. Now we need to update passwords manually in Cloud Foundry.Run MIG080- OAuth credentialsRun CPI MIG030 for variable migration:Run CPI MIG060 to migrate Custom public certificates:Run CPI MIG120 to migrate custom content: There is a field in environment file “key”: “migratePackages”, if we want to migrate all the custom packages then we can leave this field value empty, else we can specify the package IDs to be migrated.We migrated successfully 3 packages which contains multiple Integration Flows from Neo to CF.Once we migrate the Integration Flows to cloud foundry environment, we need to configure them and deploy them manually. After deployment we need to make a note of endpoints and share with the system that call Cloud Integration. We need to update the firewalls or IP address which are whitelisted in Neo environment to Cloud Foundry. Reference:https://me.sap.com/notes/33518442937549 – SAP Cloud Integration for process services: Content Migration from Neo Environment to Multi-Cloud Foundation – SAP for MeMigrating SAP Cloud Integration to SAP Integration Suite | SAP Help Portal Thanks & Regards,Nisha Shrivansh Read More Technology Blogs by Members articles
#SAP
#SAPTechnologyblog
| UCI Enduro World Cup Practice