Provisioning customer tenants in the SAP Business One Cloud Landscape SAP Business One Cloud Landscape Workshop
Section Objectives
This section of the course will enable you to: Provision customers in the SAP Business One Cloud landscape Manage users in the SAP Business One Cloud landscape Manage and deploy extensions in the SAP Business One Cloud landscape
© 2013 SAP AG. All rights reserved.
2
The SAP Business One Cloud Customer Journey
Trial/Purchase
Maintenance & Upgrades
License
Operation & Support
Provision
Extend © 2013 SAP AG. All rights reserved.
3
Customers, Tenants and Users Windows Domain Users
Customer Customer Tenant Tenant
Tenant Tenant
SAP Business One Cloud Standard Users
Tenant Tenant
SAP Business One Cloud Power Users
Customer Tenant
Customer Users
SAP Business One Cloud Super Users
Tenant
Customer Customer
Tenant Tenant
Partner Users
© 2013 SAP AG. All rights reserved.
Tenant Tenant Tenant Tenant
SAP Business One Cloud Partner Support Users SAP Business One Cloud Operators
Tenant
Customer Tenant
Tenant Tenant
4
Naming Conventions
Think about the naming conventions that you want to use within your SAP Business One Cloud Landscape: Tenants
•
• • •
Follow SQL Server guidelines for character restrictions in database names Think about security and integrity of the data, keep the names of the databases not the actual names of the companies whose data they contain. Create a convention that includes an indicator for the type of tenant
Users
•
• • • • •
Users present their own challenge Unless you do some custom work currently a user cannot log in with their email address Username must be a domain name in windows active directory SAP Business One usernames are currently limited to 8 characters How long before you have John Smith, John Doe, John Fiedler as users in the landscape? Difficult to use actual names
© 2013 SAP AG. All rights reserved.
5
SAP Business One Cloud License Types
License Name SAP Business One Professional User for SAP B1 Cloud SAP Business One Limited Financial User for SAP B1 Cloud SAP Business One Limited Logistic User for SAP B1 Cloud SAP Business One Limited CRM User for SAP B1 Cloud SAP Business One Integration Framework for SAP B1 Cloud SAP Business One Indirect Access User for SAP B1 Cloud SAP Business One Starter Package User for SAP B1 Cloud License Requirements and Licensing Rules: •
One (1) SAP Business One Starter Package User or one (1) SAP Business One Professional User per installation.
•
No limitation on maximum number of users
•
Additional users may only be ordered in packages of 1 User per customer/end user
Important Note: Not all SAP Business One on premise license types are available on the SAP Business One Cloud price list. For complete information please check the SAP Business One Cloud Price List © 2013 SAP AG. All rights reserved.
6
Demonstration
Provisioning a new customer and default tenant
© 2013 SAP AG. All rights reserved.
7
Exercise
Provision a new customer in your SAP Business One Cloud Landscape •
Create a fictitious customer
•
Use the provided license
•
Create and assign a user (don’t forget to create the user in the customer group in Active Directory first)
•
Create a new tenant (using a blank localization database)
Further information to assist you in the completion of this exercise can be found in the SAP Business One Cloud Administrator Guide
© 2013 SAP AG. All rights reserved.
8
SAP Business One Extensions
Why not SAP Business One add-ons? Compatible SAP Business One add-ons
•
•
Add-ons which don’t have fully automated lifecycle management for use in SAP Business One Cloud environments Manual installations and configuration Partial configuration in the SAP Business One Cloud Control Center
• •
Add-ons for lightweight deployment
•
•
Fully compliant add-on certified by SAP •
Fully automated lifecycle management for use in SAP Business One Cloud environments
•
Complete technical configuration of add-ons through the SAP Business One Cloud Control Center
•
Fully compliant add-on certified not by SAP •
All of the above benefits but not certified because they are not being distributed to a wide audience of partners (e.g. this are partner developed add-ons typically)
SAP Business One Script
•
•
Lightweight, JavaScript based extension system that can be used with SAP Business One Cloud to rapidly adapt SAP Business One for a customer’s needs
© 2013 SAP AG. All rights reserved.
9
What should you think about when running an on-premise add-on in SAP Business One Cloud? Application Servers are shared by multiple customers •
There can be multiple application servers in one service unit, they all have to be identical.
•
You cannot store information on an application server: • •
User specific information into their roaming folder Add-on information stored in the add-on’s shared folder
SAP Business One Shared Folder •
The SAP Business One Shared Folder (B1_SHR) does not exist in the SAP Business One Cloud environment
© 2013 SAP AG. All rights reserved.
10
What should you think about when running an on-premise add-on in SAP Business One Cloud? Connection to the Common and Tenant Databases is based on trusted authentication •
Users may no longer know a username/password to log on to the DB
DI-API only add-ons are not managed by the SAP Business One Cloud Control Center at the moment •
Cannot be fully compliant as they need manual involvement to deploy within the SAP Business One Cloud landscape
Click for more information on SAP Business One Cloud Add-ons
© 2013 SAP AG. All rights reserved.
11
SAP Extensions in the SAP Business One Cloud Landscape SAP Add-ons are automatically deployed in the cloud landscape, these include: •
Payment Engine
•
Intrastat
•
Datev
•
Fixed Assets
•
EFM Format Definition
•
Screen Painter
•
XLReporter
•
ELSTERLW
•
SBO Script
© 2013 SAP AG. All rights reserved.
12
The Lightweight Deployment Model
The Lightweight Deployment Model was developed for SAP Business One Cloud and is available for fully compliant SAP Business One Cloud add-ons
Benefits: •
Automate add-on lifecycle management without user interaction
•
No service unit downtime
•
Supports deployment of multiple add-on versions within the same SAP Business One Cloud service unit
•
Auxiliary Property – configure add-ons within the SAP Business One Cloud Control Center by Tenant, Service Unit and Data Center
© 2013 SAP AG. All rights reserved.
13
Managing non-SAP Extensions in the SAP Business One Cloud Landscape Non-SAP extensions are managed in a specific extension repository Repositories can be set up to allow 3rd party access via (e.g. the extension provider via FTP) to upload new versions of the extension for automatic synchronization of versions. For an extension to be made available the following needs to happen: 1.
Synchronize the extension in the repository.
2.
Deploy the extension to a Service Unit
3.
Assign the extension to a Tenant
Multiple versions of lightweight add-ons can exist in one Service Unit (to be used across different Tenants)
© 2013 SAP AG. All rights reserved.
14
Demonstration
Overview of extensions and provisioning an extension to a tenant
© 2013 SAP AG. All rights reserved.
15
Exercise
Using the provided lightweight deployment demonstration extension: 1.
Create the required repository structure
2.
Synchronize, deploy and assign the extension to a tenant
3.
Test your extension
Further information to assist you in the completion of this exercise can be found in sections 3, 4, 5 and 6 of Managing Extensions in the SAP Business One Cloud Landscape.
© 2013 SAP AG. All rights reserved.
16
Introducing SAP Business One Script
SAP Business One Script is a lightweight, JavaScript-based extension system that you can use to quickly adapt SAP Business One to business-specific processes in on-demand environments. Benefits: •
Sandboxed, with managed access to system functionality (unlike traditional addons)
•
Quickly develop solution to address last mile extensibility for the customer
•
No need for add-on certification
Click for more information on working with SAP Business One Script
© 2013 SAP AG. All rights reserved.
17
SAP Business One Script Technical Architecture
© 2013 SAP AG. All rights reserved.
18
Deploying and using SAP Business One Script
First deploy the SAP Business One Script extension: •
Ensure that the SAP Business One Script is deployed to the required Service Unit in the Cloud Control Center
•
Deploy SAP Business One Script to the required Tenant
•
Enable the SAP Business One Script add-on in the SAP Business One Client (this can only be done by a super user). • •
Administration Add-ons Add-on Manager Installed Add-ons tab, start SBOScript.
•
Ensure that Google Chrome or Mozilla Firefox on the presentation server(s) is installed to allow for JavaScript debugging of extensions
•
Ensure that users have an SDK Tools license
© 2013 SAP AG. All rights reserved.
19
Managing SAP Business One Scripts
Use the Script Manager window in SAP Business One to manage scripts: •
Administration
Extension Management
Script Manager
The creation of new scripts is beyond the scope of this workshop but further information can be found in the Working with SAP Business One Script guide. © 2013 SAP AG. All rights reserved.
20
Demonstration
Deploying, enabling and importing a SAP Business One Script extension
© 2013 SAP AG. All rights reserved.
21
Exercise
Using the provided SAP Business One Script demonstration extension: 1.
Deploy SAP Business One Script to a Service Unit
2.
Assign the extension to your tenant
3.
In SAP Business One enable SAP Business One Script then using the Script Manager import and activate the demonstration script
4.
Test your SAP Business One Script
Further information to assist you in the completion of this exercise can be found in Working with SAP Business One Script.
© 2013 SAP AG. All rights reserved.
22
Summary
In this section we have: •
Learnt how to provision customers, tenants and users into the SAP Business One Cloud Landscape.
•
Learnt about the different types of extensions for SAP Business One Cloud and considered the implications of running add-ons in the cloud
•
Gained an understanding of the new SAP Business One Script extensions and how to work with them in a SAP Business One Cloud Landscape
© 2013 SAP AG. All rights reserved.
23
© 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.
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.
Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems Inc.
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.
HTML, XML, XHTML, and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts Institute of Technology.
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.
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.
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.
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.
© 2013 SAP AG. All rights reserved.
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.
24
Avatars
© 2013 SAP AG. All rights reserved.
25
