4 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 XI AF Building Blocks
XI XI Adapter Framework on SAP J2EE Server 6.40 Connected

System
2
R R R 3rd Party
XI Messaging AF Module
Integration Server JCA 1.0
Service Processor
Adapter
R 3 R
Adapter
Generic AF
specific
modules R
modules
external
R 4 R protocol
Configuration
Integration Directory
Services
1
R R
System Landscape JCA 1.0
Directory Cache Framework
R 5R
Administratio
Runtime Workbench
nal Services
7
Utilities 6 R
Logging
(Threads,
API
Transactions)
Log File &

Audit DB
4R
Adapter (configuration) meta
data (xsd)
Integration Repository 8R
Message Definition
(WSDL, xsd, dtd)

The XI 3.0 Adapter Engine Scenario
http://<IntegrationServerURL> System Landscape Directory

IS • Holds component description
Runtime including address data
Config.
cache XI Message Adapter
OK / Error
Framework
Adapter Engine in SAP J2EE
Module Processor Adapter B
http://<AdapterEngineURL> J Sender a
Channel
C c
A k
Q Adapter e
Integration Builder / Directory: Receiver n
Messaging d
... Receiver determination

• Party->Service->Interface Configuration Tracing
cache Logging Adapter-
... Channel Definition: Security
Specific
Component
• Adapter Engine Services
• Adapter Type Monitoring Administration
• Message Protocol
• Transport Protocol
Configuration
• Security Master
• Channel Configuration Runtime Workbench
End-to-End Monitoring • Uis for administration,
(Sender / Receiver Agreement: Message flow over all XI monitoring
• Party/Service/Interface <-> Channel components / applications

Partner Connectivity Kit
• Purpose: Open an XI landscape to partners without XI,

but the need to use adapters
Firewall
Runtime Workbench Adapter
End-to-End • Uis for administration, Framework
Monitoring monitoring
PCK in SAP
Adapter J2EE
Engine in SAP J2EE B
Module Adapter a
XI Sender
Channel Processor c
IS https://<IntegrationServerURL> Message Adapter k
Runtime Q Recv. e
https://<AdapterEngineURL> n
Conf. ´Messaging d
cache
Configura Tracing Adapter-
tion Logging Specific
Conf Master Security Compone
nt
Integration Builder / UI Services
Monitoring Administration
Directory:
Mon. UI Adm. UI
... Receiver
Configuration
determination Master
• Party->Service->Interface
...
System Landscape Dir.
• component description
including address data
Third Party Adapters
SAP Intranet SAP DMZ Internet Partner VPN
XI 3.0SP1 XI Adapter Framework on SAP J2EE Server 6.30 SP4 Connected

System
2
e.g. A2A:
R R R 3rd Party
XI Messaging AF Module Siebel,
Integration Server JCA 1.0
Service Processor Oracle,
Adapter Peoplesoft
R 3 R or B2B:
UCCnet,
Adapter CIDX,
Generic AF EDIFact
specific
modules R
modules
VPN
Client external
R 4 R protocol
Configuration
Integration Directory
Services
1
R R
System Landscape JCA 1.0
Directory Cache Framework
R 5 R
Administratio
Runtime Workbench
nal Services
7
Utilities 6 R
Logging
(Threads,
API
Transactions)
Log File &

Audit DB
R
Integration Repository Client
GUI external
protocol
4 R
R
Adapter (configuration) meta
8
data (xml)
Message Definition
(WSDL, xsd, dtd)

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

Agenda
1. Overview – New J2EE based Adapter

Engine/AF/PCK
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

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!

Select Adapter Framework from the SAP Netweaver CD

CPA Cache - Registration
SLD
Change
in XI ID
3
2 4 5
AE CPA Cache

CPA-Cache Service Directory or PCK?

CPA Cache

Parameter Cache Service - SLDAccess

Connection to the Central Exchange Profile

Users „UME with DB only“
XIDIRUSER
XIISUSER
XIAFUSER
(XILDUSER)

Give Access to Messaging System Monitor for Admin

Give Access to Messaging System Monitor for Admin

Address of the System Landscape Directory

SXI_CACHE

Start & Stop Service vs. Communication Channel

Message Monitoring - Alias MDT

Messaging System
http://<host>:<port>/MessagingSystem

Detailed Audit Log

Enable Single Trace for AF

Switch Individual Trace On

Log Destination

Adapter Metadata in Repository

SLD Entries and http-ports

Agenda
1. Overview – New J2EE based Adapter

Engine/AF/PCK
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

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

The “New” RFC-Adapter: Architecture – Logical View
Channel
cache
J2EE AF
(AE/PCK)
XI-SOAP/http RFC
Integration RFC-
Server Messaging Modul XI RFC Server/Client
System Processor Adapter
XI-SOAP/http RFC
M1 JRFC/Jco
M.. -lib
Mn
Adapter: module
Localeejbs/RFCAFBean

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

Advanced Mode and Metadata Repository

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)

IDoc-Adapter – Receiver Channel Type IDoc

IDoc Party and XI Party
IDoc Control Record XI Message Header
DOCNUM GUID
MANDT sender party agency

SNDPOR sender party scheme
sender party name
SNDPRN sender service
SNDPRT
SNDPFC receiver party agency
receiver party scheme
RCVPRN receiver party name
RCVPRT receiver service
RCVPFC
interface namespace
MESTYP interface name
IDOCTYP
CIMTYP
...

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 := ‚SYSID‘_Client‘ or ‚logical system‘
obligatory
service name (XI partyless service)

Relation Sender System to XI Party-less Service

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)

Relation IDoc Party to XI Party
One business party, i.e. TravelAgency,

as IDoc party in different systems
system client IDoc party name party type party function

BCE 123 4711 LI -
BCE 123 8004711 DE LF
ALR 456 Meyer LI -
party name := IDoc party name

party scheme := ALE#‚party type‘[#‚party function‘]
party agency := service
optional
party name := ‚business party‘

party scheme := XIParty not visible
party agency := http://sap.com/xi/XI/Systems

in Directory

Relation IDoc party to XI party
system client IDoc party name party type party function

BCE 123 4711 LI -
BCE 123 8004711 DE LF
ALR 456 Meyer LI -
Configuration of relations in Integration Directory

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

Overview: IDoc control record
The IDoc-Adapter sends out IDocs with a Control record,

overview how to configure the control record fields
routing mapping channel IDoc

pipeline service definition / outbound
identification adapter
party payload party role build

& modification & IDoc control
interface technical record
determination routing
fields of IDoc * MESTYP * RCVPOR SNDPOR

control record IDOCTYP * SNDPRN * MANDT
CIMTYP * SNDPRT * DIRECT
* SNDPFC * CREDATE
RCVPRN CRETIME
RCVPRT TABNAM
RCVPFC 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 (*)

IDoc-Adapter – Supports EOIO
Application System Partner Directory: Communication

Profile Channel

IDoc-Adapter – Other Changes
 Port not generated automatically out of the

end point anymore
 Fixed namespace urn:sap-

com:document:sap:idoc:messages not
mandatory, i.e. not checked by the adapter and no
influence on the suggested adapter type in the
directory

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

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

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

SOAP Adapter Sender Additional parameters
XI Parameters
 Interface Namespace
 Interface Name
Processing Parameters
 Best Effort (BE)
 Exactly Once (EO)
 Exactly Once In Order (EOIO)

SOAP Adapter Receiver
Used to send information from remote clients to the integration

server

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) – hard-

coded
 Unchanged: => http 1.0

=> no fault messages/attachments
(ignored)
 New parameters on the query string (party, agency,

scheme, service, Queue ID, QoS EOIO)

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

File Adapter: Sender

File System Access Parameters:
 Source Directory and Filename
 File Type
 Text OR
 Binary (Suggested)

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

File Adapter Sender: Specifying File content Conv.
Required to convert non-xml file (flat) to XMB (xml) file or Vice-

Versa.

File Adapter Receiver
File System Access Parameters:
 Target Directory
 File Name Schema
 File Construction Mode

 Create
 Append
 Add Timestamp
 Add MessageID
 Add Counter

File Adapter Receiver
Parameters Continued…
 File Type
 Text
 Binary
 File Encoding

JDBC-Adapter
 Type JDBC

agreement per
Communication channel

agreement

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

JMS-Adapter
 Type JMS

communication channel per
Sender-CPA

agreement
 Asynchronous

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

JMS Adapter: Sender

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

JMS Adapter Sender
WebSphereMQ (MQ Series) JMS Provider

 Queue manager name
 Channel name
 JMS queue
 Character set for non-ASCII names
 Transport/network protocol
 Target client

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

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

JMS Adapter Sender
XI Settings
 Mapping the Message
 Entire XMB message to be JMS-payload
 XMB payload to be the JMS-payload
 Quality of Service
 Best Effort (BE)
 Exactly Once
 Exactly Once In Order
 Specify the Queue ID and
 Processing J2EE cluster Server (Cluster ID)

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

The parameters depend upon the JMS Provider chosen in the

transport protocol
Sonic MQ JMS Provider

 Server port
 JMS queue

WebSphereMQ (MQ Series) JMS Provider

 Queue manager name
 Channel name
 JMS queue
 Character set for non-ASCII names
 Transport/network protocol
 Target client

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

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

XI Settings
 Mapping the Message
 Entire XMB message to be JMS-payload
 XMB payload to be the JMS-payload

JMS Adapter Modules
Sender Adapter Modules

JMS Adapter Modules
Receiver Adapter Modules

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

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

Configuring SOAP adapter
SOAP adapter enables exchange of SOAP messages between

clients or web service servers and the Integration Server

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“

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

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

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

Acknowledgements
Type Sender Receiver
Idoc Adapter all (*2*) all (*3*)
RNIF Adapter 3/4 (*4*) 1/4 (*5*)
Others none 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)
Certified 3rd Party Adapters
Num Semantic Name Owner Type Category
1 Adapter Access JCA 1.0 SPI SAP J2EE JCA Container Mandatory
2 Message Exchange Proprietary or XI AF Java library Mandatory

XI AF CCI
3 Module XI AF MP XI AF Java library Optional
4 Configuration XI AF IB/PCK XI AF/IB XML upload, J2EE Mandatory

service
5 Administration XI AF RWB XI AF TBD Optional
6 J2EE Ressource Access XI AF Util XI AF Java service Mandatory
7 Logging&Monitoring XI AF Trace XI AF, PMI, SAP Java library Optional

J2EE
8 Message Defintion XI IR Ex.Def. XI IR File upload Optional

Stay Tuned!
 User Interface for Start/Stop, CPA Cache

Refresh, Test
 Acks-Concept for RA‘s/API Messaging

System
 Specification for modules
 Synchronous JMS
 RFC-Adapter: Several function calls with one

Commit, external Systems, SNC
 PIM-Integration (Technical Adapter, RA‘s)

How to address the J2SE-based AE?
Type „XI“
Questions?
Thank you!!!
Questions??

4 RDXI30 Unit4 AdapterFramework Detail V4

Uploaded by

Copyright:

Available Formats

You might also like

4 RDXI30 Unit4 AdapterFramework Detail V4

Uploaded by

Document Information

Original Description:

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

4 RDXI30 Unit4 AdapterFramework Detail V4

Uploaded by

Copyright:

Available Formats

Adapter Engine & Technical

As a result of this session, you will :

 Understand the SAP XI 3.0 in the area of technical

 SAP AG 2003, Holger Kunitz/ 2 SAP INTERNAL!

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

2. J2EE –based Adapter Engine -Installation and

3. Technical Aspects of Individual Technical Adapters

RNIF adapter introduction

 SAP AG 2003, Holger Kunitz/ 3 SAP INTERNAL!

XI XI Adapter Framework on SAP J2EE Server 6.40 Connected

Log File &

 SAP AG 2003, Holger Kunitz/ 4 SAP INTERNAL!

http://<IntegrationServerURL> System Landscape Directory

... Receiver determination

 SAP AG 2003, Holger Kunitz/ 5 SAP INTERNAL!

• Purpose: Open an XI landscape to partners without XI,

SAP Intranet SAP DMZ Internet Partner VPN

XI 3.0SP1 XI Adapter Framework on SAP J2EE Server 6.30 SP4 Connected

Log File &

 SAP AG 2003, Holger Kunitz/ 7 SAP INTERNAL!

J2EE Based SAP XI AF:

 SAP AG 2003, Holger Kunitz/ 8 SAP INTERNAL!

1. Overview – New J2EE based Adapter

2. New J2EE –based Adapter Engine -

3. Technical Aspects of Individual Technical

 SAP AG 2003, Holger Kunitz/ 9 SAP INTERNAL!

 Central AE: uses UME with ABAP (J2EE with

 Decentral AE: uses UME with DB only

 SAP AG 2003, Holger Kunitz/ 10 SAP INTERNAL!

 SAP AG 2003, Holger Kunitz/ 11 SAP INTERNAL!

 SAP AG 2003, Holger Kunitz/ 17 SAP INTERNAL!

 SAP AG 2003, Holger Kunitz/ 18 SAP INTERNAL!

 SAP AG 2003, Holger Kunitz/ 19 SAP INTERNAL!

 SAP AG 2003, Holger Kunitz/ 20 SAP INTERNAL!

 SAP AG 2003, Holger Kunitz/ 21 SAP INTERNAL!

 SAP AG 2003, Holger Kunitz/ 22 SAP INTERNAL!

 SAP AG 2003, Holger Kunitz/ 23 SAP INTERNAL!

 SAP AG 2003, Holger Kunitz/ 24 SAP INTERNAL!

 SAP AG 2003, Holger Kunitz/ 25 SAP INTERNAL!

 SAP AG 2003, Holger Kunitz/ 26 SAP INTERNAL!

 SAP AG 2003, Holger Kunitz/ 27 SAP INTERNAL!

 SAP AG 2003, Holger Kunitz/ 28 SAP INTERNAL!

 SAP AG 2003, Holger Kunitz/ 29 SAP INTERNAL!

 SAP AG 2003, Holger Kunitz/ 30 SAP INTERNAL!

 SAP AG 2003, Holger Kunitz/ 31 SAP INTERNAL!

 SAP AG 2003, Holger Kunitz/ 32 SAP INTERNAL!

 SAP AG 2003, Holger Kunitz/ 33 SAP INTERNAL!

 SAP AG 2003, Holger Kunitz/ 34 SAP INTERNAL!

 SAP AG 2003, Holger Kunitz/ 35 SAP INTERNAL!

1. Overview – New J2EE based Adapter

2. New J2EE –based Adapter Engine -

3. Technical Aspects of Individual Technical

 SAP AG 2003, Holger Kunitz/ 36 SAP INTERNAL!

 Specify an Adapter Type (File,

 Direction (Sender / Receiver)

 Used to select attributes

 Evaluate conditions require