Seeburger AS2 Authentication

Hello,
Wanted to know in Seeburger AS2 Recv Adapter : while authneticating : what is realm field?
Realm signifies ?
Thank You

Hi,
Well "realm" i something like a "domain", ie. sometime you have logged in a PC which has other domain, so put this information:
user: PCDOMAIN\myuser
password: mypassword
"PCDOMAIN" is the realm.
I hope this helps you
Regards
Ivan

Similar Messages

  • 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

  • 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

  • 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

  • Seeburger AS2 Adapter:  Receiving multiple messages

    Hi guys,
    I'm having some trouble using AS2 Adapter for receiving multiple messages. The problem is really similar to Peter's problem.
    Seebuger AS2 adapter for XI as sender for multiple messages
    I have it configured for one scenario and it's working fine. The problem is when I'm trying to receive other messages for the same Party but different services. Meaning, I've one Party(example BMW) and several services (BMW_DE, BMW_USA, etc). I'm able to receive messages from service BMW_DE but when configuring BMW_USA I'm getting HTTP 403 Forbidden.
    This error may have different reasons:
    a) You or your partner has entered an incorrect AS2 ID for one of the involved parties.
    b) A valid sender agreement is missing.
    c) There are more then one AS2 sender agreements with the same sender AND receiver party.
    d) The corresponding inbound channel is set to inactive.
    And the problem is that there are two sender agreements. Although the services are different, XI is not able to find the correct sender agreement to be used. After deleting the second second agreement, I'm able to send the  respective message....
    Can anyone give me a hint on how to solve this problem?

    Hi,
    this is done by different AS2 subjects. The sender agreement is selected based on this. So create separate AS2 receiver adapters for every message you need and put there different message subjects.
    So if you'll have 3 AS2 receiver channels with subjects:
    MessageType1_DE
    MessageType1_US
    the AS2 adapter will work like following:
    first it tries to find an exact message subject, if it is found, message is "assigned" to this sender agreement. If no exact message matches the subject, then wildcards are used. (this mechanism is described in the Seeburger AS2 guide).
    If you are getting 403 HTTP code, there may be also problem with authentication certificates.
    Another problem may be, you don't have configured AS2 receiver channel for current subject.
    Does this help you? Or you meant it another way?
    Peter
    p.s. check the answer above my post, Vardharajan's right
    Edited by: Peter Jarunek on May 19, 2008 2:11 PM

  • SEEBURGER AS2: AS2 Adapter failure - Cannot authenticate the user

    Hello,
    All was working fine but now I got these errors in an AS2 scenario. Sending a message via AS2. Also we don't receive any messages via AS2 anymore. This is the error when sending a message:
    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: Cannot authenticate the user., SEEBURGER AS2: AS2 Adapter failure # java.lang.Exception: AS2 message composition failed: com.seeburger.ksm.cryptoapi.exception.CryptoApiException: Cannot authenticate the user.
    MP: Exception caught with cause javax.resource.ResourceException: 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: Cannot authenticate the user., SEEBURGER AS2: AS2 Adapter failure # java.lang.Exception: AS2 message composition failed: com.seeburger.ksm.cryptoapi.exception.CryptoApiException: Cannot authenticate the user.
    Exception caught by adapter framework: 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: Cannot authenticate the user., SEEBURGER AS2: AS2 Adapter failure # java.lang.Exception: AS2 message composition failed: com.seeburger.ksm.cryptoapi.exception.CryptoApiException: Cannot authenticate the user
    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: AS2 Adapter failure # java.lang.Exception: AS2 message composition failed: com.seeburger.ksm.cryptoapi.exception.CryptoApiException: Cannot authenticate the user., SEEBURGER AS2: AS2 Adapter failure # java.lang.Exception: AS2 message composition failed: com.seeburger.ksm.cryptoapi.exception.CryptoApiException: Cannot authenticate the user.: javax.resource.ResourceException: Fatal exception: com.sap.aii.af.ra.cci.XIRecoverableException: SEEBURGER AS2: AS2 Adapter failure.
    Please advice, many thanks!
    Erik

    Are you using the "Use Authentication" option in the communication channel? If yes, then ensure that the user provided is correct and is not locked. Also recheck the authentication certificate settings.
    Regards,
    Prateek

  • Seeburger AS2 Adapter scenario ?

    Hi Frnds,
    I want See Burger ,AS2 Adapter end to end scenario with screen shots, If anybody know link or having end to end scenario pls share to me its too urgent.
    Regards,
    Ravi kumar

    Hi ,
    Ravi, I am also looking for seeburger scenario, i got information from forum, i providing info, i hope it will give some idea... if its not excuse me....
    The SEEBURGER FTP/VAN Adapter is responsible for transmitting files according to the File Transfer Protocol, with the particular support of various VANs. This protocol was installed as a user gateway protocol by several of the largest VAN providers, such as IBM, GE and Sterling IIB and Sterling Commerce.
    The FTP/VAN adapter must be configured in the configuration part of the Integration Builder. The adapter is based on the Adapter Framework and is executed by the SAP J2EE Adapter Engine.
    The FTP/VAN Adapter supports the following protocols:
    • IBMIE VAN, all report options.
    • GEIS (GeMarkIII) and GeMark3000, all report options, report file is only extracted, if needed.
    • EXITE (ECODEX), EDIFACT file processing, DISPATCHED reports.
    • Sterling Commerce and Sterling IIB.
    • MCI EDI*Net.
    The following FTP options are supported:
    • SSL, both IMPLICIT and AUTH_TLS support, server authentication.
    • All popular FTP proxy types like: USERWL, USERWOL, SITEWL, OPENWOL.
    • Active and Passive connection modes.
    • "KeepAlive" feature.
    • Binary, ASCII and custom transfer types.
    Seeburger adapters like OFTPS,AS2,X400 are used for B2B scenario where the file is coming through WAn network or mailbox. As XI dont have capability to convert the EDIFACT format file to XML the same work will be done by seeburger adapters.
    The SEEBURGER Business Integration Converter (BIC) is an any-to-any format converter, used to translate EDI data and legacy data formats into XML and vice versa. It can also be used for complex, high performance XML-to-XML mappings or to interface to existing JDBC data sources.
    Supported EDI formats include:
    • ANSI
    • EDIFACT
    • INHOUSE
    • IDOC
    • XML Schema
    • XML DTD
    • CSV
    • Delimited Data
    • positional data
    • SWIFT
    • EANCOM
    and many more.
    See for converting the EDI XML to EDI and XML-EDI you need to have a seeburger mapping program at the adapter module which does the conversion. For this module you need a BIC tool of seeburger which provides the different module program for EDI to XML and XML-EDI. This program needs to be deployed on XI and through adapter it has to be called for conversion.
    AS2 vs OFTPS:
    AS2 & OFTPS
    /people/bla.suranyi/blog/2006/06/08/sap-xi-supports-edifact
    Please see the below blogs
    /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/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
    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
    https://www.sdn.sap.com/irj/sdn/forums
    /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
    EDI Adapter by SeeBurger
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/206e2b65-2ca8-2a10-edad-f2d1391644cb
    B2B(EDI) Integration using SAP Netweaver XI and Seeburger AS2 Adapter
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/00f9cdf5-d812-2a10-03b4-aff3bbf792bf
    Integrating XI with SeeBurger
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/6dc02f5d-0601-0010-cd9d-f4ff9a7e8c33
    Regards,
    Raj

  • 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 - message does not arrive when "Athentication required" is ON

    Hi guys!
    If somebody of you is using the Seeburger Adapter:
    I have an inbound scenario and everything works fine. But when I set "Authentication Required" flag to be ON, messages are refused. This is strange, because incoming messages are signed.
    Any ideas, what could be wrong? There are several settings for certificates and maybe I have some wrong setting.. Does anybody have experience with this?
    Thank you, Peter

    Sai, you probably don't have experience with Seeburger AS2, do you? It works in a special way - that's why I'm asking people, who have experience with this..
    But for clarification: My inbound Seeburger AS2 channel receives message scorrectly, but when I enable uthentication on it, AS2 messages are refused - so they are not in the AE, they are not in the IE.
    Peter
    p.s. I will not reward your answer, sorry
    Message was edited by:
            Peter Jarunek

  • Seeburger AS2 - import certificate type .p7b (PKCS#7)

    Dear Seeburger AS2 experts,
    Has anyone ever imported (loaded) a certificate file type *.p7b (PKCS#7)?   I've got a .p7b certificate file from my trading partner but I cannot import it, as XI does not have the option to load this type.  I tried loading a .cer file, but that did not work (as2 authentication error) for some reasons.  My trading partner does not have a .p8 or .p12 certificate.  Is there any way to load a .p7b into XI?
    Thanks.
    Sakkarn

    Is this resolved...
    Regards
    Ravi R

  • Seeburger AS2 connectivity issues.

    Hello,
    is it possible to have one single certificate for both AS2 and SSL, using HTTPS protocol.
    if yes should we upload the certificates twice (AS2 & SSL)?
    Also when we sent some messages via AS2, the seeburger AS2 server seems to be closing the connection abruptly. are there any logs generated on the seeburger side in order to check what actually happened?

    Hi
    AS2 and SSL follows two different protocols. So It's not possible to use same certificate for both of them.
    for AS2 connectivity you can ask your network team to open the network port only for AS2 authentication.
    regards
    chandra

  • Renewing public key certificate used for Seeburger AS2

    My general question is when a public key certificate, used for Seeburger AS2 payload decryption and digital signatures, needs to be renewed, how carefully do the certificate renewal steps need to be coordinated for a seamless transition?  More specifically...
    1. Once we import the CSR response from the CA, will the public key currently used by our partner become invalid, or will it continue to work until its expiration date? 
    2. Will our partner be able to validate our signature after the new CSR has been imported, but prior to them applying the new public key certificate in their system? 
    3. Or can we renew the certificate, import the CSR request, provide our partner with the renewed certificate, and let them apply the certificate at their own volition, provided they do it prior to the original certificate expiration?

    Hi Kurt
    In my experience, the renewal/replacement of AS2 certificates for encryption/decryption & signing/authentication requires coordinated effort on both sides.
    This is because AS2 uses asymmetrical encryption, so both parties need to use the same pair of certificates at the same time, i.e. you encrypt on your private key, and partner decrypt on the public key matching your private key. If the keys used do not belong to the same pair, then decryption will not work.
    I'm not sure what AS2 software your partner uses and if it has the feature of automatic rollover of certificate, but PI/Seeburger does not. The approach in PI/Seeburger can either be one of the following:-
    i) import new cert replacing original cert of the same name
    ii) import new cert into new name, manually update sender/receiver agreements
    Due to the manual nature of the tasks, normally it requires coordinated effort during a cutover window.
    Rgds
    Eng Swee

  • As2 receiver channel, SEEBURGER AS2: 500 Internal Server Error

    Hi,
    There is one scenario in our landscape, its running in production, Proxy to As2. The interface working fine for last 2 weeks, today its showing error in As2 receiver channel saying
    Message processing failed. Cause: javax.resource.ResourceException: Fatal exception: javax.resource.ResourceException: SEEBURGER AS2: 500 Internal Server Error # , SEEBURGER AS2: 500 Internal Server Error #
    I have searched in forum, but couldnt get much idea on why this error encounters and how can we resolve it.
    Kindly provide your inputs to help me resolve this.
    Thanks,
    Ruchi

    Hi Ruchi,
    500 means the requested server does not understand the request (the requested service is unknown). The reason is obvisiously outside of PI. You have to contact the 3rd party owner and ask why the system is refusing the request instead of responsing like before.
    Regards,
    Udo

  • There is no key entry with such alias in keystore seeburger AS2

    Hi,
    Error message  in RWB shows the following
    Message entered module processor exit bean and will be transferred to JCA adapter
    2011-04-06 06:19:29 Success SEEBURGER/AS2: Received order from system.
    2011-04-06 06:19:29 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: java.security.PrivilegedActionException: com.seeburger.ksm.cryptoapi.exception.CryptoApiException: There is no key entry with such alias in keystore, SEEBURGER AS2: AS2 Adapter failure # java.lang.Exception: AS2 message composition failed: com.seeburger.ksm.cryptoapi.exception.CryptoApiException: java.security.PrivilegedActionException: com.seeburger.ksm.cryptoapi.exception.CryptoApiExc
    2011-04-06 06:19:29 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: AS2 Adapter failure # java.lang.Exception: AS2 message composition failed: com.seeburger.ksm.cryptoapi.exception.CryptoApiException: java.security.PrivilegedActionException: com.seeburger.ksm.cryptoapi.exception.CryptoApiException: There is no key entry with such alias in keystore, SEEBURGER AS2: AS2 Adapter failure # java.lang.Exception: AS2 message composition failed: com.seeburger.ksm.cryptoapi.exception.CryptoApiException: java.security.PrivilegedActionException: com.
    2011-04-06 06:19:29 Error The message status set to NDLV.
    2011-04-06 06:19:29 Error MP: Exception caught with cause javax.resource.ResourceException: 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: java.security.PrivilegedActionException: com.seeburger.ksm.cryptoapi.exception.CryptoApiException: There is no key entry with such alias in keystore, SEEBURGER AS2: AS2 Adapter failure # java.lang.Exception: AS2 message composition failed: com.seeburger.ksm.cryptoapi.exception.CryptoApiException: java.security.PrivilegedActionException: com.seeburger.ks
    unable to send / receiver messages through AS2. Please let us know what could be the error. How/ where to resolve it.

    Please check the SDN thread below
    AS2 Adapter Configuration to Customer / no signature certificate
    Also, check the help page below
    http://help.sap.com/saphelp_sm40/helpdata/DE/84/be18d66b2a47f6b4adc704a7c0e23e/content.htm
    for instructions on how to get the "SEEBURGER EDIINT AS2 Adapter for SAP Exchange Infrastructure Configuration Guide" from the Service Marketplace. Then, on this guide, please check the configuration according to your sender or receiver communication channel regarding the Security (certificates) parameters.
    Are the key Store entries imported correctly? Please check if the certificates were imported in the right order and none of the certificates on the chain are expired.

  • Seeburger AS2 comm channel problem (B2B) - "perhaps AS2ID missing"

    Hi guys!
    We try to configure B2B scenario using Seeburger AS2, but communication channel monitor returns error:
    Error type: COMPONENT_ERROR,NOT_TRANSMITTED >> Error date: 9/25/07 10:05 AM >> Description: AS2 Adapter failure Outbound configuration error: Sender configuration incomplete - perhaps AS2ID missing.. com.seeburger.as2.AS2Plugin.execute(AS2Plugin.java:321) [9/25/07 10:05 AM]
    We're not sure about the scenario configuration and using identifiers (cos' this is probably the problem).
    Did someone of u already configured Seeburger AS2?
    We have configured in receiver party alternative identifier Seeburger - AS2ID, however, the message sent to target has always agency XI and scheme XIParty. It should be probably Seeburger and AS2ID (the alternative one).
    <SAP:Receiver>
      <SAP:Party agency="http://sap.com/xi/XI" scheme="XIParty">XXXX</SAP:Party>
      <SAP:Service>BS_3RD_XXXXX</SAP:Service>
      <SAP:Interface
    How to achieve it?
    Thanx a lot!
    Peter

    Hi Anoop!
    Yes, we use it on receiver side.
    ModuleProcessorExitbean exists, so it should be ok.
    What I'm not sure about is the thing with identifiers..
    In Party (let's call it X) - Identifiers, we have default agency http://sap.com/xi/XI, scheme XIParty and name X.
    What values should be there for Seeburger?
    We have Agency: Seeburger, Scheme: AS2ID; Name: X.
    Is it correct?
    We also received some 9 char long number - probably some ID to adapter(?). Any idea, if it is necessary and where to use it?
    Is it necessary to configure identifier seeburger also in Identifiers tab of Receiver communication channel? Or we can leave it empty (both- sender, receiver)?
    We use this in B2B scenario, of course: Target system is party, but we use our R/3 as Business System w/o party. Is it ok, or do we laso have to "be" as Party in our configuration scenario?
    A lot of questions, but points will be awarded 4 sure
    Thanx!
    Peter

Maybe you are looking for