Fixpack Readme

IBM WebSphere Portlet Factory 6.0.0.2

This edition applies to version 6.0.0.2 of IBM WebSphere Portlet Factory and to all subsequent releases and modifications until otherwise indicated in new editions.

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

CONTENTS:

1. ABOUT THIS RELEASE
2. FIXPACK INSTALLATION INFORMATION
3. FIXPACK REMOVAL INSTRUCTIONS
4. CONTACTING CUSTOMER SUPPORT
5. NOTICES AND TRADEMARKS

1.0 About this Release

1.1 Fixes Contained in this Fixpack

Ref 27823 -- Linked model regeneration issue: When linked models are regenerated, the regenerations are not cached. This has a negative impact on performance. Model regeneration is now cached so that only a single regeneration of each model at the top level is performed for improved performance.

Ref 27891 -- Debug Tracing Builder "Additional debug output" input issue: The "Additional debug output" Debug Tracing Builder input does not generate any output. The "Additional debug output" Debug Tracing Builder input now functions properly.

Ref 28002 -- Service Operation Builder "Specify Input Values" input errors with SAP and Domino issue: When the Service Operation Builder "Input Field Mapping" input is set to "Specify input values," calling an SAP function that has a nested input structure causes a Java exception. In Domino, an update operation with "Input Field Mapping" input set to "Specify input values" fails to update the document correctly. Both of these problems have been resolved.

Ref 28035 -- File encoding issue: Portlets may not render correctly due to an internal character encoding or decoding error. This problem can occur when Portlet Factory is running on a JVM where the default platform character encoding is not UTF-8, and non-ASCII characters are directly inserted into a page rather than being referenced by an indirect reference (for example, by using Data Column Modifier to specify non-ASCII text for a column header). This problem has been resolved.

Ref 28090 -- "Profile Row of Inputs" scrolling issue: When profiling a row in a list with many columns, data flows off the screen. It is now possible to scroll. It is now also possible to resize the screen in which the list is displayed.

Ref 28113 -- Support for nested table results in SAP Builder issue: The SAP Remote Function Call Builder returns incorrect XML results for nested tables. The Builder now returns correct results.

Ref 28117 -- Null pointer exception initializing resource bundles issue: An internal code change in the way Portlet Factory initializes resource bundles causes Java to throw a null pointer exception. This problem has been resolved.

Ref 28127 -- Excel Export Builder exception on iSeries issue: The Excel Export Builder causes a Java exception on iSeries. This problem has been resolved.

Ref 28137 -- Excel data display in SSL issue: In SSL environments, exported Excel data cannot be displayed in Internet Explorer. This problem has been solved. This problem has been resolved.

Ref 28143 -- Field values display in a model or portlet results page issue: Field values do not display correctly in a model or portlet when the model meets all of the following conditions:

  1. The model has a link or button (or similar control) with "Action Type" set to link to an action, and the action takes at least one argument.

  2. The link or button (or similar control) passes an indirect reference to the source data as an argument.

This problem has been resolved.

1.2 - APARs Addressed by this Release

LO16485 -- Resolves fix Ref 28127 above.

LO16648 -- Resolves fix Ref 28143 above.

top

2.0 Fixpack Installation Information

2.1 Hardware Requirements

Refer to WebSphere Portlet Factory 6.0 Release Notes.

2.2 Software Requirements

Refer to WebSphere Portlet Factory 6.0 Release Notes.

In addition, note that Portlet Factory now supports all versions of the zOS operating system that are supported by WebSphere Portal 5.1.

2.3 Fixpack Installation Instructions

To apply this fixpack to an installed copy of WebSphere Portlet Factory 6.0:

  1. Exit WebSphere Portlet Factory 6.0 Designer.

  2. Extract the contents of the fixpack to a convenient location on the machine where Portlet Factory Designer is installed.

  3. Locate and run the Fixpack.exe file.

  4. Follow the instructions in the fixpack installation program to apply the fixpack to the installed version of WebSphere Portlet Factory 6.0.

Note: To successfully install this fixpack, you must know the path where Portlet Factory is installed.

2.3.1 Verify Fixpack Installation

To verify that the fixpack was correctly installed:

  1. Start Portlet Factory Designer.

  2. In the Eclipse Help menu, select About Eclipse SDK.

  3. In the About Eclipse SDK window, click the IBM WebSphere Portlet Factory icon.

  4. In the About Eclipse SDK Features screen, note that the Portlet Factory Designer version is 6.0.0.2.

2.4 Upgrading a Project

Once you have applied this fixpack to Portlet Factory Designer, you must modify previously created projects to incorporate fixpack improvements. To incorporate fixpack changes into a project, follow these steps each of which gives you the option of canceling the operation without making changes:

  1. Start Portlet Factory Designer and load a project.

  2. In the project's right-click menu, select WebSphere Portlet Factory Project > Modify.

  3. When prompted, select OK to initiate the process of overwriting existing product files or adding new ones. Project Factory displays a confirmation box. Click OK to continue.

  4. The New Project Wizard Add Feature Sets page is displayed. Note that Feature Sets previously installed in the project are selected. These Feature Sets must now be reinstalled to pick up fixpack changes.

  5. Click Next to install or upgrade selected Feature Sets.

  6. As Additional Project Wizard screens are displayed, click Next to accept existing project settings.

  7. Click Finish to complete project modification and upgrade. When you click Finish, Portlet Factory begins the actual modification of the project files. When the first file that the process would overwrite is encountered, Portlet Factory displays a dialog box that prompts you to choose to overwrite the file (Yes), retain the file in its current form (No), overwrite all existing files (Yes to All), or leave all existing files in their current state (No to All).

  8. Restart the WebSphere Application Server to insure project changes are picked up in the deployed project WAR file.

3.0 Fixpack Removal Instructions

To remove this fixpack from an installed copy of WebSphere Portlet Factory 6.0:

  1. Halt Portlet Factory Designer.

  2. Open the Windows Control Panel and select Add or Remove Programs.

  3. In the Installed Programs list,  select the WebSphere Portlet Factory Fixpack 6.0.0.2 program.

  4. Click Change/Remove to start the fixpack uninstall program.

  5. Click Next to uninstall the fixpack.

3.1 Removing Fixpack Artifacts from a Project

Follow these steps to remove fixpack enhancements and changes to the software. Note that you will have to modify your projects by hand if you have made any changes to them between installing and uninstalling the fixpack as you would between any version change.

  1. Remove the fixpack from Portlet Factory Designer. (See section 3.0 above.)

  2. Start Portlet Factory Designer and load the project.

  3. In the project's right-click menu, select: WebSphere Portlet Factory Project > Modify.

  4. When prompted, select OK to initiate the process of restoring 6.0.0.1 product files. Project Factory displays a confirmation box. Click OK to continue.

  5. The New Project Wizard Add Feature Sets page is displayed. Note that Feature Sets previously installed in the project are selected. These Feature Sets must now be reinstalled to override fixpack changes.

  6. Click Next to restore the selected Feature Sets.

  7. As Additional Project Wizard screens are displayed, click Next to accept 6.0.0.1 project settings.

  8. Click Finish to complete project rollback. When you click Finish, Portlet Factory begins the actual modification of the project files. When the first file that the process would overwrite is encountered, Portlet Factory displays a dialog box that prompts you to choose to overwrite the file (Yes), retain the file in its current form (No), overwrite all existing files (Yes to All), or leave all existing files in their current state (No to All).

  9. Restart the WebSphere Application Server to insure project changes are picked up in the deployed project WAR file.

top

4.0 Contacting Customer Support

As of May 15th 2006, all support for Bowstreet and new IBM derivative products is being provided through IBM Customer Support. All Bowstreet email and electronic incident submission systems have been replaced by the IBM Electronic Service Request (ESR) system.

In addition, new support forums have been created on IBM developerWorks. Included are 8 different forums for the IBM Portlet Factory and 4 forums for the IBM Workplace Dashboard. These forums are available to external customers and they will be monitored by IBM resources. Links to these forums are included in the support announcement.

4.1 Voice Support

Call 800-IBM-SERV (800-426-7378) in the US and Canada. When calling from outside the US or Canada, please call the appropriate number below:
Europe, Middle East and Africa: +44(0)1475-897169
Inside Australia: 131-426 or 1-800-257373

4.2 Electronic Support

You can directly submit support tickets to IBM. For more information on the IBM ESR sytem, refer to: ibm.com/software/support/probsub.html

top

5.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 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 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-0032, 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.

Copyrights and Acknowledgments
Licensed Materials - Property of IBM
Copyright IBM Corp. 2006 All Rights Reserved.
US Government Users Restricted Rights - Use, duplication or disclosure restricted by SGA ADP Schedule Contract with IBM Corp.

Supplemental Copyrights and Acknowledgments
The following Copyrights and Acknowledgments apply to various software components included in IBM WebSphere Portlet Factory, but neither created nor owned by IBM.
This offering is based on technology from the Eclipse Project (http://www.eclipse.org/).
This product includes software developed by the Apache Software Foundation (http://www.apache.org).
Portions of this software provided by JDOM. Copyright (C) 2001 Brett McLaughlin & Jason Hunter. All rights reserved.
Portions of this software provided by the membership of the XML-DEV mailing list. You can obtain a copy of the SAX copyright status at http:// www.megginson.com /SAX/.
The following terms are trademarks of International Business Machines Corporation in the United States, other countries, or both:
Cloudscape
IBM
Lotus
WebSphere
Workplace

top