Akamai Connector for Salesforce Commerce Cloud

Suggest Edits

If you’re a customer of both Salesforce Commerce Cloud and Akamai, with the Akamai Connector for Salesforce Commerce Cloud you can:

Maintain your existing Akamai delivery service, communicating directly with Salesforce Commerce Cloud.
Tailor your site acceleration and protection features based on your company’s unique requirements.
Take advantage of additional Akamai products.

Implementation

Open a Salesforce support ticket to begin the Akamai Connector integration.
Once Salesforce confirms that their setup tasks are complete, open Property Manager.
In Property Manager, select the property and rule you want to add the Connector behavior to.
Add and set up the Akamai Connector for Salesforce Commerce Cloud behavior:

Field	Action
Enable	Set to On to enable the Connector for this property.
Salesforce Connector ID	Enter the ID provided by Salesforce Commerce Cloud. When entering the ID, make sure it starts with the correct instance for your implementation. The instance can either be production or development (sandbox). For example, this ID would be for a development instance of Salesforce Commerce Cloud: `development-urn.example.salesforce-example_name`.
Type of Salesforce Origin	Select whether to use a default or a custom Salesforce origin with the Connector. The default is the Host header value from the incoming request.
Custom Salesforce Origin	If using a custom origin, enter the hostname or IP address of the custom Salesforce origin.
Type of Salesforce Host Header	Enter the hostname or IP address of the custom Salesforce host header. The default is the Host header value from the incoming request.
Custom Salesforce Host Header	If using a custom host header, enter the hostname or IP address of the custom Salesforce host header.
Override Salesforce Origin Cache Key	Enable to override the forwarding origin’s cache key.

Save your changes to the rule.
Activate the property version.
If you generate dynamic content on your Salesforce Commerce Cloud Origin, review Custom Client IP header Considerations.
Review purge considerations.

Custom Client IP Header Considerations

If you generate dynamic content on your Salesforce Commerce Cloud Origin, you may need to complete a few extra steps to get the Connector to work.

In the Salesforce Commerce Cloud Business Manager, review your Customer Content Delivery Network Settings.
Specify which HTTP request header contains the client IP address.

If you enter True-Client-IP, Business Manager displays a warning that is safe to ignore.

If the value of the Client IP Header field is not True-Client-IP, continue with this procedure. By default, the Connector sends the True-Client-IP header to Salesforce Commerce Cloud.
In Property Manager, add the Modify Incoming Request Header behavior to the property containing your Connector settings.
In the Modify Incoming Request Header behavior:
- Add the name of your custom client IP header.
- Set the header value to the AK_CLIENT_IP system variable for Property Manager: {{builtin.AK_CLIENT_IP}}.
Save your changes and test them before activating the updated property version to production.

Purging Cache for the Connector

When the Connector is in use, Salesforce caches objects from your Salesforce Commerce Cloud origins within their configurations. Given this, Salesforce needs to purge your objects from their cache on your behalf. If you run into issues purging when using the Connector, contact your Salesforce representative.

However, if either Image Manager or Dynamic Page Caching is enabled on the same property as the Connector, Salesforce first has to purge the content on their configurations and inform you that the purge is complete. You'll then have to purge the cache for these products manually on the Akamai platform. To purge the derivative images and pages, you can use either Fast Purge or the Content Control Utility. Issues encountered with purging in these cases may require assistance from both Salesforce and Akamai, so contact Akamai technical support for further guidance.

Updated almost 3 years ago