IBM Security Verify Governance Adapter for Sybase 10.0.1 - Release notes

IBM Security Verify Governance Adapter for Sybase 10.0.1 is available. Compatibility, installation, and other getting-started issues are addressed.

Copyright International Business Machines Corporation 2003, 2026. All rights reserved.
US Government Users Restricted Rights -- Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

Contents

Preface

Adapter Features and Purpose

License Agreement

Contents of this Release

Installation and Configuration Notes

Customizing or Extending Adapter Features

Supported Configurations

Notices

Preface

These Release Notes contain information for the following products that was not available when the IBM Security Verify Governance Server manuals were printed:

· Sybase Adapter Installation and Configuration Guide

Adapter Features and Purpose

The Sybase Adapter is designed to create and manage accounts on a Sybase Adaptive Server Enterprise (ASE). The adapter runs in "agentless" mode and communicates using JDBC to the systems being managed.

IBM recommends this adapter (and the prerequisite Tivoli Directory Integrator) be installed on each node of an IBM Security Verify Governance Server WebSphere cluster. A single copy of the adapter can handle multiple IBM Security Verify Governance Server services. The deployment configuration is based, in part, on the topology of your network domain, but the primary factor is the planned structure of your IBM Security Verify Governance Server Provisioning Policies and Approval Workflow process. Please refer the IBM Knowledge Centre for a discussion of these topics.

IBM Security Verify Governance Server adapters are powerful tools that require Administrator Level authority. Adapters operate much like a human system administrator, creating accounts, permissions and home directories. Operations requested from IBM Security Verify Governance Server will fail if the adapter is not given sufficient authority to perform the requested task. IBM recommends that this adapter run with administrative (root) permissions.

Service Groups Management

IBM Security Verify Governance Server has the ability to manage service groups. By service groups, IBM Security Verify Governance Server is referring to any logical entity that can group accounts together on the managed resource.

Managing service groups implies the following:

· Create service groups on the managed resource.

· Modify attribute of a service group.

· Delete a service group.

Note: Service group name change is not supported in IBM Security Verify Governance Server release.

The Sybase Adapter does not support management of service groups.

License Agreement

Review and agree to the terms of the IBM Security Verify Governance Adapter License prior to using this product.

The license can be viewed from the "license" folder included in the product package.

Contents of this Release

Adapter Version

Component	Version
Release Date	2026 March 26 04.48.40
Adapter Version	10.0.1
Component Versions	Adapter build: 10.0.1.1 Profile:  10.0.1.1 Dispatcher: 7.1.39 or higher (packaged separately)
Documentation	The following guides are available in the IBM Knowledge Centre · Sybase Adapter Installation and Configuration Guide

New Features

Internal#	RFE/IDEA#	Description
		Items included in current release (10.0.1)
SVGAD-5854	ADAPT-231	Certify the adapter for use with IBM Security Verify Directory Integrator version 10.0.0
SVGAD-5854	ADAPT-236	Certify the adapter for use with IBM Verify Identity Governance version 11.x
SVGAD-6111	ADAPT-249	Certify the adapter for use with IBM Verify Directory Integrator version 11.x
		Items included in 7.1.9 release
		None
		Items included in 7.1.8 release
RTC 171794 Bug 2504		US - As a Sybase adapter developer, I should allow customers to enable or disable database password encryption
		Items included in 7.0.7 release
RTC 151774		Add Support for Identity Governance and Intelligence (IGI) v5.2.2 This adapter is now designed for use with IBM Security Identity Manager, Privileged Identity Manager, and Identity Governance and Intelligence.
		Items included in 7.0.6 release
		Initial Release

Closed Issues

Internal#	APAR#/CASE#	PMR# / Description
		Items closed in current Release (10.0.1)
		None
		Items closed in 7.1.9 Release
RTC 181005		As a Sybase adapter developer, I should check that attributes in SybaseProfile file are mapped correctly.
		Items closed in 7.1.8 Release
		None
		Items closed in 7.0.7 Release
		None
		Items closed in 7.0.6 Release
		Initial Release

Known Limitations

Internal#	APAR#	PMR# / Description
		None

Installation and Configuration Notes

See the Sybase Adapter Installation Guide for detailed instructions.

Corrections to Installation Guide

The following corrections to the Installation Guide apply to this release:

Chapter 1: Overview

No updates for the current release

Chapter 2: Planning

Prerequisites:

Directory Integrator

Replace "IBM Security Verify Directory Integrator Version 7.1.1 + 7.1.1-TIV-TDI-FP0004 + 7.2.0-ISS-SDI-LA0008" in the description with "Please consult the release notes for the currently supported versions of the below products".

Remove " IBM Security Verify Directory Integrator Version 7.2"

Remove "The adapter supports IBM Security Directory Integrator 7.2, which is available only to customers who have the correct entitlement. Contact your IBM representative to find out whether you have the entitlement to download IBM Security Directory Integrator 7.2." from the note.

Identity Server IBM Security Verify Governance Servers

Remove existing description and update description as below:

The following servers are supported:

- IBM Verify Identity Governance

- IBM Security Verify Governance Identity Manager

- IBM Security Verify Governance

Sybase Adaptive Server Enterprise

Remove existing description and update with "Please consult the release notes for the currently supported versions of the below products".

Sybase JDBC Driver

Replace jconn4.jar with jconn*.jar and add description with "Please consult the release notes for the currently supported versions of the below products".

Chapter 3: Installing

Installing ILMT-Tags File
(Please add new section "Installing ILMT-Tags" File under the section Installing > Installing ILMT-Tags in install guide.)

Before you begin:

- The Dispatcher must be installed

Procedure:

Copy the files in the ILMT-Tags folder to the specified location:

1. Windows: < SDI-HOME > /swidtag

2. Unix/Linux: < SDI-HOME >/swidtag

Installing in the virtual appliance (Only for Identity Governance/ISVG)

For Sybase target management, you can install an IBM Security Verify Governance Adapters or a custom adapter on the built-in Security Directory Integrator in the virtual appliance instead of installing the adapter externally. As such, there is no need to manage a separate virtual machine or system.

About this task

This procedure is applicable to install this adapter on the virtual appliance.

Procedure

1.      Download the adapter package from the IBM Passport Advantage.

For example, Adapter-<Adaptername>.zip.

The adapter package includes the following files:

Table 1. Adapter package contents
Files	Description
bundledefinition.json	The adapter definition file. It specifies the content of the package, and the adapter installation and configuration properties that are required to install and update the adapter.
Adapter JAR profile	A Security Directory Integrator adapter always include a JAR profile which contains: ·        targetProfile.json ·        Service provider configuration ·        Resource type configuration ·        SCIM schema extensions ·        List of assembly lines ·        A set of assembly lines in XML files ·        A set of forms in XML files ·        Custom properties that include labels and messages for supported languages. Use the Target Administration module to import the target profile.
Additional adapter specific files	Examples of adapter specific files: ·        Connector jar files ·        Configuration files ·        Script files ·        Properties files The file names are specified in the adapter definition file along with the destination directory in the virtual appliance.

2.      From the top-level menu of the Appliance Dashboard, click Configure > SDI Management.

3.      Select the instance of the Security Directory Integrator for which you want to manage the adapters and click Manage > SDI Adapters

The SDI Adapters window is displayed with a table that list the name, version, and any comments about the installed adapters.

4.      On the SDI Adapters window, click Install.

5.      On the File Upload window, click Browse to locate the adapter package and then click OK.

For example, Adapter-<Adaptername>.zip.

6.      Provide the missing 3rd party libraries when prompted.

a.      On the File Upload for Pre-requisite files window, click Select Files.

A new File Upload window is displayed.

b.      Browse and select all the missing libraries. For example, httpclient-4.0.1.jar

c.      Click Open.

The selected files are listed in the File Upload for Pre-requisite files window.

d.      Click OK.

The missing files are uploaded, and the adapter package is updated with the 3rd party libraries.

7.      Enable secure communication.

a.      Select the instance of the Security Directory Integrator for which you want to manage the adapter.

b.      Click Edit.

c.      Click the Enable SSL check box.

d.      Click Save Configuration.

8.      Import the SSL certificate to the IBM® Security Directory Integrator server.

a.      Select the instance of the Security Directory Integrator for which you want to manage the adapter.

b.      Click Manage > Certificates.

c.      Click the Signer tab.

d.      Click Import.

The Import Certificate window is displayed.

e.      Browse for the certificate file.

f.       Specify a label for the certificate. It can be any name.

g.      Click Save.

Note: While uploading the Adapter package, you may receive System Error: A file included in the SDI Adapter zip already exists on the system and the Server Message log under Appliance tab of VA will have a reference to error com.ibm.identity.sdi.SDIManagementService E File ibm.com_IBM_Verify_Identity_Governance_xxxx.swidtag found in the adapter zip at location ILMT-Tags/ already exists in system. This is because, you can install the same swidtags only once. So, if another adapter of the same type is installed, remove the swidtags.

The ibm.com_IBM_Verify_Identity_Governance_Enterprise-xxxx.swidtag file is common to all adapters. In addition to the common swidtag file, an application adapter needs ibm.com_IBM_Verify_Identity_Governance_Application_Adapters-xxxx.swidtag file and an infra adapter needs ibm.com_IBM_Verify_Identity_Governance_Lifecycle-xxxx.swidtag and ibm.com_IBM_Verify_Identity_Governance_Compliance-xxxx.swidtag files. So, if an application adapter is already installed and this is an infra adapter, then only install the infra-specific swidtags and the other way around. Please visit Security Verify Governance Adapters v10.x link to identify the adapter type of the installed adapters.

Installing in an IBM Security Verify Directory Dispatcher Container

Before you begin

The steps to install adapter and related files into the container can be performed using the adapterUtil.sh script, which is shipped with the dispatcher package. This script should be staged on the machine running Kubernetes cli. The adapterUtil.sh script is also readily available in the bin directory of ISIM IBM Security Verify Governance Identity Manager Container Starter Kit installation directory (If ISVDI was selected for installation during the ISIM container installation steps).

If, for any reason, the adapter util script cannot be executed or used, the below manual instructions must be followed to copy the files to the persistent volume.

Note: The container must be restarted after installing or uninstalling the adapter and any changes to the configuration yaml. To activate changes and restart the container run the following commands:
- <path_to_starterkit>/bin/createConfigs.sh isvdi
- For OpenShift container: oc -n isvgim rollout restart deployment isvdi
- For Kubernetes container: kubectl -n isvgim rollout restart deployment isvdi

Note: This document only describes the adapterUtil.sh command options that are required to install this adapter. For other command options, such as listing installed connectors and 3rd party jars, please refer to the Dispatcher10 Installation and Configuration Guide.

Installing / Upgrading / Re-installing / Downgrading the adapter

Using Script

Use below command to install / upgrade/ re-install / downgrade the adapter:

/path/to/adapterUtil.sh -loadAdapter "/path/to/Adapter-Sybase-*.zip" accept

Where /path/to/adapterUtil.sh is the location where the adapterUtil.sh script is installed and /path/to/Adapter-Sybase-*.zip is the location where the Adapter zip file is staged on the machine running Kubernetes cli.

Manually copying files to Persistent Volume

Copy the files to the persistent volume mapped to the /opt/IBM/svgadapters directory of the container image as per the given directory structure:

ILMT-Tags

Copy below files to <Persistent_Volume>/swidtag directory:

- ibm.com_IBM_Verify_Identity_Governance_Enterprise-11.0.0.swidtag

- ibm.com_IBM_Verify_Identity_Governance_Lifecycle-11.0.0.swidtag

- ibm.com_IBM_Verify_Identity_Governance_Compliance-11.0.0.swidtag 

Copying 3rd party libraries:

Using Script

Use below command to copy 3rd party jars:

/path/to/adapterUtil.sh -copyTo3rdpartyOthers "/path/to/jconn*.jar"

This command will copy the 3rd party jars to <Persistent_Volume>/jars/3rdparty/others directory.

Manually copying files to Persistent Volume

Copy below 3rd party jar files to <Persistent_Volume>/jars/3rdparty/others directory (Refer release notes for the supported jar versions):

- jconn*.jar

Enabling TLS 1.2

Refer https://www.ibm.com/docs/api/v1/content/SSCQGF_10.0.0/container/html/verify-directory-integrator.html#advanced page from SVDI.

If the config.yaml file which is used as the YAML_CONFIG_FILE environment variable for the container doesn't have an advanced configuration element, follow the instructions that are provided in https://www.ibm.com/docs/api/v1/content/SSCQGF_10.0.0/container/html/verify-directory-integrator.html#advanced to add an advanced configuration section to the config.yaml file.

To enable TLSv1.2, add 2 attr and value (key pair as mentioned in the SVDI guide) as below:

- attr: com.ibm.di.SSLProtocols

  value: 'TLSv1.2'

- attr: com.ibm.di.SSLServerProtocols

  value: 'TLSv1.2'

Note: The container must be restarted after making these changes to the configuration yaml. To activate changes and restart the container run the following commands:

- <path_to_starterkit>/bin/createConfigs.sh isvdi

- For OpenShift container: oc -n isvgim rollout restart deployment isvdi

- For Kubernetes container: kubectl -n isvgim rollout restart deployment isvdi

Enabling debug logs and disabling json-logging

Refer https://www.ibm.com/docs/api/v1/content/SSCQGF_10.0.0/container/html/verify-directory-integrator.html#general_logging page from SVDI.
If the config.yaml file which is used as the YAML_CONFIG_FILE environment variable for the container doesn't have root-level and json-logging configuration elements, follow the instructions that are provided in https://www.ibm.com/docs/api/v1/content/SSCQGF_10.0.0/container/html/verify-directory-integrator.html#general_logging to the add root-level and json-logging configuration elements section to the config.yaml file.

To enable debug logs, set value for root-level to debug and to disable json logging, set value for json-logging element to false.

Note: The container must be restarted after making these changes to the configuration yaml. To activate changes and restart the container run the following commands:

- <path_to_starterkit>/bin/createConfigs.sh isvdi

- For OpenShift container: oc -n isvgim rollout restart deployment isvdi

- For Kubernetes container: kubectl -n isvgim rollout restart deployment isvdi

Uninstalling the adapter

Using Script

Use below command to remove the adapter:

/path/to/adapterUtil.sh -removeAdapter Adapter-Sybase

Manually copying files to Persistent Volume

Remove files from the given directory structure of the persistent volume mapped to /opt/IBM/svgadapters directory of the container image.

ILMT-Tags
Remove below files from <Persistent_Volume>/swidtag directory:

- ibm.com_IBM_Verify_Identity_Governance_Enterprise-11.0.0.swidtag

- ibm.com_IBM_Verify_Identity_Governance_Lifecycle-11.0.0.swidtag

- ibm.com_IBM_Verify_Identity_Governance_Compliance-11.0.0.swidtag

3rd party jars
Remove 3rd party jar files used by this adapter listed below from <Persistent_Volume>/jars/3rdparty/others directory:

- jconn*.jar

Attribute Mapping

Remove this chapter for Identity Manager.

Service Target/Form details

Service Information Tab

(Add below detail after Sybase Admin Password)

Enable Password Encryption:

This field is used to enable or disable the password encryption for a database. By default, the value is set to true i.e. it enables the password encryption.

Chapter 4: Upgrading

No updates for the current release

Chapter 5: Configuring

Enabling TLSv1.2 in Security Directory Integrator

Procedure:

1. Apply recommended fix packs and limited availability (LA) versions on the Security Directory Integrator. See Recommended fixes for IBM Security Directory Integrator (SDI).

2. After applying the appropriate updates, modify the solution.properties file by appending the following text to the bottom of the file:

#####################
# # Protocols to enforce SSL protocols in a SDI Server
# # Optional values for com.ibm.di.SSL* property (TLSv1, TLSv1.1, TLSv1.2). # # This can be a multi-valued comma separated property
# # Optional values for com.ibm.jsse2.overrideDefaultProtocol property (SSL_TLSv2, TLSv1,TLSv11,TLSv12).
# # This is a single value property.
#####################
com.ibm.di.SSLProtocols=TLSv1,TLSv1.1,TLSv1.2
com.ibm.di.SSLServerProtocols=TLSv1,TLSv1.1,TLSv1.2
com.ibm.jsse2.overrideDefaultProtocol=TLSv1
com.ibm.jsse2.overrideDefaultTLS=true
#####################

Chapter 6: Uninstalling

No updates for the current release

Chapter 7: Troubleshooting

Enabling DEBUG Logs on SDI Server

Procedure:

1. Stop the SDI Server process

Pre-7.2.0-ISS-SDI-FP0008
2. Edit the <SDI_Solution_Directory>/etc/log4j.properties
3. Modify the following line:

log4j.rootCategory=INFO, Default

to

log4j.rootCategory=DEBUG, Default

Post-7.2.0-ISS-SDI-FP0008
2. Edit the <SDI_HOME>/etc/log4j2.xml
3. Modify the following line:

 <Root level="info">

to

<Root level="debug">

Post-7.2.0-ISS-SDI-FP0011 (To enable TCB block in debug)
4. Append the line com.ibm.di.logging.close=false in the <SDI_HOME>/etc/global.properties file.

5. Start the SDI Server process
6. Re-create the problem and collect the <SDI_Solution_Dir>/logs/ibmdi.log

Logs are not getting printed in FP13 in Windows OS

Procedure:

1. Copy log4j2.xml file from <SDI_Home_Dir>/etc and add to the <SDI_Solution_Dir>/etc (which was missing there).

2. Configure ibmdiservice.props with below parameter:

jvmcmdoptions=-Dlog4j2.configurationFile=etc\log4j2.xml

3. Restart SDI Server process

Chapter 8: Reference

Adapter attributes and object classes

(Add below row in Table 1. Attributes, object identifiers, descriptions, and corresponding column/table name on the Sybase Adapter after "Sybase Adapter Admin Password".)

Enable Password Encryption

ersybenablepswdencrypt

Specifies whether the password encryption for a database should be enabled or not

String

Customizing or Extending Adapter Features

Customizing or Extending Adapter Features

The IBM Security Verify Governance Adapter s can be customized and/or extended. The type and method of this customization may vary from adapter to adapter.

Getting Started

Customizing and extending adapters requires a number of additional skills. The developer must be familiar with the following concepts and skills prior to beginning the modifications:

· IBM Security Verify Governance Adapter administration

· IBM Security Directory Integrator management

· IBM Security Directory Integrator assemblyline development

· LDAP schema management

· Working knowledge of Java scripting language

· Working knowledge of LDAP object classes and attributes

· Working knowledge of XML document structure

Note: If the customization requires a new IBM Security Directory Integrator connector, the developer must also be familiar with IBM Security Directory Integrator connector development and working knowledge of Java programming language.

Support for Customized Adapters

The integration to the IBM Security Verify Identity server "the adapter framework" is supported. However, IBM does not support the customizations, scripts, or other modifications. If you experience a problem with a customized adapter, IBM Support may require the problem to be demonstrated on the GA version of the adapter before a Support Case is opened.

Supported Configurations

Adapter Installation Platform:

Due to continuous Java security updates that may be applied to your IBM Security Verify servers, the following SDI releases are the officially supported versions:

· Security Directory Integrator 7.2 + FP14

· Security Verify Directory Integrator 10.0 FP5

· Verify Directory Integrator 11.0.0

Earlier versions of SDI that are still supported may function properly, however to resolve any communication errors, you must upgrade your SDI releases to the officially supported versions by the adapters. Please refer to the adapters installation and configuration guides for the latest update on IBM Security Directory Integrator versions and fix packs

3rd Party Client Libraries:

· jconn4.jar
https://mvnrepository.com/artifact/jdbc.sybase/jconn4/16.0

Managed Resource:

· Sybase Adaptive Server Enterprise (ASE) v15.7 with Sybase Open Client v15.7

· Sybase(SAP) Adaptive Server Enterprise (ASE) v16.0with Sybase(SAP) Open Client v16.0

Verify Governance:

· IBM Verify Identity Governance 11.x

· IBM Security Verify Governance Identity Manager 10.x

· IBM Security Verify Governance 10.x*

*Unless this document specifies a specific fix pack version of ISVG Identity Manager v10, we expect the adapter to work with ISIM 6 as well. However, it will only be debugged and fixed from the perspective of ISVG-IM v10

Notices

This information was developed for products and services offered in the U.S.A. IBM may not offer the products, services, or features discussed in this document in other countries. Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be used instead. However, it is the user's responsibility to evaluate and verify the operation of any non-IBM product, program, or service.

IBM may have patents or pending patent applications covering subject matter described in this document. The furnishing of this document does not give you any license to these patents. You can send license inquiries, in writing, to:

IBM Director of Licensing

IBM Corporation

North Castle Drive

Armonk, NY  10504-1785  U.S.A.

For license inquiries regarding double-byte (DBCS) information, contact the IBM Intellectual Property Department in your country or send inquiries, in writing, to:

Intellectual Property Licensing

Legal and Intellectual Property Law

IBM Japan, Ltd.

1623-14, Shimotsuruma, Yamato-shi

Kanagawa 242-8502 Japan

The following paragraph does not apply to the United Kingdom or any other country where such provisions are inconsistent with local law:

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 states 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.

Any references in this information to non-IBM Web sites are provided for convenience only and do not in any manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of the materials for this IBM product and use of those Web sites is at your own risk.

IBM may use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you.

Licensees of this program who wish to have information about it for the purpose of enabling: (i) the exchange of information between independently created programs and other programs (including this one) and (ii) the mutual use of the information which has been exchanged should contact:

IBM Corporation

2ZA4/101

11400 Burnet Road

Austin, TX 78758  U.S.A.

Such information may be available, subject to appropriate terms and conditions, including in some cases, payment of a fee.

The licensed program described in this information and all licensed material available for it are provided by IBM under terms of the IBM Customer Agreement, IBM International Program License Agreement, or any equivalent agreement between us.

Any performance data contained herein was determined in a controlled environment. Therefore, the results obtained in other operating environments may vary significantly. Some measurements may have been made on development-level systems and there is no guarantee that these measurements will be the same on generally available systems. Furthermore, some measurements may have been estimated through extrapolation. Actual results may vary. Users of this document should verify the applicable data for their specific environment.

Information concerning non-IBM products was obtained from the suppliers of those products, their published announcements or other publicly available sources. IBM has not tested those products and cannot confirm the accuracy of performance, compatibility or any other claims related to non-IBM products. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products.

This information contains examples of data and reports used in daily business operations. To illustrate them as completely as possible, the examples include the names of individuals, companies, brands, and products. All of these names are fictitious and any similarity to the names and addresses used by an actual business enterprise is entirely coincidental.

COPYRIGHT LICENSE:

This information contains sample application programs in source language, which illustrate programming techniques on various operating platforms. You may copy, modify, and distribute these sample programs in any form without payment to IBM, for the purposes of developing, using, marketing or distributing application programs conforming to the application programming interface for the operating platform for which the sample programs are written. These examples have not been thoroughly tested under all conditions. IBM, therefore, cannot guarantee or imply reliability, serviceability, or function of these programs. You may copy, modify, and distribute these sample programs in any form without payment to IBM for the purposes of developing, using, marketing, or distributing application programs conforming to IBM's application programming interfaces.

Each copy or any portion of these sample programs or any derivative work, must include a copyright notice as follows:

� (your company name) (year). Portions of this code are derived from IBM Corp. Sample Programs. � Copyright IBM Corp. _enter the year or years_. All rights reserved.

If you are viewing this information in softcopy form, the photographs and color illustrations might not be displayed.

Trademarks

IBM, the IBM logo, and ibm.com are trademarks or registered trademarks of International Business Machines Corp., registered in many jurisdictions worldwide. Other product and service names might be trademarks of IBM or other companies. A current list of IBM trademarks is available on the Web at "Copyright and trademark information" at www.ibm.com/legal/copytrade.shtml. 

Adobe, Acrobat, PostScript and all Adobe-based trademarks are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States, other countries, or both.

IT Infrastructure Library is a registered trademark of the Central Computer and Telecommunications Agency which is now part of the Office of Government Commerce.

Intel, Intel logo, Intel Inside, Intel Inside logo, Intel Centrino, Intel Centrino logo, Celeron, Intel Xeon, Intel SpeedStep, Itanium, and Pentium are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries.

Linux is a trademark of Linus Torvalds in the United States, other countries, or both.

Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both. ITIL is a registered trademark, and a registered community trademark of the Office of Government Commerce, and is registered in the U.S. Patent and Trademark Office.

UNIX is a registered trademark of The Open Group in the United States and other countries.

Java and all Java-based trademarks and logos are trademarks or registered trademarks of Oracle and/or its affiliates.

Cell Broadband Engine is a trademark of Sony Computer Entertainment, Inc. in the United States, other countries, or both and is used under license therefrom.

Linear Tape-Open, LTO, the LTO Logo, Ultrium, and the Ultrium logo are trademarks of HP, IBM Corp. and Quantum in the U.S. and other countries.

End of Release Notes