Home
Administrator Guides
Transactional Message Administrator Guide
Integration with the Deliver transactional message service
The Deliver Transactional messaging System (TMS) is a web service hosted as part of HCL Unica hosted services. Application developers must work with digital marketers in your organization to create the client applications required to integrate your corporate transactional systems with the Deliver TMS. These client applications initiate each transactional message by making a SOAP request to the Deliver TMS over an HTTPS connection.
Connection to the Deliver TMS
You must design the local transactional message client to automatically connect to the Unica data center assigned to your hosted message account. The client must be able to provide the appropriate authentication credentials as part of the web service request.
WSDL for Deliver transactional email
Unica provides two versions of the WSDL for building applications that access the Deliver TMS. The choice of WSDL depends on if you plan to use email attachments and on how the client application provides access credentia. WSDL describes how to construct an interface to the Deliver TMS that supports providing email attachments. It also describes how to specify access credentials as parameters in the web service request, instead of modifying the SOAP header.

Administrator Guides
- Startup and Administrator Guide
- Transactional Message Administrator Guide
  - About Deliver and transactional message
    A transactional message is a single message sent in response to a specific, predetermined transaction detected in your business systems. Unica provides the Deliver Transactional messaging Service (TMS) as a hosted web service to process transactional messages. Digital marketers work with application developers to integrate corporate transaction management systems with the Deliver TMS.
  - Integration with the Deliver transactional message service
    The Deliver Transactional messaging System (TMS) is a web service hosted as part of HCL Unica hosted services. Application developers must work with digital marketers in your organization to create the client applications required to integrate your corporate transactional systems with the Deliver TMS. These client applications initiate each transactional message by making a SOAP request to the Deliver TMS over an HTTPS connection.
    - Identification of transaction events
      Application developers must design the local transactional message client to interact with transaction monitoring systems used by your organization. The client must take transaction notifications as input and distinguish the type of transaction event that the transaction management system is reporting.
    - Access to recipient data
      To personalize transactional messages, the local transactional message client must access business systems and databases that can provide recipient-specific data used in transactional message.
    - Connection to the Deliver TMS
      You must design the local transactional message client to automatically connect to the Unica data center assigned to your hosted message account. The client must be able to provide the appropriate authentication credentials as part of the web service request.
      - Deliver TMS addresses
        Unica has established message domains reserved for processing transactional messages. You must configure your transactional message applications to request access to HCL Unica using the correct domain. The domain you use depends on which Unica data center processes your request.
      - WSDL for Deliver transactional email
        Unica provides two versions of the WSDL for building applications that access the Deliver TMS. The choice of WSDL depends on if you plan to use email attachments and on how the client application provides access credentia. WSDL describes how to construct an interface to the Deliver TMS that supports providing email attachments. It also describes how to specify access credentials as parameters in the web service request, instead of modifying the SOAP header.
        Second-generation WSDL
        The second-generation WSDL describes how to construct an interface to the Deliver TMS that supports providing email attachments. This WSDL also describes how to specify access credentials as parameters in the web service request, instead of modifying the SOAP header.
      - About providing authentication credentials for transactional message
        The local transactional message client must be able to provide the authentication credentials required to connect to the Deliver TMS automatically.
    - Attachments in transactional email requests
      The Deliver TMS supports attaching one or more files to a transactional email message. The web services request must contain the file contents and information that describes each file.
    - Construction of the transactional email request
      To access the Deliver TMS, the transactional email client must be able to provide credentials to connect to the TMS. It must also provide mailing and message information as part of the web service request. Unica provides two versions of a WSDL as a guide to structuring a SOAP request that includes all information required to send a transactional email.
  - Deliver sample TMS client
  - The Deliver Transactional Mailing Service API
    The Deliver Transactional Mailing Service is a web service hosted in HCL Unica. It provides an API that contains one method calledsendMailing.
  - Sample client
    Unica provides sample transactional message clients to guide application developers that create client applications that make web service calls to the Deliver Transactional Messaging Service (TMS). This sample client is based on the second-generation WSDL.
  - About Dynamic Transactional Images
    Dynamic transactional images are images specific to a particular individual that you can include with transactional email messages. Dynamic transactional images are sent as attachments to transactional email but they display as images embedded in the body of the message.
  - Deliver sample TMS client

WSDL for Deliver transactional email

Unica provides two versions of the WSDL for building applications that access the Deliver TMS. The choice of WSDL depends on if you plan to use email attachments and on how the client application provides access credentia. WSDL describes how to construct an interface to the Deliver TMS that supports providing email attachments. It also describes how to specify access credentials as parameters in the web service request, instead of modifying the SOAP header.

The WSDL is available for download from the Unica data center that Unica has instructed you to use for connecting to the Deliver TMS. Construct the download URL as follows:

<URL for connecting to your assigned TMS>/delivertms/services/TMS?wsdl

Unica provides an example of how to create the local transactional email client based on the second-generation WSDL. To view the example, see Sample client

Note: If you have already constructed a transactional email client based on the first-generation WSDL you must recompile the code if you change to a client design based on the second-generation WSDL.

Rate this topic

5 stars 4 stars 3 stars 2 stars 1 star

Comment on this topic.

By clicking this box, you acknowledge that you are NOT a U.S. Federal Government employee or agency, nor are you submitting information with respect to or on behalf of one. HCL provides software and services to U.S. Federal Government customers through its partners immixGroup, Inc. Contact this team at https://hcltechsw.com/resources/us-government-contact. Do not include any personal data in this Comment box.