![]() |
![]() |
[ Bottom of Page | Previous Page | Next Page | Contents ]
This section contains new and updated information for IBM Tivoli Configuration Manager User’s Guide for Inventory:
Signature data includes the name, size, and usually the quick checksum value of the file used to identify the software product.
with the following text:
Signature data includes the name and the size of the file used to identify the software product.
Signature data includes the name, size, and usually the Quick checksum value of the file used to identify the software product.
with the following text:
Signature data includes the name and the size of the file used to identify the software product.
Adds one or more signatures to the configuration repository, and modifies existing signatures. Each signature must have a unique file name and size. If the specified signature already exists, the information for the existing signature (for example, the description or version) is modified.
Specifies the name of a file that contains the data for one or more signatures. The signature data in the file must be in the following format:
<I>,name,size,description,version
The signature file supports also the XML file format.
Setting the CIT processes priority on Windows
On Windows platforms, you can specify locally on each endpoint the priority for the different CIT processes by editing the cit.properties file and adding for example the following priorities:
fscanner.changepriority=low swscanner.changepriority=low hwscanner.changepriority=low vpdscanner.changepriority=lowIf you want to add the priority settings directly to the CIT_win.spb package used to install CIT, perform the following steps:
wdubldsp.exeThe command extracts a software package (.sp file) and the CIT files.
fscanner.changepriority=low swscanner.changepriority=low hwscanner.changepriority=low vpdscanner.changepriority=lowSave the file.
wdbldspb.exeThe new CIT_win.spb now includes the new cit.properties file with the priority settings you set.
ORA-00918: column ambiguously definedYou can run the command only with Tivoli queries where only one table and view have the TME_OBJECT_ID field.
This section contains new and updated information for IBM Tivoli Configuration Manager Database Schema Reference:
ACCESSED_TIME
Column name | Description |
ACCESSED_TIME | The GMT time when the signature file was last accessed. |
ACCESSED_TIME
By default, the h_database_schema.sql scripts create a table to correspond to every inventory table in the inv_database_schema.sql script that contains the attribute COMPUTER_SYS_ID. If there are tables for which you do not want to keep history tables, perform the following steps:
You can find the SQL statements for performing these operations in the h_inv_*_schema_423_FP09.sql script file.
Column Name | Description |
---|---|
MANUFACTURER | Processor manufacturer. Examples: Intel, AMD, IBM, SUN, HP. If the manufacturer is not recognized (is not in the list of families supported by Common Inventory Technology) then this field has value of "Unknown". |
FAMILY | Processor family. Examples: Pentium 4, Xeon, Athlon 64, POWER5, UltraSparc-T1, PA-RISC. If the family is not recognized (not in the list of families supported by Common Inventory Technology) then this field has value of "Unknown". |
TYPE | Processor type. Examples: 170 for AMD Opteron 150, 670 for Intel Pentium 4 670. If Common Inventory Technology does not support type identification for the family of processors then this field has value of an empty string. If Common Inventory Technology supports type identification for the family of processors but the type of processor is not recognized then this field has value of "Unknown". |
CPU_FREQ | Processor frequency in MHz. This field is optional and vendor-specific. Depending on the processor family it might be nominal or current CPU frequency. CPU frequency might be interpreted differently across processor architectures and families. If not valid this field is 0. |
L2_CACHE_SIZE | Size of L2 cache in Kilobytes. This field is optional, 0 if not valid. |
L3_CACHE_SIZE | Size of L3 cache in Kilobytes. This field is optional, 0 if not valid or there is no L3 cache. |
SIGNATURE | Processor signature. This field is optional and platform- and vendor-specific. The value of this field might be taken from different sources on each platform and even for different processor families. If available this is processor model identifier as reported by CPUID instruction, BIOS or OS. This field is for internal Common Inventory Technology purposes only, the exploiter should make no assumption on contents nor format of this field. |
If the printer is a local printer or a network printer, and is the default printer or not. This column can have one of the following values:
This section contains new and updated information for IBM Tivoli Configuration Manager Patch Management Guide:
http://download.windowsupdate.com/v6/windowsupdate/redist/standalone/WindowsUpdateAgent20-x86.exe
Before starting the Tivoli Configuration Manager Automation Server installation, checks the correctness of the directories for the configuration files and that Windows Instrumentation Service is not running to prevent the failure of the MQ Series component .
with the following text:
Before starting the Tivoli Configuration Manager Automation Server installation, checks the correctness of the directories for the configuration files.
The new output of the mount -m command will be:
mount -f -s -b "C:/cygwin/bin" "/usr/bin" mount -f -s -b "C:/cygwin/lib" "/usr/lib" mount -f -s -b "C:/cygwin" "/"
This section contains new and updated information for IBM Tivoli Configuration Manager Reference Manual for Software Distribution:
The sections where these stanzas are described show the structure in which you should define each stanza and provide examples.
add the following paragraph:
At installation time, the installation of a software package starts only if, during the check of the conditions specified in all software package stanzas, all these conditions are verified.
add the following note:
Note: If you set this attribute to y when creating on UNIX platforms software packages, to which a directory is added containing backward slashes, performing the winstsp command on the software package fails. To successfully install the software package on UNIX platforms, do not add to the package a directory containing backward slashes.
[ Top of Page | Previous Page | Next Page | Contents ]