(lmbi) guide businessobjects business intelligence

PUBLICSAP BusinessObjects Business Intelligence platformDocument Version: 4.2 Support Package 7 – 2020-06-12

License Measurement Tool for SAP BusinessObjects Business Intelligence Platform (LMBI) Guide

© 2

020

SAP

SE o

r an

SAP affi

liate

com

pany

. All r

ight

s re

serv

ed.

THE BEST RUN

Content

1 Document History. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

2 Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62.1 What is the LMBI?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62.2 Additional Documents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62.3 Process Overview and System Landscape. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Measurement Components Read Raw Data from the Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . 7Consolidation Component Evaluates and Merges the Measurements Based on Provided Contractual Counting Rules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

2.4 Which Systems Require Measurement?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82.5 Shipments. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82.6 Limitations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Limitations of the Measurement Component. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8Limitations of the Consolidation Component. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

3 Measurement Component. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .103.1 General Installation Comments and Recommendations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103.2 Preparative Steps to the Measurement. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Third-party Authentication. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10Finding Disabled or Expired Users with Authentication Method SAP R/3/ SAP. . . . . . . . . . . . . . . 12Increase the memory settings for large installations (> 40,000 users). . . . . . . . . . . . . . . . . . . . . 12Estimates on the Measurement Runtime. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13Required Administration Rights for User that Runs LMBI Tool. . . . . . . . . . . . . . . . . . . . . . . . . . . 14

3.3 Installing and Running the BI 4.X Measurement Component. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16Version Numbers and How to Install LMBI Patches. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16Checking the Java Runtime Version. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16Measuring SAP BusinessObjects BI platform 4.x Systems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

3.4 Installing and Running the Measurement Components for XI 3 and XI R2. . . . . . . . . . . . . . . . . . . . . 24How to Get the XI3 and XI R2 Measurement Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24Summary. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24Version Numbers (such as 3.0.34) and How to Install LMBI Patches. . . . . . . . . . . . . . . . . . . . . . 24Checking the Java Runtime Version. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24Measuring SAP BusinessObjects BI platform XI 3.x and XIR2 systems. . . . . . . . . . . . . . . . . . . . 25

3.5 Installing and Running the Measurement Components for BOE 5.1 and BOE 6.5. . . . . . . . . . . . . . . . 32How to Get BOE 5.1 and BOE 6.5 Measurement Components . . . . . . . . . . . . . . . . . . . . . . . . . . 32Measuring SAP BusinessObjects 5.x/6.x Systems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

2 PUBLIC


Content

3.6 Special Adjustments & Exception Handling. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37How to Read the Settings for the CMS and the Request Port in the CMS. . . . . . . . . . . . . . . . . . . 37Full Control for Everyone on Windows 7 on Installation Folder. . . . . . . . . . . . . . . . . . . . . . . . . . . 37Exception Handling. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38How to Identify and Solve a Connection Issue. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

3.7 Requesting Technical Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 403.8 How User Rights Classify Users?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

User Rights Relevant for SAP BusinessObjects Business Intelligence Platform 4.x. . . . . . . . . . . . 41User Rights Relevant for BusinessObjects Enterprise Platform XI 3.x and XIR 2. . . . . . . . . . . . . . 42User Rights Relevant for BusinessObjects Enterprise Platform 5.1.x and 6.x. . . . . . . . . . . . . . . . 43

3.9 CPU Metrics - Where to Find Required Data?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43BI System in Virtual Machines – Find the Required Data in the Hypervisor. . . . . . . . . . . . . . . . . . 43Find the CPU Data in the Operating System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47Find the CPU Data for Physical Deployments. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49Further CPU Data Options for Clustered BI Servers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

4 Consolidation Component. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 524.1 Installation and Folder Structure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 524.2 Install LMBI Patches / Updates of the Consolidation Component. . . . . . . . . . . . . . . . . . . . . . . . . . 524.3 Start the Consolidation Component. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Start and Log Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53Data Store Location. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53Preferences. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .53Running the Consolidation Component on Machine with Older JAVA Version (<JDK 1.6). . . . . . . . 54

4.4 Steps Inside the Consolidation Component. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54Step 1.2: View and Import System Measures. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54Step 1.3: View and Import Contract/Licenses. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55Step 2.1: Assign System Measures to License. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56Step 3.1: Group and Consolidate. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57Step 3.2: View Results. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

4.5 Sending LMBI Results to SAP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 604.6 Multiple Consolidations at Different Enterprise Levels - From Subsidiaries to Corporate Results

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .604.7 Requesting Technical Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

5 Optimizing User Licenses by Merging Audit Results of SAP BusinessObjects BI Platform and SAP classic (ABAP-based systems) in the LAW. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

5.1 LMBI's Scalability Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 625.2 What are the Benefits of Merging Results Inside LAW?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 625.3 Required Patch and Service Pack Stack Levels. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .635.4 How to Match User IDs of SAP BusinessObjects BI Platform & SAP Classic Systems. . . . . . . . . . . . . 645.5 How to Load LMBI Results into LAW. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

License Measurement Tool for SAP BusinessObjects Business Intelligence Platform (LMBI) GuideContent PUBLIC 3

Grouping and Consolidating Users in LMBI is a Prerequisite. . . . . . . . . . . . . . . . . . . . . . . . . . . . 65Choose the Correct LMBI Result File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66LAW 2.0: Import LMBI Result File into LAW 2.0. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66LAW 1.0: Convert the LMBI Result File into a Text File Compatible with LAW 1.0. . . . . . . . . . . . . . 66LAW 1.0: Import the Converted LMBI Result File into LAW 1.0 and Consolidate. . . . . . . . . . . . . . . 67

6 Security Guide & Privacy Aspects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .686.1 Data Measured at Customer Side. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .686.2 Data Sent to SAP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

7 Frequently Asked Questions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

8 Abbreviations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

4 PUBLIC


Content

1 Document History

Version Date Change

14.2.7 2019-02-28 ● Updated the topic General Installation Comments and Recommendations [page 10]

● Added a note in the following topics:○ Checking the Java Runtime

Version [page 24] for installing and running BI 4.x measurement component.

○ Checking the Java Runtime Version [page 24] for installing and running measurement components for XI 3 and XI R2.

○ Where to Install the Measurement Component? [page 32]

○ Installation and Folder Structure [page 52]

License Measurement Tool for SAP BusinessObjects Business Intelligence Platform (LMBI) GuideDocument History PUBLIC 5

2 Introduction

2.1 What is the LMBI?

The License Measurement tool for SAP BusinessObjects Business Intelligence platform (LMBI) provides measurement functionality to calculate and evaluate the main set of licenses sold for the SAP BusinessObjects BI platform in the large enterprise market segment in approximately the last decade. LMBI allows you to extract the license audit information from the BI Platform server(s) easily. LMBI can be used by customers for self-evaluations or in audits requested by the software vendor. This guide takes you through all the required steps of the license measurement and tells you which files you need for the evaluation.

LMBI contains a measurement and a consolidation component. The provided measurement component is a standalone Java client. The corresponding measurement components exist to address the different versions of the SAP BusinessObjects Business Intelligence Platforms. The measurement components will read deployed license keys, the defined users with their user rights and some server metrics. Based on the user rights, it will classify each user to certain categories, such as editor or viewer for Web Intelligence.

The measurement components save the results in XML files which starting with the prefix “measure”. These files are required to compute the audit result.

When license is in use which is also relevant for classical SAP NetWeaver/SAP Business Suite systems, consolidated LMBI results can additionally be loaded into the ABAP-based License Administration Workbench (LAW, version 1.0 and 2.0).

The tool follows a conservative approach. The set of licenses examined is limited to those that can be measured in a pragmatic way. License terms may still require more extensive licenses than those indicated in the tool result. As the license measurement may cause some additional load on the system, you may consider running the license measurement out of times with system peak loads.

2.2 Additional Documents

While this guide focuses on the handling of the LMBI itself, you can find more information on license measurements in the corresponding section of the SAP Support Portal . The information there also includes a presentation Map User Rights to Licenses in LMBI.

6 PUBLIC


Introduction

http://help.sap.com/disclaimer?site=https%3A%2F%2Fsupport.sap.com%2Fen%2Fmy-support%2Fsystems-installations%2Fsystem-measurement%2Fbusinessobjects-bi-measurement.html

2.3 Process Overview and System Landscape

2.3.1 Measurement Components Read Raw Data from the Server

The measurement component is a Java client that can connect to a SAP BusinessObjects BI/ Enterprise platform to run a standardized license measurement. The technical specifications of different versions of the SAP BusinessObjects BI/Enterprise platform are covered by the corresponding measurement components.

The measurement components read the deployed license keys, the defined users with their user rights and attributes, some server metrics, and counts the documents per type and authorship. Based on the user rights, it assigns each user to usage categories which are described in detail in the provided Map User Rights to Licenses in LMBI documentation (see 1.2). The measurement results are saved in XML files that have to be provided to the consolidation component.

As the license measurement may cause some additional load on the system, you can consider running the license measurement out of times with system peak loads.

2.3.2 Consolidation Component Evaluates and Merges the Measurements Based on Provided Contractual Counting Rules

The consolidation component is a stand-alone tool to calculate the number of required licenses. Therefore, it requires contractual information to evaluate the measurements. This information is provided with each license audit request in form of a customer specific contract file and without such a file, no result can be calculated. In the LMBI tool, the sample contract files are available for testing purpose.

License Measurement Tool for SAP BusinessObjects Business Intelligence Platform (LMBI) GuideIntroduction PUBLIC 7

2.4 Which Systems Require Measurement?

Generally, all systems at customer side running an SAP BusinessObjects BI Platform/Enterprise (or Crystal Reports) server requires measurement with the LMBI tool. This does not only refer to the productive systems, but also to any other system, irrespective of its purpose of use like test or development. The consolidation component and SAP’s license auditors consider the contractual obligations including the terms if, which and how many licenses you require for non-productive systems.

2.5 Shipments

Starting with BI 4.2 SP06, LMBI is by default included in the shipment of the BI platform. The required file LMBI.zip can be found in the BusinessObjectsServer Collaterals\lmbi folder. LMBI is also available in patch builds Collaterals/lmbi folder for use. This standard shipment contains a measurement component which supports all BI 4.x versions, the consolidation component and generic contract files.

For cases with ended maintenance, particularly older BI platform versions with ended mainstream maintenance, a different version for the LMBI.zip is in place in a restricted shipment which includes additional measurement components for XI 3, XIR2 and versions BOE 5 and 6. To get this restricted shipment, create a corresponding incident on support component BI-BIP-LMT.

2.6 Limitations

2.6.1 Limitations of the Measurement Component

The current version of LMBI comes with a few limitations described here.

Limitations of the Measurement Component

The list below comprises of different versions of the SAP Analytics' products that support the measurement component.

● SAP BusinessObjects BI Platform 4.2*● SAP Crystal Server 2016● SAP BusinessObjects BI Platform 4.1*● SAP Crystal Server 2013● SAP BusinessObjects BI Platform 4.0 FP3*● SAP BusinessObjects BI Platform 4.0*

8 PUBLIC


Introduction

http://help.sap.com/disclaimer?site=https%3A%2F%2Flaunchpad.support.sap.com%2F%23%2Fincident%2Fcreate

● SAP Crystal Server 2011● BusinessObjects Enterprise XI 3.1*● BusinessObjects Enterprise XI 3.0*● BusinessObjects Enterprise XI R2(a)● BusinessObjects Enterprise 6.x● BusinessObjects Enterprise 5.1.x

NoteApart form 4.x LMBI measurement component, other measurement components fail to connect to the server remotely, you need to run the LMBI measurement component on the same box where the server is installed.

All SSL LMBI measurement components should run on the same box where the server is installed.

The starred versions of the BI platform includes the corresponding SAP BusinessObjects BI Platform, Edge edition.

2.6.2 Limitations of the Consolidation Component

Up-to-date Java (required version is minimum 1.6.0_04)

An up-to-date Java version 8 (referred here as 1.8) is recommended. The consolidation component requires a Java runtime environment with version 1.6.0_04 or newer (means a higher version of 1.6 or any later version like 1.7 or 1.8). Both 32-bit and 64-bit JREs are supported.

Required Operating system is Windows (for LMBI consolidation component)

The LMBI consolidation component needs to run on a Windows machine, 32-bit and 64-bit Windows variants are supported. Most LMBI measurement components will also run on Linux.

License Measurement Tool for SAP BusinessObjects Business Intelligence Platform (LMBI) GuideIntroduction PUBLIC 9

3 Measurement Component

3.1 General Installation Comments and Recommendations

The “installation” of the components is not more than unzipping the provided files into a folder where you have full control (particularly write permissions – see the chapter, Special Adjustments & Exception Handling if you run into issues).

The following steps describe how to run LMBI on a Windows machine where the downloaded LMBI zip file has been extracted to the folder C:\LMBI, so that the subfolders consolidation and measurement are created.

For Linux, the description uses the folder /home/usr/Downloads/LMBI.

The LMBI.zip file from the BI 4.2 SP07 shipment contains two measurement components:

● BI4.x_Component, works with all the BI 4.x server versions, except the older versions that are using SSL.● BI4.x_Component_SSL_BI4.0_to_BI4.2_SP03, works for all the BI server with versions BI 4.0, BI 4.1 up to

SP10, and BI 4.2 up to SP03, including any SSL configuration.

In case you use older BI server versions (XI 3, XIR2(a), BOE 5/6), further measurement components are provided in a restricted shipment. For details, refer to the SAP BusinessObjects BI Measurement page in the SAP Support Portal.

3.2 Preparative Steps to the Measurement

3.2.1 Third-party Authentication

The BI platform supports different types of third-party authentication methods. By default, the BI platform uses Enterprise authentication.

For more information, refer to the SAP BusinessObjects Business Intelligence Platform Administrator Guide.

NoteSAP BusinessObjects Enterprise XI 3.1

● SAP R/3● LDAP● Windows Active Directory● Windows NT

SAP BusinessObjects Business Intelligence Platform

10 PUBLIC


Measurement Component


● Enterprise● LDAP● Windows AD● SAP● Oracle EBS● Siebel● JD Edwards● PeopleSoft

For users with the default authentication method, the user data is stored in the BI platform's server. However, it is different for the users who are accessing the BI platform using any third-party authentication.

In cases where a user is accessing the BI platform through third-party authentication methods, the user object, which holds the BI platform specific data, resides in the BI platform's server. Further, the relevant data like the validity of the user remains with the third-party system and is validated during the authentication process. This might become a challenge during the license measurement. The measurement loops over the list of user IDs. The disabled user IDs with Enterprise authentication are marked and not considered during measurement.

Therefore, all the user IDs on the BI platform's server with third-party authentication are counted because the BI platform server doesn’t hold data on the validity of a user ID. To prevent counting of disabled or expired users during license measurement, you should disable the third-party authentication aliases for the corresponding users. Alternatively, you can remove the user IDs of these disabled users from the BI platform server before the measurement.

License Measurement Tool for SAP BusinessObjects Business Intelligence Platform (LMBI) GuideMeasurement Component PUBLIC 11

3.2.1.1 Finding Disabled or Expired Users with Authentication Method SAP R/3/ SAP

The disabled or expired users with SAP R/3 authentication can be identified and excluded with corresponding reports on the ABAP system. The transaction SUIM (report By Logon Date and Password Change) can be helpful to identify invalid users. Further, reports (e.g. Users by Complex Selection Criteria) or transaction SU10 with the selection of Authorization Data allows the selection of invalid users in combination with certain roles. The relevant roles for the BI platform server shall be removed from invalid (disabled or expired) users on the ABAP side. Additionally, the user/role synchronization between the ABAP and the BI platform system must be refreshed to remove the invalid user IDs from the BI platform's server and prevent them from being counted.

3.2.2 Finding Disabled or Expired Users with Authentication Method SAP R/3/ SAP

The disabled or expired users with SAP R/3 authentication can be identified and excluded with corresponding reports on the ABAP system. The transaction SUIM (report By Logon Date and Password Change) can be helpful to identify invalid users. Further, reports (e.g. Users by Complex Selection Criteria) or transaction SU10 with the selection of Authorization Data allows the selection of invalid users in combination with certain roles. The relevant roles for the BI platform server shall be removed from invalid (disabled or expired) users on the ABAP side. Additionally, the user/role synchronization between the ABAP and the BI platform system must be refreshed to remove the invalid user IDs from the BI platform's server and prevent them from being counted.

3.2.3 Increase the memory settings for large installations (> 40,000 users)

NoteYou should refer to this topic only if the user count is more than 40 thousand. You can check the user count in CMC by navigating to Users and Groups User list .

If the number of users exceed 40,000, the startup script of the measurement component should be adjusted to provide sufficient memory. An estimate for the required amount of memory is given in the table below.

Number of Users (in thousands) Estimated Disk Space (in MB)

25 600

50 1100

75 1600

100 2100

125 2600

12 PUBLIC



Number of Users (in thousands) Estimated Disk Space (in MB)

150 3100

175 3600

200 4100

Generally, 500 MB memory is assigned per 25,000 users with a minimal use of 100 MB.

To change the memory settings for a measurement component, you should follow the steps described in chapters Installing and Running the Measurement Components (for BI 4.x or XI 3 and XI R2).

After the following the recommended steps, you should:

1. Open the respective folder of the version that is aimed to be measured. For example, BI4.x_Component-3.0.34 for SAP BusinessObjects BI 4.x systems.

2. In the folder, open the Measure.cmd file (or Measure.sh for Linux).3. The memory settings are set close to the end of the script in these line: java -Xms32m -Xmx1024m %SSL

% com.sap.glas.systemMeasurement.Run -classpath %CLASSPATH%.

NoteIn the default configuration, the Java virtual machine will be started with a maximum heap size of 1024 MB (and an initial minimum heap size of 32 MB).

4. Increase the value of the parameter –Xmx accordingly, for example, to –Xmx1100m, if you have a system with 50,000 users or less.

Note1. Before adjusting the parameter and running a measurement, it should be considered that enough main memory for the operating system (for Windows e.g. at least 2 GB RAM) and other applications or services that may run remain.

2. In addition, be aware that a 32-bit Java runtime (JRE) on Windows would only be able to allocate around 1.5 GB RAM. Hence, the larger installations require a 64-bit JRE to have sufficient memory available.

3.2.4 Estimates on the Measurement Runtime

The estimated time to run the measurement depends on the factors given below:

• Number of users and groups

• Number of documents/objects (and if they are in the cache)

• The number access levels and broken user rights inheritance

After every ten seconds, the measurement component provides information on the progress and the estimated duration for the time-consuming user rights measurement. For more information, refer to chapter 3.5.9.

This can be a range between several minutes to hours or even days. However, the measurement script doesn't cause a significant load on the BI platform server (nor the data base server) if you have more than two cores.


3.2.5 Required Administration Rights for User that Runs LMBI Tool

The user that runs the measurement has unrestricted administration rights. LMBI v3.0.28 and above validates the necessary rights after logon. If any mandatory rights are missing, then the list of missing rights is displayed in a popup.

NoteThe access rights to folders are currently not checked, but still will have a negative impact if they are not granted.

3.2.5.1 Read permissions for Folders and Personal Folders

The user requires the View objects right on Folders (root folder) and on Personal Folders.

To grant the right for Folders to a user in the CMC,

1. Select Folders > Manage > Top-Level Security > All Folders > Add Principal.

2. Select the user that runs the measurement.

3. Navigate to Add and Assign Security > Advanced > Add/Remove Rights.

4. Select the radio button in the column Granted for the right View objects.

NoteTo grant the right for Personal Folders, manage the top-level security for All Personal Folders.

14 PUBLIC



Read Permissions for Users and User Groups

The user requires at least the right View objects on Users and User Groups.

To grant the right for Users, manage the top-level security for All Users accordingly.

To grant the right for User Groups, manage the top-level security for All User Groups accordingly.

Read Permissions for Servers and Server Groups

The user requires at least the right View objects on Servers and Server Groups.

To grant the right for Servers, manage the top-level security for All Servers accordingly.

To grant the right for Server Groups, manage the top-level security for All Server Groups accordingly.

Access to the License Keys

The user must be a member of the group Administrators.

Access to the CMC Application

To grant the required rights in the CMC,


1. Select Applications > Central Management Console > User Security > Add Principal > select the user that runs the measurement > Add and Assign Security > Advanced > Add/Remove Rights.

2. Select the radio button in the column Granted for the right Log on to the CMC and view this object in the CMC

3.3 Installing and Running the BI 4.X Measurement Component

3.3.1 Summary

This is a brief summary of the main steps described with more details in the next chapters:

Take the file LMBI.zip, extract it and unzip the file BI4.x_Component.zip from the contained Measurement folder. Run the proper Measure script, Select the BI 4 Template in the UI which pops up, click on the Prepare > Logon menu and log on with an administrator account. Use menu Prepare > Read from Repository & Evaluate Licenses to run the actual measurement. Take the created measurement file and continue with the LMBI consolidation component.

3.3.2 Version Numbers and How to Install LMBI Patches

LMBI is now part of BI 4.2 package/patches and shipped as Collaterals and versioning will be now 14.2.x. For example, BI4.x_Component-3.0.34.zip will be changed to BI4.x_Component.zip.

NoteYou can ignore version numbers in file names if they differ from the current version if you are still using BI4.2 SP5 or older version and/or out of maintenance contract. You can refer to 1854405 that lists the available patches for LMBI.

3.3.3 Checking the Java Runtime Version

The system you choose for the measurement component installation requires a Java Runtime Environment (JRE) or a Java Software Development Kit (SDK, SE or EE). The supported versions are listed in the chapter 1.3.1.

NoteIt is recommended to run LMBI on the BI server to use the JRE provided with the BI platform. If you prefer to run LMBI on a client, you must care for a JRE yourself. For more details on JRE licensing options, refer to the SAP note 2700275 .

16 PUBLIC



http://help.sap.com/disclaimer?site=https://launchpad.support.sap.com/#/notes/1854405


TipYou can check the configuration of JRE by executing a shell command java –version to get a prompt. The first response line contains the version number and the second line indicates if it is a 64-bit version.

If you do not have a proper Java version, you may copy the Java folder with a suitable JRE/JDK from another machine and set the path for LMBI as described in the exception handling section of chapter 3.7.3. This keeps the existing JRE/JDK installation untouched for potentially existing server applications requiring a specific Java version.

Do not use the BusinessObjects License Measurement Tool (BOLMT) tool in the BI platform shipment

The Business Intelligence Platform Administrator Guide (selective versions) describes the use of the BOLMT. However, the results generated by the current BOLMT cannot be used for license audits and shall not be loaded into LMBI or LAW.

3.3.4 Measuring SAP BusinessObjects BI platform 4.x Systems

Required ports if the measurement component runs on a client PC

The measurement component acts as a client on any Microsoft Windows or Linux machine connecting to the BI platform server. You should have access to the BI platform server via browser (HTTP port). The measurement component runs on top of the BI platform Java SDK and uses a CORBA component to communicate with the BI platform server using a mutual connection between the Name Server Port (default setting is TCP Port 6400) and the Request Port (default setting is auto assign). If you have a firewall between the BI platform server and the computer where the measurement component runs, make sure you can establish a connection using these two ports. Chapter 3.7.1 describes the details how to determine the settings in your installation. To access the data on the BI platform server, you have to log on with administrator rights.


3.3.4.1 Installation Folder

Unzip the file BI4.x_Component.zip in the measurement subfolder. The LMBI measurement component must be extracted.

Limitation:

The current measurement scripts do not support network drives with locations like \\<host_IP>\lmbi\measurement\BI4.x_Component. You should copy the files locally (or find way to modify the settings in the start script properly).

3.3.4.2 Adjustments for SSL Support

To check if SSL is enabled on a BI 4.X system, then open the Central Configuration Manager and check the properties of theServer Intelligence Agent (SIA). SSL is enabled if the Enable SSL checkbox is checked in the Protocol’s tab. If SSL is enabled, you must have a copy of these files shown on this tab in the machine/PC, where you start the LMBI measurement.

LMBI Configuration for Windows


LMBI Configuration for UNIX

For Linux, you have to check if the script Measure_with_SSL.sh has the correct configuration. The default directory (/home/user/Downloads/SSL) and the file names for the certificates are cacert.der and servercert.der, the key is server.key, and passphrase is passphares.txt.

18 PUBLIC



3.3.4.3 Start the Measurement Component

Windows

Start the measurement with a double-click on

• the Measure.cmd script, if SSL is not enabled.

• the Measure_with_SSL.cmd script, if SSL is enabled.

The execution of .cmd file sets the SSL parameters and then start the Measure.cmd script.

Linux

First, ensure that both the scripts Measure.sh and Measure_with_SSL.sh are enabled for execution. You should enable the execution with the chmod command. To run the command, open a terminal window and use the cd command to navigate to the folder with the corresponding measurement component, for example, to the folder /home/usr/Downloads/LMBI/measurement/BI4.x_Component. In that folder, run the command chmod 755 Measure.sh and chmod 755 Measure_with_SSL.sh.

To start the measurement, run the corresponding shell script with a double-click in a file explorer or in terminal window using the command sh Measure.sh or the sh Measure_with_SSL.sh. You should use

• the Measure.sh script, if SSL is not enabled.

• the Measure_with_SSL.sh script, if SSL is enabled.

The measurement uses a (Java Swing) UI. If you use a text-based remote connection tool like Putty, the system throws a NoClassDefFoundError: sun.awt.X11GraphicsEnvironment error.

Exception Handling

If you notice any issues, then refer to Exception Handling [page 38].


3.3.4.4 Select a Template / Repository

After starting the measurement component, a command shell and a window is displayed.

Select the corresponding repository for your measurement:

• To measure a system with version BI 4.x, click on the entry Template for SAP BusinessObjects BI 4.x systems. A selection marker (blue background) appears and shows the details.

Additional Information:

Refer to the information below for SAP BusinessObjects Enterprise releases.

• To measure a system with version XI3, click on the entry Template for SAP BusinessObjects Enterprise XI 3.x systems. A selection marker (blue background) will appear and show details on the right-hand side.

• To measure a system with version XIR2, click on the entry Template for SAP BusinessObjects Enterprise XIR2 systems. A selection marker (blue background) will appear and show details on the right-hand side.

3.3.4.5 Logon to the Repository

Navigate to Prepare -> Log On to start the log on to the repository. The input fields and their meaning are described in the logon screen.


• Server name: The server’s network name (used to ping it). It is also contained in the URL used access the CMS.

20 PUBLIC



• It is highly recommended to use a free text system alias to track the measurements easier in the consolidation component.

• The settings for Productive / Non-Productive System and standalone user can be changed later, if necessary.

• Standalone means there is no data loaded/shown from classic SAP systems for example, SAP NetWeaver Business Warehouse, and SAP Business Suite.

To proceed, select the Log On button. The logon popup is replaced by a Trying to connect to popup. All the menu entries are blocked till the log on is completed.

You’ll get the confirmation that You are now connected to CMS server <your server name> in the measurement component.


Once the logon is completed, the measurement component checks some of the administrative rights required for the user who runs the measurement. If the checks are ok, then you will see several lines of “User ‘<your user>’ has sufficient authorization to …” in the command line output.

If the log on fails, then you’ll get an exception message (in your local language). In such a scenario, you should check if you have chosen the correct server name and ask your network administrator if the port is blocked. For more details, please refer to chapter 3.7.4.

3.3.4.6 Read User Rights and Determine User Types

After the successful log on, you may now start the actual measurement. To start reading the user rights, navigate to Prepare -> Read from Repository & Evaluate Licenses. After a click, the menu remains frozen until the measurement is completed. The measurement component reads the license keys, server metrics, the number of documents, and the effective rights of each user with regards to certain user types. For more information on the measurement runtime, refer to chapter 2.3. The status prompts indicate the progress during measurement. During the user measurement, an estimate for the remaining time is prompted every 10 seconds in the command prompt. You can stop the (incomplete) measurement at any time by terminating the measurement component (use the End Process feature in the task manager to stop the corresponding java.exe process).

22 PUBLIC



Once the user rights evaluation is completed, the location of result file is displayed in the command shell. In addition, the measurement component changes its view and shows a list of User Rights Categories. You can see the list of users belonging to a user rights category by selecting any category.

You can use the View option to switch between User categories and Effective Rights, where you can select individual user IDs, an application like CMC or Web Intelligence, and check the list of rights granted to the selected user.

A log off is automatically executed when closing the measurement component.

3.3.4.7 File Location of the Measurement Results

Measurement result is shown in the display and is saved in the _measures subfolder. The file measure_<your bi server name>.xml is used by the consolidation component.

3.3.4.8 Measuring Further Systems

If you have to measure several systems, you have to close the measurement component and restart it. If you measure the same server again, the old result file is renamed.


3.4 Installing and Running the Measurement Components for XI 3 and XI R2

3.4.1 How to Get the XI3 and XI R2 Measurement Components

See Shipments [page 8] for more details.

3.4.2 Summary

This is a brief summary of the main steps described with more details in the next chapters and follows mainly the same steps as the measurement for BI 4.x.

Take the downloaded file LMBI.zip, extract it and extract from the contained Measurement folder the file XI3_Component-3.0.34.zip / XIR2_Component-3.0.34.zip. Run the proper Measure script, Select the Template in the UI which pops up, click on the Prepare > Logon menu and log on with an administrator account. Use menu Prepare > Read from Repository & Evaluate Licenses to run the actual measurement. Take the created measurement file and continue with the LMBI consolidation component.

3.4.3 Version Numbers (such as 3.0.34) and How to Install LMBI Patches

Future patches may have similar file names with different version numbers in the file names (for example, BI4.x_Component-3.0.34.zip may become BI4.x_Component-3.0.35.zip).

File and directory names in this document and in screenshots will not be updated for each patch and might show outdated version numbers. Please ignore version numbers in file names if they differ from the current version you are using.

The release note 1854405 lists the available patches for LMBI.

3.4.4 Checking the Java Runtime Version

The system you choose for the measurement component installation requires a Java Runtime Environment (JRE) or a Java Software Development Kit (SDK, SE or EE). The supported versions are listed in the chapter 1.3.1.

24 PUBLIC





TipYou can check the configuration of JRE by executing a shell command java –version to get a prompt. The first response line contains the version number and the second line indicates if it is a 64-bit version.

If you do not have a proper Java version, you may copy the Java folder with a suitable JRE/JDK from another machine and set the path for LMBI as described in the exception handling section of chapter 3.7.3. This keeps the existing JRE/JDK installation untouched for potentially existing server applications requiring a specific Java version.

Do not use the BusinessObjects License Measurement Tool (BOLMT) tool in the BI platform shipment

The Business Intelligence Platform Administrator Guide (selective versions) describes the use of the BOLMT. However, the results generated by the current BOLMT cannot be used for license audits and shall not be loaded into LMBI or LAW.

3.4.5 Measuring SAP BusinessObjects BI platform XI 3.x and XIR2 systems

Required ports if the measurement component runs on a client PC

The measurement component acts as a client on any Microsoft Windows or Linux machine connecting to the BI server. It supports a measurement for versions XIR2 and XI3 from any computer with proper network access. Please make sure that you have access to the BOE server via browser (HTTP port). The measurement component runs on top of the BOE Java SDK and uses a CORBA component to communicate with the BI server using a handshake connection on two ports, the Name Server Port (default setting is TCP Port 6400) and the Request Port (default setting is auto assign). In case you have a firewall between the BOE server and the computer where the measurement component runs, make sure you can establish a connection using these two ports. Chapter 3.7.1 describes the details how to determine the settings in your installation.



To access the data on the BI server, you have to log on with administrator rights.

3.4.5.1 Adjustments for SSL Support


LMBI Configuration for Windows


LMBI Configuration for UNIX

For Linux, you have to check if the script Measure_with_SSL.sh has the correct configuration. The default directory (/home/user/Downloads/SSL) and the file names for the certificates are cacert.der and servercert.der, the key is server.key, and passphrase is passphares.txt.

26 PUBLIC




Windows

Start the measurement with a double-click on

• the Measure.cmd script, if SSL is not enabled.

• the Measure_with_SSL.cmd script, if SSL is enabled.

The execution of .cmd file sets the SSL parameters and then start the Measure.cmd script.

Linux

First, ensure that both the scripts Measure.sh and Measure_with_SSL.sh are enabled for execution. You should enable the execution with the chmod command. To run the command, open a terminal window and use the cd command to navigate to the folder with the corresponding measurement component, for example, to the folder /home/usr/Downloads/LMBI/measurement/BI4.x_Component. In that folder, run the command chmod 755 Measure.sh and chmod 755 Measure_with_SSL.sh.

To start the measurement, run the corresponding shell script with a double-click in a file explorer or in terminal window using the command sh Measure.sh or the sh Measure_with_SSL.sh. You should use

• the Measure.sh script, if SSL is not enabled.

• the Measure_with_SSL.sh script, if SSL is enabled.

The measurement uses a (Java Swing) UI. If you use a text-based remote connection tool like Putty, the system throws a NoClassDefFoundError: sun.awt.X11GraphicsEnvironment error.

Exception Handling

If you notice any issues, then refer to Exception Handling [page 38].

3.4.5.3 Select a Template / Repository

After starting the measurement component, a command shell and a window is displayed.


Select the corresponding repository for your measurement:

• To measure a system with version BI 4.x, click on the entry Template for SAP BusinessObjects BI 4.x systems. A selection marker (blue background) appears and shows the details.


Refer to the information below for SAP BusinessObjects Enterprise releases.

• To measure a system with version XI3, click on the entry Template for SAP BusinessObjects Enterprise XI 3.x systems. A selection marker (blue background) will appear and show details on the right-hand side.

• To measure a system with version XIR2, click on the entry Template for SAP BusinessObjects Enterprise XIR2 systems. A selection marker (blue background) will appear and show details on the right-hand side.

3.4.5.4 Logon to the Repository

Navigate to Prepare -> Log On to start the log on to the repository. The input fields and their meaning are described in the logon screen.


• Server name: The server’s network name (used to ping it). It is also contained in the URL used access the CMS.

• It is highly recommended to use a free text system alias to track the measurements easier in the consolidation component.

• The settings for Productive / Non-Productive System and standalone user can be changed later, if necessary.

• Standalone means there is no data loaded/shown from classic SAP systems for example, SAP NetWeaver Business Warehouse, and SAP Business Suite.

28 PUBLIC



To proceed, select the Log On button. The logon popup is replaced by a Trying to connect to popup. All the menu entries are blocked till the log on is completed.

You’ll get the confirmation that You are now connected to CMS server <your server name> in the measurement component.


Once the logon is completed, the measurement component checks some of the administrative rights required for the user who runs the measurement. If the checks are ok, then you will see several lines of “User ‘<your user>’ has sufficient authorization to …” in the command line output.

If the log on fails, then you’ll get an exception message (in your local language). In such a scenario, you should check if you have chosen the correct server name and ask your network administrator if the port is blocked. For more details, please refer to chapter 3.7.4.

3.4.5.5 Read User Rights and Determine User Types

After the successful log on, you may now start the actual measurement. To start reading the user rights, navigate to Prepare -> Read from Repository & Evaluate Licenses. After a click, the menu remains frozen until the measurement is completed. The measurement component reads the license keys, server metrics, the number of documents, and the effective rights of each user with regards to certain user types. For more information on the measurement runtime, refer to chapter 2.3. The status prompts indicate the progress during measurement. During the user measurement, an estimate for the remaining time is prompted every 10 seconds in the command prompt. You can stop the (incomplete) measurement at any time by terminating the measurement component (use the End Process feature in the task manager to stop the corresponding java.exe process).

30 PUBLIC



Once the user rights evaluation is completed, the location of result file is displayed in the command shell. In addition, the measurement component changes its view and shows a list of User Rights Categories. You can see the list of users belonging to a user rights category by selecting any category.

You can use the View option to switch between User categories and Effective Rights, where you can select individual user IDs, an application like CMC or Web Intelligence, and check the list of rights granted to the selected user.

A log off is automatically executed when closing the measurement component.

3.4.5.6 File Location of the Measurement Results

Measurement result is shown in the display and is saved in the _measures subfolder. The file measure_<your bi server name>.xml is used by the consolidation component.

3.4.5.7 Measuring Further Systems

If you have to measure several systems, you have to close the measurement component and restart it. If you measure the same server again, the old result file is renamed.


3.4.5.8 Installation Folder

The required LMBI measurement component must be extracted. It is a best practice to extract the files into a subfolder with the zip files name, e.g. extract XI3_Component-3.0.34.zip to the subfolder XI3_Component-3.0.34 of the measurement folder.

• For BusinessObjects Enterprise XI 3, extract XI3_Component-3.0.34.zip

• For BusinessObjects Enterprise XIR2, extract XIR2_Component-3.0.34.zip

• For BusinessObjects Enterprise 6.x and 5.1.x, extract X_BOE-3.0.34.zip (on the BOE server).

The current measurement scripts do not support network drives with locations like \\192.168.1.2\lmbi\measurement\BI4.x_Component. You’ll have to copy the files locally (or find way to modify the settings in the start script properly).

3.5 Installing and Running the Measurement Components for BOE 5.1 and BOE 6.5

3.5.1 How to Get BOE 5.1 and BOE 6.5 Measurement Components

See Shipments [page 8] for more information.

3.5.2 Measuring SAP BusinessObjects 5.x/6.x Systems

3.5.2.1 Where to Install the Measurement Component?

The measurement component acts as a client on any Microsoft Windows machine (Linux not supported), but requires some parts of the SAP BusinessObjects installation (Designer & BusinessObjects executable and their ODBC connection). To keep the required preparation reasonable, we assume that the installation of the measurement component is done on the BOE server itself. A Java Runtime Environment (JRE) or a Java Software Development Kit (SDK, SE or EE) with Java version 5 (1.5) or above.


32 PUBLIC




3.5.2.2 Installation folder

The required LMBI measurement component must be extracted. It is a best practice to extract the files into a subfolder with the zip files name, e.g. extract X_BOE_5+6_Component-3.0.34.zip to the subfolder X_BOE_5+6_Component-3.0.34 of the measurement folder. The current measurement scripts do not support network drives with locations like \\<host_IP>\lmbi\measurement\X_BOE_5+6_Component-3.0.34. You’ll have to copy the files locally (or find way to modify the settings in the start script properly).

3.5.2.3 Copy the GLAS.unv File to Universe Folder

Copy the file GLAS.unv from the \universes subfolder into your BusinessObjects universes folder.

• The default location for a version 5 installation is C:\BO517\BusinessObjects 5.0\Universe.

• The default location for a version 6 installation is C:\Documents and Settings\<your windows user>\Application Data\Business Objects\Business Objects 6.0\universes.

3.5.2.4 Adjust Program Paths in the Configuration.xml Files

If the default values documented here do not match your local settings, you should use an XML editor to adjust them in the corresponding configuration file.

For BOE 5 servers

• The corresponding configuration file is Configuration_BOE5.xml in the subfolder \config.

• The value of the tag <Busobj> should address the BusinessObjects executable with the default

path C:\BO517\BusinessObjects 5.0\busobj.exe.

• The value of the tag <Designer> should address the BusinessObjects executable with the default

path C:\BO517\BusinessObjects 5.0\designer.exe.

• The value of the tag <Universe> should address the copied GLAS.unv. The default path is

C:\BO517\BusinessObjects 5.0\Universe\GLAS.unv.

• (Do not adjust the value of the tag <Report> as it is relative to the LMBI installation folder)

For BOE 6 servers

• The corresponding configuration file is Configuration_BOE6.xml in the subfolder \config.

• The value of the tag <Busobj> should address the BusinessObjects executable with the default

path C:\BO651\Business Objects\BusinessObjects Enterprise 6\bin\busobj.exe.

• The value of the tag <Designer> should address the BusinessObjects executable with the default

path C:\BO651\Business Objects\BusinessObjects Enterprise 6\bin\designer.exe.


• The value of the tag <Universe> should address the copied GLAS.unv. The default path is

C:\BO651\Business Objects\BusinessObjects Enterprise 6\auditorData\Universes\

• Universes\GLAS.unv and needs to be updated as it doesn’t match the path specified in 3.6.3.

• (Do not adjust the value of the tag <Report> as it is relative to the LMBI installation folder)

If you’ve made modifications, save the file (in the original file encoding). The tags <User> and <Password> are enclosed within comments in shipped version of the configuration files. By default, you’ll be prompted for log on data. If you want to save the log on data here, close/delete the comment lines and enter user name and password before saving the file.


Start the measurement component with the Legay_Measure.cmd script (double click it or use right mouse menu “Open” – do not use “Run as administrator). If you run into any issues, please check chapter 3.7.3 for adjustments.

3.5.2.6 Select a System / Repository

After starting the measurement component, a window similar to the one on the left should open.

• To measure a system with version 5, click on the entry Template for Version 5. A selection marker (blue background) will appear.

• To measure a system with version 6, click on the entry Template for Version 6. A selection marker (blue background) will appear.

3.5.2.7 Select Database Connection

In this topic, you will learn how to establish a database connection. Follow the steps below:

1. In the menu, navigate to Prepare -> Start Designer and then Define Connection. The SAP BusinessObjects Designer opens with the universe GLAS.unv. If the SAP BusinessObjects Designer does not open, you should check the settings as described in section 3.6.4 for the path tag <Designer> or open the universe file manually within the Designer.

2. In Designer, choose the menu File -> Parameters and select your database in the connection area.

3. Save the universe and close the Designer.

34 PUBLIC



3.5.2.8 Read User Rights

In the measurement component, navigate to Prepare -> Start BusinessObjects & Extract. SAP BusinessObjects will open. If the BusinessObjects doesn’t open, please check the settings as described in 3.6.4 for the path tag <Busobj>. Dependent on your settings, these two pop-ups might show up:

• Enable Macros, if prompted.

• Confirm with OK that the file ‘ExtractFromRepository.rep’ originates from an earlier version.

A potential pop-up message The installed add-in ‘<path>\busobj.rea’ could not be found. The file may have been renamed, moved or deleted. can be ignored. If the report doesn’t open, you can open it manually open the file ExtractFromRepository.rep from the LMBI measurement component’s subfolder /extract.

You can navigate to Tools > Macro > Macros or press Alt+F8 to launch Macros. The macro ThisDocument.exportXML is selected (if not, select it). Start its execution by pressing the Run button to read the user rights.

A message box will indicate a successful completion.


If you confirm with OK, a Windows Explorer window opens showing the subfolder legacy_raw_data in the measurement component directory (C:\LMBI\measurement\X_BOE_5+6_Component3.0.34\_measures\legacy_raw_data).

3.5.2.9 Evaluate User Types

Back in the measurement component select menu Prepare -> Evaluate Licenses. The read user rights are evaluated and the users are mapped to the user types described in the license documentation. The display will show an aggregated list of user types. The tree navigation on the left side of the spited screen has the parent node Licenses. If you select a user category there, you get the list on the right the list of the users that belong to this category. In the View menu, you can also select further entries (User categories is selected by default and the one shown in the screenshot on the right):

• Select Categories by Users to see all categories a user has been assigned to.

• Explicit Rights to see the rights that have explicitly been set on a user

• Effective Rights to see the rights resulting from all rights assignments

3.5.2.10 File Location of the Measurement Result

The result file measure_legacy.xml for the LMBI consolidation component is stored in the \_measures subfolder.

3.5.2.11 General Installation Comments and Recommendations

The installation of the components is not more than unzipping the provided files into a folder where you have full control (particularly write permissions – see 3.7.2 if you run into issues).

The following steps describe how to run LMBI on a Windows machine where the downloaded LMBI zip file has been extracted to the folder C:\LMBI, so that the subfolders consolidation and measurement are created.

For Linux, the description uses the folder /home/usr/Downloads/LMBI.

The measurement subfolder contains four zip files which each contain a measurement component specific to the BI/XI/BOE server version.

• For SAP BusinessObjects BI 4.x: BI4.x_Component-3.0.34.zip

• For BusinessObjects Enterprise XI 3: XI3_Component-3.0.34.zip

• For BusinessObjects Enterprise XIR2: XIR2_Component-3.0.34.zip

• For BusinessObjects Enterprise 6.x and 5.1.x: X_BOE-3.0.34.zip

36 PUBLIC



3.6 Special Adjustments & Exception Handling

3.6.1 How to Read the Settings for the CMS and the Request Port in the CMS

Follow the steps below:

1. Login to the CMC.2. Go to Servers and open the context menu of the corresponding CentralManagementServer.3. Select Properties.

In the Common Settings section, two ports are listed: Name Server Port (for traffic from measurement component to BOE server) and Request Port (for traffic from the BOE server to the measurement component).

NoteThe name server port will not be listed in case the Auto assign checkbox next to the Request Port is checked. In this case, the name server port need to be determined with a different approach, for example, a network port scanner software.

3.6.2 Full Control for Everyone on Windows 7 on Installation Folder

You must have Write permissions to the folder where the LMBI components are extracted. Follow the steps below to provide permissions in Windows operating system:


1. In Windows Explorer, open the context menu of the folder and select Properties.2. Switch to the tab Security and select Edit.3. Select Add.4. On the Select User, Computers, Service Accounts, or Groups dialog, enter everyone and select Check

Names.

NoteIn case more than one result is found, then select the local group and confirm all settings with OK until you get back to the permissions dialog.

5. Check Allow for the group Everyone in the line Full Control.6. Select OK for the open dialog boxes.

3.6.3 Exception Handling

Set system directory for Java

In case you face the message 'java is not recognized as an internal or external command, operable program or batch file.’, the path to your Java runtime environment (JRE) is not included in your system variable PATH. First search for it (you may search for java.exe), then

• enter it into the Measure.cmd script. To do so, edit the file in a text editor and replace the path in line 5 with your specific one to the bin folder of your JRE (where the java.exe file is located) set JAVAPATH= "C:\Program Files (x86)\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\win64_x64\sapjvm\bin".

NoteThe quotation marks are required if the path has spaces in it.

• Save the changed files and start the measurement component again.

• Alternatively add the path to the Windows system variable PATH (if you know how to and want to have this setting to be valid for the entire machine). If you don’t have a java.exe/JDK/JRE on your machine, you can copy one from another machine and adjust the settings as described.

Issues with Linux using Putty

If you use a text based remote connection tool like Putty only, the graphical user interface of the LMBI measure component can’t start and you’ll get a java.lang.ClassDefFoundError: sun.awt.X11GraphicsEnvironmnet error. Use a different type of remote connection, for example, VNC.

38 PUBLIC



3.6.4 How to Identify and Solve a Connection Issue

If you have issues to connect, first check if you are using the right script and settings for a BI server with/without SSL in place (see chapter 3.5.5). Furthermore, look up the error message code (FWM 20030 in this case) in the Error Message Guide.

These additional steps might help you to locate the issue:

1. Check if you can connect to the CMC via web browser using your system name.

2. If yes, then launch command prompt and run ping <your_system_name>. For the given example, with the system (CMS) name sapdemovm, the command would be ping sapdemovm

Example with failed ping:

Example with successful ping:

3. If the ping replies are fine, then try to telnet the system. On Microsoft Windows, a telnet client is available, but it might not be installed by default (you can simply add it via Control Panel > Programs and Features > Turn Windows features on or off). To test a telnet connection, type telnet sapdemovm 6400 where sapdemovm is your system (CMS) name and 6400 is the name server port.

Example for a failed telnet:

Example for a successful telnet:

Input


Output

You can terminate the telnet session with Ctrl + C.

4. If telnet worked fine, start the LMBI measurement component and use the system name or the IP address to connect. In addition to the steps above, you may also refer to the Business Intelligence Platform Administrator Guide in SAP Help Portal. In the version for BI 4.0 SP 11 for instance, the relevant chapter is 7.15.2 Debugging a firewalled deployment.

3.7 Requesting Technical Support

In case you have questions or face issues with an LMBI measurement component, the main contact for first level support is your auditor (the person who requested the license audit). If you face technical issues, you may also create an incident (https://launchpad.support.sap.com/#/incident/create) in the SAP Support Portal (https://support.sap.com). You must

• use the component BI-BIP-LMT,

• provide a description of the technical issue and the steps on how to reproduce the technical issue, and

• zip and attach the folder \logs (which is a subfolder to the folder, where the Measure.cmd script is located, the one you use to start the measurement). It will contain *.log and *.err files, for example audit_log_2016.03.31_13.09.12.log.

3.8 How User Rights Classify Users?

The slides available in this topic and the subsequent topics describe how a small subset of the available technical rights classify users by their assigned rights. The LMBI measurement component considers the effective user rights, no matter if these rights are assigned directly or indirectly via the security settings for the users, user groups, on access levels or application level among other components. As it runs on a local PC, no additional security aspects apply.

40 PUBLIC



3.8.1 User Rights Relevant for SAP BusinessObjects Business Intelligence Platform 4.x


3.8.2 User Rights Relevant for BusinessObjects Enterprise Platform XI 3.x and XIR 2

42 PUBLIC



3.8.3 User Rights Relevant for BusinessObjects Enterprise Platform 5.1.x and 6.x

3.9 CPU Metrics - Where to Find Required Data?

Few licenses come with CPU metric that requires the correct counting and consideration of CPUs, their cores and, in case Hyper-Threading Technology or simultaneous multithreading is active, the number of threads. This chapter gives some general directions where to find this data and how to enter it into the LMBI consolidation component.

3.9.1 BI System in Virtual Machines – Find the Required Data in the Hypervisor

3.9.1.1 VMWare

If your BI system runs in a virtual machine managed by a VMWare virtualization product, the number of configured virtual CPUs and if supported, the number of virtual cores is required. To access this data, open the configuration of the virtual machine.


Example 1 (VMWare vSphere Client):

Virtual machine Test Setup on host <IP_Address> has 2 virtual CPUs with 4 virtual core each.

Select the virtual machine > Switch to the Summary tab > Select Edit Settings > Select CPUs.

• The number of CPUs is displayed as Number of virtual sockets.

• The number of cores per CPU is displayed as Number of cores per socket.

In the VMWare Web Client, the same results can be collected. If you use another virtualization technology, collect the required data accordingly.

Example 2 (VMWare Workstation native client): 1 virtual CPU with 8 virtual cores per CPU.

44 PUBLIC



3.9.1.2 Hyper-V

The settings of the virtual machines in the Hyper-V Manager provides a configuration for Number of Virtual Processors. The resulting number of virtual CPUs and their virtual cores can’t be configured. These are based on the number of logical processors (physical CPU threads). Thus, the data in the Hyper-V Manager is helpful but not sufficient. Please refer to chapter 8.2 Error! Reference source not found, which describes how to get the required data in the guest operating system. In addition, it is recommended for you to also provide the hardware data of the physical machine.

3.9.1.3 Other Virtualization Technologies

Refer and use the procedure described in the chapter, Find the CPU Data in the Operating System [page 47] on how to find the CPU data in the guest operating system to get the correct values.

3.9.1.4 Enter the Data of a Virtual Machine into the Consolidation Component

If you have found the number of virtual processors and the number of virtual cores per processor, then the next step is to enter these values into the LMBI. Therefore, select 2.1 Assign system measures to licenses. Here, you will find an option Edit CPU/server data.

The option is visible only when you have selected a system in the upper left table and if the selected contract contains a CPU metric. Furthermore, license items with a CPU metric can only be selected if the CPU data has been entered, as otherwise its value is Missing CPU data.


When you have opened the Edit CPU/server data view, make sure you have selected the Provide system metrics (default) as well as the Yes option, which is next to the question whether the system is virtualized or not. If done so, you can enter the virtual CPU data and save the data afterwards.

NoteYou should enter the number of physical CPUs, cores, and threads as well if you use the legacy contract model.

Now, you have successfully saved your virtual CPU data and can use this information accordingly, as seen in the following screenshot:

46 PUBLIC



3.9.2 Find the CPU Data in the Operating System

Many operating systems provide sufficient data via shell commands. You should use the once listed in the subsequent topics if you have to determine the number of CPUs and cores.

3.9.2.1 Systems with Microsoft Windows

The topic describes how you can check the number of CPUs, cores per CPU, and logical processors per CPU.

Follow the steps below to check the through command prompt:

1. Launch Command Prompt.2. Run wmic cpu get DeviceId, SystemName, NumberOfCores, NumberOfLogicalProcessors to

see the number of CPUs (you will get multiple lines, one for each CPU), the number of cores per CPU and the number of threads (aka logical processors) per CPU.

Example 1: Machine with 1 CPU, 2 cores and two-way hyper threading (2 threads/core)

Example 2: Machine with 2 CPUs, 4 cores each/8 in total and no hyper threading (1 thread/core)


• The number of CPUs is equivalent to the number of lines.

• The number of cores per CPU is displayed as NumberOfCores.

If additional information is required/requested, these commands may be helpful:

• To get information about the CPUs, run wmci cpu get Name, Description, Manufacturer

• To identify the machine’s IP address (es), run ipconfig

Windows system screens showing number of CPUs, CPU type, and number of threads

The required CPU information can partially be collected in two Windows system screens.

• To get the number of CPUs, navigate to the Windows System information (Control Panel > System)

• To get the number of threads / logical processors, navigate to the Device Manager (Control Panel > Administrative Tools > Computer Management > Device Manager). However, the list of Processors is the number of CPU threads (logical processors) and you don’t get any information here if hyper threading is enabled or not. So, the only way to get the number of cores would be to check the data sheet of the CPU type that is used.

In the example given below, there is one Intel Core i7-870 processor with 4 cores. Due to hyper threading technology, there are two threads per core, which results in a list of 8 logical processors in the Windows device manager. The correct data for this hardware would be 1 CPU, 4 cores, 2 cores per thread.

48 PUBLIC



3.9.2.2 Systems with Other Operating Systems

● For Linux, use the command lscpu | grep -i socket● For Solaris, use these commands:

○ For the number of physical CPUs: psrinfo –p○ For the number of cores: kstat -p cpu_info:*:*:core_id | awk '{ a[$2]++ } END { for

(b in a) { print b } }' | wc –l● For HP-UX with physical deployment, use machinfo(1) which is located at /usr/contrib/bin.● For HP-UX with virtual partitions or virtual machines (IA64 only), use model(1).

3.9.3 Find the CPU Data for Physical Deployments

For a physical deployment of the BI system, the hardware manual is a good reference to determine the hardware metrics.


Enter the data of a physical deployment into the consolidation component

Entering the data of a physical deployment into the consolidation component is very similar to entering virtual CPU data into the consolidation component. The only difference is to select the No radio option next to the question whether the nodes system is virtualized or not (if not already selected). If done so, you can enter the virtual CPU data and save the data afterwards.

3.9.4 Further CPU Data Options for Clustered BI Servers

Besides the direct entry, there are two more options to provide the CPU data. You can check the subsequent topics for other options.

3.9.4.1 Providing Custom CPU Metric Values

This option should be used only if the metric value cannot be calculated correctly by entering the system data. You can enter the data by selecting the Enter a custom metric value radio option, entering the custom CPU metric value, and writing a note as why a custom CPU metric value is necessary. For example, in one scenario, a custom metric is used for contracts that were signed before 2006. In such cases, there is a possibility that another metric was used. However, you should contact your license auditor to clarify this. If you use this option, please provide as much CPU data/reasons as possible why you use it.

50 PUBLIC



3.9.4.2 Reusing the CPU Data of Another Server Node

You can also select the Do not count – for multiple nodes on the same system option that is only available for clusters. A cluster is a system with more than one server node. The following scenario shows a server with four clusters:

In such a scenario, it is useful for one server node to use the same value of another node. Therefore, a list of nodes that can be selected is displayed. This option cannot be used for server nodes with different IP addresses as these are different systems.

3.9.4.3 Clusters with Multiple Server Nodes

You must ensure that you have selected one of the three described options to provide CPU data for each server node by selecting the server nodes in the upper right corner. If necessary, enter the required data accordingly before saving all data.


4 Consolidation Component

4.1 Installation and Folder Structure

The description in the following steps starts with the creation of a folder C:\LMBI and the extraction of the LMBI.zip file. As a result, two subfolders, measurement and consolidation are created. For the consolidation, only one of the two .zip files in the subfolder consolidation is required.

If you have a 32-bit Java SE runtime environment, extract the file LMBI-win32.win32.x86.zip to the subfolder folder \Consolidation. In case of a 64-bit JSE, use file LMBI-win32.win32.x86_64.zip.

If you are not sure which JSE you have, open a command prompt and type java –version. The second line prompt (starting with Java HotSpot(TM) Client VM) will show the word 64-bit in case you run a 64-bit version, otherwise you run a 32-bit JSE.


The acting user requires full control access rights on the consolidation folder and its subfolders (see chapter 3.7.2 of the LMBI Measurement Guide if you need to set these rights).

4.2 Install LMBI Patches / Updates of the Consolidation Component

The latest versions has to be unpacked/installed from BI package/patch collaterals/lmbi in different folders. Refer to 1854405 for more information if you are out of maintenance contract for BI 4.x or using older BI versions.

To continue previous consolidation work, the data set folder can be either copied to become a subfolder of to the current LMBI version or can remain in place and be selected in the consolidation component via the Change data store location option.

If preferences have been modified, they need to be re-entered. Alternatively, the preference file com.sap.glas.lmbi.consolidation.prefs in the subfolder \configuration\.settings can be copied before the consolidation component is started. This file shall not be modified with a text editor to prevent encoding issues.

52 PUBLIC


Consolidation Component



4.3 Start the Consolidation Component

In the following sections, all subfolders will be given relatively to the main program folder C:\LMBI\Consolidation\LMBI-win32.win32.x86.

4.3.1 Start and Log Files

To run the consolidation component, launch lmbi.exe in the main program folder. The logs are written into the file .log in the subfolder \workspace\.metadata\. If you run into any Java issues, then check Running the Consolidation Component on Machine with Older JAVA Version (<JDK 1.6) [page 54].

4.3.2 Data Store Location

By default, the subfolder \lmbi_resultsis used as a root folder to store all data. Data from one license audit is kept together in a data set. Each data set is stored in its own subfolder. At first run, a subfolder for the first data set is created with the date in its name, for example, \lmbi_results\started_2013-04-29 (unless you create and select your own subfolder). In this folder, the copies of imported measurements and contract files as well as processed data is persisted. For all further runs, the last modified subfolder is used. For additional license audits, for example, in following years, create a new subfolder. When the data set folder is changed, potential data stored in the specified folder is loaded.

The folder where the data is stored can be changed according to individual requirements, for example, data protection regulations.

4.3.3 Preferences

Program preferences allow changing the log level, if necessary. The default log level Info generates logging for all major activity. Debug might be requested by SAP for troubleshooting. Warning show warning and errors only, Error is restricted to errors. The special character handling is intended only for advanced users in combination with integration scenarios with LAW, preferably with guidance from SAP.

In LMBI, a flag for Disguise server names is available for special data protection requirements. If the disguise flag is checked, the original server names, cluster nodes and IP addresses will be replaced by anonymized values, for example, a server name bi-prod.mycompany.corp\:6400 may become name5.domain3.tld1\:15349, an IP4 address 10.20.30.40 may become 9078.10118.9351.9934 and an IP6 address like 2002\:1a57\:1e76\:\:1a64\:1c74 may become 11070\:16616\:17081\:\:16532\:17254. IP addresses and ports have a randomized offset.

License Measurement Tool for SAP BusinessObjects Business Intelligence Platform (LMBI) GuideConsolidation Component PUBLIC 53

4.3.4 Running the Consolidation Component on Machine with Older JAVA Version (<JDK 1.6)

If you run a Java version older than the required 1.6.0_04, the consolidation component can be run by following the steps below:

Step 1: You likely have a proper Java version (≥ 1.6.0_04) on another machine. You can simply copy the folder from that installation to the BOE server which will not affect the system (besides the consumed disk space). So, let’s assume you copy that JRE or JDK folder onto the BOE server into the folder I:\programs\jdk1.6_x86\bin

Step 2: Open a command prompt and change to the directory with the lmbi.exe in there. In the example, i: was used to change the drive and cd \LMBI versions\LMBI 3.0.0 TestJenkins\Consolidation 32 bit to change the directory

Step 3: Set the path variable to the bin subdirectory of a current Java version, in the example set path="I:\programs\jdk1.6_x86\bin";%PATH% This will not affect the machine in general, but just the settings in the currently opened CMD shell.

Step 4: Start the consolidation component with the command lmbi.exe.

4.4 Steps Inside the Consolidation Component

In the initial screen of the LMBI tool, the three major program steps (with sub-steps) are shown with orange arrows on the left-hand side. These steps are split-up in sub-steps described in subsequent topics.

4.4.1 Step 1.2: View and Import System Measures

Click on the button 1.2 View and import system measures to access the import view. If steps 1.2 and 1.3 are disabled, change the data store location to a folder where write permission is granted.

When you click the Import System Measures button, a file dialog popup will appear to import the result(s) from the measurement component. When you ran the measurement component yourself, chapters 3.5.8 and 3.6.10

54 PUBLIC



of the LMBI Measurement Guide describe where the files have been stored. If you did not ran the measurement component yourself, you should have received these files from your BI server administrator(s) and store them locally/on a protected network drive.

In the file dialog popup, the file selector by default opens with a filter to show only measurement files (files that match the pattern measure*.xml). The filter can be changed/removed in the file selector screen in the bottom right corner, e.g. if result files have been renamed and don’t match this pattern any more.

Once imported, selecting a loaded system measurement on the left hand side will display some measurement details on the right hand side. Imported system measures can also be deleted there.

Starting with LMBI 3.0.31, a detailed analysis lists Usage Indicator and Authorizations for each BI component on the right column. A BI component is considered to be Active, if the number of corresponding reports/document types is available and exceeds (or equals to) a predefined threshold.

The thresholds are listed in the presentation How User Rights Map to Licenses in LMBI in the slide Document types & corresponding BI components (currently on slide 58). Formally, licenses are required for users who are “authorized” for certain functionality. However, LMBI will handle this less strict and consider and count only authorized users for BI components which are active. If the number of corresponding report/document types can’t be measured by LMBI, only authorizations will be considered and counted.

4.4.2 Step 1.3: View and Import Contract/Licenses

Select 1.3 View and import contract/licenses to access the import view. If steps 1.2 and 1.3 are disabled, then change the data store location to a folder where write permission is granted.

In the last decade, several types of licenses with different metrics and counting rules have been sold. To get the correct count on how many licenses you need, LMBI needs to know which licenses exactly you have purchased. This information is given to LMBI in a contract file that should match with your license entitlement.


The presentation Measuring BI license terms with LMBI on the SAP BusinessObjects BI Measurementpage will provide more details on the license models. If you have questions on your specific contractual situation, please get in touch with your sales representative.

When you have information about your licenses, you can select the corresponding contract file in the folder generic_contract_files in the consolidation folder. In case you have been requested to provide measurement results as part of a license audit, you likely received a customer specific contract file which contains the relevant contracts and licenses.

Technically, just use the Load Contract List File button to import a contract file.

If a contract file contains licenses from more than one contract model, the consolidation component will split it up in multiple units containing only one contract model as they may not be mixed within a single deployment.

4.4.3 Step 2.1: Assign System Measures to License

Select 2.1 Assign system measures to licenses to access the mapping view. Step 2.1 is enabled when at least one system measure and contract data have been imported.

Why systems need to be mapped contracts

Each server running BusinessObjects Enterprise platform software requires appropriate software licenses. With more than a decade pasted, several major contract models have been valid with different licensing terms and different contract model items.

Before a system measurement can be evaluated and the list and amount of required license items can be calculated, the used contract model needs to be selected. For customers with a one simple license contract, this is a 1:1 (or n:1 if n BOE servers are measures) mapping. Customers with more than one contract/contract model need to make proper assignment in this step 2.1 which contract shall cover which BOE server.

Guidance on contract models and their licenses

With the LMBI documentation, a slide deck Map user rights to licenses in LMBI is provided that gives an overview on the various contract models and their contract model items (the licenses that belong to this contract model).

Elements in the user interface

The view in this set is split. The upper left part shows the list of system measures that have been imported . The lower left part shows the contract(s) and the license items contained in there.

Once a system measurement and a contract are selected on the left, the right-hand side of the screen shows how the measured user rights translate into the contract model items of the selected contract and what is the

56 PUBLIC



http://help.sap.com/disclaimer?site=https%3A%2F%2Fsupport.sap.com%2Fcontent%2Fdam%2Fsupport%2Fen_us%2Flibrary%2Fssp%2Fmy-support%2Fsystems-installations%2Fsystem-measurement%2Fbusinessobjects-bi-measurement%2Fhow-user-rights-map-to-licenses-in-lmbi.pdf


result in terms of required licenses. For each contract model item, a corresponding license has to be selected (will be done automatically if only one option exists).

The assignment need to be saved.

If you have CPU data that needs to be considered for the consolidation, you may want to take a look at chapter 8 of the LMBI Measurement Guide that describes how to insert such data properly.

4.4.4 Step 3.1: Group and Consolidate

Select 3.1 Group and consolidate users to access the consolidation view. Step 3.1 is enabled when at least one system measure is assigned to its contract data. In the consolidation view, check which criteria(s) shall be used to group users (see explanation below). Select the Run grouping and consolidation option to start the process (that can be time consuming).

Grouping and consolidation will be disabled in cases where ONLY CPU metrics are used to cover both to platform and editors in a stand-alone scenario (this licensing option was available in Legacy and A-la-carte contracts).

Background

Usually a named user license (NUL) authorizes a person to perform the roles covered by the NUL in multiple systems. So this person might have multiple user IDs that shall be counted only as one for the license count. To do so, user IDs with the same user ID, same name or same email address can be grouped to represent one person.

The set of licenses required by one person will then be consolidated. The system measurement calculates the minimal license that is required for a user ID based on the assigned user rights and the underlying contract. Persons with multiple, grouped user IDs may have pairs of licenses that are either identical or one license contains the other. When user licenses are consolidated, the minimal set of licenses is calculated to cover all user IDs or a person. Duplicate licenses will be counted only once, contained licenses will be dropped following the rules of the shown consolidation hierarchy.

Hierarchy for license consolidation

A user licenses contains another user license if it is listed above with a direct link line.


Licenses from different license models (for example, BA&T BI Suite and BI Package, A-la carte and Legacy) can generally not be merged/consolidated below a SAP Application Business Expert license, only BI Suite and BI Components license models have some overlap.

How to verify grouping and consolidation results

When the option Write user and system attributes into the result file is checked, the created result file consolidation.xml in the lmbi_results subfolder contains all details to check which licenses are required for each individual user. A comfortable way to view this data is to open the file consolidation.xml with Microsoft Excel. The steps in Microsoft Excel are: Open it within Excel and choose As an XML table. For each user, two blocks of lines are created.

The first block fills column C to O and shows data from single system measures:

• Column C & D - SystemAlias and SystemNameServer shows in which system measurement the user entry comes from

• Columns F - K: UserNo, UserName, UserEmail, LastLogonDate and SAP Alias holds the user details and criteria that might have been used for consolidation

• Column L - P: CMID contains a key for the license model, LicItemID and LicItemName the license item that is required for this user if only this single system would be considered. For uses which have editor rights for just one component (relevant only for BI Limited licenses in the BA&T contract models 2011-2014), the right of the corresponding BI component is in BILimitedUserRight.

The second block has columns Q to U filled and shows the licenses a user require after grouping and consolidation

• Columns Q CMID2 contains a key for the license model, columns S & T LicItemID3 and LicItemName4 list which licenses are required after the grouping and consolidation.

• Columns T & U with fields LicItemID5 and Count are internal cross check values for the number of aggregated licenses required.

58 PUBLIC



4.4.5 Step 3.2: View Results

Results

Select 3.2 View Result and Status to access the result view. Step 3.2 is enabled when at least one system measure is assigned to its contract data. The first status line at the top will indicate if all systems are assigned to its contract data (3.4.3), the line below if grouping and consolidation has run. The first five columns (Contract Type to Value (total)*) of the main table contain a list which licenses are required in total and how many of them. The columns Contract to Value (system) list each system that requires (parts of) the listed licenses.

Generate final result files

Once all measured systems are mapped to contracts, the status will become completed. Click the Generate result files button to create the file(s) that will summarize the audit results. If result files already exist, the button’s label will switch to Update result files. For the result file(s) the subfolder \results for SAP will be generated (e.g. \lmbi_results\started_2013-04-29\results for SAP) and can be easily accessed via the link Explore result folder (‘results for SAP’). It will contain these file(s) (since LMBI versions 3.0.19 or higher):

result_audit_<audit id>.lmbi (e.g. result_audit_0000123456.lmbi) or

disguised_result_audit_<audit id>.lmbi if the Disguise server names flag is set (e.g. disguised_result_audit_0000123456.lmbi).

The flag for Disguise server names is available since LMBI 3.0.28 for special data protection requirements. If the disguise flag is checked, the original server names, cluster nodes and IP addresses will be replaced by anonymized values, e.g. a server name bi-prod.mycompany.corp\:6400 may become name5.domain3.tld1\:15349, an IP4 address 10.20.30.40 may become 9078.10118.9351.9934 and an IP6 address like 2002\:1a57\:1e76\:\:1a64\:1c74 may become 11070\:16616\:17081\:\:16532\:17254. IP addresses and ports will have a randomized offset.

[In LMBI versions 3.0.18 or lower, these file had been created

las_result_<audit id>.xml (e.g. las_result_0000123456.xml)

lmbi_result_<audit id>.xml (e.g. lmbi_result_0000123456.xml)

contracts.xml]

In case of relevant changes (e.g. system measurements are added/replaced/deleted, contract data is changed or assignments from measures to contracts are modified) the generated result file(s) will become outdated which is indicated in the Result files: status line.


4.5 Sending LMBI Results to SAP

If you have been requested to provide measurement results as part of a license audit, then you should send the result_audit_<audit id>.lmbi file to the auditor, even if further integration with ABAP-based systems is planned or not.

4.6 Multiple Consolidations at Different Enterprise Levels - From Subsidiaries to Corporate Results

This guide described so far a standard procedure. However, some companies might face the special situation of having multiple (globally) dispersed subsidiaries (in the following called as ‘entities’) where single consolidations for each company are not suitable anymore, as some users exist on multiple systems across the whole company. Furthermore, multiple single results lead to a challenge when using the LAW (only one LMBI result can be imported).

This section describes a methodology that ensures measuring and consolidating for such scenarios.

Generally, all entities shall measure, group and consolidate their systems based on the standard workflow. As a result, each entity has its own results based on its own systems and contract(s). In contrary to the usual procedure, the (individual) LMBI results shall not be sent directly to the auditor/ shall not be import it to LAW.

To get a corporate result, collect the all_measures.xml files from all entities (they can be renamed to get them into one folder if required). The all_measures.xml file is stored by the consolidation component in selected subfolder of the data store location, e.g. in \lmbi_results\started_2013-04-29. The all_measures.xml file hold user data, user mappings, and information about the mapped contract model (but not the contract itself!) and thus fulfill all requirements for rebuilding joint results on a corporate level.

If all files are available, open the LMBI consolidation component and change the data store location to a new end empty folder (e.g. create and select a subfolder corporate_2013-05-15). If done so, go to step 1.2 View and import system measures and click on Import System Measures. Before the collected all_measures.xml files can be picked one by one, change the filter settings in the lower right corner of the import popup window from measure*.xml to *.xml. Import all all_measures.xml files.

Afterwards, go to step 1.3 View and import contract/licenses and import a contract file that holds all contracts that have been used by the entities before. As already mentioned, the all_measures.xml file holds information about the contract model each system has been mapped to, but it does not hold the contract itself. Consequently, to rebuild the mapping successfully, the corresponding contract models and licenses have to be part of the imported contract.

When the contract file is imported, a popup whether to keep or drop the assignments of the measured systems and contracts. Here, it is important to click No and keep the assignments. If you accidentally click Yes, you will have to remove the imported contracts and systems (i.e. remove everything in step 1.2 and 1.3) and start all over again or choose a new, blank data set folder). The procedure has been successful if in step 2.1 Assign system measures to licenses each system in the top left corner has a green check mark in column two (see screenshot below), indicating that it has been mapped to a contract model. Furthermore, when clicking on a system, the corresponding mapping on the right side will appear, showing the counted number of required licenses.

60 PUBLIC



When everything works fine, go to 3.1 Group and consolidate users and run the grouping and consolidation process. Finally, generate the result files in step 3.2 View Results and Status as known from the single entity consolidation and send the overall results to SAP and/or use one of the created result files for the consolidation in the LAW.

4.7 Requesting Technical Support

In case you have questions or face issues with the LMBI consolidation component, the main contact for first level support is your auditor (the contact who requested the license audit). If you face technical issues, you may also create an incident (https://launchpad.support.sap.com/#/incident/create) in the SAP Support Portal (https://support.sap.com). You should use the component BI-BIP-LMT, provide a description of the technical issue and the steps how to reproduce it, add the log file .log in the subfolder \workspace\.metadata of the LMBI consolidation component, and add the LMBI support file anonymous_measures.xml which can be created in the LMBI consolidation component. Click on the blue underlined folder path of the Data Store location and a Windows Explorer window will show that folder with the file in it.


5 Optimizing User Licenses by Merging Audit Results of SAP BusinessObjects BI Platform and SAP classic (ABAP-based systems) in the LAW

5.1 LMBI's Scalability Information

If only SAP BusinessObjects BI systems are audited, the results generated by LMBI would be enough to complete the audit. The use of the ABAP-based License Administration Workbench (LAW) wouldn’t bring any benefit. If you have SAP classic systems that are part of the audit, but your SAP BusinessObjects BI systems do not integrate SAP classic data and none of your BI users have any roles in SAP classic systems, the only benefit of loading the SAP BusinessObjects BI results into LAW would be the overview of a total result in one place. If you have users acting in both SAP classic systems and SAP BusinessObjects BI systems or if you integrate SAP classic data into your SAP BusinessObjects BI systems (indirect usage), there is a good chance that user licenses can be optimized by merging the audit results in LAW.

5.2 What are the Benefits of Merging Results Inside LAW?

Different licensing approaches may cover user access to both SAP classic data (directly or indirectly) and SAP BusinessObjects BI platform. A user may hold a license that grants access rights to both.

Example

User Mike Miller holds a SAP Application Limited Professional User license to cover his access to the company’s SAP classic systems. In addition, he and Susan Sun have viewer rights to a SAP BusinessObjects BI system that is licensed via a BI Package contract. Therefore, they both require a BI platform license and a BI Viewer license (or a SAP Application Business Information User license for integrated scenarios). The company covers the platform with 4 licenses with CPU metric. As the SAP Application Limited Professional User license of Mike includes the SAP Application BI Viewer User, one SAP Application BI Viewer license for just Susan Sun would be enough.

62 PUBLIC


Optimizing User Licenses by Merging Audit Results of SAP BusinessObjects BI Platform and SAP classic (ABAP-based systems) in the LAW

Since LMBI only knows about the users of the BI platform, its result would show two SAP Application BI Viewer User licenses, one for Mike and one for Susan. When the LMBI result is loaded into LAW and all user IDs of Mike can be grouped and consolidated, the LAW result will show the optimized result: one SAP Application Limited Professional User (for Mike), one SAP Application BI Viewer license (for Susan) and 4 licenses with CPU metric for the platform.

5.3 Required Patch and Service Pack Stack Levels

The hierarchy of user licenses shown in 4.2 is maintained in the LAW. Each user license has a certain ID (for example, EA for the SAP Application Business Analyst User), which might be price list specific (for example, 57, BL and CF for the SAP Application Business Expert User license). The list of relevant user licenses is shown below as well as the information which user license contains which other user licenses (hierarchy). The hierarchy of user licenses in LAW will contain the entries of the SAP BusinessObjects licenses starting with these versions of the SAP_BASIS component:

7.00 -> SPS 30

7.01 -> SPS 14

7.02 -> SPS 14

7.31 -> planned for SPS 10

7.40 -> SP4

If your system is at an older release, then check the Prior to Classification section at https://support.sap.com/keys-systems-installations/Measurement/information/user-classification.html .

License Measurement Tool for SAP BusinessObjects Business Intelligence Platform (LMBI) GuideOptimizing User Licenses by Merging Audit Results of SAP BusinessObjects BI Platform and SAP classic (ABAP-based systems) in the LAW PUBLIC 63

http://help.sap.com/disclaimer?site=https%3A%2F%2Fsupport.sap.com%2Fkeys-systems-installations%2FMeasurement%2Finformation%2Fuser-classification.html

http://help.sap.com/disclaimer?site=https%3A%2F%2Fsupport.sap.com%2Fkeys-systems-installations%2FMeasurement%2Finformation%2Fuser-classification.html

5.4 How to Match User IDs of SAP BusinessObjects BI Platform & SAP Classic Systems

To get to an optimized result, the LMBI result has to be loaded into LAW and the user IDs from the BusinessObjects systems have to match the corresponding SAP classic user IDs. All details on the LAW, including how to group and consolidate users, are documented in the License Administration Workbench (LAW) section at in the SAP Support Portal at https://support.sap.com/keys-systems-installations/Measurement/law.html .

User attributes that potentially match and which might be used as the LAW’s grouping criteria are:

64 PUBLIC



http://help.sap.com/disclaimer?site=https%3A%2F%2Fsupport.sap.com%2Fkeys-systems-installations%2FMeasurement%2Flaw.html

http://help.sap.com/disclaimer?site=https%3A%2F%2Fsupport.sap.com%2Fkeys-systems-installations%2FMeasurement%2Flaw.html

● User ID – However, it is restricted to 12 characters in SAP classic.● User Name – However, BOE IDs need to be split up into first name and last name. The algorithm to do so in

the consolidation component uses spaces to split the full name into parts and assign them to the first name and the last name. For a BusinessObjects BI user ID with○ 1 space, the first part is used as first name and the second part as last name - example: “Mike Miller”

translates into “Mike” (first name) and “Miller” (last name)○ 2 spaces, the first and second part are used as first name and the third part as last name - example:

“Mike Peter Miller” translates into “Mike Peter” (first name) and “Miller” (last name)○ 3 spaces, the first two parts are used as first name and the last two parts as last name - example:

“Javier Jaime Ruiz Guzman” translates into “Javier Jaime” (first name) and “Ruiz Guzman” as last name

○ more than 3 spaces, the first two parts are used as first name and the rest as last name - example: “Carmen Maria Duran del Ruiz” translates into “Carmen Maria” (first name) and “Duran del Ruiz” as last name

○ no space, the first name and last name will be left empty● The email address is potentially a good match; in some cases it can’t be used for grouping because people

share the same email address such as [email protected] and would be merged as into one user● If the BOE server is connected to SAP classic systems and SAP aliases are maintained with the BOE user

IDs, those might be a good match, too. The LMBI result file for the LAW will then replace the BOE user ID by the SAP alias. If more than one SAP system is connected per BOE server, or if several BOE servers have been measured which are connected to different SAP classic systems, the situation may occur that a user has more than one (different) SAP aliases. In this case LMBI will take the SAP alias from the “first” system where the user has a SAP alias. This might seem a little bit unspecified, however it is questionable if the SAP classic user ID is a suitable grouping criteria in LAW at all if already user IDs do not match among the SAP classic systems. In case a SAP alias occurs with invalid characters, it will be replaced by an automatically generated, unique ID generated by LMBI. The LAW 1.0 usually allows characters A-Z, a-z, 0-9 and special characters. Generally there is no indication to change the set of allowed characters. For special situations it can be extended in the LMBI preferences, but should be done carefully as it may lead to export/import issues of the generated result files.

5.5 How to Load LMBI Results into LAW

5.5.1 Grouping and Consolidating Users in LMBI is a Prerequisite

It is a technical prerequisite to run grouping and consolidating users in LMBI first, otherwise the required result files for the LAW will not be generated. The idea behind it is that all BusinessObjects BI systems with grouped and consolidated users can be handled just the same way as one SAP classic component system.


5.5.2 Choose the Correct LMBI Result File

If grouping and consolidation has run, up to three additional files will be generated in the data set folder (for example, \lmbi_results\started_2013-04-29) when the Generate result files (Update result files) button is pressed:

• law_result_with_boe_ids.xml – this file can be used if the user IDs on the BOE servers match with the user IDs of the SAP classic systems. The file will only be generated if Group identical user IDs has been checked when starting grouping and consolidation.

• law_result_with_sap_ids.xml – this file can be used if the SAP aliases of the BOE users shall be used as user IDs in LAW. The file will only be generated if Group identical** SAP aliases (alias-alias and alias-user ID pairs) has been checked when starting grouping and consolidation. If email address or user name shall be used as grouping criteria in LAW, any of the files may be used.

• law_result_with_lmbi_ids.xml – use it for rare cases where different users have the same user ID and for that reason the user ID can’t be used as a grouping criterion in LMBI (step 3.1 / chapter 3.4.4). The user IDs in this file have been replaced by unique, continuous IDs like/in the format LMBI01234567.

If none of these files has been generated, likely the step 3.1 Group and consolidate users has not been performed or no named user license metrics are in use that can be merged in LAW.

This applies in particularly to cases where ONLY CPU metrics are used to cover both to platform and editors in a stand-alone scenario (this licensing option was available in Legacy and A-la-carte contracts). For these cases the step 3.1 Group and consolidate users is disabled and as such no LAW files can be generated – as well as there is no need/benefit to bring the LMBI results into LAW.

5.5.3 LAW 2.0: Import LMBI Result File into LAW 2.0

If you are using LAW 2.0, you won’t have to go through the conversion. You can import the LMBI file directly. To do so, go to step 2 in LAW 2.0 Manage results and use the Import Result button to load one of the files.

5.5.4 LAW 1.0: Convert the LMBI Result File into a Text File Compatible with LAW 1.0

LAW 1.0 doesn’t support the import of the XML result files generated by LMBI directly. Therefore, the files need to be converted into a text file.

In the ABAP system that hosts your LAW, start transaction SE38. Enter the program name SLIM_XML_CONV and run it (for example, by pressing F8). If the program is not yet available or not on version 5, use transaction SNOTE and SAP note 1782186 to install it. Versions 4 and will likely not work due to bug: If users IDs with a length different from 12 characters are loaded, the converter fails with an exception.

In the converter, choose the option Convert XML File to SID Format and press run. A file selection dialog opens. Select one of the XML result files described in 4.5.2. and press open. The converter will read the selected XML file and will generate a text file with the same name (with the file ending .txt instead of .xml) in the same folder.

66 PUBLIC



Copying or moving the file might influence the code page used for its encoding with negative impact on its compatibility.

5.5.5 LAW 1.0: Import the Converted LMBI Result File into LAW 1.0 and Consolidate

Run the transaction SLAW to start the LAW. Use the Measurement Data > Import Data > From Component System to import the converted LMBI result file.

The LAW will handle the set of measured system such as one SAP classic component system. The standard LAW features to display, group and consolidate users will be available in the same way as to SAP classic systems. Complete the consolidation and send the joint result to SAP.


6 Security Guide & Privacy Aspects

6.1 Data Measured at Customer Side

The set of data that is processed by the LMBI is restricted to what is needed for license measurement and consist of:

• the list of license keys deployed to the system

• the list of server nodes of the system and some metrics such as CPU information and IP addresses

• the number of documents per document type and the number of unique user IDs who created/duplicated them

• the list of users in the system, their user attributes, authentication method and their (effective) user rights, limited to a small subset of rights to keep license evaluation effective

• Counts of user classifications and licenses

• a list of technical rights available in the system

• metadata such as version numbers, start dates & duration of the measurement

The list of users might be an object of your local data protection policy. The measurement files and the persistence files created by the consolidation component includes user identities (ID, names, email, aliases, last logon date and creation date of the user ID; for BI 4.1 with multi-tenant setup, the tenant ID might be added in future) and their assigned license profiles per system. If necessary, those files shall be stored in secured file persistence (e.g. network share with limited access by a well-defined set of users). The consolidation component of the LMBI works only with the result files from the measurement.

6.2 Data Sent to SAP

Most of the data measured at customer side will also be sent to SAP with the result file. However, user list will be excluded from the final result file (result_audit_<audit id>.lmbi or lmbi_result_<audit id>.xml).

In case a support file is generated, the user attributes user ID, user name, user email and alias name will be anonymized, for example, the user names of the first user will be replaced by "name_1".

68 PUBLIC


Security Guide & Privacy Aspects

7 Frequently Asked Questions

LMBI Consolidation Component

1. Will the installation make entries to the Microsoft Windows registry? What is the “footprint” of LMBI? How to uninstall LMBI?

LMBI has a minimal footprint; it will not make any changes to the Microsoft Windows registry nor causes the generation of system restore points etc. The “installation” of LMBI is practically just the extraction of files to a folder structure. During its operation, LMBI will generate files to store results, for logging and configuration data. In addition the activity of the measurement component might leave traces on the BusinessObjects Enterprise server in the logging and auditing functionality. By default, all these files will be stored in subfolders. When you delete the folder structure, all traces of the LMBI on the client will be gone. However, SAP highly recommends to keep the result files at least until the license audit is completed.

LMBI Measurement Component

1. Which data does LMBI send to SAP?

LMBI itself has no build-in transfer mechanism. All results are stored in local text/xml files, so you have full control and can review the data before sending it. Data transfer needs to be handled outside the LMBI tool, e.g. via email. When you send in results to your (SAP) auditor, the final result files will only contain aggregated numbers and counting, but no individual/personal user data. For further details, please refer to chapter 5.

2. With the installation of the LMBI, will SAP continuously track my users?

No. The measurement component will only read data when it is started by a user and requires administrative rights. In addition, the LMBI will write data only to the local file system into predefined folders, but will not transfer any files to SAP itself.

3. Will the installation make entries to the Microsoft Windows registry? What is the “footprint” of LMBI? How to uninstall LMBI?

LMBI has a minimal footprint; it will not make any changes to the Microsoft Windows registry nor causes the generation of system restore points etc. The “installation” of LMBI is practically just the extraction of files to a folder structure. During its operation, LMBI will generate files to store results, for logging and configuration data. In addition, the activity of the measurement component might leave traces on the BusinessObjects Enterprise server in the logging and auditing functionality. By default, all these files will be stored in subfolders. When you delete the folder structure, all traces of the LMBI on the client will be gone. However, SAP highly recommends to keep the result files at least until the license audit is completed.

4. Which user rights do I need on my Microsoft Windows desktop to install and run the tool?

You’ll need to have permission to create files, particularly a root folder for the installation of the LMBI. In addition, a proper Java Runtime Environment needs to be set up. Practically, it could also, run as a portable

License Measurement Tool for SAP BusinessObjects Business Intelligence Platform (LMBI) GuideFrequently Asked Questions PUBLIC 69

application from an USB stick. The firewall needs to allow communication via the ports in use (by default 6400, 6401 and the HTTP port, also refer to the chapter Working with Firewalls in the BOE Administrator Guide).

70 PUBLIC


Frequently Asked Questions

8 Abbreviations

Abbreviation Description

BI Business Intelligence, the main capability of SAP BusinessObjects Enterprise platform. It is not meant for the usage type as Business Intelligence of the SAP NetWeaver platform.

BOE Former name of the SAP BusinessObjects Business Intelligence platform

BW SAP NetWeaver Business Warehouse (formerly also known as usage type Business Intelligence of the SAP NetWeaver platform or SAP Business Information Warehouse)

CAL Concurrent access license

CMS Central management system

CMC Central management console

CPU Most common CPU metric definition to calculate the metric value: For each CPU, the first processor core shall be multiplied by 1, and each incremental processor core of that CPU is multiplied by 0.5. The sum for all CPUs shall then be rounded up to the next whole number.

CSBL Concurrent session based license

GLAS Global license auditing services; partially used for labeling files

JRE Java runtime environment

JSE Java platform, standard edition

LAW License administration workbench; SAP ABAP based system to consolidate user and engine results from SAP classic; can also integrate SAP BusinessObjects BI audit results

LMBI License measurement tool for SAP BusinessObjects BI platform

NUL Named user license

ODBC Open Database Connectivity

SBOP SAP BusinessObjects portfolio

SDK Software development kit

License Measurement Tool for SAP BusinessObjects Business Intelligence Platform (LMBI) GuideAbbreviations PUBLIC 71

Important Disclaimers and Legal Information

HyperlinksSome links are classified by an icon and/or a mouseover text. These links provide additional information.About the icons:

● Links with the icon : You are entering a Web site that is not hosted by SAP. By using such links, you agree (unless expressly stated otherwise in your agreements with SAP) to this:

● The content of the linked-to site is not SAP documentation. You may not infer any product claims against SAP based on this information.● SAP does not agree or disagree with the content on the linked-to site, nor does SAP warrant the availability and correctness. SAP shall not be liable for any

damages caused by the use of such content unless damages have been caused by SAP's gross negligence or willful misconduct.

● Links with the icon : You are leaving the documentation for that particular SAP product or service and are entering a SAP-hosted Web site. By using such links, you agree that (unless expressly stated otherwise in your agreements with SAP) you may not infer any product claims against SAP based on this information.

Videos Hosted on External PlatformsSome videos may point to third-party video hosting platforms. SAP cannot guarantee the future availability of videos stored on these platforms. Furthermore, any advertisements or other content hosted on these platforms (for example, suggested videos or by navigating to other videos hosted on the same site), are not within the control or responsibility of SAP.

Beta and Other Experimental FeaturesExperimental features are not part of the officially delivered scope that SAP guarantees for future releases. This means that experimental features may be changed by SAP at any time for any reason without notice. Experimental features are not for productive use. You may not demonstrate, test, examine, evaluate or otherwise use the experimental features in a live operating environment or with data that has not been sufficiently backed up.The purpose of experimental features is to get feedback early on, allowing customers and partners to influence the future product accordingly. By providing your feedback (e.g. in the SAP Community), you accept that intellectual property rights of the contributions or derivative works shall remain the exclusive property of SAP.

Example CodeAny software coding and/or code snippets are examples. They are not for productive use. The example code is only intended to better explain and visualize the syntax and phrasing rules. SAP does not warrant the correctness and completeness of the example code. SAP shall not be liable for errors or damages caused by the use of example code unless damages have been caused by SAP's gross negligence or willful misconduct.

Gender-Related LanguageWe try not to use gender-specific word forms and formulations. As appropriate for context and readability, SAP may use masculine word forms to refer to all genders.

72 PUBLIC


Important Disclaimers and Legal Information

License Measurement Tool for SAP BusinessObjects Business Intelligence Platform (LMBI) GuideImportant Disclaimers and Legal Information PUBLIC 73

www.sap.com/contactsap

© 2020 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. The information contained herein may be changed without prior notice.

Some software products marketed by SAP SE and its distributors contain proprietary software components of other software vendors. 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 or its affiliated companies shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP 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.

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. All other product and service names mentioned are the trademarks of their respective companies.

Please see https://www.sap.com/about/legal/trademark.html for additional trademark information and notices.

THE BEST RUN

https://www.sap.com/about/legal/trademark.html