Building your SAP Business One Cloud Landscape. SAP Business One Cloud Landscape Workshop

Transcription

1 Building your SAP Business One Cloud Landscape SAP Business One Cloud Landscape Workshop

2 Section Objectives This section of the course will enable you to: Complete the steps necessary to build a SAP Business One Cloud landscape. SAP Business One Cloud Landscape Workshop: Section SAP AG. All rights reserved. 2

3 Topics in this section 1. Prerequisites 2. Configuring the Server Landscape 3. Managing Remote Access 4. Configuring Database Instances 5. Installing the SAP Business One Cloud Software Components SAP Business One Cloud Landscape Workshop: Section SAP AG. All rights reserved. 3

5 Prerequisites (Hardware/Software) Server Requirements: You have configured the required number of machines for your landscape (based on your estimated requirements) You have installed Microsoft Server 2008 R2 Standard or Enterprise edition You have installed Microsoft SQL Server 2008 R2 Standard or Enterprise on the Database Server(s) If using Microsoft Remote Desktop Services you have configured Internet Information Services (IIS) on the User Access Portal Server(s) You have installed Adobe Reader and Adobe Flash on all Presentation Servers Install Mozilla Firefox on the Central Management Server Software Requirements: Compatibility with the SAP Business One client application, which you can find in SAP Note SAP Business One Cloud Landscape Workshop: Section SAP AG. All rights reserved. 5

6 Prerequisites (SSL Certificates) The following certificates are required for an SAP Business One Cloud landscape: Certificates for Remote Desktop Services Remote Desktop Services components require certificates for authentication. For more information, see Certificates for the System Landscape Directory If you select Hypertext Transfer Protocol Secure (HTTPS) as the web protocol the SLD uses for connections, a certificate is required for authentication. For more information, see Installing SAP Business One Cloud Components. You can acquire the necessary certificates using either of the following methods: Third-party Certificate Authority You can purchase certificates from a third-party global certificate authority that Microsoft Windows trusts by default. Certificate Authority Server You can configure a Certificate Authority (CA) server in the SAP Business One Cloud landscape to issue certificates. If you choose this method, you must configure all servers in the landscape to trust the CA s root certificate. SAP Business One Cloud Landscape Workshop: Section SAP AG. All rights reserved. 6

7 Introducing the workshop cloud landscape AcXess Sandboxed SAP Business One Cloud Workshop Landscape Active Directory User Access Portal RDS Gateway Domain Controller Server SAP Business One Client Presentation Server SQL Instance for Service Unit(s) SQL Instance for System Landscape Directory Cloud Control Center License Server Integration Component SBO Mailer Database Server Software Repository Shared Storage Central Management Server SAP Business One Cloud Landscape Workshop: Section SAP AG. All rights reserved. 7

9 Exercise Login to your training landscape using the login details provided by your instructor. In Building the SAP Business One Cloud Landscape complete the table in section 2.1 SAP Business One Cloud Landscape Workshop: Section SAP AG. All rights reserved. 9

11 Configuring the Server Landscape Windows Time Server Time service tool required by the Kerberos authentication protocol Ensures that all machines in the SAP Business One Cloud Landscape use a common time Without a time server synchronization errors will occur in the authentication processes. More information on setup can be found at SAP Business One Cloud Landscape Workshop: Section SAP AG. All rights reserved. 11

12 Configuring the Server Landscape Configuring the Domain Controller Ensure the Windows Active Directory Service has been installed on the Domain Controller(s) Create a new domain Design the structure you want to use in Active Directory Users and Computers, e.g. sapbusinessonecloud.net (Domain) Cloud Operators OU (Organizational Unit) Cloud Infrastructure Operator GP (Group) Cloud Application Operator GP(Group) Customer Organization (Organizational Unit) Customer ABC OU (Organizational Unit) Created for each customer Customer ABC GP (Group) Service Unit X GP(Group) Service Unit Y GP(Group) SAP Business One Cloud Landscape Workshop: Section SAP AG. All rights reserved. 12

13 Exercise In Building the SAP Business One Cloud Landscape: Complete section to setup a Windows Time Server Using the suggested structure described in this section create a suitable Active Directory structure in the landscape Domain Controller SAP Business One Cloud Landscape Workshop: Section SAP AG. All rights reserved. 13

14 Configuring the Server Landscape Define a User Account naming convention Currently it is not possible to use a user s address as their login credentials Careful consideration should be given to the convention used to cater for a large number of users This naming convention should also consider other aspects of the landscape (e.g. tenant databases etc.) Windows Roaming user profile A productive landscape requires more than one Presentation Server, a Windows Roaming User Profile provides a mechanism to store user data and provide it to the computers users log on to. Each domain user requires one SAP Business One Cloud Service User User that is used by the SAP Business One System Landscape Directory (SLD) Service and SAP Business One SLD Agent throughout the landscape SAP Business One Cloud Landscape Workshop: Section SAP AG. All rights reserved. 14

15 Configuring the Server Landscape An SAP Business One Cloud landscape requires the following shared folders for storing files: Software Repositories Shared Folders Implementation Repositories Company Template Repositories Tenant Storage User Storage SAP Business One Cloud Landscape Workshop: Section SAP AG. All rights reserved. 15

16 Exercise In Building the SAP Business One Cloud Landscape: Complete section to create the required domain users Complete section to configure the roaming profile Complete section 3.2 to create the required storage in the landscape SAP Business One Cloud Landscape Workshop: Section SAP AG. All rights reserved. 16

18 Managing Remote Access Remote Desktop Licensing The Remote Desktop Licensing server role manages Remote Desktop Services client access licenses that are required for devices and users to connect to a Remote Desktop Session Host server. Remote Desktop Session Host(s) The Remote Desktop Session Host is the server role that runs Windows programs or provides users with a full Windows Desktop experience. Multiple servers can be configured to act as a farm to provide scalability and redundancy. Remote Desktop Connection Broker The Remote Desktop Connection Broker manages user sessions in a loadbalanced Remote Desktop Session Host server farm. Functionality includes session distribution and user reconnection among others. SAP Business One Cloud Landscape Workshop: Section SAP AG. All rights reserved. 18

19 Managing Remote Access* Remote Desktop Session Host Server Farm Each Remote Desktop Session Host Server farm is a collection of presentation servers that provide access to SAP Business One Cloud for a single Service Unit Users are connected to a presentation server by the domain controller, connection broker and gateway servers. User Access Portal Server The SAP Business One Cloud User Access Portal is a customized version of the portal delivered for Remote Desktop Web Access by Microsoft and should be configured for productive use by your team. Remote Desktop Gateway The Remote Desktop Gateway is a server that allows authorized users to connect to remote computers in the network from any internet connection. The Remote Desktop Gateway uses SSL to transmit data securely and avoids firewall issues that can occur with RDP. *Assuming use of Microsoft Remote Desktop Services (RDS) in this workshop, if you are using a different solution check our SAP Business One Cloud InfoHub or your 3rd party solution documentation SAP Business One Cloud Landscape Workshop: Section SAP AG. All rights reserved. 19

20 Exercise In Building the SAP Business One Cloud Landscape: Complete section to install the necessary certificates Complete section to install Microsoft Remote Desktop Web Access and the Remote Desktop Gateway roles Complete section to configure Microsoft Remote Desktop Web Access Complete sections to configure Remote Desktop Licensing Complete section to configure the Microsoft Remote Desktop Session Host Complete section to configure the Microsoft Remote Desktop Connection Broker SAP Business One Cloud Landscape Workshop: Section SAP AG. All rights reserved. 20

22 Configuring Database Instances There are two different use cases for a database instance in the SAP Business One Cloud Landscape: A database instance for the SAP Business One Cloud System Landscape Directory (SLD). This is the database that stores and maintains data related to the operation of the SAP Business One Cloud Landscape. A database instance for a Service Unit. A Service Unit can only operate one version of SAP Business One, which means each Service Unit can only have one database instance related to it. This database instance stores all tenant databases and common database for a single Service Unit. Each landscape can have multiple Service Units High Availability Scenarios Microsoft SQL Server can be configured to allow failover capability by creating a cluster of servers. See note SQL Server Cluster Service, Indexing or Log Shipping for more information The SAP Business One Cloud SLD Service can also be installed as part of a cluster allowing for high availability of the SLD Database. See Configuring a High-Availability Failover solution for the SLD on the SAP Business One Cloud Landscape InfoHub SAP Business One Cloud Landscape Workshop: Section SAP AG. All rights reserved. 22

23 Exercise In Building the SAP Business One Cloud Landscape: Review section 3.4 that configured the two Microsoft SQL Server Instances Complete section to configure the installed Microsoft SQL Server Instances (instead of the instructions in disable the firewalls on the SQL, RDS and CCC servers) SAP Business One Cloud Landscape Workshop: Section SAP AG. All rights reserved. 23

25 Installing the SAP Business One Cloud Software Components Create a software repository The software repository will be used to store: The versions of SAP Business One that are required in this landscape Each version of SAP Business One will need to be stored in it s own shared folder The folders will need the correct permissions set to allow the Cloud Control Center access to it. Create the folders in the Software Repository setup already earlier in the workshop Name the folders so it is easy to tell what version exists in the folder SAP Business One Cloud Landscape Workshop: Section SAP AG. All rights reserved. 25

26 Installing the SAP Business One Cloud Software Components Installing the SAP Business One License Server A license server is a central component that manages the application license mechanism. Since the license server is compatible with all versions of SAP Business One, multiple service units can share a single license server. For the integration component and mailer service to function correctly in ondemand environments, in the SAP Business One License Manager, register any common databases and ensure you select the Use Trusted Connection checkbox. For more information about installing and configuring a license server, see the SAP Business One Administrator s Guide SAP Business One Cloud Landscape Workshop: Section SAP AG. All rights reserved. 26

27 Installing the SAP Business One Cloud Software Components Installing the SAP Business One Mailer The SAP Business One Mailer provides services for SAP Business One tenants. When installing SAP Business One Mailer in a SAP Business One Cloud environment you must ensure that: There is one SAP Business One Mailer for each Service Unit The machine that it is installed on is configured for SAP Business One Cloud (via the registry settings) The logon account for the SAP Business One Mailer Service has local administration privileges, e.g. if following the workshop documentation this can be set to SAPServiceB1C. The SAP Business One Mailer is automatically registered into the Cloud Landscape when it is started but you must manually assign it to the correct Service Unit SAP Business One Cloud Landscape Workshop: Section SAP AG. All rights reserved. 27

28 Installing the SAP Business One Cloud Software Components The System Landscape Directory and SAP Business One Cloud Control Center The System Landscape Directory (SLD) is formed of a service that provides information about the landscape components and their settings. And also a database that stores all of the relevant information about the SAP Business One Cloud Landscape. The SAP Business One Cloud Control Center provides a HTML5 based interface for managing the components in the SAP Business One Cloud Landscape. The SLD Agent Service The SLD Agent Service performs various tasks on behalf of the SLD, such as installing an SAP Business One client or performing database upgrades. It should be installed on any server in the landscape that will host an SAP Business One or SAP Business One Cloud Software component. The SLD Agent Service install can be configured to be deployed as part of a Group Policy Object. Include the UAP install SAP Business One Cloud Landscape Workshop: Section SAP AG. All rights reserved. 28

29 Installing the SAP Business One Cloud Software Components The SAP Business One Cloud User Access Portal The SAP Business One Cloud User Access Portal is an example portal that you can use as a template to create your own customized portal. It is a customized version of the Remote Desktop Web Portal, with SAP Business One branding and the inclusion of: Single Sign-on Trial Request functionality SAP Business One Cloud Landscape Workshop: Section SAP AG. All rights reserved. 29

30 Exercise In Building the SAP Business One Cloud Landscape: Complete section 4.1 to create a new SAP Business One software repository using the provided SAP Business One download. Complete section 4.2 to install the SAP Business One License Server and SAP Business One Mailer Complete section 4.3 to install the SAP Business One Cloud Control Center Complete section 4.4 to install the SAP Business One Cloud SLD Agent Complete section 4.5 to install the SAP Business One Cloud User Access Portal SAP Business One Cloud Landscape Workshop: Section SAP AG. All rights reserved. 30

31 Installing the SAP Business One Cloud Software Components Configure the Registry Settings for SAP Business One Cloud For the SAP Business One Cloud Landscape to function correctly each machine needs two settings in the registry to be configured Hosting This indicates to SAP Business One that this is an OnDemand implementation of the application and modifies certain behaviours accordingly. For instance this triggers the use of single sign on to SAP Business One Cloud, so that the user is not prompted for their login credentials when they access the system. SLDAddress This tells the SAP Business One Cloud SLD Agent where to find the server that is hosting the SAP Business One Cloud SLD Service so that it can communicate with it. We could manually create these registry keys on all required machines but this soon becomes impractical and prone to error as the landscape scales. Alternatively we can use a Group Policy Object (GPO) to distribute these settings to the required machines using Administrative Templates. SAP Business One Cloud Landscape Workshop: Section SAP AG. All rights reserved. 31

32 Exercise In Building the SAP Business One Cloud Landscape: Complete section 4.6 to ensure all servers are correctly configured for the SAP Business One Cloud Landscape. SAP Business One Cloud Landscape Workshop: Section SAP AG. All rights reserved. 32

33 Installing the SAP Business One Cloud Software Components Microsoft Office Integration There are actually a number of different alternatives for working with Microsoft Office, you need to evaluate which approach is the best for you: SAP Business One Outlook Integration is not supported. Install Microsoft Office on the Remote Desktop Session Hosts Ability to open Excel and Word documents from SAP Business One within the cloud landscape Additional cost to be considered. Install OpenOffice on the Remote Desktop Session Hosts Ability to open Excel and Word documents from SAP Business One within the cloud landscape Use the Microsoft Excel Integration solution from SAP Uses WebDav to share files back to the user s local machine and open the Excel document there. Some limitations in larger landscapes. Requires registry changes and also a small program to be installed on the user s local machine. (Can be done via GPO) Use Drive Mapping Allows users to store the exported document from SAP Business One Cloud to a folder that is on their local machine. They can then manually open it from there SAP Business One Cloud Landscape Workshop: Section SAP AG. All rights reserved. 33

34 Exercise In Building the SAP Business One Cloud Landscape: Complete section 4.7 to configure the landscape to use WebDav to provide Microsoft Office Integration SAP Business One Cloud Landscape Workshop: Section SAP AG. All rights reserved. 34

35 Summary In this section we have: Prepared the cloud infrastructure for use as a SAP Business One Cloud landscape including: Active Directory Remote Desktop Services Microsoft SQL Server Installed the core SAP Business One Cloud components ready for configuration in the next step. SAP Business One Cloud Landscape Workshop: Section SAP AG. All rights reserved. 35

36 2013 SAP AG. 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 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, Excel, Outlook, PowerPoint, Silverlight, and Visual Studio are registered trademarks of Microsoft Corporation. IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System z10, z10, z/vm, z/os, OS/390, zenterprise, PowerVM, Power Architecture, Power Systems, POWER7, POWER6+, POWER6, POWER, PowerHA, purescale, PowerPC, BladeCenter, System Storage, Storwize, XIV, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, AIX, Intelligent Miner, WebSphere, Tivoli, Informix, and Smarter Planet are trademarks or registered trademarks of IBM Corporation. Linux is the registered trademark of Linus Torvalds in the United States and other countries. Adobe, the Adobe logo, Acrobat, PostScript, and Reader are trademarks or registered trademarks of Adobe Systems Incorporated in the United States and other countries. Oracle and Java are registered trademarks of Oracle and its affiliates. 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. Apple, App Store, ibooks, ipad, iphone, iphoto, ipod, itunes, Multi-Touch, Objective-C, Retina, Safari, Siri, and Xcode are trademarks or registered trademarks of Apple Inc. IOS is a registered trademark of Cisco Systems Inc. RIM, BlackBerry, BBM, BlackBerry Curve, BlackBerry Bold, BlackBerry Pearl, BlackBerry Torch, BlackBerry Storm, BlackBerry Storm2, BlackBerry PlayBook, and BlackBerry App World are trademarks or registered trademarks of Research in Motion Limited. Google App Engine, Google Apps, Google Checkout, Google Data API, Google Maps, Google Mobile Ads, Google Mobile Updater, Google Mobile, Google Store, Google Sync, Google Updater, Google Voice, Google Mail, Gmail, YouTube, Dalvik and Android are trademarks or registered trademarks of Google Inc. INTERMEC is a registered trademark of Intermec Technologies Corporation. Wi-Fi is a registered trademark of Wi-Fi Alliance. Bluetooth is a registered trademark of Bluetooth SIG Inc. Motorola is a registered trademark of Motorola Trademark Holdings LLC. Computop is a registered trademark of Computop Wirtschaftsinformatik GmbH. SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP BusinessObjects Explorer, StreamWork, SAP HANA, 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 other countries. Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects Software Ltd. Business Objects is an SAP company. Sybase and Adaptive Server, ianywhere, Sybase 365, SQL Anywhere, and other Sybase products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Sybase Inc. Sybase is an SAP company. Crossgate, m@gic EDDY, B2B 360, and B2B 360 Services are registered trademarks of Crossgate AG in Germany and other countries. Crossgate is an SAP company. 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. The information in this document is proprietary to SAP. No part of this document may be reproduced, copied, or transmitted in any form or for any purpose without the express prior written permission of SAP AG. SAP Business One Cloud Landscape Workshop: Section SAP AG. All rights reserved. 36