IBM Support

IBM® Tivoli® Composite Application Manager for Microsoft® Applications: 6.3.1.20

Release Notes


Abstract

This release contains new features and enhancements for Microsoft Applications agent.

Content

Download Description

You can download the IBM Tivoli Composite Application Manager (ITCAM) for Microsoft Applications Version 6.3.1.20 installer from IBM Passport Advantage website by selecting the below package name and Part Number.
  • IBM Tivoli Composite Application Manager for Microsoft Applications V6.3.1.20
  • Advance Component Software for Multiple Platforms
  • Part number: M06FKML
Language Pack Details:
  • IBM Tivoli Composite Application Manager for Microsoft Applications V6.3.1.20
  • Advance Microsoft Agents Language Support for Windows Platforms Multilingual
  • Part number: M06FLML
Note: This installer is for new installations and for upgrade of an existing agent environment to 6.3.1.20.
Component: IBM(R) Tivoli(R) Composite Application Manager for Microsoft (R) Applications: ITCAMMA Version 6.3.1 Fix Pack 20
Date: Sep 8, 2022

Contents

1.0 General description

This fix pack resolves the APARs and defects listed in the "Problems fixed" section.
This fix pack also includes few enhancements made in this release.

2.0 Architecture and prerequisites

For information about system requirements, refer to the IBM Software Product Compatibility Reports (SPCR) and search for the IBM Tivoli Composite Application Manager for Microsoft Applications product:
https://www.ibm.com/software/reports/compatibility/clarity/index.html
2.1 Prerequisites for this fix pack
---------------------------------------
The minimum required version of IBM Tivoli Monitoring is V6.3.0, Fix Pack 7 SP7.
The default version of IBM Tivoli Monitoring is V6.3.0, Fix Pack 7 SP7.

3.0 Problems fixed

The following problems are resolved in this fix pack.
3.1 APARs
-------------
Common
APAR- IJ41127
Abstract: The MS-Apps agents installer code needs to be updated with the latest one otherwise the agents go offline when secure main is enabled and the update Agent cmd is attempted.
Internet Information Services Agent
APAR- IJ39321
Abstract: KQ7ScriptCaller.exe using HIGH CPU for IIS agent environment.
3.2 Defects
--------------
Microsoft SQL Server Agent
Defect:190325
Abstract: Added Watchdog support on Windows platform for the MS SQL agent.
Microsoft Cluster Server Agent
DEFECT: 190252
Abstract: HyperV Virtual Machine’ workspace is not visible under Resources navigator item for the MS Cluster Agent.
Internet Information Services Agent
DEFECT: 190453
Abstract: Agent Should log if user doesn't have .NET Framework Version below 4.7.2.
Microsoft Exchange Server Agent
DEFECT: 190579
Abstract: OverSizeEmailCount.log file is not getting created under the agent logs folder.
DEFECT: 190608
Abstract: Message Tracking Collection Interval field is disabled on Exchange Server 2019.
3.3 Enhancements
----------------------
Microsoft SQL Server Agent
RFE: ITMAPM-I-53
Abstract: Added the Option to disable the fragmentation of tables present under selected databases.
Additional Information: Use COLL_FRAG_DISABLE_TBLD environment variable to disable the data collection of ‘Fragmentation’ and ‘Optimizer Statistics Age’ for selected databases.
Microsoft Exchange Server Agent
  • Added the following new workspace in Navigator Item 'Server’:
    • Certificate Details (Exchange Server 2013 Onwards)
  • Added the following new attribute group:
    • MS Exchange Certificate Details
  • Added Windows 2022 platform support.
  • Removed cluster properties input section displayed under “Exchange server Properties” tab from config panel.
  • Removed MS Exchange Server version 2003 and 2007 support from agent side.
Microsoft .NET Framework Agent
  • Upgraded .Net Framework to 4.7.2
  • Removed VS 2008 references from Agent side.
Microsoft .NET Data Collector
  • Upgraded .Net Framework to 4.7.2
  • Removed VS 2008 references from Agent side.
Internet Information Services Agent
  • Upgraded .Net Framework to 4.7.2
  • Removed VS 2008 references from Agent side.
General enhancements
  • Added support for IBM Tivoli Monitoring 6.3.0 Fix Pack 7 Service Pack 12.
3.4 Supersede fixes
-----------------------
6.3.1-TIV-ITM_MSAPP-FP0019
3.5 APARs and defects included from supersede fixes
--------------------------------------------------------------
3.5.1 APARs
---------------
Internet Information Services Agent
APAR- IJ35021
Abstract: KQ7ScriptCaller process is consuming high system resources.
Microsoft Exchange Server Agent
APAR-IJ35855
Abstract: Added edge role check before accessing active directory to fetch data.
3.5.2 Defects
---------------
Microsoft SQL Server Agent
DEFECT: 190062
Abstract: MSSQL ITM FP23: Process detail int overflow
Additional Information: SQL Server has various internal processes. When one of the process CPU time goes beyond 21474836 the data collection fails for process detail as SQL integer overflow happens.
DEFECT: 190069
Abstract: Potential buffer overflow in logging functions.
Additional Information: Fixed a potential buffer overflow issue in agent and collector logging functions.
Internet Information Services Agent
DEFECT: 190259
Abstract: High Memory and Virtual bytes consumption observed for KQ7ScriptCaller exe.
3.5.3 Enhancements
---------------
Microsoft SQL Server Agent

RFE: ITMAPM-I-30
Abstract: ITCAM MS SQL Server Agent should self-recover the Collector on SQL Server recycle
Additional Information: The ITM MS SQL Agent will be able to monitor SQL Server after it restarts. If SQL Server is down, the data collection process (koqcoll.exe) will wait for SQL Server to be up and then it will start monitoring it.
TASK: 190064
Abstract: Remove Long Live database connection option
Additional Information: Removed the long live database connection configuration option from agent. Now by default the agent will connect to SQL Server with long lived connection.
TASK: 190065
Abstract: Add custom query timeout for all attribute groups
Additional Information: Added CUSTOMIZED_QUERY_TIMEOUT environment variable, which can configure query timeout for attribute group level. For more information, please refer installation and configuration guide.
TASK: 190235
Abstract: Solved general memory access issues
Additional Information: Solved number of memory access issues.
TASK: 190057
Abstract: Added Windows Server 2022 Support.
Microsoft Exchange Server Agent
  • Added the following new workspace in Navigator Item 'Server’:
    • Message Tracking Logs (Exchange Server 2013 Onwards)
  • Added the following new view in "Message Tracking Logs (Exchange Server 2013 Onwards)" workspace:
    • Message Tracking Log Details
  • Added the following new attribute group:
    • MS Exchange Msgtrk Log Details
Active Directory Server Agent
  • Added the new workspace: “Failed Certificates” workspace in Navigator Item ‘ADCS’
  • Added the following view in " Failed Certificates Details " workspace
    • Failed Certificates Details Table view
  • Added new attribute groups: Failed Certificates
  • Added Windows Server 2022 Support
Microsoft .NET Framework Agent
Added Windows Server 2022 Support.

 
Microsoft .NET Data Collector
Added Windows Server 2022 Support.
 
Internet Information Services Agent
 Added Windows Server 2022 Support.
Microsoft SharePoint Server Agent
  • Added Windows 2022 platform support.
  • Added support for Microsoft SharePoint Server Subscription Edition.
  • Deprecated “Trace Log” attribute group for all SharePoint versions.
Microsoft Cluster Server Agent
Added Windows Server 2022 Support
Microsoft Hyper-V Server agent
Added Windows Server 2022 Support
General enhancements
Added support for IBM Tivoli Monitoring 6.3.0 Fix Pack 7 Service Pack 9
 

4.0 Installation instructions

To install this fix, see the following publications:
IBM Tivoli Monitoring Installation and Setup Guide
Installation and Configuration Guide of the respective agents. For more information, see ITCAM for Microsoft Applications Knowledge Center.

5.0 Additional installation information

5.1 Installation instructions for agents baroc file
--------------------------------------------------------
For information about installation and configuration of the baroc files, see the "Setting up event forwarding to Tivoli Enterprise Console" section from IBM Tivoli Monitoring Installation and Setup Guide.
5.2 Verifying the update
-------------
  1. To verify if the agent is updated correctly, use the tacmd command to view the current version of the agent after the agent is restarted. Ensure that you log on to the Tivoli Enterprise Monitoring Server before you view the agent version.

    For example,
    On UNIX systems, where $CANDLEHOME is the IBM Tivoli Monitoring installation directory, the default location is /opt/IBM/ITM.

    > $CANDLEHOME/bin/tacmd login -s <server>
                                  -u     <itmuser>
                                  -p     <password>  
    > $CANDLEHOME/bin/tacmd listSystems -t OQ

    On Windows systems, where %CANDLE_HOME% is the IBM Tivoli Monitoring installation directory, the default location is C:\IBM\ITM.

    > %CANDLE_HOME%\bin\tacmd login -s <server>
                                    -u     <itmuser>
                                    -p     <password>  
    > %CANDLE_HOME%\bin\tacmd listSystems -t OQ

    Note: The component (-t) for the tacmd listSystems command is specified as two characters (OQ), not three characters (KOQ).

    When the agent is updated, the agent version is changed to 06.31.20.00 except for the MS SQL agent (KOQ).

    For the MSSQL agent, the version is 06.31.24.00.

    For all other agents, the agent version is 06.31.20.00.

    After you restart the agent, you can also use the GUI to verify the agent updates.

  2. To verify whether the agent support files are updated correctly, use the kincinfo command on Windows systems or the cinfo command on Linux or UNIX systems.

    On UNIX or Linux systems:

    To validate if all components are installed, run the following command:
    $CANDLEHOME/bin/cinfo -i

    On Windows systems:

    To validate if all components are installed, run the following command:
    %CANDLE_HOME%\bin\kincinfo –i

6.0 Known problems and workarounds

Microsoft SQL Server Agent
 
Abstract: Remote Upgrade from v631FP23 to v631FP24 through tacmd commands shows incorrect status on CLI on WIN2K22.
Problem: Remote upgrade status got failed on CLI and the agent got updated from 06.31.23.00 to 06.31.24.00 agent. To upgrade agent, it is taking more than default time (600 seconds) So we need to set TIMEOUT Variable in ITM TEMS configuration file.
Workaround: Increase the Tivoli Enterprise Monitoring Server timeout value to 1200 seconds (TIMEOUT=7200). The default is 600 seconds.
On Windows ITM: installation_dir\CMS\KBBENV
On UNIX ITM: installation_dir/ config/host_name_ms_Tivoli_Enterprise_Monitoring_Server_ID.config.
Active Directory Server Agent

Abstract: Remote Upgrade from v631FP16 to v631FP17 through tacmd commands shows incorrect status.
Problem: Remote Upgrade from v631FP16 to v631FP17 through tacmd commands shows incorrect status in deployment status summary and agent remains in stopped state.
Workaround: Manually start the Active Directory Agent.
BizTalk Server Agent

Abstract: When you click the "Databases" and "Log and Space Information" cross-links in these views, the target workspaces of the SQL Server agent does not open automatically.
Problem: The Databases workspace of the BizTalk Server agent contains the “Databases Information” and "Log and Space Information" cross-links in the following views:
  • Management Database
  • MessageBox Database
  • Rule Engine Database
  • BAM Database
  • Tracking Database
  • Single Sign-On Database
Workaround: After you click the cross-links, when prompted, select the target instance manually.
Problem: List of attribute groups and workspace names that are no longer supported by BizTalk Server agent in ITCAMMA Version 6.3.1 Fix Pack 17.
  • Attribute Groups:
    • Human_Workflow_Services
    • SOAP_Receive_Adapter
    • SOAP_Send_Adapter
    • SQL_Receive_Adapter
    • SQL_Send_Adapter
    • Windows_SharePoint_Services
    • Windows_SharePoint_Services_Adapter
    • BizTalk_NET_Adapter_for_Oracle_DB
    • BizTalk_NET_Adapter_for_Oracle_EBusiness_Suite
    • BizTalk_NET_Adapter_for_SAP
    • BizTalk_NET_Adapter_for_Siebel
    • BizTalk_NET_Adapter_for_SQL
    • BAM_Interceptor
    • Distributors
    • Events
    • Subscriptions
    • Notifications
    • Delivery_Channels
    • Event_Providers
    • Generator
    • Vacuumer
    • Subscribers
    • RFID_Devices
    • RFID_Processes
  • Workspace:
    • Human Workflow Services
    • SOAP Receive Adapter
    • SOAP Send Adapter
    • SQL Receive Adapter
    • SQL Send Adapter
    • Windows SharePoint Services Adapter
    • BAM Interceptor
    • Distributors and Subscriptions
    • Events
    • Notifications
    • Delivery Channels and Event Providers
    • Generator
    • Vacuumer
    • Subscribers
    • Business Activity Monitoring
    • RFID
Workaround: None
Microsoft Host Integration Server Agent

Problem: List of attribute groups and workspace names that are no longer supported by HIS Server agent in ITCAMMA Version 6.3.1 Fix Pack 17.

  • Attribute Groups:
    • APPLICATION_INTEGRATION_HIP
    • APPLICATION_INTEGRATION_WIP
    • MANAGED_APPLICATION_INTEGRATION
    • MQBRIDGE_CHANNEL
    • MQBRIDGE_SERVICE
    • MQBRIDGE_CONNECTED_NETWORK
    • MQBRIDGE_MESSAGE_PIPE
  • Workspace:
    • HIP Method Execution Statistics
    • HIP Host Request Statistics
    • WIP Byte Transfer Statistics
    • WIP Host Response Statistics
    • WIP Method Call Statistics
    • Managed WIP Calls Request Response Stats
    • HIP Byte Transfer Statistics
    • Application Integration
    • HIP Work Flow Process Statistics
    • Channel and Message Pipe Configuration
    • Message Integration
Workaround: None
Microsoft Exchange Server Agent
Abstract: On the Tivoli Enterprise Portal, the status for the two situations is displayed as a "problem”.
Problem: The Tivoli Enterprise Portal shows the status as a problem due to the incorrect formula that is specified in the Manage Situations window for the following situations:
  • EX_Replication_Failed_Warn
  • EX_Replication_Suspended_Warn

Workaround: Modify the formula or create a custom situation with the correct formula. The correct formula is as follows: For the EX_Replication_Failed_Warn situation: Replication_Failed EQ Yes For the EX_Replication_Suspended_Warn situation: Replication_Suspended EQ Yes

Abstract: Duplicate workspace is displayed after agent upgrade from 631FP15 to 631FP16
Workaround : If agent is upgraded from 631FP15 to later release version, “Policy and Compliance” navigator item is displayed twice.
User can ignore the first navigator item in the list. You can follow the workaround steps as follows :
  1. Remove support of 631FP15 from TEPD and TEMS (uninstall support).
  2. Install support of higher version on ITM side, and point the upgraded agent to TEMS.
Microsoft .NET Framework Agent
Abstract: The backward compatibility may cause issue for monitoring asp.net 2.0, 3.0,3.5 applications when their app pool is set to .NET v2.0.
Problem: User may not be able to monitor lower versions of applications.
Workaround: User can try by setting app pool to .NET v4.5 instead of .NET v2.0 for .net framework 2.0 and 3.0 applications.
Microsoft .NET Data Collector
All the limitations that are mentioned in the "Problems and Workarounds" chapter of the .NET Data Collector Troubleshooting Guide V7.3.2 are still applicable. In addition to these problems and workarounds, the following problems and workarounds are applicable:
Abstract: When only .NET Framework 4.0 is installed on a server that runs on a 64-bit operating system, an error that is related to the ttapi.dll is generated.
Problem: If the ISAPI or HTTPModule components of the .NET Data Collector are enabled and the .NET Framework 4.0 is installed on a server that runs on a 64-bit operating system, error messages are generated while processing a web request.
  • If the ISAPI component is enabled, the following error message is displayed:
    "Service Unavailable"

  • If the ISAPI component is disabled and the HTTPModule component is enabled, the following error message is displayed:
    "Unable to load DLL ttapi.dll:
    •  This application fails to start because the application configuration is incorrect. Reinstalling the application may fix this problem. (Exception from HRESULT: 0x800736B1)" Workaround: Install the Microsoft Visual C++ 2005 Service Pack 1 Redistributable package (x64) on the computer where the .NET Data Collector is installed. You can download this package from the following website: https://www.microsoft.com/en-in/download/details.aspx?id=26347
    Abstract: When the WCF service is processed, the application name is displayed as w3wp and the component name is displayed as Microsoft .NET in the Transactions workspace of the Transaction Reporter agent on the Tivoli Enterprise Portal.
    Problem: This problem occurs when a WCF service is processed for which ASP.NET impersonation is not enabled.
    Workaround: Enable the ASP.NET impersonation for the service that is processed.
    Abstract: When a one-way web service is processed, an asynchronous arrow from the client is displayed in the Transaction topology from where this method was initiated. In the Transactions workspace, the application name of the web service is displayed as .asmx.
    Problem: One-way web services are called asynchronous and the user does not wait for a response from the server. As all the interception points of the SOAP component of the .NET data collector are not called, the asynchronous arrow is seen in the Transaction topology.
    Workaround: None
    Abstract: If a SOAP request is sent from a client computer where the .NET Data Collector is not installed to a server where the .NET Data Collector is installed, the web service node is displayed as .asmx or .svc in the Transaction topology.
    Problem: If all interception points for the SOAP component of the .Net Data Collector are not called, the web service nodes are displayed as .asmx or .svc. If the .NET Data Collector KD4 logging is enabled, the following message is seen in the logs: object reference not set to an instance of an object.
    Workaround: None
    Abstract: Visual Studio 2008 runtime environment should be installed before you upgrade the .NET Data Collector from V7.3.1 to V7.3.2 or V7.3.2, Fix Pack 1 or V7.3.2, Fix Pack 2.
    Problem: When you unregister the .NET Data Collector, the .dll files of the Microsoft Visual C++ 2008 redistributable package are required.
    Workaround: Install the Microsoft Visual C++ 2008 Service Pack 1 Redistributable Package. For a 32-bit operating system, download the Microsoft Visual C++ 2008 Service Pack 1 Redistributable Package (x86) from: https://www.microsoft.com/en-us/download/details.aspx?id=26368
    For a 64-bit operating system, download the Microsoft Visual C++ 2008 Service Pack 1 Redistributable Package (x64) from: https://www.microsoft.com/en-us/download/details.aspx?id=26368
    Abstract: When the database calls are made by using ODBC, the component name is shown as Microsoft .NET in the Transactions workspace of the Transaction Reporter agent.
    Problem: This problem occurs due to the aggregation of ODBC events.
    Workaround: Disable the ADO Event Aggregation by completing the following steps:
    1. Open the dotNetDcConfig.properties.inactive file.
    2. Change the value of the ktj_ADOAggregation.Enabled property to false, for example, ktj_ADOAggregation.Enabled=false.
    3. Open the command prompt and browse to the bin directory of the .NET Data Collector.
    4. Run the configdc activate config command.
    5. Restart all the .NET applications.
    Abstract: When database calls are made from a stand-alone client, ADO.NET nodes are not generated.
    Problem: This problem occurs when ADO Event Aggregation is enabled in the properties file. When a database call is made from a stand-alone client, the instance at which the user closes the application is not known to the .NET Data Collector because of which the ADO events are not aggregated.
    Workaround: Disable the ADO Event Aggregation by completing the following steps:
    1. Open the dotNetDcConfig.properties.inactive file.
    2. Change the value of the ktj_ADOAggregation.Enabled property to false, for example, ktj_ADOAggregation.Enabled=false.
    3. Open the command prompt and browse to the bin directory of the .NET Data Collector.
    4. Run the configdc activate config command.
    5. Restart all the .NET applications.
    Abstract: After remote or silent installation, the .NET Data Collector needs manual configuration by going to a particular installed instance.
    Problem: The .NET Data Collector is configured using its own utilities by using “configdc” or by UI tool “KK4ConfigProperties.exe” present at “\ k4\bin\PropertiesEditor”. In the ITM architecture, there is no way to provide inputs to these configuration utilities remotely unlike any other agent using tacmd or TEP GUI.
    Workaround: Currently, there is no workaround for this problem. The user needs to manually configure the .NET Data Collector using either “configdc” through command line or “KK4ConfigProperties.exe UI”.
    Abstract: Upgrade to .NET Data Collector Version 6.3.1 Fix Pack 17 from earlier version is not supported.
    Problem: KK4 agent upgrade from 631FP16 to 631FP17 is not supported.
    Workaround: To use the current 64-bit .NET Data Collector, install the .NET Data Collector Version 6.3.1 Fix Pack 17.
    Internet Information Services Agent
    Abstract: Unable to configure and start the agent through remote deploy command.
    Problem: Agent remained in unconfigured and stopped state when user tries remote deploy.
    Workaround: Configure and start the agent in Silent mode OR GUI Mode.
    Abstract: Agent is not finding KQ7_sda_6.3.1.2000.jar file and throwing file doesn't exist error.
    Problem: User can see ‘file doesn't exist error’ message in the log files.
    Workaround: None.
    Skype for Business Server Agent
    Abstract: Task Scheduler behavior at Daylight Saving Time transitions and other events.
    Problem: The behavior of the Microsoft Task Scheduler is not specified for tasks that are scheduled to run during the transition hours of the Daylight Saving Time. Other events can also affect the actual time at which a scheduled task runs.
    Workaround: None
    SharePoint Server Agent
    Abstract: TEP shows navigator item name Logs twice after agent upgrade from 631FP15 or 631FP16 to 631FP17.
    Workaround: - User can ignore the first navigator item in the list or perform the following steps:
    1. Remove the existing ITCAM for Microsoft Applications version 6.3.1 Fix Pack 16 or earlier version from TEPD and TEMS.
    2. Install ITCAM for Microsoft Applications version 6.3.1 Fix Pack 17 at ITM side.
    3. Point upgraded agent to TEMS.

    7.0 Additional product information

    Active Directory Server Agent
    1. To run the agent as a non-administrator user, provide the following permissions to the user:
      • Read access to the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet \Services\NTDS\Parameters directory
      • Read access to the C:\Windows\NTDS directory
      • Full access to the HKEY_LOCAL_MACHINE\SOFTWARE\Candle directory
    2. When you run the agent as a non-administrator user, the following attribute groups display the incorrect data:
      • Active Directory Database Information
      • Moved or Deleted Organizational Unit
      • Password Setting Objects
      • Containers
      • LDAP Attributes
    3. To run a Take Action command, run the Active Directory agent as an administrator user.
    Hyper-V Server Agent
    1. The following attribute groups are not supported on the Windows Server 2012 R2 operating system:
      • Hyper V Task Manager Detail
      • Hyper V Task Manager Recent Time
      • Hyper V VM Association with Virtual Network
      • Hyper V Legacy Network Adapter
    2. The HV_VMMigrate_Info situation is not supported on the Windows Server 2012 R2 operating system.
    3. The following attribute groups are not supported on the Windows Server 2016 operating system:
      • Hyper V Task Manager Detail
      • Hyper V Task Manager Recent Time
      • Hyper V VM Association with Virtual Network
      • Hyper V VM IO APIC
      • Hyper-V Virtual IDE Controller
    Microsoft Cluster Server Agent
     
    To get data of ‘NIC Team Members’ view , run the agent as a domain administrator and allow Internet access.
    Skype for Business Server Agent
     
    1. Partially supports archiving, monitoring, and CDR roles of the Lync Server for version 2013 and Skype for Business 2015 and 2019.
    2. The agent does not support remote monitoring of the SQL RTC buffer manager.
    3. To get data in the Lync Topology workspace, run the agent as a domain administrator, and change the agent startup from automatic to manual.
    4. For the configuration settings for the Synthetic Transaction, if a weekly scheduling frequency is set, then the scheduler runs every Monday at the time that is configured by the user. If a monthly scheduling frequency is set, then the scheduler runs on the first day of every month at the time that is configured by the user.
    5. The configuration panel does not validate any parameters. The user must follow the guidelines that are mentioned in every field and enter the data in the correct format.
    For additional documentation information, see the following websites:

    8.0 Copyright and trademark information

    A current list of IBM trademarks is available on the Web at "Copyright and trademark information" at www.ibm.com/legal/copytrade.shtml.

    9.0 Notices

    INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON- INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
    Some jurisdictions do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you. This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice.
    Microsoft, Windows, and Windows Server are trademarks of Microsoft Corporation in the United States, other countries, or both.
    Java and all Java-based trademarks and logos are trademarks or registered trademarks of Oracle and/or its affiliates.
    UNIX is a registered trademark of The Open Group in the United States and other countries.
    Linux is a registered trademark of Linus Torvalds in the United States, other countries, or both.
    Other company, product, or service names may be trademarks or service marks of others.
    Third-Party License Terms and Conditions, Notices and Information
    ----------------------------------------------------------------------------
    The license agreement for this product refers you to this file for details concerning terms and conditions applicable to third party software code included in this product, and for certain notices and other information IBM must provide to you under its license to certain software code. The relevant terms and conditions, notices, and other information are provided or referenced below. Please note that any non-English version of the licenses below is unofficial and is provided to you for your convenience only. The English version of the licenses below, provided as part of the English version of this file, is the official version.
    Notwithstanding the terms and conditions of any other agreement you may have with IBM or any of its related or affiliated entities (collectively "IBM"), the third-party software code identified below are "Excluded Components" and are subject to the following terms and conditions:
    -The Excluded Components are provided on an "AS IS" basis
    -IBM DISCLAIMS ANY AND ALL EXPRESS AND IMPLIED WARRANTIES AND CONDITIONS WITH RESPECT TO THE EXCLUDED COMPONENTS, INCLUDING, BUT NOT LIMITED TO, THE WARRANTY OF NON-INFRINGEMENT OR INTERFERENCE AND THE IMPLIED WARRANTIES AND CONDITIONS OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
    -IBM will not be liable to you or indemnify you for any claims related to the Excluded Components
    -IBM will not be liable for any direct, indirect, incidental, special, exemplary, punitive, or consequential damages with respect to the Excluded Components.

    [{"Type":"MASTER","Line of Business":{"code":"LOB45","label":"Automation"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSDKXQ","label":"Tivoli Composite Application Manager for Microsoft Applications"},"ARM Category":[{"code":"a8m50000000L1hcAAC","label":"ITCAM-for-Applications-\u003EITCAM-for-Microsoft-Applications"}],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"All Versions"}]

    Document Information

    Modified date:
    23 February 2023

    UID

    ibm16619093

    Page Feedback