3631192 - SuccessFactors DC23 to DC82 Migration – Standard Integration Task

To comply with upcoming regulatory changes in KSA, we will be migrating our DC23 Data Center, separating Public and Private Cloud solutions.

A new data center (DC82) will be created for Public Cloud customers with new URLs for BizX, API, SFTP, and Mail endpoints.

Post-Migration Data Center Details:

After the migration is complete, our data center setup will be as follows:

• DC82: For Public Cloud customers, receiving new URLs for BizX, API, SFTP, and Mail endpoints.
• DC23: For Private Cloud customers, keeping the already existing URLs/endpoints.

Impact on Your Services:

• Private Cloud customers: No changes are planned, and no action is required from your side.
• Public Cloud customers: You will be affected by this migration. Please refer to the required actions outlined in this KBA to ensure a smooth transition.

Image/data in this KBA is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental.

SAP SuccessFactors HCM Suite

Migrated URLs

API: search for "DC82" in KBA 2215682.

These are the endpoints that will be migrated, so consider them when updating the configuration of the solutions being presented below.

Standard Integrations on Boomi

1 - Canceling Schedules

Prior to the company instance migration, you need to cancel the schedules of all the standard integrations.

2 - Updating the Configuration of Standard Integrations

Post the company instance migration, review the configuration of the standard integrations (as described below) and schedule them again:

1. Navigate to Boomi > Manage > Runtime Management > Select the desired environment.
2. Navigate to Environment Extensions > Choose the desired integration.
3. Configure the new endpoints to the SF Instance and review the other configurations as well. 
   • In case the data center API URL is not found in the Endpoint dropdown, then choose the option as 'Other' and then make use of the 'Other Endpoint' option to specify it manually.
     <MISSING CONTENT: SPECIFY HERE WHAT WOULD BE THE API URL TO BE INSERTED MANUALLY>
     
      
     

Note: make sure the new data center atom is available and added to the desired environment so that the executions can happen with this new atom.

3 - Updating the Last Execution Timestamp

Since there will be an atom change, you'll have to provide the last execution timestamp values from the old atom to the new atom. Do that once the schedules are restored, so the integration fetches data from the same referenced time and avoid any duplicate data or even data loss. Follow these steps:

1. 1. In the old Atom, go to Deployed Processes > Select the Desired Process > Edit Process Properties 
   2. Copy the value of this persisted timestamp 
   3. New Atom > Deployed Processes > Select the desired process > Edit Process Properties > Create the property with same name and paste the earlier copied value
   4. Save this configuration

4 - Connectivity Issues

For any Boomi jobs post migration, there are possibilities of connectivity issues with:

• External SFTP servers
• SMTP servers
• HTTP endpoints

In order to deal with such issues, the allowlisting of the Boomi's Atom IP's will be required on the target side. Additionally, an allowlisting will also be required on Boomi side for allowing connection to the external IP addresses. For more details please refer to the KBA 2341429.

Standard Integrations on SAP Cloud Integration (SCI)

1 - Canceling Schedules

Prior to the company instance migration, cancel the schedules of all the standard integrations.

2 - Updating the Configuration of Standard Integrations

Post the company instance migration, review the configuration of the standard integrations and schedule them again. 

1. Create a new SuccessFactors credential in Security Material and deploy it.
2. Provide this credential name in the receivers that connect to SuccessFactors.
3. Update the new SF DC API URL.
   Note: refer to the "DC82" URL mentioned in KBA 2215682.
   
   

Integration Center and Business Scenarios

1 - SuccessFactors SFTPs

If you are using DC23 specific SFTP, then you need to update it in "Destination Settings" (if it's an outbound integration) or "Source Settings" (if it's an inbound integration).

This is applicable to both Integration Center jobs and Business Scenarios.

2 - Connectivity Issues

For any Integration Center job post migration, there are possibilities of connectivity issues with:

• External SFTP servers
• SMTP servers
• HTTP endpoints

In order to deal with such issues, the allowlisting of SF DC IP's will be required on the target side. More details in KBA 2395508.

Additionally, an allowlisting will also be required on SF side for allowing connection to the external IP addresses. This allowlisting is done by SAP Support, refer to more details in KBA 3122406.

migration, standard integration, dc82, dc23, public cloud, private cloud, ksa, boomi, cpi, integration center , KBA , LOD-SF-INT-API , API & Adhoc API Framework , Product Enhancement