IBM Tivoli License Manager – Technical Overview

1. IBM Tivoli License Manager – Technical Overview Joe Hamblin Certified IT Specialist jhamblin@us.ibm.com

2. Abstract IBM Tivoli License Manager is a new, WebSphere-based software license management product in the C&O portfolio. We will cover the architectural overview of the solution, the technical value proposition.

3. Agenda • ITLM Overview • Platform Support and Product Restrictions • Tivoli Enterprise Warehouse Integration • Competitive Landscape • Pre-demo prep and Demo Planning • Product pre-requisites and Tuning Parameters

4. IBM Tivoli License Manager A Software License Management Solution Including: • Contract management (2003) • License entitlement management • Software inventory • Software usage (patent pending) • Usage policy enforcement (patent pending) • Web-based administration • XML integration with 3rd party applications • Value-added reporting

5. License Manager Value Proposition • Enables customers to maintain compliance with software license T’s and C’s • By tracking license usage automatically (without requiring applications to be instrumented) • By managing contract expiration terms and renewals • Reduces Software TCO • ROI through software license savings • Avoid penalties from under buying licenses or maintenance • Avoid overbuying licenses or maintenance “License management is becoming a priority because IT budgets are scaling back and that's a potential savings area.” Audrey Rasmussen, VP, Enterprise Management Associates

6. Web-based Architecture • 3-Tier Architecture • Admin Server • Historical repository • Administration • Reporting • Runtime Server • Runtime repository • Enforcement & usage metering • Reporting • Agents • Data collection • Enforcement { • WebSphere Application Server • DB2 Universal Database Limited-use license

7. scheduling data scheduling data (targeted) Administration Server Runtime Server Agent inventory statistics scan results Information Flow between Components • Define scanning schedules on Administration Server • Agent sends scan results to Runtime Server • Runtime Server processes scan results and sends results to Administration Server • Administration Server handles historical data store

8. product and license data product information Administration Server Runtime Server Agent usage statistics license requests Information Flow between Components • Define license pools on Administration Server • Agent requests license from Runtime Server and reports back on application usage • Runtime Server keeps real-time application usage • Runtime Server reports usage statistics to Administration Server

9. Web-based Administration • Multi-customer administration • Roles • Administrator • Full access and control • Licensing Manager • Access and control for entitlement management • Other • Reporting access only • E-mail notification • Approaching usage limits • Runtime server events • Agent events

10. Agent Details • Basic information needed for: • Identification • Location • Hardware-based licensing models • CPUs • Memory • Disk drives • Environment management

11. Software Licensing Licensing Models Variations

12. Entitlement Settings • Product Entitlement Settings • Capacity type • Users, CPUs, memory… • Hard stop • Optional enforcement of limits • Multi-instance • Enable for single count per user/group/node • Disable to count each instance per user/group/node • Quantity • Threshold • Event notification • Target type • Enterprise, division, node, or agent • Dates • Entitlement start/stop dates

13. Software Inventory Schedule inventory scans View products by agent View agents by product

14. Usage Snapshot Report • Key Data Elements • Procured • Total of available licenses • In use • Number in use for the selected division/group • Total in use • Sum of all divisions • Total HWM • Max volume in use on all agents Drill-down to entitlements Drill-down to agents

15. Usage Trend Analysis Define the Report View the Results

16. Level Analysis Report • Use Levels to find… • Products with high or low peaks • Products with high or low average use • Date/time of peaks for planning purposes

17. Leveraging Tivoli… • Tivoli Enterprise Data Warehouse • ETL (extract-transform-load) scripts to extract information from IBM Tivoli License Manager into the data warehouse • Agent Topology, Product Install, and Product Usage reports available through the warehouse reporting interface • First release of Tivoli License Manager • Configuration Manager – Inventory • Provides installed software information to TLM for 1st level License Management • Second release of Tivoli License Manager • Configuration Manager - Software Distribution • Deploy TLM agent via CM with unattended installation • Second release of Tivoli License Manager

18. Technology Talking Points • Web-based three level architecture, for maximum performance and scalability • Single, multi-customer administration point for license management and reporting • Completely Web-based solution: no client applications, administered through the Web browser • Communication based on HTTP/S protocol, working within any network environment • Web-deployment of the agent, with minimal intervention from the end user • Unattended installation through Install Shield (use Configuration Manager to distribute for example) • Kernel extension technique, to enforce compliance • Notification of important events through automatic e-mail warnings • Collection of real-time/historical software inventory and usage statistics • Comparison of installed, used and procured licenses through web reports • Integration with asset management tools through XML import of machine and demographic data

19. Supported Platforms • Administration / Runtime Server • Windows NT 4 / 2000 Server • IBM AIX 4.3.3 (must be at ML 4330-02) / 5.1 • Agent • Windows 95/98/ME/NT4/2000 • Linux Red Hat 7.0 for Intel (kernel 2.2.16-22) • Linux Suse 7.0 for s390 (kernel 2.2.16) • Linux Red Hat 7.2 for s390 (kernel 2.4.9-17) • SunOS 5.7/5.8 (64 bit) • IBM AIX 4.3.3/5/1 (32 bit)

20. Data Warehouse Pre-reqs for ITLM Pack • DB2 Enterprise Edition 7.2.6 (DB2 7.2 with FP 6) • TEDW e-fix for DB2 (1.1-TDW-0002) • TEDW 1.1 Fix Pack 1 (1.1-TDW-FP01a) • TEDW 1.1 Fix Pack 2 (1.1-TDW-FP02) • Obtain these fixes at: • http://www.ibm.com/software/sysmgmt/products/support/TivoliEnterpriseDataWarehouse.html

21. ITLM Warehouse Enablement Pack Processes • COD_c05_Extract_TLM_Data_Process • Extracts a snapshot of products and agents installed in the enterprise, based on the IBM Tivoli License Manager database. Schedule this process to run daily. • If run repeatedly in a 24-hour period, the previous run’s data of the day will be replaced by the new one. • COD_m05_Populate_Mart_Process • Extracts data from the central data warehouse and places the information into the data mart for the application. This process should be scheduled to run daily.

22. ITLM Warehouse Enablement Pack Reports • Products installed by division extreme report • shows the n largest number of product installations • Products installed by division summary report • shows the summary of all products installed • ITLM agents installed by division extreme report • shows the n largest number of IBM Tivoli License Manager agents, Version 1.1, installations • ITLM agents installed by division summary report • shows the summary of all IBM Tivoli License Manager agents, Version 1.1, installed Any of these reports can be sorted by any combination of customer,division, operating system, and product name.

23. Tuning Parameters for a POC Environment • General Tuning Parameters • Change size of Thread Pool in the HTTP server from 50 to 150. In http.conf this changes: • ThreadsPerChild (WINDOWS 2000) • MaxClients (AIX) • Change DB2 buffer pool (on the Admin server) to 50.000 (equivalent to 200 Mb) • Change default Minimum Heap Size from 128 Mb to 256 Mb • Tuning parameters for the Admin Server • hwmScanPeriod=10 (minutes) • adminWakeUpPeriod=5 (minutes) • maxUsageAge=2 (days)

24. Tuning Parameters for a POC Environment • Tuning parameters for the Runtime Server • runtimePluginPeriod=5 • inventoryUpdatePeriod=5 • cacheUpdatePeriod=7 • adminDownloadPeriod=9 • adminUploadPeriod=11 • licenseCleanupPeriod=13 • usageSnapshotPeriod=15 These are all in minutes

25. Tuning Parameters for a POC Environment • Tuning parameters for the Agent • pingPeriod=360 • downloadParametersPeriod=300 • downloadCatalogPeriod=360 • uploadMinTime=660 • updateAgentEnabled=yes • updateAgentPeriod=3600 • E-mail Configuration Settings • smtpServer= Enter the address for your SMTP server here • mailSender= Enter the email address that you want to appear in the From: field • mailRecipient= Enter the email address of a recipient (other than the one specified in the Web GUI) – if desired These are all in seconds

26. Value Proposition • Maintain compliance with software license Ts and Cs • By tracking license usage automatically (without requiring applications to be instrumented) • By managing contract expiration terms and renewals • Mapping software use with entitlements • Reduces Software TCO • ROI through software license savings • Avoid penalties from underbuying licenses or maintenance • Avoid overbuying licenses or maintenance • Automate the data collection process and eliminate manual tracking and spreadsheets • Strengthen the customer’s bargaining position during contract renewal

27. Today’s Challenges… Distributed users • Geographically dispersed • Intermittent connectivity • Self-empowered, they don’t ask permission Software vendors • No common way to license software • Various levels of vendor control over deployment and usage • Frequent requests for evidence of compliance Decentralized software acquisitions • Users download to personal workstations • Divisions procure licenses for their employees • Many contracts with different license expiration dates, even from the same vendor Changing environment • Users move, change jobs, leave the company… • Corporate acquisitions and data center consolidations How can you maintain compliance and optimize spending???

28. ITLM and Configuration Manager • Functional similarities • Software inventory scanning • Limited Hardware data elements • Number of CPUs, amount of memory… • Only those needed for licensing models • Functional differences… ITLM adds: • Metering capability • Track software use, not just installations • Entitlement data • Tracks how much software you should be running • Contract data (2003) • Store and view relevant information about the contract Ts & Cs, expiration dates, contract types… • Enforcement capability • Ability to limit software use to customer-defined quantities

29. IBM Tivoli License Manager Increased control over… • Software compliance and audits • Contract renewal activities • Rapidly changing environments Return on investment through… • Minimized manual effort • Fact-based license investments, renewals, and reductions

30. Web-based Architecture • 3-Tier Architecture • Admin Server • Historical repository • Administration • Reporting • Runtime Server • Runtime repository • Enforcement & usage metering • Reporting • Agents • Data collection • Enforcement { • WebSphere Application Server • DB2 Universal Database Limited-use license

31. Questions ?