cancel
Showing results for 
Search instead for 
Did you mean: 

Using Seebeurger AS2 and Message-Splitter (Frontend) for non-EDI XML messages

former_member105769
Participant
0 Kudos

All
We are using Seeburger AS2 for Edifact and Tradacoms with no problems.
We now have a requirement to receive non-EDI XML messages using Seeburger AS2, and I would like to use the "Message-Splitter Configuration Frontend" to identify the Sender Agreement with the correct Interface (as there will be different XML documents coming in).

I am using PI7.1 enh.1

I'd like to know if this is possible, and if so:
- How does the Module chain need to look on the Sender AS2 channel
- Can I get away without calling localejbs/CallBicXIRaBean (as the message is already in XML format)
- Which interface should be specified on the Sender Agreement attached to the AS2 Sender channel (for real EDI, we have this set to the functional Ack. )

thanks in advance

SteveB

Accepted Solutions (1)

Accepted Solutions (1)

former_member105769
Participant
0 Kudos

I was able to solve this by writing a module to parse the inbound XML and set the following Dynamic Attribute:

"http://seeburger.com/xi/splitter", "targetChannel"

the value has to be: 'Sender|Mapping|State'.  where:
Sender   = sender as identified by interogating the message
Mapping = any constant, which you choose to enter in the splitter frontend 'Mapping-Name' field
state = 'ACCEPTED'

| = delimiter for the above

Answers (0)