BI Admins become Landlords - UK & Ireland SAP Users Group · PDF fileReal-World BI Platform...

BI Admins become "Landlords" : Real-World BI Platform Multi-Tenancy Deployment for Shared-Services,

Charge-Back & Infrastructure-Consolidation

Overview As most major companies and public-sector organizations are asked to "Do More, Do it Better & Do it with Fewer Resources" they are embracing the IT Management concepts of Shared-Services, Charge-Back & Infrastructure-Consolidation. How will these CIO-level directions impact your current and future deployments of the SAP BO-BI 4.1 platform, and how can you "Future-Proof" your environment(s) to accommodate their demands...? The SAP BO-BI 4.1 platform now includes a "Multi-Tenancy" manager option in the CMC which allows for much greater control of your environment at a new TENANT level, which sits above the GROUPS and USERS hierarchy that BI Admins are used to managing. This session will discuss some different Multi-Tenancy options, scenarios and their appropriate use-cases, plus an actual "Real World" use of Multi-Tenancy Concurrent-User controls to manage Charge-Back and Resource-Availability in a SAP BO-BI 4.1 (Production) environment which support more that Fifty (50) different Applications and Lines-of-Business.

Learning Points • The Corporate pressures that will demand Multi-Tenancy

solutions.

• Setting-up Basic Multi-Tenancy scenarios for the SAP BO-BI 4.1 platform in the CMC.

• A "Real World" use of Multi-Tenancy Concurrent-User controls to manage Charge-Back and Resource-Availability.

Why should we listen to this guy…? • Mark J. Richardson (Independent Consultant) • 17+ years of Crystal Reports and Business Objects experience starting

from Crystal 7.5 and Seagate Info. • Focus on high-volume Operational and Transactional reporting

deployments. • Ramp-Up Deployment for SAP BO-BI 4.1 (1st Ten World-Wide) • Designed and Deployed a number of SAP Business Objects Enterprise

architectures for different Real-World clients in a number of different sectors…

Know my audience (Who is attending this session..?) Show of Hands

Never used SAP Business Objects…? Some experience with SAP Business Objects..? Many Years of experience with SAP Business Objects..?

End-Users…? Administrators…? Architects…?

Business Objects Enterprise XI (R2)…? [Not Supported] Business Objects Enterprise 3.0/3.1…? SAP Business Objects Platform 4.0/4.1…?

Multiple PROD deployments of SAP BO-BI…? Need to Consolidate Platforms or Hardware…? Providing SAP BO-BI services to many Clients / Dept / LoBs…?

What is Multi-tenancy…? • Multitenancy is the enhanced ability to

have multiple user entities (eg. companies, departments, teams etc.) share a Single BOE environment without them being aware of the other entities.

• Hotel / Landlord / Administrator.

• Single-Room and/or VIP suites.

What is Multi-tenancy…? • Multitenancy is not a new concept, but

until now BOE administrators were forced to custom-create the structure(s) in the BOE environments by hand.

GROUP USER

What is Multi-tenancy…? • Multitenancy is not a new concept, but

until now BOE administrators were forced to custom-create the structure(s) in the BOE environments by hand.

TENANT (*Optional)

GROUP USER

What is Multi-tenancy…? • IMPORTANT : A User can belong to

multiple Groups, but a User can ONLY belong to ONE (1) Tenant.

TENANT (*Optional)

GROUP USER

Why do we need Multi-Tenancy in BOE…?

• Platform Migration & Consolidation.

• Corporate Mergers & Acquisitions.

• 3rd Party BOE Service Provider (OEM, etc)

Platform Migration & Consolidation

HR FINANCE

Shared-Platform

Business

Objects

Enterprise

XI (R2)

Business

Objects

Enterprise

(3.1)

SAP Business

Objects

BI 4.1

Corporate Mergers & Acquisitions

A B C

Shared-Platform (A, B & C)

Business

Objects

Enterprise

(3.1)

SAP Business

Objects

BI 4.1

Business

Objects

Enterprise

(3.1)

SAP Business

Objects

BI 4.1

Shared-Services Mandate

• Shared-Services Mandate.

• Reducing Hardware & Data Centre Costs.

• 3rd Party BOE Service Provider (OEM, etc)

Deployment Options in SAP BO-BI 4.1

• Stand-Alone Hardware • Stand-Alone BOE • Nothing Shared

• Shared / VM Hardware • Stand-Alone BOE • Hardware Resource

Sharing Only

• Shared Hardware • Shared BOE • Shared Services • eg. BOE “Private Cloud”

Data Storage and Schema

Tenant Provisioning Tool

Applies to SAP BusinessObjects BI 4.0 SP4

© 2014 SAP SE or an SAP affiliate company. All rights reserved. 18 Public

Tenant Provisioning Tool – Tenant Onboarding Process

Tenants in a multi-tenants system have structural similarity. Tenant templates serve as model to manage tenants in a well defined and repeatable manner.

Create an exemplar tenant in the system: Do once for all tenants Using standard tools such as CMC and Universe designer Run the Command line tool to add a new tenant

SAP BI 4.0 SP4


Tenant Provisioning Tool – Automatable Operations

Operations automated by the tenant provisioning tool Creating user groups Creating folders Setting ACL (Access Control List) on folders Copying documents and universes from template folder to individual tenant folder Adding universe restrictions for UNV only Creating connections

Materializing tenant objects from template

SAP BI 4.0 SP4


Tenant Provisioning Tool – Tenant Template Definition File

Tenant template definition file describes the location of tenant template, and specifies run time options

tenantName=CompanyABC

templateToken=$TenantTemplate$

templateContentFolder =$TenantTemplate$_;

templateUniverseFolder =$TenantTemplate$

templateConnectionFolder =$TenantTemplate$

templateCategoryFolder =$TenantTemplate$

templateEventFolder=/Custom Events/ $TenantTemplate$;

optionIncludeUniverses=false

optionIncludeConnections=false

optionIncludeCategories=true

optionIncludeEvents=true

optionIncludeAccessLevels=true

optionUseSharedUniverses=false

Just an extract!

SAP BI 4.0 SP4


Tenant Provisioning Tool – Provisioning

After a tenant is created, the standard content (documents, universe, connection) can still undergo changes. New stock BI documents made available to tenants Changes to stock BI documents Changes to stock universe

The tool does not handle the situation where a content copied to the tenant is modified by the tenant

itself as well as by the central provider. In this case the tool would not attempt any merging of changes from two paths.

SAP BI 4.0 SP4


Tenant Provisioning Tool – Tenant Template

Template Folders

Template Documents

User Group templates

SAP BI 4.0 SP4


Tenant Provisioning Tool – Run time

Tenant_template_def.properties

SAP BI 4.0 SP4



You run the tenant provisioning tool from the Command Prompt.

When done it shows you what it created.

SAP BI 4.0 SP4



Your Access Levels content before running the tenant provisioning tool.

Your Access Levels content after running the tenant provisioning tool.

SAP BI 4.0 SP4



Tenant specific content

SAP BI 4.0 SP4


Tenant Provisioning Tool - Supported Document Scenarios

Direct to data: – CR – CR4Ent Shared database and semantic layer

– CR4Ent connected to single-source unx, pquery and BICS – WebI connected to unv including

universe restriction overload – WebI connected to single-source unx, BICS (as of 4.1) Separate database with distinct semantic layer

– CR4Ent connected to single source unx – WebI connected to unv and single-source unx (as of 4.1.) Separate database with shared semantic layer

– WebI connected to unv using universe connection overload

SAP BI 4.0 SP4/ SAP BI 4.1

Tenant definition in CMC

Applies to SAP BusinessObjects BI 4.1


Tenant definition in CMC (1/4)

Tenants that were onboarded via the tenant onboarding command line tool are now visible in a new Multitenancy tab in the CMC

SAP BI 4.1



Ability to change tenant properties such as tenant name, concurrent user limit and associated user groups

SAP BI 4.1



Ability to see which user or user group belongs to which tenant New Tenant column is filterable

–

SAP BI 4.1



Ability to delete a tenant and all its associate infoobjects with the option to exclude certain infoobjects

SAP BI 4.1

Limitation on concurrent logons per tenant Applies to SAP BusinessObjects BI 4.1


Limitation on concurrent logons per tenant (1/2)

Ensure service availability by limiting the number of concurrent users that a tenant can logon at a given time. Once the tenant's limit has been reached no further tenant’s users will be able to log on until another

tenant's user has logged out.

SAP BI 4.1


Limitation on concurrent logons per tenant (2/2)

Ability to set concurrent user limit at tenant onboarding time in the tenant definition file or via CMC UI

# (Mandatory) Name of the tenant being added.

tenantName=XYZ

# (Mandatory) Template token identifier used for tenant name replacing

templateToken=$Tenant_Template$

# (Optional) Number of concurrent users allowed for the tenant being # added. Defaults to -1 meaning unlimited in which

# case the number of concurrent users for this tenant will only be # limited by what the BOE license key allows

# for the entire system. When not specified, this option will be set to # default during the tenant's first on-board,

# or unchanged during tenant's provisioning.

# - Tenant specific info

tenantConcurrentUserLimit=100

SAP BI 4.1

Tenant ID in auditing record

Applies to SAP BusinessObjects BI 4.1


Tenant ID in auditing record

Ability to track system usages by tenant using auditing functionality – Applications can include tenant billing that depends on resources utilization. – For example, the following metrics can be used for billing: number of logons by a tenant, number of

report views or refreshes, etc. Enable and configure auditing events that you are interested it. To determine which auditing event is generated by which tenant use 2 new lookup tables in the

auditing database: ADS_TENANT and ADS_USER

SAP BI 4.1


New Tables

ADS_TENANT table:

ADS_USER table:

Joins should be performed between: ADS_TENANT.Tenant_ID and ADS_USER.Tenant_ID ADS_USER.User_ID and ADS_EVENT.User_ID ADS_TENANT.Cluster_ID and ADS_CLUSTER_Cluster_ID ADS_USER.Cluster_ID and ADS_CLUSTER_Cluster_ID

Cluster_ID Tenant_ID Tenant_Name AWNaY20WHpGok DNah47WHhsKZ Company A

Cluster_ID Tenant_ID User_ID User_Name AWNaY20WHpGok DNah47WHhsKZ SBUn83SZOw_91 John McGreg

SAP BI 4.1

Learning Points • The Corporate pressures that will demand Multi-Tenancy

solutions.

• Setting-up Basic Multi-Tenancy scenarios for the SAP BO-BI 4.1 platform in the CMC.

• A "Real World" use of Multi-Tenancy Concurrent-User controls to manage Charge-Back and Resource-Availability.

External Resources • SAP [SCN] Overview of SAP BI 4.x Multitenancy

Management Tool http://scn.sap.com/community/bi-platform/blog/2013/06/18/overview-of-sap-bi-4x-

multitenancy-management-tool

• SAP [SCN] BI Suite Official Product Tutorials (4.1 Platform – workflows, etc.)

http://www.sdn.sap.com/irj/scn/bi-platform-elearning?refer=main

• @ASUG_BI https://twitter.com/asug_bi

http://scn.sap.com/community/bi-platform/blog/2013/06/18/overview-of-sap-bi-4x-multitenancy-management-tool








https://twitter.com/asug_bi

https://twitter.com/asug_bi

41

• Q and A

• Contact Information Mark J. Richardson

Rose-Richardson Enterprises, Inc. Toronto, Ontario, Canada

[email protected]

Connect to me on LinkedIn http://ca.linkedin.com/pub/mark-richardson/20/a66/701

Follow us on Twitter….

@ASUG_Ontario

mailto:[email protected]

http://ca.linkedin.com/pub/mark-richardson/20/a66/701

BI Admins become Landlords - UK & Ireland SAP Users Group · PDF fileReal-World BI Platform...

Documents

Transcript of BI Admins become Landlords - UK & Ireland SAP Users Group · PDF fileReal-World BI Platform...