AS2 receiver adapter seems to be transmitting duplicate message to Partner

Hello guys,
we have serious issue in prod. we have a partner with whom we share EDI data using As2 adapter.
let me take eg here
our AS2 id- AAA
partner AS2 id - DDD
first we had problem with them
"could not send asynchron mdn to partner url" but before we rectified this issue ,DDD has upgraded the As2 sofware which solved current issue but created different issue which is described below :
as per partner ,messages are sent twice from AAA to DDD . but AAA is claiming that they dont send duplicate messages
as per DDD sometime they receive whole set of message twice. which AAA cant see at all at their side. but AAA do receive MDN back but with error "MIC not verified # duplicate-document"
so now AAA also have doubt that why the messages are rejected from the DDD when AAA is not sending the duplicate.
but anyone has encountered this problem before ???

Hi Rai,
I have a similar problem.
AAA is send AS2 to DDD and from time to time (not always) I get back an AS2 notification saying
MIC not verified # duplicate-document
Did you find the solution on this?
Regards,
Luis.

Similar Messages

  • 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.

  • What is "delivery transmission report" checkbox on AS2 receiver adapter?

    Hi Gurus,
    we have an AS2 adapter from seeburger and there is a checkbox on receiver adapter "delivery transmission report". What is this good for?
    Thank you,
    Olian

    Hi Olian,
    If you check this box you'll receive a "special transmission report is delivered to the report channel". I know this description is really vague but I've been comparing this transmission report and a delivery report. The delivery report is the MDN itself, referring to whom you've sent the message, the messageID and to the channelID.
    Hope it helps....

  • AS2 Receiver Adapter

    Hi,
    My scenario is IDOC to AS2 ... AS2 Adapter  need to send a Fixed Length file as an attachment in AS2 Adapter.
    Kinldy let me know any one can help me.

    Hi,
    You need to change the *XI Message as 'Attachement' in the comms channel and then use the EJB in the module tab of the comms channel  to send the attachment.
    Regards,
    Vishal

  • Seeburger AS2 receiver adapter conf PI 7.1

    Dear All,
    I have seen a changed AS2 adapter on PI 7.1,the options are totally different than what we have in previous version of AS2 adapter.
    I am looking for seeburger AS2 adapter documents and configuration steps for PI7.1 version.
    Any inputs...
    chirag
    Edited by: Chirag Gohil on Sep 8, 2010 5:03 AM

    AS2Receiver:
    ModuleName: localejbs/ModuleProcessorExitBean
    Type: Local Enterprise Bean
    Module Key: Exit
    -_Module Parameter_-
    Module Key: Exit
    Parameter Name: JNDIName
    Parameter Value: deployedAdapters/SeeXIAS2/shareable/SeeXIAS2
    -_Parameters Tab_-
    HTTP
    Server - Computer with listening AS2 Server
    Port - Port of the endpoint with listening AS2 Server
    URL Path - Path to the endpoint with listening AS2 server
    HTTP Timeout - Timeout in seconds for waiting for server's response
    HTTP Keep Alive - If enabled, the HTTP session is re-used. This optimizes the performance.
    Basic Authentication
    User - User for basic authentication
    Password - Password for basic authentication
    Realm - Realm for basic authentication
    Proxy
    Proxy Server - Your proxy server
    Proxy Port - The port of the proxy server
    Proxy User - User for optional authentication
    Proxy Password - Password for optional authentication
    Proxy Protocol - Select either - HTTP 1.0 or -HTTP 1.1
    AS2
    Compress - Select this option if the payload is to be compressed
    Sign - Select this if the payload is to be signed
    Signing Algorithm - Select an algorithm which is applied for signing the payload; we recommend "SHA-12"
    Encrypt - Select this, if the payload is to be encrypted
    Encryption Algorithm - Select an algorithm that is used for encrypting the payload; we recommend "RC2/128" or "3DES"
    MDN Mode - SYNC to request a synchronous MDN; ASYNC to request an asynchronous MDN; NONE if no MDN is required
    Receipt Delivery Address - Enter the URL of the Asynchronous MDNs that are to be delivered (i.e. the URL of your own AS2 server)
    MDN Timeout - Enter a time period (in min), after which an outstanding asynchronous MDN will be interpreted as an error. The value "0" means no timeout
    Sign MDN - Select this option, if the MDN is to be signed
    Message Subject - This text is sent to the server within the optional HTTP header "subject"
    Content Type - The content type should be set. A random content type can be set, but we recommend one of the following
    = "application/edifact" for EDIFACT files
    = "application/edi-x12" for ANSI X.12 files
    = "application/xml" for XML files
    = "text/plain" for plain text files
    = "application/octet-stream" for arbitrary binary files
    Delivery transmission report - A special transmission report is delivered to the report channel

  • Creating Flat file using AS2 Receiver adapter

    Hello everyone
    This is my first AS2 scenario,we are sending 850/Purchaser order  information from SAP to partner.
    what is the processing sequence and module configuration parameters we need to mention for converting the target structure to flat file?
    Regards
    Uday

    Try to search Seeburger scenarios on SDN. There are many blogs and wikis availble now. There you may refer to BIC, classifier and split modules. Understanding of all these will help you in configuring the scenario. If you are stuck somewhere, come up with specific doubt.
    Regards,
    Prateek Raj Srivastava

  • File Receiver Adapter:Run Operating System COmmand after message Processig:

    Dear All,
    I have gone through this link
    [http://help.sap.com/saphelp_nw2004s/helpdata/EN/e3/94007075cae04f930cc4c034e411e1/content.htm]
    But i have a problem.
    In the scenario which we have, File name is DYNAMICALLY GENERATED by a UDF
    I want to call the file at run time after message processing via Command Line and execute some os commands.
    But since the file name is Dynamic....How will i call the file at run time in Command Line:
    SYNTAX: %f(FileName)
    How will i specify the file name in the above syntax as the file name is Dynamic and not constatnt.
    Please Advice.
    Senthilprakash.

    Dear All,
    Yes just now i got the answer from this thread[OS command line script - Need help;
    Actually i have another doubt now
    In REVEIVER FILE ADAPTER:
    when we give Run Operating system Command After Message processing
    does the OS command get executed after the output file is placed in the Receiver folder/server or before its placed in the receiver folder?
    Regards,
    Senthilprakash.

  • 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..  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.

  • FileName in the AS2 receiver?

    Hi Guys,
    we are sending a file to the partner with the AS2 and we want to maintain the same file name as the sender. I dont see any adapter specific attributes in the AS2 adapter.
    How can i maintain the same file in the AS2 receiver adapter. any help or suggestions would be appreciated
    Thanks,
    Srini

    Hi sarvesh,
    The problem is resolved using the seeburger AttributeMapper module.
    Thanks,
    Srini

  • Dynamic subject in AS2 receiver

    hi experts,
        I have a scenario in which i am sending data to third party using AS2 adapter.
    My scenario is PROXY->XI->AS2. In AS2 receiver adapter I need to use dynamic subject.
    For that I have used adpater module  "localejbs/Seeburger/AttribMapper"
    *PARAMETER NAME:-- http://seeburger.com/xi/common/dtSubject*
    PARAMETER VALUE:--  DYNSUBJECT
    while mapping in IR I am passing one field(strSubject)  as  input data to the below code:-
    DynamicConfiguration conf = (DynamicConfiguration) container.get(StreamTransformationConstants.DYNAMIC_CONFIGURATION);
    DynamicConfigurationKey keySubject = DynamicConfigurationKey.create( "http://seeburger.com/xi/common/dtSubject", "DYNSUBJECT");
    conf.put(keySubject, strSubject);
    The value of strSubject should be the subject in AS2 message.
    The scenario is working fine but I m getting below error in communication channel:
    Exception caught by adapter framework: AttribMapper:Could not evaluate expresion DYNSUBJECT . Error: Unexpected token <EOT> at position 0. ( expected
    Help will be appreciated
    Thanks
    Jaideep

    Let me expalin you the complete thing.
    In mapping i m using this UDF for dynamic subject.
    DateFormat dfCurrentDate = new SimpleDateFormat("yyyy-MM-dd");
    DateFormat dfCurrentTime = new SimpleDateFormat("HH:mm:ss.SS");
    Date dCurrentDate = new Date();
    String strCurrentDate = dfCurrentDate.format(dCurrentDate) + "T" + dfCurrentTime.format(dCurrentDate) + "Z";
    String strSubject="Literal"+ "_" + strCurrentDate;
    // Dynamic Subject
    DynamicConfiguration conf = (DynamicConfiguration) container.getTransformationParameters().get(StreamTransformationConstants.DYNAMIC_CONFIGURATION);
    DynamicConfigurationKey keySubject = DynamicConfigurationKey.create( "http://seeburger.com/xi/common/dtSubject", "DYNSUBJECT");
    conf.put(keySubject,strSubject);
    return "";
    In receiver service I have used "localejbs/Seeburger/AttribMapper" module.
    Parameter name  http://seeburger.com/xi/common/dtSubject
    Parameter value  @http://seeburger.com/xi/common/dtSubject/DYNSUBJECT
    In moni I can see the dynamic configuration tab(neither Tab nor value)
    But in RWB comm. channel monitoring I can see in Audit log but not in SOAP document.
    Hope i have cleared you..
    Thanks
    Jaideep

  • Error while updating database using jdbc receiver adapter

    Hi All,
    I am trying to update a single record using jdbc receiver adapter.
    This is my the message that is getting created..
    <?xml version="1.0" encoding="UTF-8" ?>
    - <ns0:Data xmlns:ns0="urn:Test">
    - <STATEMENT>
    - <TABLENAME ACTION="UPDATE_INSERT">
      <TABLE>ORDERS</TABLE>
    - <ACCESS>
      <OrderID>99999</OrderID>
      <CustomerID>VICTE</CustomerID>
      <EmployeeID>3</EmployeeID>
      <ShipAddress>VICTE</ShipAddress>
      </ACCESS>
    - <KEY>
      <OrderID compareOperation="EQ">99999</OrderID>
      <ShipAddress compareOperation="EQ">VICTE</ShipAddress>
      </KEY>
      </TABLENAME>
      </STATEMENT>
      </ns0:Data>
    But in Adapter Monitoring i am getting the following error..
    <i>Error while parsing or executing XML-SQL document: Error processing request in sax parser: Error when executing statement for table/stored proc. 'ORDERS' (structure 'STATEMENT'): java.sql.SQLException: [Microsoft][ODBC SQL Server Driver][SQL Server]Line 1: Incorrect syntax near 'VICTE'.</i>
    Regards,
    Rahul

    Rahul,
    > In this case i believe the interface has to be synch.
    > So what will the response message type be like..
    Not necessary. UPDATE can be asynch as well.
    Can you turn the trace on like pointed by Michal and then you can see the Query in the Audit Log of the adapter montioring. Try to execute the same query from your DB Client like TOAD and see what is the Syntax error you are getiing.!
    The problem looks like some field has some dataype / column name mismatch.
    Regards
    Bhavesh

  • JMS Receiver Adapter to MQ - additional message property error

    Hi,
    I'm trying to add addional message properties to a Receiver JMS message for MQ Server queue. Creating the message in the MQ queue only works when I don't try to
    add additional message properties. As soon as I try to add additional message properties the XI-Monitor says it's OK but there is no message in the queue.
    Our system constellation is a bit odd cause we implemented the JMS/MQ classes of release 5.3 in XI/J2EE.
    Our actual used MQ Server is on release 5.1 due to compatibilty reasons of other productive software.
    Is there a need to use a MQ server of release 5.3 ?
    Has anybody a step by step description for implementing a JMS receiver Adapter for MQ with with additional message property (f.ex. mesType = salesOrder) in the MQ header?
    Thanx a lot in advance
    Hans

    Hi,
    You also might want to look at sap note 856346...for this ..
    2.6) I am connecting to a JMS provider using JNDI mode. How do I add pass an extra name,value property pair while setting up the JNDI initial context?
    Answer: Assuming that your property value is a string, please add the following name, value pair in "JMS Additional properties" table of your channel configuration:
    JNDI.InitialContext.property.X=java.lang.String propertyName, java.lang.String propertyValue
    where X is a number, the LHS part needs to be put in the name column and the RHS part in the value column of the table respectively.
    This note covers frequently asked questions that arise during the installation, configuration or administration of the XI JMS Adapter from the Adapter Framework (AF).
    Other terms
    JMS - Java Message Service
    AF - Adapter Framework
    AE - Adapter Engine
    SP - Service Pack
    Reason and Prerequisites
    This note clarifies the frequently asked questions on the XI/PI JMS adapter for released 3.0, 7.0 and 7.1 in the form of an FAQ. References to external information is provided at the end.
    Solution
    1. Documentation
    1.1) Where do I find the JMS adapter documentation?
    Answer: In the SAP online help. Go to http://help.sap.com and select  SAP Netweaver-> SAP Netweaver 7.1 or SAP NetWeaver 7.0 (2004s) or SAP Netweaver 2004. This opens up SAP Library topic page for that release.
    For releases 3.0 and 7.0:
    Select SAP Netweaver Library -> SAP Netweaver by Key capability-> Process Integration by Key Capability -> SAP Netweaver Exchange Infrastructure -> Runtime -> Connectivity -> Adapters -> JMS Adapter.
    For releases 7.1:
    Select SAP Netweaver Process Integration 7.1 -> SAP Netweaver Process Integration Library -> Function Oriented View > Advanced Adapter Engine.
    In the topic page click on the JMS Adapter link.
    Alternatively, you may simply enter the search string "JMS adapter" and navigate to the documentation page directly from the relevant search results. This is much faster.
    1.2) Which JMS providers are supported?
    Answer: The JMS Adapter supports JMS 1.02b and 1.1. JMS providers that also claim to be compatible with JMS 1.02b or 1.1 can be accessed using the JMS Adapter.
    Furthermore, SAP makes no assertions as to whether a particular JMS provider is tested or can be recommended, because SAP has not set up a certification or testing process.
    2. Functions and architecture
    2.1) Does the JMS Adapter support JMS topics (publish&subscribe)?
    Answer: No. Currently the JMS Adapter works with JMS queues because 100% Exactly Once (In Order) service quality can only be guaranteed with  JMS queues. However, this capability might be planned for introduction at a future release. (no planned time estimate)
    2.2) I have JMS message properties that are of significant. How do I get this data into XI? How do I get this data out of XI?
    Answer:
    A feature generically referred to as XI adapter-specific message properties was introduced in the adapter framework. This allowed additional adapter information to be attached to a XI message which can be used the routing, mapping and BPE. The message properties of different adapters are differentiated by namespaces.
    If you are on XI 3.0 support pack 18 onwards, the JMS adapter allows you to copy JMS message properties into these XI adapter specific message properties (at the sender JMS channel), and to copy the values of XI adapter specific message properties back into JMS message properties (at the receiver JMS channel).
    The JMS adapter currently supports upto 10 JMS message properties to be copied into the XI message properties with the name DCJMSMessageProperty0 to DCJMSMessageProperty9. The configuration details of how to achieve this are explained in the sub-topic pages of the JMS adapter documentation. (See sub topics: "Configuring the Sender JMS adapter", "Configuring the Receiver JMS adapter")
    JMS Message properties can have values belonging to types: boolean, byte, short, int, long, float, double, and String (defined in the specification). These are all normalized to strings when converted to the their respective XI message properties at the sender JMS channel.
    However, in the receiver JMS channel configuration, you can enter specific JMS message property types, such that these normalized XI message properties may be coerced back into their original types (or any compatible JMS message property type) when translating a XI message into a JMS message.
    Transfer of custom JMS Message properties from/to XI adapters-specific message attributes is only supported for JMS compliant messages, i.e. this feature will not work for Websphere MQ in legacy mode.
    Deprecated Information on this feature
    Between support pack 14 to support pack 18, the JMS adapter allowed the allowed you append only up to two JMS string properties to the XI message in the sender channel, which could then be analyzed in XI routing, mapping and BPE. In the JMS receiver channel, the XI adapter-specific message attributes could be read, and up to two JMS string properties could be set. The names of the (now deprecated) XI message properties were DCJMSStringProperty1 and DCJMSStringProperty2.
    Regards
    Ravi Raman

  • How many messsages can we insert using JDBC receiver adapter in to DB

    Hi Friends,
    We are having 30 JDBC receiver interfaces in my current implementation project; load of JDBC receiver interfaces was 50 k messages per day and Performing only INSERT operation on data base.
    We have created individual communication channel for every JDBC receiver interface and max concurrency value set in CC was 5.
    Now we are testing all interfaces in quality with all possible cases, but we found that JDBC receiver adapter unable to process 50 k messages per day, we are on PI 7.1 EHP1 SP7.
    Please share your experiences with JDBC adapter receiver like per day how many messages we can transfer.
    Thanks a Ton,
    Raj

    Raja Sekhar Reddy T wrote:
    we are processing 50 k individual messages.
    >
    > I have increased max threads for JDBC receiver to 20 but no luck same rate only . My questions here is how many messages we can trasfer using JDBC receiver adapter?
    >
    > Regards,
    > Raj
    Hi raj,
    I have seen some interfaces that deal with upload of 5000 rows at a rime.. I don't there will be a restriction in the no of messages that can be transferred using the JDBC adapter as such  unless until the requirement is so para-normal and in your case it is not
    Kind regards
    XA

  • Service Number/Port Number in HTTP receiver adapter

    Dear Experts,
    I have a scenario where I am to do HTTP Post to a 3rd party web application via a url in the following format:
    https://x.y.info/abc/sap/customer.cgi
    The HTTP Post data is submitted to the CGI script which is then processed further by the web application. The URL works ok via IE or even PI soap receiver adapter is able to post XML message to the URL but using SOAP.
    But I have to do only HTTP Post and now my problem is that the URL dont have a so called port number that I can fill in the "Service Number" field in HTTP receiver channel or in SM59.
    Does SAP always need a service number or how to deal with this case where server doesnot expose the port.
    Thanks in advance.
    Br
    Suman

    Hello,
    The HTTP Post data is submitted to the CGI script which is then processed further by the web application. The URL works ok via IE or even PI soap receiver adapter is able to post XML message to the URL but using SOAP.
    By definition, the SOAP Adapter is also using HTTP POST as its HTTP method the only difference is that there is a SOAP Envelope that is being sent.
    But I have to do only HTTP Post and now my problem is that the URL dont have a so called port number that I can fill in the "Service Number" field in HTTP receiver channel or in SM59.
    Service number is the port number of the URL that you will be connecting to, if it is not shown, it is assumed that it is 80 for http and 443 for https (as Gzegorz mentioned). Since you are using HTTPs, you should use HTTP Destination that points to an SM59 configuration.
    Hope this helps,
    Mark

Maybe you are looking for