Transactional messaging (Message Center) is a Campaign module designed for managing triggered messages. Learn more about Transactional messaging in this section.
Understand transactional messaging architecture in this page.
As a Managed Cloud Services user, contact Adobe to install and configure Campaign Transactional messaging in your environment.
To create new users for Message Center execution instances hosted on Adobe Cloud, you need to contact Adobe Customer Care. Message Center users are specific operators that require dedicated permissions to access ‘Real time events’ (nmsRtEvent) folders.
All schema extensions made on the schemas used by Message Center technical workflows on either control or execution instances need to be duplicated on the other instances used by Adobe Campaign transactional messaging module.
When combined with Mobile app channel module, transactional messaging enables you to push transactional messages through notifications on mobile devices.
To send transactional push notifications, you need to perform the following configurations:
Install the Mobile App Channel package onto the control and execution instances.
Check your license agreement before installing a new Campaign built-in package.
Replicate the Mobile application service and the associated mobile applications on the execution instances.
In addition, the event must contain the following elements:
Below is an example of an event configuration to send transactional push notifications:
<SOAP-ENV:Envelope xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"> <SOAP-ENV:Body> <urn:PushEvent> <urn:sessiontoken>mc/</urn:sessiontoken> <urn:domEvent> <rtEvent wishedChannel="41" type="DELIVERY" registrationToken="2cefnefzef758398493srefzefkzq483974"> <mobileApp _operation=”none” uuid="com.adobe.NeoMiles"/> <ctx> <deliveryTime>1:30 PM</deliveryTime> <url>http://www.adobe.com</url> </ctx> </rtEvent> </urn:domEvent> </urn:PushEvent> </SOAP-ENV:Body> </SOAP-ENV:Envelope>
You can adapt the deployment wizard settings to configure how long the data is to be stored in the database.
Event purging is carried out automatically by the Database cleanup technical workflow. This workflow purges the events received and stored on the execution instances and events archived on a control instance.
Use the arrows as appropriate to change the purge settings for the Events (on an execution instance) and Archived events (on a control instance).
You must ensure that the technical workflows on your control and execution instances have been started before deploying any transactional message templates.
These workflows can then be accessed from the Administration > Production > Message Center folder.
On the control instance, you must create one archiving workflow for each Message Center execution instance external account. Click the Create the archiving workflow button to create and start the workflow.
On the execution instance(s), you must start the following technical workflows:
Processing batch events (internal name: batchEventsProcessing ): this workflow lets you break down batch events in a queue before they are linked to a message template.
Processing real time events (internal name: rtEventsProcessing ): this workflow lets you break down real time events in a queue before they are linked to a message template.
Update event status (internal name: updateEventStatus ): this workflow lets you attribute a status to the event.
Possible event statuses are: