1. ILMT/SUA demo- 02/09/2015 IBM ILMT/SUA Dev Team
IBM’s statements regarding its plans, directions, and intent are subject to change or withdrawal without notice at IBM’s sole discretion. Information regarding potential future products is intended to outline our general product direction and it should not be relied on in making a purchasing decision. The information mentioned regarding potential future products is not a commitment, promise, or legal obligation to deliver any material, code or functionality. Information about potential future products may not be incorporated into any contract. The development, release, and timing of any future features or functionality described for our products remains at our sole discretion.
All of the material in the following charts is speculative and is not part of any booked plan. Therefore the actual delivered products may or may not include the items on this roadmap. The information on these products is intended to outline our general product direction and it should not be relied on in making a purchasing decision. The information on these products is for informational purposes only and may not be incorporated into any contract. The information on these products is not a commitment, promise, or legal obligation to deliver any material, code or functionality. The development, release, and timing of any features or functionality described for our products remains at IBM's sole discretion
IBM ILMT/SUA Dev Team

2. Agenda INTRODUCTION: Summary of ILMT/SUA application updates to date
Duration: 10 minutes
Presenter: Tomasz Zeller
PART 1: Installation of SUA 9 on Windows with MS SQL [Live demo]
Duration: 20 minutes
Presenter: Boguslaw Nowak
We will show an installation of SUA 9 on Windows and its configuration to work with MS SQL.
PART 2: Optimized volume of scanned file data in SUA 9 [Overview]
Duration: 5 minutes
Presenter: Malgorzata Jablonska (
We will show an overview how to reduce number of information that is uploaded to the server but not used for software catalog customizations to improve import process.
PART 3: Scan Groups migration from LMT/TAD4D 7.5 to LMT/SUA 9 [Live demo]
Presenter: Malgorzata Jablonska/Dariusz Glocki (
We will show an overview of scan groups migration process plus demonstrate a sample migration scenario.

3. Summary of ILMT/SUA application updates to date
Tomasz Zeller
ILMT/SUA Development Manager

4. IBM License Metric Tool and IEM Software Use Analysis – evolution of 9
IBM License Metric Tool and IEM Software Use Analysis – evolution of 9.x product line.
2014
2015
Jun
July
Aug
Sept
Oct
Nov
Dec
Jan
Feb
Mar
Apr
SUA/LMT
GA Dec 19
Planned:
SUA/LMT 9.2
ILMT 9.0.1
IEM for SUA 9.1 Application Update 9.0.1
GA Aug 12
SUA/LMT
GA Oct 30

5. IBM License Metric Tool 9
IBM License Metric Tool IBM Endpoint Manager for Software Use Analysis 9.1 Application Update
August 2014:
All-In-One installer on Linux/DB2 for ILMT
Integration with Smart Cloud Control Desk Making available sub-capacity license usage data to Smart Cloud Control Desk
Single user interface for Infrastructure management
Automation of capacity configuration on Linux on System z as well as support Group Capping technology on this system
Better scan management and serviceability
Support for discovering IBM tags based on ISO standard - it demonstrates our strategy to support and promote open standards for Software Discovery and Management
More info at:
See What’s new in SUA (Video):
What’s new in LMT (Video):

6. SUA/LMT 9.0.1.1 and 9.0.1.2 October 2014 - SUA/LMT 9.0.1.1
Reduced time of loading the software catalog during the import
Support for IBM® Endpoint Manager 9.2
Support for Power Systems on Linux
Export of the entire software inventory to a CSV file
December SUA/LMT
migration from ILMT and TAD4D version 7.5 (bundling and VM Managers conf)
a new 'Scan Health' widget
enablement of scanning remote file systems
serviceability and performance improvements
(SUA only) import and export of custom signatures between SUA instances
More info at:
What’s new in LMT and (Video):
What’s new in SUA and (Video):
Migration from 7.5 (Q&A session):
Migration from 7.5 (Cookbook):
Migration from 7.5 (Video Part 1):
Migration from 7.5 (Video Part 2):
Exporting custom signatures in SUA (Video):

7. Next release content – March 2015
ILMT/SUA – next release
Windows MSSQL support
7.x-> 9.x migration including scans groups migration
Performance optimizations including
Optimized volume of scanned file data
Try it in the scope of ILMT/SUA Beta Program !!

8. https://ibm.biz/Bdxptb
Community and Beta Program
Try and test our beta drop Access a hosted system installed and configured with the latest evaluation code or download it and play in your own environment.
Watch videos and explore capabilities Review brief feature demos at your leisure and provide feedback with a few mouse-clicks.
Comment on new documentation Read and comment on new documentation provided with the latest evaluation code.
Comment and discuss

9. Installation of SUA 9 on Windows with MS SQL
Boguslaw Nowak
ILMT/SUA Installation and Migration Product Owner

10. Installation of SUA 9 on Windows with MS SQL
This solution is for Customers who prefer Windows/MS SQL over Linux/DB2 as a platform for their asset management solution.
For both IBM License Metric Tool (ILMT) and IEM for Software Use Analysis (SUA) there is no difference in available functions and look and feel of UI compared to version for Linux/DB2 .
For Windows/MS SQL there is no All-In-One installer, which was available only for Linux/DB2.
The way how to install on Windows is standard for IEM family – from IEM console dashboard.

11. Demonstration scenario
Install SUA 9 on Windows 2012 R2 server.
Configure SUA to work with MS SQL using Windows Authentication as SUA database
Configure the datasource using SQL Authentication to connect to IEM MS SQL database Prerequisites: IBM Endpoint Manager and MS SQL

12. Installation of ILMT/SUA 9 on Windows with MS SQL – prerequisite steps
Installing IEM server It can be downloaded from Pasport Advantage portal
Creating the license authorization file The license authorization file contains deployment and licensing information used during the installation of IBM® Endpoint Manager to create your license files and certificates.
You can use IBM formular to get the file.
Installing database software Install MS SQL Server. For ILMT only, for small environments (less than 500 endpoints) MS SQL Server Express edition is supported option.

13. Live Demo

14. How to access installable Windows/MS SQL Beta
You need an account on IBM DeveloperWorks
Detailed instructions available on our Beta community: d99d587a5c_466d_866e_814dee2e0268/page/Cloud
You need to go to section: „SUA or LMT version 9 running on Windows and MSSQL”
To access installation files you need to send to – you will be given personal access key that will allow you to download the code
You need to have ILMT or SUA Beta fixlet site in your IEM – then the SUA or LMT installer on Windows can be downloaded from this site using a fixlet
If you are existing SUA or LMT customer, write us a note on – your IEM license will be updated with entitlement to Beta fixlet site
For ILMT – you can request new Beta IEM license using a simple HTML form available on the Beta community (link above)

15. Optimized volume of scanned file data
Malgorzata Jablonska
ILMT/SUA Licensing Product owner

16. Optimized volume of scanned file data – introduction
Solution for Software Use Analysis customers who would like to refresh inventory reports data more frequently
Balance load between SUA server and endpoint
Server side signature matching vs endpoint side signature matching
File scan data volumne on the server vs catalog content propagated to the endpoint
May significanlty reduce the overall import process time – depends on specific data in your infrastructure
Software discovery results remain the same once the upgrade is fully completed
How to tune performance further
Product documentation under Tuning performance section
Scalability guideline document available on product wiki page

17. Files with particular extensions
SUA only
Optimized volume of scanned file data
The Scanned File Data report show files with particular extensions that were discovered on the computers in your infrastructure. This information is typically used for creating custom software signatures.
Good practice: Narrowing down the list of file extensions to only those that are typically used for creating software signatures.
.exe
.bin
.sh
Files with particular extensions
Scanned File Data
report
Custom signatures

18. Optimized volume of scanned file data - configuration
Configuration panel after the upgrade*
This step can be skipped.
The number of monitored file extensions can be changed manually later if needed.
File extensions that will be monitored after the change. Extensions used in the existing custom catalog content are preserved.
File extensions that will NOT be monitored after the change.
* Fresh installation - default setting is with optimized extensions list

19. Optimized volume of scanned file data – important action
Perform the following steps to start using the new list of file extensions.
Optional: Upload a new software catalog to SUA.
Run an import. First import takes longer because the catalog is reimported.
Stop the current scan action and initiate a new one with the new catalog.
Run an import. From now on, the optimized list of file extensions is used.
Important: After the import, some software items might not be visible on the reports. It is an expected behavior. Rescan the infrastructure and run another import for the software inventory to be properly reported.

20. Optimized volume of scanned file data – manual configuration
The number of monitored file extensions can be changed manually at any later time. The procedure is available in user documentation and scalability guideline document.
Stop the SUA server.
Remove unwanted file extensions from the following files:
file_names_all.txt
file_names_unix.txt
file_names_windows.txt
Start the SUA server.
Optional: Upload a new software catalog to SUA.
Run an import. First import takes longer because the catalog is reimported.
Stop the current scan action and initiate a new one.
Run an import. From now on, the optimized list of file extensions is used.

21. Migration of scan groups from LMT/TAD4D 7 to LMT/SUA 9
Malgorzata Jablonska
ILMT/SUA Licensing Product owner

22. Migration Early Access Program – Invitation
Development Team wants to invite you to our Beta program.
Already available is migration
ILMT/TAD4d 7.5 or to ILMT/SUA 9.x
It migrates the most needed, User provided data
Software Classification (Bundling and Exclusions)
VM configuration management
Scan Groups NEW!
Migration is side by side
7.x and 9.x servers coexist during migration
Coexistence of 7.x and IEM agents for agents mapping and later software classification migration is needed

23. Scan groups in 7.x vs computer groups in 9.x
Scan groups are used to partition infrastructure into distinct groups, potentially scanned with different schedules to avoid server congestion or hypervisors overload.
Each computer belongs to only one scan group.
Computer groups in 9.x (IEM)
Computers may belong to multiple computer groups.
IEM computer groups can be either manual or automatic
For manual groups the list of endpoints needs to be provided/selected manually
Automatic groups contain specified criteria (e.g. IP address in some range)
Automatic groups can change their population depending on the evaluation of the group properties
Action (like Software Scan) can be targeted to be executed on a given computer group, on a list of manually selected computers, or the target can be evaluated in a similar way as the computer group definition.

24. Scan groups migration
You execute an enhanced version of the existing migration tool to replicate 7.x scan groups into IEM server.
IEM Computer groups are re-created in the IEM server based on 7.x scan groups, the new IEM computer groups are named in the following way:
Migrated_<7.x_SCAN_GROUP_NAME>_<7.x_SERVER_ADDRESS>
You can change the name after migration.
Scan schedules can be re-created in the IEM server (optional)
Schedules that exist in IEM are not overridden
In Endpoint Manager, you can schedule scans to run every 1, 2, 3, 5, 7, 15, or 30 days. Because the options differ from the options that are available in version 7.x, only scan schedules that can be re-created in Endpoint Manager are migrated.
Migration can be executed any number of times, allowing continuous operations of both 7.x and 9.x servers.

25. Use of migration tool to move 7.x scan groups
IEM computer groups & schedules
Each endpoint tagged with the scan group name
Agents reconciled by ILMT Agent ID found by IEM Agent
IEM computer group created to contain all the endpoints sharing the same scan group tag
SUA/ILMT scan actions optionally created with the same schedule as in 7.x
ILMT/TAD4D 7.2.2/7.5.x
IEM
ILMT/SUA v9.x
IEM Server
ILMT/SUA Server
ILMT/TAD4D Server
DB2
direct SQL
queries
IEM REST API
Migration utility
Single migration utility to move bundlings, VM Managers and scan groups.
Direct connections to 7.x and IEM required.

26. Live Demo

27. How to access Beta code for 7.x → 9.x migration
You need an account on IBM DeveloperWorks
Detailed instructions available on our Beta community: d99d587a5c_466d_866e_814dee2e0268/page/Cloud
To access migration tools you need to send to – you will be given personal access key that will allow you to download the code
Migration tools work with latest LMT or SUA production version ( ) => if you are existing LMT/SUA customer, just upgrade to this latest version
For testing migration to ILMT 9 even if you are not yet ILMT 9 user, the tool is free and you can install newest version (details on community)
For testing migration to SUA 9 if you are not yet SUA 9 customer, write an to – we will work to grant you a limited Beta license

28. Thank You!