Upload
others
View
0
Download
0
Embed Size (px)
Citation preview
Technical InfrastructureSAP Enterprise Portal 6.0
Bernhard SteigleiderNetweaver RIG, Enterprise PortalSAP AGLecture
only
SAP AG 2003, TechED_Basel / PRTL201_EMEA, Bernhard Steigleider / 2
Learning Objectives
As a result of this workshop, you will be able to:
n Describe EP 6.0 architecture and list its component parts
n Understand the basic terminology “load-balancing”, “clustering” and “high availability” as it regards EP 6.0
n Know most reasonable technical infrastructures for EP 6.0 and its components
n Evaluate the pros and cons for each infrastructure
n Know how to expand a simple EP 6.0 installation into an EP 6.0 cluster
SAP AG 2003, TechED_Basel / PRTL201_EMEA, Bernhard Steigleider / 3
Agenda
Basic Portal Architecture
EP 6.0 Cluster Components
SAP J2EE Engine Clustering
Database Clustering
Content Management Clustering
TRex Clustering
Typical EP6 Technical Infrastructures
Summary
SAP AG 2003, TechED_Basel / PRTL201_EMEA, Bernhard Steigleider / 4
Portal Framework
Connector FrameworkConnectors
Information SourcesDocuments AppsSAP R/3 EIS Databases Web
User Management Engine
Unification
ApplicationUnifiers
Database Unifier
KnowledgeManagement
Collabor-ation
TREX
CM
Portal Runtime
Portal Components Portal Services
Logical Components of EP 6.0
Browser, Devices
User PersistenceStore
PortalDatabase
Backend Systems
SAP Enterprise Portal 6.0
Portal ContentDirectory
PageBuilder
UserManagement
AdminTools
SAP AG 2003, TechED_Basel / PRTL201_EMEA, Bernhard Steigleider / 5
Technical Components of EP 6.0
Java App Server (SAP J2EE engine)
Web Server
Unification
User Persistence Store
Portal
Web Server
Unifier 1
Web Server
Unifier 2
RealtimeCollaboration
Retrieval & Classification
PortalDatabase
Persistence
Applications, Information, Services
Unification Server
TRex Servers
Web Server
Portal Runtime
Connector Framework
Backend Systems
SAP Enterprise Portal 6.0
Browser, Devices
User Management Engine (UME)
Portal Framework
Content Management
SAP AG 2003, TechED_Basel / PRTL201_EMEA, Bernhard Steigleider / 6
User Management (UM) Architecture
Basic user data
Basic group data
User à group assignment
User/group à role assignment
User mapping (for SSO purposes)
User roles (metadata)
Content à role assignment
User’s personalization data
PortalServer
PCD InstanceUM Instance
• LDAP Directory• Database• SAP System
Store portal-specific data
User Persistence
Store
Portal Database
SAP AG 2003, TechED_Basel / PRTL201_EMEA, Bernhard Steigleider / 7
Portal System Landscape
Inner Firewall
Outer Firewall
Browser, PDA, etc.
Web Server*
Web Server*
Web Server*
http/https
Web Server
UnificationServer
Retrieval &Classification
(as part of KM platform)
ClusteredCorporate User
Management
ClusteredPortal
Database
Load Balancer
Web Server
(ssl) (ssl)(ssl) (ssl)
Persistence
Engines
Retrieval & Classification
Index
(ssl)
DMZ
Portal Server(incl. CM)
Portal Server(incl. CM)
Portal Servers(incl. CM)
Dispatcher Dispatcher Dispatcher
* Reverse Proxy functionality
SAP AG 2003, TechED_Basel / PRTL201_EMEA, Bernhard Steigleider / 8
Agenda
Portal Architecture
EP 6.0 Cluster Components
SAP J2EE Engine 6.20 Clustering
Database Clustering
Content Management Clustering
TRex Clustering
Typical EP6 Technical Infrastructures
Summary
SAP AG 2003, TechED_Basel / PRTL201_EMEA, Bernhard Steigleider / 9
Basic Idea of Clustering
Two or more servers are working together in order to act as one logical system („the cluster“). Programs using servicesoffered by the cluster don‘t know which cluster node isactually doing the work.
Two general types of cluster are available :n Active/Active (All nodes work at the same time)n Active/Passive (One works, the other doesn‘t)
In an active/active cluster all nodes are working at the sametime. If one node is down the other servers just take over thetasks.
In an active/passive cluster, if one machine or service iscorrupted or not working anymore, (one of) the othermachine takes over the task as soon as possible.
SAP AG 2003, TechED_Basel / PRTL201_EMEA, Bernhard Steigleider / 10
Active / Active Clustering
Load Balancing
LB Node 1 LB Node 2 LB-Node <n>
Client
Keep Alive ImplementationDistribution Policies
Stickyness Implementation
Keep Alive ImplementationDistribution Policies
Stickyness Implementation
Can be used to • achieve High Availability and• scale up the application
Can be used to • achieve High Availability and• scale up the application
SAP AG 2003, TechED_Basel / PRTL201_EMEA, Bernhard Steigleider / 11
Active / Passive Clustering
Cluster-Node 1Shared DiskSAN / NAS Cluster-Node 2
Failover
Error DetectionFailover Initiation
Failover TimeResource Definitions
Fallback Initiation
Error DetectionFailover Initiation
Failover TimeResource Definitions
Fallback Initiation
Can be used to achieve High Availability only
Can be used to achieve High Availability only
SAP AG 2003, TechED_Basel / PRTL201_EMEA, Bernhard Steigleider / 12
High Availability
Client
Load Balancer
Cluster Database 1
DB Files
Clustered DB
Cluster Database 2
Portal 1 Portal 2 Portal 3
No Single Point of Failure !
No Single Point of Failure !
Portal 4
LDAP Server 2
LDAP Server 1
Load Balanced LDAP
Synchronisation
SAP AG 2003, TechED_Basel / PRTL201_EMEA, Bernhard Steigleider / 13
Talking about an “EP 6 Cluster”
n Generally, a cluster only means that several components act as one logical system.
n This means, an EP 6 Cluster is consisting of more than one component (machines), representing one logical portal.
n In a typical EP6 cluster, several components can be “clustered”:
uSAP J2EE Engine including Portal Platform
uContent Management within the Portal Platform
uTRex
uDatabase Repository (ORACLE)
uUnification Server including Unifier Projects
n “Setting up a EP6-Cluster” can therefore describe different technical solutions.
SAP AG 2003, TechED_Basel / PRTL201_EMEA, Bernhard Steigleider / 14
Webserver
Load Balancer
Database (ORACLE)
TRex
Webserver (Trex)
IS, QS, PS, NS
SAP J2EE Engine
CM
Portal PlatformUnfication Server
Webserver(Unification)
Unifier Project
Unification DB (SQL-Server)
Clusterable EP6 Components
HW-Load Balancer Cluster
Webserverclustering
J2EE Clustering
DB Clustering
Unification Clustering
Trex Clustering
Clustering of Unification DB
EP6 Cluster
CM Clustering
SAP AG 2003, TechED_Basel / PRTL201_EMEA, Bernhard Steigleider / 15
Agenda
Portal Architecture
EP 6.0 Cluster Components
SAP J2EE Engine 6.20 Clustering
Database Clustering
Content Management Clustering
TRex Clustering
Typical EP6 Technical Infrastructures
Summary
SAP AG 2003, TechED_Basel / PRTL201_EMEA, Bernhard Steigleider / 16
SAP J2EE 6.20 Cluster Architecture
A SAP J2EE 6.20 clusterconsists of two types of nodes:n A dispatcher node receives
the client requests and dispatches them to the servernode with the lowest load.
n On a server node theapplication logic is executed.
n A cluster may consist of several dispatchers and several servers running on the same or different hosts.
n Each node is running in itsown JVM (process).
Client Client Client
Host 1
AppServer(JVM1)
Host n
Database Server
Persistent Data
Dispatcher(JVM)
R R R R
R R R R
AppServer(JVM x)
AppServer(JVM 1)
AppServer(JVM x)
J2EE 6.20
SAP AG 2003, TechED_Basel / PRTL201_EMEA, Bernhard Steigleider / 17
J2EE Engine 6.20 Cluster Requirements
There are a number of requirements that must be met to configure a SAP J2EE Engine 6.20 cluster.
n There must be at least one dispatcher node; otherwise, no cluster can exist. The order in which the server nodes and the dispatcher node are started is not important; however, several server nodescannot communicate with each other without the presence of a dispatcher.
n All machines on which the dispatcher and server nodes are started must be on the same Local Area Network (LAN). The IP addresses of the hosts can be either static or dynamic.
n All identical services on SAP J2EE Engine 6.20 nodes must be of the same version.
n Typically, all identical services on the nodes in the cluster must be configured the same in relation to external resources.
J2EE 6.20
SAP AG 2003, TechED_Basel / PRTL201_EMEA, Bernhard Steigleider / 18
Simple SAP J2EE Engine Installation (1:1)
Client requests Cluster Internal CommunicationPersistence to be added
Dispatcher
J2EEServerEP 6.0
J2EE 6.20
SAP AG 2003, TechED_Basel / PRTL201_EMEA, Bernhard Steigleider / 19
SAP J2EE (1:n) Cluster Configuration
Dispatcher
J2EEServerEP 6.0
Client requests Cluster Internal CommunicationPersistence to be added
J2EEServer
J2EEServer
J2EEServer
EP 6.0 EP 6.0
EP 6.0
J2EE 6.20
SAP AG 2003, TechED_Basel / PRTL201_EMEA, Bernhard Steigleider / 20
J2EEServerEP 6.0
J2EEServer
J2EEServerEP 6.0 EP 6.0
Dispatcher
J2EEServerEP 6.0
High Available SAP J2EE 6.20 (n:m)
J2EE uses active/active cluster technologies onlyJ2EE uses active/active cluster technologies only
Client requests Cluster Internal CommunicationPersistence to be added
Web Server Web Server
HW-LoadBalancer
J2EE 6.20
J2EEServer
J2EEServer
J2EEServer
EP 6.0 EP 6.0
EP 6.0
Dispatcher
J2EEServerEP 6.0
Each node communicates to each other
node
SAP AG 2003, TechED_Basel / PRTL201_EMEA, Bernhard Steigleider / 21
Dispatcher
J2EEServerEP 6.0
Installer Option:
Portal Platform
Dispatcher
J2EEServerEP 6.0
Installer Option:
Additional Node
Default EP6 Cluster Installation (n:n)
Persistence to be added Load Balancing within localhost onlyCluster internal communication between all nodes
Web Server Web Server
HW-LoadBalancer
J2EE 6.20
SAP AG 2003, TechED_Basel / PRTL201_EMEA, Bernhard Steigleider / 22
Example: SAP J2EE 6.20 Cluster
Dispatcher 1
Server 1 Server 2 Server 3
Dispatcher 2
Server 4 Server 5 Server 6
Dispatcher 3
Server 7 Server 8 Server 9
Server 1 Server 2
Server 3
Load Balancer
J2EE 6.20
SAP AG 2003, TechED_Basel / PRTL201_EMEA, Bernhard Steigleider / 23
J2EEServer
J2EEServer
J2EEServer
EP 6.0 EP 6.0
EP 6.0
Dispatcher
J2EEServer
Web Server
EP 6.0
Clients EMEA
EMEA
No Cluster internal
Communication
Not allowed: Two separated J2EE Clusters
J2EEServerEP 6.0
J2EEServer
J2EEServerEP 6.0 EP 6.0
Web Server
Dispatcher
J2EEServerEP 6.0
Clients US
DB Repository
US
! Not
Pos
sible
!! Not Possible !
All cluster nodes must be connected to
the same J2EE cluster
All cluster nodes must reside in the same
IP Subnet !
J2EE 6.20
See also Technical Infrastructure Guide, pg. 13
SAP AG 2003, TechED_Basel / PRTL201_EMEA, Bernhard Steigleider / 24
Agenda
Portal Architecture
EP 6.0 Cluster Components
SAP J2EE Engine 6.20 Clustering
Database Clustering
Content Management Clustering
TRex Clustering
Typical EP6 Technical Infrastructures
Summary
SAP AG 2003, TechED_Basel / PRTL201_EMEA, Bernhard Steigleider / 25
Database Clustering Technologies
EP6 is able to work with active / passive database cluster technologies, e.g.
n ORACLE Failsafe
n Microsoft SQL Server on Microsoft Cluster Service (MSCS)
SAP AG 2003, TechED_Basel / PRTL201_EMEA, Bernhard Steigleider / 26
Example: ORACLE Failsafe for ORACLE 9i / Windows
ORACLE Installation
ORA Instance 1a
UME
PCD
WCM
WCM_ACL
J2EEServerEP 6.0
J2EEServerEP 6.0
J2EEServerEP 6.0
Database Files
Failover
MSCS Cluster
Heartbeat
Server 1 Server 2
Oracle Failsafe
ORACLE Installation
ORA Instance 1b
UME
PCD
WCM
WCM_ACL
Oracle Failsafe
SAP AG 2003, TechED_Basel / PRTL201_EMEA, Bernhard Steigleider / 27
Agenda
Portal Architecture
EP 6.0 Cluster Components
SAP J2EE Engine 6.20 Clustering
Database Clustering
Content Management Clustering
TRex Clustering
Typical EP6 Technical Infrastructures
Summary
SAP AG 2003, TechED_Basel / PRTL201_EMEA, Bernhard Steigleider / 28
CM Clustering: Overview (I)
n Central configuration store (single point of administration for complete cluster)
n Dedicated servers in the cluster for:
n Crawling
n Subscription
n ICE packaging
n Other scheduled jobs
n Consistent de-validation across the CM cluster
n Cluster installation with hot reload
Content Management includes a solution for EP6 with thefollowing characteristics:
SAP AG 2003, TechED_Basel / PRTL201_EMEA, Bernhard Steigleider / 29
CM Clustering: Overview (II)
Characteristics of the following Scenarios:
n All CMs are using one Database instance
n The data stored in the Database is identical in all CMs
n The ACLs are identical
n There is one central configuration for all CMs
n All CM instances share one …\etc and …\config directory on a file system
n Due to HotReload functionality of CM most of the settings are available in all CMs after saving the changes
SAP AG 2003, TechED_Basel / PRTL201_EMEA, Bernhard Steigleider / 30
Example 1: Content Management Cluster
Shared CM data
R
portal cluster withn portal servers
Client A Client B Client C
Portal Server
R
R
R
CM
CMDataabase
Load Balancer
Portal Server
CM
cm installations for allschedulerd jobs, should notbe used inside the loadbalanced cluster
Shared cmconfiguration
Shared cm configuration thatis used from all cminstances inside or outsidethe cluster
R
R
CM installations for all scheduled jobs, should not be used inside the load balancing cluster
Shared CM configuration that is used from all cm instances inside or outside the cluster
SAP AG 2003, TechED_Basel / PRTL201_EMEA, Bernhard Steigleider / 31
Example 2: Content Management Cluster
Shared CM data
portal cluster
Client A Client B Client C
R
R
R
CMDataabase
Load Balancer
Shared cmconfiguration
Shared cm configuration thatis used from all cminstances inside or outsidethe cluster
RR
Portal Server
CM
Portal Server
CM
Portal Server
CM
Portal Server
CM
Portal Server
CM
Portal Server
CM
CM-ID 1- browse- indexing
RR RR
CM-ID 2- browse- ICE
CM-ID 3- browse- subscr.
CM-ID 4- browse- tbp
CM-ID 5- browse
CM-ID 6- browse
R
Shared CM configuration that is used from all CM instances inside or outside the cluster
SAP AG 2003, TechED_Basel / PRTL201_EMEA, Bernhard Steigleider / 32
Agenda
Portal Architecture
EP 6.0 Cluster Components
SAP J2EE Engine 6.20 Clustering
Database Clustering
Content Management Clustering
TRex Clustering
Typical EP6 Technical Infrastructures
Summary
SAP AG 2003, TechED_Basel / PRTL201_EMEA, Bernhard Steigleider / 33
TRex General Architecture
SAP AG 2003, TechED_Basel / PRTL201_EMEA, Bernhard Steigleider / 34
Small Distributed TRex System
SAP AG 2003, TechED_Basel / PRTL201_EMEA, Bernhard Steigleider / 35
High Available TRex System
SAP AG 2003, TechED_Basel / PRTL201_EMEA, Bernhard Steigleider / 36
Agenda
Portal Architecture
EP 6.0 Cluster Components
SAP J2EE Engine 6.20 Clustering
Database Clustering
Content Management Clustering
TRex Clustering
Typical EP6 Technical Infrastructures
Summary
SAP AG 2003, TechED_Basel / PRTL201_EMEA, Bernhard Steigleider / 37
Overview of Possible Technical Infrastructures
The following typical technical infrastructures are can be setup:
Non-clustered Technical Infrastructures
n Demo/Test Installation (Single Host)
n Dual Host Installationu Portal/DB-Server and TRex-Serveru Portal-Server and DB/TRex-Server
n Triple Host Installation
SAP J2EE Engine Clustering Possibilities
n Several J2EE Server nodes on one machine (Scale-In)
n One J2EE server node on several machines (Scale-Out)
High available Technical Infrastructures
n High available EP6 cluster without DB-Clustering
n High available EP6 cluster with DB-Clustering
n High available EP6 cluster with HA TRex-Architecture
n High available EP6 cluster with DMZ-Architecture
SAP AG 2003, TechED_Basel / PRTL201_EMEA, Bernhard Steigleider / 38
Demo/Test-Installation (Single Host)
Portal Platform (PP) and ContentManagement (CM) are installed in one single J2EE server node.
Also the Database and TRex areinstalled on the same machine.Dispatcher
J2EEServer
PP + CM
Database TRex
SAP AG 2003, TechED_Basel / PRTL201_EMEA, Bernhard Steigleider / 39
TRex
Dual Host (Portal+DB and TRex)
Portal Platform (PP) and Content Management (CM) are installed in one single J2EE server node.
Also the Database is installed on the first machine.
Due to SAP’s strong recommendation to install TRexseparately TRex is installed on a separate box.
Dispatcher
J2EEServer
PP + CM
Database
SAP AG 2003, TechED_Basel / PRTL201_EMEA, Bernhard Steigleider / 40
TRex
Dual Host (Portal- and DB/TRex-Server)
Portal Platform (PP) and Content Management (CM) are installed on one single J2EE server node on the first machine.
TRex is installed on a second machine.
Customer decides to install the DB on the second machine as well e.g. in order to secure the DB-Server behind a firewall.
Dispatcher
J2EEServer
PP + CM
Database
Firewall
SAP AG 2003, TechED_Basel / PRTL201_EMEA, Bernhard Steigleider / 41
TRex
Triple Host Installation
Portal Platform (PP) and Content Management (CM) are installed on one single J2EE server node on the first machine.
TRex is installed on a second machine.
The Database is installed on the third machine.
Dispatcher
J2EEServer
PP + CM
Database Default recommendationfor productive environments
Default recommendationfor productive environments
SAP AG 2003, TechED_Basel / PRTL201_EMEA, Bernhard Steigleider / 42
Dispatcher
J2EEServer
PP + CM
J2EEServer
J2EEServer
J2EEServer
PP + CM PP + CM
PP + CM
TRex
Several J2EE Server nodes on one machine (Scale-In)
Portal Platform (PP) and Content Management (CM) are installed on several J2EE server nodes on the one machine.
TRex is installed on a second machine.
The Database is installed on the third machine.
DatabaseThis architecture is already
an EP6 Cluster
This architecture is alreadyan EP6 Cluster
SAP AG 2003, TechED_Basel / PRTL201_EMEA, Bernhard Steigleider / 43
Dispatcher
J2EEServer
PP + CM
Dispatcher
J2EEServer
PP + CM
External Loadbalancer
TRex
One J2EE server node on several machines (Scale-Out)
An external loadbalancingdevice (HW or SW Loadbalancer) is needed.
Portal Platform (PP) and Content Management (CM) are installed on one J2EE server node on several machines.
TRex is installed on a separate machine.
The Database is installed on a separate machine.
Database
Dispatcher
J2EEServer
PP + CM
The typical EP5 cluster approach is also possible
with EP6
The typical EP5 cluster approach is also possible
with EP6
SAP AG 2003, TechED_Basel / PRTL201_EMEA, Bernhard Steigleider / 44
Dispatcher
J2EEServer
PP + CM
J2EEServer
J2EEServer
J2EEServer
PP + CM PP + CM
PP + CM
TRex
High available EP6 cluster without DB-Clustering
An external Loadbalancerdevice (SW or HW Loadbalancer) is needed.
Portal Platform (PP) and Content Management (CM) are installed on severalJ2EE server nodes on the several machines.
The Database is installed on a separate machine.
TRex is installed on a separate machine.
Database
Dispatcher
J2EEServer
PP + CM
J2EEServer
J2EEServer
J2EEServer
PP + CM PP + CM
PP + CM
External LoadbalancerExternal Loadbalancer
SAP AG 2003, TechED_Basel / PRTL201_EMEA, Bernhard Steigleider / 45
Dispatcher
J2EEServer
PP + CM
J2EEServer
J2EEServer
J2EEServer
PP + CM PP + CM
PP + CM
TRex
High available EP6 cluster with DB-Clustering
An external Loadbalancerdevice (SW or HW Loadbalancer) is needed.
Portal Platform (PP) and Content Management (CM) are installed on severalJ2EE server nodes on the several machines.
DB-Clustering is enabled in an active/passive mode.
TRex is installed on a separate machine.
Active/Passive Cluster Service
Shared deviceSAN/NAS …
Dispatcher
J2EEServer
PP + CM
J2EEServer
J2EEServer
J2EEServer
PP + CM PP + CM
PP + CM
External Loadbalancer
Database Database
External Loadbalancer
SAP AG 2003, TechED_Basel / PRTL201_EMEA, Bernhard Steigleider / 46
Dispatcher
J2EEServer
PP + CM
J2EEServer
J2EEServer
J2EEServer
PP + CM PP + CM
PP + CM
TRex
High available EP6 cluster with HA TRex-Architecture
An external Loadbalancerdevice (SW or HW Loadbalancer) is needed.
Portal Platform (PP) and Content Management (CM) are installed on severalJ2EE server nodes on the several machines.
DB/Clustering is enabled in an active/passive mode.
TRex can be set up in a HA mode as well.
Active/Passive Cluster Service
Shared device
Dispatcher
J2EEServer
PP + CM
J2EEServer
J2EEServer
J2EEServer
PP + CM PP + CM
PP + CM
External Loadbalancer
Database Database
External Loadbalancer
SAP AG 2003, TechED_Basel / PRTL201_EMEA, Bernhard Steigleider / 47
Dispatcher
J2EEServer
PP + CM
J2EEServer
J2EEServer
J2EEServer
PP + CM PP + CM
PP + CM
TRex
High available EP6 cluster with DMZ-Architecture
An external Loadbalancerdevice (SW or HW Loadbalancer) is needed.
Each J2EE Dispatcher needsist own Webserver. A firewallprotects the portalservers.
Portal Platform (PP) and Content Management (CM) are installed on several J2EE server nodes on the severalmachines.
A Firewall protects thedatabase and TRex servers
DB/Clustering is enabled in an active/passive mode.
TRex can be set up in a HA mode as well.
Active/Passive Cluster Service
Shared device
Dispatcher
J2EEServer
PP + CM
J2EEServer
J2EEServer
J2EEServer
PP + CM PP + CM
PP + CM
External Loadbalancer
Database Database
WEB-ServerISAPI/RevProxy
WEB-ServerISAPI/RevProxy
External Loadbalancer
SAP AG 2003, TechED_Basel / PRTL201_EMEA, Bernhard Steigleider / 48
Summary
You are now able to:
n Describe EP 6.0 architecture and list its component parts
n Understand the basic terminology “load-balancing”, “clustering” and “high availability” as it regards EP 6.0
n Know most reasonable technical infrastructures for EP 6.0 and its components
n Evaluate the pros and cons for each infrastructure
n Know how to expand a simple EP 6.0 installation into an EP 6.0 cluster
SAP AG 2003, TechED_Basel / PRTL201_EMEA, Bernhard Steigleider / 49
Further Information
è Public Web:www.sap.comè solutionsè mySAP Enterprise Portal
SAP Customer Services Network: http://www.sap.com/services/SAP Service Marketplace: http://service.sap.com/epSAP Help Portal: http://help.sap.com
Technical Infrastructure Guide for EP 6.0 (Standard Documentation)How To use MSCS Cluster Service for Enterprise Portal 5.0SAP J2EE 6.20 Documentation
è Related SAP Education Training Opportunitieshttp://www.sap.com/education/RTEP1W, EP 6.0 Portal WorkshopTTEP01, mySAP Enterprise Portal Configuration (EP 5.0 SP5)
è Consulting ContactRoy Wood, VP SAP NetWeaver Consulting Practice ([email protected])
SAP AG 2003, TechED_Basel / PRTL201_EMEA, Bernhard Steigleider / 50
Q&A
Questions?
SAP AG 2003, TechED_Basel / PRTL201_EMEA, Bernhard Steigleider / 51
Please complete your session evaluation anddrop it in the box on your way out.
Feedback
Thank You !
The SAP TechEd ’03 Basel Team
SAP AG 2003, TechED_Basel / PRTL201_EMEA, Bernhard Steigleider / 52
n 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 changed without prior notice.
n Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.
n Microsoft®, WINDOWS®, NT®, EXCEL®, Word®, PowerPoint® and SQL Server® are registered trademarks of Microsoft Corporation.
n IBM®, DB2®, DB2 Universal Database, OS/2®, Parallel Sysplex®, MVS/ESA, AIX®, S/390®, AS/400®, OS/390®, OS/400®, iSeries, pSeries, xSeries, zSeries, z/OS, AFP, Intelligent Miner, WebSphere®, Netfinity®, Tivoli®, Informix and Informix® Dynamic ServerTM are trademarks of IBM Corporation in USA and/or other countries.
n ORACLE® is a registered trademark of ORACLE Corporation.
n UNIX®, X/Open®, OSF/1®, and Motif® are registered trademarks of the Open Group.
n Citrix®, the Citrix logo, ICA®, Program Neighborhood®, MetaFrame®, WinFrame®, VideoFrame®, MultiWin® and other Citrix product names referenced herein are trademarks of Citrix Systems, Inc.
n HTML, DHTML, XML, XHTML are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts Institute of Technology.
n JAVA® is a registered trademark of Sun Microsystems, Inc.
n JAVASCRIPT® is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape.
n MarketSet and Enterprise Buyer are jointly owned trademarks of SAP AG and Commerce One.
n SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver and other SAP products and services mentioned herein as well as their respective 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 are the trademarks of their respective companies.
Copyright 2003 SAP AG. All Rights Reserved