comparison of versions 7.5 and 9 - ibm · web browsers for web ui lmt/tad4d 7.5 lmt/sua 9.2...

Post on 22-Jul-2018

219 Views

Category:

Documents

2 Downloads

Preview:

Click to see full reader

TRANSCRIPT

Comparison of versions 7.5 and 9.2

IBM License Metric Tool &

Software Use AnalysisQuestions and Answers

ILMT Central Team

Agenda

02Operating systems

03Architecture

comparison

08New concepts

07Server

06Agent (client)

05SwKBT (SUA only)

04Supported metrics

09DemoIntroduction

01

10Useful links

Introduction 01

• Discovers detailed

information about hardware,

installed IBM software and

third party software

• Delivers flexible options for

monitoring software usage

• Integrates for IBM Control

Desk for discovered hardware

and software assets

Software Use Analysis

Introduction 02

The session applies to License Metric Tool and Software Use Analysis 9.x. Unless

stated otherwise, presented information applies to both products.

• Discovers PVU software• Measures maximum core capacity in

PVUs available to the deployed software

• Required for subcapacity licensing

License Metric Tool

Operating systems 02

Server 02Operating system LMT/TAD4D 7.5 LMT/SUA 9.2

AIX 5.36.17.1

HP-UX 11i v211i v3

Oracle Solaris 10

Red Hat Enterprise Linux 56

6.3 or a higher 6.x version

SUSE Linux Enterprise Server 1011

Windows Server 2003Server 2008Server 2008 R2

2008 R2 2012 2012 R2

Database 02LMT/TAD4D 7.5 LMT/SUA 9.2

DB2 9.7 FP 6 and higher9.5 FP 10 and higher9.1 FP 12 and higher

10.5 with FP5 or higher10.1 with FP2 or higher

Microsoft SQL Server Express

Not supported 2014 (LMT only)

Microsoft SQL Server

Not supported 20082008 R22012

Architecture

comparison 03

Architecture comparison

Web UI

Database

Software Knowledge Base Toolkit

WebSphere Application Server

IEM Server

Server

Console

Database

IEM client

7.5

Web UI

Command-lineServer Database

Software Knowledge Base Toolkit

Tivoli Integrated Portal

WebSphere Application Server

Agent

9.2

Scalability

LMT/TAD4D 7.5 LMT/SUA 9.2

Customer proved scalability per server

25K 250K

Web browsers for Web UI

LMT/TAD4D 7.5 LMT/SUA 9.2

Internet Explorer 811 (with FP 1 and iFix 23)

9 or higher

Firefox 3.610 (with FP 1)

17 Extended Support Release (ESR) or higher ESR editions

Chrome N/A 35 or higher

Supported metrics

04

Supported metrics

LMT/TAD4D 7.5 LMT/TAD4D 7.5 FP1 LMT/SUA 9.2

PVU Full capacity

Subcapacity

RVU Full capacity N/A Partial

Subcapcity N/A Partial

Systemslicensing

N/A

Software Knowledge

Base Toolkit 05

Software Knowledge Base Toolkit

LMT 7.5 LMT 9.2 TAD4D 7.5 SUA 9.2

Availability Not available Not available Obligatory Optional(file and packagesignatures can be created in SUA)

Supported versions

N/A N/A 1.2.2 1.2.2 interim fix 1 (highly recommended)

1.2.2 1.2.2 interim fix 1 (highly recommended)

Notes Important: The instance of SwKBT used with TAD4D cannot be used with SUA. A separate instance is necessary.

Agent (client) 06

Agent (client)

Content LMT/TAD4D 7.5 LMT/SUA 9.2

Installation directory

Windows C:\Windows\itlm C:\Program Files\BigFix Enterprise\BES Client

Linux /var/itlm /opt/BESClient/bin

Configuration Windows C:\Windows\itlm\tlmagent.ini Windows Registry

Linux /etc/tlmagent.ini /var/opt/BESClient/besclient.config

Logs Windows <Tivoli_common_dir>\COD\logs\agent\trace C:\Program Files\BigFix Enterprise\BES Client\__BESData\__Global\Logs

Linux <Tivoli_common_dir>/COD/logs/agent/trace /var/opt/BESClient/__BESData/__Global/Logs

Log settings Windows C:\Windows\itlm\tlmlog.properties Specified by the _BESClient_EMsg_File setting in the IEM console.

Linux /etc/tlmlog.properties Specified by the _BESClient_EMsg_File setting in the IEM console.

Agent (client)

Content LMT/TAD4D 7.5 LMT/SUA 9.2

Useful links Agent information: TAD4D / LMTConfiguring agents: TAD4D / LMTAgent settings: TAD4D / LMTAgent files: TAD4D / LMT

Common file locationsAgent logsLogging guide

Configuring agent (client) parameters

Parameter LMT/TAD4D 7.5 Set in the command-line interface

LMT/SUA 9.2Set by using fixlets

CPU consumption cpu_threshold Select the 'Initiate the software scan with CPU threshold' option in the Initiate Software Scan fixlet

Software scans inv_rate_typeinv_rate_valueinv_start_date

Run the Initaite Software Scan fixlet

Useful links: Configuring agents: TAD4D / LMTAgent commands: TAD4D / LMTConfiguring the tlmagent.ini file: TAD4D / LMT

Configuration settingsEditing the masthead file (Windows)Editing the masthead file (Linux)

Manually executing agent (client) commands

Command LMT/TAD4D 7.5 LMT/SUA 9.2

Starting Windows tlmagent.exe –g Run the Start Service fixlet from IEM console for BESClient service

Linux tlmagent –g /etc/init.d/BESClient start

Stopping Windows tlmagent.exe –e Run the Stop Service fixlet from IEM console for BESClient service

Linux tlmagent –e /etc/init.d/BESClient stop

Ping tlmagent.exe –p tlmagent –p

N/A

Run software scan tlmagent.exe –s tlmagent -s

Run the Initiate Software Scan fixlet from IEM console

Run hardware scan tlmagent.exe –htlmagent –h

Run the Initiate Software Scan fixlet from IEM console

Send scan results to the server

tlmagent –sw / tlmagent.exe –swtlmagent –hw /tlmagent.exe –hw

Run the Upload Software Scan Results fixlet from IEM console

Scan types in 9.2

Scans are started by running the Initiate Software Scan fixlet.

Available in SUA only

Scan types in 9.2

Catalog-based scan The SUA server creates scanner catalogs that are sent to the endpoints. They do not include signatures that can be found based on the list of file extensions or entries that are irrelevant for a particular operating system. Based on these catalogs, the scanner discovers exact matches and sends its findings to the IEM server. This data is then transferred to the SUA server.

File system scan (SUA-only) The scanner uses a list of file extensions to create a list of all files with those extensions on an endpoint.

Package data scan The scanner searches the system registry (Windows) or package management system (Linux, UNIX) to gather information about packages that are installed on the endpoints. Then, it returns the findings to the IEM server where the discovered packages are compared with the software catalog. If a particular package matches an entry in the catalog, the software is discovered.

Application usage statistics (SUA-only) The scanner gathers information about processes that are running on the target endpoints

Software identification tags scan The scanner searches for software identification tags that are delivered with software products. It is an authoritative, secure, repeatable and transparent software discovery thru ISO 19970-2 tag files. Over 400 (and growing) IBM products are already providing SWID tag files.

Scan files

Command LMT/TAD4D 7.5 LMT/SUA 9.2

Scan file name tlm_fullhw_output.gz tlm_hw_output.gz tlm_remote_sw_output.gztlm_use_output.gz

<agent_ID>_isotag.tar.gz/zip<agent_ID>_cit.xml.bz2<agent_ID>.xml.bz2

Location on the agent

Windows C:\Windows\itlm\scanner C:\Program Files\BigFix Enterprise\BES Client\LMT\CIT

Linux /var/itlm/scanner opt/BES Client/LMT/CIT

Location on the server

Windows Unpackaged in the tmp directory and deleted C:\Program Files\IBM\LMT\UploadManagerData\BufferDir\sha1/<agent_ID_modulo_100>/<agent_ID>

Linux Unpackaged in the tmp directory and deleted /opt/ibm/LMT/UploadManagerData/BufferDir/sha1/<agent_ID_modulo_100>/<agent_ID>

Software catalog

LMT 7.5 LMT 9.2 TAD4D 7.5 SUA 9.2

Downloadingnew catalog

From website From website orfrom fixlet: Software Catalog Update

From websiteFrom fixlet: Software Catalog Update

Uploading the catalog to the application

Import Software Catalogpanel

Catalog Upload panel SwKBT orImport Software Catalogpanel

Catalog Upload panel or SwKBT

Useful links Software catalog update

Working with software catalogs

Software catalog update

Working with software catalogs

Software catalog update

Working with software catalogs

Working with software catalogs

Server 07

Server installation location

LMT/TAD4D 7.5 LMT/SUA 9.2

/opt/IBM/TAD4D/opt/IBM/LMT

/opt/ibm/SUA/opt/ibm/LMT

C:\Program Files\IBM\TAD4DC:\Program Files\IBM\LMT

C:\Program Files\IBM\SUAC:\Program Files\IBM\LMT

Server installation logs

LMT/TAD4D 7.5 LMT/SUA 9.2** LMT examples are given in the table. For SUA paths, substitute LMT with SUA

Installation log file

ibm\tivoli\common\COD\logs\install\message\msg_servers.log

Traces:ibm\tivoli\common\COD\logs\install\trace

trace_servers.log - the main installation log trace_db_servers.log – database-related logsewas.log - output of the jacl scripts run by the installerDB2install.log – database-related logssu.log - gathers output from all su commands performed during the installation, migration, or uninstallation

• Log created during installation:C\Users\Admin\LMT_9.2 %USERPROFILE%\ia.log

root/LMT_9.2root/ia.log

• Log created after an incomplete installation:C\Users\Admin\LMT_9.2_timestamp_logs.ziproot/LMT_9.2_timestamp_logs.tar.gz

• Log created after a successful installation:C:\Program Files\IBM\LMT\LMT_9.2_timestamp_logs.zip/opt/ibm/LMT/LMT_9.2_timestamp_logs.tar.gz

Server log settings

LMT/TAD4D 7.5 LMT/SUA 9.2

Log file /var/ibm/tivoli/common/COD/logs/admin/trace/trace1.log /var/ibm/tivoli/common/COD/logs/msghandler/trace/trace1.log

install_dir\wlp\usr\servers\server1\logs\tema.log

Log settings <TIP_INSTALL_DIR>\profiles\TIPProfile\installedApps\TIPCell\isc.ear\tad4d_admin.war\WEB-INF\conf\log.properties

install_dir\wlp\usr\servers\server1\server.xml

Server log settings

LMT/TAD4D 7.5 LMT/SUA 9.2

Parameters itlm.tracelogger.level - level of trace logged during operation of the server

itlm.tracefilehandler.maxFileBytes - the maximum file size, in KB, of the specified trace file before it is rolled over

itlm.messagefilehandler.maxFileBytes - the maximum file size, in KB, of the specified trace file before it is rolled over

itlm.tracefilehandler.maxFiles – the maximum number of iteration of the trace file

itlm.messagefilehandler.maxFiles - the maximum number of iteration of the message file

cli.maxFileBytes - the maximum size of a single iteration of a command-line message file

cli.maxFiles - the maximum number of iterations of the command-line message file

messageFileName - the server log file name

logDirectory - the server log file location

maxFileSize - the maximum size (in MB) that a log file can reach before it is rolled over

maxFiles - the maximum number of iterations of the server log file

Server log settings

LMT/TAD4D 7.5 LMT/SUA 9.2** LMT examples are given in the table. For SUA paths, substitute LMT with SUA

Changing the log level

C:\Program Files\IBM\TIP\profiles\TIPProfile\installedApps\TIPCell\isc.ear\lmt_admin.war\WEB-INF\conf\log.properties

/opt/IBM/TIP/profiles/TIPProfile/installedApps/TIPCell/isc.ear/lmt_admin.war/WEB-INF/conf/log.properties

C:\Program Files\IBM\LMT\wlp\usr\servers\server1\config\log4j.properties

/opt/ibm/LMT/wlp/usr/servers/server1/config/log4j. properties

Logging level

DEBUG_MINDEBUG_MIDDEBUG_MAX

FATAL ERROR WARN INFO DEBUG

ETL (import) logs in 9.2

ETL (import) logs:install_dir\wlp\usr\servers\server1\logs\importsinstall_dir/wlp/usr/servers/server1/logs/imports

The latest import log can also be accessed from the LMT/SUA user interface. Click Management > Data Imports.

Server restart

Action LMT/TAD4D 7.5 LMT/SUA 9.2

Stop the server/opt/IBM/TAD4D/cli/srvstop.sh/opt/IBM/LMT/cli/srvstop.sh

C:\Program Files\IBM\TAD4D\cli\srvstop.batC:\Program Files\IBM\LMT\cli\srvstop.bat

/etc/init.d/SUAserver stop/etc/init.d/LMTserver stop

C:\Program Files\IBM\SUA\cli\srvstop.batC:\Program Files\IBM\LMT\cli\srvstop.bat

Start the server/opt/IBM/TAD4D/cli/srvstart.sh/opt/IBM/LMT/cli/srvstart.sh

C:\Program Files\IBM\TAD4D\cli\srvstart.batC:\Program Files\IBM\LMT\cli\srvstart.bat

/etc/init.d/SUAserver start/etc/init.d/LMTserver start

C:\Program Files\IBM\SUA\cli\srvstart.batC:\Program Files\IBM\LMT\cli\srvstart.bat

New concepts 08

Extract, Transform, Load (ETL, import)

Extract LoadTransform

Extracting information about the infrastructure, installed agents, and detected softwarefrom the IEM server

Checking whether a new software catalog is available

Gathering information about the software scan and files that are present on the endpoints

Collecting data from VM managers

Transforming the data to a single format that can be loaded to the LMT/SUA database

Matching scan data with the software catalog

Calculating PVUs

Processing the capacity scan

Loading the data into the database

SUA

LMT

Audit Trail

Required permission: View Audit Trail

The report provides information about actions that have influence on the information that is displayed on other reports, including:● Modifications to the software classification: confirming and changing the default classification, sharing an

instance between products, including an instance in and excluding it from pricing calculations● Uploads: successful or failed upload of the software catalog, charge unit data, and PVU table● Imports: successful or failed import of the software catalog, charge unit data, and PVU table● VM managers: adding, modifying, and deleting VM managers● Updates to the scan configuration in the Scan Configurations page

Location of the discovered component

PVU and RVU consumption trend

Viewing the catalog

To view the catalog content, go to Reports > Software Catalog.

You can also search the catalog from the dasboard.

Simple catalog management in SUA

SwKBT is not necessary if you create only file and package signatures. You can create them directly in SUA, either from scratch or from the Package Data and Scanned File Data reports.

SUA signature community

You can share your custom signatures (created by using the simple catalog management in SUA) with other users, or search the community for signatures that you are missing. Check it out at: http://bigfix.me/signature.

Dashboard

Demo 09

Useful links 10

Wiki

IBMLicenseMetricTool

Forum

@ILMTCentralTeam

Documentation

License Metric Tool

Scalability Guide

Migration cookbook (LMT)

Development plans

Questions?

Thank you!

top related