AS2 Sender adapter

Hi,
The scenario I'm working on is AS2 -> PI -> File. I am receving the AS2 messages perfectly and the file is being generated without any problems. Also, the MDN response message is sent without any problems (however it is not signed or encrypted).
I need to sign and encrypt the response MDN message however I'm unsure how to do this. Does anyone have a step-by-step link or document that can guide me on how to set this up?
Thanks
Krishneel

Hi Gounder,
You need to install the certificates in xi server. Please check this threads for some information:
MDN not authenticated
Re: Asynchronous/sync mdn
Regards,
---Satish

Similar Messages

AS2 Sender Adapter -- Need few details.

Hi Seeburger Experts,
Im new to seeburger and i just to know regarding AS2 adapter.
Im a bit clear about the AS2 receiver adapter there we have an option of giving partner Server,URL and Port to send the messages from XI.
In the same way, I couldn't find the fields for AS2 Sender adapter to provide Server,Port and URL.
So im just wondering how we will be receiving the messages from Partner system thorugh AS2 adapter.?
as we are not providing any information like URl,port,path or Directory.. etc
Can anyone pls share ur answers.
Thanks&Regards
Deepthi.
Edited by: deepthi reddy on Dec 24, 2007 5:35 AM

HI Deepthi,
We need to give the AS2ID in the party identifier tab,AS2ID that is entered here will be used for identifying the sender and receiver of the document.
1)The value of the Agency field must be Seeburger.
2)The value of the Schema field must be AS2ID.
Every partner is assigned the WAN no which is provided by the WAN service provider. That WAn no we need to configure in the party identifier tab.
I hope It is clear to u now.
Thnx
Chirag.

AS2 Sender Adapter -- Need clarity.. Very Very Urgent...!!!

Hi AS2 experts,
Regarding AS2 sender adapter:
We will provide the details
TP: HTTP
MP: AS2
*Message Subject = **
1. Can anyone please clarify what is this message subject ??
Its the incoming file name we need to provide?
According to few blogs,
2. We will be providing the below URl to the partner system to send there messages.
HTTP://<your-xi-server>:50000/SeeburgerAS2/AS2Server
Consider im having partner systems A,B,C .
and we will be creating 3 communication channels(CC1 ,CC2 ,CC3) to three partner systems.
If i provide same URL to all the three partner systems.
Then how it will differentiate like which file is belongs to which interface (from which partner it is coming)?
And im not providing anything specific in all the AS2 sender comunication channels to differentiate these files.
What is this AS2ID which we will provide in Party Configuration.
WIll it makes any difference to above problem?
Kindly suggest me if anyone has idea about this asap.
Its Very very urgent.
ThankYou.
Regards
Deepthi.

Hi,
>>>>1. We need to provide the below URl and Port to the partner to receive the messages?? HTTP://<your-xi-server>:50000/SeeburgerAS2/AS2Server
I guess yes . you need to provide this URI.
>>>>>2.Is it possible to do content based routing by using Message Subject?
yes it is possible to determine the receiver depending upon ur condition. Please provide the context object at design time and at the time of Configuration , using XPATH you can determine conditional receiver.
please look in to this links u will come to know about seeburger adapter.
/people/bla.suranyi/blog/2006/06/08/sap-xi-supports-edifact
/people/william.li/blog/2006/03/17/how-to-get-started-using-conversion-agent-from-itemfield
/people/paul.medaille/blog/2005/11/17/more-on-the-sap-conversion-agent-by-itemfield
http://www.stylusstudio.com/edi/XML_to_X12.html
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/b0b355ae-0501-0010-3b83-8f2bb566fa47
Details on XI EDI adapter from seeburger
/people/bla.suranyi/blog/2006/06/08/sap-xi-supports-edifact
http://www.seeburger.it/fileadmin/it/pdf/2005_04_sapphire_Ferrero_transcript.pdf
http://www.seeburger.com/fileadmin/com/pdf/Butler_Group_SEEBURGER_Technology_Audit.pdf
http://www.seeburger.com/fileadmin/com/pdf/AS2_General_Overview.pdf
SAP Adapters
EDI with XI
http://www.seeburger.com
http://www.seeburger.com/fileadmin/com/pdf/AS2_General_Overview.pdf
http://www.seeburger.it/fileadmin/it/pdf/2005_04_sapphire_Ferrero_transcript.pdf
http://www.seeburger.com/fileadmin/com/pdf/SEEBURGER_SAP_Adapter_engl.pdf
http://www.seeburger.com/fileadmin/com/pdf/Butler_Group_SEEBURGER_Technology_Audit.pdf
http://www.sap.com/france/company/events/2006/02-01-Automotive-Seeburger.pdf
http://h41123.www4.hp.com/presentations/ISUG/XISeeBurger.ppt
http://www.sap.com/asia/company/events/nwtechdays/presentation/australia-slides/Pre-Built_Integration.pdf
http://www.seeburger.com
http://www.seeburger.it/fileadmin/it/pdf/2005_04_sapphire_Ferrero_transcript.pdf
http://www.seeburger.com/fileadmin/com/pdf/Butler_Group_SEEBURGER_Technology_Audit.pdf
http://www.sap.com/france/company/events/2006/02-01-Automotive-Seeburger.pdf
http://h41123.www4.hp.com/presentations/ISUG/XISeeBurger.ppt
Hope this will help you.
Regards
Aashish Sinha
PS : reward points if helpful

AS2 Sender adapter.. How we can receive 2 messages from same partner??

Hi all,
I have to receive 2 AS2 messages from my partner like ORDERS and REMADV information.
I kept Message Subject as * for both my AS2 Sender adapters.
I configured both the scenarios and i ask my partner to send the messages and he got the error as
"403 : FORBIDDEN" .
But these two scenarios are working when i delete one scenario and run the other by keeping message subject as *
I felt like the messages can be diffferentiated only with Message subject when we are dealing with AS2 adapters.
Questions :
Is there any option in AS2 sender adapter where we can differentiate the messages apart from Message subject because my partners are sending the messages without any message subject.
Kindly let me know.. its urgent.
Regards
Seema.

Hi Swarup,
Thanks for the reply.
I think you totally misunderstood my question.
Here i will explain clearly..
Sender Party : PartyA
Sender AS2ID : A-AS2
Recevier party: PartyB
Receiver AS2ID : B-AS2
PartyB will be receiving messages from PartyA.
Say it is receving ORDERS and REMADV messages.Both are XML files.
So PartyB will be configured with two complete new scenarios and 2 AS2 sender adapters to receive the messages.I kept Message subject as * in both the sender adapters.
The messages are not coming in and clearly there is a confilct in selecting the correct communication channel.
Actually i read in one of the thread that the messages which are coming to XI will be picked up based on two things:
1) AS2 ID of the partner which is dicussed above and the second one is
2) Message subject
But from my partners we are receving the messages without any Message subject.
So in this situation how we can differentiate each messages and how the messages will go to correct communication channel.??
Regards
Seema.

Seeburger AS2 Sender Adapter : http: 403 error

Hi All,
We have a scenario where the external party is sending xml message to xi.
While sending they are getting the below error.
u2022 Error(Error(com.cyclonecommerce.tradingengine.transport.TransportException: Retryable response: 403 Forbidden), ExchangePointId(Id(147995587),
Has anyone encountered this error before?
Any idea what might be the problem?
Regards,
Aarthi

Hi,
This error may have different reasons:
1) You or your partner has entered an incorrect AS2 ID for one of the involved parties.
2) A valid sender agreement is missing.
3) There are more then one AS2 sender agreements with the same sender AND receiver party.
4) The corresponding inbound channel is set to inactive.
Regards,
Prakasu.M

AS2 Sender Adapter test

Hi Experts,
I am working on a 856 AS2 to file scenario. I have followed the links EDI to 850 and a few blogs as well.
I have configured the scenario as following:
IR
Message mapping and Interface mapping have been created for 856 to file and 997 to 997 EDI.
ID (party used .. (BC_CUST, sender) and (BC_XI, receiver ))
2 Sender Comm. Channel - for 856 (Send_856, type AS2) and 997 (Split_997, type Split997)
2 Receiver Comm. Channel - file receiver and (AS2 receiver for 997)
2 Receiver determination -
----Sender... || Interface ..... || Receiver ||
BC_CUST || A_856.......... || BC_XI ....|| (for 856)
BC_CUST || A_997 ..........|| BC_XI ....|| (for 997 ... * Is the sender correct * or it should be BC_XI ... )
2 Interface determination
2 Sender Aggrements
----Sender... || Interface ..... || Sender CC ||
BC_CUST || A_856........ || Split_997 (as defined above) * Is this correct * or it should be Send_856 ...
BC_CUST || A_997 ........|| Send_856 (as defined above)
2 Receiver Aggrement
Sender... || Interface ..... || Receiver CC || Receiver **
BC_CUST || A_856........ || file receiver ..|| BC_XI
BC_CUST || A_997 ........|| AS2_997 ......|| BC_XI
Please check and confirm that this config is correct or not, As we are getting an '500 internal erroru2019 when customer is sending 856 data.
Is ther any test tool available for AS2 adapter?
Regards,
Sachin Dhingra

Hi Shabarish,
Thank you for prompt reply..
I tried that, but i am not able to locate the right one, novice to Seeburber.. Please provide the link for right one and also please check the confg once...
Regards,
Sachin Dhingra

AS2 sender adapter 403 forbidden error

Hi Experts,
I have a scenario which is connecting with third party using sender AS2 adapter.
while third party sending message to PI they are getting 403 forbidden error.
sender agreements are created one for MDN reports and another particular interface for the same sender party and receiver party.
certificates are installed properly and message subjects & AS2 ID also maintained correctly.
i am using pi7.11 version and seeburger AS2 adapter.
Please suggest any configuration or setting if missed which causes this issue.
Thanks in advance.

Hi Eng Swee,
Thanks for your reply
Please find the below sender agreements & corresponding CC
second one:
third one:
Fourth one
E is for the third party & M is our own party.
F,P,V,V are communication components
all these are working

Howto configure Seeburger AS2 Sender Adapter without using subject

Hello Experts,
we're going to implement AS2 Communication with a partner who isn't able to send the XML message with a subject in AS2 HTTTP headerfield but a different dtAS2FileName per message.
We have configured the scenario and it works as long as the partner only sends one message type (e.g. ORDER-XML). But of course there will be more than ORDERS and I don't know how to configure the scenario because I have to use only one Sender agreement with the same PARTNER-IDs (as mentioned in Seeburger AS2 Adapter Configuration Guide)
Can you please provide me the required configuration to deal with different Message-Interfaces from the same Partner.
We are an NW 7.0, Seeburger is on 1.8.1
Thanks in advance
Christian Sperlich

Christian Sperlich wrote:
Hi Suresh
>
> thanks for your answer. Exactly this scenario cames to our mind and was also suggested by another SAP Consultant. I'm sure this will work but (sorry!) this can't be the solution. Not only the additional configuration but also the monitoring of the EDI-Messages is more difficult if there were more than 1000 messages per day.
>
> Any other possibility / configurations?
>
> Kind regards
>
> Christian
Hi
You dont need to create another file channel to poll the files from a folder. This will be a additinal overhead to the system.
You can directly route the file on the fly based on dtAS2FileName to different receivers as well as interfaces.
You need to use condition in receiver/interface detyermination.
Your condition type shound be context object(not XPATH).
Then search for context object dtAS2FileName.

AS2 sender communication channel

Hi All,
I have one As2 to proxy scenario, using AS2 sender adapter,PI will be receiving flat file from party and I am performing content conversion in sender As2 channel, there is no mapping involved, and PI is sending this data to SAP system via proxy using integrated configuration.
I have used 2 parties, one sender and one receiver, used 2 business components corresponding to each and one SAP system BC.I have mentioned AS2 ids in both the parties, and did the header mapping for receiver in integrated configuration ->Outbound processing tab.
Now when the file is pushed from AS2 server, there is no log in sender channel monitoring, means the file is not getting picked up from the AS2 server at all.
Can anyone please provide inputs how can we debug this problem.
Thanks,
Ruchi

Hi,
If you are using Seeburger AS2 adapter, then:
1. Check if the URL http://XXXXX:50000/SeeburgerAS2/AS2Server is up. It should show-"405 Method Not Allowed "
2. Check for AS2 messages in Seeburger workbench message-MessageIdStore Monitor
Thanks
Rajeev Gupta

Seeburger AS2 sender comm channel config

Hello,
I have to put in place a scenario for message reicipt of EDI messages via Internet using AS2 on http.
We use the seeburger AS2 adapter.
I try to configure the AS2 sender adapter, but there are many options, which I do not know how to fill, and which aint documented either.
I use the following config:
Tranport Protocol: http
Message Protocol:AS2
Adapter Engine: Integration Server
AS2 Authentification neccessary: When do I have to set this?
Message Title: *
Asynchronous MDN configuration
SSL certificate alias: where do I get this from?
SSL client certificate: what do I put in here?
use proxy: Do I specify the data of our SAP Web dispatcher here?
Thanks
Matthias

HI,
See the below links
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/135b0b94-0701-0010-f6a9-86a14057544a
/people/bla.suranyi/blog/2006/06/08/sap-xi-supports-edifact
/people/william.li/blog/2006/03/17/how-to-get-started-using-conversion-agent-from-itemfield
/people/paul.medaille/blog/2005/11/17/more-on-the-sap-conversion-agent-by-itemfield
http://www.stylusstudio.com/edi/XML_to_X12.html
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/b0b355ae-0501-0010-3b83-8f2bb566fa47
Details on XI EDI adapter from seeburger
Check this for Conversions-
/people/bla.suranyi/blog/2006/06/08/sap-xi-supports-edifact
http://www.seeburger.it/fileadmin/it/pdf/2005_04_sapphire_Ferrero_transcript.pdf
http://www.seeburger.com/fileadmin/com/pdf/Butler_Group_SEEBURGER_Technology_Audit.pdf
http://www.seeburger.com/fileadmin/com/pdf/AS2_General_Overview.pdf
SAP Adapters
EDI with XI
http://www.seeburger.com
http://www.seeburger.com/fileadmin/com/pdf/SEEBURGER_SAP_Adapter_engl.pdf
http://www.sap.com/france/company/events/2006/02-01-Automotive-Seeburger.pdf
http://h41123.www4.hp.com/presentations/ISUG/XISeeBurger.ppt
http://www.sap.com/asia/company/events/nwtechdays/presentation/australia-slides/Pre-Built_Integration.pdf
seeburger adapter configuration
Regards
Chilla

AS2 Sender configuration - Authentication Certificate

Hello guys,
We're implementing EDI with a partner with AS2. We have AS2 sender adapter configured. Everything works fine (we're able to receive data from partner and send back MDN) without signing.
Now we're working on getting data signed. We have uploaded partner cert to keystore (TrustedCAs) and have provided partner with our certificate as well.
On Sender agreement--> Security Settings --> AS2 Sender Configuration --> Authentication Certificate how do we specify the certificate we're using. Should it be just the fullname like TrustedCAs/PartnerCert ?
Also How should we specify the Decryption Key and Signing Key under AS2 Receiver Configuration?
I was expecting to be able to choose from available keystores, but it is a free text field.
Can anybody please help me on this?
Thanks
Karthik

Hi Karthik,
>>On Sender agreement--> Security Settings --> AS2 Sender Configuration --> Authentication Certificate how do we specify the certificate we're using. Should it be just the fullname like TrustedCAs/PartnerCert ?
You need to mention the fullname as TrstedCAs/PartnerCert.
>>Also How should we specify the Decryption Key and Signing Key under AS2 Receiver Configuration?
Yes you need to since you are using signed messages here..
Regards
Suraj

AS2 Sender problem with German "Umlaute"

Hello experts,
I have an AS2 sender adapter sending orders into my SAP system. My problem is though that it deletes all German "Umlaute" before converting it into XML.
I used to use the "CallBicXIRaBean" to do the Encoding with ISO-8859-1 and it did not work. So now I am using the "CharsetConversion" to do that but it still does not work.
In the Module of the AS2 sender I am using:
1) CharsetConversion
- sourceDest --> MainDocument
- targetDest --> MainDocument
- sourceEnc --> ISO-8859-1
- targetEnc --> ISO-8859-1
2) CallBicXIRaBean
- mappingName --> E2X_ORDERS_UN_D93A
3) localejbs/CallSapAdapter
- 0
Does anyone have an idea what I have to change?
Thank you very much for your help!
Best regards,
Peter

Hello Iddo,
Thank you for your answer.
When I expect Umlaute in a message I always use ISO-8859-1 and not UTF-8.
The Umlaute are actually deleted. For example the German "für" looks like this "f". Or "Präferenzsituation" looks like this: "Prerenzsituation". So it kills the Umlaut and the following character.
The sender insists that he sends the messages with Umlaute. Now I activated the AS2 Message Dumping and hopefully will see what the message really looks like. Maybe the Umlaute are already deleted when they get to the AS2 adapter. I hope to find out soon.
Best regards,
Peter

AS2 error The FILE send adapter cannot open file

I have AS2 setup under biztalk. I have receive port which listen to HTTP adapter and keep listening on web site.Then there is corresponding send port which just write that file in folder . Send port just have filter for Receive adapter name.
It works fine, but some time I get error message
The FILE send adapter cannot open file <folder name\guid.txt > for writing.
Details: The system cannot find the path specified.
I am not able to understand what is error for this? Please help me to figure-out this.

Specifying the Backup transport is not going to solve the problem. Specifying the backup transport in this case is something like addressing the symptom of the issue and not finding the solution to root cause of the issue.
As you specified, if the mentioned error only happens some time but not always. In this case, the message "The
FILE send adapter cannot open file <folder name\guid.txt > for writing." would just be a warning message. Just by setting the retry in the send port will solve the issue. i..e Since this issue occurs rarely, it may be short lived glitch.
So by setting the retry count (lets say 3 times) with retry interval (let say 5 mins), this issue can be easily mitigated. You would not lose the message. So during the glitch you would get this message as warning, send port will retry "after specified
retry interval so after 5 mins", so by that time chances of files transfer is high. So this problem can be easily handled just by having retry count and retry interval in send port.
But you need to find the actual cause for this issue or you need to find the permanent resolution for this issue.
If this answers your question please mark it accordingly. If this post is helpful, please vote as helpful by clicking the upward arrow mark next to my reply.

DtReport structure and Alerts Settings from sender AS2 Reports adapter

Hi,
I have imported DtReport for MDN's from SeeBurger AS2 adapter documentation as external definition into PI. However, in the mapping, when I select DtReport as source, I could see only the following structure:
<?xml version="1.0" encoding="UTF-8"?>
<ns0:DtReport xmlns:ns0="http://uri.seeburger.com/dt/master/schema">
   <ns0:clientId/>
   <ns0:correlationId/>
   <ns0:category/>
   <ns0:state/>
   <ns0:finalReport/>
   <ns0:freeText/>
   <ns0:specificData/>
   <ns0:reportAttachment/>
   <ns0:archiving/>
</ns0:DtReport>
But when I import the test MDN message that we received it has key and value elements underneath the tag 'specificData'. How do I get these two elements from external definitation?? Anything that I should in External References??
How does the following 'Alerts Settings' work from sender AS2 Reports adapter:
Enable alerts
Negative transmission report alert
Negative delivery repot alert
Negative receipt report alert
Thanks,
Riya

Here is the XSD:
?xml version="1.0" encoding="ISO-8859-1"?
xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:att="http://uri.seeburger.com/bisas/message/schema" xmlns:tns="http://uri.seeburger.com/dt/master/schema" xmlns="http://uri.seeburger.com/dt/master/schema" targetNamespace="http://uri.seeburger.com/dt/master/schema" elementFormDefault="qualified" attributeFormDefault="unqualified"
     xsd:import namespace="http://uri.seeburger.com/bisas/message/schema" schemaLocation="attachments.xsd" /
     xsd:include schemaLocation="dtglobaltypes.xsd" /
     xsd:include schemaLocation="dtarchiving.xsd" /
     xsd:element name="DtReport" type="tns:DtReportType" /
     xsd:complexType name="DtReportType"
          xsd:sequence
               xsd:element name="clientId" default="000" type="tns:stringLength3Type"
                    xsd:annotation
                         xsd:documentation
                         Logical System ID
                         /xsd:documentation
                    /xsd:annotation
               /xsd:element
               xsd:element name="correlationId" type="tns:uuidType" /
               xsd:element name="category" type="tns:reportCategoryType" /
               xsd:element name="state" type="tns:reportStateType" /
               xsd:element name="finalReport" type="xsd:boolean"
                    xsd:annotation
                         xsd:documentation
                         True if this report is the last one for the given correlationId
                    E.g. if this report is a deliveryReport but there is also a remaining ReadReceipt, then finalReport would have the value 'false'
                         /xsd:documentation
                    /xsd:annotation
               /xsd:element
               xsd:element name="freeText" type="xsd:string" minOccurs="0" /
               xsd:element name="specificData" type="tns:keyValueType" minOccurs="0" maxOccurs="unbounded"
                    xsd:annotation
                         xsd:documentation
                         Optional report data specific to the components and protocols
                         /xsd:documentation
                    /xsd:annotation
               /xsd:element
               xsd:element name="reportAttachment" type="att:AttachmentRefType" minOccurs="0"
                    xsd:annotation
                         xsd:documentation
                         Optionally holds the report as attachment in its raw format.
                         /xsd:documentation
                    /xsd:annotation
               /xsd:element
               xsd:element name="archiving" type="tns:archivingType" minOccurs="0" maxOccurs="unbounded" /
          /xsd:sequence
     /xsd:complexType
     xsd:complexType name="responseReportHandlingType"
          xsd:annotation
               xsd:documentation
               Information in a DtResponse about the report handling of the sent payload.
               /xsd:documentation
          /xsd:annotation
          xsd:sequence
               xsd:element name="reportsExpected" type="xsd:boolean"
                    xsd:annotation
                         xsd:documentation
                         True if at least one report is pending (false if the one and only report is contained in response).
                         /xsd:documentation
                    /xsd:annotation
               /xsd:element
               xsd:element name="expectedReports" type="tns:expectedReportsType" minOccurs="0" maxOccurs="unbounded"
                    xsd:annotation
                         xsd:documentation
                         List of expected reports - also including the one optionally included in the response.
                        If reportsExpected is true then this list must contain at least one entry, else it must be empty.
                         /xsd:documentation
                    /xsd:annotation
               /xsd:element
               xsd:element name="dtReport" type="tns:DtReportType" minOccurs="0"
                    xsd:annotation
                         xsd:documentation
                         Optional report if it was synchronously received.
                         /xsd:documentation
                    /xsd:annotation
               /xsd:element
          /xsd:sequence
     /xsd:complexType
     xsd:complexType name="initiationReportHandlingType"
          xsd:annotation
               xsd:documentation
               Information in a DtRequestInitiation about the report handling of the received payload.
               /xsd:documentation
          /xsd:annotation
          xsd:sequence
               xsd:element name="reportsExpected" type="xsd:boolean"
                    xsd:annotation
                         xsd:documentation
                         True if at least one report was requested.
                         /xsd:documentation
                    /xsd:annotation
               /xsd:element
               xsd:element name="preparedReports" type="tns:preparedReportsType" minOccurs="0" maxOccurs="unbounded" /
          /xsd:sequence
     /xsd:complexType
     xsd:complexType name="expectedReportsType"
          xsd:sequence
               xsd:element name="category" type="tns:reportCategoryType" /
               xsd:element name="timeoutDate" type="xsd:dateTime" /
               xsd:element name="deliveryState" type="tns:deliveryStateType" /
          /xsd:sequence
     /xsd:complexType
     xsd:complexType name="preparedReportsType"
          xsd:sequence
               xsd:element name="category" type="tns:reportCategoryType" /
               xsd:element name="timeoutDate" type="xsd:dateTime" minOccurs="0" /
               xsd:element name="reportMessage" type="att:AttachmentRefType" /
          /xsd:sequence
     /xsd:complexType
     xsd:simpleType name="reportCategoryType"
          xsd:restriction base="xsd:NCName"
               xsd:enumeration value="DeliveryReport"
                    xsd:annotation
                         xsd:documentation
                         Report informing about the state of the delivery on a physical base
                         /xsd:documentation
                    /xsd:annotation
               /xsd:enumeration
               xsd:enumeration value="ReceiptReport"
                    xsd:annotation
                         xsd:documentation
                         Report informing about the state of the receipt on a semantic base
                         /xsd:documentation
                    /xsd:annotation
               /xsd:enumeration
               xsd:enumeration value="TransmissionReport"
                    xsd:annotation
                         xsd:documentation
                         Report informing about the state of the transmission on a physical base
                         /xsd:documentation
                    /xsd:annotation
               /xsd:enumeration
          /xsd:restriction
     /xsd:simpleType
     xsd:simpleType name="deliveryStateType"
          xsd:restriction base="xsd:NCName"
               xsd:enumeration value="DELIVERED"
                    xsd:annotation
                         xsd:documentation
                         Delivery proceeded
                         /xsd:documentation
                    /xsd:annotation
               /xsd:enumeration
               xsd:enumeration value="PENDING"
                    xsd:annotation
                         xsd:documentation
                         Delivery pending
                         /xsd:documentation
                    /xsd:annotation
               /xsd:enumeration
          /xsd:restriction
     /xsd:simpleType
     xsd:simpleType name="reportStateType"
          xsd:restriction base="xsd:NCName"
               xsd:enumeration value="SUCCESS"
                    xsd:annotation
                         xsd:documentation
                         Positive report
                         /xsd:documentation
                    /xsd:annotation
               /xsd:enumeration
               xsd:enumeration value="FAILURE"
                    xsd:annotation
                         xsd:documentation
                         Negative report
                         /xsd:documentation
                    /xsd:annotation
               /xsd:enumeration
               xsd:enumeration value="EXPIRED"
                    xsd:annotation
                         xsd:documentation
                         No report received in time
                         /xsd:documentation
                    /xsd:annotation
               /xsd:enumeration
          /xsd:restriction
     /xsd:simpleType
/xsd:schema
Edited by: Riya Patil @SAP on Feb 4, 2010 9:05 PM
Edited by: Riya Patil @SAP on Feb 4, 2010 9:05 PM

AS2 Receiver Adapter Error

Hello,
when trying to send a message using Seeburger AS2 Receiver Adapter I get the following error (strange thing is that it worked before we made some changes, now we changed back and the error occurs):
Description: AS2 Adapter failure MessageId entry with secondaryId <xxxxxxxxxxxxxxxxxxxxxxxx> does not exist! com.seeburger.as2.AS2Plugin.execute
The error message is not meaningful to me. I tried all possible combinations but with no result. What could be the reason for this?

Hi,
Is your issue solved? Can you check the connection without using Certificates. Looks like issue with Certificates.
>> When I uncheck the button the flag "SIGN" in the as2 receiver comm channel. The message is sent out to the partner and we get back a negative acknowledgement (also there is an error MIC not verified in comm chan. ). So maybe it is a problem with digital signature? I have checked the receiver agreement, everything there should be fine
Is your scenario is AS2>XI>AS2 and using Certificates to exchange the messages?
please deactivate the use of dynamic attributes in the AS2 receiver channel. The dynamic attributes are set in the sender channel, there-fore the receiver channel overwrites the data given in the commchannel configuration with the data from the sender channel. Therefore, this is an issue specific for AS2 -> XI -> AS2 scenarios. Your partner might use the wrong certificate or not find the certificate because of the wrong payload name that was initially set in the sender channel.
Can you please check the Message Subject and Content Type how it is going using certificates and without using Certificates.?
-Deepthi.

AS2 Sender adapter

Similar Messages

Maybe you are looking for