Exception caught by adapter framework: No configuration / default adapter specified for EDISeparator

[#1]

Hello Experts,

I am configuring the scenario ( AS2 to EDISeparator and EDISeparator to IDOC ).

Can you please help me with the error below which is from the either the EDISeparator Receiver channel or the EDISeparator Sender channle.

09.06.2014 17:52:18.709	Information	Message is encrypted with 1.3.14.3.2.7 algorithm
09.06.2014 17:52:18.778	Information	AS2 Message is signed with SHA1 (1.3.14.3.2.26) algorithm
09.06.2014 17:52:18.779	Information	AS2 Message message signature is validated, signer ID is X509CertSelector: [ Serial Number: 1624063516 Issuer: CN=Mendelson AS2 TEST,OU=Integration,O=Mendelson,L=Berlin,ST=Unknown,C=GE matchAllSubjectAltNames flag: true ]
09.06.2014 17:52:18.784	Information	AS2 document size is 350 Bytes
09.06.2014 17:52:18.784	Information	Payload charset converted from ISO-8859-15 to ISO-8859-15
09.06.2014 17:52:18.785	Information	B2B EdifactConverterModule : EDI format detected as EANCOM
09.06.2014 17:52:18.785	Information	B2B EdifactConverterModule: Message will be read as ISO-8859-1.
09.06.2014 17:52:18.785	Information	MP: processing local module localejbs/EdifactConverterModule
09.06.2014 17:52:18.785	Information	0}: The module-paramteter "eancom.subversion.prefix" is not set. Using default value "false"
09.06.2014 17:52:18.786	Information	0}: The module-paramteter "eancom..audit" is not set. Using default value "false"
09.06.2014 17:52:18.791	Information	MP: processing local module localejbs/CallSapAdapter
09.06.2014 17:52:18.791	Information	Application attempting to send an XI message asynchronously using connection AS2_http://sap.com/xi/XI/AS2
09.06.2014 17:52:18.792	Information	Trying to put the message into the send queue
09.06.2014 17:52:18.831	Information	Message successfully put into the queue
09.06.2014 17:52:18.831	Information	The application sent the message asynchronously using connection AS2_http://sap.com/xi/XI/AS2. Returning to application
09.06.2014 17:52:18.836	Information	MIC (DeJYUIusqQj6aaYRASdHhAo+4J0=) is calculated using SHA1 algorithm.
09.06.2014 17:52:18.838	Information	The message was successfully retrieved from the send queue
09.06.2014 17:52:18.843	Information	Message status set to DLNG
09.06.2014 17:52:18.845	Information	MDN is succcessfully signed with SHA1 (1.3.14.3.2.26) algorithm
09.06.2014 17:52:18.859	Information	Trying to put the message into the send queue

09.06.2014 17:52:18.912	Information	Message successfully put into the queue
09.06.2014 17:52:18.913	Information	The message was successfully retrieved from the send queue
09.06.2014 17:52:18.918	Information	Message status set to DLNG
09.06.2014 17:52:18.961	Information	Trying to put the message into the send queue
09.06.2014 17:52:19.001	Information	Message successfully put into the queue
09.06.2014 17:52:19.001	Information	The message was successfully retrieved from the send queue
09.06.2014 17:52:19.006	Error	MP: exception caught with message No configuration / default adapter specified for EDISeparator
09.06.2014 17:52:19.006	Information	Delivering to channel: B2BSE00002_O2C_ORDERS_VANS_PO_WRITE_EDISeparator
09.06.2014 17:52:19.006	Information	Message status set to DLNG
09.06.2014 17:52:19.009	Error	Exception caught by adapter framework: No configuration / default adapter specified for EDISeparator
09.06.2014 17:52:19.010	Error	Transmitting the message to endpoint <local> using connection AS2_http://sap.com/xi/XI/AS2 failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.lang.Exception: No configuration / default adapter specified for EDISeparator
09.06.2014 17:52:19.015	Information	The asynchronous message was successfully scheduled to be delivered at Mon Jun 09 17:57:19 CEST 2014
09.06.2014 17:52:19.015	Information	Message status set to WAIT

[Dimitri]

Hi Saurabh,

You need a sender EDIseparator communication channel configured for your incoming message type.

Kind regards,

Dimitri

[saurabhkumbhare]

Hi Dimitri,

I have configured the following scenario :

Interface 1:

Sender AS2 -> Receiver EDISeparator

Interface 2:

Sender EDISeperator -> Receiver IDOC

For the Receiver EDISeperator; I have the following paramters in the adaptor :

Message Protocol : Electronic document interfchange

General tab : Nothing checked

997 acknowledgment / CONTRL : Not required

Module tab:

localejbs/ModuleProcessorExitBean      exit

exit            JNDIName     deployedAdapters/com.sap.aii.adapter.ediseparator.ra/shareable/com.sap.aii.adapter.ediseparator.ra

For the Sender EDISeperator; I have the following paramters in the adaptor :

Message protocol : EANCOM

Message Type : .*

Message version number : All versions

Message release number : All message releases

Interchange sender identification : .*

Interchange sender identification code qualifier :All codes

Interchange receiver identification : .*

Interchange receiver identification code qualifier :All codes

Module tab:

localejbs/CallSapAdapter Local Enterprise Bean entry

localejbs/EdifactConverterModule Local Enterprise Bean 1

EDI Message:

UNA:+.? 'UNB+UNOC:2+333333333:14+111111111:14+140312:1157+

1205972'UNH+120597200001+

ORDERS:D:96A:UN:EAN008+548198'

Sender party is assigned maintained as 333333333 | 014 | 14/EAN International

Can you please help..Many thanks in advance

Thanks

Saurabh

[Dimitri]

Message Protocol should not be EANCOM. You are exchanging EDI messages.

[ruchir_sinha]

Hi Dimitri,

I think he should be using EANCOM in the scenario association because his input file is of type EANCOM (He has EAN008 in UNH segment).

Former Member: . Please import the EANCOM B2B file if you have not done this earlier and define an appropriate Scenario Association for the EANCOM SAP Control key. You have configured the EDI Separator Sender channel for EANCOM and that is correct.

Best Regards,

Ruchir