Fixpack Readme

IBM WebSphere Portlet Factory Version 6.0.1.2 (fixpack 2 for 6.0.1)

This edition applies to version 6.0.1.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 2007. All rights reserved. US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

Contents

• About this release
• APARs addressed in this fixpack
• Fixpack installation
• Fixpack removal
• Contacting customer support
• Notices and trademarks

1.0 About this Release

This document contains information about updates to WebSphere Portlet Factory provided by the fixpack for Version 6.0.1. This fixpack includes fixes and updates for Portlet Factory Version 6.0.1. For details about previous updates and fixes, refer to information provided at the download page for each fixpack. The download pages are available from the support site at the following URL:

http://www.ibm.com/support/search.wss?rs=3044&tc=SSRUWN%2BSS3LP9&q=fixpack

1.1 Fixes contained in this fixpack

The following defects are addressed by this fixpack.

• Ref 29933    Profile Selection: "depth" of profile were not being used correctly to resolve inherited profile for role.

  If more than one profile applies for a selected profile segment, the "most derived" (lowest in the hierarchy) profile will be selected. This fix reflects how the documentation describes profile selection.

• Ref 29515  The SAP builder did not support the use of mshost for server connection.

  The use of mshost and ashost are now supported if properly configured.

• Ref 29773  In the Transform Sort Builder, there was incorrect text in the drop down menu for numeric sorting.

  The Transform Sort builder now sorts correctly based on numerical values. If you have existing models that use the Transform Sort builder, it may be necessary to open the builder calls in the Designer, and re-select "Number" as the Compare Type, and then save the model. In addition, if you are invoking the Transform Sort builder through a Rich Data Definition file, you should change the comparison type to "Numbers" in the data definition XML file.

• Ref 30033  Profile Sets in DB could not be migrated with DB2 9.1 drivers.

  Profile sets can now be migrated to DB2 9.1.

• Ref 30040  Session size diagnostics did not work correctly.

  The session size diagnostic tool was not logging information to the sessionsize.csv file in the WEB-INF/logs directory. The session size tracing functionality now logs the information.

• Ref 30131  SAP builder caused excessive calls to SAP for fetching metadata.

  Calls now have been significantly reduced and performance has been improved.

• Ref 30196  SAP Batch Input builder did not work on newer versions of SAP.

  The new default function RFC_CALL_TRANSACTION_USING is now used by the Batch Input builder. Developers who use the older version of SAP (4.6C) will need to manually call the older RFC_CALL_TRANSACTION function. You can set this property in overrides.properties: bowstreet.sap.batch.useOldBatchRfc=true

• Ref 30112  PeopleSoft: PSSessionFactory.validateServer did not work with multiple server names.

  You can now specify multiple PeopleSoft server instances in the PeopleSoft server connection properties file. For example, you can specify multiple server instances in the case that one is down. The first active server found will be used. The property value should look similar to: HostServer=pplsoft_1:9000,pplsoft_2:9000

• Ref 29991  PeopleSoft: Issues with a property called "GetDummyRows" that allows or prevents dummy rows from being automatically inserted into empty scrolls.

  We now support the ability to set the "GetDummyRows" property for a Component Interface.

• Ref 30305  PeopleSoft: Enhanced runtime PeopleSoft diagnostic tracing.

  The logging should only be enabled during model development since it can generate large amounts of trace data and impact overall model performance.

• Ref 30287  Using Print page Contents and Excel Export on same tag caused problems.

  Using Print Page Contents and Excel Export on same tag is now supported. Developers should place Print page Contents below Excel Export in the outline for best results.

• Ref 30236  Schema Parsing - A null pointer exception occurred when a null basetype exists in the schema.

  Schemas that use types with no base type (For example: xsd:anySimpleType) are now parsed correctly.

• Ref 30346  There was an exception loading schema with double-byte characters

  Schemas with double-byte characters are now parsed correctly.

• Ref 30372  Non-ascii characters returned by Web Services could be improperly encoded.

  When non-ASCII characters were being encoded as numerical character references (for example: "&#123)", under some circumstances, the leading ampersand could get encoded twice, such that the sequence then appeared as "&#123". This has been fixed.

• Ref 30004  Add a way to stop model execution when an exception occurs.

  The new com.bowstreet.webapp.util.TerminateProcessingException can be thrown by an error handler to stop further processing of the request.

• Ref 30374  Data Page schema parsing with recursive elements causes null exception.

  Recursive schemas should now be correctly parsed without producing null pointer exceptions.

• Ref 30395  Dynamic classloading not working correctly with java2 security turned on..

  To support Java2 security for dynamically loaded classes (eg, work/classes and work/lib) which may execute protected operations (eg, file read/write or dynamically loading yet another class), this fixpack provides a dynamic classloader option that must be set to true in your project's WEB-INF/config/override.properties file:
  
  bowstreet.classloader.copyProtectionDomain=true
  
  In addition, if your WebSphere Portal has Java2 security turned on, then you'll need to include a was.policy file in your projects's WebContent/META-INF folder, with the following content:

  grant codeBase "file:${application}" {
  	permission java.security.AllPermission;
  };
  

1.2 APARs addressed in this fixpack

2.0 Fixpack installation

2.1 Hardware requirements

Refer to WebSphere Portlet Factory 6.0.1 Release Notes.

2.2 Software requirements

Refer to WebSphere Portlet Factory 6.0.1 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:

1. Exit WebSphere Portlet Factory 6.0.1 Designer. Then, note the path where Portlet Factory is installed. Supply this information during the fixpack installation.

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

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

2.4 Upgrading a project

After you apply this fixpack to Portlet Factory Designer, modify previously created projects to incorporate fixpack improvements. To incorporate fixpack changes into a project, follow these steps:

1. Start Portlet Factory Designer and load a project.

2. In the navigator, right-click project and click WebSphere Portlet Factory Project > Upgrade Project Version.

3. When prompted, click OK. The project is upgraded to use the latest plug-in components.

4. Click Yes to deploy the project and upgrade the deployed development and portlet WAR files.

3.0 Fixpack removal

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

1. Close 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.1.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.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.1 project settings.

8. Click Finish to complete project rollback.

   Portlet Factory modifies the project files. When the first file that the process would overwrite is encountered, Portlet Factory prompts you 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 system, refer to the following URL:

http://www.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