Week 2 Unit 2: System Landscape Setup and Installation

Transcription

1 Week 2 Unit 2: System Landscape Setup and Installation

2 Ttrade s system landscape at a glance 1.1 Prepare SAP Best Practices Sandbox System Use software appliance for jump-start implementation 1.2 Prepare 3-tier system landscape SAP S/4HANA back- systems SAP Fiori front- server Prepare SAP Best Practices clients 1.3 Connect SAP Solution Manager 7.2 SAP Solution Manager 7.2* 1.1 SAND BOX Fit to Standard Analysis DEV QAS PRD Transport Set up SAP Solution Manager 7.2 with SAP Best Practices Front Back Front Back Transport Front Back * Ttrade has SolMan 7.2 in place already Configuration Testing Production 2016 SAP SE or an SAP affiliate company. All rights reserved. Public 2

3 1.1 Use the software appliance to prepare the system USE CASE 1: Trial 30-day hosted trial in SAP CAL USE CASE 2: Sandbox USE CASE 3: Proof-of-Concept Hosted subscription in SAP CAL or Download on-premise 2016 SAP SE or an SAP affiliate company. All rights reserved. Public 3

4 1.1 Software appliance Which ABAP client is used for what ABAP Client Description Mainly suited for 100 Trial client 200 Ready-to-Activate client Pre-activated best practices configuration & sample master data (Germany, USA)* Additional configuration for -to- sample business process Transactional data in company code for Germany USE CASE 1: Trial Technical preparation activities prior to best practices content activation USE CASE 3: POC from scratch 300 Best Practices reference client 400 IBP client 500 Client Best Practices client Pre-activated best practices configuration (all localization)* USE CASE 2: Sandbox Pre-activated content for SAP Integrated Business Planning (IBP) for finance Full copy of client 000 Customizing with SAP S/4HANA 1610 Best Practices activation on top* All scenarios that use IBP for finance USE CASE 2 (optional): Sandbox * Integration with SAP Ariba, SAP Financial Services Network not included but can be configured by customer / partner Processes localized with sample master & transactional data for US. Vertex configuration requires additional customer configuration and a valid Vertex account 2016 SAP SE or an SAP affiliate company. All rights reserved. Public 4

5 1.1 Use the software appliance to prepare the sandbox system Technical Components of the Appliance SAP S/4HANA, On-Premise 1610 Software Appliance (1) SAP S/4HANA ABAP Server S/4CORE 1610 SAP HANA Gateway + SAP Fiori SAP NetWeaver 7.51 SAP Best Practices (2) SAP NW JAVA / ADS JAVA Server Adobe Document Services SAP NetWeaver JAVA 7.50 SAP Sybase ASE (3) Remote Desktop MS Windows Remote Desktop Mozilla Firefox SAP GUI / NWBC ABAP Dev Tools / SAP HANA studio SAP Lumira SAP Design Studio MS Windows Server Remote desktop only via SAP CAL * Note: Windows remote desktop is only available when using the SAP Cloud Appliance Library (SAP CAL) 2016 SAP SE or an SAP affiliate company. All rights reserved. Public 5

6 1.2 Install SAP S/4HANA back- systems 2 flavors Start with complete new bundles: Certified Hardware Start with Tailored Datacenter Integration: TDI 2016 SAP SE or an SAP affiliate company. All rights reserved. Public 6

7 1.2 Install SAP S/4HANA back- systems Sizing Access SAP HANA Quick Sizer, create a sizing project, and enter the customer scenario data SAP HANA Quick Sizer calculates the input and provides sizing result Check for sample configurations Provide HW vor with project name; HW vor proposes configuration 2016 SAP SE or an SAP affiliate company. All rights reserved. Public 7

8 1.2 Install SAP Fiori front- server Dedicated front- server per back DEV QAS PRD Front- SAP Fiori on any SAP DB Embedded Front End SAND BOX SAP CAL or on-premise DEV QAS PRD Back- SAP S/4HANA on SAP HANA DB SAP SE or an SAP affiliate company. All rights reserved. Public 8

9 1.2 Install SAP S/4HANA Component architecture SAP Web Dispatcher SAP S/4HANA Back-End Server 1 n SAP Fiori Front-End Server 1 n Industry Solutions* Add-Ons and BPs* SAP S/4HANA Enterprise Management SAP NetWeaver SAP HANA DB Operating System SAP Fiori Add-Ons SAP NetWeaver ANY SAP DB Operating System 2016 SAP SE or an SAP affiliate company. All rights reserved. Public 9

10 1.2 Install SAP S/4HANA systems Installation process OS Installation Process 1 Maintenance Planner 2 Software Provisioning Manager Plan a new system Input system ID Select products, systems to install Select software stack level Follow on-screen instructions Download installation files Stack.xml generated / can be downloaded SAP Installation Program Stack.xml from Maintenance Planner as input parameter All components can be installed at once Standards have to be defined during installation process (e.g. parameters, passwords) Connectivity between SAP HANA and SAP S/4HANA is set up System languages can be selected Result SAP S/4HANA SAP NW 7.5 SAP HANA DB OS stack.xml 2016 SAP SE or an SAP affiliate company. All rights reserved. Public 10

11 1.2 Prepare new SAP Best Practices clients SBX DEV QAS PRD Client 000 Client 000 Client 000 Client 000 Client 100 (BP) Client 200 (BP) New Client xyz (Best Practices Client) Client copy with profile SAP_CUST New Client xyz (Best Practices Client) Client copy with profile SAP_CUST New Client xyz (Best Practices Client) Client copy with profile SAP_CUST Client 300 (BP) Sandbox Development Quality Production 2016 SAP SE or an SAP affiliate company. All rights reserved. Public 11

12 1.3 Prepare SAP Solution Manager Setup The following slides describe how SAP Solution Manager 7.2 is set up Install and Create Solution Assign Logical Component Groups Load SAP Best Practices Content Create Project and Change Cycle Install SAP Solution Manager 7.2 on-premise. This is used to administer implementation Create solution in SAP Solution Manager 7.2 Create branches: import and development Import branch is created as a sub-branch of development Create and assign relevant logical component groups to solution and branches Download the SAP Best Practices package into SAP Solution Manager 7.2 in the import branch Initial SAP Activate project can be downloaded Create the relevant change cycle and assign to the project Enable change control for development branch 2016 SAP SE or an SAP affiliate company. All rights reserved. Public 12

13 1.3 Prepare SAP Solution Manager Ttrade s approach for branch setup Production branch Production branch represents the productive solution Operations branch Operations branch to apply monitoring instrumentation Maintenance branch Maintenance branch to change the productive solution Innovation branches Import branch to import new best-practice processes Design branch to design customer target operating model As-is solution To-be solution As-is solution To-be solution Development branch to build the actual operating model = Locked = Change controlled Fix & Enhance Innovate 2016 SAP SE or an SAP affiliate company. All rights reserved. Public 13

14 Ttrade s system landscape is prepared 1.1 Prepare SAP Best Practices sandbox system Use software appliance for jump-start implementation 1.2 Prepare 3-tier system landscape SAP S/4HANA back- systems SAP Fiori front- server Prepare SAP Best Practices clients 1.3 Connect SAP Solution Manager SAND BOX Fit to Standard Analysis DEV QAS PRD Transport Set up SAP Solution Manager 7.2 with SAP Best Practices 1.2 * Ttrade has SolMan 7.2 in place already SAP Solution Manager 7.2* 1.3 Front Back Front Back Transport Front Back Configuration Testing Production 2016 SAP SE or an SAP affiliate company. All rights reserved. Public 14

15 Thank you Contact information:

16 2016 SAP SE or an SAP affiliate company. 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 SE or an SAP affiliate company. SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE (or an SAP affiliate company) in Germany and other countries. Please see for additional trademark information and notices. Some software products marketed by SAP SE and its distributors contain proprietary software components of other software vors. National product specifications may vary. These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or warranty of any kind, and SAP SE or its affiliated companies shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP SE or SAP affiliate company 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. In particular, SAP SE or its affiliated companies have no obligation to pursue any course of business outlined in this document or any related presentation, or to develop or release any functionality mentioned therein. This document, or any related presentation, and SAP SE s or its affiliated companies strategy and possible future developments, products, and/or platform directions and functionality are all subject to change and may be changed by SAP SE or its affiliated companies at any time for any reason without notice. The information in this document is not a commitment, promise, or legal obligation to deliver any material, code, or functionality. All forwardlooking statements are subject to various risks and uncertainties that could cause actual results to differ materially from expectations. Readers are cautioned not to place undue reliance on these forward-looking statements, which speak only as of their dates, and they should not be relied upon in making purchasing decisions SAP SE or an SAP affiliate company. All rights reserved. Public 16