Session ID: PRTL203

Technical Infrastructures of SAP Enterprise Portal 6.0

Contributing Speaker(s)
Bernhard Steigleider
SAP NW RIG EMEA, SAP AG

Nicholas Holshouser
SAP NW RIG Americas, SAP Labs LLC.

© SAP AG 2004, SAP TechEd / PRTL203 / 2

Learning Objectives

As a result of this presentation, you will be able to:
Describe the architecture of EP 6.0 on Web AS 6.40 and list its components Understand the basic terminology “load-balancing”, “clustering” and “high availability” as it pertains technical infrastructure of EP 6.0 on Web AS 6.40 Know most reasonable technical infrastructures for EP 6.0 on Web AS 6.40 and its components Evaluate the pros and cons for each technical infrastructure Understand how to expand a simple installation into an large high available implementation

© SAP AG 2004, SAP TechEd / PRTL203 / 3

Introduction EP6 on Web AS 6.40 High Availability for EP6 on Web AS 6.40 in General Basic Infrastructures for EP6 on Web AS 6.40 Java Technical Infrastructures for TREX Web Infrastructure Considerations Summary .

40 in General Basic Infrastructures for EP6 on Web AS 6.Introduction EP6 on Web AS 6.40 High Availability for EP6 on Web AS 6.40 Java Technical Infrastructures for TREX Web Infrastructure Considerations Summary .

SAP TechEd / PRTL203 / 6 .Introduction Applications require appropriate technical infrastructure Technical infrastructure must ensure Performance and scalability High availability Security Smooth network integration Low cost of ownership Web AS 6.40 Architecture and Web infrastructure are crucial parts Technical infrastructure depends on the application Consider technical infrastructure at an early stage in a project! © SAP AG 2004.

Outline of an Technical Infrastructure (Example) Browser. etc. SAP TechEd / PRTL203 / 7 Clustered Web AS Database Retrieval & Classification Index Persistence . http/https Outer Firewall Load Balancer Web Server* (ssl) Web AS (PP&CM) Web Server* (ssl) Web Server* (ssl) (ssl) (ssl) Web Infrastructure Inner Firewall TREX Web AS Instance Web AS Instance Web AS Instance Web Server Retrieval & Classification (as part of KM platform) Engines Database Clustered Corporate User Management * Reverse Proxy functionality © SAP AG 2004. PDA.

Deliverables of Technical Infrastructure Design Deliverables of Technical Infrastructure Design: Outline of all machines (and other hardware components) which are necessary to run a certain EP6 portal solution Definition of all necessary software components including the assignments on which machines they are going to be installed and be executed Estimation of the load.40: Web AS Cluster (including Portal Platform. Content Management and Java Unification) Database TREX Web Infrastructure (“The infrastructure between the Client browser an the Portal Servers”) © SAP AG 2004. each software component will cause on a particular machine Determine the sizing of every machine (and other hardware parts) derived from the expected load This comprises the following parts of EP6 on Web AS 6. SAP TechEd / PRTL203 / 8 .

Lecture (1h) © SAP AG 2004. System Landscape “System Landscape” belongs to another story: “System Landscape” focuses on which (logical SAP-) systems are necessary to ensure the quality of a productive system “System Landscape” belongs to the area of Software Logistic “System Landscape”-Information can be stored in SAP System Landscape Directory (SLD). a technical infrastructure needs to be discussed Technical Infrastructure is NOT THE SAME as System Landscape Technical Infrastructure is NOT THE SAME as System Landscape Watch out for these TechED 2004 sessions: Java102: SAP Java Development Infrastructure .Technical Infrastructure vs.Intelligent System Landscape Handling. SAP TechEd / PRTL203 / 9 . An EP6 System can be registered there as well. SLD is heavily used by the SAP NetWeaver Java Development Infrastructure Normally.An Overview. Lecture (2h) LCM208: SAP SLD . a quality assurance or test system (TST) and a productive (PRD) System For each system within a “System Landscape” (e. customers consider to set up one or several development (Consolidation) systems (DEV). PRD).g.

Introduction EP6 on Web AS 6.40 Java Technical Infrastructures for TREX Web Infrastructure Considerations Summary .40 In General Basic Infrastructures for EP6 on Web AS 6.40 High Availability for EP6 on Web AS 6.

you are dealing with Up to EP6/SP2 requires SAP J2EE Engine 6.0 on Web AS 6.0 version.40 (EP6/SP3+)! This session concentrates on SAP EP 6.40 EP 6.40 relies on the clustering capabilities of the Web AS itself.0 on Web AS 6. SAP TechEd / PRTL203 / 11 .0 on Web AS 6.40 – The Support Package matters ! Carefully watch out the EP 6.40. Review SAP note 709354 for restriction regarding DB-Clustering This session concentrates on SAP EP 6.40 (without EP6) and EP6 on Web AS 6.EP 6. Only a few EP6 specifics are left: Check the Product Availability Matrix (PAM) for differences of supported platforms between Web AS 6.0 on Web AS 6.20 Starting with EP6/SP3 requires Web AS 6.40 (EP6/SP3+)! © SAP AG 2004.

40 (AddIn) Web AS 6.40 Java © SAP AG 2004.40 – Which Web AS Stack to use? Web AS 6.0 on Web AS 6.0 on Web AS 6.40 Java !! This session concentrates on Web AS 6.40 (EP6/SP3+) is only installed and executed within the Java Stack of the Web AS 6.40 (AddIn) is supported with NW04/SPS09 onwards (EP6/SP9+).40 Java EP 6. This session concentrates on Web AS 6.40 Java ABAP Stack and Java Stack is installed Java Stack only is installed “Adding” a ABAP Stack onto an “Java only” Installation is currently not possible EP 6.EP 6.40 does not necessarily require an ABAP Stack.40 EP6 on Web AS 6. It is sufficient to install EP6/SP3+ within Web AS 6.40 is shipped in two flavors Web AS 6. SAP TechEd / PRTL203 / 12 .0 on Web AS 6.

40 Add-In Central Instance ICM Java ABAP Components Central Services Instance Java Engine Internet Communication Manager ABAP Instance RDBMS Instance SCS Instance Enqueue Server Message Server Java Dispatcher Server Processes Dispatcher Work Processes Gateway Enqueue Server Message Server SAPCCM4X SDM (*) Database ABAP Schema Java Schema SAP J2EE Engine 6.30/SP4+) IGS (Internet Graphics Server) IGS SAPCCMSR SAPOSCOL Monitoring Tools (SAPCCMSR and SAPOsCol) EP 6.40 (Add-In) Web AS 6.0 on Web AS 6. SAP TechEd / PRTL203 / 13 .Architectural Overview Web AS 6.40 (6.40 is installed and executed solely EP 6.40 is installed and executed solely within the JAVA stack within the JAVA stack © SAP AG 2004.0 on Web AS 6.

Architecture Web AS 6. SAP TechEd / PRTL203 / 14 . broadcasts. exchange of cache content.40 Java: The Building Blocks Central Java Instance: Java Dispatcher Receives client requests and forwards them to the server processes accordingly Web AS 6.40 Java Central Java Instance Java Dispatcher Java Server Processes Java Server Processes Actually process the requests Server Processes hold the session data Central Services Instance Enqueue Server Message Server Central Services Instance: Java Enqueue Service Manages logical locks Ensure server synchronization SDM Database SAPCCMSR SAPOSCOL Java Schema Java Message Service Central service for cluster internal communication. like event notifications. Provides cluster state information to SAP Web Dispatcher © SAP AG 2004. etc.

40 Java Cluster Communication “Star”-Approach Java Node Java Node Java Node Java Node Java Node Java Node Java Node Java Node Java Node Java Node Java Node Java Node Messaging Locking Java Node Central Config DB Java Node Java Node Java Node Improved cluster internal communication with Web AS 6.40 © SAP AG 2004.40 Improved cluster internal communication with Web AS 6.New Cluster Internal Communication Architecture Web AS 6. SAP TechEd / PRTL203 / 15 .20 Java Cluster Communication “Peer to Peer”-Approach (“Fully Connected Ring”) Web AS 6.

Message Service . The message service is aware of all the active Java Instances.Details Definition The message service is a separate program used for communication between the elements of a Java cluster. Usage The message service is responsible for the following tasks in the Java cluster: Notification of events that arise in the cluster. SAP TechEd / PRTL203 / 16 . for example. or when a service is started or stopped. if a cluster node gets lost (through failure or shut-down of the instance). Communication between different services Forwarding of messages and requests to all participants (broadcast) Prepare logon information for the SAP Web Dispatcher Support for message server failover Guaranteed message transmission Exchange of cache information in the cluster © SAP AG 2004.

It manages the lock table in the main memory and receives requests for setting or releasing locks. Proved SAP lock concept is used for this.Enqueue Service . Usage: The Enqueue service has the following tasks: Internally it is used for synchronization within the Java cluster. It maps the logical locks to the database. The Enqueue service processes these requests and manages the lock table with the existing locks. SAP TechEd / PRTL203 / 17 . The applications can lock objects and release locks again. © SAP AG 2004.Details Definition: The Enqueue service is used to manage logical locks. Structure: The Enqueue service runs on the Central Services instance of the Java cluster.

Web AS 6.40 Java Startup Framework - Basics
The Web AS Java is started via …
On Windows platforms: SAP MMC On UNIX platforms: startsap / stopsap scripts

The Java Startup and Control Framework
… is an infrastructure, situated between the OS and the Java VM … is used to start, stop, and monitor the Java Instance(s) … offers aggregated status information about all cluster entities … loads the Java VM and restarts processes, which have died/crashed … comprises the programs Jcontrol, Jlaunch and Jcmon

Important features in regards to Technical Infrastructure:
Bootstrapping process in place to ensure consistency between DB and file system Integration of Java Processes into the SAP instance concept Control and Restart functionality of Java processes (Watchdog) Remote Control of all Java instances in the cluster (start, restart, stop, …) …

© SAP AG 2004, SAP TechEd / PRTL203 / 18

SAP Web AS Java 6.40 – Startup Process in Detail
startsap (UNIX) / SAP Service (Windows)
starts 1 instance of

SAPOsCol Database Instance (if local) Java Message Server Java Enqueue Server
Web AS Java Startup Framework

JControl
• Reads Java instance description from profile and instance.properties • Create Shared Memory Segment holding administrative instance data • Starts/Stops Java VM hosting processes (JLaunch) for each Java Dispatcher, Java Server Process and SDM

JLaunch JLaunch JLaunch (per VM specific properties process) • Reads instances

Reads instances specific properties • • • Parameterizes,specific properties Reads instances loads and hosts Java VM to start the process VM to • • •Parameterizes, loads and hosts Javacreatedstart the process Parameterizes, loads and hosts Java VM to start the process Attachesinstance to SHM segment created by JControl instance to SHM segment by JControl • • Attaches Attaches instance to SHM segment created by JControl

© SAP AG 2004, SAP TechEd / PRTL203 / 19

Architecture of Web AS 6.40 Java Startup Framework

Bootstrapping Bootstrapping process ensures process ensures overall Web AS overall Web AS consistency consistency between file between file system and system and Database Database Automatic restart of died/crashed processes and Automatic restart of died/crashed processes and Automatic termination of hanging processes Automatic termination of hanging processes
© SAP AG 2004, SAP TechEd / PRTL203 / 20

JCMon – Program to Monitor the Startup Framework Command line tool Overview about the instance and process state Local administration menu for the local instance and their processes Cluster administration menu for remote operations © SAP AG 2004. SAP TechEd / PRTL203 / 21 .

“Message server”. within its central database … is based on a new cluster internal communication architecture … has a bootstrapping concept in place. which ensures consistency throughout the Web AS cluster . is started and stopped by using the Java Startup Framework.40 Java … consists of the main building blocks “Dispatcher”.0 … runs on Web AS 6. binaries.Summary: EP6 on Web AS 6. SAP TechEd / PRTL203 / 22 .. and central Database … stores all configuration data.40 Web AS 6.. “Server Processes”.40 beginning with EP6/SP3 . ”Enqueue server”.. is installed and executed in the Java Stack of the Web AS 6.. © SAP AG 2004. which is able To terminate hanging processes To restart died/crashed processes automatically. web applications etc.40 in General EP 6.

Introduction EP6 on Web AS 6.40 In General Basic Infrastructures for EP6 on Web AS 6.40 High Availability for EP6 on Web AS 6.40 Java Technical Infrastructures for TREX Web Infrastructure Considerations Summary .

Basic Types of Clustering Technologies Active/Active Clustering How it works: All nodes are up and running at a certain point of time. (one of) the others takes it over as soon as possible. Important Criteria Keep Alive Implementation Distribution Policies Stickiness Implementation Important Criteria Error Detection / Failover Initiation Failover Duration Fallback Initiation Usage: Achieve High Availability Increase Workload capabilities Usage: Achieve High Availability © SAP AG 2004. If one node goes down. exactly one service is up and running while the others are not started or waiting to take over If a service is corrupted or not working anymore. Active/Passive Clustering How it works: At a certain point of time. the others just take over its tasks. SAP TechEd / PRTL203 / 24 .

Enqueue) Central Instance (Dispatcher. … Dialog Instance (Dispatcher. SAP TechEd / PRTL203 / 25 .Overview Central System Machine 1: Central Service Instance (Message. Enqueue) Central Instance (Dispatcher. 4. SDM. Server) © SAP AG 2004. SDM) (additional Dialog instances with Dispatcher and Servers) Database Distributed System Machine 1: Central Service Instance (Message. SDM) (additional Dialog instances with Dispatcher and Servers) Machine 2: Database Distributed System with Dialog Instances Machine 1: Central Service Instance (Message.Basic Technical Infrastructures . 5. Server. IGS) (additional Dialog instances with Dispatcher and Servers) Machine 2: Database Machine 3. Servers. Enqueue) Central Instance (Dispatcher. Servers.

DB on one host) or a distributed system (SCS. the one and only distribution option for a system is. SAP TechEd / PRTL203 / 26 At least 22Hosts  At least Hosts  . whether you want to install a central system (SCS. CI. SCS instance is always installed on the host of the central Java instance So.Distribution Options: Central vs. Distributed System As of SPS05. CI and DB on different hosts) Complexity is reduced Central System Central System Distributed System Distributed System SAP Web Application Server Central Services Instance Central Java Instance SAP Web AS Java SAP Web Application Server Central Services Instance Central Java Instance SAP Web AS Java Database Instance Java Schema ABAP Schema Database Instance Java Schema ABAP Schema At least 11Host  At least Host  © SAP AG 2004.

Web AS 6.-must be developed accordingly. © SAP AG 2004. onto the Web AS like EP6 must be developed accordingly. SAP TechEd / PRTL203 / 27 .40 Java Central System SAPCCMSR SAPOSCOL Central Java Instance Java Dispatcher Java Server Processes Central Services Instance Enqueue Server Message Server SDM Database Java Schema Note: The Central System may already have several Java server processes. any application deployed onto the Web AS . Whenever more than one server process is running. Note: The Central System may already have several Java server processes.-like EP6 . any application deployed Whenever more than one server process is running.

Web AS 6. SAP TechEd / PRTL203 / 28 .40 Java Distributed System SAPCCMSR SAPOSCOL Central Java Instance Java Dispatcher Java Server Processes Central Services Instance Enqueue Server Message Server Probably the most important Probably the most important infrastructure (starting point) for infrastructure (starting point) for productive EP6 systems based productive EP6 systems based on Web AS 6.40 Java ! ! on Web AS 6.40 Java SDM SAPCCMSR SAPOSCOL Database Java Schema © SAP AG 2004.

Expand an installation by Adding Dialog Instances … Database Instance ABAP Schema Java Schema Dialog Instances (Additional Hosts) do not have Central Services © SAP AG 2004. SAP TechEd / PRTL203 / 29 .

SAP TechEd / PRTL203 / 30 .… And Introducing an External Load Balancer © SAP AG 2004.

Note.Web AS 6.40 Java Central System with Dialog Instances SAPCCMSR SAPOSCOL Central Java Instance Java Dispatcher Java Server Server Server Process Process Process Java Central Services Instance Enqueue Server Message Server Java Dialog Instance Java Dispatcher Java Server Server Server Process Process Process Java Java Dialog Instance Java Dispatcher Java Server Server Server Process Process Process Java SDM Database Java Schema This setup can be chosen: This setup can be chosen: • • To make use of plenty machine resources (Scale-In approach) To make use of plenty machine resources (Scale-In approach) • • When the customer doesn’t want to allow end users to access the Central Java Instance When the customer doesn’t want to allow end users to access the Central Java Instance while nevertheless want to run them on the same machine. that the CI then would most probably would run one server process only. that the CI then would most probably would run one server process only. while nevertheless want to run them on the same machine. SAP TechEd / PRTL203 / 31 . • • Load Balancing is necessary to distribute the requests between the different Java Load Balancing is necessary to distribute the requests between the different Java Dispatchers accordingly Dispatchers accordingly © SAP AG 2004. Note.

Web AS 6.40 Java Cluster on Several Hosts SAPCCMSR SAPOSCOL SAPCCMSR SAPOSCOL SAPCCMSR SAPOSCOL Central Java Instance Java Dispatcher Java Server Processes Central Services Instance Enqueue Server Message Server Java Dialog Instance Java Dispatcher Java Server Processes Java Dialog Instance Java Dispatcher Java Server Processes SDM SAPCCMSR SAPOSCOL Database Java Schema Straight forward “Scale-Out” Cluster ! ! Straight forward “Scale-Out” Cluster © SAP AG 2004. SAP TechEd / PRTL203 / 32 .

SAP TechEd / PRTL203 / 33 .40 Starting Point of any installation is either a Central or a Distributed installation Scaling up EP 6 on Web AS 6.40 © SAP AG 2004. SAP Web Dispatcher) is necessary “Scale-In” as well as “Scale-Out” approaches can be setup with EP6 on Web AS 6.Summary: Basic Infrastructures for EP6 on Web AS 6. a load balancing solution (e.g.40 can be achieved by adding Server Processes or Dialog Instances As soon as a Dialog Instance is added to an installation.

40 High Availability for EP6 on Web AS 6.Introduction EP6 on Web AS 6.40 In General Basic Infrastructures for EP6 on Web AS 6.40 Java Technical Infrastructures for TREX Web Infrastructure Considerations Summary See also TechED 2004 session CI205 High Availability for SAP Solutions See also TechED 2004 session CI205 High Availability for SAP Solutions .

Updates. etc. etc.Preface to High Availability (1) High Availability is the requirement to maximize system availability from an end-users point of view. From a technical infrastructure point of view. Implement disaster recovery scenarios to minimize impacts of disasters … improved Service Level Agreements! Having a highly available Technical Infrastructure in place is crucial in order to reduce “unplanned downtimes” which can be caused by hardware crashes. the architectural and technical single point of failures (SPOF) need to be identified and secured in an appropriate manner. SAP TechEd / PRTL203 / 35 . Patches. application failures/crashes. High Availability comprises much more than just a “Highly Available” Technical Infrastructure: Reducing planned downtimes for Backup. operational mistakes. © SAP AG 2004.

SAP TechEd / PRTL203 / 36 .High Availability from an Infrastructure Point of View Client Load Balancer No Single No Single Point of Point of Failure !! Failure Portal 1 Portal 2 Portal 3 Portal 4 Clustered DB Load Balanced LDAP Synchronization Cluster Database 1 DB Files Cluster Database 2 LDAP Server 1 LDAP Server 2 © SAP AG 2004.

SAP TechEd / PRTL203 / 37 . which also offer specific consulting and support.Preface to High Availability (2) High Availability solutions are heavily platform dependent and often rely on third party solutions like Microsoft Cluster Service (MSCS) SUN Cluster HP Service Guard. HP Service Insight Manager Veritas Cluster Server ORACLE Failsafe. © SAP AG 2004. ORACLE Real-time Application Server … Not covered within this presentation: Aspects of hardware internal high availability measurements Highly available storage solutions Details about highly available load balancer solutions High Availability solutions are offered by Hardware vendors.

Central Database Besides these architectural SPOF. the central file share (“/sapmnt/. Central Services 3. represents also SPOF from technical (installation) point of view. © SAP AG 2004.”) Besides these architectural SPOF.”) represents also aaSPOF from aatechnical (installation) point of view.. Load balancer and other Web Infrastructure Components 2. the central file share (“/sapmnt/.. SAP TechEd / PRTL203 / 38 .40: Architectural Single Points of Failure 1...Web AS 6.

SAP TechEd / PRTL203 / 39 .Possibilities to Secure the Single Point of Failures Single Point of Failure Central Database Technical Possibilities to eliminate the SPOF Switch-over solutions See SAP notes 709354 and 711093 Automatic restart of MSG and ENQ server Setup separate SCS environment (planned for NW04/SR1) most probably within a switch-over environment Setup a Replicated Enqueue Server Central Services Central File share Cluster file share by switch-over solution NFS file share Highly available file system (Hardware based highly available Storage Solution) © SAP AG 2004.

SAP TechEd / PRTL203 / 40 Java Schema .Web AS Cluster with Clustered Database Cluster Group for Database Database Switch Over solution for Central Database © SAP AG 2004.

40 EP 6.40 EP 6.0 Web AS 6.0 Web AS 6.0 MSCS Cluster Oracle Failsafe Failover ORACLE Installation ORA Instance 1a Java Heartbeat Oracle Failsafe ORACLE Installation ORA Instance 1b Java Server 1 Server 2 Database Files © SAP AG 2004.Example: ORACLE Failsafe for ORACLE 9i / Windows Web AS 6. SAP TechEd / PRTL203 / 41 .40 EP 6.

40 EP 6.0 DB Server 1 ORACLE Installation ORA Instance 1 Java Redo logs Failover DB Server 2 ORACLE Installation ORA Instance 2 Java Data Files Archive Log Mode Permanent Recovery Data Files © SAP AG 2004. SAP TechEd / PRTL203 / 42 .40 EP 6.0 Web AS 6.0 Web AS 6.Example: ORACLE 9i Hot Standby Server Web AS 6.40 EP 6.

microsoft.aspx?scid=kb.en-us. SAP TechEd / PRTL203 / 43 .Database Clustering for EP6 on Web AS 6.40 Known limitations of SAP NetWeaver SPS05 (as of Sep 30th.40 Switch-Over Setup for Web AS 6. 2004): SAP note 709354: Release Restrictions for SAP EP 6.40 (without EP6) released with SAP approval only Known restriction for MSCS & NLB: MSCS for DB failover and NLB for load balancing on the same host is not supported by Microsoft http://support.40 DB-Cluster for EP6 will not be supported in NW ’04 Technical Feasibility for switchover solutions to be done No support of active/active DB-clustering solutions For ORACLE RAC Details please review SAP Note 527843) Real-time collaboration (RTC) does not work in a cluster failover situation (planned for NW04/SPS11) SAP note 711093: Release Restriction Note for Web AS 6.0 on Web AS 6.235305 © SAP AG 2004.com/default.

Automatic Restart of Central Services SAPCCMSR SAPOSCOL SAPCCMSR SAPOSCOL SAPCCMSR SAPOSCOL Central Java Instance Java Dispatcher Java Server Processes Central Services Instance Enqueue Server Message Server Java Dialog Instance Java Dispatcher Java Server Processes Java Dialog Instance Java Dispatcher Java Server Processes SDM Restarting the Message and Enqueue Restarting the Message and Enqueue Server maximizes their availability Server maximizes their availability SAP Notes 729945 and 768727 SAP Notes 729945 and 768727 SAPCCMSR SAPOSCOL Database Java Schema © SAP AG 2004. SAP TechEd / PRTL203 / 44 .

Failover for SAP Central Instance One active lock table ! ! One active lock table Enqueue Server Message Server Enqueue Server Message Server Database Processes Database Processes ENQ and MSG Server are separately installed (planned for NW04/SR1) within a switch over environment Database Java Schema © SAP AG 2004. SAP TechEd / PRTL203 / 45 .

SAP TechEd / PRTL203 / 46 Database Processes Database Processes Database Java Schema . the restarted ENQ server finds all locks in the Shared Memory Segment of the locks in the Shared Memory Segment of the failover machine automatically. If the ENQ Service fails from one machine to If the ENQ Service fails from one machine to another. are lost. thus no locks failover machine automatically. thus no locks are lost. the restarted ENQ server finds all another. © SAP AG 2004.Failover With Standalone Enqueue Server Two active lock tables Two active lock tables Replicating Standalone Enqueue Server Replicating Standalone Enqueue Server Rep ENQ Server Message Server Rep ENQ Server Message Server The Standalone ENQ server writes the locks The Standalone ENQ server writes the locks into two shared memory segments in parallel. into two shared memory segments in parallel.

the Database and the central file share “/sapmnt/…” must be considered as single points of failure All SPOF can be secured in an appropriate manner.sap. the Message Server. SAP TechEd / PRTL203 / 47 .com/ha © SAP AG 2004. the Enqueue Server. thus enabling High Available Solutions Please check SAP Notes and contact your Hardware Partner for known issues and limitations for HA solutions Additional information can be found at http://service. which also offer implementation and support for their solutions From an Technical Infrastructure point of view.40 High Availability Solutions are offered by Hardware Partners.Summary: High Availability for EP6 on Web AS 6.

40 High Availability for EP6 on Web AS 6.40 Java Technical Infrastructures for TREX Web Infrastructure Considerations Summary .40 In General Basic Infrastructures for EP6 on Web AS 6.Introduction EP6 on Web AS 6.

TREX General Architecture © SAP AG 2004. SAP TechEd / PRTL203 / 49 .

SAP TechEd / PRTL203 / 50 .Small Distributed TREX System (Example) © SAP AG 2004.

“How To Scale TREX” available “How To Scale TREX” available http://service. SAP TechEd / PRTL203 / 51 .High Available TREX System (Example) TREX uses its own technologies to avoid TREX uses its own technologies to avoid Single Point of Failure.sap.com/netweaver © SAP AG 2004.sap.com/netweaver http://service. Single Point of Failure.

sap.Summary: Technical Infrastructures for TREX TREX scales within all its sub components TREX uses its own technologies to avoid Single Point of Failure. SAP TechEd / PRTL203 / 52 . Additional information can be found at http://service.com/EP60HowToGuides © SAP AG 2004.

40 In General Basic Infrastructures for EP6 on Web AS 6.40 High Availability for EP6 on Web AS 6.Introduction EP6 on Web AS 6.40 Java Technical Infrastructures for TREX Web Infrastructure Considerations Summary .

SAP TechEd / PRTL203 / 54 . Influencing factors: Costs Performance Robustness and high availability Ease of configuration and operation (TCO) Integration into existing infrastructure and security policy Implementation of session Stickiness Session ID (Cookie or URL) IP address of client Cookies inserted into the data stream by load balancer © SAP AG 2004.40 EP6 requires session stickiness because it is a stateful application.Web Infrastructure “The infrastructure between the Client (browser) an the Portal Servers” Requirements of EP6 on Web AS 6.

Web Infrastructure Requirements of EP6 on Web AS 6. Entrust Get Access.40 Influencing factors (continued): Perhaps EAM Authentication necessary. SAP TechEd / PRTL203 / 55 . like Netegrity Siteminder. etc … Perhaps Security considerations requires a DMZ network architecture Perhaps SSL Accelerators and https-Termination are required Where to is SSL decrypted and encrypted? How is session stickiness implemented then? SSL Accelerators needed/required? Etc… Which Load Balancing solution is in place or preferred? SAP Web Dispatcher or external load balancing solution? Client side or Server Side Load-Balancing? Functional Load-Balancing required? Etc … Just some examples to get an idea … Just some examples to get an idea … © SAP AG 2004.

company.g.g.Client-Side Load Balancing by Web AS Message Server 2 e. myportal1.com:500?? 2 1 e.company. © SAP AG 2004.com:50100 DI EP6 DI EP6 DI EP6 1 myportal.company.company.com:500?? DI EP6 CI EP6 Can be implemented without any additional effort by launching the MSG-Server URL. SAP TechEd / PRTL203 / 56 . myportal3.com:50100 myportal.

One Level Load Balancing LB Level 1 DI EP6 DI EP6 DI EP6 LB LB DI EP6 CI EP6 e. SAP TechEd / PRTL203 / 57 .g. SAP Web Dispatcher © SAP AG 2004.

URLs DI (ESS) ESS.g.URLs LB LB EP6-URLs EP6-URLs DI (EP6) DI (EP6) CI EP6 e.One Level (functional) Load Balancing LB Level 1 DI (ESS) ESS. SAP Web Dispatcher with respective Login groups © SAP AG 2004. SAP TechEd / PRTL203 / 58 .

One Level Load Balancing with Reverse Proxy Rev Proxy DI EP6 DI EP6 DI EP6 LB Level 1 Rev Proxy Rev Proxy LB LB Rev Proxy DI EP6 CI EP6 Firewall Firewall e. External load balancing solution and reverse proxy © SAP AG 2004. SAP TechEd / PRTL203 / 59 .g.

Two Level Load Balancing with Reverse Proxy DI EP6 LB Level 1 Rev Proxy LB Level 2 DI EP6 DI EP6 LB 1 LB1 Rev Proxy LB 2 LB2 Rev Proxy DI EP6 CI EP6 Firewall Firewall e. External load balancing solution on LB level 1.g. SAP TechEd / PRTL203 / 60 . Reverse proxy SAP Web Dispatcher on LB level 2 © SAP AG 2004.

SAP TechEd / PRTL203 / 61 .Several Web Infrastructures in front of the Web AS Firewall LB Level 1 Rev Proxy Rev Proxy Rev Proxy Firewall DI EP6 DI EP6 DI EP6 Internet Internet LB LB11 LB 2 LB2 DI EP6 CI EP6 Intranet Intranet Internet-User Intranet-User © SAP AG 2004.

0 on Web AS 6. SAP TechEd / PRTL203 / 62 .Summary: Web Infrastructure EP 6.40 installation Additional information can be found at http://service.sap.com/ti © SAP AG 2004.40 requires Session Stickiness Web Infrastructure should be considered already in early project phases SAP Web Dispatcher as well as Reverse Proxies and external load balancing solutions can be used to build the Web Infrastructure Several different Web Infrastructures can be set up in front of one EP6 on Web AS 6.

Introduction EP6 on Web AS 6.40 In General Basic Infrastructures for EP6 on Web AS 6.40 Java Technical Infrastructures for TREX Web Infrastructure Considerations Summary .40 High Availability for EP6 on Web AS 6.

0 on Web AS 6.40 and its components Evaluate the pros and cons for each technical infrastructure Understand how to expand a simple installation into an large high available implementation © SAP AG 2004.40 Know most reasonable technical infrastructures for EP 6. “clustering” and “high availability” as it pertains technical infrastructure of EP 6. SAP TechEd / PRTL203 / 64 .Summary You are now able to: Describe the architecture of EP 6.0 on Web AS 6.0 on Web AS 6.40 and list its components Understand the basic terminology “load-balancing”.

40 Java 676073: MSCS Installation for SAP Web AS 6.Interesting SAP Notes SAP Notes 709354: Release Restrictions for SAP EP 6. SAP TechEd / PRTL203 / 65 .40 527843: FAQ: Oracle Real Application Cluster (RAC) 757692: Changing Hostname on Web AS 6.40 711093: Release Restriction Note for Web AS 6.40 524816: Standalone Enqueue Server 729945: Auto-restart function for processes in sapstartsrv 768727: Automatic process restart function in sapstart © SAP AG 2004.40 on Windows 728879: MaxDB: MSCS installation based on Web AS 6.0 on Web AS 6.

sdn.help.sap.com/netweaver Related SAP Education Training Opportunities http://www.Intelligent System Landscape Handling.sap.sap.com … ..sap.sap.An Overview. … … Developer Areas Enterprise Portal EP Technical Consulting Forums Enterprise Portal EP Implementation Forums Web Application Server Web AS General SAP Customer Services Network: www. Lecture (1h) High Availability for SAP Solutions.An Overview.com/services/ NetWeaver 04 Documentation at www.Further Information Public Web: SAP’s Web Site www. SAP TechEd / PRTL203 / 66 .. Lecture (2h) SAP Infrastructure Security.sap. Lecture (2h) SAP Java Development Infrastructure . Lecture (2h) SAP SLD .com How To Guides available at http://service.com SAP Developer Network: www. Lecture (1h) © SAP AG 2004.com/education/ Related Workshops/Lectures at SAP TechED 2004 Java104: CI205: SCUR201: Java102: LCM208: SAP Web Application Server .

Coming in December.com/ © SAP AG 2004.sap.sdn.SAP Developer Network Look for SAP TechEd ’04 presentations and videos on the SAP Developer Network. http://www. SAP TechEd / PRTL203 / 67 .

Questions? Q&A © SAP AG 2004. SAP TechEd / PRTL203 / 68 .

and do not take the handouts for the following session.Feedback Please complete your session evaluation. Be courteous — deposit your trash. SAP TechEd / PRTL203 / 69 . Thank You ! © SAP AG 2004.

These materials are subject to change without notice. xApps. zSeries. xSeries. DB2 Universal Database. The information contained herein may be changed without prior notice. S/390. © SAP AG 2004.com. UNIX. if any. z/OS. AFP. WinFrame. DB2. Outlook. Nothing herein should be construed as constituting an additional warranty. AIX. All 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. Parallel Sysplex. Inc. SAP. World Wide Web Consortium. and Motif are registered trademarks of the Open Group. and SAP Group shall not be liable for errors or omissions with respect to the materials. XML. ICA. MetaFrame. Program Neighborhood. AS/400. Massachusetts Institute of Technology. JavaScript is a registered trademark of Sun Microsystems. IBM. Sweden. Java is a registered trademark of Sun Microsystems. OS/390. used under license for technology invented and implemented by Netscape. Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors. Oracle is a registered trademark of Oracle Corporation. 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. National product specifications may vary. HTML. SAP TechEd / PRTL203 / 70 .Copyright 2004 SAP AG. MVS/ESA. R/3. and MultiWin are trademarks or registered trademarks of Citrix Systems. OS/2. Inc. WebSphere. X/Open. and Informix are trademarks or registered trademarks of IBM Corporation in the United States and/or other countries. Tivoli. XHTML and W3C are trademarks or registered trademarks of W3C®. Microsoft. without representation or warranty of any kind. xApp. Intelligent Miner.. OS/400. All other product and service names mentioned are the trademarks of their respective companies. pSeries. Inc. OSF/1. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services. Netfinity. iSeries. and PowerPoint are registered trademarks of Microsoft Corporation. mySAP. These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only. Citrix. Data contained in this document serves informational purposes only. mySAP. VideoFrame. MaxDB is a trademark of MySQL AB. Windows.

Sign up to vote on this title
UsefulNot useful