Assigning the IBM Watson Campaign Automation message type to its transport method

After you create an email template in IBM Watson Campaign Automation, you can assign the template to a message type to be sent by the IBM Watson Campaign Automation transport method. Complete this task for each IBM Watson Campaign Automation email template that you create so that you can send emails for each specific transaction. That is, ensure that a corresponding IBM Watson Campaign Automation message type and transport method exists in the WebSphere Commerce Administration Console for each existing IBM Watson Campaign Automation email template.

Procedure

Open the Administration Console.
Select Site on the Administration Console Site/Store Selection page.
Or, select Store and your store name to configure the transport at the store level.
Click Configuration > Message Types.
Select the check box next to the message type to which the transport is to be assigned from the Message Type list and click Change.
For example, Message for a received order.

The Change Message Transport Assignment page displays.
Enter the transport configuration values in the appropriate fields.
In general, a message severity of 0.0 is recommended.
Select the IBM Watson Campaign Automation transport.
Select the IBM Watson Campaign Automation device format.
Click Next to configure the transport parameters for the specified message type.

Enter the values to be used by the transport method:

Parameter	Value
Client ID	The client ID that is provided by IBM Watson Campaign Automation when you configure IBM Watson Campaign Automation to work with WebSphere Commerce.
Client Secret	The client secret that is provided by IBM Watson Campaign Automation when you configure IBM Watson Campaign Automation to work with WebSphere Commerce.
OAuth URL	The OAuth URL that is assigned to you by IBM Watson Campaign Automation. The default value is https://api`X`.silverpop.com/oauth/token, where `X` is the pod number assigned to you by IBM Watson Campaign Automation. For example, if you are assigned the following URL, http://engage2.silverpop.com, the pod number that is assigned to you is 2. Therefore, your OAuth URL value is https://api2.silverpop.com/oauth/token.
Refresh Token	The refresh token that is provided by email from IBM Watson Campaign Automation when you configure IBM Watson Campaign Automation to work with WebSphere Commerce.
Transact XML URL	The Transact XML URL that is assigned to you by IBM Watson Campaign Automation. The default value is https://transact`X`.silverpop.com/XTMail, where `X` is the pod number assigned to you by IBM Watson Campaign Automation. For example, if you are assigned the following URL, http://engage2.silverpop.com, the pod number that is assigned to you is 2. Therefore, your Transact XML URL value is https://transact2.silverpop.com/XTMail.
Campaign ID	The unique ID that is assigned by IBM Watson Campaign Automation when you create the transactional email group. This value contains the email template for the transactional email. If you do not specify the campaign ID value in this field, it must instead be specified in the message JSP file. The campaign ID is specified in the message JSP file within the `<CAMPAIGN_ID>` XML element. To use the specified campaign ID from this field, specify the `[campaignId]` variable in the message JSP file. For example, `<CAMPAIGN_ID>[campaignId]</CAMPAIGN_ID>`. To specify the campaign ID in the message JSP file, enter the campaign ID value. For example, `<CAMPAIGN_ID>80108123</CAMPAIGN_ID>`.
Recipient	The recipient email address. Leave this field empty. The recipient is dynamically set when the email is sent.
Subject	The email subject line. Leave this field empty. The subject is dynamically set when the email is sent.

Click Finish.
The Message Type Configuration page displays, and the Transport Status column is set to Active.
Important: After you assign a message type to a transport method for a site or store, the message profile that is created is based on the initial transport and has its own record in the database. If you change the initial transport, you must update the parameters for all the message types.