Integration for Tivoli

Integrating HP asset information with Tivoli Inventory 56
Also, before attempting any configuration, ensure that Tivoli Policy Regions, Profile Managers, Profiles, and
associated resource rights have been created or assigned in the appropriate locale to match the Logical
Architecture standards of the environment.
The HP Inventory Collector (Collect.exe) 7.3.2 or later is also required. This utility works with HP Insight
Management Agents to gather in-depth asset information for HP ProLiant servers and is supplied with the HP
Insight Integration for Tivoli 5.1 in the hpq\Inventory directory.
The HP Inventory Collection utility gathers several hundred hardware asset attributes. The actual amount of
data gathered is dependent on the type of system being scanned and the number of configured options.
Initiate Inventory Collection task
The HP Insight Integration for Tivoli includes the task "Initiate Inventory Collection," which runs the HP
Inventory Collector (Collect.exe) to gather hardware asset data on selected subscribers and save the output
in an .MIF format suitable for import into the Tivoli Inventory database. The resultant .MIF file is saved in a
specified location on selected subscribers.
NOTE: Importing the collected HP data into the Tivoli Inventory Database is a separate process
to the Initiate Inventory Collection task and is described later in this chapter.
NOTE: The required SNMP services and HP Insight Management Agents must be installed and
configured on all HP systems designated to be managed with this task.
HP recommends using Insight Management Agents 5.50 or later.
The Initiate Inventory Collection task provided with the HP Insight Integration for Tivoli runs the
Collect.exe /f <path>\hp.mif /tpem executable and can be used with the variables listed in the
following table:
Command line variable Description
/f
Instructs the output to be saved as single file. Without this parameter, each MIB
collection is saved as a separate file.
Path
Specifies the location for the resultant .MIF file provided by the user.
hp.mif
Specifies the name of the resultant .MIF file.
/tpem
Defines the format of the output fields. This switch translates spaces in the attribute and
group names to underscores and removes several unnecessary statements in the .MIF
output file. This process makes the MIF file format suitable for importing into Microsoft®
SQL Server, Sybase, and Oracle® databases.
The resultant .MIF file contains hardware asset data and is saved locally on each target system as HP.MIF in
the path specified by the user. If no path is specified, the file is saved in \Tivoli\db\Host_name.db, where
Host_name refers to the name of the target system.
The output HP.MIF file is provided in a format that can be imported into Microsoft® SQL, Sybase, and
Oracle® database applications.