Migrate Site Traffic
Configure traffic migration to move traffic over to eCDN
-
Pre-validate the hostname if you want to. This step is required when the following
conditions apply:
- You want to avoid downtime when cutting traffic over to eCDN
- You want to stack a third-party CDN in front of eCDN, for example, Akamai
- Eample TXT validation record:
_cf-custom-hostname.stg.mystore.com. IN TXT 3adc7a39-12d7-4baf-be1b-c5ea5295181b
If Commerce Cloud Engineering completed the eCDN configurations, they provide you the TXT validation record.
IMPORTANT: Submit validation records as soon as possible. After the configurations are created, automated validation checks are performed up to 4 hours apart for 7 days. If you donβt complete the validation within 7 days, you can request Commerce Cloud Engineering to manually restart the validation checks.
-
Send traffic directly to eCDN by updating DNS to the CNAME values.
The CNAME target uses this format:
commcloud.<zone_name>
.Example CNAME record:stg.mystore.com. IN CNAME commcloud.stg-abcd-mystore-com.cc-ecdn.net.
Note: If you donβt pre-validate the hostname, pointing traffic directly to the eCDN serves as validation. This approach results in downtime for the period between when DNS is updated and the next validation check. -
(Optional) Stack a third-party eCDN. This step requires a validated host name.
Ensure that the connections to eCDN use SNI. SNI is required for eCDN configurations.
- On Akamai, SNI support for upstream connections is disabled by default. Refer to the Akamai documentation on configuring Origin Server behavior. The SNI TLS Extension must be enabled.
- For all other CDNs, work with the CDN provider to determine how to enable SNI to the origin if itβs not enabled by default. For guidance on suggested Business Manager settings, see Configure an External CDN or Third-Party Proxy. Use the target value from the provided CNAME as the origin server.
-
(Optional) Delete the TXT validation records.
Before you delete the records, confirm that the host name is validated and that traffic is flowing through eCDN.
Infocenter Retirement: On June 30, 2023, the Infocenter was retired, and documentation currently hosted on the Infocenter will be published to Salesforce Help, Commerce Cloud Developer Center, and Salesforce B2C Commerce Developer Documentation Resources. For more information, see the release note.