IBM WebSphere Integration Developer Fix Pack 6.0.1.2

for WebSphere Integration Developer 6.0.1

Welcome to IBM^® WebSphere^® Integration Developer fix pack 6.0.1.2 for WebSphere Integration Developer 6.0.1.

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.1 before installing the fix pack.

2.0 Product fix history

This fix pack contains many corrections and a few additions to WebSphere Integration Developer 6.0.1.

This fix pack includes WebSphere Integration Developer Fix Pack 6.0.1.1 and interim fix 001, interim fix 003, interim fix 004, interim fix 005, interim fix 006, interim fix 007, and interim fix 009.

The main addition is the refactoring function. Refactoring lets you rename and move service component architecture (SCA) artifacts such as interfaces and business objects. A number of samples have been revised to improve ease-of-use and better readability. There have been some performance improvements including reducing the time to rebuild applications. WebSphere Integration Developer has been improved to work easier with the IBM Rational ClearCase® file management system.

The following list is an overview of the components that have been updated and a description of some of the more significant problems addressed by the fix pack. There have been many minor user interface corrections to nearly all wizards and editors. There have also been numerous but minor documentation corrections. These minor corrections are not listed in detail here, though if there were a significant user interface or documentation update in a particular component, it is noted. APAR numbers, if applicable, are in parentheses.

Assembly editor: Adding a Java component could lead to unconventional behavior of the check in and check out functions of a ClearCase file management system (APAR JR24028). The problem has been addressed. When using the binding tab, the properties view would fail to refresh. The problem has been fixed. An interface map was being automatically created when components were being wired together without allowing a user to assign a name or verify if a map should be created. You will now be able to change the name and verify the map creation. After adding and removing a binding from an export several times, the remove binding option would no longer be enabled. This error has been fixed. If a JMS import was created with an interface and then an attempt was made to wire it to a new standalone reference with the same interface (that is, the interfaces were identical but schematically different), it would fail. The problem has been fixed. Contextual help has been added for some new fields.
Business process editor: In an assign activity, copying and pasting a fixed value could fail (APAR JR23714). The problem has been fixed. Opening a business process could fail with an unable to instantiate editor error (APAR JR24032). The error has been corrected. Importing a project interchange file could result in an illegal argument exception or a null pointer exception. This problem has been fixed. Messages with single quotation marks were not formatting correctly. A correction has been made. Deleting nested activities could result in an illegal argument exception. The problem has been fixed.
Business rules: Moving a selector into a subfolder of a project resulted in an exception being thrown. This problem has been fixed. A validation error on a rule set file allowed an invalid expression to be marked as valid, which resulted in a null pointer exception at run time. A correction has been made. Business objects which had only simple content by extension (without a named element or attribute) could not be handled, which resulted in an error message that stated that a source type was incompatible with an expression type. The problem has been fixed. In the rule group editor, if you corrected an error in an operation default, even though you had corrected the error, the error remained. The problem has been fixed. Hover help has been added to the decision table editor and a sample has been added to the documentation to clarify understanding of this editor.
Business state machine editor: When using a ClearCase file management system previously, you could set a transition with the editor and not be prompted to check a file out. A correction has been made and a user will be prompted in future. If a user had a new empty workspace and imported a project interchange file, the editor would fail to open. This problem has been fixed. A null pointer exception could be thrown when switching from business state machine editor to the assembly editor. This problem has been fixed. Some user interface changes make the editor consistent with other editors in visual presentation and actions.
Debugger: If you created an error-free decision table and then added an error to it as you developed the decision table, an error dialog would not appear when rebuilding. Instead, an exception would only appear in the console. This error has been fixed.
Documentation generator: Using the generate documentation function on a business process
created the activities section and its header but the information section was empty (APAR JR24090). A correction has been made. After generation, the namespace information for a parent business object was missing. The problem has been fixed.
Event monitor: Several corrections were made for easier integration with the ClearCase file management system. When building an application, many jobs labeled Monitor Handle Add File would appear. They have now been hidden. Imports and exports no longer can be monitored since this monitoring was not supported in the run time.
Human task editor: Performing an undo operation of a deleted escalation resulted in a false error message. A correction has been made. A browse button on the implementation property page incorrectly displayed all .tel file in a workspace. The scope has been correctly reduced to the current module.
Importing and exporting EIS services: An imported resource adapter could fail to appear in the enterprise service discovery wizard. The problem has been fixed. Managed connection factory properties could not be modified after a redo operation. A correction has been made. Support for the table property from the Enterprise Metadata Discovery specification has been added. Changes to the organization of properties after generating EIS or JMS bindings make finding and updating the properties easier. Hover help on the configure JMS import or export service fields has been added to improve ease-of-use. Callback destination properties could fail to appear in the properties after a drag-and-drop operation. The problem has been addressed.
Information center: A new section has been added explaining refactoring for service component architecture (SCA) artifacts. A new section has been created for messaging, which was formerly under the Importing and exporting EIS services section, with details explaining the relationship between JMS client constructs and SCA artifacts. An explanation of how private business objects are displayed in the business object mapping editor has been added to the business object mapping information (APAR JR23821). A section has been added to the importing and exporting EIS services section to show how to convert a business object to a COBOL copybook and vice-versa (APAR JR23564). The testing of a mediation flow component has been clarified to explain that it must be wired to a reference (APAR JR23904).
Interface editor: Data objects were incorrectly indexed as complex types resulting in errors when used by the interface mapping editor (APAR JR23991). A correction has been made. If an operation of a different style was added to an interface, it could result in an error in the interface mapping editor (APAR JR23630). This problem has been corrected. Creating a business process with the IBM Business Process Modeler, importing it into WebSphere Integration Developer, and then generating an EAR file resulted in a pathname error. An underscore was created where a forward slash should have been produced (APAR JR24412). This generation error has been fixed. Renaming an operation with another editor open could result in an error. The problem has been addressed. Dragging and dropping an interface with multiple services could lead to the generation of an incorrect binding. A correction has been made.
Interface mapping editor: When an interface map was created without specifying the interfaces and the destination, there was no indication of how to add the interface and destination (APAR JR23813). A button has been added to select an interface and destination. Multiple mappings were possible to the same target input if the source interfaces had the same two input parameters. This problem has been fixed.
Mediation flow editor: The editor now shows all schema details. Previously it showed only the first xsd:schema section's details from a WSDL file (APAR JR23987). A mediation flow file would remain even though a user had deleted the mediation flow in the editor. This problem has been fixed. After deleting an operation connection between a source interface and a target reference, some properties still remained in the mediation flow file. This error has been fixed. The XPath dialog would fail to open if the schema had no namespace. A correction has been made. Using the quick fix function to correct a ghost interface created an improperly positioned operation connection link. The error has been fixed.
Migration: Migration of a boolean <wpc:literal type="xsd:boolean> element was incorrect and has now been fixed.
Relationship editor: When working with the ClearCase file management system, a user could be incorrectly asked to check out a file that was not modified (APAR JR23966). This problem has been fixed.
Samples and tutorials: Several samples have been revised to improve their readability and ease-of-use.
Integration test client: An error in interpreting business objects could cause the test client to fail when the interface was invoked (APAR JR24390). A correction has been made. Problems could occur because the test client allowed a user to set values for each type in a hierarchy when only the top-most type should have been allowed (APAR JR24009). This problem has been fixed. A test case using emulation to emulate references, components, and so on could show old data when the test case was run again at a later time. This error has been addressed.
Visual snippet editor: Generated files were placed in the wrong folder. This problem has been corrected. A reference to a business object created in a Java snippet could fail to appear in the references view. A correction has been made. A validation error issued a warning on an assignment (for example, x=2) that the result was never used even though there is no result on assignment. A correction has been made.

3.0 Customer support

The product home page for WebSphere Integration Developer is www.ibm.com/software/integration/wid/. 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, 2006. 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-2006, 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 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.

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.