Assigning the IBM Marketing Cloud Transact XML message type to its transport method

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


Procedure

  1. Open the Administration Console.

  2. Select Site on the Administration Console Site/Store Selection page. Or, select Store and the store name to configure the transport at the store level.

  3. Click Configuration > Message Types.

  4. 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.

  5. Enter the transport configuration values in the appropriate fields. In general, a message severity of 0.0 is recommended.

  6. Select the IBM Marketing Cloud Transact XML transport.

  7. Select the IBM Marketing Cloud Transact XML device format.

  8. Click Next to configure the transport parameters for the specified message type.

  9. Enter the values to be used by the transport method:

    Parameter Value
    Client ID The client ID that is provided by IBM Marketing Cloud Transact XML when you configure IBM Marketing Cloud Transact XML to work with WebSphere Commerce.
    Client Secret The client secret that is provided by IBM Marketing Cloud Transact XML when you configure IBM Marketing Cloud Transact XML to work with WebSphere Commerce.
    OAuth URL The OAuth URL assigned to you by IBM Marketing Cloud Transact XML. The default value is https://apiX.silverpop.com/oauth/token, where X is the pod number assigned to you by IBM Marketing Cloud Transact XML.

    For example, if we are assigned the following URL, http://engage2.silverpop.com, the pod number 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 Marketing Cloud Transact XML when you configure IBM Marketing Cloud Transact XML to work with WebSphere Commerce.
    Transact XML URL The Transact XML URL assigned to you by IBM Marketing Cloud Transact XML. The default value is https://transactX.silverpop.com/XTMail, where X is the pod number assigned to you by IBM Marketing Cloud Transact XML.

    For example, if we are assigned the following URL, http://engage2.silverpop.com, the pod number assigned to you is 2. Therefore, your Transact XML URL value is https://transact2.silverpop.com/XTMail.

    Campaign ID The unique ID assigned by IBM Marketing Cloud Transact XML when creating 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.

  10. 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, we must update the parameters for all the message types.

Previous topic: Creating transactional email templates in IBM Marketing Cloud Transact XML
Next topic: Creating email message JSP files