Seeburger AS2 Message IDs missing

[shweta_walaskar2]

Hi,

We have a scenario where we are using AS2 connection with a partner.

Now the problem is,in case,they send something to us,when we double click the message in Seeburger monitor,we cannot see the original Message ID in the pop-up.

On the other hand,if we send something to them,we can see the original Message ID but not the MDN message ID.

However,we can see both Message IDs in trace and log files.

Can anybody please let me know what could be the reason for this.

Thanks.

Best Regards,

Shweta

[former_member181962 · Accepted solution]

Hi Shweta,

I assume you are talking about messages in seeburger workbench.

I think it is normal behavior.

When you send a document, you would not have the MDN unless you enable Message Disposition in your AS2 adapter(There is a checkbox). An MDN as you might know, is a Technical Acknowledgement as AS2 level. So, you will not see the MDNs message ID as and when you send the message.

Do not confuse the message ID in your Integration Server with the IDs in seeburger.

Both can be different.

Regards,

Ravi Kanth Talagana

[shweta_walaskar2 · Accepted solution]

Hi Ravi,

Yes,I am talking about Messages in Seeburger Workbench.

This is not a normal behaviour.

We can see these Message IDs and MDN IDs in all our scenarios except this.

So I would like to know what could be different with this partner.

Thanks.

Regards,

Shweta

[Former Member · Accepted solution]

Let's assume you are using 1.7x of SEEBURGER AS2 adapter.

When sending a message (receiver channel) with the as2 adapter, the first field of the details view called Message ID is the external AS2 Message ID of the message. The second field (Correlation ID) is the internal XI Message ID of the message.

Maybe you should check whether the other "working" scenarios are using different adapters ?

[shweta_walaskar2 · Accepted solution]

Hi,

These are the details when I double click in the message from this partner which opens a pop-up in Seeburger Workbench (When we send to them)

Message ID <211979426512738426691240383808269.SEEBURGER.abcadm@111.22.333.444>

Sender AS2 ID {our AS2 ID}

Receiver AS2 ID {partner's AS2 ID}

State All requested reports are OK

Status Description Correlation successful.

Timestamp 04/22/2009 09:03:28

Content Type application/xml

MIC T/DxDemZCwYlHlaVpcvZYX8YP3Q=

Message Subject Test Subject

Receipt requested sync

Encrypted

Direction SENT

Compressed

Signed

Receipt (MDN) details

Type sync

MDN Message ID * Partner ID {partner AS2 ID} Payload State ok Payload State Details MDN Timestamp 04/22/2009 09:03:32 Own ID {our AS2 ID} When they send to us: Message ID *

Sender AS2 ID {their AS2 ID}

Receiver AS2 ID {our AS2 ID}

State All requested reports are OK

Status Description Correlation successful.

Timestamp 04/22/2009 09:03:28

Content Type application/xml

MIC T/DxDemZCwYlHlaVpcvZYX8YP3Q=

Message Subject Test Subject

Receipt requested sync

Encrypted

Direction SENT

Compressed

Signed

Receipt (MDN) details

Type sync

MDN Message ID

Partner ID {our AS2 ID}

Payload State ok

Payload State Details

MDN Timestamp 04/22/2009 09:03:32

Own ID {their AS2 ID}

This is the message from a working scenario:

Message ID <211979426512738426691240383808269.SEEBURGER.abcadm@111.22.333.444>

Sender AS2 ID {our AS2 ID}

Receiver AS2 ID {partner's AS2 ID}

State All requested reports are OK

Status Description Correlation successful.

Timestamp 04/22/2009 09:03:28

Content Type application/xml

MIC T/DxDemZCwYlHlaVpcvZYX8YP3Q=

Message Subject Test Subject

Receipt requested sync

Encrypted

Direction SENT

Compressed

Signed

Receipt (MDN) details

Type sync

MDN Message ID 3fbd8f7a-a007-443a-95f3-3d3748447c46@abc-def

Partner ID {partner AS2 ID}

Payload State ok

Payload State Details

MDN Timestamp 04/22/2009 09:03:32

Own ID {our AS2 ID}

You can see both message IDs are there.

I hope I could explain in a better way now.

Regards,

Shweta

[shweta_walaskar2 · Accepted solution]

Hi,

We are using the same adapters in working scenarios too.

It is Seeburger AS2 1.7.

Regards,

Shweta

[former_member181962 · Accepted solution]

Did you check in manual u201CSEEBURGER Message Monitor for SAP XIu201D ?

Usually you will get this when you install seeburger in your system

Ravi

[shweta_walaskar2 · Accepted solution]

Hi Ravi,

Yes,we have done the settings as per this manual and it works fine for other scenarios only not for this scenario.

Thanks.

Best Regards,

Shweta

[shweta_walaskar2 · Accepted solution]

Hi,

Our partner has provided us the trace files at their end and we can see the message IDs in them.

What could be different with this partner that their message IDs are not visible in Seeburger Workbench?

Any idea?

Thanks.

Regards,

Shweta

[prateek · Accepted solution]

Could this be possible that you are trying to check the messageIDs for some old message (older than say 7 days) which could have been deleted. For for other scenarios you are checking some current messages.

Regards,

Prateek

[shweta_walaskar2 · Accepted solution]

Hi Prateek,

Sorry,but we don't have this possibility too as I cant see the message ID from this partner even for today's message.

I have analysed a number of messages from different partners and found that we have this problem sometimes with other partners too.

I forgot to mention,in case of original message ID,I cannot see it against Message ID in the pop up ,but this is visible as the header of that pop-up window.

So I checked message IDs appearing on the window headers and noticed a strange thing.

Whenever, a message ID starts with <{an alphabet}.... it is missing. ex <ASTEST123...

But if it starts with <{a numeric value}.... it is present. ex <1232...

Is there a rule that message ID should start with a number?If yes,how can we handle this situation.

SMIME encoding in Sender Communication channel???

Please let me know.

Thanks.

Regards,

Shweta

[shweta_walaskar2 · Accepted solution]

Hi All,

Can anyone please help in this?

Thanks.

Regards,

Shweta

[shweta_walaskar2]

Hello,

As I mentioned:

"I forgot to mention,in case of original message ID,I cannot see it against Message ID in the pop up ,but this is visible as the header of that pop-up window."

We could find a workaround to this,in the pop-up where message ID is not displayed,we can do a view source and message ID can be copied from there.

Thanks a lot to all who have helped in this.

Regards,

Shweta