IBM FileNet Application Engine 4.0.2.13-P8AE-FP013 Fix Pack Readme
© Copyright IBM Corporation 2012. All Rights Reserved.

About this fix pack

Accessing IBM FileNet documentation, compatibility matrices, and fix packs

Compatibility

Known Issues

New in this fix pack

Other notes

Installation, migration, upgrade, and configuration

Requirements

Install this fix pack

Uninstall this fix pack

Product fix history

Contact customer support

Notices

Trademarks

About this Fix Pack

This document provides information about the IBM® FileNet® Application Engine 4.0.2.13-P8AE-FP013 fix pack. The fix pack contains an updated security certificate used to sign FileNet Application Engine .jar and client installer files.

In addition to upgrading existing systems, this fix pack can be used for new installations as it contains a complete install package.

Accessing IBM FileNet documentation, compatibility matrices, and fix packs

Documentation and compatibility matrices

To access documentation and compatibility matrices for IBM FileNet products:

1. Navigate to the Product Documentation for FileNet P8 Platform support page (www.ibm.com/support/docview.wss?rs=3247&uid=swg27010422).
2. Select a PDF or a Doc Link, whichever is appropriate.

Fix packs

To access fix packs:

1. You can navigate directly to the Application Engine 4.0.2.13 fix packs or manually locate the fix packs by doing one of the following:
• Navigate to the Fix Central page for the Application Engine 4.0.2.x fix packs.
• Manually locate the fix packs by specifying the product group, product, installed version, and platform with the following options:
  • Product Group: Information Management
  • Product: FileNet Application Engine
  • Installed Version: 4.0.2.*
  • Platform: All

  Click Continue and identify the fixes you want to locate or select Browse for fixes.

2. View the list of available fix packs.

Compatibility

• As of 4.0.2.5-P8AE-FP005, Turkish language translation is available.
• As of 4.0.2.4-P8AE-FP004, an updated security certificate used to sign FileNet Application Engine .jar and client installer files is included with the installation. The previous certificate signature expires October 30, 2009 and the files need to be resigned. The resigned .jar files provided by the fix pack will be valid from the time of installation until March 16, 2012. It is also required that you update any Process Engine .jar files using the Process Engine interim fix or fix pack that matches the Process Engine version installed on your system.
• The following features are available after you install 4.0.2.3-P8AE-FP003:
  • Two new site preferences, "Show step name column" and "Maximum number of rows to return" located under the "My Active Workflows" section of General Site Preferences. These preferences allow the administrator to tune the My Active Workflows page in order to improve performance for environments where users have a large set of active workflow items.
  • An enhancement to the step name column on the My Active Workflows page which will indicate a workflow in multiple steps by appending ellipses (...) to the listed step name.
  • The Get Info icon is now enabled on the My Active Workflows page items. This allows users to open the Information Page to see the full list of step names when a workflow has multiple in process steps in addition to the standard info page functionality.
  • If the step name is in a protected state, the step name will display as [Unavailable]. If the user is a defined tracker, that user can open the Tracker from the Information Page view to get the workflow details.
• As of 4.0.2.1-P8AE-FP001, a translated user interface for Hungarian is available.
• As of P8AE-4.0.1-005, Firefox 3 is supported.
• As of P8AE-4.0.1-004, Windows XP Service Pack 3 is supported.
• As of P8AE-4.0.1-004, Windows Vista 64 bit is supported.
• As of P8AE-4.0.1-004, Federal Desktop Core Configuration (FDCC) support on Windows Vista is supported.
• As of P8AE-4.0.1-003, Windows Vista Service Pack 1 is supported.
• As of P8AE-4.0.1-003, Federal Desktop Core Configuration (FDCC) on Windows XP is supported.
• As of P8AE-4.0.1-002, MS Office 2007 Service Pack 1 is supported.
• As of P8AE-4.0.1-002, Java™ SE Runtime Environment 6 (1.6.x) for client machines is supported.
• As of P8AE-4.0.1-002, enhanced annotation tool tips to display the Creator and Date Created is available.
• As of P8AE-4.0.1-002, eForms jar files are placed in the WEB-INF/lib folder. This causes a runtime dependency on the Application Engine, where previously there was a compile-time dependency with Application Engine. This change was made to support Lotus Forms.

For compatibility information, see the:

• IBM FileNet P8 Hardware and Software Requirements Guide
• IBM FileNet P8 Fix Pack Dependency/Compatibility Matrix

Known Issues

• When using JRE 1.6.0_17 or above in a trusted configuration as documented in http://www-01.ibm.com/support/docview.wss?uid=swg27023011,
  Process Simulation designer is unable to save a scenario. To resolve the issue, manually add application-utils to the appletParameters.properties file.

  #Trustedjars, default list
  trusted=pe, pe3pt,javaapi,wcm, application-utils

• If you are using Workplace with Firefox 3.6.3, you cannot open workflow attachments.
• Due to a known WebLogic 8.1 SP6 issue, Application Engine 4.0.2 fix pack users are unable to log into Workplace with WebDAV in a WebLogic 8.1 SP6 environment. This issue is resolved in WebLogic 9. To work around the issue with WebLogic 8.1 SP6, do the following:
1. Contact WebLogic support to download the CR287255_810sp6_v2.jar file.
2. Copy the CR287255_810sp6_v2.jar file to: /opt/bea/weblogic81/server/lib.
3. Edit startWebLogic.sh, find classpath, and add {WL_HOME}\server\lib\CR287255_810sp6_v2.jar.
4. Edit the config.xml file located in /opt/bea/user_projects/domains/p8domain/.
5. Find SecurityConfiguration, add EnforceValidBasicAuthCredentials="false" before Name="p8domain" (ecmdb00747807).
• A Content Engine search on Oracle 11gR2 using an inner join may fail when there is a LOB column in the select list and there is an ORDER BY clause.

The Define Step Map - Advanced Options page in the IBM FileNet P8 help documentation does not identify all options available for the Advanced Options page. The available options are as follows:

Field	Description
Page	ITX form pages that are available to display in the selected workflow.
Visibility	Display options for the pages at the steps listed in the workflow step of the selected workflow: Visible - The tab for this page is displayed in the form policy. Visible with no page tab - The page is accessbile but the page tab does not appear in the rendered form policy. Not Accessible - The page is not accessible in the rendered form policy.
Printable	Select this option to set the form pages as printable.
Start Page	Select the page you want to appear first when the policy is rendered.
Order Form Pages	Click Order Form Pages to access settings to change the order in which the form pages are displayed in the form policy.

NOTE The Order Form Pages option was added as part of this fix pack.

New in this fix pack

The IBM® FileNet® Application Engine 4.0.2.13-P8AE-FP013 fix pack contains an updated security certificate used to sign FileNet Application Engine .jar and client installer files included with the installation. The previous certificate signature expires March 16, 2012 and the files need to be re-signed. The re-signed .jar files provided by the fix pack will be valid from the time of installation until February 19, 2015. It is also required that you update any Process Engine .jar files using the Process Engine interim fix or fix pack that matches the Process Engine version installed on your system.

For more information about Application Engine new features, existing languages, and known issues, see the IBM FileNet P8 Release Notes.

Other Notes

The installer panels for Application Engine 4.0.2.13 show the Oracle WebLogic Application Server as BEA WebLogic.

The correct name in the panels should be Oracle WebLogic. However, this is a cosmetic issue only, and does not affect installation.

Installation, migration, upgrade, and configuration

This topic contains instructions for installing the Application Engine 4.0.2.13-P8AE-FP013 fix pack.

Support documentation

Before installing this fix pack, verify you have an installed copy of the latest IBM FileNet P8 Platform Documentation package. This documentation package contains additional information that you might need to perform the procedures mentioned in this readme, such as stopping services and applications.

Search is enabled in the help system only if you have installed it as a web site on a web server that supports Java™ applications.

Requirements

Caution Do not install this Application Engine 4.0.2.13-P8AE-FP013 fix pack until all of your FileNet P8 functional expansions, such as Records Manager, support it. For details, see the latest edition of the FileNet P8 Hardware and Software Requirements document and the FileNet P8 Fix Pack Dependency/Compatibility Matrix.

• Installation of the fix pack requires 800 MB of available permanent storage space.

• When using a Turkish browser locale, JRE 1.6 is the minimum level required to open Search Designer and Publishing Designer components.

• This fix pack requires the following minimum versions of the supporting FileNet P8 Platform software:

  • For new installations:
  • P8CE-4.0.1-006
  • P8PE-4.0.3 (requires the Process Engine client installer version P8PE-4.0.3-000.001)
  • For upgrades:
    • P8CE-4.0.1

    • P8PE-4.0.1-001

  If the optional IBM FileNet P8 eForms components are installed, the following minimum versions are required:

  • For new installations:
    • P8eF-4.0.2
  • If eForms are installed prior to upgrading to 4.0.2.13-P8AE-FP013:
    • P8eF-4.0.1-002

For more information, see the FileNet P8 Hardware and Software Requirements Guide and the FileNet P8 Fix Pack Dependency/Compatibility Matrix.

Install this fix pack

Install this fix pack on each machine where you have installed Application Engine software.

To install the Application Engine 4.0.2.13-P8AE-FP013 fix pack

1. Log on to the application server:
   • UNIX Log on as a user with read, write, and execute access to the directory where you plan to install Application Engine.
   • Windows Log on as a member of the local Administrators group or a user with equivalent permissions.
2. From Process Task Manager, stop Component Manager (if running), then exit Process Task Manager.
3. (Windows only) From the Windows Services console, stop the Process Application Engine Services Manager service.
4. (Windows only) Using the Windows Task Manager, verify that no javaw.exe processes are running.

   If the applications in the preceding steps stopped correctly, no Application Engine related javaw.exe processes should be running. If needed, use Windows Task Manager or some other process management tool to stop all javaw.exe processes with the directory path <AE_install_path>\_AEjvm\bin.
   
   <AE_install_path> is a variable that indicates the location of the installed Application Engine source files. Below are the default values for this variable:

   UNIX /opt/FileNet/AE
   Windows C:\Program Files\FileNet\AE\

5. For a new installation, continue from Step 8 below.
6. Back up, undeploy, and remove the Workplace web application from the J2EE application server.
   • WebSphere 5.x
     1. Backup the deployed Workplace directory:

        <WAS_HOME>/installedApps/<node_name>/<instance>.ear/app_engine.war

     2. Stop the Workplace Application from the WebSphere administration console.
     3. Uninstall the Workplace application from Enterprise Applications.
     4. Save the changes and stop the WebSphere server.
     5. Delete the temp Workplace directory (default: app_engine.war) from:

        <WebSphere_HOME>/WebSphere/AppServer/temp/<node_name>/<server>/<Workplace_application_name>

   • WebSphere 6.x
     1. Backup the deployed Workplace directory:
        • For WebSphere 6.0:
          <WAS_HOME>/profiles/<profile_name>/installedApps/<node_name>/<instance>.ear/app_engine.war
        • For WebSphere 6.1:
          <WAS_HOME>/profiles/<profile_name>/installedApps/<node_name>/<instance>.ear/app_engine.war
     2. Stop the Workplace Application from the WebSphere administration console.
     3. Uninstall the Workplace application from Enterprise Applications.
     4. Save the changes and stop the WebSphere server.
     5. Delete the temp Workplace directory (default: app_engine.war) from:
        • For WebSphere 6.0:
          <WAS_HOME>/profiles/<profile_name>/temp/<node_name>/<Server>/<instance>/app_engine.war
        • For WebSphere 6.1:
          <WAS_HOME>/profiles/<profile_name>/temp/<node_name>/<Server>/<instance>/app_engine.war
   • WebSphere 7.x
     1. Backup the deployed Workplace directory:
        • <WAS_HOME>/profiles/<profile_name>/installedApps/<node_name>/<instance>.ear/app_engine.war
     2. Stop the Workplace Application from the WebSphere administration console.
     3. Uninstall the Workplace application from Enterprise Applications.
     4. Save the changes and stop the WebSphere server.
     5. Delete the temp Workplace directory (default: app_engine.war) from:
        • <WAS_HOME>/profiles/<profile_name>/temp/<node_name>/<Server>/<instance>/app_engine.war
        • <WAS_HOME>/profiles/<profile_name>/wstemp
          
   • WebLogic 9.x, 10.x, and 11g
     1. From the WebLogic administration console stop the Workplace Web Application Module.
     2. Make a backup copy of the Workplace folder or of the deployed Workplace directory:
        • <AE_install_path>/Workplace
        • <AE_install_path>/deploy/app_engine.war
        • <AE_install_path>/deploy/app_engine.ear
     3. Delete the Workplace Web Application Module.
     4. Stop the WebLogic server.
     5. Delete the temporary Workplace AE directory (default: WorkplaceAE or web_client) from:
        <WL_HOME>/user_projects/domains/<WL_Domain>/servers/<Server>/tmp/_WL_user/app_engine
   • JBoss 4.x.x
     1. Stop the JBoss Application Server.
     2. Make a backup copy of the deployed Workplace directory:
        • <JB_install_path>/server/<instance>/deploy/<application_name>.war or .ear
     3. Delete the existing deployed Workplace application.
     4. Clear out all files and folders within the following temp directories:
        • <JBoss_home>/server/server_name/tmp/deploy
        • <JBoss_home>/server/server_name/work/jboss.web/localhost
   • JBoss 5.x.x Upgrade
     1. Stop the JBoss Application Server.
     2. Make a backup copy of the deployed Workplace directory:
        • <JB_install_path>/server/<instance>/deploy/<application_name>.war or .ear
     3. Delete the existing deployed Workplace application.
     4. Clear out all files and folders within the following temp directories:
        • <JBoss_home>/server/server_name/tmp/deploy
        • <JBoss_home>/server/server_name/work/jboss.web/localhost
        
        After upgrading JBoss, if you upgrading from JBoss 4.x, copy the jboss-classloading.xml file from: install directory\FileNet\AE\jbossFiles, to: install directory\FileNet\AE\Workplace\WEB-INF.
        
7. Copy existing configuration files.

   To retain your existing configurations, copy the following configuration files from the backup copy of your deployed Workplace application to the appropriate folder, as listed below, in the installed directory on your application server, overwriting the existing installed files. You must do this before you apply the fix pack to the existing Application Engine installation.

   Copy the following files from the corresponding folder in the backed-up Workplace directory created in the previous step to the following locations:

   • WcmApiConfig.properties
   • web.xml to:
     
     <AE_install_path>/Workplace/WEB-INF/

   Note If BPF4.1.x-00x is installed on this environment, perform a backup of the following file:

        Integration.xml

        After redeploying Application Engine, add BPF information to the new installation in the Workplace deployed folder.

        The backup of these files is to ensure the files are still available in case there is any reason to revert to the previous versions.
        When redeploying after installing the fix pack, any custom settings will be added back to the deployed working directory.

8. Install or Upgrade Application Engine.

   For more general information about installing Application Engine, see “Install Application Engine” in the FileNet P8 Platform Installation and Upgrade Guide.

   1. Access the IBM FileNet 4.0.2.13-P8AE-FP013 fix pack software package.
   2. Launch the appropriate Setup program (P8AE-4.0.2.13-<operating_system>.bin/.exe).
   3. Complete the Setup screens and finish the installation.
      
   4. Verify that no errors or failures were logged in the app_engine_install_log_4_0_2_13.txt file, located in <AE_install_path>/logs. Correct any errors before proceeding.
   5. If you are upgrading, view the out.txt and err.txt files, located in <AE_install_path>/backup-4_0_2_13/, and verify that no errors or failures were logged. Correct any errors before proceeding.
9. Install the Content Engine and Process Engine client files matching the versions of the Content Engine and Process Engine that are used in your environment. See the sections "Installing the latest Content Engine Client files on Application Engine servers" and "Installing the latest Process Engine Client files on Application Engine servers" within the IBM FileNet P8 Installation guide.

   Notes

   • This step is not necessary if you are upgrading only the Application Engine, and not the Content Engine or Process Engine, and have previously installed the Content Engine and/or the Process Engine client files (the files match the currently installed Content Engine and/or Process Engine).
   • To download the latest software updates, and to determine which of these updates are required for use with other components and expansion products, contact your service representative.

10. (Windows only) After installing the fix pack, start the Process Application Engine Services Manager service from the Windows Services console.
11. Deploy Application Engine.

    For details, see one of the following topics in the FileNet P8 Platform Installation and Upgrade Guide:

    • “Deploy Application Engine (WebSphere).”
    • “Deploy Application Engine (WebLogic).”
    • “Deploy Application Engine (JBoss).”

    Note It is strongly recommended that all client machines using the P8 Office Integration or File Tracker applications upgrade to the version that corresponds with this fix pack. See the "Upgrade Application Integration and File Tracker" topic in the IBM FileNet P8 Platform Installation and Upgrade Guide for upgrade instructions.

12. (FileNet P8 systems using Image Services Integration only) Verify that you are running a supported version of Image Services Resource Adaptor (ISRA).

    See the FileNet P8 4.0.x Hardware and Software Requirements document for details on supported ISRA versions.

    For more information on how to upgrade ISRA and configure Image Services integration, see your ISRA documentation and “Enable Application Engine to use ISRA” in the IBM FileNet P8 Platform Installation and Upgrade Guide.

13. (Business Process Framework only) If BPF4.1.0 or later is installed on this environment, please refer to FileNet Business Process Framework Installation Guide for 4.1.0 to perform the steps in the section "Applying IBM FileNet P8 Platform changes to the Business Process Framework installation."

Install this fix pack silently

To Silently Install Application Engine

1. Access the IBM FileNet 4.0.2.13-P8AE-FP013 fix pack installation software package, and copy the appropriate AE_silent_install.txt file to a local directory.
2. Edit the file to reflect the appropriate responses for your installation, following the instructions included in the silent input file.
3. From a command prompt, navigate to and execute the installer:

   For UNIX:

   ./P8AE-4.0.2.13-<operating_system>.bin -options <path_to_edited_input_file>/AE_silent_install.txt -silent

   For Windows:

   P8AE-4.0.2.13-WIN.exe -options "<path_to_edited_input_file>\AE_silent_install.txt" -silent

4. Continue with the View the app_engine_install_log_4_0_2_13.txt file step above, and complete all post-installation steps that follow.

To silently upgrade Application Integration or File Tracker

Silent upgrades of Application Integration or File Tracker from 4.0.2.4-AE-FP004 or earlier to 4.0.2.5-AE-FP005 fix pack or later, additional steps are required.

To perform a silent upgrade of any previous version of Application Integration to Application Integration 4.0.2.5 or later:

1. From a command line, use this statement to silently uninstall the existing version of Application Integration. Note User settings will be retained on uninstall:

   MsiExec.exe /X{35907B7D-02E2-490C-8F3B-54C4E3729D90} /qn LICENSE_ACCEPTED="true"

2. Download or copy the Application Integration installer to the local client.
3. Open a command window and change the current directory to the directory where ApplicationIntegration.exe resides.
4. Enter the following command to silently install the current Application Integration fix pack version. Please see the "Installing Application Integration silently" section of the IBM FileNet P8 Platform Installation and Upgrade Guide for more details.
   ApplicationIntegration.exe /s/v"/qn <additional msi arguments included in string> LICENSE_ACCEPTED=true"
   For example:
   ApplicationIntegration.exe /s /v"/qn /L*v C:\temp\AppIntSetup.txt LICENSE_ACCEPTED=true"

To perform a silent upgrade of any previous version of File Tracker to File Tracker 4.0.2.5 or later.

1. Enter the following command to silently uninstall File Tracker:
   Msiexec.exe /X{4291FBBC-C585-43ED-9416-5F22D8C6FEE9} /qn LICENSE_ACCEPTED="true"
2. Download or copy the File Tracker installer to the local client.
3. Open a command window and change the current directory to the directory where FileTracker.exe resides.
4. From the command line, execute the following to silently install the current FileTracker version. Please see the "Installing the File Tracker software silently" section of the IBM FileNet P8 Platform Installation and Upgrade Guide for details.

   FileTracker.exe /s /v"/qn /L*v C:\temp\FileTrackerSetup.txt LICENSE_ACCEPTED=true"

   Direct upgrades of Application Integration and File Tracker using the silent installer will only work from 4.0.2.5-AE-FP005 and later.

Install this Fix Pack with Multiple Application Engine Instances

If you are installing this fix pack in an environment where you have multiple instances of Workplace on a single application server, follow the instructions in this readme, with the following modifications to the "To install the Application Engine Fix Pack 4.0.2.13-P8AE-FP013" topic above:

• In Step 6 Back up, undeploy, and remove the Workplace web application from the J2EE application server, you must:
  • Make backup copies of all deployed instances or Workplace.
  • Uninstall all deployed instances of Workplace.
  • Delete the temp directory for all instances of Workplace.
• In Step 7 Copy existing configuration files, you must copy the web.xml files for each deployed instance of Workplace, and give it a descriptive name (such as web.xml.2 etc.)
• After Step 7 you must backup the existing configuration files in ...Config/AE2 etc., and then copy the updated configuration files in ...Config/AE to ...Config/AE2 and manually edit in any custom changes from the old configuration files to the new updated files.
• In Step 11 Deploy Application Engine, you must repackage the WAR/EAR files for the additional instances of Workplace using the modified web.xml files mentioned above. For information, see the "Deploy Multiple Application Engine Instances" task of the FileNet P8 Platform Installation and Upgrade Guide.

Uninstall this fix pack

The fix pack uninstaller will uninstall the entire Application Engine installation. You cannot remove the fix pack by itself.

Run the uninstaller from <AE_install_path>/_AEuninst/uninstaller.bin (.exe)

Always use the uninstaller from the _AEuninst folder with the highest number appended. For example, if both _AEuninst and _AEuninst2 exist, use _AEuninst2.

Product Fix History

There are no product fixes in this fix pack, only an updated security certificate used to sign the FileNet Application Engine .jar file, and two client installer files.

4.0.2.12-P8AE-FP012

4.0.2.11-P8AE-FP011

4.0.2.10-P8AE-FP010

4.0.2.9-P8AE-FP009

4.0.2.7-P8AE-FP007

4.0.2.6-P8AE-FP006

4.0.2.5-P8AE-FP005

4.0.2.4-P8AE-FP004

4.0.2.3-P8AE-FP003

4.0.2.2-P8AE-FP002

4.0.2.1-P8AE-FP001

P8AE 4.0.2-000

Contact Customer Support

For information about contacting customer support:

1. Navigate to the Information Management support page (www.ibm.com/software/data/support).
2. On the Information Management Support page, search for: How to get support for IBM FileNet products.

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 grant you any license to these patents. You can send license inquiries, in writing, to:

IBM Corporation
J74/G4
555 Bailey Avenue
San Jose, CA 95141
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
J46A/G4
555 Bailey Avenue
San Jose, CA  95141-1003
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 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.

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.

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. The sample programs are provided "AS IS", without warranty of any kind. IBM shall not be liable for any damages arising out of your use of the sample programs.

Trademarks

• IBM, the IBM logo, and ibm.com are trademarks or registered trademarks of International Business Machines Corporation in the United States, other countries, or both. If these and other IBM trademarked terms are marked on their first occurrence in this information with a trademark symbol (® or ™), these symbols indicate U.S. registered or common law trademarks owned by IBM at the time this information was published. Such trademarks may also be registered or common law trademarks in other countries. A current list of IBM trademarks is available on the Web at "Copyright and trademark information" at www.ibm.com/legal/copytrade.shtml.
• Adobe, the Adobe logo, PostScript, and the PostScript logo are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States, and/or other countries.
• Cell Broadband Engine is a trademark of Sony Computer Entertainment, Inc. in the United States, other countries, or both and is used under license there from.
• Java and all Java-based trademarks 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.
• 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.
• 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.
• 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
• IT Infrastructure Library is a registered trademark of the Central Computer and Telecommunications Agency, which is now part of the Office of Government Commerce.
• Other company, product, or service names may be trademarks or service marks of others.