70
Session ID: PRTL203 Technical Infrastructures of SAP Enterprise Portal 6.0

Technical Infrastructures of SAP Enterprise Portal 6.0

Embed Size (px)

Citation preview

Page 1: Technical Infrastructures of SAP Enterprise Portal 6.0

Session ID: PRTL203

Technical Infrastructures of SAP Enterprise Portal 6.0

Page 2: Technical Infrastructures of SAP Enterprise Portal 6.0

© SAP AG 2004, SAP TechEd / PRTL203 / 2

Contributing Speaker(s)

Bernhard SteigleiderSAP NW RIG EMEA, SAP AG

Nicholas HolshouserSAP NW RIG Americas, SAP Labs LLC.

Page 3: Technical Infrastructures of SAP Enterprise Portal 6.0

© SAP AG 2004, SAP TechEd / PRTL203 / 3

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 componentsUnderstand the basic terminology “load-balancing”, “clustering” and “high availability” as it pertains technical infrastructure of EP 6.0 on Web AS 6.40Know most reasonable technical infrastructures for EP 6.0 on Web AS 6.40 and its componentsEvaluate the pros and cons for each technical infrastructureUnderstand how to expand a simple installation into an large high available implementation

Page 4: Technical Infrastructures of SAP Enterprise Portal 6.0

Introduction

Basic Infrastructures for EP6 on Web AS 6.40High Availability for EP6 on Web AS 6.40 JavaTechnical Infrastructures for TREX

EP6 on Web AS 6.40 in General

Web Infrastructure ConsiderationsSummary

Page 5: Technical Infrastructures of SAP Enterprise Portal 6.0

Introduction

Basic Infrastructures for EP6 on Web AS 6.40High Availability for EP6 on Web AS 6.40 JavaTechnical Infrastructures for TREX

EP6 on Web AS 6.40 in General

Web Infrastructure ConsiderationsSummary

Page 6: Technical Infrastructures of SAP Enterprise Portal 6.0

© SAP AG 2004, SAP TechEd / PRTL203 / 6

Introduction

Applications require appropriate technical infrastructure

Technical infrastructure must ensurePerformance and scalabilityHigh availabilitySecuritySmooth network integration Low cost of ownership

Technical infrastructure depends on the application

Consider technical infrastructure at an early stage in a project!

Web AS 6.40 Architecture and

Web infrastructure are crucial parts

Page 7: Technical Infrastructures of SAP Enterprise Portal 6.0

© SAP AG 2004, SAP TechEd / PRTL203 / 7

Outline of an Technical Infrastructure (Example)

Outer Firewall

Browser, PDA, etc.

Web Server*

Web Server*

Web Server*

http/https

Clustered Corporate User

Management

Clustered Web AS

Database

Load Balancer

(ssl) (ssl)(ssl) (ssl)

Persistence

EnginesRetrieval &Classification

(as part of KM platform)

Web Server

Retrieval & Classification

Index

(ssl)

WebInfrastructure

* Reverse Proxy functionality

Inner Firewall

Database

TREX

Web AS Instance

Web AS Instance

Web AS Instance

Web AS(PP&CM)

Page 8: Technical Infrastructures of SAP Enterprise Portal 6.0

© SAP AG 2004, SAP TechEd / PRTL203 / 8

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 solutionDefinition of all necessary software components including the assignments on which machines they are going to be installed and be executedEstimation of the load, each software component will cause on a particular machineDetermine 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.40:Web AS Cluster (including Portal Platform, Content Management and Java Unification)DatabaseTREXWeb Infrastructure (“The infrastructure between the Client browser an the Portal Servers”)

Page 9: Technical Infrastructures of SAP Enterprise Portal 6.0

© SAP AG 2004, SAP TechEd / PRTL203 / 9

Technical Infrastructure vs. 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). An EP6 System can be registered there as well.SLD is heavily used by the SAP NetWeaver Java Development Infrastructure Normally, customers consider to set up

one or several development (Consolidation) systems (DEV), a quality assurance or test system (TST) and a productive (PRD) System

For each system within a “System Landscape” (e.g. PRD), a technical infrastructure needs to be discussed

Technical Infrastructure is NOT THE SAME as System LandscapeTechnical Infrastructure is NOT THE SAME as System Landscape

Watch out for these TechED 2004 sessions:Java102: SAP Java Development Infrastructure - An Overview, Lecture (2h)LCM208: SAP SLD - Intelligent System Landscape Handling, Lecture (1h)

Page 10: Technical Infrastructures of SAP Enterprise Portal 6.0

Introduction

Basic Infrastructures for EP6 on Web AS 6.40High Availability for EP6 on Web AS 6.40 JavaTechnical Infrastructures for TREX

EP6 on Web AS 6.40 In General

Web Infrastructure ConsiderationsSummary

Page 11: Technical Infrastructures of SAP Enterprise Portal 6.0

© SAP AG 2004, SAP TechEd / PRTL203 / 11

EP 6.0 on Web AS 6.40 – The Support Package matters !

Carefully watch out the EP 6.0 version, you are dealing withUp to EP6/SP2 requires SAP J2EE Engine 6.20Starting with EP6/SP3 requires Web AS 6.40

EP 6.0 on Web AS 6.40 relies on the clustering capabilities of the Web AS itself. Only a few EP6 specifics are left:

Check the Product Availability Matrix (PAM) for differences of supported platforms between Web AS 6.40 (without EP6) and EP6 on Web AS 6.40.Review SAP note 709354 for restriction regarding DB-Clustering

This session concentrates on SAP EP 6.0 on Web AS 6.40 (EP6/SP3+)!This session concentrates on SAP EP 6.0 on Web AS 6.40 (EP6/SP3+)!

Page 12: Technical Infrastructures of SAP Enterprise Portal 6.0

© SAP AG 2004, SAP TechEd / PRTL203 / 12

EP 6.0 on Web AS 6.40 – Which Web AS Stack to use?

Web AS 6.40 is shipped in two flavorsWeb AS 6.40 (AddIn) ABAP Stack and Java Stack is installedWeb AS 6.40 Java Java Stack only is installed“Adding” a ABAP Stack onto an “Java only” Installation is currently not possible

EP 6.0 on Web AS 6.40 (EP6/SP3+) is only installed and executed within the Java Stack of the Web AS 6.40

EP6 on Web AS 6.40 does not necessarily require an ABAP Stack. It is sufficient to install EP6/SP3+ within Web AS 6.40 JavaEP 6.0 on Web AS 6.40 (AddIn) is supported with NW04/SPS09 onwards (EP6/SP9+).

This session concentrates on Web AS 6.40 Java !This session concentrates on Web AS 6.40 Java !

Page 13: Technical Infrastructures of SAP Enterprise Portal 6.0

© SAP AG 2004, SAP TechEd / PRTL203 / 13

Architectural Overview Web AS 6.40 (Add-In)

Components

Internet Communication Manager

ABAP Instance

RDBMS Instance

SCS Instance

SAP J2EE Engine 6.40 (6.30/SP4+)

IGS (Internet Graphics Server)

Monitoring Tools (SAPCCMSR and SAPOsCol)

Central ServicesInstance

Central Instance

Java

ServerProcesses

JavaDispatcher

WorkProcesses

Dispatcher

SDM

EnqueueServer

Gateway

MessageServer

EnqueueServer

MessageServer

Java Engine

ABAP

ICM

Database(*)

Java Schema

ABAP Schema

IGS

SAPCCM4X

SAPCCMSRSAPOSCOL

Web AS 6.40 Add-In

EP 6.0 on Web AS 6.40 is installed and executed solely within the JAVA stack

EP 6.0 on Web AS 6.40 is installed and executed solely within the JAVA stack

Page 14: Technical Infrastructures of SAP Enterprise Portal 6.0

© SAP AG 2004, SAP TechEd / PRTL203 / 14

Architecture Web AS 6.40 Java: The Building Blocks

Central Java Instance:Java Dispatcher

Receives client requests and forwards them to the server processes accordingly

Java Server ProcessesActually process the requestsServer Processes hold the session data

Central Services Instance:Java Enqueue Service

Manages logical locksEnsure server synchronization

Java Message ServiceCentral service for cluster internal communication, like event notifications, broadcasts, exchange of cache content, etc.Provides cluster state information to SAP Web Dispatcher

Web AS 6.40 Java

Central JavaInstance

Java ServerProcesses

JavaDispatcher

SDM

SAPCCMSRSAPOSCOL

Central ServicesInstance

Enqueue Server

Message Server

Database

Java Schema

Page 15: Technical Infrastructures of SAP Enterprise Portal 6.0

© SAP AG 2004, SAP TechEd / PRTL203 / 15

New Cluster Internal Communication Architecture

JavaNode

JavaNode

JavaNode

JavaNode

JavaNode

JavaNode

JavaNode

JavaNode

JavaNode

JavaNode

JavaNode

JavaNode

JavaNode

JavaNode

JavaNode

JavaNode

MessagingLocking

CentralConfig DB

Web AS 6.20 JavaCluster Communication

Improved cluster internal communication with Web AS 6.40Improved cluster internal communication with Web AS 6.40

Web AS 6.40 JavaCluster Communication

“Peer to Peer”-Approach(“Fully Connected Ring”)

“Star”-Approach

Page 16: Technical Infrastructures of SAP Enterprise Portal 6.0

© SAP AG 2004, SAP TechEd / PRTL203 / 16

Message Service - Details

DefinitionThe message service is a separate program used for communicationbetween the elements of a Java cluster. The message service is aware of all the active Java Instances.

UsageThe message service is responsible for the following tasks in the Java cluster:

Notification of events that arise in the cluster, for example, if a cluster node gets lost (through failure or shut-down of the instance), or when a service is started or stopped.Communication between different servicesForwarding of messages and requests to all participants (broadcast)Prepare logon information for the SAP Web DispatcherSupport for message server failoverGuaranteed message transmissionExchange of cache information in the cluster

Page 17: Technical Infrastructures of SAP Enterprise Portal 6.0

© SAP AG 2004, SAP TechEd / PRTL203 / 17

Enqueue Service - Details

Definition:The Enqueue service is used to manage logical locks. Proved SAP lock concept is used for this.

Usage:The Enqueue service has the following tasks:

Internally it is used for synchronization within the Java cluster.The applications can lock objects and release locks again. The Enqueue service processes these requests and manages the lock table with the existing locks.

Structure:The Enqueue service runs on the Central Services instance of the Java cluster. It manages the lock table in the main memory and receives requests for setting or releasing locks. It maps the logical locks to the database.

Page 18: Technical Infrastructures of SAP Enterprise Portal 6.0

© SAP AG 2004, SAP TechEd / PRTL203 / 18

Web AS 6.40 Java Startup Framework - Basics

The Web AS Java is started via …On Windows platforms: SAP MMCOn 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 systemIntegration of Java Processes into the SAP instance conceptControl and Restart functionality of Java processes (Watchdog)Remote Control of all Java instances in the cluster (start, restart, stop, …)…

Page 19: Technical Infrastructures of SAP Enterprise Portal 6.0

© SAP AG 2004, SAP TechEd / PRTL203 / 19

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

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

Web

AS

Java

St

artu

p Fr

amew

ork

SAP Web AS Java 6.40 – Startup Process in Detail

JLaunch (per VM process)•Reads instances specific properties•Parameterizes, loads and hosts Java VM to start the process•Attaches instance to SHM segment created by JControl

Database Instance (if local)

Java Message Server

Java Enqueue Server

SAPOsCol

star

ts 1

ins

tanc

e of

startsap (UNIX) / SAP Service (Windows)

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

Page 20: Technical Infrastructures of SAP Enterprise Portal 6.0

© SAP AG 2004, SAP TechEd / PRTL203 / 20

Architecture of Web AS 6.40 Java Startup Framework

Automatic restart of died/crashed processes andAutomatic termination of hanging processes

Automatic restart of died/crashed processes andAutomatic termination of hanging processes

Bootstrapping process ensures overall Web AS

consistency between file system and Database

Bootstrapping process ensures overall Web AS

consistency between file system and Database

Page 21: Technical Infrastructures of SAP Enterprise Portal 6.0

© SAP AG 2004, SAP TechEd / PRTL203 / 21

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

Page 22: Technical Infrastructures of SAP Enterprise Portal 6.0

© SAP AG 2004, SAP TechEd / PRTL203 / 22

Summary: EP6 on Web AS 6.40 in General

EP 6.0 … runs on Web AS 6.40 beginning with EP6/SP3... is installed and executed in the Java Stack of the Web AS 6.40

Web AS 6.40 Java… consists of the main building blocks “Dispatcher”, “Server Processes”, “Message server”, ”Enqueue server”, and central Database… stores all configuration data, binaries, web applications etc. 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, which is able

To terminate hanging processes To restart died/crashed processes automatically.

Page 23: Technical Infrastructures of SAP Enterprise Portal 6.0

Introduction

Basic Infrastructures for EP6 on Web AS 6.40High Availability for EP6 on Web AS 6.40 JavaTechnical Infrastructures for TREX

EP6 on Web AS 6.40 In General

Web Infrastructure ConsiderationsSummary

Page 24: Technical Infrastructures of SAP Enterprise Portal 6.0

© SAP AG 2004, SAP TechEd / PRTL203 / 24

Basic Types of Clustering Technologies

Active/Active ClusteringHow it works:

All nodes are up and running at a certain point of time. If one node goes down, the others just take over its tasks.

Important CriteriaKeep Alive ImplementationDistribution PoliciesStickiness Implementation

Usage:Achieve High AvailabilityIncrease Workload capabilities

Active/Passive ClusteringHow it works:

At a certain point of time, exactly one service is up and running while the others are not started or waiting to take overIf a service is corrupted or not working anymore, (one of) the others takes it over as soon as possible.

Important CriteriaError Detection / Failover InitiationFailover DurationFallback Initiation

Usage:Achieve High Availability

Page 25: Technical Infrastructures of SAP Enterprise Portal 6.0

© SAP AG 2004, SAP TechEd / PRTL203 / 25

Central SystemMachine 1:

Central Service Instance (Message, Enqueue)Central Instance (Dispatcher, Servers, SDM)(additional Dialog instances with Dispatcher and Servers)Database

Distributed SystemMachine 1:

Central Service Instance (Message, Enqueue)Central Instance (Dispatcher, Servers, SDM)(additional Dialog instances with Dispatcher and Servers)

Machine 2:Database

Distributed System with Dialog InstancesMachine 1:

Central Service Instance (Message, Enqueue)Central Instance (Dispatcher, Server, SDM, IGS)(additional Dialog instances with Dispatcher and Servers)

Machine 2:Database

Machine 3, 4, 5, …Dialog Instance (Dispatcher, Server)

Basic Technical Infrastructures - Overview

Page 26: Technical Infrastructures of SAP Enterprise Portal 6.0

© SAP AG 2004, SAP TechEd / PRTL203 / 26

Distribution Options: Central vs. Distributed System

As of SPS05, SCS instance is always installed on the host of the central Java instance

So, the one and only distribution option for a system is, whether you want to install a central system (SCS, CI, DB on one host) or a distributed system (SCS, CI and DB on different hosts)

Complexity is reduced

SAP Web Application Server

Database Instance

ABAPSchema

JavaSchema

Database Instance

ABAPSchema

JavaSchema

At least 1 Host At least 1 Host At least 2 Hosts At least 2 Hosts

SAP Web AS Java

Central ServicesInstance

Central Java

Instance

SAP Web Application Server

SAP Web AS Java

Central ServicesInstance

CentralJava

Instance

Central SystemCentral System Distributed SystemDistributed System

Page 27: Technical Infrastructures of SAP Enterprise Portal 6.0

© SAP AG 2004, SAP TechEd / PRTL203 / 27

Web AS 6.40 Java Central System

Central ServicesInstance

Central JavaInstance

Java ServerProcesses

JavaDispatcher

SDM

EnqueueServer

MessageServer

Database

Java Schema

SAPCCMSRSAPOSCOL

Note: The Central System may already have several Java server processes.

Whenever more than one server process is running, any application deployed onto the Web AS - like EP6 - must be developed accordingly.

Note: The Central System may already have several Java server processes.

Whenever more than one server process is running, any application deployed onto the Web AS - like EP6 - must be developed accordingly.

Page 28: Technical Infrastructures of SAP Enterprise Portal 6.0

© SAP AG 2004, SAP TechEd / PRTL203 / 28

Web AS 6.40 Java Distributed System

Central ServicesInstance

Central JavaInstance

Java ServerProcesses

JavaDispatcher

SDM

EnqueueServer

MessageServer

SAPCCMSRSAPOSCOL

Database

Java Schema

SAPCCMSRSAPOSCOL

Probably the most important infrastructure (starting point) for productive EP6 systems based

on Web AS 6.40 Java !

Probably the most important infrastructure (starting point) for productive EP6 systems based

on Web AS 6.40 Java !

Page 29: Technical Infrastructures of SAP Enterprise Portal 6.0

© SAP AG 2004, SAP TechEd / PRTL203 / 29

Expand an installation by Adding Dialog Instances …

Database Instance

Java Schema

ABAP Schema

Dialog Instances (Additional Hosts) do not have Central Services

Page 30: Technical Infrastructures of SAP Enterprise Portal 6.0

© SAP AG 2004, SAP TechEd / PRTL203 / 30

… And Introducing an External Load Balancer

Page 31: Technical Infrastructures of SAP Enterprise Portal 6.0

© SAP AG 2004, SAP TechEd / PRTL203 / 31

Web AS 6.40 Java Central System with Dialog Instances

This setup can be chosen:

• 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

while nevertheless want to run them on the same machine. Note, that the CI then would most probably would run one server process only.

• Load Balancing is necessary to distribute the requests between the different Java Dispatchers accordingly

This setup can be chosen:

• 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

while nevertheless want to run them on the same machine. Note, that the CI then would most probably would run one server process only.

• Load Balancing is necessary to distribute the requests between the different Java Dispatchers accordingly

Database

Java Schema

Central JavaInstance

JavaDispatcher

SDM

SAPCCMSRSAPOSCOL

Java Server

Process

Java Server

Process

Server Process

Java DialogInstance

JavaDispatcher

Java Server

Process

Java Server

Process

Server Process

Java DialogInstance

JavaDispatcher

Java Server

Process

Java Server

Process

Server Process

Central ServicesInstance

Enqueue Server

Message Server

Page 32: Technical Infrastructures of SAP Enterprise Portal 6.0

© SAP AG 2004, SAP TechEd / PRTL203 / 32

Web AS 6.40 Java Cluster on Several Hosts

Database

Java Schema

SAPCCMSRSAPOSCOL

Java DialogInstance

Java ServerProcesses

JavaDispatcher

SAPCCMSRSAPOSCOL

Java DialogInstance

Java ServerProcesses

JavaDispatcher

SAPCCMSRSAPOSCOL

Straight forward “Scale-Out” Cluster !Straight forward “Scale-Out” Cluster !

Central JavaInstance

Java ServerProcesses

JavaDispatcher

SDM

SAPCCMSRSAPOSCOL

Central ServicesInstance

Enqueue Server

Message Server

Page 33: Technical Infrastructures of SAP Enterprise Portal 6.0

© SAP AG 2004, SAP TechEd / PRTL203 / 33

Summary: Basic Infrastructures for EP6 on Web AS 6.40

Starting Point of any installation is either a Central or a Distributed installation

Scaling up EP 6 on Web AS 6.40 can be achieved by adding Server Processes or Dialog Instances

As soon as a Dialog Instance is added to an installation, a loadbalancing solution (e.g. SAP Web Dispatcher) is necessary

“Scale-In” as well as “Scale-Out” approaches can be setup with EP6 on Web AS 6.40

Page 34: Technical Infrastructures of SAP Enterprise Portal 6.0

Introduction

Basic Infrastructures for EP6 on Web AS 6.40High Availability for EP6 on Web AS 6.40 JavaTechnical Infrastructures for TREX

EP6 on Web AS 6.40 In General

Web Infrastructure ConsiderationsSummary

See also TechED 2004 session CI205 High Availability for SAP SolutionsSee also TechED 2004 session CI205 High Availability for SAP Solutions

Page 35: Technical Infrastructures of SAP Enterprise Portal 6.0

© SAP AG 2004, SAP TechEd / PRTL203 / 35

Preface to High Availability (1)

High Availability is the requirement to maximize system availability from an end-users point of view.

High Availability comprises much more than just a “Highly Available” Technical Infrastructure:

Reducing planned downtimes for Backup, Updates, Patches, etc.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, application failures/crashes, operational mistakes, etc.

From a technical infrastructure point of view, the architectural and technical single point of failures (SPOF) need to be identified and secured in an appropriate manner.

Page 36: Technical Infrastructures of SAP Enterprise Portal 6.0

© SAP AG 2004, SAP TechEd / PRTL203 / 36

High Availability from an Infrastructure Point of View

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

Synchronization

Page 37: Technical Infrastructures of SAP Enterprise Portal 6.0

© SAP AG 2004, SAP TechEd / PRTL203 / 37

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 ClusterHP Service Guard, HP Service Insight ManagerVeritas Cluster ServerORACLE Failsafe, ORACLE Real-time Application Server…

Not covered within this presentation:Aspects of hardware internal high availability measurementsHighly available storage solutions Details about highly available load balancer solutions

High Availability solutions are offered by Hardware vendors, which also offer specific consulting and support.

Page 38: Technical Infrastructures of SAP Enterprise Portal 6.0

© SAP AG 2004, SAP TechEd / PRTL203 / 38

Web AS 6.40: Architectural Single Points of Failure

1. Central Services

2. Central Database3. Load balancerand other Web Infrastructure Components

Besides these architectural SPOF, the central file share (“/sapmnt/...”) represents also a SPOF from a technical (installation) point of view.

Besides these architectural SPOF, the central file share (“/sapmnt/...”) represents also a SPOF from a technical (installation) point of view.

Page 39: Technical Infrastructures of SAP Enterprise Portal 6.0

© SAP AG 2004, SAP TechEd / PRTL203 / 39

Possibilities to Secure the Single Point of Failures

Switch-over solutionsSee SAP notes 709354 and 711093

Central Database

Cluster file share by switch-over solution

NFS file share

Highly available file system (Hardware based highly available Storage Solution)

Central File share

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

Technical Possibilities to eliminate the SPOF

Single Point of Failure

Page 40: Technical Infrastructures of SAP Enterprise Portal 6.0

© SAP AG 2004, SAP TechEd / PRTL203 / 40

Web AS Cluster with Clustered Database

Database

Java Schema

Cluster Group for Database

Switch Over solution for Central Database

Page 41: Technical Infrastructures of SAP Enterprise Portal 6.0

© SAP AG 2004, SAP TechEd / PRTL203 / 41

Example: ORACLE Failsafe for ORACLE 9i / Windows

Web AS 6.40

EP 6.0

Web AS 6.40

EP 6.0

Web AS 6.40

EP 6.0

Database Files

Failover

MSCS Cluster

Heartbeat

Server 1

ORACLE Installation

ORA Instance 1a

Java

Oracle Failsafe

Server 2

ORACLE Installation

ORA Instance 1b

Java

Oracle Failsafe

Page 42: Technical Infrastructures of SAP Enterprise Portal 6.0

© SAP AG 2004, SAP TechEd / PRTL203 / 42

DB Server 2DB Server 1

Example: ORACLE 9i Hot Standby Server

Data Files

Web AS6.40

EP 6.0

Web AS6.40

EP 6.0

Web AS6.40

EP 6.0

Redo logs

Archive Log Mode

Permanent Recovery

FailoverORACLE Installation

ORA Instance 1

Java

Data Files

ORACLE Installation

ORA Instance 2

Java

Page 43: Technical Infrastructures of SAP Enterprise Portal 6.0

© SAP AG 2004, SAP TechEd / PRTL203 / 43

Database Clustering for EP6 on Web AS 6.40

Known limitations of SAP NetWeaver SPS05 (as of Sep 30th, 2004):SAP note 709354: Release Restrictions for SAP EP 6.0 on Web AS 6.40

DB-Cluster for EP6 will not be supported in NW ’04 Technical Feasibility for switchover solutions to be doneNo 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.40 Switch-Over Setup for Web AS 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.microsoft.com/default.aspx?scid=kb;en-us;235305

Page 44: Technical Infrastructures of SAP Enterprise Portal 6.0

© SAP AG 2004, SAP TechEd / PRTL203 / 44

Automatic Restart of Central Services

Central JavaInstance

Java ServerProcesses

JavaDispatcher

SDM

SAPCCMSRSAPOSCOL

Java DialogInstance

Java ServerProcesses

JavaDispatcher

SAPCCMSRSAPOSCOL

Java DialogInstance

Java ServerProcesses

JavaDispatcher

SAPCCMSRSAPOSCOL

Central ServicesInstance

Enqueue Server

Message Server

Database

Java Schema

SAPCCMSRSAPOSCOLRestarting the Message and Enqueue

Server maximizes their availability SAP Notes 729945 and 768727

Restarting the Message and Enqueue Server maximizes their availability

SAP Notes 729945 and 768727

Page 45: Technical Infrastructures of SAP Enterprise Portal 6.0

© SAP AG 2004, SAP TechEd / PRTL203 / 45

Failover for SAP Central Instance

Database

Java Schema

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

One active lock table !One active lock table !

Page 46: Technical Infrastructures of SAP Enterprise Portal 6.0

© SAP AG 2004, SAP TechEd / PRTL203 / 46

Failover With Standalone Enqueue Server

Database

Java Schema

Database Processes

Database ProcessesThe Standalone ENQ server writes the locks

into two shared memory segments in parallel.

If the ENQ Service fails from one machine to another, the restarted ENQ server finds all locks in the Shared Memory Segment of the failover machine automatically, thus no locks are lost.

The Standalone ENQ server writes the locks into two shared memory segments in parallel.

If the ENQ Service fails from one machine to another, the restarted ENQ server finds all locks in the Shared Memory Segment of the failover machine automatically, thus no locks are lost.

Rep ENQServer

Message Server

Rep ENQ Server

Message Server

Two active lock tablesTwo active lock tables

Replicating Standalone Enqueue ServerReplicating Standalone Enqueue Server

Page 47: Technical Infrastructures of SAP Enterprise Portal 6.0

© SAP AG 2004, SAP TechEd / PRTL203 / 47

Summary: High Availability for EP6 on Web AS 6.40

High Availability Solutions are offered by Hardware Partners, which also offer implementation and support for their solutions

From an Technical Infrastructure point of view, the Message Server, the Enqueue Server, 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, 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.sap.com/ha

Page 48: Technical Infrastructures of SAP Enterprise Portal 6.0

Introduction

Basic Infrastructures for EP6 on Web AS 6.40High Availability for EP6 on Web AS 6.40 JavaTechnical Infrastructures for TREX

EP6 on Web AS 6.40 In General

Web Infrastructure ConsiderationsSummary

Page 49: Technical Infrastructures of SAP Enterprise Portal 6.0

© SAP AG 2004, SAP TechEd / PRTL203 / 49

TREX General Architecture

Page 50: Technical Infrastructures of SAP Enterprise Portal 6.0

© SAP AG 2004, SAP TechEd / PRTL203 / 50

Small Distributed TREX System (Example)

Page 51: Technical Infrastructures of SAP Enterprise Portal 6.0

© SAP AG 2004, SAP TechEd / PRTL203 / 51

High Available TREX System (Example)

TREX uses its own technologies to avoid Single Point of Failure.

“How To Scale TREX” available http://service.sap.com/netweaver

TREX uses its own technologies to avoid Single Point of Failure.

“How To Scale TREX” available http://service.sap.com/netweaver

Page 52: Technical Infrastructures of SAP Enterprise Portal 6.0

© SAP AG 2004, SAP TechEd / PRTL203 / 52

Summary: Technical Infrastructures for TREX

TREX scales within all its sub components

TREX uses its own technologies to avoid Single Point of Failure.

Additional information can be found at http://service.sap.com/EP60HowToGuides

Page 53: Technical Infrastructures of SAP Enterprise Portal 6.0

Introduction

Basic Infrastructures for EP6 on Web AS 6.40High Availability for EP6 on Web AS 6.40 JavaTechnical Infrastructures for TREX

EP6 on Web AS 6.40 In General

Web Infrastructure ConsiderationsSummary

Page 54: Technical Infrastructures of SAP Enterprise Portal 6.0

© SAP AG 2004, SAP TechEd / PRTL203 / 54

Web Infrastructure

“The infrastructure between the Client (browser) an the Portal Servers”

Requirements of EP6 on Web AS 6.40 EP6 requires session stickiness because it is a stateful application.

Influencing factors:CostsPerformanceRobustness and high availabilityEase of configuration and operation (TCO)Integration into existing infrastructure and security policyImplementation of session Stickiness

Session ID (Cookie or URL)IP address of clientCookies inserted into the data stream by load balancer

Page 55: Technical Infrastructures of SAP Enterprise Portal 6.0

© SAP AG 2004, SAP TechEd / PRTL203 / 55

Web Infrastructure Requirements of EP6 on Web AS 6.40

Influencing factors (continued):Perhaps EAM Authentication necessary, like Netegrity Siteminder, Entrust Get Access, 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 …

Page 56: Technical Infrastructures of SAP Enterprise Portal 6.0

© SAP AG 2004, SAP TechEd / PRTL203 / 56

Client-Side Load Balancing by Web AS Message Server

DIEP6

DIEP6

CIEP6

DIEP6

DIEP6

e.g. myportal1.company.com:501002

myportal.company.com:500??1

myportal.company.com:500??1

e.g. myportal3.company.com:501002

Can be implemented without any additional effort bylaunching the MSG-Server URL.

Page 57: Technical Infrastructures of SAP Enterprise Portal 6.0

© SAP AG 2004, SAP TechEd / PRTL203 / 57

LB

One Level Load Balancing

DIEP6

DIEP6

CIEP6

LB

DIEP6

DIEP6

LB Level 1

e.g. SAP Web Dispatcher

Page 58: Technical Infrastructures of SAP Enterprise Portal 6.0

© SAP AG 2004, SAP TechEd / PRTL203 / 58

LB

One Level (functional) Load Balancing

DI(ESS)

DI(ESS)

DI(EP6)

DI(EP6)

CIEP6

LBEP6-U

RLs

ESS-UR

Ls

ESS- URLs

EP6-URLs

LB Level 1

e.g. SAP Web Dispatcher with respective Login groups

Page 59: Technical Infrastructures of SAP Enterprise Portal 6.0

© SAP AG 2004, SAP TechEd / PRTL203 / 59

LB

One Level Load Balancing with Reverse Proxy

DIEP6

DIEP6

CIEP6

LB

RevProxy

RevProxy

DIEP6

RevProxy

DIEP6

RevProxy

LB Level 1

e.g. External load balancing solution and reverse proxy

Firewall Firewall

Page 60: Technical Infrastructures of SAP Enterprise Portal 6.0

© SAP AG 2004, SAP TechEd / PRTL203 / 60

LB 2LB 1

Two Level Load Balancing with Reverse Proxy

DIEP6

DIEP6

DIEP6

DIEP6

CIEP6

LB1

RevProxy

RevProxy

RevProxy

LB2

LB Level 2LB Level 1

Firewall Firewall

e.g. External load balancing solution on LB level 1, Reverse proxySAP Web Dispatcher on LB level 2

Page 61: Technical Infrastructures of SAP Enterprise Portal 6.0

© SAP AG 2004, SAP TechEd / PRTL203 / 61

IntranetIntranet

InternetInternet

Several Web Infrastructures in front of the Web AS

LB 2

DIEP6

DIEP6

DIEP6

DIEP6

CIEP6

LB2

LB 1LB1

RevProxy

RevProxy

RevProxy

LB Level 1

Firewall Firewall

Internet-User

Intranet-User

Page 62: Technical Infrastructures of SAP Enterprise Portal 6.0

© SAP AG 2004, SAP TechEd / PRTL203 / 62

Summary: Web Infrastructure

EP 6.0 on Web AS 6.40 requires Session Stickiness

Web Infrastructure should be considered already in early projectphases

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.40 installation

Additional information can be found at http://service.sap.com/ti

Page 63: Technical Infrastructures of SAP Enterprise Portal 6.0

Introduction

Basic Infrastructures for EP6 on Web AS 6.40High Availability for EP6 on Web AS 6.40 JavaTechnical Infrastructures for TREX

EP6 on Web AS 6.40 In General

Web Infrastructure ConsiderationsSummary

Page 64: Technical Infrastructures of SAP Enterprise Portal 6.0

© SAP AG 2004, SAP TechEd / PRTL203 / 64

Summary

You are now able to:

Describe the architecture of EP 6.0 on Web AS 6.40 and list its componentsUnderstand the basic terminology “load-balancing”, “clustering” and “high availability” as it pertains technical infrastructure of EP 6.0 on Web AS 6.40Know most reasonable technical infrastructures for EP 6.0 on Web AS 6.40 and its componentsEvaluate the pros and cons for each technical infrastructureUnderstand how to expand a simple installation into an large high available implementation

Page 65: Technical Infrastructures of SAP Enterprise Portal 6.0

© SAP AG 2004, SAP TechEd / PRTL203 / 65

Interesting SAP Notes

SAP Notes709354: Release Restrictions for SAP EP 6.0 on Web AS 6.40 711093: Release Restriction Note for Web AS 6.40 527843: FAQ: Oracle Real Application Cluster (RAC)757692: Changing Hostname on Web AS 6.40 Java676073: MSCS Installation for SAP Web AS 6.40 on Windows 728879: MaxDB: MSCS installation based on Web AS 6.40 524816: Standalone Enqueue Server 729945: Auto-restart function for processes in sapstartsrv768727: Automatic process restart function in sapstart

Page 66: Technical Infrastructures of SAP Enterprise Portal 6.0

© SAP AG 2004, SAP TechEd / PRTL203 / 66

Further Information

Public Web:SAP’s Web Site www.sap.comSAP Developer Network: www.sdn.sap.com …

… Developer Areas Enterprise Portal EP Technical Consulting... Forums Enterprise Portal EP Implementation… Forums Web Application Server Web AS General

SAP Customer Services Network: www.sap.com/services/NetWeaver 04 Documentation at www.help.sap.comHow To Guides available at http://service.sap.com/netweaver

Related Workshops/Lectures at SAP TechED 2004Java104: SAP Web Application Server - An Overview, Lecture (1h)CI205: High Availability for SAP Solutions, Lecture (2h)SCUR201: SAP Infrastructure Security, Lecture (2h)Java102: SAP Java Development Infrastructure - An Overview, Lecture (2h)LCM208: SAP SLD - Intelligent System Landscape Handling, Lecture (1h)

Related SAP Education Training Opportunitieshttp://www.sap.com/education/

Page 67: Technical Infrastructures of SAP Enterprise Portal 6.0

© SAP AG 2004, SAP TechEd / PRTL203 / 67

SAP Developer Network

Look for SAP TechEd ’04 presentations and videos on the SAP Developer Network.

Coming in December.

http://www.sdn.sap.com/

Page 68: Technical Infrastructures of SAP Enterprise Portal 6.0

© SAP AG 2004, SAP TechEd / PRTL203 / 68

Q&A

Questions?

Page 69: Technical Infrastructures of SAP Enterprise Portal 6.0

© SAP AG 2004, SAP TechEd / PRTL203 / 69

Please complete your session evaluation.

Be courteous — deposit your trash, and do not take the handouts for the following session.

Feedback

Thank You !

Page 70: Technical Infrastructures of SAP Enterprise Portal 6.0

© SAP AG 2004, SAP TechEd / PRTL203 / 70

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.Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.Microsoft, Windows, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation. 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, and Informix are trademarks or registered trademarks of IBM Corporation in the United States and/or other countries.Oracle is a registered trademark of Oracle Corporation.UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc.HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts Institute of Technology. Java is a registered trademark of Sun Microsystems, Inc.JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape. MaxDB is a trademark of MySQL AB, Sweden.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. Data contained in this document serves informational purposes only. National product specifications may vary.These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. 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, if any. Nothing herein should be construed as constituting an additional warranty.

Copyright 2004 SAP AG. All Rights Reserved