IBM Rational Application Developer for WebSphere Software, Version 7.0.0.3 Readme

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

1.0 About this release

This fix pack contains new features, enhancements, and fixes to the version 7.0, version 7.0.0.1 and version 7.0.0.2 releases of IBM^® Rational^® Application Developer for WebSphere^® Software.

For an updated version of this readme file, see the file available online at: http://download.boulder.ibm.com/ibmdl/pub/software/rationalsdp/v7/rad/7003/docs/readme/readme.html

In addition, see the release notes for version 7.0 of this product to learn about its new features and any limitations or problems known at the time of its release. The release notes for version 7.0 are available at: http://download.boulder.ibm.com/ibmdl/pub/software/rationalsdp/v7/rad/70/docs/readme/readme.html

This version also includes all enhancements and new features from the following fix packs:

1.1 New in this release

This release of Rational Application Developer contains the following new features and enhancements:

Platform, operating system, and software integration support enhancements:
- Red Hat Enterprise Linux^® 4 Update 5
- Citrix Presentation Server 4.0.
  Note:
  - The server must run on an operating system that is supported by Rational Application Developer.
  - You must use a floating license for sharing license keys with multiple users. The use of an authorized user license is not supported.
- IBM Installation Manager, Version 1.0.0.4 includes the enhancement to allow updates to be rolled back. For information, see the version 1.0.0.4 readme file at http://download.boulder.ibm.com/ibmdl/pub/software/rationalsdp/v7/im/1004/docs/readme/readme.html.
- IBM WebSphere Application Server, Version 6.0.2 Fix Pack 15
- IBM WebSphere Application Server, Version 6.1 Fix Pack 9
- IBM WebSphere Application Server, Version 6.1 Feature Pack for Web Services
- Eclipse Modeling Framework (EMF) 2.2.3. For information, visit the Eclipse Modeling Framework home page at http://www.eclipse.org/modeling/emf/downloads/?project=emf.
New installable features:
Note:
New installable product features are not displayed and cannot be added while running the Update Packages wizard in Installation Manager. To view and add new installable product features, run the Modify Packages wizard in Installation Manager after you have installed the fix pack.
- Web services feature pack Provides features for assembling and deploying reliable, asynchronous, secure, and interoperable Java^® Web services for application components. The Web services feature pack is designed for IBM WebSphere Application Server, version 6.1, extended with the WebSphere Application Server feature pack for Web services. This feature supports the development of Web services from annotated Java or from Web Services Description Language (WSDL) using any XML Schema.
- IBM WebSphere Application Server, version 6.1 Feature Pack for Web services Upgrades IBM WebSphereApplication Server, version 6.1 to version 6.1.0.9 and installs the runtime required to support the Feature Pack for Web Services.
  The WebSphere Application Server V6.1 Feature Pack for Web Services extends the capabilities of WebSphere Application Server V6.1 to enable Web services messages to be sent asynchronously, reliably, and securely, focusing on interoperability with other vendors and to provide support for the Java API for XML Web Services (JAX-WS) 2.0 programming model.
  The Feature Pack for Web Services introduces a set of Web services standards that support interoperable and reliable Web services applications. You can send messages asynchronously, which means that your messages can communicate reliably even if one of the parties is temporarily offline, busy, or not available. You can send messages securely and rest assured your messages are not vulnerable to attack. You can be confident that your communication is reliable and reaches its destination while interoperating with other vendors.
  JAX-WS simplifies application development through a standard, annotation-based model to develop Web services applications and clients. A common set of binding rules for XML and Java objects make it easy to incorporate XML data and processing functions in Java applications; and a further set of enhancements help you send binary attachments, such as images or files, with the Web services request in an optimal way.
  Simplified management using Web services profiles makes it easy to configure and reuse configurations, so you can introduce new Web Services profiles seamlessly in the future. These configurations are captured in a grouping called Policy Sets which allows you to select and associate different qualities of service with an application. You can configure policy sets to allow only those capabilities within a given WS-Interoperability (WS-I) profile, thereby limiting and ensuring that the only configurable portions are those that are desired. WS-I is an open industry organization chartered to promote Web Services interoperability across platforms, operating systems and programming languages.
  The Feature Pack for Web Services includes support for:
  - New Web services standards, including:
    - Web Services Reliable Messaging (WS-RM)
  - New standards-based programming model support:
    - Java API for XML Web Services (JAX-WS 2.0)
EJB domain modeling enhancements: Enterprise JavaBeans (EJB) domain modeling was enhanced by adding property views for these items:
- EJB beans
- CMP fields of entity beans
- EJB interfaces
- EJB Java archive (JAR) files
WSDL domain modeling enhancements: The WSDL domain modeling has been enhanced to support:
- Creating a binding to a port type in a different WSDL file
- Assigning messages from one WSDL file to an operation in a different WSDL file
- Importing WSDL/XSD files
- Importing existing local and remote XSD schemas

2.0 Installation information

This section describes the installation requirements and specific installation instructions for this fix pack.

You can install this fix pack as an update to version 7.0, 7.0.0.1, or 7.0.0.2 of IBM Rational Application Developer already installed on your computer. It can also be installed at the same time that you install IBM Rational Application Developer, Version 7.0.

Important note about upgrading from Microsoft^® Windows^® XP to Windows Vista:: If you plan to upgrade your Microsoft Windows XP operating system to Windows Vista and IBM Rational Application Developer, Version 7.0, 7.0.0.1 or 7.0.0.2 is currently installed, refer to the instructions on the Support Web site, http://www.ibm.com/support/docview.wss?uid=swg21257411.

For information about installing Rational Application Developer, Version 7.0, including installation prerequisites, see the Installation Guide online at http://download.boulder.ibm.com/ibmdl/pub/software/rationalsdp/v7/rad/70/docs/install_instruction/install.html.

For instructions on installing Rational Application Developer on a Windows Vista computer for the first time, see section 2.4.3 Installing Rational Application Developer, Version 7.0.0.3 on a Windows Vista computer.

2.1 Hardware requirements

There are no additional processor or memory requirements for installing this fix pack; however, there might be additional disk space requirements depending on whether you are installing the fix pack at the same time that you install Rational Application Developer, Version 7.0 or if you are installing the fix pack as an update:

If you are installing the fix pack at the same time that you install Rational Application Developer, Version 7.0, then the disk space requirements are essentially the same as for version 7.0.
If you are installing the fix pack as an update, however, you might need up to an additional 2 GB of disk space. Your actual disk space requirements depend on the features that you selected for the version of the product currently installed on your computer.

If you choose to download the update as a compressed file for local installation, you require approximately 6 GB to store and extract the compressed file.

2.2 Software requirements

This section describes the additional software requirements for installing Rational Application Developer, Version 7.0.0.3; to see the requirements for installing Rational Application Developer, version 7.0, see the Installation Guide.

Before you can install this fix pack, you must install IBM Installation Manager, Version 1.0.0.4. In Installation Manager, if you have not disabled the default setting to search the linked repositories during installation and update, IBM Installation Manager, Version 1.0.0.4 is automatically installed on your computer when you attempt to update or install packages using an earlier version of Installation Manager.

For additional information about Installation Manager, Version 1.0.0.4, refer to http://download.boulder.ibm.com/ibmdl/pub/software/rationalsdp/v7/im/1004/docs/readme/readme.html.

If you are extending an Eclipse IDE, then before you install this fix pack you must install version 3.2.2 or higher of the Eclipse IDE and one of the following Java runtime environments:

For Windows: IBM 32-bit Runtime Environment for Windows, Java 2 Technology Edition, Version 5.0 service release 4; Sun Java 2 Platform Standard Edition Runtime Environment Version 5.0 Update 11 for Microsoft Windows
For Linux: IBM 32-bit Runtime Environment for Linux on Intel® architecture, Java 2 Technology Edition, Version 5.0 service release 4; Sun Java 2 Platform Standard Edition Runtime Environment Version 5.0 Update 11 for Linux x86 (not supported for SUSE Linux Enterprise Server [SLES] Version 9)

Note:: For Windows Vista: If you install Eclipse inside the Program Files directory (C:\Program Files), then you must run Rational Application Developer as the administrator. (Right-click the program shortcut and click Run as administrator.)

To update an existing Eclipse IDE to version 3.2.2 or later, if you have Internet access, complete the following steps:

Start Rational Application Developer.
Click Help > Software Updates > Manage Configuration.
In the Manage Configuration dialog box, expand the folder that contains the current Eclipse IDE and click the entry starting with Eclipse Project SDK 3.2.1.r321.
In the right-hand pane, click Scan for updates.
In the Update Site Mirrors window, select an update site mirror and click OK.
In the Updates wizard, on the Search results page, select an Eclipse update site and click Next.
Follow the on-screen instructions in the Updates wizard to install the update.
Note: When you are prompted to verify the update of the features that have not been digitally signed, click Install All.
After the update is completed, in the Install/Update window, click Yes to restart the product.

Now your Eclipse IDE meets the prerequisite version for installing this fix pack.

2.3 Other requirements

Internet access is usually required because, by default, the update is located and installed by Installation Manager directly from the IBM update repository for Rational Application Developer, Version 7.0.

Important: When Rational Application Developer is installed, the location of its update repository is automatically embedded in Installation Manager. For Installation Manager to search the default update repository, the preference Search the linked repositories during installation and updates on the Repositories preference page must be selected. This preference is selected by default.

To install the fix pack from a different repository location (for example, if the fix pack is available on a shared drive or HTTP or HTTPS server), you must add the repository location in Installation Manager. To add a repository location:

Start Installation Manager
On the Start page of Installation Manager, click File > Preferences, and then click Repositories. The Repositories page opens.
On the Repositories page, click Add Repository.
In the Add repository window, enter the URL of the repository location or browse to it and enter a file path, and then click OK.
Click OK to close the Preference page.

2.4 Installation instructions

The following are two ways to install this update:

If IBM Rational Application Developer, Version 7.0, 7.0.0.1 or 7.0.0.2 is already installed on your system, then you can install this update by using the Update Packages wizard in IBM Installation Manager. For general instructions on installing an update, refer to the section "Updating Rational Application Developer" in the Installation Guide. For detailed instructions, see section 2.4.1 Installing Rational Application Developer, Version 7.0.0.3 as an update.
If you are installing IBM Rational Application Developer, Version 7.0 for the first time or if you are installing an additional instance of it, then you can install this update at the same time that you install IBM Rational Application Developer, Version 7.0 by clicking Check for updates on the Install page of the Installing Packages wizard in IBM Installation Manager. For general instructions on installing an update, refer to the section "Installing IBM Rational Application Developer using the IBM Installation Manager graphical interface" in the Installation Guide.

Important - if you are installing Rational Application Developer for the first time on Windows Vista, refer to the section 2.4.3 Installing Rational Application Developer, Version 7.0.0.3 for the first time on a Windows Vista computer for instructions.

By default, the update is installed directly from the IBM update repository; however, it is also available for download. For details, see the specific installation instructions noted below for Rational Application Developer, Version 7.0.0.3.

2.4.1 Installing Rational Application Developer, Version 7.0.0.3 as an update

Install the fix pack with the same user account that installed the product.

Restrictions:

Rational Application Developer, Version 7.0, 7.0.0.1 or 7.0.0.2 must be installed.
The product cannot be open when you install this fix pack. Also, ensure that all browsers and other applications opened by Rational Application Developer are closed.

To find and install Rational Application Developer, Version 7.0.0.3 as an update:

Start IBM Installation Manager.
On Windows Vista:
You must run Installation Manager as administrator. (Right-click the program shortcut and click Run as administrator.)
On the Start page of Installation Manager, click the Update Packages button.
If a new version of Installation Manager is found, you are prompted to confirm that you want to install it before you can continue. Click OK to proceed. Installation Manager automatically installs the new version, stops, restarts, and resumes.
In the Update packages wizard, select the Installed Location for Rational Application Developer and click Next. Installation Manager searches for updates in the Rational Application Developer repository on the Web, as well as any repository locations that you entered. A progress indicator shows the search is taking place.
By default, recommended updates are displayed and selected on the Update Packages page. Ensure that you select Version 7.0.0.3 for Rational Application Developer, then click Next.
On the Licenses page, read the license agreements for the update. On the left side of the License page; click each item to display the license agreement text.
1. If you agree to the terms for all of the license agreements, click I accept the terms of the license agreements
2. Click Next to continue.
3. On the Summary page, review the information displayed, and then click Update. A progress indicator shows the percentage of the installation completed.
When the update process completes, a message that confirms the success of the process is displayed near the top of the page. Click View log file to open the log file for the current session in a new window. You must close the Installation Log window to continue.
For Windows Vista: Refer to section 2.5 Starting Rational Application Developer on Windows Vista for information about starting Rational Application Developer on Windows Vista.

2.4.2 Downloading the fix pack for local installations

You can download compressed files containing the Rational Application Developer, Version 7.0.0.3 fix pack; the files that you extract from the compressed files form a repository for the fix pack. You can install the fix pack from the repository on your own computer, or you can use IBM Packaging Utility to create the repository that can be hosted on a shared drive or an HTTP or HTTPs server.

To download and install the fix pack, complete the following steps:

Download the fix pack from http://www.ibm.com/support/docview.wss?uid=swg24015738.
Extract the compressed files in an appropriate directory. For example, extract the file to C:\temp\update.
Add the fix pack repository location in IBM Installation Manager:
1. Start IBM Installation Manager.
2. On the Start page of Installation Manager, click File > Preferences, and then click Repositories. The Repositories page opens.
3. On the Repositories page, click Add Repository.
4. On the Add repository window, browse to or enter the file path to the diskTag.inf file, which is located in the disk1 sub-directory in the directory where you extracted the compressed files. For example, enter C:\temp\updates\disk1\diskTag.inf and then click OK.
5. Click OK to close the Preference page.
Install the fix pack as described previously in this document.
Note:
During the process of updating from a local repository, Installation Manager might prompt you for the location of the repository for Rational Application Developer, Version 7.0. If you installed the product from CDs or other media, they must be available when you use the update feature.

2.4.3 Installing Rational Application Developer, Version 7.0.0.3 for the first time on a Windows Vista computer

The steps for Installing Rational Application Developer, Version 7.0.0.3 on a Windows Vista computer are essentially the same as installing on other Windows computers. However, there are some important differences that are summarized below.

Sample installation steps are provided in this section. For additional details and installation scenarios, see the Installation Guide.

Installation notes for Windows Vista:

You must run Installation Manager as administrator. (Right-click the program shortcut and click Run as administrator.)
If you are starting the installation of Rational Application Developer from the launchpad program, then you must run the launchpad program as administrator.
Note:
If the launchpad program starts automatically (for example, if you are installing from a CD), stop the launchpad program and then restart it using the Run as administrator command; navigate to the CD or disk image, right-click on launchpad.exe (at the top level of the CD or image) and click Run as Administrator.
Selecting installation directories within the Program Files directory (typically C:\Program Files) is not recommended.
Note:
If you select either an installation location or shared resources directory within the Program Files directory, then the packages that you install must be run as administrator. See 2.5 Starting Rational Application Developer on Windows Vista for details.

Sample installation steps for Rational Application Developer, Version 7.0.0.3 on Windows Vista

Start the launchpad program as administrator. (Right-click the launchpad program and click Run as administrator.
If you have not done so already, read the release information by clicking Release notes.
When you are ready to begin the installation, click Install IBM Rational Application Developer.
A message window opens to inform you whether the program IBM Installation Manager is detected on your workstation.
If IBM Installation Manager is not detected on your system, then you are informed that you must install it before you can continue.
1. Click OK to install IBM Installation Manager. The IBM Installation Manager installation wizard starts. Follow the on-screen instructions in the wizard to complete the installation of IBM Installation Manager.
2. When the installation of IBM Installation Manager completes successfully, click Finish to close the wizard.
3. Read the message that opens and click OK. Installation Manager starts and automatically opens the Install Packages wizard.
If IBM Installation Manager is detected on your system, click OK and Installation Manager starts and automatically opens the Install Packages wizard.
On the Install page, click Check for updates.
If a new version of Installation Manager is found, you are prompted to confirm that you want to install it before you can continue. Click OK to proceed. Installation Manager automatically installs the new version, stops, restarts, and resumes.
Click Check for new updates and extensions and select the latest version of the product (7.0.0.3).
Follow the on-screen instructions in the Install Packages wizard to complete the installation. Note that you should not choose a Shared resources directory or an installation location in the Program Files directory (C:\Program Files).

2.5 Starting Rational Application Developer, Version 7.0.0.3 on a Windows Vista computer

If the installation location or shared resources directory for Rational Application Developer is in a directory in the path C:\Program Files, then you must run Rational Application Developer as the administrator. To run as administrator, right-click the program shortcut and click Run as administrator.

On Windows Vista, the Program Files directory is virtualized in order to allow users who are not running as the administrator to have write access to this protected directory. However, the virtualization workaround is not compatible with Rational Application Developer.

If you selected an installation location or shared resources directory in the path C:\Program Files and you do not want to require running Rational Application Developer as administrator, then do one of the following steps:

If you selected an installation location in a directory in the path C:\Program Files, then reinstall Rational Application Developer (and any other programs sharing the same installation location) and select an installation location that is not in the path C:\Program Files.
If you selected a shared resources directory in the path C:\Program Files, then reinstall Rational Application Developer and all Rational Software Development Platform products (regardless of their installation location) and select shared resources directory and installation locations that are not in the path C:\Program Files.

For more information on running Rational Application Developer on Windows Vista, refer to the technote at http://www.ibm.com/support/docview.wss?uid=swg21257842

2.6 Uninstalling the fix pack

If you updated a previously installed version to version 7003, you can revert to the previous version by using the rollback feature of Installation Manager. For instructions on uninstalling the product, see the Installation Guide.

The rollback feature uninstalls the updated resources and reinstalls the resources from the previous version. You can only roll back one version level at a time.

When you roll back to an earlier version of a package, it will be restored with same features that were associated with that version; any features that you added after upgrading to version 7003 by using the Modify Packages wizard will be removed, and any features that you removed will be restored.

During the rollback process, Installation Manager must access files from the earlier version of the package. By default, these files are stored on your system when you install a package. If you changed the default setting or deleted the files by using the Remove Stored Files option on the Roll Back preferences page (File > Preferences > Rollback Files), Installation Manager will require access to your installation repository or media. If you installed the product from a repository, you must have listed in your Preferences (File > Preferences > Repositories) the repository from which you installed the previous version of the product. If you installed the product from CDs or other media, they must be available when you use the rollback feature.

Before you roll back Rational Systems Developer, Version 7.0.0.3, complete the following steps:

Log in with a user account that has the same privileges as the account that was used to install the packages to be uninstalled.
Close Rational Application Developer, Version 7.0.0.3 and any other applications that you installed by using Installation Manager.
If any applications started by Rational Systems Developer are still open or running, such as a browser, close them.

To roll back an updated package, complete the following steps:

Start IBM Installation Manager.
On the Start page, click Roll Back Packages.
In the Rollback wizard, from the Package Group Name list, select the package group that contains the packages that you want to roll back and click Next.
Select the version of the package that you want to roll back to and click Next.
Read the summary information and click Roll Back.

For additional instructions on uninstalling Rational Application Developer, see the Installation Guide or see the Installation Manager online help.

3.0 Fixes contained in this release

This section list the APARS that are fixed in this release. This fix pack also includes the fixes from the following fix packs:

The following APARs are fixed in this release:

2.1 XML tools

(JR23857) Validation preferences cannot be imported.

(PK35355) WSDL and XML Schema documentation generation needs to be enhanced.

2.2 Crystal reports

(PK38654) The "result set closed" error occurs when changing Crystal Report Stored Procedure.

2.3 JavaServer Faces and ODC tools

(PK40357) An error occurs at runtime when linking a relational record list with relationships to a combobox.

(PK41983) A page containing an inputText field with the mask converter and inputHelperAssist leaves invalid content in "blank" fields.

(PK42477) Link Renderers (output and request) mishandle null parameter values.

(PK44414) hx:datatTableEx shows poor performance for a large data set.

(PK44622) A semi-colon is missing for JSFSlider in files hxclient_core_v3_0_2.js & hxclient_be_v3_0_2.js coming from jsf-ibm.jar file.

(PK44865) Selecting an h:outputText element in PageDesigner throws NullPointer exception.

(PK44890) Onchange event is not executed when typeahead is enabled.

(PK45392) The application does not include any reference to the targetAction attribute for behaviorKeyPress JSF component.

2.4 Web services

(PK40097) Errors occur in mapping Danish national characters to SOAP request.

(JR26203) When creating a Web service from an EJB, the router module mapping in the webservice IBM binding file is incorrect if the router module contains spaces in the name.

2.5 J2EE tools

(PK41092) A deletion process of a project cannot be cancelled.

2.6 Portal and portlet tools

(PK39143) Hidden input is used to specify action name parameter for cooperative portlets.

(PK40729) Exceptions occur when removing portlet project from Portal 6 server.

(PK44778) SAP/PSFT/Siebel mediators xxxParams() and xxxResult() are not available on Page Data

(PK45651) Problems occur when deploying Portlets to Portal v6.

(PK46786) My Portal Pages cannot be modified from my Portal Configuration project.

2.7 Data tools

(PK42092) NullPointerException in com.ibm.datatools.modelmigration.ModelMigration.

(PK43245) DB2^® UDB zSeries^® V8 cannot be connected via the Database Explorer.

2.8 EJB tools

(JR26203) When creating a Web service from an EJB, the router module mapping in the webservice IBM binding file is incorrect if the router module contains spaces in the name.

2.9 User assistance

(PK39383) The tutorial "Creating a Web service client using Faces" WSDL location needs updating.

(PK41145) The silent installation (including updates) needs documentation.

(PK41861) Discrepancy in documentation on MySQL support status.

(PK42109) The documentation on setting COBOL Importer Preferences does not highlight table defaults used by Importer tools.

(PK42120) Documentation is missing on setting up a remote Portal 6.0 server.

(PK42836) The JSF progressBar component documentation needs improvement.

(PK44124) Documentation is missing on J2EE projects targeting WebSphere Application Server v5.0.

(PK44662) Documentation is missing on the fact that Changing of Targeted Runtimes requires changing WebSphere Project Facets.

2.10 Web tools

(PK37552) Free layout table in design time page template cannot be shrunk when at limits.

(PK38484) Parts cannot be created in an opening JSP page that has only <%jsp code%>.

(PK40306 ) LinksBuilder cannot convert links if context root has a slash (/myroot/context).

(PK41818) The CPU is used by 100% when saving a specific JSP file in the source tab of the Page Designer.

(PK46779) Relational record list returns incorrect datatype for Oracle 10.

2.11 UML modeling framework

(PK35527) Problems in changing default value of stereotype properties.

2.12 UML modeling and visualization

(PK36747) Boundary class shape images don't display properly on diagrams in migrated models.

2.13 EJB deployment tools

(PK42209) When attempting to deploy an invalid Enterprise Archive or Enterprise JavaBean Archive file, the command line tool EJB Deploy does not display the proper error messages.

(PK41663) An EJB-QL statement defined to accept two input parameters causes a runtime failure because only one parameter in the generated deployment code is set.

(PK38245) Infinite publishing occurs when deploying an EJB application to a v6.0 or v6.1 WebSphere Application Server.

2.14 Server tools

(PK40728) The connection to the version 6 WebSphere Application Server runtime is lost when using RMI as the connector and the localhost network address changes.

(PK42167) Publishing an EJB application to a v6.x WebSphere Application Server causes the application to be published to the server, started, stopped, and then started again.

(PK42597) The hyperlinks in the console for the versions 5.1, 6.0, and 6.1 WebSphere Application Server runtimes does not link to the messages file provided by the WebSphere Application Server runtime.

(PK43743) When publishing an application to a v6.x WebSphere Application Server, binary JAR files residing in the Enterprise Application project or the WEB-INF\lib folder of a Web project are being included on the looseconfig.xml file, causing an OpenFailureException error when the application is published to WebSphere Application Server.

2.15 Compare/merge

(PK45586/PK45577) Comparing a model with a previous version fails.

(PK41354) CVS Watch/Edit does not work correctly for elements such as documentation, advanced properties, and name changes on diagrams.

2.16 Rational RequisitePro^® integration

(PK25839) Requirement does not reflect location of the element.

2.17 Struts tools

(PK39634) The Struts Configuration File Editor text box behaves erratically.

(PK39637) The Struts Config File Editor scope scroll-down box option is not written to the source.

(PK39744) Pressing Ctrl-v to paste in the Struts Config File Editor with focus on the text field puts copied text in random place in source editor.

2.18 Installation

(PK38586) The application cannot be installed due to IBM Support Assistant shortcut.

(PK43970) Updating to V7002 causes error: the com.ibm.cds plugin cannot be found.

2.19 Tutorials and samples

(PK42614) Auction Portlet tutorial requires revision.

2.20 Jython editor

(PK41918) If viewing a tooltip for a Jython artifact in the Jython editor when the product window is maximized, then the window is no longer maximized and is shifted to the right.

2.21 WebSphere Application Server extensions

(PK43578) If a workspace is created with a previous product release and server targeting is not applied to the projects in the workspace, then when this workspace is migrated, a StackOverflowException will occur if the Enterprise Application project contains binary EJB or WAR files.

3.22 EJB mediator

(PK41413) Cannot add a mediation handler from the EJB deployment descriptor editor.

4.0 Known limitations, problems, and workarounds

4.1 On Windows Vista, execution of ClearCase "clearviewupdate" command fails if UAC is turned on

In the IBM Rational ClearCase^® integration with the application on Windows Vista, execution of ClearCase "clearviewupdate" command fails with Error 740 when you create a snapshot view and you cannot update the ClearCase view by using the menu, if User Account Control (UAC) is turned on by default.

Workaround:

Disable the UAC feature. For more information about this and other known issues with ClearCase on Windows Vista, refer to http://www.ibm.com/support/docview.wss?uid=swg21257474

4.2 Enabled profile must be adopted to enable WebSphere Application Server v6.1 test environment with IBM WebSphere Application Server V6.1 Feature Pack for Web Services

After installing the IBM WebSphere Application Server V6.1 Feature Pack for Web Services feature for the WebSphere Application Server v6.1 test environment, the updated WebSphere Application Server v6.1 test environment is not visible unless you manually adopt a server profile that is enabled with the IBM WebSphere Application Server V6.1 Feature Pack for Web Services.

Cause:

When you install the Web Services Feature Pack option, if WebSphere Application Server v6.1 is also selected, or is already installed, then you must also install the WebSphere Application Server Version 6.1 Feature Pack for Web Services feature. With this update, a server profile that is enabled for WebSphere Application Server V6.1 Feature Pack for Web Services is created with the name 'AppSrvWSFP01'. However, this server profile is not associated with any server definition by default.

Workaround:

To use the server profile that is enabled for IBM WebSphere Application Server V6.1 Feature Pack for Web Services, when you launch the workbench for the first time after installing IBM WebSphere Application Server V6.1 Feature Pack for Web Services, do one of the following tasks:

Create a new server definition that uses AppSrvWSFP01 server profile. For instructions, see http://publib.boulder.ibm.com/infocenter/radhelp/v7r0m0/index.jsp?topic=/com.ibm.ws.ast.st.v6.ui.doc/topics/twcrtins_v6.html.

Modify existing default server definition to point to AppSrvWSFP01 server profile. For instructions, see http://publib.boulder.ibm.com/infocenter/radhelp/v7r0m0/topic/org.eclipse.wst.server.ui.astrxd.doc.user/topics/twedtins.html.

4.3 CICS^® Transaction Gateway V7.0 does not support Vista

CICS Transaction Gateway V7.0 does not currently support Windows Vista. Please see the following Web page for more information on supported environment for use with the CICS Transaction Gateway: http://www.ibm.com/software/htp/cics/ctg/reqs/

4.4 CICS Transaction Gateway v7 RARs can be deployed only on WebSphere Application Server v6.1.

CICS Transaction Gateway v7 RARs are built using the IBM SDK Java 2 Technology Edition, V5 and therefore are only supported for deployment on WebSphere Application Server v6.1.

For further details on the support and enhancements in CICS TG V7.0 refer to IBM United States Software Announcement 206-303 available at http://www.ibm.com/common/ssi/fcgi-bin/ssialias?infotype=an&subtype=ca&supplier=897&letternum=ENUS206-303

4.5 When installing the WebSphere Web Services Feature Pack feature, the corequisite feature IBM WebSphere Application Server Version 6.1 Feature Pack for Web Services is not automatically selected

If you are installing or have already installed the WebSphere Application Server Version 6.1 feature and want to install the WebSphere Web Services Feature pack feature, then you must also install the IBM WebSphere Application Server Version 6.1 Feature Pack for Web Services, which provides the updates required for the WebSphere Application Server feature to support the Web Services feature pack functions. This corequisite feature is not selected automatically, which is the expected behavior.

Workaround:

Ensure that you select both the WebSphere Web Services Feature pack feature and the IBM WebSphere Application Server Version 6.1 Feature Pack for Web Services feature.

4.6 Selecting "Run on Server" after modifying portlet JSP files containing SDOs in a portlet application causes the portlet application to restart instead of just refreshing the browser

Selecting "Run on Server" after modifying portlet JSP files containing SDOs in a portlet application causes the portlet application to restart instead of just refreshing the browser.

In version 7.0.0.3, if a change is made to a portlet application - for example, a change in a JSP or a change in a class file - selecting "Run on Server" does not require a restart of the portlet application; instead, the browser is refreshed (thereby saving time).
However, if you modify a JSP file in a portlet application that contains SDOs, selecting "Run on Server" causes the portlet application to restart.
Workaround:
To avoid restarting complete portlet application after modifying a JSP file containing SDO, manually refresh the browser to see your changes; do not select "Run on Server."

4.7 Difficult to clear the selection to install the IBM WebSphere Application Server, Version 6.1 feature

On the feature selection page during the installation, IBM WebSphere Application Server, Version 6.1 is selected by default and cannot be cleared by clicking it.

Workaround:

To choose to not install 'IBM WebSphere Application Server, version 6.1:

Select IBM WebSphere Application Server Version 6.1 Feature Pack for Web Services first (notice the gray-out of the selection box for 'IBM WebSphere Application Server, version 6.1 is removed) , and

Click the IBM WebSphere Application Server, version 6.1 check box. This clears the selection of both features.

4.8 Error when rolling back to version 7.0 or 7.0.0.1 when Rational Agent Controller is running

If you have updated to version 7.0.0.2 or 7.0.0.3 and then attempt to roll back to version 7.0 or 7.0.0.1, then you might get an error if Rational Agent Controller is running.

Cause:

During the rollback process, the Java runtime installed is restored to the previous version. If Rational Agent Controller is running, it might lock some of the files in the JRE and prevent the update.

Workaround:

Make sure that you stop Rational Agent Controller before starting the rollback process.

4.9 Error "Unnecessary classpath entries duplicating MANIFEST.MF entries" in J2EE project

When working with J2EE projects, you might see an error message "Unnecessary classpath entries duplicating MANIFEST.MF entries" in the Problems view.; These errors might prevent you from being able to deploy the application to the sever.

Cause:

The project contains a .classpath entry which is unnecessary because the class path information is computed dynamically from the META-INF/MANIFEST.MF file (which is the method that is used at runtime). The result is an error message reporting that the .classpath entry is unnecessary.

Workaround:

To fix this error, either remove the .classpath entry manually or right-click on the error and select Quickfix to have the .classpath entry automatically removed. If there are many errors of this type in the project, they can all be fixed simultaneously:

Right-click one of the errors,

Select Quickfix.

In the Quickfix dialog, select Find similar problems.

4.10 Published applications may not run after updating to 7003 with Web service features installed

If you update from version 7.0, version 7.0.0.1 or version 7.0.0.2 to version 7.0.0.3 and then install the new Web services feature pack and IBM WebSphere Application Server Version 6.1 Feature Pack for Web services features, then applications that you added to the WebSphere Application Server V6.1 test environment before updating to version 7.0.0.3 and installing the new Web services features might not run on the server.

Workaround:

Remove the applications from the server and then add them again.

4.11 On Windows Vista, permission issues are encountered when starting a local WebSphere Application Server test environment

On Windows Vista, you might have permission problems when starting the server if you are starting a local WebSphere Application Server.
Workaround:

If you experience permission issues when starting the server, then you must launch the workspace with the "Run as administrator" option.

To launch the application with the "Run as administrator" option, right-click the "IBM Rational Application Developer" or "IBM Rational Software Architect" icon and select Run as administrator.
As an alternative, you can:

Right-click the "IBM Rational Application Developer" or "IBM Rational Software Architect" icon and select Properties.

On the Compatibility tab, select Run this program as an administrator.

After you select this option you can double-click to launch the workspace with the "Run as administrator" option.

4.12 Asynchronous exceptions are not properly reported in generated JSPs

When using an asynchronous method on the generated JSPs and an exception occurs, the problem is not reported correctly. The exception should be displayed in the result pane, but instead the message "The service has been invoked" is displayed.

Workaround:

You can modify the result.jsp file to catch asynchronous exceptions and return them to the result.jsp file.

4.13 The Web Service Explorer does not allow the removal of items from a List

When using the Web Service Explorer and executing an operation containing a list. you are given the opportunity to add an item to the list but you will not be able to remove the item.

Workaround:

You can remove the object from the list by switching the view from form to source. In this way you will see the raw xml and be able to adjust the list.

4.14 Client EAR files are published to incorrect server when using the Web service client wizard

When using the Web service client wizard and using multiple WebSphere Application Server servers, the client wizard might add the client EAR to a different server than the one that you specified.

Workaround:

Remove the EAR from the incorrect server and add it to the intended server.

4.15 Error occurs when installing the WebSphere Application Server V6.1 Feature Pack for Web Services if you manually updated the WebSphere Application Server V6.1 Test Environment

If you installed the WebSphere Application Server V6.1 test environment feature and manually updated (in other words, updated without using Installation Manager) it with the WebSphere Application Server V6.1 Fix Pack 9 or later, then an error will occur when you install the WebSphere Application Server V6.1 Feature Pack for Web Services feature.

Workaround:

You must manually remove the manually installed fix pack before you can install the WebSphere Application Server V6.1 Feature Pack for Web Services feature.

4.16 Web Service Explorer cannot publish business to a private UDDI registry when using userid and password

When using the Web Service Explorer to publish a business to a private UDDI registry, you will get a user password mismatch if you use both a userid and a password.

Workaround:

Enter the userid without a password; this will allow you to publish the business.

4.17 When profiling in version 7.0.0.3 on WebSphere Application Server V6.1, using the integrated Agent Controller (IAC) or an installed Rational Agent Controller V7.0.2, you might get a warning message

When profiling in version 7.0.0.3 on WebSphere Application Server V6.1, using the integrated Agent Controller (IAC) or an installed Rational Agent Controller V7.0.2, you might get a warning message:
"Could not resolve the launch delegate of the data collector org.eclipse.tptp.trace.ui.jvmpiMechanism."

Workaround:

The message is a warning only and is caused by an obsolete extension point. Close the dialog box and continue profiling.

4.18 The .apt_generated source folder is not restored as the source folder after being deleted

When the Feature Pack for Web Services 1.0 facet is enabled, a folder called .apt_generated is created in the Web project.
If the folder is accidentally deleted, it will be restored by Eclipse automatically but it no longer behaves as a source folder. This results in
the classes in this folder not being built into the Web project's classpath, and it may cause ClassNotFound exceptions after the Web project is deployed.

Workaround:
After the folder is deleted, it will not be present in the J2EE perspective. Follow these steps to restore the source folder:

Open the Resource perspective. You should see the .apt_generated folder which is automatically regenerated.

Open the .settings/org.eclipse.wst.common.component file

From the Source view, delete the following line:
<wb-resource deploy-path="/WEB-INF/classes" source-path="/.apt_generated"/>

Right-click the project and select Properties > Java Build Path.

On the Source tab, add .apt_generated to the list of Source folders.

4.19 Sample JSPs generation not supported if workspace has stub runtime only

If the workspace has only stubs as installed server runtimes, sample JSPs will not be generated for the client proxy. This is applicable for both JAX-RPC and JAX-WS client proxies. If you launch the Web Service client wizard to generate a client and sample JSPs, the wizard will display a warning message on the first page of the wizard stating that there are only stub runtimes. Although the client wizard allows you to continue, sample JSPs will not be generated by the wizard even if you select to test the client. If you right-click the client proxy Java class and select Web Services > Generate Sample JSPs for a JAX-RPC client or Web Services > Generate JAX-WS 2.0 JSPs for a JAX-WS 2.0 client, there are two outcomes:

Nothing displays if the workspace has a remote server defined. The client application will be automatically published to the remote server.

An error message displays if the workspace has no remote server defined. The message states that there are only stub runtimes in the workspace.

Workaround:

Open Preferences > Server > Installed Runtimes.

Click Add and add a non-stub server runtime definition.

Generate your sample JSPs.

4.20 Dynamic WSDL may not be available if local WSDL file is not generated and Web service is not running on a server

With the new JAX-WS Web services, not all the Web service enabled projects will contain a WSDL file. This will occur if you have chosen to create a Web service without generating a WSDL file, and if the server referenced by the Web service module is not running and thus the dynamic WSDL is not available. To support the JAX-WS Web services tooling - specifically generating a Web service skeleton, generating a Web service client, or testing the Web service using the Web Services Explorer - a WSDL file is generated in the temporary directory.

Workaround:
If the WSDL file is not available to the Web services tools, the SOAP address URL in the temporarily generated WSDL will be REPLACE_WITH_ACTUAL_URL. Using this WSDL, you can still generate
a functional skeleton Web service. In the case Web Services Explorer or a Web service client, you may be able to look at the generated code or the SOAP envelope.

4.21 JSR-109 and JAX-WS Web Services tree node might not update, even after a refresh

When you create, change, or delete a JSR-109 or JAX-WS Web service or Web service client with the IBM WebSphere Application Server Toolkit, the corresponding Web services tree node might not update to reflect the change. This problem occurs even if you perform a manual refresh.

Workaround:
In most cases, restarting the Application Server Toolkit workspace corrects the problem. If the tree node for the JSR-109 or JAX-WS Web services is still not updated with the changes, then perform the following actions:

Close all of the perspectives in the workbench by clicking Window > Close all perspectives.

Re-open the Java 2 Platform Enterprise Edition (J2EE) perspective by clicking Window > Open perspective > J2EE.

4.22 The Web Services Explorer does not support SOAP 1.2 WSDL

The Web Services Explorer in the IBM® WebSphere® Application Server Toolkit cannot invoke Web services with SOAP Version 1.2 bindings. When the tool encounters a Web Services Description Language (WSDL) file with SOAP V1.2 bindings, the Web Services Explorer displays the SOAP V1.2 bindings as unsupported.
This issue applies to the Web Services Feature Pack feature.

Cause:

This is a limitation in the current design of the Web Services Explorer.

Workaround:

To test a SOAP V1.2 Web service, you can use one of the following methods:

Create a Java API for XML-Based Web Services (JAX-WS) Web service client and use the JAX-WS 2.0 sample JavaServer Pages (JSP) files.

Use the Universal Test Client to test the Web service.

4.23 A failure is not obvious when publishing a J2EE enterprise application to a server if the Web Services Feature Pack is installed

If an error scenario is encountered when publishing a Java 2 Platform, Enterprise Edition (J2EE) enterprise application to a server, the publishing task might fail without displaying any error message. Therefore, the publish task might seem to finish successfully. This scenario occurs only when the Feature Pack for Web Services is installed.

If the publishing task fails without warning, then the server status shows "Republish" and a status is not shown for the J2EE enterprise application in the Servers view. The application status should say "Started". Also, the application is not listed in the Administrative Console for IBM WebSphere Application Server.

Workaround:
To identify the root cause for why the publishing process for the application failed, open the file named .log, which is located in the workspace/.metadata directory.
The workspace variable is the name of your workspace directory
Correct any errors shown in the .log file and re-publish the application.

4.24 A NullPointerException error occurs when running the bottup-up Web service wizard if J2EE dependencies are not set up correctly for a utility project.

A NullPointerException error occurs when running the bottom-up Web service wizard if your Web project includes a Java bean which uses classes in a Java utility project, and both the dynamic Web project and Java utility project reside in the same EAR.
The error message starts similar to the following text:
Errors occurred during wsgen.
Note:        ap round: 1
Problem encountered during annotation processing;
see stacktrace below for more information.
java.lang.NullPointerException
at com.sun.tools.ws.processor.modeler.annotation.WebServiceAP.isSubtype(WebServiceAP.
java:416)
Workaround:

To resolve this issue, perform the following steps:

Right-click the EAR project and click Properties > J2EE Module Dependencies. Ensure that both the Web project and Java utility project are selected in the Available J2EE modules list, and then click OK.

Right-click the Web project and click Properties > J2EE Module Dependencies.

Click the Web libraries tab, The utility project should be in the list of Web Library projects. Select the utility project and then click OK.

Re-run the bottom-up Java bean Web service wizard.

4.25 TCP/IP monitor is not shown on the server's monitoring properties page

After creating a Web service client with TCP/IP monitoring enabled, the TCP/IP monitor is set up but it does not show up in the server's monitoring properties page (which is accessed by right-clicking on the server in Servers view and selecting Monitoring > Properties).

Workaround:

To view or change the settings for the TCP/IP monitor, the open the TCP/IP monitor page (Window > Preferences > Run/Debug > TCP/IP monitor) page instead; the TCP/IP monitor will be shown on this page.

4.26 Correction to TCP/IP monitor information in JAX-WS Do and Learn tutorial

In the "Do and Learn" section of the Tutorial Gallery, there is a tutorial titled "Creating a secured JAX-WS Web Service from a WSDL file". Lesson 3, step 7 of this tutorial instructs you to confirm the TCP/IP monitor is set up by right-clicking on the server in Servers view and selecting Monitoring > Properties. However, when the properties page displays, the TCP/IP monitor is not shown even though it is set up properly.

Workaround:
Open the TCP/IP monitor page (Window > Preferences > Run/Debug > TCP/IP monitor) instead. You can view the TCP/IP monitor on this page.

4.27 Rational Functional Tester V7.0.0.2 doesn't work when run as non-root users on Linux

The problem occurs when Rational Functional Tester V7.0.0.2 is installed as root, but started as a non-root user. When Rational Functional Tester loads up, the Functional Test Projects view does not load and shows "Unable to create view: null argument:" error message. You may also see problems creating new Functional Test Projects with the same error message.

Workaround:

To resolve this error, you must do one of the following:

Run Rational Functional Tester V7.0.0.2 for the first time by the root user; or

Ensure that the <RFT install dir>/FunctionalTester/bin directory has write permission for the non-root user.

4.28 Projects might not be added to the server when completing wizards such as the Run On Server wizard.

In the following wizards, there is a page called Add and Remove Projects that enables you to add projects to the server:

New server (In the Servers view, right-click and select New > Server)

Run on server (Right-click a project and select Run As > Run on Server)

Debug on server (Right-click a project and select Run As > Debug on Server)

Profile on server (Right-click a project and select Run As > Run on Server)

On the Add and Remove Projects page, if you add projects to the server and then complete the wizard by selecting Finish while still on this page, then the projects are added to the server as expected. However, if you add projects to the server on the Add and Remove Projects page, click Next, and then click Finish on the subsequent page, the projects are not added to the server.

Workaround:

To add projects to the server using the wizards mentioned above, perform one of the following tasks:

Complete the wizard by clicking Finish on the Add and Remove Projects page.

If you complete the wizard without adding projects to the server, you can manually add projects from the Servers view (right-click the server and select Add and Remove Projects from the context menu).

4.29 NullPointerException error thrown at runtime when using an EJB reference from a Web Module due to missing JNDI binding information

If you use the Web Application editor to add an EJB reference, the JNDI binding information might be missing, causing a NullPointerException error. This might happen if both the Web module and EJB module are contained within the same enterprise application.

Workaround:

Manually add the JNDI binding information to the EJB reference with the Web Application editor. The correct format for the binding information is similar to:

ejb/the fully qualified EJB home class name

For example, if the EJB home class is foo.bar.TestHome, then the default bindings information would be:

ejb/foo/bar/TestHome

4.30 Incorrect version of WebSphere Application Server shows in the Administrative Console after uninstalling IBM WebSphere Application Server Version 6.1 Feature Pack for Web services feature

Installing the IBM WebSphere Application Server Version 6.1 Feature Pack for Web services feature (which is required when installing the Web services feature pack feature) updates the installed WebSphere Application Server feature version to 6.1.0.9. This version number is displayed on the Welcome page of the WebSphere Application Server Administrative Console. If you uninstall the WebSphere Application Server Version 6.1 Feature Pack for Web services feature by uninstalling the version 7.0.0.3 fix pack, then the version number might still display as 6.1.0.9.

Only the Welcome page in the WebSphere Application Server Administrative Console displays the incorrect version. The version information reported in other places, such as by running the versionInfo command, will be correct.

4.31 Long delays when publishing applications with large JAR files in a Web module to a WebSphere Application Server V6.1 with Feature Pack for Web Services

When an application contains many JAR files or a large sized JAR file in the WEB-INF/lib folder of a Web module, the application may take a long time to publish to the server. This problem will happen on a WebSphere Application Server v6.1 with Feature Pack for Web Services installed on remote servers. In addition, the problem occurs on local servers when the publishing option, Run server with resources on Server is selected. For example, an application with 15 JAR files with a total file size of 17 megabyte in the WEB-INF/lib directory may take around 15-20 minutes to publish the application.

During the publishing of the server, in the Servers view the server remains in the Publishing state and appears as if the server has hung. However, the publish should complete and until the publish completes the state of the server changes to Synchronized.

You might experience similar performance problems with other tasks, such as running applications with JavaServer Faces (JSF).
Workaround:

This is a known problem in the WebSphere Application Server v6.1 with the Feature Pack for Web Services and there is an interim fix available for the server. To fix the problem occurring on the server, visit the following link: http://www.ibm.com/support/docview.wss?rs=180&uid=swg21263650

5.0 IBM Rational Software Support

IBM Rational Software Support provides you with technical assistance.

For contact information and guidelines or reference materials that you will need when you require support, read the IBM Software Support Handbook at http://techsupport.services.ibm.com/guides/handbook.html.

For FAQs, lists of known problems and fixes, and other support information, visit the product support page for Rational Application Developer at www.ibm.com/software/awdtools/developer/application/support/index.html

For product news, events, and other information, visit the product home page for Rational Application Developer at www.ibm.com/software/awdtools/developer/application/.

Before you contact IBM Rational Software Support, gather the background information that you will need to describe your problem. When describing a problem to an IBM software support specialist, be as specific as possible and include all relevant background information so that the specialist can help you solve the problem efficiently. To save time, know the answers to these questions:

What software versions were you running when the problem occurred?
Do you have logs, traces, or messages that are related to the problem?
Can you reproduce the problem? If so, what steps do you take to reproduce it?
Is there a workaround for the problem? If so, be prepared to describe the workaround.

6.0 Notices and trademarks

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 documentation 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 documentation. The furnishing of this documentation 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 OR CONDITIONS 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.

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:

Intellectual Property Dept. for Rational Software
IBM Corporation
3600 Steeles Avenue East
Markham, Ontario
Canada L3R 9Z7

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

Trademarks and service marks

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

CICS
ClearCase
DB2
IBM
Rational
RequisitePro
WebSphere
zSeries

Intel is a registered trademark of Intel Corporation or its subsidiaries in the United States, other countries, or both.

Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both.

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

Microsoft and Windows are trademarks of Microsoft Corporation in the United States, other countries, or both.

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