Product Documentation
Abstract
WebSphere Integration Developer provides periodic fixes for editions of release version 7.0. The following is a complete listing of fixes for WebSphere Integration Developer version 7.0.
Content
7.0.0 Fix Pack 5 (7.0.0.5)
7.0.0.4 Interim Fix 001
7.0.0 Fix Pack 4 (7.0.0.4)
7.0.0.3 Interim Fix 002
7.0.0.3 Interim Fix 001
7.0.0 Fix Pack 3 (7.0.0.3)
7.0.0.2 Interim Fix 001
7.0.0 Fix Pack 2 (7.0.0.2)
7.0.0.1 Interim Fix 001
7.0.0 Fix Pack 1 (7.0.0.1)
7.0.0 Fix Pack 5 (7.0.0.5)
Fix release date: 26 June 2012Last modified: 26 June 2012
Status: Recommended
The following list describes the components that have been updated. APAR numbers, if applicable, are also listed.
Component | APAR | Description |
Adapters | JR41945 | If the data being received over the binding contains characters that end up being invalid XML characters after data conversion, the transformation of the data into a Data Object will fail. |
Assembly editor | JR41558 | The default parameter name for the throw activity is translated and the languages listed above included a space in the translation, which breaks the Java™ identifier rule. This parameter name is automatically created and is not directly editable from within the java editor |
Business calendar editor | JR41943 | When user selects different time interval for displaying its properties, some property values are not refreshed properly, as they are still displaying the values of the previously selected time interval |
Business process editor | JR40593 | The problems view will show errors relating to correlation sets not being found. These BPEL extensions in the WSDL file are physically located above the WSDL imports, when the model is being read in the PropertyAlias objects don't resolve the Property objects as the model doesn't know about the imports at this point. |
JR40670 | If customer uses soap data handler and the response message includes soap fault, the element in <faultcode> is SAAJ 1.2 format, which is not expected by some XML parser. | |
Business projects | JR40423 | When generating an EJB Import that has a WSDL interface and XSD types, there is a possibility that two types are generated whose names are the same (except for the case of some of the letters) and whose namespace is the same. WID attempts to save those types in their own, separate XSD file. The names of those files derive from their type names and this causes problems on WID when running on Windows. Windows does not support two files whose names are the same except for the case of some letters. One file will be saved and the other file is not saved - causing one of the types to be missing. This causes errors where the missing type is referenced. |
JR40521 | Users importing an EAR from WID into WSRR may fail with an error like Error GSR0008E | |
JR40784 | Exported integration module missing /src | |
JR41293 | The namespace prefixes of the soap header messages are not being updated when the WSDLs are being merged during export. | |
JR41294 | An OutOfMemoryError occurs during the building of the workspace. | |
Human task editor | JR40514 | The namespace for property based on element reference is not correct. |
JR40782 | Optional Business Objects like arrays are specified in the HTML Dojo form with the a specific dojo type which describes arrays. The name of each element in the dojo HTML form specifies in an xpath like way the position of the element in the xml message of the task. Arrays are marked with the an array marker [], as optional Business Objects are represented by the array dojo type they also need the array marker in the path. This fix inserts the missing array marker [] for optional Business Objects, which improves upload time of the task form in Business Space Task Information widget, for tasks using optional Business Objects. | |
Integration test client | JR40154 | The XML values for a BO will not change from the first event it is seen in. |
JR40779 | When creating a test case to invoke a web service export with no input parameter, the test case does not create a input variable for the input SOAP message. As a result, the invocation is not done correctly. Instead of doing a web service invocation, the test case does an SCA invocation. | |
JR41987 | An index out of bounds exception is thrown when the Component test runtime deserializes certain types of complex Business objects in Lazy mode, on the server. | |
JR42586 | The test client runtime assumed a Business Object would always have fields.We need to check whether there are any before we try to create the Service Data Object at runtime. | |
JR42631 | When selecting variables to show in BPEL Fine-Grained Trace, if any selected are interface variables rather than data type variables, an exception will occur when trying to display the Fine-Grained Trace events. Similarly, an exception will occur when creating a Verify event for activities with BPEL interface variables. | |
JR42994 | A StackOverflowException is thrown anytime the test project was built, when it contains certain XSD constructs. | |
Mediation flow editor | JR42550 | Type filter condition with root /body cannot be removed when the MFC editor is re-opened. |
JR41311 | When a subflow property is promoted to the main flow, its property type is not correctly determined. It always returns as a string type. | |
Monitor toolkit | JR41074 | When adding a new Verify Monitor Event step in a test case, the codegen of the updated test case may not be updated properly. |
See Fix/Update list for WebSphere Business Monitor development toolkit V7.0 | ||
Reporting | JR42256 | Documentation is split into multiple PDF files, when it should be single document. |
Webservice custom callback handler | JR41329 | The custom callback handler is currently a selected list and a custom callback handler can not be put into the UI. |
XML mapping editor | JR43079 JR40926 | A problem marker similar to "The count function is not available", is generated on XML Map files containing the XPath count or ceiling |
JR41295 | The XPath validator is confusing the element name "attribute" with the XPath Axis attribute:: node. As a result, the XPath validator is incorrectly reporting the following message: "The name attribute in XPath ... was not found in the XML Schema." |
There have been updates to the WebSphere Process Server V7.0.0.5 runtime, which is included with this Fix Pack if you installed the IBM WebSphere Process Server V7.0.0.5 test environment feature
Note:
The runtime interim fix XC7004x available from this link updates the business object lazy parsing mode which is now supported for use with mediation components in WebSphere Process Server and WebSphere Enterprise Service Bus version 7.0.0 Fix Pack 4. This runtime interim fix extends the support for use of business object lazy parsing mode to include use with mediation flow components.
The business object eager parsing mode (which corresponds with the business object parsing mode in all previous version 6.x releases) continues to be the default in version 7.0.0.3, and remains the business object parsing mode for production use for any module that contains mediation flow components.
Feedback and questions regarding the lazy business object parsing mode can be directed to the WebSphere Process Server forum.
Applications created with WebSphere Integration Developer 7.0.0.5 can be deployed to a WebSphere Process Server for Multiplatforms or WebSphere Enterprise Service Bus for Multiplatforms server which is at the 7.0.0.5 level or later. They can also be deployed to a 7.0.0.0 level if the new V7 business object runtime framework is not used.
Applications created with WebSphere Integration Developer 7.0.0.5 can be deployed to a WebSphere Process Server for z/OS or WebSphere Enterprise Service Bus for z/OS server which is at the 7.0.0.5 level or later. They can also be deployed to a 7.0.0.0 level if the new V7 business object runtime framework is not used.
When using Installation Manager for updates, your set of files can grow substantially. It is recommended that you consider removing the old files. To do this, select File > Preferences > File for Rollback. Click Delete Saved Files. To return to a previous version, you must use files from the media or repositories that created the install package.
7.0.0.4 Interim Fix 1
Fix release date: 3 October 2011Last modified: 3 October 2011
Status: Recommended
The following list describes the components that have been updated. APAR numbers, if applicable, are also listed.
Component | APAR | Description |
Assembly editor | JR40058 | An error marker appears on a wire between the Java Component reference and the Mediation Flow Component interface. The error marker reads: "CWSCA8019E: A matching interface cannot be found on the MediationFlowComponent target." |
Integration test client | JR40238 | A CTNoRuleFoundException occurs when emulating a component or human task, but it is not apparent from the exception why the emulator definition tasks cannot be found. |
JR40705 | An IndexOutOfBoundException occurs when running a test in the test client where the Component Test Explorer attempts to emulate a component. | |
Mediation flow editor | JR39986 | An error such as "The element <elementName> is used as an input before its value or result is computed or assigned" occurs. |
JR40531 | An error is observed when attempting to run the XSL Transformation node within a Mediation Flow Component, starting with the following: "00000071 SystemErr R ERROR: 'The input document is not a stylesheet (the XSL namespace is not declared in the root element).'" | |
XML mapping editor | Feature Enhancement | |
JR40153 | After refactoring the namespace of a schema, some of the XML Maps in the workspace have errors with unresolved objects. The XML Maps affected are those leveraging the Casting feature within the maps which references the schema namespace being refactored in the workspace. | |
JR40253 | After selecting the parameter "Current Date and Time" when using the "Transform - format-date" operation and saving the project, a subsequent review shows the parameter selection has reverted back to "XPath". As it has switched back to the XPath string definition and since it is empty, it causes an XSLT runtime exception at runtime. | |
JR40530 | If a DataObject input to a map has the xsi:nil="true" flag set, a Move will not copy the xsi:nil="true" flag to the output. | |
JR40777 | For a required nillable field, if the input is missing, xsi:nil="true" should be added to the output by default. |
There have been updates to the WebSphere Process Server V7.0.0.4 runtime, which is included with this Fix Pack if you installed the IBM WebSphere Process Server V7.0.0.4 test environment feature
Note:
The runtime interim fix XC7004x available from this link updates the business object lazy parsing mode which is now supported for use with mediation components in WebSphere Process Server and WebSphere Enterprise Service Bus version 7.0.0 Fix Pack 4. This runtime interim fix extends the support for use of business object lazy parsing mode to include use with mediation flow components.
The business object eager parsing mode (which corresponds with the business object parsing mode in all previous version 6.x releases) continues to be the default in version 7.0.0.3, and remains the business object parsing mode for production use for any module that contains mediation flow components.
Feedback and questions regarding the lazy business object parsing mode can be directed to the WebSphere Process Server forum.
Applications created with WebSphere Integration Developer 7.0.0.4 can be deployed to a WebSphere Process Server for Multiplatforms or WebSphere Enterprise Service Bus for Multiplatforms server which is at the 7.0.0.4 level or later. They can also be deployed to a 7.0.0.0 level if the new V7 business object runtime framework is not used.
Applications created with WebSphere Integration Developer 7.0.0.4 can be deployed to a WebSphere Process Server for z/OS or WebSphere Enterprise Service Bus for z/OS server which is at the 7.0.0.4 level or later. They can also be deployed to a 7.0.0.0 level if the new V7 business object runtime framework is not used.
When using Installation Manager for updates, your set of files can grow substantially. It is recommended that you consider removing the old files. To do this, select File > Preferences > File for Rollback. Click Delete Saved Files. To return to a previous version, you must use files from the media or repositories that created the install package.
7.0.0 Fix Pack 4
Fix release date: 8 July 2011Last modified: 8 July 2011
Status: Recommended
The following list describes the components that have been updated. APAR numbers, if applicable, are also listed.
Component | APAR | Description |
Adapters | JR38026 | SAP Adapter error processing IDOCs WSDL |
Fix List | WebSphere Adapters V7.0 fix list for WebSphere Integration Developer V7.0 | |
Assembly editor | JR38867 | Error when generating Web Services binding with SOAP/JMS |
Business process editor | JR39959 | Unable to select the Correlation ID |
JR37661 | Issues in snippet package insert in V6.2 and V7.0 | |
JR38496 | Copy and paste of human task activity in BPEL editor causes an exception | |
JR38509 | Wait activity causes error in a BPEL process | |
JR39820 | Issues while copying inside of BPEL processes | |
JR38265 | Display issue with showing wrong "NewName" during process version | |
JR39707 | "Save All" function only saves the last changes in BPEL editor | |
Business projects | JR38837 | Application could not be deployed to local WTE when using .jar files embedded in a global library |
JR39930 | When exporting a module that contains a user-authored Web project, files were missing from the .war archive, namely .jar files | |
JR38312 | Java code containing SDO object manipulation and an //$NON-NLS-*$ comment, causes NPE during validation | |
Business Rules | JR37858 | Build error : Stack overflow |
CEI (Event Monitor) and Monitor support | JR38052 | Error at runtime that events were received out of order |
Documentation | JR38828 | Documentation update for emulator definition task usage |
EJB import handler | JR38806 | Generating EJB imports from EJB client interface doesn't work |
Installation | JR37766 | Error coding in runAntWidSecurity script. |
JR39486 | Wrong OS prereq checking causing exception when installing V7.0.0.3 interim fixes 001 and 002 | |
Interface Editor | JR39699 | Refactoring a WSDL namespace causes errors on referencing |
JR38728 | Validating WSDL duplicate messages showed a warning in WebSphere Integration Developer V7.0.0.2 and became error in WebSphere Integration Developer V7.0.0.3 | |
JR38245 | Using "Remove" in Advanced Configuration for HTTP import bindings panel throws an error | |
JR38443 | Exception thrown using Policy Set for Web service binding | |
JR37655 | Refactor and Move causing error | |
Java component handler | JR39582 | Java component handler did not generate the callback method for the request-response operation |
Integration test client | JR38293 | Hang in BPEL flow |
JR38868 | Error in WebSphere Integration Developer component test client | |
JR39708 | Component test project expects wrong fault | |
JR38015 | Changing the type to a complex type causes error in test | |
Mediation flow editor | JR38818 | Exceptions occurred when trying to validate a subflow in a headless environment |
Feature Enhancement | Improvement in compare/merge for mediations | |
JR39334 | Map node can not be deleted | |
Monitor Toolkit | Fix List | Fix/Update list for WebSphere Business Monitor development toolkit V7.0 |
Project Validation | JR39699 | Unexpected project level validation settings |
XML mapping editor | JR39380 | Empty Assign results Null in a string object |
JR39235 | Submap links inside the moved map are broken when refactoring | |
JR38626 | Mapping a concrete type throws an error | |
JR38169 | Local map from head element to sub element doesn't produce correct results | |
JR38160 | WebSphere Integration Developer V7.0.0.3 hangs when using the element filter | |
JR39688 | String function "translate" dropped in WebSphere Integration Developer V7.0.0.3 | |
JR39176 | Validation error when a submap transform created to reference a calling map with the same namespace as the current caller map | |
JR39859 | The SMO loader is not properly resolving the ANYTYPES within the CONTEXT element | |
JR38554 | Wrong behavior in mapping editor using an IF/ELSE in a mediation flow | |
JR38097 | Spaces are deleted in string 'MM/dd/yyyy hh:mm:dd' | |
XPath editor | JR39696 | Test map view is slow |
JR39146 | Custom XSLT value drop down list closes too quickly | |
JR39628 | Exception gets thrown during the invocation pages of the XML map on the server |
There have been updates to the WebSphere Process Server V7.0.0.4 runtime, which is included with this Fix Pack if you installed the IBM WebSphere Process Server V7.0.0.4 test environment feature
Note:
The runtime interim fix XC7004x available from this link updates the business object lazy parsing mode which is now supported for use with mediation components in WebSphere Process Server and WebSphere Enterprise Service Bus version 7.0.0 Fix Pack 4. This runtime interim fix extends the support for use of business object lazy parsing mode to include use with mediation flow components.
The business object eager parsing mode (which corresponds with the business object parsing mode in all previous version 6.x releases) continues to be the default in version 7.0.0.3, and remains the business object parsing mode for production use for any module that contains mediation flow components.
Feedback and questions regarding the lazy business object parsing mode can be directed to the WebSphere Process Server forum.
Applications created with WebSphere Integration Developer 7.0.0.4 can be deployed to a WebSphere Process Server for Multiplatforms or WebSphere Enterprise Service Bus for Multiplatforms server which is at the 7.0.0.4 level or later. They can also be deployed to a 7.0.0.0 level if the new V7 business object runtime framework is not used.
Applications created with WebSphere Integration Developer 7.0.0.4 can be deployed to a WebSphere Process Server for z/OS or WebSphere Enterprise Service Bus for z/OS server which is at the 7.0.0.4 level or later. They can also be deployed to a 7.0.0.0 level if the new V7 business object runtime framework is not used.
When using Installation Manager for updates, your set of files can grow substantially. It is recommended that you consider removing the old files. To do this, select File > Preferences > File for Rollback. Click Delete Saved Files. To return to a previous version, you must use files from the media or repositories that created the install package.
7.0.0.3 Interim Fix 002
Fix release date: 8 April 2011Last modified: 8 April 2011
Status: Recommended
The following list describes the components that have been updated. APAR numbers, if applicable, are also listed.
Component | APAR | Description |
Activity editor | JR39332 | Variable expressions are not properly initialized. Note: WebSphere Business Modeler customers using data maps and exporting to WebSphere Integration Developer may experience this problem. |
Business process editor | JR38703 | The Add Correlation Property dialog hangs if the referred business object has a cyclic structure. |
JR38527 | The display of auto-generated catch elements in a fault handler is different from V6. | |
JR38528 | BPEL editor marks the process as changed, although nothing was changed if a catch is selected. | |
Getting started menu | Getting Started exceptions when using a very large display. | |
Integration test client | JR38833 | Cannot work with the work basket. The work items of the task instance are not inherited to the activity instance. |
JR38937 | During verify event for fine-grained trace events, a NPE may occur. | |
JR39005 | An error occurs due to an illegal character when the component test log is loaded in the server. | |
JR38646 | Memory leak observed when enabling fine-grained trace support in the test client which involves a subflow. | |
JR38975 | A verification event can fail with a BOXML serialize exception in the server log indicating that it cannot resolve some elements. Note: this fix needs to be applied to runtime, see WebSphere Process Server sysroute APAR JR39180. | |
Feature Enhancement | When a Fail primitive is run, the mediation flow throws a runtime exception which will fail the test case. | |
Migration | JR39048 | "XPATH element not found in XML schema" error after migration. |
JR39075 | Error in migrating projects that contain maps referenced by mediation flows from V6.0.2 to V7.0.0.3 | |
Relationships | JR38829 | When using a revised lookup transform the runtime log contains warnings about unrecognized set methods in the lookup engine. |
JR38773 | NPE occurs when adding a condition to a relationship look up. | |
XML mapping editor | JR38099 | Data wrapper needed for global element with named type. |
JR37815 | Submap transform does not work as expected. | |
JR38726 | XML map generation runs out of memory when an XSL file is set to "read only" and there is a submap reference within the map file. | |
JR38938 | The XSLT runtime engine does not provide support for certain EXSLT functions. | |
JR39027 | Namespace declaration missing in output XML. | |
XPath editor | JR39186 | XPATH validation errors or warnings appear on expressions which should be valid. |
There have been updates to the WebSphere Process Server V7.0.0.3 runtime, which is included with this Fix Pack if you installed the IBM WebSphere Process Server V7.0.0.3 test environment feature. The following APARs are included with this Fix Pack: APAR JR38504, JR37773 and JR39245.
Note:
The runtime interim fix XC70031 available from this link updates the business object lazy parsing mode which is now supported for use with mediation components in WebSphere Process Server and WebSphere Enterprise Service Bus version 7.0.0 Fix Pack 3. This runtime interim fix extends the support for use of business object lazy parsing mode to include use with mediation flow components.
The business object eager parsing mode (which corresponds with the business object parsing mode in all previous version 6.x releases) continues to be the default in version 7.0.0.3, and remains the business object parsing mode for production use for any module that contains mediation flow components.
Feedback and questions regarding the lazy business object parsing mode can be directed to the WebSphere Process Server forum.
Applications created with WebSphere Integration Developer 7.0.0.3 can be deployed to a WebSphere Process Server for Multiplatforms or WebSphere Enterprise Service Bus for Multiplatforms server which is at the 7.0.0.3 level or later. They can also be deployed to a 7.0.0.0 level if the new V7 business object runtime framework is not used.
Applications created with WebSphere Integration Developer 7.0.0.3 can be deployed to a WebSphere Process Server for z/OS or WebSphere Enterprise Service Bus for z/OS server which is at the 7.0.0.3 level or later. They can also be deployed to a 7.0.0.0 level if the new V7 business object runtime framework is not used.
When using Installation Manager for updates, your set of files can grow substantially. It is recommended that you consider removing the old files. To do this, select File > Preferences > File for Rollback. Click Delete Saved Files. To return to a previous version, you must use files from the media or repositories that created the install package.
7.0.0.3 Interim Fix 001
Fix release date: 18 November 2010Last modified: 18 November 2010
Status: Recommended
The following list describes the components that have been updated. APAR numbers, if applicable, are also listed.
Component | APAR | Description |
Business object mapping editor | JR38166 | Unable to resolve referenced business object: ContextType or HeaderType |
EJB import handler | JR37881 | Errors when creating an EJB import |
Interface map editor | JR37883 | A Null Pointer Exception occurs when attempting the specific IFM |
Note:
The runtime interim fix XC70031 available from this link updates the business object lazy parsing mode which is now supported for use with mediation components in WebSphere Process Server and WebSphere Enterprise Service Bus version 7.0.0 Fix Pack 3. This runtime interim fix extends the support for use of business object lazy parsing mode to include use with mediation flow components.
The business object eager parsing mode (which corresponds with the business object parsing mode in all previous version 6.x releases) continues to be the default in version 7.0.0.3, and remains the business object parsing mode for production use for any module that contains mediation flow components.
Feedback and questions regarding the lazy business object parsing mode can be directed to the WebSphere Process Server forum.
Applications created with WebSphere Integration Developer 7.0.0.3 can be deployed to a WebSphere Process Server for Multiplatforms or WebSphere Enterprise Service Bus for Multiplatforms server which is at the 7.0.0.3 level or later. They can also be deployed to a 7.0.0.0 level if the new V7 business object runtime framework is not used.
Applications created with WebSphere Integration Developer 7.0.0.3 can be deployed to a WebSphere Process Server for z/OS or WebSphere Enterprise Service Bus for z/OS server which is at the 7.0.0.3 level or later. They can also be deployed to a 7.0.0.0 level if the new V7 business object runtime framework is not used.
When using Installation Manager for updates, your set of files can grow substantially. It is recommended that you consider removing the old files. To do this, select File > Preferences > File for Rollback. Click Delete Saved Files. To return to a previous version, you must use files from the media or repositories that created the install package.
7.0.0 Fix Pack 3 (7.0.0.3)
Fix release date: 3 September 2010Last modified: 3 September 2010
Status: Recommended
The following list describes the components that have been updated. APAR numbers, if applicable, are also listed.
Component | APAR | Description |
Adapters | See WebSphere Adapters V7.0 fix list for WebSphere Integration Developer V7.0 | |
JR36728 | Failed message recovery mode is not available for one way operations. | |
Business process editor | JR36727 | Comparing and Merging produces BPEL files with errors which can not be deployed. |
JR36724 | Error thrown using "Group" as people assignment for BPEL admin Human Tasks. | |
JR36872 | Error markers appear when changing the fault name of a catch element. | |
JR37194 | Opening a BPEL file and making changes to it, might cause a pop up dialogue box. | |
JR37331 | Creating a catch in a BPEL fault handler might cause a significant delay. | |
Business object mapping editor | JR37460 | Errors are created when refactoring Business Object. |
JR36584 | ClassCaseException happens when performing a clean project if the module contains the Java code to treat simple type as Business Object. | |
JR37509 | Build error after migration from V6.0.2 to V6.2.0.3 | |
JR36391 | Exception occurs during a workspace build or during validation checks on the business object map custom transform as "Invalid XPath with Invalid symbol '{' ". | |
Documentation | JR37333 | Documentation on HTTPStreamDataBindingBytes data binding were not clear. |
EJB Import Handler | JR37176 | The code generation to WSDL/XSDs from java interface is failed when the return type in java interface is an array. |
JR37141 | Dragging an EJB on an Assembly Diagram to create an Import resulted a stack overflow. | |
Event monitor | JR37414 | Duration metric and stopwatch were not working for process. |
Integration test client | JR37301 | Test client error with Business Object does not have the namespace. |
JR36920 | Failed to add Verify Event task for fine-grained trace. | |
JR37079 | Clip adornment and browser were missing in test view. | |
JR37527 | Non-English characters are not exported properly when exploring parameter values to a file from the integration test client. | |
JR37609 | The verify event task throws an exception when verifying the data. | |
Human Tasks | JR37094 | Synchronizing WebSphere Business Modeler exports generates wrong details. |
Install | JR37447 | Classic Update validates features which are not loaded causing dependencies which do not exist to flag the system improper. |
Interface editor | JR37335 | Import location is not updated correctly when a binding WSDL is refactored to another project. |
JR36979 | Set the default web service runtime to JAX-WS | |
JR37332 | Refactoring Business Object causing Business "Object Not Found" | |
Mediation | JR37059 | BO Maps in a subflow don't show types set by Set Message Type primitive within the SMO. |
JR37515 | Some XPATH can not be set in a fan out. | |
Monitor Toolkit | See the list of fixes for WebSphere Business Monitor development toolkit V7.0 Fix Pack 3 (7.0.0.3) | |
XML mapping editor | JR37459 | Null pointer exception observed trying to refactor a Business Object Name |
JR36941 | Error occurs, when running an XML Map on the server that uses an XSLT Custom transform without an input parameter being set. | |
JR36818 | Failure in re-generating the XSLT, when changing an XML schema. | |
JR37611 | No valid XML Maps were found that could be tested | |
Xpath Editor | JR36919 | When using XPath parser, 'id' not recognized as a variable.It's parsed as it's own type/kind. |
There have been updates to the WebSphere Process Server V7.0.0.3 runtime, which is included with this Fix Pack if you installed the IBM WebSphere Process Server V7.0.0.3 test environment feature. The following APARs are included with this Fix Pack: APAR IC68738 and JR36799.
WebSphere Process Server and WebSphere Enterprise Service Bus have enabled a new lazy parsing mode for business objects in version 7.0.0.3. Although the lazy parsing mode is available for all components of 7.0.0.3, usage of the business object lazy parsing mode is not supported for mediation flow components. For more information see WebSphere Process Server and WebSphere Enterprise Service Bus - Support statement for the business object lazy parsing mode in version 7.0.0.3 and mediation flow components.
Applications created with WebSphere Integration Developer 7.0.0.3 can be deployed to a WebSphere Process Server for Multiplatforms or WebSphere Enterprise Service Bus for Multiplatforms server which is at the 7.0.0.3 level or later. They can also be deployed to a 7.0.0.0 level if the new V7 business object runtime framework is not used.
Applications created with WebSphere Integration Developer 7.0.0.3 can be deployed to a WebSphere Process Server for z/OS or WebSphere Enterprise Service Bus for z/OS server which is at the 7.0.0.3 level or later. They can also be deployed to a 7.0.0.0 level if the new V7 business object runtime framework is not used.
When using Installation Manager for updates, your set of files can grow substantially. It is recommended that you consider removing the old files. To do this, select File > Preferences > File for Rollback. Click Delete Saved Files. To return to a previous version, you must use files from the media or repositories that created the install package.
7.0.0.2 Interim Fix 001
Fix release date: 19 July 2010Last modified: 19 July 2010
Status: Recommended
The following list describes the components that have been updated. APAR numbers, if applicable, are also listed.
Component | APAR | Description |
Comparing and merging | Improved support of instance migration for business processes modeled in WebSphere Business Modeler | |
Installing | The problem with the Business Integration perspective and view not being available after deleting saved files for rollback has been fixed |
There has been an update to the Rational Application Developer, which is included with this Fix Pack. The following APAR is included with this Interim Fix: PM16842.
WebSphere Process Server and WebSphere Enterprise Service Bus have enabled a new business object framework as a Technology Preview in the 7.0.0.2 Fix Pack.
Applications created with WebSphere Integration Developer 7.0.0.2 can be deployed to a WebSphere Process Server for Multiplatforms or WebSphere Enterprise Service Bus for Multiplatforms server which is at the 7.0.0.2 level or later. They can also be deployed to a 7.0.0.0 level if the new V7 business object runtime framework is not used.
Applications created with WebSphere Integration Developer 7.0.0.2 can be deployed to a WebSphere Process Server for z/OS or WebSphere Enterprise Service Bus for z/OS server which is at the 7.0.0.2 level or later. They can also be deployed to a 7.0.0.0 level if the new V7 business object runtime framework is not used.
When using Installation Manager for updates, your set of files can grow substantially. It is recommended that you consider removing the old files. To do this, select File > Preferences > File for Rollback. Click Delete Saved Files. To return to a previous version, you must use files from the media or repositories that created the install package.
7.0.0 Fix Pack 2 (7.0.0.2)
Fix release date: 26 June 2012Last modified: 26 June 2012
Status: Recommended
The following list describes the components that have been updated. APAR numbers, if applicable, are also listed.
Component | APAR | Description |
Adapters | See WebSphere Adapters V7.0 fix list for WebSphere Integration Developer V7.0 | |
Business calendar | Hijiri Calendar support | |
Business process editor | Support of instance migration for business processes modeled in WebSphere Business Modeler | |
JR36240 | NPE during variable rename | |
JR35498 | Unable to open BPC editor for migrated flow from WebSphere Business Modeler | |
Business object mapping editor | JR35500 | Refactoring of service operation name breaks existing business object maps |
Documentation | JR36002 | Some topics in WebSphere Integration Developer V7.0.0.0 information center contain references to V6.0 or V6.1 |
Integration test client | JR36193 | XML editor missing in component test user interface |
Interface editor | JR35231 | WSDL/XSD export wizard allows Finish button to be enabled when it must be disabled |
Mediation flow editor | JR35824 | Datahandler properties has not been saved |
JR36389 | User interface issue for Fan Out Xpath expression | |
Monitor Toolkit | See the list of fixes for WebSphere Business Monitor development toolkit V7.0 Fix Pack 2 (7.0.0.2) | |
Rational ClearCase | Support for Rational ClearCase V7.1.1 | |
Rational Team Concert | Support for Rational Team Concert V1.0.X and V2.0.0.2 | |
Search and index framework | JR35410 | Deadlock in IndexSystemCache.getBackingUserFilesFor() |
Visual snippet editor | JR35722 | Performance settings for VisualSnippetEditor activated by default |
XML mapping editor | JR35816 | XPATH and XML mapping editor do not show ANYTYPE when WSDL message references a global element set to XSD:ANYTYPE |
JR35869 | XSLT mapping editor hangs or loops |
There have been updates to the WebSphere Process Server V7.0.0.2 runtime, which is included with this Fix Pack if you installed the IBM WebSphere Process Server V7.0.0.2 test environment feature. The following APARs are included with this Fix Pack: APAR JR35669, JR35601, JR35693 and JR35798.
WebSphere Process Server and WebSphere Enterprise Service Bus have enabled a new business object framework as a Technology Preview in the 7.0.0.2 Fix Pack.
Applications created with WebSphere Integration Developer 7.0.0.2 can be deployed to a WebSphere Process Server for Multiplatforms or WebSphere Enterprise Service Bus for Multiplatforms server which is at the 7.0.0.2 level or later. They can also be deployed to a 7.0.0.0 level if the new V7 business object runtime framework is not used.
Applications created with WebSphere Integration Developer 7.0.0.2 can be deployed to a WebSphere Process Server for z/OS or WebSphere Enterprise Service Bus for z/OS server which is at the 7.0.0.2 level or later. They can also be deployed to a 7.0.0.0 level if the new V7 business object runtime framework is not used.
When using Installation Manager for updates, your set of files can grow substantially. It is recommended that you consider removing the old files. To do this, select File > Preferences > File for Rollback. Click Delete Saved Files. To return to a previous version, you must use files from the media or repositories that created the install package.
7.0.0.1 Interim Fix 001
Fix release date: 28 January 2010Last modified: 28 January 2010
Status: Recommended
The following list describes the components that have been updated. APAR numbers, if applicable, are also listed.
Component | APAR | Description |
Adapters | See WebSphere Adapters V7.0 fix list for WebSphere Integration Developer V7.0 | |
Monitor Support | When the monitor model was generated for a BPEL process with an inline human task, the wizard would not launch properly. |
There have been updates to the WebSphere Process Server V7.0.0.1 runtime, which is included with this interim fix if you installed the IBM WebSphere Process Server V7.0.0.1 test environment feature.
WebSphere Process Server and WebSphere Enterprise Service Bus have enabled a new business object framework as a Technology Preview in the 7.0.0.1 Fix Pack.
Applications created with WebSphere Integration Developer 7.0.0.1 can be deployed to a WebSphere Process Server for Multiplatforms or WebSphere Enterprise Service Bus for Multiplatforms server which is at the 7.0.0.1 level or later. They can also be deployed to a 7.0.0.0 level if the new V7 business object runtime framework is not used.
Applications created with WebSphere Integration Developer 7.0.0.1 can be deployed to a WebSphere Process Server for z/OS or WebSphere Enterprise Service Bus for z/OS server which is at the 7.0.0.1 level or later. They can also be deployed to a 7.0.0.0 level if the new V7 business object runtime framework is not used.
When using Installation Manager for updates, your set of files can grow substantially. It is recommended that you consider removing the old files. To do this, select File > Preferences > File for Rollback. Click Delete Saved Files. To return to a previous version, you must use files from the media or repositories that created the install package.
7.0.0 Fix Pack 1 (7.0.01)
Fix release date: 26 June 2012Last modified: 26 June 2012
Status: Recommended
The following list describes the components that have been updated. APAR numbers, if applicable, are also listed.
Component | APAR | Description |
Activity editor | JR35060 | Business object extended from simpleType does not compile in a CustomSnippet. |
Content Assist Window in the activity editor can now be resized. | ||
Adapters | JR35026 | Data handler definition file unexpectedly updated. |
A new checkbox is added in the wizard to disable XA (Extended Architecture) connection for the MQ and MQJMS bindings. | ||
Business process editor | Business process input variable name with hyphen will not generate validation error when saved. | |
Double-clicking the Data Map activity will now open the map editor. | ||
Local variable in the Tray Category View will not disappear after right-clicking on it. | ||
Refactoring a renamed variable will no longer result in a null pointer exception. | ||
Selections in the compensation handler are now showing up on the Properties tab. | ||
Business process instance administration task with null reference is not modifiable during process migration. | ||
Business vocabulary editor | Business vocabulary in a folder structure can now be resolved by Business Service. | |
Expanded the list of simple types allowed for Business Items implementation. | ||
Comparing and merging | Duplicate library dependency will no longer occur during comparing and merging. | |
Documentation | Numerous additions to the installed Help. | |
Added information on how to run server scripts when the server install directory contains spaces. | ||
The instructions for task flow’s "Create a sample service" now opens the correct module. | ||
Updated the steps on how to create referenced attachment application. | ||
Added documentation to describe a V6.2 module with a mix of Web Service exports using JAX-RPC SOAP/HTTP and JAX-WS SOAP/HTTP will not migrate to V7.0. | ||
Updated instructions with additional step to avoid errors in the Reading and Writing Files sample. | ||
Human task editor | Lotus Form content is now correctly updated when the related Business Items are updated. | |
A null pointer exception no longer occurs when selecting the “Potential Owner” and switch to Properties tab in the Aggregation page. | ||
Interface editor | JR35203 | Interface with name-space containing back slash is now recognized. |
Exception no longer happens when generating Web Service export with attachment type. | ||
Integration test client | JR35133 | Exception opening old .wbiexetrace file. |
JR35151 | Performance delay in WebSphere Integration Developer when loading the date from datapool. | |
Publishing a renamed application when URL hostname verification is enabled no longer results in failure. | ||
Specifying "Never Occur" in the component test suite editor now works properly. | ||
The date value for simple list type is serialized in the proper format recognizable by the XML parser. | ||
Deployed test projects in the component test explorer are now appearing in the list of test cases to run. | ||
Using headless WebSphere Integration Developer mode, the GET task will no longer return an input/output exception. | ||
Mediation flow editor | The editor will no longer be marked as edited when navigating between rows in MessageFilter flows. | |
ServiceInvoke connections have been added in the Overview for existing project interchanges. | ||
Static gateway generation with empty mediation flow component no longer fails when the set header information checkbox is enabled. | ||
Migration | Support has been added for the V7 business object runtime framework. | |
Module deployment editor | RunAs support is now added. | |
Patterns | Broken link warnings are no longer issued. | |
When two modules are created based on a proxy gateway pattern and a dynamic gateway pattern, a dependent warning is no longer issued. | ||
Reporting | JR35200 | The report documentation of mediation flow created in a folder is properly generated. |
JR35201 | Java files containing DBCS character will be reported correctly. | |
JR35202 | The Assembly Documentation Unit no longer throws a Null Pointer Exception for a component without a type attribute. | |
XML mapping editor | JR35022 | Submap involving SMO element contains an error marker. |
The validation error is no longer issued when a lower-case 'and' is used in the XPath expression. | ||
Deleting an empty project when the Test Map view is on no longer results in a null pointer exception. | ||
Validation error is now issued when there are more the two submap mappings on the same root. |
There have been updates to the WebSphere Process Server V7.0.0.1 runtime, which is included with this interim fix if you installed the IBM WebSphere Process Server V7.0.0.1 test environment feature.
WebSphere Process Server and WebSphere Enterprise Service Bus have enabled a new business object framework as a Technology Preview in the 7.0.0.1 Fix Pack.
Applications created with WebSphere Integration Developer 7.0.0.1 can be deployed to a WebSphere Process Server for Multiplatforms or WebSphere Enterprise Service Bus for Multiplatforms server which is at the 7.0.0.1 level or later. They can also be deployed to a 7.0.0.0 level if the new V7 business object runtime framework is not used.
Applications created with WebSphere Integration Developer 7.0.0.1 can be deployed to a WebSphere Process Server for z/OS or WebSphere Enterprise Service Bus for z/OS server which is at the 7.0.0.1 level or later. They can also be deployed to a 7.0.0.0 level if the new V7 business object runtime framework is not used.
When using Installation Manager for updates, your set of files can grow substantially. It is recommended that you consider removing the old files. To do this, select File > Preferences > File for Rollback. Click Delete Saved Files. To return to a previous version, you must use files from the media or repositories that created the install package.
Was this topic helpful?
Document Information
Modified date:
17 June 2018
UID
swg27017696