Transcription

End-to-End ProcessIntegrationAdapter FrameworkSAP NetWeaverProduct ManagementSAP AG

AgendaAdapter Framework OverviewAdapter StrategyAdapter Modules and DevelopmentSummary

Process Integration – ArchitectureIntegration Repository / Integration Directory / System Landscape DirectoryIntegration ServerBusiness Process EngineIntegration Engine SAP AG 2007, End-to-End Process Integration –Adapter Framework / 3File/DB/JMSMarketplace3rd Party Sys.File/DB/JMSMarketplace3rd Party Sys.and MonitoringAdapter FWMessagingQueuingSecurity HandlingResourceAdapterSAP &Non-SAPSystemAdapter FWMessagingQueuingSecurity HandlingResourceAdapterFileDBJMSSOAPAdapter FrameworkMessagingQueuingSecurity HandlingResourceAdapterAdapterOptional non-centralAdapter EngineCentralAdapter r ConnectivityKit PCK ConfigurationFile/DB/JMSMarketplace3rd Party Sys.

Adapter Framework based on SAP J2EE EngineAdapter Framework provides common functionality for AdapterEngine and SAP Partner Connectivity KitAdapter Framework is based on SAP J2EE Engine as part of SAPWeb ASAdapter Framework inherits properties and features such asscalability, clustering, high availability, thread management, etc.Adapter Framework provides its own queuing and loggingservicesTemporary stand-alone operation without connection to anIntegration Server is possible, while still providing e. g. guaranteedexactly once messaging to and from connected application system SAP AG 2007, End-to-End Process Integration –Adapter Framework / 4

JCA enabled Adapter FrameworkAdapter Framework supports J2EE Connector Architecture (JCA)JCA is standard architecture for connecting the J2EE platform toEnterprise Information Systems (EIS), e. g. ERP, DBMS, etc.A Resource Adapter plugs into an application server, providingconnectivity between the EIS and a Java applicationJCA enabled Adapter Framework provides defined interfaces towhich both our adapters and 3rd party adapters can conformJCA is a widely accepted standard that 3rd party adapter providersare familiar with SAP AG 2007, End-to-End Process Integration –Adapter Framework / 5

Central configuration, administration, monitoringAdditionally Adapter Framework provides comprehensiveintegration for central configuration, administration, monitoringof deployed adaptersOne single point of access, only one common UI, enhancedtransparancyAllows to move/copy configuration from one Adapter Frameworkto another (transportable configuration):To transport configuration from test landscape to productivelandscapeFor high availability/failoverAvoid redundant maintenance, ensure consistencyEnd-to-end monitoring of the message flow over all components /applications SAP AG 2007, End-to-End Process Integration –Adapter Framework / 6

Adapters vs. ProxiesProxiesOutside-in development approachInterfaces designed centrally in Integration RepositoryConnect new SAP applicationsNative connectivity to Application system (adapter-less)AdaptersInside-out development approachInterface semantics externally pre-definedConnect existing (legacy) systemsSpecific wire protocol SAP AG 2007, End-to-End Process Integration –Adapter Framework / 7

Process Integration – ArchitectureIntegration Repository / Integration Directory / System Landscape DirectoryIntegration ServerBusiness Process EngineIntegration Engine SAP AG 2007, End-to-End Process Integration –Adapter Framework / 8File/DB/JMSMarketplace3rd Party Sys.File/DB/JMSMarketplace3rd Party Sys.and MonitoringAdapter FWMessagingQueuingSecurity HandlingResourceAdapterSAP &Non-SAPSystemAdapter FWMessagingQueuingSecurity HandlingResourceAdapterFileDBJMSSOAPAdapter FrameworkMessagingQueuingSecurity HandlingResourceAdapterAdapterOptional non-centralAdapter EngineCentralAdapter r ConnectivityKit PCK ConfigurationFile/DB/JMSMarketplace3rd Party Sys.

Full integration of Adapter EngineAdapter Engine is based on Adapter FrameworkAdapter Engine fully integratedCentral configuration of connections to application systems(through appropriate adapters) in Integration DirectoryReuse of Integration Directory’s existing versioning and transportcapabilitiesCentral administration and monitoring over adapters, IntegrationServer, Integration Engine through Runtime WorkbenchThe Adapter Engine can be deployed centrally as part ofIntegration Server, or as optional local Adapter Engine on itsown SAP J2EE Server; reasons for use of local Adapter Engine:Protocol of Sender- / Receiver system (e.g. ftp not allowed)Performance, High AvailabilityOrganizational Aspects, IT requirements SAP AG 2007, End-to-End Process Integration –Adapter Framework / 9

PI Adapters developed by SAPTechnical AdaptersFile/FTP (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 AdaptersRFCIDocIndustry Standard AdaptersRNIF 2.0 (RosettaNet)RNIF 1.1 (RosettaNet)CIDX (RNIF 1.1) SAP AG 2007, End-to-End Process Integration –Adapter Framework / 10

Industry Standard Adapters as part of Business PackagesBusiness Package for RosettaNetOrder to Invoice Scenario:PIP3A4 Request Purchase OrderPIP3A7 Notify of Purchase Order UpdatePIP3A8 Request Purchase Order ChangePIP3A9 Request Purchase Order CancellationPIP3B2 Notify of Advance ShipmentPIP3C3 Notify of InvoicePIP3A6 Distribute Order StatusPIP3C6 Notify of Remittance AdviceBusiness Package for CIDXOrder to Invoice Scenario:Order CreateOrder ResponseOrder ChangeShip NoticeInvoiceBusiness Packages include scenario descriptions, business processes,message interfaces, message types, mappings, adapter etc. SAP AG 2007, End-to-End Process Integration –Adapter Framework / 11

Partner Eco SystemSAP relies on a system of partners to provide connectivitysolutions for other applications and certain industry standardsConnectivity Reseller Agreements withSeeburger AGiWay SoftwareInformatica3rd-Party solutions are sold and delivered through SAPTechnical support for partner solutions via theSAP Support Portal, 24x7 SAP AG 2007, End-to-End Process Integration –Adapter Framework / 12

PI Adapters by Seeburger (1)Technical EDI AdaptersAS2 (EDIINT/HTTP(S))Protocol: AS2OFTPProtocol: OFTP/ISDN, OFTP/TCPIPVAN AccessProtocol: P7 / X.400, VAN FTPBusiness EDI AdaptersGeneric EDIProtocol: OFTP/ISDN or P7 / X.400, VAN FTPEDI Converter: ANSI X.12, EDIFACTMapping Templates: Purchase order, Order confirmation,Dispatch advice, InvoicePayment (Financial Service Providers)Protocol: OFTP/ISDN, P7 / X.400, VAN FTPEDI Converter: EDIFACT, SWIFTMapping Templates: Payment orders, Debit advice,Credit advice, Account Statement SAP AG 2007, End-to-End Process Integration –Adapter Framework / 13

PI Adapters by Seeburger (2)Industry Specific EDI AdaptersAerospace and DefenseAutomotiveChemicalsConsumer ation ProtocolsOFTP/ISDN, P7 / X.400, VAN FTPEDI Converter (EDI - XML)AECMA/SPEC 2000, ANSI X.12, CHEM eStandards, EDIFACT, GALIA,ODETTE, TRADACOM, VDAMapping Templates within Integration RepositoryDelivery forecast, Dispatch advise, Invoice, Purchase order, OrderconfirmationMessage Library for Integration RepositoryHuge message catalog with EDI XML schema definitions SAP AG 2007, End-to-End Process Integration –Adapter Framework / 14

PI Adapters by iWay SoftwareApplication AdaptersAribaBaanBroadvisionClarifyJD Edwards One World XEJD Edwards Worldi2LawsonManugisticsMicrosoft CRMOracle ApplicationsPeoplesoftQAD MFG ProSiebelVantiveIndustry Standard AdaptersSwiftUCCnet SAP AG 2007, End-to-End Process Integration –Adapter Framework / 15Transora

PI Adapters by iWay SoftwareTechnical AdaptersAS1 (EDIINT/SMTP)AS2 (EDIINT/HTTP(S))BEA WLICOM /DCOMCorbaLotus NotesTibco RendezvousMainframe/transaction AdaptersCICSTMS/IMSTelnet (3270)Telnet (5250)TuxedoOptionally further adapters can be added from a list of 160 iWayadapters, e. g. HL7 (already certified), DB2, AS3, ebXML SAP AG 2007, End-to-End Process Integration –Adapter Framework / 16

SAP Conversion Agent by InformaticaSeamlessly integrated into Process IntegrationBi-directional conversion of unstructured and semi structured data from / to XMLTransformation on message payloadProtocol support via SAP’s technical adapter (PI / XI adapter framework)Transformations integrated via PI / XI AF moduleConversionAgent StudioCA AFModuleConversion Agent J2EELibConversion Agent Engine SAP AG 2007, End-to-End Process Integration –Adapter Framework / 17Adapter.ConversionAgent ServicesXML2ExcelPI / XI Adapter FrameworkAdapterText2XMLPDF2XMLSAP J2EE

Supported Data Formats by Informatica (partial list) using SAP technical adapter and Conversion Agent:UNSTRUCTUREDMicrosoft WordMicrosoft ExcelPowerPointPDFStar OfficeWord PerfectASCII reportsHTMLEBCDICUndocumented binariesFlat filesRPGANSIPRINT STREAMSAFPPost ScriptDJDE SAP AG 2007, End-to-End Process Integration –Adapter Framework / LFIXCargo IMPMVRSWIFTOTHER STANDARDSLegalXMLIFXcXMLebXMLHL7 V3.0ACORD (AL3, XML)

Conversion Agent vs. 3rd Party AdaptersConversion Agent3rd Party AdaptersBi-directional conversion ofunstructured and semistructured formats from/to XMLBi-directional conversion of onededicated data format (e.g.SWIFT, ANSI-X12, ) from/to XMLLinked through PI / XI adapterframework module based onSAP’s technical adapter – notransport protocol, manipulatespayload informationRuns within PI / XI adapterframework - support payloadtransformation and transportprotocolSAP NetWeaver-wide use (viaJ2EE library)Per adapter dedicated use withinone SAP NetWeaver component SAP AG 2007, End-to-End Process Integration –Adapter Framework / 19

More Info about Connectivity CapabilitiesConnectivity and Interoperability** http://service.sap.com/xi SAP AG 2007, End-to-End Process Integration –Adapter Framework / 20xi in detailconnectivity

Adapter Download from SAP Service MarketplaceSAP Service Marketplace: http://service.sap.com/swdcDownloadInstallations and UpgradesEntry by Application GroupAdapters SAP AG 2007, End-to-End Process Integration –Adapter Framework / 21

Certification Programs for Process IntegrationPI Based Certification Programs** http://www.sdn.sap.comPartners and ISVsIntegration and Certification Exchange Infrastructure SAP AG 2007, End-to-End Process Integration –Adapter Framework / 22

Public info about certified PI adaptersCertified PI Adapters** tion.epxThird Party Defined Integration Scenarios: NW-XI-AF 3.0 SAP AG 2007, End-to-End Process Integration –Adapter Framework / 23

Adapter ConfigurationAdapter independentparametersAdapter specificparameters SAP AG 2007, End-to-End Process Integration –Adapter Framework / 24

Adapter Enginehttp:// IntegrationServerURL ISRuntimeSystem Landscape Directory Holds component descriptionincluding address dataConfig.cacheAdapterFrameworkMessageOK / ErrorAdapter Engine in SAP J2EEIntegrationIntegration RepositoryRepository HoldsAdapterHolds AdaptermetadatametadataAdapterSenderModule Processorhttp:// AdapterEngineURL ChannelQIntegration Builder / Directory:AdapterReceiver Messaging. Receiver determination Party- Service- ActionConfigurationcache. Channel Definition: Adapter Engine Adapter Type Message Protocol Transport Protocol Security Channel tionMasterEnd-to-End Monitoring(Sender / Receiver Agreement: Party/Service/Action - Channel SAP AG 2007, End-to-End Process Integration –Adapter Framework / 25Message flow over allcomponents / applicationsRuntime Workbench Uis for adminstration,monitoringEIS

Transport Level SecurityLevels of SecurityTransport ProtocolAuthenticationSupported byIDocRFC and SNCClient AuthenticationRFCRFC and SNCClient AuthenticationPlain HTTPHTTPsClient AuthenticationFile/FTPFile Transfer Protocolusing SSL/TLSClient AuthenticationSOAPHTTPsSMTPs (Receiver only)Client AuthenticationMailSMTPs, POP3, IMAP4CRAM-MD5MarketplaceHTTPsClient AuthenticationRNIF 2.0 – AdapterHTTPsClient AuthenticationRNIF 1.1 – AdapterHTTPsClient AuthenticationCDIX – AdapterHTTPsClient Authentication SAP AG 2007, End-to-End Process Integration –Adapter Framework / 26

Message Level SecuritySignatureNonRepudiationof originEncryptionTechnologyXI S/MIMEMail-Adapter33S/MIMERNIF 2.0 – Adapter3333S/MIMERNIF 1.1 – Adapter333PKCS#7CDIX – Adapter333PKCS#7Levels of SecuritySupported by SAP AG 2007, End-to-End Process Integration –Adapter Framework / 27NonRepudiation ofreceipt

Access control listRestrict access to the runtime environmentfor sender services of type Business Service or Business Systemfor interfaces of these sender servicesRestrict access to particular (service) usersCheck authorization at runtimeConfigure access control in the Integration DirectorySender service: Specify authorized users in the configuration of thecorresponding (sender) serviceInterface: Specify authorized users in the configuration of therelevant sender agreement which contains the interface in the objectkey SAP AG 2007, End-to-End Process Integration –Adapter Framework / 28

Dynamic Adapter ConfigurationEnable adapters to read / write dynamic message headersSender 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, interfacedetermination (routing), mappingReceiver 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 SAP AG 2007, End-to-End Process Integration –Adapter Framework / 29

Sender Adapter Configuration (1) SAP AG 2007, End-to-End Process Integration –Adapter Framework / 30

Sender Adapter Configuration (2)Add the filename et.al. to the message SAP AG 2007, End-to-End Process Integration –Adapter Framework / 31

Receiver DeterminationDeterminefilenamedependent receiver SAP AG 2007, End-to-End Process Integration –Adapter Framework / 32

Receiver AdapterStore the file withthe name set inthe messageattribute SAP AG 2007, End-to-End Process Integration –Adapter Framework / 33

Monitoring Adapter EngineAfter selecting a message, „Details“ View: SAP AG 2007, End-to-End Process Integration –Adapter Framework / 34

Monitoring Integration ServerAfter selecting a message, „Display“: SAP AG 2007, End-to-End Process Integration –Adapter Framework / 35

Remark: Future of SAP XI 2.0 Adapter EngineSAP XI 2.0 Adapter Engine is available in SAP NW 04 and SAPNW 2004s as „Plain J2SE Adapter Engine“Functional scope as in SAP XI 2.0:Adopted to the SAP XI 3.0 message protocolMinor maintenance issues, bug fixesRecommendation:Use where platform requirements or limitations (hardware,operating system, JVM support) demand itSAP XI 2.0 Adapter Engine works with SAP NW 04 and SAP NW2004s landscapes, too SAP AG 2007, End-to-End Process Integration –Adapter Framework / 36

Process Integration – ArchitectureIntegration Repository / Integration Directory / System Landscape DirectoryIntegration ServerBusiness Process EngineIntegration Engine SAP AG 2007, End-to-End Process Integration –Adapter Framework / 37File/DB/JMSMarketplace3rd Party Sys.File/DB/JMSMarketplace3rd Party Sys.and MonitoringAdapter FWMessagingQueuingSecurity HandlingResourceAdapterSAP &Non-SAPSystemAdapter FWMessagingQueuingSecurity HandlingResourceAdapterFileDBJMSSOAPAdapter FrameworkMessagingQueuingSecurity HandlingResourceAdapterAdapterOptional non-centralAdapter EngineCentralAdapter r ConnectivityKit PCK ConfigurationFile/DB/JMSMarketplace3rd Party Sys.

SAP Partner Connectivity Kit OverviewEnablement of smaller companies / subsidiaries to exchange XMLdocuments with their business partner’s / headquarter’s PI / XILarge Business Partner /HeadquarterSmaller Company / SubsidiarySAPApplicationSAP / 3rdParty Appl.SAPPCKInternetPI / XI3rd PartyApplicationProviding a platform for development of own JCA Resource AdaptersSAPPCK SAP AG 2007, End-to-End Process Integration –Adapter Framework / 38

SAP PCK – AdaptersSAP Partner Connectivity Kit (PCK) is based on AdapterFrameworkSAP PCK‘s objective is to enable XML document exchangebetween PI / XI and business partner not using PI / XISAP PCK also provides an extensible platform for developingand running individual JCA Resource adaptersCommunication between PI / XI and SAP PCK is via SAP XImessaging protocolSAP PCK Includes the following adapters: File/FTP, JDBC, JMS,SOAP, RFC, IDoc (once available for SAP PCK), Mail, SAP BCOptionally SAP PCK can host further adapters that are availablefrom SAP or 3rd party adapter providers SAP AG 2007, End-to-End Process Integration –Adapter Framework / 39

SAP PCK – Configuration, MappingSAP PCK is deployed on stand-alone SAP J2EE Engine (part ofSAP Web AS) within business partner’s landscapeConfiguration, administration, monitoring done locally on SAPPCK itself without need for an Integration DirectoryConfiguration UI provides same „look and feel“ as configurationUI of Adapter EngineSAP PCK supports the development of message mappingsusing an integrated graphical mapping editorAny source XML structure can be mapped to any target XMLstructureStandard functions are provided to perform calculations, Booleancomparisons, text mappings, and other transformationsOptionally the standard functions can be enhanced with userdefined functions in Java SAP AG 2007, End-to-End Process Integration –Adapter Framework / 40

SAP PCK – Configuration UIConfigurationUI to configure Party, Service, Communication Channel, Sender andReceiver agreementsSample screenshot for configuration of communication channel withadapter type ‚File / FTP‘ SAP AG 2007, End-to-End Process Integration –Adapter Framework / 41

AgendaAdapter Framework OverviewAdapter StrategyAdapter Modules and DevelopmentSummary

SAP Exchange Infrastructure - OpennessIntegration of SAP and non-SAP applicationsAdapter Framework for comprehensive integration of adaptersAdapters are used for technical connectivityAdapter metadata, mappings are stored in Integration Repository SAP AG 2007, End-to-End Process Integration –Adapter Framework / 43

Dual StrategyDual connectivity strategyAdapter Framework for comprehensive integration of adapters toprovide technical connectivity, including central configuration,administration, monitoring of adaptersInteroperability based on open standards (SOAP, JMS, HTTP(S)) tointeroperate with EAI providersValue propositionStandardized interfaces allow easy integration of adapters fromdifferent partnersMinimum knowledge of end-to-end process integration requiredComprehensive integration avoids redundant maintenance, ensuresconsistency, enhances transparancyOpenness to integrate non-SAP applications, 3rd party systems, etc.Reduced TCO SAP AG 2007, End-to-End Process Integration –Adapter Framework / 44

CertificationCertificationSAP NetWeaver Certification of 3rd party adapters based on theadapter frameworkValue propositionQuality (stability, HA aspects, performance, etc.) of adapters iscontrolledCertification helps customers to find right solutionQuick and convenient search for a variety of certified productswith the online partner and product SearchSolution.epx)Faster implementation time and lower integration costs throughthe use of tested 3rd party integrationReduced TCO SAP AG 2007, End-to-End Process Integration –Adapter Framework / 45

Adapter Mappings, Metadata in Integration RepositoryAdapter mappings and adapter metadata are stored in theIntegration RepositoryCentralized Integration Repository contains all relevantinformation for collaborative and integrative processesAll content adheres to open standardsAdapters provide technical connectivityValue propositionUse largest content catalogReduce costs in integration projectsReduce maintenance costsReduced TCO SAP AG 2007, End-to-End Process Integration –Adapter Framework / 46

AgendaAdapter Framework OverviewAdapter StrategyAdapter Modules and DevelopmentSummary

Module Processor ConceptFor every adapter it is possible to define generic modulesin the module processor: possibility to extend thefunctionality of the specific adapterEquivalent to the dispatcher classes in the J2SE adapterengine; migration and examplesThe default module configuration for the certain adapteris displayed in the channel configurationModules are EJB‘sSequence matters! SAP AG 2007, End-to-End Process Integration –Adapter Framework / 48

Adapter Module ChainCustom modulescan be added todefault modulechainsAdditionalconfigurationparameters canbe specified eachmodule SAP AG 2007, End-to-End Process Integration –Adapter Framework / 49

Module Processor DocumentationSAP Help Portal (http://help.sap.com)SAP XI RuntimeConnectivityAdaptersModule ProcessorFeedback: Mail to [email protected] SAP AG 2007, End-to-End Process Integration –Adapter Framework / 50

Development EnvironmentAdapter development, deployment andtesting is possible on a single machine, nofull-blown PI / XI is required.PCK Configurationand MonitoringAdapter FWMessagingQueuingSecurity HandlingResourceAdapterFor testing purposes integration scenarioscan be configured in SAP PCK(e.g. loopback scenario).SAP Partner ConnectivityKitInstallation of SAP PCK already contains asample adapter (including Adapter MetaData) that should serve as a starting point.File/DB/JMSMarketplace3rd Party Sys. SAP AG 2007, End-to-End Process Integration –Adapter Framework / 51

Adapter Development DocumentationSAP Help Portal (http://help.sap.com)SAP XI RuntimeConnectivityPartner Connectivity KitFeedback: Mail to [email protected] SAP AG 2007, End-to-End Process Integration –Adapter Framework / 52Adapter Development

Requirements for Adapters (1)NumAF InterfaceCategoryDescription1JCA 1.0 conformanceMandatoryAdapter must fulfill JCA 1.0 requirements (e. g.deployment) plus optional JCA 1.5 parts which areused by PI / XI2AF Message ExchangeMandatoryAdapter must be able to receive messages from AF andforward them to connected system and vice versa3AF Adapter SpecificModulesOptionalSAP XI message and protocol conversion may be doneentirely by the adapter; or as adapter specific moduleand being called in the AF module chain context4Configuration ServicesMandatoryUnique configuration approach to manage ation and Monitoring6Utility ServiceMandatoryAccess to basic J2EE resources, e. g. transactions andmultithreading, must be under control of J2EE server7Logging APIOptionalAdapters may use their own logging8Message MetadataExchangeOptionalProvide structure definition of message payloadIf not supported, the definition of message types can bedone in the Integration Repository SAP AG 2007, End-to-End Process Integration –Adapter Framework / 53

Requirements for Adapters (2)Cluster-enabledConsider side-effects of clustering, e. g. „ExactlyOnceInOrder“:Avoid passing maneuversSpecializationBuild connection to exactly one type of business system or industrystandard protocolDirectnessBuild connection to business system or industry standard protocoldirectly without any intermediate software componentsSmoothnessLight-weighted, low footprint adapter, unnecessary system changes(many new or changed system DLL) should be avoided SAP AG 2007, End-to-End Process Integration –Adapter Framework / 54

Sample Adapter Source CodeBeside the APIdocumentation aworking sample adapteris shipped.The source code isavailable afterinstallation.Analyzing the codehelps understandingthe Adapter Framework. SAP AG 2007, End-to-End Process Integration –Adapter Framework / 55

Adapter MetadataAdapter Metadata (AMD)XML file defines allconfiguration parameterseach adapterAMD can be uploaded intoIntegration Iepositoryand SAP PCKConfigurationparameters are renderedinto the graphicalconfiguaration frontend SAP AG 2007, End-to-End Process Integration –Adapter Framework / 56

Adapter Metadata Fragment I AdapterTypeMetaData version "09" Type NAESB /Type Inbound TransportProtocol ChannelAttributes AttributeGroup Name CRYPT.Configuration /Name GuiLabels Label language "EN" Cryptographic Configuration /Label /GuiLabels AttributeReference ReferenceName CRYPT.UseSigning /ReferenceName /Inbound SAP AG 2007, End-to-End Process Integration –Adapter Framework / 57

Adapter Metadata Fragment II Attribute Name CRYPT.UseSigning /Name DataType xsd:boolean /DataType GuiLabels Label language "EN" Use Signing /Label Label language "DE" Verwendung von Signierung /Label /GuiLabels /Attribute SAP AG 2007, End-to-End Process Integration –Adapter Framework / 58

Adapter ConfigurationConfigurationattribute of typeboolean isrendered to acheck-box SAP AG 2007, End-to-End Process Integration –Adapter Framework / 59

Adapter Metadata Upload (PCK)Integration Repositorydoes not exist in case ofSAP PCK installationsThe upload mechanismfor Adaper Meta Datafor SAP PCK installationsrequires additonalparameters SAP AG 2007, End-to-End Process Integration –Adapter Framework / 60

AF CPA CacheThe 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. SAP AG 2007, End-to-End Process Integration –Adapter Framework / 61

Packaging Adapter ComponentsSAP recommends touse SAP SoftwareDeployment Manager(SDM) for deploymentSoftware DeliveryArchives (SDA) cancontain softwarecomponents of differenttypes (e.g. applications,libraries)Detailed versioninformation anddependencies to othercomponents simplifyprogram management SAP AG 2007, End-to-End Process Integration –Adapter Framework / 62

AgendaAdapter Framework OverviewAdapter StrategyAdapter Modules and DevelopmentSummary

SummaryAdapter Framework runs on J2EE Stack of SAP Web ASAdapter Framework is platform for Adapter Engine and SAP PCKAdapter Framework provides an extensible platform fordeveloping and running adaptersAdapter Engine utilizes central configuration, monitoring,administrationDual connectivity strategyAdapter Framework for comprehensive integration of adaptersInteroperability via open standards to interop. with EAI providersSAP NetWeaver Certification for adapters based on AdapterFramework availableAdapter mappings, metadata stored in Integration Repository SAP AG 2007, End-to-End Process Integration –Adapter Framework / 64

Informatica 3rd-Party solutions are sold and delivered through SAP . Adapter Download from SAP Service Marketplace SAP Service Marketplace: . IDoc RFC and SNC Client Authentication Client Authentication Client Authentication Client Authe