deployment recommendations for sap enterprise portal · pdf filelandscape deployment...

Landscape Deployment Recommendations for

SAP Enterprise PortalSAP SE

April 2016

© 2016 SAP SE or an SAP affiliate company. All rights reserved. 2Customer

Disclaimer

This presentation outlines our general product direction and should not be relied on in making a

purchase decision. This presentation is not subject to your license agreement or any other

agreement with SAP. SAP has no obligation to pursue any course of business outlined in this

presentation or to develop or release any functionality mentioned in this presentation. This

presentation and SAP's strategy and possible future developments are subject to change and may

be changed by SAP at any time for any reason without notice. This document is provided without a

warranty of any kind, either express or implied, including but not limited to, the implied warranties

of merchantability, fitness for a particular purpose, or non-infringement. SAP assumes no

responsibility for errors or omissions in this document, except if such damages were caused by

SAP intentionally or grossly negligent.


Agenda

Introduction

Methodology & Scope of Landscape Deployment Recommendations

Basic Landscape Setups

Recommendations for Application Portal

Additional Landscape Setups

Corporate Intranet Portal

External Facing Portal

Interoperability with 3rd Party Portals

Appendix

Configuration Options

IntroductionMethodology & Scope of Landscape Deployment Recommendations


System Landscapes at CustomersDesigning the Optimal Landscape Layout

Business Aspects

Operations

Costs

Speed of

Innovation

Security

Architectural

Strategy

Performance &

ScalabilityLegal Aspects

…

OS/DB platform

strategy

SLA &

Availability

IT Aspects

Product Roadmaps

Technical Documentation(Planning, Installation &

Configuration Guides, etc.)

Deployment Recommendations

for SAP Products

SLD

Dual Stack

SAP

Solution Manager

ABAP

JEE

Solution Mng

Component

AS ABAP

ECC

Server

SAP ERP

ABAP

ERP

Components

AS ABAP

SRM

Server

SAP SRM

ABAP

SRM

Components

AS ABAP

SCM

Server

SAP SCM

ABAP

SCM

Components

AS ABAP

CRM

Server

SAP CRM

ABAP

CRM

Components

BW

AS ABAP

Business Warehouse

SEM

Central BI

Content

ABAP

EP

AS JAVA

BEx Web

JEE

BI JAVA

BICS

PI

PI Dual Stack

Process Integration

ABAP

JEE

ESR&SR

ESR Content

SLD

SolMan Content

SAP NetWeaver Hubs

SAP Business Suite

Backend Systems

EP Core

AS JAVA

Application Portal

JEE

Additional SAP BS Instance

Portal

Content

ADOBE

Solution Landscape

of Customer


Landscape Deployment Recommendations for SAP ProductsGuiding Principles

Allow flexibility by offering different deployment options (not one-size-fits-all)

Provide guidance by rating different options

Ease decisions by listing pros & cons

Simplify consumption of information by using a common methodology

Increase reliability by considering SAP product strategy, achieved landscape qualities and

cross-product alignment

High-Level Guidance

for optimized

Landscape Layouts

SLD

Dual Stack

SAP

Solution Manager

ABAP

JEE

Solution Mng

Component

AS ABAP

ECC

Server

SAP ERP

ABAP

ERP

Components

AS ABAP

SRM

Server

SAP SRM

ABAP

SRM

Components

AS ABAP

SCM

Server

SAP SCM

ABAP

SCM

Components

AS ABAP

CRM

Server

SAP CRM

ABAP

CRM

Components

BW

AS ABAP

Business Warehouse

SEM

Central BI

Content

ABAP

EP

AS JAVA

BEx Web

JEE

BI JAVA

BICS

PI

PI Dual Stack

Process Integration

ABAP

JEE

ESR&SR

ESR Content

SLD

SolMan Content

SAP NetWeaver Hubs

SAP Business Suite

Backend Systems

EP Core

AS JAVA

Application Portal

JEE

Additional SAP BS Instance

Portal

Content

ADOBE

Solution Landscape

of Customer

Deployment Recommendations

for SAP Products


Ease Landscape Planning By Stronger Guidance Used Methodology

Clear recommendations by categorization of deployment options

Outlining main important aspects

Optimal trade-off between flexibility and simplicity

Applied to main building blocks of SAP products

Alternative deployment options typically have different pros & cons

Customer individual assessment is not compensated

Goal

Consider

Option IOption II

Option

IIIGeneral Recommendation

Best choice for majority of typical

landscape use cases

Recommended by SAP’s strategy

Accepted by a wide base of

customersReasonable Alternative

Useful choice for certain use

cases or customer scenarios

Supported and confirmed by

SAP’s strategy

Possible Exception

Only useful for specific use cases

Supported by SAP, but limitations

might occur


High Level Product Overview

Fiori UX (FLP on EP) Traditional L shape

ApplicationPortal

HR, SRM, BEx, BO,Design Studio,Fiori analytics,

SAP transactions….

Corporate

Intranet

Web content,

Collaboration,

Docs & Apps

External

Facing

B2C B2B

Portal iViews &

Fiori Remote Catalogs Portal iViews

SAP Enterprise Portal


Application Portal vs. Corporate Intranet Portal

Corporate Intranet PortalApplication Portal

20% applications/analytics vs. 80%

unstructured content (web pages/

documents)

80% applications/analytics vs.

20% unstructured content (web

pages/ documents)

Content

Typically based on SAP Enterprise

Portal (EP) extended by further

capabilities or consumption of 3rd party

content

Typically based on SAP Enterprise

Portal Core (EP Core)

Portal Components

AJAX Framework Page (AFP)Fiori Framework Page (FFP)Recommended Framework Page

Personalized and role-based access to

SAP and NON-SAP applications,

connecting heterogeneous information

sources, and enabling a central

collaboration platform and 3rd party

interoperability

Central, role-based, personalized

and unified access, primarily to

SAP backends

Typical Technical Use Cases


Scope of Landscape RecommendationsBuilding Blocks in System Landscapes for SAP Enterprise Portal

JEE

SAP system with

own database

available platform

technology

Rolemain role of this

system

Considered main usage scenarios

Application Portal for SAP Business Suite

Corporate Intranet Portal in landscapes


Interoperability with 3rd Party Portals

Considered main building blocks

SAP NetWeaver Enterprise Portal (EP)

SAP NetWeaver Enterprise Portal Core (EP Core)

Fiori Frontend Server

EP Core

Application Server JAVA

Application Portal

JEE

Portal Content

Portal based

SAP Instance

Java-based

SAP Instance

SAP UI5

Fiori Launchpad

Gateway

Server

AS ABAP

Fiori Front-End Server

ABAP

Central UI Technology

Fiori Uis for ERP, SRM

Enterprise Portal

Application Server JAVAJEE

EP Core

Portal-Add-On


Portal Content

Basic Landscape SetupsRecommendations for Application Portal


Deployment of SAP Enterprise PortalCentral Hub Deployment integrated with central SAP Fiori-Front-End Server

General Recommendation

Single SAP Enterprise Portal for central user access

Use SAP Fiori Launchpad on Portal (FLP on EP)

One stop-shop for Fiori and Portal content

Consume remote catalogs (via Fiori Frontend Server) as much as possible

Avoid embedded deployment within the application backend system

Benefits Centrally governed and administrated user access

Supports independent innovation speeds

Incorporates many opportunities for new benefits, by protecting and leveraging past

investments with new innovations

Different configuration options for integration with central Fiori Front-End Server (refer to

Appendix: iViews vs. Remote Catalogs)

Re-use of Portal as runtime for still existing SAP Business Suite JAVA UIs

Best aligned with SAP’s new UX strategy and roadmap - SAP Fiori Road Map

Enables integration of S/4 HANA, ERP/ERP on HANA, BI and more

Considerations

Version interoperability to connected application systems to be checked (Note 1388258)

Consider the different DB options (learn about SAP HANA Database)

Maintenance Strategy for FLP on Portal (Note 2261419)

Support of S/4 HANA integration into SAP Enterprise Portal is planned for Q4 2016

Example

Web Dispatcher

ECC

Server

ERP

HANA

Gateway enabl.

Suite content

BW

Data Warehouse

System

ABAP

S/4

Server

S/4HANA

Gateway enabl.

S4/H content

HANA

Fiori Remote Catalogs

Portal iViews

integration

BI JAVA

JEE

EP Core

Application Server JAVA

Application Portal

JEE

Portal Content

Biller DirectXSS

SAP UI5

Fiori LaunchpadGateway

Server

AS ABAP

Fiori Front-End Server

ABAP

Central UI Technology

Fiori Uis for ERP, SRM

Portal iViews

integration

BEx Web

Fiori UI

integration

https://service.sap.com/~sapidb/012002523100016328952014E.pdf

http://service.sap.com/sap/support/notes/1388258

http://www.sap.com/pc/tech/in-memory-computing-hana/software/in-memory-database/index.html

http://service.sap.com/sap/support/notes/2261419


Deployment of SAP Enterprise PortalCentral Hub Deployment integrated with separated JAVA-UI & application runtime systems

Benefits

Central access and role-based navigation

Autonomous local UIs/applications

Local changes do not impact central application portal

Considerations

Workaround for Java-UIs/applications closely coupled to backend systems

More complex landscape setup

Higher TCO

Higher integration effort

Relevant only for Java UIs

Legacy Architecture, only the recommended architecture follows the SAP Enterprise

Portal roadmap, which is focused on Fiori and Fiori Launchpad as part of SAP’s UX

strategy (refer to SAP Fiori Road Map)

Reasonable Alternative

Shared SAP NetWeaver Portal for central user access

Additional local sidecar systems as runtime for SAP Business

Suite Java-UIs, remotely integrated with central portal

Avoid embedded deployment within the application backend system

* details regarding content sharing see slide „Additional Information“

Example

BI JAVA

BEx Web

JEE

BW

Data Warehouse

System

ABAP

SRM

Server

SAP SRM

Backend

ABAP

AS JAVA

Local SRM

JAVA System

JEE

LAC

ECC

Server

SAP ERP

Backend

ABAP

AS JAVA

Local

HR Portal

JEE

XSS

EP Core

Local content

Content sharing with

Application Portal*

EP Core

AS JAVA

Application Portal

JEE

Portal Content



Possible Exception

Portal capabilities within BEx Web system configured

Provide a role-based user access to (few) application backend systems

Avoid deployment of further portal applications on the portal system

Deployment of SAP Enterprise PortalCo-deployment with central BEx Web system

Benefits

Reuse of portal infrastructure for BW reporting and application portal scenarios

Simplified landscape setup

Centrally administrated user access

Considerations

BEx Web system as corporate intranet portal not supported

No automated separation of BI JAVA for later scale-out

Innovation speed of portal and BEx Web capabilities to be synchronized

BW web reporting impacts performance of portal usage

Interoperability to connected application systems to be checked

Legacy Architecture, only the recommended architecture follows the SAP Enterprise

Portal roadmap, which is focused on Fiori and Fiori Launchpad as part of SAP’s UX

strategy (refer to SAP Fiori Road Map)

Example

SAP ERP

Backend

ECC

Server

ABAP

EP

AS JAVA

BEx Web for Data

Warehouse

JEE

BI JAVA

Portal content of SAP ERP

backend system deployed

within BEx Web system

Portal Content

BW

AS ABAPABAP

Data Warehouse



Deployment of SAP Enterprise PortalMultiple federating Hub Deployments

Benefits Central access to content via consumer portal

Autonomous sub-portals for different business units

Independent content administration

Considerations Complex landscape setup

Configuration effort to setup FPN scenario

Higher administration & maintenance effort for additional producer portal

Same user basis required within consumer and producer portal

Only content administration can be distributed

Restrictions as defined in SAP note 880482

Legacy Architecture, only the recommended architecture follows the SAP Enterprise Portal

roadmap, which is focused on Fiori and Fiori Launchpad as part of SAP’s UX strategy (refer

to SAP Fiori Road Map)

Possible Exception

Federated Portal Network (FPN) with a consumer portal for central

end user access to application systems of different business units

Local producer portal for independent content administration

Remote scenarios through RAI (Remote Application Integration) is recommended


Example

AS JAVA

Producer Portal

JEEAS JAVA

Producer Portal

JEEAS JAVA

Producer Portal

JEEAS JAVA

Producer Portal

JEE

AS JAVA

Consumer Portal

JEE

SRM

Server

SAP SRM

Backend

ABAP

ECC

Server

SAP ERP

Backend

ABAP

ECC

Server

SAP ERP

Backend

ABAP

Application

Backend

NON SAP

Application

Federation between

multiple

autonomous

application portal*

RAI RAI

EP Core

Portal Content

EP Core

Portal Content

EP Core

Portal Content

Domain 1 Domain 2


Additional Landscape Setups

Additional Scenarios for SAP Enterprise Portal Based System Landscapes


Corporate Intranet PortalContent Sharing with Corporate Intranet Portal

Benefits

Centrally governed and administrated

Single point of access to all corporate assets

Autonomous local UIs/applications

Higher scalability

Less effort to keep the Intranet portal stable

Considerations

More complex landscape setup

Additional administration effort

Higher integration effort

Relevant only for Java UIs

Only the recommended architecture follows the SAP NetWeaver Portal roadmap,

which is focused on Fiori and Fiori Launchpad as part of SAP UX strategy (refer

to SAP Fiori Road Map)

Content Sharing with Corporate Intranet Portal

Enterprise-wide intranet portal for central access to all applications

Deployed as separate system and central collaboration platform

Additional local systems as runtime for SAP Business Suite Java-UIs,

remotely integrated into central corporate intranet portal

Example

Content sharing with

Corporate Intranet

Portal*

EP

AS JAVAJEE

Portal Content

KM

Forums

Wikis


BI JAVA

BEx Web

JEE

BW

Data Warehouse

System

ABAP

SRM

Server

SAP SRM

Backend

ABAP

AS JAVA

Local SRM

JAVA System

JEE

LAC

ECC

Server

SAP ERP

Backend

ABAP

AS JAVA

Local

HR Portal

JEE

XSS

EP Core

Local

content




External Facing PortalLandscape Option for External User

Implementing External Facing Portal

Emphasizes general recommendation of central portal approach

Re-use existing central portal for external users like vendors or suppliers

Web infrastructure setup should balance security requirements, performance and

hardware costs

Benefits

Existing portal landscape re-used

Consider needs of internal and external users

Access performs well over Internet

Portal operates similar to standard, customizable web sites

Considerations

Company security requirements may drive separate external portal architecture

Not every scenario supported, check SAP note 853509 for known restrictions

Example

EP/

EP Core

SAP Enterprise

Portal

JEE

ECC

Server

SAP ERP

Backend

ABAP

CRM

Server

SAP CRM

Backend

ABAP

Server

NON SAP

Information Source

EXTERNALUSER

INTERNALUSER

Firewall


capabilities used for

connecting external users


Interoperability with 3rd Party PortalsIntegrating 3rd party content into SAP Enterprise Portal

Integrating 3rd

party content into SAP Enterprise Portal

SAP Enterprise Portal serves as central Corporate Intranet Portal

Complementary 3rd party content and services integrated via open standards

and APIs

Benefits

Single point of access to all corporate assets

Open platform for 3rd party content integration

SAP Enterprise Portal smoothly enhanced with existing NON-SAP content &

capabilities

Considerations

Custom coding or 3rd party integration packages may need to be implemented

Look&Feel of different portals to be aligned

Example

Server

NON SAP

Information Source

NON SAP

Portal

3rd Party Content

Integrating

3rd party content

into SAP Enterprise

PortalEP

AS JAVAJEE

Portal Content

KM

Forums

Wikis


SRM

Server

SAP SRM

Backend

ABAP

AS JAVA

Local SRM

JAVA System

JEE

LAC

ECC

Server

SAP ERP

Backend

ABAP

AS JAVA

Local

HR Portal

JEE

XSS

EP Core

Local content


Interoperability with 3rd Party PortalsIntegrating SAP Enterprise Portal into 3rd Party Portal

Integrating SAP Enterprise Portal into 3rd

party portal

SAP Enterprise Portal serves as central application portal for SAP applications

SAP applications integrated into 3rd party portal via interoperability capabilities

of SAP Enterprise Portal

Benefits

Re-use of existing non-SAP portal infrastructure

Smoother integration of SAP applications via SAP Portal into 3rd party portal

(e.g. SSO, session management)

Considerations

Additional SAP Portal required

Not all SAP portal functionality available to end user

Look&Feel of different portals to be aligned

Example

SRM

Server

SAP SRM

Backend

3rd Party

Portal

Company Portal

Server

NON SAP

Information Source

SAP NetWeaver Portal produces

content for central

NON-SAP Company Portal

ECC

Server

SAP ERP

Backend

ABAP

Application

Backend

NON SAP

Application

EP Core

AS JAVA

Application Portal

JEE

Portal Content

Biller Direct

XSS

AppendixDifferent Configuration Options: iViews vs. Remote Catalogs


Fiori integration in FLP on EP: Fiori iView vs. Remote Catalogs

Fiori iView

iView properties (Content – Fiori)

iView per application

Limited number of Fiori apps

iFrame Integration

Available in all Framework Pages

Remote Catalogs

New editor via Role editor

Discovery of catalogs and groups

Non-iFrame integration

Available only in Fiori Framework Page


Remote Catalog Benefits Compare to Fiori iView

Enable fast and easy integration of all Fiori content

Superior runtime integration - iFrame-less integration and better performance

Automatic presentation of dynamic values on tiles

Lower TCO - changes in catalogs take affect without Portal configuration changes

Thank you

deployment recommendations for sap enterprise portal · pdf filelandscape deployment...

Documents