![]() |
![]() |
[ Bottom of Page | Previous Page | Next Page | Contents ]
This section contains new and updated information for IBM(R) Tivoli(R) Configuration User's Guide for Inventory:
APAR IY88685
Add a new chapter called "Installing and uninstalling Common Inventory Technology (CIT)". The new chapter contains the following text:
Tivoli Configuration Manager 4.2.3 Fix pack 3 requires Common Inventory Technology (CIT) Version 2.3. When a Tivoli Configuration Manager activity is started on a workstation, Tivoli Configuration Manager checks if Common Inventory Technology (CIT) is already installed and installs it, if it is not found. CIT is installed using default paths, so during the installation the following directories are created:
If you update from IBM Tivoli Configuration Manager, Version 4.2.3 Fix Pack 1 to IBM Tivoli Configuration Manager, Version 4.2.3 Fix Pack 3, the data created with CIT 1.1.1 is removed. For example, files such as wscanner*, libInvHW.*, libInvSW.* and libInvReg.* are removed from the lcf_root/inv/SCAN directory.
To enable the Inventory endpoint traces, run the wdistinv command using the inv_ep_debug option. Every time an Inventory scan is run on the endpoint, a log file called INVxxxxx.LOG (where xxxxx is the scan_id) is created under the inv/SCAN directory.
As an alternative to using default paths, you can install the CIT binary files in other directories by performing the following steps:
$BINDIR/../generic/inv/SCRIPTS/CIT_import.pl -uninstIf you have not previously installed CIT, move to step 2.
$BINDIR/../generic/inv/SCRIPTS/CIT_import.pl CD_ROM/CIT_SPBwhere
winstsp -f -DCIT_ExploiterID=ITCM -DCIT_DestinationDirectory=/mydir @CIT_Preinstall.CIT @Endpoint:ep1where:
winstsp -f @CIT.2.3.1012 @Endpoint:ep1where:
This procedure must be completed before performing any Inventory or Tivoli License Manager operation based on CIT, because also Tivoli License Manager can install CIT on the same workstation. By following this procedure you can customize the CIT product binary directory, but you cannot customize the cit.ini directory and the CIT log files directory.
You can uninstall CIT using the Software Distribution component of IBM Tivoli Configuration Manager. This operation requires uninstalling CIT for all its registered exploiters. Before uninstalling CIT, verify that it is no longer required by any of the exploiters listed in the cit.ini file.
You must uninstall CIT software packages in the following order.
To uninstall CIT using the Software Distribution component of IBM Tivoli Configuration Manager, perform the following steps:
wdrevsp -f @CIT.2.3.1012
lists the errors which might occur if you do not correctly manage the list of exploiters in the cit.ini file:
Return code | Error reason | Recovery action |
---|---|---|
11 | At least one exploiter is still registered in the cit.ini file. | Remove the exploiter ID as explained in step 2. |
12 | You have not specified the exploiter name. | Specify the exploiter name. |
13 | The exploiter you specified is unknown. | Check the exploiter name in the cit.ini file and specify it again. |
You can add, remove, and verify the automatic download of IBM Tivoli License Manager and CIT using the standard Framework bundle dependency set. To perform this operation, use the winvdeps command.
winvdeps -a depset
winvdeps -r depset
winvdeps -s depset
The winvdeps command specifies dependencies that a method needs to run. You can use the command to add, remove, and verify a dependency set.
The winvdeps command returns one of the following:
To accept add the CIT dependency set, enter the following command:
winvdeps -a CIT
None.
This section contains new and updated information for IBM Tivoli Configuration Database Schema Reference:
DEVICES_NOT_BOOTSTRAPPED_QUERY
Returns all the Nokia devices which have not yet been bootstrapped.
Runs against the table DEVICE.
The column in this query is as follows:
BOOTSTRAPPED
DEVICE
Stores the details of the pervasive devices. One entry exists for each device registered on the Web Gateway.
Populated by a device creation on the Tivoli server, by an auto-enrollment, or by a Provisioning job successfully run.
The columns in this table are as follows:
MO_TARM_LOCK_QUERY
Returns information on the MO_TARM object of the Nokia devices.
Runs against the view MO_TARM_LOCK_VIEW.
The column in this query is as follows:
MO_TARM_LOCK
Stores the device information about the lock status.
The columns in this table are as follows:
MO_TARM_LOCK_VIEW
Returns information on the MO_TARM object of the Nokia devices.
Based on the MO_TARM_LOCK table.
The columns of this view are as follows:
Add to the list of the table columns:
PHYSICAL_PROCESSOR
Displays the correct number of physical processors, logical processors assigned to each core, and the cores on the physical processor in the inventory tables, views, and queries.
The columns in this table are as follows:
Add the following column to the LPAR_SYSTEMS_VIEW:
Add the following columns to the LOGICAL_PARTITIONS_VIEW:
Based on the COMPUTER e PHYSICAL_PROCESSOR tables.
Add the following columns to the PROCESSOR_NUM_VIEW:
PHYSICAL_PROCESSOR_VIEW
Displays the correct number of physical processors, logical processors assigned to each core, and the cores on the physical processor in the inventory tables, views, and queries.
Based on the COMPUTER and PHYSICAL_PROCESSOR tables.
The columns in this view are as follows:
Add to the list of the query columns:
H_PHYSICAL_PROCESSOR_VIEW
H_PHYSICAL_PROCESSOR
This section provides information about commands that have been added or changed but for which new man pages are not available.
Software distribution
The changes to these commands are documented in the IBM Tivoli Configuration Manager: Reference Manual for Software Distribution.
Activity Planner
The changes to this command are documented in the IBM Tivoli Configuration Manager: User' Guide for Deployment Services.
[ Top of Page | Previous Page | Next Page | Contents ]