Landscape Deployment Recommendations for SAP Marketing

Transcription

1 Landscape Deployment Recommendations for Marketing September, 2018

2 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. 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 's strategy and possible future developments are subject to change and may be changed by 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. assumes no responsibility for errors or omissions in this document, except if such damages were caused by intentionally or grossly negligent. 2

3 Major Changes or Updates Summary Major changes or updates to former landscape deployment recommendations Type of change Former Status New Status Reason Reference (former presentation) Reference (current presentation) Enhancement (not available) Support for S/4HANA on premise Availability of S/4HANA on premise./ Deployment Rating Possible Exception Not Supported Complex maintenance and sizing dependencies Co-deployment with on same AS system Slide 17 Deployment Rating General Recommendation Possible Exception Complex CPU and sizing dependencies Hub Deployment with shared HANA system Slide 14 Deployment Rating Reasonable Alternative Possible Exception Complex CPU and sizing dependencies Hub Deployment with shared HANA system, Side-by-Side Deployment with shared HANA system Slide 15/16 3

4 Agenda Introduction Methodology & Scope of Landscape Deployment Recommendations Basic Landscape Setups Recommendations for Marketing Recommendations Marketing UI deployment 4

5 Introduction Methodology & Scope of Landscape Recommendations

6 JEE JEE JEE JEE System Landscapes at Customers Designing the Optimal Landscape Layout Customer Product Roadmaps ERP SRM SCM ERP Components SRM Components SCM Components Components Business Aspects ECC Server AS SRM Server AS SCM Server AS Server AS Solution Manager Business Suite Backend Systems SolMan Content Solution Mng Component SLD Dual Stack NetWeaver Hubs Application Portal Business Warehouse BEx Web Process Integration Operations Costs Architectural Strategy Security Additional BS Instance Portal Content ADOBE EP Core AS JAVA SEM Central BI Content BW AS BICS BI JAVA EP AS JAVA ESR Content ESR&SR PI SLD PI Dual Stack Deployment Recommendations for Products Speed of Innovation Performance & Scalability Legal Aspects Solution Landscape of Customer OS/DB platform strategy IT Aspects SLA & Availability Technical Documentation (Planning, Installation & Configuration Guides, etc.) 6

7 JEE JEE JEE JEE Deployment Recommendations for Products Guiding Principles ERP SRM SCM ERP Components SRM Components SCM Components Components ECC Server SRM Server SCM Server Server AS AS AS AS Solution Manager Business Suite Backend Systems SolMan Content Solution Mng Component SLD Dual Stack NetWeaver Hubs Application Portal Additional BS Instance Portal Content EP Core AS JAVA ADOBE Business Warehouse SEM Central BI Content BW AS BEx Web BICS BI JAVA EP AS JAVA Solution Landscape of Customer Process Integration ESR Content ESR&SR PI SLD PI Dual Stack High-Level Guidance for optimized Landscape Layouts Deployment Recommendations for Products 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 product strategy, achieved landscape qualities and cross-product alignment 7

8 Ease Landscape Planning By Stronger Guidance Used Methodology Clear recommendations by categorization of deployment options Possible Exception Only useful for specific use cases Supported by, but limitations might occur Reasonable Alternative Useful choice for certain use cases or customer scenarios Supported and confirmed by s strategy Option III Option II Option I General Recommendation Best choice for majority of typical landscape use cases Recommended by s strategy Accepted by a wide base of customers Goal Consider Outlining main important aspects Optimal trade-off between flexibility and simplicity Applied to main building blocks of products Alternative deployment options typically have different pros & cons Customer individual assessment is not compensated 8

9 Architecture Overview JAM User Interface Commerce/ Web Shop ERP C4C Social & Consumer Data Non- / Web Page Marketing UI: Fiori with Launchpad OData via Web Dispatcher Fiori Marketing Application Server Marketing: Tables, Views, Procedures, Search Models HANA Private Cloud On-Premise Social / Web Campaign Service Provider SMS Service Provider 9

10 Product Deployment View Marketing in System Landscapes ERP or S/4HANA ERP or S/4 Application System NON Integration Middleware Webdispatcher Marketing UI for AS HANA System for HANA Content Primary DB connection HANA Main required products External Application System based on NetWeaver AS Marketing () Add-On UI5-based UI for content for HANA HANA system BS application system replicating business data Integration Middleware Process Integration (PI)/ Cloud Platform Integration (CPI) for ERP or S/4HANA, and NON- applications on project basis Landscape Transformation (LT) for ERP and (not S/4HANA) Data Services for NON- applications 10

11 Basic Landscape Setups Recommendations for Marketing

12 Deployment of Marketing Overview of Recommended Landscape Patterns Integration Middleware Marketing UI for General Recommendation ERP or S/4HANA ERP or S/4 AS HANA System for Primary DB connection Application System NON HANA Content HANA Hub Deployment with separate HANA system and separate AS Integration Middleware Marketing UI for ERP ERP Integration Middleware Marketing UI for Data Warehouse BW Possible Exception Application System NON AS AS Primary DB connections HANA System for HANA Content HANA ERP or S/4HANA ERP or S/4 Application System NON AS AS Primary DB connections HANA System HANA Content HANA Content BW HANA Hub Deployment with shared HANA system of Business Suite Hub Deployment with shared HANA system of other application 12

13 Deployment of Marketing Hub Deployment with separate HANA system and separate AS General Recommendation ( Non-disruptive deployment into existing Business Suite landscape ) centrally integrated with multiple business applications (e.g. ERP or S/4HANA on premise,, NON-) deployed in the cloud or on-premise on a separate AS and HANA system All required business data is replicated to the HANA for system Example Benefits Fast adoption of via hybrid cloud or separate on-premise deployment Integration Middleware Marketing UI for Independent innovation speed for new capabilities Integration of ERP or S/4HANA with business data for possible Simple sizing No need to migrate ERP or to HANA first ERP or S/4HANA AS No risk for existing ERP/ system (performance, patching, downtime, etc.) ERP or S/4 HANA System for Primary DB connection Considerations One additional HANA system required (could be deployed in the cloud) Application System HANA Content Connecting multiple ERP or S/4HANA or multiple systems not supported NON HANA 13

14 Deployment of Marketing Hub Deployment with shared HANA system Possible Exception ( Deployment with shared HANA ) centrally integrated with multiple business applications (e.g. ERP,, NON-) deployed on a separate AS system, but co-deployed on HANA system of one Business Suite Application ( onhana or ERPonHANA) or S/4HANA Example Benefits Independent innovation speed for new capabilities Marketing ERP Integration of ERP or S/4HANA with business data for possible Integration Middleware UI for ERP Flexible decision which HANA system to use ( or ERP) Application System NON HANA Content AS Primary DB connections HANA System for HANA AS Considerations Requires at least 7.03 on HANA (resp. ERP 6.07 on HANA) More complex HANA sizing Shared resources (CPU, memory) influence performance of other applications on top of HANA system Impact on existing HANA system during lifecycle operations (patching, downtime, etc.) Consider restrictions of HANA co-deployments ( note , ) Connecting multiple ERP or multiple systems not supported S/4HANA OnPremise cannot be integrated through cross schema access 14

15 Deployment of Marketing Hub Deployment with shared HANA system General Remarks Possible Exception ( Deployment with shared HANA ) Multiple Components one Database (MCOD)* HANA Appliance HANA System <SID> DB Schema 1 DB Schema 2 HANA Database 1 HANA Appliance 1 HANA System 1 HANA Database n Applications in different schemas Multi Database Containers (MDC) HANA Appliance HANA System <SID> DB Schema Tenant Database 1 System Database DB Schema Tenant Database 2 1 HANA Appliance 1 HANA System n HANA Databases Disks CPUs Memory * only supported for applications listed on white list ( Notes , ) Disks CPUs Memory HANA system shared with other whitelist applications like, ERP or S/4HANA Other HANA applications BW Co-deployment on HANA via MCOD installation Integration of ERP or data across different schemas into Marketing HANA system shared with any other application Co-deployment on HANA via MDC installation Replication of, ERP or S/4HANA data into Marketing has to be done via integration middleware 15

16 Deployment of Marketing Business Warehouse Hub Deployment with shared HANA system Possible Exception ( Data sharing with other HANA-based application ) centrally integrated with multiple business applications (e.g. ERP or S/4HANA,, NON-) deployed on a separate AS system, but co-deployed with other application(s), e.g. BW, on same HANA system and other HANA-based application(s) allow data sharing within HANA system All required business data is replicated to the HANA system Example Benefits Independent innovation speed for new capabilities ERP or S/4HANA ERP or S/4 Integration Middleware Marketing UI for AS Primary DB connections Data Warehouse BW AS Integration of ERP or S/4HANA with business data for possible Lower TCO due to shared HANA system and shared replication data Mutual data consumption between and other HANA-based application (e.g. ADT accessing BW data) No risk for existing ERP/ system (performance, patching, downtime, etc.) No need to migrate ERP or to HANA first Application System NON HANA Content HANA System HANA HANA Content BW Considerations Connecting multiple ERP or multiple systems not supported More complex HANA sizing Impact on existing HANA system applications(performance, patching, downtime, etc.) Co-deployment on HANA only supported for applications listed on whitelist ( note ) 16

17 Deployment of Marketing Add-On Deployment with shared and HANA system Not Supported ( Hardware minimized deployment with on HANA ) locally integrated with co-deployed on AS and HANA system of business data is directly accessed by Example with Marketing AS HANA System HANA Primary DB connections HANA Content Implications Shared system not supported for (or any other Business Suite application or S/4HANA) Innovation speed for dependent from High maintenance dependencies High manual effort for later scale-out, if needs to be separated More complex sizing ( and HANA) Impact on existing HANA system of (performance, patching, downtime, etc.) Consider restrictions of HANA co-deployments ( note ) 17

18 Deployment of Marketing Hub Deployment with shared and HANA system Not Supported centrally integrated with multiple business applications (e.g. ERP,, NON-) co-deployed on AS and HANA system with other -based HANA application Required business data is replicated to the HANA system Example UI for Marketing and other application AS HANA System Other application Primary DB connections Implications No support of a co-deployment with any other application on the same AS system Innovation speed for needs to be aligned with other application Upgrades may not be possible Low maintenance flexibility High manual effort for later scale-out, if needs to be separated More complex sizing ( and HANA) Co-deployment on HANA only supported for applications listed on whitelist ( note ) HANA Content HANA 18

19 Recommendations Marketing UI Deployment

20 Deployment of UI for Marketing Embedded UI Deployment with AS system General Recommendation UIs for deployed within product Marketing UIs for locally integrated with backend functionality UIs for co-deployed with backend application on same AS system Example Webdispatcher Benefits Automated installation & configuration with backend functionality ERP or S/4HANA Integration Middleware Marketing UI for AS UI and backend application automatically in sync Lower alignment and regression test effort for updates (only concerned) All UIs are integrated within same environment (single URL, no Fiori Launchpad required) No additional system required Lower maintenance effort ERP or S/4 Primary DB connection HANA System for Considerations Innovation speed of UIs closely coupled with backend functionality Application System HANA Content No cross-integration with other Fiori UI applications NON HANA 20

21 Deployment of UI for Marketing Add-On Deployment with central Fiori Front-End Server Not Supported UIs for co-deployed with Fiori UIs of other applications on central Fiori Front-End Server Fiori Frontend Server Example UI for Fiori UIs of other applications UI Add-On Gateway Server Marketing AS End-user access to Reasons UIs for not shipped separately, but only as part of Marketing Manual additional installation & configuration for backend connectivity required Strict version dependencies with backend application, frontend and backend parts need to be manually kept in sync Alignment and regression test effort for all UI applications after required updates of AS of central Frontend-Server Additional system required Performance and downtime side effects due to shared usage of Frontend-Server Primary DB connection HANA System for Hana Content HANA 21

22 Thank you. Contact information: By mail to or by a Support Incident on component name CEC--ITC