IBM WebSphere Integration Developer Fix Pack 6.0.2.2

for WebSphere Integration Developer 6.0.2

Welcome to the IBM^® WebSphere^® Integration Developer Fix Pack 6.0.2.2 for WebSphere Integration Developer 6.0.2.

1.0 Prerequisites
2.0 Product fix history
3.0 Customer support
4.0 Notices and trademarks

1.0 Prerequisites

You must install IBM WebSphere Integration Developer 6.0.2 before installing the fix pack. If you still need to install version 6.0.2, the download is located at the WebSphere Integration Developer support site.

2.0 Product fix history

This fix pack contains many significant updates, corrections and performance improvements to WebSphere Integration Developer 6.0.2. The following list is an overview of most of the components that have been updated with a description of the more significant problems addressed by the fix pack. APAR numbers, if applicable, are in parentheses.

There have been many minor functional and user interface corrections to the wizards and editors. There have also been many but minor documentation corrections. These minor updates are not noted.

Adapters: The WebSphere Adapters for JDBC, Flat Files and SAP Software have been updated with corresponding fix packs.
Assembly editor: Components in the editor were not being correctly serialized in the assembly editor. The problem has been addressed. Component names and the name of the file containing the component should be the same. But the editor failed to prompt when, in the physical resources view, an attempt was made to rename a file, thus creating an inconsistency. The problem has been addressed. Even though an error was corrected, the assembly editor did not remove the error label. The problem has been fixed. In the physical resources view, you could delete a reference to an component in a file but then not save the change. The assembly editor would incorrectly delete the wire to the component as if the deletion had been saved. This problem has been fixed. A class cast exception could be issued in the log file after wiring a reference to a new component. The problem has been fixed. The refactoring performance has improved when renaming an import or export. Refactoring the name of an export could result in another export being created with the original name. This problem has been fixed. Binding information in the properties view of one module could disappear after switching to the assembly editor in another module and then returning to the original module. This error has been corrected.
Business object editor: Changing a business object attribute in the business object editor did not change the underlying element in the file. The problem has been corrected. You were previously prevented from referencing an element with an anonymous complex type. This restriction has been removed. Selecting a business object attribute could result in a null pointer exception in the log file. This problem has been fixed.
Business object mapping editor: Arrays are now supported in the editor (APAR JR26716). Deleting transformations could result in incorrectly changing the numbers in a sequence (APAR JR26770). This problem has been fixed. Refactoring a business object map did not update the underlying elements in the file for the map correctly. The problem has been fixed. The editor failed to detect if some custom Java code in the business object map had been modified by a user. The problem has been fixed. Transformations were incorrect after using refactoring to rename an attribute. The problem has been fixed. Inputs and variables in the visual snippet editor of the business object mapping editor were not being updated after refactoring renamed an artifact. This problem has been fixed. Refactoring a namespace that was null (a nameless namespace) caused an error. This problem has been fixed. The properties displayed by selecting the cardinality tab could be incorrect if the map contained two transformations. The problem has been fixed.
Business state machine editor: Adding a Java import to a business state machine could fail; that is, the Java code would not get added to the business state machine. The problem has been fixed. Renaming artifacts with the refactoring function could cause a message indicating an internal error. The problem has been fixed. Breakpoints set on a visual snippet could behave inconsistently when testing the business state machine. This problem has been fixed.
Business process editor: Files created when a business process added inline human tasks activities were not being removed (APAR JR26581). The problem has been corrected. In a choice activity, conditions added to a case attribute could disappear though a save had been performed. The problem has been fixed. Renaming a reference partner with the refactoring function could fail in the business process editor. The problem has been corrected. A null pointer exception caused by a business process could occur when closing WebSphere Integration Developer. The problem has been fixed. Generating a business process also generates reference partners. Changing the name of a reference partner resulted in an error. This problem has been fixed. The timestamps in files were not updated after a refactoring operation. The problem has been fixed. Renaming a business process interface caused a null pointer exception in the log. The error has been corrected. Even though using a valid schema, a null pointer exception could be added to the log when selecting an element for a condition in a choice activity. This problem has been fixed. If a business process was defined in WebSphere Business Modeler then the generated business process activities uses a link construct to associate one activity with another. Removing a link name closed the business process editor. This problem has been fixed. Changing a microflow process to a long running process could result in errors. The problem has been fixed. Renaming a module with the refactoring function caused the editor to lose the error markers on its canvas. This problem has been fixed. A business process could appear in the navigation with a file type (for example, process.bpel). The problem has been corrected. Duplicate identification (ID) numbers could be generated into a business process file, which led to compile and deployment errors. The problem has been fixed. Incorrect file references from a business process to an XML Schema Definition (XSD) file in another module could occur. The problem has been fixed.
Business rules: Renaming a business object attribute with the refactoring function caused an error in the generated Java. This problem has been fixed. Refactoring a business object name and namespace caused the business objects' attributes used in business rules to have compile errors. The problem has been fixed. Moving a rule group to another folder failed to update the new location in the related component file. This problem has been corrected. In a decision table, a method could return an Object type instead of a DataObject type. The problem has been corrected. If you created a new interface while in the process of creating a rule group, you would see errors appear in the rule group and an exception when deleting the module containing it. This problem has been fixed. Creating one action rule in the ruleset editor and converting it to a template resulted in a false error message. The problem has been corrected. A decision table containing a float data type would change to a double data type when the table was converted to a template. The data type now remains as it should. Dragging a rule group to the assembly editor resulted in a null pointer exception. The problem has been fixed. Deleting a condition from a decision table could result in a failure to delete the condition and a null pointer exception. This problem has been corrected.
Debugger: The debugger could fail to refresh properly forcing a user to change perspectives and return to the debugger to continue (APAR JR25119). The problem has been fixed. Stepping through a Java code snippet in a business state machine could cause the debugger to hang. The problem has been fixed. A null pointer exception could be thrown after refreshing projects. The problem has been fixed. A breakpoint set in a visual snippet could later at runtime could lead to several types of exceptions. The problem has been fixed. Deleting an activity containing a set breakpoint created errors. The problem has been fixed. Closing WebSphere Integration Developer could result in a null pointer exception related to the debugger. The problem has been corrected. Setting a snippet breakpoint in a mediation flow could later at runtime, when debugging, cause a failure to return from the snippet to the mediation flow. The problem has been fixed. Breakpoint labels were not updated after refactoring functions were performed.
Deployment: Deploying a module with a single export could result in a no class definition found error. The problem has been fixed.
Enterprise service discovery wizard: If an operation name was changed by refactoring, the method attribute value in the method binding of an import did not get updated. The problem has been corrected. An export and an import is often created as a pair for a request-response operation. The import can be quickly created by dragging and dropping the export into another module. However, in doing so with an MQ JMS binding, a few errors were thrown. These problems have been fixed. Generating either an import or export with a JMS binding produced an error in the log file. The problem has been fixed. When using the enterprise service discovery wizard with a CICS RAR file, a Java Naming and Directory Interface (JNDI) name could not be retained. The problem has been fixed. When using the enterprise service discovery wizard with the Flat Files RAR, a number of values were not retained. The problem has been fixed. When using the enterprise service discovery wizard with an Email RAR, selecting the Show Advanced button during configuration added incorrect values into some fields. The problem has been addressed.
Event monitor: Updating the event monitor settings in the properties view and saving their contents, then deleting an operation in an interface, and finally returning the assembly editor and undoing the Add Event action, resulted in a null pointer exception. This problem has been fixed. Event monitor commands would appear in the human task editor when using the undo function. The problem has been fixed. Creating a new event definition created a no class definition found error in the log file. The problem has been corrected. After a refactoring function was used, error markers and properties exhibited unexpected behavior. The problem has been corrected.
Human task editor: Adding a section for a Business Process Choreographer explorer (BPC) client failed when the interface containing the input and output for the section contained fault messages. The problem has been addressed. In the BPC client, the input data values would not appear if the operation was using a document literal style. The problem has been fixed. Adding a human task to handle an error for a fault message could fail. The problem has been addressed. The editor could show incorrect values for user roles requiring the editor to be closed and reopened to return to the correct values. The problem has been addressed. If you configured email notification for an escalation, the default subject in the email should have had a colon (:) in the subject line. The subject line has been corrected. If a module had dependencies on two libraries and in each library was the same interface, a human task failed to validate the interface with an error when it was selected. This problem has been fixed. Creating a custom client for a human task resulted in exceptions in the log file. The problem has been fixed. When testing a human task using the JSF client and the BPC explorer, the data in the JSF client was inconsistent with the BPC explorer. This problem has been fixed.
Information center and samples: A new section, "WSDL binding styles", has been added describing the different styles and the advantages and disadvantages of each one. The refactoring section has been updated to indicate that refactoring now results in triggering another menu if referenced items should also be included in the refactoring operation. The limitations of refactoring with respect to Java components are specified. A link has been added to the WebSphere Process Server information center from the opening page in the WebSphere Integration Developer help. Some updates have been made to the human task editor to improve usability including more information on versioning human tasks. In the business object mapping editor section, an update describes the support for arrays and mapping between large and small business objects. A discussion of security considerations when publishing to the integration test client or the WebSphere Process Server has been added. A new topic, "Specifying the default time zone" in the "Testing modules and components" section clarifies time zone issues to be considered when testing applications. In the "Debugging components" section, a new topic called "Preparing for debugging when security is enabled" discusses the implications to debugging when security is enabled. The "Relationships and mapping" sample has been updated with corrections to the "Adding roles and key attributes" section.
Installation: A value of 'Beta' had been left in a registry (APAR JR26702). A correction has been made. When installing product updates with the Rational Product Updater (RPU), the installation would hang. The problem has been fixed. Rolling back an update resulted in missing components. The problem has been fixed.
Integration test client: Time zone values in the text client were not as expected by users (APAR JR26892). The problem has been corrected. Though the server would indicate it had stopped, the Java process would continue to run. The problem has been fixed. An SQL exception could be thrown when testing a human task component using the BPC explorer. The problem has been corrected. An array out of bounds exception was occasionally thrown while running an application. This problem has been fixed. The table requesting input values could fail to display all the input parameters. This problem has been addressed. After a refactoring function was used, the emulation editor did not refresh properly. The problem has been fixed. The values for an XML file could only be imported once. A correction has been made. There are a number of fixes that require the latest integration test client runtime update to be applied to the WebSphere Process Server. Installation of this fix pack will update the integration test client, so you only need to apply the update to your standalone server.
Interface editor: A null pointer exception could be thrown when generating a Web service binding. This problem has been fixed. Business objects created from an imported Web Services Description Language (WSDL) file could fail to appear in the Data Types folder. The problem has been fixed.
Interface mapping editor: A stack overflow error could occur when editing an interface map. The problem has been addressed. When using refactoring with this editor, the properties could fail to update. The problem has been fixed. A created interface map could fail to appear later in the user interface though the file was created. This problem has been corrected. On the SUSE operating system, an interface map could fail to be created. The problem has been fixed. When refactoring an interface map with two interfaces having the same name but in different namespaces, the refactoring function failed to detect the namespace difference. This problem has been fixed.
Java components: When adding a session bean into an assembly diagram and accepting the creation of a WSDL to Java mapper facade, errors would occur after following the recommendation to synchronize interfaces and references. The problem has been fixed. Double-clicking a Java implementation failed to launch the Java implementation in a Java editor. This Java capability is now enabled. False markers would be created when dragging a Java implementation containing Java API for XML-based RPC (JAX-RPC) types onto the assembly editor. A correction has been made.
Mediation flow editor: Numerous corrections were made to this editor. The most visible ones to a user are stated here. A business graph could fail to be active in a mediation module (APAR JR26868). This problem has been fixed. The outline view did not reflect the current state of a transformation (APAR JR26547). A correction has been made. Creating a mediation flow with a custom Java snippet could result in losing the Java when the mediation module was checked into a source configuration management system (APAR JR26877). The problem has been fixed. Hierarchical business objects in a mediation module were not displayed correctly (APAR JR26928).The problem has been fixed. A class cast exception could occur when working with an XSL transformation (XSLT) (APAR JR27069).The problem has been fixed. Deploying a service created with this editor took a long time. This problem has been addressed. Better error reporting after a refactoring operation produced unexpected results has been added. Rewiring an import in a mediation module created runtime errors. The problem has been addressed. After using refactoring to rename an operation in an interface of an XSL transformation (XSLT), several errors occurred. Several other problems related to refactoring when using this editor have been found. These problems have been corrected. XML maps (XMX) and custom mediation flows were not properly validated. The validation has been improved. When a mediation flow component and its implementation is out-of-sync, an error marker is created. However, the error marker would remain even when it was back in-sync. This problem has been corrected. Breakpoint markers failed to appear. The problem has been corrected. Regenerating the implementation of a mediation flow component could result in a null pointer exception. The problem has been fixed. In the edit properties dialog that opens when creating an endpoint lookup, the entered text could appear backwards. A correction has been made.
MQ data bindings: Some properties were missing from the MQ binding properties panel. The problem has been addressed. More consistency had been applied to the naming conventions between JMS and MQ bindings. An incorrect Coded Character Set Identifier (CCSID) error could occur when dragging an export into another module to create an import (often used to create an import and export pair to send and receive data).
Refactoring: When you refactor artifacts in WebSphere Integration Developer, there are often implications to other related items. For example, renaming an artifact may require some refactoring in another area that is referencing this name. When there is such an implication in any editor, you will be prompted and given the option to update the other affected artifacts. Numerous refactoring problems have been addressed in this fix pack. Refactoring problems related to specific editors have been added to the information on those editors.
Relationship editor: An unexpected dialog box for saving changes could open though only a renaming function in refactoring had taken place. This problem has been fixed.
Visual snippet editor: Creating a visual snippet in the mediation flow editor could result in a null pointer exception. The problem has been fixed. Incorrect Java code could be created from a visual snippet leading to a Java compilation error. This problem has been fixed. After a new property was added to an event, the custom visual snippet editor could fail to open. The problem has been fixed. Syntax errors could appear after the creation of a custom visual snippet even though there were no real syntax errors. The problem has been fixed.
WSDL importer: Importing a Web Services Descriptive Language (WSDL) file from from a Map Network Drive resulted in a hang. This problem has been addressed.

The following fixes to the WebSphere Process Server 6.0.2 runtime are included with this fix pack when you install the IBM WebSphere Process Server 6.0.2 test environment feature: JR26785 and JR26969.

Additional fixes for WebSphere Process Server 6.0.2 may be added at any time. Since these runtime fixes are not included with the WebSphere Integration Developer fix packs, check the recommended fixes and published APAR list on the WebSphere Process Server support page.

The following fixes to Rational Application Developer, which is included with WebSphere Integration Developer, have been added to this fix pack: JR26205, JR26408 and JR26760.

3.0 Customer support

The general product information for WebSphere Integration Developer, see the product home page. For FAQs, lists of known problems and fixes, and other support information, visit the Support page on the product home page.

4.0 Notices and trademarks

© Copyright IBM Corporation 2000, 2007. All Rights Reserved.

The XDoclet Documentation included in this IBM product is used with permission and is covered under the following copyright attribution statement: Copyright © 2000-2005, XDoclet Team. All rights reserved.

Portions based on Design Patterns: Elements of Reusable Object-Oriented Software, by Erich Gamma, Richard Helm, Ralph Johnson and John Vlissides, Copyright © 1995 by Addison-Wesley Publishing Company, Inc. All rights reserved.

U.S. Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

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.

IBM may use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you.

Licensees of this program who wish to have information about it for the purpose of enabling: (i) the exchange of information between independently created programs and other programs (including this one) and (ii) the mutual use of the information which has been exchanged, should contact:

Intellectual Property for WebSphere Integration Developer
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.

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.

This information contains sample application programs in source language, which illustrates programming techniques on various operating platforms. You may copy, modify, and distribute these sample programs in any form without payment to IBM, for the purposes of developing, using, marketing or distributing application programs conforming to the application programming interface for the operating platform for which the sample programs are written. These examples have not been thoroughly tested under all conditions. IBM, therefore, cannot guarantee or imply reliability, serviceability, or function of these programs.

Each copy or any portion of these sample programs or any derivative work, must include a copyright notice as follows:

If you are viewing a soft copy of this information, the photographs and color illustrations may not appear.

Programming interface information

Programming interface information is intended to help you create application software using this program.

General-use programming interfaces allow you to write application software that obtain the services of this program's tools.

However, this information may also contain diagnosis, modification, and tuning information. Diagnosis, modification, and tuning information is provided to help you debug your application software.

Warning: Do not use this diagnosis, modification, and tuning information as a programming interface because it is subject to change.

Trademarks and service marks

See www.ibm.com/legal/copytrade.shtml.

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