Setup Procedure

The initial setup and configuration of the integration involves several processes. Use this checklist to ensure that all steps are completed. The Tech Ops team performs some of these steps.

Note: Some pages referenced here are only visible to internal Salesforce users, such as Client Services.

Verify successful deployment of Salesforce B2C Commerce.
Set up the tenant realm:
1. In Order Management Administration, open Utilities > Integration and check the Tenant Pattern.
2. If the first four digits of the tenant pattern match the B2C Commerce instance realm, then the integrated realm is configured and you can proceed. If not, then retrieve the B2C Commerce realm ID and log a ticket with Commerce Cloud Tech Ops to configure the integrated realm. (Contact Support if you do not know the realm ID.) Be sure to allow at least 2 business days for Tech Ops to address your ticket.
(Tech Ops) Add to safelist for outgoing POD addresses on the Order Management server.
Enable the Heartbeat job in Order Management:
1. In Administration, open Utilities > Add-In Jobs.
2. In the search form, select Commerce from the Group dropdown and click Search.
3. To open the job dialog, select the heartbeat job.
4. Check the 'X' icon in the upper right corner of the dialog. If it's red, then the job is suspended. To unsuspend the job, click the icon.
5. Look at the Next Run Date section. Make sure that the Recurring radio button and the Enabled checkbox are selected.
Note: The heartbeat job fails until later in the configuration process.
Install the Account Manager client certificate on all Order Management servers that run Task Manager. In addition, do the following:
- Grant the IIS_IUSER permission to the certificate's private keys.
- Grant the user account that runs Task Manager permission to access the certificate's private keys.
- Note the Certificate Thumbprint. This thumbprint is used when configuring Order Management.
Ensure that the same Account Manager is configured and tested on both the B2C Commerce and Order Management servers and in the Order Management Administration module.
If this implementation is a legacy that uses the Order Management Cartridge in B2C Commerce, disable the order export job in B2C Commerce. See the Migration Procedure topic.
To configure settings in the Digital Integration Provider, perform the following steps:
1. Generate a 2048-bit RSA key and set the Private and Public (base64 encoding) Keys in the provider. The private key includes the RSA header and footer, while the public key does not.
2. To add a B2C Commerce connection, click Add. Configure the connection as follows:
  - Digital Base URL: Enter the base URL for the B2C Commerce instance. This URL is the same one that you would use to make OCAPI calls. The URL must be within the demandware.net domain.
    Note: If you get SSL security exceptions, you can temporarily change the URL to get SSL working. For example, if the URL is a.b.c.demandware.net/s/-, you can change it to a-b-c.demandware.net. When SSL is working, change the URL back to a.b.c.demandware.net/s/-.
  - State: Set to disabled.
  - Accept Orders: Leave this box unselected.
  - Leave all other settings with their default values.
3. To send the configuration data to the B2C Commerce instance and link it with your Order Management instance, click Send Configuration.
  Note: If Apache returns OCIntegrationFault: VersionNotNegotiatedException, it's possible that the heartbeat job hasn't kicked in yet. Wait 10–15 minutes and try again.
When the communication link between B2C Commerce and Order Management is active, the heartbeat job succeeds. It can take up to 15 minutes from when you first send the configuration. Verify that the job is working before proceeding.
In your stage environment, map the shipping methods in B2C Commerce to external shipping method IDs defined in Order Management. Create the map in your stage environment and let the replication process copy the mappings to the production environment. Don't make these changes directly in the production environment. The procedure is as follows:
- In Business manager, select Merchant Tools > Ordering > Shipping Methods.
- To open the details page for that method, select a shipping method ID.
- Select the corresponding Order Management shipping method from the Order Management Shipping Method dropdown.
- Click Apply.
- Repeat the procedure for each shipping method.
  Note: Map all of your virtual and electronic shipping methods (such as the methods used for electronic gift cards), not only physical shipping methods.
Note: The Shipping Methods Map in the Demandware Provider is not used in the new integration. It's only used by the legacy connector.
Configure the Payment Methods Map in the Demandware Provider.
Now it's time to enable the integration:
1. In the B2C Commerce Integration Provider, click the Edit link for the connection that you created in step 9 to open the Edit Connection page.
2. Select the Accept Orders checkbox. The state changes to Active.
3. To activate the integration, click the Send Configuration button.
4. Exit the Edit Connection page. The entry for the connection now shows a check mark in the Accepts Orders column.
In the Demandware Provider, click the Integration Cleanup button. The cleanup finds orders created after the legacy cartridge order export was disabled and before the new integration was enabled and sends them to Order Management.
Enable the order request job in Order Management:
1. In Administration, open Utilities > Add-In Jobs.
2. In the search form, select Commerce from the Group dropdown and click Search.
3. To open the job dialog, select the Request Orders job.
4. Check the 'X' icon in the upper right corner of the dialog. If it's red, then the job is suspended. To unsuspend the job, click the icon.
5. Look at the Next Run Date section. Make sure that the Recurring radio button and the Enabled checkbox are selected.