IBM®Tivoli® Federated Identity Manager, Fix Pack 6.1.0-TIV-TFIM-FP0001 README

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

NOTE: Before using this information and the product it supports, read the general information under Notices in this document.

  1. About the fix pack
    1. Patch contents and distribution
    2. Architectures
    3. Fix packs superseded by this fix pack
    4. Fix pack structure
  2. Upgrades made by this fix pack
    1. What's new
    2. Changes to Integrated Solutions Console
    3. Problems fixed by fix pack 6.1.0-TIV-TFIM-FP0001
  3. Before installing the fix pack
  4. Installing the update installer
  5. Installing the fix pack
  6. Deactivating the 6.1.0 console
  7. Deploying the fix pack runtime component
  8. Updating the security role to user mapping
  9. Updating the demonstration application
  10. Uninstalling the fix pack
  11. Uninstalling the update installer
  12. Documentation updates
    1. Use of the Tivoli Federated Identity Manager Configuration Tool tfimcfg.jar (IY94354)
  13. Software limitations
    1. Installing a 6.1.0 component
  14. Known problems and workarounds
  15. Notices
    1. Trademarks

About the fix pack

This fix pack corrects problems in IBM Tivoli Federated Identity Manager, Version 6.1.0, by upgrading its installed components to Tivoli Federated Identity Manager 6.1.1.1. It requires that IBM Tivoli Federated Identity Manager, Version 6.1.0, be installed. After installing this fix pack, your installation will be at level 6.1.1.1.

Patch contents and distribution

This fix pack package contains:

This fix pack is distributed as an electronic download from the IBM Support Web Site.

Architectures

This fix pack package supports the same operating system releases as the Tivoli Federated Identity Manager 6.1.0 release that are listed in the Release Notes.

Fix packs superseded by this fix pack

None.

Fix pack structure

Tivoli Federated Identity Manager consists of three components that can be installed separately:

All components must be at the same level. Therefore, if you install a fix pack for one of the components, you must install that fix pack for the rest of the components. Components at one release level are not guaranteed to interoperate with components at a different release or fix pack level.

Upgrades made by this fix pack

Changes made by this fix pack

This fix pack upgrades your Tivoli Federated Identity Manager, version 6.1.0, to Tivoli Federated Identity Manager, version 6.1.1 with fix pack 1 (6.1.1.1).

What's new

For details about what's new in version 6.1.1, see the What's new description.

Changes to Integrated Solutions Console

The Tivoli Federated Identity Manager 6.1.1 console component requires WebSphere Application Server 6.1. For this reason, the fix pack will automatically install the embedded version of WebSphere Application Server 6.1. However, the old console will not be removed or deactivated.

The embedded version will be installed with administrative security enabled and the administrator user information will be stored in a local WebSphere user registry.

The administrator user name will be fimadmin and, by default, the password will be ewasadmin.

For information about working with the new console, refer to the online help and the Tivoli Federated Identity Manager 6.1.1 information center.

Problems fixed by fix pack 6.1.0-TIV-TFIM-FP0001

The following problems in Tivoli Federated Identity Manager version 6.1.0 and 6.1.1 are corrected by this fix pack. For more information about the APARs listed here, refer to the Tivoli Federated Identity Manager support site.

Note: Some APARs listed here have two numbers. The first number is the APAR assigned to version 6.1.0. The second number is the APAR assigned to version 6.1.1.

APAR IY95589/IY90361
SYMPTOM: When using SAML 2.0 in a federation, an exception error can occur that prevents the SAML message from being built.

APAR IY95587/IY94088
SYMPTOM: Using the modify_partner.py staging utility to modify a SAML 2.0 federation partner properties fails with a string exception.

APAR IY94103
SYMPTOM: When using a SAML 2.0 federation, a user must first initiate federated single-sign on in the session before they can defederate the account.

APAR IY96453/IY97207
SYMPTOM: Using the modify_federation.py staging utility to modify SAML 2.0 federation properties fails with a string exception when a profile property is set to "Disabled".

Internal defect 74200
SYMPTOM: A memory leak might occur under a heavy load.

Internal defect 74203
SYMPTOM: In a custom map module, the setPrincipalName method does not update the STSUser instance correctly.

Internal defect 74215
SYMPTOM: The SAML 2.0 assertion in a SecurityToken is incorrect.

Internal defect 74217
SYMPTOM: Single sign-on fails when a SAML 1.x service provider has more than one identity provider partner configured.

Internal defect 74346
SYMPTOM: A VPD file cannot be created when using HP-UX 11i version 2.

Internal defect 74459
SYMPTOM: Thread issues occur during Liberty and SAML single sign-on actions.

Internal defect 74779
SYMPTOM: Using the WSSM wsdl2tfim tool with WebSphere Application Server 6.1.0.3 causes errors to occur.

Internal defect 74855
SYMPTOM: Sending SAML requests to the artifact service can cause an exception.

Internal defect 74909
SYMPTOM: Signature validation fails if the document contains two elements with the same ID.

Before installing the fix pack

Be aware of the following considerations before installing this fix pack:

Prerequisites

This fix pack requires that you have Tivoli Federated Identity Manager 6.1.0 and its prerequisites installed.

Update Installer

This fix pack requires the use of the Tivoli Federated Identity Manager Update Installer. You will need to install the Update Installer for your operating system on each computer where you will install the fix pack. Details about the Update Installer are described in Installing the update installer.

Fix Pack packaging

The fix pack package is provided in a zip file for each supported platform. The downloadable zip file contains:

Automatic creation of a backup directory

The Update Installer saves backup copies of the files that it replaces during the installation. You do not need to manually backup the Tivoli Federated Identity Manager files.

Installing the update installer

The installation of this fix pack requires the use of the Tivoli Federated Identity Manager Update Installer. You must install the Update Installer before you can install the fix pack.

  1. Locate the appropriate zip file for your operating system in the Download section of the Support page where the fix pack download is located.
  2. Download the file to each computer where you will install the fix pack.
  3. Unzip the file using the unzip utility for your operating system.
  4. The zip file contains:

  5. Open a command prompt.
  6. Change to the directory where you unzipped the file, and then:

    For HP-UX, Linux®, Solaris®, and AIX®, turn on the installer's execute bit by executing
    chmod a+x *.bin.

    For graphical installation mode, type the appropriate installation command for your operating system:

    For text-only installation mode, type the appropriate installation command for your operating system:

    For silent installation mode:

    1. Modify the response.rsp file in the directory where you unzipped the fix pack:

      Change the following variables, as needed:

      -P installLocation="/opt/IBM/FIMUI"
      The location where you want the Update Installer to be installed.

      -W FIMLocation.TFIMLocationPath="$D(install)/IBM/FIM"
      The location of Tivoli Federated Identity Manager.
      $D(install) is the default installation path (such as C:\Program Files for Windows®; /opt for HP-UX, Linux®, Solaris®, and AIX®).
      To specify a different path, replace $D(install)/IBM/FIM with the correct absolute path.

    2. Save and close the response.rsp file.
    3. Type the appropriate installation command for your operating system:

      • ./install_linux_ppc.bin -silent -options response.rsp
      • ./install_linux_x86.bin -silent -options response.rsp
      • ./install_linux_s390.bin -silent -options response.rsp
      • ./install_aix_ppc.bin -silent -options response.rsp
      • ./install_sol_sparc.bin -silent -options response.rsp
      • ./install_hpux_ia64.bin -silent -options response.rsp
      • ./install_win32.exe -silent -options response.rsp

  7. Follow the installation instructions as prompted. For example, you will be prompted to specify the directory where Tivoli Federated Identity Manager is installed if you are using the graphical or console installation methods.

    The progress of the installation is shown.

    Note: If you use the text-only installation mode, several exceptions might be displayed, such as:

    exception: java.lang.SecurityException: java.lang.Exception - protected system package 'java.lang'

    However, these messages are for informational purposes only and do not adversely affect the installation of the Update Installer.

    On each computer where you have a Tivoli Federated Identity Manager component installed, repeat these steps. Then, continue with the instructions in Installing the fix pack.

NOTE: Although it will not affect the installation of this fixpack, there is a defect in the TFIM Update Installer that could prevent installing any future fix packs for TFIM or TDI. Go to the TFIM Support page and search for a Technote entitled "TFIM Update Installer may fail for future fix packs" to see the corrective actions.

Installing the fix pack

NOTE: Before installing this fix pack, be sure that you have reviewed the prerequisites in Before installing the fix pack.

After you have downloaded the fix pack and installed the Update Installer, you need to perform a few steps before you can run the installation program.

  1. Unzipping the fix pack file

    1. Locate the directory where you unzipped the file that contains the Update Installer and the fix pack zip file.
    2. Use the unzip option of the zip program for your operating system to unzip the fix pack zip file.
    3. A different fixup is needed before installing the fix pack, depending on your platform.
      • If you are using AIX, HP-UX, Linux, or Solaris, the execute permission flag is turned off on all the scripts (all .sh files). Before invoking any of these scripts make sure you turn on the execute permisison for all the scripts by executing chmod +x *.sh in the /script directory.

      • If you are using Windows, TFIM 6.1.0 stored the runtime's Websphere path incorrectly. Before applying the fixpack this path needs to be manually corrected to point to the proper location of WAS.

        Using any text editor open the file
        <FIM INSTALL DIR>\pkg\software.properties.
        The default location of this file is
        C:\Program Files\IBM\FIM\pkg\software.properties.
        In that file look for a line that looks like
        com.tivoli.am.fim.was.home=C\:Program FilesIBMWebSphereAppServer.
        Change that line by adding escaped backslashes. For example
        com.tivoli.am.fim.was.home=C\:\\Program Files\\IBM\\WebSphere\\AppServer.

        Note that the colon is also escaped. After fixing that line you can proceed with the fixpack installation

  2. Preparing the variables file

    Before installing the fix pack, you must:

    1. Providing passwords
    2. The fix pack variables file contains the following passwords:

      TFIMRuntimeWASSecurityEnabled=
      Indicates whether WebSphere Application Server Security is enabled. Specify "true" if enabled or "false" if not.
      TFIMRuntimeWASAdmin=
      The WebSphere administrator user ID, such as wasadmin
      TFIMRuntimeWASPassword=
      The WebSphere administrator password.
      TFIMRuntimeWASTrustStorePath=
      The location of the trust keystore, such as
      /opt/IBM/WebSphere/AppServer1/profiles/AppSrv01/etc/DummyServerTrustFile.jks
      TFIMRuntimeTrustedJksPassword=
      The trust keystore password.
      TFIMRuntimeJksPassword=
      The Java keystore password.
      TFIMConsoleWASPassword=ewasadmin
      The password that will be used for the new console that is installed by this fix pack. The default password is ewasadmin. To change this default value, uncomment this variable by removing the # symbol and change ewasadmin to a new password. Note that the userid for the new console is always fimadmin.

      To provide the appropriate passwords:

      1. Locate the file called variables in the fix pack /script directory.
      2. Open the file in a text editor.
      3. Specify the passwords that are used on the system on which you are installing the fix pack. Take care not to add trailing blanks to the password field, otherwise they will be included as part of the password.
      4. Specify a password for the new console that will be installed by this fix pack, if desired. The default password is ewasadmin. To change this default, uncomment this variable by removing the # symbol and change ewasadmin to a new password. Take care not to add trailing blanks to the password field, otherwise they will be included as part of the password.
      5. Save the file and continue with the next step.

      ATTENTION: If you added passwords to the variables file, as described here, the passwords are in plain text in this file. Be sure to remove the passwords from this file to prevent a security breach.

    3. Specifying the ports
    4. When installing the fix pack on a system where the console component is installed, ensure that the assigned ports for the installation of the embedded version of WebSphere Application Server will not conflict with the ports of any other running program on the system.

      The following ports are defined in the variables file:

      WC_defaulthost=9085
      WC_adminhost=9065
      WC_defaulthost_secure=9448
      WC_adminhost_secure=9048
      BOOTSTRAP_ADDRESS=2814
      SOAP_CONNECTOR_ADDRESS=8885
      SAS_SSL_SERVERAUTH_LISTENER_ADDRESS=9406
      CSIV2_SSL_SERVERAUTH_LISTENER_ADDRESS=9408
      CSIV2_SSL_MUTUALAUTH_LISTENER_ADDRESS=9407
      ORB_LISTENER_ADDRESS=9105
      DCS_UNICAST_ADDRESS=9358
      SIB_ENDPOINT_ADDRESS=7281
      SIB_ENDPOINT_SECURE_ADDRESS=7291
      SIB_MQ_ENDPOINT_ADDRESS=5563
      SIB_MQ_ENDPOINT_SECURE_ADDRESS=5583
      SIP_DEFAULTHOST=5065
      SIP_DEFAULTHOST_SECURE=5066

      To change these port settings:

      1. Locate the variables file in the fix pack /script directory.
      2. Open the file in a text editor, if you have not already done so.
      3. Change any port values that will cause a conflict.
      4. Uncomment each changed port by removing the # symbol.
      5. Save and close the file.

  3. Running the Update Installer

    1. Ensure that the WebSphere Application Server that hosts the Tivoli Federated Identity Manager runtime and management service component is running.
    2. Ensure that the service acsisrv is running, as follows:
      • For Windows:
        Check the Services console. If the IBM ADE service is not running, start it with the Start button.
      • For HP-UX, Linux, Solaris, or AIX:
        1. Open a command prompt.
        2. Type ps -ef|grep acsisrv
        3. If the service is running, you will see the process and an associated PID. Close the command prompt window.
          If the service is not running, type: /usr/ibm/common/acsi/bin/acsisrv.sh -start. Then ensure the service is running.
    3. Open a command prompt.
    4. Change to the /script subdirectory of the directory where you unzipped the fix pack zip file.
    5. Type the installation command:
      • install.bat on Windows systems
      • ./install.sh for AIX, Solaris, Linux, or HP-UX
    6. Press Enter.
    7. The progress of the installation is shown. When the installation has completed, repeat these steps on each computer where the fix pack must be installed. Then continue with Deploying the fix pack runtime component.

    ATTENTION: If you added passwords to the variables file, as described in Preparing the variables file, the passwords are in plain text in this file. Be sure to remove the passwords from this file to prevent a security breach.

Deactivating the 6.1.0 console

The Tivoli Federated Identity Manager 6.1.1 console component requires WebSphere Application Server 6.1. For this reason, the fix pack will automatically install the embedded version of WebSphere Application Server 6.1. However, the old console will not be removed or deactivated.

ATTENTION:

To deactivate the console, run the following command:

where
<ISC_install_dir> is the directory where the 6.1.0 console was installed.
<username> is the administrator user name for the console, such as iscadmin.
<password> is the administrator password for the console.

To reactivate the console, run the following command:

where
<ISC_install_dir> is the directory where the 6.1.0 console was installed.

Deploying the fix pack runtime component

After you have successfully installed the fix pack, you will need to redeploy the Tivoli Federated Identity Manager runtime.

This task is identical to the deployment task you completed after initial installation of the management service and runtime component. For example, in a WebSphere cluster environment you must ensure that the new runtime component is deployed to each WebSphere node.

See the Runtime node management chapter of the Tivoli Federated Identity Manager Configuration Guide. Complete the topic "Deploying the runtime as a WebSphere Application Server application."

NOTES

  1. Log in to the administration console.
  2. Select Domain Management -> Runtime Node Management.
  3. Make sure the new runtime (version 6.1.1.1) is displayed as available.
  4. Click Deploy Runtime.
  5. Restart WebSphere Application Server.
  6. Verify that the current deployed version is 6.1.1.1.
    1. In the administration console, go to the Runtime Node Management panel.
    2. Look in the Runtime Management section of the Runtime Nodes portlet in the right panel. Review the Runtime Information.
      For example:
             Runtime Information
      ----------------------------------------------
      Current deployed version 6.1.1.1 [070406a]

      Note: The number within the brackets [070406a] might be different from this example.

    3. Repeat this step for each node in a WebSphere cluster environment.

Updating the security role to user mapping

In Tivoli Federated Identity Manager 6.1.1, the Tivoli Federated Identity Manager Runtime application provides security roles for controlling access to the Trust Service for applications using the WSSM component.

If you are using the WSSM component, then after you have deployed the runtime, you need to update the 'security role to user/group mapping'.

See the Web Services Security Management Guide, Chapter 2, the Section titled "Trust Service authorization access" for details on using security roles to control access to the trust service.

Updating the demonstration application

To update the demonstration application (itfim-ivtapp), you will need to uninstall the 6.1.0 version and deploy the 6.1.1 version that was installed by the fix pack.

To uninstall the 6.1.0 version:

  1. Log in to the administration console.
  2. Locate the Enterprise Applications panel.
  3. Select the ITFIM-ivtapp application, and click the Stop button to stop the application.
  4. Click the Uninstall button to uninstall the application.

To deploy the 6.1.1 version, refer to the instructions in "Deploying the demonstration application onto an existing WebSphere server", which is a section in the Tivoli Federated Identity Manager 6.1.1 Single Sign-On Guide.

Uninstalling the fix pack

If you want to return your installation to the state it was in prior to installing the fix pack, you can uninstall the fix pack.

The uninstallation process removes the fix pack, including the embedded version of WebSphere Application Server, if that version was installed by the fix pack.

ATTENTION -- When you remove the management service and runtime component fix pack, you will lose any configuration (domains, federations, and so on) that you added after the fix pack was installed.

  1. Ensure that the WebSphere Application Server that hosts the Tivoli Federated Identity Manager runtime and management service component are running.
  2. Ensure that the WebSphere Application Server that hosts the Tivoli Federated Identity Manager console component is running.
  3. Ensure that the service acsisrv is running, as follows:
  4. Open a command prompt.
  5. Change to the directory where the fix pack was unzipped.
  6. If security was enabled and you removed the passwords from the variables file that was used when the fix pack was installed, edit the file and add the appropriate passwords. Then save and close the file.
  7. Change to the /script directory and the type the uninstall command:

    The uninstall process will remove the fix pack and revert to the previous versions of files that were changed by the fix pack.

  8. ATTENTION: If you uninstall the fixpack, then you will need to reactivate the 6.1.0 console. To reactivate the console, run the following command:
    On HP-UX, Solaris, Linux, or AIX:
    <ISC_install_dir>/PortalServer/bin/startISC.sh ISC_Portal
    On Windows:
    <ISC_install_dir>/PortalServer/bin/startISC.bat ISC_Portal
    where
    ISC_install_dir is the directory where the 6.1.0 console was installed.
  9. Verify successful uninstallation of the fix pack:
    1. Log in to the administration console.
    2. In the Welcome panel, verify that the version number is not 6.1.1.1 and corresponds to the software level on which you installed fix pack 1.

      For example, since you installed fix pack 1 onto a Tivoli Federated Identity Manager 6.1.1.0 system, after uninstalling fix pack 1 you would see the following:

      	Suite Name                           Version
      ----------------------------------------------------------
      Tivoli Federated Identity Manager 6.1.0.0 [060524a]
  10. Redeploy the runtime for each domain:
    1. Log in to the administration console.
    2. Select Domain Management -> Runtime Node Management.
    3. Click Deploy Runtime.
    4. Restart WebSphere Application Server.
      • When deploying into a standalone WAS server environment, restart the application server.
      • When deploying into a cluster environment, restart the WAS Deployment Manager and the nodes.
  11. Verify that the current deployed version is the version you had prior to installing the fix pack.
    1. In the administration console, go to the Runtime Node Management panel.
    2. Look in the Runtime Management section of the Runtime Nodes portlet in the right panel. Review the Runtime Information.
      For example:
             Runtime Information
      ----------------------------------------------
      Current deployed version 6.1.0.0 [060524a]
    3. Repeat this step for each node in a WebSphere cluster environment.

Uninstalling the update installer

ATTENTION: Uninstalling the Update Installer will not remove the fix pack. See Uninstalling the fix pack for those instructions. Also, because the Update Installer will be used for future maintenance of Tivoli Federated Identity Manager, uninstalling the Update Installer is NOT recommended.

  1. Open a command prompt.
  2. Change the directory to the /_uninst subdirectory where the Update Installer was installed.
  3. Type the uninstall command:

Documentation updates

The product documentation for Tivoli Federated Identity Manager, Version 6.1.1, can be found at this location .

Updates to the documentation follow:

Use of the Tivoli Federated Identity Manager Configuration Tool tfimcfg.jar (IY94354)

A white paper has been added to the Tivoli Identity Manager support site that explains the use of the tfimcfg.jar tool. The tfimcfg.jar tool is used to configure Tivoli Access Manager WebSEAL as a contact point for a federation. This white paper supplements the information in the Tivoli Federated Identity Manager Single Sign-On Guide.

To locate the white paper:

  1. Go to the Tivoli Federated Identity Manager support site.
  2. Under the Learn heading, click Whitepapers. The tfimcfg.jar white paper is listed. Click its link for more information and to get to the white paper PDF® file.

Software limitations

Installing a 6.1.0 component

If you install a Tivoli Federated Identity Manager 6.1.0 component to the system after the fix pack has been applied, you must reinstall the fix pack on that system, so that all components are at the same level.

To re-apply the fixpack:

  1. Run the registration script for the component that was added from the 6.1.0 installation media:
    1. Open a command prompt on the system where the component was installed.
    2. Change to the following directory where the Tivoli Federated Identity Manager Update Installer was installed:

      <TFIM UPDATE INSTALLER>/DE/test/

      where <TFIM UPDATE INSTALLER> is the directory where the update installer was installed.
  2. Run the appropriate script for the installed component. The scripts are:

    Console component:
    ./addconsolefeat.sh on AIX, Linux, Solaris, or HP-UX
    addconsolefeat.bat on Windows

    Runtime and Management Services component:
    ./addmgmtfeat.sh on AIX, Linux, Solaris, or HP-UX
    addmgmtfeat.bat on Windows

    WSSM component:
    ./addwssmfeat.sh on AIX, Linux, Solaris, or HP-UX
    addwssmfeat.bat on Windows

    Web Services Provisioning component:
    ./addwspfeat.sh on AIX, Linux, Solaris, or HP-UX
    addwspfeat.bat on Windows
  3. After running the script, the added component has been registered. Install the fix pack as described in Installing the fix pack and Deploying the fix pack runtime component.

Known problems and workarounds

None.

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:

IBM World Trade Asia Corporation
Licensing
2-31 Roppongi 3-chome, Minato-ku
Tokyo 106, 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 that has been exchanged, should contact:

IBM Corporation
2Z4A/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 document 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 measurement 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.

All statements regarding IBM's future direction or intent are subject to change or withdrawal without notice, and represent goals and objectives only.

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.

Trademarks

The following terms are trademarks or registered trademarks of International Business Machines Corporation in the United States, other countries, or both:

AIX
IBM
IBM logo
iSeries
pSeries
S/390
Tivoli
Tivoli logo
xSeries
zSeries

Adobe, Acrobat, Portable Document Format (PDF), and PostScript are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States, other countries, or both.

Java and all Java-based trademarks and logos are trademarks of Sun Microsystems, Inc. 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.

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

Other company, product, and service names may be trademarks or service marks of others.