The latest Ariba Release, 2102, brought up the ability to switch the CIG Datacenter from Europe to the USA for buyers based in the Americas only. Please refer to the official documentation for all the details, check this link and this one for all details including prerequisites and restrictions.
The objective of this blog post is to provide the steps necessary to get the CIG datacenter migrated and up and running for transactions/master data in little time.
Please note that is highly recommended to plan some downtime ahead of time when moving the Production instance since all configurations and mappings in CIG have to be manually redone. Also as stated no the documentation, move your TEST account before moving Production.
Before we start to see the steps necessary, here are some important considerations before moving to the US Datacenter:
- Moving to US datacenter is NOT mandatory for existing customers. Do it only if there’s a hard requirement of data location. This switch is one-time only, there’s no way to revert the Datacenter back to Europe.
- Make sure you capture all configurations from the CIG portal, nothing will be migrated to the new CIG. If you have lots of custom mappings and custom routings be aware that everything will be lost.
- In order to be able to move to the US DC you have to update to the latest CIG addon release ARBCI1 SP012.
All steps below were done from the Ariba Network buyer account, but the switching process can be initiated from one of the Ariba solutions as well. If Ariba B&I/Sourcing are in scope please raise an SR requesting feature PL-26167 to be enabled. Also, there’s no middleware involved, only the standard SAP Cloud Connector for inbound transactions.
- Go to the CIG configuration area under the Administration section in the AN, you will see that there’s a new checkbox that will allow. Select it and hit Save.
2. Confirm the next screen – please note the migration duration is usually very fast, a few minutes at most, but it can take a couple of hours depending on the day.
3. As soon as the migration is completed you will see the new Datacenter is already available. Note: a new P-user will be created for this Datacenter. Please check the admin email for instructions and password setup.
4. Go to the CIG portal and download the new public certificate for the US datacenter under the resources section.
5. Now a little deviation before we import the certificate into SAP. Go to the cloud connector connected to the European CIG and replace all European sub-accounts with the US sub-accounts. You find them here. Also perform all the other steps necessary in the Cloud Connector as mentioned on the same previous link.
6. Now in SAP, import the new US certificate (STRUST) and then restart the ICM service(SMICM).
7. Change the RFC destination URL and enter the new P-user/password.
Target Host: testacig-us.ariba.com for test and acig-us.ariba.com for production
8. Click on Connection Test and if you get 500 it means it is successful.
9. Go to SPRO and execute
Fill in all the relevant fields relevant to your landscape and select the US Datacenter under the Data Center section.
10. Go to SPRO and execute
Check all transactions in scope and set the credentials and other relevant fields and select the US Datacenter.
Please note if there are other Ariba solutions in scope the same step has to be done for each solution on SPRO.
This is the last step needed in SAP.
11. Go to the CIG portal and recreate the projects, setup the cross references, custom mappings and custom routing as needed. Once again, there’s no migration tool for the time being.
12. Test the connection from the CIG portal and you will get a green light if everything is fine.
13. Lastly, run a regression test to check if everything is working as before.
The CIG US datacenter was made available last release, 2102, so now any buyer with an address based in the American continent will be able to use it. New customers will be automatically pushed to the US datacenter whereas old customers will have the option to migrate to the new datacenter. However an important point to take into consideration is that no migration tool is available so if the customer has a heavy customized CIG set up on the portal side, the migration will be very time-consuming.