IBM License Metric Tool
Version 7.2.2
Installing with embedded WebSphere
Application Server
IBM License Metric Tool
Version 7.2.2
Installing with embedded WebSphere
Application Server
Installation Guide
This edition applies to version 7.2.2 of IBM Tivoli Asset Discovery for Distributed (product number 5724-S94) and to all subsequent releases and modifications until otherwise indicated in new editions.
Contents
Chapter 1. Installing IBM License Metric
Tool
. . . 1
Introduction . . . 1
License Metric Tool components . . . 1
Chapter 2. Installing with embedded
WebSphere Application Server . . . 3
Planning the License Metric Tool server installation . 3 Planning the topology . . . 4
Supported operating systems for the server and database . . . 4
CPU and memory requirements for the server and database . . . 8
Space requirements for the server and database. . 9
Other software prerequisites . . . 15
Supported versions of WebSphere Application Server . . . 17
Topology and capacity planning . . . 17
Network planning . . . 18
Security considerations . . . 19
Proof-of-concept installation . . . 20
Installing the server (embedded WebSphere Application Server) . . . 21
Installation checklist - installing on embedded WebSphere Application Server . . . 21
Preinstallation steps . . . 23
Preparing installation images . . . 23
Server installer files. . . 24
A summary of IBM License Metric Tool 7.2.2 installation images . . . 25
Information regarding installing DB2 . . . . 25
Synchronizing the clocks of server and database computers . . . 26
Changing SELinux settings before installing License Metric Tool on Red Hat Linux . . . 26
Installing in interactive mode . . . 27
Installing the server in interactive mode . . . 27
Installing IBM License Metric ToolTivoli Asset Discovery for Distributed in interactive mode on separate computers. . . 32
Verifying the interactive installation . . . . 36
Resuming a stopped or failed License Metric Tool installation . . . 37
Installing in silent mode . . . 40
Installing the IBM License Metric Tool server in silent mode . . . 41
Server installation response files . . . 42
Verifying the silent installation . . . 45
Resuming a stopped or failed License Metric Tool installation . . . 45
Moving the TLMA database to a separate server 49 Troubleshooting server installation. . . 50
Troubleshooting server installation and uninstallation . . . 50
Server installation problems on AIX operating system . . . 50
Server installation problems on Solaris operating system . . . 51
Server installation problems on UNIX operating systems . . . 52
Server installation problems on Windows operating system . . . 53
Database problems . . . 54
Other installation problems . . . 55
Chapter 3. Installing agents . . . 61
Agent hardware and software requirements . . . 61
Supported operating systems for agents . . . . 61
VMware and Microsoft virtualization considerations . . . 70
Other software requirements for the agents . . . 71
Disk space requirements . . . 72
Support for high availability environments . . . 76
Supported national languages for IBM i agents 76 Agent preinstallation steps . . . 77
Preparing agent certificates for client authentication . . . 78
Running Common Inventory Technology enabler 79 Disabling SELinux when installing the agent on RedHat Linux . . . 81
Setting up a proxy server . . . 81
Performing agent security-related tasks . . . 83
Installing agents using native installers . . . 83
Installing agents on AIX using native installers 84 Installing agents on HP-UX using native installers . . . 86
Installing agents on IBM i using native installers 87 Installing agents on Linux using native installers 88 Installing agents on Linux on System z . . . . 89
Installing agents on Solaris using native installers 91 Installing agents interactively . . . 91
Installing agents on Windows using a native installer. . . 92
Installing agents in silent mode. . . 95
Rerunning a failed agent installation . . . 96
Rerunning agent installation that failed in the preinstallation phase . . . 96
Rerunning agent installation that failed in the postinstallation phase . . . 96
Installing agents on UNIX using shell installers . . 97
Using IBM Tivoli Configuration Manager to install the agents in bulk . . . 98
Software package parameters . . . 100
Installing agents with Windows logon scripts. . . 102
Performing a refresh installation of agents . . . . 104
Image cloning with preinstalled agents . . . 105
Agent installation response files . . . 106
Windows agent installation response file and logon script configuration file . . . 106
UNIX agents installation response file . . . . 108
IBM i agent installation response file . . . . 111
Troubleshooting agent installation and uninstallation . . . 113
Agent installation problems on AIX platforms 113 Agent installation problems on Linux operating system. . . 114
Agent installation problems on IBM i, Windows and Solaris platforms . . . 115
Agent upgrade and self-update problems . . . 116
Other agent installation problems. . . 117
Disabling rollback of failed agent installations 118
Chapter 4. Uninstalling . . . 121
Uninstalling the License Metric Tool servers and databases. . . 121
Uninstalling the server in interactive mode . . 121
Uninstalling the server in silent mode . . . . 122
The server and database uninstallation response file . . . 123
Running scripts to uninstall License Metric Tool 124 Scripts used in undeploying the server on WebSphere Application base version . . . . 125
Uninstalling agents . . . 125
Uninstalling License Metric Tool agents using the tlmunins script . . . 125
Uninstalling agents using native installation tools . . . 126
Uninstalling AIX agents . . . 126
Uninstalling HP-UX agents . . . 126
Uninstalling IBM i agents . . . 126
Uninstalling Linux agents . . . 127
Uninstalling Solaris agents . . . 127
Uninstalling Windows agents . . . 127
Notices . . . 129
Trademarks . . . 130
Chapter 1. Installing IBM License Metric Tool
Read this guide to learn how to perform the License Metric Tool installation.
The following changes in the installation process and packages have been introduced in release 7.2.2:
v InstallAnywhere 2009 installation framework has been implemented (installation wizard),
v installation of DB2 has been removed from the installation wizard,
v the files for manual deployment are now in a separate package (Passport Advantage download) or on a separate DVD (they cannot be extracted from the wizard).
Introduction
IBM®License Metric Tool helps you maintain an up-to-date inventory of the IBM
distributed software assets in your IT infrastructure, and measure the processor value units (PVU) available to and consumed by them. It also allows you to ensure compliance with IBM subcapacity licensing requirements and demonstrate good IT governance if you are using PVU-based licensed products.
The use of License Metric Tool is required under the Passport Advantage®licensing
offering, and optional for tracking full-capacity processor value unit licenses. It replaces Tivoli® License Compliance Manager for IBM software, previously
required for tracking the presence of IBM software and generating required reports.
License Metric Tool components
IBM License Metric Tool consists of a server with a DB2® database and Web interface, a command-line interface and agents installed on monitored machines.
Server components
License Metric Tool server
The server collects the inventory data from the agents and enables subscribed users to be notified about events which are relevant to their roles. Each installation of License Metric Tool has a single server, which can run either on the embedded or base
version of the WebSphere®Application Server software.
Database
The License Metric Tool database stores the collected data, such as products installed on systems, processor value units (PVU)
information, hardware information needed for the PVU pricing model, and configuration settings. The database runs on DB2 software.
Integrated Solutions Console
Integrated Solutions Console is the Web interface for the server. Registered users can use it to perform administrative tasks, such as producing PVU capacity reports and inventory information over time.
Command-line interface
The command-line interface can be used to manage License Metric Tool.
Agents
Agents are installed on each operating system that should be monitored by License Metric Tool. They perform hardware and software scans and forward the results to the server.
Chapter 2. Installing with embedded WebSphere Application
Server
Before IBM License Metric Tool is ready for use, install and configure the server and its database. Then, deploy the agents.
Start troubleshooting
the server OPTIONAL
Verify the installation OPTIONAL Is the server running properly? NO YES Configure the product
REQUIRED
Install the agents REQUIRED
Start using the product NO
Perform pre-installation steps SOME STEPS ARE REQUIRED
Reuse the existing DB2
installation?
Would you like to install the server
Interactively?
Install with a wizard Install in silent mode
YES NO
YES
Start the installation of the product Plan the installation
REQUIRED
Install DB2 OPTIONAL
1. Plan the installation. Before starting the server installation, review the information in this section to learn about hardware and software requirements and other considerations. (REQUIRED)
2. If you do not want to reuse an existing instance of the database, install DB2 (REQUIRED), either on the same or separate server. For more information on the advantages and disadvantages of each topology, consult “Planning the topology” on page 4.
3. Install the server interactively or silently. You might want to install the server in a distributed
environment (with the database on a separate computer). (REQUIRED)
4. Start Web user interface to verify the installation. (OPTIONAL)
5. Start troubleshooting the server installation if problems have occurred. (OPTIONAL)
After you have installed the server, configure it. The next task is to , install the agents.
Planning the License Metric Tool server installation
Before starting the server installation, review the information in this section to learn about hardware and software requirements and other considerations.
Planning the topology
Depending on your needs, you can install the IBM License Metric Tool server with the embedded or base WebSphere Application Server. You can also consider installing DB2 on a separate server computer.
Procedure
1. Decide if you are going to install DB2 on the same or separate server computer (you might also reuse it). Consider the following factors:
Table 1. Single versus two-server topology
One-server topology Two-server topology
v Less computing power needed v Faster installation
v More processing power can be assigned to resource-hungry database queries.
v Existing DB2 installation can be reused.
v Fast network connection to the database server is needed.
2. Analyze the advantages and disadvantages of using the embedded versus base WebSphere Application Server. Determine how large your environment is and whether your infrastructure is likely to grow dramatically in the future. Consider the following factors:
Table 2. The embedded versus base WebSphere Application Server Embedded WebSphere Application
Server Base WebSphere Application Server
1. Number of monitored endpoints
Up to 8000 Up to 45000
2. Automatic installation of the application server
Yes. Embedded WebSphere Application Server installed from product installer.
No. Base WebSphere Application Server must be installed before installing the product
3. Graphical installer Yes No. Advanced manual installation (scripted).
Sample scripts are provided.
4. Silent installation Yes No
5. The possibility to set up proxy servers (to connect networks)
No Yes
6. WebSphere Application Server administration console
No. Advanced manual
configuration/maintenance (scripted)
Yes. Graphical user interface for configuration/maintenance.
Note: If you choose to install IBM License Metric Tool on the embedded
WebSphere Application Server, you can later upgrade it to base WebSphere Application Server. No data is lost during the upgrade.
3. Choose the appropriate installation path:
v Chapter 2, “Installing with embedded WebSphere Application Server,” on page 3
v Installing on base WebSphere Application Server
Supported operating systems for the server and database
Ensure that the computer where you are installing the IBM License Metric Tool server runs on one of the supported versions of operating systems.Supported versions of IBM AIX®
Version Required level, service packs, patches
7.1
6.1 v APAR IZ37466 - to apply the fix, the AIX®6.1 instance must be
upgraded to Technology Level 3.
v When installing the DB2 database on AIX, you also need the xlC.aix*.rte 8.0.0.4 or higher XL C/C++ runtime environment which you can download from http://www-01.ibm.com/software/ awdtools/xlcpp/support/
v APAR IZ71102 - to apply the fix, the 6.1.3.6 libc library is required 5.3 (64-bit)
Supported versions of HP-UX
Version Required level, service packs, patches
HP-UX 11i integrity V11.23 Itanium® (64-bit)
HP-UX 11i v3 Itanium (64-bit)
Supported versions of Red Hat Enterprise Linux®
Note: The server and database and their prerequisites require 32-bit support. If you are installing a server or database on the Red Hat Enterprise Linux 64-bit platform, you must ensure that 32-bit support is enabled. In addition to the required packages listed below, you also must install the Compatibility
Architecture Support or Compatibility Architecture Development Support on your system.
Table 3. Supported versions of Red Hat Enterprise Linux
Version Required level, service packs, patches
ES/AS/WS 5 for Intel®x86 (32–bit) compat-libstdc++-33
AS, version 5 for IBM Power Systems™(64-bit)
compat-libstdc++-33
compat-libstdc++-295-2.95.3-81
Both 64-bit and 32-bit versions of the following packages: compat-libstdc++
compat-db-4.1.25-9
xorg-x11-deprecated-libs-6.8.1 or xorg-x11-deprecated-libs-6.8.2 The following 32-bit version packages:
pam
cracklib-dicts cracklib glib2 libselinux
Table 3. Supported versions of Red Hat Enterprise Linux (continued)
Version Required level, service packs, patches
AS, version 5 for IBM System z®
(64–bit)
Update 1, compat-libstdc++-33 compat-libstdc++-295-2.95.3-81
Both 64-bit and 31-bit versions of the following packages: compat-libstdc++
compat-db-4.1.25-9
xorg-x11-deprecated-libs-6.8.1 or xorg-x11-deprecated-libs-6.8.2 The following 31-bit version packages:
pam
cracklib-dicts cracklib glib2 libselinux
Supported versions of SUSE Linux Enterprise Server
Version Required level, service packs, patches
11 for Intel/AMD x86
11 for EM64T and AMD64 pam-modules-32bit 11 for IBM Power Systems (64-bit) pam-modules-32bit 11 for IBM System z (64-bit) on 64-bit
hardware
pam-modules-32bit 10 for Intel/AMD x86 compat-libstdc++
If you plan to install DB2 9.7: Service Pack 2
glibc-2.4-31
libaio-64bit-0.3.104-14.2
The following 32-bit version packages: pam
cracklib-dicts cracklib glib2 libselinux
The following 64-bit version packages: xorg-x11-libs-64bit-6.9.0-50.58.ppc.rpm expat-64bit-2.0.0-13.2.ppc.rpm
fontconfig-64bit-2.3.94-18.16.ppc.rpm freetype2-64bit-2.1.10-18.14.ppc.rpm pam-modules-32bit
Version Required level, service packs, patches
10 for IBM Power Systems (64-bit) compat-libstdc++
Service Pack 1 or later for LPAR mobility If you plan to install DB2 9.7:
Service Pack 2 glibc-2.4-31 libaio-64bit-0.3.104-14.2 vacpp.rte-9.0.0-5 xlsmp.msg.rte-1.7.0-5 xlsmp.rte-1.7.0-5
The following 32-bit version packages: pam
cracklib-dicts cracklib glib2 libselinux
The following 64-bit version packages: xorg-x11-libs-64bit-6.9.0-50.58.ppc.rpm expat-64bit-2.0.0-13.2.ppc.rpm
fontconfig-64bit-2.3.94-18.16.ppc.rpm freetype2-64bit-2.1.10-18.14.ppc.rpm 10 for IBM System z (64-bit) on 64-bit
hardware
compat-libstdc++
If you plan to install DB2 9.7: Service Pack 2
glibc-2.4-31
libaio-64bit-0.3.104-14.2 vacpp.rte-9.0.0-5
The following 31-bit version packages: pam
cracklib-dicts cracklib glib2 libselinux
The following 64-bit version packages: xorg-x11-libs-64bit-6.9.0-50.58.ppc.rpm expat-64bit-2.0.0-13.2.ppc.rpm
fontconfig-64bit-2.3.94-18.16.ppc.rpm freetype2-64bit-2.1.10-18.14.ppc.rpm
Version Required level, service packs, patches
10 Operating System for SPARC platforms (64-bit)
9 Operating System for SPARC platforms (64-bit)
Supported versions of Windows®
Version Required level, service packs, patches
Server 2008 R2 Datacenter Server 2008 R2 Standard Edition (64-bit) for Intel x86
Server 2008 R2 Enterprise Edition (64-bit) for Intel x86
Server 2008 Standard Edition (32-bit and 64-bit) for Intel x86
Server 2008 Enterprise Edition (32-bit and 64-bit) for Intel x86
Server 2003 Standard Edition (32-bit and 64-bit)
Server 2003 Enterprise Edition (32-bit and 64-bit)
Supported partitioning technologies - servers
Any partitioning technology that runs on one of the supported operating systems mentioned above.
CPU and memory requirements for the server and database
Ensure that the computer where you are installing the IBM License Metric Tool server meets the minimal CPU, and memory requirements for the server and database elements.The requirements are divided into:
v Hardware requirements for environments with up to 8 000 agents. v Hardware requirements for environments with 8 000 to 45 000 agents.
CPU requirements for environments with up to 8 000 agents
Server AIX and Linux 2 Power4 1.2 GHz Linux and Windows x86,
32 and 64–bit
at least one Intel Core Solo T1300 1.66 GHz processor
Solaris SPARC Sun-Fire-280R 1015 MHz two–way processor HP-UX rp2470, at least two PA-RISC 2.0 650 MHz
processors Linux on zSeries®
CPU requirements for environments with up to 8 000 agents
Database For CPU requirements for DB2 9.1, 9.5, and 9.7 see http://www-01.ibm.com/ software/data/db2/9/sysreqs.html.
Memory requirements for environments with up to 8 000 agents
Server only 1 GB RAM
Server and database 3 GB RAM
CPU requirements for environments with 8 000 to 45 000 agents
Server AIX and Linux At least one Power6 4.7 GHz processor Linux x86, 32 and 64–bit Intel®
Xeon®
2.5 GHz, four-way processor Solaris SPARC One SPARC VI, 2150 MHz (4 threads) processor HP-UX rp8420, at least two PA-RISC 2.0 1.0 GHz
processors
Linux on zSeries Type 2084, two dedicated processors Windows x86, 32 and
64–bit
One Dual Core AMD Opteron, 2.6 GHz processor
Database For CPU requirements for DB2 9.1, 9.5, and 9.7 see http://www-01.ibm.com/ software/data/db2/9/sysreqs.html.
Memory requirements for environments with 8 000 to 45 000 agents
Server only 1 GB RAM
Server and database 4 GB RAM
Space requirements for the server and database
Check if your computer has the required amount of disk space for server and database installation.
You can install the IBM License Metric Tool server and database on the same computer, or on two different computers. You need to install the DB2 database software before you start the installation process or you can use a working installation of DB2.
The table below shows how much space you need depending on your operating system and the components that you are installing on this machine. The space requirements for the server component were measured for the embedded version of WebSphere Application Server included in the installation package. If you want to install the License Metric Tool server on base WebSphere Application Server (recommended for large environments with more than 8000 agents), visit WebSphere Application Server information center for space requirements: http://publib.boulder.ibm.com/infocenter/wasinfo/v7r0/index.jsp?topic=/ com.ibm.websphere.nd.doc/info/welcome_nd.html.
Important: In addition to the space requirements described below, remember to
reserve some space for the database in the database location. When you sign a report, it is first generated and stored as an XML file on your hard disk drive. For large environments and long reporting periods, the file can be up to 2 GB in size.
If there is not enough free space, the signing of the report fails. You can specify the location where the XML file is generated by editing the reportPath parameter in the setserverconf command.
The first installation step is the self-extraction of the installer into a temporary directory.
Windows The installer self-extracts into the temp directory. The directory is
specified by the TEMP environment variable. Before the installer is extracted, the tool checks if there is enough disk space for the installation. The required space exceeds three times the size of the installer. If there is not enough space available, the installer prompts you for a different extraction location.
UNIX The installer self-extracts into the /tmp directory. The tool checks if there
is enough disk space for the installation. If you specify a different location by setting the IATEMPDIR environment variable, the installer uses it if there is not enough space available.
Note:
1. You can specify a directory other than /tmp by setting the IATEMPDIR variable. 2. If there is not enough space in the temporary directory or the directory is not
available, the installer uses the $HOME directory. The requirements below are for installation only.
Operating system Installed
components Directory Required space
AIX Server and database, including the DB2 prerequisite Product installation directory 1941 MB DB2 installation directory 507 MB Database installation directory 562 MB /tmp 632 MB /etc under 1 MB /var under 1 MB Total 3644 MB Server and database without the DB2 prerequisite Product installation directory 1941 MB Database installation directory 553 MB /tmp 632 MB /etc under 1 MB /var 259 MB Total 3386 MB
Server only Product installation directory 1941 MB /tmp 632 MB /etc under 1 MB /var under 1 MB Total 2575 MB Database, including the DB2 prerequisite Product installation directory 125 MB DB2 installation directory 507 MB Database installation directory 562 MB /tmp 632 MB /etc under 1 MB /var 125 MB Total 1952 MB Database without the DB2 prerequisite Product installation directory 125 MB Database installation directory 553 MB /tmp 121 MB /etc under 1 MB /var 125 MB Total 925 MB
Operating system Installed
components Directory Required space
HP-UX Server and database, including the DB2 prerequisite Product installation directory 1873 MB DB2 installation directory 1537 MB Database installation directory 2973 MB /tmp 349 MB /etc under 1 MB /var/tmp 418 MB Total 7151 MB Server and database without the DB2 prerequisite Product installation directory 1873 MB Database installation directory 517 MB /tmp 343 MB /etc under 1 MB /var under 1 MB /var/tmp 418 MB Total 3153 MB
Server only Product installation directory 1845 MB /tmp 343 MB /etc under 1 MB /var/tmp 418 MB Total 2607 MB Database, including the DB2 prerequisite Product installation directory 293 MB DB2 installation directory 1537 MB Database installation directory 2973 MB /tmp 349 MB /etc under 1 MB /var under 1 MB /var/tmp 418 MB Total 5572 MB Database without the DB2 prerequisite Product installation directory 293 MB Database installation directory 472 MB /tmp 343 MB /etc under 1 MB /var under 1 MB /var/tmp under 1 MB Total 1111 MB
Operating system Installed
components Directory Required space
Linux Server and database, including the DB2 prerequisite Product installation directory 1889 MB DB2 installation directory 830 MB Database installation directory 556 MB /tmp 121 MB /etc under 1 MB /var under 1 MB /var/tmp under 1 MB Total 3399 MB Server and database without the DB2 prerequisite Product installation directory 1889 MB Database installation directory 509 MB /tmp 591 MB /etc under 1 MB /var under 1 MB /var/tmp under 1 MB Total 2992 MB
Server only Product installation directory 1889 MB /tmp 591 MB /etc under 1 MB /var 4 MB /var/tmp under 1 MB Total 2486 MB Database, including the DB2 prerequisite Product installation directory 296 MB DB2 installation directory 830 MB Database installation directory 556 MB /tmp 121 MB /etc under 1 MB /var 2 MB /var/tmp under 1 MB Total 1807 MB Database without the DB2 prerequisite Product installation directory 296 MB Database installation directory 509 MB /tmp 121 MB /etc under 1 MB /var 2 MB
Operating system Installed
components Directory Required space
Solaris Server and database, including the DB2 prerequisite Product installation directory 1999 MB DB2 installation directory 1262 MB Database installation directory 2370 MB /tmp 216 MB /etc under 1 MB /var 260 MB /var/tmp 259 MB Total 6367 MB Server and database without the DB2 prerequisite Product installation directory 1999 MB Database installation directory 472 MB /tmp 182 MB /etc under 1 MB /var 222 MB /var/tmp 222 MB Total 3098 MB
Server only Product installation directory 1971 MB /tmp 182 MB /var 259 MB /var/tmp 259 MB Total 2671 MB Database, including the DB2 prerequisite Product installation directory 181 MB DB2 installation directory 1262 MB Database installation directory 2370 MB /tmp 216 MB /etc under 1 MB /var 259 MB /var/tmp 260 MB Total 4549 MB Database without the DB2 prerequisite Product installation directory 181 MB Database installation directory 508 MB /tmp 181 MB /etc under 1 MB /var under 1 MB Total 872 MB
Operating system Installed
components Directory Required space
Windows Server and database, including the DB2 prerequisite Product installation directory 1662 MB DB2 installation directory 530 MB /tmp 590 MB Database installation directory 437 MB Total 3219 MB Server and database without the DB2 prerequisite Product installation directory 1881 MB
DB2 installation directory under 1 MB
/tmp 590 MB
Database installation directory
437 MB
Total 2909 MB
Server only Product installation directory 1881 MB /tmp 590 MB Total 2471 MB Database, including the DB2 prerequisite Product installation directory 123 MB DB2 installation directory 530 MB /tmp 590 MB Database installation directory 437 MB Total 1680 MB Database without the DB2 prerequisite Product installation directory 123 MB
DB2 installation directory under 1 MB
/tmp 112 MB
Database installation directory
437 MB
Total 673 MB
Other software prerequisites
Ensure that all required prerequisite software is installed on the computer where you are installing the IBM License Metric Tool server.
Administration server
Table 4. Prerequisites for administration serverDatabase driver JDBC driver type 4 is automatically installed if not already present.
UNIX®shell To install the servers on UNIX platforms you must have the Bourne shell (sh) installed and
activated. It is not necessary to run the installation from the Bourne shell.
Table 4. Prerequisites for administration server (continued)
Web browser A web browser is required to access the web user interface of the server. It is also needed for the installation launchpad to start; however, it is also possible to start the installation of License Metric Tool without the launchpad. Supported browsers on different platforms: v Supported MS Windows versions
– Internet Explorer 6.x, and 7.x, – Firefox 2.0.x
v Other supported platforms – Firefox 2.0.x
Note: It is important not to turn the JavaScript™option off in the browser as some of the
functionalities of the web interface might not function properly. For secure connections, cookies need to be enabled.
Gzip compression utility UNIX Linux It is needed for the installation process to run.
gdiplus.dlllibrary Windows This library is needed to run the License Metric Tool Launchpad.
Administration server database
You have two options for installing the DB2 software prerequisite:
v You can install it ahead of time, using the installation media provided with License Metric Tool.
v You can use an existing instance of DB2 that you have already installed. Refer to the following table for required software levels.
WebSphere Application Server
You have two options for installing the WebSphere software prerequisite: v If you do not plan to support more than 8000 agents, you can install the
embedded version of the WebSphere Application Server from the License Metric
Tool wizard.
v To support a larger infrastructure, you must install a base version of WebSphere Application Server before installing License Metric Tool. You can install the base edition using the 6.1 installation media that are provided with this product, or you can use an existing installation of WebSphere Application Server 6.1 or later. For more details about WebSphere installation, refer to the WebSphere
information center.
Table 5. Prerequisites for WebSphere Application Server
Preparing the operating system for product installation http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/topic/ com.ibm.websphere.base.doc/info/aes/ae/tins_prepare.html embeddedWebSphere Application Server V6.1 Fix Pack 33
This fix pack and Update Installer are shipped with the product.
baseWebSphere Application Server V6.1 Fix Pack 33
Supported versions of WebSphere Application Server
For large production environments, you can install the server on the base version of WebSphere Application Server, instead of the embedded version that can be installed as part of IBM License Metric Tool.
License Metric Tool supports the following versions of WebSphere:
v WebSphere Application Server, version 6.1, Fix Pack 23, Fix Pack 29 or later v WebSphere Application Server Network Deployment, version 6.1 (standard
application server profile only), Fix Pack 23, Fix Pack 29 or later
On Solaris 9 operating system for SPARC platforms (64-bit), License Metric Tool supports only the 32-bit version of the application server.
Note: If you are installing on the base version of WebSphere Application Server, with enabled secure agent-server communication, you must apply a Java™update
on WebSphere Application Server. You can download the update from the following page: http://www-01.ibm.com/support/docview.wss?rs=180 &uid=swg24019127. If you do not apply the Java update, the secure
communication will not work properly. Depending on the security level, the agent will be able to connect to the server but other operations such as catalog download or the import of a private certificate when configuring agents will cause GSKit exceptions.
Topology and capacity planning
Before installing IBM License Metric Tool to monitor the installed software in your organization, you need to plan the placement of the product components.
Scan groups
Scan groups are units for grouping agents. Scans of installed software and hardware are scheduled on a scan group level. Decide how you want to divide agents between scan groups so that the operations which you can perform by scan groups are meaningful within your organization. Each agent must be assigned to a scan group.
Note: Creating scan groups is not mandatory but preferable. There is always a
scan group to which agents are assigned by default.
To find out more about scan groups, go to Scan groups in the Administering section of the Information Center.
Placement of server components
For performance reasons, it is recommended that you install the server software on a dedicated computer or on a dedicated partition (It means License Metric Tool can consume all of the available processor and memory resources allocated to a
dedicated computer/partition). You can install the database on the same computer/partition as the server or on a different one. If you are installing the database on a different computer/partition than the server, you must run the installer twice on both computers/partitions.
Depending on the size of your IT infrastructure, you need to make the following choices:
v If you will support fewer than 8000 agents, you can install the limited-use version of WebSphere Application Server software that is embedded with License Metric Tool.
v If you will support more than 8000 agents, it is recommended that you install base WebSphere Application Server version 6.1 or higher on the computer where you will install the License Metric Tool server. One instance of WebSphere Application Server can support up to 45000 agents. You do not need an additional license for this type of WebSphere Application Server - it is covered by License Metric Tool license.
Placement of agents
In a partitioned operating environment, you must install agents on every guest operating system that hosts the software products for which you need to monitor license compliance.
Agent backward compatibility
The following versions of License Metric Tool agents are able to connect to the License Metric Tool 7.2.2 server:
v License Metric Tool 7.2.1 GA, and Fix Pack 1 v License Metric Tool 7.2 GA, and Fix Pack 1 v License Metric Tool 7.1 GA, and Fix Pack 1 v 2.3 Fix Pack 4, 5, 6, and 7
Using secure communications
The use of secure communications between the infrastructure elements is described fully in the Security section of the information center.
Network planning
IBM License Metric Tool and its agents do not generate heavy data traffic for extended periods of time. However, some network planning is required.
A single agent does not require high bandwidth for the communication with the server. The amount of data exchanged with the License Metric Tool server can be as high as 350 kilobytes in a 24-hour timeframe (This includes the upload of software and hardware scan results).
If the database is installed on a separate computer from the monitoring server, provide a high-speed connection between the two.
Secure communication can have an impact both on network traffic and server performance, especially on the maximum security level.
License Metric Tool uses the following ports for the data exchange between the server and its agents.
Note: The ports below are only the default values and can be changed during the
Table 6. Ports used by License Metric Tool
Type Value
User Interface 8899 (http) and 8888 (https)
These ports are default ports for embedded WebSphere Application Server. If you are not using default ports, you can check the port values in Installation_folder/admin/master.tag.
For the base version of WebSphere Application Server, the port numbers are characteristic of the profile on which the product is deployed.
Agent-server communication
9988 (http), 9999 (https) and 9977 (https with client authentication)
Database (DB2) default value of 50000
For information about configuring DB2 ports see
http://publib.boulder.ibm.com/infocenter/db2luw/v9/topic/ com.ibm.db2.udb.uprun.doc/doc/t0004727.htm.
Security considerations
There are some security issues that you need to take into consideration while installing and configuring IBM License Metric Tool.
Required access privileges for the installation
In order to install the License Metric Tool server or agent, log on to the computer where you want to install the software as a user with administrative rights on Windows or as a root on UNIX platforms. The only exception to this rule is if you are installing agents using IBM Tivoli Configuration Manager.
Database user IDs
During the installation process, you need to specify a user ID and password for performing DB2 administrative tasks, such as creating and dropping databases. You also need to provide a password for the tlmsrv ID, which is used by server processes to access the database.
Levels of security
There are three possible levels of security used for communication between the server and agents. You need to select one of them depending on the security regulations in your organization.
Minimum
The agent communicates with the server computer on the nonsecure port and no check of the client or server identity is made.
Medium
The agent communicates on the secure port and an SSL certificate is used to authenticate the identity of the server.
Maximum
The server must authenticate all clients that contact it. Therefore, all agents that communicate with the server must also be configured for maximum
security and must have personal certificates deployed. The server listens on the secure port and the secure port is configured to require both client and server authentication.
Ports
For the list of ports used by License Metric Tool, go to “Network planning” on page 18.
Security-Enhanced Linux
Security-Enhanced Linux set to enforcing mode can cause problems with the installation and use of License Metric Tool server and agents. If your operating system enables SELinux, you will need to either set it to permissive, or disable it completely.
Proof-of-concept installation
You can perform proof-of-concept installation of the server before the actual production installation. This will allow you to quickly set up an environment, check if it is working and if it satisfies your business needs.
Proof-of-concept installation has all the functions of the production version, but the database parameters are scaled down and the communication times between product components are reduced. If you use this mode of installation, you cannot install the Administration server and Administration server database on separate computers. You can launch proof-of-concept installation by selecting Test
Environmentat the start of the server installation.
Note: Proof-of-concept installation can be performed only on the embedded
version of WebSphere Application Server. After you finish testing, you can install the server in production mode either with the embedded or on the base version of WebSphere Application Server.
The table includes a comparison of parameter values for test (proof-of-concept) and production environment installations.
Table 7. Proof-of-concept and production installations
Configuration parameters stored in the database Test environment Production environment
Server BUFFERPOOL 20000 80000
upload_usage_period(minutes) 5 360
ping_period(minutes) 2 60
report_finalization_delay(days) 1 7
testEnvironmentEnabled true false
fipsEnabled false false
agentToServerSecurityLevel 0 0 productInventoryBuilderPeriod (minutes) 60 300 maxAggregateUsageAge(days) 1 2 inventoryScanGracePeriod(hours) 1 10
Table 7. Proof-of-concept and production installations (continued)
Agent down_parms_period(minutes) 7 360
maxAgentInactivity(minutes) 30 10080
maxAgentInactivityToDelete
(minutes)
43200 43200
After you have tested the configuration by performing the proof-of-concept installation, you can begin installing the License Metric Tool server and agents.
Installing the server (embedded WebSphere Application Server)
After you have decided on the installation path, check the software and hardware requirements. Then, install the server either on the embedded or base WebSphere Application Server.
Installation checklist - installing on embedded WebSphere
Application Server
You can print the checklist and use it during the installation to ensure that you have completed all the necessary steps.
Table 8. Installing IBM License Metric Tool on the embedded version of WebSphere Application Server
Step Task Status
1 Plan and prepare to install
1.1 Plan the topology.
Depending on your needs you can install the server with the embedded or base WebSphere Application Server. You can also consider installing DB2 on a separate server computer. 1.2 Ensure that the computer where you are installing the server fulfills all software and hardware
requirements.
Before you install the server, you need to make sure that the computer meets the minimal CPU, and memory requirements for the server and database elements. You also need to check if there is enough disk space for the installation. Next, make sure that you use one of the supported operating systems and all the prerequisite software is installed.
1.3 Consider the level of security for the communication between the server and agents.
You need to take into consideration the level of security that you want to use for the communication between the server and agents.
1.4 Prepare the files for installation.
If you have downloaded the installation image from Passport Advantage, extract the files before installing the product. On the computer where you are running the installer, log on as root (UNIX or Linux) or Administrator (Windows). Place all the downloaded installation images in a single directory on the computer where you are running the installer, and extract them.
Table 8. Installing IBM License Metric Tool on the embedded version of WebSphere Application Server (continued)
Step Task Status
2.1 If you are installing the server and its database on different computers, synchronize the clocks of the server and database computers.
If you have decided to install the server and the database on separate computers, the time difference between the two computers should not be greater than 300 seconds. Use a
non-manual method of clock synchronization, for example Network Time Protocol. All recent UNIX and Windows systems have the ability to synchronize with the Network Time Protocol servers. To configure time synchronization on other operating systems, refer to user
documentation.
2.2 Linux Change SELinux settings.
Red Hat Enterprise Linux enables SELinux by default, which is incompatible with License Metric tool. To ensure proper server installation, you need to change the SELinux settings from enforcing mode to either permissive or disabled. This change must be permanent because turning enforcing mode back on prevents the server from working.
2.3 Ensure that you have the required version of DB2 and its fix packs installed on your computer
The supported versions of DB2 are: 9.1, 9.5, and 9.7.
2.4 If you have decided to install the server in interactive mode, run the installation wizard.
In this option, you need to specify all parameters as the installation proceeds. If you have decided to install the database on a separate computer than the server, for example to improve the performance of the server, run the installer twice on each of the computers. DB2 software should already be installed on the designated computer.
As an alternative to using the installation wizard, you can specify parameters in a response file and start the installation from the command-line interface.
2.5 Verify the installation that you have run either in interactive or in silent mode.
To make sure that the installation has been successful, check the log files and start the Web user interface. Open the msg_servers.log file and check if it contains information that the application was successfully installed. The file is by default stored under the following path:
Tivoli_Common_Directory/COD/logs/install/message. Access the login page at the following address: http://administration_server_IP_address:8899/ibm/console/login.do and check the Home page for information about any problems that might have occurred during installation.
3 Configure the server
3.1 Create scan groups and assign agents to chosen scan groups.
To organize scan schedules, first create scan groups and then associate agents with those scan groups. The agents belonging to the same scan group share the same configuration parameters, for example the same scan schedule, set by means of the setagentconf command or by means of the user interface.
3.2 Import the software catalog.
The IBM®
catalog is a knowledge base of product information that provides the information required by License Metric Tool to recognize which products are installed and in use on monitored computers. Use the Integrated Solutions Console to obtain the IBM catalog and import it into the server database.
3.3 Import the processor value units table.
The processor value units table is required to support processor-based pricing models in which charges differ according to the type of processor on which the licensed product is installed and running. In the table, a number of units is assigned to each processor type on which this type of pricing model is available. Use the Integrated Solutions Console to obtain the processor value units table and import it into the database.
Table 8. Installing IBM License Metric Tool on the embedded version of WebSphere Application Server (continued)
Step Task Status
3.5 Optional. Add VM Managers that gather information about your VM infrastructure. 3.7 Required. Enable and configure server security .
Log on to the Integrated Solutions Console to enable the server security. 3.8 Optional. Configure permissions for users.
After you have enabled security for the License Metric Tool server, you need to configure access rights for the users. You can do it by assigning user to roles.
3.9 Optional. Configure event notifications.
You can configure the server to generate email notifications of significant licensing and system administration events. The notifications are then sent to recipients that you select in the Web interface. To configure event notifications, use the setserverconf command.
Preinstallation steps
Before you start the installation, prepare installation images and install DB2. If you want to install the server and the database on different computers, synchronize the server and database clocks.
1. “Preparing installation images” 2. “Server installer files” on page 24
3. “A summary of IBM License Metric Tool 7.2.2 installation images” on page 25 4. “Information regarding installing DB2” on page 25
5. “Synchronizing the clocks of server and database computers” on page 26 6. “Changing SELinux settings before installing License Metric Tool on Red Hat
Linux” on page 26
Preparing installation images
If you downloaded the installation image from Passport Advantage, extract the files before installing the product.
There are two forms of installation media: v Product disks
v The IBM Passport Advantage Web site. Licensed customers can download installation images for each of the DVDs.
If you are using downloaded installation images, perform the following steps to create the directory structure for a central installation image repository.
Procedure
1. Download the software from Passport Advantage. Information about the download is described in the download document. Use the tabs to open the download documents for supported operating systems.
2. On the computer where you are running the installer, log on as root (UNIX or Linux) or Administrator (Windows).
3. Place all the downloaded installation images in a single directory on the computer where you are running the installer. For example:
v Linux UNIX
v Windows
C:\install_images
Note: It is important to extract the files on the computer where you are running the installer, because the files must have the correct permissions when you extract them from the images.
4. Extract the contents of all installation images to the directory that you have created.
Server installer files
After you extract the installer file on a given platform, a directory structure is created with different installer files.
Table 9. The most important License Metric Tool installer files
Path (Windows platform) Description
\server\parts\CDROM_Installers\Disk1\InstData\Win32\VM\ eWAS_6.1.0.23.zip
Embedded WebSphere Application Server package
\server\parts\CDROM_Installers\Disk1\InstData\platformVM\ setupServers.exeor /server/parts/CDROM_Installers/Disk1/ InstData/platformVM/setupServers.bin
Installation application launcher
\server\parts\CDROM_Installers\Disk1\InstData\
Resource1.zipserver\parts\CDROM_Installers\Disk1\InstData\ MediaId.properties
Internal installer files
\server\parts\CDROM_Installers\Disk1\InstData\desc Image description
\installResponsePOC.txt The response file used in test installation \installResponseProduction.txt The response file used in production
installation \LMT-server-7.2.2-windows-x86_number_of_bits.bat or
\LMT-server-7.2.2-operating_system-platform_number_of_bits.sh
The server installer file name (by platform)
\tools\expmap The directory contains the ExpMapTool files. The ExpMapTool exports the
deployment configuration of Tivoli License Compliance Manager 2.3 into an XML file. \tools\checkVersion.sh The script checks the version of WebSphere
Application Server on UNIX and Linux operating systems. This script calls the checkVersion.jaclscript.
\tools\checkVersion.jacl The JACL script checks the version of WebSphere Application Server and Integrated Solutions Console.
\tools\checkVersion.bat The script checks the version of WebSphere Application Server on Windows platform. \tools\getarch Internal installer helper script
\license\supported_lang_directory The license directory contains sixteen sub-directories with IBM licenses in supported national languages.
\license\non_ibm_license.txt The file contains terms and conditions for separately licensed code.
\license\notices.txt The file contains notices and third party license terms and conditions.
Table 9. The most important License Metric Tool installer files (continued)
Path (Windows platform) Description
\launchpad\ The directory contains launchpad binary, content and configuration files.
A summary of IBM License Metric Tool 7.2.2 installation images
To perform the installation, you need several packages that you can download from the Passport Advantage or Software Support web site (fix pack) or copy from the product DVD. Some of the images can differ depending on whether you install on the embedded or base WebSphere Application Server. You will also need fix pack files which are required for bringing WebSphere Application Server to the required software level.
Table 10. Installation packages for installing on the embedded WebSphere Application Server No Type of image If you install on embedded WebSphere Application Server
1. Server images License Metric Tool 7.2.2 platform specific server installation package. It contains the following packages:
v The embedded WebSphere Application Server 6.1 is packaged with the License Metric Tool 7.2.2 server installation package
v Integrated Solutions Console version 7.1.0.9 package for embedded Websphere Application Server
2. Agent images v License Metric Tool 7.2.2 agent installation package (native installer) v Agent installation package, collection of Software Package Blocks only for
Tivoli Configuration Manager-based installation
v Agent shell installation packages for all UNIX platforms v Agent shell installation package, collection of all shell installers v Common Inventory Technology Enabler
3. WebSphere Application Server images
IBM Update Installer 7.0.0.9 for WebSphere Software is available on the following download page or on the product DVD, in the directory server/fixpacks.
Embedded WebSphere Application Server 6.1.0 fix pack 33 is needed only if you upgrade from License Metric Tool 7.2 to 7.2.2. The file
6.1.0-WS-WASEmbded-Platform-FP0000033.pakis available on ftp server at ftp://
ftp.software.ibm.com/software/websphere/appserv/support/fixpacks/was61/ cumulative/cf61023/.
Integrated Solutions Console 7.1.0, fix pack 9 (the file 6.1.0.11-WS-WASFeature-FEISCAE7109EWAS.pak) is available on the product DVD in the directory
server/fixpacks.
4. DB2 images v DB2 Enterprise Server Edition 9.7
v DB2 Enterprise Server Edition 9.7 Restricted Use Activation 5. Documentation images v Quick Start Guide
v License Metric Tool 7.2.2 Quick Start (this image contains complete information center).
6. Additional images v IBM Prerequisite Scanner for UNIX platforms v IBM Prerequisite Scanner for Windows platform
Information regarding installing DB2
Install DB2 before you start installing IBM License Metric Tool. You can install it on the same or separate computer, depending on the size of your infrastructure.
For information how to install DB2 refer to the highest level topics in DB2 information centers:
v Installing DB2 Version 9.1 v Installing DB2 Version 9.5 v Installing DB2 Version 9.7
After you have installed DB2 you need to apply the license entitlement certificate. For information on how to do that refer to the topic Registering a DB2 product or
feature license key using the db2licm command in the following information centers:
v DB2 9.1 v DB2 9.5 v DB2 9.7
To get the db2ese_o.lic license file uncompress the DB2 Enterprise Server Edition
V9.1 Restricted Use Activation package (part number C150QML, file name
DB2_ESE_Restricted_Activation_V91.zip) downloaded from Passport Advantage. You can list all the DB2 products with available license information, including the product identifier by issuing the following command: db2licm -l.
Now, you can install License Metric Tool.
Synchronizing the clocks of server and database computers
If you have decided to install the server and the database on separate computers, the time difference between the two computers should not be grater than 300 seconds. A greater time difference might result in data loss or corruption in the server database.
If the clocks are not synchronized, the server will start in problem determination mode, and some features will not be accessible.
Use a non-manual method of clock synchronization, for example Network Time Protocol. All recent UNIX and Windows systems have the ability to synchronize with Network Time Protocol servers. To configure time synchronization on other operating systems, refer to user documentation.
The following example shows how you can ensure that the clocks are synchronized on the Windows XP operating system. The method shown here requires that both computers are connected to the Internet.
Procedure
1. On the application server, open the Windows Control Panel and select Date
and Time.
2. On the Internet Time tab, select the time of the server that you want to synchronize with.
3. Repeat this operation on the computer where you will install the database.
Changing SELinux settings before installing License Metric Tool
on Red Hat Linux
Red Hat Enterprise Linux enables SELinux by default, which is incompatible with IBM License Metric Tool. To ensure proper server installation, you need to change the SELinux setting from enforcing mode to either permissive or disabled.
This change must be permanent because turning enforcing mode back on prevents the server from working.
Do not set the enforcing mode by changing the context to textrel_shlib_t for all the libraries used by server.
Procedure
1. Open the /etc/selinux/config file.
2. Change the SELINUX parameter to permissive or disabled. 3. Restart the computer.
Installing in interactive mode
When performing an interactive installation, you provide the required parameters as the installation proceeds.
1. “Preinstallation steps” on page 23
Before you start the installation, prepare installation images and install DB2. If you want to install the server and the database on different computers, synchronize the server and database clocks.
2. “Installing the server in interactive mode”
Use the installation wizard to specify all parameters as the installation proceeds.
3. “Installing IBM License Metric ToolTivoli Asset Discovery for Distributed in interactive mode on separate computers” on page 32
If you have decided to install the database on a separate computer than the server, for example to improve the performance of the server, run the installer twice on each of the computers. Install DB2 before you run the installer on the designated computer.
4. “Verifying the interactive installation” on page 36
Check the log files and start the Web user interface to verify that the server installation has been successful.
5. “Resuming a stopped or failed License Metric Tool installation” on page 37 There are three phases of server installation on embedded WebSphere Application Server: preinstallation, installation and postinstallation. If the installation fails or stops, there can be different ways to rerun it, depending on the phase or method used.
Installing the server in interactive mode
Use the installation wizard to specify all parameters as the installation proceeds.
Before you begin
v You must have the following operating system privileges:
– UNIX Linux root
– Windows Administrator
v On UNIX and Linux server computers, there must be graphical interface available. Otherwise, you must use silent mode.
v If you have downloaded the installation image from Passport Advantage, ensure that you have prepared your files for installation.
v Before you start the installation of the server, you must apply the DB2 license entitlement certificate. For information about how to do that see the topic Registering a DB2 product or feature license key using the db2licm command
(DB2 9.1). To get the db2ese_o.lic license file uncompress the DB2 Enterprise
Server Edition V9.1 Restricted Use Activation package (part number C150QML, file
name DB2_ESE_Restricted_Activation_V91.zip) downloaded from Passport Advantage.
Procedure
1. In the directory where you extracted the installation files, run launchpad.exe (Windows) or launchpad.sh (other platforms). The Welcome page opens. You can also launch the installation file
v UNIX Linux ILMT-server-7.2.2-your_platform.shor
v Windows ILMT-server-7.2.2-your_platform.bat(Windows)
directly from the DIRECTORY_WITH_INSTALLATION_FILES\server. You do not need the web browser for this method. You are directed straight to the language selection window.
2. In the left navigation bar, click Install or upgrade to IBM License Metric
Tool.
3. Click Launch the server installation wizard. A splash screen opens.
4. Select the language of the installation and click OK. The installation wizard starts and the welcome panel opens. Click Next.
5. Accept the terms of the license agreement, and click Next. Specify the directory where you want to install License Metric Tool. Click Next. 6. On the new panel, specify the type of installation that you want:
v For typical installation, select Production Environment. v For proof-of-concept installation, select Test Environment.
You can compare the differences between the Production and Test installations by reading the information in the help area on this panel.
Note: If you select Test environment, both components are installed on the
local computer. Click Next.
7. Select the components that you want to install. You can install the server and database on the same computer or on different computers. If you have already installed a component on this computer, or you are running the
proof-of-concept installation, that selection is unavailable and this panel does not appear.
If you select both components or start with the database installation, you will be able to test the connection between the server and the database. After completing the installation of both components, you will not need to restart the server. If you first install the server and then the database, you will need to restart the database. Click Next.
8. If you have decided to install the server database, you must specify: v Windows The location of the DB2 instance.
v UNIX Linux The home directory of the DB2 instance owner.
You can enter the location of DB2 manually or you can choose from the list of found DB2 instances. The drop-down list contains all local DB2 instances found, including those that are not supported. They are marked with a different color and you cannot select them.
After you have clicked Next, the selected database will be verified and the verification results will be presented on the panel.
Once the Checklist items are verified, you can proceed to the next panel by clicking Next.
9. If you have decided to install the server, you can accept or change the ports for communication with the server console and agents. The installer checks if the ports you selected are already in use. If there are any conflicts, or you duplicated the values for the ports, a message about the problem displays.
Click Next to start verification. Then click Next again to access the next panel. 10. If you have decided to install the server database, you must specify the
password for the tlmsrv user, which is created during installation (The password is stored in an encrypted form in the application server configuration files). After clicking Next, the password is validated for correctness. Additionally, the installation wizard searches for the existing server database in the selected DB2 instance. In case the server database is found, the installer verifies whether it can be used or migrated. If the database is not found, it is created.
If you have decided not to install the server database, you must specify the details of the connection to the remote server database. Select Do not validate
the remote databaseif you plan to install it later. After clicking Next, the installation wizard tries to open a JDBC connection using the provided values. Additionally, if the remote database was created by different version or product or it was created in a different mode, it is reported as a warning. Click Next to access the next panel.
11. Define the security settings:
Use FIPS 140-2 cryptography
This option is available only when you are installing the server. Select it to enable the encryption of data using approved algorithms from the Federal Information Processing Standard 140–2. This setting applies to the server that communicates with the agents.
IBM i FIPS cannot be used on System i platforms. If your
environment includes even one agent running on IBM i, FIPS cannot be turned on.
Security Level
v If you set the minimum or medium security level, agents can communicate with the server by either the secure or nonsecure port, depending on the security level that you define when you deploy agents.
v If you set the maximum security level, you must set the same level of security for all agents when you deploy them.
Attention: For information about how to set the level of security before installing agents, refer to the topic Performing agent security-related tasks.
12. Click Next and review the installation information. On the installation summary page, check the information that is provided and confirm that you have enough space to complete the installation. The creation of temporary files might require more space, than the total size shown. If the amount of available space is close to the total size shown, clear some space before proceeding. Click Install to install the product.
Important: The installation program creates some temporary files, so at times
more disk space is required than the total size shown on this page. Consider this extra requirement before proceeding with the installation; if necessary, clear additional space.
13. When the installation completes, click Finish to exit the wizard.
If you are installing the server and database on separate computers, log on to the other computer and run the installer again.
After both the server and database are installed, configure the server security, add users in the web interface, and install the agents.
Installing IBM License Metric ToolTivoli Asset Discovery for
Distributed in interactive mode on separate computers
If you have decided to install the database on a separate computer than the server, for example to improve the performance of the server, run the installer twice on each of the computers. Install DB2 before you run the installer on the designated computer.
Installing the database on a designated computer: Before you begin
Before you start the installation of the server you need to apply the DB2 license entitlement certificate. For information on how to do that refer to the topic
Registering a DB2 product or feature license key using the db2licm command (DB2 9.1). To get the db2ese_o.lic license file uncompress the DB2 Enterprise Server
Edition V9.1 Restricted Use Activation package (part number C150QML, file name
DB2_ESE_Restricted_Activation_V91.zip) downloaded from Passport Advantage. If you start with the database installation, you will be able to test the connection between the server and the database. After the installation of both components is completed, the server will not need to be restarted to work. If you first install the server and then the database, you will need to restart the server.
Procedure
1. In the directory where you extracted the installation files, run launchpad.exe (Windows) or launchpad.sh (other platforms). The Welcome page opens. You can also launch the installation file
v UNIX Linux ILMT-server-7.2.2-your_platform.shor
v Windows ILMT-server-7.2.2-your_platform.bat(Windows)
directly from the DIRECTORY_WITH_INSTALLATION_FILES\server. You do not need the Web browser for this method. You are directed straight to the language selection window.
2. In the left navigation bar, click Install or upgrade to IBM License Metric
Tool.
3. Click Launch the server installation wizard. A splash screen opens.
4. Select the language of the installation and click OK. The installation wizard starts and the welcome panel opens. Click Next.
5. Accept the terms of the license agreement, and click Next. Specify the directory where you want to install License Metric Tool. Click Next. 6. On the new panel, specify the type of installation that:
v For a typical installation, select Production Environment.
Note: Test mode enforces both components to be installed on local computer.
Click Next.
7. Select the Database for administration server component and click Next. 8. On the next panel specify:
v Windows DB2 installation directory
v UNIX Linux The home directory of the DB2 instance owner.
You can enter the location of DB2 manually or you can choose from the list of found DB2 instances. The dropdown list contains all local DB2 instances found, including those that are not supported. They are marked with a different color and you cannot select them.
After you have clicked Next, the selected database will be verified and the verification results will be presented on the panel.
Once the Checklist items are verified, you can proceed to the next panel by clicking Next.
9. Specify the password for the tlmsrv user, which is created during the installation (The tlmsrv is stored in an encrypted form in the application server configuration files). After clicking Next, the password is validated for correctness. Additionally, the installation wizard searches for the existing server database in the selected DB2 instance. In case the server database is found, the installer verifies whether it can be used. If the database is not found, it will be created.
10. Define the security settings:
Security Level
v If you set the minimum or medium security level, agents can communicate with the server by either the secure or the nonsecure port, depending on the security level that you define when you deploy agents.
v If you set the maximum security level, you must set the same level of security for all agents when you deploy them.
