Seeburger AS2 Adapter: Receiving multiple messages

[Former Member]

Hi guys,

I'm having some trouble using AS2 Adapter for receiving multiple messages. The problem is really similar to Peter's problem.

I have it configured for one scenario and it's working fine. The problem is when I'm trying to receive other messages for the same Party but different services. Meaning, I've one Party(example BMW) and several services (BMW_DE, BMW_USA, etc). I'm able to receive messages from service BMW_DE but when configuring BMW_USA I'm getting HTTP 403 Forbidden.

This error may have different reasons:

a) You or your partner has entered an incorrect AS2 ID for one of the involved parties.

b) A valid sender agreement is missing.

c) There are more then one AS2 sender agreements with the same sender AND receiver party.

d) The corresponding inbound channel is set to inactive.

And the problem is that there are two sender agreements. Although the services are different, XI is not able to find the correct sender agreement to be used. After deleting the second second agreement, I'm able to send the respective message....

Can anyone give me a hint on how to solve this problem?

[Former Member · Accepted solution]

Hi,

this is done by different AS2 subjects. The sender agreement is selected based on this. So create separate AS2 receiver adapters for every message you need and put there different message subjects.

So if you'll have 3 AS2 receiver channels with subjects:

MessageType1_DE

MessageType1_US

*

the AS2 adapter will work like following:

first it tries to find an exact message subject, if it is found, message is "assigned" to this sender agreement. If no exact message matches the subject, then wildcards are used. (this mechanism is described in the Seeburger AS2 guide).

If you are getting 403 HTTP code, there may be also problem with authentication certificates.

Another problem may be, you don't have configured AS2 receiver channel for current subject.

Does this help you? Or you meant it another way?

Peter

p.s. check the answer above my post, Vardharajan's right

Edited by: Peter Jarunek on May 19, 2008 2:11 PM

[Former Member · Accepted solution]

Hi Vardharajan,

Thanks for your advice.

Answering your question, yes they both have the same ID's. They're BusinessServices which belong to a thirdParty which has the same AS2ID. The reason is due to different bpm's with different conditions.

Hi Peter,

Thanks for your advice.

Excellent tip!!! It works great for receiving multiple messages.

By the way, looking the AS2 manual and after your answer, excuse my ignorance but what's a wildcard in the as2 message subject context? What is the purpose of a wildcard?

Thanks for your quick replies!!!

Points awarded for both.

[Former Member · Accepted solution]

Hi,

wildcards in AS2 context are the same as wildcards in any other context

Wildcards are "special" characters, which can be replaced by other characters. Especially in AS2 "*" (asterisk) is used.

Example: you want to handle MessageType1_DE and MessageType1_US messages by the same message processing. So you create an AS2 receiver communication channel with message subject MessageType1_* . And all messages with subject MessageType1_US, MessageType1_DE or MessageType1_anything will be processed by the same message processing.

Is it clear now?

Peter

[Former Member · Accepted solution]

One more example - when you will have some exact message subjects for all of the AS2 CCs, and some sender will try to send you a message which doesn't match any of them, you will never know, that somebody has tried to send a message 2 u! So I for example use 1 receiver CC with message subject "*". This will ensure, that I'll see all the AS2 messages sent to our system.

Peter

[Former Member · Accepted solution]

Hi Peter,

Excellent example and perfect explanation

Thanks Peter.

[Former Member]

Hi,

Can u tell me Whether BMW_DE and BMW_USA both have same AS2ID. If both have the same AS2 id,then why do u want to create two different sender agreements. Can u elobrate the scenario.

While receiving AS2 message, if the AS2ID's are not matching, then you will get this errror.

With Regards

K.Varadharajan