Monthly TKU releases encompass content packaged as two separate product archives each containing a set of archives.

The archives are:

• Technology-Knowledge-Update-YYYY-MM-N-RELEASE.zip containing:
  • TKU-CORE-YYYY-MM-N-RELEASE.zip – Archive containing core software discovery patterns.
  • TKU-DBDETAILS-YYYY-MM-N-RELEASE.zip – Extended database patterns to recover detailed content information.

• Extended-Data-Pack-YYYY-MM-N-RELEASE.zip containing:
  • TKU-HRD-YYYY-MM-N-RELEASE.zip – Patterns to link Host nodes and Hardware Reference Data nodes.
  • TKU-HRD-YYYY-MM-N-RELEASE.csv – The Hardware Reference Data file.
  • TKU-SUPPORTDETAILS-YYYY-MM-N-RELEASE.zip – Patterns to link Host nodes and a Support Detail nodes when support (EOL) information is available for the OS or SI version.

From TKU and EDP August 2010 the naming is as follows:

• Technology-Knowledge-Update-YYYY-MM-N-RELEASE.zip contains:
  • TKU-Core-YYYY-MM-N-RELEASE.zip – Archive containing core software discovery patterns.
  • TKU-Deep-DB-Discovery-YYYY-MM-N-RELEASE.zip – Extended database patterns to recover detailed content information.

• Extended-Data-Pack-YYYY-MM-N-RELEASE.zip contains:
  • TKU-HW-Data-Mapping-YYYY-MM-N-RELEASE.zip – Patterns to link Host nodes and Hardware Reference Data nodes.
  • TKU-HW-Data-YYYY-MM-N-RELEASE.csv – The Hardware Reference Data file.
  • TKU-EOL-Data-YYYY-MM-N-RELEASE.zip – Patterns to link Host nodes and a Support Detail nodes when EOL (support) information is available for the OS or SI version.

The zip archives within the product archive contain subdirectories in which pattern files are stored. The subdirectories are named after the application categories covered by the patterns they contain. For example, the Sybase ASE pattern file, SybaseASE.tpl is contained in the Relational_Database_Management_Systems directory.

In each case RELEASE is the minimum Tideway Foundation or Atrium Discovery release the TKU release is compatible with.

Installing Archives

These instructions apply to the zip archives extracted from Technology-Knowledge-Update-YYYY-MM-N-RELEASE.zip and Extended-Data-Pack-YYYY-MM-N-RELEASE.zip. Uploading the Hardware Reference Data file is described in Importing Hardware Reference Data.

1. Copy the TKU archive to your local filesystem.
2. In the Tideway Foundation User Interface, from the Discovery tab, select Pattern Management.
3. Click the Upload New Package link. The Upload New Package window is displayed.
4. Enter the pattern filename into the Upload New Package dialog, or use the Browse... button to locate a file.
   • Either:
5. Click Upload to upload the file to the Appliance. It can be activated later to allow the use of patterns in a Discovery. To activate the patterns, click the Activate button, followed by clicking the Commit All Listed Changes button.
   • Or:
6. Click Upload and Activate to upload the file to the Appliance and activate it immediately.

Activation means that the pattern is loaded and from then will be used to identify software instances.

For more information on managing packages in Tideway Foundation, see the "Pattern Management" section in Chapter 6 of the Tideway Foundation Configuration Guide.

Upgrading a TKU

TKU updates contain all of the content of previous TKU updates in addition to the new pattern modules. The previous TKU content is therefore not required if installing the next upgrade.

These instructions apply to the zip archives extracted from Technology-Knowledge-Update-YYYY-MM-N-RELEASE.zip and Extended-Data-Pack-YYYY-MM-N-RELEASE.zip. Uploading the Hardware Reference Data file is described in Importing Hardware Reference Data.

1. Copy the TKU archive to your local filesystem.
2. In the Tideway Foundation User Interface, from the Discovery tab, select Pattern Management.
3. If you do not wish to delete the Software Instances created using previous TKU patterns, the default upload/activation procedure, described below, retains your existing software instances.
4. If you wish to delete the software Instances created using previous TKU patterns then select the previous TKU package and click the Delete button, followed by clicking the Commit All Listed Changes button.

1. Click the Upload New Package link. The Upload New Package window is displayed.
2. Enter the pattern filename into the Upload New Package dialog, or use the Browse... button to locate a file.
   • Either:
3. Click Upload to upload the file to the Appliance. It can be activated later to allow the use of patterns in a Discovery. To activate the patterns, click the Activate button, followed by clicking the Commit All Listed Changes button.
   • Or:
4. Click Upload and Activate to upload the file to the Appliance and activate it immediately.

Importing Hardware Reference Data

Hardware Reference Data provides the following vendor specification data: Rack Unit size, Power W, Power VA and Heat Output BTU. Import of Hardware Reference Data (HRD) into Tideway Foundation will enable customers to associate discovered systems with physical assets and report on both directly from Tideway Foundation.

Importing a Hardware Reference Data File

To import a Hardware Reference Data File:

1. From the Model section of the Administration tab, select HRD Import. The Import Hardware Reference Data page is displayed.
   
   The options on this page are described below:
   

   Field Name	Details
   File To Upload	The file to upload. Click the Browse... button to display a file browser window. Select the file to import and click Open. See File Format for details on the format of HRD files.
   Action	Do you want update, create or delete existing Hardware Reference Data? Create and Update will perform both actions as described below. Create will import records that do not already exist, but will not change any records already imported. Update is used ONLY when non-key fields in an existing record need to be updated. Key fields are vendor, model, and config_num_processors. Update will find all imported records that match existing data and update with the imported values. New records in the imported data will NOT be created. If you need to change a key field, you must first Delete the existing records and then Create the new records. Delete is used to delete records selectively. All records imported that match an existing record will cause that existing record to be removed. Existing records that do not appear in the import set will not be deleted. The HRD patterns automatically recreate the HRD nodes; you do not have to rescan the hosts. Choose "Create And Update", "Create", "Update" or "Delete" from the drop-down list.
   Logging Level	Choose the logging level from the drop-down list. This may be Debug, Info, Warning, Error, or Critical.

2. Click Apply to import the Hardware Reference Data File.

File Format

You can import csv files which must have a heading row specifying the Hardware Reference Data node attributes. For example:

vendor,model,known_model_names,config_num_processors,processor_type,max_ram,u_size,power_va,power_watts,btu_h,va_ru,watts_ru,btu_h_ru
Sun Microsystems,Sun Fire V440,"['Sun Fire V440','SUNW,Sun Fire V440']",4,UltraSPARC-IIIi,32768,4,908,636,2172,227,159,543
Sun Microsystems,Sun Fire 280R,['Sun Fire 280R'],2,UltraSPARC-III+,4096,4,454,318,1086,114,80,272