SAP NetWeaver Process Integration 7.1 1
SAP NetWeaver Process Integration 7.1Advanced Adapter Engine
SAP NetWeaver Regional Implementation GroupSAP NetWeaver Product ManagementDecember 2007
SAP NetWeaver Process Integration 7.1 2
Benefits
After reading this presentation you will be able to:Explain the architecture of the Advanced Adapter Engine (AAE)Describe the benefits, features and configuration of the AAEIdentify valid integration scenarios empowered by the AAE
SAP NetWeaver Process Integration 7.1 3
1. Introduction and Architecture2. Features and Configuration3. Integration Scenarios4. Summary
Agenda
SAP NetWeaver Process Integration 7.1 4
1. Introduction and Architecture2. Features and Configuration3. Integration Scenarios4. Summary
Agenda
SAP NetWeaver Process Integration 7.1 5
From Adapter & Integration Engine toAdvanced AE (AAE)
JEE AAE ABAP IE
anyAdapter
ModuleProcessor
XI Msg.Handler
Msg.Sys.
IDocAdapter
Bus.ProcEngineXIAdapter
Route MapPipeline
DB DBhttp
… to
JEE AE ABAP IE
Integration Server (central AE plus IE)
anyAdapter
ModuleProcessor
XI Msg.Handler
Msg.Sys.
IDocAdapter
Bus.ProcEngineXIAdapter
Route MapPipeline
DB DBhttp
Route Map
Runtime Picture: From…
3-4 persistence steps
2 times rendering / parsingfor http transport incl. userauthentication, processswitch
1 persistence step
The Advanced Adapter Engine (AAE) is an evolution of the Adapter Engine, that is known from formerreleases. It is part of SAP NW PI 7.1 and from a deployments perspective, there is just the deploymentfor an AAE (i.e. there is no deployment option for the AAE OR AE!!). It is just up to the configuration if oneuses the advanced features for a particular scenario, but not an installation/deployment decision! It runson SAP NW JEE5.
Objectives of SAP NW PI 7.10 are High Volume Support and to be the cornerstone of customers' SOAstrategy. The new AAE with its features targets both of them.
The AAE enables for end-to-end message processing without any help from the Integration Engine duringruntime.
It increases message processing speed and throughput by reducing latencies and resource consumption(both memory and processing time).
Local Processing in AAE: Initegration Server (IS) is not involved during runtime (mapping and routing isalso carried out within the AAE)
Classical Processing with AAE: Processing also through the IS
Local processing is probably feasible for existing java-based adapters, and it represents a performanceand resource usage improvement.
The AAE is available centrally (i.e. with installation and instance of IS) and non-centrally.
SAP NetWeaver Process Integration 7.1 6
Local vs. „Classical“ Processing
Sender Adapter Parse
Module Processor
Messaging System Persist
Integration Server Transfer, Persist, Parse
Routing Persist
Mapping Transfer
XI Adapter
Messaging System Transfer, Persist, Parse
Module Processor
Receiver Adapter Render
Sender Adapter Parse
Module Processor
Messaging System Persist
Routing
Mapping
Module Processor
Receiver Adapter Render
Classical via IS Local Processing
Individual Steps for classical processing via IS:
1. The message enters the Sender Adapter where it is parsed.
2. Then it is sent to the module processor.
3. Subsequently it goes to the messaging system, where it is persisted.
4. Later the message is transmitted to the Integration Engine
There, the message is transformed into XML format, replicated, authenticated, parsed again, persistedon IS.
5. Then the message is logically routed to the destinations and persisted again.
6. For each destination the message is mapped (usually executing a JCO call to the java stack).
7. Then the XI adapter starts the transmission back to the Adapter Engine executing all the internal steps itdid before.
8. After that the module processor takes action again.
9. Finally the Message is sent to the adapter and to the target system.
Having the new local processing configured, several steps can be skipped: less persistency steps, lesscommunication steps (AE<->IS, Mapping)
SAP NetWeaver Process Integration 7.1 7
SAP NW PI 7.1 Landscape
JEE Advanced Adapter Engine ABAP IE
Integration Server (central AAE and IS)
anyAdapter
ModuleProcessor
XI Msg.Handler
Msg.Sys.
IDocAdapter
Bus.ProcEngine
XIAdapter
Route MapPipeline
DB DBhttp
IB Directory
IB Repository (ESR)
NWA / Runtime Workbench(RWB)
System Landscape Dir.(SLD) & Exchange Profile
JEE AAEModuleProcessor
XI Msg.Handler
Msg.Sys.
JEE AAEModuleProcessor
XI Msg.Handler
Msg.Sys.
The central and non-central AAE is supported.
On the central instance from a deployment view: each component/package is deployed just once (i.e.there is no messaging system for AAE and AE, no adapter type xyz for AE or AAE). There is just onemonitoring per adapter type independent if it is used with the central IS or in a AAE-local scenario.
From an adapter developments and validations process point of view there is also no difference, i.e. theadapter development needs no case distinction within its coding for local and classical processing.
The decision if the JEE AAE is used solely or if the IS is involved, is a feature of the runtime, that takes acertain configuration into account.
Besides the already existing cache mechanisms originating and well known from former PI-releases thereis an additional cache mechanism involved for mappings.
The known CPA cache is extended with objects resulting from the integrated configuration object, thatalso includes the routing information now and refers to the mapping that is separately distributed for AAE(formerly runtime cache, i.e. RWB => Cache Monitoring => „Integration Server Java Cache“, containingmapping, value mapping and channels for lookup-API).
PI 7.1 also still supports the configuration and runtime of PI 7.0 based non-central adapter engines via PI7.1.
SAP NetWeaver Process Integration 7.1 8
Summary
Local Processing in the Advanced Adapter Engine
Natural evolution of adapter engineProvides mapping, routing to by-pass Integration ServerAdapter to adapter communicationFor sync and async scenarios
SAPSAP
ISIS
Integration Engine& ccBPM Engine
Integration Engine& ccBPM Engine
Adapter EngineAdapter Engine
AB
AP
Java
SOAPSOAP RFCRFC ......
3rd PartyApplication SAPSAP
Customers require high-volume throughput.
The Adapter Engine (central and non-central) evolves to “local processing engine” -> non-disruptiveevolution, can be used like a non-central Adapter Engine.
It provides mapping, routing etc., and allows to by-pass the Integration Server and improves performanceon the IS.
Improved performance/message turnaround for adapter-to-adapter communication
Central configuration and monitoring in Integration Directory and Runtime Workbench
Allows customers to distribute execution of mission-critical processes
Open for further (deployment) scenarios
Usage of local processing within AAE and integrated configuration is optional, i.e. processing via IS is stillanother option
SAP NetWeaver Process Integration 7.1 9
1. Introduction and Architecture2. Features and Configuration3. Integration Scenarios4. Summary
Agenda
SAP NetWeaver Process Integration 7.1 10
Advanced Adapter Engine – Features
Both synchronous and asynchronous messagesSender and receiver adapters located on the same Adapter EngineSupport of decentral Adapter Engine with central configurationand monitoringAvailable for adapter types hosted on the Adapter Engine(IDoc-, http-, XI-, iSpeak- adapters excluded)One to one message mapping (no ABAP based mapping types)Single Static Routing
(i.e. no content based routing or message split yet)
The scope of the AAE:
Supports synchronous and asynchronous messages
Supports non-central Adapter Engines
And supported all java-based adapters already in use, in the future some other adapters will besupported as well.
In the following service packages additional functionality is planned to be added for this same PI 7.1version, for example it is intended to support:
IDoc and Web services
More routing and mapping functionalities
Additional optional persistence steps
Plain-http can be implemented with SOAP-Adapter; XI adapter can be implemented technically on projectbasis with SOAP-Adapter in Axis-mode
iSpeak: scenarios often use IDoc, ccBPM
SAP NetWeaver Process Integration 7.1 11
Advanced Adapter Engine – AdditionalAvailable Features
ACL‘s
Mapping Lookups
Principal Propagation (if supported by the adapter)
Value Mapping, Sequence Mapping
Schema Validation
Header Mapping (if supported by the adapter)
Message Prioritization
Async => Sync-bridge without BPM works.
SAP NetWeaver Process Integration 7.1 12
Directory Configuration: IntegratedConfiguration
New Directory Object: Integrated Configuration Object
Used for configuring local processing within adavanced adapter engine.Therefore the AAE provides routing and mapping services locally.
Object Type used in Directory
ICO
IS-pipeline NOTinvoked
IS-pipelineinvoked
Local Processing is always optional.
SAP NetWeaver Process Integration 7.1 13
Directory Configuration: IntegratedConfiguration
Integrated Configuration Object (ICO)Contains sender- & receiver agreement and interfacedeterminationIs transferred to the CPA-Cache of the individual AAE with areference to the mapping maintained within the interfacedetermination sectionFor each operation in interface determination a separate entryis created in CPA (receiver interface determination)The integrated configuration object is transferred as one singleobject to the AAE.
= ( + )+ +
SAP NetWeaver Process Integration 7.1 14
Details – Directory Configuration
From four configuration entities to one single entity
At configuration time, instead of creating a Sender Agreement, Receiver Determination, InterfaceDetermination and Receiver Agreement, you have to create an “Integrated Configuration” object.
For routing, entering a receiver is optional (e.g. Virtual Receiver for Sender) can be used.
The Integrated Configuration Object is used for local processing in an AAE only!
ACL can be assigned by using a separate section in the Integrated Configuration Object
The “Integrated Configuration” object, divides in three tab strips al the required configurations. They are:
The “Sender Connectivity”: Basically corresponds to the “Sender Agreement”.
The “Routing and Mapping”: It comprises the “Receiver Determination” and “InterfaceMapping” objects.
The “Receiver Connectivity: Basically corresponds to the “Receiver Agreement”.
Upon activation the “Integrated Configuration” is replicated to the AAEs local caches. That means that allthe routings and mappings are executed locally.
SAP NetWeaver Process Integration 7.1 15
Integrated Configuration Objects, Mapping &Cache
Delta Cache Refresh:
CPA-Cache and Mapping Runtime Cacheare updated independently, i.e.
1. Mappings objects peractivation/change are transferred toALL Mapping Runtime Caches of allAdvanced Adapter Engines
2. CPA-Cache-Refresh is usually carriedout after activation/change ofdirectory objects. Objects are justtransferred to the Advanced AdapterEngine where configured to be used
Can be viewed in the Cache Monitoring ofthe RWB. (other monitoring is reused; noSXMB_MONI)
Initial Full Cache Refresh: after the first start of the AAE, a flag is set for a full CPA-Cache refresh; it willbe reset after exactly one SUCCESSFUL full cache refresh; full cache refresh can be always triggeredfrom adapter engine later-on in addition
Process and Results:
CPA-Cache gets all known objects, configured and activated for the particular AAE, inclusively the newroutings and mapping references(!) resulting from the Integrated Configuration Objects
The new mapping runtime cache corresponds to the former „Integration Server Java Cache“ (JavaRuntime Cache) in previous releases but is now integral part of the adapter engine that also results in adecentral deployment option (Mapping Cache in Decentral AAE)
SAP NetWeaver Process Integration 7.1 16
AAE
Advanced Adapter Engine
AnySenderAdapter
ModuleProcessor
ModuleProcessor Any
ReceiverAdapter
XI Msg.Handler
Messag.System
ReceiverDetermination
InterfaceDetermination
MappingRuntime
Mappingprograms
MappingPrograms
Mapping Cache
Integrated Conf.Objects (ICOs)
Inte
grat
edC
onf.
Obj
.
Inte
grat
edC
onf.
Obj
.
Flow ofRuntimeData(messages)
Flow ofConfigurationData
New dev.In AAE
EnhancedFor AAE
Legend:
Cha
nnel
,Se
nder
Agr
eem
ent
Cha
nnel
,R
ecei
ver A
gree
men
t
Directory Configuration („CPA Cache“)
Directory Channels,Agreements
Mappingprograms
IntegratedConfiguration
Kept
Compatible
AE vs. AAE!
Kept
Compatible
AE vs. AAE!
Check for ICO
„classic AE“(http to IS)
SAP NetWeaver Process Integration 7.1 17
Message Prioritization
Msg.System
Adapter-spec.queues
6.40 / 7.00 Message Processingwithout prioritization
In previous releases we have adapter-specific queues. The number of maximum threads could beconfigured per direction (sender, receiver), server node and adapter type with the help of the VisualAdministrator.
SAP NetWeaver Process Integration 7.1 18
Message Prioritization
- Outline: „Works as inABAP IS“
- Weighted msg. Deliveryfor async. Messages
- Probability high / normal /low: 75:20:5
- Configuration in RWB:
high
normal
low
Remarks:- Message Prioritization is designed to avoid that ‚prio high‘ messages
get stuck due to a backlog of other messages on the same node- To ‚see it working‘ at all you need a backlog in the messaging system- To see the expected ratio in message delivery you need in addition
comparable fast backends
Msg.System
Dispatcher Adapter-spec.queuesnew
7.10 Message Processingwith prioritization
Message Prioritization is designed to avoid that ‚prio high‘ messages get stuck due to a backlog of othermessages on the same node.
To ‚see it working‘ at all you need a backlog in the messaging system.
To see the expected ratio in message delivery you need in addition comparable fast backends.
SAP NetWeaver Process Integration 7.1 19
Message Prioritization in AAE – Configuration
Rules within Component Monitoringwith 3 different categories (high, low,normal)per Sender/Receiver Party/Component,Interface, Namespace
Corresponding to properties„messaging.prioritization.high“,„messaging.prioritization.low“and „messaging.prioritization.normal“ of„XPI Service Messaging System“ thatcan be set per server node (onlinemodifiable)
All QoS supported (EOIO serial perscenario)
Prioritization during runtime takes placein principle whenever for a givenadapter type and at a given moment oftime all worker threads are occupied
View Dispatcher Queue: RWB ->Component Monitoring -> AdapterEngine -> Status
Prioritization.dispatcherThreadCount: by default equal 1; measurements show no significant performanceincrease if this parameter is changed; one dispatcher per server node
Maintain values in percent but this is just a rough estimation (i.e. percent of number of messages; if amessage is processed, there is a certain probablilty that this is a high/medium/ low priority message inaccordance with the configuration; default: 75/5/20%)
Most specific configuration is used
If nothing is configured for a certain scenario: priority medium is assigned
If for one individual adapter type all the worker threads are occupied (at a given node), prioritization takesplace
Dispatcher Queue can be monitored: RWB => Component Monitoring => Adapter Engine => Status
SAP NetWeaver Process Integration 7.1 20
Message Prioritization – Sender via IS
C1
C2
C3
C4
QA1
QA2
C1
C2
C3
C4
QA1
QA2
Persistency
PD
PDPD = PrioritizationDispatcher
C = Communication Channel
A = Sender Adapter Type
Q = Queue (per Adapter Type)
Node 1 Node 1
Node 2 Node 2
Appl.Thread
A1
A2
A1
A2
The picture is valid for all QoS; to be more exact: 4 queues per adapter type (sync/async,sender/receiver); for all adapters even with own handler
Performance depends also very much on the adapter‘s implementation (session/connection pooling,multihread etc.)
Number of worker threads is configured per adapter type
7.0 Queue Separation: You can configure the max worker count values according to your specific
needs, using the "messaging.connectionDefinition" property of the "SAP
XI AF Core" service. Using the "name=global" entry some global template
settings are defined. For each adapter type these defaults can be
individually overwritten, by adding additional configuration entries,
according to the following syntax:
messaging.connectionDefinition=(name=global,...)(name=<
AdapterTypeIdentifier>, Send.maxConsumers=<a>, Recv.maxConsumers=<b>,
Call.maxConsumers=<c>, Rqst.maxConsumers=<d>)
with <AdapterTypeIdentifier>=<AdapterType>_<Namespace>
(e.g.: File_http://sap.com/xi/XI/System) )
SAP NetWeaver Process Integration 7.1 21
Message Prioritization –Receiver Local Processing or via IS
QA1
QA2
QA1
QA2
PDPD = PrioritizationDispatcher
C = Communication Channel
A = Sender Adapter Type
Q = Queue (per Adapter Type)
Node 1
Node 2
Appl.Thread
C1
C2
C3
C4
PD
Persistency
C1
C2
C3
C4
A1
A1
A2
A2
The picture is valid for all QoS; to be more exact: 4 queues per adapter type (sync/async,sender/receiver)
Number of worker threads is configured per adapter type!
SAP NetWeaver Process Integration 7.1 22
Audit Log Cache
3 Modes: DB, Cache&DB (2000 entries per node), non
Audit Log Memory Cache (stores audit log data in memory;in case of errors the log will be written to database)
Configuration: Service „XPI Service: Messaging System“component name „com.sap.aii.af.ms.svc“
Property : messaging.auditLog.memoryCache default false
Property: messaging.auditLogEnabled default true
Audit Log Memory Cache (stores audit log data in memory, if processing fails audit log will be written todatabase)
Cache in memory: 2000 per node
The services are „Online Modifiable“
Especially for the AAE with local processing mode writing audit logs is relatively expensive
SAP NetWeaver Process Integration 7.1 23
Q & A
Q1: Which adapters are supported?
A1: - All technical adapters running in the Adapter Framework
- No iSpeak-Adapters (RNIF/CIDX), no IDoc/http-Adapter,XI-Adapter
- Third party upon release (no Adapters that require ccBPM)
Q2: Which mapping types are supported within the AAE?
A2: - Message Mapping, Java, XSLT (no ABAP)
Q3: Now, since mapping and routing is carried out on the AAE, can we change thesequence of individual pipeline steps?
A3: - No
Q4: Can the locally processed messages be seen within SXMB_MONI?
A4: - No
Q5: Is there any change/case distinction in developing and testing adapters between aclassic configuration via IS and integrated object configuration within the AdvancedAdapter Engine?
A5: No. Even there does not exist an official/released API that e.g. modules candetect if they run in a classical or Integrated Object mode.
Plain-http can be implemented with the SOAP-Adapter; the XI adapter can be implemented technically onproject basis with SOAP-Adapter in Axis-mode
iSpeak: scenarios often use IDoc, ccBPM
SAP NetWeaver Process Integration 7.1 24
On the Radar – Stay Tuned
Performance Monitoring
Integrated Configuration Objects via Directory API
Message persistence after mapping (optional)
Content Based Routing
Condition in interface determination
Split of any kind (Split-Mapping, multiple receivers)
Multimessage-Mapping/Enhanced Interface Determination
Extended Receiver Determination
IDoc-Adapter/WS-RM Adapter
Improvements of cache mechanism for full cache refresh and mapping cache
Adjustment of Sizing Guide/Quicksizer (planned for URS PI 7.1)
Important Remark: Subject to change at any time withoutprior and further notice!!!
Support of ICO within the Directory Configuration Assistant
Flags „Maintain order at runtime“ (Interface Determination)
Message persistence after mapping (optional): SOX compliance
SAP NetWeaver Process Integration 7.1 25
1. Introduction and Architecture2. Features and Configuration3. Integration Scenarios4. Summary
Agenda
SAP NetWeaver Process Integration 7.1 26
S1S2
S3
S1 => BPM/ABAP-services
S2/3 => intensivemappingsteps
+ Lower processing times, Speed (improved response times), lesslatency, increased throughput
+ Better support for synchronous scenarios
+ Flexibility in distributing pipeline resources (scenario outsourcing)
+ Dedicated AAE for scenarios with high throughput requirements
IS Central
Scenario 1 – Performance and ResourceConsumption
S = Scenario
Even with central AAE there is less resource consumption and lower processing times in average for anindividual message for a certain scenario compared to the same scenario with the „traditionalconfiguration“ via IS
SAP NetWeaver Process Integration 7.1 27
Scenario 2 – Network Constraints
Need for decentral AdapterEngine and limited networkcapacities or firewallrestrictions
S1S2
+ Less communication overhead
+ Large payloads are not transferred across different network domains
S1 => BPM/ABAP-services
S2/3 => intensivemapping steps
IS Central
S = Scenario
SAP NetWeaver Process Integration 7.1 28
Scenario 3 – Connect to IS, PCK, Proxy, AAENatively
S1 S1
S1&S2
S1&S2
- No XI-Protocol or WS-RM
- No PCK-replacement
S1 => BPM/ABAP-services
S2/3 => intensivemapping steps
IS Central
S = Scenario
SAP NetWeaver Process Integration 7.1 29
1. Introduction and Architecture2. Features and Configuration3. Integration Scenarios4. Summary
Agenda
SAP NetWeaver Process Integration 7.1 30
AAE – Preliminary Results PI 7.1
System: 4 x Opteron 2.6 GHzScenario without Mapping and without Packaging for IS;Mapping reduces comparison factor from 10 to 7-8Audit Log Memory Cache enabled for AAE processing
13.6
140.8
0.0
20.0
40.0
60.0
80.0
100.0
120.0
140.0
160.0
Mes
sage
s/s
IS AAE
Throughput - Soap2Soap
Throughput: messages/s; 8Kb Message Size; boost message processing throughput up to 10 times;QoS=EO
Significant performance improvements can be achieved always with local processing (if available) for acertain scenario;
This is valid for all adapter types; huge mapping runtimes, slow networks, slow (receiver) applicationsreduce the throughput and therefore, rated for the overall scenario, also reduce the benefit of localprocessing in terms of overall throughput and response time measurement.
The greatest benefit is recognized for small payloads (comparison: 10k, 50k, 500k) and asynchronousmessages.
SAP NetWeaver Process Integration 7.1 31
Synchronous Processing Response Times -Examples
Response times depend on backend service performance, additional used PI services (e.g.content-based routing, mapping) and underlying hardwareAdvanced Adapter Engine local processing can reduce response times to <100 ms
429
176
79
0
50100150
200250300350
400450
Res
pons
e Ti
me
[ms]
Xeon 2.4 GHz (IS) Opteron 2.6 GHz (IS) Opteron 2.6 GHz(AAE)
Hardware and Deployment Option
Response Time Comparison - Soap2Soap
Details about the sceanrio: end-to-end; QoS=BE with WebService Client AAE Provider(no applicationlogic)
SAP NetWeaver Process Integration 7.1 32
Summary
The Advanced Adapter Engine also allows forend-to-end message processing without invoking the centralABAP-based pipeline of the Integration Server
If local processing is configured, several communication calls andpersistency steps can be eliminated
Reduces resource consumption and latency and increases messagethroughput
Flexibility to deploy and run complete message broker scenarios onindividual instances (decentral AAE); thereforeimproved scalability for large volumes by using autonomousprocessing units
The AAE is an additional feature required for an Enterprise Service Bus architecture.
SAP NetWeaver Process Integration 7.1 33
Copyright 2007 SAP AGAll rights reserved
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changedwithout prior notice.Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.
SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver, Duet, Business ByDesign, ByDesign, PartnerEdge and other SAP products and services mentioned herein as well as theirrespective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other product and service names mentioned andassociated logos displayed are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary.
The information in this document is proprietary to SAP. This document is a preliminary version and not subject to your license agreement or any other agreement with SAP. This documentcontains only intended strategies, developments, and functionalities of the SAP® product and is not intended to be binding upon SAP to any particular course of business, product strategy,and/or development. SAP assumes no responsibility for errors or omissions in this document. SAP does not warrant the accuracy or completeness of the information, text, graphics, links, orother items contained within this material. This document is provided without a warranty of any kind, either express or implied, including but not limited to the implied warranties ofmerchantability, fitness for a particular purpose, or non-infringement.
SAP shall have no liability for damages of any kind including without limitation direct, special, indirect, or consequential damages that may result from the use of these materials. This limitationshall not apply in cases of intent or gross negligence.
The statutory liability for personal injury and defective products is not affected. SAP has no control over the information that you may access through the use of hot links contained in thesematerials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages
Weitergabe und Vervielfältigung dieser Publikation oder von Teilen daraus sind, zu welchem Zweck und in welcher Form auch immer, ohne die ausdrückliche schriftliche Genehmigung durchSAP AG nicht gestattet. In dieser Publikation enthaltene Informationen können ohne vorherige Ankündigung geändert werden.Einige von der SAP AG und deren Vertriebspartnern vertriebene Softwareprodukte können Softwarekomponenten umfassen, die Eigentum anderer Softwarehersteller sind.
SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver, Duet, Business ByDesign, ByDesign, PartnerEdge und andere in diesem Dokument erwähnte SAP-Produkte und Servicessowie die dazugehörigen Logos sind Marken oder eingetragene Marken der SAP AG in Deutschland und in mehreren anderen Ländern weltweit. Alle anderen in diesem Dokument erwähntenNamen von Produkten und Services sowie die damit verbundenen Firmenlogos sind Marken der jeweiligen Unternehmen. Die Angaben im Text sind unverbindlich und dienen lediglich zuInformationszwecken. Produkte können länderspezifische Unterschiede aufweisen.
Die in diesem Dokument enthaltenen Informationen sind Eigentum von SAP. Dieses Dokument ist eine Vorabversion und unterliegt nicht Ihrer Lizenzvereinbarung oder einer anderenVereinbarung mit SAP. Dieses Dokument enthält nur vorgesehene Strategien, Entwicklungen und Funktionen des SAP®-Produkts und ist für SAP nicht bindend, einen bestimmtenGeschäftsweg, eine Produktstrategie bzw. -entwicklung einzuschlagen. SAP übernimmt keine Verantwortung für Fehler oder Auslassungen in diesen Materialien. SAP garantiert nicht dieRichtigkeit oder Vollständigkeit der Informationen, Texte, Grafiken, Links oder anderer in diesen Materialien enthaltenen Elemente. Diese Publikation wird ohne jegliche Gewähr, wederausdrücklich noch stillschweigend, bereitgestellt. Dies gilt u. a., aber nicht ausschließlich, hinsichtlich der Gewährleistung der Marktgängigkeit und der Eignung für einen bestimmten Zwecksowie für die Gewährleistung der Nichtverletzung geltenden Rechts.SAP übernimmt keine Haftung für Schäden jeglicher Art, einschließlich und ohne Einschränkung für direkte, spezielle, indirekte oder Folgeschäden im Zusammenhang mit der Verwendungdieser Unterlagen. Diese Einschränkung gilt nicht bei Vorsatz oder grober Fahrlässigkeit.Die gesetzliche Haftung bei Personenschäden oder die Produkthaftung bleibt unberührt. Die Informationen, auf die Sie möglicherweise über die in diesem Material enthaltenen Hotlinkszugreifen, unterliegen nicht dem Einfluss von SAP, und SAP unterstützt nicht die Nutzung von Internetseiten Dritter durch Sie und gibt keinerlei Gewährleistungen oder Zusagen überInternetseiten Dritter ab.
Alle Rechte vorbehalten.