Integrating XI With EDI
Content
Integrating XI with EDI
Prasad illapani
SAP Labs LLC, Redmond, WA
Topics
XI30 Overview B2B in XI30 Seeburger EDI Adapter Deployment & Configuration in XI30 Demo
Why Choose SAP Exchange Infrastructure?
SAP XI30: • enables an easy integration of applications and business partners based on open standards • is harmonized with all other components of the integration suite SAP NetWeaver • provides “out of the box” implementation through XI content
SERVER BUILDER
© SAP AG 2005, Title of Presentation / Speaker Name / 3
Openness and Interoperability
Openness
• Use open, XML-based standards • Leverage Industry Standards in B2B scenarios
3rd Party Application
Interoperability
• Connect to applications using specialized adapters • Connect to existing integration solutions using JMS (e.g. MQSeries) or SOAP
SAP Application 3rd Party Middleware Component
Evolution
• Reuse existing technologies like JCAcompliant adapters or XSLT-/ Java mappings • Integrate existing Web Services
3rd Party Application
Benefits n Lower TCO by using open / industry-specific standards n Leverage existing investments n Arrive at new integration landscape in an evolutionary manner
© SAP AG 2005, Title of Presentation / Speaker Name / 4
All SAP Road(map)s lead to ESA
Goal No. 1 for SAP NetWeaver is to enable Enterprise Services Architecture
Enterprise Services Architecture
PEOPLE PRODUCTIVITY
ANALYTICS/REPORTING SERVICE COMPOSITION AND ORCHESTRATION
Openness n Open Web services standards n Open integration platform n Interoperability Adaptability n Model driven n Configurable n Extensible n Services composition n Process innovation
Lower TCO n Deployment options through configuration n Common operational services n “Always On” platform Productivity n People productivity n Embedded analytics n Process efficiency n Process flexibility
SERVICE ENABLEMENT
Enterprise Services Repository
SAP’s Enterprise Services
Partner Services
Business Objects, Components, and Engines
Bus. Partner Legacy
LIFE-CYCLE MGMT LIFE-
© SAP AG 2005, Title of Presentation / Speaker Name / 5
Topics
XI30 Overview B2B in XI30 EDI Adapter (Seeburger) Deployment in XI30 & Configuration Demo
B2B in XI3.0
Any
Application SAPApplication
Industry Standard Protocols Integration Server Integration Repository & Integration Directory
BPE Business Partners
Integration Engine
B2B Messaging
Business Partners
Adapter Engine Partner Connectivity Kit Small Trading Partners
© SAP AG 2005, Title of Presentation / Speaker Name / 7
Security
Support of EDI standards
SAP relies on a system of partners to provide adapters for other applications and certain industry EDI standards
n SEEBURGER AG
n n
n
EDI Adapters: Technical Adapters for EDIINT AS2, Generic EDI, OFTP, VAN Access, Payment EDI Adapters: Industry Specific Adapters (incl. mappings) for Aerospace & Defense, Automotive, Chemical, Consumer Products, High-Tech, Paper, Pharmaceuticals, Retail Industry Mappings between IDoc and EDIFACT business documents (purchase order, order confirmation, invoice etc.) JCA Resource Adapters that run within SAP XI Adapter Engine. UCCnet Adapter More to come (Peoplesoft-, Siebel-, Oracle, UCCnet-, Transora- and AS2adapters already certified for SAP XI 3.0) … No separate runtime required: adapters run on top of SAP XI Adapter Framework
n
n iWay Software
n n
n
© SAP AG 2005, Title of Presentation / Speaker Name / 8
Purchase Order Flow - EDI
Buyer Seller
P.O. (850)
VAN
Manual Retries upon failure …
VAN
P.O. (850)
ERP System
VAN
P.O. Acknowledgment (855)
ERP System
EDI Translator
EDI Translator
© SAP AG 2005, Title of Presentation / Speaker Name / 9
B2B related configuration in the directory
Creation of Party
n The object party facilitates the B2B functions of SAP Exchange Infrastructure and contains the following information: n Name, description, and additional identifiers (DUNS, GLN or SCAC) of the party
© SAP AG 2005, Title of Presentation / Speaker Name / 10
B2B related configuration in the directory
Creation of Service
n The object service generalizes business systems. n A service can represent:
A business system (in A2A scenarios) Semantical units (grouping of interfaces), which are used mainly for routing purposes in the communication between multiple B2B parties.
© SAP AG 2005, Title of Presentation / Speaker Name / 11
B2B related configuration in the directory
Creation of a Channel
Communication channels can be used in two directions: n Sender communication channel n Receiver communication channel For configuring specific adapters you can use the pre-delivered communication channels called channel templates Channel templates also contain the security policies Contains specific information for the message protocol, transport protocol, URL, logon data and adapter specific onfiguration This also helps in the central configuration of adapters in the Integration directory
© SAP AG 2005, Title of Presentation / Speaker Name / 12
B2B related configuration in the directory
Creation of Sender and Receiver Agreements
The objects sender agreement and receiver agreement describe which channel to use and specify the party related security settings like certificates The sender agreement is used on the Integration Server for inbound processing, the receiver agreement for outbound processing. Sender agreement and receiver agreement can be subsumed under the term “collaboration agreement“.
© SAP AG 2005, Title of Presentation / Speaker Name / 13
Topics
XI30 Overview B2B in XI30 Seeburger EDI Adapter Deployment & Configuration in XI30 Demo
Seeburger BIC & FTP Adapter in XI30
SAP relies on Partners (Ex: Seeburger) to provide the following EDI Adapters for XI30. 1. Seeburger Business Integration Converter (BIC) Adapter is used in XI30 for EDI related message exchange. BIC Adapter converts a EDI-xml message to a EDI formatted message. n For Ex: ANSIX12-xml message to ANSIX12 format. 1. Seebuger FTP adapter is used in XI30 mainly to route the EDI messages via FTP Transport Protocol. There are various message Protcols being used for transporting the messages depending upon the industry defined ones. n For EX: IBM Information Exchange message Protocol is used to route the messages to a VAN.
© SAP AG 2005, Title of Presentation / Speaker Name / 15
Seeburger BIC Adapter Deployment in XI30
Prequisites: XI30-SP09 is installed and configured. Installation: The following SDA files are deployed on XI30 using the SDM tool. For more information about the Library files check the BIC Adapter for XI30 Setup Guide. I. Deploy SDA files: The following 7 Libraries are deployed in the order of preference
n SeeLogger.sda n SeeFunctionsXILib.sda n Mappings_user.sda n Mappings_sys.sda n bicXIRa-libs.sda n bicXIRa.sda n CallBicXIRaEAR.ear
© SAP AG 2005, Title of Presentation / Speaker Name / 16
Seeburger BIC Adapter Deployment in XI30
II. Deploy the Adapter Metadata file: BICAdapterMetadata.xml Follow the below steps . 1. Start the Integration Repository (Design) from Integration Builder. 2. Import the SEEBURGER Adapter Software Component Version (directory.\data\Content\XI3_0_SEEBURGER_EDI_ADAPTER_3.0_of_ Seeburger.tpz). The installation procedure is described in the manual “SEEBURGER EDI Content for SAP XI 3.0”. 3. Create a namespace. The following value: http://seeburger.com/xi must be used. 4. Create a new metadata object called “BIC” and enter the name and description. 5. Select the XML metadata file by clicking the "Upload" button. 6. When the XML file has been uploaded, the metadata can be seen. 7. Save and activate the changes.
© SAP AG 2005, Title of Presentation / Speaker Name / 17
Seeburger FTP Adapter Deployment in XI30
Prequisites: XI30-SP09 is installed and configured. Installation: The following SDA files are deployed on XI30 using the SDM tool. For more information about the Library files check the Seeburger FTP Adapter for XI30 Setup Guide I. Deploy SDA files: The following 4 Libraries are deployed in the order of preference.
n FTPTableDeployment.sda n SeeXICryptoSourceBridgeLib.sda n SeeXIFTP.sda n SeeXIMessageIdMonitor.sda
© SAP AG 2005, Title of Presentation / Speaker Name / 18
Seeburger FTP Adapter Deployment in XI30
II. Deploy the Adapter Metadata file: FTPAdapterMetadata.xml The Adapter Metadata file FTPAdatperMetadata.xml is deployed as follows: 1. Start the Integration Repository (Design). 2. Import the SEEBURGER Adapter Software Component Version (directory.\data\Content\XI3_0_SEEBURGER_EDI_ADAPTER_3.0_of_ Seeburger.tpz). The installation procedure is described in the manual “SEEBURGER EDI Content for SAP XI 3.0”. 3. Create a namespace. The following value: http://seeburger.com/xi must be used 4. Select the Adapter Objects node and create a new Adapter Metadata object. The following value for the adapter name must be used: FTP
© SAP AG 2005, Title of Presentation / Speaker Name / 19
Configuring the Communication Channel in XI30
Example of the Receiver FTP Adapter Communication Channel Parameters.
© SAP AG 2005, Title of Presentation / Speaker Name / 20
Configuring the Communication Channel in XI30
Example of the Receiver FTP Adapter Communication Channel: Module Configuration
© SAP AG 2005, Title of Presentation / Speaker Name / 21
Topics
XI30 Overview B2B in XI30 EDI Adapter (Seeburger) Deployment in XI30 & Configuration Demo
Demo
© SAP AG 2005, Title of Presentation / Speaker Name / 23
Questions?
Q&A
© SAP AG 2005, Title of Presentation / Speaker Name / 24
Copyright 2005 SAP AG. All Rights Reserved
n n n n
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice. Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors. Microsoft, Windows, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation. IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries, pSeries, xSeries, zSeries, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, and Informix are trademarks or registered trademarks of IBM Corporation in the United States and/or other countries. Oracle is a registered trademark of Oracle Corporation. UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group. Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc. HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts Institute of Technology. Java is a registered trademark of Sun Microsystems, Inc. JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape. MaxDB is a trademark of MySQL AB, Sweden. SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary.
n n n n n n n n
n n
The information in this document is proprietary to SAP. No part of this document may be reproduced, copied, or transmitted in any form or for any purpose without the express prior written permission of SAP AG. This document is a preliminary version and not subject to your license agreement or any other agreement with SAP. This document contains only intended strategies, developments, and functionalities of the SAP® product and is not intended to be binding upon SAP to any particular course of business, product strategy, and/or development. Please note that this document is subject to change and may be changed by SAP at any time without notice. SAP assumes no responsibility for errors or omissions in this document. SAP does not warrant the accuracy or completeness of the information, text, graphics, links, or other items contained within this material. This document is provided without a warranty of any kind, either express or implied, including but not limited to the implied warranties of merchantability, fitness for a particular purpose, or non-infringement. SAP shall have no liability for damages of any kind including without limitation direct, special, indirect, or consequential damages that may result from the use of these materials. This limitation shall not apply in cases of intent or gross negligence. The statutory liability for personal injury and defective products is not affected. SAP has no control over the information that you may access through the use of hot links contained in these materials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages.
n
n n
© SAP AG 2005, Title of Presentation / Speaker Name / 25
Copyright 2005 SAP AG. Alle Rechte vorbehalten
n n n n n n n n n n n n
Weitergabe und Vervielfältigung dieser Publikation oder von Teilen daraus sind, zu welchem Zweck und in welcher Form auch immer, ohne die ausdrückliche schriftliche Genehmigung durch SAP AG nicht gestattet. In dieser Publikation enthaltene Informationen können ohne vorherige Ankündigung geändert werden. Die von SAP AG oder deren Vertriebsfirmen angebotenen Softwareprodukte können Softwarekomponenten auch anderer Softwarehersteller enthalten. Microsoft, Windows, Outlook, und PowerPoint sind eingetragene Marken der Microsoft Corporation. IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries, pSeries, xSeries, zSeries, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, und Informix sind Marken oder eingetragene Marken der IBM Corporation in den USA und/oder anderen Ländern. Oracle ist eine eingetragene Marke der Oracle Corporation. UNIX, X/Open, OSF/1, und Motif sind eingetragene Marken der Open Group. Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, und MultiWin sind Marken oder eingetragene Marken von Citrix Systems, Inc. HTML, XML, XHTML und W3C sind Marken oder eingetragene Marken des W3C®, World Wide Web Consortium, Massachusetts Institute of Technology. Java ist eine eingetragene Marke von Sun Microsystems, Inc. JavaScript ist eine eingetragene Marke der Sun Microsystems, Inc., verwendet unter der Lizenz der von Netscape entwickelten und implementierten Technologie. MaxDB ist eine Marke von MySQL AB, Schweden. SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver und weitere im Text erwähnte SAP-Produkte und -Dienstleistungen sowie die entsprechenden Logos sind Marken oder eingetragene Marken der SAP AG in Deutschland und anderen Ländern weltweit. Alle anderen Namen von Produkten und Dienstleistungen sind Marken der jeweiligen Firmen. Die Angaben im Text sind unverbindlich und dienen lediglich zu Informationszwecken. Produkte können länderspezifische Unterschiede aufweisen.
n n
Die in dieser Publikation enthaltene Information ist Eigentum der SAP. Weitergabe und Vervielfältigung dieser Publikation oder von Teilen daraus sind, zu welchem Zweck und in welcher Form auch immer, nur mit ausdrücklicher schriftlicher Genehmigung durch SAP AG gestattet. Bei dieser Publikation handelt es sich um eine vorläufige Version, die nicht Ihrem gültigen Lizenzvertrag oder anderen Vereinbarungen mit SAP unterliegt. Diese Publikation enthält nur vorgesehene Strategien, Entwicklungen und Funktionen des SAP®-Produkts. SAP entsteht aus dieser Publikation keine Verpflichtung zu einer bestimmten Geschäfts- oder Produktstrategie und/oder bestimmten Entwicklungen. Diese Publikation kann von SAP jederzeit ohne vorherige Ankündigung geändert werden. SAP übernimmt keine Haftung für Fehler oder Auslassungen in dieser Publikation. Des Weiteren übernimmt SAP keine Garantie für die Exaktheit oder Vollständigkeit der Informationen, Texte, Grafiken, Links und sonstigen in dieser Publikation enthaltenen Elementen. Diese Publikation wird ohne jegliche Gewähr, weder ausdrücklich noch stillschweigend, bereitgestellt. Dies gilt u. a., aber nicht ausschließlich, hinsichtlich der Gewährleistung der Marktgängigkeit und der Eignung für einen bestimmten Zweck sowie für die Gewährleistung der Nichtverletzung geltenden Rechts. SAP haftet nicht für entstandene Schäden. Dies gilt u. a. und uneingeschränkt für konkrete, besondere und mittelbare Schäden oder Folgeschäden, die aus der Nutzung dieser Materialien entstehen können. Diese Einschränkung gilt nicht bei Vorsatz oder grober Fahrlässigkeit. Die gesetzliche Haftung bei Personenschäden oder Produkthaftung bleibt unberührt. Die Informationen, auf die Sie möglicherweise über die in diesem Material enthaltenen Hotlinks zugreifen, unterliegen nicht dem Einfluss von SAP, und SAP unterstützt nicht die Nutzung von Internetseiten Dritter durch Sie und gibt keinerlei Gewährleistungen oder Zusagen über Internetseiten Dritter ab.
n
n n
© SAP AG 2005, Title of Presentation / Speaker Name / 26
Prasad illapani
SAP Labs LLC, Redmond, WA
Topics
XI30 Overview B2B in XI30 Seeburger EDI Adapter Deployment & Configuration in XI30 Demo
Why Choose SAP Exchange Infrastructure?
SAP XI30: • enables an easy integration of applications and business partners based on open standards • is harmonized with all other components of the integration suite SAP NetWeaver • provides “out of the box” implementation through XI content
SERVER BUILDER
© SAP AG 2005, Title of Presentation / Speaker Name / 3
Openness and Interoperability
Openness
• Use open, XML-based standards • Leverage Industry Standards in B2B scenarios
3rd Party Application
Interoperability
• Connect to applications using specialized adapters • Connect to existing integration solutions using JMS (e.g. MQSeries) or SOAP
SAP Application 3rd Party Middleware Component
Evolution
• Reuse existing technologies like JCAcompliant adapters or XSLT-/ Java mappings • Integrate existing Web Services
3rd Party Application
Benefits n Lower TCO by using open / industry-specific standards n Leverage existing investments n Arrive at new integration landscape in an evolutionary manner
© SAP AG 2005, Title of Presentation / Speaker Name / 4
All SAP Road(map)s lead to ESA
Goal No. 1 for SAP NetWeaver is to enable Enterprise Services Architecture
Enterprise Services Architecture
PEOPLE PRODUCTIVITY
ANALYTICS/REPORTING SERVICE COMPOSITION AND ORCHESTRATION
Openness n Open Web services standards n Open integration platform n Interoperability Adaptability n Model driven n Configurable n Extensible n Services composition n Process innovation
Lower TCO n Deployment options through configuration n Common operational services n “Always On” platform Productivity n People productivity n Embedded analytics n Process efficiency n Process flexibility
SERVICE ENABLEMENT
Enterprise Services Repository
SAP’s Enterprise Services
Partner Services
Business Objects, Components, and Engines
Bus. Partner Legacy
LIFE-CYCLE MGMT LIFE-
© SAP AG 2005, Title of Presentation / Speaker Name / 5
Topics
XI30 Overview B2B in XI30 EDI Adapter (Seeburger) Deployment in XI30 & Configuration Demo
B2B in XI3.0
Any
Application SAPApplication
Industry Standard Protocols Integration Server Integration Repository & Integration Directory
BPE Business Partners
Integration Engine
B2B Messaging
Business Partners
Adapter Engine Partner Connectivity Kit Small Trading Partners
© SAP AG 2005, Title of Presentation / Speaker Name / 7
Security
Support of EDI standards
SAP relies on a system of partners to provide adapters for other applications and certain industry EDI standards
n SEEBURGER AG
n n
n
EDI Adapters: Technical Adapters for EDIINT AS2, Generic EDI, OFTP, VAN Access, Payment EDI Adapters: Industry Specific Adapters (incl. mappings) for Aerospace & Defense, Automotive, Chemical, Consumer Products, High-Tech, Paper, Pharmaceuticals, Retail Industry Mappings between IDoc and EDIFACT business documents (purchase order, order confirmation, invoice etc.) JCA Resource Adapters that run within SAP XI Adapter Engine. UCCnet Adapter More to come (Peoplesoft-, Siebel-, Oracle, UCCnet-, Transora- and AS2adapters already certified for SAP XI 3.0) … No separate runtime required: adapters run on top of SAP XI Adapter Framework
n
n iWay Software
n n
n
© SAP AG 2005, Title of Presentation / Speaker Name / 8
Purchase Order Flow - EDI
Buyer Seller
P.O. (850)
VAN
Manual Retries upon failure …
VAN
P.O. (850)
ERP System
VAN
P.O. Acknowledgment (855)
ERP System
EDI Translator
EDI Translator
© SAP AG 2005, Title of Presentation / Speaker Name / 9
B2B related configuration in the directory
Creation of Party
n The object party facilitates the B2B functions of SAP Exchange Infrastructure and contains the following information: n Name, description, and additional identifiers (DUNS, GLN or SCAC) of the party
© SAP AG 2005, Title of Presentation / Speaker Name / 10
B2B related configuration in the directory
Creation of Service
n The object service generalizes business systems. n A service can represent:
A business system (in A2A scenarios) Semantical units (grouping of interfaces), which are used mainly for routing purposes in the communication between multiple B2B parties.
© SAP AG 2005, Title of Presentation / Speaker Name / 11
B2B related configuration in the directory
Creation of a Channel
Communication channels can be used in two directions: n Sender communication channel n Receiver communication channel For configuring specific adapters you can use the pre-delivered communication channels called channel templates Channel templates also contain the security policies Contains specific information for the message protocol, transport protocol, URL, logon data and adapter specific onfiguration This also helps in the central configuration of adapters in the Integration directory
© SAP AG 2005, Title of Presentation / Speaker Name / 12
B2B related configuration in the directory
Creation of Sender and Receiver Agreements
The objects sender agreement and receiver agreement describe which channel to use and specify the party related security settings like certificates The sender agreement is used on the Integration Server for inbound processing, the receiver agreement for outbound processing. Sender agreement and receiver agreement can be subsumed under the term “collaboration agreement“.
© SAP AG 2005, Title of Presentation / Speaker Name / 13
Topics
XI30 Overview B2B in XI30 Seeburger EDI Adapter Deployment & Configuration in XI30 Demo
Seeburger BIC & FTP Adapter in XI30
SAP relies on Partners (Ex: Seeburger) to provide the following EDI Adapters for XI30. 1. Seeburger Business Integration Converter (BIC) Adapter is used in XI30 for EDI related message exchange. BIC Adapter converts a EDI-xml message to a EDI formatted message. n For Ex: ANSIX12-xml message to ANSIX12 format. 1. Seebuger FTP adapter is used in XI30 mainly to route the EDI messages via FTP Transport Protocol. There are various message Protcols being used for transporting the messages depending upon the industry defined ones. n For EX: IBM Information Exchange message Protocol is used to route the messages to a VAN.
© SAP AG 2005, Title of Presentation / Speaker Name / 15
Seeburger BIC Adapter Deployment in XI30
Prequisites: XI30-SP09 is installed and configured. Installation: The following SDA files are deployed on XI30 using the SDM tool. For more information about the Library files check the BIC Adapter for XI30 Setup Guide. I. Deploy SDA files: The following 7 Libraries are deployed in the order of preference
n SeeLogger.sda n SeeFunctionsXILib.sda n Mappings_user.sda n Mappings_sys.sda n bicXIRa-libs.sda n bicXIRa.sda n CallBicXIRaEAR.ear
© SAP AG 2005, Title of Presentation / Speaker Name / 16
Seeburger BIC Adapter Deployment in XI30
II. Deploy the Adapter Metadata file: BICAdapterMetadata.xml Follow the below steps . 1. Start the Integration Repository (Design) from Integration Builder. 2. Import the SEEBURGER Adapter Software Component Version (directory.\data\Content\XI3_0_SEEBURGER_EDI_ADAPTER_3.0_of_ Seeburger.tpz). The installation procedure is described in the manual “SEEBURGER EDI Content for SAP XI 3.0”. 3. Create a namespace. The following value: http://seeburger.com/xi must be used. 4. Create a new metadata object called “BIC” and enter the name and description. 5. Select the XML metadata file by clicking the "Upload" button. 6. When the XML file has been uploaded, the metadata can be seen. 7. Save and activate the changes.
© SAP AG 2005, Title of Presentation / Speaker Name / 17
Seeburger FTP Adapter Deployment in XI30
Prequisites: XI30-SP09 is installed and configured. Installation: The following SDA files are deployed on XI30 using the SDM tool. For more information about the Library files check the Seeburger FTP Adapter for XI30 Setup Guide I. Deploy SDA files: The following 4 Libraries are deployed in the order of preference.
n FTPTableDeployment.sda n SeeXICryptoSourceBridgeLib.sda n SeeXIFTP.sda n SeeXIMessageIdMonitor.sda
© SAP AG 2005, Title of Presentation / Speaker Name / 18
Seeburger FTP Adapter Deployment in XI30
II. Deploy the Adapter Metadata file: FTPAdapterMetadata.xml The Adapter Metadata file FTPAdatperMetadata.xml is deployed as follows: 1. Start the Integration Repository (Design). 2. Import the SEEBURGER Adapter Software Component Version (directory.\data\Content\XI3_0_SEEBURGER_EDI_ADAPTER_3.0_of_ Seeburger.tpz). The installation procedure is described in the manual “SEEBURGER EDI Content for SAP XI 3.0”. 3. Create a namespace. The following value: http://seeburger.com/xi must be used 4. Select the Adapter Objects node and create a new Adapter Metadata object. The following value for the adapter name must be used: FTP
© SAP AG 2005, Title of Presentation / Speaker Name / 19
Configuring the Communication Channel in XI30
Example of the Receiver FTP Adapter Communication Channel Parameters.
© SAP AG 2005, Title of Presentation / Speaker Name / 20
Configuring the Communication Channel in XI30
Example of the Receiver FTP Adapter Communication Channel: Module Configuration
© SAP AG 2005, Title of Presentation / Speaker Name / 21
Topics
XI30 Overview B2B in XI30 EDI Adapter (Seeburger) Deployment in XI30 & Configuration Demo
Demo
© SAP AG 2005, Title of Presentation / Speaker Name / 23
Questions?
Q&A
© SAP AG 2005, Title of Presentation / Speaker Name / 24
Copyright 2005 SAP AG. All Rights Reserved
n n n n
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice. Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors. Microsoft, Windows, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation. IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries, pSeries, xSeries, zSeries, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, and Informix are trademarks or registered trademarks of IBM Corporation in the United States and/or other countries. Oracle is a registered trademark of Oracle Corporation. UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group. Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc. HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts Institute of Technology. Java is a registered trademark of Sun Microsystems, Inc. JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape. MaxDB is a trademark of MySQL AB, Sweden. SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary.
n n n n n n n n
n n
The information in this document is proprietary to SAP. No part of this document may be reproduced, copied, or transmitted in any form or for any purpose without the express prior written permission of SAP AG. This document is a preliminary version and not subject to your license agreement or any other agreement with SAP. This document contains only intended strategies, developments, and functionalities of the SAP® product and is not intended to be binding upon SAP to any particular course of business, product strategy, and/or development. Please note that this document is subject to change and may be changed by SAP at any time without notice. SAP assumes no responsibility for errors or omissions in this document. SAP does not warrant the accuracy or completeness of the information, text, graphics, links, or other items contained within this material. This document is provided without a warranty of any kind, either express or implied, including but not limited to the implied warranties of merchantability, fitness for a particular purpose, or non-infringement. SAP shall have no liability for damages of any kind including without limitation direct, special, indirect, or consequential damages that may result from the use of these materials. This limitation shall not apply in cases of intent or gross negligence. The statutory liability for personal injury and defective products is not affected. SAP has no control over the information that you may access through the use of hot links contained in these materials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages.
n
n n
© SAP AG 2005, Title of Presentation / Speaker Name / 25
Copyright 2005 SAP AG. Alle Rechte vorbehalten
n n n n n n n n n n n n
Weitergabe und Vervielfältigung dieser Publikation oder von Teilen daraus sind, zu welchem Zweck und in welcher Form auch immer, ohne die ausdrückliche schriftliche Genehmigung durch SAP AG nicht gestattet. In dieser Publikation enthaltene Informationen können ohne vorherige Ankündigung geändert werden. Die von SAP AG oder deren Vertriebsfirmen angebotenen Softwareprodukte können Softwarekomponenten auch anderer Softwarehersteller enthalten. Microsoft, Windows, Outlook, und PowerPoint sind eingetragene Marken der Microsoft Corporation. IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries, pSeries, xSeries, zSeries, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, und Informix sind Marken oder eingetragene Marken der IBM Corporation in den USA und/oder anderen Ländern. Oracle ist eine eingetragene Marke der Oracle Corporation. UNIX, X/Open, OSF/1, und Motif sind eingetragene Marken der Open Group. Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, und MultiWin sind Marken oder eingetragene Marken von Citrix Systems, Inc. HTML, XML, XHTML und W3C sind Marken oder eingetragene Marken des W3C®, World Wide Web Consortium, Massachusetts Institute of Technology. Java ist eine eingetragene Marke von Sun Microsystems, Inc. JavaScript ist eine eingetragene Marke der Sun Microsystems, Inc., verwendet unter der Lizenz der von Netscape entwickelten und implementierten Technologie. MaxDB ist eine Marke von MySQL AB, Schweden. SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver und weitere im Text erwähnte SAP-Produkte und -Dienstleistungen sowie die entsprechenden Logos sind Marken oder eingetragene Marken der SAP AG in Deutschland und anderen Ländern weltweit. Alle anderen Namen von Produkten und Dienstleistungen sind Marken der jeweiligen Firmen. Die Angaben im Text sind unverbindlich und dienen lediglich zu Informationszwecken. Produkte können länderspezifische Unterschiede aufweisen.
n n
Die in dieser Publikation enthaltene Information ist Eigentum der SAP. Weitergabe und Vervielfältigung dieser Publikation oder von Teilen daraus sind, zu welchem Zweck und in welcher Form auch immer, nur mit ausdrücklicher schriftlicher Genehmigung durch SAP AG gestattet. Bei dieser Publikation handelt es sich um eine vorläufige Version, die nicht Ihrem gültigen Lizenzvertrag oder anderen Vereinbarungen mit SAP unterliegt. Diese Publikation enthält nur vorgesehene Strategien, Entwicklungen und Funktionen des SAP®-Produkts. SAP entsteht aus dieser Publikation keine Verpflichtung zu einer bestimmten Geschäfts- oder Produktstrategie und/oder bestimmten Entwicklungen. Diese Publikation kann von SAP jederzeit ohne vorherige Ankündigung geändert werden. SAP übernimmt keine Haftung für Fehler oder Auslassungen in dieser Publikation. Des Weiteren übernimmt SAP keine Garantie für die Exaktheit oder Vollständigkeit der Informationen, Texte, Grafiken, Links und sonstigen in dieser Publikation enthaltenen Elementen. Diese Publikation wird ohne jegliche Gewähr, weder ausdrücklich noch stillschweigend, bereitgestellt. Dies gilt u. a., aber nicht ausschließlich, hinsichtlich der Gewährleistung der Marktgängigkeit und der Eignung für einen bestimmten Zweck sowie für die Gewährleistung der Nichtverletzung geltenden Rechts. SAP haftet nicht für entstandene Schäden. Dies gilt u. a. und uneingeschränkt für konkrete, besondere und mittelbare Schäden oder Folgeschäden, die aus der Nutzung dieser Materialien entstehen können. Diese Einschränkung gilt nicht bei Vorsatz oder grober Fahrlässigkeit. Die gesetzliche Haftung bei Personenschäden oder Produkthaftung bleibt unberührt. Die Informationen, auf die Sie möglicherweise über die in diesem Material enthaltenen Hotlinks zugreifen, unterliegen nicht dem Einfluss von SAP, und SAP unterstützt nicht die Nutzung von Internetseiten Dritter durch Sie und gibt keinerlei Gewährleistungen oder Zusagen über Internetseiten Dritter ab.
n
n n
© SAP AG 2005, Title of Presentation / Speaker Name / 26
