Seeburger As2 adapter error after upgrade

Hello,
After an upgrade from PI 7.01 to PI 7.11 we have problems with our AS2 seeburger adapter. We installed the compatible version of seeburger but got stuck on the following error:
Message could not be forwarded to the JCA adapter. Reason: Fatal exception: javax.resource.ResourceException: SEEBURGER AS2: AS2 Adapter failure # java.lang.Exception: AS2 message composition failed: java.io.IOException: org.bouncycastle.cms.CMSException: key inappropriate for algorithm., SEEBURGER AS2: AS2 Adapter failure # java.lang.Exception: AS2 message composition failed: java.io.IOException: org.bouncycastle.cms.CMSException: key inappropriate for algorithm.
Thanks a lot for any advice,
Regards,
Erik

Hi
Pls chk the security jar files. you can download the latest version of these from java portal. This might fix the issues related to Key.
Srikanth Srinivasan

Similar Messages

Sender File adapter - Error after upgrade to SP16 !!

Hi ,
After upgrade from SP14 to SP16 , i see this error in Adapter monitor in rwb. The file does not get picked up. Any ideas on how to troubleshoot this ?
Configured at 2006-04-20 06:50:27 GMT
History:
- 2006-04-20 09:55:00 GMT: Retry interval started. Length: 30.000 s
- 2006-04-20 09:55:00 GMT: Error: BaseTransactionRolledbackLocalException: Exception thrown in method process. The transaction is marked for rollback.
- 2006-04-20 09:55:00 GMT: Processing started
- 2006-04-20 09:54:36 GMT: Error: BaseTransactionRolledbackLocalException: Exception thrown in method process. The transaction is marked for rollback.
- 2006-04-20 09:54:33 GMT: Processing started
Is there a patch that will fix this issue ?
Regards
matthias isenburg

thanks for yours tipps...
here the output of the defaultTrace.trc:
[EXCEPTION]
com.sap.engine.services.ejb.exceptions.BaseTransactionRolledbackLocalException: Exception thrown in method process. The transaction is marked for rollback.
     at com.sap.aii.af.mp.module.ModuleLocalLocalObjectImpl0.process(ModuleLocalLocalObjectImpl0.java:118)
     at com.sap.aii.af.mp.ejb.ModuleProcessorBean.process(ModuleProcessorBean.java(Compiled Code))
     at com.sap.aii.af.mp.processor.ModuleProcessorLocalLocalObjectImpl0.process(ModuleProcessorLocalLocalObjectImpl0.java(Compiled Code))
     at com.sap.aii.adapter.file.File2XI.send(File2XI.java(Compiled Code))
     at com.sap.aii.adapter.file.File2XI.processFtpList(File2XI.java(Compiled Code))
     at com.sap.aii.adapter.file.File2XI.invoke(File2XI.java(Compiled Code))
     at com.sap.aii.af.service.scheduler.JobBroker$Worker.run(JobBroker.java(Compiled Code))
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java(Compiled Code))
     at java.security.AccessController.doPrivileged1(Native Method)
     at java.security.AccessController.doPrivileged(AccessController.java(Compiled Code))
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java(Compiled Code))
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java(Compiled Code))
Caused by: javax.xml.transform.TransformerFactoryConfigurationError: Provider com.sap.engine.lib.jaxp.TransformerFactoryImpl not found
     at javax.xml.transform.TransformerFactory.newInstance(Unknown Source)
     at com.euh.FileModule.GetFileNameBean.process(GetFileNameBean.java:76)
     at com.sap.aii.af.mp.module.ModuleLocalLocalObjectImpl0.process(ModuleLocalLocalObjectImpl0.java:103)
     ... 11 more
Error during processing local bean localejbs/sap.com/com.euh.FileModule/GetFileNameBean
Module Exception 'com.sap.aii.af.mp.processor.ModuleProcessorException: Processing Error caused by: com.sap.engine.services.ejb.exceptions.BaseTransactionRolledbackLocalException: Exception thrown in method process. The transaction is marked for rollback.' found, cause: com.sap.engine.services.ejb.exceptions.BaseTransactionRolledbackLocalException: Exception thrown in method process. The transaction is marked for rollback.
Channel Orders_ftp_sender: Sending file failed with com.sap.engine.services.ejb.exceptions.BaseTransactionRolledbackLocalException: Exception thrown in method process. The transaction is marked for rollback. - continue processing
Should this traces give me more information?
mfg,
matthias

Seeburger AS2 Adapter Error :AUTHENTICATION_ERROR

i am doing the scenario for Purchase Order -> XI ->File
custumer is posting the purchase order
and XI Receives the PO using AS2 Adapter (Seeburger) and sends the output as File
i have done all the AS2 Adapter configurations as mentioned below but still i am getting the error in Seeburger Monitoring, the Error is Authentication_Error
1. Communication chennel
Adapter Type : AS2
Direction : Sender
Transport protocol : HTTP
Message Protocol : AS2
AS2 : Authentication Required is Enabled
Message Subject : Filled which is in Seeburger Monitor
2. Sender Agreement
Sender Communicational chennel which is created above
Security Setting
AS2 Sender Config :
Authentication Certificate : Customer public key
AS2 Receiver Config :
Decryption Key : Private key
3. in Party Identifiers
Party Name
AS2 ID
is there any settings missing to rectify the error "AUTHENTICATION_ERROR"

Hi
Check with PIAPPLUSER authentication
With this Check the following content on AS2 may be you get more clue.
http://www.customware.net/repository/display/WMFAQ/AS2-authenticationfailureinreceivingEDIINT+MDN
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/135b0b94-0701-0010-f6a9-86a14057544a
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/bpxproj/edi%2bwith%2bpi
Handling EDI interfaces using Seeburger BIC modules
Thanks
Gaurav

Seeburger AS2 Adapter error

Hi,
I'm trying to test AS2 connection with External system and got some errors.
I'm able to send message successfully to the external system with MDN Mode Synchronus with out any errors and got the MDN back, I changed the MDN mode to Asynchronus and got the below error. Do we need to do any extra configuration for Asynchronus mode MDN?
Waiting for your valuble suggestions.
Error message : Error in unkown channel: (No session available) >> Error type: COMMUNICATION_ERROR >> Error date: 9/23/10 2:19 PM >> Description: 500 - Internal Server Error: Error while handle incoming request: java.lang.NullPointerException: while trying to invoke the method java.lang.String.toUpperCase() of an object returned from com.seeburger.as2.tasks.result.MDNDecomposerResult.getMdnOriginalMessageID() [9/23/10 2:19 PM]
Thanks,
Kishore

Hi,
Sorry for the late reply.
Receipt Delivery Address : Enter the URL of yr own AS2.
Yes, I specified our AS2 address as http://xxxx:50000/SeeburgerAS2/AS2Server
Time Out: What you have given.
10 min
In case of asynchronous MDN mode, an Report channel and Sender agreement always have to be configured also when u201CRefer to XI systemu201D is disabled
Yes, I have created Sender agreement and Sender communication channel with Message protocol as Reports.
Thanks,
Kishore

Seeburger AS2 Adapter sending message error

I have configured a FAck scenario as described by the Seeburger Manual and am testing a AS2 messaging scenario with a vendor (basically the inbound EDI message is passed to the Seeburger splitter to create a new message for the inbound order, and then the existing payload is mapped to a Funcational Acknowledgement and sent back to the vendor). I receive the message fine and the message split to create the order works fine, however when the FAck is passed to the AS2 receiver adapter (for transmission to the 3rd party) I get the following error:
LOCATION [null, null, 91fcf4f0-5223-11dd-9c8d-5cd90a641602] >> ERROR TYPE [, COMPONENT_ERROR, not retryable, not fatal]] >> DESCRIPTION [AS2 Adapter failure >> MID
MID <[email protected]22.2> already exists. - Duplicate will not be sent [LOC: com.seeburger.as2.component.AS2Client.storeMID]
Message processing failed. Cause: javax.resource.ResourceException: Fatal exception: com.sap.aii.af.ra.cci.XIDeliveryException: SEEBURGER AS2: AS2 Adapter failure # MID <[email protected]22.2> already exists. - Duplicate will not be sent, SEEBURGER AS2: AS2 Adapter failure # MID <[email protected]22.2> already exists. - Duplicate will not be sent
I'm not sure where the "duplicate" message comes from as this message definitely has not been sent before.
If I extract the same inbound message from the payload and pass it in using a file adapter (rather than the AS2 sender adapter) then the functional acknowledgement is created and transmitted to the vendor without any issues ...
Has anyone who has had some experience with the Seeburger AS2 adapter got any possible suggestions for resolving this issue?
Regards,
Jason

Hello ,
same issue occurred in my system
Exception caught by adapter framework: Fatal exception: com.sap.aii.af.ra.cci.XIDeliveryException: SEEBURGER AS2: AS2 Adapter failure # MID <[email protected]> already exists. - Duplicate will not be sent, SEEBURGER AS2: AS2 Adapter failure # MID <[email protected]> already exists. - Duplicate will not be sent
I'm not sure where the "duplicate" message comes from as this message definitely has not been sent before.
Has anyone who has had some experience with the Seeburger AS2 adapter got any possible suggestions for resolving this issue?
Please advise asap.

AS2 adapter error during inbound processing

Hello,
We have upgraded PI to version 7.1 and now we are testing the Seeburger AS2 adapter.
We have received a testmessage from an AS2 partner and it is shown in the message monitoring of the Seeburger adapter workbench, with status succesfull.
Only the message is not on the integration server. The message is not shown in sxmb_moni or the message monitor of the RWB.
In the RWB the communication channel (CC_AS2_Sender) gives the following error:
"Message inititiation failed: Processing error"
The message itself gives the following error:
"Inbound message processing failed! performing rollback
Can anyone help us with this?
Thanks in advance.
Regards,
Marco

Hi Marco,
the message is not forwarded to the intergration egine because there might be an error in your communication channel.
Are there any other modules in the module chain of this communication channel?
Can you check "default_trace" and "application_log" for exceptions (/j2ee/cluster/serverXX/log)?
Did you also restart the Java Stack after the Upgrade?
regards,
Daniel
Edited by: Daniel Rexter on Jun 30, 2010 2:59 PM

File adapter error after updating to SP19 (INBOUND_BINDING_ERROR)

File adapter error after updating to SP19 (INBOUND_BINDING_ERROR)
Hi all,
im having some troubles after the installation of SP19 (from SP16 in NW04) with File Adapter (File->Idoc scenario).
In message monitoring (Adapter Engine), I have several messages with status "System Error". The error text is :
Received XI System Error. ErrorCode: INBOUND_BINDING_ERROR
ErrorText: ErrorStack: Error in sender agreement for party '', service 'LEGACY_DEV', interface namespace 'http://XXXXX.com/XXXXXX', interface 'INTERFACE_OB' No sender agreement found for , , , , ,
Im sure that the Integration Directory settings have not been changed. So I tried the following, but the problem persists:
- Deactivation/Activation of File Adapter channel
- check that user XIISUSER is not locked
- checked SXI_CACHE (it seems ok)
- Many CPA full refresh
- Dummy modifications of File Adapter channels (a dummy modification of the description)
- Reboot J2EE
I've seen that someone else had problems after upgrading to SP19. I'd really appreciate any suggestion of how to solve my issue.
Thank you
Manuel

Hi Prabhu,
I've already tried to restart server, but nothing happened. (Before update to SP19, the interface worked well).
This is the error log from message monitoring:
 2007-01-16 16:37:34 Success Channel cc_File_Snd_Bolle: Entire file content converted to XML format
2007-01-16 16:37:34 Success Send binary file "BOLLE_20061229142059.CSV" from FTP server "AS810T:/sapinbound", size 8733 bytes with QoS EOIO
2007-01-16 16:37:34 Success Application attempting to send an XI message asynchronously using connection AFW.
2007-01-16 16:37:34 Success Trying to put the message into the send queue.
2007-01-16 16:37:35 Success Message successfully put into the queue.
2007-01-16 16:37:35 Success The application sent the message asynchronously using connection AFW. Returning to application.
2007-01-16 16:37:35 Success The message was successfully retrieved from the send queue.
2007-01-16 16:37:35 Success File "BOLLE_20061229142059.CSV" successfully archived on FTP server "AS810T" as "/sapinbound/bolle/20070116-163735-245_BOLLE_20061229142059.CSV"
2007-01-16 16:37:35 Success The message status set to DLNG.
2007-01-16 16:37:35 Error Received XI System Error. ErrorCode: INBOUND_BINDING_ERROR ErrorText: ErrorStack: Error in sender agreement for party '', service 'LEGACY_DEV', interface namespace http://XXXXX.com/XXXXXX', interface 'INTERFACE_OB' No sender agreement found for , , , , ,
2007-01-16 16:37:35 Error Transmitting the message to endpoint http://SERVERNAME:8000/sap/xi/engine?type=entry using connection AFW failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: INBOUND_BINDING_ERROR:. 
2007-01-16 16:37:35 Success The asynchronous message was successfully scheduled to be delivered at Tue Jan 16 16:42:35 CET 2007.
2007-01-16 16:37:35 Success The message status set to WAIT.
2007-01-16 16:42:35 Success Retrying to send message. Retry: 1
After this, the system try to resend the message, and the same error appears several times.
Ty,
Manuel

Client Auth and SSL with Seeburger AS2 adapter

Hello All,
We are using the Seeburger AS2 adapter in our landscape and I am in the process of setting the same up and have made quite some progress in all my issues.
and I hope that you will be able to help me out.
1. Server SSL on Receiver AS2 adapter
I am sending a message from XI using the Receiver AS2 adapter to my AS2 test tool using Server SSL.
This is working perfectly fine. In my AS2 adapter I have selected HTTPS as the protocol and the message goes via SSL to the target test tool, is processed and the MDN comes back to XI perfectly.
The issue here is :
Irrespective of what is provided in the Server Certificate ( Keystore) , the message goes to my target test tool. I even left this field blank with no certificate entry and still the SSL connection was established and the message went to the target system.
Is there no validation that XI does here? I am lost what is the use of this entry Server Certificate if XI blindly accepts all SSL connections.
I am using a Decentral Adapter Engine with LoadBalancer.
2. Client Auth on Receiver AS2 Adapter
I tried to perform Client Authentication by proving my Server's private key in the AS2 adapter. The corresponding public key is loaded in my partner's Keystore.
XI error's with the error "SSL handshake failed - Bad Certificate" .
I am not sure why XI is erroring out here and I have a feeling that I have misunderstood the use of the fields in the AS2 adapter,
Server Certificate ( Keystore) and Private Key for Client Authentication.
Has anyone tried this? If further details are needed, I will be able to furnish the same.
Regards,
Bhavesh

Hello Jens,
Thanks for your reply.
1. The Encryption and Signature part of the Interface is working absolutely fine and I use the same concept highlighted by you - The Sender always signs the message with his private key and encrypts with message with the partner's public key in the corresponding agreement.
2. Server SSL is also working perfectly fine, i.e, when XI initiates the connection the SSL connection is established to the partner.
3. Mutual Auth was the issue where I was getting the bad certificate issue.
To investigate further I moved the same setup to my Central Adapter Engine and all the issues I had described above seem to have vanished and things work exactly as I was expecting, ie.
The field : Server Certificate (Keystore) is used to provide the Target System's Server SSL's public Certificate.
The field : Private Key for Client Authentication is used where XI provides its own Server SSL's private key for Mutual / Client Authentication.
The problem seems to be with my Decentral Adapter engine and not my central adapter engine and so I guess,
1. I either have the incorrect certificates on my Decentral Adapter Engine.
2. I also have 2 instances of a Decentral Adapter Engine with a Webdispatcher and so maybe the 2 Visual Admin's of the 2 Decentral AE are inconsistent.
3. Maybe it was just a long day and I did something wrong
Will investigate further for the root cause but I am glad that my concepts remain intact and things do work as I expected them to work.
A blog on all this is on the cards sometime soon.
Cheers,
Bhavesh

AS2 Adapter Error: Error while parsing AS2 message: AUTHENTICATION_ERROR #

Hi,
Following Scenario: Inbound.
i have been receiving messages via Seeburger AS2 Adapter with the following Error message
Error while parsing AS2 message: AUTHENTICATION_ERROR #
I have done the following in the AS2 adapter as per findings in the forum
1. Unchecked the Authentication Required Flag.
2. AS2 Certificates are fine.
3. Use Authentication: Disabled (there is no authentication)
even though every thing seems to be fine i am not able to receive messages successfully. Please let me know what could have gone wrong here.

Hi Venkatesh,
>> Everything is provided in the Sender Agreement. Partners Certificate, Self Encryption & Signing certificate
How come you are using encryption when you are receiving the message. I think it might be decryption.
1. Anyway please cross check whether you provide the following correct details in Sender agreement.
Sender Configuration
Authentication Certificate : Partner's public certificate.
AS2 Receiver Configuration
Decryption Key : Own private key.
Signing Key : Own private key.
2. Can you please check and tell in the Seeburger Monitoring for the incoming message, whether they are sending the message with encryption and signing? This you can check in the Seeburger Monitoring.

Seeburger AS2 Adapter: "MDN not signed"

Dear all,
we just updated our test system from XI 3.0 to PI 7.1. Now we are facing a problem with our Seeburger AS2 Adapter.
I sent out a message via AS2 and get the follwing error message in Seeburger AS2 Monitor:
"MDN not signed"
In the Receiver Communication Channel I checked the Option "Sign MDN". In XI 3.0 this Scenario was working perfectly. So I contacted our communication partner and asked them if our AS2 message really contained a request for a signed MDN. Our commnucation partner confirmed and sent the MDN as text file to me. This text file shows that the MDN is signed. So it seems that the Seeburger AS2 adapter does not notice that the received MDN is a signed one. But why? Do you have an idea?
Just for testing purposes I unchecked the "Signe MDN" option. In this case the transmission finished successfully.
Who can help?
Thanks
Michael

Dear Vikrant,
many thanks for your reply. But I am not sure if we are really facing the same issue as you described it in your article.
Currently we have this situation:
When I send out a message the Seeburge Workbench provides only the following error message:
"MDN not signed"
Via the Recovery Monitor I can check the received MDN. Here I can see that the MDN is signed and positive.
In the Runtime Workbench I checked the following:
1. In the Message Monitor (Adapter engine) the message is in status "System Error". Here are the details:
Message could not be forwarded to the JCA adapter. Reason: Fatal exception: javax.resource.ResourceException: SEEBURGER AS2: Negative synchron MDN received., SEEBURGER AS2: Negative synchron MDN received.
Adapter Framework caught exception: Fatal exception: javax.resource.ResourceException: SEEBURGER AS2: Negative synchron MDN received., SEEBURGER AS2: Negative synchron MDN received.
Delivering the message to the application using connection AS2_http://seeburger.com/xi failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: javax.resource.ResourceException: Fatal exception: javax.resource.ResourceException: SEEBURGER AS2: Negative synchron MDN received., SEEBURGER AS2: Negative synchron MDN received..
2. The Communication Channel Monitor shows the following error messages:
Error type: REPORT_ERROR >> Error date: 12/14/10 12:02 PM >> Description: MDN not signed [12/14/10 12:02 PM]
Message processing failed. Cause: javax.resource.ResourceException: Fatal exception: javax.resource.ResourceException: SEEBURGER AS2: Negative synchron MDN received., SEEBURGER AS2: Negative synchron MDN received.
I do not understand why the MDN is recognized as negative and unsigned even if the plain text version of the MDN shows that it is signed and positive.
In your article you recommend to create a sender communication channel for MDN and a corresponding sender agreement. We already did that in XI 3.0 to forward the MDN as STATUS IDOC to SAP ECC.
Maybe you have an additional idea?
Thanks
Michaek

Download SEEBURGER AS2 Adapter

Hi All,
I would appreciate if you could let me know, from where I could download the SEEBURGER AS2 adapter which will be compatible to PI 7.10 EhP1?
Regards,
Ramanathan EKAMBARAM

Hi Hemant,
We have it installed on our current PI 7.0 environment and have the necessary license. However, when I look into Installations and Upgrades - Entry by Application Group - Adapters - Seeburger - XI-A GENERIC EDI BY SEEB., I could see only NW71-PI-A GEN SEEB 2.1 and not SEEBURGER AS2.
Let me know, if SEEBURGER AS2. contains NW71-PI-A GEN SEEB 2.1.
Regards,
Ramanathan EKAMBARAM

Seeburger AS2- Authentication Error

Hi All,
We are using Seeburger AS2 adapter and we will send and receive EDI documents to two Mail Box.
We are using certificates for signing and encrypting the message. While sending and receiving EDI documents to Mail Box1, all messages are successfull.
When we send message to Mail Box 2 . It is successfully delivered to the receiving partner. But when we are receiving message from trading partner we are facing following error in the Seburger Workbench.
Error while parsing message in AS2 adapter:AUTHENTICATION FAILURE.
We have restarted the server and tried, still same error we are facing.
For AS2 Channel Configuration in Integration Directory we followed SAPXI_AS2Adapter_en document.
Can any one suggest solution to solve the error.
Regards
Prakash

It is certificate issue which was solved

Time machine fails backing up with a "backup disk not found" error after upgrade to Lion 10.7.2

Time machine fails backing up with a "backup disk not found" error after upgrade to Lion 10.7.2. I've erased and reformatted the drive; reconnected Time Machine(it saw it) and began a new backup. The backup starts again but fails before completing with backup drive not found error. I used the 10.7.2 combo update. Any help on how to fix this problem would be appreciated.

Arghhhhhhhhhhhhhhhhhhh!!!!!!
After waiting since October for a fix, I have now upgraded the firmware on the Time Capsule and installed the new Airport Utility, released yesterday, and the situation is even worse.
Up until now, the Airport Utility had an option to disconnect all drives manually and the Time Capsule would then work until the next reboot – a temporary (?) work-around.
Now that option does not exist in the new-look Airport Utility. And the Airport Utility installation can’t be rolled back and the old utility won’t restore.
The sparesbundle is still not accessible. Anyone worked out a work-around in the new environment yet?
I have another Time Machine backup working fine to a trusty old Lacie Drive so erased the one on my Time Capsule to see if that works. I have renamed the Capsule and the Time Capsule Drive. But to build another full backup will take at least two days and I shall be away from tomorrow and am reluctant to leave the Capsule and computer up and running for a week. And I’ll bet the sparsbundle will still be nowhere to be found.
How can Apple screw up so badly when they are to become the richest company in the entire world and – soon – will have more cash in the bank than the entire United States? Can’t they afford someone who really can sort this out? Especially when a Firewire connected hard drive – my trusty and simple LaCie – works fine.
Words, almost, fail me.

Seeburger AS2 Adapter implementation in PI 7.1

HI Experts,
We have seen lot of implemetation of seeburger adapters in PI 7.0 but didnt got any chance to look ahead for any documents related to seeburger AS2 adapter implementation in PI 7.1 .
Request if you can please guide or provide some hands on documents which can give the clear overview of how to configure AS2 adapter in PI 7.1 and its parameters.
Thanks & Regards,
Abhishek

Hi,
refer the blog by prateek:-
http://wiki.sdn.sap.com/wiki/display/XI/ParametersUsedinModuleProcessingforSeeburgerAS2AdapterforSAP-PI
u can also refer other blogs for details search on SDN
http://www.sdn.sap.com/irj/scn/advancedsearch?query=seeburger
I think everything remains same.
chirag

How to deal Inhouse files using Seeburger AS2 adapter...!!!

Hi all,
Has anyone managed to configure the Seeburger AS2 adapter for XI successfully to process multiple inbound message types.
We have an issue here with inbound messages being received by the AS2 adapter. We currently have it configured for inbound deliveries(Which deals with EDI files) which is working fine. The issue is that we would now like to send other messages as well. It seems the AS2 adapter only looks at the sender/receiver party combination to determine the correct sender agreement, but does not look at the message type which is a limitation. I have heard mention of a splitter module which can be used to distinguish between different messages and pass them to the correct sender agreement for processing, information on this is thin on the ground to non existent.
I have few custom Inhouse files where i need to recieve through AS2 adapter.
I need to differentiate the messages hitting to my communication channel.
ex:
1st message will be having
HDR PICKS
2nd message will be having
HDR PURCH
so based on the second field which has "PICKS" or "PURCH" , i need to pass the message to run the corresponding map.
How i need to configure to acheive these kind of custom Inhouse files through AS2 adapter??
Do i need to use splitter for these as well?? If yes how i need to use?
Is there any setting we can make at Sender AS2 adapter to differentiate each message??
Waiting for the answers.
Kindly reply if anyone knows.
Thanks&Regards
Seema.

Hi,
i have setup a scenario with edifact (different message types) using as2.
first i had to create a mapping using bic.
edifact_xxxx
in: edifact_service
out: functional acknowledgement.
in the mapping code i adjusted the called mapping, standard it will use see* changed it to e2x* (custom mapping)
in your case using flatfiles maybe you should take a look at the VDA structure, these files are also defined under inhouse.
when you define a input file adapter are you getting a classifier message?
like
<classifier><type>Edifact</type><classifierMappingID>XXXX</classifierMappingID><encoding>US-ASCII</encoding><additionalIdentifier></additionalIdentifier></classifier>

Seeburger As2 adapter error after upgrade

Similar Messages

Maybe you are looking for