IBM WebSphere Integration Developer Refresh Pack 6.0.2

for WebSphere Integration Developer 6.0.1

Welcome to the IBM^® WebSphere^® Integration Developer Refresh Pack 6.0.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 refresh pack.

2.0 Product fix history

This refresh pack contains some significant additions to WebSphere Integration Developer 6.0.1 and many corrections. It also contains performance improvements.

See New features in WebSphere Integration Developer 6.0.2 for a list of new additions in WebSphere Integration Developer 6.0.2.

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 refresh pack. APAR numbers, if applicable, are in parentheses.

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

Assembly editor: When files were checked out from the Business Integration view and into a version control system, the checked files were no longer viewable except in the Physical Resources view (APAR JR23872). This problem has been corrected. Selectors and interface maps formerly allowed an advanced wiring dialog, which resulted in referencing problems. Advanced wiring has been disabled for selectors and the number of references limited in the case of interface maps. Updates to event sequencing fields could be lost. The problem has been addressed. The display name of a component in the properties view and in the assembly editor now correctly correspond. The preferred interaction style of an interface would fail to appear in expected places on the user interface or appear when it should not. This inconsistency has been addressed. An interface from a library could not be added to a component in a module even though a dependency on that library had been created. This problem has been fixed.
Bindings: A WebSphere MQ binding has been added and an MQ JMS binding has been added. Several serialization types and another function selector have been added to the JMS and MQ JMS bindings. A correction has been made so that if a project containing JMS imports and exports is imported along with a
WebSphere default messaging provider project it does not result in a null pointer exception.
Business object editor: In a table view, you could not enter the space character for a default value with a string type (APAR JR24804). A business graph can no longer be selected as a type in a business object, which was incorrectly permitted previously. Copying and pasting using the keyboard shortcut (Ctrl + C and Ctrl + V) now works as expected. The values for minOccurs and maxOccurs were not checked permitting a minOccurs value greater than a maxOccurs value. This problem has been fixed. When a default value was cleared, the element in the schema retained an empty default tag (default="") instead of removing the default tag, which resulted in errors. The default tag is now removed.
Business object mapping editor: You can now use the move function between a simple type and a complex type (APAR JR25298). The namespace field for business object maps, which previously had not been validated, is now checked. When both the business object mapping editor and business object editor were open and changes were made to attributes in the business object editor, these changes were not reflected in the business mapping editor. The editors have now been synchronized properly. Values now correctly appear in the details view after an assignment mapping. Previously, these values could disappear. When using the debugger and changing markers, the markers were not refreshed in the business object mapping editor. A correction has been made to reflect the accurate state of the markers.
Business state machine editor: The editor failed to display a property of a business object if it were a property inherited from another business object (APAR JR24267). This problem has been fixed. You can now generate reports on a business state machine. You can now select any interface for your business state machine, which is similar to the behavior of other editors. Formerly, you could not make an interface selection. Some variable names will no longer be permitted as they are reserved variables in the generated Business Process Execution Language (BPEL) code. The editor will no longer expand all composite nodes when the editor is opened regardless of the visual state when previously closed, as typically composites indicate a large state machine that you do not want fully expanded.
Business process editor: Setting an expiration on an activity followed by a save and then a change to no expression resulted in the old value still appearing (APAR JR24439). This error has been corrected. With arrays, the assign task editor only displayed the data type of an array element and ignored displaying the fact that it was itself an array (APAR JR24697). This inconsistency has been addressed. Similarly, when assigning a fixed value to a string element of an array, there was no indication that the element was an array (APAR JR24697). This problem has been fixed. Variables created as business graphs and imported into the business process process editor will now be displayed (APAR JR25408). If a project interchange file was imported into the workspace, the case expressions beneath a choice element inside a business process would fail to appear. The error has been corrected.
Business rules: The property page of the decision table rule editor now supports the select all keyboard shortcut (Ctrl-A). If you created a rule set with an action rule calling a a create business object then an incorrect template would be created if you converted that rule to a template. This problem has been addressed. Rule sets and decision tables are now checked for name uniqueness. Previously, the names were not checked leading to a possible name collision. Comparing a string array with a business object array failed to produce an error message. An error message is now issued.
Debugger: Input and output breakpoints set on the message input node and the message output node in a mediation flow were ignored during debugging. They are now recognized. Breakpoints set on a business rule could fail to open in the debugger. The breakpoints are now recognized. After restarting a workbench, opening a business object map with breakpoints led to error messages. This problem has been corrected. A mediation flow Java snippet breakpoint would on opening only provide basic information. Now the details of the custom mediation that contained the snippet are provided.
Documentation generator: The inheritance relationship between two business objects will now be reported. Previously, it had been missing. If a namespace were not defined in the business rule group editor then no report would be generated. This error has been fixed. If interfaces without operations were added to a rule group component, they would fail to appear in the generated report. The problem has been fixed. If you used the value Java when you specified your criteria in the selection field and there was no Java code or visual snippet present, a null pointer exception would be thrown. This problem has been addressed.
Enterprise service discovery wizard: The enterprise service discovery wizard can now retrieve services from a WebSphere Service Registry and Repository. Several additional IBM WebSphere Adapters have been provided for development purposes. When using the enterprise service discovery wizard, saved managed connection factory properties could be incorrect. This problem has been addressed.
Event monitor: Changes to Common Event Infrastructure (CEI) events using the human task editor did not occur until the server was restarted (APAR JR24868). This problem has been fixed. The event monitor editor tab is now present in the properties page of imports and exports created for a resource adapter. Selecting the global events settings tab in a business process failed to create the expected default events section. The default events section will now appear as expected. The behavior of error markers in the event definition editor was inconsistent with other editors in WebSphere Integration Developer. The behavior has been corrected.
Human task editor: If a human task were created and the business process choreographer were used to test it along with the generated Java ServerPage (JSP), there were errors finding and starting the JSP (APAR JR23467). This problem has been fixed. When creating a new human task in an environment using a version control system, an incorrect error could be issued requesting you to first check out the human task (APAR JR23682). This problem has been fixed. Several defects have been fixed with regards to erratic email notification behavior in the human task editor. Generating a client for your human task to test the human task at run time could fail at generation time. This error has been fixed.
Information center: Many updates have been made to the information center to reflect the product updates and the corrections in the editors and wizards. There is a new Quick Start guide.
Installation: An installation log file has been created to capture all events at installation time. Uninstalling now removes most extraneous files leaving more free disk space than previously. A reminder has been added to the installation that updates to WebSphere Process Server are done independently of WebSphere Integration Developer with a link to the server support site. The installation instructions have been updated to improve the usability of the installation experience.
Integration test client: Canceling the password dialog on a secure server allowed the test to incorrectly continue. The problem has been fixed. The default values will now be picked up when you add an element to an array. Previously, they were ignored. Usability has been improved for loading data from a data pool. If you ran a test when the assembly diagram was empty, a null pointer exception was thrown. A correction has been made.
Interface editor: There could be an error at run time caused by an inability to determine if the binding style is document literal or document literal wrapped (APAR JR25068). This problem has been fixed. The binding style is now shown in the operation properties, as the binding style can change from operation to operation. Namespace terminology has been made consistent between the wizard and the editor. The Save As function, which had not been operational, has been fixed.
Interface mapping editor: Using an extract parameter mapping with a business graph could result in an unexpected error (APAR JR24626). The problem has been addressed. Map selection has been made more precise so that only valid maps with correct input and output are shown. Using the undo function could cause a parameter map to disappear. A correction has been made. Changing a parameter mapping type in a table view could result in a null pointer exception. This problem has been fixed.
Interoperability: Web Services Description Language (WSDL) files can now be imported into WebSphere Integration Developer through a new importer that also can separate inline schemas into separate files on import. Conversely, an exporter can merge separate WSDL files into one file with inline schemas. This function makes it possible to share WSDL files between a development environment that uses inline schemas and a development environment that does not use inline schemas.
Mediation flow editor: The Endpoint Lookup primitive can now access the WebSphere Service Registry and Repository (WSRR) in a mediation flow. Generation performance has been improved. Adding a custom mediation primitive to a request flow without wiring it resulted in an error when a new reference was added. This problem has been fixed. Adding a message filter to a to a mediation flow followed by adding an output terminal and renaming it resulted in a terminal that could not be selected. This problem has been fixed. If multiple rows in a table were marked as promoted, all of the values in the promoted rows became the same - the value of the property that was most recently updated. This error has been addressed. In a mediation module if the mediation flow editor tried to add an interface created separately to the mediation flow component, the result would be an error instead of seeing the interface added. This problem has been fixed.
Migration: Due to an erroneous check of short and long paths, migrating a project with BPEL files could result in an array index out of bounds error. This problem is corrected. When migrating from WebSphere Studio Application Developer Integration Edition (WSADIE), duplicate namespaces would result in errors. This problem has been corrected. Several defects were addressed to migrate bindings from a WebSphere Studio Application Developer Integration Edition perspective to the imports and exports used in WebSphere Integration Developer. A fix has been made to prevent null pointer exceptions being thrown during a migration when an expected WSDL file is missing.
Refactoring: When federated schema files were used in a configuration with a version control system, it resulted in check-in and check-out problems (APAR JR25043). This problem has been addressed. Using refactoring in cases with stateless session EJBs, a mapper and inline schemas could result in the corruption of WSDL files. This issue has been fixed. Using move could result in an incorrect form of a schemaLocation reference
in artifacts that used import, include and redefine in their XSD code. This problem has been fixed. A correction has been made so that refactoring a business object that includes a federated schema does not result in a failure.
Relationship editor: The add button in the attribute table was formerly not always active, as it should have been. This error has been corrected. After creating a new relationship and adding a role a class cast exception could be thrown. This error has been fixed. If the enterprise service discovery wizard was used with a resource adapter to create business objects and a relationship map was created between the business objects then the keys to the relationship roles, which should have had single values, instead had array types. This problem has been fixed. When saving a relationship map with a role, an error message could appear that the file could not be found. This false error will no longer appear.
Samples and tutorials: Many samples have been revised and are now presented in a new format that makes creating the samples easier. In this new format, more information has been provided explaining the value of aspects of a sample. Some tutorials have been updated.
Selector editor: A refresh problem meant that the rule group editor did not refresh after an operation had been deleted from an interface. The problem has been fixed. Changing a name in the properties view now also changes the selector editor title, which it formerly did not update. If a module with a selector was imported along with a library containing a necessary interface, a null pointer exception could be thrown. This error has been addressed.
Visual snippet editor: A visual snippet using a business object without a namespace resulted in the generation of incorrect Java code. This error has been fixed. A correction has been made so that a repeating loop in a visual snippet does not issue an incorrect null pointer exception. A deployment error could occur when an integer data type was converted to a string in a visual snippet, which has now been fixed. Adding a day of the week activity to a visual snippet generated incorrect Java code. The problem has been fixed.
Welcome: the welcome view has been restructured to provide faster access to needed information on WebSphere Integration Developer for new and returning users.

The following fixes to the WebSphere Process Server 6.0.2 runtime are included with this refresh pack when you install the IBM WebSphere Process Server 6.0.2 test environment feature:

IC51328
IY92589
JR25464
JR25465
JR25487
JR25491
JR25492
JR25494
PK32396
PK32982
PK35039
PK35285
PK35426
PK35444

Additional fixes for WebSphere Process Server 6.0.2 may be added at any time. Therefore, check the recommended fixes and published APAR list on the WebSphere Process Server support page.

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