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

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

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

  • Problems with Seeburger FTP Receiver adapter

    Hello,
    I am working on a scenario sending ORDERS05 Idocs to EDI vendors.
    For this i have configured Seeburger Receiver FTP adapter with 2 modules to convert XML-EDI format. Since this is the test, I have pointed Seeburger to local FTP server with following settings
    Hostname <Hostname of our FTP server>
    Port <Port # of our FTP server>
    Host Path/VAN partner id <some local directory of FTP server>
    Payload mode: Maindocument.
    At runtime i received following exception
    Message could not be forwarded to the JCA adapter. Reason: Fatal exception: javax.resource.ResourceException: >> Description: com.seeburger.jftp.app.exception.FtpExceptionSoftProcessingError: Unexpected reply: 500 'SITE system 1': command not understood>> Details: com.seeburger.jftp.app.exception.FtpExceptionRethrowError: Error in session: {type:FTPConnectionId}{binding:82ea8d3089dc3e898ae2e608d9d8487d}{channel:a52d1aaa8dd63ff59c2f590e78586a77}{toparty:TestEDIParty} CAUSED BY: com.seeburger.jftp.app.exception.FtpExceptionOpenConnectionError: Error while connection to remote host CAUSED BY: com.seeburger.jftp.app.exception.FtpExceptionRethrowError: Error while executing command QUOTE site system 1 CAUSED BY: com.seeburger.jftp.app.exception.FtpExceptionSoftProcessingError: Unexpected reply: 500 'SITE system 1': command not understood>>SendingStatus: NOT_TRANSMITTED>>FaultCategory: COMMUNICATION_ERROR>>Retryable: true>>Fatal: true
    Few questions related to this
    1] can we use Seeburger adapter to generate EDI files on local FTP server
    2] If not Seeburger can we use normal File adapter to do the same. I tried the same by configuring BIC module in File adapter so that it would convert XML to EDI format and was hoping file to be generated on FTP server. It generated one line XML file with following text "<info>Converted message locates in a attachment</info>". Any idea how to retreive attachments in File receiver adapter (as far as i know no attachments are supported in File receiver adapter).
    Any idea how to generate EDI files with Seeburger FTP on test server?
    Thanks in advance.
    Regards
    Rajeev

    Hi Rajeev,
    > 1] can we use Seeburger adapter to generate EDI files on local FTP server
    Yes we can use.
    > Any idea how to generate EDI files with Seeburger FTP on test server?
    It is like a normal process, how to generate the EDI files in normal means without FTP. Check this link
    https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/10b17369-9522-2c10-84a6-d75d8a8ace22
    BIC
    https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/00b66651-eeea-2b10-e5a6-8459ec30d948
    Regards
    Ramesh

  • Configuring a Seeburger FTP Receiver Adapter

    Hello,
    I am trying to build a scenario where SAP ECC 6 sends an invoice to a customer via EDI.
    We are using ECC 6.0 and PI 7.0 and the Generic Seeburger EDI Adapters. The VAN is a GEIS EDISWITCH VAN (Eircom in Ireland).
    I am able to successfully send an IDoc from ECC 6 and into PI where a Seeburger map converts the message to EDI-XML format. I can use a file adapter to create a file in normal EDI format. But I can't get the Seeburger FTP adapter to work with the VAN.
    I have configured the correct IP, port, username and password but I keep getting the following message when the communication channel tries to send the message:
    <h6>Message processing failed. Cause: javax.resource.ResourceException: Fatal exception: com.sap.aii.af.ra.cci.XIRecoverableException: >> Description: com.seeburger.jftp.app.exception.FtpExceptionSoftProcessingError: Unexpected reply: 501-Syntax errors in parameter.    usage: %[recipient id]%[APRF]       where either [recipient] or [APRF] can be omitted.           (to change your current default SEND relationship).           %% (places you in your 'HOME' TR).   &['s'|'single'] ('get' command gets single file).   &['m'|'multiple'] ('get' command gets multiple files). >> </h6>
    The FTP session is expecting a PUT command with the recipient id and APRF as parameters but these are not getting passed. I suspect this is because I am not passing the correct variables to the receiver adapter but I don't know what variables it expects and where they should be specified. And I can't find the answers in the documentation.
    Can anyone shed some light on what I need to do?
    Thanks,
    Ben

    Hi Prateek,
    Thanks for your comments. The channel is set to GEIS(GeMarkIII). There is nowhere to specify a directory or filename. The settings I have used are as follows:
    Adapter Type: FTP (http://seeburger.com/xi)
    Receiver
    Transport Protocol: FTP
    Message Protocol: GEIS/GeMarkIII
    Adapter Engine: Integration Server
    Host name: <IP address of VAN server>
    port: 21
    User Id: <Our mailbox number>
    Password: <Correct password>
    Host path/VAN Partner ID: <blank>
    Script file: <blank>
    Transfer type: ASCII
    Connection mode: Passive
    Use keep alive: <Not checked>
    Security Mode: None
    Proxy Mode: none
    Resource ID: <blank>
    Deliver transmission report: <not checked>
    Payload mode: Attachment
    Attachment ID: SeeburgerMain
    Channel status: Active
    Use dynamic attributes: <Checked>
    Use non-empty attributes: <Checked>
    Request displayed report: <Not checked>
    Request dispatched report: <Not checked>
    Report timeout (minutes): 720
    Handle received reports: Refer reports to XI system
    There is nowhere in the communication channel configuration that allows me to specify the receiver ID or the APRF. The documentation say this is read from the EDI data and the relevant fields are populated.
    Any ideas?
    Thanks,
    Ben

  • Seeburger As2 Receiver channel exception for large files

    Hello Folks,
    We have JMS to seeburger AS2 interface we are facing follwing issue in As2 reciver channel for files larger than 20 MB.But In Production it is wokring fine for even 40 MB also.
    Delivering the message to the application usingconnection 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: org.apache.commons.httpclient.ProtocolException: Unbuffered entity enclosing request can not be repeated. # , SEEBURGER AS2:org.apache.commons.httpclient.ProtocolException: Unbuffered entity enclosingrequest can not be repeated. # .
    Please through some light on the issue .
    Regards
    Praveen Reddy

    Hi Praveen,
    The problem would be related to server size. genrally test system do not have same sizing as production server due to that you can not process large files in test system.
    check the sizing of the system.
    regards,
    Harish

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

  • Seeburger sFTP receiver adapter error: Socket Write Error, EOF Received

    Hello experts,
    We have a sFTP to sFTP scenario for which we are getting below error every time the scenario is executed.
    Error Messages are as follows:
    Put File: Could not connect to remote host, Reason: Unexpected termination; software caused connection abort; socket write error[unknown cause].
    Sometimes below error occurs :
    Put File: Could not connect to remote host, Reason: EOF received from remote side [unknown cause].
    Every time after restart of sFTP adapter on XI box, failed messages are sent successfully to receiver sFTP server.
    There is no error for sender sFTP channel. This error occurs only for the receiver sFTP channel.
    On receiver sFTP side, we are using Public key-private key authentication.
    Can anyone please let me know what could be the cause of connection failure. ?
    Thanks a lot in advance!
    (I searched many threads on SDN but could not find anything relevant to this particular situation, so posting a separate question.)
    Minal

    Thanks Naveen for the reply..
    I missed to mention that we are working on XI3.0 with SP19 and seeburger sFTP is 1.7.4
    Looks like key exchange is working properly as after every restart of adapter all failed messages are processed successfully..
    It is observed that if there is an idle time of 8-10 hours between last data transfer and current data transfer then this error occurs.
    We have increased connection timeout and transmission timeout parameters also for sFTP properties in visual admin.
    Thanks,
    Minal
    Edited by: Minal Vaidya on Oct 5, 2011 8:46 AM

  • 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

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

  • Seeburger - async receiving MDN problem- no binding found for AS2

    Hi guys!
    We have configured AS2 receiver adapter but during receiveing Async MDN we get following error (sending of message is successful) :
    Cannot receive async MDN: com.seeburger.as2.exception.AS2PluginException: Inbound communication from 90586 to 22266 not allowed: com.seeburger.conf.BackingStoreException: Unable to execute query because: com.seeburger.xi.config.ConfigException: No binding found for: AS2, http://seeburger.com/xi, Gloria, R3
    Note: Gloria & R3 are names of XI identifiers (scheme: XIParty) and 22266 & 90586 are names from AS2ID scheme - alternative identifiers.
    22266 - is sender of original message
    90586 - is receiver
    What is wrong on the settings? Why the sending message uses alternative identifiers and incoming MDN does not?
    Thanx for answers & suggestions!
    Peter

    Hi Peter
    checkm this thread discuss the same ..... hope it will solve ur all querry
    Seeburger AS2 Adapter No binding found for: AS2, http://seeburger.com/xi
    Thanks !!!
    Questions are welcome here!!
    <b>Also mark helpful answers by rewarding points</b>
    Thanks,
    Abhishek Agrahari

  • SEEBURGER AS2: AS2 Adapter failure -- CryptoApiException: Access Denied.

    Hi,
    I am trying to send AS2 message to my partner by using Certificates and I am getting the following error at AS2 receiver adapter.Looks like it doesn't have User Credentials to access the certificates.But we provided all the details.We are not sure where it is going wrong.
    2008-08-30 14:49:42 Error Unable to forward message to JCA adapter. Reason: Fatal exception: com.sap.aii.af.ra.cci.XIRecoverableException: SEEBURGER AS2: AS2 Adapter failure # java.lang.Exception: AS2 message composition failed:com.seeburger.ksm.cryptoapi.exception.CryptoApiException: Access Denied., SEEBURGER AS2: AS2 Adapter failure # java.lang.Exception: AS2 message composition failed: com.seeburger.ksm.cryptoapi.exception.CryptoApiException: Access Denied.
    Can anyone please suggest us what is missing and where it is going wrong?
    Regards
    Stephano

    Hi,
    1) First of all create the Seeburger Certificates.
    2) You have to deploy those certiates in your Visual Administrator.
    After that in  Interration Builder -
    > Receiver Agreement -
    > In Security Settings -
    >
                       AS2 Sender Configuration -
    > Signing Key -
    >give the certificate name over there.
                       AS2 Sender Configuration -
    > Encription Certificate & Authenitication Certificate is there
                       u have to give u r certificate names over there.
    Thanks,
    Satya Kumar

  • Error in AS2 RCV adapter.. SEEBURGER AS2: 307 Temporary Redirect #

    Hi all,
    Iam just doing File to File scenario and passing the resultant file to Partner system through AS2 adapter.
    I gave the following details in AS2 RCV adapter..
    SND>XI->Webdispatcher--->Partner.
    My message will be reached to webdispatcher.. from there it will route to Partner Url.
    So i will be giving my webdispatcher URL in my AS2 RCV adapter.
    TP : HTTP
    MP : AS2
    Server : vvvvvv.com.NZ
    Port : 50000
    Url :  /as2gs1/partnera
    Message is processed succesfully but its failing in AS2 RCV adapter with following error.
    Success      SEEBURGER/AS2: Received order from system.
    Error      Unable to forward message to JCA adapter. Reason: Fatal exception: com.sap.aii.af.ra.cci.XIRecoverableException: SEEBURGER AS2: 307 Temporary Redirect # , SEEBURGER AS2: 307 Temporary Redirect #
    Error      MP: Exception caught with cause javax.resource.ResourceException: Fatal exception: com.sap.aii.af.ra.cci.XIRecoverableException: SEEBURGER AS2: 307 Temporary Redirect # , SEEBURGER AS2: 307 Temporary Redirect #
    Error      Exception caught by adapter framework: Fatal exception: com.sap.aii.af.ra.cci.XIRecoverableException: SEEBURGER AS2: 307 Temporary Redirect # , SEEBURGER AS2: 307 Temporary Redirect #
    Error      Delivery of the message to the application using connection AS2_http://seeburger.com/xi failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: Fatal exception: com.sap.aii.af.ra.cci.XIRecoverableException: SEEBURGER AS2: 307 Temporary Redirect # , SEEBURGER AS2: 307 Temporary Redirect # : javax.resource.ResourceException: Fatal exception: com.sap.aii.af.ra.cci.XIRecoverableException: SEEBURGER AS2: 307 Temporary Redirect # , SEEBURGER AS2: 307 Temporary Redirect #.
    Error      The message status set to NDLV.
    Kindly let me know if anyone know th solution.
    Regards
    Seema.

    Hi Peter,
    >> a, what do you mean with the Web Dispatcher?
    We are not using the partner URL directly.We will be using Webdispatcher URL .. from there they have written the rule to goto Partner URL.
    >> b, you receive a HTTP code 307, which means that the target AS2 location has been moved. Try to connect the target AS2 server on the URL and check, if it is really there and if it is working.
    Looks like this is working.. its showed success state for a while and after few minutes.. its showing the below error in communication channel monitoring.
    Delivery of the message to the application using connection AS2_http://seeburger.com/xi failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: Fatal exception: com.sap.aii.af.ra.cci.XIRecoverableException: SEEBURGER AS2: java.net.SocketException: Connection timed out:could be due to invalid address # , SEEBURGER AS2: java.net.SocketException: Connection timed out:could be due to invalid address # : javax.resource.ResourceException: Fatal exception: com.sap.aii.af.ra.cci.XIRecoverableException: SEEBURGER AS2: java.net.SocketException: Connection timed out:could be due to invalid address # , SEEBURGER AS2: java.net.SocketException: Connection timed out:could be due to invalid address #.
    This is the error it is showing in Seeburger Monitoring.
    State                          : Error on send, will be retried
    Status Description  : Could not deliver as2 message to partner: java.net.SocketException: Connection timed out:could be due to invalid address # null
    What is this error?
    Do u think there is no problem with AS2 adapter.. its the problem wit webdispatcher.??
    Waiting for your reply.
    -Seema.

Maybe you are looking for