Skip to Content
avatar image
Former Member

SEEBURGER AS2 Adapter Security

Hello,

I am running into an issue on the install of the SEEBURGER AS2 Adapter. We currently have other AS2 communication software in place, which are in our DMZ for security purposes. However, we do not want to put our SAP XI server in the DMZ because we would like it more protected. We are getting around this problem by using a reverse proxy scenario to get it through our firewall.

Is there a more effecient way to install the SEEBURGER AS2 adapter without exposing the entire SAP XI server to the DMZ?

Thank you, any help or advice would be appreciated.

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

2 Answers

  • Best Answer
    avatar image
    Former Member
    Sep 05, 2006 at 05:54 PM

    Hi Carley,

    I will tell you something about Seeburger Adapters in detail, Just see if it helps...

    Seeburger EDI Adapter provides an EDI solution on internet via HTTP or AS2 to replace the expensive VAN. It provides some pre-built mappings for IDOC to ANSI X12(810,850,855,856 etc.,) and Idoc to EDIFACT(ORDERS,DESADV,INVOIC etc.,) and has the ability to build your own. These pre-defined mappings transform the IDOC-XML to EDI-XML format.

    These transformed EDI-XML messages are then converted to EDI specific format using the Seeburger's BIC(Business Integration Converter)adapter. In addition, Seeburger provides adapters like AS2,FTP(EDI specific) and so on to route these EDI messages to external EDI Partners.

    Seeburger EDI Adapter leverages SAP XI's Adapter Framework. This Adapter is used to perform conversion between EDI and XML format. It also provides some canned EDI layouts and the ability to build your own. It is used to transfer the EDI message via HTTP or AS2 protocols.

    The most direct way of using the Seeburger adapters is to configure the BIC as a module. There is a software component from seeburger called bicmapper which will allow you to do the following:

    1. define or import the inbound message metadefinition in various formats ( edifact, xml,...)

    2. using a mapping create an xml variant as the output metadefinition or edifact in the other direction.

    3. create a one to one mapping between input en output.

    4. export the metadata in xsd or sda format for import in XI

    5. generate an SDA which can be deployed in XI and used as a module.

    Please go through the following links which clearly explains what you want and it also helps you in understanding the same in depth:

    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

    Regards,

    Abhy

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member

      The problem with this approach is that decrypting in the DMZ is a security risk. You're better off having the proxy pass it to a server in the trusted segment of your network.

  • avatar image
    Former Member
    Sep 05, 2006 at 05:18 PM

    The way you are using is the most common-seen

    way. Why you need other ways?

    Please give points. Thx.

    Add comment
    10|10000 characters needed characters exceeded