Download License Measurement for SAP BusinessObjects Enterprise

License measurement tool for
SAP BusinessObjects Business Intelligence
platform (LMBI)
Version 3
Measurement Guide
Document version 1.9
License Measurement for SAP BusinessObjects Enterprise
Typographic Conventions
Type Style
Example
Description
Example
Output on the screen.
EXAMPLE
Keys on the keyboard, for example, F 2 or E N T E R .
File names
Document History
Version
Date
Change
1.9
2017-01-02
Several updates related to changes in file and path names in LMBI 3.0.28
Added chapter 2.4
Added chapter 3.5.3 Adjustments for SSL setups
Updated CPU commands for Solaris in 8.2.1
1.8
2016-07-22
Added handling for Hyper-V (8.1.2)
Added chapter 3.7.4
Added chapter 4
Updated page footer
1.7
2016-01-14
Updated supported JRE/JDK versions and BI platform versions
Java memory settings adjusted in 2.2 (default now is yet 1024MB)
Updated measurement runtime, chapter (2.3)
Included Linux measurement instructions (SAP note 2158262)
Updated how to measure multiple systems
Added SAP Crystal Server to the list of supported servers
1.6
2015-07-23
Updated CPU metric section
Added note how to run the measurement on Linux (chapter 1.3.1)
Updated Security Guide (additional user attributes read)
Updated FAQs
1.5
2015-03-10
Initial version (previously part of the LMBI master guide)
LMBI packaging changed with version 3.0.8 - updated affected sections
Updated link to SAP support portal
Updated section 2.1 third party authentication
Added screenshot in chapter
LMBI 3 Measurement Guide
Page 2
License Measurement for SAP BusinessObjects Enterprise
Table of contents
1
INTRODUCTION ........................................................................................................................................ 5
1.1
ABOUT THE LMBI AND THIS GUIDE .................................................................................................................. 5
1.2
WHICH SYSTEMS NEED TO BE MEASURED .......................................................................................................... 5
1.3
LIMITATIONS ............................................................................................................................................... 5
1.3.1
Limitations of the measurement components................................................................................. 5
1.4
OPERATIONAL TASKS OVERVIEW ...................................................................................................................... 6
1.4.1
Pre-requisites................................................................................................................................... 6
1.4.2
Installation information .................................................................................................................. 6
1.4.3
Configuration information............................................................................................................... 6
1.4.4
Operations Information ................................................................................................................... 6
1.4.5
Security information ........................................................................................................................ 6
1.4.6
Upgrade information ....................................................................................................................... 6
1.4.7
Requesting technical support .......................................................................................................... 6
2
PREPARATIVE STEPS TO THE MEASUREMENT ........................................................................................... 7
2.1
THIRD PARTY AUTHENTICATION - PREVENT COUNTING OF DISABLED OR EXPIRED USERS ............................................... 7
2.1.1
Finding disabled or expired users with authentication method “SAP R/3”/“SAP” .......................... 7
2.2
INCREASE THE MEMORY SETTINGS FOR LARGE INSTALLATIONS (> 40.000 USERS) ...................................................... 8
2.3
ESTIMATES ON THE MEASUREMENT RUNTIME .................................................................................................... 8
2.4
REQUIRED ADMINISTRATION RIGHTS FOR THE USER THAT RUNS THE LMBI MEASUREMENT ......................................... 8
2.4.1
Read permissions for “Folders” and “Personal Folders”.................................................................. 9
2.4.2
Read permissions for “Users” and “User Groups” ........................................................................... 9
2.4.3
Read permissions for “Servers” and “Server Groups”...................................................................... 9
2.4.4
Access to the license keys .............................................................................................................. 10
2.4.5
Access to the CMC application ...................................................................................................... 10
3
INSTALLING AND RUNNING THE MEASUREMENT COMPONENTS ........................................................... 11
3.1
GENERAL INSTALLATION COMMENTS AND RECOMMENDATIONS ........................................................................... 11
3.2
VERSION NUMBERS (SUCH AS 3.0.28) AND HOW TO INSTALL LMBI PATCHES .................................................... 11
3.3
CHECKING THE JAVA RUNTIME VERSION .......................................................................................................... 11
3.4
DO NOT USE THE BOLMT TOOL IN THE BI PLATFORM SHIPMENT ......................................................................... 11
3.5
MEASURING SAP BUSINESSOBJECTS BI PLATFORM 4.X, XI 3.X AND XIR2 SYSTEMS ................................................ 12
3.5.1
Required ports if the measurement component runs on a client PC ............................................. 12
3.5.2
Installation folder .......................................................................................................................... 12
3.5.3
Adjustments for SSL support ......................................................................................................... 12
3.5.4
Start the measurement component .............................................................................................. 13
3.5.5
Exception handling ........................................................................................................................ 13
3.5.6
Select a template / repository ....................................................................................................... 13
3.5.7
Log on to the repository ................................................................................................................ 14
3.5.8
Read user rights and determine user types ................................................................................... 15
3.5.9
File location of the measurement results ...................................................................................... 16
3.5.10 Measuring further systems............................................................................................................ 16
3.6
MEASURING BUSINESSOBJECTS 5.X / 6.X SYSTEMS........................................................................................... 17
3.6.1
Where to install the measurement component? ........................................................................... 17
3.6.2
Installation folder .......................................................................................................................... 17
3.6.3
Copy the GLAS.unv file to your universe folder .............................................................................. 17
3.6.4
Adjust program paths in the configuration .xml files .................................................................... 17
3.6.5
Start the measurement component .............................................................................................. 18
3.6.6
Select a System / Repository ......................................................................................................... 18
3.6.7
Select database connection ........................................................................................................... 18
3.6.8
Read user rights ............................................................................................................................. 19
3.6.9
Evaluate user types ....................................................................................................................... 21
3.6.10 File location of the measurement result ........................................................................................ 21
3.7
SPECIAL ADJUSTMENTS & EXCEPTION HANDLING............................................................................................... 21
3.7.1
How to read the settings for the CMS and the Request Port in the CMS ...................................... 21
3.7.2
‚Full Control‘ for ‚Everyone‘ on Windows 7 on installation folder ................................................. 22
3.7.3
Exception handling: ....................................................................................................................... 23
3.7.4
How to identify and solve a connection issue ................................................................................ 23
Page 3
LMBI 3 Measurement Guide
License Measurement for SAP BusinessObjects Enterprise
4
REQUESTING TECHNICAL SUPPORT ........................................................................................................ 25
5
SECURITY GUIDE ..................................................................................................................................... 25
6
FREQUENTLY ASKED QUESTIONS ............................................................................................................ 26
7
HOW USER RIGHTS CLASSIFY USERS ....................................................................................................... 27
7.1
7.2
7.3
8
USER RIGHTS RELEVANT FOR SAP BUSINESSOBJECTS BUSINESS INTELLIGENCE PLATFORM 4.X ................................... 28
USER RIGHTS RELEVANT FOR BUSINESSOBJECTS ENTERPRISE PLATFORM XI 3.X AND XIR 2 ....................................... 29
USER RIGHTS RELEVANT FOR BUSINESSOBJECTS ENTERPRISE PLATFORM 5.1.X AND 6.X ........................................... 29
CPU METRIC - WHERE TO FIND REQUIRED HARDWARE DATA? ............................................................... 30
8.1
BI SYSTEM RUNS IN A VIRTUAL MACHINE ......................................................................................................... 30
8.1.1
Find the required data in the configuration of the hypervisor ...................................................... 30
8.1.2
Hyper-V - find the required data ................................................................................................... 31
8.1.3
Other virtualization technologies - find the required data in the guest operating system ........... 31
8.1.4
Enter the data of a virtual machine into the consolidation component ........................................ 31
8.2
PHYSICAL DEPLOYMENT OF THE BI SYSTEM (CAN ALSO BE USED INSIDE A VM) ........................................................ 32
8.2.1
Find the required data in the operating system ............................................................................ 32
8.2.2
Enter the data of a physical deployment into the consolidation component ................................ 34
8.3
FURTHER CPU DATA OPTIONS FOR CLUSTERED BI SERVERS ................................................................................. 34
8.3.1
Providing custom CPU metric values ............................................................................................. 35
8.3.2
Reusing the CPU data of another server node .............................................................................. 35
8.3.3
Clusters with multiple server nodes ............................................................................................... 35
9
ABBREVIATIONS ..................................................................................................................................... 36
10 COPYRIGHT ............................................................................................................................................. 37
10.1
FURTHER REMARKS ..................................................................................................................................... 37
LMBI 3 Measurement Guide
Page 4
License Measurement for SAP BusinessObjects Enterprise
1
Introduction
1.1
About the LMBI and this guide
The license measurement tool for SAP BusinessObjects Business Intelligence platform (LMBI)
provides a standardized way to extract information required for a license audit from a BI/
BusinessObjects Enterprise platform (or Crystal Reports) server(s). This documentation will guide you
through all required steps of the license measurement and will tell you which files you shall provide.
The provided measurement components are standalone Java clients. Corresponding measurement
components exist to address the different versions of the BI/BusinessObjects Enterprise 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. Details are described in chapter 7 “”.
The measurement components save the results in XML files which starting with the prefix
“measure”. These files are required to compute the audit result. Chapters 3.5.9 and 3.6.10
describe where to find these files.
As the license measurement may cause some additional load on the system (see hints in chapter 2.3),
you may consider running the license measurement out of times with system peak loads.
1.2
Which systems need to be measured
Generally, all systems at customer side running a BusinessObjects Enterprise server or Crystal
Reports server have to be measured with the LMBI. This does not only refer to productive systems,
but also to any other system whatever propose it is used for (test, development etc.). SAP’s license
auditors will consider the contractual obligations including the terms if and how many licenses you
require for non-productive systems.
1.3
Limitations
The current version LMBI 3.0 comes with a few limitations described here.
1.3.1
Limitations of the measurement components
Supported versions of the BusinessObjects Enterprise platform
The measurement component supports all recent (SAP) BusinessObjects Business Intelligence
products that are based on the BusinessObjects Enterprise platform. The list of supported versions is:












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*
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
*) Including the corresponding SBOP Edge BI versions.
Required Java version and supported (client) operating systems
The measurement components require a Java runtime environment with version 1.5 or newer. You
may run them on Linux (except BusinessObjects Enterprise 6.x and 5.x) and Windows.
Page 5
LMBI 3 Measurement Guide
License Measurement for SAP BusinessObjects Enterprise
1.4
Operational tasks overview
1.4.1
Pre-requisites
There are no pre-requisites.
1.4.2






Installation information
General – chapter 3.1
Measurement component for BI 4.x - chapters 3.5.1 and 3.5.2
Measurement component for BOE XI 3 - chapters 3.5.1 and 3.5.2
Measurement component for BOE XIR2 - chapters 3.5.1 and 3.5.2
Measurement component for BOE 6.x - chapters 3.6.1 to 3.6.3
Measurement component for BOE 5.1.x - chapters 3.6.1 to 3.6.3
1.4.3
Configuration information
 Measurement component for BOE 6.x – chapter 3.6.4
 Measurement component for BOE 5.1.x - chapter 3.6.4
1.4.4





Operations Information
Measurement component for BI 4.x - chapter 3.3
Measurement component for BOE XI 3 - chapter 3.3
Measurement component for BOE XIR2 – chapter 3.3
Measurement component for BOE 6.x – chapter 3.6
Measurement component for BOE 5.1.x – chapter 3.6
1.4.5
Security information
Refer to chapter 5.
1.4.6
Upgrade information
Refer to chapter 3.2.
1.4.7
Requesting technical support
Refer to chapter 4.
LMBI 3 Measurement Guide
Page 6
License Measurement for SAP BusinessObjects Enterprise
2
Preparative steps to the measurement
2.1
Third party authentication - prevent counting of disabled or expired users
By default, the BOE server handles the authentication itself with the Enterprise authentication method.
In addition, third party authentication methods are supported.
Chapter 12 of the Administrator’s Guide
(http://help.sap.com/boe31) lists these
authentication methods for BOE 3.1:




SAP R/3
LDAP
Windows Active Directory
Windows NT
Chapter 9.1 of the Administrator’s Guide
(http://help.sap.com/boe31) lists these
authentication methods for BI 4.1 SP 2:
 Enterprise
 LDAP
 Windows AD
 SAP
 Oracle EBS
 Siebel
 JD Edwards
 PeopleSoft
For users with the default authentication method Enterprise, all user data is stored on the BOE server
itself. This is different for users with assigned third party authentication. Often just a skeleton of a user
object resides on the BOE server that holds BOE specific data. Further relevant data like the validity of
the user remain on the third party system and is typically checked during the authentication process.
This may become a challenge during the license measurement. The measurement will loop over the
BOE list of user IDs. User IDs with Enterprise authentication that are disabled will be marked as such
and will not be considered.
In contrast, all user IDs on the BOE server with third party authentication will be counted, as the BOE
server doesn’t hold data on the validity of a user ID. To prevent counting of disabled or expired users
in the license measurement, disable the corresponding third party authentication aliases for the
corresponding users. Alternatively, remove the users IDs of these disabled users from the BOE server
before the measurement.
2.1.1
Finding disabled or expired users with authentication method “SAP R/3”/“SAP”
Disabled or expired users with SAP R/3 authentication can be identified and excluded with
corresponding reports on the ABAP system. Transaction S U I M (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 S U 1 0 with the selection of Authorization Data would allow the selection of
invalid users in combination with certain roles. The relevant roles for the BOE server shall be removed
Page 7
LMBI 3 Measurement Guide
License Measurement for SAP BusinessObjects Enterprise
from invalid (disabled or expired) users on the ABAP side and the user/role synchronization between
the ABAP and the BOE system need to be refreshed to remove the invalid user IDs from the BOE
server and prevent them from being counted.
2.2
Increase the memory settings for large installations (> 40.000 users)
If your BOE server has less than 40.000 users, this chapter can be skipped. The number of users can
be checked in the CMC (Users and Groups > User list > view the total number of users in the lower
right corner).
Number of estimated MB of
If the number of users exceeds 40.000, the startup script of the
users
memory
measurement component needs to be adjusted to provide sufficient
memory. An estimate for the required amount of memory is given in the
25.000
600 MB
table on the right. As a rule of thumb, some 500 MB per 25.000 users
50.000
1.100 MB
would be required with a minimal use of some 100 MB.
75.000
1.600 MB
To change the memory settings for a measurement component, make
100.000
2.100 MB
sure you followed at least the steps described in chapters 3.1 to 3.5. If
done so, open the respective folder of the version aimed to measure (e.g.
125.000
2.600 MB
BI4.x_Component-3.0.0 for SAP BusinessObjects BI 4.x systems) and
150.000
3.100 MB
open the Measure.cmd file (or Measure.sh for Linux). The memory
175.000
3.600 MB
settings are set close to the end of the script in these line:
200.000
java -Xms32m -Xmx1024m %SSL% com.sap.glas.systemMeasurement.Run -classpath
%CLASSPATH%
4.100 MB
In the default configuration, the Java virtual machine will be started with a maximum heap size of 1024
MByte (and an initial minimum heap size of 32 MByte).
Increase the value of the parameter –Xmx accordingly, e.g. to –Xmx1100m if you have a system
with 50.000 users or less. 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.
In addition, be aware that a 32-bit Java runtime (JRE) on Windows would only be able to allocate
around 1,5 GB RAM. So larger installations require a 64-bit JRE to have sufficient memory available.
2.3
Estimates on the measurement runtime
The time required to run the measurement is influenced by various factors. It will grow with:
 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
The measurement components will provide information on the progress and the estimated duration, for
the time consuming user rights measurement every 10 seconds (see chapter 3.5.8 for details). Apart
from this information, it is difficult to make a reliable prediction how long the measurement time will be.
This can be a range between several minutes up to hours or in some cases even days. Fortunately the
measurement script usually will not cause a significant load on the BI server (nor the data base
server), at lease if you have more than two cores.
2.4
Required administration rights for the user that runs the LMBI measurement
The user that runs the measurement ideally has unrestricted administration rights.
If this is not possible, please make sure the user has at least rights listed in the rest of this chapter.
For some of these rights, LMBI starting with version 3.0.28 will perform a check right after logon. If any
of the checked rights is missing, these will be listed in a popup like the one shown on the screenshot
below. The access rights to folders (2.4.1) are currently not checked, but still will have a negative
impact if they are not granted.
LMBI 3 Measurement Guide
Page 8
License Measurement for SAP BusinessObjects Enterprise
2.4.1
Read permissions for “Folders” and “Personal Folders”
The user requires at least the right “View objects” on “Folders” (root folder) and on “Personal Folders”.
To grant the right for “Folders” to a user in the CMC, click on Folders  Manage  Top-Level Security
 All Folders  Add Prinicpal  select the user that runs the measurement Add and Assign
Security  Advanced  Add/Remove Rights  select the radio button in the column Granted for the
right View objects.
To grant the right for “Personal Folders”, manage the top-level security for All Personal Folders
accordingly.
2.4.2
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.
2.4.3
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.
Page 9
LMBI 3 Measurement Guide
License Measurement for SAP BusinessObjects Enterprise
To grant the right for “Server Groups”, manage the top-level security for All Server Groups accordingly.
2.4.4
Access to the license keys
The user must be a member of the group Administrators.
2.4.5
Access to the CMC application
To grant the required rights in the CMC, click on Applications  Central Management Console 
User Security  Add Principal  select the user that runs the measurement Add and Assign
Security  Advanced  Add/Remove Rights  select the radio button in the column Granted for the
right Log on to the CMC and view this object in the CMC.
LMBI 3 Measurement Guide
Page 10
License Measurement for SAP BusinessObjects Enterprise
3
Installing and running the measurement components
3.1
General installation comments and recommendations
The LMBI measurement components for BI 4.x, XI 3 and XIR2 can run from a local PC and connect to
the BI server. Just the measurement component for BusinessObjects Enterprise (BOE) 6.x and 5.1.x
systems need to run on the BOE server itself.
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.28.zip
For BusinessObjects Enterprise XI 3: XI3_Component-3.0.28.zip
For BusinessObjects Enterprise XIR2: XIR2_Component-3.0.28.zip
For BusinessObjects Enterprise 6.x and 5.1.x: X_BOE-3.0.28.zip
3.2
Version numbers (such as 3.0.28) and how to install LMBI patches
Future patches will have similar file names with different version numbers in the file names (e.g.
BI4.x_Component-3.0.28.zip may become BI4.x_Component-3.0.29.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 central release note 1854405 lists the available patches for LMBI.
3.3
Checking the Java Runtime version
The computer you choose for the measurement component installation requires a Java Runtime
Environment (JRE) or a Java Software Development Kit (SDK, SE or EE) with Java version 5 (1.5)
or newer. If you encounter errors or if you are not sure if the JRE is configured properly, you can
check this by simply open a command shell and type java –version to get a prompt. The first
response line will contain the version number, the second line will indicate if it is a 64-Bit version (left
screenshot below).
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 will keep the existing JRE/JDK installation untouched for potentially existing server
applications requiring a specific Java version.
3.4
Do not use the BOLMT tool in the BI platform shipment
Some versions of the Business Intelligence Platform Administrator Guide describes the use of the
BusinessObjects License Measurement Tool (BOLMT). However, the results generated by the current
BOLMT can NOT be used for license audits and shall not be loaded into LMBI or LAW.
Page 11
LMBI 3 Measurement Guide
License Measurement for SAP BusinessObjects Enterprise
3.5
Measuring SAP BusinessObjects BI platform 4.x, XI 3.x and XIR2 systems
3.5.1
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, XI3 and BI 4 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.5.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 BI4.x_Component-3.0.28.zip to the
subfolder BI4.x_Component-3.0.28 of the measurement folder.




For SAP BusinessObjects BI 4.x, extract BI4.x_Component-3.0.28.zip
For BusinessObjects Enterprise XI 3, extract XI3_Component-3.0.28.zip
For BusinessObjects Enterprise XIR2, extract XIR2_Component-3.0.28.zip
For BusinessObjects Enterprise 6.x and 5.1.x, extract X_BOE-3.0.28.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.3
Adjustments for SSL support
To check if you have SSL enabled on a BI
4 system, open the Central Configuration
Manager and check the properties of the
Server Intelligence Agent (SIA). SSL is
enabled, if the Enable SSL checkbox is
checked on the Protocol’s tab.
If SSL is enabled, you must have a copy of
these files shown on this tab on the
machine/PC where you start the LMBI
measurement.
Configuration if LMBI runs on Windows
For Windows you have to check if the script Measure_with_SSL.cmd has the correct configuration.
The default directory for the SSL files C:\SSL (line 4), the file names for the certificates cacert.der
(line 5) and servercert.der (line 6), the key server.key (line 7) and passphrase passphares.txt
(line 8) can be reconfigured if required.
Configuration if LMBI runs on Linux
For Linux you have to check if the script Measure_with_SSL.sh has the correct configuration. In line
23 the default directory (/home/user/Downloads/SSL) and the file names for the certificates
LMBI 3 Measurement Guide
Page 12
License Measurement for SAP BusinessObjects Enterprise
cacert.der and servercert.der, the key server.key and passphrase passphares.txt can be
reconfigured if required.
3.5.4
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. This will set the SSL parameters
accordingly and then start the Measure.cmd script.
Linux
First make sure that both scripts the Measure.sh and Measure_with_SSL.sh are enabled for
execution. You enable the execution with the chmod command. To do so, open a terminal window and
use the cd command navigate to the folder with the corresponding measurement component, e.g. to
the folder /home/usr/Downloads/LMBI/measurement/BI4.x_Component-3.0.28. In that folder,
execute the command chmod 755 Measure.sh and chmod 755 Measure_with_SSL.sh.
To start the measurement, start the corresponding shell script with a double-click in a file explorer or
in terminal window using the sh Measure.sh / the sh Measure_with_SSL.sh command. Use


the Measure.sh script if SSL is not enabled.
the Measure_with_SSL.sh script if SSL is enabled.
The measurement will use a (Java Swing) UI. If you just use a text based remote connection tool like
Putty, you will get a NoClassDefFoundError: sun.awt.X11GraphicsEnvironmnet error.
3.5.5
Exception handling
If you face any issues, please check chapter 3.7.3.
3.5.6
Select a template / repository
After starting the measurement component, a command shell and a window similar to the ones below
should open.
Click on 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) will appear and show
details on the right hand side.
 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.
Page 13
LMBI 3 Measurement Guide
License Measurement for SAP BusinessObjects Enterprise

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.5.7
Log on to the repository
Use the menu “Prepare”  “Log On” to start the log on to the repository.
The input fields and their meaning are described in the logon screen. Additional comments:
 Server name: The server’s network name (e.g. used to ping it). It is also contained in the URL
used access the CMS.
Example: Use the server name prod-sp2.sap.com for the field system if you use http://prodsp2.sap.com:8080/businessobjects/enterprise115/admin/en/admin.cwr to access the CMC.
If you use a name server port different from 6400, you’ll have to add that, e.g. prodsp2.sap.com:7400 if your name server port has been changed to 7400.
 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 stand-alone user can be changed later if
necessary
 “Stand-alone” means there is no data loaded/shown from classic SAP systems (e.g. SAP
(NetWeaver) Business Warehouse, SAP Business Suite, etc.)
To proceed, click the Log On button.
The logon popup will be replaced by a “Trying to connect to …” popup. As long as the log on is
taking place, all menu entries are blocked.
LMBI 3 Measurement Guide
Page 14
License Measurement for SAP BusinessObjects Enterprise
You’ll get the confirmation “You are now connected to CMS server <your server name>.” in the
measurement component.
Once the logon is completed, the measurement component will also check some of the administrative
rights required for the user who runs the measurement. If the checks are ok, you will see several lines
of “User ‘<your user>’ has sufficient authorization to …” in the command line output.
In case you don’t succeed with the log on, you’ll get
an exception message (in your local language). In
this case, please check if you have chosen the
correct server name and ask your network
administrator if the port is blocked. For further
details, please refer to chapter 3.7.4.
3.5.8
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, click on the menu item “Prepare”  “Read from
Repository & Evaluate Licenses“. After a click, the menu
remains like “frozen” until the measurement is completed.
The measurement component reads the license keys, some
server metrics, the amount of documents and the effective rights of each user with regards to certain
user types. This may be a time consuming job and may cause some load on the BOE server. Some
hints on the measurement runtime are given in chapter 2.3. During the measurement, status prompts
will indicate the progress. 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).
Once the user rights evaluation is completed, location of result file is displayed in the command shell
(like “User rights evaluation completed, results stored in D:\LMBI Versions\XI3_Component3.0.28\_measures\measure_iwdfvm3312.xml” in the screenshot above).
In addition, the measurement component will change its view and show a list of User Rights
Categories. If you select one on the left, you can see the list of users that belong to it on the right.
Page 15
LMBI 3 Measurement Guide
License Measurement for SAP BusinessObjects Enterprise
You can use the View menu to switch between this view (User categories)
and a second view (Effective Rights) where you can select individual user
IDs on the left, an application like CMC or Web Intelligence (on the right
upper side) so that in the lower right side the list of rights is shown with information if that right is
granted or not to the selected user.
A log off is automatically executed when closing the measurement component.
3.5.9
File location of the measurement results
Measurements result is not only shown in the display, but
also saved in the _measures subfolder, compare the folder
structure shown to the right.
The file measure_<your bi server name>.xml is the one
to be used for the consolidation component.
3.5.10 Measuring further systems
In case 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 will be renamed.
LMBI 3 Measurement Guide
Page 16
License Measurement for SAP BusinessObjects Enterprise
3.6
Measuring BusinessObjects 5.x / 6.x Systems
3.6.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 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 newer.
3.6.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.28.zip to the
subfolder X_BOE_5+6_Component-3.0.28 of the measurement folder.
The current measurement scripts do not support network drives with locations like
\\192.168.1.2\lmbi\measurement\X_BOE_5+6_Component-3.0.28. You’ll have to copy the files
locally (or find way to modify the settings in the start script properly).
3.6.3
Copy the GLAS.unv file to your 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.6.4
Adjust program paths in the configuration .xml files
If the default values documented here do not match your local settings, you have to use Notepad or a
proper XML tool 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.
Page 17
LMBI 3 Measurement Guide
License Measurement for SAP BusinessObjects Enterprise
3.6.5
Start the measurement component
Start the measurement component with the 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.6.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.6.7
Select database connection
Use the menu Prepare  Start Designer & Define Connection. The BusinessObjects Designer will
open with the universe GLAS.unv.
If the BusinessObjects Designer does not open, please check the settings as described in 3.6.4 for the
path tag <Designer> or open the universe file manually within the Designer.
LMBI 3 Measurement Guide
Page 18
License Measurement for SAP BusinessObjects Enterprise
Inside Designer choose the menu File  Parameters and select your database in the connection
area.
Save the universe and close the Designer.
3.6.8
Read user rights
Back in the measurement component
choose the menu Prepare  Start
BusinessObjects & Extract.
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 you are asked to.
 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.
Page 19
LMBI 3 Measurement Guide
License Measurement for SAP BusinessObjects Enterprise
Inside BusinessObjects press Alt+F8 or select menu Tools  Macro  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.28\_measures\legacy_raw_data).
LMBI 3 Measurement Guide
Page 20
License Measurement for SAP BusinessObjects Enterprise
3.6.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.6.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.7
Special adjustments & exception handling
3.7.1
How to read the settings for the CMS and the Request Port in the CMS
If you connect to the CMC, go to Servers and right-click the corresponding CentralManagementServer
to select its 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) (the 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, e.g. a network port scanner software.)
Page 21
LMBI 3 Measurement Guide
License Measurement for SAP BusinessObjects Enterprise
3.7.2
‚Full Control‘ for ‚Everyone‘ on Windows 7 on installation folder
The folder where the LMBI components are extracted to needs to have write permissions. If this is not
the case, the permissions can be set in Windows Explorer with a click on the right mouse button on
the folder (in this example C:\Program Files\SAP). A properties window opens (1). Switch to the tab
„Security“. Click on „Edit“ (2) and Add“ (3). On the „Select User, Computers, Service Accounts, or
Groups“ dialog, enter everyone (4) and click on “Check Names” (5). In case more than one result is
found (6), select the local group (6) and confirm all settings with OK (7), until you get back to the
permissions dialog. Check the “Allow” box to for the group Everyone in the line ““Full control” (8) and
confirm all open dialogs with OK.
LMBI 3 Measurement Guide
Page 22
License Measurement for SAP BusinessObjects Enterprise
3.7.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 e.g. with Notepad 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\jdk\bin". The quotation marks are required if the path has
spaces in it like the default value has.
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 (proper) 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, e.g. VNC.
3.7.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.4).
Furthermore, look up the error message code (FWM 20030 in
this case) in the Error Message Guide (e.g. version 4.2 in
English, linked at http://help.sap.com/bobip42?current=bobi, or directly
http://help.sap.com/businessobject/product_guides/sbo42/en/sbo42_error_messages_en.pdf).
These additional steps might help to locate the issue:
Page 23
LMBI 3 Measurement Guide
License Measurement for SAP BusinessObjects Enterprise
1. Check if you can connect to the CMC via web browser using your system name
2. If yes, open a command prompt and type 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 ok, try to telnet the system. On Microsoft Windows, a telnet client is
available, but it might not 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:
turns into
(You can terminate the telnet session with C t r l + 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 on SAP’s Help Portal. In the version for BI 4.0 SP 11 for instance, the relevant chapter is 7.15.2
Debugging a firewalled deployment.
LMBI 3 Measurement Guide
Page 24
License Measurement for SAP BusinessObjects Enterprise
4
Requesting technical support
In case you have questions or face issues with a 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). Please



5
use the component XX-SER-LAS,
provide a description of the technical issue and the steps how to reproduce it 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.
Security Guide
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 their (hardware) metrics,
 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 and their (effective) user rights, limited to a small
subset of rights to keep license evaluation effective.
 a list of technical rights available in the system
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 will include 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 will only work with result files from the measurement
component. As it runs on a local PC, no additional security aspects apply.
Page 25
LMBI 3 Measurement Guide
License Measurement for SAP BusinessObjects Enterprise
6
Frequently asked questions
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” 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
chapter “Working with firewalls” in the BOE Administrator Guide).
LMBI 3 Measurement Guide
Page 26
License Measurement for SAP BusinessObjects Enterprise
7
How user rights classify users
The following slides will describe how a small subset of the available technical rights classify users by
their assigned rights. The LMBI measurement component will consider the effective user rights, no
matter if these rights are assigned directly or indirectly via the security settings for users, user groups,
on access levels or on application level etc.
Page 27
LMBI 3 Measurement Guide
License Measurement for SAP BusinessObjects Enterprise
7.1
User rights relevant for SAP BusinessObjects Business Intelligence platform 4.x
LMBI 3 Measurement Guide
Page 28
License Measurement for SAP BusinessObjects Enterprise
7.2
User rights relevant for BusinessObjects Enterprise platform XI 3.x and XIR 2
7.3
User rights relevant for BusinessObjects Enterprise platform 5.1.x and 6.x
Page 29
LMBI 3 Measurement Guide
License Measurement for SAP BusinessObjects Enterprise
8
CPU metric - where to find required hardware data?
Some 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.
8.1
BI system runs in a virtual machine
8.1.1
Find the required data in the configuration of the hypervisor
If your BI system runs in a virtual machine, the number of configured virtual CPUs and - if supported –
the number virtual cores is required. To access this data, open the configuration of the virtual machine,
which may look similar to this:
Example 1 (VMWare vSphere Client):
Virtual machine “Test Setup” on host 10.20.19.2017 has 2 virtual CPUs with 4 virtual core each
Select the virtual machine > Switch to the Summary tab > Click on Edit Settings > Click on 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
LMBI 3 Measurement Guide
Page 30
License Measurement for SAP BusinessObjects Enterprise
8.1.2
Hyper-V - find the required data
The settings of virtual machines in the Hyper-V Manager only provide 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).
Chapter 8.2.1 describes how to get the required data in the guest operating system. In addition we
recommend to also provide the hardware data of the physical machine.
8.1.3
Other virtualization technologies - find the required data in the guest operating
system
You can always apply the procedure described in chapter 8.2.1 to the guest operating system to get
the correct values.
8.1.4
Enter the data of a virtual machine into the consolidation component
If you have found the numbers of virtual processors and the numbers of virtual cores per processor,
the next step is to enter this data into the LMBI. Therefore, click the button 2.1 Assign system
measures to licenses. Here, you will find another button name Edit CPU/server data. Please be aware
that the button only shows up 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 CPU data have been entered, as otherwise its value is Missing CPU data.
When you have opened the Edit CPU/server data view, make sure you clicked the Provide system
metrics (default) radio button as well as the Yes radio button 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.
Page 31
LMBI 3 Measurement Guide
License Measurement for SAP BusinessObjects Enterprise
Please note that you will have to 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:
8.2
Physical deployment of the BI system (can also be used inside a VM)
8.2.1
Find the required data in the operating system
For a physical deployment of the BI system, a good reference to determine the hardware metrics is the
hardware manual. Also, most operating systems provide sufficient data. Some examples are given
below.
Using Command Prompt in Microsoft Windows
Start a command prompt (Start > Run > “CMD”). Type
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)
LMBI 3 Measurement Guide
Page 32
License Measurement for SAP BusinessObjects Enterprise
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, type

To identify the machine’s IP address(es), type
wmci cpu get Name, Description, Manufacturer
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 an
information here if hyper threading is enabled or not. So the only way to get the number of
cores would be check the data sheet of the CPU type used.
Page 33
LMBI 3 Measurement Guide
License Measurement for SAP BusinessObjects Enterprise
In this example, 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.
Shell commands for other operating systems


For Linux, use the command lscpu | grep -i socket
For Solaris, use these commands:
o For the number of physical CPUs: psrinfo –p
o For the number of cores: kstat -p cpu_info:*:*:core_id | awk '{ a[$2]++ }


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)
END { for (b in a) { print b } }' | wc –l
8.2.2
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 as described in section 8.1.4. The only difference is
to select the No radio button 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.
8.3
Further CPU data options for clustered BI servers
Chapters 8.1.4 and 8.2.2 describe how to enter CPU data directly for virtual or physical deployments.
Besides the direct entry, there are two more options to provide the CPU data.
LMBI 3 Measurement Guide
Page 34
License Measurement for SAP BusinessObjects Enterprise
8.3.1
Providing custom CPU metric values
This option shall only be used if the metric value cannot be calculated correctly by entering the system
data. Entering such data is straightforward. Click the Enter a custom metric value radio button, enter
the custom CPU metric value and write a note why a custom CPU metric value was necessary. One
scenario where a custom metric is used is for contracts that were signed before 2006. In such cases, it
is possible that there was another used metric. However, you should contact your license auditor to
clarify this.
8.3.2
Reusing the CPU data of another server node
The other selectable option is the Do not count – for multiple nodes on the same system option that is
only available for clusters, i.e. for a system with more than one server node. The following scenario
shows a server with four clusters:
In such a scenario, it can be useful for one server node to use the same value of another node.
Therefore, a list of selectable nodes is displayed and can be chosen.
8.3.3
Clusters with multiple server nodes
Please make sure 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.
Page 35
LMBI 3 Measurement Guide
License Measurement for SAP BusinessObjects Enterprise
9
Abbreviations
BI
Business Intelligence, the main capability of the SAP BusinessObjects Enterprise
platform – it is not meant the usage type Business Intelligence of the SAP NetWeaver
platform
BOE
BusinessObjects Enterprise
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
Central processing unit
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
LMBI 3 Measurement Guide
Page 36
License Measurement for SAP BusinessObjects Enterprise
10
Copyright
Bound to SAP BusinessObjects licenses, a simple usage right for the LMBI is granted. In particular
licensees are is not permitted to decompile or change the LMBI or to pass it on to any third party.
10.1
Further remarks
No part of this publication may be reproduced or transmitted in any form or for any purpose without the
express permission of SAP AG. The information contained herein may be changed without prior
notice.
Some software products marketed by SAP AG and its distributors contain proprietary software
components of other software vendors.
Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft
Corporation.
IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z,
System z10, System z9, z10, z9, iSeries, pSeries, xSeries, zSeries, eServer, z/VM, z/OS, i5/OS,
S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server, PowerVM, Power Architecture,
POWER6+, POWER6, POWER5+, POWER5, POWER, OpenPower, PowerPC, BatchPipes,
BladeCenter, System Storage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2,
Parallel Sysplex, MVS/ESA, AIX, Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are
trademarks or registered trademarks of IBM Corporation.
Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.
Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered
trademarks of Adobe Systems Incorporated in the United States and/or other countries.
Oracle is a registered trademark of Oracle Corporation.
UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.
Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are
trademarks or registered trademarks of Citrix Systems, Inc.
HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide Web
Consortium, Massachusetts Institute of Technology.
Java is a registered trademark of Sun Microsystems, Inc.
JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology
invented and implemented by Netscape.
SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP Business ByDesign, and other SAP
products and services mentioned herein as well as their respective logos are trademarks or registered
trademarks of SAP AG in Germany and other countries.
Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal
Decisions, Web Intelligence, Xcelsius, and other Business Objects products and services mentioned
herein as well as their respective logos are trademarks or registered trademarks of Business Objects
S.A. in the United States and in other countries. Business Objects is an SAP company.
All other product and service names mentioned are the trademarks of their respective companies.
Data contained in this document serves informational purposes only. National product specifications
may vary.
These materials are subject to change without notice. These materials are provided by SAP AG and
its affiliated companies ("SAP Group") for informational purposes only, without representation or
warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the
materials. The only warranties for SAP Group 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 warrant.
Page 37
LMBI 3 Measurement Guide