Upload
voquynh
View
244
Download
0
Embed Size (px)
Citation preview
End-to-End Process IntegrationAdapter Framework
SAP NetWeaverProduct ManagementSAP AG
Adapter Modules and Development
Summary
Adapter Framework Overview
Adapter Strategy
Agenda
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 3
Integration Server
PlainJ2SE
Adapter Engine
Partner ConnectivityKitOptional non-central
Adapter EngineCentral Adapter Engine
Process Integration ndash Architecture
Integration Repository Integration Directory System Landscape Directory
Business Process Engine
Integration Engine
Adapter FrameworkMessagingQueuing
Security Handling
Resource
Adapter
Resource
Adapter
Resource
Adapter
Adapter FWMessagingQueuing
Security Handling
Adapter FWMessagingQueuing
Security Handling
PCK Configurationand Monitoring
HTTP
IDoc
Adapter
Adapter
FileDBJMSMarketplace
3rd Party Sys
FileDB
JMSSOAP
SAP ampNon-SAPSystem
FileDBJMSMarketplace
3rd Party Sys
FileDBJMSMarketplace
3rd Party Sys
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 4
Adapter Framework based on SAP J2EE Engine
Adapter Framework provides common functionality for Adapter Engine and SAP Partner Connectivity Kit
Adapter Framework is based on SAP J2EE Engine as part of SAP Web AS
Adapter Framework inherits properties and features such as scalability clustering high availability thread management etc
Adapter Framework provides its own queuing and logging services
Temporary stand-alone operation without connection to an Integration Server is possible while still providing e g guaranteed exactly once messaging to and from connected application system
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 5
JCA enabled Adapter Framework
Adapter Framework supports J2EE Connector Architecture (JCA)
JCA is standard architecture for connecting the J2EE platform toEnterprise Information Systems (EIS) e g ERP DBMS etcA Resource Adapter plugs into an application server providing connectivity between the EIS and a Java applicationJCA enabled Adapter Framework provides defined interfaces to which both our adapters and 3rd party adapters can conformJCA is a widely accepted standard that 3rd party adapter providers are familiar with
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 6
Central configuration administration monitoring
Additionally Adapter Framework provides comprehensive integration for central configuration administration monitoring of deployed adapters
One single point of access only one common UI enhanced transparancyAllows to movecopy configuration from one Adapter Framework to another (transportable configuration)
To transport configuration from test landscape to productive landscapeFor high availabilityfailover
Avoid redundant maintenance ensure consistencyEnd-to-end monitoring of the message flow over all components applications
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 7
ProxiesOutside-in development approachInterfaces designed centrally in Integration RepositoryConnect new SAP applications
Native connectivity to Application system (adapter-less)
AdaptersInside-out development approach Interface semantics externally pre-defined Connect existing (legacy) systemsSpecific wire protocol
Adapters vs Proxies
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 8
Integration Server
PlainJ2SE
Adapter Engine
Partner ConnectivityKitOptional non-central
Adapter EngineCentral Adapter Engine
Process Integration ndash Architecture
Integration Repository Integration Directory System Landscape Directory
Business Process Engine
Integration Engine
Adapter FrameworkMessagingQueuing
Security Handling
Resource
Adapter
Resource
Adapter
Resource
Adapter
Adapter FWMessagingQueuing
Security Handling
Adapter FWMessagingQueuing
Security Handling
PCK Configurationand Monitoring
HTTP
IDoc
Adapter
Adapter
FileDBJMSMarketplace
3rd Party Sys
FileDB
JMSSOAP
SAP ampNon-SAPSystem
FileDBJMSMarketplace
3rd Party Sys
FileDBJMSMarketplace
3rd Party Sys
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 9
Full integration of Adapter Engine
Adapter Engine is based on Adapter Framework
Adapter Engine fully integratedCentral configuration of connections to application systems (through appropriate adapters) in Integration DirectoryReuse of Integration Directoryrsquos existing versioning and transport capabilitiesCentral administration and monitoring over adapters IntegrationServer Integration Engine through Runtime Workbench
The Adapter Engine can be deployed centrally as part of Integration Server or as optional local Adapter Engine on its own SAP J2EE Server reasons for use of local Adapter Engine
Protocol of Sender- Receiver system (eg ftp not allowed)Performance High AvailabilityOrganizational Aspects IT requirements
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 10
PI Adapters developed by SAP
Technical AdaptersFileFTP (File Systems FTP Servers)JDBC (RDBMS systems)JMS (Messaging systems e g MQSeries SonicMQ)SOAP (Web Services)Plain HTTPMail (Mail Servers via SMTP IMAP4 POP3)SAP Business Connector (SAP BC)Marketplace (mySAP Marketplaces)
Application AdaptersRFCIDoc
Industry Standard AdaptersRNIF 20 (RosettaNet)RNIF 11 (RosettaNet)CIDX (RNIF 11)
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 11
Industry Standard Adapters as part of Business Packages
Business Package for RosettaNetOrder to Invoice Scenario
PIP3A4 Request Purchase Order PIP3A7 Notify of Purchase Order UpdatePIP3A8 Request Purchase Order ChangePIP3A9 Request Purchase Order CancellationPIP3B2 Notify of Advance ShipmentPIP3C3 Notify of Invoice PIP3A6 Distribute Order StatusPIP3C6 Notify of Remittance Advice
Business Package for CIDXOrder to Invoice Scenario
Order CreateOrder ResponseOrder ChangeShip NoticeInvoice
Business Packages include scenario descriptions business processes message interfaces message types mappings adapter etc
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 12
Partner Eco System
SAP relies on a system of partners to provide connectivity solutions for other applications and certain industry standards
Connectivity Reseller Agreements withSeeburger AGiWay SoftwareInformatica
3rd-Party solutions are sold and delivered through SAP
Technical support for partner solutions via theSAP Support Portal 24x7
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 13
PI Adapters by Seeburger (1)
Technical EDI AdaptersAS2 (EDIINTHTTP(S))Protocol AS2OFTPProtocol OFTPISDN OFTPTCPIPVAN AccessProtocol P7 X400 VAN FTP
Business EDI AdaptersGeneric EDIProtocol OFTPISDN or P7 X400 VAN FTPEDI Converter ANSI X12 EDIFACTMapping Templates Purchase order Order confirmation
Dispatch advice Invoice
Payment (Financial Service Providers)Protocol OFTPISDN P7 X400 VAN FTPEDI Converter EDIFACT SWIFTMapping Templates Payment orders Debit advice
Credit advice Account Statement
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 14
PI Adapters by Seeburger (2)
Industry Specific EDI AdaptersAerospace and Defense AutomotiveChemicals Consumer ProductsHigh-Tech PaperPharmaceutical Retail
Communication ProtocolsOFTPISDN P7 X400 VAN FTP
EDI Converter (EDI lt-gt XML)AECMASPEC 2000 ANSI X12 CHEM eStandards EDIFACT GALIAODETTE TRADACOM VDA
Mapping Templates within Integration RepositoryDelivery forecast Dispatch advise Invoice Purchase order Order confirmation
Message Library for Integration RepositoryHuge message catalog with EDI XML schema definitions
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 15
PI Adapters by iWay Software
Application AdaptersAriba BaanBroadvision ClarifyJD Edwards One World XE JD Edwards Worldi2 LawsonManugistics Microsoft CRMOracle Applications PeoplesoftQAD MFG Pro SiebelVantive
Industry Standard AdaptersSwift TransoraUCCnet
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 16
PI Adapters by iWay Software
Technical AdaptersAS1 (EDIINTSMTP) AS2 (EDIINTHTTP(S))BEA WLI COM+DCOMCorba Lotus NotesTibco Rendezvous
Mainframetransaction AdaptersCICS TMSIMSTelnet (3270) Telnet (5250) Tuxedo
Optionally further adapters can be added from a list of 160 iWayadapters e g HL7 (already certified) DB2 AS3 ebXML
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 17
SAP Conversion Agent by Informatica
Bi-directional conversion of unstructured and semi structured data from to XMLTransformation on message payloadProtocol support via SAPrsquos technical adapter (PI XI adapter framework)Transformations integrated via PI XI AF module
SAP J2EEPI XI Adapter Framework
Adapter
Adapter
Text2XML
XML2Excel
PDF2XML
ConversionAgent Studio
ConversionAgent Services
Conversion Agent Engine
CA AF Module
Conversion Agent J2EE Lib
Seamlessly integrated into Process Integration
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 18
Supported Data Formats by Informatica (partial list)
UNSTRUCTUREDMicrosoft WordMicrosoft ExcelPowerPointPDFStar OfficeWord PerfectASCII reportsHTMLEBCDICUndocumented binariesFlat filesRPGANSI
PRINT STREAMSAFPPost ScriptDJDE
SEMI-STRUCTURED HL7HIPAAASTMANSIndashX12EDIFACTCOBOLFIXCargo IMPMVRSWIFT
OTHER STANDARDSLegalXMLIFX cXMLebXML HL7 V30 ACORD (AL3 XML)
hellip using SAP technical adapter and Conversion Agent
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 19
Conversion Agent
Bi-directional conversion of unstructured and semi structured formats fromto XMLLinked through PI XI adapter framework module based on SAPrsquos technical adapter ndash no transport protocol manipulates payload informationSAP NetWeaver-wide use (via J2EE library)
3rd Party Adapters
Bi-directional conversion of one dedicated data format (eg SWIFT ANSI-X12 hellip) fromto XMLRuns within PI XI adapter framework - support payload transformation and transport protocol
Per adapter dedicated use within one SAP NetWeaver component
Conversion Agent vs 3rd Party Adapters
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 20
More Info about Connectivity Capabilities
httpservicesapcomxi xi in detail connectivity
Connectivity and Interoperability
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 21
Adapter Download from SAP Service Marketplace
SAP Service Marketplace httpservicesapcomswdc Download Installations and Upgrades Entry by Application Group Adapters
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 22
Certification Programs for Process Integration
httpwwwsdnsapcom Partners and ISVsIntegration and Certification Exchange Infrastructure
PI Based Certification Programs
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 23
Public info about certified PI adapters
httpwwwsapcompartnersdirectoriesSearchSolutionepxThird Party Defined Integration Scenarios NW-XI-AF 30
Certified PI Adapters
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 24
Adapter Configuration
Adapter independent parameters
Adapter specific parameters
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 25
Configurationcache
Adapter Engine
ISRuntime
AdapterSender
AdapterReceiver
Adapter Engine in SAP J2EE
Q
Administration
Security
Monitoring
Adapter-Specific
ComponentServices
TracingLogging
Module ProcessorEIS
Channel
acuteMessaging
Configcache
End-to-End MonitoringMessage flow over all components applications
Runtime Workbenchbull Uis for adminstration
monitoring
Integration Builder Directory
Receiver determinationbull Party-gtService-gtAction
Channel Definitionbull Adapter Enginebull Adapter Typebull Message Protocolbull Transport Protocolbull Securitybull Channel Configuration
(Sender Receiver Agreementbull PartyServiceAction lt-gt Channel
ConfigurationMaster
System Landscape Directorybull Holds component description
including address data
AdapterFramework
Integration Repositorybull Holds Adapter metadataIntegration Repositorybull Holds Adapter metadata
httpltIntegrationServerURLgt
Message
httpltAdapterEngineURLgt
OK Error
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 26
Transport Level Security
Transport Protocol Authentication
IDoc RFC and SNC Client Authentication
Client Authentication
Client Authentication
Client Authentication
Client Authentication
CRAM-MD5
Client Authentication
Client Authentication
Client Authentication
CDIX ndash Adapter HTTPs Client Authentication
RFC RFC and SNC
Plain HTTP HTTPs
FileFTP File Transfer Protocol using SSLTLS
SOAP HTTPsSMTPs (Receiver only)
Mail SMTPs POP3 IMAP4
Marketplace HTTPs
RNIF 20 ndash Adapter HTTPs
RNIF 11 ndash Adapter HTTPs
Supported by
Levels of Security
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 27
Message Level Security
Signature Non-Repudiation
of origin
Non-Repudiation of
receipt
Encryption
CDIX ndash Adapter PKCS7
Technology
XI protocol WS-Security
SOAP-Adapter WS-Security
SMIME
Mail-Adapter SMIME
RNIF 20 ndash Adapter SMIME
RNIF 11 ndash Adapter PKCS7
Supported by
Levels of Security
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 28
Access control list
Restrict access to the runtime environmentfor sender services of type Business Service or Business Systemfor interfaces of these sender services
Restrict access to particular (service) users
Check authorization at runtime
Configure access control in the Integration DirectorySender service Specify authorized users in the configuration of the corresponding (sender) serviceInterface Specify authorized users in the configuration of the relevant sender agreement which contains the interface in the object key
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 29
Dynamic Adapter Configuration
Enable adapters to read write dynamic message headers
Sender Adapter (constructing messages)Attach adapter specific information to message headerExamples File name source file size JMS timestamp mail subjectRead access to these attributes in receiver channel interface determination (routing) mapping
Receiver Adapter (consuming messages)Read attributes to overwrite values of channel configurationExamples Directory Name JMS Priority Mail Sender SOAP target URLSet attributes in mapping orUse attributes from sender in receiver channel
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 30
Sender Adapter Configuration (1)
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 31
Sender Adapter Configuration (2)
Add the filename et al to the message
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 32
Receiver Determination
Determinefilename-dependent receiver
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 33
Receiver Adapter
Store the file withthe name set in the messageattribute
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 34
Monitoring Adapter Engine
After selecting a message bdquoDetailsldquo View
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 35
Monitoring Integration Server
After selecting a message bdquoDisplayldquo
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 36
Remark Future of SAP XI 20 Adapter Engine
SAP XI 20 Adapter Engine is available in SAP NW acute04 and SAP NW 2004s as bdquoPlain J2SE Adapter Engineldquo
Functional scope as in SAP XI 20Adopted to the SAP XI 30 message protocolMinor maintenance issues bug fixes
RecommendationUse where platform requirements or limitations (hardware operating system JVM support) demand it
SAP XI 20 Adapter Engine works with SAP NW acute04 and SAP NW 2004s landscapes too
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 37
Integration Server
PlainJ2SE
Adapter Engine
Partner ConnectivityKitOptional non-central
Adapter EngineCentral Adapter Engine
Process Integration ndash Architecture
Integration Repository Integration Directory System Landscape Directory
Business Process Engine
Integration Engine
Adapter FrameworkMessagingQueuing
Security Handling
Resource
Adapter
Resource
Adapter
Resource
Adapter
Adapter FWMessagingQueuing
Security Handling
Adapter FWMessagingQueuing
Security Handling
PCK Configurationand Monitoring
HTTP
IDoc
Adapter
Adapter
FileDBJMSMarketplace
3rd Party Sys
FileDB
JMSSOAP
SAP ampNon-SAPSystem
FileDBJMSMarketplace
3rd Party Sys
FileDBJMSMarketplace
3rd Party Sys
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 38
SAP Partner Connectivity Kit Overview
SAP 3rdParty Appl PI XI
Smaller Company Subsidiary
SAPPCK
SAPApplication
3rd PartyApplication
Large Business Partner Headquarter
Internet
Enablement of smaller companies subsidiaries to exchange XML documents with their business partnerrsquos headquarterrsquos PI XI
SAPPCK
Providing a platform for development of own JCA Resource Adapters
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 39
SAP PCK ndash Adapters
SAP Partner Connectivity Kit (PCK) is based on Adapter Framework
SAP PCKlsquos objective is to enable XML document exchangebetween PI XI and business partner not using PI XI
SAP PCK also provides an extensible platform for developing and running individual JCA Resource adapters
Communication between PI XI and SAP PCK is via SAP XI messaging protocol
SAP PCK Includes the following adapters FileFTP JDBC JMS SOAP RFC IDoc (once available for SAP PCK) Mail SAP BC
Optionally SAP PCK can host further adapters that are available from SAP or 3rd party adapter providers
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 40
SAP PCK ndash Configuration Mapping
SAP PCK is deployed on stand-alone SAP J2EE Engine (part of SAP Web AS) within business partnerrsquos landscape
Configuration administration monitoring done locally on SAP PCK itself without need for an Integration Directory
Configuration UI provides same bdquolook and feelldquo as configuration UI of Adapter Engine
SAP PCK supports the development of message mappings using an integrated graphical mapping editor
Any source XML structure can be mapped to any target XML structureStandard functions are provided to perform calculations Boolean comparisons text mappings and other transformationsOptionally the standard functions can be enhanced with user-defined functions in Java
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 41
SAP PCK ndash Configuration UI
ConfigurationUI to configure Party Service Communication Channel Sender and Receiver agreementsSample screenshot for configuration of communication channel with adapter type sbquoFile FTPlsquo
Adapter Modules and Development
Summary
Adapter Framework Overview
Adapter Strategy
Agenda
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 43
SAP Exchange Infrastructure - Openness
Integration of SAP and non-SAP applicationsAdapter Framework for comprehensive integration of adaptersAdapters are used for technical connectivityAdapter metadata mappings are stored in Integration Repository
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 44
Dual Strategy
Dual connectivity strategyAdapter Framework for comprehensive integration of adapters to provide technical connectivity including central configurationadministration monitoring of adaptersInteroperability based on open standards (SOAP JMS HTTP(S)) tointeroperate with EAI providers
Value propositionStandardized interfaces allow easy integration of adapters from different partnersMinimum knowledge of end-to-end process integration requiredComprehensive integration avoids redundant maintenance ensures consistency enhances transparancyOpenness to integrate non-SAP applications 3rd party systems etcReduced TCO
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 45
Certification
CertificationSAP NetWeaver Certification of 3rd party adapters based on the adapter framework
Value propositionQuality (stability HA aspects performance etc) of adapters is controlledCertification helps customers to find right solutionQuick and convenient search for a variety of certified products with the online partner and product directory (httpwwwsapcompartnersdirectoriesSearchSolutionepx)Faster implementation time and lower integration costs through the use of tested 3rd party integrationReduced TCO
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 46
Adapter Mappings Metadata in Integration Repository
Adapter mappings and adapter metadata are stored in the Integration Repository
Centralized Integration Repository contains all relevant information for collaborative and integrative processesAll content adheres to open standards Adapters provide technical connectivity
Value propositionUse largest content catalogReduce costs in integration projectsReduce maintenance costsReduced TCO
Adapter Modules and Development
Summary
Adapter Framework Overview
Adapter Strategy
Agenda
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 48
For every adapter it is possible to define generic modules in the module processor possibility to extend the functionality of the specific adapter
Equivalent to the dispatcher classes in the J2SE adapter engine migration and examples
The default module configuration for the certain adapter is displayed in the channel configuration
Modules are EJBlsquos
Sequence matters
Module Processor Concept
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 49
Adapter Module Chain
Custom modulescan be added to default modulechains
Additional configurationparameters canbe specified eachmodule
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 50
Module Processor Documentation
SAP Help Portal (httphelpsapcom)SAP XI Runtime Connectivity Adapters Module ProcessorFeedback Mail to xidocumentationsapcom
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 51
Development Environment
Adapter development deployment and testing is possible on a single machine no full-blown PI XI is required
For testing purposes integration scenarioscan be configured in SAP PCK(eg loopback scenario)
Installation of SAP PCK already contains a sample adapter (including Adapter Meta Data) that should serve as a starting point
SAP Partner ConnectivityKit
Adapter FWMessagingQueuing
Security Handling
Resource
Adapter
PCK Configurationand Monitoring
FileDBJMSMarketplace
3rd Party Sys
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 52
Adapter Development Documentation
SAP Help Portal (httphelpsapcom)SAP XI Runtime Connectivity Partner Connectivity Kit Adapter DevelopmentFeedback Mail to xidocumentationsapcom
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 53
Requirements for Adapters (1)
Num AF Interface Category Description
1 JCA 10 conformance Mandatory Adapter must fulfill JCA 10 requirements (e g deployment) plus optional JCA 15 parts which are used by PI XI
2 AF Message Exchange Mandatory Adapter must be able to receive messages from AF and forward them to connected system and vice versa
3 AF Adapter Specific Modules
Optional SAP XI message and protocol conversion may be done entirely by the adapter or as adapter specific module and being called in the AF module chain context
4 Configuration Services Mandatory Unique configuration approach to manage adapters
5 Administrational Services
Optional Administration and Monitoring
6 Utility Service Mandatory Access to basic J2EE resources e g transactions and multithreading must be under control of J2EE server
7 Logging API Optional Adapters may use their own logging
8 Message Metadata Exchange
Optional Provide structure definition of message payloadIf not supported the definition of message types can be done in the Integration Repository
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 54
Requirements for Adapters (2)
Cluster-enabledConsider side-effects of clustering e g bdquoExactlyOnceInOrderldquo Avoid passing maneuvers
SpecializationBuild connection to exactly one type of business system or industrystandard protocol
DirectnessBuild connection to business system or industry standard protocoldirectly without any intermediate software components
SmoothnessLight-weighted low footprint adapter unnecessary system changes(many new or changed system DLL) should be avoided
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 55
Sample Adapter Source Code
Beside the API documentation a working sample adapter is shipped
The source code is available after installation
Analyzing the code helps understanding the Adapter Framework
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 56
Adapter Metadata
Adapter Metadata (AMD)XML file defines all configuration parameterseach adapter
AMD can be uploaded intoIntegration Iepositoryand SAP PCK
Configurationparameters are renderedinto the graphicalconfiguaration frontend
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 57
Adapter Metadata Fragment I
ltAdapterTypeMetaData version=09gt
ltTypegtNAESBltTypegt
ltInboundgt
ltTransportProtocolgt
ltChannelAttributesgt
ltAttributeGroupgt
ltNamegtCRYPTConfigurationltNamegt
ltGuiLabelsgtltLabel language=ENgtCryptographic ConfigurationltLabelgtltGuiLabelsgt
ltAttributeReferencegtltReferenceNamegtCRYPTUseSigningltReferenceNamegt
ltInboundgt
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 58
Adapter Metadata Fragment II
ltAttributegt
ltNamegtCRYPTUseSigningltNamegt
ltDataTypegtxsdbooleanltDataTypegt
ltGuiLabelsgt
ltLabel language=ENgtUse SigningltLabelgt
ltLabel language=DEgtVerwendung von SignierungltLabelgt
ltGuiLabelsgt
ltAttributegt
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 59
Adapter Configuration
Configuration attribute of type boolean is rendered to a check-box
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 60
Adapter Metadata Upload (PCK)
Integration Repositorydoes not exist in case ofSAP PCK installations
The upload mechanismfor Adaper Meta Datafor SAP PCK installationsrequires additonalparameters
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 61
AF CPA Cache
The Adapter configuration is deployed from the configuration time(SAP PCK or Integration Directory) to the J2EE service CPACache(Collaboration Profile Agreement)
The Adapter configuration can be accessed at runtime from withinadapter modules or JCA resource adapters via the CPACache API
The two main use cases are implemented inLookupManager to retrieve adapter configuation andNormalizationManager to retrieve Party information
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 62
Packaging Adapter Components
SAP recommends to use SAP Software Deployment Manager (SDM) for deployment
Software Delivery Archives (SDA) can contain software components of different types (eg applications libraries)
Detailed version information and dependencies to other components simplify program management
Adapter Modules and Development
Summary
Adapter Framework Overview
Adapter Strategy
Agenda
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 64
Summary
Adapter Framework runs on J2EE Stack of SAP Web AS
Adapter Framework is platform for Adapter Engine and SAP PCK
Adapter Framework provides an extensible platform for developing and running adapters
Adapter Engine utilizes central configuration monitoring administration
Dual connectivity strategyAdapter Framework for comprehensive integration of adaptersInteroperability via open standards to interop with EAI providers
SAP NetWeaver Certification for adapters based on Adapter Framework available
Adapter mappings metadata stored in Integration Repository
Adapter Modules and Development
Summary
Adapter Framework Overview
Adapter Strategy
Agenda
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 3
Integration Server
PlainJ2SE
Adapter Engine
Partner ConnectivityKitOptional non-central
Adapter EngineCentral Adapter Engine
Process Integration ndash Architecture
Integration Repository Integration Directory System Landscape Directory
Business Process Engine
Integration Engine
Adapter FrameworkMessagingQueuing
Security Handling
Resource
Adapter
Resource
Adapter
Resource
Adapter
Adapter FWMessagingQueuing
Security Handling
Adapter FWMessagingQueuing
Security Handling
PCK Configurationand Monitoring
HTTP
IDoc
Adapter
Adapter
FileDBJMSMarketplace
3rd Party Sys
FileDB
JMSSOAP
SAP ampNon-SAPSystem
FileDBJMSMarketplace
3rd Party Sys
FileDBJMSMarketplace
3rd Party Sys
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 4
Adapter Framework based on SAP J2EE Engine
Adapter Framework provides common functionality for Adapter Engine and SAP Partner Connectivity Kit
Adapter Framework is based on SAP J2EE Engine as part of SAP Web AS
Adapter Framework inherits properties and features such as scalability clustering high availability thread management etc
Adapter Framework provides its own queuing and logging services
Temporary stand-alone operation without connection to an Integration Server is possible while still providing e g guaranteed exactly once messaging to and from connected application system
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 5
JCA enabled Adapter Framework
Adapter Framework supports J2EE Connector Architecture (JCA)
JCA is standard architecture for connecting the J2EE platform toEnterprise Information Systems (EIS) e g ERP DBMS etcA Resource Adapter plugs into an application server providing connectivity between the EIS and a Java applicationJCA enabled Adapter Framework provides defined interfaces to which both our adapters and 3rd party adapters can conformJCA is a widely accepted standard that 3rd party adapter providers are familiar with
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 6
Central configuration administration monitoring
Additionally Adapter Framework provides comprehensive integration for central configuration administration monitoring of deployed adapters
One single point of access only one common UI enhanced transparancyAllows to movecopy configuration from one Adapter Framework to another (transportable configuration)
To transport configuration from test landscape to productive landscapeFor high availabilityfailover
Avoid redundant maintenance ensure consistencyEnd-to-end monitoring of the message flow over all components applications
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 7
ProxiesOutside-in development approachInterfaces designed centrally in Integration RepositoryConnect new SAP applications
Native connectivity to Application system (adapter-less)
AdaptersInside-out development approach Interface semantics externally pre-defined Connect existing (legacy) systemsSpecific wire protocol
Adapters vs Proxies
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 8
Integration Server
PlainJ2SE
Adapter Engine
Partner ConnectivityKitOptional non-central
Adapter EngineCentral Adapter Engine
Process Integration ndash Architecture
Integration Repository Integration Directory System Landscape Directory
Business Process Engine
Integration Engine
Adapter FrameworkMessagingQueuing
Security Handling
Resource
Adapter
Resource
Adapter
Resource
Adapter
Adapter FWMessagingQueuing
Security Handling
Adapter FWMessagingQueuing
Security Handling
PCK Configurationand Monitoring
HTTP
IDoc
Adapter
Adapter
FileDBJMSMarketplace
3rd Party Sys
FileDB
JMSSOAP
SAP ampNon-SAPSystem
FileDBJMSMarketplace
3rd Party Sys
FileDBJMSMarketplace
3rd Party Sys
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 9
Full integration of Adapter Engine
Adapter Engine is based on Adapter Framework
Adapter Engine fully integratedCentral configuration of connections to application systems (through appropriate adapters) in Integration DirectoryReuse of Integration Directoryrsquos existing versioning and transport capabilitiesCentral administration and monitoring over adapters IntegrationServer Integration Engine through Runtime Workbench
The Adapter Engine can be deployed centrally as part of Integration Server or as optional local Adapter Engine on its own SAP J2EE Server reasons for use of local Adapter Engine
Protocol of Sender- Receiver system (eg ftp not allowed)Performance High AvailabilityOrganizational Aspects IT requirements
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 10
PI Adapters developed by SAP
Technical AdaptersFileFTP (File Systems FTP Servers)JDBC (RDBMS systems)JMS (Messaging systems e g MQSeries SonicMQ)SOAP (Web Services)Plain HTTPMail (Mail Servers via SMTP IMAP4 POP3)SAP Business Connector (SAP BC)Marketplace (mySAP Marketplaces)
Application AdaptersRFCIDoc
Industry Standard AdaptersRNIF 20 (RosettaNet)RNIF 11 (RosettaNet)CIDX (RNIF 11)
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 11
Industry Standard Adapters as part of Business Packages
Business Package for RosettaNetOrder to Invoice Scenario
PIP3A4 Request Purchase Order PIP3A7 Notify of Purchase Order UpdatePIP3A8 Request Purchase Order ChangePIP3A9 Request Purchase Order CancellationPIP3B2 Notify of Advance ShipmentPIP3C3 Notify of Invoice PIP3A6 Distribute Order StatusPIP3C6 Notify of Remittance Advice
Business Package for CIDXOrder to Invoice Scenario
Order CreateOrder ResponseOrder ChangeShip NoticeInvoice
Business Packages include scenario descriptions business processes message interfaces message types mappings adapter etc
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 12
Partner Eco System
SAP relies on a system of partners to provide connectivity solutions for other applications and certain industry standards
Connectivity Reseller Agreements withSeeburger AGiWay SoftwareInformatica
3rd-Party solutions are sold and delivered through SAP
Technical support for partner solutions via theSAP Support Portal 24x7
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 13
PI Adapters by Seeburger (1)
Technical EDI AdaptersAS2 (EDIINTHTTP(S))Protocol AS2OFTPProtocol OFTPISDN OFTPTCPIPVAN AccessProtocol P7 X400 VAN FTP
Business EDI AdaptersGeneric EDIProtocol OFTPISDN or P7 X400 VAN FTPEDI Converter ANSI X12 EDIFACTMapping Templates Purchase order Order confirmation
Dispatch advice Invoice
Payment (Financial Service Providers)Protocol OFTPISDN P7 X400 VAN FTPEDI Converter EDIFACT SWIFTMapping Templates Payment orders Debit advice
Credit advice Account Statement
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 14
PI Adapters by Seeburger (2)
Industry Specific EDI AdaptersAerospace and Defense AutomotiveChemicals Consumer ProductsHigh-Tech PaperPharmaceutical Retail
Communication ProtocolsOFTPISDN P7 X400 VAN FTP
EDI Converter (EDI lt-gt XML)AECMASPEC 2000 ANSI X12 CHEM eStandards EDIFACT GALIAODETTE TRADACOM VDA
Mapping Templates within Integration RepositoryDelivery forecast Dispatch advise Invoice Purchase order Order confirmation
Message Library for Integration RepositoryHuge message catalog with EDI XML schema definitions
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 15
PI Adapters by iWay Software
Application AdaptersAriba BaanBroadvision ClarifyJD Edwards One World XE JD Edwards Worldi2 LawsonManugistics Microsoft CRMOracle Applications PeoplesoftQAD MFG Pro SiebelVantive
Industry Standard AdaptersSwift TransoraUCCnet
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 16
PI Adapters by iWay Software
Technical AdaptersAS1 (EDIINTSMTP) AS2 (EDIINTHTTP(S))BEA WLI COM+DCOMCorba Lotus NotesTibco Rendezvous
Mainframetransaction AdaptersCICS TMSIMSTelnet (3270) Telnet (5250) Tuxedo
Optionally further adapters can be added from a list of 160 iWayadapters e g HL7 (already certified) DB2 AS3 ebXML
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 17
SAP Conversion Agent by Informatica
Bi-directional conversion of unstructured and semi structured data from to XMLTransformation on message payloadProtocol support via SAPrsquos technical adapter (PI XI adapter framework)Transformations integrated via PI XI AF module
SAP J2EEPI XI Adapter Framework
Adapter
Adapter
Text2XML
XML2Excel
PDF2XML
ConversionAgent Studio
ConversionAgent Services
Conversion Agent Engine
CA AF Module
Conversion Agent J2EE Lib
Seamlessly integrated into Process Integration
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 18
Supported Data Formats by Informatica (partial list)
UNSTRUCTUREDMicrosoft WordMicrosoft ExcelPowerPointPDFStar OfficeWord PerfectASCII reportsHTMLEBCDICUndocumented binariesFlat filesRPGANSI
PRINT STREAMSAFPPost ScriptDJDE
SEMI-STRUCTURED HL7HIPAAASTMANSIndashX12EDIFACTCOBOLFIXCargo IMPMVRSWIFT
OTHER STANDARDSLegalXMLIFX cXMLebXML HL7 V30 ACORD (AL3 XML)
hellip using SAP technical adapter and Conversion Agent
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 19
Conversion Agent
Bi-directional conversion of unstructured and semi structured formats fromto XMLLinked through PI XI adapter framework module based on SAPrsquos technical adapter ndash no transport protocol manipulates payload informationSAP NetWeaver-wide use (via J2EE library)
3rd Party Adapters
Bi-directional conversion of one dedicated data format (eg SWIFT ANSI-X12 hellip) fromto XMLRuns within PI XI adapter framework - support payload transformation and transport protocol
Per adapter dedicated use within one SAP NetWeaver component
Conversion Agent vs 3rd Party Adapters
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 20
More Info about Connectivity Capabilities
httpservicesapcomxi xi in detail connectivity
Connectivity and Interoperability
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 21
Adapter Download from SAP Service Marketplace
SAP Service Marketplace httpservicesapcomswdc Download Installations and Upgrades Entry by Application Group Adapters
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 22
Certification Programs for Process Integration
httpwwwsdnsapcom Partners and ISVsIntegration and Certification Exchange Infrastructure
PI Based Certification Programs
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 23
Public info about certified PI adapters
httpwwwsapcompartnersdirectoriesSearchSolutionepxThird Party Defined Integration Scenarios NW-XI-AF 30
Certified PI Adapters
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 24
Adapter Configuration
Adapter independent parameters
Adapter specific parameters
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 25
Configurationcache
Adapter Engine
ISRuntime
AdapterSender
AdapterReceiver
Adapter Engine in SAP J2EE
Q
Administration
Security
Monitoring
Adapter-Specific
ComponentServices
TracingLogging
Module ProcessorEIS
Channel
acuteMessaging
Configcache
End-to-End MonitoringMessage flow over all components applications
Runtime Workbenchbull Uis for adminstration
monitoring
Integration Builder Directory
Receiver determinationbull Party-gtService-gtAction
Channel Definitionbull Adapter Enginebull Adapter Typebull Message Protocolbull Transport Protocolbull Securitybull Channel Configuration
(Sender Receiver Agreementbull PartyServiceAction lt-gt Channel
ConfigurationMaster
System Landscape Directorybull Holds component description
including address data
AdapterFramework
Integration Repositorybull Holds Adapter metadataIntegration Repositorybull Holds Adapter metadata
httpltIntegrationServerURLgt
Message
httpltAdapterEngineURLgt
OK Error
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 26
Transport Level Security
Transport Protocol Authentication
IDoc RFC and SNC Client Authentication
Client Authentication
Client Authentication
Client Authentication
Client Authentication
CRAM-MD5
Client Authentication
Client Authentication
Client Authentication
CDIX ndash Adapter HTTPs Client Authentication
RFC RFC and SNC
Plain HTTP HTTPs
FileFTP File Transfer Protocol using SSLTLS
SOAP HTTPsSMTPs (Receiver only)
Mail SMTPs POP3 IMAP4
Marketplace HTTPs
RNIF 20 ndash Adapter HTTPs
RNIF 11 ndash Adapter HTTPs
Supported by
Levels of Security
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 27
Message Level Security
Signature Non-Repudiation
of origin
Non-Repudiation of
receipt
Encryption
CDIX ndash Adapter PKCS7
Technology
XI protocol WS-Security
SOAP-Adapter WS-Security
SMIME
Mail-Adapter SMIME
RNIF 20 ndash Adapter SMIME
RNIF 11 ndash Adapter PKCS7
Supported by
Levels of Security
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 28
Access control list
Restrict access to the runtime environmentfor sender services of type Business Service or Business Systemfor interfaces of these sender services
Restrict access to particular (service) users
Check authorization at runtime
Configure access control in the Integration DirectorySender service Specify authorized users in the configuration of the corresponding (sender) serviceInterface Specify authorized users in the configuration of the relevant sender agreement which contains the interface in the object key
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 29
Dynamic Adapter Configuration
Enable adapters to read write dynamic message headers
Sender Adapter (constructing messages)Attach adapter specific information to message headerExamples File name source file size JMS timestamp mail subjectRead access to these attributes in receiver channel interface determination (routing) mapping
Receiver Adapter (consuming messages)Read attributes to overwrite values of channel configurationExamples Directory Name JMS Priority Mail Sender SOAP target URLSet attributes in mapping orUse attributes from sender in receiver channel
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 30
Sender Adapter Configuration (1)
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 31
Sender Adapter Configuration (2)
Add the filename et al to the message
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 32
Receiver Determination
Determinefilename-dependent receiver
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 33
Receiver Adapter
Store the file withthe name set in the messageattribute
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 34
Monitoring Adapter Engine
After selecting a message bdquoDetailsldquo View
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 35
Monitoring Integration Server
After selecting a message bdquoDisplayldquo
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 36
Remark Future of SAP XI 20 Adapter Engine
SAP XI 20 Adapter Engine is available in SAP NW acute04 and SAP NW 2004s as bdquoPlain J2SE Adapter Engineldquo
Functional scope as in SAP XI 20Adopted to the SAP XI 30 message protocolMinor maintenance issues bug fixes
RecommendationUse where platform requirements or limitations (hardware operating system JVM support) demand it
SAP XI 20 Adapter Engine works with SAP NW acute04 and SAP NW 2004s landscapes too
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 37
Integration Server
PlainJ2SE
Adapter Engine
Partner ConnectivityKitOptional non-central
Adapter EngineCentral Adapter Engine
Process Integration ndash Architecture
Integration Repository Integration Directory System Landscape Directory
Business Process Engine
Integration Engine
Adapter FrameworkMessagingQueuing
Security Handling
Resource
Adapter
Resource
Adapter
Resource
Adapter
Adapter FWMessagingQueuing
Security Handling
Adapter FWMessagingQueuing
Security Handling
PCK Configurationand Monitoring
HTTP
IDoc
Adapter
Adapter
FileDBJMSMarketplace
3rd Party Sys
FileDB
JMSSOAP
SAP ampNon-SAPSystem
FileDBJMSMarketplace
3rd Party Sys
FileDBJMSMarketplace
3rd Party Sys
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 38
SAP Partner Connectivity Kit Overview
SAP 3rdParty Appl PI XI
Smaller Company Subsidiary
SAPPCK
SAPApplication
3rd PartyApplication
Large Business Partner Headquarter
Internet
Enablement of smaller companies subsidiaries to exchange XML documents with their business partnerrsquos headquarterrsquos PI XI
SAPPCK
Providing a platform for development of own JCA Resource Adapters
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 39
SAP PCK ndash Adapters
SAP Partner Connectivity Kit (PCK) is based on Adapter Framework
SAP PCKlsquos objective is to enable XML document exchangebetween PI XI and business partner not using PI XI
SAP PCK also provides an extensible platform for developing and running individual JCA Resource adapters
Communication between PI XI and SAP PCK is via SAP XI messaging protocol
SAP PCK Includes the following adapters FileFTP JDBC JMS SOAP RFC IDoc (once available for SAP PCK) Mail SAP BC
Optionally SAP PCK can host further adapters that are available from SAP or 3rd party adapter providers
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 40
SAP PCK ndash Configuration Mapping
SAP PCK is deployed on stand-alone SAP J2EE Engine (part of SAP Web AS) within business partnerrsquos landscape
Configuration administration monitoring done locally on SAP PCK itself without need for an Integration Directory
Configuration UI provides same bdquolook and feelldquo as configuration UI of Adapter Engine
SAP PCK supports the development of message mappings using an integrated graphical mapping editor
Any source XML structure can be mapped to any target XML structureStandard functions are provided to perform calculations Boolean comparisons text mappings and other transformationsOptionally the standard functions can be enhanced with user-defined functions in Java
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 41
SAP PCK ndash Configuration UI
ConfigurationUI to configure Party Service Communication Channel Sender and Receiver agreementsSample screenshot for configuration of communication channel with adapter type sbquoFile FTPlsquo
Adapter Modules and Development
Summary
Adapter Framework Overview
Adapter Strategy
Agenda
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 43
SAP Exchange Infrastructure - Openness
Integration of SAP and non-SAP applicationsAdapter Framework for comprehensive integration of adaptersAdapters are used for technical connectivityAdapter metadata mappings are stored in Integration Repository
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 44
Dual Strategy
Dual connectivity strategyAdapter Framework for comprehensive integration of adapters to provide technical connectivity including central configurationadministration monitoring of adaptersInteroperability based on open standards (SOAP JMS HTTP(S)) tointeroperate with EAI providers
Value propositionStandardized interfaces allow easy integration of adapters from different partnersMinimum knowledge of end-to-end process integration requiredComprehensive integration avoids redundant maintenance ensures consistency enhances transparancyOpenness to integrate non-SAP applications 3rd party systems etcReduced TCO
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 45
Certification
CertificationSAP NetWeaver Certification of 3rd party adapters based on the adapter framework
Value propositionQuality (stability HA aspects performance etc) of adapters is controlledCertification helps customers to find right solutionQuick and convenient search for a variety of certified products with the online partner and product directory (httpwwwsapcompartnersdirectoriesSearchSolutionepx)Faster implementation time and lower integration costs through the use of tested 3rd party integrationReduced TCO
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 46
Adapter Mappings Metadata in Integration Repository
Adapter mappings and adapter metadata are stored in the Integration Repository
Centralized Integration Repository contains all relevant information for collaborative and integrative processesAll content adheres to open standards Adapters provide technical connectivity
Value propositionUse largest content catalogReduce costs in integration projectsReduce maintenance costsReduced TCO
Adapter Modules and Development
Summary
Adapter Framework Overview
Adapter Strategy
Agenda
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 48
For every adapter it is possible to define generic modules in the module processor possibility to extend the functionality of the specific adapter
Equivalent to the dispatcher classes in the J2SE adapter engine migration and examples
The default module configuration for the certain adapter is displayed in the channel configuration
Modules are EJBlsquos
Sequence matters
Module Processor Concept
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 49
Adapter Module Chain
Custom modulescan be added to default modulechains
Additional configurationparameters canbe specified eachmodule
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 50
Module Processor Documentation
SAP Help Portal (httphelpsapcom)SAP XI Runtime Connectivity Adapters Module ProcessorFeedback Mail to xidocumentationsapcom
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 51
Development Environment
Adapter development deployment and testing is possible on a single machine no full-blown PI XI is required
For testing purposes integration scenarioscan be configured in SAP PCK(eg loopback scenario)
Installation of SAP PCK already contains a sample adapter (including Adapter Meta Data) that should serve as a starting point
SAP Partner ConnectivityKit
Adapter FWMessagingQueuing
Security Handling
Resource
Adapter
PCK Configurationand Monitoring
FileDBJMSMarketplace
3rd Party Sys
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 52
Adapter Development Documentation
SAP Help Portal (httphelpsapcom)SAP XI Runtime Connectivity Partner Connectivity Kit Adapter DevelopmentFeedback Mail to xidocumentationsapcom
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 53
Requirements for Adapters (1)
Num AF Interface Category Description
1 JCA 10 conformance Mandatory Adapter must fulfill JCA 10 requirements (e g deployment) plus optional JCA 15 parts which are used by PI XI
2 AF Message Exchange Mandatory Adapter must be able to receive messages from AF and forward them to connected system and vice versa
3 AF Adapter Specific Modules
Optional SAP XI message and protocol conversion may be done entirely by the adapter or as adapter specific module and being called in the AF module chain context
4 Configuration Services Mandatory Unique configuration approach to manage adapters
5 Administrational Services
Optional Administration and Monitoring
6 Utility Service Mandatory Access to basic J2EE resources e g transactions and multithreading must be under control of J2EE server
7 Logging API Optional Adapters may use their own logging
8 Message Metadata Exchange
Optional Provide structure definition of message payloadIf not supported the definition of message types can be done in the Integration Repository
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 54
Requirements for Adapters (2)
Cluster-enabledConsider side-effects of clustering e g bdquoExactlyOnceInOrderldquo Avoid passing maneuvers
SpecializationBuild connection to exactly one type of business system or industrystandard protocol
DirectnessBuild connection to business system or industry standard protocoldirectly without any intermediate software components
SmoothnessLight-weighted low footprint adapter unnecessary system changes(many new or changed system DLL) should be avoided
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 55
Sample Adapter Source Code
Beside the API documentation a working sample adapter is shipped
The source code is available after installation
Analyzing the code helps understanding the Adapter Framework
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 56
Adapter Metadata
Adapter Metadata (AMD)XML file defines all configuration parameterseach adapter
AMD can be uploaded intoIntegration Iepositoryand SAP PCK
Configurationparameters are renderedinto the graphicalconfiguaration frontend
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 57
Adapter Metadata Fragment I
ltAdapterTypeMetaData version=09gt
ltTypegtNAESBltTypegt
ltInboundgt
ltTransportProtocolgt
ltChannelAttributesgt
ltAttributeGroupgt
ltNamegtCRYPTConfigurationltNamegt
ltGuiLabelsgtltLabel language=ENgtCryptographic ConfigurationltLabelgtltGuiLabelsgt
ltAttributeReferencegtltReferenceNamegtCRYPTUseSigningltReferenceNamegt
ltInboundgt
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 58
Adapter Metadata Fragment II
ltAttributegt
ltNamegtCRYPTUseSigningltNamegt
ltDataTypegtxsdbooleanltDataTypegt
ltGuiLabelsgt
ltLabel language=ENgtUse SigningltLabelgt
ltLabel language=DEgtVerwendung von SignierungltLabelgt
ltGuiLabelsgt
ltAttributegt
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 59
Adapter Configuration
Configuration attribute of type boolean is rendered to a check-box
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 60
Adapter Metadata Upload (PCK)
Integration Repositorydoes not exist in case ofSAP PCK installations
The upload mechanismfor Adaper Meta Datafor SAP PCK installationsrequires additonalparameters
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 61
AF CPA Cache
The Adapter configuration is deployed from the configuration time(SAP PCK or Integration Directory) to the J2EE service CPACache(Collaboration Profile Agreement)
The Adapter configuration can be accessed at runtime from withinadapter modules or JCA resource adapters via the CPACache API
The two main use cases are implemented inLookupManager to retrieve adapter configuation andNormalizationManager to retrieve Party information
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 62
Packaging Adapter Components
SAP recommends to use SAP Software Deployment Manager (SDM) for deployment
Software Delivery Archives (SDA) can contain software components of different types (eg applications libraries)
Detailed version information and dependencies to other components simplify program management
Adapter Modules and Development
Summary
Adapter Framework Overview
Adapter Strategy
Agenda
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 64
Summary
Adapter Framework runs on J2EE Stack of SAP Web AS
Adapter Framework is platform for Adapter Engine and SAP PCK
Adapter Framework provides an extensible platform for developing and running adapters
Adapter Engine utilizes central configuration monitoring administration
Dual connectivity strategyAdapter Framework for comprehensive integration of adaptersInteroperability via open standards to interop with EAI providers
SAP NetWeaver Certification for adapters based on Adapter Framework available
Adapter mappings metadata stored in Integration Repository
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 3
Integration Server
PlainJ2SE
Adapter Engine
Partner ConnectivityKitOptional non-central
Adapter EngineCentral Adapter Engine
Process Integration ndash Architecture
Integration Repository Integration Directory System Landscape Directory
Business Process Engine
Integration Engine
Adapter FrameworkMessagingQueuing
Security Handling
Resource
Adapter
Resource
Adapter
Resource
Adapter
Adapter FWMessagingQueuing
Security Handling
Adapter FWMessagingQueuing
Security Handling
PCK Configurationand Monitoring
HTTP
IDoc
Adapter
Adapter
FileDBJMSMarketplace
3rd Party Sys
FileDB
JMSSOAP
SAP ampNon-SAPSystem
FileDBJMSMarketplace
3rd Party Sys
FileDBJMSMarketplace
3rd Party Sys
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 4
Adapter Framework based on SAP J2EE Engine
Adapter Framework provides common functionality for Adapter Engine and SAP Partner Connectivity Kit
Adapter Framework is based on SAP J2EE Engine as part of SAP Web AS
Adapter Framework inherits properties and features such as scalability clustering high availability thread management etc
Adapter Framework provides its own queuing and logging services
Temporary stand-alone operation without connection to an Integration Server is possible while still providing e g guaranteed exactly once messaging to and from connected application system
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 5
JCA enabled Adapter Framework
Adapter Framework supports J2EE Connector Architecture (JCA)
JCA is standard architecture for connecting the J2EE platform toEnterprise Information Systems (EIS) e g ERP DBMS etcA Resource Adapter plugs into an application server providing connectivity between the EIS and a Java applicationJCA enabled Adapter Framework provides defined interfaces to which both our adapters and 3rd party adapters can conformJCA is a widely accepted standard that 3rd party adapter providers are familiar with
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 6
Central configuration administration monitoring
Additionally Adapter Framework provides comprehensive integration for central configuration administration monitoring of deployed adapters
One single point of access only one common UI enhanced transparancyAllows to movecopy configuration from one Adapter Framework to another (transportable configuration)
To transport configuration from test landscape to productive landscapeFor high availabilityfailover
Avoid redundant maintenance ensure consistencyEnd-to-end monitoring of the message flow over all components applications
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 7
ProxiesOutside-in development approachInterfaces designed centrally in Integration RepositoryConnect new SAP applications
Native connectivity to Application system (adapter-less)
AdaptersInside-out development approach Interface semantics externally pre-defined Connect existing (legacy) systemsSpecific wire protocol
Adapters vs Proxies
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 8
Integration Server
PlainJ2SE
Adapter Engine
Partner ConnectivityKitOptional non-central
Adapter EngineCentral Adapter Engine
Process Integration ndash Architecture
Integration Repository Integration Directory System Landscape Directory
Business Process Engine
Integration Engine
Adapter FrameworkMessagingQueuing
Security Handling
Resource
Adapter
Resource
Adapter
Resource
Adapter
Adapter FWMessagingQueuing
Security Handling
Adapter FWMessagingQueuing
Security Handling
PCK Configurationand Monitoring
HTTP
IDoc
Adapter
Adapter
FileDBJMSMarketplace
3rd Party Sys
FileDB
JMSSOAP
SAP ampNon-SAPSystem
FileDBJMSMarketplace
3rd Party Sys
FileDBJMSMarketplace
3rd Party Sys
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 9
Full integration of Adapter Engine
Adapter Engine is based on Adapter Framework
Adapter Engine fully integratedCentral configuration of connections to application systems (through appropriate adapters) in Integration DirectoryReuse of Integration Directoryrsquos existing versioning and transport capabilitiesCentral administration and monitoring over adapters IntegrationServer Integration Engine through Runtime Workbench
The Adapter Engine can be deployed centrally as part of Integration Server or as optional local Adapter Engine on its own SAP J2EE Server reasons for use of local Adapter Engine
Protocol of Sender- Receiver system (eg ftp not allowed)Performance High AvailabilityOrganizational Aspects IT requirements
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 10
PI Adapters developed by SAP
Technical AdaptersFileFTP (File Systems FTP Servers)JDBC (RDBMS systems)JMS (Messaging systems e g MQSeries SonicMQ)SOAP (Web Services)Plain HTTPMail (Mail Servers via SMTP IMAP4 POP3)SAP Business Connector (SAP BC)Marketplace (mySAP Marketplaces)
Application AdaptersRFCIDoc
Industry Standard AdaptersRNIF 20 (RosettaNet)RNIF 11 (RosettaNet)CIDX (RNIF 11)
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 11
Industry Standard Adapters as part of Business Packages
Business Package for RosettaNetOrder to Invoice Scenario
PIP3A4 Request Purchase Order PIP3A7 Notify of Purchase Order UpdatePIP3A8 Request Purchase Order ChangePIP3A9 Request Purchase Order CancellationPIP3B2 Notify of Advance ShipmentPIP3C3 Notify of Invoice PIP3A6 Distribute Order StatusPIP3C6 Notify of Remittance Advice
Business Package for CIDXOrder to Invoice Scenario
Order CreateOrder ResponseOrder ChangeShip NoticeInvoice
Business Packages include scenario descriptions business processes message interfaces message types mappings adapter etc
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 12
Partner Eco System
SAP relies on a system of partners to provide connectivity solutions for other applications and certain industry standards
Connectivity Reseller Agreements withSeeburger AGiWay SoftwareInformatica
3rd-Party solutions are sold and delivered through SAP
Technical support for partner solutions via theSAP Support Portal 24x7
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 13
PI Adapters by Seeburger (1)
Technical EDI AdaptersAS2 (EDIINTHTTP(S))Protocol AS2OFTPProtocol OFTPISDN OFTPTCPIPVAN AccessProtocol P7 X400 VAN FTP
Business EDI AdaptersGeneric EDIProtocol OFTPISDN or P7 X400 VAN FTPEDI Converter ANSI X12 EDIFACTMapping Templates Purchase order Order confirmation
Dispatch advice Invoice
Payment (Financial Service Providers)Protocol OFTPISDN P7 X400 VAN FTPEDI Converter EDIFACT SWIFTMapping Templates Payment orders Debit advice
Credit advice Account Statement
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 14
PI Adapters by Seeburger (2)
Industry Specific EDI AdaptersAerospace and Defense AutomotiveChemicals Consumer ProductsHigh-Tech PaperPharmaceutical Retail
Communication ProtocolsOFTPISDN P7 X400 VAN FTP
EDI Converter (EDI lt-gt XML)AECMASPEC 2000 ANSI X12 CHEM eStandards EDIFACT GALIAODETTE TRADACOM VDA
Mapping Templates within Integration RepositoryDelivery forecast Dispatch advise Invoice Purchase order Order confirmation
Message Library for Integration RepositoryHuge message catalog with EDI XML schema definitions
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 15
PI Adapters by iWay Software
Application AdaptersAriba BaanBroadvision ClarifyJD Edwards One World XE JD Edwards Worldi2 LawsonManugistics Microsoft CRMOracle Applications PeoplesoftQAD MFG Pro SiebelVantive
Industry Standard AdaptersSwift TransoraUCCnet
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 16
PI Adapters by iWay Software
Technical AdaptersAS1 (EDIINTSMTP) AS2 (EDIINTHTTP(S))BEA WLI COM+DCOMCorba Lotus NotesTibco Rendezvous
Mainframetransaction AdaptersCICS TMSIMSTelnet (3270) Telnet (5250) Tuxedo
Optionally further adapters can be added from a list of 160 iWayadapters e g HL7 (already certified) DB2 AS3 ebXML
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 17
SAP Conversion Agent by Informatica
Bi-directional conversion of unstructured and semi structured data from to XMLTransformation on message payloadProtocol support via SAPrsquos technical adapter (PI XI adapter framework)Transformations integrated via PI XI AF module
SAP J2EEPI XI Adapter Framework
Adapter
Adapter
Text2XML
XML2Excel
PDF2XML
ConversionAgent Studio
ConversionAgent Services
Conversion Agent Engine
CA AF Module
Conversion Agent J2EE Lib
Seamlessly integrated into Process Integration
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 18
Supported Data Formats by Informatica (partial list)
UNSTRUCTUREDMicrosoft WordMicrosoft ExcelPowerPointPDFStar OfficeWord PerfectASCII reportsHTMLEBCDICUndocumented binariesFlat filesRPGANSI
PRINT STREAMSAFPPost ScriptDJDE
SEMI-STRUCTURED HL7HIPAAASTMANSIndashX12EDIFACTCOBOLFIXCargo IMPMVRSWIFT
OTHER STANDARDSLegalXMLIFX cXMLebXML HL7 V30 ACORD (AL3 XML)
hellip using SAP technical adapter and Conversion Agent
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 19
Conversion Agent
Bi-directional conversion of unstructured and semi structured formats fromto XMLLinked through PI XI adapter framework module based on SAPrsquos technical adapter ndash no transport protocol manipulates payload informationSAP NetWeaver-wide use (via J2EE library)
3rd Party Adapters
Bi-directional conversion of one dedicated data format (eg SWIFT ANSI-X12 hellip) fromto XMLRuns within PI XI adapter framework - support payload transformation and transport protocol
Per adapter dedicated use within one SAP NetWeaver component
Conversion Agent vs 3rd Party Adapters
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 20
More Info about Connectivity Capabilities
httpservicesapcomxi xi in detail connectivity
Connectivity and Interoperability
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 21
Adapter Download from SAP Service Marketplace
SAP Service Marketplace httpservicesapcomswdc Download Installations and Upgrades Entry by Application Group Adapters
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 22
Certification Programs for Process Integration
httpwwwsdnsapcom Partners and ISVsIntegration and Certification Exchange Infrastructure
PI Based Certification Programs
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 23
Public info about certified PI adapters
httpwwwsapcompartnersdirectoriesSearchSolutionepxThird Party Defined Integration Scenarios NW-XI-AF 30
Certified PI Adapters
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 24
Adapter Configuration
Adapter independent parameters
Adapter specific parameters
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 25
Configurationcache
Adapter Engine
ISRuntime
AdapterSender
AdapterReceiver
Adapter Engine in SAP J2EE
Q
Administration
Security
Monitoring
Adapter-Specific
ComponentServices
TracingLogging
Module ProcessorEIS
Channel
acuteMessaging
Configcache
End-to-End MonitoringMessage flow over all components applications
Runtime Workbenchbull Uis for adminstration
monitoring
Integration Builder Directory
Receiver determinationbull Party-gtService-gtAction
Channel Definitionbull Adapter Enginebull Adapter Typebull Message Protocolbull Transport Protocolbull Securitybull Channel Configuration
(Sender Receiver Agreementbull PartyServiceAction lt-gt Channel
ConfigurationMaster
System Landscape Directorybull Holds component description
including address data
AdapterFramework
Integration Repositorybull Holds Adapter metadataIntegration Repositorybull Holds Adapter metadata
httpltIntegrationServerURLgt
Message
httpltAdapterEngineURLgt
OK Error
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 26
Transport Level Security
Transport Protocol Authentication
IDoc RFC and SNC Client Authentication
Client Authentication
Client Authentication
Client Authentication
Client Authentication
CRAM-MD5
Client Authentication
Client Authentication
Client Authentication
CDIX ndash Adapter HTTPs Client Authentication
RFC RFC and SNC
Plain HTTP HTTPs
FileFTP File Transfer Protocol using SSLTLS
SOAP HTTPsSMTPs (Receiver only)
Mail SMTPs POP3 IMAP4
Marketplace HTTPs
RNIF 20 ndash Adapter HTTPs
RNIF 11 ndash Adapter HTTPs
Supported by
Levels of Security
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 27
Message Level Security
Signature Non-Repudiation
of origin
Non-Repudiation of
receipt
Encryption
CDIX ndash Adapter PKCS7
Technology
XI protocol WS-Security
SOAP-Adapter WS-Security
SMIME
Mail-Adapter SMIME
RNIF 20 ndash Adapter SMIME
RNIF 11 ndash Adapter PKCS7
Supported by
Levels of Security
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 28
Access control list
Restrict access to the runtime environmentfor sender services of type Business Service or Business Systemfor interfaces of these sender services
Restrict access to particular (service) users
Check authorization at runtime
Configure access control in the Integration DirectorySender service Specify authorized users in the configuration of the corresponding (sender) serviceInterface Specify authorized users in the configuration of the relevant sender agreement which contains the interface in the object key
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 29
Dynamic Adapter Configuration
Enable adapters to read write dynamic message headers
Sender Adapter (constructing messages)Attach adapter specific information to message headerExamples File name source file size JMS timestamp mail subjectRead access to these attributes in receiver channel interface determination (routing) mapping
Receiver Adapter (consuming messages)Read attributes to overwrite values of channel configurationExamples Directory Name JMS Priority Mail Sender SOAP target URLSet attributes in mapping orUse attributes from sender in receiver channel
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 30
Sender Adapter Configuration (1)
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 31
Sender Adapter Configuration (2)
Add the filename et al to the message
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 32
Receiver Determination
Determinefilename-dependent receiver
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 33
Receiver Adapter
Store the file withthe name set in the messageattribute
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 34
Monitoring Adapter Engine
After selecting a message bdquoDetailsldquo View
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 35
Monitoring Integration Server
After selecting a message bdquoDisplayldquo
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 36
Remark Future of SAP XI 20 Adapter Engine
SAP XI 20 Adapter Engine is available in SAP NW acute04 and SAP NW 2004s as bdquoPlain J2SE Adapter Engineldquo
Functional scope as in SAP XI 20Adopted to the SAP XI 30 message protocolMinor maintenance issues bug fixes
RecommendationUse where platform requirements or limitations (hardware operating system JVM support) demand it
SAP XI 20 Adapter Engine works with SAP NW acute04 and SAP NW 2004s landscapes too
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 37
Integration Server
PlainJ2SE
Adapter Engine
Partner ConnectivityKitOptional non-central
Adapter EngineCentral Adapter Engine
Process Integration ndash Architecture
Integration Repository Integration Directory System Landscape Directory
Business Process Engine
Integration Engine
Adapter FrameworkMessagingQueuing
Security Handling
Resource
Adapter
Resource
Adapter
Resource
Adapter
Adapter FWMessagingQueuing
Security Handling
Adapter FWMessagingQueuing
Security Handling
PCK Configurationand Monitoring
HTTP
IDoc
Adapter
Adapter
FileDBJMSMarketplace
3rd Party Sys
FileDB
JMSSOAP
SAP ampNon-SAPSystem
FileDBJMSMarketplace
3rd Party Sys
FileDBJMSMarketplace
3rd Party Sys
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 38
SAP Partner Connectivity Kit Overview
SAP 3rdParty Appl PI XI
Smaller Company Subsidiary
SAPPCK
SAPApplication
3rd PartyApplication
Large Business Partner Headquarter
Internet
Enablement of smaller companies subsidiaries to exchange XML documents with their business partnerrsquos headquarterrsquos PI XI
SAPPCK
Providing a platform for development of own JCA Resource Adapters
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 39
SAP PCK ndash Adapters
SAP Partner Connectivity Kit (PCK) is based on Adapter Framework
SAP PCKlsquos objective is to enable XML document exchangebetween PI XI and business partner not using PI XI
SAP PCK also provides an extensible platform for developing and running individual JCA Resource adapters
Communication between PI XI and SAP PCK is via SAP XI messaging protocol
SAP PCK Includes the following adapters FileFTP JDBC JMS SOAP RFC IDoc (once available for SAP PCK) Mail SAP BC
Optionally SAP PCK can host further adapters that are available from SAP or 3rd party adapter providers
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 40
SAP PCK ndash Configuration Mapping
SAP PCK is deployed on stand-alone SAP J2EE Engine (part of SAP Web AS) within business partnerrsquos landscape
Configuration administration monitoring done locally on SAP PCK itself without need for an Integration Directory
Configuration UI provides same bdquolook and feelldquo as configuration UI of Adapter Engine
SAP PCK supports the development of message mappings using an integrated graphical mapping editor
Any source XML structure can be mapped to any target XML structureStandard functions are provided to perform calculations Boolean comparisons text mappings and other transformationsOptionally the standard functions can be enhanced with user-defined functions in Java
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 41
SAP PCK ndash Configuration UI
ConfigurationUI to configure Party Service Communication Channel Sender and Receiver agreementsSample screenshot for configuration of communication channel with adapter type sbquoFile FTPlsquo
Adapter Modules and Development
Summary
Adapter Framework Overview
Adapter Strategy
Agenda
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 43
SAP Exchange Infrastructure - Openness
Integration of SAP and non-SAP applicationsAdapter Framework for comprehensive integration of adaptersAdapters are used for technical connectivityAdapter metadata mappings are stored in Integration Repository
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 44
Dual Strategy
Dual connectivity strategyAdapter Framework for comprehensive integration of adapters to provide technical connectivity including central configurationadministration monitoring of adaptersInteroperability based on open standards (SOAP JMS HTTP(S)) tointeroperate with EAI providers
Value propositionStandardized interfaces allow easy integration of adapters from different partnersMinimum knowledge of end-to-end process integration requiredComprehensive integration avoids redundant maintenance ensures consistency enhances transparancyOpenness to integrate non-SAP applications 3rd party systems etcReduced TCO
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 45
Certification
CertificationSAP NetWeaver Certification of 3rd party adapters based on the adapter framework
Value propositionQuality (stability HA aspects performance etc) of adapters is controlledCertification helps customers to find right solutionQuick and convenient search for a variety of certified products with the online partner and product directory (httpwwwsapcompartnersdirectoriesSearchSolutionepx)Faster implementation time and lower integration costs through the use of tested 3rd party integrationReduced TCO
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 46
Adapter Mappings Metadata in Integration Repository
Adapter mappings and adapter metadata are stored in the Integration Repository
Centralized Integration Repository contains all relevant information for collaborative and integrative processesAll content adheres to open standards Adapters provide technical connectivity
Value propositionUse largest content catalogReduce costs in integration projectsReduce maintenance costsReduced TCO
Adapter Modules and Development
Summary
Adapter Framework Overview
Adapter Strategy
Agenda
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 48
For every adapter it is possible to define generic modules in the module processor possibility to extend the functionality of the specific adapter
Equivalent to the dispatcher classes in the J2SE adapter engine migration and examples
The default module configuration for the certain adapter is displayed in the channel configuration
Modules are EJBlsquos
Sequence matters
Module Processor Concept
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 49
Adapter Module Chain
Custom modulescan be added to default modulechains
Additional configurationparameters canbe specified eachmodule
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 50
Module Processor Documentation
SAP Help Portal (httphelpsapcom)SAP XI Runtime Connectivity Adapters Module ProcessorFeedback Mail to xidocumentationsapcom
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 51
Development Environment
Adapter development deployment and testing is possible on a single machine no full-blown PI XI is required
For testing purposes integration scenarioscan be configured in SAP PCK(eg loopback scenario)
Installation of SAP PCK already contains a sample adapter (including Adapter Meta Data) that should serve as a starting point
SAP Partner ConnectivityKit
Adapter FWMessagingQueuing
Security Handling
Resource
Adapter
PCK Configurationand Monitoring
FileDBJMSMarketplace
3rd Party Sys
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 52
Adapter Development Documentation
SAP Help Portal (httphelpsapcom)SAP XI Runtime Connectivity Partner Connectivity Kit Adapter DevelopmentFeedback Mail to xidocumentationsapcom
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 53
Requirements for Adapters (1)
Num AF Interface Category Description
1 JCA 10 conformance Mandatory Adapter must fulfill JCA 10 requirements (e g deployment) plus optional JCA 15 parts which are used by PI XI
2 AF Message Exchange Mandatory Adapter must be able to receive messages from AF and forward them to connected system and vice versa
3 AF Adapter Specific Modules
Optional SAP XI message and protocol conversion may be done entirely by the adapter or as adapter specific module and being called in the AF module chain context
4 Configuration Services Mandatory Unique configuration approach to manage adapters
5 Administrational Services
Optional Administration and Monitoring
6 Utility Service Mandatory Access to basic J2EE resources e g transactions and multithreading must be under control of J2EE server
7 Logging API Optional Adapters may use their own logging
8 Message Metadata Exchange
Optional Provide structure definition of message payloadIf not supported the definition of message types can be done in the Integration Repository
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 54
Requirements for Adapters (2)
Cluster-enabledConsider side-effects of clustering e g bdquoExactlyOnceInOrderldquo Avoid passing maneuvers
SpecializationBuild connection to exactly one type of business system or industrystandard protocol
DirectnessBuild connection to business system or industry standard protocoldirectly without any intermediate software components
SmoothnessLight-weighted low footprint adapter unnecessary system changes(many new or changed system DLL) should be avoided
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 55
Sample Adapter Source Code
Beside the API documentation a working sample adapter is shipped
The source code is available after installation
Analyzing the code helps understanding the Adapter Framework
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 56
Adapter Metadata
Adapter Metadata (AMD)XML file defines all configuration parameterseach adapter
AMD can be uploaded intoIntegration Iepositoryand SAP PCK
Configurationparameters are renderedinto the graphicalconfiguaration frontend
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 57
Adapter Metadata Fragment I
ltAdapterTypeMetaData version=09gt
ltTypegtNAESBltTypegt
ltInboundgt
ltTransportProtocolgt
ltChannelAttributesgt
ltAttributeGroupgt
ltNamegtCRYPTConfigurationltNamegt
ltGuiLabelsgtltLabel language=ENgtCryptographic ConfigurationltLabelgtltGuiLabelsgt
ltAttributeReferencegtltReferenceNamegtCRYPTUseSigningltReferenceNamegt
ltInboundgt
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 58
Adapter Metadata Fragment II
ltAttributegt
ltNamegtCRYPTUseSigningltNamegt
ltDataTypegtxsdbooleanltDataTypegt
ltGuiLabelsgt
ltLabel language=ENgtUse SigningltLabelgt
ltLabel language=DEgtVerwendung von SignierungltLabelgt
ltGuiLabelsgt
ltAttributegt
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 59
Adapter Configuration
Configuration attribute of type boolean is rendered to a check-box
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 60
Adapter Metadata Upload (PCK)
Integration Repositorydoes not exist in case ofSAP PCK installations
The upload mechanismfor Adaper Meta Datafor SAP PCK installationsrequires additonalparameters
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 61
AF CPA Cache
The Adapter configuration is deployed from the configuration time(SAP PCK or Integration Directory) to the J2EE service CPACache(Collaboration Profile Agreement)
The Adapter configuration can be accessed at runtime from withinadapter modules or JCA resource adapters via the CPACache API
The two main use cases are implemented inLookupManager to retrieve adapter configuation andNormalizationManager to retrieve Party information
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 62
Packaging Adapter Components
SAP recommends to use SAP Software Deployment Manager (SDM) for deployment
Software Delivery Archives (SDA) can contain software components of different types (eg applications libraries)
Detailed version information and dependencies to other components simplify program management
Adapter Modules and Development
Summary
Adapter Framework Overview
Adapter Strategy
Agenda
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 64
Summary
Adapter Framework runs on J2EE Stack of SAP Web AS
Adapter Framework is platform for Adapter Engine and SAP PCK
Adapter Framework provides an extensible platform for developing and running adapters
Adapter Engine utilizes central configuration monitoring administration
Dual connectivity strategyAdapter Framework for comprehensive integration of adaptersInteroperability via open standards to interop with EAI providers
SAP NetWeaver Certification for adapters based on Adapter Framework available
Adapter mappings metadata stored in Integration Repository
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 4
Adapter Framework based on SAP J2EE Engine
Adapter Framework provides common functionality for Adapter Engine and SAP Partner Connectivity Kit
Adapter Framework is based on SAP J2EE Engine as part of SAP Web AS
Adapter Framework inherits properties and features such as scalability clustering high availability thread management etc
Adapter Framework provides its own queuing and logging services
Temporary stand-alone operation without connection to an Integration Server is possible while still providing e g guaranteed exactly once messaging to and from connected application system
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 5
JCA enabled Adapter Framework
Adapter Framework supports J2EE Connector Architecture (JCA)
JCA is standard architecture for connecting the J2EE platform toEnterprise Information Systems (EIS) e g ERP DBMS etcA Resource Adapter plugs into an application server providing connectivity between the EIS and a Java applicationJCA enabled Adapter Framework provides defined interfaces to which both our adapters and 3rd party adapters can conformJCA is a widely accepted standard that 3rd party adapter providers are familiar with
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 6
Central configuration administration monitoring
Additionally Adapter Framework provides comprehensive integration for central configuration administration monitoring of deployed adapters
One single point of access only one common UI enhanced transparancyAllows to movecopy configuration from one Adapter Framework to another (transportable configuration)
To transport configuration from test landscape to productive landscapeFor high availabilityfailover
Avoid redundant maintenance ensure consistencyEnd-to-end monitoring of the message flow over all components applications
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 7
ProxiesOutside-in development approachInterfaces designed centrally in Integration RepositoryConnect new SAP applications
Native connectivity to Application system (adapter-less)
AdaptersInside-out development approach Interface semantics externally pre-defined Connect existing (legacy) systemsSpecific wire protocol
Adapters vs Proxies
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 8
Integration Server
PlainJ2SE
Adapter Engine
Partner ConnectivityKitOptional non-central
Adapter EngineCentral Adapter Engine
Process Integration ndash Architecture
Integration Repository Integration Directory System Landscape Directory
Business Process Engine
Integration Engine
Adapter FrameworkMessagingQueuing
Security Handling
Resource
Adapter
Resource
Adapter
Resource
Adapter
Adapter FWMessagingQueuing
Security Handling
Adapter FWMessagingQueuing
Security Handling
PCK Configurationand Monitoring
HTTP
IDoc
Adapter
Adapter
FileDBJMSMarketplace
3rd Party Sys
FileDB
JMSSOAP
SAP ampNon-SAPSystem
FileDBJMSMarketplace
3rd Party Sys
FileDBJMSMarketplace
3rd Party Sys
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 9
Full integration of Adapter Engine
Adapter Engine is based on Adapter Framework
Adapter Engine fully integratedCentral configuration of connections to application systems (through appropriate adapters) in Integration DirectoryReuse of Integration Directoryrsquos existing versioning and transport capabilitiesCentral administration and monitoring over adapters IntegrationServer Integration Engine through Runtime Workbench
The Adapter Engine can be deployed centrally as part of Integration Server or as optional local Adapter Engine on its own SAP J2EE Server reasons for use of local Adapter Engine
Protocol of Sender- Receiver system (eg ftp not allowed)Performance High AvailabilityOrganizational Aspects IT requirements
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 10
PI Adapters developed by SAP
Technical AdaptersFileFTP (File Systems FTP Servers)JDBC (RDBMS systems)JMS (Messaging systems e g MQSeries SonicMQ)SOAP (Web Services)Plain HTTPMail (Mail Servers via SMTP IMAP4 POP3)SAP Business Connector (SAP BC)Marketplace (mySAP Marketplaces)
Application AdaptersRFCIDoc
Industry Standard AdaptersRNIF 20 (RosettaNet)RNIF 11 (RosettaNet)CIDX (RNIF 11)
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 11
Industry Standard Adapters as part of Business Packages
Business Package for RosettaNetOrder to Invoice Scenario
PIP3A4 Request Purchase Order PIP3A7 Notify of Purchase Order UpdatePIP3A8 Request Purchase Order ChangePIP3A9 Request Purchase Order CancellationPIP3B2 Notify of Advance ShipmentPIP3C3 Notify of Invoice PIP3A6 Distribute Order StatusPIP3C6 Notify of Remittance Advice
Business Package for CIDXOrder to Invoice Scenario
Order CreateOrder ResponseOrder ChangeShip NoticeInvoice
Business Packages include scenario descriptions business processes message interfaces message types mappings adapter etc
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 12
Partner Eco System
SAP relies on a system of partners to provide connectivity solutions for other applications and certain industry standards
Connectivity Reseller Agreements withSeeburger AGiWay SoftwareInformatica
3rd-Party solutions are sold and delivered through SAP
Technical support for partner solutions via theSAP Support Portal 24x7
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 13
PI Adapters by Seeburger (1)
Technical EDI AdaptersAS2 (EDIINTHTTP(S))Protocol AS2OFTPProtocol OFTPISDN OFTPTCPIPVAN AccessProtocol P7 X400 VAN FTP
Business EDI AdaptersGeneric EDIProtocol OFTPISDN or P7 X400 VAN FTPEDI Converter ANSI X12 EDIFACTMapping Templates Purchase order Order confirmation
Dispatch advice Invoice
Payment (Financial Service Providers)Protocol OFTPISDN P7 X400 VAN FTPEDI Converter EDIFACT SWIFTMapping Templates Payment orders Debit advice
Credit advice Account Statement
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 14
PI Adapters by Seeburger (2)
Industry Specific EDI AdaptersAerospace and Defense AutomotiveChemicals Consumer ProductsHigh-Tech PaperPharmaceutical Retail
Communication ProtocolsOFTPISDN P7 X400 VAN FTP
EDI Converter (EDI lt-gt XML)AECMASPEC 2000 ANSI X12 CHEM eStandards EDIFACT GALIAODETTE TRADACOM VDA
Mapping Templates within Integration RepositoryDelivery forecast Dispatch advise Invoice Purchase order Order confirmation
Message Library for Integration RepositoryHuge message catalog with EDI XML schema definitions
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 15
PI Adapters by iWay Software
Application AdaptersAriba BaanBroadvision ClarifyJD Edwards One World XE JD Edwards Worldi2 LawsonManugistics Microsoft CRMOracle Applications PeoplesoftQAD MFG Pro SiebelVantive
Industry Standard AdaptersSwift TransoraUCCnet
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 16
PI Adapters by iWay Software
Technical AdaptersAS1 (EDIINTSMTP) AS2 (EDIINTHTTP(S))BEA WLI COM+DCOMCorba Lotus NotesTibco Rendezvous
Mainframetransaction AdaptersCICS TMSIMSTelnet (3270) Telnet (5250) Tuxedo
Optionally further adapters can be added from a list of 160 iWayadapters e g HL7 (already certified) DB2 AS3 ebXML
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 17
SAP Conversion Agent by Informatica
Bi-directional conversion of unstructured and semi structured data from to XMLTransformation on message payloadProtocol support via SAPrsquos technical adapter (PI XI adapter framework)Transformations integrated via PI XI AF module
SAP J2EEPI XI Adapter Framework
Adapter
Adapter
Text2XML
XML2Excel
PDF2XML
ConversionAgent Studio
ConversionAgent Services
Conversion Agent Engine
CA AF Module
Conversion Agent J2EE Lib
Seamlessly integrated into Process Integration
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 18
Supported Data Formats by Informatica (partial list)
UNSTRUCTUREDMicrosoft WordMicrosoft ExcelPowerPointPDFStar OfficeWord PerfectASCII reportsHTMLEBCDICUndocumented binariesFlat filesRPGANSI
PRINT STREAMSAFPPost ScriptDJDE
SEMI-STRUCTURED HL7HIPAAASTMANSIndashX12EDIFACTCOBOLFIXCargo IMPMVRSWIFT
OTHER STANDARDSLegalXMLIFX cXMLebXML HL7 V30 ACORD (AL3 XML)
hellip using SAP technical adapter and Conversion Agent
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 19
Conversion Agent
Bi-directional conversion of unstructured and semi structured formats fromto XMLLinked through PI XI adapter framework module based on SAPrsquos technical adapter ndash no transport protocol manipulates payload informationSAP NetWeaver-wide use (via J2EE library)
3rd Party Adapters
Bi-directional conversion of one dedicated data format (eg SWIFT ANSI-X12 hellip) fromto XMLRuns within PI XI adapter framework - support payload transformation and transport protocol
Per adapter dedicated use within one SAP NetWeaver component
Conversion Agent vs 3rd Party Adapters
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 20
More Info about Connectivity Capabilities
httpservicesapcomxi xi in detail connectivity
Connectivity and Interoperability
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 21
Adapter Download from SAP Service Marketplace
SAP Service Marketplace httpservicesapcomswdc Download Installations and Upgrades Entry by Application Group Adapters
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 22
Certification Programs for Process Integration
httpwwwsdnsapcom Partners and ISVsIntegration and Certification Exchange Infrastructure
PI Based Certification Programs
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 23
Public info about certified PI adapters
httpwwwsapcompartnersdirectoriesSearchSolutionepxThird Party Defined Integration Scenarios NW-XI-AF 30
Certified PI Adapters
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 24
Adapter Configuration
Adapter independent parameters
Adapter specific parameters
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 25
Configurationcache
Adapter Engine
ISRuntime
AdapterSender
AdapterReceiver
Adapter Engine in SAP J2EE
Q
Administration
Security
Monitoring
Adapter-Specific
ComponentServices
TracingLogging
Module ProcessorEIS
Channel
acuteMessaging
Configcache
End-to-End MonitoringMessage flow over all components applications
Runtime Workbenchbull Uis for adminstration
monitoring
Integration Builder Directory
Receiver determinationbull Party-gtService-gtAction
Channel Definitionbull Adapter Enginebull Adapter Typebull Message Protocolbull Transport Protocolbull Securitybull Channel Configuration
(Sender Receiver Agreementbull PartyServiceAction lt-gt Channel
ConfigurationMaster
System Landscape Directorybull Holds component description
including address data
AdapterFramework
Integration Repositorybull Holds Adapter metadataIntegration Repositorybull Holds Adapter metadata
httpltIntegrationServerURLgt
Message
httpltAdapterEngineURLgt
OK Error
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 26
Transport Level Security
Transport Protocol Authentication
IDoc RFC and SNC Client Authentication
Client Authentication
Client Authentication
Client Authentication
Client Authentication
CRAM-MD5
Client Authentication
Client Authentication
Client Authentication
CDIX ndash Adapter HTTPs Client Authentication
RFC RFC and SNC
Plain HTTP HTTPs
FileFTP File Transfer Protocol using SSLTLS
SOAP HTTPsSMTPs (Receiver only)
Mail SMTPs POP3 IMAP4
Marketplace HTTPs
RNIF 20 ndash Adapter HTTPs
RNIF 11 ndash Adapter HTTPs
Supported by
Levels of Security
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 27
Message Level Security
Signature Non-Repudiation
of origin
Non-Repudiation of
receipt
Encryption
CDIX ndash Adapter PKCS7
Technology
XI protocol WS-Security
SOAP-Adapter WS-Security
SMIME
Mail-Adapter SMIME
RNIF 20 ndash Adapter SMIME
RNIF 11 ndash Adapter PKCS7
Supported by
Levels of Security
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 28
Access control list
Restrict access to the runtime environmentfor sender services of type Business Service or Business Systemfor interfaces of these sender services
Restrict access to particular (service) users
Check authorization at runtime
Configure access control in the Integration DirectorySender service Specify authorized users in the configuration of the corresponding (sender) serviceInterface Specify authorized users in the configuration of the relevant sender agreement which contains the interface in the object key
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 29
Dynamic Adapter Configuration
Enable adapters to read write dynamic message headers
Sender Adapter (constructing messages)Attach adapter specific information to message headerExamples File name source file size JMS timestamp mail subjectRead access to these attributes in receiver channel interface determination (routing) mapping
Receiver Adapter (consuming messages)Read attributes to overwrite values of channel configurationExamples Directory Name JMS Priority Mail Sender SOAP target URLSet attributes in mapping orUse attributes from sender in receiver channel
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 30
Sender Adapter Configuration (1)
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 31
Sender Adapter Configuration (2)
Add the filename et al to the message
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 32
Receiver Determination
Determinefilename-dependent receiver
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 33
Receiver Adapter
Store the file withthe name set in the messageattribute
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 34
Monitoring Adapter Engine
After selecting a message bdquoDetailsldquo View
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 35
Monitoring Integration Server
After selecting a message bdquoDisplayldquo
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 36
Remark Future of SAP XI 20 Adapter Engine
SAP XI 20 Adapter Engine is available in SAP NW acute04 and SAP NW 2004s as bdquoPlain J2SE Adapter Engineldquo
Functional scope as in SAP XI 20Adopted to the SAP XI 30 message protocolMinor maintenance issues bug fixes
RecommendationUse where platform requirements or limitations (hardware operating system JVM support) demand it
SAP XI 20 Adapter Engine works with SAP NW acute04 and SAP NW 2004s landscapes too
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 37
Integration Server
PlainJ2SE
Adapter Engine
Partner ConnectivityKitOptional non-central
Adapter EngineCentral Adapter Engine
Process Integration ndash Architecture
Integration Repository Integration Directory System Landscape Directory
Business Process Engine
Integration Engine
Adapter FrameworkMessagingQueuing
Security Handling
Resource
Adapter
Resource
Adapter
Resource
Adapter
Adapter FWMessagingQueuing
Security Handling
Adapter FWMessagingQueuing
Security Handling
PCK Configurationand Monitoring
HTTP
IDoc
Adapter
Adapter
FileDBJMSMarketplace
3rd Party Sys
FileDB
JMSSOAP
SAP ampNon-SAPSystem
FileDBJMSMarketplace
3rd Party Sys
FileDBJMSMarketplace
3rd Party Sys
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 38
SAP Partner Connectivity Kit Overview
SAP 3rdParty Appl PI XI
Smaller Company Subsidiary
SAPPCK
SAPApplication
3rd PartyApplication
Large Business Partner Headquarter
Internet
Enablement of smaller companies subsidiaries to exchange XML documents with their business partnerrsquos headquarterrsquos PI XI
SAPPCK
Providing a platform for development of own JCA Resource Adapters
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 39
SAP PCK ndash Adapters
SAP Partner Connectivity Kit (PCK) is based on Adapter Framework
SAP PCKlsquos objective is to enable XML document exchangebetween PI XI and business partner not using PI XI
SAP PCK also provides an extensible platform for developing and running individual JCA Resource adapters
Communication between PI XI and SAP PCK is via SAP XI messaging protocol
SAP PCK Includes the following adapters FileFTP JDBC JMS SOAP RFC IDoc (once available for SAP PCK) Mail SAP BC
Optionally SAP PCK can host further adapters that are available from SAP or 3rd party adapter providers
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 40
SAP PCK ndash Configuration Mapping
SAP PCK is deployed on stand-alone SAP J2EE Engine (part of SAP Web AS) within business partnerrsquos landscape
Configuration administration monitoring done locally on SAP PCK itself without need for an Integration Directory
Configuration UI provides same bdquolook and feelldquo as configuration UI of Adapter Engine
SAP PCK supports the development of message mappings using an integrated graphical mapping editor
Any source XML structure can be mapped to any target XML structureStandard functions are provided to perform calculations Boolean comparisons text mappings and other transformationsOptionally the standard functions can be enhanced with user-defined functions in Java
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 41
SAP PCK ndash Configuration UI
ConfigurationUI to configure Party Service Communication Channel Sender and Receiver agreementsSample screenshot for configuration of communication channel with adapter type sbquoFile FTPlsquo
Adapter Modules and Development
Summary
Adapter Framework Overview
Adapter Strategy
Agenda
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 43
SAP Exchange Infrastructure - Openness
Integration of SAP and non-SAP applicationsAdapter Framework for comprehensive integration of adaptersAdapters are used for technical connectivityAdapter metadata mappings are stored in Integration Repository
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 44
Dual Strategy
Dual connectivity strategyAdapter Framework for comprehensive integration of adapters to provide technical connectivity including central configurationadministration monitoring of adaptersInteroperability based on open standards (SOAP JMS HTTP(S)) tointeroperate with EAI providers
Value propositionStandardized interfaces allow easy integration of adapters from different partnersMinimum knowledge of end-to-end process integration requiredComprehensive integration avoids redundant maintenance ensures consistency enhances transparancyOpenness to integrate non-SAP applications 3rd party systems etcReduced TCO
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 45
Certification
CertificationSAP NetWeaver Certification of 3rd party adapters based on the adapter framework
Value propositionQuality (stability HA aspects performance etc) of adapters is controlledCertification helps customers to find right solutionQuick and convenient search for a variety of certified products with the online partner and product directory (httpwwwsapcompartnersdirectoriesSearchSolutionepx)Faster implementation time and lower integration costs through the use of tested 3rd party integrationReduced TCO
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 46
Adapter Mappings Metadata in Integration Repository
Adapter mappings and adapter metadata are stored in the Integration Repository
Centralized Integration Repository contains all relevant information for collaborative and integrative processesAll content adheres to open standards Adapters provide technical connectivity
Value propositionUse largest content catalogReduce costs in integration projectsReduce maintenance costsReduced TCO
Adapter Modules and Development
Summary
Adapter Framework Overview
Adapter Strategy
Agenda
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 48
For every adapter it is possible to define generic modules in the module processor possibility to extend the functionality of the specific adapter
Equivalent to the dispatcher classes in the J2SE adapter engine migration and examples
The default module configuration for the certain adapter is displayed in the channel configuration
Modules are EJBlsquos
Sequence matters
Module Processor Concept
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 49
Adapter Module Chain
Custom modulescan be added to default modulechains
Additional configurationparameters canbe specified eachmodule
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 50
Module Processor Documentation
SAP Help Portal (httphelpsapcom)SAP XI Runtime Connectivity Adapters Module ProcessorFeedback Mail to xidocumentationsapcom
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 51
Development Environment
Adapter development deployment and testing is possible on a single machine no full-blown PI XI is required
For testing purposes integration scenarioscan be configured in SAP PCK(eg loopback scenario)
Installation of SAP PCK already contains a sample adapter (including Adapter Meta Data) that should serve as a starting point
SAP Partner ConnectivityKit
Adapter FWMessagingQueuing
Security Handling
Resource
Adapter
PCK Configurationand Monitoring
FileDBJMSMarketplace
3rd Party Sys
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 52
Adapter Development Documentation
SAP Help Portal (httphelpsapcom)SAP XI Runtime Connectivity Partner Connectivity Kit Adapter DevelopmentFeedback Mail to xidocumentationsapcom
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 53
Requirements for Adapters (1)
Num AF Interface Category Description
1 JCA 10 conformance Mandatory Adapter must fulfill JCA 10 requirements (e g deployment) plus optional JCA 15 parts which are used by PI XI
2 AF Message Exchange Mandatory Adapter must be able to receive messages from AF and forward them to connected system and vice versa
3 AF Adapter Specific Modules
Optional SAP XI message and protocol conversion may be done entirely by the adapter or as adapter specific module and being called in the AF module chain context
4 Configuration Services Mandatory Unique configuration approach to manage adapters
5 Administrational Services
Optional Administration and Monitoring
6 Utility Service Mandatory Access to basic J2EE resources e g transactions and multithreading must be under control of J2EE server
7 Logging API Optional Adapters may use their own logging
8 Message Metadata Exchange
Optional Provide structure definition of message payloadIf not supported the definition of message types can be done in the Integration Repository
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 54
Requirements for Adapters (2)
Cluster-enabledConsider side-effects of clustering e g bdquoExactlyOnceInOrderldquo Avoid passing maneuvers
SpecializationBuild connection to exactly one type of business system or industrystandard protocol
DirectnessBuild connection to business system or industry standard protocoldirectly without any intermediate software components
SmoothnessLight-weighted low footprint adapter unnecessary system changes(many new or changed system DLL) should be avoided
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 55
Sample Adapter Source Code
Beside the API documentation a working sample adapter is shipped
The source code is available after installation
Analyzing the code helps understanding the Adapter Framework
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 56
Adapter Metadata
Adapter Metadata (AMD)XML file defines all configuration parameterseach adapter
AMD can be uploaded intoIntegration Iepositoryand SAP PCK
Configurationparameters are renderedinto the graphicalconfiguaration frontend
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 57
Adapter Metadata Fragment I
ltAdapterTypeMetaData version=09gt
ltTypegtNAESBltTypegt
ltInboundgt
ltTransportProtocolgt
ltChannelAttributesgt
ltAttributeGroupgt
ltNamegtCRYPTConfigurationltNamegt
ltGuiLabelsgtltLabel language=ENgtCryptographic ConfigurationltLabelgtltGuiLabelsgt
ltAttributeReferencegtltReferenceNamegtCRYPTUseSigningltReferenceNamegt
ltInboundgt
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 58
Adapter Metadata Fragment II
ltAttributegt
ltNamegtCRYPTUseSigningltNamegt
ltDataTypegtxsdbooleanltDataTypegt
ltGuiLabelsgt
ltLabel language=ENgtUse SigningltLabelgt
ltLabel language=DEgtVerwendung von SignierungltLabelgt
ltGuiLabelsgt
ltAttributegt
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 59
Adapter Configuration
Configuration attribute of type boolean is rendered to a check-box
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 60
Adapter Metadata Upload (PCK)
Integration Repositorydoes not exist in case ofSAP PCK installations
The upload mechanismfor Adaper Meta Datafor SAP PCK installationsrequires additonalparameters
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 61
AF CPA Cache
The Adapter configuration is deployed from the configuration time(SAP PCK or Integration Directory) to the J2EE service CPACache(Collaboration Profile Agreement)
The Adapter configuration can be accessed at runtime from withinadapter modules or JCA resource adapters via the CPACache API
The two main use cases are implemented inLookupManager to retrieve adapter configuation andNormalizationManager to retrieve Party information
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 62
Packaging Adapter Components
SAP recommends to use SAP Software Deployment Manager (SDM) for deployment
Software Delivery Archives (SDA) can contain software components of different types (eg applications libraries)
Detailed version information and dependencies to other components simplify program management
Adapter Modules and Development
Summary
Adapter Framework Overview
Adapter Strategy
Agenda
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 64
Summary
Adapter Framework runs on J2EE Stack of SAP Web AS
Adapter Framework is platform for Adapter Engine and SAP PCK
Adapter Framework provides an extensible platform for developing and running adapters
Adapter Engine utilizes central configuration monitoring administration
Dual connectivity strategyAdapter Framework for comprehensive integration of adaptersInteroperability via open standards to interop with EAI providers
SAP NetWeaver Certification for adapters based on Adapter Framework available
Adapter mappings metadata stored in Integration Repository
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 5
JCA enabled Adapter Framework
Adapter Framework supports J2EE Connector Architecture (JCA)
JCA is standard architecture for connecting the J2EE platform toEnterprise Information Systems (EIS) e g ERP DBMS etcA Resource Adapter plugs into an application server providing connectivity between the EIS and a Java applicationJCA enabled Adapter Framework provides defined interfaces to which both our adapters and 3rd party adapters can conformJCA is a widely accepted standard that 3rd party adapter providers are familiar with
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 6
Central configuration administration monitoring
Additionally Adapter Framework provides comprehensive integration for central configuration administration monitoring of deployed adapters
One single point of access only one common UI enhanced transparancyAllows to movecopy configuration from one Adapter Framework to another (transportable configuration)
To transport configuration from test landscape to productive landscapeFor high availabilityfailover
Avoid redundant maintenance ensure consistencyEnd-to-end monitoring of the message flow over all components applications
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 7
ProxiesOutside-in development approachInterfaces designed centrally in Integration RepositoryConnect new SAP applications
Native connectivity to Application system (adapter-less)
AdaptersInside-out development approach Interface semantics externally pre-defined Connect existing (legacy) systemsSpecific wire protocol
Adapters vs Proxies
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 8
Integration Server
PlainJ2SE
Adapter Engine
Partner ConnectivityKitOptional non-central
Adapter EngineCentral Adapter Engine
Process Integration ndash Architecture
Integration Repository Integration Directory System Landscape Directory
Business Process Engine
Integration Engine
Adapter FrameworkMessagingQueuing
Security Handling
Resource
Adapter
Resource
Adapter
Resource
Adapter
Adapter FWMessagingQueuing
Security Handling
Adapter FWMessagingQueuing
Security Handling
PCK Configurationand Monitoring
HTTP
IDoc
Adapter
Adapter
FileDBJMSMarketplace
3rd Party Sys
FileDB
JMSSOAP
SAP ampNon-SAPSystem
FileDBJMSMarketplace
3rd Party Sys
FileDBJMSMarketplace
3rd Party Sys
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 9
Full integration of Adapter Engine
Adapter Engine is based on Adapter Framework
Adapter Engine fully integratedCentral configuration of connections to application systems (through appropriate adapters) in Integration DirectoryReuse of Integration Directoryrsquos existing versioning and transport capabilitiesCentral administration and monitoring over adapters IntegrationServer Integration Engine through Runtime Workbench
The Adapter Engine can be deployed centrally as part of Integration Server or as optional local Adapter Engine on its own SAP J2EE Server reasons for use of local Adapter Engine
Protocol of Sender- Receiver system (eg ftp not allowed)Performance High AvailabilityOrganizational Aspects IT requirements
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 10
PI Adapters developed by SAP
Technical AdaptersFileFTP (File Systems FTP Servers)JDBC (RDBMS systems)JMS (Messaging systems e g MQSeries SonicMQ)SOAP (Web Services)Plain HTTPMail (Mail Servers via SMTP IMAP4 POP3)SAP Business Connector (SAP BC)Marketplace (mySAP Marketplaces)
Application AdaptersRFCIDoc
Industry Standard AdaptersRNIF 20 (RosettaNet)RNIF 11 (RosettaNet)CIDX (RNIF 11)
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 11
Industry Standard Adapters as part of Business Packages
Business Package for RosettaNetOrder to Invoice Scenario
PIP3A4 Request Purchase Order PIP3A7 Notify of Purchase Order UpdatePIP3A8 Request Purchase Order ChangePIP3A9 Request Purchase Order CancellationPIP3B2 Notify of Advance ShipmentPIP3C3 Notify of Invoice PIP3A6 Distribute Order StatusPIP3C6 Notify of Remittance Advice
Business Package for CIDXOrder to Invoice Scenario
Order CreateOrder ResponseOrder ChangeShip NoticeInvoice
Business Packages include scenario descriptions business processes message interfaces message types mappings adapter etc
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 12
Partner Eco System
SAP relies on a system of partners to provide connectivity solutions for other applications and certain industry standards
Connectivity Reseller Agreements withSeeburger AGiWay SoftwareInformatica
3rd-Party solutions are sold and delivered through SAP
Technical support for partner solutions via theSAP Support Portal 24x7
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 13
PI Adapters by Seeburger (1)
Technical EDI AdaptersAS2 (EDIINTHTTP(S))Protocol AS2OFTPProtocol OFTPISDN OFTPTCPIPVAN AccessProtocol P7 X400 VAN FTP
Business EDI AdaptersGeneric EDIProtocol OFTPISDN or P7 X400 VAN FTPEDI Converter ANSI X12 EDIFACTMapping Templates Purchase order Order confirmation
Dispatch advice Invoice
Payment (Financial Service Providers)Protocol OFTPISDN P7 X400 VAN FTPEDI Converter EDIFACT SWIFTMapping Templates Payment orders Debit advice
Credit advice Account Statement
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 14
PI Adapters by Seeburger (2)
Industry Specific EDI AdaptersAerospace and Defense AutomotiveChemicals Consumer ProductsHigh-Tech PaperPharmaceutical Retail
Communication ProtocolsOFTPISDN P7 X400 VAN FTP
EDI Converter (EDI lt-gt XML)AECMASPEC 2000 ANSI X12 CHEM eStandards EDIFACT GALIAODETTE TRADACOM VDA
Mapping Templates within Integration RepositoryDelivery forecast Dispatch advise Invoice Purchase order Order confirmation
Message Library for Integration RepositoryHuge message catalog with EDI XML schema definitions
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 15
PI Adapters by iWay Software
Application AdaptersAriba BaanBroadvision ClarifyJD Edwards One World XE JD Edwards Worldi2 LawsonManugistics Microsoft CRMOracle Applications PeoplesoftQAD MFG Pro SiebelVantive
Industry Standard AdaptersSwift TransoraUCCnet
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 16
PI Adapters by iWay Software
Technical AdaptersAS1 (EDIINTSMTP) AS2 (EDIINTHTTP(S))BEA WLI COM+DCOMCorba Lotus NotesTibco Rendezvous
Mainframetransaction AdaptersCICS TMSIMSTelnet (3270) Telnet (5250) Tuxedo
Optionally further adapters can be added from a list of 160 iWayadapters e g HL7 (already certified) DB2 AS3 ebXML
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 17
SAP Conversion Agent by Informatica
Bi-directional conversion of unstructured and semi structured data from to XMLTransformation on message payloadProtocol support via SAPrsquos technical adapter (PI XI adapter framework)Transformations integrated via PI XI AF module
SAP J2EEPI XI Adapter Framework
Adapter
Adapter
Text2XML
XML2Excel
PDF2XML
ConversionAgent Studio
ConversionAgent Services
Conversion Agent Engine
CA AF Module
Conversion Agent J2EE Lib
Seamlessly integrated into Process Integration
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 18
Supported Data Formats by Informatica (partial list)
UNSTRUCTUREDMicrosoft WordMicrosoft ExcelPowerPointPDFStar OfficeWord PerfectASCII reportsHTMLEBCDICUndocumented binariesFlat filesRPGANSI
PRINT STREAMSAFPPost ScriptDJDE
SEMI-STRUCTURED HL7HIPAAASTMANSIndashX12EDIFACTCOBOLFIXCargo IMPMVRSWIFT
OTHER STANDARDSLegalXMLIFX cXMLebXML HL7 V30 ACORD (AL3 XML)
hellip using SAP technical adapter and Conversion Agent
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 19
Conversion Agent
Bi-directional conversion of unstructured and semi structured formats fromto XMLLinked through PI XI adapter framework module based on SAPrsquos technical adapter ndash no transport protocol manipulates payload informationSAP NetWeaver-wide use (via J2EE library)
3rd Party Adapters
Bi-directional conversion of one dedicated data format (eg SWIFT ANSI-X12 hellip) fromto XMLRuns within PI XI adapter framework - support payload transformation and transport protocol
Per adapter dedicated use within one SAP NetWeaver component
Conversion Agent vs 3rd Party Adapters
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 20
More Info about Connectivity Capabilities
httpservicesapcomxi xi in detail connectivity
Connectivity and Interoperability
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 21
Adapter Download from SAP Service Marketplace
SAP Service Marketplace httpservicesapcomswdc Download Installations and Upgrades Entry by Application Group Adapters
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 22
Certification Programs for Process Integration
httpwwwsdnsapcom Partners and ISVsIntegration and Certification Exchange Infrastructure
PI Based Certification Programs
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 23
Public info about certified PI adapters
httpwwwsapcompartnersdirectoriesSearchSolutionepxThird Party Defined Integration Scenarios NW-XI-AF 30
Certified PI Adapters
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 24
Adapter Configuration
Adapter independent parameters
Adapter specific parameters
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 25
Configurationcache
Adapter Engine
ISRuntime
AdapterSender
AdapterReceiver
Adapter Engine in SAP J2EE
Q
Administration
Security
Monitoring
Adapter-Specific
ComponentServices
TracingLogging
Module ProcessorEIS
Channel
acuteMessaging
Configcache
End-to-End MonitoringMessage flow over all components applications
Runtime Workbenchbull Uis for adminstration
monitoring
Integration Builder Directory
Receiver determinationbull Party-gtService-gtAction
Channel Definitionbull Adapter Enginebull Adapter Typebull Message Protocolbull Transport Protocolbull Securitybull Channel Configuration
(Sender Receiver Agreementbull PartyServiceAction lt-gt Channel
ConfigurationMaster
System Landscape Directorybull Holds component description
including address data
AdapterFramework
Integration Repositorybull Holds Adapter metadataIntegration Repositorybull Holds Adapter metadata
httpltIntegrationServerURLgt
Message
httpltAdapterEngineURLgt
OK Error
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 26
Transport Level Security
Transport Protocol Authentication
IDoc RFC and SNC Client Authentication
Client Authentication
Client Authentication
Client Authentication
Client Authentication
CRAM-MD5
Client Authentication
Client Authentication
Client Authentication
CDIX ndash Adapter HTTPs Client Authentication
RFC RFC and SNC
Plain HTTP HTTPs
FileFTP File Transfer Protocol using SSLTLS
SOAP HTTPsSMTPs (Receiver only)
Mail SMTPs POP3 IMAP4
Marketplace HTTPs
RNIF 20 ndash Adapter HTTPs
RNIF 11 ndash Adapter HTTPs
Supported by
Levels of Security
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 27
Message Level Security
Signature Non-Repudiation
of origin
Non-Repudiation of
receipt
Encryption
CDIX ndash Adapter PKCS7
Technology
XI protocol WS-Security
SOAP-Adapter WS-Security
SMIME
Mail-Adapter SMIME
RNIF 20 ndash Adapter SMIME
RNIF 11 ndash Adapter PKCS7
Supported by
Levels of Security
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 28
Access control list
Restrict access to the runtime environmentfor sender services of type Business Service or Business Systemfor interfaces of these sender services
Restrict access to particular (service) users
Check authorization at runtime
Configure access control in the Integration DirectorySender service Specify authorized users in the configuration of the corresponding (sender) serviceInterface Specify authorized users in the configuration of the relevant sender agreement which contains the interface in the object key
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 29
Dynamic Adapter Configuration
Enable adapters to read write dynamic message headers
Sender Adapter (constructing messages)Attach adapter specific information to message headerExamples File name source file size JMS timestamp mail subjectRead access to these attributes in receiver channel interface determination (routing) mapping
Receiver Adapter (consuming messages)Read attributes to overwrite values of channel configurationExamples Directory Name JMS Priority Mail Sender SOAP target URLSet attributes in mapping orUse attributes from sender in receiver channel
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 30
Sender Adapter Configuration (1)
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 31
Sender Adapter Configuration (2)
Add the filename et al to the message
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 32
Receiver Determination
Determinefilename-dependent receiver
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 33
Receiver Adapter
Store the file withthe name set in the messageattribute
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 34
Monitoring Adapter Engine
After selecting a message bdquoDetailsldquo View
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 35
Monitoring Integration Server
After selecting a message bdquoDisplayldquo
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 36
Remark Future of SAP XI 20 Adapter Engine
SAP XI 20 Adapter Engine is available in SAP NW acute04 and SAP NW 2004s as bdquoPlain J2SE Adapter Engineldquo
Functional scope as in SAP XI 20Adopted to the SAP XI 30 message protocolMinor maintenance issues bug fixes
RecommendationUse where platform requirements or limitations (hardware operating system JVM support) demand it
SAP XI 20 Adapter Engine works with SAP NW acute04 and SAP NW 2004s landscapes too
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 37
Integration Server
PlainJ2SE
Adapter Engine
Partner ConnectivityKitOptional non-central
Adapter EngineCentral Adapter Engine
Process Integration ndash Architecture
Integration Repository Integration Directory System Landscape Directory
Business Process Engine
Integration Engine
Adapter FrameworkMessagingQueuing
Security Handling
Resource
Adapter
Resource
Adapter
Resource
Adapter
Adapter FWMessagingQueuing
Security Handling
Adapter FWMessagingQueuing
Security Handling
PCK Configurationand Monitoring
HTTP
IDoc
Adapter
Adapter
FileDBJMSMarketplace
3rd Party Sys
FileDB
JMSSOAP
SAP ampNon-SAPSystem
FileDBJMSMarketplace
3rd Party Sys
FileDBJMSMarketplace
3rd Party Sys
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 38
SAP Partner Connectivity Kit Overview
SAP 3rdParty Appl PI XI
Smaller Company Subsidiary
SAPPCK
SAPApplication
3rd PartyApplication
Large Business Partner Headquarter
Internet
Enablement of smaller companies subsidiaries to exchange XML documents with their business partnerrsquos headquarterrsquos PI XI
SAPPCK
Providing a platform for development of own JCA Resource Adapters
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 39
SAP PCK ndash Adapters
SAP Partner Connectivity Kit (PCK) is based on Adapter Framework
SAP PCKlsquos objective is to enable XML document exchangebetween PI XI and business partner not using PI XI
SAP PCK also provides an extensible platform for developing and running individual JCA Resource adapters
Communication between PI XI and SAP PCK is via SAP XI messaging protocol
SAP PCK Includes the following adapters FileFTP JDBC JMS SOAP RFC IDoc (once available for SAP PCK) Mail SAP BC
Optionally SAP PCK can host further adapters that are available from SAP or 3rd party adapter providers
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 40
SAP PCK ndash Configuration Mapping
SAP PCK is deployed on stand-alone SAP J2EE Engine (part of SAP Web AS) within business partnerrsquos landscape
Configuration administration monitoring done locally on SAP PCK itself without need for an Integration Directory
Configuration UI provides same bdquolook and feelldquo as configuration UI of Adapter Engine
SAP PCK supports the development of message mappings using an integrated graphical mapping editor
Any source XML structure can be mapped to any target XML structureStandard functions are provided to perform calculations Boolean comparisons text mappings and other transformationsOptionally the standard functions can be enhanced with user-defined functions in Java
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 41
SAP PCK ndash Configuration UI
ConfigurationUI to configure Party Service Communication Channel Sender and Receiver agreementsSample screenshot for configuration of communication channel with adapter type sbquoFile FTPlsquo
Adapter Modules and Development
Summary
Adapter Framework Overview
Adapter Strategy
Agenda
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 43
SAP Exchange Infrastructure - Openness
Integration of SAP and non-SAP applicationsAdapter Framework for comprehensive integration of adaptersAdapters are used for technical connectivityAdapter metadata mappings are stored in Integration Repository
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 44
Dual Strategy
Dual connectivity strategyAdapter Framework for comprehensive integration of adapters to provide technical connectivity including central configurationadministration monitoring of adaptersInteroperability based on open standards (SOAP JMS HTTP(S)) tointeroperate with EAI providers
Value propositionStandardized interfaces allow easy integration of adapters from different partnersMinimum knowledge of end-to-end process integration requiredComprehensive integration avoids redundant maintenance ensures consistency enhances transparancyOpenness to integrate non-SAP applications 3rd party systems etcReduced TCO
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 45
Certification
CertificationSAP NetWeaver Certification of 3rd party adapters based on the adapter framework
Value propositionQuality (stability HA aspects performance etc) of adapters is controlledCertification helps customers to find right solutionQuick and convenient search for a variety of certified products with the online partner and product directory (httpwwwsapcompartnersdirectoriesSearchSolutionepx)Faster implementation time and lower integration costs through the use of tested 3rd party integrationReduced TCO
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 46
Adapter Mappings Metadata in Integration Repository
Adapter mappings and adapter metadata are stored in the Integration Repository
Centralized Integration Repository contains all relevant information for collaborative and integrative processesAll content adheres to open standards Adapters provide technical connectivity
Value propositionUse largest content catalogReduce costs in integration projectsReduce maintenance costsReduced TCO
Adapter Modules and Development
Summary
Adapter Framework Overview
Adapter Strategy
Agenda
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 48
For every adapter it is possible to define generic modules in the module processor possibility to extend the functionality of the specific adapter
Equivalent to the dispatcher classes in the J2SE adapter engine migration and examples
The default module configuration for the certain adapter is displayed in the channel configuration
Modules are EJBlsquos
Sequence matters
Module Processor Concept
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 49
Adapter Module Chain
Custom modulescan be added to default modulechains
Additional configurationparameters canbe specified eachmodule
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 50
Module Processor Documentation
SAP Help Portal (httphelpsapcom)SAP XI Runtime Connectivity Adapters Module ProcessorFeedback Mail to xidocumentationsapcom
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 51
Development Environment
Adapter development deployment and testing is possible on a single machine no full-blown PI XI is required
For testing purposes integration scenarioscan be configured in SAP PCK(eg loopback scenario)
Installation of SAP PCK already contains a sample adapter (including Adapter Meta Data) that should serve as a starting point
SAP Partner ConnectivityKit
Adapter FWMessagingQueuing
Security Handling
Resource
Adapter
PCK Configurationand Monitoring
FileDBJMSMarketplace
3rd Party Sys
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 52
Adapter Development Documentation
SAP Help Portal (httphelpsapcom)SAP XI Runtime Connectivity Partner Connectivity Kit Adapter DevelopmentFeedback Mail to xidocumentationsapcom
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 53
Requirements for Adapters (1)
Num AF Interface Category Description
1 JCA 10 conformance Mandatory Adapter must fulfill JCA 10 requirements (e g deployment) plus optional JCA 15 parts which are used by PI XI
2 AF Message Exchange Mandatory Adapter must be able to receive messages from AF and forward them to connected system and vice versa
3 AF Adapter Specific Modules
Optional SAP XI message and protocol conversion may be done entirely by the adapter or as adapter specific module and being called in the AF module chain context
4 Configuration Services Mandatory Unique configuration approach to manage adapters
5 Administrational Services
Optional Administration and Monitoring
6 Utility Service Mandatory Access to basic J2EE resources e g transactions and multithreading must be under control of J2EE server
7 Logging API Optional Adapters may use their own logging
8 Message Metadata Exchange
Optional Provide structure definition of message payloadIf not supported the definition of message types can be done in the Integration Repository
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 54
Requirements for Adapters (2)
Cluster-enabledConsider side-effects of clustering e g bdquoExactlyOnceInOrderldquo Avoid passing maneuvers
SpecializationBuild connection to exactly one type of business system or industrystandard protocol
DirectnessBuild connection to business system or industry standard protocoldirectly without any intermediate software components
SmoothnessLight-weighted low footprint adapter unnecessary system changes(many new or changed system DLL) should be avoided
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 55
Sample Adapter Source Code
Beside the API documentation a working sample adapter is shipped
The source code is available after installation
Analyzing the code helps understanding the Adapter Framework
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 56
Adapter Metadata
Adapter Metadata (AMD)XML file defines all configuration parameterseach adapter
AMD can be uploaded intoIntegration Iepositoryand SAP PCK
Configurationparameters are renderedinto the graphicalconfiguaration frontend
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 57
Adapter Metadata Fragment I
ltAdapterTypeMetaData version=09gt
ltTypegtNAESBltTypegt
ltInboundgt
ltTransportProtocolgt
ltChannelAttributesgt
ltAttributeGroupgt
ltNamegtCRYPTConfigurationltNamegt
ltGuiLabelsgtltLabel language=ENgtCryptographic ConfigurationltLabelgtltGuiLabelsgt
ltAttributeReferencegtltReferenceNamegtCRYPTUseSigningltReferenceNamegt
ltInboundgt
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 58
Adapter Metadata Fragment II
ltAttributegt
ltNamegtCRYPTUseSigningltNamegt
ltDataTypegtxsdbooleanltDataTypegt
ltGuiLabelsgt
ltLabel language=ENgtUse SigningltLabelgt
ltLabel language=DEgtVerwendung von SignierungltLabelgt
ltGuiLabelsgt
ltAttributegt
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 59
Adapter Configuration
Configuration attribute of type boolean is rendered to a check-box
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 60
Adapter Metadata Upload (PCK)
Integration Repositorydoes not exist in case ofSAP PCK installations
The upload mechanismfor Adaper Meta Datafor SAP PCK installationsrequires additonalparameters
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 61
AF CPA Cache
The Adapter configuration is deployed from the configuration time(SAP PCK or Integration Directory) to the J2EE service CPACache(Collaboration Profile Agreement)
The Adapter configuration can be accessed at runtime from withinadapter modules or JCA resource adapters via the CPACache API
The two main use cases are implemented inLookupManager to retrieve adapter configuation andNormalizationManager to retrieve Party information
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 62
Packaging Adapter Components
SAP recommends to use SAP Software Deployment Manager (SDM) for deployment
Software Delivery Archives (SDA) can contain software components of different types (eg applications libraries)
Detailed version information and dependencies to other components simplify program management
Adapter Modules and Development
Summary
Adapter Framework Overview
Adapter Strategy
Agenda
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 64
Summary
Adapter Framework runs on J2EE Stack of SAP Web AS
Adapter Framework is platform for Adapter Engine and SAP PCK
Adapter Framework provides an extensible platform for developing and running adapters
Adapter Engine utilizes central configuration monitoring administration
Dual connectivity strategyAdapter Framework for comprehensive integration of adaptersInteroperability via open standards to interop with EAI providers
SAP NetWeaver Certification for adapters based on Adapter Framework available
Adapter mappings metadata stored in Integration Repository
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 6
Central configuration administration monitoring
Additionally Adapter Framework provides comprehensive integration for central configuration administration monitoring of deployed adapters
One single point of access only one common UI enhanced transparancyAllows to movecopy configuration from one Adapter Framework to another (transportable configuration)
To transport configuration from test landscape to productive landscapeFor high availabilityfailover
Avoid redundant maintenance ensure consistencyEnd-to-end monitoring of the message flow over all components applications
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 7
ProxiesOutside-in development approachInterfaces designed centrally in Integration RepositoryConnect new SAP applications
Native connectivity to Application system (adapter-less)
AdaptersInside-out development approach Interface semantics externally pre-defined Connect existing (legacy) systemsSpecific wire protocol
Adapters vs Proxies
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 8
Integration Server
PlainJ2SE
Adapter Engine
Partner ConnectivityKitOptional non-central
Adapter EngineCentral Adapter Engine
Process Integration ndash Architecture
Integration Repository Integration Directory System Landscape Directory
Business Process Engine
Integration Engine
Adapter FrameworkMessagingQueuing
Security Handling
Resource
Adapter
Resource
Adapter
Resource
Adapter
Adapter FWMessagingQueuing
Security Handling
Adapter FWMessagingQueuing
Security Handling
PCK Configurationand Monitoring
HTTP
IDoc
Adapter
Adapter
FileDBJMSMarketplace
3rd Party Sys
FileDB
JMSSOAP
SAP ampNon-SAPSystem
FileDBJMSMarketplace
3rd Party Sys
FileDBJMSMarketplace
3rd Party Sys
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 9
Full integration of Adapter Engine
Adapter Engine is based on Adapter Framework
Adapter Engine fully integratedCentral configuration of connections to application systems (through appropriate adapters) in Integration DirectoryReuse of Integration Directoryrsquos existing versioning and transport capabilitiesCentral administration and monitoring over adapters IntegrationServer Integration Engine through Runtime Workbench
The Adapter Engine can be deployed centrally as part of Integration Server or as optional local Adapter Engine on its own SAP J2EE Server reasons for use of local Adapter Engine
Protocol of Sender- Receiver system (eg ftp not allowed)Performance High AvailabilityOrganizational Aspects IT requirements
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 10
PI Adapters developed by SAP
Technical AdaptersFileFTP (File Systems FTP Servers)JDBC (RDBMS systems)JMS (Messaging systems e g MQSeries SonicMQ)SOAP (Web Services)Plain HTTPMail (Mail Servers via SMTP IMAP4 POP3)SAP Business Connector (SAP BC)Marketplace (mySAP Marketplaces)
Application AdaptersRFCIDoc
Industry Standard AdaptersRNIF 20 (RosettaNet)RNIF 11 (RosettaNet)CIDX (RNIF 11)
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 11
Industry Standard Adapters as part of Business Packages
Business Package for RosettaNetOrder to Invoice Scenario
PIP3A4 Request Purchase Order PIP3A7 Notify of Purchase Order UpdatePIP3A8 Request Purchase Order ChangePIP3A9 Request Purchase Order CancellationPIP3B2 Notify of Advance ShipmentPIP3C3 Notify of Invoice PIP3A6 Distribute Order StatusPIP3C6 Notify of Remittance Advice
Business Package for CIDXOrder to Invoice Scenario
Order CreateOrder ResponseOrder ChangeShip NoticeInvoice
Business Packages include scenario descriptions business processes message interfaces message types mappings adapter etc
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 12
Partner Eco System
SAP relies on a system of partners to provide connectivity solutions for other applications and certain industry standards
Connectivity Reseller Agreements withSeeburger AGiWay SoftwareInformatica
3rd-Party solutions are sold and delivered through SAP
Technical support for partner solutions via theSAP Support Portal 24x7
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 13
PI Adapters by Seeburger (1)
Technical EDI AdaptersAS2 (EDIINTHTTP(S))Protocol AS2OFTPProtocol OFTPISDN OFTPTCPIPVAN AccessProtocol P7 X400 VAN FTP
Business EDI AdaptersGeneric EDIProtocol OFTPISDN or P7 X400 VAN FTPEDI Converter ANSI X12 EDIFACTMapping Templates Purchase order Order confirmation
Dispatch advice Invoice
Payment (Financial Service Providers)Protocol OFTPISDN P7 X400 VAN FTPEDI Converter EDIFACT SWIFTMapping Templates Payment orders Debit advice
Credit advice Account Statement
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 14
PI Adapters by Seeburger (2)
Industry Specific EDI AdaptersAerospace and Defense AutomotiveChemicals Consumer ProductsHigh-Tech PaperPharmaceutical Retail
Communication ProtocolsOFTPISDN P7 X400 VAN FTP
EDI Converter (EDI lt-gt XML)AECMASPEC 2000 ANSI X12 CHEM eStandards EDIFACT GALIAODETTE TRADACOM VDA
Mapping Templates within Integration RepositoryDelivery forecast Dispatch advise Invoice Purchase order Order confirmation
Message Library for Integration RepositoryHuge message catalog with EDI XML schema definitions
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 15
PI Adapters by iWay Software
Application AdaptersAriba BaanBroadvision ClarifyJD Edwards One World XE JD Edwards Worldi2 LawsonManugistics Microsoft CRMOracle Applications PeoplesoftQAD MFG Pro SiebelVantive
Industry Standard AdaptersSwift TransoraUCCnet
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 16
PI Adapters by iWay Software
Technical AdaptersAS1 (EDIINTSMTP) AS2 (EDIINTHTTP(S))BEA WLI COM+DCOMCorba Lotus NotesTibco Rendezvous
Mainframetransaction AdaptersCICS TMSIMSTelnet (3270) Telnet (5250) Tuxedo
Optionally further adapters can be added from a list of 160 iWayadapters e g HL7 (already certified) DB2 AS3 ebXML
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 17
SAP Conversion Agent by Informatica
Bi-directional conversion of unstructured and semi structured data from to XMLTransformation on message payloadProtocol support via SAPrsquos technical adapter (PI XI adapter framework)Transformations integrated via PI XI AF module
SAP J2EEPI XI Adapter Framework
Adapter
Adapter
Text2XML
XML2Excel
PDF2XML
ConversionAgent Studio
ConversionAgent Services
Conversion Agent Engine
CA AF Module
Conversion Agent J2EE Lib
Seamlessly integrated into Process Integration
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 18
Supported Data Formats by Informatica (partial list)
UNSTRUCTUREDMicrosoft WordMicrosoft ExcelPowerPointPDFStar OfficeWord PerfectASCII reportsHTMLEBCDICUndocumented binariesFlat filesRPGANSI
PRINT STREAMSAFPPost ScriptDJDE
SEMI-STRUCTURED HL7HIPAAASTMANSIndashX12EDIFACTCOBOLFIXCargo IMPMVRSWIFT
OTHER STANDARDSLegalXMLIFX cXMLebXML HL7 V30 ACORD (AL3 XML)
hellip using SAP technical adapter and Conversion Agent
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 19
Conversion Agent
Bi-directional conversion of unstructured and semi structured formats fromto XMLLinked through PI XI adapter framework module based on SAPrsquos technical adapter ndash no transport protocol manipulates payload informationSAP NetWeaver-wide use (via J2EE library)
3rd Party Adapters
Bi-directional conversion of one dedicated data format (eg SWIFT ANSI-X12 hellip) fromto XMLRuns within PI XI adapter framework - support payload transformation and transport protocol
Per adapter dedicated use within one SAP NetWeaver component
Conversion Agent vs 3rd Party Adapters
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 20
More Info about Connectivity Capabilities
httpservicesapcomxi xi in detail connectivity
Connectivity and Interoperability
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 21
Adapter Download from SAP Service Marketplace
SAP Service Marketplace httpservicesapcomswdc Download Installations and Upgrades Entry by Application Group Adapters
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 22
Certification Programs for Process Integration
httpwwwsdnsapcom Partners and ISVsIntegration and Certification Exchange Infrastructure
PI Based Certification Programs
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 23
Public info about certified PI adapters
httpwwwsapcompartnersdirectoriesSearchSolutionepxThird Party Defined Integration Scenarios NW-XI-AF 30
Certified PI Adapters
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 24
Adapter Configuration
Adapter independent parameters
Adapter specific parameters
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 25
Configurationcache
Adapter Engine
ISRuntime
AdapterSender
AdapterReceiver
Adapter Engine in SAP J2EE
Q
Administration
Security
Monitoring
Adapter-Specific
ComponentServices
TracingLogging
Module ProcessorEIS
Channel
acuteMessaging
Configcache
End-to-End MonitoringMessage flow over all components applications
Runtime Workbenchbull Uis for adminstration
monitoring
Integration Builder Directory
Receiver determinationbull Party-gtService-gtAction
Channel Definitionbull Adapter Enginebull Adapter Typebull Message Protocolbull Transport Protocolbull Securitybull Channel Configuration
(Sender Receiver Agreementbull PartyServiceAction lt-gt Channel
ConfigurationMaster
System Landscape Directorybull Holds component description
including address data
AdapterFramework
Integration Repositorybull Holds Adapter metadataIntegration Repositorybull Holds Adapter metadata
httpltIntegrationServerURLgt
Message
httpltAdapterEngineURLgt
OK Error
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 26
Transport Level Security
Transport Protocol Authentication
IDoc RFC and SNC Client Authentication
Client Authentication
Client Authentication
Client Authentication
Client Authentication
CRAM-MD5
Client Authentication
Client Authentication
Client Authentication
CDIX ndash Adapter HTTPs Client Authentication
RFC RFC and SNC
Plain HTTP HTTPs
FileFTP File Transfer Protocol using SSLTLS
SOAP HTTPsSMTPs (Receiver only)
Mail SMTPs POP3 IMAP4
Marketplace HTTPs
RNIF 20 ndash Adapter HTTPs
RNIF 11 ndash Adapter HTTPs
Supported by
Levels of Security
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 27
Message Level Security
Signature Non-Repudiation
of origin
Non-Repudiation of
receipt
Encryption
CDIX ndash Adapter PKCS7
Technology
XI protocol WS-Security
SOAP-Adapter WS-Security
SMIME
Mail-Adapter SMIME
RNIF 20 ndash Adapter SMIME
RNIF 11 ndash Adapter PKCS7
Supported by
Levels of Security
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 28
Access control list
Restrict access to the runtime environmentfor sender services of type Business Service or Business Systemfor interfaces of these sender services
Restrict access to particular (service) users
Check authorization at runtime
Configure access control in the Integration DirectorySender service Specify authorized users in the configuration of the corresponding (sender) serviceInterface Specify authorized users in the configuration of the relevant sender agreement which contains the interface in the object key
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 29
Dynamic Adapter Configuration
Enable adapters to read write dynamic message headers
Sender Adapter (constructing messages)Attach adapter specific information to message headerExamples File name source file size JMS timestamp mail subjectRead access to these attributes in receiver channel interface determination (routing) mapping
Receiver Adapter (consuming messages)Read attributes to overwrite values of channel configurationExamples Directory Name JMS Priority Mail Sender SOAP target URLSet attributes in mapping orUse attributes from sender in receiver channel
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 30
Sender Adapter Configuration (1)
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 31
Sender Adapter Configuration (2)
Add the filename et al to the message
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 32
Receiver Determination
Determinefilename-dependent receiver
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 33
Receiver Adapter
Store the file withthe name set in the messageattribute
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 34
Monitoring Adapter Engine
After selecting a message bdquoDetailsldquo View
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 35
Monitoring Integration Server
After selecting a message bdquoDisplayldquo
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 36
Remark Future of SAP XI 20 Adapter Engine
SAP XI 20 Adapter Engine is available in SAP NW acute04 and SAP NW 2004s as bdquoPlain J2SE Adapter Engineldquo
Functional scope as in SAP XI 20Adopted to the SAP XI 30 message protocolMinor maintenance issues bug fixes
RecommendationUse where platform requirements or limitations (hardware operating system JVM support) demand it
SAP XI 20 Adapter Engine works with SAP NW acute04 and SAP NW 2004s landscapes too
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 37
Integration Server
PlainJ2SE
Adapter Engine
Partner ConnectivityKitOptional non-central
Adapter EngineCentral Adapter Engine
Process Integration ndash Architecture
Integration Repository Integration Directory System Landscape Directory
Business Process Engine
Integration Engine
Adapter FrameworkMessagingQueuing
Security Handling
Resource
Adapter
Resource
Adapter
Resource
Adapter
Adapter FWMessagingQueuing
Security Handling
Adapter FWMessagingQueuing
Security Handling
PCK Configurationand Monitoring
HTTP
IDoc
Adapter
Adapter
FileDBJMSMarketplace
3rd Party Sys
FileDB
JMSSOAP
SAP ampNon-SAPSystem
FileDBJMSMarketplace
3rd Party Sys
FileDBJMSMarketplace
3rd Party Sys
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 38
SAP Partner Connectivity Kit Overview
SAP 3rdParty Appl PI XI
Smaller Company Subsidiary
SAPPCK
SAPApplication
3rd PartyApplication
Large Business Partner Headquarter
Internet
Enablement of smaller companies subsidiaries to exchange XML documents with their business partnerrsquos headquarterrsquos PI XI
SAPPCK
Providing a platform for development of own JCA Resource Adapters
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 39
SAP PCK ndash Adapters
SAP Partner Connectivity Kit (PCK) is based on Adapter Framework
SAP PCKlsquos objective is to enable XML document exchangebetween PI XI and business partner not using PI XI
SAP PCK also provides an extensible platform for developing and running individual JCA Resource adapters
Communication between PI XI and SAP PCK is via SAP XI messaging protocol
SAP PCK Includes the following adapters FileFTP JDBC JMS SOAP RFC IDoc (once available for SAP PCK) Mail SAP BC
Optionally SAP PCK can host further adapters that are available from SAP or 3rd party adapter providers
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 40
SAP PCK ndash Configuration Mapping
SAP PCK is deployed on stand-alone SAP J2EE Engine (part of SAP Web AS) within business partnerrsquos landscape
Configuration administration monitoring done locally on SAP PCK itself without need for an Integration Directory
Configuration UI provides same bdquolook and feelldquo as configuration UI of Adapter Engine
SAP PCK supports the development of message mappings using an integrated graphical mapping editor
Any source XML structure can be mapped to any target XML structureStandard functions are provided to perform calculations Boolean comparisons text mappings and other transformationsOptionally the standard functions can be enhanced with user-defined functions in Java
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 41
SAP PCK ndash Configuration UI
ConfigurationUI to configure Party Service Communication Channel Sender and Receiver agreementsSample screenshot for configuration of communication channel with adapter type sbquoFile FTPlsquo
Adapter Modules and Development
Summary
Adapter Framework Overview
Adapter Strategy
Agenda
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 43
SAP Exchange Infrastructure - Openness
Integration of SAP and non-SAP applicationsAdapter Framework for comprehensive integration of adaptersAdapters are used for technical connectivityAdapter metadata mappings are stored in Integration Repository
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 44
Dual Strategy
Dual connectivity strategyAdapter Framework for comprehensive integration of adapters to provide technical connectivity including central configurationadministration monitoring of adaptersInteroperability based on open standards (SOAP JMS HTTP(S)) tointeroperate with EAI providers
Value propositionStandardized interfaces allow easy integration of adapters from different partnersMinimum knowledge of end-to-end process integration requiredComprehensive integration avoids redundant maintenance ensures consistency enhances transparancyOpenness to integrate non-SAP applications 3rd party systems etcReduced TCO
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 45
Certification
CertificationSAP NetWeaver Certification of 3rd party adapters based on the adapter framework
Value propositionQuality (stability HA aspects performance etc) of adapters is controlledCertification helps customers to find right solutionQuick and convenient search for a variety of certified products with the online partner and product directory (httpwwwsapcompartnersdirectoriesSearchSolutionepx)Faster implementation time and lower integration costs through the use of tested 3rd party integrationReduced TCO
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 46
Adapter Mappings Metadata in Integration Repository
Adapter mappings and adapter metadata are stored in the Integration Repository
Centralized Integration Repository contains all relevant information for collaborative and integrative processesAll content adheres to open standards Adapters provide technical connectivity
Value propositionUse largest content catalogReduce costs in integration projectsReduce maintenance costsReduced TCO
Adapter Modules and Development
Summary
Adapter Framework Overview
Adapter Strategy
Agenda
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 48
For every adapter it is possible to define generic modules in the module processor possibility to extend the functionality of the specific adapter
Equivalent to the dispatcher classes in the J2SE adapter engine migration and examples
The default module configuration for the certain adapter is displayed in the channel configuration
Modules are EJBlsquos
Sequence matters
Module Processor Concept
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 49
Adapter Module Chain
Custom modulescan be added to default modulechains
Additional configurationparameters canbe specified eachmodule
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 50
Module Processor Documentation
SAP Help Portal (httphelpsapcom)SAP XI Runtime Connectivity Adapters Module ProcessorFeedback Mail to xidocumentationsapcom
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 51
Development Environment
Adapter development deployment and testing is possible on a single machine no full-blown PI XI is required
For testing purposes integration scenarioscan be configured in SAP PCK(eg loopback scenario)
Installation of SAP PCK already contains a sample adapter (including Adapter Meta Data) that should serve as a starting point
SAP Partner ConnectivityKit
Adapter FWMessagingQueuing
Security Handling
Resource
Adapter
PCK Configurationand Monitoring
FileDBJMSMarketplace
3rd Party Sys
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 52
Adapter Development Documentation
SAP Help Portal (httphelpsapcom)SAP XI Runtime Connectivity Partner Connectivity Kit Adapter DevelopmentFeedback Mail to xidocumentationsapcom
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 53
Requirements for Adapters (1)
Num AF Interface Category Description
1 JCA 10 conformance Mandatory Adapter must fulfill JCA 10 requirements (e g deployment) plus optional JCA 15 parts which are used by PI XI
2 AF Message Exchange Mandatory Adapter must be able to receive messages from AF and forward them to connected system and vice versa
3 AF Adapter Specific Modules
Optional SAP XI message and protocol conversion may be done entirely by the adapter or as adapter specific module and being called in the AF module chain context
4 Configuration Services Mandatory Unique configuration approach to manage adapters
5 Administrational Services
Optional Administration and Monitoring
6 Utility Service Mandatory Access to basic J2EE resources e g transactions and multithreading must be under control of J2EE server
7 Logging API Optional Adapters may use their own logging
8 Message Metadata Exchange
Optional Provide structure definition of message payloadIf not supported the definition of message types can be done in the Integration Repository
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 54
Requirements for Adapters (2)
Cluster-enabledConsider side-effects of clustering e g bdquoExactlyOnceInOrderldquo Avoid passing maneuvers
SpecializationBuild connection to exactly one type of business system or industrystandard protocol
DirectnessBuild connection to business system or industry standard protocoldirectly without any intermediate software components
SmoothnessLight-weighted low footprint adapter unnecessary system changes(many new or changed system DLL) should be avoided
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 55
Sample Adapter Source Code
Beside the API documentation a working sample adapter is shipped
The source code is available after installation
Analyzing the code helps understanding the Adapter Framework
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 56
Adapter Metadata
Adapter Metadata (AMD)XML file defines all configuration parameterseach adapter
AMD can be uploaded intoIntegration Iepositoryand SAP PCK
Configurationparameters are renderedinto the graphicalconfiguaration frontend
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 57
Adapter Metadata Fragment I
ltAdapterTypeMetaData version=09gt
ltTypegtNAESBltTypegt
ltInboundgt
ltTransportProtocolgt
ltChannelAttributesgt
ltAttributeGroupgt
ltNamegtCRYPTConfigurationltNamegt
ltGuiLabelsgtltLabel language=ENgtCryptographic ConfigurationltLabelgtltGuiLabelsgt
ltAttributeReferencegtltReferenceNamegtCRYPTUseSigningltReferenceNamegt
ltInboundgt
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 58
Adapter Metadata Fragment II
ltAttributegt
ltNamegtCRYPTUseSigningltNamegt
ltDataTypegtxsdbooleanltDataTypegt
ltGuiLabelsgt
ltLabel language=ENgtUse SigningltLabelgt
ltLabel language=DEgtVerwendung von SignierungltLabelgt
ltGuiLabelsgt
ltAttributegt
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 59
Adapter Configuration
Configuration attribute of type boolean is rendered to a check-box
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 60
Adapter Metadata Upload (PCK)
Integration Repositorydoes not exist in case ofSAP PCK installations
The upload mechanismfor Adaper Meta Datafor SAP PCK installationsrequires additonalparameters
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 61
AF CPA Cache
The Adapter configuration is deployed from the configuration time(SAP PCK or Integration Directory) to the J2EE service CPACache(Collaboration Profile Agreement)
The Adapter configuration can be accessed at runtime from withinadapter modules or JCA resource adapters via the CPACache API
The two main use cases are implemented inLookupManager to retrieve adapter configuation andNormalizationManager to retrieve Party information
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 62
Packaging Adapter Components
SAP recommends to use SAP Software Deployment Manager (SDM) for deployment
Software Delivery Archives (SDA) can contain software components of different types (eg applications libraries)
Detailed version information and dependencies to other components simplify program management
Adapter Modules and Development
Summary
Adapter Framework Overview
Adapter Strategy
Agenda
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 64
Summary
Adapter Framework runs on J2EE Stack of SAP Web AS
Adapter Framework is platform for Adapter Engine and SAP PCK
Adapter Framework provides an extensible platform for developing and running adapters
Adapter Engine utilizes central configuration monitoring administration
Dual connectivity strategyAdapter Framework for comprehensive integration of adaptersInteroperability via open standards to interop with EAI providers
SAP NetWeaver Certification for adapters based on Adapter Framework available
Adapter mappings metadata stored in Integration Repository
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 7
ProxiesOutside-in development approachInterfaces designed centrally in Integration RepositoryConnect new SAP applications
Native connectivity to Application system (adapter-less)
AdaptersInside-out development approach Interface semantics externally pre-defined Connect existing (legacy) systemsSpecific wire protocol
Adapters vs Proxies
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 8
Integration Server
PlainJ2SE
Adapter Engine
Partner ConnectivityKitOptional non-central
Adapter EngineCentral Adapter Engine
Process Integration ndash Architecture
Integration Repository Integration Directory System Landscape Directory
Business Process Engine
Integration Engine
Adapter FrameworkMessagingQueuing
Security Handling
Resource
Adapter
Resource
Adapter
Resource
Adapter
Adapter FWMessagingQueuing
Security Handling
Adapter FWMessagingQueuing
Security Handling
PCK Configurationand Monitoring
HTTP
IDoc
Adapter
Adapter
FileDBJMSMarketplace
3rd Party Sys
FileDB
JMSSOAP
SAP ampNon-SAPSystem
FileDBJMSMarketplace
3rd Party Sys
FileDBJMSMarketplace
3rd Party Sys
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 9
Full integration of Adapter Engine
Adapter Engine is based on Adapter Framework
Adapter Engine fully integratedCentral configuration of connections to application systems (through appropriate adapters) in Integration DirectoryReuse of Integration Directoryrsquos existing versioning and transport capabilitiesCentral administration and monitoring over adapters IntegrationServer Integration Engine through Runtime Workbench
The Adapter Engine can be deployed centrally as part of Integration Server or as optional local Adapter Engine on its own SAP J2EE Server reasons for use of local Adapter Engine
Protocol of Sender- Receiver system (eg ftp not allowed)Performance High AvailabilityOrganizational Aspects IT requirements
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 10
PI Adapters developed by SAP
Technical AdaptersFileFTP (File Systems FTP Servers)JDBC (RDBMS systems)JMS (Messaging systems e g MQSeries SonicMQ)SOAP (Web Services)Plain HTTPMail (Mail Servers via SMTP IMAP4 POP3)SAP Business Connector (SAP BC)Marketplace (mySAP Marketplaces)
Application AdaptersRFCIDoc
Industry Standard AdaptersRNIF 20 (RosettaNet)RNIF 11 (RosettaNet)CIDX (RNIF 11)
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 11
Industry Standard Adapters as part of Business Packages
Business Package for RosettaNetOrder to Invoice Scenario
PIP3A4 Request Purchase Order PIP3A7 Notify of Purchase Order UpdatePIP3A8 Request Purchase Order ChangePIP3A9 Request Purchase Order CancellationPIP3B2 Notify of Advance ShipmentPIP3C3 Notify of Invoice PIP3A6 Distribute Order StatusPIP3C6 Notify of Remittance Advice
Business Package for CIDXOrder to Invoice Scenario
Order CreateOrder ResponseOrder ChangeShip NoticeInvoice
Business Packages include scenario descriptions business processes message interfaces message types mappings adapter etc
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 12
Partner Eco System
SAP relies on a system of partners to provide connectivity solutions for other applications and certain industry standards
Connectivity Reseller Agreements withSeeburger AGiWay SoftwareInformatica
3rd-Party solutions are sold and delivered through SAP
Technical support for partner solutions via theSAP Support Portal 24x7
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 13
PI Adapters by Seeburger (1)
Technical EDI AdaptersAS2 (EDIINTHTTP(S))Protocol AS2OFTPProtocol OFTPISDN OFTPTCPIPVAN AccessProtocol P7 X400 VAN FTP
Business EDI AdaptersGeneric EDIProtocol OFTPISDN or P7 X400 VAN FTPEDI Converter ANSI X12 EDIFACTMapping Templates Purchase order Order confirmation
Dispatch advice Invoice
Payment (Financial Service Providers)Protocol OFTPISDN P7 X400 VAN FTPEDI Converter EDIFACT SWIFTMapping Templates Payment orders Debit advice
Credit advice Account Statement
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 14
PI Adapters by Seeburger (2)
Industry Specific EDI AdaptersAerospace and Defense AutomotiveChemicals Consumer ProductsHigh-Tech PaperPharmaceutical Retail
Communication ProtocolsOFTPISDN P7 X400 VAN FTP
EDI Converter (EDI lt-gt XML)AECMASPEC 2000 ANSI X12 CHEM eStandards EDIFACT GALIAODETTE TRADACOM VDA
Mapping Templates within Integration RepositoryDelivery forecast Dispatch advise Invoice Purchase order Order confirmation
Message Library for Integration RepositoryHuge message catalog with EDI XML schema definitions
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 15
PI Adapters by iWay Software
Application AdaptersAriba BaanBroadvision ClarifyJD Edwards One World XE JD Edwards Worldi2 LawsonManugistics Microsoft CRMOracle Applications PeoplesoftQAD MFG Pro SiebelVantive
Industry Standard AdaptersSwift TransoraUCCnet
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 16
PI Adapters by iWay Software
Technical AdaptersAS1 (EDIINTSMTP) AS2 (EDIINTHTTP(S))BEA WLI COM+DCOMCorba Lotus NotesTibco Rendezvous
Mainframetransaction AdaptersCICS TMSIMSTelnet (3270) Telnet (5250) Tuxedo
Optionally further adapters can be added from a list of 160 iWayadapters e g HL7 (already certified) DB2 AS3 ebXML
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 17
SAP Conversion Agent by Informatica
Bi-directional conversion of unstructured and semi structured data from to XMLTransformation on message payloadProtocol support via SAPrsquos technical adapter (PI XI adapter framework)Transformations integrated via PI XI AF module
SAP J2EEPI XI Adapter Framework
Adapter
Adapter
Text2XML
XML2Excel
PDF2XML
ConversionAgent Studio
ConversionAgent Services
Conversion Agent Engine
CA AF Module
Conversion Agent J2EE Lib
Seamlessly integrated into Process Integration
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 18
Supported Data Formats by Informatica (partial list)
UNSTRUCTUREDMicrosoft WordMicrosoft ExcelPowerPointPDFStar OfficeWord PerfectASCII reportsHTMLEBCDICUndocumented binariesFlat filesRPGANSI
PRINT STREAMSAFPPost ScriptDJDE
SEMI-STRUCTURED HL7HIPAAASTMANSIndashX12EDIFACTCOBOLFIXCargo IMPMVRSWIFT
OTHER STANDARDSLegalXMLIFX cXMLebXML HL7 V30 ACORD (AL3 XML)
hellip using SAP technical adapter and Conversion Agent
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 19
Conversion Agent
Bi-directional conversion of unstructured and semi structured formats fromto XMLLinked through PI XI adapter framework module based on SAPrsquos technical adapter ndash no transport protocol manipulates payload informationSAP NetWeaver-wide use (via J2EE library)
3rd Party Adapters
Bi-directional conversion of one dedicated data format (eg SWIFT ANSI-X12 hellip) fromto XMLRuns within PI XI adapter framework - support payload transformation and transport protocol
Per adapter dedicated use within one SAP NetWeaver component
Conversion Agent vs 3rd Party Adapters
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 20
More Info about Connectivity Capabilities
httpservicesapcomxi xi in detail connectivity
Connectivity and Interoperability
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 21
Adapter Download from SAP Service Marketplace
SAP Service Marketplace httpservicesapcomswdc Download Installations and Upgrades Entry by Application Group Adapters
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 22
Certification Programs for Process Integration
httpwwwsdnsapcom Partners and ISVsIntegration and Certification Exchange Infrastructure
PI Based Certification Programs
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 23
Public info about certified PI adapters
httpwwwsapcompartnersdirectoriesSearchSolutionepxThird Party Defined Integration Scenarios NW-XI-AF 30
Certified PI Adapters
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 24
Adapter Configuration
Adapter independent parameters
Adapter specific parameters
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 25
Configurationcache
Adapter Engine
ISRuntime
AdapterSender
AdapterReceiver
Adapter Engine in SAP J2EE
Q
Administration
Security
Monitoring
Adapter-Specific
ComponentServices
TracingLogging
Module ProcessorEIS
Channel
acuteMessaging
Configcache
End-to-End MonitoringMessage flow over all components applications
Runtime Workbenchbull Uis for adminstration
monitoring
Integration Builder Directory
Receiver determinationbull Party-gtService-gtAction
Channel Definitionbull Adapter Enginebull Adapter Typebull Message Protocolbull Transport Protocolbull Securitybull Channel Configuration
(Sender Receiver Agreementbull PartyServiceAction lt-gt Channel
ConfigurationMaster
System Landscape Directorybull Holds component description
including address data
AdapterFramework
Integration Repositorybull Holds Adapter metadataIntegration Repositorybull Holds Adapter metadata
httpltIntegrationServerURLgt
Message
httpltAdapterEngineURLgt
OK Error
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 26
Transport Level Security
Transport Protocol Authentication
IDoc RFC and SNC Client Authentication
Client Authentication
Client Authentication
Client Authentication
Client Authentication
CRAM-MD5
Client Authentication
Client Authentication
Client Authentication
CDIX ndash Adapter HTTPs Client Authentication
RFC RFC and SNC
Plain HTTP HTTPs
FileFTP File Transfer Protocol using SSLTLS
SOAP HTTPsSMTPs (Receiver only)
Mail SMTPs POP3 IMAP4
Marketplace HTTPs
RNIF 20 ndash Adapter HTTPs
RNIF 11 ndash Adapter HTTPs
Supported by
Levels of Security
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 27
Message Level Security
Signature Non-Repudiation
of origin
Non-Repudiation of
receipt
Encryption
CDIX ndash Adapter PKCS7
Technology
XI protocol WS-Security
SOAP-Adapter WS-Security
SMIME
Mail-Adapter SMIME
RNIF 20 ndash Adapter SMIME
RNIF 11 ndash Adapter PKCS7
Supported by
Levels of Security
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 28
Access control list
Restrict access to the runtime environmentfor sender services of type Business Service or Business Systemfor interfaces of these sender services
Restrict access to particular (service) users
Check authorization at runtime
Configure access control in the Integration DirectorySender service Specify authorized users in the configuration of the corresponding (sender) serviceInterface Specify authorized users in the configuration of the relevant sender agreement which contains the interface in the object key
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 29
Dynamic Adapter Configuration
Enable adapters to read write dynamic message headers
Sender Adapter (constructing messages)Attach adapter specific information to message headerExamples File name source file size JMS timestamp mail subjectRead access to these attributes in receiver channel interface determination (routing) mapping
Receiver Adapter (consuming messages)Read attributes to overwrite values of channel configurationExamples Directory Name JMS Priority Mail Sender SOAP target URLSet attributes in mapping orUse attributes from sender in receiver channel
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 30
Sender Adapter Configuration (1)
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 31
Sender Adapter Configuration (2)
Add the filename et al to the message
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 32
Receiver Determination
Determinefilename-dependent receiver
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 33
Receiver Adapter
Store the file withthe name set in the messageattribute
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 34
Monitoring Adapter Engine
After selecting a message bdquoDetailsldquo View
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 35
Monitoring Integration Server
After selecting a message bdquoDisplayldquo
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 36
Remark Future of SAP XI 20 Adapter Engine
SAP XI 20 Adapter Engine is available in SAP NW acute04 and SAP NW 2004s as bdquoPlain J2SE Adapter Engineldquo
Functional scope as in SAP XI 20Adopted to the SAP XI 30 message protocolMinor maintenance issues bug fixes
RecommendationUse where platform requirements or limitations (hardware operating system JVM support) demand it
SAP XI 20 Adapter Engine works with SAP NW acute04 and SAP NW 2004s landscapes too
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 37
Integration Server
PlainJ2SE
Adapter Engine
Partner ConnectivityKitOptional non-central
Adapter EngineCentral Adapter Engine
Process Integration ndash Architecture
Integration Repository Integration Directory System Landscape Directory
Business Process Engine
Integration Engine
Adapter FrameworkMessagingQueuing
Security Handling
Resource
Adapter
Resource
Adapter
Resource
Adapter
Adapter FWMessagingQueuing
Security Handling
Adapter FWMessagingQueuing
Security Handling
PCK Configurationand Monitoring
HTTP
IDoc
Adapter
Adapter
FileDBJMSMarketplace
3rd Party Sys
FileDB
JMSSOAP
SAP ampNon-SAPSystem
FileDBJMSMarketplace
3rd Party Sys
FileDBJMSMarketplace
3rd Party Sys
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 38
SAP Partner Connectivity Kit Overview
SAP 3rdParty Appl PI XI
Smaller Company Subsidiary
SAPPCK
SAPApplication
3rd PartyApplication
Large Business Partner Headquarter
Internet
Enablement of smaller companies subsidiaries to exchange XML documents with their business partnerrsquos headquarterrsquos PI XI
SAPPCK
Providing a platform for development of own JCA Resource Adapters
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 39
SAP PCK ndash Adapters
SAP Partner Connectivity Kit (PCK) is based on Adapter Framework
SAP PCKlsquos objective is to enable XML document exchangebetween PI XI and business partner not using PI XI
SAP PCK also provides an extensible platform for developing and running individual JCA Resource adapters
Communication between PI XI and SAP PCK is via SAP XI messaging protocol
SAP PCK Includes the following adapters FileFTP JDBC JMS SOAP RFC IDoc (once available for SAP PCK) Mail SAP BC
Optionally SAP PCK can host further adapters that are available from SAP or 3rd party adapter providers
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 40
SAP PCK ndash Configuration Mapping
SAP PCK is deployed on stand-alone SAP J2EE Engine (part of SAP Web AS) within business partnerrsquos landscape
Configuration administration monitoring done locally on SAP PCK itself without need for an Integration Directory
Configuration UI provides same bdquolook and feelldquo as configuration UI of Adapter Engine
SAP PCK supports the development of message mappings using an integrated graphical mapping editor
Any source XML structure can be mapped to any target XML structureStandard functions are provided to perform calculations Boolean comparisons text mappings and other transformationsOptionally the standard functions can be enhanced with user-defined functions in Java
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 41
SAP PCK ndash Configuration UI
ConfigurationUI to configure Party Service Communication Channel Sender and Receiver agreementsSample screenshot for configuration of communication channel with adapter type sbquoFile FTPlsquo
Adapter Modules and Development
Summary
Adapter Framework Overview
Adapter Strategy
Agenda
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 43
SAP Exchange Infrastructure - Openness
Integration of SAP and non-SAP applicationsAdapter Framework for comprehensive integration of adaptersAdapters are used for technical connectivityAdapter metadata mappings are stored in Integration Repository
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 44
Dual Strategy
Dual connectivity strategyAdapter Framework for comprehensive integration of adapters to provide technical connectivity including central configurationadministration monitoring of adaptersInteroperability based on open standards (SOAP JMS HTTP(S)) tointeroperate with EAI providers
Value propositionStandardized interfaces allow easy integration of adapters from different partnersMinimum knowledge of end-to-end process integration requiredComprehensive integration avoids redundant maintenance ensures consistency enhances transparancyOpenness to integrate non-SAP applications 3rd party systems etcReduced TCO
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 45
Certification
CertificationSAP NetWeaver Certification of 3rd party adapters based on the adapter framework
Value propositionQuality (stability HA aspects performance etc) of adapters is controlledCertification helps customers to find right solutionQuick and convenient search for a variety of certified products with the online partner and product directory (httpwwwsapcompartnersdirectoriesSearchSolutionepx)Faster implementation time and lower integration costs through the use of tested 3rd party integrationReduced TCO
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 46
Adapter Mappings Metadata in Integration Repository
Adapter mappings and adapter metadata are stored in the Integration Repository
Centralized Integration Repository contains all relevant information for collaborative and integrative processesAll content adheres to open standards Adapters provide technical connectivity
Value propositionUse largest content catalogReduce costs in integration projectsReduce maintenance costsReduced TCO
Adapter Modules and Development
Summary
Adapter Framework Overview
Adapter Strategy
Agenda
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 48
For every adapter it is possible to define generic modules in the module processor possibility to extend the functionality of the specific adapter
Equivalent to the dispatcher classes in the J2SE adapter engine migration and examples
The default module configuration for the certain adapter is displayed in the channel configuration
Modules are EJBlsquos
Sequence matters
Module Processor Concept
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 49
Adapter Module Chain
Custom modulescan be added to default modulechains
Additional configurationparameters canbe specified eachmodule
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 50
Module Processor Documentation
SAP Help Portal (httphelpsapcom)SAP XI Runtime Connectivity Adapters Module ProcessorFeedback Mail to xidocumentationsapcom
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 51
Development Environment
Adapter development deployment and testing is possible on a single machine no full-blown PI XI is required
For testing purposes integration scenarioscan be configured in SAP PCK(eg loopback scenario)
Installation of SAP PCK already contains a sample adapter (including Adapter Meta Data) that should serve as a starting point
SAP Partner ConnectivityKit
Adapter FWMessagingQueuing
Security Handling
Resource
Adapter
PCK Configurationand Monitoring
FileDBJMSMarketplace
3rd Party Sys
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 52
Adapter Development Documentation
SAP Help Portal (httphelpsapcom)SAP XI Runtime Connectivity Partner Connectivity Kit Adapter DevelopmentFeedback Mail to xidocumentationsapcom
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 53
Requirements for Adapters (1)
Num AF Interface Category Description
1 JCA 10 conformance Mandatory Adapter must fulfill JCA 10 requirements (e g deployment) plus optional JCA 15 parts which are used by PI XI
2 AF Message Exchange Mandatory Adapter must be able to receive messages from AF and forward them to connected system and vice versa
3 AF Adapter Specific Modules
Optional SAP XI message and protocol conversion may be done entirely by the adapter or as adapter specific module and being called in the AF module chain context
4 Configuration Services Mandatory Unique configuration approach to manage adapters
5 Administrational Services
Optional Administration and Monitoring
6 Utility Service Mandatory Access to basic J2EE resources e g transactions and multithreading must be under control of J2EE server
7 Logging API Optional Adapters may use their own logging
8 Message Metadata Exchange
Optional Provide structure definition of message payloadIf not supported the definition of message types can be done in the Integration Repository
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 54
Requirements for Adapters (2)
Cluster-enabledConsider side-effects of clustering e g bdquoExactlyOnceInOrderldquo Avoid passing maneuvers
SpecializationBuild connection to exactly one type of business system or industrystandard protocol
DirectnessBuild connection to business system or industry standard protocoldirectly without any intermediate software components
SmoothnessLight-weighted low footprint adapter unnecessary system changes(many new or changed system DLL) should be avoided
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 55
Sample Adapter Source Code
Beside the API documentation a working sample adapter is shipped
The source code is available after installation
Analyzing the code helps understanding the Adapter Framework
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 56
Adapter Metadata
Adapter Metadata (AMD)XML file defines all configuration parameterseach adapter
AMD can be uploaded intoIntegration Iepositoryand SAP PCK
Configurationparameters are renderedinto the graphicalconfiguaration frontend
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 57
Adapter Metadata Fragment I
ltAdapterTypeMetaData version=09gt
ltTypegtNAESBltTypegt
ltInboundgt
ltTransportProtocolgt
ltChannelAttributesgt
ltAttributeGroupgt
ltNamegtCRYPTConfigurationltNamegt
ltGuiLabelsgtltLabel language=ENgtCryptographic ConfigurationltLabelgtltGuiLabelsgt
ltAttributeReferencegtltReferenceNamegtCRYPTUseSigningltReferenceNamegt
ltInboundgt
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 58
Adapter Metadata Fragment II
ltAttributegt
ltNamegtCRYPTUseSigningltNamegt
ltDataTypegtxsdbooleanltDataTypegt
ltGuiLabelsgt
ltLabel language=ENgtUse SigningltLabelgt
ltLabel language=DEgtVerwendung von SignierungltLabelgt
ltGuiLabelsgt
ltAttributegt
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 59
Adapter Configuration
Configuration attribute of type boolean is rendered to a check-box
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 60
Adapter Metadata Upload (PCK)
Integration Repositorydoes not exist in case ofSAP PCK installations
The upload mechanismfor Adaper Meta Datafor SAP PCK installationsrequires additonalparameters
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 61
AF CPA Cache
The Adapter configuration is deployed from the configuration time(SAP PCK or Integration Directory) to the J2EE service CPACache(Collaboration Profile Agreement)
The Adapter configuration can be accessed at runtime from withinadapter modules or JCA resource adapters via the CPACache API
The two main use cases are implemented inLookupManager to retrieve adapter configuation andNormalizationManager to retrieve Party information
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 62
Packaging Adapter Components
SAP recommends to use SAP Software Deployment Manager (SDM) for deployment
Software Delivery Archives (SDA) can contain software components of different types (eg applications libraries)
Detailed version information and dependencies to other components simplify program management
Adapter Modules and Development
Summary
Adapter Framework Overview
Adapter Strategy
Agenda
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 64
Summary
Adapter Framework runs on J2EE Stack of SAP Web AS
Adapter Framework is platform for Adapter Engine and SAP PCK
Adapter Framework provides an extensible platform for developing and running adapters
Adapter Engine utilizes central configuration monitoring administration
Dual connectivity strategyAdapter Framework for comprehensive integration of adaptersInteroperability via open standards to interop with EAI providers
SAP NetWeaver Certification for adapters based on Adapter Framework available
Adapter mappings metadata stored in Integration Repository
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 8
Integration Server
PlainJ2SE
Adapter Engine
Partner ConnectivityKitOptional non-central
Adapter EngineCentral Adapter Engine
Process Integration ndash Architecture
Integration Repository Integration Directory System Landscape Directory
Business Process Engine
Integration Engine
Adapter FrameworkMessagingQueuing
Security Handling
Resource
Adapter
Resource
Adapter
Resource
Adapter
Adapter FWMessagingQueuing
Security Handling
Adapter FWMessagingQueuing
Security Handling
PCK Configurationand Monitoring
HTTP
IDoc
Adapter
Adapter
FileDBJMSMarketplace
3rd Party Sys
FileDB
JMSSOAP
SAP ampNon-SAPSystem
FileDBJMSMarketplace
3rd Party Sys
FileDBJMSMarketplace
3rd Party Sys
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 9
Full integration of Adapter Engine
Adapter Engine is based on Adapter Framework
Adapter Engine fully integratedCentral configuration of connections to application systems (through appropriate adapters) in Integration DirectoryReuse of Integration Directoryrsquos existing versioning and transport capabilitiesCentral administration and monitoring over adapters IntegrationServer Integration Engine through Runtime Workbench
The Adapter Engine can be deployed centrally as part of Integration Server or as optional local Adapter Engine on its own SAP J2EE Server reasons for use of local Adapter Engine
Protocol of Sender- Receiver system (eg ftp not allowed)Performance High AvailabilityOrganizational Aspects IT requirements
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 10
PI Adapters developed by SAP
Technical AdaptersFileFTP (File Systems FTP Servers)JDBC (RDBMS systems)JMS (Messaging systems e g MQSeries SonicMQ)SOAP (Web Services)Plain HTTPMail (Mail Servers via SMTP IMAP4 POP3)SAP Business Connector (SAP BC)Marketplace (mySAP Marketplaces)
Application AdaptersRFCIDoc
Industry Standard AdaptersRNIF 20 (RosettaNet)RNIF 11 (RosettaNet)CIDX (RNIF 11)
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 11
Industry Standard Adapters as part of Business Packages
Business Package for RosettaNetOrder to Invoice Scenario
PIP3A4 Request Purchase Order PIP3A7 Notify of Purchase Order UpdatePIP3A8 Request Purchase Order ChangePIP3A9 Request Purchase Order CancellationPIP3B2 Notify of Advance ShipmentPIP3C3 Notify of Invoice PIP3A6 Distribute Order StatusPIP3C6 Notify of Remittance Advice
Business Package for CIDXOrder to Invoice Scenario
Order CreateOrder ResponseOrder ChangeShip NoticeInvoice
Business Packages include scenario descriptions business processes message interfaces message types mappings adapter etc
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 12
Partner Eco System
SAP relies on a system of partners to provide connectivity solutions for other applications and certain industry standards
Connectivity Reseller Agreements withSeeburger AGiWay SoftwareInformatica
3rd-Party solutions are sold and delivered through SAP
Technical support for partner solutions via theSAP Support Portal 24x7
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 13
PI Adapters by Seeburger (1)
Technical EDI AdaptersAS2 (EDIINTHTTP(S))Protocol AS2OFTPProtocol OFTPISDN OFTPTCPIPVAN AccessProtocol P7 X400 VAN FTP
Business EDI AdaptersGeneric EDIProtocol OFTPISDN or P7 X400 VAN FTPEDI Converter ANSI X12 EDIFACTMapping Templates Purchase order Order confirmation
Dispatch advice Invoice
Payment (Financial Service Providers)Protocol OFTPISDN P7 X400 VAN FTPEDI Converter EDIFACT SWIFTMapping Templates Payment orders Debit advice
Credit advice Account Statement
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 14
PI Adapters by Seeburger (2)
Industry Specific EDI AdaptersAerospace and Defense AutomotiveChemicals Consumer ProductsHigh-Tech PaperPharmaceutical Retail
Communication ProtocolsOFTPISDN P7 X400 VAN FTP
EDI Converter (EDI lt-gt XML)AECMASPEC 2000 ANSI X12 CHEM eStandards EDIFACT GALIAODETTE TRADACOM VDA
Mapping Templates within Integration RepositoryDelivery forecast Dispatch advise Invoice Purchase order Order confirmation
Message Library for Integration RepositoryHuge message catalog with EDI XML schema definitions
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 15
PI Adapters by iWay Software
Application AdaptersAriba BaanBroadvision ClarifyJD Edwards One World XE JD Edwards Worldi2 LawsonManugistics Microsoft CRMOracle Applications PeoplesoftQAD MFG Pro SiebelVantive
Industry Standard AdaptersSwift TransoraUCCnet
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 16
PI Adapters by iWay Software
Technical AdaptersAS1 (EDIINTSMTP) AS2 (EDIINTHTTP(S))BEA WLI COM+DCOMCorba Lotus NotesTibco Rendezvous
Mainframetransaction AdaptersCICS TMSIMSTelnet (3270) Telnet (5250) Tuxedo
Optionally further adapters can be added from a list of 160 iWayadapters e g HL7 (already certified) DB2 AS3 ebXML
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 17
SAP Conversion Agent by Informatica
Bi-directional conversion of unstructured and semi structured data from to XMLTransformation on message payloadProtocol support via SAPrsquos technical adapter (PI XI adapter framework)Transformations integrated via PI XI AF module
SAP J2EEPI XI Adapter Framework
Adapter
Adapter
Text2XML
XML2Excel
PDF2XML
ConversionAgent Studio
ConversionAgent Services
Conversion Agent Engine
CA AF Module
Conversion Agent J2EE Lib
Seamlessly integrated into Process Integration
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 18
Supported Data Formats by Informatica (partial list)
UNSTRUCTUREDMicrosoft WordMicrosoft ExcelPowerPointPDFStar OfficeWord PerfectASCII reportsHTMLEBCDICUndocumented binariesFlat filesRPGANSI
PRINT STREAMSAFPPost ScriptDJDE
SEMI-STRUCTURED HL7HIPAAASTMANSIndashX12EDIFACTCOBOLFIXCargo IMPMVRSWIFT
OTHER STANDARDSLegalXMLIFX cXMLebXML HL7 V30 ACORD (AL3 XML)
hellip using SAP technical adapter and Conversion Agent
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 19
Conversion Agent
Bi-directional conversion of unstructured and semi structured formats fromto XMLLinked through PI XI adapter framework module based on SAPrsquos technical adapter ndash no transport protocol manipulates payload informationSAP NetWeaver-wide use (via J2EE library)
3rd Party Adapters
Bi-directional conversion of one dedicated data format (eg SWIFT ANSI-X12 hellip) fromto XMLRuns within PI XI adapter framework - support payload transformation and transport protocol
Per adapter dedicated use within one SAP NetWeaver component
Conversion Agent vs 3rd Party Adapters
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 20
More Info about Connectivity Capabilities
httpservicesapcomxi xi in detail connectivity
Connectivity and Interoperability
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 21
Adapter Download from SAP Service Marketplace
SAP Service Marketplace httpservicesapcomswdc Download Installations and Upgrades Entry by Application Group Adapters
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 22
Certification Programs for Process Integration
httpwwwsdnsapcom Partners and ISVsIntegration and Certification Exchange Infrastructure
PI Based Certification Programs
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 23
Public info about certified PI adapters
httpwwwsapcompartnersdirectoriesSearchSolutionepxThird Party Defined Integration Scenarios NW-XI-AF 30
Certified PI Adapters
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 24
Adapter Configuration
Adapter independent parameters
Adapter specific parameters
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 25
Configurationcache
Adapter Engine
ISRuntime
AdapterSender
AdapterReceiver
Adapter Engine in SAP J2EE
Q
Administration
Security
Monitoring
Adapter-Specific
ComponentServices
TracingLogging
Module ProcessorEIS
Channel
acuteMessaging
Configcache
End-to-End MonitoringMessage flow over all components applications
Runtime Workbenchbull Uis for adminstration
monitoring
Integration Builder Directory
Receiver determinationbull Party-gtService-gtAction
Channel Definitionbull Adapter Enginebull Adapter Typebull Message Protocolbull Transport Protocolbull Securitybull Channel Configuration
(Sender Receiver Agreementbull PartyServiceAction lt-gt Channel
ConfigurationMaster
System Landscape Directorybull Holds component description
including address data
AdapterFramework
Integration Repositorybull Holds Adapter metadataIntegration Repositorybull Holds Adapter metadata
httpltIntegrationServerURLgt
Message
httpltAdapterEngineURLgt
OK Error
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 26
Transport Level Security
Transport Protocol Authentication
IDoc RFC and SNC Client Authentication
Client Authentication
Client Authentication
Client Authentication
Client Authentication
CRAM-MD5
Client Authentication
Client Authentication
Client Authentication
CDIX ndash Adapter HTTPs Client Authentication
RFC RFC and SNC
Plain HTTP HTTPs
FileFTP File Transfer Protocol using SSLTLS
SOAP HTTPsSMTPs (Receiver only)
Mail SMTPs POP3 IMAP4
Marketplace HTTPs
RNIF 20 ndash Adapter HTTPs
RNIF 11 ndash Adapter HTTPs
Supported by
Levels of Security
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 27
Message Level Security
Signature Non-Repudiation
of origin
Non-Repudiation of
receipt
Encryption
CDIX ndash Adapter PKCS7
Technology
XI protocol WS-Security
SOAP-Adapter WS-Security
SMIME
Mail-Adapter SMIME
RNIF 20 ndash Adapter SMIME
RNIF 11 ndash Adapter PKCS7
Supported by
Levels of Security
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 28
Access control list
Restrict access to the runtime environmentfor sender services of type Business Service or Business Systemfor interfaces of these sender services
Restrict access to particular (service) users
Check authorization at runtime
Configure access control in the Integration DirectorySender service Specify authorized users in the configuration of the corresponding (sender) serviceInterface Specify authorized users in the configuration of the relevant sender agreement which contains the interface in the object key
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 29
Dynamic Adapter Configuration
Enable adapters to read write dynamic message headers
Sender Adapter (constructing messages)Attach adapter specific information to message headerExamples File name source file size JMS timestamp mail subjectRead access to these attributes in receiver channel interface determination (routing) mapping
Receiver Adapter (consuming messages)Read attributes to overwrite values of channel configurationExamples Directory Name JMS Priority Mail Sender SOAP target URLSet attributes in mapping orUse attributes from sender in receiver channel
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 30
Sender Adapter Configuration (1)
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 31
Sender Adapter Configuration (2)
Add the filename et al to the message
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 32
Receiver Determination
Determinefilename-dependent receiver
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 33
Receiver Adapter
Store the file withthe name set in the messageattribute
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 34
Monitoring Adapter Engine
After selecting a message bdquoDetailsldquo View
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 35
Monitoring Integration Server
After selecting a message bdquoDisplayldquo
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 36
Remark Future of SAP XI 20 Adapter Engine
SAP XI 20 Adapter Engine is available in SAP NW acute04 and SAP NW 2004s as bdquoPlain J2SE Adapter Engineldquo
Functional scope as in SAP XI 20Adopted to the SAP XI 30 message protocolMinor maintenance issues bug fixes
RecommendationUse where platform requirements or limitations (hardware operating system JVM support) demand it
SAP XI 20 Adapter Engine works with SAP NW acute04 and SAP NW 2004s landscapes too
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 37
Integration Server
PlainJ2SE
Adapter Engine
Partner ConnectivityKitOptional non-central
Adapter EngineCentral Adapter Engine
Process Integration ndash Architecture
Integration Repository Integration Directory System Landscape Directory
Business Process Engine
Integration Engine
Adapter FrameworkMessagingQueuing
Security Handling
Resource
Adapter
Resource
Adapter
Resource
Adapter
Adapter FWMessagingQueuing
Security Handling
Adapter FWMessagingQueuing
Security Handling
PCK Configurationand Monitoring
HTTP
IDoc
Adapter
Adapter
FileDBJMSMarketplace
3rd Party Sys
FileDB
JMSSOAP
SAP ampNon-SAPSystem
FileDBJMSMarketplace
3rd Party Sys
FileDBJMSMarketplace
3rd Party Sys
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 38
SAP Partner Connectivity Kit Overview
SAP 3rdParty Appl PI XI
Smaller Company Subsidiary
SAPPCK
SAPApplication
3rd PartyApplication
Large Business Partner Headquarter
Internet
Enablement of smaller companies subsidiaries to exchange XML documents with their business partnerrsquos headquarterrsquos PI XI
SAPPCK
Providing a platform for development of own JCA Resource Adapters
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 39
SAP PCK ndash Adapters
SAP Partner Connectivity Kit (PCK) is based on Adapter Framework
SAP PCKlsquos objective is to enable XML document exchangebetween PI XI and business partner not using PI XI
SAP PCK also provides an extensible platform for developing and running individual JCA Resource adapters
Communication between PI XI and SAP PCK is via SAP XI messaging protocol
SAP PCK Includes the following adapters FileFTP JDBC JMS SOAP RFC IDoc (once available for SAP PCK) Mail SAP BC
Optionally SAP PCK can host further adapters that are available from SAP or 3rd party adapter providers
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 40
SAP PCK ndash Configuration Mapping
SAP PCK is deployed on stand-alone SAP J2EE Engine (part of SAP Web AS) within business partnerrsquos landscape
Configuration administration monitoring done locally on SAP PCK itself without need for an Integration Directory
Configuration UI provides same bdquolook and feelldquo as configuration UI of Adapter Engine
SAP PCK supports the development of message mappings using an integrated graphical mapping editor
Any source XML structure can be mapped to any target XML structureStandard functions are provided to perform calculations Boolean comparisons text mappings and other transformationsOptionally the standard functions can be enhanced with user-defined functions in Java
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 41
SAP PCK ndash Configuration UI
ConfigurationUI to configure Party Service Communication Channel Sender and Receiver agreementsSample screenshot for configuration of communication channel with adapter type sbquoFile FTPlsquo
Adapter Modules and Development
Summary
Adapter Framework Overview
Adapter Strategy
Agenda
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 43
SAP Exchange Infrastructure - Openness
Integration of SAP and non-SAP applicationsAdapter Framework for comprehensive integration of adaptersAdapters are used for technical connectivityAdapter metadata mappings are stored in Integration Repository
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 44
Dual Strategy
Dual connectivity strategyAdapter Framework for comprehensive integration of adapters to provide technical connectivity including central configurationadministration monitoring of adaptersInteroperability based on open standards (SOAP JMS HTTP(S)) tointeroperate with EAI providers
Value propositionStandardized interfaces allow easy integration of adapters from different partnersMinimum knowledge of end-to-end process integration requiredComprehensive integration avoids redundant maintenance ensures consistency enhances transparancyOpenness to integrate non-SAP applications 3rd party systems etcReduced TCO
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 45
Certification
CertificationSAP NetWeaver Certification of 3rd party adapters based on the adapter framework
Value propositionQuality (stability HA aspects performance etc) of adapters is controlledCertification helps customers to find right solutionQuick and convenient search for a variety of certified products with the online partner and product directory (httpwwwsapcompartnersdirectoriesSearchSolutionepx)Faster implementation time and lower integration costs through the use of tested 3rd party integrationReduced TCO
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 46
Adapter Mappings Metadata in Integration Repository
Adapter mappings and adapter metadata are stored in the Integration Repository
Centralized Integration Repository contains all relevant information for collaborative and integrative processesAll content adheres to open standards Adapters provide technical connectivity
Value propositionUse largest content catalogReduce costs in integration projectsReduce maintenance costsReduced TCO
Adapter Modules and Development
Summary
Adapter Framework Overview
Adapter Strategy
Agenda
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 48
For every adapter it is possible to define generic modules in the module processor possibility to extend the functionality of the specific adapter
Equivalent to the dispatcher classes in the J2SE adapter engine migration and examples
The default module configuration for the certain adapter is displayed in the channel configuration
Modules are EJBlsquos
Sequence matters
Module Processor Concept
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 49
Adapter Module Chain
Custom modulescan be added to default modulechains
Additional configurationparameters canbe specified eachmodule
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 50
Module Processor Documentation
SAP Help Portal (httphelpsapcom)SAP XI Runtime Connectivity Adapters Module ProcessorFeedback Mail to xidocumentationsapcom
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 51
Development Environment
Adapter development deployment and testing is possible on a single machine no full-blown PI XI is required
For testing purposes integration scenarioscan be configured in SAP PCK(eg loopback scenario)
Installation of SAP PCK already contains a sample adapter (including Adapter Meta Data) that should serve as a starting point
SAP Partner ConnectivityKit
Adapter FWMessagingQueuing
Security Handling
Resource
Adapter
PCK Configurationand Monitoring
FileDBJMSMarketplace
3rd Party Sys
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 52
Adapter Development Documentation
SAP Help Portal (httphelpsapcom)SAP XI Runtime Connectivity Partner Connectivity Kit Adapter DevelopmentFeedback Mail to xidocumentationsapcom
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 53
Requirements for Adapters (1)
Num AF Interface Category Description
1 JCA 10 conformance Mandatory Adapter must fulfill JCA 10 requirements (e g deployment) plus optional JCA 15 parts which are used by PI XI
2 AF Message Exchange Mandatory Adapter must be able to receive messages from AF and forward them to connected system and vice versa
3 AF Adapter Specific Modules
Optional SAP XI message and protocol conversion may be done entirely by the adapter or as adapter specific module and being called in the AF module chain context
4 Configuration Services Mandatory Unique configuration approach to manage adapters
5 Administrational Services
Optional Administration and Monitoring
6 Utility Service Mandatory Access to basic J2EE resources e g transactions and multithreading must be under control of J2EE server
7 Logging API Optional Adapters may use their own logging
8 Message Metadata Exchange
Optional Provide structure definition of message payloadIf not supported the definition of message types can be done in the Integration Repository
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 54
Requirements for Adapters (2)
Cluster-enabledConsider side-effects of clustering e g bdquoExactlyOnceInOrderldquo Avoid passing maneuvers
SpecializationBuild connection to exactly one type of business system or industrystandard protocol
DirectnessBuild connection to business system or industry standard protocoldirectly without any intermediate software components
SmoothnessLight-weighted low footprint adapter unnecessary system changes(many new or changed system DLL) should be avoided
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 55
Sample Adapter Source Code
Beside the API documentation a working sample adapter is shipped
The source code is available after installation
Analyzing the code helps understanding the Adapter Framework
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 56
Adapter Metadata
Adapter Metadata (AMD)XML file defines all configuration parameterseach adapter
AMD can be uploaded intoIntegration Iepositoryand SAP PCK
Configurationparameters are renderedinto the graphicalconfiguaration frontend
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 57
Adapter Metadata Fragment I
ltAdapterTypeMetaData version=09gt
ltTypegtNAESBltTypegt
ltInboundgt
ltTransportProtocolgt
ltChannelAttributesgt
ltAttributeGroupgt
ltNamegtCRYPTConfigurationltNamegt
ltGuiLabelsgtltLabel language=ENgtCryptographic ConfigurationltLabelgtltGuiLabelsgt
ltAttributeReferencegtltReferenceNamegtCRYPTUseSigningltReferenceNamegt
ltInboundgt
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 58
Adapter Metadata Fragment II
ltAttributegt
ltNamegtCRYPTUseSigningltNamegt
ltDataTypegtxsdbooleanltDataTypegt
ltGuiLabelsgt
ltLabel language=ENgtUse SigningltLabelgt
ltLabel language=DEgtVerwendung von SignierungltLabelgt
ltGuiLabelsgt
ltAttributegt
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 59
Adapter Configuration
Configuration attribute of type boolean is rendered to a check-box
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 60
Adapter Metadata Upload (PCK)
Integration Repositorydoes not exist in case ofSAP PCK installations
The upload mechanismfor Adaper Meta Datafor SAP PCK installationsrequires additonalparameters
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 61
AF CPA Cache
The Adapter configuration is deployed from the configuration time(SAP PCK or Integration Directory) to the J2EE service CPACache(Collaboration Profile Agreement)
The Adapter configuration can be accessed at runtime from withinadapter modules or JCA resource adapters via the CPACache API
The two main use cases are implemented inLookupManager to retrieve adapter configuation andNormalizationManager to retrieve Party information
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 62
Packaging Adapter Components
SAP recommends to use SAP Software Deployment Manager (SDM) for deployment
Software Delivery Archives (SDA) can contain software components of different types (eg applications libraries)
Detailed version information and dependencies to other components simplify program management
Adapter Modules and Development
Summary
Adapter Framework Overview
Adapter Strategy
Agenda
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 64
Summary
Adapter Framework runs on J2EE Stack of SAP Web AS
Adapter Framework is platform for Adapter Engine and SAP PCK
Adapter Framework provides an extensible platform for developing and running adapters
Adapter Engine utilizes central configuration monitoring administration
Dual connectivity strategyAdapter Framework for comprehensive integration of adaptersInteroperability via open standards to interop with EAI providers
SAP NetWeaver Certification for adapters based on Adapter Framework available
Adapter mappings metadata stored in Integration Repository
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 9
Full integration of Adapter Engine
Adapter Engine is based on Adapter Framework
Adapter Engine fully integratedCentral configuration of connections to application systems (through appropriate adapters) in Integration DirectoryReuse of Integration Directoryrsquos existing versioning and transport capabilitiesCentral administration and monitoring over adapters IntegrationServer Integration Engine through Runtime Workbench
The Adapter Engine can be deployed centrally as part of Integration Server or as optional local Adapter Engine on its own SAP J2EE Server reasons for use of local Adapter Engine
Protocol of Sender- Receiver system (eg ftp not allowed)Performance High AvailabilityOrganizational Aspects IT requirements
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 10
PI Adapters developed by SAP
Technical AdaptersFileFTP (File Systems FTP Servers)JDBC (RDBMS systems)JMS (Messaging systems e g MQSeries SonicMQ)SOAP (Web Services)Plain HTTPMail (Mail Servers via SMTP IMAP4 POP3)SAP Business Connector (SAP BC)Marketplace (mySAP Marketplaces)
Application AdaptersRFCIDoc
Industry Standard AdaptersRNIF 20 (RosettaNet)RNIF 11 (RosettaNet)CIDX (RNIF 11)
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 11
Industry Standard Adapters as part of Business Packages
Business Package for RosettaNetOrder to Invoice Scenario
PIP3A4 Request Purchase Order PIP3A7 Notify of Purchase Order UpdatePIP3A8 Request Purchase Order ChangePIP3A9 Request Purchase Order CancellationPIP3B2 Notify of Advance ShipmentPIP3C3 Notify of Invoice PIP3A6 Distribute Order StatusPIP3C6 Notify of Remittance Advice
Business Package for CIDXOrder to Invoice Scenario
Order CreateOrder ResponseOrder ChangeShip NoticeInvoice
Business Packages include scenario descriptions business processes message interfaces message types mappings adapter etc
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 12
Partner Eco System
SAP relies on a system of partners to provide connectivity solutions for other applications and certain industry standards
Connectivity Reseller Agreements withSeeburger AGiWay SoftwareInformatica
3rd-Party solutions are sold and delivered through SAP
Technical support for partner solutions via theSAP Support Portal 24x7
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 13
PI Adapters by Seeburger (1)
Technical EDI AdaptersAS2 (EDIINTHTTP(S))Protocol AS2OFTPProtocol OFTPISDN OFTPTCPIPVAN AccessProtocol P7 X400 VAN FTP
Business EDI AdaptersGeneric EDIProtocol OFTPISDN or P7 X400 VAN FTPEDI Converter ANSI X12 EDIFACTMapping Templates Purchase order Order confirmation
Dispatch advice Invoice
Payment (Financial Service Providers)Protocol OFTPISDN P7 X400 VAN FTPEDI Converter EDIFACT SWIFTMapping Templates Payment orders Debit advice
Credit advice Account Statement
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 14
PI Adapters by Seeburger (2)
Industry Specific EDI AdaptersAerospace and Defense AutomotiveChemicals Consumer ProductsHigh-Tech PaperPharmaceutical Retail
Communication ProtocolsOFTPISDN P7 X400 VAN FTP
EDI Converter (EDI lt-gt XML)AECMASPEC 2000 ANSI X12 CHEM eStandards EDIFACT GALIAODETTE TRADACOM VDA
Mapping Templates within Integration RepositoryDelivery forecast Dispatch advise Invoice Purchase order Order confirmation
Message Library for Integration RepositoryHuge message catalog with EDI XML schema definitions
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 15
PI Adapters by iWay Software
Application AdaptersAriba BaanBroadvision ClarifyJD Edwards One World XE JD Edwards Worldi2 LawsonManugistics Microsoft CRMOracle Applications PeoplesoftQAD MFG Pro SiebelVantive
Industry Standard AdaptersSwift TransoraUCCnet
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 16
PI Adapters by iWay Software
Technical AdaptersAS1 (EDIINTSMTP) AS2 (EDIINTHTTP(S))BEA WLI COM+DCOMCorba Lotus NotesTibco Rendezvous
Mainframetransaction AdaptersCICS TMSIMSTelnet (3270) Telnet (5250) Tuxedo
Optionally further adapters can be added from a list of 160 iWayadapters e g HL7 (already certified) DB2 AS3 ebXML
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 17
SAP Conversion Agent by Informatica
Bi-directional conversion of unstructured and semi structured data from to XMLTransformation on message payloadProtocol support via SAPrsquos technical adapter (PI XI adapter framework)Transformations integrated via PI XI AF module
SAP J2EEPI XI Adapter Framework
Adapter
Adapter
Text2XML
XML2Excel
PDF2XML
ConversionAgent Studio
ConversionAgent Services
Conversion Agent Engine
CA AF Module
Conversion Agent J2EE Lib
Seamlessly integrated into Process Integration
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 18
Supported Data Formats by Informatica (partial list)
UNSTRUCTUREDMicrosoft WordMicrosoft ExcelPowerPointPDFStar OfficeWord PerfectASCII reportsHTMLEBCDICUndocumented binariesFlat filesRPGANSI
PRINT STREAMSAFPPost ScriptDJDE
SEMI-STRUCTURED HL7HIPAAASTMANSIndashX12EDIFACTCOBOLFIXCargo IMPMVRSWIFT
OTHER STANDARDSLegalXMLIFX cXMLebXML HL7 V30 ACORD (AL3 XML)
hellip using SAP technical adapter and Conversion Agent
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 19
Conversion Agent
Bi-directional conversion of unstructured and semi structured formats fromto XMLLinked through PI XI adapter framework module based on SAPrsquos technical adapter ndash no transport protocol manipulates payload informationSAP NetWeaver-wide use (via J2EE library)
3rd Party Adapters
Bi-directional conversion of one dedicated data format (eg SWIFT ANSI-X12 hellip) fromto XMLRuns within PI XI adapter framework - support payload transformation and transport protocol
Per adapter dedicated use within one SAP NetWeaver component
Conversion Agent vs 3rd Party Adapters
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 20
More Info about Connectivity Capabilities
httpservicesapcomxi xi in detail connectivity
Connectivity and Interoperability
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 21
Adapter Download from SAP Service Marketplace
SAP Service Marketplace httpservicesapcomswdc Download Installations and Upgrades Entry by Application Group Adapters
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 22
Certification Programs for Process Integration
httpwwwsdnsapcom Partners and ISVsIntegration and Certification Exchange Infrastructure
PI Based Certification Programs
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 23
Public info about certified PI adapters
httpwwwsapcompartnersdirectoriesSearchSolutionepxThird Party Defined Integration Scenarios NW-XI-AF 30
Certified PI Adapters
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 24
Adapter Configuration
Adapter independent parameters
Adapter specific parameters
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 25
Configurationcache
Adapter Engine
ISRuntime
AdapterSender
AdapterReceiver
Adapter Engine in SAP J2EE
Q
Administration
Security
Monitoring
Adapter-Specific
ComponentServices
TracingLogging
Module ProcessorEIS
Channel
acuteMessaging
Configcache
End-to-End MonitoringMessage flow over all components applications
Runtime Workbenchbull Uis for adminstration
monitoring
Integration Builder Directory
Receiver determinationbull Party-gtService-gtAction
Channel Definitionbull Adapter Enginebull Adapter Typebull Message Protocolbull Transport Protocolbull Securitybull Channel Configuration
(Sender Receiver Agreementbull PartyServiceAction lt-gt Channel
ConfigurationMaster
System Landscape Directorybull Holds component description
including address data
AdapterFramework
Integration Repositorybull Holds Adapter metadataIntegration Repositorybull Holds Adapter metadata
httpltIntegrationServerURLgt
Message
httpltAdapterEngineURLgt
OK Error
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 26
Transport Level Security
Transport Protocol Authentication
IDoc RFC and SNC Client Authentication
Client Authentication
Client Authentication
Client Authentication
Client Authentication
CRAM-MD5
Client Authentication
Client Authentication
Client Authentication
CDIX ndash Adapter HTTPs Client Authentication
RFC RFC and SNC
Plain HTTP HTTPs
FileFTP File Transfer Protocol using SSLTLS
SOAP HTTPsSMTPs (Receiver only)
Mail SMTPs POP3 IMAP4
Marketplace HTTPs
RNIF 20 ndash Adapter HTTPs
RNIF 11 ndash Adapter HTTPs
Supported by
Levels of Security
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 27
Message Level Security
Signature Non-Repudiation
of origin
Non-Repudiation of
receipt
Encryption
CDIX ndash Adapter PKCS7
Technology
XI protocol WS-Security
SOAP-Adapter WS-Security
SMIME
Mail-Adapter SMIME
RNIF 20 ndash Adapter SMIME
RNIF 11 ndash Adapter PKCS7
Supported by
Levels of Security
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 28
Access control list
Restrict access to the runtime environmentfor sender services of type Business Service or Business Systemfor interfaces of these sender services
Restrict access to particular (service) users
Check authorization at runtime
Configure access control in the Integration DirectorySender service Specify authorized users in the configuration of the corresponding (sender) serviceInterface Specify authorized users in the configuration of the relevant sender agreement which contains the interface in the object key
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 29
Dynamic Adapter Configuration
Enable adapters to read write dynamic message headers
Sender Adapter (constructing messages)Attach adapter specific information to message headerExamples File name source file size JMS timestamp mail subjectRead access to these attributes in receiver channel interface determination (routing) mapping
Receiver Adapter (consuming messages)Read attributes to overwrite values of channel configurationExamples Directory Name JMS Priority Mail Sender SOAP target URLSet attributes in mapping orUse attributes from sender in receiver channel
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 30
Sender Adapter Configuration (1)
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 31
Sender Adapter Configuration (2)
Add the filename et al to the message
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 32
Receiver Determination
Determinefilename-dependent receiver
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 33
Receiver Adapter
Store the file withthe name set in the messageattribute
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 34
Monitoring Adapter Engine
After selecting a message bdquoDetailsldquo View
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 35
Monitoring Integration Server
After selecting a message bdquoDisplayldquo
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 36
Remark Future of SAP XI 20 Adapter Engine
SAP XI 20 Adapter Engine is available in SAP NW acute04 and SAP NW 2004s as bdquoPlain J2SE Adapter Engineldquo
Functional scope as in SAP XI 20Adopted to the SAP XI 30 message protocolMinor maintenance issues bug fixes
RecommendationUse where platform requirements or limitations (hardware operating system JVM support) demand it
SAP XI 20 Adapter Engine works with SAP NW acute04 and SAP NW 2004s landscapes too
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 37
Integration Server
PlainJ2SE
Adapter Engine
Partner ConnectivityKitOptional non-central
Adapter EngineCentral Adapter Engine
Process Integration ndash Architecture
Integration Repository Integration Directory System Landscape Directory
Business Process Engine
Integration Engine
Adapter FrameworkMessagingQueuing
Security Handling
Resource
Adapter
Resource
Adapter
Resource
Adapter
Adapter FWMessagingQueuing
Security Handling
Adapter FWMessagingQueuing
Security Handling
PCK Configurationand Monitoring
HTTP
IDoc
Adapter
Adapter
FileDBJMSMarketplace
3rd Party Sys
FileDB
JMSSOAP
SAP ampNon-SAPSystem
FileDBJMSMarketplace
3rd Party Sys
FileDBJMSMarketplace
3rd Party Sys
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 38
SAP Partner Connectivity Kit Overview
SAP 3rdParty Appl PI XI
Smaller Company Subsidiary
SAPPCK
SAPApplication
3rd PartyApplication
Large Business Partner Headquarter
Internet
Enablement of smaller companies subsidiaries to exchange XML documents with their business partnerrsquos headquarterrsquos PI XI
SAPPCK
Providing a platform for development of own JCA Resource Adapters
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 39
SAP PCK ndash Adapters
SAP Partner Connectivity Kit (PCK) is based on Adapter Framework
SAP PCKlsquos objective is to enable XML document exchangebetween PI XI and business partner not using PI XI
SAP PCK also provides an extensible platform for developing and running individual JCA Resource adapters
Communication between PI XI and SAP PCK is via SAP XI messaging protocol
SAP PCK Includes the following adapters FileFTP JDBC JMS SOAP RFC IDoc (once available for SAP PCK) Mail SAP BC
Optionally SAP PCK can host further adapters that are available from SAP or 3rd party adapter providers
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 40
SAP PCK ndash Configuration Mapping
SAP PCK is deployed on stand-alone SAP J2EE Engine (part of SAP Web AS) within business partnerrsquos landscape
Configuration administration monitoring done locally on SAP PCK itself without need for an Integration Directory
Configuration UI provides same bdquolook and feelldquo as configuration UI of Adapter Engine
SAP PCK supports the development of message mappings using an integrated graphical mapping editor
Any source XML structure can be mapped to any target XML structureStandard functions are provided to perform calculations Boolean comparisons text mappings and other transformationsOptionally the standard functions can be enhanced with user-defined functions in Java
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 41
SAP PCK ndash Configuration UI
ConfigurationUI to configure Party Service Communication Channel Sender and Receiver agreementsSample screenshot for configuration of communication channel with adapter type sbquoFile FTPlsquo
Adapter Modules and Development
Summary
Adapter Framework Overview
Adapter Strategy
Agenda
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 43
SAP Exchange Infrastructure - Openness
Integration of SAP and non-SAP applicationsAdapter Framework for comprehensive integration of adaptersAdapters are used for technical connectivityAdapter metadata mappings are stored in Integration Repository
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 44
Dual Strategy
Dual connectivity strategyAdapter Framework for comprehensive integration of adapters to provide technical connectivity including central configurationadministration monitoring of adaptersInteroperability based on open standards (SOAP JMS HTTP(S)) tointeroperate with EAI providers
Value propositionStandardized interfaces allow easy integration of adapters from different partnersMinimum knowledge of end-to-end process integration requiredComprehensive integration avoids redundant maintenance ensures consistency enhances transparancyOpenness to integrate non-SAP applications 3rd party systems etcReduced TCO
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 45
Certification
CertificationSAP NetWeaver Certification of 3rd party adapters based on the adapter framework
Value propositionQuality (stability HA aspects performance etc) of adapters is controlledCertification helps customers to find right solutionQuick and convenient search for a variety of certified products with the online partner and product directory (httpwwwsapcompartnersdirectoriesSearchSolutionepx)Faster implementation time and lower integration costs through the use of tested 3rd party integrationReduced TCO
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 46
Adapter Mappings Metadata in Integration Repository
Adapter mappings and adapter metadata are stored in the Integration Repository
Centralized Integration Repository contains all relevant information for collaborative and integrative processesAll content adheres to open standards Adapters provide technical connectivity
Value propositionUse largest content catalogReduce costs in integration projectsReduce maintenance costsReduced TCO
Adapter Modules and Development
Summary
Adapter Framework Overview
Adapter Strategy
Agenda
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 48
For every adapter it is possible to define generic modules in the module processor possibility to extend the functionality of the specific adapter
Equivalent to the dispatcher classes in the J2SE adapter engine migration and examples
The default module configuration for the certain adapter is displayed in the channel configuration
Modules are EJBlsquos
Sequence matters
Module Processor Concept
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 49
Adapter Module Chain
Custom modulescan be added to default modulechains
Additional configurationparameters canbe specified eachmodule
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 50
Module Processor Documentation
SAP Help Portal (httphelpsapcom)SAP XI Runtime Connectivity Adapters Module ProcessorFeedback Mail to xidocumentationsapcom
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 51
Development Environment
Adapter development deployment and testing is possible on a single machine no full-blown PI XI is required
For testing purposes integration scenarioscan be configured in SAP PCK(eg loopback scenario)
Installation of SAP PCK already contains a sample adapter (including Adapter Meta Data) that should serve as a starting point
SAP Partner ConnectivityKit
Adapter FWMessagingQueuing
Security Handling
Resource
Adapter
PCK Configurationand Monitoring
FileDBJMSMarketplace
3rd Party Sys
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 52
Adapter Development Documentation
SAP Help Portal (httphelpsapcom)SAP XI Runtime Connectivity Partner Connectivity Kit Adapter DevelopmentFeedback Mail to xidocumentationsapcom
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 53
Requirements for Adapters (1)
Num AF Interface Category Description
1 JCA 10 conformance Mandatory Adapter must fulfill JCA 10 requirements (e g deployment) plus optional JCA 15 parts which are used by PI XI
2 AF Message Exchange Mandatory Adapter must be able to receive messages from AF and forward them to connected system and vice versa
3 AF Adapter Specific Modules
Optional SAP XI message and protocol conversion may be done entirely by the adapter or as adapter specific module and being called in the AF module chain context
4 Configuration Services Mandatory Unique configuration approach to manage adapters
5 Administrational Services
Optional Administration and Monitoring
6 Utility Service Mandatory Access to basic J2EE resources e g transactions and multithreading must be under control of J2EE server
7 Logging API Optional Adapters may use their own logging
8 Message Metadata Exchange
Optional Provide structure definition of message payloadIf not supported the definition of message types can be done in the Integration Repository
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 54
Requirements for Adapters (2)
Cluster-enabledConsider side-effects of clustering e g bdquoExactlyOnceInOrderldquo Avoid passing maneuvers
SpecializationBuild connection to exactly one type of business system or industrystandard protocol
DirectnessBuild connection to business system or industry standard protocoldirectly without any intermediate software components
SmoothnessLight-weighted low footprint adapter unnecessary system changes(many new or changed system DLL) should be avoided
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 55
Sample Adapter Source Code
Beside the API documentation a working sample adapter is shipped
The source code is available after installation
Analyzing the code helps understanding the Adapter Framework
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 56
Adapter Metadata
Adapter Metadata (AMD)XML file defines all configuration parameterseach adapter
AMD can be uploaded intoIntegration Iepositoryand SAP PCK
Configurationparameters are renderedinto the graphicalconfiguaration frontend
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 57
Adapter Metadata Fragment I
ltAdapterTypeMetaData version=09gt
ltTypegtNAESBltTypegt
ltInboundgt
ltTransportProtocolgt
ltChannelAttributesgt
ltAttributeGroupgt
ltNamegtCRYPTConfigurationltNamegt
ltGuiLabelsgtltLabel language=ENgtCryptographic ConfigurationltLabelgtltGuiLabelsgt
ltAttributeReferencegtltReferenceNamegtCRYPTUseSigningltReferenceNamegt
ltInboundgt
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 58
Adapter Metadata Fragment II
ltAttributegt
ltNamegtCRYPTUseSigningltNamegt
ltDataTypegtxsdbooleanltDataTypegt
ltGuiLabelsgt
ltLabel language=ENgtUse SigningltLabelgt
ltLabel language=DEgtVerwendung von SignierungltLabelgt
ltGuiLabelsgt
ltAttributegt
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 59
Adapter Configuration
Configuration attribute of type boolean is rendered to a check-box
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 60
Adapter Metadata Upload (PCK)
Integration Repositorydoes not exist in case ofSAP PCK installations
The upload mechanismfor Adaper Meta Datafor SAP PCK installationsrequires additonalparameters
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 61
AF CPA Cache
The Adapter configuration is deployed from the configuration time(SAP PCK or Integration Directory) to the J2EE service CPACache(Collaboration Profile Agreement)
The Adapter configuration can be accessed at runtime from withinadapter modules or JCA resource adapters via the CPACache API
The two main use cases are implemented inLookupManager to retrieve adapter configuation andNormalizationManager to retrieve Party information
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 62
Packaging Adapter Components
SAP recommends to use SAP Software Deployment Manager (SDM) for deployment
Software Delivery Archives (SDA) can contain software components of different types (eg applications libraries)
Detailed version information and dependencies to other components simplify program management
Adapter Modules and Development
Summary
Adapter Framework Overview
Adapter Strategy
Agenda
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 64
Summary
Adapter Framework runs on J2EE Stack of SAP Web AS
Adapter Framework is platform for Adapter Engine and SAP PCK
Adapter Framework provides an extensible platform for developing and running adapters
Adapter Engine utilizes central configuration monitoring administration
Dual connectivity strategyAdapter Framework for comprehensive integration of adaptersInteroperability via open standards to interop with EAI providers
SAP NetWeaver Certification for adapters based on Adapter Framework available
Adapter mappings metadata stored in Integration Repository
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 10
PI Adapters developed by SAP
Technical AdaptersFileFTP (File Systems FTP Servers)JDBC (RDBMS systems)JMS (Messaging systems e g MQSeries SonicMQ)SOAP (Web Services)Plain HTTPMail (Mail Servers via SMTP IMAP4 POP3)SAP Business Connector (SAP BC)Marketplace (mySAP Marketplaces)
Application AdaptersRFCIDoc
Industry Standard AdaptersRNIF 20 (RosettaNet)RNIF 11 (RosettaNet)CIDX (RNIF 11)
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 11
Industry Standard Adapters as part of Business Packages
Business Package for RosettaNetOrder to Invoice Scenario
PIP3A4 Request Purchase Order PIP3A7 Notify of Purchase Order UpdatePIP3A8 Request Purchase Order ChangePIP3A9 Request Purchase Order CancellationPIP3B2 Notify of Advance ShipmentPIP3C3 Notify of Invoice PIP3A6 Distribute Order StatusPIP3C6 Notify of Remittance Advice
Business Package for CIDXOrder to Invoice Scenario
Order CreateOrder ResponseOrder ChangeShip NoticeInvoice
Business Packages include scenario descriptions business processes message interfaces message types mappings adapter etc
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 12
Partner Eco System
SAP relies on a system of partners to provide connectivity solutions for other applications and certain industry standards
Connectivity Reseller Agreements withSeeburger AGiWay SoftwareInformatica
3rd-Party solutions are sold and delivered through SAP
Technical support for partner solutions via theSAP Support Portal 24x7
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 13
PI Adapters by Seeburger (1)
Technical EDI AdaptersAS2 (EDIINTHTTP(S))Protocol AS2OFTPProtocol OFTPISDN OFTPTCPIPVAN AccessProtocol P7 X400 VAN FTP
Business EDI AdaptersGeneric EDIProtocol OFTPISDN or P7 X400 VAN FTPEDI Converter ANSI X12 EDIFACTMapping Templates Purchase order Order confirmation
Dispatch advice Invoice
Payment (Financial Service Providers)Protocol OFTPISDN P7 X400 VAN FTPEDI Converter EDIFACT SWIFTMapping Templates Payment orders Debit advice
Credit advice Account Statement
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 14
PI Adapters by Seeburger (2)
Industry Specific EDI AdaptersAerospace and Defense AutomotiveChemicals Consumer ProductsHigh-Tech PaperPharmaceutical Retail
Communication ProtocolsOFTPISDN P7 X400 VAN FTP
EDI Converter (EDI lt-gt XML)AECMASPEC 2000 ANSI X12 CHEM eStandards EDIFACT GALIAODETTE TRADACOM VDA
Mapping Templates within Integration RepositoryDelivery forecast Dispatch advise Invoice Purchase order Order confirmation
Message Library for Integration RepositoryHuge message catalog with EDI XML schema definitions
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 15
PI Adapters by iWay Software
Application AdaptersAriba BaanBroadvision ClarifyJD Edwards One World XE JD Edwards Worldi2 LawsonManugistics Microsoft CRMOracle Applications PeoplesoftQAD MFG Pro SiebelVantive
Industry Standard AdaptersSwift TransoraUCCnet
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 16
PI Adapters by iWay Software
Technical AdaptersAS1 (EDIINTSMTP) AS2 (EDIINTHTTP(S))BEA WLI COM+DCOMCorba Lotus NotesTibco Rendezvous
Mainframetransaction AdaptersCICS TMSIMSTelnet (3270) Telnet (5250) Tuxedo
Optionally further adapters can be added from a list of 160 iWayadapters e g HL7 (already certified) DB2 AS3 ebXML
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 17
SAP Conversion Agent by Informatica
Bi-directional conversion of unstructured and semi structured data from to XMLTransformation on message payloadProtocol support via SAPrsquos technical adapter (PI XI adapter framework)Transformations integrated via PI XI AF module
SAP J2EEPI XI Adapter Framework
Adapter
Adapter
Text2XML
XML2Excel
PDF2XML
ConversionAgent Studio
ConversionAgent Services
Conversion Agent Engine
CA AF Module
Conversion Agent J2EE Lib
Seamlessly integrated into Process Integration
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 18
Supported Data Formats by Informatica (partial list)
UNSTRUCTUREDMicrosoft WordMicrosoft ExcelPowerPointPDFStar OfficeWord PerfectASCII reportsHTMLEBCDICUndocumented binariesFlat filesRPGANSI
PRINT STREAMSAFPPost ScriptDJDE
SEMI-STRUCTURED HL7HIPAAASTMANSIndashX12EDIFACTCOBOLFIXCargo IMPMVRSWIFT
OTHER STANDARDSLegalXMLIFX cXMLebXML HL7 V30 ACORD (AL3 XML)
hellip using SAP technical adapter and Conversion Agent
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 19
Conversion Agent
Bi-directional conversion of unstructured and semi structured formats fromto XMLLinked through PI XI adapter framework module based on SAPrsquos technical adapter ndash no transport protocol manipulates payload informationSAP NetWeaver-wide use (via J2EE library)
3rd Party Adapters
Bi-directional conversion of one dedicated data format (eg SWIFT ANSI-X12 hellip) fromto XMLRuns within PI XI adapter framework - support payload transformation and transport protocol
Per adapter dedicated use within one SAP NetWeaver component
Conversion Agent vs 3rd Party Adapters
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 20
More Info about Connectivity Capabilities
httpservicesapcomxi xi in detail connectivity
Connectivity and Interoperability
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 21
Adapter Download from SAP Service Marketplace
SAP Service Marketplace httpservicesapcomswdc Download Installations and Upgrades Entry by Application Group Adapters
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 22
Certification Programs for Process Integration
httpwwwsdnsapcom Partners and ISVsIntegration and Certification Exchange Infrastructure
PI Based Certification Programs
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 23
Public info about certified PI adapters
httpwwwsapcompartnersdirectoriesSearchSolutionepxThird Party Defined Integration Scenarios NW-XI-AF 30
Certified PI Adapters
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 24
Adapter Configuration
Adapter independent parameters
Adapter specific parameters
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 25
Configurationcache
Adapter Engine
ISRuntime
AdapterSender
AdapterReceiver
Adapter Engine in SAP J2EE
Q
Administration
Security
Monitoring
Adapter-Specific
ComponentServices
TracingLogging
Module ProcessorEIS
Channel
acuteMessaging
Configcache
End-to-End MonitoringMessage flow over all components applications
Runtime Workbenchbull Uis for adminstration
monitoring
Integration Builder Directory
Receiver determinationbull Party-gtService-gtAction
Channel Definitionbull Adapter Enginebull Adapter Typebull Message Protocolbull Transport Protocolbull Securitybull Channel Configuration
(Sender Receiver Agreementbull PartyServiceAction lt-gt Channel
ConfigurationMaster
System Landscape Directorybull Holds component description
including address data
AdapterFramework
Integration Repositorybull Holds Adapter metadataIntegration Repositorybull Holds Adapter metadata
httpltIntegrationServerURLgt
Message
httpltAdapterEngineURLgt
OK Error
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 26
Transport Level Security
Transport Protocol Authentication
IDoc RFC and SNC Client Authentication
Client Authentication
Client Authentication
Client Authentication
Client Authentication
CRAM-MD5
Client Authentication
Client Authentication
Client Authentication
CDIX ndash Adapter HTTPs Client Authentication
RFC RFC and SNC
Plain HTTP HTTPs
FileFTP File Transfer Protocol using SSLTLS
SOAP HTTPsSMTPs (Receiver only)
Mail SMTPs POP3 IMAP4
Marketplace HTTPs
RNIF 20 ndash Adapter HTTPs
RNIF 11 ndash Adapter HTTPs
Supported by
Levels of Security
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 27
Message Level Security
Signature Non-Repudiation
of origin
Non-Repudiation of
receipt
Encryption
CDIX ndash Adapter PKCS7
Technology
XI protocol WS-Security
SOAP-Adapter WS-Security
SMIME
Mail-Adapter SMIME
RNIF 20 ndash Adapter SMIME
RNIF 11 ndash Adapter PKCS7
Supported by
Levels of Security
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 28
Access control list
Restrict access to the runtime environmentfor sender services of type Business Service or Business Systemfor interfaces of these sender services
Restrict access to particular (service) users
Check authorization at runtime
Configure access control in the Integration DirectorySender service Specify authorized users in the configuration of the corresponding (sender) serviceInterface Specify authorized users in the configuration of the relevant sender agreement which contains the interface in the object key
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 29
Dynamic Adapter Configuration
Enable adapters to read write dynamic message headers
Sender Adapter (constructing messages)Attach adapter specific information to message headerExamples File name source file size JMS timestamp mail subjectRead access to these attributes in receiver channel interface determination (routing) mapping
Receiver Adapter (consuming messages)Read attributes to overwrite values of channel configurationExamples Directory Name JMS Priority Mail Sender SOAP target URLSet attributes in mapping orUse attributes from sender in receiver channel
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 30
Sender Adapter Configuration (1)
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 31
Sender Adapter Configuration (2)
Add the filename et al to the message
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 32
Receiver Determination
Determinefilename-dependent receiver
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 33
Receiver Adapter
Store the file withthe name set in the messageattribute
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 34
Monitoring Adapter Engine
After selecting a message bdquoDetailsldquo View
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 35
Monitoring Integration Server
After selecting a message bdquoDisplayldquo
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 36
Remark Future of SAP XI 20 Adapter Engine
SAP XI 20 Adapter Engine is available in SAP NW acute04 and SAP NW 2004s as bdquoPlain J2SE Adapter Engineldquo
Functional scope as in SAP XI 20Adopted to the SAP XI 30 message protocolMinor maintenance issues bug fixes
RecommendationUse where platform requirements or limitations (hardware operating system JVM support) demand it
SAP XI 20 Adapter Engine works with SAP NW acute04 and SAP NW 2004s landscapes too
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 37
Integration Server
PlainJ2SE
Adapter Engine
Partner ConnectivityKitOptional non-central
Adapter EngineCentral Adapter Engine
Process Integration ndash Architecture
Integration Repository Integration Directory System Landscape Directory
Business Process Engine
Integration Engine
Adapter FrameworkMessagingQueuing
Security Handling
Resource
Adapter
Resource
Adapter
Resource
Adapter
Adapter FWMessagingQueuing
Security Handling
Adapter FWMessagingQueuing
Security Handling
PCK Configurationand Monitoring
HTTP
IDoc
Adapter
Adapter
FileDBJMSMarketplace
3rd Party Sys
FileDB
JMSSOAP
SAP ampNon-SAPSystem
FileDBJMSMarketplace
3rd Party Sys
FileDBJMSMarketplace
3rd Party Sys
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 38
SAP Partner Connectivity Kit Overview
SAP 3rdParty Appl PI XI
Smaller Company Subsidiary
SAPPCK
SAPApplication
3rd PartyApplication
Large Business Partner Headquarter
Internet
Enablement of smaller companies subsidiaries to exchange XML documents with their business partnerrsquos headquarterrsquos PI XI
SAPPCK
Providing a platform for development of own JCA Resource Adapters
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 39
SAP PCK ndash Adapters
SAP Partner Connectivity Kit (PCK) is based on Adapter Framework
SAP PCKlsquos objective is to enable XML document exchangebetween PI XI and business partner not using PI XI
SAP PCK also provides an extensible platform for developing and running individual JCA Resource adapters
Communication between PI XI and SAP PCK is via SAP XI messaging protocol
SAP PCK Includes the following adapters FileFTP JDBC JMS SOAP RFC IDoc (once available for SAP PCK) Mail SAP BC
Optionally SAP PCK can host further adapters that are available from SAP or 3rd party adapter providers
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 40
SAP PCK ndash Configuration Mapping
SAP PCK is deployed on stand-alone SAP J2EE Engine (part of SAP Web AS) within business partnerrsquos landscape
Configuration administration monitoring done locally on SAP PCK itself without need for an Integration Directory
Configuration UI provides same bdquolook and feelldquo as configuration UI of Adapter Engine
SAP PCK supports the development of message mappings using an integrated graphical mapping editor
Any source XML structure can be mapped to any target XML structureStandard functions are provided to perform calculations Boolean comparisons text mappings and other transformationsOptionally the standard functions can be enhanced with user-defined functions in Java
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 41
SAP PCK ndash Configuration UI
ConfigurationUI to configure Party Service Communication Channel Sender and Receiver agreementsSample screenshot for configuration of communication channel with adapter type sbquoFile FTPlsquo
Adapter Modules and Development
Summary
Adapter Framework Overview
Adapter Strategy
Agenda
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 43
SAP Exchange Infrastructure - Openness
Integration of SAP and non-SAP applicationsAdapter Framework for comprehensive integration of adaptersAdapters are used for technical connectivityAdapter metadata mappings are stored in Integration Repository
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 44
Dual Strategy
Dual connectivity strategyAdapter Framework for comprehensive integration of adapters to provide technical connectivity including central configurationadministration monitoring of adaptersInteroperability based on open standards (SOAP JMS HTTP(S)) tointeroperate with EAI providers
Value propositionStandardized interfaces allow easy integration of adapters from different partnersMinimum knowledge of end-to-end process integration requiredComprehensive integration avoids redundant maintenance ensures consistency enhances transparancyOpenness to integrate non-SAP applications 3rd party systems etcReduced TCO
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 45
Certification
CertificationSAP NetWeaver Certification of 3rd party adapters based on the adapter framework
Value propositionQuality (stability HA aspects performance etc) of adapters is controlledCertification helps customers to find right solutionQuick and convenient search for a variety of certified products with the online partner and product directory (httpwwwsapcompartnersdirectoriesSearchSolutionepx)Faster implementation time and lower integration costs through the use of tested 3rd party integrationReduced TCO
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 46
Adapter Mappings Metadata in Integration Repository
Adapter mappings and adapter metadata are stored in the Integration Repository
Centralized Integration Repository contains all relevant information for collaborative and integrative processesAll content adheres to open standards Adapters provide technical connectivity
Value propositionUse largest content catalogReduce costs in integration projectsReduce maintenance costsReduced TCO
Adapter Modules and Development
Summary
Adapter Framework Overview
Adapter Strategy
Agenda
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 48
For every adapter it is possible to define generic modules in the module processor possibility to extend the functionality of the specific adapter
Equivalent to the dispatcher classes in the J2SE adapter engine migration and examples
The default module configuration for the certain adapter is displayed in the channel configuration
Modules are EJBlsquos
Sequence matters
Module Processor Concept
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 49
Adapter Module Chain
Custom modulescan be added to default modulechains
Additional configurationparameters canbe specified eachmodule
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 50
Module Processor Documentation
SAP Help Portal (httphelpsapcom)SAP XI Runtime Connectivity Adapters Module ProcessorFeedback Mail to xidocumentationsapcom
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 51
Development Environment
Adapter development deployment and testing is possible on a single machine no full-blown PI XI is required
For testing purposes integration scenarioscan be configured in SAP PCK(eg loopback scenario)
Installation of SAP PCK already contains a sample adapter (including Adapter Meta Data) that should serve as a starting point
SAP Partner ConnectivityKit
Adapter FWMessagingQueuing
Security Handling
Resource
Adapter
PCK Configurationand Monitoring
FileDBJMSMarketplace
3rd Party Sys
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 52
Adapter Development Documentation
SAP Help Portal (httphelpsapcom)SAP XI Runtime Connectivity Partner Connectivity Kit Adapter DevelopmentFeedback Mail to xidocumentationsapcom
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 53
Requirements for Adapters (1)
Num AF Interface Category Description
1 JCA 10 conformance Mandatory Adapter must fulfill JCA 10 requirements (e g deployment) plus optional JCA 15 parts which are used by PI XI
2 AF Message Exchange Mandatory Adapter must be able to receive messages from AF and forward them to connected system and vice versa
3 AF Adapter Specific Modules
Optional SAP XI message and protocol conversion may be done entirely by the adapter or as adapter specific module and being called in the AF module chain context
4 Configuration Services Mandatory Unique configuration approach to manage adapters
5 Administrational Services
Optional Administration and Monitoring
6 Utility Service Mandatory Access to basic J2EE resources e g transactions and multithreading must be under control of J2EE server
7 Logging API Optional Adapters may use their own logging
8 Message Metadata Exchange
Optional Provide structure definition of message payloadIf not supported the definition of message types can be done in the Integration Repository
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 54
Requirements for Adapters (2)
Cluster-enabledConsider side-effects of clustering e g bdquoExactlyOnceInOrderldquo Avoid passing maneuvers
SpecializationBuild connection to exactly one type of business system or industrystandard protocol
DirectnessBuild connection to business system or industry standard protocoldirectly without any intermediate software components
SmoothnessLight-weighted low footprint adapter unnecessary system changes(many new or changed system DLL) should be avoided
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 55
Sample Adapter Source Code
Beside the API documentation a working sample adapter is shipped
The source code is available after installation
Analyzing the code helps understanding the Adapter Framework
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 56
Adapter Metadata
Adapter Metadata (AMD)XML file defines all configuration parameterseach adapter
AMD can be uploaded intoIntegration Iepositoryand SAP PCK
Configurationparameters are renderedinto the graphicalconfiguaration frontend
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 57
Adapter Metadata Fragment I
ltAdapterTypeMetaData version=09gt
ltTypegtNAESBltTypegt
ltInboundgt
ltTransportProtocolgt
ltChannelAttributesgt
ltAttributeGroupgt
ltNamegtCRYPTConfigurationltNamegt
ltGuiLabelsgtltLabel language=ENgtCryptographic ConfigurationltLabelgtltGuiLabelsgt
ltAttributeReferencegtltReferenceNamegtCRYPTUseSigningltReferenceNamegt
ltInboundgt
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 58
Adapter Metadata Fragment II
ltAttributegt
ltNamegtCRYPTUseSigningltNamegt
ltDataTypegtxsdbooleanltDataTypegt
ltGuiLabelsgt
ltLabel language=ENgtUse SigningltLabelgt
ltLabel language=DEgtVerwendung von SignierungltLabelgt
ltGuiLabelsgt
ltAttributegt
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 59
Adapter Configuration
Configuration attribute of type boolean is rendered to a check-box
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 60
Adapter Metadata Upload (PCK)
Integration Repositorydoes not exist in case ofSAP PCK installations
The upload mechanismfor Adaper Meta Datafor SAP PCK installationsrequires additonalparameters
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 61
AF CPA Cache
The Adapter configuration is deployed from the configuration time(SAP PCK or Integration Directory) to the J2EE service CPACache(Collaboration Profile Agreement)
The Adapter configuration can be accessed at runtime from withinadapter modules or JCA resource adapters via the CPACache API
The two main use cases are implemented inLookupManager to retrieve adapter configuation andNormalizationManager to retrieve Party information
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 62
Packaging Adapter Components
SAP recommends to use SAP Software Deployment Manager (SDM) for deployment
Software Delivery Archives (SDA) can contain software components of different types (eg applications libraries)
Detailed version information and dependencies to other components simplify program management
Adapter Modules and Development
Summary
Adapter Framework Overview
Adapter Strategy
Agenda
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 64
Summary
Adapter Framework runs on J2EE Stack of SAP Web AS
Adapter Framework is platform for Adapter Engine and SAP PCK
Adapter Framework provides an extensible platform for developing and running adapters
Adapter Engine utilizes central configuration monitoring administration
Dual connectivity strategyAdapter Framework for comprehensive integration of adaptersInteroperability via open standards to interop with EAI providers
SAP NetWeaver Certification for adapters based on Adapter Framework available
Adapter mappings metadata stored in Integration Repository
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 11
Industry Standard Adapters as part of Business Packages
Business Package for RosettaNetOrder to Invoice Scenario
PIP3A4 Request Purchase Order PIP3A7 Notify of Purchase Order UpdatePIP3A8 Request Purchase Order ChangePIP3A9 Request Purchase Order CancellationPIP3B2 Notify of Advance ShipmentPIP3C3 Notify of Invoice PIP3A6 Distribute Order StatusPIP3C6 Notify of Remittance Advice
Business Package for CIDXOrder to Invoice Scenario
Order CreateOrder ResponseOrder ChangeShip NoticeInvoice
Business Packages include scenario descriptions business processes message interfaces message types mappings adapter etc
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 12
Partner Eco System
SAP relies on a system of partners to provide connectivity solutions for other applications and certain industry standards
Connectivity Reseller Agreements withSeeburger AGiWay SoftwareInformatica
3rd-Party solutions are sold and delivered through SAP
Technical support for partner solutions via theSAP Support Portal 24x7
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 13
PI Adapters by Seeburger (1)
Technical EDI AdaptersAS2 (EDIINTHTTP(S))Protocol AS2OFTPProtocol OFTPISDN OFTPTCPIPVAN AccessProtocol P7 X400 VAN FTP
Business EDI AdaptersGeneric EDIProtocol OFTPISDN or P7 X400 VAN FTPEDI Converter ANSI X12 EDIFACTMapping Templates Purchase order Order confirmation
Dispatch advice Invoice
Payment (Financial Service Providers)Protocol OFTPISDN P7 X400 VAN FTPEDI Converter EDIFACT SWIFTMapping Templates Payment orders Debit advice
Credit advice Account Statement
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 14
PI Adapters by Seeburger (2)
Industry Specific EDI AdaptersAerospace and Defense AutomotiveChemicals Consumer ProductsHigh-Tech PaperPharmaceutical Retail
Communication ProtocolsOFTPISDN P7 X400 VAN FTP
EDI Converter (EDI lt-gt XML)AECMASPEC 2000 ANSI X12 CHEM eStandards EDIFACT GALIAODETTE TRADACOM VDA
Mapping Templates within Integration RepositoryDelivery forecast Dispatch advise Invoice Purchase order Order confirmation
Message Library for Integration RepositoryHuge message catalog with EDI XML schema definitions
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 15
PI Adapters by iWay Software
Application AdaptersAriba BaanBroadvision ClarifyJD Edwards One World XE JD Edwards Worldi2 LawsonManugistics Microsoft CRMOracle Applications PeoplesoftQAD MFG Pro SiebelVantive
Industry Standard AdaptersSwift TransoraUCCnet
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 16
PI Adapters by iWay Software
Technical AdaptersAS1 (EDIINTSMTP) AS2 (EDIINTHTTP(S))BEA WLI COM+DCOMCorba Lotus NotesTibco Rendezvous
Mainframetransaction AdaptersCICS TMSIMSTelnet (3270) Telnet (5250) Tuxedo
Optionally further adapters can be added from a list of 160 iWayadapters e g HL7 (already certified) DB2 AS3 ebXML
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 17
SAP Conversion Agent by Informatica
Bi-directional conversion of unstructured and semi structured data from to XMLTransformation on message payloadProtocol support via SAPrsquos technical adapter (PI XI adapter framework)Transformations integrated via PI XI AF module
SAP J2EEPI XI Adapter Framework
Adapter
Adapter
Text2XML
XML2Excel
PDF2XML
ConversionAgent Studio
ConversionAgent Services
Conversion Agent Engine
CA AF Module
Conversion Agent J2EE Lib
Seamlessly integrated into Process Integration
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 18
Supported Data Formats by Informatica (partial list)
UNSTRUCTUREDMicrosoft WordMicrosoft ExcelPowerPointPDFStar OfficeWord PerfectASCII reportsHTMLEBCDICUndocumented binariesFlat filesRPGANSI
PRINT STREAMSAFPPost ScriptDJDE
SEMI-STRUCTURED HL7HIPAAASTMANSIndashX12EDIFACTCOBOLFIXCargo IMPMVRSWIFT
OTHER STANDARDSLegalXMLIFX cXMLebXML HL7 V30 ACORD (AL3 XML)
hellip using SAP technical adapter and Conversion Agent
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 19
Conversion Agent
Bi-directional conversion of unstructured and semi structured formats fromto XMLLinked through PI XI adapter framework module based on SAPrsquos technical adapter ndash no transport protocol manipulates payload informationSAP NetWeaver-wide use (via J2EE library)
3rd Party Adapters
Bi-directional conversion of one dedicated data format (eg SWIFT ANSI-X12 hellip) fromto XMLRuns within PI XI adapter framework - support payload transformation and transport protocol
Per adapter dedicated use within one SAP NetWeaver component
Conversion Agent vs 3rd Party Adapters
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 20
More Info about Connectivity Capabilities
httpservicesapcomxi xi in detail connectivity
Connectivity and Interoperability
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 21
Adapter Download from SAP Service Marketplace
SAP Service Marketplace httpservicesapcomswdc Download Installations and Upgrades Entry by Application Group Adapters
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 22
Certification Programs for Process Integration
httpwwwsdnsapcom Partners and ISVsIntegration and Certification Exchange Infrastructure
PI Based Certification Programs
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 23
Public info about certified PI adapters
httpwwwsapcompartnersdirectoriesSearchSolutionepxThird Party Defined Integration Scenarios NW-XI-AF 30
Certified PI Adapters
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 24
Adapter Configuration
Adapter independent parameters
Adapter specific parameters
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 25
Configurationcache
Adapter Engine
ISRuntime
AdapterSender
AdapterReceiver
Adapter Engine in SAP J2EE
Q
Administration
Security
Monitoring
Adapter-Specific
ComponentServices
TracingLogging
Module ProcessorEIS
Channel
acuteMessaging
Configcache
End-to-End MonitoringMessage flow over all components applications
Runtime Workbenchbull Uis for adminstration
monitoring
Integration Builder Directory
Receiver determinationbull Party-gtService-gtAction
Channel Definitionbull Adapter Enginebull Adapter Typebull Message Protocolbull Transport Protocolbull Securitybull Channel Configuration
(Sender Receiver Agreementbull PartyServiceAction lt-gt Channel
ConfigurationMaster
System Landscape Directorybull Holds component description
including address data
AdapterFramework
Integration Repositorybull Holds Adapter metadataIntegration Repositorybull Holds Adapter metadata
httpltIntegrationServerURLgt
Message
httpltAdapterEngineURLgt
OK Error
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 26
Transport Level Security
Transport Protocol Authentication
IDoc RFC and SNC Client Authentication
Client Authentication
Client Authentication
Client Authentication
Client Authentication
CRAM-MD5
Client Authentication
Client Authentication
Client Authentication
CDIX ndash Adapter HTTPs Client Authentication
RFC RFC and SNC
Plain HTTP HTTPs
FileFTP File Transfer Protocol using SSLTLS
SOAP HTTPsSMTPs (Receiver only)
Mail SMTPs POP3 IMAP4
Marketplace HTTPs
RNIF 20 ndash Adapter HTTPs
RNIF 11 ndash Adapter HTTPs
Supported by
Levels of Security
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 27
Message Level Security
Signature Non-Repudiation
of origin
Non-Repudiation of
receipt
Encryption
CDIX ndash Adapter PKCS7
Technology
XI protocol WS-Security
SOAP-Adapter WS-Security
SMIME
Mail-Adapter SMIME
RNIF 20 ndash Adapter SMIME
RNIF 11 ndash Adapter PKCS7
Supported by
Levels of Security
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 28
Access control list
Restrict access to the runtime environmentfor sender services of type Business Service or Business Systemfor interfaces of these sender services
Restrict access to particular (service) users
Check authorization at runtime
Configure access control in the Integration DirectorySender service Specify authorized users in the configuration of the corresponding (sender) serviceInterface Specify authorized users in the configuration of the relevant sender agreement which contains the interface in the object key
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 29
Dynamic Adapter Configuration
Enable adapters to read write dynamic message headers
Sender Adapter (constructing messages)Attach adapter specific information to message headerExamples File name source file size JMS timestamp mail subjectRead access to these attributes in receiver channel interface determination (routing) mapping
Receiver Adapter (consuming messages)Read attributes to overwrite values of channel configurationExamples Directory Name JMS Priority Mail Sender SOAP target URLSet attributes in mapping orUse attributes from sender in receiver channel
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 30
Sender Adapter Configuration (1)
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 31
Sender Adapter Configuration (2)
Add the filename et al to the message
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 32
Receiver Determination
Determinefilename-dependent receiver
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 33
Receiver Adapter
Store the file withthe name set in the messageattribute
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 34
Monitoring Adapter Engine
After selecting a message bdquoDetailsldquo View
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 35
Monitoring Integration Server
After selecting a message bdquoDisplayldquo
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 36
Remark Future of SAP XI 20 Adapter Engine
SAP XI 20 Adapter Engine is available in SAP NW acute04 and SAP NW 2004s as bdquoPlain J2SE Adapter Engineldquo
Functional scope as in SAP XI 20Adopted to the SAP XI 30 message protocolMinor maintenance issues bug fixes
RecommendationUse where platform requirements or limitations (hardware operating system JVM support) demand it
SAP XI 20 Adapter Engine works with SAP NW acute04 and SAP NW 2004s landscapes too
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 37
Integration Server
PlainJ2SE
Adapter Engine
Partner ConnectivityKitOptional non-central
Adapter EngineCentral Adapter Engine
Process Integration ndash Architecture
Integration Repository Integration Directory System Landscape Directory
Business Process Engine
Integration Engine
Adapter FrameworkMessagingQueuing
Security Handling
Resource
Adapter
Resource
Adapter
Resource
Adapter
Adapter FWMessagingQueuing
Security Handling
Adapter FWMessagingQueuing
Security Handling
PCK Configurationand Monitoring
HTTP
IDoc
Adapter
Adapter
FileDBJMSMarketplace
3rd Party Sys
FileDB
JMSSOAP
SAP ampNon-SAPSystem
FileDBJMSMarketplace
3rd Party Sys
FileDBJMSMarketplace
3rd Party Sys
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 38
SAP Partner Connectivity Kit Overview
SAP 3rdParty Appl PI XI
Smaller Company Subsidiary
SAPPCK
SAPApplication
3rd PartyApplication
Large Business Partner Headquarter
Internet
Enablement of smaller companies subsidiaries to exchange XML documents with their business partnerrsquos headquarterrsquos PI XI
SAPPCK
Providing a platform for development of own JCA Resource Adapters
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 39
SAP PCK ndash Adapters
SAP Partner Connectivity Kit (PCK) is based on Adapter Framework
SAP PCKlsquos objective is to enable XML document exchangebetween PI XI and business partner not using PI XI
SAP PCK also provides an extensible platform for developing and running individual JCA Resource adapters
Communication between PI XI and SAP PCK is via SAP XI messaging protocol
SAP PCK Includes the following adapters FileFTP JDBC JMS SOAP RFC IDoc (once available for SAP PCK) Mail SAP BC
Optionally SAP PCK can host further adapters that are available from SAP or 3rd party adapter providers
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 40
SAP PCK ndash Configuration Mapping
SAP PCK is deployed on stand-alone SAP J2EE Engine (part of SAP Web AS) within business partnerrsquos landscape
Configuration administration monitoring done locally on SAP PCK itself without need for an Integration Directory
Configuration UI provides same bdquolook and feelldquo as configuration UI of Adapter Engine
SAP PCK supports the development of message mappings using an integrated graphical mapping editor
Any source XML structure can be mapped to any target XML structureStandard functions are provided to perform calculations Boolean comparisons text mappings and other transformationsOptionally the standard functions can be enhanced with user-defined functions in Java
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 41
SAP PCK ndash Configuration UI
ConfigurationUI to configure Party Service Communication Channel Sender and Receiver agreementsSample screenshot for configuration of communication channel with adapter type sbquoFile FTPlsquo
Adapter Modules and Development
Summary
Adapter Framework Overview
Adapter Strategy
Agenda
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 43
SAP Exchange Infrastructure - Openness
Integration of SAP and non-SAP applicationsAdapter Framework for comprehensive integration of adaptersAdapters are used for technical connectivityAdapter metadata mappings are stored in Integration Repository
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 44
Dual Strategy
Dual connectivity strategyAdapter Framework for comprehensive integration of adapters to provide technical connectivity including central configurationadministration monitoring of adaptersInteroperability based on open standards (SOAP JMS HTTP(S)) tointeroperate with EAI providers
Value propositionStandardized interfaces allow easy integration of adapters from different partnersMinimum knowledge of end-to-end process integration requiredComprehensive integration avoids redundant maintenance ensures consistency enhances transparancyOpenness to integrate non-SAP applications 3rd party systems etcReduced TCO
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 45
Certification
CertificationSAP NetWeaver Certification of 3rd party adapters based on the adapter framework
Value propositionQuality (stability HA aspects performance etc) of adapters is controlledCertification helps customers to find right solutionQuick and convenient search for a variety of certified products with the online partner and product directory (httpwwwsapcompartnersdirectoriesSearchSolutionepx)Faster implementation time and lower integration costs through the use of tested 3rd party integrationReduced TCO
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 46
Adapter Mappings Metadata in Integration Repository
Adapter mappings and adapter metadata are stored in the Integration Repository
Centralized Integration Repository contains all relevant information for collaborative and integrative processesAll content adheres to open standards Adapters provide technical connectivity
Value propositionUse largest content catalogReduce costs in integration projectsReduce maintenance costsReduced TCO
Adapter Modules and Development
Summary
Adapter Framework Overview
Adapter Strategy
Agenda
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 48
For every adapter it is possible to define generic modules in the module processor possibility to extend the functionality of the specific adapter
Equivalent to the dispatcher classes in the J2SE adapter engine migration and examples
The default module configuration for the certain adapter is displayed in the channel configuration
Modules are EJBlsquos
Sequence matters
Module Processor Concept
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 49
Adapter Module Chain
Custom modulescan be added to default modulechains
Additional configurationparameters canbe specified eachmodule
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 50
Module Processor Documentation
SAP Help Portal (httphelpsapcom)SAP XI Runtime Connectivity Adapters Module ProcessorFeedback Mail to xidocumentationsapcom
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 51
Development Environment
Adapter development deployment and testing is possible on a single machine no full-blown PI XI is required
For testing purposes integration scenarioscan be configured in SAP PCK(eg loopback scenario)
Installation of SAP PCK already contains a sample adapter (including Adapter Meta Data) that should serve as a starting point
SAP Partner ConnectivityKit
Adapter FWMessagingQueuing
Security Handling
Resource
Adapter
PCK Configurationand Monitoring
FileDBJMSMarketplace
3rd Party Sys
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 52
Adapter Development Documentation
SAP Help Portal (httphelpsapcom)SAP XI Runtime Connectivity Partner Connectivity Kit Adapter DevelopmentFeedback Mail to xidocumentationsapcom
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 53
Requirements for Adapters (1)
Num AF Interface Category Description
1 JCA 10 conformance Mandatory Adapter must fulfill JCA 10 requirements (e g deployment) plus optional JCA 15 parts which are used by PI XI
2 AF Message Exchange Mandatory Adapter must be able to receive messages from AF and forward them to connected system and vice versa
3 AF Adapter Specific Modules
Optional SAP XI message and protocol conversion may be done entirely by the adapter or as adapter specific module and being called in the AF module chain context
4 Configuration Services Mandatory Unique configuration approach to manage adapters
5 Administrational Services
Optional Administration and Monitoring
6 Utility Service Mandatory Access to basic J2EE resources e g transactions and multithreading must be under control of J2EE server
7 Logging API Optional Adapters may use their own logging
8 Message Metadata Exchange
Optional Provide structure definition of message payloadIf not supported the definition of message types can be done in the Integration Repository
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 54
Requirements for Adapters (2)
Cluster-enabledConsider side-effects of clustering e g bdquoExactlyOnceInOrderldquo Avoid passing maneuvers
SpecializationBuild connection to exactly one type of business system or industrystandard protocol
DirectnessBuild connection to business system or industry standard protocoldirectly without any intermediate software components
SmoothnessLight-weighted low footprint adapter unnecessary system changes(many new or changed system DLL) should be avoided
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 55
Sample Adapter Source Code
Beside the API documentation a working sample adapter is shipped
The source code is available after installation
Analyzing the code helps understanding the Adapter Framework
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 56
Adapter Metadata
Adapter Metadata (AMD)XML file defines all configuration parameterseach adapter
AMD can be uploaded intoIntegration Iepositoryand SAP PCK
Configurationparameters are renderedinto the graphicalconfiguaration frontend
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 57
Adapter Metadata Fragment I
ltAdapterTypeMetaData version=09gt
ltTypegtNAESBltTypegt
ltInboundgt
ltTransportProtocolgt
ltChannelAttributesgt
ltAttributeGroupgt
ltNamegtCRYPTConfigurationltNamegt
ltGuiLabelsgtltLabel language=ENgtCryptographic ConfigurationltLabelgtltGuiLabelsgt
ltAttributeReferencegtltReferenceNamegtCRYPTUseSigningltReferenceNamegt
ltInboundgt
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 58
Adapter Metadata Fragment II
ltAttributegt
ltNamegtCRYPTUseSigningltNamegt
ltDataTypegtxsdbooleanltDataTypegt
ltGuiLabelsgt
ltLabel language=ENgtUse SigningltLabelgt
ltLabel language=DEgtVerwendung von SignierungltLabelgt
ltGuiLabelsgt
ltAttributegt
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 59
Adapter Configuration
Configuration attribute of type boolean is rendered to a check-box
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 60
Adapter Metadata Upload (PCK)
Integration Repositorydoes not exist in case ofSAP PCK installations
The upload mechanismfor Adaper Meta Datafor SAP PCK installationsrequires additonalparameters
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 61
AF CPA Cache
The Adapter configuration is deployed from the configuration time(SAP PCK or Integration Directory) to the J2EE service CPACache(Collaboration Profile Agreement)
The Adapter configuration can be accessed at runtime from withinadapter modules or JCA resource adapters via the CPACache API
The two main use cases are implemented inLookupManager to retrieve adapter configuation andNormalizationManager to retrieve Party information
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 62
Packaging Adapter Components
SAP recommends to use SAP Software Deployment Manager (SDM) for deployment
Software Delivery Archives (SDA) can contain software components of different types (eg applications libraries)
Detailed version information and dependencies to other components simplify program management
Adapter Modules and Development
Summary
Adapter Framework Overview
Adapter Strategy
Agenda
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 64
Summary
Adapter Framework runs on J2EE Stack of SAP Web AS
Adapter Framework is platform for Adapter Engine and SAP PCK
Adapter Framework provides an extensible platform for developing and running adapters
Adapter Engine utilizes central configuration monitoring administration
Dual connectivity strategyAdapter Framework for comprehensive integration of adaptersInteroperability via open standards to interop with EAI providers
SAP NetWeaver Certification for adapters based on Adapter Framework available
Adapter mappings metadata stored in Integration Repository
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 12
Partner Eco System
SAP relies on a system of partners to provide connectivity solutions for other applications and certain industry standards
Connectivity Reseller Agreements withSeeburger AGiWay SoftwareInformatica
3rd-Party solutions are sold and delivered through SAP
Technical support for partner solutions via theSAP Support Portal 24x7
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 13
PI Adapters by Seeburger (1)
Technical EDI AdaptersAS2 (EDIINTHTTP(S))Protocol AS2OFTPProtocol OFTPISDN OFTPTCPIPVAN AccessProtocol P7 X400 VAN FTP
Business EDI AdaptersGeneric EDIProtocol OFTPISDN or P7 X400 VAN FTPEDI Converter ANSI X12 EDIFACTMapping Templates Purchase order Order confirmation
Dispatch advice Invoice
Payment (Financial Service Providers)Protocol OFTPISDN P7 X400 VAN FTPEDI Converter EDIFACT SWIFTMapping Templates Payment orders Debit advice
Credit advice Account Statement
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 14
PI Adapters by Seeburger (2)
Industry Specific EDI AdaptersAerospace and Defense AutomotiveChemicals Consumer ProductsHigh-Tech PaperPharmaceutical Retail
Communication ProtocolsOFTPISDN P7 X400 VAN FTP
EDI Converter (EDI lt-gt XML)AECMASPEC 2000 ANSI X12 CHEM eStandards EDIFACT GALIAODETTE TRADACOM VDA
Mapping Templates within Integration RepositoryDelivery forecast Dispatch advise Invoice Purchase order Order confirmation
Message Library for Integration RepositoryHuge message catalog with EDI XML schema definitions
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 15
PI Adapters by iWay Software
Application AdaptersAriba BaanBroadvision ClarifyJD Edwards One World XE JD Edwards Worldi2 LawsonManugistics Microsoft CRMOracle Applications PeoplesoftQAD MFG Pro SiebelVantive
Industry Standard AdaptersSwift TransoraUCCnet
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 16
PI Adapters by iWay Software
Technical AdaptersAS1 (EDIINTSMTP) AS2 (EDIINTHTTP(S))BEA WLI COM+DCOMCorba Lotus NotesTibco Rendezvous
Mainframetransaction AdaptersCICS TMSIMSTelnet (3270) Telnet (5250) Tuxedo
Optionally further adapters can be added from a list of 160 iWayadapters e g HL7 (already certified) DB2 AS3 ebXML
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 17
SAP Conversion Agent by Informatica
Bi-directional conversion of unstructured and semi structured data from to XMLTransformation on message payloadProtocol support via SAPrsquos technical adapter (PI XI adapter framework)Transformations integrated via PI XI AF module
SAP J2EEPI XI Adapter Framework
Adapter
Adapter
Text2XML
XML2Excel
PDF2XML
ConversionAgent Studio
ConversionAgent Services
Conversion Agent Engine
CA AF Module
Conversion Agent J2EE Lib
Seamlessly integrated into Process Integration
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 18
Supported Data Formats by Informatica (partial list)
UNSTRUCTUREDMicrosoft WordMicrosoft ExcelPowerPointPDFStar OfficeWord PerfectASCII reportsHTMLEBCDICUndocumented binariesFlat filesRPGANSI
PRINT STREAMSAFPPost ScriptDJDE
SEMI-STRUCTURED HL7HIPAAASTMANSIndashX12EDIFACTCOBOLFIXCargo IMPMVRSWIFT
OTHER STANDARDSLegalXMLIFX cXMLebXML HL7 V30 ACORD (AL3 XML)
hellip using SAP technical adapter and Conversion Agent
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 19
Conversion Agent
Bi-directional conversion of unstructured and semi structured formats fromto XMLLinked through PI XI adapter framework module based on SAPrsquos technical adapter ndash no transport protocol manipulates payload informationSAP NetWeaver-wide use (via J2EE library)
3rd Party Adapters
Bi-directional conversion of one dedicated data format (eg SWIFT ANSI-X12 hellip) fromto XMLRuns within PI XI adapter framework - support payload transformation and transport protocol
Per adapter dedicated use within one SAP NetWeaver component
Conversion Agent vs 3rd Party Adapters
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 20
More Info about Connectivity Capabilities
httpservicesapcomxi xi in detail connectivity
Connectivity and Interoperability
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 21
Adapter Download from SAP Service Marketplace
SAP Service Marketplace httpservicesapcomswdc Download Installations and Upgrades Entry by Application Group Adapters
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 22
Certification Programs for Process Integration
httpwwwsdnsapcom Partners and ISVsIntegration and Certification Exchange Infrastructure
PI Based Certification Programs
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 23
Public info about certified PI adapters
httpwwwsapcompartnersdirectoriesSearchSolutionepxThird Party Defined Integration Scenarios NW-XI-AF 30
Certified PI Adapters
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 24
Adapter Configuration
Adapter independent parameters
Adapter specific parameters
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 25
Configurationcache
Adapter Engine
ISRuntime
AdapterSender
AdapterReceiver
Adapter Engine in SAP J2EE
Q
Administration
Security
Monitoring
Adapter-Specific
ComponentServices
TracingLogging
Module ProcessorEIS
Channel
acuteMessaging
Configcache
End-to-End MonitoringMessage flow over all components applications
Runtime Workbenchbull Uis for adminstration
monitoring
Integration Builder Directory
Receiver determinationbull Party-gtService-gtAction
Channel Definitionbull Adapter Enginebull Adapter Typebull Message Protocolbull Transport Protocolbull Securitybull Channel Configuration
(Sender Receiver Agreementbull PartyServiceAction lt-gt Channel
ConfigurationMaster
System Landscape Directorybull Holds component description
including address data
AdapterFramework
Integration Repositorybull Holds Adapter metadataIntegration Repositorybull Holds Adapter metadata
httpltIntegrationServerURLgt
Message
httpltAdapterEngineURLgt
OK Error
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 26
Transport Level Security
Transport Protocol Authentication
IDoc RFC and SNC Client Authentication
Client Authentication
Client Authentication
Client Authentication
Client Authentication
CRAM-MD5
Client Authentication
Client Authentication
Client Authentication
CDIX ndash Adapter HTTPs Client Authentication
RFC RFC and SNC
Plain HTTP HTTPs
FileFTP File Transfer Protocol using SSLTLS
SOAP HTTPsSMTPs (Receiver only)
Mail SMTPs POP3 IMAP4
Marketplace HTTPs
RNIF 20 ndash Adapter HTTPs
RNIF 11 ndash Adapter HTTPs
Supported by
Levels of Security
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 27
Message Level Security
Signature Non-Repudiation
of origin
Non-Repudiation of
receipt
Encryption
CDIX ndash Adapter PKCS7
Technology
XI protocol WS-Security
SOAP-Adapter WS-Security
SMIME
Mail-Adapter SMIME
RNIF 20 ndash Adapter SMIME
RNIF 11 ndash Adapter PKCS7
Supported by
Levels of Security
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 28
Access control list
Restrict access to the runtime environmentfor sender services of type Business Service or Business Systemfor interfaces of these sender services
Restrict access to particular (service) users
Check authorization at runtime
Configure access control in the Integration DirectorySender service Specify authorized users in the configuration of the corresponding (sender) serviceInterface Specify authorized users in the configuration of the relevant sender agreement which contains the interface in the object key
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 29
Dynamic Adapter Configuration
Enable adapters to read write dynamic message headers
Sender Adapter (constructing messages)Attach adapter specific information to message headerExamples File name source file size JMS timestamp mail subjectRead access to these attributes in receiver channel interface determination (routing) mapping
Receiver Adapter (consuming messages)Read attributes to overwrite values of channel configurationExamples Directory Name JMS Priority Mail Sender SOAP target URLSet attributes in mapping orUse attributes from sender in receiver channel
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 30
Sender Adapter Configuration (1)
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 31
Sender Adapter Configuration (2)
Add the filename et al to the message
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 32
Receiver Determination
Determinefilename-dependent receiver
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 33
Receiver Adapter
Store the file withthe name set in the messageattribute
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 34
Monitoring Adapter Engine
After selecting a message bdquoDetailsldquo View
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 35
Monitoring Integration Server
After selecting a message bdquoDisplayldquo
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 36
Remark Future of SAP XI 20 Adapter Engine
SAP XI 20 Adapter Engine is available in SAP NW acute04 and SAP NW 2004s as bdquoPlain J2SE Adapter Engineldquo
Functional scope as in SAP XI 20Adopted to the SAP XI 30 message protocolMinor maintenance issues bug fixes
RecommendationUse where platform requirements or limitations (hardware operating system JVM support) demand it
SAP XI 20 Adapter Engine works with SAP NW acute04 and SAP NW 2004s landscapes too
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 37
Integration Server
PlainJ2SE
Adapter Engine
Partner ConnectivityKitOptional non-central
Adapter EngineCentral Adapter Engine
Process Integration ndash Architecture
Integration Repository Integration Directory System Landscape Directory
Business Process Engine
Integration Engine
Adapter FrameworkMessagingQueuing
Security Handling
Resource
Adapter
Resource
Adapter
Resource
Adapter
Adapter FWMessagingQueuing
Security Handling
Adapter FWMessagingQueuing
Security Handling
PCK Configurationand Monitoring
HTTP
IDoc
Adapter
Adapter
FileDBJMSMarketplace
3rd Party Sys
FileDB
JMSSOAP
SAP ampNon-SAPSystem
FileDBJMSMarketplace
3rd Party Sys
FileDBJMSMarketplace
3rd Party Sys
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 38
SAP Partner Connectivity Kit Overview
SAP 3rdParty Appl PI XI
Smaller Company Subsidiary
SAPPCK
SAPApplication
3rd PartyApplication
Large Business Partner Headquarter
Internet
Enablement of smaller companies subsidiaries to exchange XML documents with their business partnerrsquos headquarterrsquos PI XI
SAPPCK
Providing a platform for development of own JCA Resource Adapters
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 39
SAP PCK ndash Adapters
SAP Partner Connectivity Kit (PCK) is based on Adapter Framework
SAP PCKlsquos objective is to enable XML document exchangebetween PI XI and business partner not using PI XI
SAP PCK also provides an extensible platform for developing and running individual JCA Resource adapters
Communication between PI XI and SAP PCK is via SAP XI messaging protocol
SAP PCK Includes the following adapters FileFTP JDBC JMS SOAP RFC IDoc (once available for SAP PCK) Mail SAP BC
Optionally SAP PCK can host further adapters that are available from SAP or 3rd party adapter providers
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 40
SAP PCK ndash Configuration Mapping
SAP PCK is deployed on stand-alone SAP J2EE Engine (part of SAP Web AS) within business partnerrsquos landscape
Configuration administration monitoring done locally on SAP PCK itself without need for an Integration Directory
Configuration UI provides same bdquolook and feelldquo as configuration UI of Adapter Engine
SAP PCK supports the development of message mappings using an integrated graphical mapping editor
Any source XML structure can be mapped to any target XML structureStandard functions are provided to perform calculations Boolean comparisons text mappings and other transformationsOptionally the standard functions can be enhanced with user-defined functions in Java
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 41
SAP PCK ndash Configuration UI
ConfigurationUI to configure Party Service Communication Channel Sender and Receiver agreementsSample screenshot for configuration of communication channel with adapter type sbquoFile FTPlsquo
Adapter Modules and Development
Summary
Adapter Framework Overview
Adapter Strategy
Agenda
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 43
SAP Exchange Infrastructure - Openness
Integration of SAP and non-SAP applicationsAdapter Framework for comprehensive integration of adaptersAdapters are used for technical connectivityAdapter metadata mappings are stored in Integration Repository
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 44
Dual Strategy
Dual connectivity strategyAdapter Framework for comprehensive integration of adapters to provide technical connectivity including central configurationadministration monitoring of adaptersInteroperability based on open standards (SOAP JMS HTTP(S)) tointeroperate with EAI providers
Value propositionStandardized interfaces allow easy integration of adapters from different partnersMinimum knowledge of end-to-end process integration requiredComprehensive integration avoids redundant maintenance ensures consistency enhances transparancyOpenness to integrate non-SAP applications 3rd party systems etcReduced TCO
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 45
Certification
CertificationSAP NetWeaver Certification of 3rd party adapters based on the adapter framework
Value propositionQuality (stability HA aspects performance etc) of adapters is controlledCertification helps customers to find right solutionQuick and convenient search for a variety of certified products with the online partner and product directory (httpwwwsapcompartnersdirectoriesSearchSolutionepx)Faster implementation time and lower integration costs through the use of tested 3rd party integrationReduced TCO
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 46
Adapter Mappings Metadata in Integration Repository
Adapter mappings and adapter metadata are stored in the Integration Repository
Centralized Integration Repository contains all relevant information for collaborative and integrative processesAll content adheres to open standards Adapters provide technical connectivity
Value propositionUse largest content catalogReduce costs in integration projectsReduce maintenance costsReduced TCO
Adapter Modules and Development
Summary
Adapter Framework Overview
Adapter Strategy
Agenda
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 48
For every adapter it is possible to define generic modules in the module processor possibility to extend the functionality of the specific adapter
Equivalent to the dispatcher classes in the J2SE adapter engine migration and examples
The default module configuration for the certain adapter is displayed in the channel configuration
Modules are EJBlsquos
Sequence matters
Module Processor Concept
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 49
Adapter Module Chain
Custom modulescan be added to default modulechains
Additional configurationparameters canbe specified eachmodule
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 50
Module Processor Documentation
SAP Help Portal (httphelpsapcom)SAP XI Runtime Connectivity Adapters Module ProcessorFeedback Mail to xidocumentationsapcom
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 51
Development Environment
Adapter development deployment and testing is possible on a single machine no full-blown PI XI is required
For testing purposes integration scenarioscan be configured in SAP PCK(eg loopback scenario)
Installation of SAP PCK already contains a sample adapter (including Adapter Meta Data) that should serve as a starting point
SAP Partner ConnectivityKit
Adapter FWMessagingQueuing
Security Handling
Resource
Adapter
PCK Configurationand Monitoring
FileDBJMSMarketplace
3rd Party Sys
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 52
Adapter Development Documentation
SAP Help Portal (httphelpsapcom)SAP XI Runtime Connectivity Partner Connectivity Kit Adapter DevelopmentFeedback Mail to xidocumentationsapcom
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 53
Requirements for Adapters (1)
Num AF Interface Category Description
1 JCA 10 conformance Mandatory Adapter must fulfill JCA 10 requirements (e g deployment) plus optional JCA 15 parts which are used by PI XI
2 AF Message Exchange Mandatory Adapter must be able to receive messages from AF and forward them to connected system and vice versa
3 AF Adapter Specific Modules
Optional SAP XI message and protocol conversion may be done entirely by the adapter or as adapter specific module and being called in the AF module chain context
4 Configuration Services Mandatory Unique configuration approach to manage adapters
5 Administrational Services
Optional Administration and Monitoring
6 Utility Service Mandatory Access to basic J2EE resources e g transactions and multithreading must be under control of J2EE server
7 Logging API Optional Adapters may use their own logging
8 Message Metadata Exchange
Optional Provide structure definition of message payloadIf not supported the definition of message types can be done in the Integration Repository
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 54
Requirements for Adapters (2)
Cluster-enabledConsider side-effects of clustering e g bdquoExactlyOnceInOrderldquo Avoid passing maneuvers
SpecializationBuild connection to exactly one type of business system or industrystandard protocol
DirectnessBuild connection to business system or industry standard protocoldirectly without any intermediate software components
SmoothnessLight-weighted low footprint adapter unnecessary system changes(many new or changed system DLL) should be avoided
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 55
Sample Adapter Source Code
Beside the API documentation a working sample adapter is shipped
The source code is available after installation
Analyzing the code helps understanding the Adapter Framework
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 56
Adapter Metadata
Adapter Metadata (AMD)XML file defines all configuration parameterseach adapter
AMD can be uploaded intoIntegration Iepositoryand SAP PCK
Configurationparameters are renderedinto the graphicalconfiguaration frontend
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 57
Adapter Metadata Fragment I
ltAdapterTypeMetaData version=09gt
ltTypegtNAESBltTypegt
ltInboundgt
ltTransportProtocolgt
ltChannelAttributesgt
ltAttributeGroupgt
ltNamegtCRYPTConfigurationltNamegt
ltGuiLabelsgtltLabel language=ENgtCryptographic ConfigurationltLabelgtltGuiLabelsgt
ltAttributeReferencegtltReferenceNamegtCRYPTUseSigningltReferenceNamegt
ltInboundgt
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 58
Adapter Metadata Fragment II
ltAttributegt
ltNamegtCRYPTUseSigningltNamegt
ltDataTypegtxsdbooleanltDataTypegt
ltGuiLabelsgt
ltLabel language=ENgtUse SigningltLabelgt
ltLabel language=DEgtVerwendung von SignierungltLabelgt
ltGuiLabelsgt
ltAttributegt
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 59
Adapter Configuration
Configuration attribute of type boolean is rendered to a check-box
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 60
Adapter Metadata Upload (PCK)
Integration Repositorydoes not exist in case ofSAP PCK installations
The upload mechanismfor Adaper Meta Datafor SAP PCK installationsrequires additonalparameters
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 61
AF CPA Cache
The Adapter configuration is deployed from the configuration time(SAP PCK or Integration Directory) to the J2EE service CPACache(Collaboration Profile Agreement)
The Adapter configuration can be accessed at runtime from withinadapter modules or JCA resource adapters via the CPACache API
The two main use cases are implemented inLookupManager to retrieve adapter configuation andNormalizationManager to retrieve Party information
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 62
Packaging Adapter Components
SAP recommends to use SAP Software Deployment Manager (SDM) for deployment
Software Delivery Archives (SDA) can contain software components of different types (eg applications libraries)
Detailed version information and dependencies to other components simplify program management
Adapter Modules and Development
Summary
Adapter Framework Overview
Adapter Strategy
Agenda
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 64
Summary
Adapter Framework runs on J2EE Stack of SAP Web AS
Adapter Framework is platform for Adapter Engine and SAP PCK
Adapter Framework provides an extensible platform for developing and running adapters
Adapter Engine utilizes central configuration monitoring administration
Dual connectivity strategyAdapter Framework for comprehensive integration of adaptersInteroperability via open standards to interop with EAI providers
SAP NetWeaver Certification for adapters based on Adapter Framework available
Adapter mappings metadata stored in Integration Repository
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 13
PI Adapters by Seeburger (1)
Technical EDI AdaptersAS2 (EDIINTHTTP(S))Protocol AS2OFTPProtocol OFTPISDN OFTPTCPIPVAN AccessProtocol P7 X400 VAN FTP
Business EDI AdaptersGeneric EDIProtocol OFTPISDN or P7 X400 VAN FTPEDI Converter ANSI X12 EDIFACTMapping Templates Purchase order Order confirmation
Dispatch advice Invoice
Payment (Financial Service Providers)Protocol OFTPISDN P7 X400 VAN FTPEDI Converter EDIFACT SWIFTMapping Templates Payment orders Debit advice
Credit advice Account Statement
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 14
PI Adapters by Seeburger (2)
Industry Specific EDI AdaptersAerospace and Defense AutomotiveChemicals Consumer ProductsHigh-Tech PaperPharmaceutical Retail
Communication ProtocolsOFTPISDN P7 X400 VAN FTP
EDI Converter (EDI lt-gt XML)AECMASPEC 2000 ANSI X12 CHEM eStandards EDIFACT GALIAODETTE TRADACOM VDA
Mapping Templates within Integration RepositoryDelivery forecast Dispatch advise Invoice Purchase order Order confirmation
Message Library for Integration RepositoryHuge message catalog with EDI XML schema definitions
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 15
PI Adapters by iWay Software
Application AdaptersAriba BaanBroadvision ClarifyJD Edwards One World XE JD Edwards Worldi2 LawsonManugistics Microsoft CRMOracle Applications PeoplesoftQAD MFG Pro SiebelVantive
Industry Standard AdaptersSwift TransoraUCCnet
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 16
PI Adapters by iWay Software
Technical AdaptersAS1 (EDIINTSMTP) AS2 (EDIINTHTTP(S))BEA WLI COM+DCOMCorba Lotus NotesTibco Rendezvous
Mainframetransaction AdaptersCICS TMSIMSTelnet (3270) Telnet (5250) Tuxedo
Optionally further adapters can be added from a list of 160 iWayadapters e g HL7 (already certified) DB2 AS3 ebXML
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 17
SAP Conversion Agent by Informatica
Bi-directional conversion of unstructured and semi structured data from to XMLTransformation on message payloadProtocol support via SAPrsquos technical adapter (PI XI adapter framework)Transformations integrated via PI XI AF module
SAP J2EEPI XI Adapter Framework
Adapter
Adapter
Text2XML
XML2Excel
PDF2XML
ConversionAgent Studio
ConversionAgent Services
Conversion Agent Engine
CA AF Module
Conversion Agent J2EE Lib
Seamlessly integrated into Process Integration
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 18
Supported Data Formats by Informatica (partial list)
UNSTRUCTUREDMicrosoft WordMicrosoft ExcelPowerPointPDFStar OfficeWord PerfectASCII reportsHTMLEBCDICUndocumented binariesFlat filesRPGANSI
PRINT STREAMSAFPPost ScriptDJDE
SEMI-STRUCTURED HL7HIPAAASTMANSIndashX12EDIFACTCOBOLFIXCargo IMPMVRSWIFT
OTHER STANDARDSLegalXMLIFX cXMLebXML HL7 V30 ACORD (AL3 XML)
hellip using SAP technical adapter and Conversion Agent
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 19
Conversion Agent
Bi-directional conversion of unstructured and semi structured formats fromto XMLLinked through PI XI adapter framework module based on SAPrsquos technical adapter ndash no transport protocol manipulates payload informationSAP NetWeaver-wide use (via J2EE library)
3rd Party Adapters
Bi-directional conversion of one dedicated data format (eg SWIFT ANSI-X12 hellip) fromto XMLRuns within PI XI adapter framework - support payload transformation and transport protocol
Per adapter dedicated use within one SAP NetWeaver component
Conversion Agent vs 3rd Party Adapters
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 20
More Info about Connectivity Capabilities
httpservicesapcomxi xi in detail connectivity
Connectivity and Interoperability
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 21
Adapter Download from SAP Service Marketplace
SAP Service Marketplace httpservicesapcomswdc Download Installations and Upgrades Entry by Application Group Adapters
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 22
Certification Programs for Process Integration
httpwwwsdnsapcom Partners and ISVsIntegration and Certification Exchange Infrastructure
PI Based Certification Programs
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 23
Public info about certified PI adapters
httpwwwsapcompartnersdirectoriesSearchSolutionepxThird Party Defined Integration Scenarios NW-XI-AF 30
Certified PI Adapters
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 24
Adapter Configuration
Adapter independent parameters
Adapter specific parameters
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 25
Configurationcache
Adapter Engine
ISRuntime
AdapterSender
AdapterReceiver
Adapter Engine in SAP J2EE
Q
Administration
Security
Monitoring
Adapter-Specific
ComponentServices
TracingLogging
Module ProcessorEIS
Channel
acuteMessaging
Configcache
End-to-End MonitoringMessage flow over all components applications
Runtime Workbenchbull Uis for adminstration
monitoring
Integration Builder Directory
Receiver determinationbull Party-gtService-gtAction
Channel Definitionbull Adapter Enginebull Adapter Typebull Message Protocolbull Transport Protocolbull Securitybull Channel Configuration
(Sender Receiver Agreementbull PartyServiceAction lt-gt Channel
ConfigurationMaster
System Landscape Directorybull Holds component description
including address data
AdapterFramework
Integration Repositorybull Holds Adapter metadataIntegration Repositorybull Holds Adapter metadata
httpltIntegrationServerURLgt
Message
httpltAdapterEngineURLgt
OK Error
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 26
Transport Level Security
Transport Protocol Authentication
IDoc RFC and SNC Client Authentication
Client Authentication
Client Authentication
Client Authentication
Client Authentication
CRAM-MD5
Client Authentication
Client Authentication
Client Authentication
CDIX ndash Adapter HTTPs Client Authentication
RFC RFC and SNC
Plain HTTP HTTPs
FileFTP File Transfer Protocol using SSLTLS
SOAP HTTPsSMTPs (Receiver only)
Mail SMTPs POP3 IMAP4
Marketplace HTTPs
RNIF 20 ndash Adapter HTTPs
RNIF 11 ndash Adapter HTTPs
Supported by
Levels of Security
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 27
Message Level Security
Signature Non-Repudiation
of origin
Non-Repudiation of
receipt
Encryption
CDIX ndash Adapter PKCS7
Technology
XI protocol WS-Security
SOAP-Adapter WS-Security
SMIME
Mail-Adapter SMIME
RNIF 20 ndash Adapter SMIME
RNIF 11 ndash Adapter PKCS7
Supported by
Levels of Security
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 28
Access control list
Restrict access to the runtime environmentfor sender services of type Business Service or Business Systemfor interfaces of these sender services
Restrict access to particular (service) users
Check authorization at runtime
Configure access control in the Integration DirectorySender service Specify authorized users in the configuration of the corresponding (sender) serviceInterface Specify authorized users in the configuration of the relevant sender agreement which contains the interface in the object key
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 29
Dynamic Adapter Configuration
Enable adapters to read write dynamic message headers
Sender Adapter (constructing messages)Attach adapter specific information to message headerExamples File name source file size JMS timestamp mail subjectRead access to these attributes in receiver channel interface determination (routing) mapping
Receiver Adapter (consuming messages)Read attributes to overwrite values of channel configurationExamples Directory Name JMS Priority Mail Sender SOAP target URLSet attributes in mapping orUse attributes from sender in receiver channel
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 30
Sender Adapter Configuration (1)
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 31
Sender Adapter Configuration (2)
Add the filename et al to the message
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 32
Receiver Determination
Determinefilename-dependent receiver
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 33
Receiver Adapter
Store the file withthe name set in the messageattribute
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 34
Monitoring Adapter Engine
After selecting a message bdquoDetailsldquo View
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 35
Monitoring Integration Server
After selecting a message bdquoDisplayldquo
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 36
Remark Future of SAP XI 20 Adapter Engine
SAP XI 20 Adapter Engine is available in SAP NW acute04 and SAP NW 2004s as bdquoPlain J2SE Adapter Engineldquo
Functional scope as in SAP XI 20Adopted to the SAP XI 30 message protocolMinor maintenance issues bug fixes
RecommendationUse where platform requirements or limitations (hardware operating system JVM support) demand it
SAP XI 20 Adapter Engine works with SAP NW acute04 and SAP NW 2004s landscapes too
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 37
Integration Server
PlainJ2SE
Adapter Engine
Partner ConnectivityKitOptional non-central
Adapter EngineCentral Adapter Engine
Process Integration ndash Architecture
Integration Repository Integration Directory System Landscape Directory
Business Process Engine
Integration Engine
Adapter FrameworkMessagingQueuing
Security Handling
Resource
Adapter
Resource
Adapter
Resource
Adapter
Adapter FWMessagingQueuing
Security Handling
Adapter FWMessagingQueuing
Security Handling
PCK Configurationand Monitoring
HTTP
IDoc
Adapter
Adapter
FileDBJMSMarketplace
3rd Party Sys
FileDB
JMSSOAP
SAP ampNon-SAPSystem
FileDBJMSMarketplace
3rd Party Sys
FileDBJMSMarketplace
3rd Party Sys
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 38
SAP Partner Connectivity Kit Overview
SAP 3rdParty Appl PI XI
Smaller Company Subsidiary
SAPPCK
SAPApplication
3rd PartyApplication
Large Business Partner Headquarter
Internet
Enablement of smaller companies subsidiaries to exchange XML documents with their business partnerrsquos headquarterrsquos PI XI
SAPPCK
Providing a platform for development of own JCA Resource Adapters
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 39
SAP PCK ndash Adapters
SAP Partner Connectivity Kit (PCK) is based on Adapter Framework
SAP PCKlsquos objective is to enable XML document exchangebetween PI XI and business partner not using PI XI
SAP PCK also provides an extensible platform for developing and running individual JCA Resource adapters
Communication between PI XI and SAP PCK is via SAP XI messaging protocol
SAP PCK Includes the following adapters FileFTP JDBC JMS SOAP RFC IDoc (once available for SAP PCK) Mail SAP BC
Optionally SAP PCK can host further adapters that are available from SAP or 3rd party adapter providers
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 40
SAP PCK ndash Configuration Mapping
SAP PCK is deployed on stand-alone SAP J2EE Engine (part of SAP Web AS) within business partnerrsquos landscape
Configuration administration monitoring done locally on SAP PCK itself without need for an Integration Directory
Configuration UI provides same bdquolook and feelldquo as configuration UI of Adapter Engine
SAP PCK supports the development of message mappings using an integrated graphical mapping editor
Any source XML structure can be mapped to any target XML structureStandard functions are provided to perform calculations Boolean comparisons text mappings and other transformationsOptionally the standard functions can be enhanced with user-defined functions in Java
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 41
SAP PCK ndash Configuration UI
ConfigurationUI to configure Party Service Communication Channel Sender and Receiver agreementsSample screenshot for configuration of communication channel with adapter type sbquoFile FTPlsquo
Adapter Modules and Development
Summary
Adapter Framework Overview
Adapter Strategy
Agenda
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 43
SAP Exchange Infrastructure - Openness
Integration of SAP and non-SAP applicationsAdapter Framework for comprehensive integration of adaptersAdapters are used for technical connectivityAdapter metadata mappings are stored in Integration Repository
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 44
Dual Strategy
Dual connectivity strategyAdapter Framework for comprehensive integration of adapters to provide technical connectivity including central configurationadministration monitoring of adaptersInteroperability based on open standards (SOAP JMS HTTP(S)) tointeroperate with EAI providers
Value propositionStandardized interfaces allow easy integration of adapters from different partnersMinimum knowledge of end-to-end process integration requiredComprehensive integration avoids redundant maintenance ensures consistency enhances transparancyOpenness to integrate non-SAP applications 3rd party systems etcReduced TCO
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 45
Certification
CertificationSAP NetWeaver Certification of 3rd party adapters based on the adapter framework
Value propositionQuality (stability HA aspects performance etc) of adapters is controlledCertification helps customers to find right solutionQuick and convenient search for a variety of certified products with the online partner and product directory (httpwwwsapcompartnersdirectoriesSearchSolutionepx)Faster implementation time and lower integration costs through the use of tested 3rd party integrationReduced TCO
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 46
Adapter Mappings Metadata in Integration Repository
Adapter mappings and adapter metadata are stored in the Integration Repository
Centralized Integration Repository contains all relevant information for collaborative and integrative processesAll content adheres to open standards Adapters provide technical connectivity
Value propositionUse largest content catalogReduce costs in integration projectsReduce maintenance costsReduced TCO
Adapter Modules and Development
Summary
Adapter Framework Overview
Adapter Strategy
Agenda
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 48
For every adapter it is possible to define generic modules in the module processor possibility to extend the functionality of the specific adapter
Equivalent to the dispatcher classes in the J2SE adapter engine migration and examples
The default module configuration for the certain adapter is displayed in the channel configuration
Modules are EJBlsquos
Sequence matters
Module Processor Concept
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 49
Adapter Module Chain
Custom modulescan be added to default modulechains
Additional configurationparameters canbe specified eachmodule
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 50
Module Processor Documentation
SAP Help Portal (httphelpsapcom)SAP XI Runtime Connectivity Adapters Module ProcessorFeedback Mail to xidocumentationsapcom
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 51
Development Environment
Adapter development deployment and testing is possible on a single machine no full-blown PI XI is required
For testing purposes integration scenarioscan be configured in SAP PCK(eg loopback scenario)
Installation of SAP PCK already contains a sample adapter (including Adapter Meta Data) that should serve as a starting point
SAP Partner ConnectivityKit
Adapter FWMessagingQueuing
Security Handling
Resource
Adapter
PCK Configurationand Monitoring
FileDBJMSMarketplace
3rd Party Sys
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 52
Adapter Development Documentation
SAP Help Portal (httphelpsapcom)SAP XI Runtime Connectivity Partner Connectivity Kit Adapter DevelopmentFeedback Mail to xidocumentationsapcom
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 53
Requirements for Adapters (1)
Num AF Interface Category Description
1 JCA 10 conformance Mandatory Adapter must fulfill JCA 10 requirements (e g deployment) plus optional JCA 15 parts which are used by PI XI
2 AF Message Exchange Mandatory Adapter must be able to receive messages from AF and forward them to connected system and vice versa
3 AF Adapter Specific Modules
Optional SAP XI message and protocol conversion may be done entirely by the adapter or as adapter specific module and being called in the AF module chain context
4 Configuration Services Mandatory Unique configuration approach to manage adapters
5 Administrational Services
Optional Administration and Monitoring
6 Utility Service Mandatory Access to basic J2EE resources e g transactions and multithreading must be under control of J2EE server
7 Logging API Optional Adapters may use their own logging
8 Message Metadata Exchange
Optional Provide structure definition of message payloadIf not supported the definition of message types can be done in the Integration Repository
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 54
Requirements for Adapters (2)
Cluster-enabledConsider side-effects of clustering e g bdquoExactlyOnceInOrderldquo Avoid passing maneuvers
SpecializationBuild connection to exactly one type of business system or industrystandard protocol
DirectnessBuild connection to business system or industry standard protocoldirectly without any intermediate software components
SmoothnessLight-weighted low footprint adapter unnecessary system changes(many new or changed system DLL) should be avoided
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 55
Sample Adapter Source Code
Beside the API documentation a working sample adapter is shipped
The source code is available after installation
Analyzing the code helps understanding the Adapter Framework
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 56
Adapter Metadata
Adapter Metadata (AMD)XML file defines all configuration parameterseach adapter
AMD can be uploaded intoIntegration Iepositoryand SAP PCK
Configurationparameters are renderedinto the graphicalconfiguaration frontend
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 57
Adapter Metadata Fragment I
ltAdapterTypeMetaData version=09gt
ltTypegtNAESBltTypegt
ltInboundgt
ltTransportProtocolgt
ltChannelAttributesgt
ltAttributeGroupgt
ltNamegtCRYPTConfigurationltNamegt
ltGuiLabelsgtltLabel language=ENgtCryptographic ConfigurationltLabelgtltGuiLabelsgt
ltAttributeReferencegtltReferenceNamegtCRYPTUseSigningltReferenceNamegt
ltInboundgt
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 58
Adapter Metadata Fragment II
ltAttributegt
ltNamegtCRYPTUseSigningltNamegt
ltDataTypegtxsdbooleanltDataTypegt
ltGuiLabelsgt
ltLabel language=ENgtUse SigningltLabelgt
ltLabel language=DEgtVerwendung von SignierungltLabelgt
ltGuiLabelsgt
ltAttributegt
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 59
Adapter Configuration
Configuration attribute of type boolean is rendered to a check-box
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 60
Adapter Metadata Upload (PCK)
Integration Repositorydoes not exist in case ofSAP PCK installations
The upload mechanismfor Adaper Meta Datafor SAP PCK installationsrequires additonalparameters
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 61
AF CPA Cache
The Adapter configuration is deployed from the configuration time(SAP PCK or Integration Directory) to the J2EE service CPACache(Collaboration Profile Agreement)
The Adapter configuration can be accessed at runtime from withinadapter modules or JCA resource adapters via the CPACache API
The two main use cases are implemented inLookupManager to retrieve adapter configuation andNormalizationManager to retrieve Party information
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 62
Packaging Adapter Components
SAP recommends to use SAP Software Deployment Manager (SDM) for deployment
Software Delivery Archives (SDA) can contain software components of different types (eg applications libraries)
Detailed version information and dependencies to other components simplify program management
Adapter Modules and Development
Summary
Adapter Framework Overview
Adapter Strategy
Agenda
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 64
Summary
Adapter Framework runs on J2EE Stack of SAP Web AS
Adapter Framework is platform for Adapter Engine and SAP PCK
Adapter Framework provides an extensible platform for developing and running adapters
Adapter Engine utilizes central configuration monitoring administration
Dual connectivity strategyAdapter Framework for comprehensive integration of adaptersInteroperability via open standards to interop with EAI providers
SAP NetWeaver Certification for adapters based on Adapter Framework available
Adapter mappings metadata stored in Integration Repository
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 14
PI Adapters by Seeburger (2)
Industry Specific EDI AdaptersAerospace and Defense AutomotiveChemicals Consumer ProductsHigh-Tech PaperPharmaceutical Retail
Communication ProtocolsOFTPISDN P7 X400 VAN FTP
EDI Converter (EDI lt-gt XML)AECMASPEC 2000 ANSI X12 CHEM eStandards EDIFACT GALIAODETTE TRADACOM VDA
Mapping Templates within Integration RepositoryDelivery forecast Dispatch advise Invoice Purchase order Order confirmation
Message Library for Integration RepositoryHuge message catalog with EDI XML schema definitions
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 15
PI Adapters by iWay Software
Application AdaptersAriba BaanBroadvision ClarifyJD Edwards One World XE JD Edwards Worldi2 LawsonManugistics Microsoft CRMOracle Applications PeoplesoftQAD MFG Pro SiebelVantive
Industry Standard AdaptersSwift TransoraUCCnet
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 16
PI Adapters by iWay Software
Technical AdaptersAS1 (EDIINTSMTP) AS2 (EDIINTHTTP(S))BEA WLI COM+DCOMCorba Lotus NotesTibco Rendezvous
Mainframetransaction AdaptersCICS TMSIMSTelnet (3270) Telnet (5250) Tuxedo
Optionally further adapters can be added from a list of 160 iWayadapters e g HL7 (already certified) DB2 AS3 ebXML
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 17
SAP Conversion Agent by Informatica
Bi-directional conversion of unstructured and semi structured data from to XMLTransformation on message payloadProtocol support via SAPrsquos technical adapter (PI XI adapter framework)Transformations integrated via PI XI AF module
SAP J2EEPI XI Adapter Framework
Adapter
Adapter
Text2XML
XML2Excel
PDF2XML
ConversionAgent Studio
ConversionAgent Services
Conversion Agent Engine
CA AF Module
Conversion Agent J2EE Lib
Seamlessly integrated into Process Integration
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 18
Supported Data Formats by Informatica (partial list)
UNSTRUCTUREDMicrosoft WordMicrosoft ExcelPowerPointPDFStar OfficeWord PerfectASCII reportsHTMLEBCDICUndocumented binariesFlat filesRPGANSI
PRINT STREAMSAFPPost ScriptDJDE
SEMI-STRUCTURED HL7HIPAAASTMANSIndashX12EDIFACTCOBOLFIXCargo IMPMVRSWIFT
OTHER STANDARDSLegalXMLIFX cXMLebXML HL7 V30 ACORD (AL3 XML)
hellip using SAP technical adapter and Conversion Agent
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 19
Conversion Agent
Bi-directional conversion of unstructured and semi structured formats fromto XMLLinked through PI XI adapter framework module based on SAPrsquos technical adapter ndash no transport protocol manipulates payload informationSAP NetWeaver-wide use (via J2EE library)
3rd Party Adapters
Bi-directional conversion of one dedicated data format (eg SWIFT ANSI-X12 hellip) fromto XMLRuns within PI XI adapter framework - support payload transformation and transport protocol
Per adapter dedicated use within one SAP NetWeaver component
Conversion Agent vs 3rd Party Adapters
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 20
More Info about Connectivity Capabilities
httpservicesapcomxi xi in detail connectivity
Connectivity and Interoperability
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 21
Adapter Download from SAP Service Marketplace
SAP Service Marketplace httpservicesapcomswdc Download Installations and Upgrades Entry by Application Group Adapters
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 22
Certification Programs for Process Integration
httpwwwsdnsapcom Partners and ISVsIntegration and Certification Exchange Infrastructure
PI Based Certification Programs
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 23
Public info about certified PI adapters
httpwwwsapcompartnersdirectoriesSearchSolutionepxThird Party Defined Integration Scenarios NW-XI-AF 30
Certified PI Adapters
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 24
Adapter Configuration
Adapter independent parameters
Adapter specific parameters
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 25
Configurationcache
Adapter Engine
ISRuntime
AdapterSender
AdapterReceiver
Adapter Engine in SAP J2EE
Q
Administration
Security
Monitoring
Adapter-Specific
ComponentServices
TracingLogging
Module ProcessorEIS
Channel
acuteMessaging
Configcache
End-to-End MonitoringMessage flow over all components applications
Runtime Workbenchbull Uis for adminstration
monitoring
Integration Builder Directory
Receiver determinationbull Party-gtService-gtAction
Channel Definitionbull Adapter Enginebull Adapter Typebull Message Protocolbull Transport Protocolbull Securitybull Channel Configuration
(Sender Receiver Agreementbull PartyServiceAction lt-gt Channel
ConfigurationMaster
System Landscape Directorybull Holds component description
including address data
AdapterFramework
Integration Repositorybull Holds Adapter metadataIntegration Repositorybull Holds Adapter metadata
httpltIntegrationServerURLgt
Message
httpltAdapterEngineURLgt
OK Error
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 26
Transport Level Security
Transport Protocol Authentication
IDoc RFC and SNC Client Authentication
Client Authentication
Client Authentication
Client Authentication
Client Authentication
CRAM-MD5
Client Authentication
Client Authentication
Client Authentication
CDIX ndash Adapter HTTPs Client Authentication
RFC RFC and SNC
Plain HTTP HTTPs
FileFTP File Transfer Protocol using SSLTLS
SOAP HTTPsSMTPs (Receiver only)
Mail SMTPs POP3 IMAP4
Marketplace HTTPs
RNIF 20 ndash Adapter HTTPs
RNIF 11 ndash Adapter HTTPs
Supported by
Levels of Security
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 27
Message Level Security
Signature Non-Repudiation
of origin
Non-Repudiation of
receipt
Encryption
CDIX ndash Adapter PKCS7
Technology
XI protocol WS-Security
SOAP-Adapter WS-Security
SMIME
Mail-Adapter SMIME
RNIF 20 ndash Adapter SMIME
RNIF 11 ndash Adapter PKCS7
Supported by
Levels of Security
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 28
Access control list
Restrict access to the runtime environmentfor sender services of type Business Service or Business Systemfor interfaces of these sender services
Restrict access to particular (service) users
Check authorization at runtime
Configure access control in the Integration DirectorySender service Specify authorized users in the configuration of the corresponding (sender) serviceInterface Specify authorized users in the configuration of the relevant sender agreement which contains the interface in the object key
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 29
Dynamic Adapter Configuration
Enable adapters to read write dynamic message headers
Sender Adapter (constructing messages)Attach adapter specific information to message headerExamples File name source file size JMS timestamp mail subjectRead access to these attributes in receiver channel interface determination (routing) mapping
Receiver Adapter (consuming messages)Read attributes to overwrite values of channel configurationExamples Directory Name JMS Priority Mail Sender SOAP target URLSet attributes in mapping orUse attributes from sender in receiver channel
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 30
Sender Adapter Configuration (1)
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 31
Sender Adapter Configuration (2)
Add the filename et al to the message
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 32
Receiver Determination
Determinefilename-dependent receiver
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 33
Receiver Adapter
Store the file withthe name set in the messageattribute
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 34
Monitoring Adapter Engine
After selecting a message bdquoDetailsldquo View
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 35
Monitoring Integration Server
After selecting a message bdquoDisplayldquo
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 36
Remark Future of SAP XI 20 Adapter Engine
SAP XI 20 Adapter Engine is available in SAP NW acute04 and SAP NW 2004s as bdquoPlain J2SE Adapter Engineldquo
Functional scope as in SAP XI 20Adopted to the SAP XI 30 message protocolMinor maintenance issues bug fixes
RecommendationUse where platform requirements or limitations (hardware operating system JVM support) demand it
SAP XI 20 Adapter Engine works with SAP NW acute04 and SAP NW 2004s landscapes too
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 37
Integration Server
PlainJ2SE
Adapter Engine
Partner ConnectivityKitOptional non-central
Adapter EngineCentral Adapter Engine
Process Integration ndash Architecture
Integration Repository Integration Directory System Landscape Directory
Business Process Engine
Integration Engine
Adapter FrameworkMessagingQueuing
Security Handling
Resource
Adapter
Resource
Adapter
Resource
Adapter
Adapter FWMessagingQueuing
Security Handling
Adapter FWMessagingQueuing
Security Handling
PCK Configurationand Monitoring
HTTP
IDoc
Adapter
Adapter
FileDBJMSMarketplace
3rd Party Sys
FileDB
JMSSOAP
SAP ampNon-SAPSystem
FileDBJMSMarketplace
3rd Party Sys
FileDBJMSMarketplace
3rd Party Sys
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 38
SAP Partner Connectivity Kit Overview
SAP 3rdParty Appl PI XI
Smaller Company Subsidiary
SAPPCK
SAPApplication
3rd PartyApplication
Large Business Partner Headquarter
Internet
Enablement of smaller companies subsidiaries to exchange XML documents with their business partnerrsquos headquarterrsquos PI XI
SAPPCK
Providing a platform for development of own JCA Resource Adapters
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 39
SAP PCK ndash Adapters
SAP Partner Connectivity Kit (PCK) is based on Adapter Framework
SAP PCKlsquos objective is to enable XML document exchangebetween PI XI and business partner not using PI XI
SAP PCK also provides an extensible platform for developing and running individual JCA Resource adapters
Communication between PI XI and SAP PCK is via SAP XI messaging protocol
SAP PCK Includes the following adapters FileFTP JDBC JMS SOAP RFC IDoc (once available for SAP PCK) Mail SAP BC
Optionally SAP PCK can host further adapters that are available from SAP or 3rd party adapter providers
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 40
SAP PCK ndash Configuration Mapping
SAP PCK is deployed on stand-alone SAP J2EE Engine (part of SAP Web AS) within business partnerrsquos landscape
Configuration administration monitoring done locally on SAP PCK itself without need for an Integration Directory
Configuration UI provides same bdquolook and feelldquo as configuration UI of Adapter Engine
SAP PCK supports the development of message mappings using an integrated graphical mapping editor
Any source XML structure can be mapped to any target XML structureStandard functions are provided to perform calculations Boolean comparisons text mappings and other transformationsOptionally the standard functions can be enhanced with user-defined functions in Java
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 41
SAP PCK ndash Configuration UI
ConfigurationUI to configure Party Service Communication Channel Sender and Receiver agreementsSample screenshot for configuration of communication channel with adapter type sbquoFile FTPlsquo
Adapter Modules and Development
Summary
Adapter Framework Overview
Adapter Strategy
Agenda
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 43
SAP Exchange Infrastructure - Openness
Integration of SAP and non-SAP applicationsAdapter Framework for comprehensive integration of adaptersAdapters are used for technical connectivityAdapter metadata mappings are stored in Integration Repository
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 44
Dual Strategy
Dual connectivity strategyAdapter Framework for comprehensive integration of adapters to provide technical connectivity including central configurationadministration monitoring of adaptersInteroperability based on open standards (SOAP JMS HTTP(S)) tointeroperate with EAI providers
Value propositionStandardized interfaces allow easy integration of adapters from different partnersMinimum knowledge of end-to-end process integration requiredComprehensive integration avoids redundant maintenance ensures consistency enhances transparancyOpenness to integrate non-SAP applications 3rd party systems etcReduced TCO
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 45
Certification
CertificationSAP NetWeaver Certification of 3rd party adapters based on the adapter framework
Value propositionQuality (stability HA aspects performance etc) of adapters is controlledCertification helps customers to find right solutionQuick and convenient search for a variety of certified products with the online partner and product directory (httpwwwsapcompartnersdirectoriesSearchSolutionepx)Faster implementation time and lower integration costs through the use of tested 3rd party integrationReduced TCO
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 46
Adapter Mappings Metadata in Integration Repository
Adapter mappings and adapter metadata are stored in the Integration Repository
Centralized Integration Repository contains all relevant information for collaborative and integrative processesAll content adheres to open standards Adapters provide technical connectivity
Value propositionUse largest content catalogReduce costs in integration projectsReduce maintenance costsReduced TCO
Adapter Modules and Development
Summary
Adapter Framework Overview
Adapter Strategy
Agenda
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 48
For every adapter it is possible to define generic modules in the module processor possibility to extend the functionality of the specific adapter
Equivalent to the dispatcher classes in the J2SE adapter engine migration and examples
The default module configuration for the certain adapter is displayed in the channel configuration
Modules are EJBlsquos
Sequence matters
Module Processor Concept
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 49
Adapter Module Chain
Custom modulescan be added to default modulechains
Additional configurationparameters canbe specified eachmodule
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 50
Module Processor Documentation
SAP Help Portal (httphelpsapcom)SAP XI Runtime Connectivity Adapters Module ProcessorFeedback Mail to xidocumentationsapcom
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 51
Development Environment
Adapter development deployment and testing is possible on a single machine no full-blown PI XI is required
For testing purposes integration scenarioscan be configured in SAP PCK(eg loopback scenario)
Installation of SAP PCK already contains a sample adapter (including Adapter Meta Data) that should serve as a starting point
SAP Partner ConnectivityKit
Adapter FWMessagingQueuing
Security Handling
Resource
Adapter
PCK Configurationand Monitoring
FileDBJMSMarketplace
3rd Party Sys
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 52
Adapter Development Documentation
SAP Help Portal (httphelpsapcom)SAP XI Runtime Connectivity Partner Connectivity Kit Adapter DevelopmentFeedback Mail to xidocumentationsapcom
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 53
Requirements for Adapters (1)
Num AF Interface Category Description
1 JCA 10 conformance Mandatory Adapter must fulfill JCA 10 requirements (e g deployment) plus optional JCA 15 parts which are used by PI XI
2 AF Message Exchange Mandatory Adapter must be able to receive messages from AF and forward them to connected system and vice versa
3 AF Adapter Specific Modules
Optional SAP XI message and protocol conversion may be done entirely by the adapter or as adapter specific module and being called in the AF module chain context
4 Configuration Services Mandatory Unique configuration approach to manage adapters
5 Administrational Services
Optional Administration and Monitoring
6 Utility Service Mandatory Access to basic J2EE resources e g transactions and multithreading must be under control of J2EE server
7 Logging API Optional Adapters may use their own logging
8 Message Metadata Exchange
Optional Provide structure definition of message payloadIf not supported the definition of message types can be done in the Integration Repository
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 54
Requirements for Adapters (2)
Cluster-enabledConsider side-effects of clustering e g bdquoExactlyOnceInOrderldquo Avoid passing maneuvers
SpecializationBuild connection to exactly one type of business system or industrystandard protocol
DirectnessBuild connection to business system or industry standard protocoldirectly without any intermediate software components
SmoothnessLight-weighted low footprint adapter unnecessary system changes(many new or changed system DLL) should be avoided
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 55
Sample Adapter Source Code
Beside the API documentation a working sample adapter is shipped
The source code is available after installation
Analyzing the code helps understanding the Adapter Framework
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 56
Adapter Metadata
Adapter Metadata (AMD)XML file defines all configuration parameterseach adapter
AMD can be uploaded intoIntegration Iepositoryand SAP PCK
Configurationparameters are renderedinto the graphicalconfiguaration frontend
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 57
Adapter Metadata Fragment I
ltAdapterTypeMetaData version=09gt
ltTypegtNAESBltTypegt
ltInboundgt
ltTransportProtocolgt
ltChannelAttributesgt
ltAttributeGroupgt
ltNamegtCRYPTConfigurationltNamegt
ltGuiLabelsgtltLabel language=ENgtCryptographic ConfigurationltLabelgtltGuiLabelsgt
ltAttributeReferencegtltReferenceNamegtCRYPTUseSigningltReferenceNamegt
ltInboundgt
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 58
Adapter Metadata Fragment II
ltAttributegt
ltNamegtCRYPTUseSigningltNamegt
ltDataTypegtxsdbooleanltDataTypegt
ltGuiLabelsgt
ltLabel language=ENgtUse SigningltLabelgt
ltLabel language=DEgtVerwendung von SignierungltLabelgt
ltGuiLabelsgt
ltAttributegt
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 59
Adapter Configuration
Configuration attribute of type boolean is rendered to a check-box
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 60
Adapter Metadata Upload (PCK)
Integration Repositorydoes not exist in case ofSAP PCK installations
The upload mechanismfor Adaper Meta Datafor SAP PCK installationsrequires additonalparameters
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 61
AF CPA Cache
The Adapter configuration is deployed from the configuration time(SAP PCK or Integration Directory) to the J2EE service CPACache(Collaboration Profile Agreement)
The Adapter configuration can be accessed at runtime from withinadapter modules or JCA resource adapters via the CPACache API
The two main use cases are implemented inLookupManager to retrieve adapter configuation andNormalizationManager to retrieve Party information
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 62
Packaging Adapter Components
SAP recommends to use SAP Software Deployment Manager (SDM) for deployment
Software Delivery Archives (SDA) can contain software components of different types (eg applications libraries)
Detailed version information and dependencies to other components simplify program management
Adapter Modules and Development
Summary
Adapter Framework Overview
Adapter Strategy
Agenda
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 64
Summary
Adapter Framework runs on J2EE Stack of SAP Web AS
Adapter Framework is platform for Adapter Engine and SAP PCK
Adapter Framework provides an extensible platform for developing and running adapters
Adapter Engine utilizes central configuration monitoring administration
Dual connectivity strategyAdapter Framework for comprehensive integration of adaptersInteroperability via open standards to interop with EAI providers
SAP NetWeaver Certification for adapters based on Adapter Framework available
Adapter mappings metadata stored in Integration Repository
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 15
PI Adapters by iWay Software
Application AdaptersAriba BaanBroadvision ClarifyJD Edwards One World XE JD Edwards Worldi2 LawsonManugistics Microsoft CRMOracle Applications PeoplesoftQAD MFG Pro SiebelVantive
Industry Standard AdaptersSwift TransoraUCCnet
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 16
PI Adapters by iWay Software
Technical AdaptersAS1 (EDIINTSMTP) AS2 (EDIINTHTTP(S))BEA WLI COM+DCOMCorba Lotus NotesTibco Rendezvous
Mainframetransaction AdaptersCICS TMSIMSTelnet (3270) Telnet (5250) Tuxedo
Optionally further adapters can be added from a list of 160 iWayadapters e g HL7 (already certified) DB2 AS3 ebXML
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 17
SAP Conversion Agent by Informatica
Bi-directional conversion of unstructured and semi structured data from to XMLTransformation on message payloadProtocol support via SAPrsquos technical adapter (PI XI adapter framework)Transformations integrated via PI XI AF module
SAP J2EEPI XI Adapter Framework
Adapter
Adapter
Text2XML
XML2Excel
PDF2XML
ConversionAgent Studio
ConversionAgent Services
Conversion Agent Engine
CA AF Module
Conversion Agent J2EE Lib
Seamlessly integrated into Process Integration
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 18
Supported Data Formats by Informatica (partial list)
UNSTRUCTUREDMicrosoft WordMicrosoft ExcelPowerPointPDFStar OfficeWord PerfectASCII reportsHTMLEBCDICUndocumented binariesFlat filesRPGANSI
PRINT STREAMSAFPPost ScriptDJDE
SEMI-STRUCTURED HL7HIPAAASTMANSIndashX12EDIFACTCOBOLFIXCargo IMPMVRSWIFT
OTHER STANDARDSLegalXMLIFX cXMLebXML HL7 V30 ACORD (AL3 XML)
hellip using SAP technical adapter and Conversion Agent
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 19
Conversion Agent
Bi-directional conversion of unstructured and semi structured formats fromto XMLLinked through PI XI adapter framework module based on SAPrsquos technical adapter ndash no transport protocol manipulates payload informationSAP NetWeaver-wide use (via J2EE library)
3rd Party Adapters
Bi-directional conversion of one dedicated data format (eg SWIFT ANSI-X12 hellip) fromto XMLRuns within PI XI adapter framework - support payload transformation and transport protocol
Per adapter dedicated use within one SAP NetWeaver component
Conversion Agent vs 3rd Party Adapters
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 20
More Info about Connectivity Capabilities
httpservicesapcomxi xi in detail connectivity
Connectivity and Interoperability
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 21
Adapter Download from SAP Service Marketplace
SAP Service Marketplace httpservicesapcomswdc Download Installations and Upgrades Entry by Application Group Adapters
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 22
Certification Programs for Process Integration
httpwwwsdnsapcom Partners and ISVsIntegration and Certification Exchange Infrastructure
PI Based Certification Programs
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 23
Public info about certified PI adapters
httpwwwsapcompartnersdirectoriesSearchSolutionepxThird Party Defined Integration Scenarios NW-XI-AF 30
Certified PI Adapters
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 24
Adapter Configuration
Adapter independent parameters
Adapter specific parameters
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 25
Configurationcache
Adapter Engine
ISRuntime
AdapterSender
AdapterReceiver
Adapter Engine in SAP J2EE
Q
Administration
Security
Monitoring
Adapter-Specific
ComponentServices
TracingLogging
Module ProcessorEIS
Channel
acuteMessaging
Configcache
End-to-End MonitoringMessage flow over all components applications
Runtime Workbenchbull Uis for adminstration
monitoring
Integration Builder Directory
Receiver determinationbull Party-gtService-gtAction
Channel Definitionbull Adapter Enginebull Adapter Typebull Message Protocolbull Transport Protocolbull Securitybull Channel Configuration
(Sender Receiver Agreementbull PartyServiceAction lt-gt Channel
ConfigurationMaster
System Landscape Directorybull Holds component description
including address data
AdapterFramework
Integration Repositorybull Holds Adapter metadataIntegration Repositorybull Holds Adapter metadata
httpltIntegrationServerURLgt
Message
httpltAdapterEngineURLgt
OK Error
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 26
Transport Level Security
Transport Protocol Authentication
IDoc RFC and SNC Client Authentication
Client Authentication
Client Authentication
Client Authentication
Client Authentication
CRAM-MD5
Client Authentication
Client Authentication
Client Authentication
CDIX ndash Adapter HTTPs Client Authentication
RFC RFC and SNC
Plain HTTP HTTPs
FileFTP File Transfer Protocol using SSLTLS
SOAP HTTPsSMTPs (Receiver only)
Mail SMTPs POP3 IMAP4
Marketplace HTTPs
RNIF 20 ndash Adapter HTTPs
RNIF 11 ndash Adapter HTTPs
Supported by
Levels of Security
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 27
Message Level Security
Signature Non-Repudiation
of origin
Non-Repudiation of
receipt
Encryption
CDIX ndash Adapter PKCS7
Technology
XI protocol WS-Security
SOAP-Adapter WS-Security
SMIME
Mail-Adapter SMIME
RNIF 20 ndash Adapter SMIME
RNIF 11 ndash Adapter PKCS7
Supported by
Levels of Security
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 28
Access control list
Restrict access to the runtime environmentfor sender services of type Business Service or Business Systemfor interfaces of these sender services
Restrict access to particular (service) users
Check authorization at runtime
Configure access control in the Integration DirectorySender service Specify authorized users in the configuration of the corresponding (sender) serviceInterface Specify authorized users in the configuration of the relevant sender agreement which contains the interface in the object key
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 29
Dynamic Adapter Configuration
Enable adapters to read write dynamic message headers
Sender Adapter (constructing messages)Attach adapter specific information to message headerExamples File name source file size JMS timestamp mail subjectRead access to these attributes in receiver channel interface determination (routing) mapping
Receiver Adapter (consuming messages)Read attributes to overwrite values of channel configurationExamples Directory Name JMS Priority Mail Sender SOAP target URLSet attributes in mapping orUse attributes from sender in receiver channel
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 30
Sender Adapter Configuration (1)
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 31
Sender Adapter Configuration (2)
Add the filename et al to the message
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 32
Receiver Determination
Determinefilename-dependent receiver
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 33
Receiver Adapter
Store the file withthe name set in the messageattribute
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 34
Monitoring Adapter Engine
After selecting a message bdquoDetailsldquo View
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 35
Monitoring Integration Server
After selecting a message bdquoDisplayldquo
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 36
Remark Future of SAP XI 20 Adapter Engine
SAP XI 20 Adapter Engine is available in SAP NW acute04 and SAP NW 2004s as bdquoPlain J2SE Adapter Engineldquo
Functional scope as in SAP XI 20Adopted to the SAP XI 30 message protocolMinor maintenance issues bug fixes
RecommendationUse where platform requirements or limitations (hardware operating system JVM support) demand it
SAP XI 20 Adapter Engine works with SAP NW acute04 and SAP NW 2004s landscapes too
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 37
Integration Server
PlainJ2SE
Adapter Engine
Partner ConnectivityKitOptional non-central
Adapter EngineCentral Adapter Engine
Process Integration ndash Architecture
Integration Repository Integration Directory System Landscape Directory
Business Process Engine
Integration Engine
Adapter FrameworkMessagingQueuing
Security Handling
Resource
Adapter
Resource
Adapter
Resource
Adapter
Adapter FWMessagingQueuing
Security Handling
Adapter FWMessagingQueuing
Security Handling
PCK Configurationand Monitoring
HTTP
IDoc
Adapter
Adapter
FileDBJMSMarketplace
3rd Party Sys
FileDB
JMSSOAP
SAP ampNon-SAPSystem
FileDBJMSMarketplace
3rd Party Sys
FileDBJMSMarketplace
3rd Party Sys
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 38
SAP Partner Connectivity Kit Overview
SAP 3rdParty Appl PI XI
Smaller Company Subsidiary
SAPPCK
SAPApplication
3rd PartyApplication
Large Business Partner Headquarter
Internet
Enablement of smaller companies subsidiaries to exchange XML documents with their business partnerrsquos headquarterrsquos PI XI
SAPPCK
Providing a platform for development of own JCA Resource Adapters
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 39
SAP PCK ndash Adapters
SAP Partner Connectivity Kit (PCK) is based on Adapter Framework
SAP PCKlsquos objective is to enable XML document exchangebetween PI XI and business partner not using PI XI
SAP PCK also provides an extensible platform for developing and running individual JCA Resource adapters
Communication between PI XI and SAP PCK is via SAP XI messaging protocol
SAP PCK Includes the following adapters FileFTP JDBC JMS SOAP RFC IDoc (once available for SAP PCK) Mail SAP BC
Optionally SAP PCK can host further adapters that are available from SAP or 3rd party adapter providers
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 40
SAP PCK ndash Configuration Mapping
SAP PCK is deployed on stand-alone SAP J2EE Engine (part of SAP Web AS) within business partnerrsquos landscape
Configuration administration monitoring done locally on SAP PCK itself without need for an Integration Directory
Configuration UI provides same bdquolook and feelldquo as configuration UI of Adapter Engine
SAP PCK supports the development of message mappings using an integrated graphical mapping editor
Any source XML structure can be mapped to any target XML structureStandard functions are provided to perform calculations Boolean comparisons text mappings and other transformationsOptionally the standard functions can be enhanced with user-defined functions in Java
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 41
SAP PCK ndash Configuration UI
ConfigurationUI to configure Party Service Communication Channel Sender and Receiver agreementsSample screenshot for configuration of communication channel with adapter type sbquoFile FTPlsquo
Adapter Modules and Development
Summary
Adapter Framework Overview
Adapter Strategy
Agenda
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 43
SAP Exchange Infrastructure - Openness
Integration of SAP and non-SAP applicationsAdapter Framework for comprehensive integration of adaptersAdapters are used for technical connectivityAdapter metadata mappings are stored in Integration Repository
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 44
Dual Strategy
Dual connectivity strategyAdapter Framework for comprehensive integration of adapters to provide technical connectivity including central configurationadministration monitoring of adaptersInteroperability based on open standards (SOAP JMS HTTP(S)) tointeroperate with EAI providers
Value propositionStandardized interfaces allow easy integration of adapters from different partnersMinimum knowledge of end-to-end process integration requiredComprehensive integration avoids redundant maintenance ensures consistency enhances transparancyOpenness to integrate non-SAP applications 3rd party systems etcReduced TCO
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 45
Certification
CertificationSAP NetWeaver Certification of 3rd party adapters based on the adapter framework
Value propositionQuality (stability HA aspects performance etc) of adapters is controlledCertification helps customers to find right solutionQuick and convenient search for a variety of certified products with the online partner and product directory (httpwwwsapcompartnersdirectoriesSearchSolutionepx)Faster implementation time and lower integration costs through the use of tested 3rd party integrationReduced TCO
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 46
Adapter Mappings Metadata in Integration Repository
Adapter mappings and adapter metadata are stored in the Integration Repository
Centralized Integration Repository contains all relevant information for collaborative and integrative processesAll content adheres to open standards Adapters provide technical connectivity
Value propositionUse largest content catalogReduce costs in integration projectsReduce maintenance costsReduced TCO
Adapter Modules and Development
Summary
Adapter Framework Overview
Adapter Strategy
Agenda
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 48
For every adapter it is possible to define generic modules in the module processor possibility to extend the functionality of the specific adapter
Equivalent to the dispatcher classes in the J2SE adapter engine migration and examples
The default module configuration for the certain adapter is displayed in the channel configuration
Modules are EJBlsquos
Sequence matters
Module Processor Concept
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 49
Adapter Module Chain
Custom modulescan be added to default modulechains
Additional configurationparameters canbe specified eachmodule
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 50
Module Processor Documentation
SAP Help Portal (httphelpsapcom)SAP XI Runtime Connectivity Adapters Module ProcessorFeedback Mail to xidocumentationsapcom
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 51
Development Environment
Adapter development deployment and testing is possible on a single machine no full-blown PI XI is required
For testing purposes integration scenarioscan be configured in SAP PCK(eg loopback scenario)
Installation of SAP PCK already contains a sample adapter (including Adapter Meta Data) that should serve as a starting point
SAP Partner ConnectivityKit
Adapter FWMessagingQueuing
Security Handling
Resource
Adapter
PCK Configurationand Monitoring
FileDBJMSMarketplace
3rd Party Sys
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 52
Adapter Development Documentation
SAP Help Portal (httphelpsapcom)SAP XI Runtime Connectivity Partner Connectivity Kit Adapter DevelopmentFeedback Mail to xidocumentationsapcom
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 53
Requirements for Adapters (1)
Num AF Interface Category Description
1 JCA 10 conformance Mandatory Adapter must fulfill JCA 10 requirements (e g deployment) plus optional JCA 15 parts which are used by PI XI
2 AF Message Exchange Mandatory Adapter must be able to receive messages from AF and forward them to connected system and vice versa
3 AF Adapter Specific Modules
Optional SAP XI message and protocol conversion may be done entirely by the adapter or as adapter specific module and being called in the AF module chain context
4 Configuration Services Mandatory Unique configuration approach to manage adapters
5 Administrational Services
Optional Administration and Monitoring
6 Utility Service Mandatory Access to basic J2EE resources e g transactions and multithreading must be under control of J2EE server
7 Logging API Optional Adapters may use their own logging
8 Message Metadata Exchange
Optional Provide structure definition of message payloadIf not supported the definition of message types can be done in the Integration Repository
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 54
Requirements for Adapters (2)
Cluster-enabledConsider side-effects of clustering e g bdquoExactlyOnceInOrderldquo Avoid passing maneuvers
SpecializationBuild connection to exactly one type of business system or industrystandard protocol
DirectnessBuild connection to business system or industry standard protocoldirectly without any intermediate software components
SmoothnessLight-weighted low footprint adapter unnecessary system changes(many new or changed system DLL) should be avoided
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 55
Sample Adapter Source Code
Beside the API documentation a working sample adapter is shipped
The source code is available after installation
Analyzing the code helps understanding the Adapter Framework
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 56
Adapter Metadata
Adapter Metadata (AMD)XML file defines all configuration parameterseach adapter
AMD can be uploaded intoIntegration Iepositoryand SAP PCK
Configurationparameters are renderedinto the graphicalconfiguaration frontend
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 57
Adapter Metadata Fragment I
ltAdapterTypeMetaData version=09gt
ltTypegtNAESBltTypegt
ltInboundgt
ltTransportProtocolgt
ltChannelAttributesgt
ltAttributeGroupgt
ltNamegtCRYPTConfigurationltNamegt
ltGuiLabelsgtltLabel language=ENgtCryptographic ConfigurationltLabelgtltGuiLabelsgt
ltAttributeReferencegtltReferenceNamegtCRYPTUseSigningltReferenceNamegt
ltInboundgt
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 58
Adapter Metadata Fragment II
ltAttributegt
ltNamegtCRYPTUseSigningltNamegt
ltDataTypegtxsdbooleanltDataTypegt
ltGuiLabelsgt
ltLabel language=ENgtUse SigningltLabelgt
ltLabel language=DEgtVerwendung von SignierungltLabelgt
ltGuiLabelsgt
ltAttributegt
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 59
Adapter Configuration
Configuration attribute of type boolean is rendered to a check-box
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 60
Adapter Metadata Upload (PCK)
Integration Repositorydoes not exist in case ofSAP PCK installations
The upload mechanismfor Adaper Meta Datafor SAP PCK installationsrequires additonalparameters
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 61
AF CPA Cache
The Adapter configuration is deployed from the configuration time(SAP PCK or Integration Directory) to the J2EE service CPACache(Collaboration Profile Agreement)
The Adapter configuration can be accessed at runtime from withinadapter modules or JCA resource adapters via the CPACache API
The two main use cases are implemented inLookupManager to retrieve adapter configuation andNormalizationManager to retrieve Party information
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 62
Packaging Adapter Components
SAP recommends to use SAP Software Deployment Manager (SDM) for deployment
Software Delivery Archives (SDA) can contain software components of different types (eg applications libraries)
Detailed version information and dependencies to other components simplify program management
Adapter Modules and Development
Summary
Adapter Framework Overview
Adapter Strategy
Agenda
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 64
Summary
Adapter Framework runs on J2EE Stack of SAP Web AS
Adapter Framework is platform for Adapter Engine and SAP PCK
Adapter Framework provides an extensible platform for developing and running adapters
Adapter Engine utilizes central configuration monitoring administration
Dual connectivity strategyAdapter Framework for comprehensive integration of adaptersInteroperability via open standards to interop with EAI providers
SAP NetWeaver Certification for adapters based on Adapter Framework available
Adapter mappings metadata stored in Integration Repository
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 16
PI Adapters by iWay Software
Technical AdaptersAS1 (EDIINTSMTP) AS2 (EDIINTHTTP(S))BEA WLI COM+DCOMCorba Lotus NotesTibco Rendezvous
Mainframetransaction AdaptersCICS TMSIMSTelnet (3270) Telnet (5250) Tuxedo
Optionally further adapters can be added from a list of 160 iWayadapters e g HL7 (already certified) DB2 AS3 ebXML
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 17
SAP Conversion Agent by Informatica
Bi-directional conversion of unstructured and semi structured data from to XMLTransformation on message payloadProtocol support via SAPrsquos technical adapter (PI XI adapter framework)Transformations integrated via PI XI AF module
SAP J2EEPI XI Adapter Framework
Adapter
Adapter
Text2XML
XML2Excel
PDF2XML
ConversionAgent Studio
ConversionAgent Services
Conversion Agent Engine
CA AF Module
Conversion Agent J2EE Lib
Seamlessly integrated into Process Integration
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 18
Supported Data Formats by Informatica (partial list)
UNSTRUCTUREDMicrosoft WordMicrosoft ExcelPowerPointPDFStar OfficeWord PerfectASCII reportsHTMLEBCDICUndocumented binariesFlat filesRPGANSI
PRINT STREAMSAFPPost ScriptDJDE
SEMI-STRUCTURED HL7HIPAAASTMANSIndashX12EDIFACTCOBOLFIXCargo IMPMVRSWIFT
OTHER STANDARDSLegalXMLIFX cXMLebXML HL7 V30 ACORD (AL3 XML)
hellip using SAP technical adapter and Conversion Agent
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 19
Conversion Agent
Bi-directional conversion of unstructured and semi structured formats fromto XMLLinked through PI XI adapter framework module based on SAPrsquos technical adapter ndash no transport protocol manipulates payload informationSAP NetWeaver-wide use (via J2EE library)
3rd Party Adapters
Bi-directional conversion of one dedicated data format (eg SWIFT ANSI-X12 hellip) fromto XMLRuns within PI XI adapter framework - support payload transformation and transport protocol
Per adapter dedicated use within one SAP NetWeaver component
Conversion Agent vs 3rd Party Adapters
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 20
More Info about Connectivity Capabilities
httpservicesapcomxi xi in detail connectivity
Connectivity and Interoperability
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 21
Adapter Download from SAP Service Marketplace
SAP Service Marketplace httpservicesapcomswdc Download Installations and Upgrades Entry by Application Group Adapters
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 22
Certification Programs for Process Integration
httpwwwsdnsapcom Partners and ISVsIntegration and Certification Exchange Infrastructure
PI Based Certification Programs
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 23
Public info about certified PI adapters
httpwwwsapcompartnersdirectoriesSearchSolutionepxThird Party Defined Integration Scenarios NW-XI-AF 30
Certified PI Adapters
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 24
Adapter Configuration
Adapter independent parameters
Adapter specific parameters
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 25
Configurationcache
Adapter Engine
ISRuntime
AdapterSender
AdapterReceiver
Adapter Engine in SAP J2EE
Q
Administration
Security
Monitoring
Adapter-Specific
ComponentServices
TracingLogging
Module ProcessorEIS
Channel
acuteMessaging
Configcache
End-to-End MonitoringMessage flow over all components applications
Runtime Workbenchbull Uis for adminstration
monitoring
Integration Builder Directory
Receiver determinationbull Party-gtService-gtAction
Channel Definitionbull Adapter Enginebull Adapter Typebull Message Protocolbull Transport Protocolbull Securitybull Channel Configuration
(Sender Receiver Agreementbull PartyServiceAction lt-gt Channel
ConfigurationMaster
System Landscape Directorybull Holds component description
including address data
AdapterFramework
Integration Repositorybull Holds Adapter metadataIntegration Repositorybull Holds Adapter metadata
httpltIntegrationServerURLgt
Message
httpltAdapterEngineURLgt
OK Error
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 26
Transport Level Security
Transport Protocol Authentication
IDoc RFC and SNC Client Authentication
Client Authentication
Client Authentication
Client Authentication
Client Authentication
CRAM-MD5
Client Authentication
Client Authentication
Client Authentication
CDIX ndash Adapter HTTPs Client Authentication
RFC RFC and SNC
Plain HTTP HTTPs
FileFTP File Transfer Protocol using SSLTLS
SOAP HTTPsSMTPs (Receiver only)
Mail SMTPs POP3 IMAP4
Marketplace HTTPs
RNIF 20 ndash Adapter HTTPs
RNIF 11 ndash Adapter HTTPs
Supported by
Levels of Security
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 27
Message Level Security
Signature Non-Repudiation
of origin
Non-Repudiation of
receipt
Encryption
CDIX ndash Adapter PKCS7
Technology
XI protocol WS-Security
SOAP-Adapter WS-Security
SMIME
Mail-Adapter SMIME
RNIF 20 ndash Adapter SMIME
RNIF 11 ndash Adapter PKCS7
Supported by
Levels of Security
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 28
Access control list
Restrict access to the runtime environmentfor sender services of type Business Service or Business Systemfor interfaces of these sender services
Restrict access to particular (service) users
Check authorization at runtime
Configure access control in the Integration DirectorySender service Specify authorized users in the configuration of the corresponding (sender) serviceInterface Specify authorized users in the configuration of the relevant sender agreement which contains the interface in the object key
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 29
Dynamic Adapter Configuration
Enable adapters to read write dynamic message headers
Sender Adapter (constructing messages)Attach adapter specific information to message headerExamples File name source file size JMS timestamp mail subjectRead access to these attributes in receiver channel interface determination (routing) mapping
Receiver Adapter (consuming messages)Read attributes to overwrite values of channel configurationExamples Directory Name JMS Priority Mail Sender SOAP target URLSet attributes in mapping orUse attributes from sender in receiver channel
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 30
Sender Adapter Configuration (1)
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 31
Sender Adapter Configuration (2)
Add the filename et al to the message
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 32
Receiver Determination
Determinefilename-dependent receiver
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 33
Receiver Adapter
Store the file withthe name set in the messageattribute
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 34
Monitoring Adapter Engine
After selecting a message bdquoDetailsldquo View
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 35
Monitoring Integration Server
After selecting a message bdquoDisplayldquo
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 36
Remark Future of SAP XI 20 Adapter Engine
SAP XI 20 Adapter Engine is available in SAP NW acute04 and SAP NW 2004s as bdquoPlain J2SE Adapter Engineldquo
Functional scope as in SAP XI 20Adopted to the SAP XI 30 message protocolMinor maintenance issues bug fixes
RecommendationUse where platform requirements or limitations (hardware operating system JVM support) demand it
SAP XI 20 Adapter Engine works with SAP NW acute04 and SAP NW 2004s landscapes too
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 37
Integration Server
PlainJ2SE
Adapter Engine
Partner ConnectivityKitOptional non-central
Adapter EngineCentral Adapter Engine
Process Integration ndash Architecture
Integration Repository Integration Directory System Landscape Directory
Business Process Engine
Integration Engine
Adapter FrameworkMessagingQueuing
Security Handling
Resource
Adapter
Resource
Adapter
Resource
Adapter
Adapter FWMessagingQueuing
Security Handling
Adapter FWMessagingQueuing
Security Handling
PCK Configurationand Monitoring
HTTP
IDoc
Adapter
Adapter
FileDBJMSMarketplace
3rd Party Sys
FileDB
JMSSOAP
SAP ampNon-SAPSystem
FileDBJMSMarketplace
3rd Party Sys
FileDBJMSMarketplace
3rd Party Sys
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 38
SAP Partner Connectivity Kit Overview
SAP 3rdParty Appl PI XI
Smaller Company Subsidiary
SAPPCK
SAPApplication
3rd PartyApplication
Large Business Partner Headquarter
Internet
Enablement of smaller companies subsidiaries to exchange XML documents with their business partnerrsquos headquarterrsquos PI XI
SAPPCK
Providing a platform for development of own JCA Resource Adapters
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 39
SAP PCK ndash Adapters
SAP Partner Connectivity Kit (PCK) is based on Adapter Framework
SAP PCKlsquos objective is to enable XML document exchangebetween PI XI and business partner not using PI XI
SAP PCK also provides an extensible platform for developing and running individual JCA Resource adapters
Communication between PI XI and SAP PCK is via SAP XI messaging protocol
SAP PCK Includes the following adapters FileFTP JDBC JMS SOAP RFC IDoc (once available for SAP PCK) Mail SAP BC
Optionally SAP PCK can host further adapters that are available from SAP or 3rd party adapter providers
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 40
SAP PCK ndash Configuration Mapping
SAP PCK is deployed on stand-alone SAP J2EE Engine (part of SAP Web AS) within business partnerrsquos landscape
Configuration administration monitoring done locally on SAP PCK itself without need for an Integration Directory
Configuration UI provides same bdquolook and feelldquo as configuration UI of Adapter Engine
SAP PCK supports the development of message mappings using an integrated graphical mapping editor
Any source XML structure can be mapped to any target XML structureStandard functions are provided to perform calculations Boolean comparisons text mappings and other transformationsOptionally the standard functions can be enhanced with user-defined functions in Java
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 41
SAP PCK ndash Configuration UI
ConfigurationUI to configure Party Service Communication Channel Sender and Receiver agreementsSample screenshot for configuration of communication channel with adapter type sbquoFile FTPlsquo
Adapter Modules and Development
Summary
Adapter Framework Overview
Adapter Strategy
Agenda
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 43
SAP Exchange Infrastructure - Openness
Integration of SAP and non-SAP applicationsAdapter Framework for comprehensive integration of adaptersAdapters are used for technical connectivityAdapter metadata mappings are stored in Integration Repository
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 44
Dual Strategy
Dual connectivity strategyAdapter Framework for comprehensive integration of adapters to provide technical connectivity including central configurationadministration monitoring of adaptersInteroperability based on open standards (SOAP JMS HTTP(S)) tointeroperate with EAI providers
Value propositionStandardized interfaces allow easy integration of adapters from different partnersMinimum knowledge of end-to-end process integration requiredComprehensive integration avoids redundant maintenance ensures consistency enhances transparancyOpenness to integrate non-SAP applications 3rd party systems etcReduced TCO
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 45
Certification
CertificationSAP NetWeaver Certification of 3rd party adapters based on the adapter framework
Value propositionQuality (stability HA aspects performance etc) of adapters is controlledCertification helps customers to find right solutionQuick and convenient search for a variety of certified products with the online partner and product directory (httpwwwsapcompartnersdirectoriesSearchSolutionepx)Faster implementation time and lower integration costs through the use of tested 3rd party integrationReduced TCO
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 46
Adapter Mappings Metadata in Integration Repository
Adapter mappings and adapter metadata are stored in the Integration Repository
Centralized Integration Repository contains all relevant information for collaborative and integrative processesAll content adheres to open standards Adapters provide technical connectivity
Value propositionUse largest content catalogReduce costs in integration projectsReduce maintenance costsReduced TCO
Adapter Modules and Development
Summary
Adapter Framework Overview
Adapter Strategy
Agenda
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 48
For every adapter it is possible to define generic modules in the module processor possibility to extend the functionality of the specific adapter
Equivalent to the dispatcher classes in the J2SE adapter engine migration and examples
The default module configuration for the certain adapter is displayed in the channel configuration
Modules are EJBlsquos
Sequence matters
Module Processor Concept
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 49
Adapter Module Chain
Custom modulescan be added to default modulechains
Additional configurationparameters canbe specified eachmodule
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 50
Module Processor Documentation
SAP Help Portal (httphelpsapcom)SAP XI Runtime Connectivity Adapters Module ProcessorFeedback Mail to xidocumentationsapcom
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 51
Development Environment
Adapter development deployment and testing is possible on a single machine no full-blown PI XI is required
For testing purposes integration scenarioscan be configured in SAP PCK(eg loopback scenario)
Installation of SAP PCK already contains a sample adapter (including Adapter Meta Data) that should serve as a starting point
SAP Partner ConnectivityKit
Adapter FWMessagingQueuing
Security Handling
Resource
Adapter
PCK Configurationand Monitoring
FileDBJMSMarketplace
3rd Party Sys
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 52
Adapter Development Documentation
SAP Help Portal (httphelpsapcom)SAP XI Runtime Connectivity Partner Connectivity Kit Adapter DevelopmentFeedback Mail to xidocumentationsapcom
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 53
Requirements for Adapters (1)
Num AF Interface Category Description
1 JCA 10 conformance Mandatory Adapter must fulfill JCA 10 requirements (e g deployment) plus optional JCA 15 parts which are used by PI XI
2 AF Message Exchange Mandatory Adapter must be able to receive messages from AF and forward them to connected system and vice versa
3 AF Adapter Specific Modules
Optional SAP XI message and protocol conversion may be done entirely by the adapter or as adapter specific module and being called in the AF module chain context
4 Configuration Services Mandatory Unique configuration approach to manage adapters
5 Administrational Services
Optional Administration and Monitoring
6 Utility Service Mandatory Access to basic J2EE resources e g transactions and multithreading must be under control of J2EE server
7 Logging API Optional Adapters may use their own logging
8 Message Metadata Exchange
Optional Provide structure definition of message payloadIf not supported the definition of message types can be done in the Integration Repository
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 54
Requirements for Adapters (2)
Cluster-enabledConsider side-effects of clustering e g bdquoExactlyOnceInOrderldquo Avoid passing maneuvers
SpecializationBuild connection to exactly one type of business system or industrystandard protocol
DirectnessBuild connection to business system or industry standard protocoldirectly without any intermediate software components
SmoothnessLight-weighted low footprint adapter unnecessary system changes(many new or changed system DLL) should be avoided
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 55
Sample Adapter Source Code
Beside the API documentation a working sample adapter is shipped
The source code is available after installation
Analyzing the code helps understanding the Adapter Framework
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 56
Adapter Metadata
Adapter Metadata (AMD)XML file defines all configuration parameterseach adapter
AMD can be uploaded intoIntegration Iepositoryand SAP PCK
Configurationparameters are renderedinto the graphicalconfiguaration frontend
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 57
Adapter Metadata Fragment I
ltAdapterTypeMetaData version=09gt
ltTypegtNAESBltTypegt
ltInboundgt
ltTransportProtocolgt
ltChannelAttributesgt
ltAttributeGroupgt
ltNamegtCRYPTConfigurationltNamegt
ltGuiLabelsgtltLabel language=ENgtCryptographic ConfigurationltLabelgtltGuiLabelsgt
ltAttributeReferencegtltReferenceNamegtCRYPTUseSigningltReferenceNamegt
ltInboundgt
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 58
Adapter Metadata Fragment II
ltAttributegt
ltNamegtCRYPTUseSigningltNamegt
ltDataTypegtxsdbooleanltDataTypegt
ltGuiLabelsgt
ltLabel language=ENgtUse SigningltLabelgt
ltLabel language=DEgtVerwendung von SignierungltLabelgt
ltGuiLabelsgt
ltAttributegt
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 59
Adapter Configuration
Configuration attribute of type boolean is rendered to a check-box
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 60
Adapter Metadata Upload (PCK)
Integration Repositorydoes not exist in case ofSAP PCK installations
The upload mechanismfor Adaper Meta Datafor SAP PCK installationsrequires additonalparameters
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 61
AF CPA Cache
The Adapter configuration is deployed from the configuration time(SAP PCK or Integration Directory) to the J2EE service CPACache(Collaboration Profile Agreement)
The Adapter configuration can be accessed at runtime from withinadapter modules or JCA resource adapters via the CPACache API
The two main use cases are implemented inLookupManager to retrieve adapter configuation andNormalizationManager to retrieve Party information
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 62
Packaging Adapter Components
SAP recommends to use SAP Software Deployment Manager (SDM) for deployment
Software Delivery Archives (SDA) can contain software components of different types (eg applications libraries)
Detailed version information and dependencies to other components simplify program management
Adapter Modules and Development
Summary
Adapter Framework Overview
Adapter Strategy
Agenda
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 64
Summary
Adapter Framework runs on J2EE Stack of SAP Web AS
Adapter Framework is platform for Adapter Engine and SAP PCK
Adapter Framework provides an extensible platform for developing and running adapters
Adapter Engine utilizes central configuration monitoring administration
Dual connectivity strategyAdapter Framework for comprehensive integration of adaptersInteroperability via open standards to interop with EAI providers
SAP NetWeaver Certification for adapters based on Adapter Framework available
Adapter mappings metadata stored in Integration Repository
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 17
SAP Conversion Agent by Informatica
Bi-directional conversion of unstructured and semi structured data from to XMLTransformation on message payloadProtocol support via SAPrsquos technical adapter (PI XI adapter framework)Transformations integrated via PI XI AF module
SAP J2EEPI XI Adapter Framework
Adapter
Adapter
Text2XML
XML2Excel
PDF2XML
ConversionAgent Studio
ConversionAgent Services
Conversion Agent Engine
CA AF Module
Conversion Agent J2EE Lib
Seamlessly integrated into Process Integration
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 18
Supported Data Formats by Informatica (partial list)
UNSTRUCTUREDMicrosoft WordMicrosoft ExcelPowerPointPDFStar OfficeWord PerfectASCII reportsHTMLEBCDICUndocumented binariesFlat filesRPGANSI
PRINT STREAMSAFPPost ScriptDJDE
SEMI-STRUCTURED HL7HIPAAASTMANSIndashX12EDIFACTCOBOLFIXCargo IMPMVRSWIFT
OTHER STANDARDSLegalXMLIFX cXMLebXML HL7 V30 ACORD (AL3 XML)
hellip using SAP technical adapter and Conversion Agent
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 19
Conversion Agent
Bi-directional conversion of unstructured and semi structured formats fromto XMLLinked through PI XI adapter framework module based on SAPrsquos technical adapter ndash no transport protocol manipulates payload informationSAP NetWeaver-wide use (via J2EE library)
3rd Party Adapters
Bi-directional conversion of one dedicated data format (eg SWIFT ANSI-X12 hellip) fromto XMLRuns within PI XI adapter framework - support payload transformation and transport protocol
Per adapter dedicated use within one SAP NetWeaver component
Conversion Agent vs 3rd Party Adapters
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 20
More Info about Connectivity Capabilities
httpservicesapcomxi xi in detail connectivity
Connectivity and Interoperability
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 21
Adapter Download from SAP Service Marketplace
SAP Service Marketplace httpservicesapcomswdc Download Installations and Upgrades Entry by Application Group Adapters
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 22
Certification Programs for Process Integration
httpwwwsdnsapcom Partners and ISVsIntegration and Certification Exchange Infrastructure
PI Based Certification Programs
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 23
Public info about certified PI adapters
httpwwwsapcompartnersdirectoriesSearchSolutionepxThird Party Defined Integration Scenarios NW-XI-AF 30
Certified PI Adapters
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 24
Adapter Configuration
Adapter independent parameters
Adapter specific parameters
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 25
Configurationcache
Adapter Engine
ISRuntime
AdapterSender
AdapterReceiver
Adapter Engine in SAP J2EE
Q
Administration
Security
Monitoring
Adapter-Specific
ComponentServices
TracingLogging
Module ProcessorEIS
Channel
acuteMessaging
Configcache
End-to-End MonitoringMessage flow over all components applications
Runtime Workbenchbull Uis for adminstration
monitoring
Integration Builder Directory
Receiver determinationbull Party-gtService-gtAction
Channel Definitionbull Adapter Enginebull Adapter Typebull Message Protocolbull Transport Protocolbull Securitybull Channel Configuration
(Sender Receiver Agreementbull PartyServiceAction lt-gt Channel
ConfigurationMaster
System Landscape Directorybull Holds component description
including address data
AdapterFramework
Integration Repositorybull Holds Adapter metadataIntegration Repositorybull Holds Adapter metadata
httpltIntegrationServerURLgt
Message
httpltAdapterEngineURLgt
OK Error
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 26
Transport Level Security
Transport Protocol Authentication
IDoc RFC and SNC Client Authentication
Client Authentication
Client Authentication
Client Authentication
Client Authentication
CRAM-MD5
Client Authentication
Client Authentication
Client Authentication
CDIX ndash Adapter HTTPs Client Authentication
RFC RFC and SNC
Plain HTTP HTTPs
FileFTP File Transfer Protocol using SSLTLS
SOAP HTTPsSMTPs (Receiver only)
Mail SMTPs POP3 IMAP4
Marketplace HTTPs
RNIF 20 ndash Adapter HTTPs
RNIF 11 ndash Adapter HTTPs
Supported by
Levels of Security
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 27
Message Level Security
Signature Non-Repudiation
of origin
Non-Repudiation of
receipt
Encryption
CDIX ndash Adapter PKCS7
Technology
XI protocol WS-Security
SOAP-Adapter WS-Security
SMIME
Mail-Adapter SMIME
RNIF 20 ndash Adapter SMIME
RNIF 11 ndash Adapter PKCS7
Supported by
Levels of Security
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 28
Access control list
Restrict access to the runtime environmentfor sender services of type Business Service or Business Systemfor interfaces of these sender services
Restrict access to particular (service) users
Check authorization at runtime
Configure access control in the Integration DirectorySender service Specify authorized users in the configuration of the corresponding (sender) serviceInterface Specify authorized users in the configuration of the relevant sender agreement which contains the interface in the object key
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 29
Dynamic Adapter Configuration
Enable adapters to read write dynamic message headers
Sender Adapter (constructing messages)Attach adapter specific information to message headerExamples File name source file size JMS timestamp mail subjectRead access to these attributes in receiver channel interface determination (routing) mapping
Receiver Adapter (consuming messages)Read attributes to overwrite values of channel configurationExamples Directory Name JMS Priority Mail Sender SOAP target URLSet attributes in mapping orUse attributes from sender in receiver channel
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 30
Sender Adapter Configuration (1)
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 31
Sender Adapter Configuration (2)
Add the filename et al to the message
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 32
Receiver Determination
Determinefilename-dependent receiver
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 33
Receiver Adapter
Store the file withthe name set in the messageattribute
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 34
Monitoring Adapter Engine
After selecting a message bdquoDetailsldquo View
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 35
Monitoring Integration Server
After selecting a message bdquoDisplayldquo
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 36
Remark Future of SAP XI 20 Adapter Engine
SAP XI 20 Adapter Engine is available in SAP NW acute04 and SAP NW 2004s as bdquoPlain J2SE Adapter Engineldquo
Functional scope as in SAP XI 20Adopted to the SAP XI 30 message protocolMinor maintenance issues bug fixes
RecommendationUse where platform requirements or limitations (hardware operating system JVM support) demand it
SAP XI 20 Adapter Engine works with SAP NW acute04 and SAP NW 2004s landscapes too
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 37
Integration Server
PlainJ2SE
Adapter Engine
Partner ConnectivityKitOptional non-central
Adapter EngineCentral Adapter Engine
Process Integration ndash Architecture
Integration Repository Integration Directory System Landscape Directory
Business Process Engine
Integration Engine
Adapter FrameworkMessagingQueuing
Security Handling
Resource
Adapter
Resource
Adapter
Resource
Adapter
Adapter FWMessagingQueuing
Security Handling
Adapter FWMessagingQueuing
Security Handling
PCK Configurationand Monitoring
HTTP
IDoc
Adapter
Adapter
FileDBJMSMarketplace
3rd Party Sys
FileDB
JMSSOAP
SAP ampNon-SAPSystem
FileDBJMSMarketplace
3rd Party Sys
FileDBJMSMarketplace
3rd Party Sys
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 38
SAP Partner Connectivity Kit Overview
SAP 3rdParty Appl PI XI
Smaller Company Subsidiary
SAPPCK
SAPApplication
3rd PartyApplication
Large Business Partner Headquarter
Internet
Enablement of smaller companies subsidiaries to exchange XML documents with their business partnerrsquos headquarterrsquos PI XI
SAPPCK
Providing a platform for development of own JCA Resource Adapters
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 39
SAP PCK ndash Adapters
SAP Partner Connectivity Kit (PCK) is based on Adapter Framework
SAP PCKlsquos objective is to enable XML document exchangebetween PI XI and business partner not using PI XI
SAP PCK also provides an extensible platform for developing and running individual JCA Resource adapters
Communication between PI XI and SAP PCK is via SAP XI messaging protocol
SAP PCK Includes the following adapters FileFTP JDBC JMS SOAP RFC IDoc (once available for SAP PCK) Mail SAP BC
Optionally SAP PCK can host further adapters that are available from SAP or 3rd party adapter providers
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 40
SAP PCK ndash Configuration Mapping
SAP PCK is deployed on stand-alone SAP J2EE Engine (part of SAP Web AS) within business partnerrsquos landscape
Configuration administration monitoring done locally on SAP PCK itself without need for an Integration Directory
Configuration UI provides same bdquolook and feelldquo as configuration UI of Adapter Engine
SAP PCK supports the development of message mappings using an integrated graphical mapping editor
Any source XML structure can be mapped to any target XML structureStandard functions are provided to perform calculations Boolean comparisons text mappings and other transformationsOptionally the standard functions can be enhanced with user-defined functions in Java
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 41
SAP PCK ndash Configuration UI
ConfigurationUI to configure Party Service Communication Channel Sender and Receiver agreementsSample screenshot for configuration of communication channel with adapter type sbquoFile FTPlsquo
Adapter Modules and Development
Summary
Adapter Framework Overview
Adapter Strategy
Agenda
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 43
SAP Exchange Infrastructure - Openness
Integration of SAP and non-SAP applicationsAdapter Framework for comprehensive integration of adaptersAdapters are used for technical connectivityAdapter metadata mappings are stored in Integration Repository
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 44
Dual Strategy
Dual connectivity strategyAdapter Framework for comprehensive integration of adapters to provide technical connectivity including central configurationadministration monitoring of adaptersInteroperability based on open standards (SOAP JMS HTTP(S)) tointeroperate with EAI providers
Value propositionStandardized interfaces allow easy integration of adapters from different partnersMinimum knowledge of end-to-end process integration requiredComprehensive integration avoids redundant maintenance ensures consistency enhances transparancyOpenness to integrate non-SAP applications 3rd party systems etcReduced TCO
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 45
Certification
CertificationSAP NetWeaver Certification of 3rd party adapters based on the adapter framework
Value propositionQuality (stability HA aspects performance etc) of adapters is controlledCertification helps customers to find right solutionQuick and convenient search for a variety of certified products with the online partner and product directory (httpwwwsapcompartnersdirectoriesSearchSolutionepx)Faster implementation time and lower integration costs through the use of tested 3rd party integrationReduced TCO
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 46
Adapter Mappings Metadata in Integration Repository
Adapter mappings and adapter metadata are stored in the Integration Repository
Centralized Integration Repository contains all relevant information for collaborative and integrative processesAll content adheres to open standards Adapters provide technical connectivity
Value propositionUse largest content catalogReduce costs in integration projectsReduce maintenance costsReduced TCO
Adapter Modules and Development
Summary
Adapter Framework Overview
Adapter Strategy
Agenda
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 48
For every adapter it is possible to define generic modules in the module processor possibility to extend the functionality of the specific adapter
Equivalent to the dispatcher classes in the J2SE adapter engine migration and examples
The default module configuration for the certain adapter is displayed in the channel configuration
Modules are EJBlsquos
Sequence matters
Module Processor Concept
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 49
Adapter Module Chain
Custom modulescan be added to default modulechains
Additional configurationparameters canbe specified eachmodule
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 50
Module Processor Documentation
SAP Help Portal (httphelpsapcom)SAP XI Runtime Connectivity Adapters Module ProcessorFeedback Mail to xidocumentationsapcom
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 51
Development Environment
Adapter development deployment and testing is possible on a single machine no full-blown PI XI is required
For testing purposes integration scenarioscan be configured in SAP PCK(eg loopback scenario)
Installation of SAP PCK already contains a sample adapter (including Adapter Meta Data) that should serve as a starting point
SAP Partner ConnectivityKit
Adapter FWMessagingQueuing
Security Handling
Resource
Adapter
PCK Configurationand Monitoring
FileDBJMSMarketplace
3rd Party Sys
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 52
Adapter Development Documentation
SAP Help Portal (httphelpsapcom)SAP XI Runtime Connectivity Partner Connectivity Kit Adapter DevelopmentFeedback Mail to xidocumentationsapcom
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 53
Requirements for Adapters (1)
Num AF Interface Category Description
1 JCA 10 conformance Mandatory Adapter must fulfill JCA 10 requirements (e g deployment) plus optional JCA 15 parts which are used by PI XI
2 AF Message Exchange Mandatory Adapter must be able to receive messages from AF and forward them to connected system and vice versa
3 AF Adapter Specific Modules
Optional SAP XI message and protocol conversion may be done entirely by the adapter or as adapter specific module and being called in the AF module chain context
4 Configuration Services Mandatory Unique configuration approach to manage adapters
5 Administrational Services
Optional Administration and Monitoring
6 Utility Service Mandatory Access to basic J2EE resources e g transactions and multithreading must be under control of J2EE server
7 Logging API Optional Adapters may use their own logging
8 Message Metadata Exchange
Optional Provide structure definition of message payloadIf not supported the definition of message types can be done in the Integration Repository
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 54
Requirements for Adapters (2)
Cluster-enabledConsider side-effects of clustering e g bdquoExactlyOnceInOrderldquo Avoid passing maneuvers
SpecializationBuild connection to exactly one type of business system or industrystandard protocol
DirectnessBuild connection to business system or industry standard protocoldirectly without any intermediate software components
SmoothnessLight-weighted low footprint adapter unnecessary system changes(many new or changed system DLL) should be avoided
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 55
Sample Adapter Source Code
Beside the API documentation a working sample adapter is shipped
The source code is available after installation
Analyzing the code helps understanding the Adapter Framework
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 56
Adapter Metadata
Adapter Metadata (AMD)XML file defines all configuration parameterseach adapter
AMD can be uploaded intoIntegration Iepositoryand SAP PCK
Configurationparameters are renderedinto the graphicalconfiguaration frontend
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 57
Adapter Metadata Fragment I
ltAdapterTypeMetaData version=09gt
ltTypegtNAESBltTypegt
ltInboundgt
ltTransportProtocolgt
ltChannelAttributesgt
ltAttributeGroupgt
ltNamegtCRYPTConfigurationltNamegt
ltGuiLabelsgtltLabel language=ENgtCryptographic ConfigurationltLabelgtltGuiLabelsgt
ltAttributeReferencegtltReferenceNamegtCRYPTUseSigningltReferenceNamegt
ltInboundgt
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 58
Adapter Metadata Fragment II
ltAttributegt
ltNamegtCRYPTUseSigningltNamegt
ltDataTypegtxsdbooleanltDataTypegt
ltGuiLabelsgt
ltLabel language=ENgtUse SigningltLabelgt
ltLabel language=DEgtVerwendung von SignierungltLabelgt
ltGuiLabelsgt
ltAttributegt
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 59
Adapter Configuration
Configuration attribute of type boolean is rendered to a check-box
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 60
Adapter Metadata Upload (PCK)
Integration Repositorydoes not exist in case ofSAP PCK installations
The upload mechanismfor Adaper Meta Datafor SAP PCK installationsrequires additonalparameters
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 61
AF CPA Cache
The Adapter configuration is deployed from the configuration time(SAP PCK or Integration Directory) to the J2EE service CPACache(Collaboration Profile Agreement)
The Adapter configuration can be accessed at runtime from withinadapter modules or JCA resource adapters via the CPACache API
The two main use cases are implemented inLookupManager to retrieve adapter configuation andNormalizationManager to retrieve Party information
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 62
Packaging Adapter Components
SAP recommends to use SAP Software Deployment Manager (SDM) for deployment
Software Delivery Archives (SDA) can contain software components of different types (eg applications libraries)
Detailed version information and dependencies to other components simplify program management
Adapter Modules and Development
Summary
Adapter Framework Overview
Adapter Strategy
Agenda
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 64
Summary
Adapter Framework runs on J2EE Stack of SAP Web AS
Adapter Framework is platform for Adapter Engine and SAP PCK
Adapter Framework provides an extensible platform for developing and running adapters
Adapter Engine utilizes central configuration monitoring administration
Dual connectivity strategyAdapter Framework for comprehensive integration of adaptersInteroperability via open standards to interop with EAI providers
SAP NetWeaver Certification for adapters based on Adapter Framework available
Adapter mappings metadata stored in Integration Repository
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 18
Supported Data Formats by Informatica (partial list)
UNSTRUCTUREDMicrosoft WordMicrosoft ExcelPowerPointPDFStar OfficeWord PerfectASCII reportsHTMLEBCDICUndocumented binariesFlat filesRPGANSI
PRINT STREAMSAFPPost ScriptDJDE
SEMI-STRUCTURED HL7HIPAAASTMANSIndashX12EDIFACTCOBOLFIXCargo IMPMVRSWIFT
OTHER STANDARDSLegalXMLIFX cXMLebXML HL7 V30 ACORD (AL3 XML)
hellip using SAP technical adapter and Conversion Agent
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 19
Conversion Agent
Bi-directional conversion of unstructured and semi structured formats fromto XMLLinked through PI XI adapter framework module based on SAPrsquos technical adapter ndash no transport protocol manipulates payload informationSAP NetWeaver-wide use (via J2EE library)
3rd Party Adapters
Bi-directional conversion of one dedicated data format (eg SWIFT ANSI-X12 hellip) fromto XMLRuns within PI XI adapter framework - support payload transformation and transport protocol
Per adapter dedicated use within one SAP NetWeaver component
Conversion Agent vs 3rd Party Adapters
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 20
More Info about Connectivity Capabilities
httpservicesapcomxi xi in detail connectivity
Connectivity and Interoperability
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 21
Adapter Download from SAP Service Marketplace
SAP Service Marketplace httpservicesapcomswdc Download Installations and Upgrades Entry by Application Group Adapters
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 22
Certification Programs for Process Integration
httpwwwsdnsapcom Partners and ISVsIntegration and Certification Exchange Infrastructure
PI Based Certification Programs
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 23
Public info about certified PI adapters
httpwwwsapcompartnersdirectoriesSearchSolutionepxThird Party Defined Integration Scenarios NW-XI-AF 30
Certified PI Adapters
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 24
Adapter Configuration
Adapter independent parameters
Adapter specific parameters
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 25
Configurationcache
Adapter Engine
ISRuntime
AdapterSender
AdapterReceiver
Adapter Engine in SAP J2EE
Q
Administration
Security
Monitoring
Adapter-Specific
ComponentServices
TracingLogging
Module ProcessorEIS
Channel
acuteMessaging
Configcache
End-to-End MonitoringMessage flow over all components applications
Runtime Workbenchbull Uis for adminstration
monitoring
Integration Builder Directory
Receiver determinationbull Party-gtService-gtAction
Channel Definitionbull Adapter Enginebull Adapter Typebull Message Protocolbull Transport Protocolbull Securitybull Channel Configuration
(Sender Receiver Agreementbull PartyServiceAction lt-gt Channel
ConfigurationMaster
System Landscape Directorybull Holds component description
including address data
AdapterFramework
Integration Repositorybull Holds Adapter metadataIntegration Repositorybull Holds Adapter metadata
httpltIntegrationServerURLgt
Message
httpltAdapterEngineURLgt
OK Error
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 26
Transport Level Security
Transport Protocol Authentication
IDoc RFC and SNC Client Authentication
Client Authentication
Client Authentication
Client Authentication
Client Authentication
CRAM-MD5
Client Authentication
Client Authentication
Client Authentication
CDIX ndash Adapter HTTPs Client Authentication
RFC RFC and SNC
Plain HTTP HTTPs
FileFTP File Transfer Protocol using SSLTLS
SOAP HTTPsSMTPs (Receiver only)
Mail SMTPs POP3 IMAP4
Marketplace HTTPs
RNIF 20 ndash Adapter HTTPs
RNIF 11 ndash Adapter HTTPs
Supported by
Levels of Security
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 27
Message Level Security
Signature Non-Repudiation
of origin
Non-Repudiation of
receipt
Encryption
CDIX ndash Adapter PKCS7
Technology
XI protocol WS-Security
SOAP-Adapter WS-Security
SMIME
Mail-Adapter SMIME
RNIF 20 ndash Adapter SMIME
RNIF 11 ndash Adapter PKCS7
Supported by
Levels of Security
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 28
Access control list
Restrict access to the runtime environmentfor sender services of type Business Service or Business Systemfor interfaces of these sender services
Restrict access to particular (service) users
Check authorization at runtime
Configure access control in the Integration DirectorySender service Specify authorized users in the configuration of the corresponding (sender) serviceInterface Specify authorized users in the configuration of the relevant sender agreement which contains the interface in the object key
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 29
Dynamic Adapter Configuration
Enable adapters to read write dynamic message headers
Sender Adapter (constructing messages)Attach adapter specific information to message headerExamples File name source file size JMS timestamp mail subjectRead access to these attributes in receiver channel interface determination (routing) mapping
Receiver Adapter (consuming messages)Read attributes to overwrite values of channel configurationExamples Directory Name JMS Priority Mail Sender SOAP target URLSet attributes in mapping orUse attributes from sender in receiver channel
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 30
Sender Adapter Configuration (1)
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 31
Sender Adapter Configuration (2)
Add the filename et al to the message
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 32
Receiver Determination
Determinefilename-dependent receiver
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 33
Receiver Adapter
Store the file withthe name set in the messageattribute
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 34
Monitoring Adapter Engine
After selecting a message bdquoDetailsldquo View
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 35
Monitoring Integration Server
After selecting a message bdquoDisplayldquo
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 36
Remark Future of SAP XI 20 Adapter Engine
SAP XI 20 Adapter Engine is available in SAP NW acute04 and SAP NW 2004s as bdquoPlain J2SE Adapter Engineldquo
Functional scope as in SAP XI 20Adopted to the SAP XI 30 message protocolMinor maintenance issues bug fixes
RecommendationUse where platform requirements or limitations (hardware operating system JVM support) demand it
SAP XI 20 Adapter Engine works with SAP NW acute04 and SAP NW 2004s landscapes too
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 37
Integration Server
PlainJ2SE
Adapter Engine
Partner ConnectivityKitOptional non-central
Adapter EngineCentral Adapter Engine
Process Integration ndash Architecture
Integration Repository Integration Directory System Landscape Directory
Business Process Engine
Integration Engine
Adapter FrameworkMessagingQueuing
Security Handling
Resource
Adapter
Resource
Adapter
Resource
Adapter
Adapter FWMessagingQueuing
Security Handling
Adapter FWMessagingQueuing
Security Handling
PCK Configurationand Monitoring
HTTP
IDoc
Adapter
Adapter
FileDBJMSMarketplace
3rd Party Sys
FileDB
JMSSOAP
SAP ampNon-SAPSystem
FileDBJMSMarketplace
3rd Party Sys
FileDBJMSMarketplace
3rd Party Sys
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 38
SAP Partner Connectivity Kit Overview
SAP 3rdParty Appl PI XI
Smaller Company Subsidiary
SAPPCK
SAPApplication
3rd PartyApplication
Large Business Partner Headquarter
Internet
Enablement of smaller companies subsidiaries to exchange XML documents with their business partnerrsquos headquarterrsquos PI XI
SAPPCK
Providing a platform for development of own JCA Resource Adapters
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 39
SAP PCK ndash Adapters
SAP Partner Connectivity Kit (PCK) is based on Adapter Framework
SAP PCKlsquos objective is to enable XML document exchangebetween PI XI and business partner not using PI XI
SAP PCK also provides an extensible platform for developing and running individual JCA Resource adapters
Communication between PI XI and SAP PCK is via SAP XI messaging protocol
SAP PCK Includes the following adapters FileFTP JDBC JMS SOAP RFC IDoc (once available for SAP PCK) Mail SAP BC
Optionally SAP PCK can host further adapters that are available from SAP or 3rd party adapter providers
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 40
SAP PCK ndash Configuration Mapping
SAP PCK is deployed on stand-alone SAP J2EE Engine (part of SAP Web AS) within business partnerrsquos landscape
Configuration administration monitoring done locally on SAP PCK itself without need for an Integration Directory
Configuration UI provides same bdquolook and feelldquo as configuration UI of Adapter Engine
SAP PCK supports the development of message mappings using an integrated graphical mapping editor
Any source XML structure can be mapped to any target XML structureStandard functions are provided to perform calculations Boolean comparisons text mappings and other transformationsOptionally the standard functions can be enhanced with user-defined functions in Java
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 41
SAP PCK ndash Configuration UI
ConfigurationUI to configure Party Service Communication Channel Sender and Receiver agreementsSample screenshot for configuration of communication channel with adapter type sbquoFile FTPlsquo
Adapter Modules and Development
Summary
Adapter Framework Overview
Adapter Strategy
Agenda
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 43
SAP Exchange Infrastructure - Openness
Integration of SAP and non-SAP applicationsAdapter Framework for comprehensive integration of adaptersAdapters are used for technical connectivityAdapter metadata mappings are stored in Integration Repository
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 44
Dual Strategy
Dual connectivity strategyAdapter Framework for comprehensive integration of adapters to provide technical connectivity including central configurationadministration monitoring of adaptersInteroperability based on open standards (SOAP JMS HTTP(S)) tointeroperate with EAI providers
Value propositionStandardized interfaces allow easy integration of adapters from different partnersMinimum knowledge of end-to-end process integration requiredComprehensive integration avoids redundant maintenance ensures consistency enhances transparancyOpenness to integrate non-SAP applications 3rd party systems etcReduced TCO
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 45
Certification
CertificationSAP NetWeaver Certification of 3rd party adapters based on the adapter framework
Value propositionQuality (stability HA aspects performance etc) of adapters is controlledCertification helps customers to find right solutionQuick and convenient search for a variety of certified products with the online partner and product directory (httpwwwsapcompartnersdirectoriesSearchSolutionepx)Faster implementation time and lower integration costs through the use of tested 3rd party integrationReduced TCO
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 46
Adapter Mappings Metadata in Integration Repository
Adapter mappings and adapter metadata are stored in the Integration Repository
Centralized Integration Repository contains all relevant information for collaborative and integrative processesAll content adheres to open standards Adapters provide technical connectivity
Value propositionUse largest content catalogReduce costs in integration projectsReduce maintenance costsReduced TCO
Adapter Modules and Development
Summary
Adapter Framework Overview
Adapter Strategy
Agenda
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 48
For every adapter it is possible to define generic modules in the module processor possibility to extend the functionality of the specific adapter
Equivalent to the dispatcher classes in the J2SE adapter engine migration and examples
The default module configuration for the certain adapter is displayed in the channel configuration
Modules are EJBlsquos
Sequence matters
Module Processor Concept
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 49
Adapter Module Chain
Custom modulescan be added to default modulechains
Additional configurationparameters canbe specified eachmodule
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 50
Module Processor Documentation
SAP Help Portal (httphelpsapcom)SAP XI Runtime Connectivity Adapters Module ProcessorFeedback Mail to xidocumentationsapcom
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 51
Development Environment
Adapter development deployment and testing is possible on a single machine no full-blown PI XI is required
For testing purposes integration scenarioscan be configured in SAP PCK(eg loopback scenario)
Installation of SAP PCK already contains a sample adapter (including Adapter Meta Data) that should serve as a starting point
SAP Partner ConnectivityKit
Adapter FWMessagingQueuing
Security Handling
Resource
Adapter
PCK Configurationand Monitoring
FileDBJMSMarketplace
3rd Party Sys
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 52
Adapter Development Documentation
SAP Help Portal (httphelpsapcom)SAP XI Runtime Connectivity Partner Connectivity Kit Adapter DevelopmentFeedback Mail to xidocumentationsapcom
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 53
Requirements for Adapters (1)
Num AF Interface Category Description
1 JCA 10 conformance Mandatory Adapter must fulfill JCA 10 requirements (e g deployment) plus optional JCA 15 parts which are used by PI XI
2 AF Message Exchange Mandatory Adapter must be able to receive messages from AF and forward them to connected system and vice versa
3 AF Adapter Specific Modules
Optional SAP XI message and protocol conversion may be done entirely by the adapter or as adapter specific module and being called in the AF module chain context
4 Configuration Services Mandatory Unique configuration approach to manage adapters
5 Administrational Services
Optional Administration and Monitoring
6 Utility Service Mandatory Access to basic J2EE resources e g transactions and multithreading must be under control of J2EE server
7 Logging API Optional Adapters may use their own logging
8 Message Metadata Exchange
Optional Provide structure definition of message payloadIf not supported the definition of message types can be done in the Integration Repository
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 54
Requirements for Adapters (2)
Cluster-enabledConsider side-effects of clustering e g bdquoExactlyOnceInOrderldquo Avoid passing maneuvers
SpecializationBuild connection to exactly one type of business system or industrystandard protocol
DirectnessBuild connection to business system or industry standard protocoldirectly without any intermediate software components
SmoothnessLight-weighted low footprint adapter unnecessary system changes(many new or changed system DLL) should be avoided
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 55
Sample Adapter Source Code
Beside the API documentation a working sample adapter is shipped
The source code is available after installation
Analyzing the code helps understanding the Adapter Framework
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 56
Adapter Metadata
Adapter Metadata (AMD)XML file defines all configuration parameterseach adapter
AMD can be uploaded intoIntegration Iepositoryand SAP PCK
Configurationparameters are renderedinto the graphicalconfiguaration frontend
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 57
Adapter Metadata Fragment I
ltAdapterTypeMetaData version=09gt
ltTypegtNAESBltTypegt
ltInboundgt
ltTransportProtocolgt
ltChannelAttributesgt
ltAttributeGroupgt
ltNamegtCRYPTConfigurationltNamegt
ltGuiLabelsgtltLabel language=ENgtCryptographic ConfigurationltLabelgtltGuiLabelsgt
ltAttributeReferencegtltReferenceNamegtCRYPTUseSigningltReferenceNamegt
ltInboundgt
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 58
Adapter Metadata Fragment II
ltAttributegt
ltNamegtCRYPTUseSigningltNamegt
ltDataTypegtxsdbooleanltDataTypegt
ltGuiLabelsgt
ltLabel language=ENgtUse SigningltLabelgt
ltLabel language=DEgtVerwendung von SignierungltLabelgt
ltGuiLabelsgt
ltAttributegt
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 59
Adapter Configuration
Configuration attribute of type boolean is rendered to a check-box
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 60
Adapter Metadata Upload (PCK)
Integration Repositorydoes not exist in case ofSAP PCK installations
The upload mechanismfor Adaper Meta Datafor SAP PCK installationsrequires additonalparameters
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 61
AF CPA Cache
The Adapter configuration is deployed from the configuration time(SAP PCK or Integration Directory) to the J2EE service CPACache(Collaboration Profile Agreement)
The Adapter configuration can be accessed at runtime from withinadapter modules or JCA resource adapters via the CPACache API
The two main use cases are implemented inLookupManager to retrieve adapter configuation andNormalizationManager to retrieve Party information
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 62
Packaging Adapter Components
SAP recommends to use SAP Software Deployment Manager (SDM) for deployment
Software Delivery Archives (SDA) can contain software components of different types (eg applications libraries)
Detailed version information and dependencies to other components simplify program management
Adapter Modules and Development
Summary
Adapter Framework Overview
Adapter Strategy
Agenda
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 64
Summary
Adapter Framework runs on J2EE Stack of SAP Web AS
Adapter Framework is platform for Adapter Engine and SAP PCK
Adapter Framework provides an extensible platform for developing and running adapters
Adapter Engine utilizes central configuration monitoring administration
Dual connectivity strategyAdapter Framework for comprehensive integration of adaptersInteroperability via open standards to interop with EAI providers
SAP NetWeaver Certification for adapters based on Adapter Framework available
Adapter mappings metadata stored in Integration Repository
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 19
Conversion Agent
Bi-directional conversion of unstructured and semi structured formats fromto XMLLinked through PI XI adapter framework module based on SAPrsquos technical adapter ndash no transport protocol manipulates payload informationSAP NetWeaver-wide use (via J2EE library)
3rd Party Adapters
Bi-directional conversion of one dedicated data format (eg SWIFT ANSI-X12 hellip) fromto XMLRuns within PI XI adapter framework - support payload transformation and transport protocol
Per adapter dedicated use within one SAP NetWeaver component
Conversion Agent vs 3rd Party Adapters
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 20
More Info about Connectivity Capabilities
httpservicesapcomxi xi in detail connectivity
Connectivity and Interoperability
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 21
Adapter Download from SAP Service Marketplace
SAP Service Marketplace httpservicesapcomswdc Download Installations and Upgrades Entry by Application Group Adapters
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 22
Certification Programs for Process Integration
httpwwwsdnsapcom Partners and ISVsIntegration and Certification Exchange Infrastructure
PI Based Certification Programs
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 23
Public info about certified PI adapters
httpwwwsapcompartnersdirectoriesSearchSolutionepxThird Party Defined Integration Scenarios NW-XI-AF 30
Certified PI Adapters
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 24
Adapter Configuration
Adapter independent parameters
Adapter specific parameters
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 25
Configurationcache
Adapter Engine
ISRuntime
AdapterSender
AdapterReceiver
Adapter Engine in SAP J2EE
Q
Administration
Security
Monitoring
Adapter-Specific
ComponentServices
TracingLogging
Module ProcessorEIS
Channel
acuteMessaging
Configcache
End-to-End MonitoringMessage flow over all components applications
Runtime Workbenchbull Uis for adminstration
monitoring
Integration Builder Directory
Receiver determinationbull Party-gtService-gtAction
Channel Definitionbull Adapter Enginebull Adapter Typebull Message Protocolbull Transport Protocolbull Securitybull Channel Configuration
(Sender Receiver Agreementbull PartyServiceAction lt-gt Channel
ConfigurationMaster
System Landscape Directorybull Holds component description
including address data
AdapterFramework
Integration Repositorybull Holds Adapter metadataIntegration Repositorybull Holds Adapter metadata
httpltIntegrationServerURLgt
Message
httpltAdapterEngineURLgt
OK Error
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 26
Transport Level Security
Transport Protocol Authentication
IDoc RFC and SNC Client Authentication
Client Authentication
Client Authentication
Client Authentication
Client Authentication
CRAM-MD5
Client Authentication
Client Authentication
Client Authentication
CDIX ndash Adapter HTTPs Client Authentication
RFC RFC and SNC
Plain HTTP HTTPs
FileFTP File Transfer Protocol using SSLTLS
SOAP HTTPsSMTPs (Receiver only)
Mail SMTPs POP3 IMAP4
Marketplace HTTPs
RNIF 20 ndash Adapter HTTPs
RNIF 11 ndash Adapter HTTPs
Supported by
Levels of Security
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 27
Message Level Security
Signature Non-Repudiation
of origin
Non-Repudiation of
receipt
Encryption
CDIX ndash Adapter PKCS7
Technology
XI protocol WS-Security
SOAP-Adapter WS-Security
SMIME
Mail-Adapter SMIME
RNIF 20 ndash Adapter SMIME
RNIF 11 ndash Adapter PKCS7
Supported by
Levels of Security
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 28
Access control list
Restrict access to the runtime environmentfor sender services of type Business Service or Business Systemfor interfaces of these sender services
Restrict access to particular (service) users
Check authorization at runtime
Configure access control in the Integration DirectorySender service Specify authorized users in the configuration of the corresponding (sender) serviceInterface Specify authorized users in the configuration of the relevant sender agreement which contains the interface in the object key
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 29
Dynamic Adapter Configuration
Enable adapters to read write dynamic message headers
Sender Adapter (constructing messages)Attach adapter specific information to message headerExamples File name source file size JMS timestamp mail subjectRead access to these attributes in receiver channel interface determination (routing) mapping
Receiver Adapter (consuming messages)Read attributes to overwrite values of channel configurationExamples Directory Name JMS Priority Mail Sender SOAP target URLSet attributes in mapping orUse attributes from sender in receiver channel
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 30
Sender Adapter Configuration (1)
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 31
Sender Adapter Configuration (2)
Add the filename et al to the message
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 32
Receiver Determination
Determinefilename-dependent receiver
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 33
Receiver Adapter
Store the file withthe name set in the messageattribute
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 34
Monitoring Adapter Engine
After selecting a message bdquoDetailsldquo View
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 35
Monitoring Integration Server
After selecting a message bdquoDisplayldquo
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 36
Remark Future of SAP XI 20 Adapter Engine
SAP XI 20 Adapter Engine is available in SAP NW acute04 and SAP NW 2004s as bdquoPlain J2SE Adapter Engineldquo
Functional scope as in SAP XI 20Adopted to the SAP XI 30 message protocolMinor maintenance issues bug fixes
RecommendationUse where platform requirements or limitations (hardware operating system JVM support) demand it
SAP XI 20 Adapter Engine works with SAP NW acute04 and SAP NW 2004s landscapes too
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 37
Integration Server
PlainJ2SE
Adapter Engine
Partner ConnectivityKitOptional non-central
Adapter EngineCentral Adapter Engine
Process Integration ndash Architecture
Integration Repository Integration Directory System Landscape Directory
Business Process Engine
Integration Engine
Adapter FrameworkMessagingQueuing
Security Handling
Resource
Adapter
Resource
Adapter
Resource
Adapter
Adapter FWMessagingQueuing
Security Handling
Adapter FWMessagingQueuing
Security Handling
PCK Configurationand Monitoring
HTTP
IDoc
Adapter
Adapter
FileDBJMSMarketplace
3rd Party Sys
FileDB
JMSSOAP
SAP ampNon-SAPSystem
FileDBJMSMarketplace
3rd Party Sys
FileDBJMSMarketplace
3rd Party Sys
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 38
SAP Partner Connectivity Kit Overview
SAP 3rdParty Appl PI XI
Smaller Company Subsidiary
SAPPCK
SAPApplication
3rd PartyApplication
Large Business Partner Headquarter
Internet
Enablement of smaller companies subsidiaries to exchange XML documents with their business partnerrsquos headquarterrsquos PI XI
SAPPCK
Providing a platform for development of own JCA Resource Adapters
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 39
SAP PCK ndash Adapters
SAP Partner Connectivity Kit (PCK) is based on Adapter Framework
SAP PCKlsquos objective is to enable XML document exchangebetween PI XI and business partner not using PI XI
SAP PCK also provides an extensible platform for developing and running individual JCA Resource adapters
Communication between PI XI and SAP PCK is via SAP XI messaging protocol
SAP PCK Includes the following adapters FileFTP JDBC JMS SOAP RFC IDoc (once available for SAP PCK) Mail SAP BC
Optionally SAP PCK can host further adapters that are available from SAP or 3rd party adapter providers
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 40
SAP PCK ndash Configuration Mapping
SAP PCK is deployed on stand-alone SAP J2EE Engine (part of SAP Web AS) within business partnerrsquos landscape
Configuration administration monitoring done locally on SAP PCK itself without need for an Integration Directory
Configuration UI provides same bdquolook and feelldquo as configuration UI of Adapter Engine
SAP PCK supports the development of message mappings using an integrated graphical mapping editor
Any source XML structure can be mapped to any target XML structureStandard functions are provided to perform calculations Boolean comparisons text mappings and other transformationsOptionally the standard functions can be enhanced with user-defined functions in Java
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 41
SAP PCK ndash Configuration UI
ConfigurationUI to configure Party Service Communication Channel Sender and Receiver agreementsSample screenshot for configuration of communication channel with adapter type sbquoFile FTPlsquo
Adapter Modules and Development
Summary
Adapter Framework Overview
Adapter Strategy
Agenda
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 43
SAP Exchange Infrastructure - Openness
Integration of SAP and non-SAP applicationsAdapter Framework for comprehensive integration of adaptersAdapters are used for technical connectivityAdapter metadata mappings are stored in Integration Repository
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 44
Dual Strategy
Dual connectivity strategyAdapter Framework for comprehensive integration of adapters to provide technical connectivity including central configurationadministration monitoring of adaptersInteroperability based on open standards (SOAP JMS HTTP(S)) tointeroperate with EAI providers
Value propositionStandardized interfaces allow easy integration of adapters from different partnersMinimum knowledge of end-to-end process integration requiredComprehensive integration avoids redundant maintenance ensures consistency enhances transparancyOpenness to integrate non-SAP applications 3rd party systems etcReduced TCO
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 45
Certification
CertificationSAP NetWeaver Certification of 3rd party adapters based on the adapter framework
Value propositionQuality (stability HA aspects performance etc) of adapters is controlledCertification helps customers to find right solutionQuick and convenient search for a variety of certified products with the online partner and product directory (httpwwwsapcompartnersdirectoriesSearchSolutionepx)Faster implementation time and lower integration costs through the use of tested 3rd party integrationReduced TCO
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 46
Adapter Mappings Metadata in Integration Repository
Adapter mappings and adapter metadata are stored in the Integration Repository
Centralized Integration Repository contains all relevant information for collaborative and integrative processesAll content adheres to open standards Adapters provide technical connectivity
Value propositionUse largest content catalogReduce costs in integration projectsReduce maintenance costsReduced TCO
Adapter Modules and Development
Summary
Adapter Framework Overview
Adapter Strategy
Agenda
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 48
For every adapter it is possible to define generic modules in the module processor possibility to extend the functionality of the specific adapter
Equivalent to the dispatcher classes in the J2SE adapter engine migration and examples
The default module configuration for the certain adapter is displayed in the channel configuration
Modules are EJBlsquos
Sequence matters
Module Processor Concept
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 49
Adapter Module Chain
Custom modulescan be added to default modulechains
Additional configurationparameters canbe specified eachmodule
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 50
Module Processor Documentation
SAP Help Portal (httphelpsapcom)SAP XI Runtime Connectivity Adapters Module ProcessorFeedback Mail to xidocumentationsapcom
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 51
Development Environment
Adapter development deployment and testing is possible on a single machine no full-blown PI XI is required
For testing purposes integration scenarioscan be configured in SAP PCK(eg loopback scenario)
Installation of SAP PCK already contains a sample adapter (including Adapter Meta Data) that should serve as a starting point
SAP Partner ConnectivityKit
Adapter FWMessagingQueuing
Security Handling
Resource
Adapter
PCK Configurationand Monitoring
FileDBJMSMarketplace
3rd Party Sys
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 52
Adapter Development Documentation
SAP Help Portal (httphelpsapcom)SAP XI Runtime Connectivity Partner Connectivity Kit Adapter DevelopmentFeedback Mail to xidocumentationsapcom
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 53
Requirements for Adapters (1)
Num AF Interface Category Description
1 JCA 10 conformance Mandatory Adapter must fulfill JCA 10 requirements (e g deployment) plus optional JCA 15 parts which are used by PI XI
2 AF Message Exchange Mandatory Adapter must be able to receive messages from AF and forward them to connected system and vice versa
3 AF Adapter Specific Modules
Optional SAP XI message and protocol conversion may be done entirely by the adapter or as adapter specific module and being called in the AF module chain context
4 Configuration Services Mandatory Unique configuration approach to manage adapters
5 Administrational Services
Optional Administration and Monitoring
6 Utility Service Mandatory Access to basic J2EE resources e g transactions and multithreading must be under control of J2EE server
7 Logging API Optional Adapters may use their own logging
8 Message Metadata Exchange
Optional Provide structure definition of message payloadIf not supported the definition of message types can be done in the Integration Repository
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 54
Requirements for Adapters (2)
Cluster-enabledConsider side-effects of clustering e g bdquoExactlyOnceInOrderldquo Avoid passing maneuvers
SpecializationBuild connection to exactly one type of business system or industrystandard protocol
DirectnessBuild connection to business system or industry standard protocoldirectly without any intermediate software components
SmoothnessLight-weighted low footprint adapter unnecessary system changes(many new or changed system DLL) should be avoided
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 55
Sample Adapter Source Code
Beside the API documentation a working sample adapter is shipped
The source code is available after installation
Analyzing the code helps understanding the Adapter Framework
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 56
Adapter Metadata
Adapter Metadata (AMD)XML file defines all configuration parameterseach adapter
AMD can be uploaded intoIntegration Iepositoryand SAP PCK
Configurationparameters are renderedinto the graphicalconfiguaration frontend
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 57
Adapter Metadata Fragment I
ltAdapterTypeMetaData version=09gt
ltTypegtNAESBltTypegt
ltInboundgt
ltTransportProtocolgt
ltChannelAttributesgt
ltAttributeGroupgt
ltNamegtCRYPTConfigurationltNamegt
ltGuiLabelsgtltLabel language=ENgtCryptographic ConfigurationltLabelgtltGuiLabelsgt
ltAttributeReferencegtltReferenceNamegtCRYPTUseSigningltReferenceNamegt
ltInboundgt
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 58
Adapter Metadata Fragment II
ltAttributegt
ltNamegtCRYPTUseSigningltNamegt
ltDataTypegtxsdbooleanltDataTypegt
ltGuiLabelsgt
ltLabel language=ENgtUse SigningltLabelgt
ltLabel language=DEgtVerwendung von SignierungltLabelgt
ltGuiLabelsgt
ltAttributegt
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 59
Adapter Configuration
Configuration attribute of type boolean is rendered to a check-box
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 60
Adapter Metadata Upload (PCK)
Integration Repositorydoes not exist in case ofSAP PCK installations
The upload mechanismfor Adaper Meta Datafor SAP PCK installationsrequires additonalparameters
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 61
AF CPA Cache
The Adapter configuration is deployed from the configuration time(SAP PCK or Integration Directory) to the J2EE service CPACache(Collaboration Profile Agreement)
The Adapter configuration can be accessed at runtime from withinadapter modules or JCA resource adapters via the CPACache API
The two main use cases are implemented inLookupManager to retrieve adapter configuation andNormalizationManager to retrieve Party information
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 62
Packaging Adapter Components
SAP recommends to use SAP Software Deployment Manager (SDM) for deployment
Software Delivery Archives (SDA) can contain software components of different types (eg applications libraries)
Detailed version information and dependencies to other components simplify program management
Adapter Modules and Development
Summary
Adapter Framework Overview
Adapter Strategy
Agenda
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 64
Summary
Adapter Framework runs on J2EE Stack of SAP Web AS
Adapter Framework is platform for Adapter Engine and SAP PCK
Adapter Framework provides an extensible platform for developing and running adapters
Adapter Engine utilizes central configuration monitoring administration
Dual connectivity strategyAdapter Framework for comprehensive integration of adaptersInteroperability via open standards to interop with EAI providers
SAP NetWeaver Certification for adapters based on Adapter Framework available
Adapter mappings metadata stored in Integration Repository
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 20
More Info about Connectivity Capabilities
httpservicesapcomxi xi in detail connectivity
Connectivity and Interoperability
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 21
Adapter Download from SAP Service Marketplace
SAP Service Marketplace httpservicesapcomswdc Download Installations and Upgrades Entry by Application Group Adapters
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 22
Certification Programs for Process Integration
httpwwwsdnsapcom Partners and ISVsIntegration and Certification Exchange Infrastructure
PI Based Certification Programs
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 23
Public info about certified PI adapters
httpwwwsapcompartnersdirectoriesSearchSolutionepxThird Party Defined Integration Scenarios NW-XI-AF 30
Certified PI Adapters
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 24
Adapter Configuration
Adapter independent parameters
Adapter specific parameters
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 25
Configurationcache
Adapter Engine
ISRuntime
AdapterSender
AdapterReceiver
Adapter Engine in SAP J2EE
Q
Administration
Security
Monitoring
Adapter-Specific
ComponentServices
TracingLogging
Module ProcessorEIS
Channel
acuteMessaging
Configcache
End-to-End MonitoringMessage flow over all components applications
Runtime Workbenchbull Uis for adminstration
monitoring
Integration Builder Directory
Receiver determinationbull Party-gtService-gtAction
Channel Definitionbull Adapter Enginebull Adapter Typebull Message Protocolbull Transport Protocolbull Securitybull Channel Configuration
(Sender Receiver Agreementbull PartyServiceAction lt-gt Channel
ConfigurationMaster
System Landscape Directorybull Holds component description
including address data
AdapterFramework
Integration Repositorybull Holds Adapter metadataIntegration Repositorybull Holds Adapter metadata
httpltIntegrationServerURLgt
Message
httpltAdapterEngineURLgt
OK Error
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 26
Transport Level Security
Transport Protocol Authentication
IDoc RFC and SNC Client Authentication
Client Authentication
Client Authentication
Client Authentication
Client Authentication
CRAM-MD5
Client Authentication
Client Authentication
Client Authentication
CDIX ndash Adapter HTTPs Client Authentication
RFC RFC and SNC
Plain HTTP HTTPs
FileFTP File Transfer Protocol using SSLTLS
SOAP HTTPsSMTPs (Receiver only)
Mail SMTPs POP3 IMAP4
Marketplace HTTPs
RNIF 20 ndash Adapter HTTPs
RNIF 11 ndash Adapter HTTPs
Supported by
Levels of Security
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 27
Message Level Security
Signature Non-Repudiation
of origin
Non-Repudiation of
receipt
Encryption
CDIX ndash Adapter PKCS7
Technology
XI protocol WS-Security
SOAP-Adapter WS-Security
SMIME
Mail-Adapter SMIME
RNIF 20 ndash Adapter SMIME
RNIF 11 ndash Adapter PKCS7
Supported by
Levels of Security
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 28
Access control list
Restrict access to the runtime environmentfor sender services of type Business Service or Business Systemfor interfaces of these sender services
Restrict access to particular (service) users
Check authorization at runtime
Configure access control in the Integration DirectorySender service Specify authorized users in the configuration of the corresponding (sender) serviceInterface Specify authorized users in the configuration of the relevant sender agreement which contains the interface in the object key
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 29
Dynamic Adapter Configuration
Enable adapters to read write dynamic message headers
Sender Adapter (constructing messages)Attach adapter specific information to message headerExamples File name source file size JMS timestamp mail subjectRead access to these attributes in receiver channel interface determination (routing) mapping
Receiver Adapter (consuming messages)Read attributes to overwrite values of channel configurationExamples Directory Name JMS Priority Mail Sender SOAP target URLSet attributes in mapping orUse attributes from sender in receiver channel
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 30
Sender Adapter Configuration (1)
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 31
Sender Adapter Configuration (2)
Add the filename et al to the message
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 32
Receiver Determination
Determinefilename-dependent receiver
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 33
Receiver Adapter
Store the file withthe name set in the messageattribute
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 34
Monitoring Adapter Engine
After selecting a message bdquoDetailsldquo View
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 35
Monitoring Integration Server
After selecting a message bdquoDisplayldquo
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 36
Remark Future of SAP XI 20 Adapter Engine
SAP XI 20 Adapter Engine is available in SAP NW acute04 and SAP NW 2004s as bdquoPlain J2SE Adapter Engineldquo
Functional scope as in SAP XI 20Adopted to the SAP XI 30 message protocolMinor maintenance issues bug fixes
RecommendationUse where platform requirements or limitations (hardware operating system JVM support) demand it
SAP XI 20 Adapter Engine works with SAP NW acute04 and SAP NW 2004s landscapes too
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 37
Integration Server
PlainJ2SE
Adapter Engine
Partner ConnectivityKitOptional non-central
Adapter EngineCentral Adapter Engine
Process Integration ndash Architecture
Integration Repository Integration Directory System Landscape Directory
Business Process Engine
Integration Engine
Adapter FrameworkMessagingQueuing
Security Handling
Resource
Adapter
Resource
Adapter
Resource
Adapter
Adapter FWMessagingQueuing
Security Handling
Adapter FWMessagingQueuing
Security Handling
PCK Configurationand Monitoring
HTTP
IDoc
Adapter
Adapter
FileDBJMSMarketplace
3rd Party Sys
FileDB
JMSSOAP
SAP ampNon-SAPSystem
FileDBJMSMarketplace
3rd Party Sys
FileDBJMSMarketplace
3rd Party Sys
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 38
SAP Partner Connectivity Kit Overview
SAP 3rdParty Appl PI XI
Smaller Company Subsidiary
SAPPCK
SAPApplication
3rd PartyApplication
Large Business Partner Headquarter
Internet
Enablement of smaller companies subsidiaries to exchange XML documents with their business partnerrsquos headquarterrsquos PI XI
SAPPCK
Providing a platform for development of own JCA Resource Adapters
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 39
SAP PCK ndash Adapters
SAP Partner Connectivity Kit (PCK) is based on Adapter Framework
SAP PCKlsquos objective is to enable XML document exchangebetween PI XI and business partner not using PI XI
SAP PCK also provides an extensible platform for developing and running individual JCA Resource adapters
Communication between PI XI and SAP PCK is via SAP XI messaging protocol
SAP PCK Includes the following adapters FileFTP JDBC JMS SOAP RFC IDoc (once available for SAP PCK) Mail SAP BC
Optionally SAP PCK can host further adapters that are available from SAP or 3rd party adapter providers
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 40
SAP PCK ndash Configuration Mapping
SAP PCK is deployed on stand-alone SAP J2EE Engine (part of SAP Web AS) within business partnerrsquos landscape
Configuration administration monitoring done locally on SAP PCK itself without need for an Integration Directory
Configuration UI provides same bdquolook and feelldquo as configuration UI of Adapter Engine
SAP PCK supports the development of message mappings using an integrated graphical mapping editor
Any source XML structure can be mapped to any target XML structureStandard functions are provided to perform calculations Boolean comparisons text mappings and other transformationsOptionally the standard functions can be enhanced with user-defined functions in Java
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 41
SAP PCK ndash Configuration UI
ConfigurationUI to configure Party Service Communication Channel Sender and Receiver agreementsSample screenshot for configuration of communication channel with adapter type sbquoFile FTPlsquo
Adapter Modules and Development
Summary
Adapter Framework Overview
Adapter Strategy
Agenda
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 43
SAP Exchange Infrastructure - Openness
Integration of SAP and non-SAP applicationsAdapter Framework for comprehensive integration of adaptersAdapters are used for technical connectivityAdapter metadata mappings are stored in Integration Repository
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 44
Dual Strategy
Dual connectivity strategyAdapter Framework for comprehensive integration of adapters to provide technical connectivity including central configurationadministration monitoring of adaptersInteroperability based on open standards (SOAP JMS HTTP(S)) tointeroperate with EAI providers
Value propositionStandardized interfaces allow easy integration of adapters from different partnersMinimum knowledge of end-to-end process integration requiredComprehensive integration avoids redundant maintenance ensures consistency enhances transparancyOpenness to integrate non-SAP applications 3rd party systems etcReduced TCO
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 45
Certification
CertificationSAP NetWeaver Certification of 3rd party adapters based on the adapter framework
Value propositionQuality (stability HA aspects performance etc) of adapters is controlledCertification helps customers to find right solutionQuick and convenient search for a variety of certified products with the online partner and product directory (httpwwwsapcompartnersdirectoriesSearchSolutionepx)Faster implementation time and lower integration costs through the use of tested 3rd party integrationReduced TCO
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 46
Adapter Mappings Metadata in Integration Repository
Adapter mappings and adapter metadata are stored in the Integration Repository
Centralized Integration Repository contains all relevant information for collaborative and integrative processesAll content adheres to open standards Adapters provide technical connectivity
Value propositionUse largest content catalogReduce costs in integration projectsReduce maintenance costsReduced TCO
Adapter Modules and Development
Summary
Adapter Framework Overview
Adapter Strategy
Agenda
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 48
For every adapter it is possible to define generic modules in the module processor possibility to extend the functionality of the specific adapter
Equivalent to the dispatcher classes in the J2SE adapter engine migration and examples
The default module configuration for the certain adapter is displayed in the channel configuration
Modules are EJBlsquos
Sequence matters
Module Processor Concept
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 49
Adapter Module Chain
Custom modulescan be added to default modulechains
Additional configurationparameters canbe specified eachmodule
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 50
Module Processor Documentation
SAP Help Portal (httphelpsapcom)SAP XI Runtime Connectivity Adapters Module ProcessorFeedback Mail to xidocumentationsapcom
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 51
Development Environment
Adapter development deployment and testing is possible on a single machine no full-blown PI XI is required
For testing purposes integration scenarioscan be configured in SAP PCK(eg loopback scenario)
Installation of SAP PCK already contains a sample adapter (including Adapter Meta Data) that should serve as a starting point
SAP Partner ConnectivityKit
Adapter FWMessagingQueuing
Security Handling
Resource
Adapter
PCK Configurationand Monitoring
FileDBJMSMarketplace
3rd Party Sys
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 52
Adapter Development Documentation
SAP Help Portal (httphelpsapcom)SAP XI Runtime Connectivity Partner Connectivity Kit Adapter DevelopmentFeedback Mail to xidocumentationsapcom
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 53
Requirements for Adapters (1)
Num AF Interface Category Description
1 JCA 10 conformance Mandatory Adapter must fulfill JCA 10 requirements (e g deployment) plus optional JCA 15 parts which are used by PI XI
2 AF Message Exchange Mandatory Adapter must be able to receive messages from AF and forward them to connected system and vice versa
3 AF Adapter Specific Modules
Optional SAP XI message and protocol conversion may be done entirely by the adapter or as adapter specific module and being called in the AF module chain context
4 Configuration Services Mandatory Unique configuration approach to manage adapters
5 Administrational Services
Optional Administration and Monitoring
6 Utility Service Mandatory Access to basic J2EE resources e g transactions and multithreading must be under control of J2EE server
7 Logging API Optional Adapters may use their own logging
8 Message Metadata Exchange
Optional Provide structure definition of message payloadIf not supported the definition of message types can be done in the Integration Repository
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 54
Requirements for Adapters (2)
Cluster-enabledConsider side-effects of clustering e g bdquoExactlyOnceInOrderldquo Avoid passing maneuvers
SpecializationBuild connection to exactly one type of business system or industrystandard protocol
DirectnessBuild connection to business system or industry standard protocoldirectly without any intermediate software components
SmoothnessLight-weighted low footprint adapter unnecessary system changes(many new or changed system DLL) should be avoided
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 55
Sample Adapter Source Code
Beside the API documentation a working sample adapter is shipped
The source code is available after installation
Analyzing the code helps understanding the Adapter Framework
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 56
Adapter Metadata
Adapter Metadata (AMD)XML file defines all configuration parameterseach adapter
AMD can be uploaded intoIntegration Iepositoryand SAP PCK
Configurationparameters are renderedinto the graphicalconfiguaration frontend
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 57
Adapter Metadata Fragment I
ltAdapterTypeMetaData version=09gt
ltTypegtNAESBltTypegt
ltInboundgt
ltTransportProtocolgt
ltChannelAttributesgt
ltAttributeGroupgt
ltNamegtCRYPTConfigurationltNamegt
ltGuiLabelsgtltLabel language=ENgtCryptographic ConfigurationltLabelgtltGuiLabelsgt
ltAttributeReferencegtltReferenceNamegtCRYPTUseSigningltReferenceNamegt
ltInboundgt
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 58
Adapter Metadata Fragment II
ltAttributegt
ltNamegtCRYPTUseSigningltNamegt
ltDataTypegtxsdbooleanltDataTypegt
ltGuiLabelsgt
ltLabel language=ENgtUse SigningltLabelgt
ltLabel language=DEgtVerwendung von SignierungltLabelgt
ltGuiLabelsgt
ltAttributegt
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 59
Adapter Configuration
Configuration attribute of type boolean is rendered to a check-box
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 60
Adapter Metadata Upload (PCK)
Integration Repositorydoes not exist in case ofSAP PCK installations
The upload mechanismfor Adaper Meta Datafor SAP PCK installationsrequires additonalparameters
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 61
AF CPA Cache
The Adapter configuration is deployed from the configuration time(SAP PCK or Integration Directory) to the J2EE service CPACache(Collaboration Profile Agreement)
The Adapter configuration can be accessed at runtime from withinadapter modules or JCA resource adapters via the CPACache API
The two main use cases are implemented inLookupManager to retrieve adapter configuation andNormalizationManager to retrieve Party information
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 62
Packaging Adapter Components
SAP recommends to use SAP Software Deployment Manager (SDM) for deployment
Software Delivery Archives (SDA) can contain software components of different types (eg applications libraries)
Detailed version information and dependencies to other components simplify program management
Adapter Modules and Development
Summary
Adapter Framework Overview
Adapter Strategy
Agenda
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 64
Summary
Adapter Framework runs on J2EE Stack of SAP Web AS
Adapter Framework is platform for Adapter Engine and SAP PCK
Adapter Framework provides an extensible platform for developing and running adapters
Adapter Engine utilizes central configuration monitoring administration
Dual connectivity strategyAdapter Framework for comprehensive integration of adaptersInteroperability via open standards to interop with EAI providers
SAP NetWeaver Certification for adapters based on Adapter Framework available
Adapter mappings metadata stored in Integration Repository
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 21
Adapter Download from SAP Service Marketplace
SAP Service Marketplace httpservicesapcomswdc Download Installations and Upgrades Entry by Application Group Adapters
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 22
Certification Programs for Process Integration
httpwwwsdnsapcom Partners and ISVsIntegration and Certification Exchange Infrastructure
PI Based Certification Programs
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 23
Public info about certified PI adapters
httpwwwsapcompartnersdirectoriesSearchSolutionepxThird Party Defined Integration Scenarios NW-XI-AF 30
Certified PI Adapters
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 24
Adapter Configuration
Adapter independent parameters
Adapter specific parameters
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 25
Configurationcache
Adapter Engine
ISRuntime
AdapterSender
AdapterReceiver
Adapter Engine in SAP J2EE
Q
Administration
Security
Monitoring
Adapter-Specific
ComponentServices
TracingLogging
Module ProcessorEIS
Channel
acuteMessaging
Configcache
End-to-End MonitoringMessage flow over all components applications
Runtime Workbenchbull Uis for adminstration
monitoring
Integration Builder Directory
Receiver determinationbull Party-gtService-gtAction
Channel Definitionbull Adapter Enginebull Adapter Typebull Message Protocolbull Transport Protocolbull Securitybull Channel Configuration
(Sender Receiver Agreementbull PartyServiceAction lt-gt Channel
ConfigurationMaster
System Landscape Directorybull Holds component description
including address data
AdapterFramework
Integration Repositorybull Holds Adapter metadataIntegration Repositorybull Holds Adapter metadata
httpltIntegrationServerURLgt
Message
httpltAdapterEngineURLgt
OK Error
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 26
Transport Level Security
Transport Protocol Authentication
IDoc RFC and SNC Client Authentication
Client Authentication
Client Authentication
Client Authentication
Client Authentication
CRAM-MD5
Client Authentication
Client Authentication
Client Authentication
CDIX ndash Adapter HTTPs Client Authentication
RFC RFC and SNC
Plain HTTP HTTPs
FileFTP File Transfer Protocol using SSLTLS
SOAP HTTPsSMTPs (Receiver only)
Mail SMTPs POP3 IMAP4
Marketplace HTTPs
RNIF 20 ndash Adapter HTTPs
RNIF 11 ndash Adapter HTTPs
Supported by
Levels of Security
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 27
Message Level Security
Signature Non-Repudiation
of origin
Non-Repudiation of
receipt
Encryption
CDIX ndash Adapter PKCS7
Technology
XI protocol WS-Security
SOAP-Adapter WS-Security
SMIME
Mail-Adapter SMIME
RNIF 20 ndash Adapter SMIME
RNIF 11 ndash Adapter PKCS7
Supported by
Levels of Security
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 28
Access control list
Restrict access to the runtime environmentfor sender services of type Business Service or Business Systemfor interfaces of these sender services
Restrict access to particular (service) users
Check authorization at runtime
Configure access control in the Integration DirectorySender service Specify authorized users in the configuration of the corresponding (sender) serviceInterface Specify authorized users in the configuration of the relevant sender agreement which contains the interface in the object key
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 29
Dynamic Adapter Configuration
Enable adapters to read write dynamic message headers
Sender Adapter (constructing messages)Attach adapter specific information to message headerExamples File name source file size JMS timestamp mail subjectRead access to these attributes in receiver channel interface determination (routing) mapping
Receiver Adapter (consuming messages)Read attributes to overwrite values of channel configurationExamples Directory Name JMS Priority Mail Sender SOAP target URLSet attributes in mapping orUse attributes from sender in receiver channel
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 30
Sender Adapter Configuration (1)
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 31
Sender Adapter Configuration (2)
Add the filename et al to the message
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 32
Receiver Determination
Determinefilename-dependent receiver
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 33
Receiver Adapter
Store the file withthe name set in the messageattribute
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 34
Monitoring Adapter Engine
After selecting a message bdquoDetailsldquo View
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 35
Monitoring Integration Server
After selecting a message bdquoDisplayldquo
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 36
Remark Future of SAP XI 20 Adapter Engine
SAP XI 20 Adapter Engine is available in SAP NW acute04 and SAP NW 2004s as bdquoPlain J2SE Adapter Engineldquo
Functional scope as in SAP XI 20Adopted to the SAP XI 30 message protocolMinor maintenance issues bug fixes
RecommendationUse where platform requirements or limitations (hardware operating system JVM support) demand it
SAP XI 20 Adapter Engine works with SAP NW acute04 and SAP NW 2004s landscapes too
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 37
Integration Server
PlainJ2SE
Adapter Engine
Partner ConnectivityKitOptional non-central
Adapter EngineCentral Adapter Engine
Process Integration ndash Architecture
Integration Repository Integration Directory System Landscape Directory
Business Process Engine
Integration Engine
Adapter FrameworkMessagingQueuing
Security Handling
Resource
Adapter
Resource
Adapter
Resource
Adapter
Adapter FWMessagingQueuing
Security Handling
Adapter FWMessagingQueuing
Security Handling
PCK Configurationand Monitoring
HTTP
IDoc
Adapter
Adapter
FileDBJMSMarketplace
3rd Party Sys
FileDB
JMSSOAP
SAP ampNon-SAPSystem
FileDBJMSMarketplace
3rd Party Sys
FileDBJMSMarketplace
3rd Party Sys
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 38
SAP Partner Connectivity Kit Overview
SAP 3rdParty Appl PI XI
Smaller Company Subsidiary
SAPPCK
SAPApplication
3rd PartyApplication
Large Business Partner Headquarter
Internet
Enablement of smaller companies subsidiaries to exchange XML documents with their business partnerrsquos headquarterrsquos PI XI
SAPPCK
Providing a platform for development of own JCA Resource Adapters
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 39
SAP PCK ndash Adapters
SAP Partner Connectivity Kit (PCK) is based on Adapter Framework
SAP PCKlsquos objective is to enable XML document exchangebetween PI XI and business partner not using PI XI
SAP PCK also provides an extensible platform for developing and running individual JCA Resource adapters
Communication between PI XI and SAP PCK is via SAP XI messaging protocol
SAP PCK Includes the following adapters FileFTP JDBC JMS SOAP RFC IDoc (once available for SAP PCK) Mail SAP BC
Optionally SAP PCK can host further adapters that are available from SAP or 3rd party adapter providers
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 40
SAP PCK ndash Configuration Mapping
SAP PCK is deployed on stand-alone SAP J2EE Engine (part of SAP Web AS) within business partnerrsquos landscape
Configuration administration monitoring done locally on SAP PCK itself without need for an Integration Directory
Configuration UI provides same bdquolook and feelldquo as configuration UI of Adapter Engine
SAP PCK supports the development of message mappings using an integrated graphical mapping editor
Any source XML structure can be mapped to any target XML structureStandard functions are provided to perform calculations Boolean comparisons text mappings and other transformationsOptionally the standard functions can be enhanced with user-defined functions in Java
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 41
SAP PCK ndash Configuration UI
ConfigurationUI to configure Party Service Communication Channel Sender and Receiver agreementsSample screenshot for configuration of communication channel with adapter type sbquoFile FTPlsquo
Adapter Modules and Development
Summary
Adapter Framework Overview
Adapter Strategy
Agenda
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 43
SAP Exchange Infrastructure - Openness
Integration of SAP and non-SAP applicationsAdapter Framework for comprehensive integration of adaptersAdapters are used for technical connectivityAdapter metadata mappings are stored in Integration Repository
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 44
Dual Strategy
Dual connectivity strategyAdapter Framework for comprehensive integration of adapters to provide technical connectivity including central configurationadministration monitoring of adaptersInteroperability based on open standards (SOAP JMS HTTP(S)) tointeroperate with EAI providers
Value propositionStandardized interfaces allow easy integration of adapters from different partnersMinimum knowledge of end-to-end process integration requiredComprehensive integration avoids redundant maintenance ensures consistency enhances transparancyOpenness to integrate non-SAP applications 3rd party systems etcReduced TCO
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 45
Certification
CertificationSAP NetWeaver Certification of 3rd party adapters based on the adapter framework
Value propositionQuality (stability HA aspects performance etc) of adapters is controlledCertification helps customers to find right solutionQuick and convenient search for a variety of certified products with the online partner and product directory (httpwwwsapcompartnersdirectoriesSearchSolutionepx)Faster implementation time and lower integration costs through the use of tested 3rd party integrationReduced TCO
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 46
Adapter Mappings Metadata in Integration Repository
Adapter mappings and adapter metadata are stored in the Integration Repository
Centralized Integration Repository contains all relevant information for collaborative and integrative processesAll content adheres to open standards Adapters provide technical connectivity
Value propositionUse largest content catalogReduce costs in integration projectsReduce maintenance costsReduced TCO
Adapter Modules and Development
Summary
Adapter Framework Overview
Adapter Strategy
Agenda
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 48
For every adapter it is possible to define generic modules in the module processor possibility to extend the functionality of the specific adapter
Equivalent to the dispatcher classes in the J2SE adapter engine migration and examples
The default module configuration for the certain adapter is displayed in the channel configuration
Modules are EJBlsquos
Sequence matters
Module Processor Concept
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 49
Adapter Module Chain
Custom modulescan be added to default modulechains
Additional configurationparameters canbe specified eachmodule
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 50
Module Processor Documentation
SAP Help Portal (httphelpsapcom)SAP XI Runtime Connectivity Adapters Module ProcessorFeedback Mail to xidocumentationsapcom
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 51
Development Environment
Adapter development deployment and testing is possible on a single machine no full-blown PI XI is required
For testing purposes integration scenarioscan be configured in SAP PCK(eg loopback scenario)
Installation of SAP PCK already contains a sample adapter (including Adapter Meta Data) that should serve as a starting point
SAP Partner ConnectivityKit
Adapter FWMessagingQueuing
Security Handling
Resource
Adapter
PCK Configurationand Monitoring
FileDBJMSMarketplace
3rd Party Sys
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 52
Adapter Development Documentation
SAP Help Portal (httphelpsapcom)SAP XI Runtime Connectivity Partner Connectivity Kit Adapter DevelopmentFeedback Mail to xidocumentationsapcom
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 53
Requirements for Adapters (1)
Num AF Interface Category Description
1 JCA 10 conformance Mandatory Adapter must fulfill JCA 10 requirements (e g deployment) plus optional JCA 15 parts which are used by PI XI
2 AF Message Exchange Mandatory Adapter must be able to receive messages from AF and forward them to connected system and vice versa
3 AF Adapter Specific Modules
Optional SAP XI message and protocol conversion may be done entirely by the adapter or as adapter specific module and being called in the AF module chain context
4 Configuration Services Mandatory Unique configuration approach to manage adapters
5 Administrational Services
Optional Administration and Monitoring
6 Utility Service Mandatory Access to basic J2EE resources e g transactions and multithreading must be under control of J2EE server
7 Logging API Optional Adapters may use their own logging
8 Message Metadata Exchange
Optional Provide structure definition of message payloadIf not supported the definition of message types can be done in the Integration Repository
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 54
Requirements for Adapters (2)
Cluster-enabledConsider side-effects of clustering e g bdquoExactlyOnceInOrderldquo Avoid passing maneuvers
SpecializationBuild connection to exactly one type of business system or industrystandard protocol
DirectnessBuild connection to business system or industry standard protocoldirectly without any intermediate software components
SmoothnessLight-weighted low footprint adapter unnecessary system changes(many new or changed system DLL) should be avoided
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 55
Sample Adapter Source Code
Beside the API documentation a working sample adapter is shipped
The source code is available after installation
Analyzing the code helps understanding the Adapter Framework
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 56
Adapter Metadata
Adapter Metadata (AMD)XML file defines all configuration parameterseach adapter
AMD can be uploaded intoIntegration Iepositoryand SAP PCK
Configurationparameters are renderedinto the graphicalconfiguaration frontend
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 57
Adapter Metadata Fragment I
ltAdapterTypeMetaData version=09gt
ltTypegtNAESBltTypegt
ltInboundgt
ltTransportProtocolgt
ltChannelAttributesgt
ltAttributeGroupgt
ltNamegtCRYPTConfigurationltNamegt
ltGuiLabelsgtltLabel language=ENgtCryptographic ConfigurationltLabelgtltGuiLabelsgt
ltAttributeReferencegtltReferenceNamegtCRYPTUseSigningltReferenceNamegt
ltInboundgt
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 58
Adapter Metadata Fragment II
ltAttributegt
ltNamegtCRYPTUseSigningltNamegt
ltDataTypegtxsdbooleanltDataTypegt
ltGuiLabelsgt
ltLabel language=ENgtUse SigningltLabelgt
ltLabel language=DEgtVerwendung von SignierungltLabelgt
ltGuiLabelsgt
ltAttributegt
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 59
Adapter Configuration
Configuration attribute of type boolean is rendered to a check-box
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 60
Adapter Metadata Upload (PCK)
Integration Repositorydoes not exist in case ofSAP PCK installations
The upload mechanismfor Adaper Meta Datafor SAP PCK installationsrequires additonalparameters
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 61
AF CPA Cache
The Adapter configuration is deployed from the configuration time(SAP PCK or Integration Directory) to the J2EE service CPACache(Collaboration Profile Agreement)
The Adapter configuration can be accessed at runtime from withinadapter modules or JCA resource adapters via the CPACache API
The two main use cases are implemented inLookupManager to retrieve adapter configuation andNormalizationManager to retrieve Party information
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 62
Packaging Adapter Components
SAP recommends to use SAP Software Deployment Manager (SDM) for deployment
Software Delivery Archives (SDA) can contain software components of different types (eg applications libraries)
Detailed version information and dependencies to other components simplify program management
Adapter Modules and Development
Summary
Adapter Framework Overview
Adapter Strategy
Agenda
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 64
Summary
Adapter Framework runs on J2EE Stack of SAP Web AS
Adapter Framework is platform for Adapter Engine and SAP PCK
Adapter Framework provides an extensible platform for developing and running adapters
Adapter Engine utilizes central configuration monitoring administration
Dual connectivity strategyAdapter Framework for comprehensive integration of adaptersInteroperability via open standards to interop with EAI providers
SAP NetWeaver Certification for adapters based on Adapter Framework available
Adapter mappings metadata stored in Integration Repository
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 22
Certification Programs for Process Integration
httpwwwsdnsapcom Partners and ISVsIntegration and Certification Exchange Infrastructure
PI Based Certification Programs
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 23
Public info about certified PI adapters
httpwwwsapcompartnersdirectoriesSearchSolutionepxThird Party Defined Integration Scenarios NW-XI-AF 30
Certified PI Adapters
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 24
Adapter Configuration
Adapter independent parameters
Adapter specific parameters
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 25
Configurationcache
Adapter Engine
ISRuntime
AdapterSender
AdapterReceiver
Adapter Engine in SAP J2EE
Q
Administration
Security
Monitoring
Adapter-Specific
ComponentServices
TracingLogging
Module ProcessorEIS
Channel
acuteMessaging
Configcache
End-to-End MonitoringMessage flow over all components applications
Runtime Workbenchbull Uis for adminstration
monitoring
Integration Builder Directory
Receiver determinationbull Party-gtService-gtAction
Channel Definitionbull Adapter Enginebull Adapter Typebull Message Protocolbull Transport Protocolbull Securitybull Channel Configuration
(Sender Receiver Agreementbull PartyServiceAction lt-gt Channel
ConfigurationMaster
System Landscape Directorybull Holds component description
including address data
AdapterFramework
Integration Repositorybull Holds Adapter metadataIntegration Repositorybull Holds Adapter metadata
httpltIntegrationServerURLgt
Message
httpltAdapterEngineURLgt
OK Error
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 26
Transport Level Security
Transport Protocol Authentication
IDoc RFC and SNC Client Authentication
Client Authentication
Client Authentication
Client Authentication
Client Authentication
CRAM-MD5
Client Authentication
Client Authentication
Client Authentication
CDIX ndash Adapter HTTPs Client Authentication
RFC RFC and SNC
Plain HTTP HTTPs
FileFTP File Transfer Protocol using SSLTLS
SOAP HTTPsSMTPs (Receiver only)
Mail SMTPs POP3 IMAP4
Marketplace HTTPs
RNIF 20 ndash Adapter HTTPs
RNIF 11 ndash Adapter HTTPs
Supported by
Levels of Security
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 27
Message Level Security
Signature Non-Repudiation
of origin
Non-Repudiation of
receipt
Encryption
CDIX ndash Adapter PKCS7
Technology
XI protocol WS-Security
SOAP-Adapter WS-Security
SMIME
Mail-Adapter SMIME
RNIF 20 ndash Adapter SMIME
RNIF 11 ndash Adapter PKCS7
Supported by
Levels of Security
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 28
Access control list
Restrict access to the runtime environmentfor sender services of type Business Service or Business Systemfor interfaces of these sender services
Restrict access to particular (service) users
Check authorization at runtime
Configure access control in the Integration DirectorySender service Specify authorized users in the configuration of the corresponding (sender) serviceInterface Specify authorized users in the configuration of the relevant sender agreement which contains the interface in the object key
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 29
Dynamic Adapter Configuration
Enable adapters to read write dynamic message headers
Sender Adapter (constructing messages)Attach adapter specific information to message headerExamples File name source file size JMS timestamp mail subjectRead access to these attributes in receiver channel interface determination (routing) mapping
Receiver Adapter (consuming messages)Read attributes to overwrite values of channel configurationExamples Directory Name JMS Priority Mail Sender SOAP target URLSet attributes in mapping orUse attributes from sender in receiver channel
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 30
Sender Adapter Configuration (1)
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 31
Sender Adapter Configuration (2)
Add the filename et al to the message
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 32
Receiver Determination
Determinefilename-dependent receiver
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 33
Receiver Adapter
Store the file withthe name set in the messageattribute
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 34
Monitoring Adapter Engine
After selecting a message bdquoDetailsldquo View
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 35
Monitoring Integration Server
After selecting a message bdquoDisplayldquo
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 36
Remark Future of SAP XI 20 Adapter Engine
SAP XI 20 Adapter Engine is available in SAP NW acute04 and SAP NW 2004s as bdquoPlain J2SE Adapter Engineldquo
Functional scope as in SAP XI 20Adopted to the SAP XI 30 message protocolMinor maintenance issues bug fixes
RecommendationUse where platform requirements or limitations (hardware operating system JVM support) demand it
SAP XI 20 Adapter Engine works with SAP NW acute04 and SAP NW 2004s landscapes too
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 37
Integration Server
PlainJ2SE
Adapter Engine
Partner ConnectivityKitOptional non-central
Adapter EngineCentral Adapter Engine
Process Integration ndash Architecture
Integration Repository Integration Directory System Landscape Directory
Business Process Engine
Integration Engine
Adapter FrameworkMessagingQueuing
Security Handling
Resource
Adapter
Resource
Adapter
Resource
Adapter
Adapter FWMessagingQueuing
Security Handling
Adapter FWMessagingQueuing
Security Handling
PCK Configurationand Monitoring
HTTP
IDoc
Adapter
Adapter
FileDBJMSMarketplace
3rd Party Sys
FileDB
JMSSOAP
SAP ampNon-SAPSystem
FileDBJMSMarketplace
3rd Party Sys
FileDBJMSMarketplace
3rd Party Sys
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 38
SAP Partner Connectivity Kit Overview
SAP 3rdParty Appl PI XI
Smaller Company Subsidiary
SAPPCK
SAPApplication
3rd PartyApplication
Large Business Partner Headquarter
Internet
Enablement of smaller companies subsidiaries to exchange XML documents with their business partnerrsquos headquarterrsquos PI XI
SAPPCK
Providing a platform for development of own JCA Resource Adapters
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 39
SAP PCK ndash Adapters
SAP Partner Connectivity Kit (PCK) is based on Adapter Framework
SAP PCKlsquos objective is to enable XML document exchangebetween PI XI and business partner not using PI XI
SAP PCK also provides an extensible platform for developing and running individual JCA Resource adapters
Communication between PI XI and SAP PCK is via SAP XI messaging protocol
SAP PCK Includes the following adapters FileFTP JDBC JMS SOAP RFC IDoc (once available for SAP PCK) Mail SAP BC
Optionally SAP PCK can host further adapters that are available from SAP or 3rd party adapter providers
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 40
SAP PCK ndash Configuration Mapping
SAP PCK is deployed on stand-alone SAP J2EE Engine (part of SAP Web AS) within business partnerrsquos landscape
Configuration administration monitoring done locally on SAP PCK itself without need for an Integration Directory
Configuration UI provides same bdquolook and feelldquo as configuration UI of Adapter Engine
SAP PCK supports the development of message mappings using an integrated graphical mapping editor
Any source XML structure can be mapped to any target XML structureStandard functions are provided to perform calculations Boolean comparisons text mappings and other transformationsOptionally the standard functions can be enhanced with user-defined functions in Java
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 41
SAP PCK ndash Configuration UI
ConfigurationUI to configure Party Service Communication Channel Sender and Receiver agreementsSample screenshot for configuration of communication channel with adapter type sbquoFile FTPlsquo
Adapter Modules and Development
Summary
Adapter Framework Overview
Adapter Strategy
Agenda
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 43
SAP Exchange Infrastructure - Openness
Integration of SAP and non-SAP applicationsAdapter Framework for comprehensive integration of adaptersAdapters are used for technical connectivityAdapter metadata mappings are stored in Integration Repository
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 44
Dual Strategy
Dual connectivity strategyAdapter Framework for comprehensive integration of adapters to provide technical connectivity including central configurationadministration monitoring of adaptersInteroperability based on open standards (SOAP JMS HTTP(S)) tointeroperate with EAI providers
Value propositionStandardized interfaces allow easy integration of adapters from different partnersMinimum knowledge of end-to-end process integration requiredComprehensive integration avoids redundant maintenance ensures consistency enhances transparancyOpenness to integrate non-SAP applications 3rd party systems etcReduced TCO
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 45
Certification
CertificationSAP NetWeaver Certification of 3rd party adapters based on the adapter framework
Value propositionQuality (stability HA aspects performance etc) of adapters is controlledCertification helps customers to find right solutionQuick and convenient search for a variety of certified products with the online partner and product directory (httpwwwsapcompartnersdirectoriesSearchSolutionepx)Faster implementation time and lower integration costs through the use of tested 3rd party integrationReduced TCO
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 46
Adapter Mappings Metadata in Integration Repository
Adapter mappings and adapter metadata are stored in the Integration Repository
Centralized Integration Repository contains all relevant information for collaborative and integrative processesAll content adheres to open standards Adapters provide technical connectivity
Value propositionUse largest content catalogReduce costs in integration projectsReduce maintenance costsReduced TCO
Adapter Modules and Development
Summary
Adapter Framework Overview
Adapter Strategy
Agenda
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 48
For every adapter it is possible to define generic modules in the module processor possibility to extend the functionality of the specific adapter
Equivalent to the dispatcher classes in the J2SE adapter engine migration and examples
The default module configuration for the certain adapter is displayed in the channel configuration
Modules are EJBlsquos
Sequence matters
Module Processor Concept
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 49
Adapter Module Chain
Custom modulescan be added to default modulechains
Additional configurationparameters canbe specified eachmodule
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 50
Module Processor Documentation
SAP Help Portal (httphelpsapcom)SAP XI Runtime Connectivity Adapters Module ProcessorFeedback Mail to xidocumentationsapcom
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 51
Development Environment
Adapter development deployment and testing is possible on a single machine no full-blown PI XI is required
For testing purposes integration scenarioscan be configured in SAP PCK(eg loopback scenario)
Installation of SAP PCK already contains a sample adapter (including Adapter Meta Data) that should serve as a starting point
SAP Partner ConnectivityKit
Adapter FWMessagingQueuing
Security Handling
Resource
Adapter
PCK Configurationand Monitoring
FileDBJMSMarketplace
3rd Party Sys
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 52
Adapter Development Documentation
SAP Help Portal (httphelpsapcom)SAP XI Runtime Connectivity Partner Connectivity Kit Adapter DevelopmentFeedback Mail to xidocumentationsapcom
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 53
Requirements for Adapters (1)
Num AF Interface Category Description
1 JCA 10 conformance Mandatory Adapter must fulfill JCA 10 requirements (e g deployment) plus optional JCA 15 parts which are used by PI XI
2 AF Message Exchange Mandatory Adapter must be able to receive messages from AF and forward them to connected system and vice versa
3 AF Adapter Specific Modules
Optional SAP XI message and protocol conversion may be done entirely by the adapter or as adapter specific module and being called in the AF module chain context
4 Configuration Services Mandatory Unique configuration approach to manage adapters
5 Administrational Services
Optional Administration and Monitoring
6 Utility Service Mandatory Access to basic J2EE resources e g transactions and multithreading must be under control of J2EE server
7 Logging API Optional Adapters may use their own logging
8 Message Metadata Exchange
Optional Provide structure definition of message payloadIf not supported the definition of message types can be done in the Integration Repository
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 54
Requirements for Adapters (2)
Cluster-enabledConsider side-effects of clustering e g bdquoExactlyOnceInOrderldquo Avoid passing maneuvers
SpecializationBuild connection to exactly one type of business system or industrystandard protocol
DirectnessBuild connection to business system or industry standard protocoldirectly without any intermediate software components
SmoothnessLight-weighted low footprint adapter unnecessary system changes(many new or changed system DLL) should be avoided
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 55
Sample Adapter Source Code
Beside the API documentation a working sample adapter is shipped
The source code is available after installation
Analyzing the code helps understanding the Adapter Framework
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 56
Adapter Metadata
Adapter Metadata (AMD)XML file defines all configuration parameterseach adapter
AMD can be uploaded intoIntegration Iepositoryand SAP PCK
Configurationparameters are renderedinto the graphicalconfiguaration frontend
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 57
Adapter Metadata Fragment I
ltAdapterTypeMetaData version=09gt
ltTypegtNAESBltTypegt
ltInboundgt
ltTransportProtocolgt
ltChannelAttributesgt
ltAttributeGroupgt
ltNamegtCRYPTConfigurationltNamegt
ltGuiLabelsgtltLabel language=ENgtCryptographic ConfigurationltLabelgtltGuiLabelsgt
ltAttributeReferencegtltReferenceNamegtCRYPTUseSigningltReferenceNamegt
ltInboundgt
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 58
Adapter Metadata Fragment II
ltAttributegt
ltNamegtCRYPTUseSigningltNamegt
ltDataTypegtxsdbooleanltDataTypegt
ltGuiLabelsgt
ltLabel language=ENgtUse SigningltLabelgt
ltLabel language=DEgtVerwendung von SignierungltLabelgt
ltGuiLabelsgt
ltAttributegt
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 59
Adapter Configuration
Configuration attribute of type boolean is rendered to a check-box
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 60
Adapter Metadata Upload (PCK)
Integration Repositorydoes not exist in case ofSAP PCK installations
The upload mechanismfor Adaper Meta Datafor SAP PCK installationsrequires additonalparameters
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 61
AF CPA Cache
The Adapter configuration is deployed from the configuration time(SAP PCK or Integration Directory) to the J2EE service CPACache(Collaboration Profile Agreement)
The Adapter configuration can be accessed at runtime from withinadapter modules or JCA resource adapters via the CPACache API
The two main use cases are implemented inLookupManager to retrieve adapter configuation andNormalizationManager to retrieve Party information
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 62
Packaging Adapter Components
SAP recommends to use SAP Software Deployment Manager (SDM) for deployment
Software Delivery Archives (SDA) can contain software components of different types (eg applications libraries)
Detailed version information and dependencies to other components simplify program management
Adapter Modules and Development
Summary
Adapter Framework Overview
Adapter Strategy
Agenda
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 64
Summary
Adapter Framework runs on J2EE Stack of SAP Web AS
Adapter Framework is platform for Adapter Engine and SAP PCK
Adapter Framework provides an extensible platform for developing and running adapters
Adapter Engine utilizes central configuration monitoring administration
Dual connectivity strategyAdapter Framework for comprehensive integration of adaptersInteroperability via open standards to interop with EAI providers
SAP NetWeaver Certification for adapters based on Adapter Framework available
Adapter mappings metadata stored in Integration Repository
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 23
Public info about certified PI adapters
httpwwwsapcompartnersdirectoriesSearchSolutionepxThird Party Defined Integration Scenarios NW-XI-AF 30
Certified PI Adapters
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 24
Adapter Configuration
Adapter independent parameters
Adapter specific parameters
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 25
Configurationcache
Adapter Engine
ISRuntime
AdapterSender
AdapterReceiver
Adapter Engine in SAP J2EE
Q
Administration
Security
Monitoring
Adapter-Specific
ComponentServices
TracingLogging
Module ProcessorEIS
Channel
acuteMessaging
Configcache
End-to-End MonitoringMessage flow over all components applications
Runtime Workbenchbull Uis for adminstration
monitoring
Integration Builder Directory
Receiver determinationbull Party-gtService-gtAction
Channel Definitionbull Adapter Enginebull Adapter Typebull Message Protocolbull Transport Protocolbull Securitybull Channel Configuration
(Sender Receiver Agreementbull PartyServiceAction lt-gt Channel
ConfigurationMaster
System Landscape Directorybull Holds component description
including address data
AdapterFramework
Integration Repositorybull Holds Adapter metadataIntegration Repositorybull Holds Adapter metadata
httpltIntegrationServerURLgt
Message
httpltAdapterEngineURLgt
OK Error
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 26
Transport Level Security
Transport Protocol Authentication
IDoc RFC and SNC Client Authentication
Client Authentication
Client Authentication
Client Authentication
Client Authentication
CRAM-MD5
Client Authentication
Client Authentication
Client Authentication
CDIX ndash Adapter HTTPs Client Authentication
RFC RFC and SNC
Plain HTTP HTTPs
FileFTP File Transfer Protocol using SSLTLS
SOAP HTTPsSMTPs (Receiver only)
Mail SMTPs POP3 IMAP4
Marketplace HTTPs
RNIF 20 ndash Adapter HTTPs
RNIF 11 ndash Adapter HTTPs
Supported by
Levels of Security
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 27
Message Level Security
Signature Non-Repudiation
of origin
Non-Repudiation of
receipt
Encryption
CDIX ndash Adapter PKCS7
Technology
XI protocol WS-Security
SOAP-Adapter WS-Security
SMIME
Mail-Adapter SMIME
RNIF 20 ndash Adapter SMIME
RNIF 11 ndash Adapter PKCS7
Supported by
Levels of Security
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 28
Access control list
Restrict access to the runtime environmentfor sender services of type Business Service or Business Systemfor interfaces of these sender services
Restrict access to particular (service) users
Check authorization at runtime
Configure access control in the Integration DirectorySender service Specify authorized users in the configuration of the corresponding (sender) serviceInterface Specify authorized users in the configuration of the relevant sender agreement which contains the interface in the object key
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 29
Dynamic Adapter Configuration
Enable adapters to read write dynamic message headers
Sender Adapter (constructing messages)Attach adapter specific information to message headerExamples File name source file size JMS timestamp mail subjectRead access to these attributes in receiver channel interface determination (routing) mapping
Receiver Adapter (consuming messages)Read attributes to overwrite values of channel configurationExamples Directory Name JMS Priority Mail Sender SOAP target URLSet attributes in mapping orUse attributes from sender in receiver channel
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 30
Sender Adapter Configuration (1)
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 31
Sender Adapter Configuration (2)
Add the filename et al to the message
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 32
Receiver Determination
Determinefilename-dependent receiver
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 33
Receiver Adapter
Store the file withthe name set in the messageattribute
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 34
Monitoring Adapter Engine
After selecting a message bdquoDetailsldquo View
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 35
Monitoring Integration Server
After selecting a message bdquoDisplayldquo
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 36
Remark Future of SAP XI 20 Adapter Engine
SAP XI 20 Adapter Engine is available in SAP NW acute04 and SAP NW 2004s as bdquoPlain J2SE Adapter Engineldquo
Functional scope as in SAP XI 20Adopted to the SAP XI 30 message protocolMinor maintenance issues bug fixes
RecommendationUse where platform requirements or limitations (hardware operating system JVM support) demand it
SAP XI 20 Adapter Engine works with SAP NW acute04 and SAP NW 2004s landscapes too
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 37
Integration Server
PlainJ2SE
Adapter Engine
Partner ConnectivityKitOptional non-central
Adapter EngineCentral Adapter Engine
Process Integration ndash Architecture
Integration Repository Integration Directory System Landscape Directory
Business Process Engine
Integration Engine
Adapter FrameworkMessagingQueuing
Security Handling
Resource
Adapter
Resource
Adapter
Resource
Adapter
Adapter FWMessagingQueuing
Security Handling
Adapter FWMessagingQueuing
Security Handling
PCK Configurationand Monitoring
HTTP
IDoc
Adapter
Adapter
FileDBJMSMarketplace
3rd Party Sys
FileDB
JMSSOAP
SAP ampNon-SAPSystem
FileDBJMSMarketplace
3rd Party Sys
FileDBJMSMarketplace
3rd Party Sys
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 38
SAP Partner Connectivity Kit Overview
SAP 3rdParty Appl PI XI
Smaller Company Subsidiary
SAPPCK
SAPApplication
3rd PartyApplication
Large Business Partner Headquarter
Internet
Enablement of smaller companies subsidiaries to exchange XML documents with their business partnerrsquos headquarterrsquos PI XI
SAPPCK
Providing a platform for development of own JCA Resource Adapters
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 39
SAP PCK ndash Adapters
SAP Partner Connectivity Kit (PCK) is based on Adapter Framework
SAP PCKlsquos objective is to enable XML document exchangebetween PI XI and business partner not using PI XI
SAP PCK also provides an extensible platform for developing and running individual JCA Resource adapters
Communication between PI XI and SAP PCK is via SAP XI messaging protocol
SAP PCK Includes the following adapters FileFTP JDBC JMS SOAP RFC IDoc (once available for SAP PCK) Mail SAP BC
Optionally SAP PCK can host further adapters that are available from SAP or 3rd party adapter providers
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 40
SAP PCK ndash Configuration Mapping
SAP PCK is deployed on stand-alone SAP J2EE Engine (part of SAP Web AS) within business partnerrsquos landscape
Configuration administration monitoring done locally on SAP PCK itself without need for an Integration Directory
Configuration UI provides same bdquolook and feelldquo as configuration UI of Adapter Engine
SAP PCK supports the development of message mappings using an integrated graphical mapping editor
Any source XML structure can be mapped to any target XML structureStandard functions are provided to perform calculations Boolean comparisons text mappings and other transformationsOptionally the standard functions can be enhanced with user-defined functions in Java
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 41
SAP PCK ndash Configuration UI
ConfigurationUI to configure Party Service Communication Channel Sender and Receiver agreementsSample screenshot for configuration of communication channel with adapter type sbquoFile FTPlsquo
Adapter Modules and Development
Summary
Adapter Framework Overview
Adapter Strategy
Agenda
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 43
SAP Exchange Infrastructure - Openness
Integration of SAP and non-SAP applicationsAdapter Framework for comprehensive integration of adaptersAdapters are used for technical connectivityAdapter metadata mappings are stored in Integration Repository
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 44
Dual Strategy
Dual connectivity strategyAdapter Framework for comprehensive integration of adapters to provide technical connectivity including central configurationadministration monitoring of adaptersInteroperability based on open standards (SOAP JMS HTTP(S)) tointeroperate with EAI providers
Value propositionStandardized interfaces allow easy integration of adapters from different partnersMinimum knowledge of end-to-end process integration requiredComprehensive integration avoids redundant maintenance ensures consistency enhances transparancyOpenness to integrate non-SAP applications 3rd party systems etcReduced TCO
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 45
Certification
CertificationSAP NetWeaver Certification of 3rd party adapters based on the adapter framework
Value propositionQuality (stability HA aspects performance etc) of adapters is controlledCertification helps customers to find right solutionQuick and convenient search for a variety of certified products with the online partner and product directory (httpwwwsapcompartnersdirectoriesSearchSolutionepx)Faster implementation time and lower integration costs through the use of tested 3rd party integrationReduced TCO
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 46
Adapter Mappings Metadata in Integration Repository
Adapter mappings and adapter metadata are stored in the Integration Repository
Centralized Integration Repository contains all relevant information for collaborative and integrative processesAll content adheres to open standards Adapters provide technical connectivity
Value propositionUse largest content catalogReduce costs in integration projectsReduce maintenance costsReduced TCO
Adapter Modules and Development
Summary
Adapter Framework Overview
Adapter Strategy
Agenda
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 48
For every adapter it is possible to define generic modules in the module processor possibility to extend the functionality of the specific adapter
Equivalent to the dispatcher classes in the J2SE adapter engine migration and examples
The default module configuration for the certain adapter is displayed in the channel configuration
Modules are EJBlsquos
Sequence matters
Module Processor Concept
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 49
Adapter Module Chain
Custom modulescan be added to default modulechains
Additional configurationparameters canbe specified eachmodule
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 50
Module Processor Documentation
SAP Help Portal (httphelpsapcom)SAP XI Runtime Connectivity Adapters Module ProcessorFeedback Mail to xidocumentationsapcom
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 51
Development Environment
Adapter development deployment and testing is possible on a single machine no full-blown PI XI is required
For testing purposes integration scenarioscan be configured in SAP PCK(eg loopback scenario)
Installation of SAP PCK already contains a sample adapter (including Adapter Meta Data) that should serve as a starting point
SAP Partner ConnectivityKit
Adapter FWMessagingQueuing
Security Handling
Resource
Adapter
PCK Configurationand Monitoring
FileDBJMSMarketplace
3rd Party Sys
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 52
Adapter Development Documentation
SAP Help Portal (httphelpsapcom)SAP XI Runtime Connectivity Partner Connectivity Kit Adapter DevelopmentFeedback Mail to xidocumentationsapcom
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 53
Requirements for Adapters (1)
Num AF Interface Category Description
1 JCA 10 conformance Mandatory Adapter must fulfill JCA 10 requirements (e g deployment) plus optional JCA 15 parts which are used by PI XI
2 AF Message Exchange Mandatory Adapter must be able to receive messages from AF and forward them to connected system and vice versa
3 AF Adapter Specific Modules
Optional SAP XI message and protocol conversion may be done entirely by the adapter or as adapter specific module and being called in the AF module chain context
4 Configuration Services Mandatory Unique configuration approach to manage adapters
5 Administrational Services
Optional Administration and Monitoring
6 Utility Service Mandatory Access to basic J2EE resources e g transactions and multithreading must be under control of J2EE server
7 Logging API Optional Adapters may use their own logging
8 Message Metadata Exchange
Optional Provide structure definition of message payloadIf not supported the definition of message types can be done in the Integration Repository
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 54
Requirements for Adapters (2)
Cluster-enabledConsider side-effects of clustering e g bdquoExactlyOnceInOrderldquo Avoid passing maneuvers
SpecializationBuild connection to exactly one type of business system or industrystandard protocol
DirectnessBuild connection to business system or industry standard protocoldirectly without any intermediate software components
SmoothnessLight-weighted low footprint adapter unnecessary system changes(many new or changed system DLL) should be avoided
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 55
Sample Adapter Source Code
Beside the API documentation a working sample adapter is shipped
The source code is available after installation
Analyzing the code helps understanding the Adapter Framework
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 56
Adapter Metadata
Adapter Metadata (AMD)XML file defines all configuration parameterseach adapter
AMD can be uploaded intoIntegration Iepositoryand SAP PCK
Configurationparameters are renderedinto the graphicalconfiguaration frontend
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 57
Adapter Metadata Fragment I
ltAdapterTypeMetaData version=09gt
ltTypegtNAESBltTypegt
ltInboundgt
ltTransportProtocolgt
ltChannelAttributesgt
ltAttributeGroupgt
ltNamegtCRYPTConfigurationltNamegt
ltGuiLabelsgtltLabel language=ENgtCryptographic ConfigurationltLabelgtltGuiLabelsgt
ltAttributeReferencegtltReferenceNamegtCRYPTUseSigningltReferenceNamegt
ltInboundgt
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 58
Adapter Metadata Fragment II
ltAttributegt
ltNamegtCRYPTUseSigningltNamegt
ltDataTypegtxsdbooleanltDataTypegt
ltGuiLabelsgt
ltLabel language=ENgtUse SigningltLabelgt
ltLabel language=DEgtVerwendung von SignierungltLabelgt
ltGuiLabelsgt
ltAttributegt
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 59
Adapter Configuration
Configuration attribute of type boolean is rendered to a check-box
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 60
Adapter Metadata Upload (PCK)
Integration Repositorydoes not exist in case ofSAP PCK installations
The upload mechanismfor Adaper Meta Datafor SAP PCK installationsrequires additonalparameters
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 61
AF CPA Cache
The Adapter configuration is deployed from the configuration time(SAP PCK or Integration Directory) to the J2EE service CPACache(Collaboration Profile Agreement)
The Adapter configuration can be accessed at runtime from withinadapter modules or JCA resource adapters via the CPACache API
The two main use cases are implemented inLookupManager to retrieve adapter configuation andNormalizationManager to retrieve Party information
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 62
Packaging Adapter Components
SAP recommends to use SAP Software Deployment Manager (SDM) for deployment
Software Delivery Archives (SDA) can contain software components of different types (eg applications libraries)
Detailed version information and dependencies to other components simplify program management
Adapter Modules and Development
Summary
Adapter Framework Overview
Adapter Strategy
Agenda
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 64
Summary
Adapter Framework runs on J2EE Stack of SAP Web AS
Adapter Framework is platform for Adapter Engine and SAP PCK
Adapter Framework provides an extensible platform for developing and running adapters
Adapter Engine utilizes central configuration monitoring administration
Dual connectivity strategyAdapter Framework for comprehensive integration of adaptersInteroperability via open standards to interop with EAI providers
SAP NetWeaver Certification for adapters based on Adapter Framework available
Adapter mappings metadata stored in Integration Repository
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 24
Adapter Configuration
Adapter independent parameters
Adapter specific parameters
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 25
Configurationcache
Adapter Engine
ISRuntime
AdapterSender
AdapterReceiver
Adapter Engine in SAP J2EE
Q
Administration
Security
Monitoring
Adapter-Specific
ComponentServices
TracingLogging
Module ProcessorEIS
Channel
acuteMessaging
Configcache
End-to-End MonitoringMessage flow over all components applications
Runtime Workbenchbull Uis for adminstration
monitoring
Integration Builder Directory
Receiver determinationbull Party-gtService-gtAction
Channel Definitionbull Adapter Enginebull Adapter Typebull Message Protocolbull Transport Protocolbull Securitybull Channel Configuration
(Sender Receiver Agreementbull PartyServiceAction lt-gt Channel
ConfigurationMaster
System Landscape Directorybull Holds component description
including address data
AdapterFramework
Integration Repositorybull Holds Adapter metadataIntegration Repositorybull Holds Adapter metadata
httpltIntegrationServerURLgt
Message
httpltAdapterEngineURLgt
OK Error
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 26
Transport Level Security
Transport Protocol Authentication
IDoc RFC and SNC Client Authentication
Client Authentication
Client Authentication
Client Authentication
Client Authentication
CRAM-MD5
Client Authentication
Client Authentication
Client Authentication
CDIX ndash Adapter HTTPs Client Authentication
RFC RFC and SNC
Plain HTTP HTTPs
FileFTP File Transfer Protocol using SSLTLS
SOAP HTTPsSMTPs (Receiver only)
Mail SMTPs POP3 IMAP4
Marketplace HTTPs
RNIF 20 ndash Adapter HTTPs
RNIF 11 ndash Adapter HTTPs
Supported by
Levels of Security
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 27
Message Level Security
Signature Non-Repudiation
of origin
Non-Repudiation of
receipt
Encryption
CDIX ndash Adapter PKCS7
Technology
XI protocol WS-Security
SOAP-Adapter WS-Security
SMIME
Mail-Adapter SMIME
RNIF 20 ndash Adapter SMIME
RNIF 11 ndash Adapter PKCS7
Supported by
Levels of Security
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 28
Access control list
Restrict access to the runtime environmentfor sender services of type Business Service or Business Systemfor interfaces of these sender services
Restrict access to particular (service) users
Check authorization at runtime
Configure access control in the Integration DirectorySender service Specify authorized users in the configuration of the corresponding (sender) serviceInterface Specify authorized users in the configuration of the relevant sender agreement which contains the interface in the object key
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 29
Dynamic Adapter Configuration
Enable adapters to read write dynamic message headers
Sender Adapter (constructing messages)Attach adapter specific information to message headerExamples File name source file size JMS timestamp mail subjectRead access to these attributes in receiver channel interface determination (routing) mapping
Receiver Adapter (consuming messages)Read attributes to overwrite values of channel configurationExamples Directory Name JMS Priority Mail Sender SOAP target URLSet attributes in mapping orUse attributes from sender in receiver channel
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 30
Sender Adapter Configuration (1)
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 31
Sender Adapter Configuration (2)
Add the filename et al to the message
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 32
Receiver Determination
Determinefilename-dependent receiver
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 33
Receiver Adapter
Store the file withthe name set in the messageattribute
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 34
Monitoring Adapter Engine
After selecting a message bdquoDetailsldquo View
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 35
Monitoring Integration Server
After selecting a message bdquoDisplayldquo
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 36
Remark Future of SAP XI 20 Adapter Engine
SAP XI 20 Adapter Engine is available in SAP NW acute04 and SAP NW 2004s as bdquoPlain J2SE Adapter Engineldquo
Functional scope as in SAP XI 20Adopted to the SAP XI 30 message protocolMinor maintenance issues bug fixes
RecommendationUse where platform requirements or limitations (hardware operating system JVM support) demand it
SAP XI 20 Adapter Engine works with SAP NW acute04 and SAP NW 2004s landscapes too
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 37
Integration Server
PlainJ2SE
Adapter Engine
Partner ConnectivityKitOptional non-central
Adapter EngineCentral Adapter Engine
Process Integration ndash Architecture
Integration Repository Integration Directory System Landscape Directory
Business Process Engine
Integration Engine
Adapter FrameworkMessagingQueuing
Security Handling
Resource
Adapter
Resource
Adapter
Resource
Adapter
Adapter FWMessagingQueuing
Security Handling
Adapter FWMessagingQueuing
Security Handling
PCK Configurationand Monitoring
HTTP
IDoc
Adapter
Adapter
FileDBJMSMarketplace
3rd Party Sys
FileDB
JMSSOAP
SAP ampNon-SAPSystem
FileDBJMSMarketplace
3rd Party Sys
FileDBJMSMarketplace
3rd Party Sys
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 38
SAP Partner Connectivity Kit Overview
SAP 3rdParty Appl PI XI
Smaller Company Subsidiary
SAPPCK
SAPApplication
3rd PartyApplication
Large Business Partner Headquarter
Internet
Enablement of smaller companies subsidiaries to exchange XML documents with their business partnerrsquos headquarterrsquos PI XI
SAPPCK
Providing a platform for development of own JCA Resource Adapters
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 39
SAP PCK ndash Adapters
SAP Partner Connectivity Kit (PCK) is based on Adapter Framework
SAP PCKlsquos objective is to enable XML document exchangebetween PI XI and business partner not using PI XI
SAP PCK also provides an extensible platform for developing and running individual JCA Resource adapters
Communication between PI XI and SAP PCK is via SAP XI messaging protocol
SAP PCK Includes the following adapters FileFTP JDBC JMS SOAP RFC IDoc (once available for SAP PCK) Mail SAP BC
Optionally SAP PCK can host further adapters that are available from SAP or 3rd party adapter providers
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 40
SAP PCK ndash Configuration Mapping
SAP PCK is deployed on stand-alone SAP J2EE Engine (part of SAP Web AS) within business partnerrsquos landscape
Configuration administration monitoring done locally on SAP PCK itself without need for an Integration Directory
Configuration UI provides same bdquolook and feelldquo as configuration UI of Adapter Engine
SAP PCK supports the development of message mappings using an integrated graphical mapping editor
Any source XML structure can be mapped to any target XML structureStandard functions are provided to perform calculations Boolean comparisons text mappings and other transformationsOptionally the standard functions can be enhanced with user-defined functions in Java
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 41
SAP PCK ndash Configuration UI
ConfigurationUI to configure Party Service Communication Channel Sender and Receiver agreementsSample screenshot for configuration of communication channel with adapter type sbquoFile FTPlsquo
Adapter Modules and Development
Summary
Adapter Framework Overview
Adapter Strategy
Agenda
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 43
SAP Exchange Infrastructure - Openness
Integration of SAP and non-SAP applicationsAdapter Framework for comprehensive integration of adaptersAdapters are used for technical connectivityAdapter metadata mappings are stored in Integration Repository
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 44
Dual Strategy
Dual connectivity strategyAdapter Framework for comprehensive integration of adapters to provide technical connectivity including central configurationadministration monitoring of adaptersInteroperability based on open standards (SOAP JMS HTTP(S)) tointeroperate with EAI providers
Value propositionStandardized interfaces allow easy integration of adapters from different partnersMinimum knowledge of end-to-end process integration requiredComprehensive integration avoids redundant maintenance ensures consistency enhances transparancyOpenness to integrate non-SAP applications 3rd party systems etcReduced TCO
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 45
Certification
CertificationSAP NetWeaver Certification of 3rd party adapters based on the adapter framework
Value propositionQuality (stability HA aspects performance etc) of adapters is controlledCertification helps customers to find right solutionQuick and convenient search for a variety of certified products with the online partner and product directory (httpwwwsapcompartnersdirectoriesSearchSolutionepx)Faster implementation time and lower integration costs through the use of tested 3rd party integrationReduced TCO
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 46
Adapter Mappings Metadata in Integration Repository
Adapter mappings and adapter metadata are stored in the Integration Repository
Centralized Integration Repository contains all relevant information for collaborative and integrative processesAll content adheres to open standards Adapters provide technical connectivity
Value propositionUse largest content catalogReduce costs in integration projectsReduce maintenance costsReduced TCO
Adapter Modules and Development
Summary
Adapter Framework Overview
Adapter Strategy
Agenda
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 48
For every adapter it is possible to define generic modules in the module processor possibility to extend the functionality of the specific adapter
Equivalent to the dispatcher classes in the J2SE adapter engine migration and examples
The default module configuration for the certain adapter is displayed in the channel configuration
Modules are EJBlsquos
Sequence matters
Module Processor Concept
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 49
Adapter Module Chain
Custom modulescan be added to default modulechains
Additional configurationparameters canbe specified eachmodule
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 50
Module Processor Documentation
SAP Help Portal (httphelpsapcom)SAP XI Runtime Connectivity Adapters Module ProcessorFeedback Mail to xidocumentationsapcom
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 51
Development Environment
Adapter development deployment and testing is possible on a single machine no full-blown PI XI is required
For testing purposes integration scenarioscan be configured in SAP PCK(eg loopback scenario)
Installation of SAP PCK already contains a sample adapter (including Adapter Meta Data) that should serve as a starting point
SAP Partner ConnectivityKit
Adapter FWMessagingQueuing
Security Handling
Resource
Adapter
PCK Configurationand Monitoring
FileDBJMSMarketplace
3rd Party Sys
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 52
Adapter Development Documentation
SAP Help Portal (httphelpsapcom)SAP XI Runtime Connectivity Partner Connectivity Kit Adapter DevelopmentFeedback Mail to xidocumentationsapcom
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 53
Requirements for Adapters (1)
Num AF Interface Category Description
1 JCA 10 conformance Mandatory Adapter must fulfill JCA 10 requirements (e g deployment) plus optional JCA 15 parts which are used by PI XI
2 AF Message Exchange Mandatory Adapter must be able to receive messages from AF and forward them to connected system and vice versa
3 AF Adapter Specific Modules
Optional SAP XI message and protocol conversion may be done entirely by the adapter or as adapter specific module and being called in the AF module chain context
4 Configuration Services Mandatory Unique configuration approach to manage adapters
5 Administrational Services
Optional Administration and Monitoring
6 Utility Service Mandatory Access to basic J2EE resources e g transactions and multithreading must be under control of J2EE server
7 Logging API Optional Adapters may use their own logging
8 Message Metadata Exchange
Optional Provide structure definition of message payloadIf not supported the definition of message types can be done in the Integration Repository
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 54
Requirements for Adapters (2)
Cluster-enabledConsider side-effects of clustering e g bdquoExactlyOnceInOrderldquo Avoid passing maneuvers
SpecializationBuild connection to exactly one type of business system or industrystandard protocol
DirectnessBuild connection to business system or industry standard protocoldirectly without any intermediate software components
SmoothnessLight-weighted low footprint adapter unnecessary system changes(many new or changed system DLL) should be avoided
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 55
Sample Adapter Source Code
Beside the API documentation a working sample adapter is shipped
The source code is available after installation
Analyzing the code helps understanding the Adapter Framework
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 56
Adapter Metadata
Adapter Metadata (AMD)XML file defines all configuration parameterseach adapter
AMD can be uploaded intoIntegration Iepositoryand SAP PCK
Configurationparameters are renderedinto the graphicalconfiguaration frontend
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 57
Adapter Metadata Fragment I
ltAdapterTypeMetaData version=09gt
ltTypegtNAESBltTypegt
ltInboundgt
ltTransportProtocolgt
ltChannelAttributesgt
ltAttributeGroupgt
ltNamegtCRYPTConfigurationltNamegt
ltGuiLabelsgtltLabel language=ENgtCryptographic ConfigurationltLabelgtltGuiLabelsgt
ltAttributeReferencegtltReferenceNamegtCRYPTUseSigningltReferenceNamegt
ltInboundgt
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 58
Adapter Metadata Fragment II
ltAttributegt
ltNamegtCRYPTUseSigningltNamegt
ltDataTypegtxsdbooleanltDataTypegt
ltGuiLabelsgt
ltLabel language=ENgtUse SigningltLabelgt
ltLabel language=DEgtVerwendung von SignierungltLabelgt
ltGuiLabelsgt
ltAttributegt
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 59
Adapter Configuration
Configuration attribute of type boolean is rendered to a check-box
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 60
Adapter Metadata Upload (PCK)
Integration Repositorydoes not exist in case ofSAP PCK installations
The upload mechanismfor Adaper Meta Datafor SAP PCK installationsrequires additonalparameters
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 61
AF CPA Cache
The Adapter configuration is deployed from the configuration time(SAP PCK or Integration Directory) to the J2EE service CPACache(Collaboration Profile Agreement)
The Adapter configuration can be accessed at runtime from withinadapter modules or JCA resource adapters via the CPACache API
The two main use cases are implemented inLookupManager to retrieve adapter configuation andNormalizationManager to retrieve Party information
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 62
Packaging Adapter Components
SAP recommends to use SAP Software Deployment Manager (SDM) for deployment
Software Delivery Archives (SDA) can contain software components of different types (eg applications libraries)
Detailed version information and dependencies to other components simplify program management
Adapter Modules and Development
Summary
Adapter Framework Overview
Adapter Strategy
Agenda
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 64
Summary
Adapter Framework runs on J2EE Stack of SAP Web AS
Adapter Framework is platform for Adapter Engine and SAP PCK
Adapter Framework provides an extensible platform for developing and running adapters
Adapter Engine utilizes central configuration monitoring administration
Dual connectivity strategyAdapter Framework for comprehensive integration of adaptersInteroperability via open standards to interop with EAI providers
SAP NetWeaver Certification for adapters based on Adapter Framework available
Adapter mappings metadata stored in Integration Repository
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 25
Configurationcache
Adapter Engine
ISRuntime
AdapterSender
AdapterReceiver
Adapter Engine in SAP J2EE
Q
Administration
Security
Monitoring
Adapter-Specific
ComponentServices
TracingLogging
Module ProcessorEIS
Channel
acuteMessaging
Configcache
End-to-End MonitoringMessage flow over all components applications
Runtime Workbenchbull Uis for adminstration
monitoring
Integration Builder Directory
Receiver determinationbull Party-gtService-gtAction
Channel Definitionbull Adapter Enginebull Adapter Typebull Message Protocolbull Transport Protocolbull Securitybull Channel Configuration
(Sender Receiver Agreementbull PartyServiceAction lt-gt Channel
ConfigurationMaster
System Landscape Directorybull Holds component description
including address data
AdapterFramework
Integration Repositorybull Holds Adapter metadataIntegration Repositorybull Holds Adapter metadata
httpltIntegrationServerURLgt
Message
httpltAdapterEngineURLgt
OK Error
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 26
Transport Level Security
Transport Protocol Authentication
IDoc RFC and SNC Client Authentication
Client Authentication
Client Authentication
Client Authentication
Client Authentication
CRAM-MD5
Client Authentication
Client Authentication
Client Authentication
CDIX ndash Adapter HTTPs Client Authentication
RFC RFC and SNC
Plain HTTP HTTPs
FileFTP File Transfer Protocol using SSLTLS
SOAP HTTPsSMTPs (Receiver only)
Mail SMTPs POP3 IMAP4
Marketplace HTTPs
RNIF 20 ndash Adapter HTTPs
RNIF 11 ndash Adapter HTTPs
Supported by
Levels of Security
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 27
Message Level Security
Signature Non-Repudiation
of origin
Non-Repudiation of
receipt
Encryption
CDIX ndash Adapter PKCS7
Technology
XI protocol WS-Security
SOAP-Adapter WS-Security
SMIME
Mail-Adapter SMIME
RNIF 20 ndash Adapter SMIME
RNIF 11 ndash Adapter PKCS7
Supported by
Levels of Security
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 28
Access control list
Restrict access to the runtime environmentfor sender services of type Business Service or Business Systemfor interfaces of these sender services
Restrict access to particular (service) users
Check authorization at runtime
Configure access control in the Integration DirectorySender service Specify authorized users in the configuration of the corresponding (sender) serviceInterface Specify authorized users in the configuration of the relevant sender agreement which contains the interface in the object key
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 29
Dynamic Adapter Configuration
Enable adapters to read write dynamic message headers
Sender Adapter (constructing messages)Attach adapter specific information to message headerExamples File name source file size JMS timestamp mail subjectRead access to these attributes in receiver channel interface determination (routing) mapping
Receiver Adapter (consuming messages)Read attributes to overwrite values of channel configurationExamples Directory Name JMS Priority Mail Sender SOAP target URLSet attributes in mapping orUse attributes from sender in receiver channel
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 30
Sender Adapter Configuration (1)
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 31
Sender Adapter Configuration (2)
Add the filename et al to the message
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 32
Receiver Determination
Determinefilename-dependent receiver
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 33
Receiver Adapter
Store the file withthe name set in the messageattribute
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 34
Monitoring Adapter Engine
After selecting a message bdquoDetailsldquo View
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 35
Monitoring Integration Server
After selecting a message bdquoDisplayldquo
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 36
Remark Future of SAP XI 20 Adapter Engine
SAP XI 20 Adapter Engine is available in SAP NW acute04 and SAP NW 2004s as bdquoPlain J2SE Adapter Engineldquo
Functional scope as in SAP XI 20Adopted to the SAP XI 30 message protocolMinor maintenance issues bug fixes
RecommendationUse where platform requirements or limitations (hardware operating system JVM support) demand it
SAP XI 20 Adapter Engine works with SAP NW acute04 and SAP NW 2004s landscapes too
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 37
Integration Server
PlainJ2SE
Adapter Engine
Partner ConnectivityKitOptional non-central
Adapter EngineCentral Adapter Engine
Process Integration ndash Architecture
Integration Repository Integration Directory System Landscape Directory
Business Process Engine
Integration Engine
Adapter FrameworkMessagingQueuing
Security Handling
Resource
Adapter
Resource
Adapter
Resource
Adapter
Adapter FWMessagingQueuing
Security Handling
Adapter FWMessagingQueuing
Security Handling
PCK Configurationand Monitoring
HTTP
IDoc
Adapter
Adapter
FileDBJMSMarketplace
3rd Party Sys
FileDB
JMSSOAP
SAP ampNon-SAPSystem
FileDBJMSMarketplace
3rd Party Sys
FileDBJMSMarketplace
3rd Party Sys
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 38
SAP Partner Connectivity Kit Overview
SAP 3rdParty Appl PI XI
Smaller Company Subsidiary
SAPPCK
SAPApplication
3rd PartyApplication
Large Business Partner Headquarter
Internet
Enablement of smaller companies subsidiaries to exchange XML documents with their business partnerrsquos headquarterrsquos PI XI
SAPPCK
Providing a platform for development of own JCA Resource Adapters
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 39
SAP PCK ndash Adapters
SAP Partner Connectivity Kit (PCK) is based on Adapter Framework
SAP PCKlsquos objective is to enable XML document exchangebetween PI XI and business partner not using PI XI
SAP PCK also provides an extensible platform for developing and running individual JCA Resource adapters
Communication between PI XI and SAP PCK is via SAP XI messaging protocol
SAP PCK Includes the following adapters FileFTP JDBC JMS SOAP RFC IDoc (once available for SAP PCK) Mail SAP BC
Optionally SAP PCK can host further adapters that are available from SAP or 3rd party adapter providers
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 40
SAP PCK ndash Configuration Mapping
SAP PCK is deployed on stand-alone SAP J2EE Engine (part of SAP Web AS) within business partnerrsquos landscape
Configuration administration monitoring done locally on SAP PCK itself without need for an Integration Directory
Configuration UI provides same bdquolook and feelldquo as configuration UI of Adapter Engine
SAP PCK supports the development of message mappings using an integrated graphical mapping editor
Any source XML structure can be mapped to any target XML structureStandard functions are provided to perform calculations Boolean comparisons text mappings and other transformationsOptionally the standard functions can be enhanced with user-defined functions in Java
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 41
SAP PCK ndash Configuration UI
ConfigurationUI to configure Party Service Communication Channel Sender and Receiver agreementsSample screenshot for configuration of communication channel with adapter type sbquoFile FTPlsquo
Adapter Modules and Development
Summary
Adapter Framework Overview
Adapter Strategy
Agenda
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 43
SAP Exchange Infrastructure - Openness
Integration of SAP and non-SAP applicationsAdapter Framework for comprehensive integration of adaptersAdapters are used for technical connectivityAdapter metadata mappings are stored in Integration Repository
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 44
Dual Strategy
Dual connectivity strategyAdapter Framework for comprehensive integration of adapters to provide technical connectivity including central configurationadministration monitoring of adaptersInteroperability based on open standards (SOAP JMS HTTP(S)) tointeroperate with EAI providers
Value propositionStandardized interfaces allow easy integration of adapters from different partnersMinimum knowledge of end-to-end process integration requiredComprehensive integration avoids redundant maintenance ensures consistency enhances transparancyOpenness to integrate non-SAP applications 3rd party systems etcReduced TCO
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 45
Certification
CertificationSAP NetWeaver Certification of 3rd party adapters based on the adapter framework
Value propositionQuality (stability HA aspects performance etc) of adapters is controlledCertification helps customers to find right solutionQuick and convenient search for a variety of certified products with the online partner and product directory (httpwwwsapcompartnersdirectoriesSearchSolutionepx)Faster implementation time and lower integration costs through the use of tested 3rd party integrationReduced TCO
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 46
Adapter Mappings Metadata in Integration Repository
Adapter mappings and adapter metadata are stored in the Integration Repository
Centralized Integration Repository contains all relevant information for collaborative and integrative processesAll content adheres to open standards Adapters provide technical connectivity
Value propositionUse largest content catalogReduce costs in integration projectsReduce maintenance costsReduced TCO
Adapter Modules and Development
Summary
Adapter Framework Overview
Adapter Strategy
Agenda
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 48
For every adapter it is possible to define generic modules in the module processor possibility to extend the functionality of the specific adapter
Equivalent to the dispatcher classes in the J2SE adapter engine migration and examples
The default module configuration for the certain adapter is displayed in the channel configuration
Modules are EJBlsquos
Sequence matters
Module Processor Concept
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 49
Adapter Module Chain
Custom modulescan be added to default modulechains
Additional configurationparameters canbe specified eachmodule
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 50
Module Processor Documentation
SAP Help Portal (httphelpsapcom)SAP XI Runtime Connectivity Adapters Module ProcessorFeedback Mail to xidocumentationsapcom
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 51
Development Environment
Adapter development deployment and testing is possible on a single machine no full-blown PI XI is required
For testing purposes integration scenarioscan be configured in SAP PCK(eg loopback scenario)
Installation of SAP PCK already contains a sample adapter (including Adapter Meta Data) that should serve as a starting point
SAP Partner ConnectivityKit
Adapter FWMessagingQueuing
Security Handling
Resource
Adapter
PCK Configurationand Monitoring
FileDBJMSMarketplace
3rd Party Sys
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 52
Adapter Development Documentation
SAP Help Portal (httphelpsapcom)SAP XI Runtime Connectivity Partner Connectivity Kit Adapter DevelopmentFeedback Mail to xidocumentationsapcom
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 53
Requirements for Adapters (1)
Num AF Interface Category Description
1 JCA 10 conformance Mandatory Adapter must fulfill JCA 10 requirements (e g deployment) plus optional JCA 15 parts which are used by PI XI
2 AF Message Exchange Mandatory Adapter must be able to receive messages from AF and forward them to connected system and vice versa
3 AF Adapter Specific Modules
Optional SAP XI message and protocol conversion may be done entirely by the adapter or as adapter specific module and being called in the AF module chain context
4 Configuration Services Mandatory Unique configuration approach to manage adapters
5 Administrational Services
Optional Administration and Monitoring
6 Utility Service Mandatory Access to basic J2EE resources e g transactions and multithreading must be under control of J2EE server
7 Logging API Optional Adapters may use their own logging
8 Message Metadata Exchange
Optional Provide structure definition of message payloadIf not supported the definition of message types can be done in the Integration Repository
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 54
Requirements for Adapters (2)
Cluster-enabledConsider side-effects of clustering e g bdquoExactlyOnceInOrderldquo Avoid passing maneuvers
SpecializationBuild connection to exactly one type of business system or industrystandard protocol
DirectnessBuild connection to business system or industry standard protocoldirectly without any intermediate software components
SmoothnessLight-weighted low footprint adapter unnecessary system changes(many new or changed system DLL) should be avoided
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 55
Sample Adapter Source Code
Beside the API documentation a working sample adapter is shipped
The source code is available after installation
Analyzing the code helps understanding the Adapter Framework
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 56
Adapter Metadata
Adapter Metadata (AMD)XML file defines all configuration parameterseach adapter
AMD can be uploaded intoIntegration Iepositoryand SAP PCK
Configurationparameters are renderedinto the graphicalconfiguaration frontend
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 57
Adapter Metadata Fragment I
ltAdapterTypeMetaData version=09gt
ltTypegtNAESBltTypegt
ltInboundgt
ltTransportProtocolgt
ltChannelAttributesgt
ltAttributeGroupgt
ltNamegtCRYPTConfigurationltNamegt
ltGuiLabelsgtltLabel language=ENgtCryptographic ConfigurationltLabelgtltGuiLabelsgt
ltAttributeReferencegtltReferenceNamegtCRYPTUseSigningltReferenceNamegt
ltInboundgt
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 58
Adapter Metadata Fragment II
ltAttributegt
ltNamegtCRYPTUseSigningltNamegt
ltDataTypegtxsdbooleanltDataTypegt
ltGuiLabelsgt
ltLabel language=ENgtUse SigningltLabelgt
ltLabel language=DEgtVerwendung von SignierungltLabelgt
ltGuiLabelsgt
ltAttributegt
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 59
Adapter Configuration
Configuration attribute of type boolean is rendered to a check-box
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 60
Adapter Metadata Upload (PCK)
Integration Repositorydoes not exist in case ofSAP PCK installations
The upload mechanismfor Adaper Meta Datafor SAP PCK installationsrequires additonalparameters
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 61
AF CPA Cache
The Adapter configuration is deployed from the configuration time(SAP PCK or Integration Directory) to the J2EE service CPACache(Collaboration Profile Agreement)
The Adapter configuration can be accessed at runtime from withinadapter modules or JCA resource adapters via the CPACache API
The two main use cases are implemented inLookupManager to retrieve adapter configuation andNormalizationManager to retrieve Party information
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 62
Packaging Adapter Components
SAP recommends to use SAP Software Deployment Manager (SDM) for deployment
Software Delivery Archives (SDA) can contain software components of different types (eg applications libraries)
Detailed version information and dependencies to other components simplify program management
Adapter Modules and Development
Summary
Adapter Framework Overview
Adapter Strategy
Agenda
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 64
Summary
Adapter Framework runs on J2EE Stack of SAP Web AS
Adapter Framework is platform for Adapter Engine and SAP PCK
Adapter Framework provides an extensible platform for developing and running adapters
Adapter Engine utilizes central configuration monitoring administration
Dual connectivity strategyAdapter Framework for comprehensive integration of adaptersInteroperability via open standards to interop with EAI providers
SAP NetWeaver Certification for adapters based on Adapter Framework available
Adapter mappings metadata stored in Integration Repository
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 26
Transport Level Security
Transport Protocol Authentication
IDoc RFC and SNC Client Authentication
Client Authentication
Client Authentication
Client Authentication
Client Authentication
CRAM-MD5
Client Authentication
Client Authentication
Client Authentication
CDIX ndash Adapter HTTPs Client Authentication
RFC RFC and SNC
Plain HTTP HTTPs
FileFTP File Transfer Protocol using SSLTLS
SOAP HTTPsSMTPs (Receiver only)
Mail SMTPs POP3 IMAP4
Marketplace HTTPs
RNIF 20 ndash Adapter HTTPs
RNIF 11 ndash Adapter HTTPs
Supported by
Levels of Security
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 27
Message Level Security
Signature Non-Repudiation
of origin
Non-Repudiation of
receipt
Encryption
CDIX ndash Adapter PKCS7
Technology
XI protocol WS-Security
SOAP-Adapter WS-Security
SMIME
Mail-Adapter SMIME
RNIF 20 ndash Adapter SMIME
RNIF 11 ndash Adapter PKCS7
Supported by
Levels of Security
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 28
Access control list
Restrict access to the runtime environmentfor sender services of type Business Service or Business Systemfor interfaces of these sender services
Restrict access to particular (service) users
Check authorization at runtime
Configure access control in the Integration DirectorySender service Specify authorized users in the configuration of the corresponding (sender) serviceInterface Specify authorized users in the configuration of the relevant sender agreement which contains the interface in the object key
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 29
Dynamic Adapter Configuration
Enable adapters to read write dynamic message headers
Sender Adapter (constructing messages)Attach adapter specific information to message headerExamples File name source file size JMS timestamp mail subjectRead access to these attributes in receiver channel interface determination (routing) mapping
Receiver Adapter (consuming messages)Read attributes to overwrite values of channel configurationExamples Directory Name JMS Priority Mail Sender SOAP target URLSet attributes in mapping orUse attributes from sender in receiver channel
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 30
Sender Adapter Configuration (1)
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 31
Sender Adapter Configuration (2)
Add the filename et al to the message
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 32
Receiver Determination
Determinefilename-dependent receiver
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 33
Receiver Adapter
Store the file withthe name set in the messageattribute
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 34
Monitoring Adapter Engine
After selecting a message bdquoDetailsldquo View
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 35
Monitoring Integration Server
After selecting a message bdquoDisplayldquo
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 36
Remark Future of SAP XI 20 Adapter Engine
SAP XI 20 Adapter Engine is available in SAP NW acute04 and SAP NW 2004s as bdquoPlain J2SE Adapter Engineldquo
Functional scope as in SAP XI 20Adopted to the SAP XI 30 message protocolMinor maintenance issues bug fixes
RecommendationUse where platform requirements or limitations (hardware operating system JVM support) demand it
SAP XI 20 Adapter Engine works with SAP NW acute04 and SAP NW 2004s landscapes too
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 37
Integration Server
PlainJ2SE
Adapter Engine
Partner ConnectivityKitOptional non-central
Adapter EngineCentral Adapter Engine
Process Integration ndash Architecture
Integration Repository Integration Directory System Landscape Directory
Business Process Engine
Integration Engine
Adapter FrameworkMessagingQueuing
Security Handling
Resource
Adapter
Resource
Adapter
Resource
Adapter
Adapter FWMessagingQueuing
Security Handling
Adapter FWMessagingQueuing
Security Handling
PCK Configurationand Monitoring
HTTP
IDoc
Adapter
Adapter
FileDBJMSMarketplace
3rd Party Sys
FileDB
JMSSOAP
SAP ampNon-SAPSystem
FileDBJMSMarketplace
3rd Party Sys
FileDBJMSMarketplace
3rd Party Sys
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 38
SAP Partner Connectivity Kit Overview
SAP 3rdParty Appl PI XI
Smaller Company Subsidiary
SAPPCK
SAPApplication
3rd PartyApplication
Large Business Partner Headquarter
Internet
Enablement of smaller companies subsidiaries to exchange XML documents with their business partnerrsquos headquarterrsquos PI XI
SAPPCK
Providing a platform for development of own JCA Resource Adapters
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 39
SAP PCK ndash Adapters
SAP Partner Connectivity Kit (PCK) is based on Adapter Framework
SAP PCKlsquos objective is to enable XML document exchangebetween PI XI and business partner not using PI XI
SAP PCK also provides an extensible platform for developing and running individual JCA Resource adapters
Communication between PI XI and SAP PCK is via SAP XI messaging protocol
SAP PCK Includes the following adapters FileFTP JDBC JMS SOAP RFC IDoc (once available for SAP PCK) Mail SAP BC
Optionally SAP PCK can host further adapters that are available from SAP or 3rd party adapter providers
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 40
SAP PCK ndash Configuration Mapping
SAP PCK is deployed on stand-alone SAP J2EE Engine (part of SAP Web AS) within business partnerrsquos landscape
Configuration administration monitoring done locally on SAP PCK itself without need for an Integration Directory
Configuration UI provides same bdquolook and feelldquo as configuration UI of Adapter Engine
SAP PCK supports the development of message mappings using an integrated graphical mapping editor
Any source XML structure can be mapped to any target XML structureStandard functions are provided to perform calculations Boolean comparisons text mappings and other transformationsOptionally the standard functions can be enhanced with user-defined functions in Java
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 41
SAP PCK ndash Configuration UI
ConfigurationUI to configure Party Service Communication Channel Sender and Receiver agreementsSample screenshot for configuration of communication channel with adapter type sbquoFile FTPlsquo
Adapter Modules and Development
Summary
Adapter Framework Overview
Adapter Strategy
Agenda
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 43
SAP Exchange Infrastructure - Openness
Integration of SAP and non-SAP applicationsAdapter Framework for comprehensive integration of adaptersAdapters are used for technical connectivityAdapter metadata mappings are stored in Integration Repository
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 44
Dual Strategy
Dual connectivity strategyAdapter Framework for comprehensive integration of adapters to provide technical connectivity including central configurationadministration monitoring of adaptersInteroperability based on open standards (SOAP JMS HTTP(S)) tointeroperate with EAI providers
Value propositionStandardized interfaces allow easy integration of adapters from different partnersMinimum knowledge of end-to-end process integration requiredComprehensive integration avoids redundant maintenance ensures consistency enhances transparancyOpenness to integrate non-SAP applications 3rd party systems etcReduced TCO
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 45
Certification
CertificationSAP NetWeaver Certification of 3rd party adapters based on the adapter framework
Value propositionQuality (stability HA aspects performance etc) of adapters is controlledCertification helps customers to find right solutionQuick and convenient search for a variety of certified products with the online partner and product directory (httpwwwsapcompartnersdirectoriesSearchSolutionepx)Faster implementation time and lower integration costs through the use of tested 3rd party integrationReduced TCO
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 46
Adapter Mappings Metadata in Integration Repository
Adapter mappings and adapter metadata are stored in the Integration Repository
Centralized Integration Repository contains all relevant information for collaborative and integrative processesAll content adheres to open standards Adapters provide technical connectivity
Value propositionUse largest content catalogReduce costs in integration projectsReduce maintenance costsReduced TCO
Adapter Modules and Development
Summary
Adapter Framework Overview
Adapter Strategy
Agenda
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 48
For every adapter it is possible to define generic modules in the module processor possibility to extend the functionality of the specific adapter
Equivalent to the dispatcher classes in the J2SE adapter engine migration and examples
The default module configuration for the certain adapter is displayed in the channel configuration
Modules are EJBlsquos
Sequence matters
Module Processor Concept
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 49
Adapter Module Chain
Custom modulescan be added to default modulechains
Additional configurationparameters canbe specified eachmodule
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 50
Module Processor Documentation
SAP Help Portal (httphelpsapcom)SAP XI Runtime Connectivity Adapters Module ProcessorFeedback Mail to xidocumentationsapcom
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 51
Development Environment
Adapter development deployment and testing is possible on a single machine no full-blown PI XI is required
For testing purposes integration scenarioscan be configured in SAP PCK(eg loopback scenario)
Installation of SAP PCK already contains a sample adapter (including Adapter Meta Data) that should serve as a starting point
SAP Partner ConnectivityKit
Adapter FWMessagingQueuing
Security Handling
Resource
Adapter
PCK Configurationand Monitoring
FileDBJMSMarketplace
3rd Party Sys
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 52
Adapter Development Documentation
SAP Help Portal (httphelpsapcom)SAP XI Runtime Connectivity Partner Connectivity Kit Adapter DevelopmentFeedback Mail to xidocumentationsapcom
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 53
Requirements for Adapters (1)
Num AF Interface Category Description
1 JCA 10 conformance Mandatory Adapter must fulfill JCA 10 requirements (e g deployment) plus optional JCA 15 parts which are used by PI XI
2 AF Message Exchange Mandatory Adapter must be able to receive messages from AF and forward them to connected system and vice versa
3 AF Adapter Specific Modules
Optional SAP XI message and protocol conversion may be done entirely by the adapter or as adapter specific module and being called in the AF module chain context
4 Configuration Services Mandatory Unique configuration approach to manage adapters
5 Administrational Services
Optional Administration and Monitoring
6 Utility Service Mandatory Access to basic J2EE resources e g transactions and multithreading must be under control of J2EE server
7 Logging API Optional Adapters may use their own logging
8 Message Metadata Exchange
Optional Provide structure definition of message payloadIf not supported the definition of message types can be done in the Integration Repository
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 54
Requirements for Adapters (2)
Cluster-enabledConsider side-effects of clustering e g bdquoExactlyOnceInOrderldquo Avoid passing maneuvers
SpecializationBuild connection to exactly one type of business system or industrystandard protocol
DirectnessBuild connection to business system or industry standard protocoldirectly without any intermediate software components
SmoothnessLight-weighted low footprint adapter unnecessary system changes(many new or changed system DLL) should be avoided
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 55
Sample Adapter Source Code
Beside the API documentation a working sample adapter is shipped
The source code is available after installation
Analyzing the code helps understanding the Adapter Framework
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 56
Adapter Metadata
Adapter Metadata (AMD)XML file defines all configuration parameterseach adapter
AMD can be uploaded intoIntegration Iepositoryand SAP PCK
Configurationparameters are renderedinto the graphicalconfiguaration frontend
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 57
Adapter Metadata Fragment I
ltAdapterTypeMetaData version=09gt
ltTypegtNAESBltTypegt
ltInboundgt
ltTransportProtocolgt
ltChannelAttributesgt
ltAttributeGroupgt
ltNamegtCRYPTConfigurationltNamegt
ltGuiLabelsgtltLabel language=ENgtCryptographic ConfigurationltLabelgtltGuiLabelsgt
ltAttributeReferencegtltReferenceNamegtCRYPTUseSigningltReferenceNamegt
ltInboundgt
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 58
Adapter Metadata Fragment II
ltAttributegt
ltNamegtCRYPTUseSigningltNamegt
ltDataTypegtxsdbooleanltDataTypegt
ltGuiLabelsgt
ltLabel language=ENgtUse SigningltLabelgt
ltLabel language=DEgtVerwendung von SignierungltLabelgt
ltGuiLabelsgt
ltAttributegt
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 59
Adapter Configuration
Configuration attribute of type boolean is rendered to a check-box
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 60
Adapter Metadata Upload (PCK)
Integration Repositorydoes not exist in case ofSAP PCK installations
The upload mechanismfor Adaper Meta Datafor SAP PCK installationsrequires additonalparameters
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 61
AF CPA Cache
The Adapter configuration is deployed from the configuration time(SAP PCK or Integration Directory) to the J2EE service CPACache(Collaboration Profile Agreement)
The Adapter configuration can be accessed at runtime from withinadapter modules or JCA resource adapters via the CPACache API
The two main use cases are implemented inLookupManager to retrieve adapter configuation andNormalizationManager to retrieve Party information
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 62
Packaging Adapter Components
SAP recommends to use SAP Software Deployment Manager (SDM) for deployment
Software Delivery Archives (SDA) can contain software components of different types (eg applications libraries)
Detailed version information and dependencies to other components simplify program management
Adapter Modules and Development
Summary
Adapter Framework Overview
Adapter Strategy
Agenda
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 64
Summary
Adapter Framework runs on J2EE Stack of SAP Web AS
Adapter Framework is platform for Adapter Engine and SAP PCK
Adapter Framework provides an extensible platform for developing and running adapters
Adapter Engine utilizes central configuration monitoring administration
Dual connectivity strategyAdapter Framework for comprehensive integration of adaptersInteroperability via open standards to interop with EAI providers
SAP NetWeaver Certification for adapters based on Adapter Framework available
Adapter mappings metadata stored in Integration Repository
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 27
Message Level Security
Signature Non-Repudiation
of origin
Non-Repudiation of
receipt
Encryption
CDIX ndash Adapter PKCS7
Technology
XI protocol WS-Security
SOAP-Adapter WS-Security
SMIME
Mail-Adapter SMIME
RNIF 20 ndash Adapter SMIME
RNIF 11 ndash Adapter PKCS7
Supported by
Levels of Security
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 28
Access control list
Restrict access to the runtime environmentfor sender services of type Business Service or Business Systemfor interfaces of these sender services
Restrict access to particular (service) users
Check authorization at runtime
Configure access control in the Integration DirectorySender service Specify authorized users in the configuration of the corresponding (sender) serviceInterface Specify authorized users in the configuration of the relevant sender agreement which contains the interface in the object key
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 29
Dynamic Adapter Configuration
Enable adapters to read write dynamic message headers
Sender Adapter (constructing messages)Attach adapter specific information to message headerExamples File name source file size JMS timestamp mail subjectRead access to these attributes in receiver channel interface determination (routing) mapping
Receiver Adapter (consuming messages)Read attributes to overwrite values of channel configurationExamples Directory Name JMS Priority Mail Sender SOAP target URLSet attributes in mapping orUse attributes from sender in receiver channel
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 30
Sender Adapter Configuration (1)
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 31
Sender Adapter Configuration (2)
Add the filename et al to the message
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 32
Receiver Determination
Determinefilename-dependent receiver
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 33
Receiver Adapter
Store the file withthe name set in the messageattribute
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 34
Monitoring Adapter Engine
After selecting a message bdquoDetailsldquo View
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 35
Monitoring Integration Server
After selecting a message bdquoDisplayldquo
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 36
Remark Future of SAP XI 20 Adapter Engine
SAP XI 20 Adapter Engine is available in SAP NW acute04 and SAP NW 2004s as bdquoPlain J2SE Adapter Engineldquo
Functional scope as in SAP XI 20Adopted to the SAP XI 30 message protocolMinor maintenance issues bug fixes
RecommendationUse where platform requirements or limitations (hardware operating system JVM support) demand it
SAP XI 20 Adapter Engine works with SAP NW acute04 and SAP NW 2004s landscapes too
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 37
Integration Server
PlainJ2SE
Adapter Engine
Partner ConnectivityKitOptional non-central
Adapter EngineCentral Adapter Engine
Process Integration ndash Architecture
Integration Repository Integration Directory System Landscape Directory
Business Process Engine
Integration Engine
Adapter FrameworkMessagingQueuing
Security Handling
Resource
Adapter
Resource
Adapter
Resource
Adapter
Adapter FWMessagingQueuing
Security Handling
Adapter FWMessagingQueuing
Security Handling
PCK Configurationand Monitoring
HTTP
IDoc
Adapter
Adapter
FileDBJMSMarketplace
3rd Party Sys
FileDB
JMSSOAP
SAP ampNon-SAPSystem
FileDBJMSMarketplace
3rd Party Sys
FileDBJMSMarketplace
3rd Party Sys
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 38
SAP Partner Connectivity Kit Overview
SAP 3rdParty Appl PI XI
Smaller Company Subsidiary
SAPPCK
SAPApplication
3rd PartyApplication
Large Business Partner Headquarter
Internet
Enablement of smaller companies subsidiaries to exchange XML documents with their business partnerrsquos headquarterrsquos PI XI
SAPPCK
Providing a platform for development of own JCA Resource Adapters
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 39
SAP PCK ndash Adapters
SAP Partner Connectivity Kit (PCK) is based on Adapter Framework
SAP PCKlsquos objective is to enable XML document exchangebetween PI XI and business partner not using PI XI
SAP PCK also provides an extensible platform for developing and running individual JCA Resource adapters
Communication between PI XI and SAP PCK is via SAP XI messaging protocol
SAP PCK Includes the following adapters FileFTP JDBC JMS SOAP RFC IDoc (once available for SAP PCK) Mail SAP BC
Optionally SAP PCK can host further adapters that are available from SAP or 3rd party adapter providers
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 40
SAP PCK ndash Configuration Mapping
SAP PCK is deployed on stand-alone SAP J2EE Engine (part of SAP Web AS) within business partnerrsquos landscape
Configuration administration monitoring done locally on SAP PCK itself without need for an Integration Directory
Configuration UI provides same bdquolook and feelldquo as configuration UI of Adapter Engine
SAP PCK supports the development of message mappings using an integrated graphical mapping editor
Any source XML structure can be mapped to any target XML structureStandard functions are provided to perform calculations Boolean comparisons text mappings and other transformationsOptionally the standard functions can be enhanced with user-defined functions in Java
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 41
SAP PCK ndash Configuration UI
ConfigurationUI to configure Party Service Communication Channel Sender and Receiver agreementsSample screenshot for configuration of communication channel with adapter type sbquoFile FTPlsquo
Adapter Modules and Development
Summary
Adapter Framework Overview
Adapter Strategy
Agenda
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 43
SAP Exchange Infrastructure - Openness
Integration of SAP and non-SAP applicationsAdapter Framework for comprehensive integration of adaptersAdapters are used for technical connectivityAdapter metadata mappings are stored in Integration Repository
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 44
Dual Strategy
Dual connectivity strategyAdapter Framework for comprehensive integration of adapters to provide technical connectivity including central configurationadministration monitoring of adaptersInteroperability based on open standards (SOAP JMS HTTP(S)) tointeroperate with EAI providers
Value propositionStandardized interfaces allow easy integration of adapters from different partnersMinimum knowledge of end-to-end process integration requiredComprehensive integration avoids redundant maintenance ensures consistency enhances transparancyOpenness to integrate non-SAP applications 3rd party systems etcReduced TCO
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 45
Certification
CertificationSAP NetWeaver Certification of 3rd party adapters based on the adapter framework
Value propositionQuality (stability HA aspects performance etc) of adapters is controlledCertification helps customers to find right solutionQuick and convenient search for a variety of certified products with the online partner and product directory (httpwwwsapcompartnersdirectoriesSearchSolutionepx)Faster implementation time and lower integration costs through the use of tested 3rd party integrationReduced TCO
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 46
Adapter Mappings Metadata in Integration Repository
Adapter mappings and adapter metadata are stored in the Integration Repository
Centralized Integration Repository contains all relevant information for collaborative and integrative processesAll content adheres to open standards Adapters provide technical connectivity
Value propositionUse largest content catalogReduce costs in integration projectsReduce maintenance costsReduced TCO
Adapter Modules and Development
Summary
Adapter Framework Overview
Adapter Strategy
Agenda
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 48
For every adapter it is possible to define generic modules in the module processor possibility to extend the functionality of the specific adapter
Equivalent to the dispatcher classes in the J2SE adapter engine migration and examples
The default module configuration for the certain adapter is displayed in the channel configuration
Modules are EJBlsquos
Sequence matters
Module Processor Concept
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 49
Adapter Module Chain
Custom modulescan be added to default modulechains
Additional configurationparameters canbe specified eachmodule
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 50
Module Processor Documentation
SAP Help Portal (httphelpsapcom)SAP XI Runtime Connectivity Adapters Module ProcessorFeedback Mail to xidocumentationsapcom
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 51
Development Environment
Adapter development deployment and testing is possible on a single machine no full-blown PI XI is required
For testing purposes integration scenarioscan be configured in SAP PCK(eg loopback scenario)
Installation of SAP PCK already contains a sample adapter (including Adapter Meta Data) that should serve as a starting point
SAP Partner ConnectivityKit
Adapter FWMessagingQueuing
Security Handling
Resource
Adapter
PCK Configurationand Monitoring
FileDBJMSMarketplace
3rd Party Sys
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 52
Adapter Development Documentation
SAP Help Portal (httphelpsapcom)SAP XI Runtime Connectivity Partner Connectivity Kit Adapter DevelopmentFeedback Mail to xidocumentationsapcom
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 53
Requirements for Adapters (1)
Num AF Interface Category Description
1 JCA 10 conformance Mandatory Adapter must fulfill JCA 10 requirements (e g deployment) plus optional JCA 15 parts which are used by PI XI
2 AF Message Exchange Mandatory Adapter must be able to receive messages from AF and forward them to connected system and vice versa
3 AF Adapter Specific Modules
Optional SAP XI message and protocol conversion may be done entirely by the adapter or as adapter specific module and being called in the AF module chain context
4 Configuration Services Mandatory Unique configuration approach to manage adapters
5 Administrational Services
Optional Administration and Monitoring
6 Utility Service Mandatory Access to basic J2EE resources e g transactions and multithreading must be under control of J2EE server
7 Logging API Optional Adapters may use their own logging
8 Message Metadata Exchange
Optional Provide structure definition of message payloadIf not supported the definition of message types can be done in the Integration Repository
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 54
Requirements for Adapters (2)
Cluster-enabledConsider side-effects of clustering e g bdquoExactlyOnceInOrderldquo Avoid passing maneuvers
SpecializationBuild connection to exactly one type of business system or industrystandard protocol
DirectnessBuild connection to business system or industry standard protocoldirectly without any intermediate software components
SmoothnessLight-weighted low footprint adapter unnecessary system changes(many new or changed system DLL) should be avoided
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 55
Sample Adapter Source Code
Beside the API documentation a working sample adapter is shipped
The source code is available after installation
Analyzing the code helps understanding the Adapter Framework
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 56
Adapter Metadata
Adapter Metadata (AMD)XML file defines all configuration parameterseach adapter
AMD can be uploaded intoIntegration Iepositoryand SAP PCK
Configurationparameters are renderedinto the graphicalconfiguaration frontend
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 57
Adapter Metadata Fragment I
ltAdapterTypeMetaData version=09gt
ltTypegtNAESBltTypegt
ltInboundgt
ltTransportProtocolgt
ltChannelAttributesgt
ltAttributeGroupgt
ltNamegtCRYPTConfigurationltNamegt
ltGuiLabelsgtltLabel language=ENgtCryptographic ConfigurationltLabelgtltGuiLabelsgt
ltAttributeReferencegtltReferenceNamegtCRYPTUseSigningltReferenceNamegt
ltInboundgt
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 58
Adapter Metadata Fragment II
ltAttributegt
ltNamegtCRYPTUseSigningltNamegt
ltDataTypegtxsdbooleanltDataTypegt
ltGuiLabelsgt
ltLabel language=ENgtUse SigningltLabelgt
ltLabel language=DEgtVerwendung von SignierungltLabelgt
ltGuiLabelsgt
ltAttributegt
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 59
Adapter Configuration
Configuration attribute of type boolean is rendered to a check-box
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 60
Adapter Metadata Upload (PCK)
Integration Repositorydoes not exist in case ofSAP PCK installations
The upload mechanismfor Adaper Meta Datafor SAP PCK installationsrequires additonalparameters
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 61
AF CPA Cache
The Adapter configuration is deployed from the configuration time(SAP PCK or Integration Directory) to the J2EE service CPACache(Collaboration Profile Agreement)
The Adapter configuration can be accessed at runtime from withinadapter modules or JCA resource adapters via the CPACache API
The two main use cases are implemented inLookupManager to retrieve adapter configuation andNormalizationManager to retrieve Party information
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 62
Packaging Adapter Components
SAP recommends to use SAP Software Deployment Manager (SDM) for deployment
Software Delivery Archives (SDA) can contain software components of different types (eg applications libraries)
Detailed version information and dependencies to other components simplify program management
Adapter Modules and Development
Summary
Adapter Framework Overview
Adapter Strategy
Agenda
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 64
Summary
Adapter Framework runs on J2EE Stack of SAP Web AS
Adapter Framework is platform for Adapter Engine and SAP PCK
Adapter Framework provides an extensible platform for developing and running adapters
Adapter Engine utilizes central configuration monitoring administration
Dual connectivity strategyAdapter Framework for comprehensive integration of adaptersInteroperability via open standards to interop with EAI providers
SAP NetWeaver Certification for adapters based on Adapter Framework available
Adapter mappings metadata stored in Integration Repository
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 28
Access control list
Restrict access to the runtime environmentfor sender services of type Business Service or Business Systemfor interfaces of these sender services
Restrict access to particular (service) users
Check authorization at runtime
Configure access control in the Integration DirectorySender service Specify authorized users in the configuration of the corresponding (sender) serviceInterface Specify authorized users in the configuration of the relevant sender agreement which contains the interface in the object key
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 29
Dynamic Adapter Configuration
Enable adapters to read write dynamic message headers
Sender Adapter (constructing messages)Attach adapter specific information to message headerExamples File name source file size JMS timestamp mail subjectRead access to these attributes in receiver channel interface determination (routing) mapping
Receiver Adapter (consuming messages)Read attributes to overwrite values of channel configurationExamples Directory Name JMS Priority Mail Sender SOAP target URLSet attributes in mapping orUse attributes from sender in receiver channel
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 30
Sender Adapter Configuration (1)
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 31
Sender Adapter Configuration (2)
Add the filename et al to the message
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 32
Receiver Determination
Determinefilename-dependent receiver
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 33
Receiver Adapter
Store the file withthe name set in the messageattribute
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 34
Monitoring Adapter Engine
After selecting a message bdquoDetailsldquo View
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 35
Monitoring Integration Server
After selecting a message bdquoDisplayldquo
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 36
Remark Future of SAP XI 20 Adapter Engine
SAP XI 20 Adapter Engine is available in SAP NW acute04 and SAP NW 2004s as bdquoPlain J2SE Adapter Engineldquo
Functional scope as in SAP XI 20Adopted to the SAP XI 30 message protocolMinor maintenance issues bug fixes
RecommendationUse where platform requirements or limitations (hardware operating system JVM support) demand it
SAP XI 20 Adapter Engine works with SAP NW acute04 and SAP NW 2004s landscapes too
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 37
Integration Server
PlainJ2SE
Adapter Engine
Partner ConnectivityKitOptional non-central
Adapter EngineCentral Adapter Engine
Process Integration ndash Architecture
Integration Repository Integration Directory System Landscape Directory
Business Process Engine
Integration Engine
Adapter FrameworkMessagingQueuing
Security Handling
Resource
Adapter
Resource
Adapter
Resource
Adapter
Adapter FWMessagingQueuing
Security Handling
Adapter FWMessagingQueuing
Security Handling
PCK Configurationand Monitoring
HTTP
IDoc
Adapter
Adapter
FileDBJMSMarketplace
3rd Party Sys
FileDB
JMSSOAP
SAP ampNon-SAPSystem
FileDBJMSMarketplace
3rd Party Sys
FileDBJMSMarketplace
3rd Party Sys
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 38
SAP Partner Connectivity Kit Overview
SAP 3rdParty Appl PI XI
Smaller Company Subsidiary
SAPPCK
SAPApplication
3rd PartyApplication
Large Business Partner Headquarter
Internet
Enablement of smaller companies subsidiaries to exchange XML documents with their business partnerrsquos headquarterrsquos PI XI
SAPPCK
Providing a platform for development of own JCA Resource Adapters
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 39
SAP PCK ndash Adapters
SAP Partner Connectivity Kit (PCK) is based on Adapter Framework
SAP PCKlsquos objective is to enable XML document exchangebetween PI XI and business partner not using PI XI
SAP PCK also provides an extensible platform for developing and running individual JCA Resource adapters
Communication between PI XI and SAP PCK is via SAP XI messaging protocol
SAP PCK Includes the following adapters FileFTP JDBC JMS SOAP RFC IDoc (once available for SAP PCK) Mail SAP BC
Optionally SAP PCK can host further adapters that are available from SAP or 3rd party adapter providers
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 40
SAP PCK ndash Configuration Mapping
SAP PCK is deployed on stand-alone SAP J2EE Engine (part of SAP Web AS) within business partnerrsquos landscape
Configuration administration monitoring done locally on SAP PCK itself without need for an Integration Directory
Configuration UI provides same bdquolook and feelldquo as configuration UI of Adapter Engine
SAP PCK supports the development of message mappings using an integrated graphical mapping editor
Any source XML structure can be mapped to any target XML structureStandard functions are provided to perform calculations Boolean comparisons text mappings and other transformationsOptionally the standard functions can be enhanced with user-defined functions in Java
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 41
SAP PCK ndash Configuration UI
ConfigurationUI to configure Party Service Communication Channel Sender and Receiver agreementsSample screenshot for configuration of communication channel with adapter type sbquoFile FTPlsquo
Adapter Modules and Development
Summary
Adapter Framework Overview
Adapter Strategy
Agenda
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 43
SAP Exchange Infrastructure - Openness
Integration of SAP and non-SAP applicationsAdapter Framework for comprehensive integration of adaptersAdapters are used for technical connectivityAdapter metadata mappings are stored in Integration Repository
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 44
Dual Strategy
Dual connectivity strategyAdapter Framework for comprehensive integration of adapters to provide technical connectivity including central configurationadministration monitoring of adaptersInteroperability based on open standards (SOAP JMS HTTP(S)) tointeroperate with EAI providers
Value propositionStandardized interfaces allow easy integration of adapters from different partnersMinimum knowledge of end-to-end process integration requiredComprehensive integration avoids redundant maintenance ensures consistency enhances transparancyOpenness to integrate non-SAP applications 3rd party systems etcReduced TCO
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 45
Certification
CertificationSAP NetWeaver Certification of 3rd party adapters based on the adapter framework
Value propositionQuality (stability HA aspects performance etc) of adapters is controlledCertification helps customers to find right solutionQuick and convenient search for a variety of certified products with the online partner and product directory (httpwwwsapcompartnersdirectoriesSearchSolutionepx)Faster implementation time and lower integration costs through the use of tested 3rd party integrationReduced TCO
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 46
Adapter Mappings Metadata in Integration Repository
Adapter mappings and adapter metadata are stored in the Integration Repository
Centralized Integration Repository contains all relevant information for collaborative and integrative processesAll content adheres to open standards Adapters provide technical connectivity
Value propositionUse largest content catalogReduce costs in integration projectsReduce maintenance costsReduced TCO
Adapter Modules and Development
Summary
Adapter Framework Overview
Adapter Strategy
Agenda
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 48
For every adapter it is possible to define generic modules in the module processor possibility to extend the functionality of the specific adapter
Equivalent to the dispatcher classes in the J2SE adapter engine migration and examples
The default module configuration for the certain adapter is displayed in the channel configuration
Modules are EJBlsquos
Sequence matters
Module Processor Concept
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 49
Adapter Module Chain
Custom modulescan be added to default modulechains
Additional configurationparameters canbe specified eachmodule
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 50
Module Processor Documentation
SAP Help Portal (httphelpsapcom)SAP XI Runtime Connectivity Adapters Module ProcessorFeedback Mail to xidocumentationsapcom
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 51
Development Environment
Adapter development deployment and testing is possible on a single machine no full-blown PI XI is required
For testing purposes integration scenarioscan be configured in SAP PCK(eg loopback scenario)
Installation of SAP PCK already contains a sample adapter (including Adapter Meta Data) that should serve as a starting point
SAP Partner ConnectivityKit
Adapter FWMessagingQueuing
Security Handling
Resource
Adapter
PCK Configurationand Monitoring
FileDBJMSMarketplace
3rd Party Sys
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 52
Adapter Development Documentation
SAP Help Portal (httphelpsapcom)SAP XI Runtime Connectivity Partner Connectivity Kit Adapter DevelopmentFeedback Mail to xidocumentationsapcom
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 53
Requirements for Adapters (1)
Num AF Interface Category Description
1 JCA 10 conformance Mandatory Adapter must fulfill JCA 10 requirements (e g deployment) plus optional JCA 15 parts which are used by PI XI
2 AF Message Exchange Mandatory Adapter must be able to receive messages from AF and forward them to connected system and vice versa
3 AF Adapter Specific Modules
Optional SAP XI message and protocol conversion may be done entirely by the adapter or as adapter specific module and being called in the AF module chain context
4 Configuration Services Mandatory Unique configuration approach to manage adapters
5 Administrational Services
Optional Administration and Monitoring
6 Utility Service Mandatory Access to basic J2EE resources e g transactions and multithreading must be under control of J2EE server
7 Logging API Optional Adapters may use their own logging
8 Message Metadata Exchange
Optional Provide structure definition of message payloadIf not supported the definition of message types can be done in the Integration Repository
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 54
Requirements for Adapters (2)
Cluster-enabledConsider side-effects of clustering e g bdquoExactlyOnceInOrderldquo Avoid passing maneuvers
SpecializationBuild connection to exactly one type of business system or industrystandard protocol
DirectnessBuild connection to business system or industry standard protocoldirectly without any intermediate software components
SmoothnessLight-weighted low footprint adapter unnecessary system changes(many new or changed system DLL) should be avoided
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 55
Sample Adapter Source Code
Beside the API documentation a working sample adapter is shipped
The source code is available after installation
Analyzing the code helps understanding the Adapter Framework
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 56
Adapter Metadata
Adapter Metadata (AMD)XML file defines all configuration parameterseach adapter
AMD can be uploaded intoIntegration Iepositoryand SAP PCK
Configurationparameters are renderedinto the graphicalconfiguaration frontend
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 57
Adapter Metadata Fragment I
ltAdapterTypeMetaData version=09gt
ltTypegtNAESBltTypegt
ltInboundgt
ltTransportProtocolgt
ltChannelAttributesgt
ltAttributeGroupgt
ltNamegtCRYPTConfigurationltNamegt
ltGuiLabelsgtltLabel language=ENgtCryptographic ConfigurationltLabelgtltGuiLabelsgt
ltAttributeReferencegtltReferenceNamegtCRYPTUseSigningltReferenceNamegt
ltInboundgt
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 58
Adapter Metadata Fragment II
ltAttributegt
ltNamegtCRYPTUseSigningltNamegt
ltDataTypegtxsdbooleanltDataTypegt
ltGuiLabelsgt
ltLabel language=ENgtUse SigningltLabelgt
ltLabel language=DEgtVerwendung von SignierungltLabelgt
ltGuiLabelsgt
ltAttributegt
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 59
Adapter Configuration
Configuration attribute of type boolean is rendered to a check-box
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 60
Adapter Metadata Upload (PCK)
Integration Repositorydoes not exist in case ofSAP PCK installations
The upload mechanismfor Adaper Meta Datafor SAP PCK installationsrequires additonalparameters
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 61
AF CPA Cache
The Adapter configuration is deployed from the configuration time(SAP PCK or Integration Directory) to the J2EE service CPACache(Collaboration Profile Agreement)
The Adapter configuration can be accessed at runtime from withinadapter modules or JCA resource adapters via the CPACache API
The two main use cases are implemented inLookupManager to retrieve adapter configuation andNormalizationManager to retrieve Party information
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 62
Packaging Adapter Components
SAP recommends to use SAP Software Deployment Manager (SDM) for deployment
Software Delivery Archives (SDA) can contain software components of different types (eg applications libraries)
Detailed version information and dependencies to other components simplify program management
Adapter Modules and Development
Summary
Adapter Framework Overview
Adapter Strategy
Agenda
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 64
Summary
Adapter Framework runs on J2EE Stack of SAP Web AS
Adapter Framework is platform for Adapter Engine and SAP PCK
Adapter Framework provides an extensible platform for developing and running adapters
Adapter Engine utilizes central configuration monitoring administration
Dual connectivity strategyAdapter Framework for comprehensive integration of adaptersInteroperability via open standards to interop with EAI providers
SAP NetWeaver Certification for adapters based on Adapter Framework available
Adapter mappings metadata stored in Integration Repository
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 29
Dynamic Adapter Configuration
Enable adapters to read write dynamic message headers
Sender Adapter (constructing messages)Attach adapter specific information to message headerExamples File name source file size JMS timestamp mail subjectRead access to these attributes in receiver channel interface determination (routing) mapping
Receiver Adapter (consuming messages)Read attributes to overwrite values of channel configurationExamples Directory Name JMS Priority Mail Sender SOAP target URLSet attributes in mapping orUse attributes from sender in receiver channel
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 30
Sender Adapter Configuration (1)
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 31
Sender Adapter Configuration (2)
Add the filename et al to the message
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 32
Receiver Determination
Determinefilename-dependent receiver
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 33
Receiver Adapter
Store the file withthe name set in the messageattribute
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 34
Monitoring Adapter Engine
After selecting a message bdquoDetailsldquo View
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 35
Monitoring Integration Server
After selecting a message bdquoDisplayldquo
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 36
Remark Future of SAP XI 20 Adapter Engine
SAP XI 20 Adapter Engine is available in SAP NW acute04 and SAP NW 2004s as bdquoPlain J2SE Adapter Engineldquo
Functional scope as in SAP XI 20Adopted to the SAP XI 30 message protocolMinor maintenance issues bug fixes
RecommendationUse where platform requirements or limitations (hardware operating system JVM support) demand it
SAP XI 20 Adapter Engine works with SAP NW acute04 and SAP NW 2004s landscapes too
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 37
Integration Server
PlainJ2SE
Adapter Engine
Partner ConnectivityKitOptional non-central
Adapter EngineCentral Adapter Engine
Process Integration ndash Architecture
Integration Repository Integration Directory System Landscape Directory
Business Process Engine
Integration Engine
Adapter FrameworkMessagingQueuing
Security Handling
Resource
Adapter
Resource
Adapter
Resource
Adapter
Adapter FWMessagingQueuing
Security Handling
Adapter FWMessagingQueuing
Security Handling
PCK Configurationand Monitoring
HTTP
IDoc
Adapter
Adapter
FileDBJMSMarketplace
3rd Party Sys
FileDB
JMSSOAP
SAP ampNon-SAPSystem
FileDBJMSMarketplace
3rd Party Sys
FileDBJMSMarketplace
3rd Party Sys
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 38
SAP Partner Connectivity Kit Overview
SAP 3rdParty Appl PI XI
Smaller Company Subsidiary
SAPPCK
SAPApplication
3rd PartyApplication
Large Business Partner Headquarter
Internet
Enablement of smaller companies subsidiaries to exchange XML documents with their business partnerrsquos headquarterrsquos PI XI
SAPPCK
Providing a platform for development of own JCA Resource Adapters
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 39
SAP PCK ndash Adapters
SAP Partner Connectivity Kit (PCK) is based on Adapter Framework
SAP PCKlsquos objective is to enable XML document exchangebetween PI XI and business partner not using PI XI
SAP PCK also provides an extensible platform for developing and running individual JCA Resource adapters
Communication between PI XI and SAP PCK is via SAP XI messaging protocol
SAP PCK Includes the following adapters FileFTP JDBC JMS SOAP RFC IDoc (once available for SAP PCK) Mail SAP BC
Optionally SAP PCK can host further adapters that are available from SAP or 3rd party adapter providers
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 40
SAP PCK ndash Configuration Mapping
SAP PCK is deployed on stand-alone SAP J2EE Engine (part of SAP Web AS) within business partnerrsquos landscape
Configuration administration monitoring done locally on SAP PCK itself without need for an Integration Directory
Configuration UI provides same bdquolook and feelldquo as configuration UI of Adapter Engine
SAP PCK supports the development of message mappings using an integrated graphical mapping editor
Any source XML structure can be mapped to any target XML structureStandard functions are provided to perform calculations Boolean comparisons text mappings and other transformationsOptionally the standard functions can be enhanced with user-defined functions in Java
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 41
SAP PCK ndash Configuration UI
ConfigurationUI to configure Party Service Communication Channel Sender and Receiver agreementsSample screenshot for configuration of communication channel with adapter type sbquoFile FTPlsquo
Adapter Modules and Development
Summary
Adapter Framework Overview
Adapter Strategy
Agenda
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 43
SAP Exchange Infrastructure - Openness
Integration of SAP and non-SAP applicationsAdapter Framework for comprehensive integration of adaptersAdapters are used for technical connectivityAdapter metadata mappings are stored in Integration Repository
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 44
Dual Strategy
Dual connectivity strategyAdapter Framework for comprehensive integration of adapters to provide technical connectivity including central configurationadministration monitoring of adaptersInteroperability based on open standards (SOAP JMS HTTP(S)) tointeroperate with EAI providers
Value propositionStandardized interfaces allow easy integration of adapters from different partnersMinimum knowledge of end-to-end process integration requiredComprehensive integration avoids redundant maintenance ensures consistency enhances transparancyOpenness to integrate non-SAP applications 3rd party systems etcReduced TCO
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 45
Certification
CertificationSAP NetWeaver Certification of 3rd party adapters based on the adapter framework
Value propositionQuality (stability HA aspects performance etc) of adapters is controlledCertification helps customers to find right solutionQuick and convenient search for a variety of certified products with the online partner and product directory (httpwwwsapcompartnersdirectoriesSearchSolutionepx)Faster implementation time and lower integration costs through the use of tested 3rd party integrationReduced TCO
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 46
Adapter Mappings Metadata in Integration Repository
Adapter mappings and adapter metadata are stored in the Integration Repository
Centralized Integration Repository contains all relevant information for collaborative and integrative processesAll content adheres to open standards Adapters provide technical connectivity
Value propositionUse largest content catalogReduce costs in integration projectsReduce maintenance costsReduced TCO
Adapter Modules and Development
Summary
Adapter Framework Overview
Adapter Strategy
Agenda
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 48
For every adapter it is possible to define generic modules in the module processor possibility to extend the functionality of the specific adapter
Equivalent to the dispatcher classes in the J2SE adapter engine migration and examples
The default module configuration for the certain adapter is displayed in the channel configuration
Modules are EJBlsquos
Sequence matters
Module Processor Concept
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 49
Adapter Module Chain
Custom modulescan be added to default modulechains
Additional configurationparameters canbe specified eachmodule
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 50
Module Processor Documentation
SAP Help Portal (httphelpsapcom)SAP XI Runtime Connectivity Adapters Module ProcessorFeedback Mail to xidocumentationsapcom
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 51
Development Environment
Adapter development deployment and testing is possible on a single machine no full-blown PI XI is required
For testing purposes integration scenarioscan be configured in SAP PCK(eg loopback scenario)
Installation of SAP PCK already contains a sample adapter (including Adapter Meta Data) that should serve as a starting point
SAP Partner ConnectivityKit
Adapter FWMessagingQueuing
Security Handling
Resource
Adapter
PCK Configurationand Monitoring
FileDBJMSMarketplace
3rd Party Sys
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 52
Adapter Development Documentation
SAP Help Portal (httphelpsapcom)SAP XI Runtime Connectivity Partner Connectivity Kit Adapter DevelopmentFeedback Mail to xidocumentationsapcom
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 53
Requirements for Adapters (1)
Num AF Interface Category Description
1 JCA 10 conformance Mandatory Adapter must fulfill JCA 10 requirements (e g deployment) plus optional JCA 15 parts which are used by PI XI
2 AF Message Exchange Mandatory Adapter must be able to receive messages from AF and forward them to connected system and vice versa
3 AF Adapter Specific Modules
Optional SAP XI message and protocol conversion may be done entirely by the adapter or as adapter specific module and being called in the AF module chain context
4 Configuration Services Mandatory Unique configuration approach to manage adapters
5 Administrational Services
Optional Administration and Monitoring
6 Utility Service Mandatory Access to basic J2EE resources e g transactions and multithreading must be under control of J2EE server
7 Logging API Optional Adapters may use their own logging
8 Message Metadata Exchange
Optional Provide structure definition of message payloadIf not supported the definition of message types can be done in the Integration Repository
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 54
Requirements for Adapters (2)
Cluster-enabledConsider side-effects of clustering e g bdquoExactlyOnceInOrderldquo Avoid passing maneuvers
SpecializationBuild connection to exactly one type of business system or industrystandard protocol
DirectnessBuild connection to business system or industry standard protocoldirectly without any intermediate software components
SmoothnessLight-weighted low footprint adapter unnecessary system changes(many new or changed system DLL) should be avoided
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 55
Sample Adapter Source Code
Beside the API documentation a working sample adapter is shipped
The source code is available after installation
Analyzing the code helps understanding the Adapter Framework
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 56
Adapter Metadata
Adapter Metadata (AMD)XML file defines all configuration parameterseach adapter
AMD can be uploaded intoIntegration Iepositoryand SAP PCK
Configurationparameters are renderedinto the graphicalconfiguaration frontend
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 57
Adapter Metadata Fragment I
ltAdapterTypeMetaData version=09gt
ltTypegtNAESBltTypegt
ltInboundgt
ltTransportProtocolgt
ltChannelAttributesgt
ltAttributeGroupgt
ltNamegtCRYPTConfigurationltNamegt
ltGuiLabelsgtltLabel language=ENgtCryptographic ConfigurationltLabelgtltGuiLabelsgt
ltAttributeReferencegtltReferenceNamegtCRYPTUseSigningltReferenceNamegt
ltInboundgt
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 58
Adapter Metadata Fragment II
ltAttributegt
ltNamegtCRYPTUseSigningltNamegt
ltDataTypegtxsdbooleanltDataTypegt
ltGuiLabelsgt
ltLabel language=ENgtUse SigningltLabelgt
ltLabel language=DEgtVerwendung von SignierungltLabelgt
ltGuiLabelsgt
ltAttributegt
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 59
Adapter Configuration
Configuration attribute of type boolean is rendered to a check-box
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 60
Adapter Metadata Upload (PCK)
Integration Repositorydoes not exist in case ofSAP PCK installations
The upload mechanismfor Adaper Meta Datafor SAP PCK installationsrequires additonalparameters
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 61
AF CPA Cache
The Adapter configuration is deployed from the configuration time(SAP PCK or Integration Directory) to the J2EE service CPACache(Collaboration Profile Agreement)
The Adapter configuration can be accessed at runtime from withinadapter modules or JCA resource adapters via the CPACache API
The two main use cases are implemented inLookupManager to retrieve adapter configuation andNormalizationManager to retrieve Party information
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 62
Packaging Adapter Components
SAP recommends to use SAP Software Deployment Manager (SDM) for deployment
Software Delivery Archives (SDA) can contain software components of different types (eg applications libraries)
Detailed version information and dependencies to other components simplify program management
Adapter Modules and Development
Summary
Adapter Framework Overview
Adapter Strategy
Agenda
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 64
Summary
Adapter Framework runs on J2EE Stack of SAP Web AS
Adapter Framework is platform for Adapter Engine and SAP PCK
Adapter Framework provides an extensible platform for developing and running adapters
Adapter Engine utilizes central configuration monitoring administration
Dual connectivity strategyAdapter Framework for comprehensive integration of adaptersInteroperability via open standards to interop with EAI providers
SAP NetWeaver Certification for adapters based on Adapter Framework available
Adapter mappings metadata stored in Integration Repository
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 30
Sender Adapter Configuration (1)
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 31
Sender Adapter Configuration (2)
Add the filename et al to the message
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 32
Receiver Determination
Determinefilename-dependent receiver
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 33
Receiver Adapter
Store the file withthe name set in the messageattribute
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 34
Monitoring Adapter Engine
After selecting a message bdquoDetailsldquo View
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 35
Monitoring Integration Server
After selecting a message bdquoDisplayldquo
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 36
Remark Future of SAP XI 20 Adapter Engine
SAP XI 20 Adapter Engine is available in SAP NW acute04 and SAP NW 2004s as bdquoPlain J2SE Adapter Engineldquo
Functional scope as in SAP XI 20Adopted to the SAP XI 30 message protocolMinor maintenance issues bug fixes
RecommendationUse where platform requirements or limitations (hardware operating system JVM support) demand it
SAP XI 20 Adapter Engine works with SAP NW acute04 and SAP NW 2004s landscapes too
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 37
Integration Server
PlainJ2SE
Adapter Engine
Partner ConnectivityKitOptional non-central
Adapter EngineCentral Adapter Engine
Process Integration ndash Architecture
Integration Repository Integration Directory System Landscape Directory
Business Process Engine
Integration Engine
Adapter FrameworkMessagingQueuing
Security Handling
Resource
Adapter
Resource
Adapter
Resource
Adapter
Adapter FWMessagingQueuing
Security Handling
Adapter FWMessagingQueuing
Security Handling
PCK Configurationand Monitoring
HTTP
IDoc
Adapter
Adapter
FileDBJMSMarketplace
3rd Party Sys
FileDB
JMSSOAP
SAP ampNon-SAPSystem
FileDBJMSMarketplace
3rd Party Sys
FileDBJMSMarketplace
3rd Party Sys
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 38
SAP Partner Connectivity Kit Overview
SAP 3rdParty Appl PI XI
Smaller Company Subsidiary
SAPPCK
SAPApplication
3rd PartyApplication
Large Business Partner Headquarter
Internet
Enablement of smaller companies subsidiaries to exchange XML documents with their business partnerrsquos headquarterrsquos PI XI
SAPPCK
Providing a platform for development of own JCA Resource Adapters
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 39
SAP PCK ndash Adapters
SAP Partner Connectivity Kit (PCK) is based on Adapter Framework
SAP PCKlsquos objective is to enable XML document exchangebetween PI XI and business partner not using PI XI
SAP PCK also provides an extensible platform for developing and running individual JCA Resource adapters
Communication between PI XI and SAP PCK is via SAP XI messaging protocol
SAP PCK Includes the following adapters FileFTP JDBC JMS SOAP RFC IDoc (once available for SAP PCK) Mail SAP BC
Optionally SAP PCK can host further adapters that are available from SAP or 3rd party adapter providers
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 40
SAP PCK ndash Configuration Mapping
SAP PCK is deployed on stand-alone SAP J2EE Engine (part of SAP Web AS) within business partnerrsquos landscape
Configuration administration monitoring done locally on SAP PCK itself without need for an Integration Directory
Configuration UI provides same bdquolook and feelldquo as configuration UI of Adapter Engine
SAP PCK supports the development of message mappings using an integrated graphical mapping editor
Any source XML structure can be mapped to any target XML structureStandard functions are provided to perform calculations Boolean comparisons text mappings and other transformationsOptionally the standard functions can be enhanced with user-defined functions in Java
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 41
SAP PCK ndash Configuration UI
ConfigurationUI to configure Party Service Communication Channel Sender and Receiver agreementsSample screenshot for configuration of communication channel with adapter type sbquoFile FTPlsquo
Adapter Modules and Development
Summary
Adapter Framework Overview
Adapter Strategy
Agenda
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 43
SAP Exchange Infrastructure - Openness
Integration of SAP and non-SAP applicationsAdapter Framework for comprehensive integration of adaptersAdapters are used for technical connectivityAdapter metadata mappings are stored in Integration Repository
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 44
Dual Strategy
Dual connectivity strategyAdapter Framework for comprehensive integration of adapters to provide technical connectivity including central configurationadministration monitoring of adaptersInteroperability based on open standards (SOAP JMS HTTP(S)) tointeroperate with EAI providers
Value propositionStandardized interfaces allow easy integration of adapters from different partnersMinimum knowledge of end-to-end process integration requiredComprehensive integration avoids redundant maintenance ensures consistency enhances transparancyOpenness to integrate non-SAP applications 3rd party systems etcReduced TCO
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 45
Certification
CertificationSAP NetWeaver Certification of 3rd party adapters based on the adapter framework
Value propositionQuality (stability HA aspects performance etc) of adapters is controlledCertification helps customers to find right solutionQuick and convenient search for a variety of certified products with the online partner and product directory (httpwwwsapcompartnersdirectoriesSearchSolutionepx)Faster implementation time and lower integration costs through the use of tested 3rd party integrationReduced TCO
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 46
Adapter Mappings Metadata in Integration Repository
Adapter mappings and adapter metadata are stored in the Integration Repository
Centralized Integration Repository contains all relevant information for collaborative and integrative processesAll content adheres to open standards Adapters provide technical connectivity
Value propositionUse largest content catalogReduce costs in integration projectsReduce maintenance costsReduced TCO
Adapter Modules and Development
Summary
Adapter Framework Overview
Adapter Strategy
Agenda
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 48
For every adapter it is possible to define generic modules in the module processor possibility to extend the functionality of the specific adapter
Equivalent to the dispatcher classes in the J2SE adapter engine migration and examples
The default module configuration for the certain adapter is displayed in the channel configuration
Modules are EJBlsquos
Sequence matters
Module Processor Concept
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 49
Adapter Module Chain
Custom modulescan be added to default modulechains
Additional configurationparameters canbe specified eachmodule
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 50
Module Processor Documentation
SAP Help Portal (httphelpsapcom)SAP XI Runtime Connectivity Adapters Module ProcessorFeedback Mail to xidocumentationsapcom
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 51
Development Environment
Adapter development deployment and testing is possible on a single machine no full-blown PI XI is required
For testing purposes integration scenarioscan be configured in SAP PCK(eg loopback scenario)
Installation of SAP PCK already contains a sample adapter (including Adapter Meta Data) that should serve as a starting point
SAP Partner ConnectivityKit
Adapter FWMessagingQueuing
Security Handling
Resource
Adapter
PCK Configurationand Monitoring
FileDBJMSMarketplace
3rd Party Sys
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 52
Adapter Development Documentation
SAP Help Portal (httphelpsapcom)SAP XI Runtime Connectivity Partner Connectivity Kit Adapter DevelopmentFeedback Mail to xidocumentationsapcom
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 53
Requirements for Adapters (1)
Num AF Interface Category Description
1 JCA 10 conformance Mandatory Adapter must fulfill JCA 10 requirements (e g deployment) plus optional JCA 15 parts which are used by PI XI
2 AF Message Exchange Mandatory Adapter must be able to receive messages from AF and forward them to connected system and vice versa
3 AF Adapter Specific Modules
Optional SAP XI message and protocol conversion may be done entirely by the adapter or as adapter specific module and being called in the AF module chain context
4 Configuration Services Mandatory Unique configuration approach to manage adapters
5 Administrational Services
Optional Administration and Monitoring
6 Utility Service Mandatory Access to basic J2EE resources e g transactions and multithreading must be under control of J2EE server
7 Logging API Optional Adapters may use their own logging
8 Message Metadata Exchange
Optional Provide structure definition of message payloadIf not supported the definition of message types can be done in the Integration Repository
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 54
Requirements for Adapters (2)
Cluster-enabledConsider side-effects of clustering e g bdquoExactlyOnceInOrderldquo Avoid passing maneuvers
SpecializationBuild connection to exactly one type of business system or industrystandard protocol
DirectnessBuild connection to business system or industry standard protocoldirectly without any intermediate software components
SmoothnessLight-weighted low footprint adapter unnecessary system changes(many new or changed system DLL) should be avoided
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 55
Sample Adapter Source Code
Beside the API documentation a working sample adapter is shipped
The source code is available after installation
Analyzing the code helps understanding the Adapter Framework
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 56
Adapter Metadata
Adapter Metadata (AMD)XML file defines all configuration parameterseach adapter
AMD can be uploaded intoIntegration Iepositoryand SAP PCK
Configurationparameters are renderedinto the graphicalconfiguaration frontend
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 57
Adapter Metadata Fragment I
ltAdapterTypeMetaData version=09gt
ltTypegtNAESBltTypegt
ltInboundgt
ltTransportProtocolgt
ltChannelAttributesgt
ltAttributeGroupgt
ltNamegtCRYPTConfigurationltNamegt
ltGuiLabelsgtltLabel language=ENgtCryptographic ConfigurationltLabelgtltGuiLabelsgt
ltAttributeReferencegtltReferenceNamegtCRYPTUseSigningltReferenceNamegt
ltInboundgt
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 58
Adapter Metadata Fragment II
ltAttributegt
ltNamegtCRYPTUseSigningltNamegt
ltDataTypegtxsdbooleanltDataTypegt
ltGuiLabelsgt
ltLabel language=ENgtUse SigningltLabelgt
ltLabel language=DEgtVerwendung von SignierungltLabelgt
ltGuiLabelsgt
ltAttributegt
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 59
Adapter Configuration
Configuration attribute of type boolean is rendered to a check-box
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 60
Adapter Metadata Upload (PCK)
Integration Repositorydoes not exist in case ofSAP PCK installations
The upload mechanismfor Adaper Meta Datafor SAP PCK installationsrequires additonalparameters
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 61
AF CPA Cache
The Adapter configuration is deployed from the configuration time(SAP PCK or Integration Directory) to the J2EE service CPACache(Collaboration Profile Agreement)
The Adapter configuration can be accessed at runtime from withinadapter modules or JCA resource adapters via the CPACache API
The two main use cases are implemented inLookupManager to retrieve adapter configuation andNormalizationManager to retrieve Party information
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 62
Packaging Adapter Components
SAP recommends to use SAP Software Deployment Manager (SDM) for deployment
Software Delivery Archives (SDA) can contain software components of different types (eg applications libraries)
Detailed version information and dependencies to other components simplify program management
Adapter Modules and Development
Summary
Adapter Framework Overview
Adapter Strategy
Agenda
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 64
Summary
Adapter Framework runs on J2EE Stack of SAP Web AS
Adapter Framework is platform for Adapter Engine and SAP PCK
Adapter Framework provides an extensible platform for developing and running adapters
Adapter Engine utilizes central configuration monitoring administration
Dual connectivity strategyAdapter Framework for comprehensive integration of adaptersInteroperability via open standards to interop with EAI providers
SAP NetWeaver Certification for adapters based on Adapter Framework available
Adapter mappings metadata stored in Integration Repository
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 31
Sender Adapter Configuration (2)
Add the filename et al to the message
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 32
Receiver Determination
Determinefilename-dependent receiver
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 33
Receiver Adapter
Store the file withthe name set in the messageattribute
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 34
Monitoring Adapter Engine
After selecting a message bdquoDetailsldquo View
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 35
Monitoring Integration Server
After selecting a message bdquoDisplayldquo
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 36
Remark Future of SAP XI 20 Adapter Engine
SAP XI 20 Adapter Engine is available in SAP NW acute04 and SAP NW 2004s as bdquoPlain J2SE Adapter Engineldquo
Functional scope as in SAP XI 20Adopted to the SAP XI 30 message protocolMinor maintenance issues bug fixes
RecommendationUse where platform requirements or limitations (hardware operating system JVM support) demand it
SAP XI 20 Adapter Engine works with SAP NW acute04 and SAP NW 2004s landscapes too
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 37
Integration Server
PlainJ2SE
Adapter Engine
Partner ConnectivityKitOptional non-central
Adapter EngineCentral Adapter Engine
Process Integration ndash Architecture
Integration Repository Integration Directory System Landscape Directory
Business Process Engine
Integration Engine
Adapter FrameworkMessagingQueuing
Security Handling
Resource
Adapter
Resource
Adapter
Resource
Adapter
Adapter FWMessagingQueuing
Security Handling
Adapter FWMessagingQueuing
Security Handling
PCK Configurationand Monitoring
HTTP
IDoc
Adapter
Adapter
FileDBJMSMarketplace
3rd Party Sys
FileDB
JMSSOAP
SAP ampNon-SAPSystem
FileDBJMSMarketplace
3rd Party Sys
FileDBJMSMarketplace
3rd Party Sys
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 38
SAP Partner Connectivity Kit Overview
SAP 3rdParty Appl PI XI
Smaller Company Subsidiary
SAPPCK
SAPApplication
3rd PartyApplication
Large Business Partner Headquarter
Internet
Enablement of smaller companies subsidiaries to exchange XML documents with their business partnerrsquos headquarterrsquos PI XI
SAPPCK
Providing a platform for development of own JCA Resource Adapters
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 39
SAP PCK ndash Adapters
SAP Partner Connectivity Kit (PCK) is based on Adapter Framework
SAP PCKlsquos objective is to enable XML document exchangebetween PI XI and business partner not using PI XI
SAP PCK also provides an extensible platform for developing and running individual JCA Resource adapters
Communication between PI XI and SAP PCK is via SAP XI messaging protocol
SAP PCK Includes the following adapters FileFTP JDBC JMS SOAP RFC IDoc (once available for SAP PCK) Mail SAP BC
Optionally SAP PCK can host further adapters that are available from SAP or 3rd party adapter providers
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 40
SAP PCK ndash Configuration Mapping
SAP PCK is deployed on stand-alone SAP J2EE Engine (part of SAP Web AS) within business partnerrsquos landscape
Configuration administration monitoring done locally on SAP PCK itself without need for an Integration Directory
Configuration UI provides same bdquolook and feelldquo as configuration UI of Adapter Engine
SAP PCK supports the development of message mappings using an integrated graphical mapping editor
Any source XML structure can be mapped to any target XML structureStandard functions are provided to perform calculations Boolean comparisons text mappings and other transformationsOptionally the standard functions can be enhanced with user-defined functions in Java
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 41
SAP PCK ndash Configuration UI
ConfigurationUI to configure Party Service Communication Channel Sender and Receiver agreementsSample screenshot for configuration of communication channel with adapter type sbquoFile FTPlsquo
Adapter Modules and Development
Summary
Adapter Framework Overview
Adapter Strategy
Agenda
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 43
SAP Exchange Infrastructure - Openness
Integration of SAP and non-SAP applicationsAdapter Framework for comprehensive integration of adaptersAdapters are used for technical connectivityAdapter metadata mappings are stored in Integration Repository
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 44
Dual Strategy
Dual connectivity strategyAdapter Framework for comprehensive integration of adapters to provide technical connectivity including central configurationadministration monitoring of adaptersInteroperability based on open standards (SOAP JMS HTTP(S)) tointeroperate with EAI providers
Value propositionStandardized interfaces allow easy integration of adapters from different partnersMinimum knowledge of end-to-end process integration requiredComprehensive integration avoids redundant maintenance ensures consistency enhances transparancyOpenness to integrate non-SAP applications 3rd party systems etcReduced TCO
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 45
Certification
CertificationSAP NetWeaver Certification of 3rd party adapters based on the adapter framework
Value propositionQuality (stability HA aspects performance etc) of adapters is controlledCertification helps customers to find right solutionQuick and convenient search for a variety of certified products with the online partner and product directory (httpwwwsapcompartnersdirectoriesSearchSolutionepx)Faster implementation time and lower integration costs through the use of tested 3rd party integrationReduced TCO
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 46
Adapter Mappings Metadata in Integration Repository
Adapter mappings and adapter metadata are stored in the Integration Repository
Centralized Integration Repository contains all relevant information for collaborative and integrative processesAll content adheres to open standards Adapters provide technical connectivity
Value propositionUse largest content catalogReduce costs in integration projectsReduce maintenance costsReduced TCO
Adapter Modules and Development
Summary
Adapter Framework Overview
Adapter Strategy
Agenda
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 48
For every adapter it is possible to define generic modules in the module processor possibility to extend the functionality of the specific adapter
Equivalent to the dispatcher classes in the J2SE adapter engine migration and examples
The default module configuration for the certain adapter is displayed in the channel configuration
Modules are EJBlsquos
Sequence matters
Module Processor Concept
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 49
Adapter Module Chain
Custom modulescan be added to default modulechains
Additional configurationparameters canbe specified eachmodule
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 50
Module Processor Documentation
SAP Help Portal (httphelpsapcom)SAP XI Runtime Connectivity Adapters Module ProcessorFeedback Mail to xidocumentationsapcom
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 51
Development Environment
Adapter development deployment and testing is possible on a single machine no full-blown PI XI is required
For testing purposes integration scenarioscan be configured in SAP PCK(eg loopback scenario)
Installation of SAP PCK already contains a sample adapter (including Adapter Meta Data) that should serve as a starting point
SAP Partner ConnectivityKit
Adapter FWMessagingQueuing
Security Handling
Resource
Adapter
PCK Configurationand Monitoring
FileDBJMSMarketplace
3rd Party Sys
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 52
Adapter Development Documentation
SAP Help Portal (httphelpsapcom)SAP XI Runtime Connectivity Partner Connectivity Kit Adapter DevelopmentFeedback Mail to xidocumentationsapcom
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 53
Requirements for Adapters (1)
Num AF Interface Category Description
1 JCA 10 conformance Mandatory Adapter must fulfill JCA 10 requirements (e g deployment) plus optional JCA 15 parts which are used by PI XI
2 AF Message Exchange Mandatory Adapter must be able to receive messages from AF and forward them to connected system and vice versa
3 AF Adapter Specific Modules
Optional SAP XI message and protocol conversion may be done entirely by the adapter or as adapter specific module and being called in the AF module chain context
4 Configuration Services Mandatory Unique configuration approach to manage adapters
5 Administrational Services
Optional Administration and Monitoring
6 Utility Service Mandatory Access to basic J2EE resources e g transactions and multithreading must be under control of J2EE server
7 Logging API Optional Adapters may use their own logging
8 Message Metadata Exchange
Optional Provide structure definition of message payloadIf not supported the definition of message types can be done in the Integration Repository
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 54
Requirements for Adapters (2)
Cluster-enabledConsider side-effects of clustering e g bdquoExactlyOnceInOrderldquo Avoid passing maneuvers
SpecializationBuild connection to exactly one type of business system or industrystandard protocol
DirectnessBuild connection to business system or industry standard protocoldirectly without any intermediate software components
SmoothnessLight-weighted low footprint adapter unnecessary system changes(many new or changed system DLL) should be avoided
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 55
Sample Adapter Source Code
Beside the API documentation a working sample adapter is shipped
The source code is available after installation
Analyzing the code helps understanding the Adapter Framework
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 56
Adapter Metadata
Adapter Metadata (AMD)XML file defines all configuration parameterseach adapter
AMD can be uploaded intoIntegration Iepositoryand SAP PCK
Configurationparameters are renderedinto the graphicalconfiguaration frontend
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 57
Adapter Metadata Fragment I
ltAdapterTypeMetaData version=09gt
ltTypegtNAESBltTypegt
ltInboundgt
ltTransportProtocolgt
ltChannelAttributesgt
ltAttributeGroupgt
ltNamegtCRYPTConfigurationltNamegt
ltGuiLabelsgtltLabel language=ENgtCryptographic ConfigurationltLabelgtltGuiLabelsgt
ltAttributeReferencegtltReferenceNamegtCRYPTUseSigningltReferenceNamegt
ltInboundgt
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 58
Adapter Metadata Fragment II
ltAttributegt
ltNamegtCRYPTUseSigningltNamegt
ltDataTypegtxsdbooleanltDataTypegt
ltGuiLabelsgt
ltLabel language=ENgtUse SigningltLabelgt
ltLabel language=DEgtVerwendung von SignierungltLabelgt
ltGuiLabelsgt
ltAttributegt
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 59
Adapter Configuration
Configuration attribute of type boolean is rendered to a check-box
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 60
Adapter Metadata Upload (PCK)
Integration Repositorydoes not exist in case ofSAP PCK installations
The upload mechanismfor Adaper Meta Datafor SAP PCK installationsrequires additonalparameters
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 61
AF CPA Cache
The Adapter configuration is deployed from the configuration time(SAP PCK or Integration Directory) to the J2EE service CPACache(Collaboration Profile Agreement)
The Adapter configuration can be accessed at runtime from withinadapter modules or JCA resource adapters via the CPACache API
The two main use cases are implemented inLookupManager to retrieve adapter configuation andNormalizationManager to retrieve Party information
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 62
Packaging Adapter Components
SAP recommends to use SAP Software Deployment Manager (SDM) for deployment
Software Delivery Archives (SDA) can contain software components of different types (eg applications libraries)
Detailed version information and dependencies to other components simplify program management
Adapter Modules and Development
Summary
Adapter Framework Overview
Adapter Strategy
Agenda
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 64
Summary
Adapter Framework runs on J2EE Stack of SAP Web AS
Adapter Framework is platform for Adapter Engine and SAP PCK
Adapter Framework provides an extensible platform for developing and running adapters
Adapter Engine utilizes central configuration monitoring administration
Dual connectivity strategyAdapter Framework for comprehensive integration of adaptersInteroperability via open standards to interop with EAI providers
SAP NetWeaver Certification for adapters based on Adapter Framework available
Adapter mappings metadata stored in Integration Repository
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 32
Receiver Determination
Determinefilename-dependent receiver
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 33
Receiver Adapter
Store the file withthe name set in the messageattribute
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 34
Monitoring Adapter Engine
After selecting a message bdquoDetailsldquo View
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 35
Monitoring Integration Server
After selecting a message bdquoDisplayldquo
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 36
Remark Future of SAP XI 20 Adapter Engine
SAP XI 20 Adapter Engine is available in SAP NW acute04 and SAP NW 2004s as bdquoPlain J2SE Adapter Engineldquo
Functional scope as in SAP XI 20Adopted to the SAP XI 30 message protocolMinor maintenance issues bug fixes
RecommendationUse where platform requirements or limitations (hardware operating system JVM support) demand it
SAP XI 20 Adapter Engine works with SAP NW acute04 and SAP NW 2004s landscapes too
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 37
Integration Server
PlainJ2SE
Adapter Engine
Partner ConnectivityKitOptional non-central
Adapter EngineCentral Adapter Engine
Process Integration ndash Architecture
Integration Repository Integration Directory System Landscape Directory
Business Process Engine
Integration Engine
Adapter FrameworkMessagingQueuing
Security Handling
Resource
Adapter
Resource
Adapter
Resource
Adapter
Adapter FWMessagingQueuing
Security Handling
Adapter FWMessagingQueuing
Security Handling
PCK Configurationand Monitoring
HTTP
IDoc
Adapter
Adapter
FileDBJMSMarketplace
3rd Party Sys
FileDB
JMSSOAP
SAP ampNon-SAPSystem
FileDBJMSMarketplace
3rd Party Sys
FileDBJMSMarketplace
3rd Party Sys
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 38
SAP Partner Connectivity Kit Overview
SAP 3rdParty Appl PI XI
Smaller Company Subsidiary
SAPPCK
SAPApplication
3rd PartyApplication
Large Business Partner Headquarter
Internet
Enablement of smaller companies subsidiaries to exchange XML documents with their business partnerrsquos headquarterrsquos PI XI
SAPPCK
Providing a platform for development of own JCA Resource Adapters
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 39
SAP PCK ndash Adapters
SAP Partner Connectivity Kit (PCK) is based on Adapter Framework
SAP PCKlsquos objective is to enable XML document exchangebetween PI XI and business partner not using PI XI
SAP PCK also provides an extensible platform for developing and running individual JCA Resource adapters
Communication between PI XI and SAP PCK is via SAP XI messaging protocol
SAP PCK Includes the following adapters FileFTP JDBC JMS SOAP RFC IDoc (once available for SAP PCK) Mail SAP BC
Optionally SAP PCK can host further adapters that are available from SAP or 3rd party adapter providers
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 40
SAP PCK ndash Configuration Mapping
SAP PCK is deployed on stand-alone SAP J2EE Engine (part of SAP Web AS) within business partnerrsquos landscape
Configuration administration monitoring done locally on SAP PCK itself without need for an Integration Directory
Configuration UI provides same bdquolook and feelldquo as configuration UI of Adapter Engine
SAP PCK supports the development of message mappings using an integrated graphical mapping editor
Any source XML structure can be mapped to any target XML structureStandard functions are provided to perform calculations Boolean comparisons text mappings and other transformationsOptionally the standard functions can be enhanced with user-defined functions in Java
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 41
SAP PCK ndash Configuration UI
ConfigurationUI to configure Party Service Communication Channel Sender and Receiver agreementsSample screenshot for configuration of communication channel with adapter type sbquoFile FTPlsquo
Adapter Modules and Development
Summary
Adapter Framework Overview
Adapter Strategy
Agenda
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 43
SAP Exchange Infrastructure - Openness
Integration of SAP and non-SAP applicationsAdapter Framework for comprehensive integration of adaptersAdapters are used for technical connectivityAdapter metadata mappings are stored in Integration Repository
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 44
Dual Strategy
Dual connectivity strategyAdapter Framework for comprehensive integration of adapters to provide technical connectivity including central configurationadministration monitoring of adaptersInteroperability based on open standards (SOAP JMS HTTP(S)) tointeroperate with EAI providers
Value propositionStandardized interfaces allow easy integration of adapters from different partnersMinimum knowledge of end-to-end process integration requiredComprehensive integration avoids redundant maintenance ensures consistency enhances transparancyOpenness to integrate non-SAP applications 3rd party systems etcReduced TCO
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 45
Certification
CertificationSAP NetWeaver Certification of 3rd party adapters based on the adapter framework
Value propositionQuality (stability HA aspects performance etc) of adapters is controlledCertification helps customers to find right solutionQuick and convenient search for a variety of certified products with the online partner and product directory (httpwwwsapcompartnersdirectoriesSearchSolutionepx)Faster implementation time and lower integration costs through the use of tested 3rd party integrationReduced TCO
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 46
Adapter Mappings Metadata in Integration Repository
Adapter mappings and adapter metadata are stored in the Integration Repository
Centralized Integration Repository contains all relevant information for collaborative and integrative processesAll content adheres to open standards Adapters provide technical connectivity
Value propositionUse largest content catalogReduce costs in integration projectsReduce maintenance costsReduced TCO
Adapter Modules and Development
Summary
Adapter Framework Overview
Adapter Strategy
Agenda
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 48
For every adapter it is possible to define generic modules in the module processor possibility to extend the functionality of the specific adapter
Equivalent to the dispatcher classes in the J2SE adapter engine migration and examples
The default module configuration for the certain adapter is displayed in the channel configuration
Modules are EJBlsquos
Sequence matters
Module Processor Concept
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 49
Adapter Module Chain
Custom modulescan be added to default modulechains
Additional configurationparameters canbe specified eachmodule
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 50
Module Processor Documentation
SAP Help Portal (httphelpsapcom)SAP XI Runtime Connectivity Adapters Module ProcessorFeedback Mail to xidocumentationsapcom
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 51
Development Environment
Adapter development deployment and testing is possible on a single machine no full-blown PI XI is required
For testing purposes integration scenarioscan be configured in SAP PCK(eg loopback scenario)
Installation of SAP PCK already contains a sample adapter (including Adapter Meta Data) that should serve as a starting point
SAP Partner ConnectivityKit
Adapter FWMessagingQueuing
Security Handling
Resource
Adapter
PCK Configurationand Monitoring
FileDBJMSMarketplace
3rd Party Sys
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 52
Adapter Development Documentation
SAP Help Portal (httphelpsapcom)SAP XI Runtime Connectivity Partner Connectivity Kit Adapter DevelopmentFeedback Mail to xidocumentationsapcom
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 53
Requirements for Adapters (1)
Num AF Interface Category Description
1 JCA 10 conformance Mandatory Adapter must fulfill JCA 10 requirements (e g deployment) plus optional JCA 15 parts which are used by PI XI
2 AF Message Exchange Mandatory Adapter must be able to receive messages from AF and forward them to connected system and vice versa
3 AF Adapter Specific Modules
Optional SAP XI message and protocol conversion may be done entirely by the adapter or as adapter specific module and being called in the AF module chain context
4 Configuration Services Mandatory Unique configuration approach to manage adapters
5 Administrational Services
Optional Administration and Monitoring
6 Utility Service Mandatory Access to basic J2EE resources e g transactions and multithreading must be under control of J2EE server
7 Logging API Optional Adapters may use their own logging
8 Message Metadata Exchange
Optional Provide structure definition of message payloadIf not supported the definition of message types can be done in the Integration Repository
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 54
Requirements for Adapters (2)
Cluster-enabledConsider side-effects of clustering e g bdquoExactlyOnceInOrderldquo Avoid passing maneuvers
SpecializationBuild connection to exactly one type of business system or industrystandard protocol
DirectnessBuild connection to business system or industry standard protocoldirectly without any intermediate software components
SmoothnessLight-weighted low footprint adapter unnecessary system changes(many new or changed system DLL) should be avoided
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 55
Sample Adapter Source Code
Beside the API documentation a working sample adapter is shipped
The source code is available after installation
Analyzing the code helps understanding the Adapter Framework
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 56
Adapter Metadata
Adapter Metadata (AMD)XML file defines all configuration parameterseach adapter
AMD can be uploaded intoIntegration Iepositoryand SAP PCK
Configurationparameters are renderedinto the graphicalconfiguaration frontend
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 57
Adapter Metadata Fragment I
ltAdapterTypeMetaData version=09gt
ltTypegtNAESBltTypegt
ltInboundgt
ltTransportProtocolgt
ltChannelAttributesgt
ltAttributeGroupgt
ltNamegtCRYPTConfigurationltNamegt
ltGuiLabelsgtltLabel language=ENgtCryptographic ConfigurationltLabelgtltGuiLabelsgt
ltAttributeReferencegtltReferenceNamegtCRYPTUseSigningltReferenceNamegt
ltInboundgt
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 58
Adapter Metadata Fragment II
ltAttributegt
ltNamegtCRYPTUseSigningltNamegt
ltDataTypegtxsdbooleanltDataTypegt
ltGuiLabelsgt
ltLabel language=ENgtUse SigningltLabelgt
ltLabel language=DEgtVerwendung von SignierungltLabelgt
ltGuiLabelsgt
ltAttributegt
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 59
Adapter Configuration
Configuration attribute of type boolean is rendered to a check-box
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 60
Adapter Metadata Upload (PCK)
Integration Repositorydoes not exist in case ofSAP PCK installations
The upload mechanismfor Adaper Meta Datafor SAP PCK installationsrequires additonalparameters
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 61
AF CPA Cache
The Adapter configuration is deployed from the configuration time(SAP PCK or Integration Directory) to the J2EE service CPACache(Collaboration Profile Agreement)
The Adapter configuration can be accessed at runtime from withinadapter modules or JCA resource adapters via the CPACache API
The two main use cases are implemented inLookupManager to retrieve adapter configuation andNormalizationManager to retrieve Party information
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 62
Packaging Adapter Components
SAP recommends to use SAP Software Deployment Manager (SDM) for deployment
Software Delivery Archives (SDA) can contain software components of different types (eg applications libraries)
Detailed version information and dependencies to other components simplify program management
Adapter Modules and Development
Summary
Adapter Framework Overview
Adapter Strategy
Agenda
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 64
Summary
Adapter Framework runs on J2EE Stack of SAP Web AS
Adapter Framework is platform for Adapter Engine and SAP PCK
Adapter Framework provides an extensible platform for developing and running adapters
Adapter Engine utilizes central configuration monitoring administration
Dual connectivity strategyAdapter Framework for comprehensive integration of adaptersInteroperability via open standards to interop with EAI providers
SAP NetWeaver Certification for adapters based on Adapter Framework available
Adapter mappings metadata stored in Integration Repository
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 33
Receiver Adapter
Store the file withthe name set in the messageattribute
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 34
Monitoring Adapter Engine
After selecting a message bdquoDetailsldquo View
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 35
Monitoring Integration Server
After selecting a message bdquoDisplayldquo
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 36
Remark Future of SAP XI 20 Adapter Engine
SAP XI 20 Adapter Engine is available in SAP NW acute04 and SAP NW 2004s as bdquoPlain J2SE Adapter Engineldquo
Functional scope as in SAP XI 20Adopted to the SAP XI 30 message protocolMinor maintenance issues bug fixes
RecommendationUse where platform requirements or limitations (hardware operating system JVM support) demand it
SAP XI 20 Adapter Engine works with SAP NW acute04 and SAP NW 2004s landscapes too
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 37
Integration Server
PlainJ2SE
Adapter Engine
Partner ConnectivityKitOptional non-central
Adapter EngineCentral Adapter Engine
Process Integration ndash Architecture
Integration Repository Integration Directory System Landscape Directory
Business Process Engine
Integration Engine
Adapter FrameworkMessagingQueuing
Security Handling
Resource
Adapter
Resource
Adapter
Resource
Adapter
Adapter FWMessagingQueuing
Security Handling
Adapter FWMessagingQueuing
Security Handling
PCK Configurationand Monitoring
HTTP
IDoc
Adapter
Adapter
FileDBJMSMarketplace
3rd Party Sys
FileDB
JMSSOAP
SAP ampNon-SAPSystem
FileDBJMSMarketplace
3rd Party Sys
FileDBJMSMarketplace
3rd Party Sys
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 38
SAP Partner Connectivity Kit Overview
SAP 3rdParty Appl PI XI
Smaller Company Subsidiary
SAPPCK
SAPApplication
3rd PartyApplication
Large Business Partner Headquarter
Internet
Enablement of smaller companies subsidiaries to exchange XML documents with their business partnerrsquos headquarterrsquos PI XI
SAPPCK
Providing a platform for development of own JCA Resource Adapters
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 39
SAP PCK ndash Adapters
SAP Partner Connectivity Kit (PCK) is based on Adapter Framework
SAP PCKlsquos objective is to enable XML document exchangebetween PI XI and business partner not using PI XI
SAP PCK also provides an extensible platform for developing and running individual JCA Resource adapters
Communication between PI XI and SAP PCK is via SAP XI messaging protocol
SAP PCK Includes the following adapters FileFTP JDBC JMS SOAP RFC IDoc (once available for SAP PCK) Mail SAP BC
Optionally SAP PCK can host further adapters that are available from SAP or 3rd party adapter providers
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 40
SAP PCK ndash Configuration Mapping
SAP PCK is deployed on stand-alone SAP J2EE Engine (part of SAP Web AS) within business partnerrsquos landscape
Configuration administration monitoring done locally on SAP PCK itself without need for an Integration Directory
Configuration UI provides same bdquolook and feelldquo as configuration UI of Adapter Engine
SAP PCK supports the development of message mappings using an integrated graphical mapping editor
Any source XML structure can be mapped to any target XML structureStandard functions are provided to perform calculations Boolean comparisons text mappings and other transformationsOptionally the standard functions can be enhanced with user-defined functions in Java
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 41
SAP PCK ndash Configuration UI
ConfigurationUI to configure Party Service Communication Channel Sender and Receiver agreementsSample screenshot for configuration of communication channel with adapter type sbquoFile FTPlsquo
Adapter Modules and Development
Summary
Adapter Framework Overview
Adapter Strategy
Agenda
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 43
SAP Exchange Infrastructure - Openness
Integration of SAP and non-SAP applicationsAdapter Framework for comprehensive integration of adaptersAdapters are used for technical connectivityAdapter metadata mappings are stored in Integration Repository
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 44
Dual Strategy
Dual connectivity strategyAdapter Framework for comprehensive integration of adapters to provide technical connectivity including central configurationadministration monitoring of adaptersInteroperability based on open standards (SOAP JMS HTTP(S)) tointeroperate with EAI providers
Value propositionStandardized interfaces allow easy integration of adapters from different partnersMinimum knowledge of end-to-end process integration requiredComprehensive integration avoids redundant maintenance ensures consistency enhances transparancyOpenness to integrate non-SAP applications 3rd party systems etcReduced TCO
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 45
Certification
CertificationSAP NetWeaver Certification of 3rd party adapters based on the adapter framework
Value propositionQuality (stability HA aspects performance etc) of adapters is controlledCertification helps customers to find right solutionQuick and convenient search for a variety of certified products with the online partner and product directory (httpwwwsapcompartnersdirectoriesSearchSolutionepx)Faster implementation time and lower integration costs through the use of tested 3rd party integrationReduced TCO
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 46
Adapter Mappings Metadata in Integration Repository
Adapter mappings and adapter metadata are stored in the Integration Repository
Centralized Integration Repository contains all relevant information for collaborative and integrative processesAll content adheres to open standards Adapters provide technical connectivity
Value propositionUse largest content catalogReduce costs in integration projectsReduce maintenance costsReduced TCO
Adapter Modules and Development
Summary
Adapter Framework Overview
Adapter Strategy
Agenda
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 48
For every adapter it is possible to define generic modules in the module processor possibility to extend the functionality of the specific adapter
Equivalent to the dispatcher classes in the J2SE adapter engine migration and examples
The default module configuration for the certain adapter is displayed in the channel configuration
Modules are EJBlsquos
Sequence matters
Module Processor Concept
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 49
Adapter Module Chain
Custom modulescan be added to default modulechains
Additional configurationparameters canbe specified eachmodule
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 50
Module Processor Documentation
SAP Help Portal (httphelpsapcom)SAP XI Runtime Connectivity Adapters Module ProcessorFeedback Mail to xidocumentationsapcom
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 51
Development Environment
Adapter development deployment and testing is possible on a single machine no full-blown PI XI is required
For testing purposes integration scenarioscan be configured in SAP PCK(eg loopback scenario)
Installation of SAP PCK already contains a sample adapter (including Adapter Meta Data) that should serve as a starting point
SAP Partner ConnectivityKit
Adapter FWMessagingQueuing
Security Handling
Resource
Adapter
PCK Configurationand Monitoring
FileDBJMSMarketplace
3rd Party Sys
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 52
Adapter Development Documentation
SAP Help Portal (httphelpsapcom)SAP XI Runtime Connectivity Partner Connectivity Kit Adapter DevelopmentFeedback Mail to xidocumentationsapcom
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 53
Requirements for Adapters (1)
Num AF Interface Category Description
1 JCA 10 conformance Mandatory Adapter must fulfill JCA 10 requirements (e g deployment) plus optional JCA 15 parts which are used by PI XI
2 AF Message Exchange Mandatory Adapter must be able to receive messages from AF and forward them to connected system and vice versa
3 AF Adapter Specific Modules
Optional SAP XI message and protocol conversion may be done entirely by the adapter or as adapter specific module and being called in the AF module chain context
4 Configuration Services Mandatory Unique configuration approach to manage adapters
5 Administrational Services
Optional Administration and Monitoring
6 Utility Service Mandatory Access to basic J2EE resources e g transactions and multithreading must be under control of J2EE server
7 Logging API Optional Adapters may use their own logging
8 Message Metadata Exchange
Optional Provide structure definition of message payloadIf not supported the definition of message types can be done in the Integration Repository
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 54
Requirements for Adapters (2)
Cluster-enabledConsider side-effects of clustering e g bdquoExactlyOnceInOrderldquo Avoid passing maneuvers
SpecializationBuild connection to exactly one type of business system or industrystandard protocol
DirectnessBuild connection to business system or industry standard protocoldirectly without any intermediate software components
SmoothnessLight-weighted low footprint adapter unnecessary system changes(many new or changed system DLL) should be avoided
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 55
Sample Adapter Source Code
Beside the API documentation a working sample adapter is shipped
The source code is available after installation
Analyzing the code helps understanding the Adapter Framework
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 56
Adapter Metadata
Adapter Metadata (AMD)XML file defines all configuration parameterseach adapter
AMD can be uploaded intoIntegration Iepositoryand SAP PCK
Configurationparameters are renderedinto the graphicalconfiguaration frontend
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 57
Adapter Metadata Fragment I
ltAdapterTypeMetaData version=09gt
ltTypegtNAESBltTypegt
ltInboundgt
ltTransportProtocolgt
ltChannelAttributesgt
ltAttributeGroupgt
ltNamegtCRYPTConfigurationltNamegt
ltGuiLabelsgtltLabel language=ENgtCryptographic ConfigurationltLabelgtltGuiLabelsgt
ltAttributeReferencegtltReferenceNamegtCRYPTUseSigningltReferenceNamegt
ltInboundgt
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 58
Adapter Metadata Fragment II
ltAttributegt
ltNamegtCRYPTUseSigningltNamegt
ltDataTypegtxsdbooleanltDataTypegt
ltGuiLabelsgt
ltLabel language=ENgtUse SigningltLabelgt
ltLabel language=DEgtVerwendung von SignierungltLabelgt
ltGuiLabelsgt
ltAttributegt
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 59
Adapter Configuration
Configuration attribute of type boolean is rendered to a check-box
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 60
Adapter Metadata Upload (PCK)
Integration Repositorydoes not exist in case ofSAP PCK installations
The upload mechanismfor Adaper Meta Datafor SAP PCK installationsrequires additonalparameters
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 61
AF CPA Cache
The Adapter configuration is deployed from the configuration time(SAP PCK or Integration Directory) to the J2EE service CPACache(Collaboration Profile Agreement)
The Adapter configuration can be accessed at runtime from withinadapter modules or JCA resource adapters via the CPACache API
The two main use cases are implemented inLookupManager to retrieve adapter configuation andNormalizationManager to retrieve Party information
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 62
Packaging Adapter Components
SAP recommends to use SAP Software Deployment Manager (SDM) for deployment
Software Delivery Archives (SDA) can contain software components of different types (eg applications libraries)
Detailed version information and dependencies to other components simplify program management
Adapter Modules and Development
Summary
Adapter Framework Overview
Adapter Strategy
Agenda
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 64
Summary
Adapter Framework runs on J2EE Stack of SAP Web AS
Adapter Framework is platform for Adapter Engine and SAP PCK
Adapter Framework provides an extensible platform for developing and running adapters
Adapter Engine utilizes central configuration monitoring administration
Dual connectivity strategyAdapter Framework for comprehensive integration of adaptersInteroperability via open standards to interop with EAI providers
SAP NetWeaver Certification for adapters based on Adapter Framework available
Adapter mappings metadata stored in Integration Repository
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 34
Monitoring Adapter Engine
After selecting a message bdquoDetailsldquo View
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 35
Monitoring Integration Server
After selecting a message bdquoDisplayldquo
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 36
Remark Future of SAP XI 20 Adapter Engine
SAP XI 20 Adapter Engine is available in SAP NW acute04 and SAP NW 2004s as bdquoPlain J2SE Adapter Engineldquo
Functional scope as in SAP XI 20Adopted to the SAP XI 30 message protocolMinor maintenance issues bug fixes
RecommendationUse where platform requirements or limitations (hardware operating system JVM support) demand it
SAP XI 20 Adapter Engine works with SAP NW acute04 and SAP NW 2004s landscapes too
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 37
Integration Server
PlainJ2SE
Adapter Engine
Partner ConnectivityKitOptional non-central
Adapter EngineCentral Adapter Engine
Process Integration ndash Architecture
Integration Repository Integration Directory System Landscape Directory
Business Process Engine
Integration Engine
Adapter FrameworkMessagingQueuing
Security Handling
Resource
Adapter
Resource
Adapter
Resource
Adapter
Adapter FWMessagingQueuing
Security Handling
Adapter FWMessagingQueuing
Security Handling
PCK Configurationand Monitoring
HTTP
IDoc
Adapter
Adapter
FileDBJMSMarketplace
3rd Party Sys
FileDB
JMSSOAP
SAP ampNon-SAPSystem
FileDBJMSMarketplace
3rd Party Sys
FileDBJMSMarketplace
3rd Party Sys
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 38
SAP Partner Connectivity Kit Overview
SAP 3rdParty Appl PI XI
Smaller Company Subsidiary
SAPPCK
SAPApplication
3rd PartyApplication
Large Business Partner Headquarter
Internet
Enablement of smaller companies subsidiaries to exchange XML documents with their business partnerrsquos headquarterrsquos PI XI
SAPPCK
Providing a platform for development of own JCA Resource Adapters
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 39
SAP PCK ndash Adapters
SAP Partner Connectivity Kit (PCK) is based on Adapter Framework
SAP PCKlsquos objective is to enable XML document exchangebetween PI XI and business partner not using PI XI
SAP PCK also provides an extensible platform for developing and running individual JCA Resource adapters
Communication between PI XI and SAP PCK is via SAP XI messaging protocol
SAP PCK Includes the following adapters FileFTP JDBC JMS SOAP RFC IDoc (once available for SAP PCK) Mail SAP BC
Optionally SAP PCK can host further adapters that are available from SAP or 3rd party adapter providers
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 40
SAP PCK ndash Configuration Mapping
SAP PCK is deployed on stand-alone SAP J2EE Engine (part of SAP Web AS) within business partnerrsquos landscape
Configuration administration monitoring done locally on SAP PCK itself without need for an Integration Directory
Configuration UI provides same bdquolook and feelldquo as configuration UI of Adapter Engine
SAP PCK supports the development of message mappings using an integrated graphical mapping editor
Any source XML structure can be mapped to any target XML structureStandard functions are provided to perform calculations Boolean comparisons text mappings and other transformationsOptionally the standard functions can be enhanced with user-defined functions in Java
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 41
SAP PCK ndash Configuration UI
ConfigurationUI to configure Party Service Communication Channel Sender and Receiver agreementsSample screenshot for configuration of communication channel with adapter type sbquoFile FTPlsquo
Adapter Modules and Development
Summary
Adapter Framework Overview
Adapter Strategy
Agenda
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 43
SAP Exchange Infrastructure - Openness
Integration of SAP and non-SAP applicationsAdapter Framework for comprehensive integration of adaptersAdapters are used for technical connectivityAdapter metadata mappings are stored in Integration Repository
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 44
Dual Strategy
Dual connectivity strategyAdapter Framework for comprehensive integration of adapters to provide technical connectivity including central configurationadministration monitoring of adaptersInteroperability based on open standards (SOAP JMS HTTP(S)) tointeroperate with EAI providers
Value propositionStandardized interfaces allow easy integration of adapters from different partnersMinimum knowledge of end-to-end process integration requiredComprehensive integration avoids redundant maintenance ensures consistency enhances transparancyOpenness to integrate non-SAP applications 3rd party systems etcReduced TCO
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 45
Certification
CertificationSAP NetWeaver Certification of 3rd party adapters based on the adapter framework
Value propositionQuality (stability HA aspects performance etc) of adapters is controlledCertification helps customers to find right solutionQuick and convenient search for a variety of certified products with the online partner and product directory (httpwwwsapcompartnersdirectoriesSearchSolutionepx)Faster implementation time and lower integration costs through the use of tested 3rd party integrationReduced TCO
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 46
Adapter Mappings Metadata in Integration Repository
Adapter mappings and adapter metadata are stored in the Integration Repository
Centralized Integration Repository contains all relevant information for collaborative and integrative processesAll content adheres to open standards Adapters provide technical connectivity
Value propositionUse largest content catalogReduce costs in integration projectsReduce maintenance costsReduced TCO
Adapter Modules and Development
Summary
Adapter Framework Overview
Adapter Strategy
Agenda
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 48
For every adapter it is possible to define generic modules in the module processor possibility to extend the functionality of the specific adapter
Equivalent to the dispatcher classes in the J2SE adapter engine migration and examples
The default module configuration for the certain adapter is displayed in the channel configuration
Modules are EJBlsquos
Sequence matters
Module Processor Concept
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 49
Adapter Module Chain
Custom modulescan be added to default modulechains
Additional configurationparameters canbe specified eachmodule
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 50
Module Processor Documentation
SAP Help Portal (httphelpsapcom)SAP XI Runtime Connectivity Adapters Module ProcessorFeedback Mail to xidocumentationsapcom
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 51
Development Environment
Adapter development deployment and testing is possible on a single machine no full-blown PI XI is required
For testing purposes integration scenarioscan be configured in SAP PCK(eg loopback scenario)
Installation of SAP PCK already contains a sample adapter (including Adapter Meta Data) that should serve as a starting point
SAP Partner ConnectivityKit
Adapter FWMessagingQueuing
Security Handling
Resource
Adapter
PCK Configurationand Monitoring
FileDBJMSMarketplace
3rd Party Sys
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 52
Adapter Development Documentation
SAP Help Portal (httphelpsapcom)SAP XI Runtime Connectivity Partner Connectivity Kit Adapter DevelopmentFeedback Mail to xidocumentationsapcom
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 53
Requirements for Adapters (1)
Num AF Interface Category Description
1 JCA 10 conformance Mandatory Adapter must fulfill JCA 10 requirements (e g deployment) plus optional JCA 15 parts which are used by PI XI
2 AF Message Exchange Mandatory Adapter must be able to receive messages from AF and forward them to connected system and vice versa
3 AF Adapter Specific Modules
Optional SAP XI message and protocol conversion may be done entirely by the adapter or as adapter specific module and being called in the AF module chain context
4 Configuration Services Mandatory Unique configuration approach to manage adapters
5 Administrational Services
Optional Administration and Monitoring
6 Utility Service Mandatory Access to basic J2EE resources e g transactions and multithreading must be under control of J2EE server
7 Logging API Optional Adapters may use their own logging
8 Message Metadata Exchange
Optional Provide structure definition of message payloadIf not supported the definition of message types can be done in the Integration Repository
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 54
Requirements for Adapters (2)
Cluster-enabledConsider side-effects of clustering e g bdquoExactlyOnceInOrderldquo Avoid passing maneuvers
SpecializationBuild connection to exactly one type of business system or industrystandard protocol
DirectnessBuild connection to business system or industry standard protocoldirectly without any intermediate software components
SmoothnessLight-weighted low footprint adapter unnecessary system changes(many new or changed system DLL) should be avoided
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 55
Sample Adapter Source Code
Beside the API documentation a working sample adapter is shipped
The source code is available after installation
Analyzing the code helps understanding the Adapter Framework
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 56
Adapter Metadata
Adapter Metadata (AMD)XML file defines all configuration parameterseach adapter
AMD can be uploaded intoIntegration Iepositoryand SAP PCK
Configurationparameters are renderedinto the graphicalconfiguaration frontend
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 57
Adapter Metadata Fragment I
ltAdapterTypeMetaData version=09gt
ltTypegtNAESBltTypegt
ltInboundgt
ltTransportProtocolgt
ltChannelAttributesgt
ltAttributeGroupgt
ltNamegtCRYPTConfigurationltNamegt
ltGuiLabelsgtltLabel language=ENgtCryptographic ConfigurationltLabelgtltGuiLabelsgt
ltAttributeReferencegtltReferenceNamegtCRYPTUseSigningltReferenceNamegt
ltInboundgt
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 58
Adapter Metadata Fragment II
ltAttributegt
ltNamegtCRYPTUseSigningltNamegt
ltDataTypegtxsdbooleanltDataTypegt
ltGuiLabelsgt
ltLabel language=ENgtUse SigningltLabelgt
ltLabel language=DEgtVerwendung von SignierungltLabelgt
ltGuiLabelsgt
ltAttributegt
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 59
Adapter Configuration
Configuration attribute of type boolean is rendered to a check-box
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 60
Adapter Metadata Upload (PCK)
Integration Repositorydoes not exist in case ofSAP PCK installations
The upload mechanismfor Adaper Meta Datafor SAP PCK installationsrequires additonalparameters
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 61
AF CPA Cache
The Adapter configuration is deployed from the configuration time(SAP PCK or Integration Directory) to the J2EE service CPACache(Collaboration Profile Agreement)
The Adapter configuration can be accessed at runtime from withinadapter modules or JCA resource adapters via the CPACache API
The two main use cases are implemented inLookupManager to retrieve adapter configuation andNormalizationManager to retrieve Party information
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 62
Packaging Adapter Components
SAP recommends to use SAP Software Deployment Manager (SDM) for deployment
Software Delivery Archives (SDA) can contain software components of different types (eg applications libraries)
Detailed version information and dependencies to other components simplify program management
Adapter Modules and Development
Summary
Adapter Framework Overview
Adapter Strategy
Agenda
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 64
Summary
Adapter Framework runs on J2EE Stack of SAP Web AS
Adapter Framework is platform for Adapter Engine and SAP PCK
Adapter Framework provides an extensible platform for developing and running adapters
Adapter Engine utilizes central configuration monitoring administration
Dual connectivity strategyAdapter Framework for comprehensive integration of adaptersInteroperability via open standards to interop with EAI providers
SAP NetWeaver Certification for adapters based on Adapter Framework available
Adapter mappings metadata stored in Integration Repository
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 35
Monitoring Integration Server
After selecting a message bdquoDisplayldquo
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 36
Remark Future of SAP XI 20 Adapter Engine
SAP XI 20 Adapter Engine is available in SAP NW acute04 and SAP NW 2004s as bdquoPlain J2SE Adapter Engineldquo
Functional scope as in SAP XI 20Adopted to the SAP XI 30 message protocolMinor maintenance issues bug fixes
RecommendationUse where platform requirements or limitations (hardware operating system JVM support) demand it
SAP XI 20 Adapter Engine works with SAP NW acute04 and SAP NW 2004s landscapes too
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 37
Integration Server
PlainJ2SE
Adapter Engine
Partner ConnectivityKitOptional non-central
Adapter EngineCentral Adapter Engine
Process Integration ndash Architecture
Integration Repository Integration Directory System Landscape Directory
Business Process Engine
Integration Engine
Adapter FrameworkMessagingQueuing
Security Handling
Resource
Adapter
Resource
Adapter
Resource
Adapter
Adapter FWMessagingQueuing
Security Handling
Adapter FWMessagingQueuing
Security Handling
PCK Configurationand Monitoring
HTTP
IDoc
Adapter
Adapter
FileDBJMSMarketplace
3rd Party Sys
FileDB
JMSSOAP
SAP ampNon-SAPSystem
FileDBJMSMarketplace
3rd Party Sys
FileDBJMSMarketplace
3rd Party Sys
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 38
SAP Partner Connectivity Kit Overview
SAP 3rdParty Appl PI XI
Smaller Company Subsidiary
SAPPCK
SAPApplication
3rd PartyApplication
Large Business Partner Headquarter
Internet
Enablement of smaller companies subsidiaries to exchange XML documents with their business partnerrsquos headquarterrsquos PI XI
SAPPCK
Providing a platform for development of own JCA Resource Adapters
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 39
SAP PCK ndash Adapters
SAP Partner Connectivity Kit (PCK) is based on Adapter Framework
SAP PCKlsquos objective is to enable XML document exchangebetween PI XI and business partner not using PI XI
SAP PCK also provides an extensible platform for developing and running individual JCA Resource adapters
Communication between PI XI and SAP PCK is via SAP XI messaging protocol
SAP PCK Includes the following adapters FileFTP JDBC JMS SOAP RFC IDoc (once available for SAP PCK) Mail SAP BC
Optionally SAP PCK can host further adapters that are available from SAP or 3rd party adapter providers
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 40
SAP PCK ndash Configuration Mapping
SAP PCK is deployed on stand-alone SAP J2EE Engine (part of SAP Web AS) within business partnerrsquos landscape
Configuration administration monitoring done locally on SAP PCK itself without need for an Integration Directory
Configuration UI provides same bdquolook and feelldquo as configuration UI of Adapter Engine
SAP PCK supports the development of message mappings using an integrated graphical mapping editor
Any source XML structure can be mapped to any target XML structureStandard functions are provided to perform calculations Boolean comparisons text mappings and other transformationsOptionally the standard functions can be enhanced with user-defined functions in Java
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 41
SAP PCK ndash Configuration UI
ConfigurationUI to configure Party Service Communication Channel Sender and Receiver agreementsSample screenshot for configuration of communication channel with adapter type sbquoFile FTPlsquo
Adapter Modules and Development
Summary
Adapter Framework Overview
Adapter Strategy
Agenda
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 43
SAP Exchange Infrastructure - Openness
Integration of SAP and non-SAP applicationsAdapter Framework for comprehensive integration of adaptersAdapters are used for technical connectivityAdapter metadata mappings are stored in Integration Repository
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 44
Dual Strategy
Dual connectivity strategyAdapter Framework for comprehensive integration of adapters to provide technical connectivity including central configurationadministration monitoring of adaptersInteroperability based on open standards (SOAP JMS HTTP(S)) tointeroperate with EAI providers
Value propositionStandardized interfaces allow easy integration of adapters from different partnersMinimum knowledge of end-to-end process integration requiredComprehensive integration avoids redundant maintenance ensures consistency enhances transparancyOpenness to integrate non-SAP applications 3rd party systems etcReduced TCO
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 45
Certification
CertificationSAP NetWeaver Certification of 3rd party adapters based on the adapter framework
Value propositionQuality (stability HA aspects performance etc) of adapters is controlledCertification helps customers to find right solutionQuick and convenient search for a variety of certified products with the online partner and product directory (httpwwwsapcompartnersdirectoriesSearchSolutionepx)Faster implementation time and lower integration costs through the use of tested 3rd party integrationReduced TCO
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 46
Adapter Mappings Metadata in Integration Repository
Adapter mappings and adapter metadata are stored in the Integration Repository
Centralized Integration Repository contains all relevant information for collaborative and integrative processesAll content adheres to open standards Adapters provide technical connectivity
Value propositionUse largest content catalogReduce costs in integration projectsReduce maintenance costsReduced TCO
Adapter Modules and Development
Summary
Adapter Framework Overview
Adapter Strategy
Agenda
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 48
For every adapter it is possible to define generic modules in the module processor possibility to extend the functionality of the specific adapter
Equivalent to the dispatcher classes in the J2SE adapter engine migration and examples
The default module configuration for the certain adapter is displayed in the channel configuration
Modules are EJBlsquos
Sequence matters
Module Processor Concept
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 49
Adapter Module Chain
Custom modulescan be added to default modulechains
Additional configurationparameters canbe specified eachmodule
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 50
Module Processor Documentation
SAP Help Portal (httphelpsapcom)SAP XI Runtime Connectivity Adapters Module ProcessorFeedback Mail to xidocumentationsapcom
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 51
Development Environment
Adapter development deployment and testing is possible on a single machine no full-blown PI XI is required
For testing purposes integration scenarioscan be configured in SAP PCK(eg loopback scenario)
Installation of SAP PCK already contains a sample adapter (including Adapter Meta Data) that should serve as a starting point
SAP Partner ConnectivityKit
Adapter FWMessagingQueuing
Security Handling
Resource
Adapter
PCK Configurationand Monitoring
FileDBJMSMarketplace
3rd Party Sys
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 52
Adapter Development Documentation
SAP Help Portal (httphelpsapcom)SAP XI Runtime Connectivity Partner Connectivity Kit Adapter DevelopmentFeedback Mail to xidocumentationsapcom
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 53
Requirements for Adapters (1)
Num AF Interface Category Description
1 JCA 10 conformance Mandatory Adapter must fulfill JCA 10 requirements (e g deployment) plus optional JCA 15 parts which are used by PI XI
2 AF Message Exchange Mandatory Adapter must be able to receive messages from AF and forward them to connected system and vice versa
3 AF Adapter Specific Modules
Optional SAP XI message and protocol conversion may be done entirely by the adapter or as adapter specific module and being called in the AF module chain context
4 Configuration Services Mandatory Unique configuration approach to manage adapters
5 Administrational Services
Optional Administration and Monitoring
6 Utility Service Mandatory Access to basic J2EE resources e g transactions and multithreading must be under control of J2EE server
7 Logging API Optional Adapters may use their own logging
8 Message Metadata Exchange
Optional Provide structure definition of message payloadIf not supported the definition of message types can be done in the Integration Repository
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 54
Requirements for Adapters (2)
Cluster-enabledConsider side-effects of clustering e g bdquoExactlyOnceInOrderldquo Avoid passing maneuvers
SpecializationBuild connection to exactly one type of business system or industrystandard protocol
DirectnessBuild connection to business system or industry standard protocoldirectly without any intermediate software components
SmoothnessLight-weighted low footprint adapter unnecessary system changes(many new or changed system DLL) should be avoided
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 55
Sample Adapter Source Code
Beside the API documentation a working sample adapter is shipped
The source code is available after installation
Analyzing the code helps understanding the Adapter Framework
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 56
Adapter Metadata
Adapter Metadata (AMD)XML file defines all configuration parameterseach adapter
AMD can be uploaded intoIntegration Iepositoryand SAP PCK
Configurationparameters are renderedinto the graphicalconfiguaration frontend
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 57
Adapter Metadata Fragment I
ltAdapterTypeMetaData version=09gt
ltTypegtNAESBltTypegt
ltInboundgt
ltTransportProtocolgt
ltChannelAttributesgt
ltAttributeGroupgt
ltNamegtCRYPTConfigurationltNamegt
ltGuiLabelsgtltLabel language=ENgtCryptographic ConfigurationltLabelgtltGuiLabelsgt
ltAttributeReferencegtltReferenceNamegtCRYPTUseSigningltReferenceNamegt
ltInboundgt
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 58
Adapter Metadata Fragment II
ltAttributegt
ltNamegtCRYPTUseSigningltNamegt
ltDataTypegtxsdbooleanltDataTypegt
ltGuiLabelsgt
ltLabel language=ENgtUse SigningltLabelgt
ltLabel language=DEgtVerwendung von SignierungltLabelgt
ltGuiLabelsgt
ltAttributegt
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 59
Adapter Configuration
Configuration attribute of type boolean is rendered to a check-box
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 60
Adapter Metadata Upload (PCK)
Integration Repositorydoes not exist in case ofSAP PCK installations
The upload mechanismfor Adaper Meta Datafor SAP PCK installationsrequires additonalparameters
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 61
AF CPA Cache
The Adapter configuration is deployed from the configuration time(SAP PCK or Integration Directory) to the J2EE service CPACache(Collaboration Profile Agreement)
The Adapter configuration can be accessed at runtime from withinadapter modules or JCA resource adapters via the CPACache API
The two main use cases are implemented inLookupManager to retrieve adapter configuation andNormalizationManager to retrieve Party information
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 62
Packaging Adapter Components
SAP recommends to use SAP Software Deployment Manager (SDM) for deployment
Software Delivery Archives (SDA) can contain software components of different types (eg applications libraries)
Detailed version information and dependencies to other components simplify program management
Adapter Modules and Development
Summary
Adapter Framework Overview
Adapter Strategy
Agenda
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 64
Summary
Adapter Framework runs on J2EE Stack of SAP Web AS
Adapter Framework is platform for Adapter Engine and SAP PCK
Adapter Framework provides an extensible platform for developing and running adapters
Adapter Engine utilizes central configuration monitoring administration
Dual connectivity strategyAdapter Framework for comprehensive integration of adaptersInteroperability via open standards to interop with EAI providers
SAP NetWeaver Certification for adapters based on Adapter Framework available
Adapter mappings metadata stored in Integration Repository
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 36
Remark Future of SAP XI 20 Adapter Engine
SAP XI 20 Adapter Engine is available in SAP NW acute04 and SAP NW 2004s as bdquoPlain J2SE Adapter Engineldquo
Functional scope as in SAP XI 20Adopted to the SAP XI 30 message protocolMinor maintenance issues bug fixes
RecommendationUse where platform requirements or limitations (hardware operating system JVM support) demand it
SAP XI 20 Adapter Engine works with SAP NW acute04 and SAP NW 2004s landscapes too
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 37
Integration Server
PlainJ2SE
Adapter Engine
Partner ConnectivityKitOptional non-central
Adapter EngineCentral Adapter Engine
Process Integration ndash Architecture
Integration Repository Integration Directory System Landscape Directory
Business Process Engine
Integration Engine
Adapter FrameworkMessagingQueuing
Security Handling
Resource
Adapter
Resource
Adapter
Resource
Adapter
Adapter FWMessagingQueuing
Security Handling
Adapter FWMessagingQueuing
Security Handling
PCK Configurationand Monitoring
HTTP
IDoc
Adapter
Adapter
FileDBJMSMarketplace
3rd Party Sys
FileDB
JMSSOAP
SAP ampNon-SAPSystem
FileDBJMSMarketplace
3rd Party Sys
FileDBJMSMarketplace
3rd Party Sys
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 38
SAP Partner Connectivity Kit Overview
SAP 3rdParty Appl PI XI
Smaller Company Subsidiary
SAPPCK
SAPApplication
3rd PartyApplication
Large Business Partner Headquarter
Internet
Enablement of smaller companies subsidiaries to exchange XML documents with their business partnerrsquos headquarterrsquos PI XI
SAPPCK
Providing a platform for development of own JCA Resource Adapters
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 39
SAP PCK ndash Adapters
SAP Partner Connectivity Kit (PCK) is based on Adapter Framework
SAP PCKlsquos objective is to enable XML document exchangebetween PI XI and business partner not using PI XI
SAP PCK also provides an extensible platform for developing and running individual JCA Resource adapters
Communication between PI XI and SAP PCK is via SAP XI messaging protocol
SAP PCK Includes the following adapters FileFTP JDBC JMS SOAP RFC IDoc (once available for SAP PCK) Mail SAP BC
Optionally SAP PCK can host further adapters that are available from SAP or 3rd party adapter providers
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 40
SAP PCK ndash Configuration Mapping
SAP PCK is deployed on stand-alone SAP J2EE Engine (part of SAP Web AS) within business partnerrsquos landscape
Configuration administration monitoring done locally on SAP PCK itself without need for an Integration Directory
Configuration UI provides same bdquolook and feelldquo as configuration UI of Adapter Engine
SAP PCK supports the development of message mappings using an integrated graphical mapping editor
Any source XML structure can be mapped to any target XML structureStandard functions are provided to perform calculations Boolean comparisons text mappings and other transformationsOptionally the standard functions can be enhanced with user-defined functions in Java
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 41
SAP PCK ndash Configuration UI
ConfigurationUI to configure Party Service Communication Channel Sender and Receiver agreementsSample screenshot for configuration of communication channel with adapter type sbquoFile FTPlsquo
Adapter Modules and Development
Summary
Adapter Framework Overview
Adapter Strategy
Agenda
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 43
SAP Exchange Infrastructure - Openness
Integration of SAP and non-SAP applicationsAdapter Framework for comprehensive integration of adaptersAdapters are used for technical connectivityAdapter metadata mappings are stored in Integration Repository
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 44
Dual Strategy
Dual connectivity strategyAdapter Framework for comprehensive integration of adapters to provide technical connectivity including central configurationadministration monitoring of adaptersInteroperability based on open standards (SOAP JMS HTTP(S)) tointeroperate with EAI providers
Value propositionStandardized interfaces allow easy integration of adapters from different partnersMinimum knowledge of end-to-end process integration requiredComprehensive integration avoids redundant maintenance ensures consistency enhances transparancyOpenness to integrate non-SAP applications 3rd party systems etcReduced TCO
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 45
Certification
CertificationSAP NetWeaver Certification of 3rd party adapters based on the adapter framework
Value propositionQuality (stability HA aspects performance etc) of adapters is controlledCertification helps customers to find right solutionQuick and convenient search for a variety of certified products with the online partner and product directory (httpwwwsapcompartnersdirectoriesSearchSolutionepx)Faster implementation time and lower integration costs through the use of tested 3rd party integrationReduced TCO
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 46
Adapter Mappings Metadata in Integration Repository
Adapter mappings and adapter metadata are stored in the Integration Repository
Centralized Integration Repository contains all relevant information for collaborative and integrative processesAll content adheres to open standards Adapters provide technical connectivity
Value propositionUse largest content catalogReduce costs in integration projectsReduce maintenance costsReduced TCO
Adapter Modules and Development
Summary
Adapter Framework Overview
Adapter Strategy
Agenda
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 48
For every adapter it is possible to define generic modules in the module processor possibility to extend the functionality of the specific adapter
Equivalent to the dispatcher classes in the J2SE adapter engine migration and examples
The default module configuration for the certain adapter is displayed in the channel configuration
Modules are EJBlsquos
Sequence matters
Module Processor Concept
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 49
Adapter Module Chain
Custom modulescan be added to default modulechains
Additional configurationparameters canbe specified eachmodule
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 50
Module Processor Documentation
SAP Help Portal (httphelpsapcom)SAP XI Runtime Connectivity Adapters Module ProcessorFeedback Mail to xidocumentationsapcom
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 51
Development Environment
Adapter development deployment and testing is possible on a single machine no full-blown PI XI is required
For testing purposes integration scenarioscan be configured in SAP PCK(eg loopback scenario)
Installation of SAP PCK already contains a sample adapter (including Adapter Meta Data) that should serve as a starting point
SAP Partner ConnectivityKit
Adapter FWMessagingQueuing
Security Handling
Resource
Adapter
PCK Configurationand Monitoring
FileDBJMSMarketplace
3rd Party Sys
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 52
Adapter Development Documentation
SAP Help Portal (httphelpsapcom)SAP XI Runtime Connectivity Partner Connectivity Kit Adapter DevelopmentFeedback Mail to xidocumentationsapcom
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 53
Requirements for Adapters (1)
Num AF Interface Category Description
1 JCA 10 conformance Mandatory Adapter must fulfill JCA 10 requirements (e g deployment) plus optional JCA 15 parts which are used by PI XI
2 AF Message Exchange Mandatory Adapter must be able to receive messages from AF and forward them to connected system and vice versa
3 AF Adapter Specific Modules
Optional SAP XI message and protocol conversion may be done entirely by the adapter or as adapter specific module and being called in the AF module chain context
4 Configuration Services Mandatory Unique configuration approach to manage adapters
5 Administrational Services
Optional Administration and Monitoring
6 Utility Service Mandatory Access to basic J2EE resources e g transactions and multithreading must be under control of J2EE server
7 Logging API Optional Adapters may use their own logging
8 Message Metadata Exchange
Optional Provide structure definition of message payloadIf not supported the definition of message types can be done in the Integration Repository
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 54
Requirements for Adapters (2)
Cluster-enabledConsider side-effects of clustering e g bdquoExactlyOnceInOrderldquo Avoid passing maneuvers
SpecializationBuild connection to exactly one type of business system or industrystandard protocol
DirectnessBuild connection to business system or industry standard protocoldirectly without any intermediate software components
SmoothnessLight-weighted low footprint adapter unnecessary system changes(many new or changed system DLL) should be avoided
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 55
Sample Adapter Source Code
Beside the API documentation a working sample adapter is shipped
The source code is available after installation
Analyzing the code helps understanding the Adapter Framework
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 56
Adapter Metadata
Adapter Metadata (AMD)XML file defines all configuration parameterseach adapter
AMD can be uploaded intoIntegration Iepositoryand SAP PCK
Configurationparameters are renderedinto the graphicalconfiguaration frontend
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 57
Adapter Metadata Fragment I
ltAdapterTypeMetaData version=09gt
ltTypegtNAESBltTypegt
ltInboundgt
ltTransportProtocolgt
ltChannelAttributesgt
ltAttributeGroupgt
ltNamegtCRYPTConfigurationltNamegt
ltGuiLabelsgtltLabel language=ENgtCryptographic ConfigurationltLabelgtltGuiLabelsgt
ltAttributeReferencegtltReferenceNamegtCRYPTUseSigningltReferenceNamegt
ltInboundgt
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 58
Adapter Metadata Fragment II
ltAttributegt
ltNamegtCRYPTUseSigningltNamegt
ltDataTypegtxsdbooleanltDataTypegt
ltGuiLabelsgt
ltLabel language=ENgtUse SigningltLabelgt
ltLabel language=DEgtVerwendung von SignierungltLabelgt
ltGuiLabelsgt
ltAttributegt
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 59
Adapter Configuration
Configuration attribute of type boolean is rendered to a check-box
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 60
Adapter Metadata Upload (PCK)
Integration Repositorydoes not exist in case ofSAP PCK installations
The upload mechanismfor Adaper Meta Datafor SAP PCK installationsrequires additonalparameters
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 61
AF CPA Cache
The Adapter configuration is deployed from the configuration time(SAP PCK or Integration Directory) to the J2EE service CPACache(Collaboration Profile Agreement)
The Adapter configuration can be accessed at runtime from withinadapter modules or JCA resource adapters via the CPACache API
The two main use cases are implemented inLookupManager to retrieve adapter configuation andNormalizationManager to retrieve Party information
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 62
Packaging Adapter Components
SAP recommends to use SAP Software Deployment Manager (SDM) for deployment
Software Delivery Archives (SDA) can contain software components of different types (eg applications libraries)
Detailed version information and dependencies to other components simplify program management
Adapter Modules and Development
Summary
Adapter Framework Overview
Adapter Strategy
Agenda
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 64
Summary
Adapter Framework runs on J2EE Stack of SAP Web AS
Adapter Framework is platform for Adapter Engine and SAP PCK
Adapter Framework provides an extensible platform for developing and running adapters
Adapter Engine utilizes central configuration monitoring administration
Dual connectivity strategyAdapter Framework for comprehensive integration of adaptersInteroperability via open standards to interop with EAI providers
SAP NetWeaver Certification for adapters based on Adapter Framework available
Adapter mappings metadata stored in Integration Repository
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 37
Integration Server
PlainJ2SE
Adapter Engine
Partner ConnectivityKitOptional non-central
Adapter EngineCentral Adapter Engine
Process Integration ndash Architecture
Integration Repository Integration Directory System Landscape Directory
Business Process Engine
Integration Engine
Adapter FrameworkMessagingQueuing
Security Handling
Resource
Adapter
Resource
Adapter
Resource
Adapter
Adapter FWMessagingQueuing
Security Handling
Adapter FWMessagingQueuing
Security Handling
PCK Configurationand Monitoring
HTTP
IDoc
Adapter
Adapter
FileDBJMSMarketplace
3rd Party Sys
FileDB
JMSSOAP
SAP ampNon-SAPSystem
FileDBJMSMarketplace
3rd Party Sys
FileDBJMSMarketplace
3rd Party Sys
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 38
SAP Partner Connectivity Kit Overview
SAP 3rdParty Appl PI XI
Smaller Company Subsidiary
SAPPCK
SAPApplication
3rd PartyApplication
Large Business Partner Headquarter
Internet
Enablement of smaller companies subsidiaries to exchange XML documents with their business partnerrsquos headquarterrsquos PI XI
SAPPCK
Providing a platform for development of own JCA Resource Adapters
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 39
SAP PCK ndash Adapters
SAP Partner Connectivity Kit (PCK) is based on Adapter Framework
SAP PCKlsquos objective is to enable XML document exchangebetween PI XI and business partner not using PI XI
SAP PCK also provides an extensible platform for developing and running individual JCA Resource adapters
Communication between PI XI and SAP PCK is via SAP XI messaging protocol
SAP PCK Includes the following adapters FileFTP JDBC JMS SOAP RFC IDoc (once available for SAP PCK) Mail SAP BC
Optionally SAP PCK can host further adapters that are available from SAP or 3rd party adapter providers
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 40
SAP PCK ndash Configuration Mapping
SAP PCK is deployed on stand-alone SAP J2EE Engine (part of SAP Web AS) within business partnerrsquos landscape
Configuration administration monitoring done locally on SAP PCK itself without need for an Integration Directory
Configuration UI provides same bdquolook and feelldquo as configuration UI of Adapter Engine
SAP PCK supports the development of message mappings using an integrated graphical mapping editor
Any source XML structure can be mapped to any target XML structureStandard functions are provided to perform calculations Boolean comparisons text mappings and other transformationsOptionally the standard functions can be enhanced with user-defined functions in Java
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 41
SAP PCK ndash Configuration UI
ConfigurationUI to configure Party Service Communication Channel Sender and Receiver agreementsSample screenshot for configuration of communication channel with adapter type sbquoFile FTPlsquo
Adapter Modules and Development
Summary
Adapter Framework Overview
Adapter Strategy
Agenda
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 43
SAP Exchange Infrastructure - Openness
Integration of SAP and non-SAP applicationsAdapter Framework for comprehensive integration of adaptersAdapters are used for technical connectivityAdapter metadata mappings are stored in Integration Repository
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 44
Dual Strategy
Dual connectivity strategyAdapter Framework for comprehensive integration of adapters to provide technical connectivity including central configurationadministration monitoring of adaptersInteroperability based on open standards (SOAP JMS HTTP(S)) tointeroperate with EAI providers
Value propositionStandardized interfaces allow easy integration of adapters from different partnersMinimum knowledge of end-to-end process integration requiredComprehensive integration avoids redundant maintenance ensures consistency enhances transparancyOpenness to integrate non-SAP applications 3rd party systems etcReduced TCO
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 45
Certification
CertificationSAP NetWeaver Certification of 3rd party adapters based on the adapter framework
Value propositionQuality (stability HA aspects performance etc) of adapters is controlledCertification helps customers to find right solutionQuick and convenient search for a variety of certified products with the online partner and product directory (httpwwwsapcompartnersdirectoriesSearchSolutionepx)Faster implementation time and lower integration costs through the use of tested 3rd party integrationReduced TCO
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 46
Adapter Mappings Metadata in Integration Repository
Adapter mappings and adapter metadata are stored in the Integration Repository
Centralized Integration Repository contains all relevant information for collaborative and integrative processesAll content adheres to open standards Adapters provide technical connectivity
Value propositionUse largest content catalogReduce costs in integration projectsReduce maintenance costsReduced TCO
Adapter Modules and Development
Summary
Adapter Framework Overview
Adapter Strategy
Agenda
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 48
For every adapter it is possible to define generic modules in the module processor possibility to extend the functionality of the specific adapter
Equivalent to the dispatcher classes in the J2SE adapter engine migration and examples
The default module configuration for the certain adapter is displayed in the channel configuration
Modules are EJBlsquos
Sequence matters
Module Processor Concept
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 49
Adapter Module Chain
Custom modulescan be added to default modulechains
Additional configurationparameters canbe specified eachmodule
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 50
Module Processor Documentation
SAP Help Portal (httphelpsapcom)SAP XI Runtime Connectivity Adapters Module ProcessorFeedback Mail to xidocumentationsapcom
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 51
Development Environment
Adapter development deployment and testing is possible on a single machine no full-blown PI XI is required
For testing purposes integration scenarioscan be configured in SAP PCK(eg loopback scenario)
Installation of SAP PCK already contains a sample adapter (including Adapter Meta Data) that should serve as a starting point
SAP Partner ConnectivityKit
Adapter FWMessagingQueuing
Security Handling
Resource
Adapter
PCK Configurationand Monitoring
FileDBJMSMarketplace
3rd Party Sys
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 52
Adapter Development Documentation
SAP Help Portal (httphelpsapcom)SAP XI Runtime Connectivity Partner Connectivity Kit Adapter DevelopmentFeedback Mail to xidocumentationsapcom
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 53
Requirements for Adapters (1)
Num AF Interface Category Description
1 JCA 10 conformance Mandatory Adapter must fulfill JCA 10 requirements (e g deployment) plus optional JCA 15 parts which are used by PI XI
2 AF Message Exchange Mandatory Adapter must be able to receive messages from AF and forward them to connected system and vice versa
3 AF Adapter Specific Modules
Optional SAP XI message and protocol conversion may be done entirely by the adapter or as adapter specific module and being called in the AF module chain context
4 Configuration Services Mandatory Unique configuration approach to manage adapters
5 Administrational Services
Optional Administration and Monitoring
6 Utility Service Mandatory Access to basic J2EE resources e g transactions and multithreading must be under control of J2EE server
7 Logging API Optional Adapters may use their own logging
8 Message Metadata Exchange
Optional Provide structure definition of message payloadIf not supported the definition of message types can be done in the Integration Repository
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 54
Requirements for Adapters (2)
Cluster-enabledConsider side-effects of clustering e g bdquoExactlyOnceInOrderldquo Avoid passing maneuvers
SpecializationBuild connection to exactly one type of business system or industrystandard protocol
DirectnessBuild connection to business system or industry standard protocoldirectly without any intermediate software components
SmoothnessLight-weighted low footprint adapter unnecessary system changes(many new or changed system DLL) should be avoided
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 55
Sample Adapter Source Code
Beside the API documentation a working sample adapter is shipped
The source code is available after installation
Analyzing the code helps understanding the Adapter Framework
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 56
Adapter Metadata
Adapter Metadata (AMD)XML file defines all configuration parameterseach adapter
AMD can be uploaded intoIntegration Iepositoryand SAP PCK
Configurationparameters are renderedinto the graphicalconfiguaration frontend
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 57
Adapter Metadata Fragment I
ltAdapterTypeMetaData version=09gt
ltTypegtNAESBltTypegt
ltInboundgt
ltTransportProtocolgt
ltChannelAttributesgt
ltAttributeGroupgt
ltNamegtCRYPTConfigurationltNamegt
ltGuiLabelsgtltLabel language=ENgtCryptographic ConfigurationltLabelgtltGuiLabelsgt
ltAttributeReferencegtltReferenceNamegtCRYPTUseSigningltReferenceNamegt
ltInboundgt
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 58
Adapter Metadata Fragment II
ltAttributegt
ltNamegtCRYPTUseSigningltNamegt
ltDataTypegtxsdbooleanltDataTypegt
ltGuiLabelsgt
ltLabel language=ENgtUse SigningltLabelgt
ltLabel language=DEgtVerwendung von SignierungltLabelgt
ltGuiLabelsgt
ltAttributegt
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 59
Adapter Configuration
Configuration attribute of type boolean is rendered to a check-box
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 60
Adapter Metadata Upload (PCK)
Integration Repositorydoes not exist in case ofSAP PCK installations
The upload mechanismfor Adaper Meta Datafor SAP PCK installationsrequires additonalparameters
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 61
AF CPA Cache
The Adapter configuration is deployed from the configuration time(SAP PCK or Integration Directory) to the J2EE service CPACache(Collaboration Profile Agreement)
The Adapter configuration can be accessed at runtime from withinadapter modules or JCA resource adapters via the CPACache API
The two main use cases are implemented inLookupManager to retrieve adapter configuation andNormalizationManager to retrieve Party information
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 62
Packaging Adapter Components
SAP recommends to use SAP Software Deployment Manager (SDM) for deployment
Software Delivery Archives (SDA) can contain software components of different types (eg applications libraries)
Detailed version information and dependencies to other components simplify program management
Adapter Modules and Development
Summary
Adapter Framework Overview
Adapter Strategy
Agenda
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 64
Summary
Adapter Framework runs on J2EE Stack of SAP Web AS
Adapter Framework is platform for Adapter Engine and SAP PCK
Adapter Framework provides an extensible platform for developing and running adapters
Adapter Engine utilizes central configuration monitoring administration
Dual connectivity strategyAdapter Framework for comprehensive integration of adaptersInteroperability via open standards to interop with EAI providers
SAP NetWeaver Certification for adapters based on Adapter Framework available
Adapter mappings metadata stored in Integration Repository
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 38
SAP Partner Connectivity Kit Overview
SAP 3rdParty Appl PI XI
Smaller Company Subsidiary
SAPPCK
SAPApplication
3rd PartyApplication
Large Business Partner Headquarter
Internet
Enablement of smaller companies subsidiaries to exchange XML documents with their business partnerrsquos headquarterrsquos PI XI
SAPPCK
Providing a platform for development of own JCA Resource Adapters
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 39
SAP PCK ndash Adapters
SAP Partner Connectivity Kit (PCK) is based on Adapter Framework
SAP PCKlsquos objective is to enable XML document exchangebetween PI XI and business partner not using PI XI
SAP PCK also provides an extensible platform for developing and running individual JCA Resource adapters
Communication between PI XI and SAP PCK is via SAP XI messaging protocol
SAP PCK Includes the following adapters FileFTP JDBC JMS SOAP RFC IDoc (once available for SAP PCK) Mail SAP BC
Optionally SAP PCK can host further adapters that are available from SAP or 3rd party adapter providers
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 40
SAP PCK ndash Configuration Mapping
SAP PCK is deployed on stand-alone SAP J2EE Engine (part of SAP Web AS) within business partnerrsquos landscape
Configuration administration monitoring done locally on SAP PCK itself without need for an Integration Directory
Configuration UI provides same bdquolook and feelldquo as configuration UI of Adapter Engine
SAP PCK supports the development of message mappings using an integrated graphical mapping editor
Any source XML structure can be mapped to any target XML structureStandard functions are provided to perform calculations Boolean comparisons text mappings and other transformationsOptionally the standard functions can be enhanced with user-defined functions in Java
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 41
SAP PCK ndash Configuration UI
ConfigurationUI to configure Party Service Communication Channel Sender and Receiver agreementsSample screenshot for configuration of communication channel with adapter type sbquoFile FTPlsquo
Adapter Modules and Development
Summary
Adapter Framework Overview
Adapter Strategy
Agenda
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 43
SAP Exchange Infrastructure - Openness
Integration of SAP and non-SAP applicationsAdapter Framework for comprehensive integration of adaptersAdapters are used for technical connectivityAdapter metadata mappings are stored in Integration Repository
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 44
Dual Strategy
Dual connectivity strategyAdapter Framework for comprehensive integration of adapters to provide technical connectivity including central configurationadministration monitoring of adaptersInteroperability based on open standards (SOAP JMS HTTP(S)) tointeroperate with EAI providers
Value propositionStandardized interfaces allow easy integration of adapters from different partnersMinimum knowledge of end-to-end process integration requiredComprehensive integration avoids redundant maintenance ensures consistency enhances transparancyOpenness to integrate non-SAP applications 3rd party systems etcReduced TCO
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 45
Certification
CertificationSAP NetWeaver Certification of 3rd party adapters based on the adapter framework
Value propositionQuality (stability HA aspects performance etc) of adapters is controlledCertification helps customers to find right solutionQuick and convenient search for a variety of certified products with the online partner and product directory (httpwwwsapcompartnersdirectoriesSearchSolutionepx)Faster implementation time and lower integration costs through the use of tested 3rd party integrationReduced TCO
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 46
Adapter Mappings Metadata in Integration Repository
Adapter mappings and adapter metadata are stored in the Integration Repository
Centralized Integration Repository contains all relevant information for collaborative and integrative processesAll content adheres to open standards Adapters provide technical connectivity
Value propositionUse largest content catalogReduce costs in integration projectsReduce maintenance costsReduced TCO
Adapter Modules and Development
Summary
Adapter Framework Overview
Adapter Strategy
Agenda
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 48
For every adapter it is possible to define generic modules in the module processor possibility to extend the functionality of the specific adapter
Equivalent to the dispatcher classes in the J2SE adapter engine migration and examples
The default module configuration for the certain adapter is displayed in the channel configuration
Modules are EJBlsquos
Sequence matters
Module Processor Concept
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 49
Adapter Module Chain
Custom modulescan be added to default modulechains
Additional configurationparameters canbe specified eachmodule
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 50
Module Processor Documentation
SAP Help Portal (httphelpsapcom)SAP XI Runtime Connectivity Adapters Module ProcessorFeedback Mail to xidocumentationsapcom
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 51
Development Environment
Adapter development deployment and testing is possible on a single machine no full-blown PI XI is required
For testing purposes integration scenarioscan be configured in SAP PCK(eg loopback scenario)
Installation of SAP PCK already contains a sample adapter (including Adapter Meta Data) that should serve as a starting point
SAP Partner ConnectivityKit
Adapter FWMessagingQueuing
Security Handling
Resource
Adapter
PCK Configurationand Monitoring
FileDBJMSMarketplace
3rd Party Sys
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 52
Adapter Development Documentation
SAP Help Portal (httphelpsapcom)SAP XI Runtime Connectivity Partner Connectivity Kit Adapter DevelopmentFeedback Mail to xidocumentationsapcom
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 53
Requirements for Adapters (1)
Num AF Interface Category Description
1 JCA 10 conformance Mandatory Adapter must fulfill JCA 10 requirements (e g deployment) plus optional JCA 15 parts which are used by PI XI
2 AF Message Exchange Mandatory Adapter must be able to receive messages from AF and forward them to connected system and vice versa
3 AF Adapter Specific Modules
Optional SAP XI message and protocol conversion may be done entirely by the adapter or as adapter specific module and being called in the AF module chain context
4 Configuration Services Mandatory Unique configuration approach to manage adapters
5 Administrational Services
Optional Administration and Monitoring
6 Utility Service Mandatory Access to basic J2EE resources e g transactions and multithreading must be under control of J2EE server
7 Logging API Optional Adapters may use their own logging
8 Message Metadata Exchange
Optional Provide structure definition of message payloadIf not supported the definition of message types can be done in the Integration Repository
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 54
Requirements for Adapters (2)
Cluster-enabledConsider side-effects of clustering e g bdquoExactlyOnceInOrderldquo Avoid passing maneuvers
SpecializationBuild connection to exactly one type of business system or industrystandard protocol
DirectnessBuild connection to business system or industry standard protocoldirectly without any intermediate software components
SmoothnessLight-weighted low footprint adapter unnecessary system changes(many new or changed system DLL) should be avoided
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 55
Sample Adapter Source Code
Beside the API documentation a working sample adapter is shipped
The source code is available after installation
Analyzing the code helps understanding the Adapter Framework
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 56
Adapter Metadata
Adapter Metadata (AMD)XML file defines all configuration parameterseach adapter
AMD can be uploaded intoIntegration Iepositoryand SAP PCK
Configurationparameters are renderedinto the graphicalconfiguaration frontend
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 57
Adapter Metadata Fragment I
ltAdapterTypeMetaData version=09gt
ltTypegtNAESBltTypegt
ltInboundgt
ltTransportProtocolgt
ltChannelAttributesgt
ltAttributeGroupgt
ltNamegtCRYPTConfigurationltNamegt
ltGuiLabelsgtltLabel language=ENgtCryptographic ConfigurationltLabelgtltGuiLabelsgt
ltAttributeReferencegtltReferenceNamegtCRYPTUseSigningltReferenceNamegt
ltInboundgt
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 58
Adapter Metadata Fragment II
ltAttributegt
ltNamegtCRYPTUseSigningltNamegt
ltDataTypegtxsdbooleanltDataTypegt
ltGuiLabelsgt
ltLabel language=ENgtUse SigningltLabelgt
ltLabel language=DEgtVerwendung von SignierungltLabelgt
ltGuiLabelsgt
ltAttributegt
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 59
Adapter Configuration
Configuration attribute of type boolean is rendered to a check-box
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 60
Adapter Metadata Upload (PCK)
Integration Repositorydoes not exist in case ofSAP PCK installations
The upload mechanismfor Adaper Meta Datafor SAP PCK installationsrequires additonalparameters
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 61
AF CPA Cache
The Adapter configuration is deployed from the configuration time(SAP PCK or Integration Directory) to the J2EE service CPACache(Collaboration Profile Agreement)
The Adapter configuration can be accessed at runtime from withinadapter modules or JCA resource adapters via the CPACache API
The two main use cases are implemented inLookupManager to retrieve adapter configuation andNormalizationManager to retrieve Party information
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 62
Packaging Adapter Components
SAP recommends to use SAP Software Deployment Manager (SDM) for deployment
Software Delivery Archives (SDA) can contain software components of different types (eg applications libraries)
Detailed version information and dependencies to other components simplify program management
Adapter Modules and Development
Summary
Adapter Framework Overview
Adapter Strategy
Agenda
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 64
Summary
Adapter Framework runs on J2EE Stack of SAP Web AS
Adapter Framework is platform for Adapter Engine and SAP PCK
Adapter Framework provides an extensible platform for developing and running adapters
Adapter Engine utilizes central configuration monitoring administration
Dual connectivity strategyAdapter Framework for comprehensive integration of adaptersInteroperability via open standards to interop with EAI providers
SAP NetWeaver Certification for adapters based on Adapter Framework available
Adapter mappings metadata stored in Integration Repository
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 39
SAP PCK ndash Adapters
SAP Partner Connectivity Kit (PCK) is based on Adapter Framework
SAP PCKlsquos objective is to enable XML document exchangebetween PI XI and business partner not using PI XI
SAP PCK also provides an extensible platform for developing and running individual JCA Resource adapters
Communication between PI XI and SAP PCK is via SAP XI messaging protocol
SAP PCK Includes the following adapters FileFTP JDBC JMS SOAP RFC IDoc (once available for SAP PCK) Mail SAP BC
Optionally SAP PCK can host further adapters that are available from SAP or 3rd party adapter providers
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 40
SAP PCK ndash Configuration Mapping
SAP PCK is deployed on stand-alone SAP J2EE Engine (part of SAP Web AS) within business partnerrsquos landscape
Configuration administration monitoring done locally on SAP PCK itself without need for an Integration Directory
Configuration UI provides same bdquolook and feelldquo as configuration UI of Adapter Engine
SAP PCK supports the development of message mappings using an integrated graphical mapping editor
Any source XML structure can be mapped to any target XML structureStandard functions are provided to perform calculations Boolean comparisons text mappings and other transformationsOptionally the standard functions can be enhanced with user-defined functions in Java
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 41
SAP PCK ndash Configuration UI
ConfigurationUI to configure Party Service Communication Channel Sender and Receiver agreementsSample screenshot for configuration of communication channel with adapter type sbquoFile FTPlsquo
Adapter Modules and Development
Summary
Adapter Framework Overview
Adapter Strategy
Agenda
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 43
SAP Exchange Infrastructure - Openness
Integration of SAP and non-SAP applicationsAdapter Framework for comprehensive integration of adaptersAdapters are used for technical connectivityAdapter metadata mappings are stored in Integration Repository
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 44
Dual Strategy
Dual connectivity strategyAdapter Framework for comprehensive integration of adapters to provide technical connectivity including central configurationadministration monitoring of adaptersInteroperability based on open standards (SOAP JMS HTTP(S)) tointeroperate with EAI providers
Value propositionStandardized interfaces allow easy integration of adapters from different partnersMinimum knowledge of end-to-end process integration requiredComprehensive integration avoids redundant maintenance ensures consistency enhances transparancyOpenness to integrate non-SAP applications 3rd party systems etcReduced TCO
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 45
Certification
CertificationSAP NetWeaver Certification of 3rd party adapters based on the adapter framework
Value propositionQuality (stability HA aspects performance etc) of adapters is controlledCertification helps customers to find right solutionQuick and convenient search for a variety of certified products with the online partner and product directory (httpwwwsapcompartnersdirectoriesSearchSolutionepx)Faster implementation time and lower integration costs through the use of tested 3rd party integrationReduced TCO
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 46
Adapter Mappings Metadata in Integration Repository
Adapter mappings and adapter metadata are stored in the Integration Repository
Centralized Integration Repository contains all relevant information for collaborative and integrative processesAll content adheres to open standards Adapters provide technical connectivity
Value propositionUse largest content catalogReduce costs in integration projectsReduce maintenance costsReduced TCO
Adapter Modules and Development
Summary
Adapter Framework Overview
Adapter Strategy
Agenda
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 48
For every adapter it is possible to define generic modules in the module processor possibility to extend the functionality of the specific adapter
Equivalent to the dispatcher classes in the J2SE adapter engine migration and examples
The default module configuration for the certain adapter is displayed in the channel configuration
Modules are EJBlsquos
Sequence matters
Module Processor Concept
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 49
Adapter Module Chain
Custom modulescan be added to default modulechains
Additional configurationparameters canbe specified eachmodule
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 50
Module Processor Documentation
SAP Help Portal (httphelpsapcom)SAP XI Runtime Connectivity Adapters Module ProcessorFeedback Mail to xidocumentationsapcom
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 51
Development Environment
Adapter development deployment and testing is possible on a single machine no full-blown PI XI is required
For testing purposes integration scenarioscan be configured in SAP PCK(eg loopback scenario)
Installation of SAP PCK already contains a sample adapter (including Adapter Meta Data) that should serve as a starting point
SAP Partner ConnectivityKit
Adapter FWMessagingQueuing
Security Handling
Resource
Adapter
PCK Configurationand Monitoring
FileDBJMSMarketplace
3rd Party Sys
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 52
Adapter Development Documentation
SAP Help Portal (httphelpsapcom)SAP XI Runtime Connectivity Partner Connectivity Kit Adapter DevelopmentFeedback Mail to xidocumentationsapcom
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 53
Requirements for Adapters (1)
Num AF Interface Category Description
1 JCA 10 conformance Mandatory Adapter must fulfill JCA 10 requirements (e g deployment) plus optional JCA 15 parts which are used by PI XI
2 AF Message Exchange Mandatory Adapter must be able to receive messages from AF and forward them to connected system and vice versa
3 AF Adapter Specific Modules
Optional SAP XI message and protocol conversion may be done entirely by the adapter or as adapter specific module and being called in the AF module chain context
4 Configuration Services Mandatory Unique configuration approach to manage adapters
5 Administrational Services
Optional Administration and Monitoring
6 Utility Service Mandatory Access to basic J2EE resources e g transactions and multithreading must be under control of J2EE server
7 Logging API Optional Adapters may use their own logging
8 Message Metadata Exchange
Optional Provide structure definition of message payloadIf not supported the definition of message types can be done in the Integration Repository
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 54
Requirements for Adapters (2)
Cluster-enabledConsider side-effects of clustering e g bdquoExactlyOnceInOrderldquo Avoid passing maneuvers
SpecializationBuild connection to exactly one type of business system or industrystandard protocol
DirectnessBuild connection to business system or industry standard protocoldirectly without any intermediate software components
SmoothnessLight-weighted low footprint adapter unnecessary system changes(many new or changed system DLL) should be avoided
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 55
Sample Adapter Source Code
Beside the API documentation a working sample adapter is shipped
The source code is available after installation
Analyzing the code helps understanding the Adapter Framework
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 56
Adapter Metadata
Adapter Metadata (AMD)XML file defines all configuration parameterseach adapter
AMD can be uploaded intoIntegration Iepositoryand SAP PCK
Configurationparameters are renderedinto the graphicalconfiguaration frontend
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 57
Adapter Metadata Fragment I
ltAdapterTypeMetaData version=09gt
ltTypegtNAESBltTypegt
ltInboundgt
ltTransportProtocolgt
ltChannelAttributesgt
ltAttributeGroupgt
ltNamegtCRYPTConfigurationltNamegt
ltGuiLabelsgtltLabel language=ENgtCryptographic ConfigurationltLabelgtltGuiLabelsgt
ltAttributeReferencegtltReferenceNamegtCRYPTUseSigningltReferenceNamegt
ltInboundgt
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 58
Adapter Metadata Fragment II
ltAttributegt
ltNamegtCRYPTUseSigningltNamegt
ltDataTypegtxsdbooleanltDataTypegt
ltGuiLabelsgt
ltLabel language=ENgtUse SigningltLabelgt
ltLabel language=DEgtVerwendung von SignierungltLabelgt
ltGuiLabelsgt
ltAttributegt
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 59
Adapter Configuration
Configuration attribute of type boolean is rendered to a check-box
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 60
Adapter Metadata Upload (PCK)
Integration Repositorydoes not exist in case ofSAP PCK installations
The upload mechanismfor Adaper Meta Datafor SAP PCK installationsrequires additonalparameters
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 61
AF CPA Cache
The Adapter configuration is deployed from the configuration time(SAP PCK or Integration Directory) to the J2EE service CPACache(Collaboration Profile Agreement)
The Adapter configuration can be accessed at runtime from withinadapter modules or JCA resource adapters via the CPACache API
The two main use cases are implemented inLookupManager to retrieve adapter configuation andNormalizationManager to retrieve Party information
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 62
Packaging Adapter Components
SAP recommends to use SAP Software Deployment Manager (SDM) for deployment
Software Delivery Archives (SDA) can contain software components of different types (eg applications libraries)
Detailed version information and dependencies to other components simplify program management
Adapter Modules and Development
Summary
Adapter Framework Overview
Adapter Strategy
Agenda
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 64
Summary
Adapter Framework runs on J2EE Stack of SAP Web AS
Adapter Framework is platform for Adapter Engine and SAP PCK
Adapter Framework provides an extensible platform for developing and running adapters
Adapter Engine utilizes central configuration monitoring administration
Dual connectivity strategyAdapter Framework for comprehensive integration of adaptersInteroperability via open standards to interop with EAI providers
SAP NetWeaver Certification for adapters based on Adapter Framework available
Adapter mappings metadata stored in Integration Repository
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 40
SAP PCK ndash Configuration Mapping
SAP PCK is deployed on stand-alone SAP J2EE Engine (part of SAP Web AS) within business partnerrsquos landscape
Configuration administration monitoring done locally on SAP PCK itself without need for an Integration Directory
Configuration UI provides same bdquolook and feelldquo as configuration UI of Adapter Engine
SAP PCK supports the development of message mappings using an integrated graphical mapping editor
Any source XML structure can be mapped to any target XML structureStandard functions are provided to perform calculations Boolean comparisons text mappings and other transformationsOptionally the standard functions can be enhanced with user-defined functions in Java
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 41
SAP PCK ndash Configuration UI
ConfigurationUI to configure Party Service Communication Channel Sender and Receiver agreementsSample screenshot for configuration of communication channel with adapter type sbquoFile FTPlsquo
Adapter Modules and Development
Summary
Adapter Framework Overview
Adapter Strategy
Agenda
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 43
SAP Exchange Infrastructure - Openness
Integration of SAP and non-SAP applicationsAdapter Framework for comprehensive integration of adaptersAdapters are used for technical connectivityAdapter metadata mappings are stored in Integration Repository
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 44
Dual Strategy
Dual connectivity strategyAdapter Framework for comprehensive integration of adapters to provide technical connectivity including central configurationadministration monitoring of adaptersInteroperability based on open standards (SOAP JMS HTTP(S)) tointeroperate with EAI providers
Value propositionStandardized interfaces allow easy integration of adapters from different partnersMinimum knowledge of end-to-end process integration requiredComprehensive integration avoids redundant maintenance ensures consistency enhances transparancyOpenness to integrate non-SAP applications 3rd party systems etcReduced TCO
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 45
Certification
CertificationSAP NetWeaver Certification of 3rd party adapters based on the adapter framework
Value propositionQuality (stability HA aspects performance etc) of adapters is controlledCertification helps customers to find right solutionQuick and convenient search for a variety of certified products with the online partner and product directory (httpwwwsapcompartnersdirectoriesSearchSolutionepx)Faster implementation time and lower integration costs through the use of tested 3rd party integrationReduced TCO
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 46
Adapter Mappings Metadata in Integration Repository
Adapter mappings and adapter metadata are stored in the Integration Repository
Centralized Integration Repository contains all relevant information for collaborative and integrative processesAll content adheres to open standards Adapters provide technical connectivity
Value propositionUse largest content catalogReduce costs in integration projectsReduce maintenance costsReduced TCO
Adapter Modules and Development
Summary
Adapter Framework Overview
Adapter Strategy
Agenda
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 48
For every adapter it is possible to define generic modules in the module processor possibility to extend the functionality of the specific adapter
Equivalent to the dispatcher classes in the J2SE adapter engine migration and examples
The default module configuration for the certain adapter is displayed in the channel configuration
Modules are EJBlsquos
Sequence matters
Module Processor Concept
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 49
Adapter Module Chain
Custom modulescan be added to default modulechains
Additional configurationparameters canbe specified eachmodule
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 50
Module Processor Documentation
SAP Help Portal (httphelpsapcom)SAP XI Runtime Connectivity Adapters Module ProcessorFeedback Mail to xidocumentationsapcom
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 51
Development Environment
Adapter development deployment and testing is possible on a single machine no full-blown PI XI is required
For testing purposes integration scenarioscan be configured in SAP PCK(eg loopback scenario)
Installation of SAP PCK already contains a sample adapter (including Adapter Meta Data) that should serve as a starting point
SAP Partner ConnectivityKit
Adapter FWMessagingQueuing
Security Handling
Resource
Adapter
PCK Configurationand Monitoring
FileDBJMSMarketplace
3rd Party Sys
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 52
Adapter Development Documentation
SAP Help Portal (httphelpsapcom)SAP XI Runtime Connectivity Partner Connectivity Kit Adapter DevelopmentFeedback Mail to xidocumentationsapcom
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 53
Requirements for Adapters (1)
Num AF Interface Category Description
1 JCA 10 conformance Mandatory Adapter must fulfill JCA 10 requirements (e g deployment) plus optional JCA 15 parts which are used by PI XI
2 AF Message Exchange Mandatory Adapter must be able to receive messages from AF and forward them to connected system and vice versa
3 AF Adapter Specific Modules
Optional SAP XI message and protocol conversion may be done entirely by the adapter or as adapter specific module and being called in the AF module chain context
4 Configuration Services Mandatory Unique configuration approach to manage adapters
5 Administrational Services
Optional Administration and Monitoring
6 Utility Service Mandatory Access to basic J2EE resources e g transactions and multithreading must be under control of J2EE server
7 Logging API Optional Adapters may use their own logging
8 Message Metadata Exchange
Optional Provide structure definition of message payloadIf not supported the definition of message types can be done in the Integration Repository
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 54
Requirements for Adapters (2)
Cluster-enabledConsider side-effects of clustering e g bdquoExactlyOnceInOrderldquo Avoid passing maneuvers
SpecializationBuild connection to exactly one type of business system or industrystandard protocol
DirectnessBuild connection to business system or industry standard protocoldirectly without any intermediate software components
SmoothnessLight-weighted low footprint adapter unnecessary system changes(many new or changed system DLL) should be avoided
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 55
Sample Adapter Source Code
Beside the API documentation a working sample adapter is shipped
The source code is available after installation
Analyzing the code helps understanding the Adapter Framework
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 56
Adapter Metadata
Adapter Metadata (AMD)XML file defines all configuration parameterseach adapter
AMD can be uploaded intoIntegration Iepositoryand SAP PCK
Configurationparameters are renderedinto the graphicalconfiguaration frontend
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 57
Adapter Metadata Fragment I
ltAdapterTypeMetaData version=09gt
ltTypegtNAESBltTypegt
ltInboundgt
ltTransportProtocolgt
ltChannelAttributesgt
ltAttributeGroupgt
ltNamegtCRYPTConfigurationltNamegt
ltGuiLabelsgtltLabel language=ENgtCryptographic ConfigurationltLabelgtltGuiLabelsgt
ltAttributeReferencegtltReferenceNamegtCRYPTUseSigningltReferenceNamegt
ltInboundgt
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 58
Adapter Metadata Fragment II
ltAttributegt
ltNamegtCRYPTUseSigningltNamegt
ltDataTypegtxsdbooleanltDataTypegt
ltGuiLabelsgt
ltLabel language=ENgtUse SigningltLabelgt
ltLabel language=DEgtVerwendung von SignierungltLabelgt
ltGuiLabelsgt
ltAttributegt
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 59
Adapter Configuration
Configuration attribute of type boolean is rendered to a check-box
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 60
Adapter Metadata Upload (PCK)
Integration Repositorydoes not exist in case ofSAP PCK installations
The upload mechanismfor Adaper Meta Datafor SAP PCK installationsrequires additonalparameters
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 61
AF CPA Cache
The Adapter configuration is deployed from the configuration time(SAP PCK or Integration Directory) to the J2EE service CPACache(Collaboration Profile Agreement)
The Adapter configuration can be accessed at runtime from withinadapter modules or JCA resource adapters via the CPACache API
The two main use cases are implemented inLookupManager to retrieve adapter configuation andNormalizationManager to retrieve Party information
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 62
Packaging Adapter Components
SAP recommends to use SAP Software Deployment Manager (SDM) for deployment
Software Delivery Archives (SDA) can contain software components of different types (eg applications libraries)
Detailed version information and dependencies to other components simplify program management
Adapter Modules and Development
Summary
Adapter Framework Overview
Adapter Strategy
Agenda
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 64
Summary
Adapter Framework runs on J2EE Stack of SAP Web AS
Adapter Framework is platform for Adapter Engine and SAP PCK
Adapter Framework provides an extensible platform for developing and running adapters
Adapter Engine utilizes central configuration monitoring administration
Dual connectivity strategyAdapter Framework for comprehensive integration of adaptersInteroperability via open standards to interop with EAI providers
SAP NetWeaver Certification for adapters based on Adapter Framework available
Adapter mappings metadata stored in Integration Repository
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 41
SAP PCK ndash Configuration UI
ConfigurationUI to configure Party Service Communication Channel Sender and Receiver agreementsSample screenshot for configuration of communication channel with adapter type sbquoFile FTPlsquo
Adapter Modules and Development
Summary
Adapter Framework Overview
Adapter Strategy
Agenda
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 43
SAP Exchange Infrastructure - Openness
Integration of SAP and non-SAP applicationsAdapter Framework for comprehensive integration of adaptersAdapters are used for technical connectivityAdapter metadata mappings are stored in Integration Repository
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 44
Dual Strategy
Dual connectivity strategyAdapter Framework for comprehensive integration of adapters to provide technical connectivity including central configurationadministration monitoring of adaptersInteroperability based on open standards (SOAP JMS HTTP(S)) tointeroperate with EAI providers
Value propositionStandardized interfaces allow easy integration of adapters from different partnersMinimum knowledge of end-to-end process integration requiredComprehensive integration avoids redundant maintenance ensures consistency enhances transparancyOpenness to integrate non-SAP applications 3rd party systems etcReduced TCO
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 45
Certification
CertificationSAP NetWeaver Certification of 3rd party adapters based on the adapter framework
Value propositionQuality (stability HA aspects performance etc) of adapters is controlledCertification helps customers to find right solutionQuick and convenient search for a variety of certified products with the online partner and product directory (httpwwwsapcompartnersdirectoriesSearchSolutionepx)Faster implementation time and lower integration costs through the use of tested 3rd party integrationReduced TCO
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 46
Adapter Mappings Metadata in Integration Repository
Adapter mappings and adapter metadata are stored in the Integration Repository
Centralized Integration Repository contains all relevant information for collaborative and integrative processesAll content adheres to open standards Adapters provide technical connectivity
Value propositionUse largest content catalogReduce costs in integration projectsReduce maintenance costsReduced TCO
Adapter Modules and Development
Summary
Adapter Framework Overview
Adapter Strategy
Agenda
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 48
For every adapter it is possible to define generic modules in the module processor possibility to extend the functionality of the specific adapter
Equivalent to the dispatcher classes in the J2SE adapter engine migration and examples
The default module configuration for the certain adapter is displayed in the channel configuration
Modules are EJBlsquos
Sequence matters
Module Processor Concept
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 49
Adapter Module Chain
Custom modulescan be added to default modulechains
Additional configurationparameters canbe specified eachmodule
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 50
Module Processor Documentation
SAP Help Portal (httphelpsapcom)SAP XI Runtime Connectivity Adapters Module ProcessorFeedback Mail to xidocumentationsapcom
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 51
Development Environment
Adapter development deployment and testing is possible on a single machine no full-blown PI XI is required
For testing purposes integration scenarioscan be configured in SAP PCK(eg loopback scenario)
Installation of SAP PCK already contains a sample adapter (including Adapter Meta Data) that should serve as a starting point
SAP Partner ConnectivityKit
Adapter FWMessagingQueuing
Security Handling
Resource
Adapter
PCK Configurationand Monitoring
FileDBJMSMarketplace
3rd Party Sys
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 52
Adapter Development Documentation
SAP Help Portal (httphelpsapcom)SAP XI Runtime Connectivity Partner Connectivity Kit Adapter DevelopmentFeedback Mail to xidocumentationsapcom
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 53
Requirements for Adapters (1)
Num AF Interface Category Description
1 JCA 10 conformance Mandatory Adapter must fulfill JCA 10 requirements (e g deployment) plus optional JCA 15 parts which are used by PI XI
2 AF Message Exchange Mandatory Adapter must be able to receive messages from AF and forward them to connected system and vice versa
3 AF Adapter Specific Modules
Optional SAP XI message and protocol conversion may be done entirely by the adapter or as adapter specific module and being called in the AF module chain context
4 Configuration Services Mandatory Unique configuration approach to manage adapters
5 Administrational Services
Optional Administration and Monitoring
6 Utility Service Mandatory Access to basic J2EE resources e g transactions and multithreading must be under control of J2EE server
7 Logging API Optional Adapters may use their own logging
8 Message Metadata Exchange
Optional Provide structure definition of message payloadIf not supported the definition of message types can be done in the Integration Repository
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 54
Requirements for Adapters (2)
Cluster-enabledConsider side-effects of clustering e g bdquoExactlyOnceInOrderldquo Avoid passing maneuvers
SpecializationBuild connection to exactly one type of business system or industrystandard protocol
DirectnessBuild connection to business system or industry standard protocoldirectly without any intermediate software components
SmoothnessLight-weighted low footprint adapter unnecessary system changes(many new or changed system DLL) should be avoided
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 55
Sample Adapter Source Code
Beside the API documentation a working sample adapter is shipped
The source code is available after installation
Analyzing the code helps understanding the Adapter Framework
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 56
Adapter Metadata
Adapter Metadata (AMD)XML file defines all configuration parameterseach adapter
AMD can be uploaded intoIntegration Iepositoryand SAP PCK
Configurationparameters are renderedinto the graphicalconfiguaration frontend
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 57
Adapter Metadata Fragment I
ltAdapterTypeMetaData version=09gt
ltTypegtNAESBltTypegt
ltInboundgt
ltTransportProtocolgt
ltChannelAttributesgt
ltAttributeGroupgt
ltNamegtCRYPTConfigurationltNamegt
ltGuiLabelsgtltLabel language=ENgtCryptographic ConfigurationltLabelgtltGuiLabelsgt
ltAttributeReferencegtltReferenceNamegtCRYPTUseSigningltReferenceNamegt
ltInboundgt
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 58
Adapter Metadata Fragment II
ltAttributegt
ltNamegtCRYPTUseSigningltNamegt
ltDataTypegtxsdbooleanltDataTypegt
ltGuiLabelsgt
ltLabel language=ENgtUse SigningltLabelgt
ltLabel language=DEgtVerwendung von SignierungltLabelgt
ltGuiLabelsgt
ltAttributegt
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 59
Adapter Configuration
Configuration attribute of type boolean is rendered to a check-box
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 60
Adapter Metadata Upload (PCK)
Integration Repositorydoes not exist in case ofSAP PCK installations
The upload mechanismfor Adaper Meta Datafor SAP PCK installationsrequires additonalparameters
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 61
AF CPA Cache
The Adapter configuration is deployed from the configuration time(SAP PCK or Integration Directory) to the J2EE service CPACache(Collaboration Profile Agreement)
The Adapter configuration can be accessed at runtime from withinadapter modules or JCA resource adapters via the CPACache API
The two main use cases are implemented inLookupManager to retrieve adapter configuation andNormalizationManager to retrieve Party information
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 62
Packaging Adapter Components
SAP recommends to use SAP Software Deployment Manager (SDM) for deployment
Software Delivery Archives (SDA) can contain software components of different types (eg applications libraries)
Detailed version information and dependencies to other components simplify program management
Adapter Modules and Development
Summary
Adapter Framework Overview
Adapter Strategy
Agenda
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 64
Summary
Adapter Framework runs on J2EE Stack of SAP Web AS
Adapter Framework is platform for Adapter Engine and SAP PCK
Adapter Framework provides an extensible platform for developing and running adapters
Adapter Engine utilizes central configuration monitoring administration
Dual connectivity strategyAdapter Framework for comprehensive integration of adaptersInteroperability via open standards to interop with EAI providers
SAP NetWeaver Certification for adapters based on Adapter Framework available
Adapter mappings metadata stored in Integration Repository
Adapter Modules and Development
Summary
Adapter Framework Overview
Adapter Strategy
Agenda
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 43
SAP Exchange Infrastructure - Openness
Integration of SAP and non-SAP applicationsAdapter Framework for comprehensive integration of adaptersAdapters are used for technical connectivityAdapter metadata mappings are stored in Integration Repository
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 44
Dual Strategy
Dual connectivity strategyAdapter Framework for comprehensive integration of adapters to provide technical connectivity including central configurationadministration monitoring of adaptersInteroperability based on open standards (SOAP JMS HTTP(S)) tointeroperate with EAI providers
Value propositionStandardized interfaces allow easy integration of adapters from different partnersMinimum knowledge of end-to-end process integration requiredComprehensive integration avoids redundant maintenance ensures consistency enhances transparancyOpenness to integrate non-SAP applications 3rd party systems etcReduced TCO
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 45
Certification
CertificationSAP NetWeaver Certification of 3rd party adapters based on the adapter framework
Value propositionQuality (stability HA aspects performance etc) of adapters is controlledCertification helps customers to find right solutionQuick and convenient search for a variety of certified products with the online partner and product directory (httpwwwsapcompartnersdirectoriesSearchSolutionepx)Faster implementation time and lower integration costs through the use of tested 3rd party integrationReduced TCO
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 46
Adapter Mappings Metadata in Integration Repository
Adapter mappings and adapter metadata are stored in the Integration Repository
Centralized Integration Repository contains all relevant information for collaborative and integrative processesAll content adheres to open standards Adapters provide technical connectivity
Value propositionUse largest content catalogReduce costs in integration projectsReduce maintenance costsReduced TCO
Adapter Modules and Development
Summary
Adapter Framework Overview
Adapter Strategy
Agenda
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 48
For every adapter it is possible to define generic modules in the module processor possibility to extend the functionality of the specific adapter
Equivalent to the dispatcher classes in the J2SE adapter engine migration and examples
The default module configuration for the certain adapter is displayed in the channel configuration
Modules are EJBlsquos
Sequence matters
Module Processor Concept
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 49
Adapter Module Chain
Custom modulescan be added to default modulechains
Additional configurationparameters canbe specified eachmodule
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 50
Module Processor Documentation
SAP Help Portal (httphelpsapcom)SAP XI Runtime Connectivity Adapters Module ProcessorFeedback Mail to xidocumentationsapcom
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 51
Development Environment
Adapter development deployment and testing is possible on a single machine no full-blown PI XI is required
For testing purposes integration scenarioscan be configured in SAP PCK(eg loopback scenario)
Installation of SAP PCK already contains a sample adapter (including Adapter Meta Data) that should serve as a starting point
SAP Partner ConnectivityKit
Adapter FWMessagingQueuing
Security Handling
Resource
Adapter
PCK Configurationand Monitoring
FileDBJMSMarketplace
3rd Party Sys
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 52
Adapter Development Documentation
SAP Help Portal (httphelpsapcom)SAP XI Runtime Connectivity Partner Connectivity Kit Adapter DevelopmentFeedback Mail to xidocumentationsapcom
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 53
Requirements for Adapters (1)
Num AF Interface Category Description
1 JCA 10 conformance Mandatory Adapter must fulfill JCA 10 requirements (e g deployment) plus optional JCA 15 parts which are used by PI XI
2 AF Message Exchange Mandatory Adapter must be able to receive messages from AF and forward them to connected system and vice versa
3 AF Adapter Specific Modules
Optional SAP XI message and protocol conversion may be done entirely by the adapter or as adapter specific module and being called in the AF module chain context
4 Configuration Services Mandatory Unique configuration approach to manage adapters
5 Administrational Services
Optional Administration and Monitoring
6 Utility Service Mandatory Access to basic J2EE resources e g transactions and multithreading must be under control of J2EE server
7 Logging API Optional Adapters may use their own logging
8 Message Metadata Exchange
Optional Provide structure definition of message payloadIf not supported the definition of message types can be done in the Integration Repository
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 54
Requirements for Adapters (2)
Cluster-enabledConsider side-effects of clustering e g bdquoExactlyOnceInOrderldquo Avoid passing maneuvers
SpecializationBuild connection to exactly one type of business system or industrystandard protocol
DirectnessBuild connection to business system or industry standard protocoldirectly without any intermediate software components
SmoothnessLight-weighted low footprint adapter unnecessary system changes(many new or changed system DLL) should be avoided
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 55
Sample Adapter Source Code
Beside the API documentation a working sample adapter is shipped
The source code is available after installation
Analyzing the code helps understanding the Adapter Framework
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 56
Adapter Metadata
Adapter Metadata (AMD)XML file defines all configuration parameterseach adapter
AMD can be uploaded intoIntegration Iepositoryand SAP PCK
Configurationparameters are renderedinto the graphicalconfiguaration frontend
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 57
Adapter Metadata Fragment I
ltAdapterTypeMetaData version=09gt
ltTypegtNAESBltTypegt
ltInboundgt
ltTransportProtocolgt
ltChannelAttributesgt
ltAttributeGroupgt
ltNamegtCRYPTConfigurationltNamegt
ltGuiLabelsgtltLabel language=ENgtCryptographic ConfigurationltLabelgtltGuiLabelsgt
ltAttributeReferencegtltReferenceNamegtCRYPTUseSigningltReferenceNamegt
ltInboundgt
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 58
Adapter Metadata Fragment II
ltAttributegt
ltNamegtCRYPTUseSigningltNamegt
ltDataTypegtxsdbooleanltDataTypegt
ltGuiLabelsgt
ltLabel language=ENgtUse SigningltLabelgt
ltLabel language=DEgtVerwendung von SignierungltLabelgt
ltGuiLabelsgt
ltAttributegt
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 59
Adapter Configuration
Configuration attribute of type boolean is rendered to a check-box
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 60
Adapter Metadata Upload (PCK)
Integration Repositorydoes not exist in case ofSAP PCK installations
The upload mechanismfor Adaper Meta Datafor SAP PCK installationsrequires additonalparameters
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 61
AF CPA Cache
The Adapter configuration is deployed from the configuration time(SAP PCK or Integration Directory) to the J2EE service CPACache(Collaboration Profile Agreement)
The Adapter configuration can be accessed at runtime from withinadapter modules or JCA resource adapters via the CPACache API
The two main use cases are implemented inLookupManager to retrieve adapter configuation andNormalizationManager to retrieve Party information
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 62
Packaging Adapter Components
SAP recommends to use SAP Software Deployment Manager (SDM) for deployment
Software Delivery Archives (SDA) can contain software components of different types (eg applications libraries)
Detailed version information and dependencies to other components simplify program management
Adapter Modules and Development
Summary
Adapter Framework Overview
Adapter Strategy
Agenda
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 64
Summary
Adapter Framework runs on J2EE Stack of SAP Web AS
Adapter Framework is platform for Adapter Engine and SAP PCK
Adapter Framework provides an extensible platform for developing and running adapters
Adapter Engine utilizes central configuration monitoring administration
Dual connectivity strategyAdapter Framework for comprehensive integration of adaptersInteroperability via open standards to interop with EAI providers
SAP NetWeaver Certification for adapters based on Adapter Framework available
Adapter mappings metadata stored in Integration Repository
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 43
SAP Exchange Infrastructure - Openness
Integration of SAP and non-SAP applicationsAdapter Framework for comprehensive integration of adaptersAdapters are used for technical connectivityAdapter metadata mappings are stored in Integration Repository
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 44
Dual Strategy
Dual connectivity strategyAdapter Framework for comprehensive integration of adapters to provide technical connectivity including central configurationadministration monitoring of adaptersInteroperability based on open standards (SOAP JMS HTTP(S)) tointeroperate with EAI providers
Value propositionStandardized interfaces allow easy integration of adapters from different partnersMinimum knowledge of end-to-end process integration requiredComprehensive integration avoids redundant maintenance ensures consistency enhances transparancyOpenness to integrate non-SAP applications 3rd party systems etcReduced TCO
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 45
Certification
CertificationSAP NetWeaver Certification of 3rd party adapters based on the adapter framework
Value propositionQuality (stability HA aspects performance etc) of adapters is controlledCertification helps customers to find right solutionQuick and convenient search for a variety of certified products with the online partner and product directory (httpwwwsapcompartnersdirectoriesSearchSolutionepx)Faster implementation time and lower integration costs through the use of tested 3rd party integrationReduced TCO
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 46
Adapter Mappings Metadata in Integration Repository
Adapter mappings and adapter metadata are stored in the Integration Repository
Centralized Integration Repository contains all relevant information for collaborative and integrative processesAll content adheres to open standards Adapters provide technical connectivity
Value propositionUse largest content catalogReduce costs in integration projectsReduce maintenance costsReduced TCO
Adapter Modules and Development
Summary
Adapter Framework Overview
Adapter Strategy
Agenda
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 48
For every adapter it is possible to define generic modules in the module processor possibility to extend the functionality of the specific adapter
Equivalent to the dispatcher classes in the J2SE adapter engine migration and examples
The default module configuration for the certain adapter is displayed in the channel configuration
Modules are EJBlsquos
Sequence matters
Module Processor Concept
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 49
Adapter Module Chain
Custom modulescan be added to default modulechains
Additional configurationparameters canbe specified eachmodule
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 50
Module Processor Documentation
SAP Help Portal (httphelpsapcom)SAP XI Runtime Connectivity Adapters Module ProcessorFeedback Mail to xidocumentationsapcom
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 51
Development Environment
Adapter development deployment and testing is possible on a single machine no full-blown PI XI is required
For testing purposes integration scenarioscan be configured in SAP PCK(eg loopback scenario)
Installation of SAP PCK already contains a sample adapter (including Adapter Meta Data) that should serve as a starting point
SAP Partner ConnectivityKit
Adapter FWMessagingQueuing
Security Handling
Resource
Adapter
PCK Configurationand Monitoring
FileDBJMSMarketplace
3rd Party Sys
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 52
Adapter Development Documentation
SAP Help Portal (httphelpsapcom)SAP XI Runtime Connectivity Partner Connectivity Kit Adapter DevelopmentFeedback Mail to xidocumentationsapcom
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 53
Requirements for Adapters (1)
Num AF Interface Category Description
1 JCA 10 conformance Mandatory Adapter must fulfill JCA 10 requirements (e g deployment) plus optional JCA 15 parts which are used by PI XI
2 AF Message Exchange Mandatory Adapter must be able to receive messages from AF and forward them to connected system and vice versa
3 AF Adapter Specific Modules
Optional SAP XI message and protocol conversion may be done entirely by the adapter or as adapter specific module and being called in the AF module chain context
4 Configuration Services Mandatory Unique configuration approach to manage adapters
5 Administrational Services
Optional Administration and Monitoring
6 Utility Service Mandatory Access to basic J2EE resources e g transactions and multithreading must be under control of J2EE server
7 Logging API Optional Adapters may use their own logging
8 Message Metadata Exchange
Optional Provide structure definition of message payloadIf not supported the definition of message types can be done in the Integration Repository
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 54
Requirements for Adapters (2)
Cluster-enabledConsider side-effects of clustering e g bdquoExactlyOnceInOrderldquo Avoid passing maneuvers
SpecializationBuild connection to exactly one type of business system or industrystandard protocol
DirectnessBuild connection to business system or industry standard protocoldirectly without any intermediate software components
SmoothnessLight-weighted low footprint adapter unnecessary system changes(many new or changed system DLL) should be avoided
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 55
Sample Adapter Source Code
Beside the API documentation a working sample adapter is shipped
The source code is available after installation
Analyzing the code helps understanding the Adapter Framework
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 56
Adapter Metadata
Adapter Metadata (AMD)XML file defines all configuration parameterseach adapter
AMD can be uploaded intoIntegration Iepositoryand SAP PCK
Configurationparameters are renderedinto the graphicalconfiguaration frontend
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 57
Adapter Metadata Fragment I
ltAdapterTypeMetaData version=09gt
ltTypegtNAESBltTypegt
ltInboundgt
ltTransportProtocolgt
ltChannelAttributesgt
ltAttributeGroupgt
ltNamegtCRYPTConfigurationltNamegt
ltGuiLabelsgtltLabel language=ENgtCryptographic ConfigurationltLabelgtltGuiLabelsgt
ltAttributeReferencegtltReferenceNamegtCRYPTUseSigningltReferenceNamegt
ltInboundgt
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 58
Adapter Metadata Fragment II
ltAttributegt
ltNamegtCRYPTUseSigningltNamegt
ltDataTypegtxsdbooleanltDataTypegt
ltGuiLabelsgt
ltLabel language=ENgtUse SigningltLabelgt
ltLabel language=DEgtVerwendung von SignierungltLabelgt
ltGuiLabelsgt
ltAttributegt
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 59
Adapter Configuration
Configuration attribute of type boolean is rendered to a check-box
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 60
Adapter Metadata Upload (PCK)
Integration Repositorydoes not exist in case ofSAP PCK installations
The upload mechanismfor Adaper Meta Datafor SAP PCK installationsrequires additonalparameters
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 61
AF CPA Cache
The Adapter configuration is deployed from the configuration time(SAP PCK or Integration Directory) to the J2EE service CPACache(Collaboration Profile Agreement)
The Adapter configuration can be accessed at runtime from withinadapter modules or JCA resource adapters via the CPACache API
The two main use cases are implemented inLookupManager to retrieve adapter configuation andNormalizationManager to retrieve Party information
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 62
Packaging Adapter Components
SAP recommends to use SAP Software Deployment Manager (SDM) for deployment
Software Delivery Archives (SDA) can contain software components of different types (eg applications libraries)
Detailed version information and dependencies to other components simplify program management
Adapter Modules and Development
Summary
Adapter Framework Overview
Adapter Strategy
Agenda
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 64
Summary
Adapter Framework runs on J2EE Stack of SAP Web AS
Adapter Framework is platform for Adapter Engine and SAP PCK
Adapter Framework provides an extensible platform for developing and running adapters
Adapter Engine utilizes central configuration monitoring administration
Dual connectivity strategyAdapter Framework for comprehensive integration of adaptersInteroperability via open standards to interop with EAI providers
SAP NetWeaver Certification for adapters based on Adapter Framework available
Adapter mappings metadata stored in Integration Repository
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 44
Dual Strategy
Dual connectivity strategyAdapter Framework for comprehensive integration of adapters to provide technical connectivity including central configurationadministration monitoring of adaptersInteroperability based on open standards (SOAP JMS HTTP(S)) tointeroperate with EAI providers
Value propositionStandardized interfaces allow easy integration of adapters from different partnersMinimum knowledge of end-to-end process integration requiredComprehensive integration avoids redundant maintenance ensures consistency enhances transparancyOpenness to integrate non-SAP applications 3rd party systems etcReduced TCO
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 45
Certification
CertificationSAP NetWeaver Certification of 3rd party adapters based on the adapter framework
Value propositionQuality (stability HA aspects performance etc) of adapters is controlledCertification helps customers to find right solutionQuick and convenient search for a variety of certified products with the online partner and product directory (httpwwwsapcompartnersdirectoriesSearchSolutionepx)Faster implementation time and lower integration costs through the use of tested 3rd party integrationReduced TCO
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 46
Adapter Mappings Metadata in Integration Repository
Adapter mappings and adapter metadata are stored in the Integration Repository
Centralized Integration Repository contains all relevant information for collaborative and integrative processesAll content adheres to open standards Adapters provide technical connectivity
Value propositionUse largest content catalogReduce costs in integration projectsReduce maintenance costsReduced TCO
Adapter Modules and Development
Summary
Adapter Framework Overview
Adapter Strategy
Agenda
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 48
For every adapter it is possible to define generic modules in the module processor possibility to extend the functionality of the specific adapter
Equivalent to the dispatcher classes in the J2SE adapter engine migration and examples
The default module configuration for the certain adapter is displayed in the channel configuration
Modules are EJBlsquos
Sequence matters
Module Processor Concept
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 49
Adapter Module Chain
Custom modulescan be added to default modulechains
Additional configurationparameters canbe specified eachmodule
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 50
Module Processor Documentation
SAP Help Portal (httphelpsapcom)SAP XI Runtime Connectivity Adapters Module ProcessorFeedback Mail to xidocumentationsapcom
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 51
Development Environment
Adapter development deployment and testing is possible on a single machine no full-blown PI XI is required
For testing purposes integration scenarioscan be configured in SAP PCK(eg loopback scenario)
Installation of SAP PCK already contains a sample adapter (including Adapter Meta Data) that should serve as a starting point
SAP Partner ConnectivityKit
Adapter FWMessagingQueuing
Security Handling
Resource
Adapter
PCK Configurationand Monitoring
FileDBJMSMarketplace
3rd Party Sys
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 52
Adapter Development Documentation
SAP Help Portal (httphelpsapcom)SAP XI Runtime Connectivity Partner Connectivity Kit Adapter DevelopmentFeedback Mail to xidocumentationsapcom
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 53
Requirements for Adapters (1)
Num AF Interface Category Description
1 JCA 10 conformance Mandatory Adapter must fulfill JCA 10 requirements (e g deployment) plus optional JCA 15 parts which are used by PI XI
2 AF Message Exchange Mandatory Adapter must be able to receive messages from AF and forward them to connected system and vice versa
3 AF Adapter Specific Modules
Optional SAP XI message and protocol conversion may be done entirely by the adapter or as adapter specific module and being called in the AF module chain context
4 Configuration Services Mandatory Unique configuration approach to manage adapters
5 Administrational Services
Optional Administration and Monitoring
6 Utility Service Mandatory Access to basic J2EE resources e g transactions and multithreading must be under control of J2EE server
7 Logging API Optional Adapters may use their own logging
8 Message Metadata Exchange
Optional Provide structure definition of message payloadIf not supported the definition of message types can be done in the Integration Repository
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 54
Requirements for Adapters (2)
Cluster-enabledConsider side-effects of clustering e g bdquoExactlyOnceInOrderldquo Avoid passing maneuvers
SpecializationBuild connection to exactly one type of business system or industrystandard protocol
DirectnessBuild connection to business system or industry standard protocoldirectly without any intermediate software components
SmoothnessLight-weighted low footprint adapter unnecessary system changes(many new or changed system DLL) should be avoided
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 55
Sample Adapter Source Code
Beside the API documentation a working sample adapter is shipped
The source code is available after installation
Analyzing the code helps understanding the Adapter Framework
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 56
Adapter Metadata
Adapter Metadata (AMD)XML file defines all configuration parameterseach adapter
AMD can be uploaded intoIntegration Iepositoryand SAP PCK
Configurationparameters are renderedinto the graphicalconfiguaration frontend
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 57
Adapter Metadata Fragment I
ltAdapterTypeMetaData version=09gt
ltTypegtNAESBltTypegt
ltInboundgt
ltTransportProtocolgt
ltChannelAttributesgt
ltAttributeGroupgt
ltNamegtCRYPTConfigurationltNamegt
ltGuiLabelsgtltLabel language=ENgtCryptographic ConfigurationltLabelgtltGuiLabelsgt
ltAttributeReferencegtltReferenceNamegtCRYPTUseSigningltReferenceNamegt
ltInboundgt
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 58
Adapter Metadata Fragment II
ltAttributegt
ltNamegtCRYPTUseSigningltNamegt
ltDataTypegtxsdbooleanltDataTypegt
ltGuiLabelsgt
ltLabel language=ENgtUse SigningltLabelgt
ltLabel language=DEgtVerwendung von SignierungltLabelgt
ltGuiLabelsgt
ltAttributegt
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 59
Adapter Configuration
Configuration attribute of type boolean is rendered to a check-box
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 60
Adapter Metadata Upload (PCK)
Integration Repositorydoes not exist in case ofSAP PCK installations
The upload mechanismfor Adaper Meta Datafor SAP PCK installationsrequires additonalparameters
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 61
AF CPA Cache
The Adapter configuration is deployed from the configuration time(SAP PCK or Integration Directory) to the J2EE service CPACache(Collaboration Profile Agreement)
The Adapter configuration can be accessed at runtime from withinadapter modules or JCA resource adapters via the CPACache API
The two main use cases are implemented inLookupManager to retrieve adapter configuation andNormalizationManager to retrieve Party information
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 62
Packaging Adapter Components
SAP recommends to use SAP Software Deployment Manager (SDM) for deployment
Software Delivery Archives (SDA) can contain software components of different types (eg applications libraries)
Detailed version information and dependencies to other components simplify program management
Adapter Modules and Development
Summary
Adapter Framework Overview
Adapter Strategy
Agenda
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 64
Summary
Adapter Framework runs on J2EE Stack of SAP Web AS
Adapter Framework is platform for Adapter Engine and SAP PCK
Adapter Framework provides an extensible platform for developing and running adapters
Adapter Engine utilizes central configuration monitoring administration
Dual connectivity strategyAdapter Framework for comprehensive integration of adaptersInteroperability via open standards to interop with EAI providers
SAP NetWeaver Certification for adapters based on Adapter Framework available
Adapter mappings metadata stored in Integration Repository
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 45
Certification
CertificationSAP NetWeaver Certification of 3rd party adapters based on the adapter framework
Value propositionQuality (stability HA aspects performance etc) of adapters is controlledCertification helps customers to find right solutionQuick and convenient search for a variety of certified products with the online partner and product directory (httpwwwsapcompartnersdirectoriesSearchSolutionepx)Faster implementation time and lower integration costs through the use of tested 3rd party integrationReduced TCO
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 46
Adapter Mappings Metadata in Integration Repository
Adapter mappings and adapter metadata are stored in the Integration Repository
Centralized Integration Repository contains all relevant information for collaborative and integrative processesAll content adheres to open standards Adapters provide technical connectivity
Value propositionUse largest content catalogReduce costs in integration projectsReduce maintenance costsReduced TCO
Adapter Modules and Development
Summary
Adapter Framework Overview
Adapter Strategy
Agenda
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 48
For every adapter it is possible to define generic modules in the module processor possibility to extend the functionality of the specific adapter
Equivalent to the dispatcher classes in the J2SE adapter engine migration and examples
The default module configuration for the certain adapter is displayed in the channel configuration
Modules are EJBlsquos
Sequence matters
Module Processor Concept
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 49
Adapter Module Chain
Custom modulescan be added to default modulechains
Additional configurationparameters canbe specified eachmodule
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 50
Module Processor Documentation
SAP Help Portal (httphelpsapcom)SAP XI Runtime Connectivity Adapters Module ProcessorFeedback Mail to xidocumentationsapcom
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 51
Development Environment
Adapter development deployment and testing is possible on a single machine no full-blown PI XI is required
For testing purposes integration scenarioscan be configured in SAP PCK(eg loopback scenario)
Installation of SAP PCK already contains a sample adapter (including Adapter Meta Data) that should serve as a starting point
SAP Partner ConnectivityKit
Adapter FWMessagingQueuing
Security Handling
Resource
Adapter
PCK Configurationand Monitoring
FileDBJMSMarketplace
3rd Party Sys
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 52
Adapter Development Documentation
SAP Help Portal (httphelpsapcom)SAP XI Runtime Connectivity Partner Connectivity Kit Adapter DevelopmentFeedback Mail to xidocumentationsapcom
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 53
Requirements for Adapters (1)
Num AF Interface Category Description
1 JCA 10 conformance Mandatory Adapter must fulfill JCA 10 requirements (e g deployment) plus optional JCA 15 parts which are used by PI XI
2 AF Message Exchange Mandatory Adapter must be able to receive messages from AF and forward them to connected system and vice versa
3 AF Adapter Specific Modules
Optional SAP XI message and protocol conversion may be done entirely by the adapter or as adapter specific module and being called in the AF module chain context
4 Configuration Services Mandatory Unique configuration approach to manage adapters
5 Administrational Services
Optional Administration and Monitoring
6 Utility Service Mandatory Access to basic J2EE resources e g transactions and multithreading must be under control of J2EE server
7 Logging API Optional Adapters may use their own logging
8 Message Metadata Exchange
Optional Provide structure definition of message payloadIf not supported the definition of message types can be done in the Integration Repository
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 54
Requirements for Adapters (2)
Cluster-enabledConsider side-effects of clustering e g bdquoExactlyOnceInOrderldquo Avoid passing maneuvers
SpecializationBuild connection to exactly one type of business system or industrystandard protocol
DirectnessBuild connection to business system or industry standard protocoldirectly without any intermediate software components
SmoothnessLight-weighted low footprint adapter unnecessary system changes(many new or changed system DLL) should be avoided
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 55
Sample Adapter Source Code
Beside the API documentation a working sample adapter is shipped
The source code is available after installation
Analyzing the code helps understanding the Adapter Framework
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 56
Adapter Metadata
Adapter Metadata (AMD)XML file defines all configuration parameterseach adapter
AMD can be uploaded intoIntegration Iepositoryand SAP PCK
Configurationparameters are renderedinto the graphicalconfiguaration frontend
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 57
Adapter Metadata Fragment I
ltAdapterTypeMetaData version=09gt
ltTypegtNAESBltTypegt
ltInboundgt
ltTransportProtocolgt
ltChannelAttributesgt
ltAttributeGroupgt
ltNamegtCRYPTConfigurationltNamegt
ltGuiLabelsgtltLabel language=ENgtCryptographic ConfigurationltLabelgtltGuiLabelsgt
ltAttributeReferencegtltReferenceNamegtCRYPTUseSigningltReferenceNamegt
ltInboundgt
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 58
Adapter Metadata Fragment II
ltAttributegt
ltNamegtCRYPTUseSigningltNamegt
ltDataTypegtxsdbooleanltDataTypegt
ltGuiLabelsgt
ltLabel language=ENgtUse SigningltLabelgt
ltLabel language=DEgtVerwendung von SignierungltLabelgt
ltGuiLabelsgt
ltAttributegt
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 59
Adapter Configuration
Configuration attribute of type boolean is rendered to a check-box
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 60
Adapter Metadata Upload (PCK)
Integration Repositorydoes not exist in case ofSAP PCK installations
The upload mechanismfor Adaper Meta Datafor SAP PCK installationsrequires additonalparameters
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 61
AF CPA Cache
The Adapter configuration is deployed from the configuration time(SAP PCK or Integration Directory) to the J2EE service CPACache(Collaboration Profile Agreement)
The Adapter configuration can be accessed at runtime from withinadapter modules or JCA resource adapters via the CPACache API
The two main use cases are implemented inLookupManager to retrieve adapter configuation andNormalizationManager to retrieve Party information
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 62
Packaging Adapter Components
SAP recommends to use SAP Software Deployment Manager (SDM) for deployment
Software Delivery Archives (SDA) can contain software components of different types (eg applications libraries)
Detailed version information and dependencies to other components simplify program management
Adapter Modules and Development
Summary
Adapter Framework Overview
Adapter Strategy
Agenda
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 64
Summary
Adapter Framework runs on J2EE Stack of SAP Web AS
Adapter Framework is platform for Adapter Engine and SAP PCK
Adapter Framework provides an extensible platform for developing and running adapters
Adapter Engine utilizes central configuration monitoring administration
Dual connectivity strategyAdapter Framework for comprehensive integration of adaptersInteroperability via open standards to interop with EAI providers
SAP NetWeaver Certification for adapters based on Adapter Framework available
Adapter mappings metadata stored in Integration Repository
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 46
Adapter Mappings Metadata in Integration Repository
Adapter mappings and adapter metadata are stored in the Integration Repository
Centralized Integration Repository contains all relevant information for collaborative and integrative processesAll content adheres to open standards Adapters provide technical connectivity
Value propositionUse largest content catalogReduce costs in integration projectsReduce maintenance costsReduced TCO
Adapter Modules and Development
Summary
Adapter Framework Overview
Adapter Strategy
Agenda
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 48
For every adapter it is possible to define generic modules in the module processor possibility to extend the functionality of the specific adapter
Equivalent to the dispatcher classes in the J2SE adapter engine migration and examples
The default module configuration for the certain adapter is displayed in the channel configuration
Modules are EJBlsquos
Sequence matters
Module Processor Concept
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 49
Adapter Module Chain
Custom modulescan be added to default modulechains
Additional configurationparameters canbe specified eachmodule
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 50
Module Processor Documentation
SAP Help Portal (httphelpsapcom)SAP XI Runtime Connectivity Adapters Module ProcessorFeedback Mail to xidocumentationsapcom
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 51
Development Environment
Adapter development deployment and testing is possible on a single machine no full-blown PI XI is required
For testing purposes integration scenarioscan be configured in SAP PCK(eg loopback scenario)
Installation of SAP PCK already contains a sample adapter (including Adapter Meta Data) that should serve as a starting point
SAP Partner ConnectivityKit
Adapter FWMessagingQueuing
Security Handling
Resource
Adapter
PCK Configurationand Monitoring
FileDBJMSMarketplace
3rd Party Sys
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 52
Adapter Development Documentation
SAP Help Portal (httphelpsapcom)SAP XI Runtime Connectivity Partner Connectivity Kit Adapter DevelopmentFeedback Mail to xidocumentationsapcom
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 53
Requirements for Adapters (1)
Num AF Interface Category Description
1 JCA 10 conformance Mandatory Adapter must fulfill JCA 10 requirements (e g deployment) plus optional JCA 15 parts which are used by PI XI
2 AF Message Exchange Mandatory Adapter must be able to receive messages from AF and forward them to connected system and vice versa
3 AF Adapter Specific Modules
Optional SAP XI message and protocol conversion may be done entirely by the adapter or as adapter specific module and being called in the AF module chain context
4 Configuration Services Mandatory Unique configuration approach to manage adapters
5 Administrational Services
Optional Administration and Monitoring
6 Utility Service Mandatory Access to basic J2EE resources e g transactions and multithreading must be under control of J2EE server
7 Logging API Optional Adapters may use their own logging
8 Message Metadata Exchange
Optional Provide structure definition of message payloadIf not supported the definition of message types can be done in the Integration Repository
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 54
Requirements for Adapters (2)
Cluster-enabledConsider side-effects of clustering e g bdquoExactlyOnceInOrderldquo Avoid passing maneuvers
SpecializationBuild connection to exactly one type of business system or industrystandard protocol
DirectnessBuild connection to business system or industry standard protocoldirectly without any intermediate software components
SmoothnessLight-weighted low footprint adapter unnecessary system changes(many new or changed system DLL) should be avoided
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 55
Sample Adapter Source Code
Beside the API documentation a working sample adapter is shipped
The source code is available after installation
Analyzing the code helps understanding the Adapter Framework
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 56
Adapter Metadata
Adapter Metadata (AMD)XML file defines all configuration parameterseach adapter
AMD can be uploaded intoIntegration Iepositoryand SAP PCK
Configurationparameters are renderedinto the graphicalconfiguaration frontend
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 57
Adapter Metadata Fragment I
ltAdapterTypeMetaData version=09gt
ltTypegtNAESBltTypegt
ltInboundgt
ltTransportProtocolgt
ltChannelAttributesgt
ltAttributeGroupgt
ltNamegtCRYPTConfigurationltNamegt
ltGuiLabelsgtltLabel language=ENgtCryptographic ConfigurationltLabelgtltGuiLabelsgt
ltAttributeReferencegtltReferenceNamegtCRYPTUseSigningltReferenceNamegt
ltInboundgt
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 58
Adapter Metadata Fragment II
ltAttributegt
ltNamegtCRYPTUseSigningltNamegt
ltDataTypegtxsdbooleanltDataTypegt
ltGuiLabelsgt
ltLabel language=ENgtUse SigningltLabelgt
ltLabel language=DEgtVerwendung von SignierungltLabelgt
ltGuiLabelsgt
ltAttributegt
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 59
Adapter Configuration
Configuration attribute of type boolean is rendered to a check-box
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 60
Adapter Metadata Upload (PCK)
Integration Repositorydoes not exist in case ofSAP PCK installations
The upload mechanismfor Adaper Meta Datafor SAP PCK installationsrequires additonalparameters
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 61
AF CPA Cache
The Adapter configuration is deployed from the configuration time(SAP PCK or Integration Directory) to the J2EE service CPACache(Collaboration Profile Agreement)
The Adapter configuration can be accessed at runtime from withinadapter modules or JCA resource adapters via the CPACache API
The two main use cases are implemented inLookupManager to retrieve adapter configuation andNormalizationManager to retrieve Party information
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 62
Packaging Adapter Components
SAP recommends to use SAP Software Deployment Manager (SDM) for deployment
Software Delivery Archives (SDA) can contain software components of different types (eg applications libraries)
Detailed version information and dependencies to other components simplify program management
Adapter Modules and Development
Summary
Adapter Framework Overview
Adapter Strategy
Agenda
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 64
Summary
Adapter Framework runs on J2EE Stack of SAP Web AS
Adapter Framework is platform for Adapter Engine and SAP PCK
Adapter Framework provides an extensible platform for developing and running adapters
Adapter Engine utilizes central configuration monitoring administration
Dual connectivity strategyAdapter Framework for comprehensive integration of adaptersInteroperability via open standards to interop with EAI providers
SAP NetWeaver Certification for adapters based on Adapter Framework available
Adapter mappings metadata stored in Integration Repository
Adapter Modules and Development
Summary
Adapter Framework Overview
Adapter Strategy
Agenda
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 48
For every adapter it is possible to define generic modules in the module processor possibility to extend the functionality of the specific adapter
Equivalent to the dispatcher classes in the J2SE adapter engine migration and examples
The default module configuration for the certain adapter is displayed in the channel configuration
Modules are EJBlsquos
Sequence matters
Module Processor Concept
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 49
Adapter Module Chain
Custom modulescan be added to default modulechains
Additional configurationparameters canbe specified eachmodule
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 50
Module Processor Documentation
SAP Help Portal (httphelpsapcom)SAP XI Runtime Connectivity Adapters Module ProcessorFeedback Mail to xidocumentationsapcom
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 51
Development Environment
Adapter development deployment and testing is possible on a single machine no full-blown PI XI is required
For testing purposes integration scenarioscan be configured in SAP PCK(eg loopback scenario)
Installation of SAP PCK already contains a sample adapter (including Adapter Meta Data) that should serve as a starting point
SAP Partner ConnectivityKit
Adapter FWMessagingQueuing
Security Handling
Resource
Adapter
PCK Configurationand Monitoring
FileDBJMSMarketplace
3rd Party Sys
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 52
Adapter Development Documentation
SAP Help Portal (httphelpsapcom)SAP XI Runtime Connectivity Partner Connectivity Kit Adapter DevelopmentFeedback Mail to xidocumentationsapcom
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 53
Requirements for Adapters (1)
Num AF Interface Category Description
1 JCA 10 conformance Mandatory Adapter must fulfill JCA 10 requirements (e g deployment) plus optional JCA 15 parts which are used by PI XI
2 AF Message Exchange Mandatory Adapter must be able to receive messages from AF and forward them to connected system and vice versa
3 AF Adapter Specific Modules
Optional SAP XI message and protocol conversion may be done entirely by the adapter or as adapter specific module and being called in the AF module chain context
4 Configuration Services Mandatory Unique configuration approach to manage adapters
5 Administrational Services
Optional Administration and Monitoring
6 Utility Service Mandatory Access to basic J2EE resources e g transactions and multithreading must be under control of J2EE server
7 Logging API Optional Adapters may use their own logging
8 Message Metadata Exchange
Optional Provide structure definition of message payloadIf not supported the definition of message types can be done in the Integration Repository
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 54
Requirements for Adapters (2)
Cluster-enabledConsider side-effects of clustering e g bdquoExactlyOnceInOrderldquo Avoid passing maneuvers
SpecializationBuild connection to exactly one type of business system or industrystandard protocol
DirectnessBuild connection to business system or industry standard protocoldirectly without any intermediate software components
SmoothnessLight-weighted low footprint adapter unnecessary system changes(many new or changed system DLL) should be avoided
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 55
Sample Adapter Source Code
Beside the API documentation a working sample adapter is shipped
The source code is available after installation
Analyzing the code helps understanding the Adapter Framework
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 56
Adapter Metadata
Adapter Metadata (AMD)XML file defines all configuration parameterseach adapter
AMD can be uploaded intoIntegration Iepositoryand SAP PCK
Configurationparameters are renderedinto the graphicalconfiguaration frontend
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 57
Adapter Metadata Fragment I
ltAdapterTypeMetaData version=09gt
ltTypegtNAESBltTypegt
ltInboundgt
ltTransportProtocolgt
ltChannelAttributesgt
ltAttributeGroupgt
ltNamegtCRYPTConfigurationltNamegt
ltGuiLabelsgtltLabel language=ENgtCryptographic ConfigurationltLabelgtltGuiLabelsgt
ltAttributeReferencegtltReferenceNamegtCRYPTUseSigningltReferenceNamegt
ltInboundgt
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 58
Adapter Metadata Fragment II
ltAttributegt
ltNamegtCRYPTUseSigningltNamegt
ltDataTypegtxsdbooleanltDataTypegt
ltGuiLabelsgt
ltLabel language=ENgtUse SigningltLabelgt
ltLabel language=DEgtVerwendung von SignierungltLabelgt
ltGuiLabelsgt
ltAttributegt
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 59
Adapter Configuration
Configuration attribute of type boolean is rendered to a check-box
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 60
Adapter Metadata Upload (PCK)
Integration Repositorydoes not exist in case ofSAP PCK installations
The upload mechanismfor Adaper Meta Datafor SAP PCK installationsrequires additonalparameters
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 61
AF CPA Cache
The Adapter configuration is deployed from the configuration time(SAP PCK or Integration Directory) to the J2EE service CPACache(Collaboration Profile Agreement)
The Adapter configuration can be accessed at runtime from withinadapter modules or JCA resource adapters via the CPACache API
The two main use cases are implemented inLookupManager to retrieve adapter configuation andNormalizationManager to retrieve Party information
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 62
Packaging Adapter Components
SAP recommends to use SAP Software Deployment Manager (SDM) for deployment
Software Delivery Archives (SDA) can contain software components of different types (eg applications libraries)
Detailed version information and dependencies to other components simplify program management
Adapter Modules and Development
Summary
Adapter Framework Overview
Adapter Strategy
Agenda
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 64
Summary
Adapter Framework runs on J2EE Stack of SAP Web AS
Adapter Framework is platform for Adapter Engine and SAP PCK
Adapter Framework provides an extensible platform for developing and running adapters
Adapter Engine utilizes central configuration monitoring administration
Dual connectivity strategyAdapter Framework for comprehensive integration of adaptersInteroperability via open standards to interop with EAI providers
SAP NetWeaver Certification for adapters based on Adapter Framework available
Adapter mappings metadata stored in Integration Repository
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 48
For every adapter it is possible to define generic modules in the module processor possibility to extend the functionality of the specific adapter
Equivalent to the dispatcher classes in the J2SE adapter engine migration and examples
The default module configuration for the certain adapter is displayed in the channel configuration
Modules are EJBlsquos
Sequence matters
Module Processor Concept
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 49
Adapter Module Chain
Custom modulescan be added to default modulechains
Additional configurationparameters canbe specified eachmodule
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 50
Module Processor Documentation
SAP Help Portal (httphelpsapcom)SAP XI Runtime Connectivity Adapters Module ProcessorFeedback Mail to xidocumentationsapcom
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 51
Development Environment
Adapter development deployment and testing is possible on a single machine no full-blown PI XI is required
For testing purposes integration scenarioscan be configured in SAP PCK(eg loopback scenario)
Installation of SAP PCK already contains a sample adapter (including Adapter Meta Data) that should serve as a starting point
SAP Partner ConnectivityKit
Adapter FWMessagingQueuing
Security Handling
Resource
Adapter
PCK Configurationand Monitoring
FileDBJMSMarketplace
3rd Party Sys
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 52
Adapter Development Documentation
SAP Help Portal (httphelpsapcom)SAP XI Runtime Connectivity Partner Connectivity Kit Adapter DevelopmentFeedback Mail to xidocumentationsapcom
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 53
Requirements for Adapters (1)
Num AF Interface Category Description
1 JCA 10 conformance Mandatory Adapter must fulfill JCA 10 requirements (e g deployment) plus optional JCA 15 parts which are used by PI XI
2 AF Message Exchange Mandatory Adapter must be able to receive messages from AF and forward them to connected system and vice versa
3 AF Adapter Specific Modules
Optional SAP XI message and protocol conversion may be done entirely by the adapter or as adapter specific module and being called in the AF module chain context
4 Configuration Services Mandatory Unique configuration approach to manage adapters
5 Administrational Services
Optional Administration and Monitoring
6 Utility Service Mandatory Access to basic J2EE resources e g transactions and multithreading must be under control of J2EE server
7 Logging API Optional Adapters may use their own logging
8 Message Metadata Exchange
Optional Provide structure definition of message payloadIf not supported the definition of message types can be done in the Integration Repository
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 54
Requirements for Adapters (2)
Cluster-enabledConsider side-effects of clustering e g bdquoExactlyOnceInOrderldquo Avoid passing maneuvers
SpecializationBuild connection to exactly one type of business system or industrystandard protocol
DirectnessBuild connection to business system or industry standard protocoldirectly without any intermediate software components
SmoothnessLight-weighted low footprint adapter unnecessary system changes(many new or changed system DLL) should be avoided
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 55
Sample Adapter Source Code
Beside the API documentation a working sample adapter is shipped
The source code is available after installation
Analyzing the code helps understanding the Adapter Framework
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 56
Adapter Metadata
Adapter Metadata (AMD)XML file defines all configuration parameterseach adapter
AMD can be uploaded intoIntegration Iepositoryand SAP PCK
Configurationparameters are renderedinto the graphicalconfiguaration frontend
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 57
Adapter Metadata Fragment I
ltAdapterTypeMetaData version=09gt
ltTypegtNAESBltTypegt
ltInboundgt
ltTransportProtocolgt
ltChannelAttributesgt
ltAttributeGroupgt
ltNamegtCRYPTConfigurationltNamegt
ltGuiLabelsgtltLabel language=ENgtCryptographic ConfigurationltLabelgtltGuiLabelsgt
ltAttributeReferencegtltReferenceNamegtCRYPTUseSigningltReferenceNamegt
ltInboundgt
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 58
Adapter Metadata Fragment II
ltAttributegt
ltNamegtCRYPTUseSigningltNamegt
ltDataTypegtxsdbooleanltDataTypegt
ltGuiLabelsgt
ltLabel language=ENgtUse SigningltLabelgt
ltLabel language=DEgtVerwendung von SignierungltLabelgt
ltGuiLabelsgt
ltAttributegt
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 59
Adapter Configuration
Configuration attribute of type boolean is rendered to a check-box
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 60
Adapter Metadata Upload (PCK)
Integration Repositorydoes not exist in case ofSAP PCK installations
The upload mechanismfor Adaper Meta Datafor SAP PCK installationsrequires additonalparameters
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 61
AF CPA Cache
The Adapter configuration is deployed from the configuration time(SAP PCK or Integration Directory) to the J2EE service CPACache(Collaboration Profile Agreement)
The Adapter configuration can be accessed at runtime from withinadapter modules or JCA resource adapters via the CPACache API
The two main use cases are implemented inLookupManager to retrieve adapter configuation andNormalizationManager to retrieve Party information
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 62
Packaging Adapter Components
SAP recommends to use SAP Software Deployment Manager (SDM) for deployment
Software Delivery Archives (SDA) can contain software components of different types (eg applications libraries)
Detailed version information and dependencies to other components simplify program management
Adapter Modules and Development
Summary
Adapter Framework Overview
Adapter Strategy
Agenda
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 64
Summary
Adapter Framework runs on J2EE Stack of SAP Web AS
Adapter Framework is platform for Adapter Engine and SAP PCK
Adapter Framework provides an extensible platform for developing and running adapters
Adapter Engine utilizes central configuration monitoring administration
Dual connectivity strategyAdapter Framework for comprehensive integration of adaptersInteroperability via open standards to interop with EAI providers
SAP NetWeaver Certification for adapters based on Adapter Framework available
Adapter mappings metadata stored in Integration Repository
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 49
Adapter Module Chain
Custom modulescan be added to default modulechains
Additional configurationparameters canbe specified eachmodule
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 50
Module Processor Documentation
SAP Help Portal (httphelpsapcom)SAP XI Runtime Connectivity Adapters Module ProcessorFeedback Mail to xidocumentationsapcom
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 51
Development Environment
Adapter development deployment and testing is possible on a single machine no full-blown PI XI is required
For testing purposes integration scenarioscan be configured in SAP PCK(eg loopback scenario)
Installation of SAP PCK already contains a sample adapter (including Adapter Meta Data) that should serve as a starting point
SAP Partner ConnectivityKit
Adapter FWMessagingQueuing
Security Handling
Resource
Adapter
PCK Configurationand Monitoring
FileDBJMSMarketplace
3rd Party Sys
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 52
Adapter Development Documentation
SAP Help Portal (httphelpsapcom)SAP XI Runtime Connectivity Partner Connectivity Kit Adapter DevelopmentFeedback Mail to xidocumentationsapcom
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 53
Requirements for Adapters (1)
Num AF Interface Category Description
1 JCA 10 conformance Mandatory Adapter must fulfill JCA 10 requirements (e g deployment) plus optional JCA 15 parts which are used by PI XI
2 AF Message Exchange Mandatory Adapter must be able to receive messages from AF and forward them to connected system and vice versa
3 AF Adapter Specific Modules
Optional SAP XI message and protocol conversion may be done entirely by the adapter or as adapter specific module and being called in the AF module chain context
4 Configuration Services Mandatory Unique configuration approach to manage adapters
5 Administrational Services
Optional Administration and Monitoring
6 Utility Service Mandatory Access to basic J2EE resources e g transactions and multithreading must be under control of J2EE server
7 Logging API Optional Adapters may use their own logging
8 Message Metadata Exchange
Optional Provide structure definition of message payloadIf not supported the definition of message types can be done in the Integration Repository
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 54
Requirements for Adapters (2)
Cluster-enabledConsider side-effects of clustering e g bdquoExactlyOnceInOrderldquo Avoid passing maneuvers
SpecializationBuild connection to exactly one type of business system or industrystandard protocol
DirectnessBuild connection to business system or industry standard protocoldirectly without any intermediate software components
SmoothnessLight-weighted low footprint adapter unnecessary system changes(many new or changed system DLL) should be avoided
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 55
Sample Adapter Source Code
Beside the API documentation a working sample adapter is shipped
The source code is available after installation
Analyzing the code helps understanding the Adapter Framework
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 56
Adapter Metadata
Adapter Metadata (AMD)XML file defines all configuration parameterseach adapter
AMD can be uploaded intoIntegration Iepositoryand SAP PCK
Configurationparameters are renderedinto the graphicalconfiguaration frontend
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 57
Adapter Metadata Fragment I
ltAdapterTypeMetaData version=09gt
ltTypegtNAESBltTypegt
ltInboundgt
ltTransportProtocolgt
ltChannelAttributesgt
ltAttributeGroupgt
ltNamegtCRYPTConfigurationltNamegt
ltGuiLabelsgtltLabel language=ENgtCryptographic ConfigurationltLabelgtltGuiLabelsgt
ltAttributeReferencegtltReferenceNamegtCRYPTUseSigningltReferenceNamegt
ltInboundgt
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 58
Adapter Metadata Fragment II
ltAttributegt
ltNamegtCRYPTUseSigningltNamegt
ltDataTypegtxsdbooleanltDataTypegt
ltGuiLabelsgt
ltLabel language=ENgtUse SigningltLabelgt
ltLabel language=DEgtVerwendung von SignierungltLabelgt
ltGuiLabelsgt
ltAttributegt
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 59
Adapter Configuration
Configuration attribute of type boolean is rendered to a check-box
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 60
Adapter Metadata Upload (PCK)
Integration Repositorydoes not exist in case ofSAP PCK installations
The upload mechanismfor Adaper Meta Datafor SAP PCK installationsrequires additonalparameters
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 61
AF CPA Cache
The Adapter configuration is deployed from the configuration time(SAP PCK or Integration Directory) to the J2EE service CPACache(Collaboration Profile Agreement)
The Adapter configuration can be accessed at runtime from withinadapter modules or JCA resource adapters via the CPACache API
The two main use cases are implemented inLookupManager to retrieve adapter configuation andNormalizationManager to retrieve Party information
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 62
Packaging Adapter Components
SAP recommends to use SAP Software Deployment Manager (SDM) for deployment
Software Delivery Archives (SDA) can contain software components of different types (eg applications libraries)
Detailed version information and dependencies to other components simplify program management
Adapter Modules and Development
Summary
Adapter Framework Overview
Adapter Strategy
Agenda
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 64
Summary
Adapter Framework runs on J2EE Stack of SAP Web AS
Adapter Framework is platform for Adapter Engine and SAP PCK
Adapter Framework provides an extensible platform for developing and running adapters
Adapter Engine utilizes central configuration monitoring administration
Dual connectivity strategyAdapter Framework for comprehensive integration of adaptersInteroperability via open standards to interop with EAI providers
SAP NetWeaver Certification for adapters based on Adapter Framework available
Adapter mappings metadata stored in Integration Repository
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 50
Module Processor Documentation
SAP Help Portal (httphelpsapcom)SAP XI Runtime Connectivity Adapters Module ProcessorFeedback Mail to xidocumentationsapcom
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 51
Development Environment
Adapter development deployment and testing is possible on a single machine no full-blown PI XI is required
For testing purposes integration scenarioscan be configured in SAP PCK(eg loopback scenario)
Installation of SAP PCK already contains a sample adapter (including Adapter Meta Data) that should serve as a starting point
SAP Partner ConnectivityKit
Adapter FWMessagingQueuing
Security Handling
Resource
Adapter
PCK Configurationand Monitoring
FileDBJMSMarketplace
3rd Party Sys
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 52
Adapter Development Documentation
SAP Help Portal (httphelpsapcom)SAP XI Runtime Connectivity Partner Connectivity Kit Adapter DevelopmentFeedback Mail to xidocumentationsapcom
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 53
Requirements for Adapters (1)
Num AF Interface Category Description
1 JCA 10 conformance Mandatory Adapter must fulfill JCA 10 requirements (e g deployment) plus optional JCA 15 parts which are used by PI XI
2 AF Message Exchange Mandatory Adapter must be able to receive messages from AF and forward them to connected system and vice versa
3 AF Adapter Specific Modules
Optional SAP XI message and protocol conversion may be done entirely by the adapter or as adapter specific module and being called in the AF module chain context
4 Configuration Services Mandatory Unique configuration approach to manage adapters
5 Administrational Services
Optional Administration and Monitoring
6 Utility Service Mandatory Access to basic J2EE resources e g transactions and multithreading must be under control of J2EE server
7 Logging API Optional Adapters may use their own logging
8 Message Metadata Exchange
Optional Provide structure definition of message payloadIf not supported the definition of message types can be done in the Integration Repository
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 54
Requirements for Adapters (2)
Cluster-enabledConsider side-effects of clustering e g bdquoExactlyOnceInOrderldquo Avoid passing maneuvers
SpecializationBuild connection to exactly one type of business system or industrystandard protocol
DirectnessBuild connection to business system or industry standard protocoldirectly without any intermediate software components
SmoothnessLight-weighted low footprint adapter unnecessary system changes(many new or changed system DLL) should be avoided
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 55
Sample Adapter Source Code
Beside the API documentation a working sample adapter is shipped
The source code is available after installation
Analyzing the code helps understanding the Adapter Framework
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 56
Adapter Metadata
Adapter Metadata (AMD)XML file defines all configuration parameterseach adapter
AMD can be uploaded intoIntegration Iepositoryand SAP PCK
Configurationparameters are renderedinto the graphicalconfiguaration frontend
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 57
Adapter Metadata Fragment I
ltAdapterTypeMetaData version=09gt
ltTypegtNAESBltTypegt
ltInboundgt
ltTransportProtocolgt
ltChannelAttributesgt
ltAttributeGroupgt
ltNamegtCRYPTConfigurationltNamegt
ltGuiLabelsgtltLabel language=ENgtCryptographic ConfigurationltLabelgtltGuiLabelsgt
ltAttributeReferencegtltReferenceNamegtCRYPTUseSigningltReferenceNamegt
ltInboundgt
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 58
Adapter Metadata Fragment II
ltAttributegt
ltNamegtCRYPTUseSigningltNamegt
ltDataTypegtxsdbooleanltDataTypegt
ltGuiLabelsgt
ltLabel language=ENgtUse SigningltLabelgt
ltLabel language=DEgtVerwendung von SignierungltLabelgt
ltGuiLabelsgt
ltAttributegt
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 59
Adapter Configuration
Configuration attribute of type boolean is rendered to a check-box
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 60
Adapter Metadata Upload (PCK)
Integration Repositorydoes not exist in case ofSAP PCK installations
The upload mechanismfor Adaper Meta Datafor SAP PCK installationsrequires additonalparameters
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 61
AF CPA Cache
The Adapter configuration is deployed from the configuration time(SAP PCK or Integration Directory) to the J2EE service CPACache(Collaboration Profile Agreement)
The Adapter configuration can be accessed at runtime from withinadapter modules or JCA resource adapters via the CPACache API
The two main use cases are implemented inLookupManager to retrieve adapter configuation andNormalizationManager to retrieve Party information
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 62
Packaging Adapter Components
SAP recommends to use SAP Software Deployment Manager (SDM) for deployment
Software Delivery Archives (SDA) can contain software components of different types (eg applications libraries)
Detailed version information and dependencies to other components simplify program management
Adapter Modules and Development
Summary
Adapter Framework Overview
Adapter Strategy
Agenda
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 64
Summary
Adapter Framework runs on J2EE Stack of SAP Web AS
Adapter Framework is platform for Adapter Engine and SAP PCK
Adapter Framework provides an extensible platform for developing and running adapters
Adapter Engine utilizes central configuration monitoring administration
Dual connectivity strategyAdapter Framework for comprehensive integration of adaptersInteroperability via open standards to interop with EAI providers
SAP NetWeaver Certification for adapters based on Adapter Framework available
Adapter mappings metadata stored in Integration Repository
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 51
Development Environment
Adapter development deployment and testing is possible on a single machine no full-blown PI XI is required
For testing purposes integration scenarioscan be configured in SAP PCK(eg loopback scenario)
Installation of SAP PCK already contains a sample adapter (including Adapter Meta Data) that should serve as a starting point
SAP Partner ConnectivityKit
Adapter FWMessagingQueuing
Security Handling
Resource
Adapter
PCK Configurationand Monitoring
FileDBJMSMarketplace
3rd Party Sys
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 52
Adapter Development Documentation
SAP Help Portal (httphelpsapcom)SAP XI Runtime Connectivity Partner Connectivity Kit Adapter DevelopmentFeedback Mail to xidocumentationsapcom
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 53
Requirements for Adapters (1)
Num AF Interface Category Description
1 JCA 10 conformance Mandatory Adapter must fulfill JCA 10 requirements (e g deployment) plus optional JCA 15 parts which are used by PI XI
2 AF Message Exchange Mandatory Adapter must be able to receive messages from AF and forward them to connected system and vice versa
3 AF Adapter Specific Modules
Optional SAP XI message and protocol conversion may be done entirely by the adapter or as adapter specific module and being called in the AF module chain context
4 Configuration Services Mandatory Unique configuration approach to manage adapters
5 Administrational Services
Optional Administration and Monitoring
6 Utility Service Mandatory Access to basic J2EE resources e g transactions and multithreading must be under control of J2EE server
7 Logging API Optional Adapters may use their own logging
8 Message Metadata Exchange
Optional Provide structure definition of message payloadIf not supported the definition of message types can be done in the Integration Repository
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 54
Requirements for Adapters (2)
Cluster-enabledConsider side-effects of clustering e g bdquoExactlyOnceInOrderldquo Avoid passing maneuvers
SpecializationBuild connection to exactly one type of business system or industrystandard protocol
DirectnessBuild connection to business system or industry standard protocoldirectly without any intermediate software components
SmoothnessLight-weighted low footprint adapter unnecessary system changes(many new or changed system DLL) should be avoided
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 55
Sample Adapter Source Code
Beside the API documentation a working sample adapter is shipped
The source code is available after installation
Analyzing the code helps understanding the Adapter Framework
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 56
Adapter Metadata
Adapter Metadata (AMD)XML file defines all configuration parameterseach adapter
AMD can be uploaded intoIntegration Iepositoryand SAP PCK
Configurationparameters are renderedinto the graphicalconfiguaration frontend
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 57
Adapter Metadata Fragment I
ltAdapterTypeMetaData version=09gt
ltTypegtNAESBltTypegt
ltInboundgt
ltTransportProtocolgt
ltChannelAttributesgt
ltAttributeGroupgt
ltNamegtCRYPTConfigurationltNamegt
ltGuiLabelsgtltLabel language=ENgtCryptographic ConfigurationltLabelgtltGuiLabelsgt
ltAttributeReferencegtltReferenceNamegtCRYPTUseSigningltReferenceNamegt
ltInboundgt
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 58
Adapter Metadata Fragment II
ltAttributegt
ltNamegtCRYPTUseSigningltNamegt
ltDataTypegtxsdbooleanltDataTypegt
ltGuiLabelsgt
ltLabel language=ENgtUse SigningltLabelgt
ltLabel language=DEgtVerwendung von SignierungltLabelgt
ltGuiLabelsgt
ltAttributegt
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 59
Adapter Configuration
Configuration attribute of type boolean is rendered to a check-box
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 60
Adapter Metadata Upload (PCK)
Integration Repositorydoes not exist in case ofSAP PCK installations
The upload mechanismfor Adaper Meta Datafor SAP PCK installationsrequires additonalparameters
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 61
AF CPA Cache
The Adapter configuration is deployed from the configuration time(SAP PCK or Integration Directory) to the J2EE service CPACache(Collaboration Profile Agreement)
The Adapter configuration can be accessed at runtime from withinadapter modules or JCA resource adapters via the CPACache API
The two main use cases are implemented inLookupManager to retrieve adapter configuation andNormalizationManager to retrieve Party information
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 62
Packaging Adapter Components
SAP recommends to use SAP Software Deployment Manager (SDM) for deployment
Software Delivery Archives (SDA) can contain software components of different types (eg applications libraries)
Detailed version information and dependencies to other components simplify program management
Adapter Modules and Development
Summary
Adapter Framework Overview
Adapter Strategy
Agenda
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 64
Summary
Adapter Framework runs on J2EE Stack of SAP Web AS
Adapter Framework is platform for Adapter Engine and SAP PCK
Adapter Framework provides an extensible platform for developing and running adapters
Adapter Engine utilizes central configuration monitoring administration
Dual connectivity strategyAdapter Framework for comprehensive integration of adaptersInteroperability via open standards to interop with EAI providers
SAP NetWeaver Certification for adapters based on Adapter Framework available
Adapter mappings metadata stored in Integration Repository
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 52
Adapter Development Documentation
SAP Help Portal (httphelpsapcom)SAP XI Runtime Connectivity Partner Connectivity Kit Adapter DevelopmentFeedback Mail to xidocumentationsapcom
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 53
Requirements for Adapters (1)
Num AF Interface Category Description
1 JCA 10 conformance Mandatory Adapter must fulfill JCA 10 requirements (e g deployment) plus optional JCA 15 parts which are used by PI XI
2 AF Message Exchange Mandatory Adapter must be able to receive messages from AF and forward them to connected system and vice versa
3 AF Adapter Specific Modules
Optional SAP XI message and protocol conversion may be done entirely by the adapter or as adapter specific module and being called in the AF module chain context
4 Configuration Services Mandatory Unique configuration approach to manage adapters
5 Administrational Services
Optional Administration and Monitoring
6 Utility Service Mandatory Access to basic J2EE resources e g transactions and multithreading must be under control of J2EE server
7 Logging API Optional Adapters may use their own logging
8 Message Metadata Exchange
Optional Provide structure definition of message payloadIf not supported the definition of message types can be done in the Integration Repository
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 54
Requirements for Adapters (2)
Cluster-enabledConsider side-effects of clustering e g bdquoExactlyOnceInOrderldquo Avoid passing maneuvers
SpecializationBuild connection to exactly one type of business system or industrystandard protocol
DirectnessBuild connection to business system or industry standard protocoldirectly without any intermediate software components
SmoothnessLight-weighted low footprint adapter unnecessary system changes(many new or changed system DLL) should be avoided
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 55
Sample Adapter Source Code
Beside the API documentation a working sample adapter is shipped
The source code is available after installation
Analyzing the code helps understanding the Adapter Framework
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 56
Adapter Metadata
Adapter Metadata (AMD)XML file defines all configuration parameterseach adapter
AMD can be uploaded intoIntegration Iepositoryand SAP PCK
Configurationparameters are renderedinto the graphicalconfiguaration frontend
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 57
Adapter Metadata Fragment I
ltAdapterTypeMetaData version=09gt
ltTypegtNAESBltTypegt
ltInboundgt
ltTransportProtocolgt
ltChannelAttributesgt
ltAttributeGroupgt
ltNamegtCRYPTConfigurationltNamegt
ltGuiLabelsgtltLabel language=ENgtCryptographic ConfigurationltLabelgtltGuiLabelsgt
ltAttributeReferencegtltReferenceNamegtCRYPTUseSigningltReferenceNamegt
ltInboundgt
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 58
Adapter Metadata Fragment II
ltAttributegt
ltNamegtCRYPTUseSigningltNamegt
ltDataTypegtxsdbooleanltDataTypegt
ltGuiLabelsgt
ltLabel language=ENgtUse SigningltLabelgt
ltLabel language=DEgtVerwendung von SignierungltLabelgt
ltGuiLabelsgt
ltAttributegt
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 59
Adapter Configuration
Configuration attribute of type boolean is rendered to a check-box
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 60
Adapter Metadata Upload (PCK)
Integration Repositorydoes not exist in case ofSAP PCK installations
The upload mechanismfor Adaper Meta Datafor SAP PCK installationsrequires additonalparameters
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 61
AF CPA Cache
The Adapter configuration is deployed from the configuration time(SAP PCK or Integration Directory) to the J2EE service CPACache(Collaboration Profile Agreement)
The Adapter configuration can be accessed at runtime from withinadapter modules or JCA resource adapters via the CPACache API
The two main use cases are implemented inLookupManager to retrieve adapter configuation andNormalizationManager to retrieve Party information
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 62
Packaging Adapter Components
SAP recommends to use SAP Software Deployment Manager (SDM) for deployment
Software Delivery Archives (SDA) can contain software components of different types (eg applications libraries)
Detailed version information and dependencies to other components simplify program management
Adapter Modules and Development
Summary
Adapter Framework Overview
Adapter Strategy
Agenda
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 64
Summary
Adapter Framework runs on J2EE Stack of SAP Web AS
Adapter Framework is platform for Adapter Engine and SAP PCK
Adapter Framework provides an extensible platform for developing and running adapters
Adapter Engine utilizes central configuration monitoring administration
Dual connectivity strategyAdapter Framework for comprehensive integration of adaptersInteroperability via open standards to interop with EAI providers
SAP NetWeaver Certification for adapters based on Adapter Framework available
Adapter mappings metadata stored in Integration Repository
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 53
Requirements for Adapters (1)
Num AF Interface Category Description
1 JCA 10 conformance Mandatory Adapter must fulfill JCA 10 requirements (e g deployment) plus optional JCA 15 parts which are used by PI XI
2 AF Message Exchange Mandatory Adapter must be able to receive messages from AF and forward them to connected system and vice versa
3 AF Adapter Specific Modules
Optional SAP XI message and protocol conversion may be done entirely by the adapter or as adapter specific module and being called in the AF module chain context
4 Configuration Services Mandatory Unique configuration approach to manage adapters
5 Administrational Services
Optional Administration and Monitoring
6 Utility Service Mandatory Access to basic J2EE resources e g transactions and multithreading must be under control of J2EE server
7 Logging API Optional Adapters may use their own logging
8 Message Metadata Exchange
Optional Provide structure definition of message payloadIf not supported the definition of message types can be done in the Integration Repository
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 54
Requirements for Adapters (2)
Cluster-enabledConsider side-effects of clustering e g bdquoExactlyOnceInOrderldquo Avoid passing maneuvers
SpecializationBuild connection to exactly one type of business system or industrystandard protocol
DirectnessBuild connection to business system or industry standard protocoldirectly without any intermediate software components
SmoothnessLight-weighted low footprint adapter unnecessary system changes(many new or changed system DLL) should be avoided
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 55
Sample Adapter Source Code
Beside the API documentation a working sample adapter is shipped
The source code is available after installation
Analyzing the code helps understanding the Adapter Framework
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 56
Adapter Metadata
Adapter Metadata (AMD)XML file defines all configuration parameterseach adapter
AMD can be uploaded intoIntegration Iepositoryand SAP PCK
Configurationparameters are renderedinto the graphicalconfiguaration frontend
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 57
Adapter Metadata Fragment I
ltAdapterTypeMetaData version=09gt
ltTypegtNAESBltTypegt
ltInboundgt
ltTransportProtocolgt
ltChannelAttributesgt
ltAttributeGroupgt
ltNamegtCRYPTConfigurationltNamegt
ltGuiLabelsgtltLabel language=ENgtCryptographic ConfigurationltLabelgtltGuiLabelsgt
ltAttributeReferencegtltReferenceNamegtCRYPTUseSigningltReferenceNamegt
ltInboundgt
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 58
Adapter Metadata Fragment II
ltAttributegt
ltNamegtCRYPTUseSigningltNamegt
ltDataTypegtxsdbooleanltDataTypegt
ltGuiLabelsgt
ltLabel language=ENgtUse SigningltLabelgt
ltLabel language=DEgtVerwendung von SignierungltLabelgt
ltGuiLabelsgt
ltAttributegt
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 59
Adapter Configuration
Configuration attribute of type boolean is rendered to a check-box
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 60
Adapter Metadata Upload (PCK)
Integration Repositorydoes not exist in case ofSAP PCK installations
The upload mechanismfor Adaper Meta Datafor SAP PCK installationsrequires additonalparameters
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 61
AF CPA Cache
The Adapter configuration is deployed from the configuration time(SAP PCK or Integration Directory) to the J2EE service CPACache(Collaboration Profile Agreement)
The Adapter configuration can be accessed at runtime from withinadapter modules or JCA resource adapters via the CPACache API
The two main use cases are implemented inLookupManager to retrieve adapter configuation andNormalizationManager to retrieve Party information
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 62
Packaging Adapter Components
SAP recommends to use SAP Software Deployment Manager (SDM) for deployment
Software Delivery Archives (SDA) can contain software components of different types (eg applications libraries)
Detailed version information and dependencies to other components simplify program management
Adapter Modules and Development
Summary
Adapter Framework Overview
Adapter Strategy
Agenda
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 64
Summary
Adapter Framework runs on J2EE Stack of SAP Web AS
Adapter Framework is platform for Adapter Engine and SAP PCK
Adapter Framework provides an extensible platform for developing and running adapters
Adapter Engine utilizes central configuration monitoring administration
Dual connectivity strategyAdapter Framework for comprehensive integration of adaptersInteroperability via open standards to interop with EAI providers
SAP NetWeaver Certification for adapters based on Adapter Framework available
Adapter mappings metadata stored in Integration Repository
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 54
Requirements for Adapters (2)
Cluster-enabledConsider side-effects of clustering e g bdquoExactlyOnceInOrderldquo Avoid passing maneuvers
SpecializationBuild connection to exactly one type of business system or industrystandard protocol
DirectnessBuild connection to business system or industry standard protocoldirectly without any intermediate software components
SmoothnessLight-weighted low footprint adapter unnecessary system changes(many new or changed system DLL) should be avoided
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 55
Sample Adapter Source Code
Beside the API documentation a working sample adapter is shipped
The source code is available after installation
Analyzing the code helps understanding the Adapter Framework
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 56
Adapter Metadata
Adapter Metadata (AMD)XML file defines all configuration parameterseach adapter
AMD can be uploaded intoIntegration Iepositoryand SAP PCK
Configurationparameters are renderedinto the graphicalconfiguaration frontend
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 57
Adapter Metadata Fragment I
ltAdapterTypeMetaData version=09gt
ltTypegtNAESBltTypegt
ltInboundgt
ltTransportProtocolgt
ltChannelAttributesgt
ltAttributeGroupgt
ltNamegtCRYPTConfigurationltNamegt
ltGuiLabelsgtltLabel language=ENgtCryptographic ConfigurationltLabelgtltGuiLabelsgt
ltAttributeReferencegtltReferenceNamegtCRYPTUseSigningltReferenceNamegt
ltInboundgt
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 58
Adapter Metadata Fragment II
ltAttributegt
ltNamegtCRYPTUseSigningltNamegt
ltDataTypegtxsdbooleanltDataTypegt
ltGuiLabelsgt
ltLabel language=ENgtUse SigningltLabelgt
ltLabel language=DEgtVerwendung von SignierungltLabelgt
ltGuiLabelsgt
ltAttributegt
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 59
Adapter Configuration
Configuration attribute of type boolean is rendered to a check-box
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 60
Adapter Metadata Upload (PCK)
Integration Repositorydoes not exist in case ofSAP PCK installations
The upload mechanismfor Adaper Meta Datafor SAP PCK installationsrequires additonalparameters
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 61
AF CPA Cache
The Adapter configuration is deployed from the configuration time(SAP PCK or Integration Directory) to the J2EE service CPACache(Collaboration Profile Agreement)
The Adapter configuration can be accessed at runtime from withinadapter modules or JCA resource adapters via the CPACache API
The two main use cases are implemented inLookupManager to retrieve adapter configuation andNormalizationManager to retrieve Party information
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 62
Packaging Adapter Components
SAP recommends to use SAP Software Deployment Manager (SDM) for deployment
Software Delivery Archives (SDA) can contain software components of different types (eg applications libraries)
Detailed version information and dependencies to other components simplify program management
Adapter Modules and Development
Summary
Adapter Framework Overview
Adapter Strategy
Agenda
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 64
Summary
Adapter Framework runs on J2EE Stack of SAP Web AS
Adapter Framework is platform for Adapter Engine and SAP PCK
Adapter Framework provides an extensible platform for developing and running adapters
Adapter Engine utilizes central configuration monitoring administration
Dual connectivity strategyAdapter Framework for comprehensive integration of adaptersInteroperability via open standards to interop with EAI providers
SAP NetWeaver Certification for adapters based on Adapter Framework available
Adapter mappings metadata stored in Integration Repository
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 55
Sample Adapter Source Code
Beside the API documentation a working sample adapter is shipped
The source code is available after installation
Analyzing the code helps understanding the Adapter Framework
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 56
Adapter Metadata
Adapter Metadata (AMD)XML file defines all configuration parameterseach adapter
AMD can be uploaded intoIntegration Iepositoryand SAP PCK
Configurationparameters are renderedinto the graphicalconfiguaration frontend
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 57
Adapter Metadata Fragment I
ltAdapterTypeMetaData version=09gt
ltTypegtNAESBltTypegt
ltInboundgt
ltTransportProtocolgt
ltChannelAttributesgt
ltAttributeGroupgt
ltNamegtCRYPTConfigurationltNamegt
ltGuiLabelsgtltLabel language=ENgtCryptographic ConfigurationltLabelgtltGuiLabelsgt
ltAttributeReferencegtltReferenceNamegtCRYPTUseSigningltReferenceNamegt
ltInboundgt
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 58
Adapter Metadata Fragment II
ltAttributegt
ltNamegtCRYPTUseSigningltNamegt
ltDataTypegtxsdbooleanltDataTypegt
ltGuiLabelsgt
ltLabel language=ENgtUse SigningltLabelgt
ltLabel language=DEgtVerwendung von SignierungltLabelgt
ltGuiLabelsgt
ltAttributegt
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 59
Adapter Configuration
Configuration attribute of type boolean is rendered to a check-box
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 60
Adapter Metadata Upload (PCK)
Integration Repositorydoes not exist in case ofSAP PCK installations
The upload mechanismfor Adaper Meta Datafor SAP PCK installationsrequires additonalparameters
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 61
AF CPA Cache
The Adapter configuration is deployed from the configuration time(SAP PCK or Integration Directory) to the J2EE service CPACache(Collaboration Profile Agreement)
The Adapter configuration can be accessed at runtime from withinadapter modules or JCA resource adapters via the CPACache API
The two main use cases are implemented inLookupManager to retrieve adapter configuation andNormalizationManager to retrieve Party information
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 62
Packaging Adapter Components
SAP recommends to use SAP Software Deployment Manager (SDM) for deployment
Software Delivery Archives (SDA) can contain software components of different types (eg applications libraries)
Detailed version information and dependencies to other components simplify program management
Adapter Modules and Development
Summary
Adapter Framework Overview
Adapter Strategy
Agenda
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 64
Summary
Adapter Framework runs on J2EE Stack of SAP Web AS
Adapter Framework is platform for Adapter Engine and SAP PCK
Adapter Framework provides an extensible platform for developing and running adapters
Adapter Engine utilizes central configuration monitoring administration
Dual connectivity strategyAdapter Framework for comprehensive integration of adaptersInteroperability via open standards to interop with EAI providers
SAP NetWeaver Certification for adapters based on Adapter Framework available
Adapter mappings metadata stored in Integration Repository
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 56
Adapter Metadata
Adapter Metadata (AMD)XML file defines all configuration parameterseach adapter
AMD can be uploaded intoIntegration Iepositoryand SAP PCK
Configurationparameters are renderedinto the graphicalconfiguaration frontend
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 57
Adapter Metadata Fragment I
ltAdapterTypeMetaData version=09gt
ltTypegtNAESBltTypegt
ltInboundgt
ltTransportProtocolgt
ltChannelAttributesgt
ltAttributeGroupgt
ltNamegtCRYPTConfigurationltNamegt
ltGuiLabelsgtltLabel language=ENgtCryptographic ConfigurationltLabelgtltGuiLabelsgt
ltAttributeReferencegtltReferenceNamegtCRYPTUseSigningltReferenceNamegt
ltInboundgt
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 58
Adapter Metadata Fragment II
ltAttributegt
ltNamegtCRYPTUseSigningltNamegt
ltDataTypegtxsdbooleanltDataTypegt
ltGuiLabelsgt
ltLabel language=ENgtUse SigningltLabelgt
ltLabel language=DEgtVerwendung von SignierungltLabelgt
ltGuiLabelsgt
ltAttributegt
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 59
Adapter Configuration
Configuration attribute of type boolean is rendered to a check-box
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 60
Adapter Metadata Upload (PCK)
Integration Repositorydoes not exist in case ofSAP PCK installations
The upload mechanismfor Adaper Meta Datafor SAP PCK installationsrequires additonalparameters
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 61
AF CPA Cache
The Adapter configuration is deployed from the configuration time(SAP PCK or Integration Directory) to the J2EE service CPACache(Collaboration Profile Agreement)
The Adapter configuration can be accessed at runtime from withinadapter modules or JCA resource adapters via the CPACache API
The two main use cases are implemented inLookupManager to retrieve adapter configuation andNormalizationManager to retrieve Party information
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 62
Packaging Adapter Components
SAP recommends to use SAP Software Deployment Manager (SDM) for deployment
Software Delivery Archives (SDA) can contain software components of different types (eg applications libraries)
Detailed version information and dependencies to other components simplify program management
Adapter Modules and Development
Summary
Adapter Framework Overview
Adapter Strategy
Agenda
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 64
Summary
Adapter Framework runs on J2EE Stack of SAP Web AS
Adapter Framework is platform for Adapter Engine and SAP PCK
Adapter Framework provides an extensible platform for developing and running adapters
Adapter Engine utilizes central configuration monitoring administration
Dual connectivity strategyAdapter Framework for comprehensive integration of adaptersInteroperability via open standards to interop with EAI providers
SAP NetWeaver Certification for adapters based on Adapter Framework available
Adapter mappings metadata stored in Integration Repository
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 57
Adapter Metadata Fragment I
ltAdapterTypeMetaData version=09gt
ltTypegtNAESBltTypegt
ltInboundgt
ltTransportProtocolgt
ltChannelAttributesgt
ltAttributeGroupgt
ltNamegtCRYPTConfigurationltNamegt
ltGuiLabelsgtltLabel language=ENgtCryptographic ConfigurationltLabelgtltGuiLabelsgt
ltAttributeReferencegtltReferenceNamegtCRYPTUseSigningltReferenceNamegt
ltInboundgt
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 58
Adapter Metadata Fragment II
ltAttributegt
ltNamegtCRYPTUseSigningltNamegt
ltDataTypegtxsdbooleanltDataTypegt
ltGuiLabelsgt
ltLabel language=ENgtUse SigningltLabelgt
ltLabel language=DEgtVerwendung von SignierungltLabelgt
ltGuiLabelsgt
ltAttributegt
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 59
Adapter Configuration
Configuration attribute of type boolean is rendered to a check-box
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 60
Adapter Metadata Upload (PCK)
Integration Repositorydoes not exist in case ofSAP PCK installations
The upload mechanismfor Adaper Meta Datafor SAP PCK installationsrequires additonalparameters
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 61
AF CPA Cache
The Adapter configuration is deployed from the configuration time(SAP PCK or Integration Directory) to the J2EE service CPACache(Collaboration Profile Agreement)
The Adapter configuration can be accessed at runtime from withinadapter modules or JCA resource adapters via the CPACache API
The two main use cases are implemented inLookupManager to retrieve adapter configuation andNormalizationManager to retrieve Party information
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 62
Packaging Adapter Components
SAP recommends to use SAP Software Deployment Manager (SDM) for deployment
Software Delivery Archives (SDA) can contain software components of different types (eg applications libraries)
Detailed version information and dependencies to other components simplify program management
Adapter Modules and Development
Summary
Adapter Framework Overview
Adapter Strategy
Agenda
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 64
Summary
Adapter Framework runs on J2EE Stack of SAP Web AS
Adapter Framework is platform for Adapter Engine and SAP PCK
Adapter Framework provides an extensible platform for developing and running adapters
Adapter Engine utilizes central configuration monitoring administration
Dual connectivity strategyAdapter Framework for comprehensive integration of adaptersInteroperability via open standards to interop with EAI providers
SAP NetWeaver Certification for adapters based on Adapter Framework available
Adapter mappings metadata stored in Integration Repository
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 58
Adapter Metadata Fragment II
ltAttributegt
ltNamegtCRYPTUseSigningltNamegt
ltDataTypegtxsdbooleanltDataTypegt
ltGuiLabelsgt
ltLabel language=ENgtUse SigningltLabelgt
ltLabel language=DEgtVerwendung von SignierungltLabelgt
ltGuiLabelsgt
ltAttributegt
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 59
Adapter Configuration
Configuration attribute of type boolean is rendered to a check-box
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 60
Adapter Metadata Upload (PCK)
Integration Repositorydoes not exist in case ofSAP PCK installations
The upload mechanismfor Adaper Meta Datafor SAP PCK installationsrequires additonalparameters
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 61
AF CPA Cache
The Adapter configuration is deployed from the configuration time(SAP PCK or Integration Directory) to the J2EE service CPACache(Collaboration Profile Agreement)
The Adapter configuration can be accessed at runtime from withinadapter modules or JCA resource adapters via the CPACache API
The two main use cases are implemented inLookupManager to retrieve adapter configuation andNormalizationManager to retrieve Party information
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 62
Packaging Adapter Components
SAP recommends to use SAP Software Deployment Manager (SDM) for deployment
Software Delivery Archives (SDA) can contain software components of different types (eg applications libraries)
Detailed version information and dependencies to other components simplify program management
Adapter Modules and Development
Summary
Adapter Framework Overview
Adapter Strategy
Agenda
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 64
Summary
Adapter Framework runs on J2EE Stack of SAP Web AS
Adapter Framework is platform for Adapter Engine and SAP PCK
Adapter Framework provides an extensible platform for developing and running adapters
Adapter Engine utilizes central configuration monitoring administration
Dual connectivity strategyAdapter Framework for comprehensive integration of adaptersInteroperability via open standards to interop with EAI providers
SAP NetWeaver Certification for adapters based on Adapter Framework available
Adapter mappings metadata stored in Integration Repository
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 59
Adapter Configuration
Configuration attribute of type boolean is rendered to a check-box
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 60
Adapter Metadata Upload (PCK)
Integration Repositorydoes not exist in case ofSAP PCK installations
The upload mechanismfor Adaper Meta Datafor SAP PCK installationsrequires additonalparameters
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 61
AF CPA Cache
The Adapter configuration is deployed from the configuration time(SAP PCK or Integration Directory) to the J2EE service CPACache(Collaboration Profile Agreement)
The Adapter configuration can be accessed at runtime from withinadapter modules or JCA resource adapters via the CPACache API
The two main use cases are implemented inLookupManager to retrieve adapter configuation andNormalizationManager to retrieve Party information
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 62
Packaging Adapter Components
SAP recommends to use SAP Software Deployment Manager (SDM) for deployment
Software Delivery Archives (SDA) can contain software components of different types (eg applications libraries)
Detailed version information and dependencies to other components simplify program management
Adapter Modules and Development
Summary
Adapter Framework Overview
Adapter Strategy
Agenda
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 64
Summary
Adapter Framework runs on J2EE Stack of SAP Web AS
Adapter Framework is platform for Adapter Engine and SAP PCK
Adapter Framework provides an extensible platform for developing and running adapters
Adapter Engine utilizes central configuration monitoring administration
Dual connectivity strategyAdapter Framework for comprehensive integration of adaptersInteroperability via open standards to interop with EAI providers
SAP NetWeaver Certification for adapters based on Adapter Framework available
Adapter mappings metadata stored in Integration Repository
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 60
Adapter Metadata Upload (PCK)
Integration Repositorydoes not exist in case ofSAP PCK installations
The upload mechanismfor Adaper Meta Datafor SAP PCK installationsrequires additonalparameters
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 61
AF CPA Cache
The Adapter configuration is deployed from the configuration time(SAP PCK or Integration Directory) to the J2EE service CPACache(Collaboration Profile Agreement)
The Adapter configuration can be accessed at runtime from withinadapter modules or JCA resource adapters via the CPACache API
The two main use cases are implemented inLookupManager to retrieve adapter configuation andNormalizationManager to retrieve Party information
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 62
Packaging Adapter Components
SAP recommends to use SAP Software Deployment Manager (SDM) for deployment
Software Delivery Archives (SDA) can contain software components of different types (eg applications libraries)
Detailed version information and dependencies to other components simplify program management
Adapter Modules and Development
Summary
Adapter Framework Overview
Adapter Strategy
Agenda
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 64
Summary
Adapter Framework runs on J2EE Stack of SAP Web AS
Adapter Framework is platform for Adapter Engine and SAP PCK
Adapter Framework provides an extensible platform for developing and running adapters
Adapter Engine utilizes central configuration monitoring administration
Dual connectivity strategyAdapter Framework for comprehensive integration of adaptersInteroperability via open standards to interop with EAI providers
SAP NetWeaver Certification for adapters based on Adapter Framework available
Adapter mappings metadata stored in Integration Repository
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 61
AF CPA Cache
The Adapter configuration is deployed from the configuration time(SAP PCK or Integration Directory) to the J2EE service CPACache(Collaboration Profile Agreement)
The Adapter configuration can be accessed at runtime from withinadapter modules or JCA resource adapters via the CPACache API
The two main use cases are implemented inLookupManager to retrieve adapter configuation andNormalizationManager to retrieve Party information
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 62
Packaging Adapter Components
SAP recommends to use SAP Software Deployment Manager (SDM) for deployment
Software Delivery Archives (SDA) can contain software components of different types (eg applications libraries)
Detailed version information and dependencies to other components simplify program management
Adapter Modules and Development
Summary
Adapter Framework Overview
Adapter Strategy
Agenda
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 64
Summary
Adapter Framework runs on J2EE Stack of SAP Web AS
Adapter Framework is platform for Adapter Engine and SAP PCK
Adapter Framework provides an extensible platform for developing and running adapters
Adapter Engine utilizes central configuration monitoring administration
Dual connectivity strategyAdapter Framework for comprehensive integration of adaptersInteroperability via open standards to interop with EAI providers
SAP NetWeaver Certification for adapters based on Adapter Framework available
Adapter mappings metadata stored in Integration Repository
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 62
Packaging Adapter Components
SAP recommends to use SAP Software Deployment Manager (SDM) for deployment
Software Delivery Archives (SDA) can contain software components of different types (eg applications libraries)
Detailed version information and dependencies to other components simplify program management
Adapter Modules and Development
Summary
Adapter Framework Overview
Adapter Strategy
Agenda
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 64
Summary
Adapter Framework runs on J2EE Stack of SAP Web AS
Adapter Framework is platform for Adapter Engine and SAP PCK
Adapter Framework provides an extensible platform for developing and running adapters
Adapter Engine utilizes central configuration monitoring administration
Dual connectivity strategyAdapter Framework for comprehensive integration of adaptersInteroperability via open standards to interop with EAI providers
SAP NetWeaver Certification for adapters based on Adapter Framework available
Adapter mappings metadata stored in Integration Repository
Adapter Modules and Development
Summary
Adapter Framework Overview
Adapter Strategy
Agenda
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 64
Summary
Adapter Framework runs on J2EE Stack of SAP Web AS
Adapter Framework is platform for Adapter Engine and SAP PCK
Adapter Framework provides an extensible platform for developing and running adapters
Adapter Engine utilizes central configuration monitoring administration
Dual connectivity strategyAdapter Framework for comprehensive integration of adaptersInteroperability via open standards to interop with EAI providers
SAP NetWeaver Certification for adapters based on Adapter Framework available
Adapter mappings metadata stored in Integration Repository
copy SAP AG 2007 End-to-End Process Integration ndashAdapter Framework 64
Summary
Adapter Framework runs on J2EE Stack of SAP Web AS
Adapter Framework is platform for Adapter Engine and SAP PCK
Adapter Framework provides an extensible platform for developing and running adapters
Adapter Engine utilizes central configuration monitoring administration
Dual connectivity strategyAdapter Framework for comprehensive integration of adaptersInteroperability via open standards to interop with EAI providers
SAP NetWeaver Certification for adapters based on Adapter Framework available
Adapter mappings metadata stored in Integration Repository