SAP XI 3.0 RDXI30 - Unit4 - AdapterFramework - Detail - V4.

Adapter Engine & Technical Adapters in Detail
SAP AG
SAP INTERNAL ONLY!
Learning Objectives
As a result of this session, you will :

Understand the SAP XI 3.0 in the area of technical
adapters Have an impression of the J2EE based Adapter Engine Be familiar with technical aspects of the individual adapters in detail
SAP AG 2003, Holger Kunitz/ 2
SAP INTERNAL!
Agenda
1. Overview New J2EE based Adapter Engine/AF/PCK
2. J2EE based Adapter Engine -Installation and Administration Issues 3. Technical Aspects of Individual Technical Adapters - RFC-Adapter in detail - IDoc-Adapter in detail - http-Adapter in detail - File/JMS/JDBC in detail - SOAP-Adapter in detail - MarketSet-Adapter introduction RNIF adapter introduction
SAP INTERNAL!
SAP XI AF Building Blocks

XI
R Integration Server XI Adapter Framework on SAP J2EE Server 6.40 R 2 R Connected System 3rd Party JCA 1.0 Adapter
XI Messaging Service
AF Module Processor R 3
Generic AF modules R Integration Directory R Cache R Runtime Workbench Administratio nal Services Utilities (Threads, Transactions) 6 R
Adapter specific modules 4
R external protocol 1 R
Configuration Services
System Landscape Directory
JCA 1.0 Framework 5R
7 R Logging API
Log File & Audit DB
4R
Adapter (configuration) meta data (xsd)
Integration Repository
8R
Message Definition (WSDL, xsd, dtd)
SAP INTERNAL!
The XI 3.0 Adapter Engine Scenario

IS Runtime
Config. cache OK / Error http://<IntegrationServerURL>

Holds component description including address data
XI Message
Adapter Engine in SAP J2EE

http://<AdapterEngineURL> Channel Module Processor
Adapter Framework
Adapter B a c k e n d
Q Integration Builder / Directory: ... Receiver determination

Party->Service->Interface
Configuration cache
Tracing Logging Security Monitoring Administration
J Sender C A
Adapter Receiver
Messaging
... Channel Definition: Adapter Engine

Adapter Type Message Protocol Transport Protocol Security Channel Configuration
AdapterSpecific Component Services
Configuration Master
End-to-End Monitoring (Sender / Receiver Agreement:

Party/Service/Interface <-> Channel
Runtime Workbench Uis for administration,

monitoring
Message flow over all XI components / applications
SAP INTERNAL!
Partner Connectivity Kit

Purpose: Open an XI landscape to partners without XI, but the need to use adapters
Firewall
End-to-End Monitoring
Runtime Workbench Uis for administration,

monitoring
Adapter Framework
PCK in SAP J2EE Adapter Engine in SAP J2EE
B a c k e n d
IS Runtime
Conf. cache
https://<IntegrationServerURL>
XI Message
Module Channel Processor
Q
https://<AdapterEngineURL> Messaging Configura tion Master Tracing Logging Security
Adapter Sender Adapter Recv.
Integration Builder / Directory:
Conf UI
Monitoring Administration
AdapterSpecific Compone nt Services
... Receiver determination

...
Mon. UI Adm. UI
Configuration Master
Party->Service->Interface
System Landscape Dir. SAP INTERNAL!

component description including address data
Third Party Adapters

SAP Intranet SAP DMZ Internet Partner VPN
XI 3.0SP1
R Integration Server
XI Adapter Framework on SAP J2EE Server 6.30 SP4 R 2 R
XI Messaging Service
AF Module Processor R 3
3rd Party JCA 1.0 Adapter
Generic AF modules R Integration Directory R Cache R Runtime Workbench Administratio nal Services Utilities (Threads, Transactions) 6 R
Adapter specific modules 4
Connected System e.g. A2A: Siebel, Oracle, Peoplesoft or B2B: UCCnet, CIDX, EDIFact VPN Client
R external protocol
Configuration Services
JCA 1.0 Framework 5 R
1 R
7 R Logging API
Log File & Audit DB
Integration Repository
Client GUI
R external protocol
4 R 8
Adapter (configuration) meta data (xml)
Message Definition (WSDL, xsd, dtd)
SAP INTERNAL!
Overview - Summary
J2EE Based SAP XI AF:

-Provides common services for technical, application system, industry-Specific adapters (B2B, A2A, B2A) => Security => Transactions => Monitoring, Audit Log, Trace => SLD Registration (6.40) and Access
- Used by central/decentral AE, PCK, 3rd Parties, (JPR)

- Makes Use of JCA 1.0 - Based on SAP J2EE 1.3 ? 1.4 - Open for Partner solutions (certification process) no additional runtime engine - Decentral and Central installation but central configuration, monitoring, administration
SAP INTERNAL!
Agenda

2. New J2EE based Adapter Engine Installation and Administration Issues 3. Technical Aspects of Individual Technical Adapters - RFC-Adapter - IDoc-Adapter - http-Adapter - File/JMS/JDBC - SOAP-Adapter - MarketSet-Adapter
SAP INTERNAL!
Installation of SAP WAS and User/UME
Central AE: uses UME with ABAP (J2EE with Add-In option), i.e. UME of this engine is configured against the coresponding ABAP stack automatically during installation) Decentral AE: uses UME with DB only (default) or UME with ABAP (su01, PFCG; roles visible as groups; CUSTOM INSTALLATION); decision at installation time!
SAP INTERNAL!
Select Adapter Framework from the SAP Netweaver CD
SAP INTERNAL!
CPA Cache - Registration
SLD
1 Change in XI ID 5
3 2
AE CPA Cache
SAP INTERNAL!
CPA-Cache Service Directory or PCK?
SAP INTERNAL!
CPA Cache
SAP INTERNAL!
Parameter Cache Service - SLDAccess
SAP INTERNAL!
Connection to the Central Exchange Profile
SAP INTERNAL!
Users UME with DB only

XIDIRUSER XIISUSER XIAFUSER (XILDUSER)
SAP INTERNAL!
Give Access to Messaging System Monitor for Admin
SAP INTERNAL!
Give Access to Messaging System Monitor for Admin
SAP INTERNAL!
Address of the System Landscape Directory
SAP INTERNAL!
SXI_CACHE
SAP INTERNAL!
Start & Stop Service vs. Communication Channel
SAP INTERNAL!
Message Monitoring - Alias MDT
SAP INTERNAL!
Messaging System
http://<host>:<port>/MessagingSystem
SAP INTERNAL!
Detailed Audit Log
SAP INTERNAL!
Enable Single Trace for AF
SAP INTERNAL!
Switch Individual Trace On
SAP INTERNAL!
Log Destination
SAP INTERNAL!
Adapter Metadata in Repository
SAP INTERNAL!
SLD Entries and http-ports
SAP INTERNAL!
Agenda

2. New J2EE based Adapter Engine Installation and Administration Issues 3. Technical Aspects of Individual Technical Adapters - RFC-Adapter - IDoc-Adapter - http-Adapter - File/JMS/JDBC - SOAP-Adapter - MarketSet-Adapter
SAP INTERNAL!
Communication Channel Template

To Preconfigure a communication channel required at configuration time. Specify an Adapter Type (File, JMS, RFC, etc) Direction (Sender / Receiver) Transport Protocol
Message Protocol
Used to select attributes specific to the adapter type Evaluate conditions require defining additional field values
SAP INTERNAL!
The New RFC-Adapter: Architecture Logical View

Channel cache
J2EE AF (AE/PCK)
XI-SOAP/http RFC
Integration Server
Messaging Modul XI RFC System Processor Adapter XI-SOAP/http JRFC/Jco M1 M.. -lib Mn
RFCServer/Client
RFC
Adapter: module Localeejbs/RFCAFBean

SAP INTERNAL!
The New RFC-Adapter

Runs as a service in the J2EE environment of the Adapter Engine (i.e. also central configuration) Is also part of the PCK Support for synchronous and tRFC Uses JRFC (additional parameters in the expert mode of the communication channel) Supports SAPRouter Current Refresh of Metadata: - activate/deactivate communication channel - restart the adapter service
Communication Channel: type RFC; Service of type BS without party
SAP INTERNAL!
Advanced Mode and Metadata Repository
SAP INTERNAL!
New RFC-Adapter (Current)Limitations
No Call-Back; No RFC-GUI-Debug
No qRFC Just one payload/attachment
No digital signature
Currently:
not released for external system (in test; dedicated RFC-gateway necessary, i.e. this will not be delivered with the J2EE Service) no SNC not several function calls with one TID/ within one LUW (this is also a change to XI 2.0)
SAP INTERNAL!
IDoc-Adapter Receiver Channel Type IDoc
SAP INTERNAL!
IDoc Party and XI Party

IDoc Control Record DOCNUM MANDT SNDPOR SNDPRN SNDPRT SNDPFC RCVPRN RCVPRT RCVPFC XI Message Header GUID sender sender sender sender party agency party scheme party name service party agency party scheme party name service
receiver receiver receiver receiver
MESTYP IDOCTYP CIMTYP ...

interface namespace interface name
SAP INTERNAL!
Relation Sender System to XI Party-less service

The sender system identifies itself with the fields SNDPOR(sender port) and Client of the IDoc control record. The sender system must fill the field sender port: R/3 System => sender port := SAP + SYSID other => sender port := logical system
Identification obligatory
:= SYSID_Client or logical system
service name (XI partyless service)
SAP INTERNAL!
Relation Sender System to XI Party-less Service
SAP INTERNAL!
IDoc-Adapter How to Fill Control Record from External?

! = mandatory
Technical fields:
!MANDT: 100 !DOCREL: SNDPOR: WCU !DIRECT: 1 !TABNAM: EDI_DC40 !DOCNUM: 0000000000000001
Interface:
!IDOCTYP: WMTCID02 ZIMTYP: for customer extension !MESTYP: WMTOCO MESCODE:
MESFUNC:
!SNDPRT: LS !SNDPRN: WMUNIT SNDPFC: optional Partner Function !RCVPRT: LS !RCVPRN: SP4CLNT800 RCVPFC: Optional TEST: optional SERIAL: optional
(valid for structure: edi_dc40)
SAP INTERNAL!
Relation IDoc Party to XI Party

One business party, i.e. TravelAgency, as IDoc party in different systems system BCE BCE ALR client IDoc party name 123 123 456 4711 8004711 Meyer party type LI DE LI party function LF -
party name := IDoc party name party scheme := ALE#party type[#party function] party agency := service
optional party name := business party party scheme := XIParty party agency := http://sap.com/xi/XI/Systems
not visible in Directory
SAP INTERNAL!
Relation IDoc party to XI party
system BCE
client IDoc party name 123 4711
party type LI
party function -
BCE
ALR
123
456
8004711
Meyer
DE
LI
LF
-
Configuration of relations in Integration Directory
SAP INTERNAL!
Relation XI Party to IDoc party

XI Partner Travel Agency, role for IDoc party unknown, must be defined by the administrator for the IDoc outbound case
Configuration of relation in the Integration Directory
SAP INTERNAL!
Overview: IDoc control record

The IDoc-Adapter sends out IDocs with a Control record, overview how to configure the control record fields
routing pipeline service
mapping
channel definition / identification party role & technical routing RCVPOR * SNDPRN * * SNDPRT * * SNDPFC * RCVPRN RCVPRT RCVPFC
IDoc outbound adapter build IDoc control record
party & interface determination fields of IDoc control record * MESTYP * IDOCTYP CIMTYP
payload modification
SNDPOR MANDT DIRECT CREDATE CRETIME TABNAM STATUS OUTMOD DOCREL ARCKEY
Fields are set by the system runtime, no configuration possible Fields are configured by the administrator, IDoc key fields are marked with an asterix (*)
SAP INTERNAL!
IDoc-Adapter Supports EOIO
Application System Partner Profile
Directory: Communication Channel
SAP INTERNAL!
IDoc-Adapter Other Changes
Port not generated automatically out of the end point anymore Fixed namespace urn:sapcom:document:sap:idoc:messages not mandatory, i.e. not checked by the adapter and no
influence on the suggested adapter type in the directory
SAP INTERNAL!
SOAP Adapter
Directory: Adapter Type SOAP Module-name:

localejbs/sap.com/com.sap.aii.af.soapadapter/XISOAPAdapterBean
Inbound:
http://<host_and_port>/XISOAPAdapter/MessageServlet?query
SAP INTERNAL!
SOAP Adapter
SOAP adapter enables exchange of SOAP messages between remote clients or Web service servers and the Integration Server
The transport protocol supported by SOAP adapter is HTTP and the message protocol being SOAP 1.1
Choose the Adapter Engine where the SOAP adapter needs to be configured
SAP INTERNAL!
SOAP Adapter Sender
Keep Headers will enable web service header to be included in the XI message Keep Attachments will enable web service attachment to be included in the XI message A true for Encoded headers will encode the header
SAP INTERNAL!
SOAP Adapter Sender Additional parameters
XI Parameters
Interface Namespace Interface Name
Processing Parameters

Best Effort (BE) Exactly Once (EO) Exactly Once In Order (EOIO)
SAP INTERNAL!
SOAP Adapter Receiver

Used to send information from remote clients to the integration server
SAP INTERNAL!
http-Adapter

Supports EOIO now (URL) Module processor not used Directory: only receiver communication channel necessary Switch for Content Types (e.g. BC-IDoc-XML) hardcoded Unchanged: => http 1.0 => no fault messages/attachments (ignored)
New parameters on the query string (party, agency, scheme, service, Queue ID, QoS EOIO)
SAP INTERNAL!
File Adapter
Type File
Exactly one sender agreement per Communication channel
At least interface name and sender service must be qualified in the sender agreement
SAP INTERNAL!
File Adapter: Sender
SAP INTERNAL!

File System Access Parameters: Source Directory and Filename File Type

Text OR Binary (Suggested)
SAP INTERNAL!

File Processing Parameters: Quality of Service
Best Effort
EO
EOIO Specify Queue name in this case
Poll Interval Processing Mode

Archive w.timestamp possible Set to Read only Delete Test
Processing Sequence
Operating system command
SAP INTERNAL!
File Adapter Sender: Specifying File content Conv.

Required to convert non-xml file (flat) to XMB (xml) file or ViceVersa.
SAP INTERNAL!
File Adapter Receiver

File System Access Parameters: Target Directory File Name Schema File Construction Mode

Create Append
Add Timestamp
Add MessageID Add Counter
SAP INTERNAL!
File Adapter Receiver

Parameters Continued File Type
Text
Binary
File Encoding
SAP INTERNAL!
JDBC-Adapter
Type JDBC Exactly one sender agreement per Communication channel At least interface name and sender service must be qualified in the sender agreement
SAP INTERNAL!
Vendor Specific Driver (JMS, JDBC)

Add driver(s) (jar) to aii_af_jmsproviderlib.sda Unpack, modify and pack provider.xml from/to aii_af_jmsproviderlib.sda; for packing: use the same path/server Deploy aii_af_jmsproviderlib.sda (ignore version) JMS only: remove the javax/jms classes from the driver jar first
SAP INTERNAL!
JMS-Adapter
Type JMS Exactly one sender communication channel per Sender-CPA At least interface name and sender service must be qualified in the sender agreement Asynchronous
SAP INTERNAL!
JMS Adapter
To connect Messaging systems to the Integration Engine
JMS Protocols Transport Protocol

Sonic MQ WebSphere MQ JNDI JMS provider lookup JMS provider Objects via file Generic JMS Provider
Message Protocol
JMS 1.x
SAP INTERNAL!
JMS Adapter: Sender
SAP INTERNAL!
JMS Adapter Sender parameters

The parameters depend upon the JMS Provider chosen in the transport protocol Sonic MQ JMS Provider
Java class QueueConnectionFactory Java class queue IP address or server name Server port JMS queue
SAP INTERNAL!
JMS Adapter Sender

WebSphereMQ (MQ Series) JMS Provider
Java class QueueConnectionFactory Java class queue IP address or server name Queue manager name Channel name JMS queue Character set for non-ASCII names
Transport/network protocol Target client
SAP INTERNAL!
JMS Adapter Sender

JNDI JMS Provider Lookup
JNDI name of QueueConnectionFactory JNDI name of JMS queue Name of JNDI Initial Context Factory Address of JNDI server JNDI users JNDI password with confirmation
JMS Provider Administered Objects via File

File name of serialized object QueueConnectionFactory File name of serialized object Queue
SAP INTERNAL!
JMS Adapter Sender

Generic JMS Provider
All the required parameters are entered in the table
Additional JMS Parameters
Done via entering parameters and values in the table
General JMS Settings

Transaction JMS Session
If you want to use a transactional JMS session use this setting. Following processing of a message, a transactional session ends either with a COMMIT, or in the case of an error, with a ROLLBACK
SAP INTERNAL!
JMS Adapter Sender

XI Settings
Mapping the Message

Entire XMB message to be JMS-payload XMB payload to be the JMS-payload Best Effort (BE) Exactly Once Exactly Once In Order
Specify the Queue ID and Processing J2EE cluster Server (Cluster ID)
Quality of Service

SAP INTERNAL!
JMS Adapter Receiver

To convert XML messages from the Integration server into JMS messages. Transport Protocols

Sonic MQ JMS Provider WebSphereMQ (MQ Series) JNDI JMS Provider lookup JMS Provider Administered Objects via File Generic JMS Provider
Message Protocol
JMS 1.x
SAP INTERNAL!

The parameters depend upon the JMS Provider chosen in the transport protocol Sonic MQ JMS Provider
Java class QueueConnectionFactory Java class queue IP address or server name Server port JMS queue
SAP INTERNAL!

WebSphereMQ (MQ Series) JMS Provider
Java class QueueConnectionFactory Java class queue IP address or server name Queue manager name Channel name JMS queue Character set for non-ASCII names
Transport/network protocol Target client
SAP INTERNAL!

JNDI JMS Provider Lookup
JNDI name of QueueConnectionFactory JNDI name of JMS queue Name of JNDI Initial Context Factory Address of JNDI server JNDI users JNDI password with confirmation
JMS Provider Administered Objects via File

File name of serialized object QueueConnectionFactory File name of serialized object Queue
SAP INTERNAL!

Generic JMS Provider
All the required parameters are entered in the table
Additional JMS Parameters
Done via entering parameters and values in the table
General JMS Settings

Transaction JMS Session
If you want to use a transactional JMS session use this setting. Following processing of a message, a transactional session ends either with a COMMIT, or in the case of an error, with a ROLLBACK
You can also specify the quality of service
Save JMS messages in the JMS provider Do not save JMS messages in the JMS provider
SAP INTERNAL!

XI Settings
Mapping the Message

Entire XMB message to be JMS-payload XMB payload to be the JMS-payload
SAP INTERNAL!
JMS Adapter Modules

Sender Adapter Modules
SAP INTERNAL!
JMS Adapter Modules

Receiver Adapter Modules
SAP INTERNAL!
JMS Adapter Generic JMS Provider
JMS Adapter Modules

localejbs/sap.com/com.sap.aii.af.jmsadapter/ConvertJMSMessageToBinary localejbs/sap.com/com.sap.aii.af.jmsadapter/ConvertBinaryToXMBMessage localejbs/sap.com/com.sap.aii.af.adapter. caller/CallAdapterWithMessageBean
JMS Adapter Configuration Parameters

XMB.InterfaceNamespace XMB.Interface XMB.SenderService
XMB.SenderParty
SAP INTERNAL!
Adding External drivers

For JMS and JDBC adapters the J2EE server needs to be deployed with external jar files. 1. Modify the file providerlib.xml from aii_af_jmsproviderlib.sda to look like this:
<jars> <jar-name> jmsdriver.jar </jar-name> <jar-name> jdbcdriver.jar </jar-name> </jars>
2. Add the above jar files into aii_af_jmsproviderlib.sda 3. Deploy the modified aii_af_jmsproviderlib.sda into the J2EE server in a standalone mode using SDM 4. Restart the J2EE server for the change to take effect
SAP INTERNAL!
Configuring SOAP adapter

SOAP adapter enables exchange of SOAP messages between clients or web service servers and the Integration Server
SAP INTERNAL!
Marketplace Adapter
XSDK not necessary anymore

Transport protocols Sender Adapter:
http/https JMS Sonic 3.5
Transport protocols Receiver Adapter

http/https JMS Sonic 3.5
Adapter Type Marketplace
SAP INTERNAL!
Module Processor Concept
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; currently: no direct migration path for this classes from SAP XI 2.0 to XI3.0
If no module is specified in the communication channel explicitly: the default module for the certain adapter is used
SAP INTERNAL!
Module Processor per Adapter

Adapter specific Modules localejbs/sap.com/com.sap.aii.af.adapter.caller/CallAdapterWith MessageBean
RFC adapter
File/FTP Adapter JDBC Adapter JMS Adapter ???
localejbs/sap.com/com.sap.all.af.SoapAdapter/xisoapAdapterBe an
SOAP Adapter
localejbs/RNIFModuleListener
RNIF Adapter
SAP INTERNAL!
Encryption & https

1) Install the SAP Java Cryptographic Toolkit
- download the SDA from either - service.sap.com/download - https://security.wdf.sap.corp/public/projects/iaik/ - (here you'll also find the "SAP J2EE Engine Security Documentation" and links to the SAPNetCA and TestCA) - deploy the SDA (tc_sec_java_crypto_signed_fs_lib_630SP1.sda) with SDM - extract and copy jars contained in the SDA to usr\sap\<SID>\<instance>\j2ee\admin\lib - use the config tool to set the startup method of the keystore and ssl service to "always"
2)
Create the Server's Key pair to use for SSL

- you can either import an existing private key pair from the file system (PKCS#12 file required -> .p12) - or you create an certificate request using the J2EE keystore service - import private server keys to the service_ssl keystore view - when creating an entry to user for SSL, use the server's host name as the Common Name part of th Distinguished Name. - if the certificate has not yet been signed by a CA, then follow the instructions in "SAP J2EE 6.30 Administration Manual" page 244 - for the SAP CA, follow the instructions provided by the SAP Trust Center Service at http://service.sap.com/tcs - for the Test-CA use the link: http://service.sap.com/SSLTest
3)
Assign the key pair to use for the specific SSL port - prequisites: - key pair exists as a private key in the service_ssl view of the keystore service - the SSL provider service is running for each dispatcher and server instance that is to support SSL - follow the instructions in "SAP J2EE 6.30 Administration Manual" page 245
4) Configure client certificates - optional and currently not supported by XI internal communication - configuration described in "SAP J2EE 6.30 Administration Manual" page 275
SAP INTERNAL!
Acknowledgements
Type Sender Receiver
Idoc Adapter
all (*2*)
all (*3*)
RNIF Adapter
Others
3/4 (*4*)
none
1/4 (*5*)
2/4 (*1)
(*1*) Delivery Acks (SysAcks) only (*2*) Per Default the Idoc Adapter requests all Acks. Can be configured if no Acks should be requested (transparent table IDXNOALE) (*3*) If Acks are replied, depends on ALEAUDIT configuration in target system. (*4*) RNIF Adapter always requests positiv und negative SystemAcks and negative ApplicationAcks (*5*) RNIF Adapter supports only positive SystemAcks (*6*) Scenario Proxy IDoc now possible (*7*) Message split and acks: status unknown (except ABAP-proxy)
SAP INTERNAL!
Certified 3rd Party Adapters

Num Semantic Name Owner Type Category
Adapter Access
JCA 1.0 SPI
SAP J2EE
JCA Container
Mandatory
Message Exchange
Proprietary or XI AF CCI XI AF MP XI AF IB/PCK
XI AF
Java library
Mandatory
3 4
Module Configuration
XI AF XI AF/IB
Java library XML upload, J2EE service
Optional Mandatory
5 6
Administration J2EE Ressource Access
XI AF RWB XI AF Util
XI AF XI AF
TBD Java service
Optional Mandatory
Logging&Monitoring
XI AF Trace
XI AF, PMI, SAP J2EE
Java library
Optional
Message Defintion
XI IR Ex.Def.
XI IR
File upload
Optional
SAP INTERNAL!
Stay Tuned!
User Interface for Start/Stop, CPA Cache Refresh, Test

Acks-Concept for RAs/API Messaging System Specification for modules Synchronous JMS RFC-Adapter: Several function calls with one Commit, external Systems, SNC PIM-Integration (Technical Adapter, RAs)
SAP INTERNAL!
How to address the J2SE-based AE?
Type XI
SAP INTERNAL!
Questions?
Thank you!!!
Questions??
SAP INTERNAL!

SAP XI 3.0 RDXI30 - Unit4 - AdapterFramework - Detail - V4.

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

SAP XI 3.0 RDXI30 - Unit4 - AdapterFramework - Detail - V4.

Uploaded by

Copyright:

Available Formats

Adapter Engine & Technical Adapters in Detail

As a result of this session, you will :

SAP AG 2003, Holger Kunitz/ 2

SAP AG 2003, Holger Kunitz/ 3

SAP XI AF Building Blocks

Adapter specific modules 4

System Landscape Directory

JCA 1.0 Framework 5R

Log File & Audit DB

Adapter (configuration) meta data (xsd)

Message Definition (WSDL, xsd, dtd)

SAP AG 2003, Holger Kunitz/ 4

The XI 3.0 Adapter Engine Scenario

System Landscape Directory

Adapter Engine in SAP J2EE

Q Integration Builder / Directory: ... Receiver determination

... Channel Definition: Adapter Engine

AdapterSpecific Component Services

End-to-End Monitoring (Sender / Receiver Agreement:

Runtime Workbench Uis for administration,

Message flow over all XI components / applications

Partner Connectivity Kit

Runtime Workbench Uis for administration,

Module Channel Processor

Adapter Sender Adapter Recv.

Integration Builder / Directory:

AdapterSpecific Compone nt Services

... Receiver determination

System Landscape Dir. SAP INTERNAL!

SAP AG 2003, Holger Kunitz/ 6

Third Party Adapters

XI Adapter Framework on SAP J2EE Server 6.30 SP4 R 2 R

3rd Party JCA 1.0 Adapter

Adapter specific modules 4

System Landscape Directory

JCA 1.0 Framework 5 R

Log File & Audit DB

Adapter (configuration) meta data (xml)

Message Definition (WSDL, xsd, dtd)

SAP AG 2003, Holger Kunitz/ 7

J2EE Based SAP XI AF:

- Used by central/decentral AE, PCK, 3rd Parties, (JPR)

SAP AG 2003, Holger Kunitz/ 8

1. Overview New J2EE based Adapter Engine/AF/PCK

SAP AG 2003, Holger Kunitz/ 9

Installation of SAP WAS and User/UME

SAP AG 2003, Holger Kunitz/ 10

Select Adapter Framework from the SAP Netweaver CD

SAP AG 2003, Holger Kunitz/ 11

CPA Cache - Registration

SAP AG 2003, Holger Kunitz/ 17

CPA-Cache Service Directory or PCK?

SAP AG 2003, Holger Kunitz/ 18

SAP AG 2003, Holger Kunitz/ 19

Parameter Cache Service - SLDAccess

SAP AG 2003, Holger Kunitz/ 20

Connection to the Central Exchange Profile

SAP AG 2003, Holger Kunitz/ 21

Users UME with DB only

SAP AG 2003, Holger Kunitz/ 22

Give Access to Messaging System Monitor for Admin

SAP AG 2003, Holger Kunitz/ 23

Give Access to Messaging System Monitor for Admin