© Copyright International Business Machines Corporation 2003, 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 releaseThis fix pack contains fixes to the version 6.1.1 release of IBM® WebSphere® Application Server Toolkit.
The following known limitations or problems that were listed in the version 6.1.1 release notes have been fixed in this release:
- In J2EE extensions, a validation error occurs for a compound primary key that is generated from IBM xdoclet annotations.
- In J2EE extensions, IBM xdoclet annotations do not always update the JNDI name correctly.
- In J2EE extensions, an invalid value for destination type occurs when using IBM xdoclet annotations
- In Software Development Platform core, some User Interfaces are displayed in the platform locale language even if only English is selected in installation by IBM Installation Manager.
- In Software Development Platform core, if you search the online documentation in the Help window (Help > Help Contents) and click one of the results, the content frame displays an XML source file rather than something readable.
- In WebSphere server tools, the New Server wizard might not retrieve the correct port information.
- In WebSphere server tools, the Profile Management tool does not work under a 64 bit processor.
- In WebSphere server tools, publishing large applications is slower than in the previous version.
- In WebSphere server tools, a TargetInvocationException error might occur when using the Table and Data Source Creator wizard
- In WebSphere testing and publishing tools, EJB jar changes are not picked up after running EJB through Universal Test Client (UTC).
- In User Assistance, Welcome pages may show errors or unexpected behavior.
- If you have an instance of the WebSphere Application Server Toolkit running, please shut it down while the update is being installed.
- Start Rational Product Updater:
- On Windows® operating systems, click Start > Programs > IBM WebSphere > Application Server Toolkit V6.1.1 > Rational Product Updater.
- On Red Hat Enterprise Linux® 3.0 (GNOME desktop environment), open the main menu and click Programming > Rational Product Updater v6.0.1.
- On SuSE Linux Enterprise Server 9.0 (K Desktop Environment), open the main menu and click IBM Rational > Rational Product Updater v6.0.1.
Note: On Red Hat Enterprise Linux 3.0 and SuSE Linux Enterprise Server 9.0, if you use a desktop environment other than the default, the product shortcuts might not appear in the default location.
Note: The IBM Rational Product Updater requires luanching as a root user.
- Click Find Updates.
If Rational Product Updater requires an update, you are prompted to install it before you can continue. Click OK. Rational Product Updater installs the update, restarts, and retrieves a list of available updates.- By default, all available updates are selected. Ensure that you select WebSphere Application Server Toolkit V6.1.1 Fix Pack 1.
- Click Install Updates.
- In the License Agreement window, read the license agreement and, if you accept the terms and conditions, click I accept the terms in the license agreement; then click OK.
Depending on the speed of your computer processor, the amount of RAM, and the speed of your Internet connection, the update might take an extended period of time to download and install.
After the installation is complete, Rational Product Updater lists the installed updates on the Installed Products page.- Close Rational Product Updater.
For hardware requirements for this interim fix, refer to the WebSphere Application Server Toolkit Hardware Requirements in the readme packaged with 6.1.1.
This interim fix can be installed on top of WebSphere Application Server Toolkit, Version 6.1.1.
This section describes known limitations and problems specific to this release, and any workarounds that are available.
The "Developing data access applications" section of the information center incorrectly contains a reference to functionality supporting the deployment of JAR files for Java™ stored procedures, in the topic called "Routine and JAR file deployment."
JAR file deployment is not supported, and the reference should be ignored. The rest of the information in this topic is accurate.
If you attempt to publish an EJB project containing more than one source folder (for example, an annotation project that has an alternative source folder), publishing fails with errors.
You might see errors similar to the following example in the Console view:
[1/11/07 15:28:36:906 PST] 00000027 SystemErr R
*** ERROR ***: Thu Jan 11 15:28:36 PST 2007 org.eclipse.jst.j2ee.commonarchivecore.internal.exception.OpenFailureException: IWAE0023E Unable to open module file "AuctionV60EJB.jar" in EAR file "C:\v7001workspaces\7001Week2\AuctionV60EAR"
Stack trace of nested exception:
org.eclipse.jst.j2ee.commonarchivecore.internal.exception.OpenFailureException: IWAE0006E Archive is not a valid EJB JAR File because the deployment descriptor can not be found (case sensitive): META-INF/ejb-jar.xmlWorkaround: Edit the looseconfig.xmi file (a generated file) using the following steps:
If the server is still running, restart the server for the changes to take effect.
- On your computer, navigate to your workspace directory open in an editor the file /.metadata/.plugins/com.ibm.etools.wrd.websphere/looseconfigurations/EAR project name/looseconfig.xmi, where EAR project name is the name of your EAR project.
- Change the two path attributes binariesPath and resourcesPath so to reference "ejbModule" instead of "gen/src" for the EJB jar file.
- Save your changes.
You should now be able to successfully publish the EJB.
Use of this feature is subject to the same terms and conditions which govern the use of the Product which included this feature.