Adobe Campaign Classic: BatchEvents not delivered and processed by MTA

Avatar

Avatar
Level 1
Sergio_Ribeiro_
Level 1

Likes

0 likes

Total Posts

1 post

Correct reply

0 solutions
View profile

Avatar
Level 1
Sergio_Ribeiro_
Level 1

Likes

0 likes

Total Posts

1 post

Correct reply

0 solutions
View profile
Sergio_Ribeiro_
Level 1

27-02-2019

We are having problems sending Transactional PUSH notification BatchEvents when using SOAP calls.

All the messages are Ignored by Delivery (Status #11).

This issue only occours using the BatchEvent Service. For the same Registration token, on the same event and mobileApp it works using rtEvent

It looks like that MTA instance is not processing BatchEvents.

Are we forgetting some config tag on serverConf to make BatchEvents works correctly? Why MTA does't pick up my events?

Example call...

/nl/jsp/soaprouter.jsp

Header:

SOAPAction  ->  nms:batchEvent#PushEvents

Body:

<?xml version="1.0" encoding="UTF-8" ?>

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:urn="urn:nms:batchEvent">

<soapenv:Header/>

<soapenv:Body>

<urn:PushEvents>           

<urn:sessiontoken>mc/</urn:sessiontoken>

<urn:domEventCollection>            

<Events>                  

    <batchEvent wishedChannel="42" origin="sergio" type="evtDemo" registrationToken="eiJusOwM_ZY:APA91...">               

    <mobileApp uuid="E0209B31-8D8B-4D33-9F05-B050EBFA5A44"/>                      

    <ctx>

             <title>myTitle</title>

             <url>http://myurl.com</url>

    </ctx>               

    </batchEvent>    

    <batchEvent wishedChannel="42" origin="sergio" type="evtDemo" registrationToken="eiJusOwM_ZY:APA91...">                

    <mobileApp uuid="E0209B31-8D8B-4D33-9F05-B050EBFA5A44"/>                      

    <ctx>

             <title>anotherTitle</title>

             <url>http://anotherurl.com</url>

    </ctx>               

    </batchEvent>      

</Events>

</urn:domEventCollection>

</urn:PushEvents>

</soapenv:Body>

</soapenv:Envelope>

Accepted Solutions (0)

Answers (0)