sap web dispatcher vs f5 ltm

9
1 CONFIDENTIAL SAP “Reference architecture for SAP HTTP and SAP GUI Landscapes” [email protected]

Upload: lsudhakar

Post on 07-Apr-2015

1.768 views

Category:

Documents


63 download

TRANSCRIPT

Page 1: SAP Web Dispatcher vs f5 LTM

1 CONFIDENTIAL

SAP

“Reference architecture for SAP HTTP and SAP GUI Landscapes”

[email protected]

Page 2: SAP Web Dispatcher vs f5 LTM

2 CONFIDENTIAL

SAP GUI and Web Clients

SAP Core Deployment Applications

SAP EIS and ECC Servers

In a basic SAP Landscape clients make direct connections from SAP GUI or a web browser to SAP instances.

Business Warehouse

SAP Enterprise Portal

SAP Composite J2EE, WebDynPro

User Send Traffic Server Response Traffic

Intranet or WAN

Page 3: SAP Web Dispatcher vs f5 LTM

3 CONFIDENTIAL

DMZ

SAP with Web Dispatcher

SAP GUI and Web Clients

Business Warehouse

SAP Enterprise Portal

SAP Composite J2EE, WebDynPro

User Send Traffic Server Response Traffic

Intranet or WAN SAP EIS and ECC Servers

SAP Message Server

SAP State Information

In a software load balanced SAP Landscape, high availability is achieved when SAP clients connect directly with Web Dispatcher and then are load balanced to the back-end

Portal Servers.

Firewall/connection manager

SAP Router

Configuration: 1.  Manual 2.  Retrieve from SAP

Message Server

Load balancing: 1.  Round-robin (weighted) 2.  Load-based 3.  Use information from SAP

Message Server

High availability: 1.  Check individual Web AS

instances 2.  Use information from SAP

Message Server

Security: 1.  SSL Termination 2.  SSL Termination and re-

encryption

Persistence: 1.  Source IP 2.  Cookie

Web Dispatcher

Single Point of Failure

Page 4: SAP Web Dispatcher vs f5 LTM

4 CONFIDENTIAL

DMZ

SAP Web Dispatcher with failure

SAP GUI and Web Clients

Business Warehouse

SAP Enterprise Portal

SAP Composite J2EE, WebDynPro

User Send Traffic Server Response Traffic

Intranet or WAN SAP EIS and ECC Servers

Web Dispatcher

SAP Message Server

SAP State Information

In a software load balanced SAP Landscape, high availability is achieved when SAP clients connect directly with Web Dispatcher and then are load balanced to the back-end Portal Servers.

Since the updated information of the SAP landscape is achieved by pulling/pushing a multi-tier landscape you will have large delays in updating the Web Dispatcher with Portal status.

1.  Message Server queries SAP Portal TCP50000 2.  Message Server queries SAP Portal TCP50200 3.  Message Servers updates Web Dispatcher 4.  Web Dispatcher removes Portal Server from LB

Client traffic will be load balanced to available Portal Servers using round robin only.

SAP Router

2

4 3

1

SAP Web Dispatcher will continue to send traffic to all servers until SAP Message Server updates Web Dispatcher.

Single Point of Failure

Page 5: SAP Web Dispatcher vs f5 LTM

5 CONFIDENTIAL

Web Dispatcher   Protocols supported

–  HTTP based protocols

  Persistency detection –  Client IP based –  SAP Web AS specific (ABAP and J2EE) –  External Session ID

  Load Balancing –  Static Round Robin –  Weighted Round Robin

  Dynamic load balancing –  Client IP-address based

  Security –  SSL offload

  Performance –  Optimized, Lazy HTTP parser –  HTTP proxy cache in Web Dispatcher –  File Access for static content

Page 6: SAP Web Dispatcher vs f5 LTM

6 CONFIDENTIAL

Deploying a new system   SAP - Comparison of LB (Hardware/Software)

Source: SAP

Page 7: SAP Web Dispatcher vs f5 LTM

7 CONFIDENTIAL

DMZ

SAP Portal with f5 Load Balancing

SAP GUI and Web Clients

Business Warehouse

SAP Enterprise Portal

SAP Composite J2EE, WebDynPro

User Send Traffic Server Response Traffic

Intranet or WAN SAP EIS and ECC Servers

SAP Router Web Dispatcher SAP Message Server

SAP Health Monitor

In a hardware load balanced SAP Landscape, high availability, security, acceleration, health monitoring, and intelligent session persistence can be achieved. When an SAP client makes a direct connection with f5’s BIG-IP Local Traffic Manager, they are intelligently load balanced to only available backend services.

Session Mirror Shared Virtual IP

1.  Monitoring of Portal servers with real HTTP GET/ 2.  JSession or Cookie persistence 3.  SSL Offload 4.  WAN and LAN Optimization 5.  Active/Standby Solution 6.  Traffic Flow Modification 7.  One Connect

BIG-IP Local Traffic Manager checks health of each Portal Server, and all failed services will be removed and logged on the Load Balancer.

Page 8: SAP Web Dispatcher vs f5 LTM

8 CONFIDENTIAL

F5 BIG-IP Local Traffic Manager   Protocols Profiles supported

–  TCP –  UDP –  SIP –  RTSP –  Others

  Persistency detection –  Client IP based –  Cookie –  JSession –  External Session ID –  iRules

  Load Balancing –  Round Robin Static /Weighted –  Ratio –  Least Connection –  Observed –  Predictive –  Fastest (Application) –  Dynamic Ratio –  CPU through SNMP –  Etc..

  Performance –  Optimized, WAN & LAN –  HTTP Full proxy –  RAMCache

  Security –  SSL offload and End-To-End SSL

Page 9: SAP Web Dispatcher vs f5 LTM

9 CONFIDENTIAL

F5 and SAP documents

  F5 Website “F5’s SAP solution center” –  http://www.f5.com/sap

  SAP Website “SAP’s EcoHub” –  https://ecohub.sdn.sap.com/irj/ecohub/solutions?query=f5