Error in AS2 reciever Communication channel

[Former Member]

Hi all,

We are working on Idoc to AS2 scenario using SAP PI 7.1. we have installed the certificates provided by the AS2 partner on the PI system and used them in the Reciever agreement. When trying to test this interface, we are getting the following error in AS2 communication channel:

Message-Verarbeitung fehlgeschlagen. Grund: javax.resource.ResourceException: Fatal exception: javax.resource.ResourceException: SEEBURGER AS2: AS2 Adapter failure # java.lang.Exception: AS2 message composition failed: com.seeburger.ediint.edi.EDIMessageException: EDI message composing failed: signature generation failed: signature generation failed: java.security.NoSuchProviderException: provider BC not found., SEEBURGER AS2: AS2 Adapter failure # java.lang.Exception: AS2 message composition failed: com.seeburger.ediint.edi.EDIMessageException: EDI message composing failed: signature generation failed: signature generation failed: java.security.NoSuchProviderException: provider BC not found.

Can anyone please help us in resolving this?

Regards

Jagruthi

[Former Member]

Hi,

The signing key mentioned in the receiver agreement would be normally your AS2 certificates key rather than your AS2 partners.

Make sure that your certificates are properly loaded and that you have given the names correctly.

Regards

Krish

[Former Member]

Hi all,

This error is resolved.

This was because of incorrect AS2 server address maintained in Channel.

Regards

Jagruthi

[Former Member]

Hi Jagruti,

I am also looking for the same scenarios with Receiver AS2 adapter on PI 7.1

I have noticed that in my AS2 receiver adaper i am not getting AS2 server details instead the conf is different from previous AS2 adapter.

I am getting below options

channel attribute for RTP

Scurity attribute for RTP etc.

can u pls help me whether anything is missing in deployment why I am not getting other optins.

can u also share any conf doc which u hav

chirag

[Former Member]

have a look upon this thread,.. might be some configuration is missing for signing key.

[;