Page tree

Skip to end of metadata
Go to start of metadata


The Tideway Knowledge Update 2009-Oct-1 (TKU October 2009) is a deliverable for Tideway Foundation platform version 7.2 and later.

Release Compatibility

TKU 2009-Oct-1 has been tested and verified against Tideway Foundation version 7.2.x / 7.3.

Note

TKU October (TKU 2009-Oct-1) is not compatible with nor supported on versions of Tideway Foundation before v7.2

Download

Customers can access this TKU release from the Tideway Downloads site and then clicking Download Area->latesttku. If you're a customer or partner and don't already have a login to this site or have forgotten yours please contact support@tideway.com.

Contents of the Knowledge Update

The Tideway Knowledge Update comprises four main components:

  • Core - Patterns that model various software products
  • Database detail - Patterns that extend some of the core database patterns to obtain additional detailed information about certain databases
  • Product Lifecycle - Patterns that populate Foundation with information about End-of-Life, End-of-Support, and End-of-Extended-Support for versions of certain host Operating Systems as well as versions of certain software products
  • Hardware Reference Data - Patterns and data import CSV file that populate Foundation with power and heat consumption figures for various hosts.

To see some of the highlights of this release visit the October In The Spotlight Page

Installation and Upgrade

  • Foundation 7.2 - Installation and upgrade instructions are provided here
  • Foundation 7.3 - Installation and upgrade instructions are provided here

Note

Due to an issue with pattern module names, if you are upgrading directly from TKU-2009-Apr-1 to TKU-2009-Oct-1 without removing the TKU April, you will need to manually disable the EMC_Powerpath pattern module in TKU-SUPPORTDETAILS-2009-04-1

A matrix covering ALL commands executed and ALL files retrieved by the patterns is available to our customers from the Tideway Downloads site

TKU Core

New Software Instance Patterns

Note

Oracle VM pattern requires Foundation version 7.3 in order to execute

Vendor Product Category Platforms Instances Versioning Module
Autonomy DiSH Application Monitoring UNIX, Windows Y N

Autonomy.DiSH

Autonomy IDOL Content Management UNIX, Windows Y Y

Autonomy.IDOL

Flowerfire Sawmill Advanced Analytics Software UNIX, Windows Y Y

Flowerfire.Sawmill

IBM InfoSphere Replication Server Relational Database Management Systems UNIX, Windows Y Y

IBM.InfoSphereReplicationServer

IBM Rational AppScan Enterprise Edition Security and Vulnerability Management Software Windows Y Y

IBM.Rational.AppScanEnterpriseEdition

IBM Rational Policy Tester Security and Vulnerability Management Software Windows Y Y

IBM.Rational.AppScanEnterpriseEdition

IBM Tivoli Netcool/Webtop Identity and Access Management UNIX, Windows Y Y

IBM.Tivoli.NetcoolWebtop

IBM Tivoli System Automation for Integrated Operations Management System and Network Management Software Windows Y Y

IBM.TivoliSAfIOM

IBM Tivoli Directory Integrator Data Integration and Access Software UNIX, Windows Y Y

IBM.Tivoli.DirectoryIntegrator

IBM WebSphere Business Modeler Business Process Modeling Windows Y Y

IBM.WebSphere.BusinessModeler

Microsoft Office Communications Server Messaging Applications Windows Y Y

Microsoft.CommunicationsServer

Microsoft Speech Server Messaging Applications Windows Y Y

Microsoft.SpeechServer

Oracle VM Virtual Machine Software UNIX Y Y

Oracle.OracleVM

Parallels Virtuzzo Containers Virtual Machine Software UNIX Y Y

Parallels.VirtuozzoContainers

Enhanced Software Instance Patterns

Vendor Product Enhancement SI Key Change Pattern Module
IBM DB2 Database Server Active versioning approach improved on Windows. Modeling of the product improved on Windows Y

IBM.DB2.RDBMS

Microsoft IIS The IIS pattern now retrieves a list of applications being hosted on the server N

Microsoft.IIS

Microsoft IIS The IIS pattern now retrieves a list of applications being hosted on the server N

Microsoft.IIS

Symantec VERITAS NetBackup VERITAS NetBackup Server pattern enhanced to identify whether the Server is Master Server, Media Server, or SAN Media Server and set the SI type accordingly. Additionally, the Server pattern optionally (user configurable) retrieves information about NetBackup Clients with active agents and stores it on the SI for use by the NetBackup Client pattern. NetBackup Client pattern can optionally (user configurable) on UNIX platforms, attempt to identify non standalone NetBackup clients. The pattern now also has improved versioning, as well as optionally recording the list of NetBackup Agents that are 'active' - i.e. that have been executed by the client in the last 30 days (actual time period is user configurable) Y

Symantec.VERITAS.NetBackup

Symantec VERITAS Cluster Server License information for all VERITAS Storage Foundation components is now stored as Detail nodes in our model. Y

Symantec.VERITAS.ClusterServer

Symantec VERITAS Storage Foundation File System License information for all VERITAS Storage Foundation components is now stored as Detail nodes in our model. Y

Symantec.VERITAS.Filesystem

Symantec VERITAS Storage Foundation License information for all VERITAS Storage Foundation components is now stored as Detail nodes in our model. Y

Symantec.VERITAS.StorageFoundation

Symantec VERITAS Storage Foundation for Windows License information for all VERITAS Storage Foundation components is now stored as Detail nodes in our model. Y

Symantec.VERITAS.StorageFoundationWindows

Symantec VERITAS Volume Manager License information for all VERITAS Storage Foundation components is now stored as Detail nodes in our model. Y

Symantec.VERITAS.VolumeManager

Symantec VERITAS Volume Replicator License information for all VERITAS Storage Foundation components is now stored as Detail nodes in our model. Y

Symantec.VERITAS.VolumeReplicator

Xen Source Xen Domain Virtualization Software Pattern enhance to ensure that it does not incorrectly label Oracle VM as Xen Source Xen N

XenVM

Bugs Fixed

The following bugs have been fixed in Tideway Knowledge Update 2009-Oct-1

Case No Defect No Details Pattern Module
N/A 12465 Sun xVM Virtual Box Virtual Machine pattern could not detect headless virtual machines. Pattern enhanced to detect these. In addition to that, the way the SI key is created has been improved

Sun.xVM.VirtualBox

N/A 12514 Fixed an error in the implementation the versioning table of Microsoft Operations Manager pattern which could cause an ECA Engine error if version not matched within the table.

Microsoft.OperationsManager

N/A 12519 The code in Symantec ESM pattern that is setting the product_version attribute has been enhanced to try and set it to major.minor whenever possible

Security.Management.ESM

N/A 12528 Problem: Certain patterns that use WMI do not escape correctly the namespace path. Typically, the path is left as 'root\CIMV2' but it should either be preceded by the 'raw' modifier or entered as 'root\\CIMV2'. Foundation Discovery however uses the default namespace (root\CIMV2) when it encounters a namespace it does not recognize, hence the patterns did not show any obvious issues. Solution: WMI namespace string modified to ensure that it is passed to Foundation Discovery in the correct format

Microsoft.CommerceServer

N/A 12528 Problem: Certain patterns that use WMI do not escape correctly the namespace path. Typically, the path is left as 'root\CIMV2' but it should either be preceded by the 'raw' modifier or entered as 'root\\CIMV2'. Foundation Discovery however uses the default namespace (root\CIMV2) when it encounters a namespace it does not recognize, hence the patterns did not show any obvious issues. Solution: WMI namespace string modified to ensure that it is passed to Foundation Discovery in the correct format

Microsoft.IdentityLifecycleManager

N/A 12528 Problem: Certain patterns that use WMI do not escape correctly the namespace path. Typically, the path is left as 'root\CIMV2' but it should either be preceded by the 'raw' modifier or entered as 'root\\CIMV2'. Foundation Discovery however uses the default namespace (root\CIMV2) when it encounters a namespace it does not recognize, hence the patterns did not show any obvious issues. Solution: WMI namespace string modified to ensure that it is passed to Foundation Discovery in the correct format

Microsoft.OfficeCommunicator

N/A 12528 Problem: Certain patterns that use WMI do not escape correctly the namespace path. Typically, the path is left as 'root\CIMV2' but it should either be preceded by the 'raw' modifier or entered as 'root\\CIMV2'. Foundation Discovery however uses the default namespace (root\CIMV2) when it encounters a namespace it does not recognize, hence the patterns did not show any obvious issues. Solution: WMI namespace string modified to ensure that it is passed to Foundation Discovery in the correct format

Microsoft.OfficeGroove

N/A 12528 Problem: Certain patterns that use WMI do not escape correctly the namespace path. Typically, the path is left as 'root\CIMV2' but it should either be preceded by the 'raw' modifier or entered as 'root\\CIMV2'. Foundation Discovery however uses the default namespace (root\CIMV2) when it encounters a namespace it does not recognize, hence the patterns did not show any obvious issues. Solution: WMI namespace string modified to ensure that it is passed to Foundation Discovery in the correct format

Microsoft.SystemCenterVirtualMachineManager

N/A 12528 Problem: Certain patterns that use WMI do not escape correctly the namespace path. Typically, the path is left as 'root\CIMV2' but it should either be preceded by the 'raw' modifier or entered as 'root\\CIMV2'. Foundation Discovery however uses the default namespace (root\CIMV2) when it encounters a namespace it does not recognize, hence the patterns did not show any obvious issues. Solution: WMI namespace string modified to ensure that it is passed to Foundation Discovery in the correct format

Microsoft.SystemCenterDataProtectionManager

22540 12566 Problem: SAP Suite pattern could fail with an ECA Engine error in cases where an installation of SAP is not using databases we can interrogate as part of the SAP installation. This was caused by an incorrectly implemented database name mapping table Solution: Pattern fixed - database naming table updated and additional error checking inserted

SAP.SAPR3

22624 12567 Problem: Microsoft System Center Virtual Machine Manager Agent does not populate product_version SI attribute if the pattern comes accross an internal product version that does not exist in the version mapping table Solution: Version mapping table updated. Furthermore, pattern will fall back to setting the product version to the same value as internal version if this internal version cannot be mapped to a known product version

Microsoft.SystemCenterVirtualMachineManager

22631 12572 An error in the implementation of package versioning in Microsoft System Center Data Protection Manager Agent pattern could in certain cases cause the pattern to exit with an ECA Engine error. The code has now been fixed.

Microsoft.SystemCenterDataProtectionManager

Product Lifecycle Patterns

You can use Tideway Foundation and OS / Software product lifecycle data to:

  • Identify operating systems and software that are exposed to security / stability risks as they are no longer supported by patch updates
  • Identify operating systems and software that you may may be paying a premium maintenance subscription for
  • Identify operating systems and software that are no longer shipping so may increase costs and risks associated with variance

Operating System Product Lifecycle Patterns

TKU 2009-Oct-1 includes product life cycle patterns providing End Of Life, End Of Support and End Of Extended Support dates for:

  • 11 publishers
  • 17 operating systems
  • 177 operating system versions

Go to the OS Product Life Cycle Patterns - TKU 2009-Nov-1 page for a full list of products included in this release.

Software Product Lifecycle Patterns

This TKU includes product life cycle patterns providing End Of Life, End Of Support and End Of Extended Support dates for:

  • 33 publishers
  • 226 software products
  • 1,271 software product versions

Go to the Software Product Life Cycle Patterns - TKU 2009-Oct-1 page for a full list of products included in this release.

Hardware Reference Data

You can use Tideway Foundation hardware reference data to:

  • Identify servers that can be expanded in situations where space is a constraining factor in the data center
  • Identify server refresh / rationalization candidates in situations where cooling is a constraining factor in the data center
  • Identify server refresh / rationalization candidates in situations where power is a constraining factor in the data center

This TKU includes hardware reference data providing Rack Size, Power Consumption, Heat Output and Maximum Memory capacity for:

  • 9 manufacturers
  • 401 server models
  • 1,166 server model configurations

Go to the Hardware Reference Data - TKU 2009-Oct-1 page for a full list of products included in this release.

  • No labels