Moved Permanently. The document has moved here. The following list identifies the supported releases of IBM Integration Designer from which you can select specific detailed system requirements.

1. V8.0.1

APAR Description Adapter WebSphere Adapters V7.5.0.X fix list for IBM Integration Designer V7.5.1 Assembly Unable to create EJB Import binding. When selecting Generate Export, Enterprise Java™Bean Binding, a NPException occurs when pressing Finish on the wizard. Build Project Error during building workspace after a process migration with migration specification. NPE during the build if a project contains webservice imports based on JAX-WS. Under some situations when building the workspace, an Error dial might appear reporting a NPE. Refresh and publish from IID to PC takes a long time when there are large bumber of PA/TKs,snapshots or BPD/AIS Snapshot installation fails due to an error computing changes for the process instance migration.

Business Object Slow performance for Business Object Editor The project cannot be build due to NullPointer exception. Business Process Cancel button is not handled properly under the Select or Add People Directory dialog (BPEL Human Task). SetProcessCustomProperty(String, String) method does not validate properly even though it is supported during runtime Deployment Unable to deploy the snapshot application which include an associated SCA module with BPEL templates.

Mediation Flow After migration of a Fan Out context the type definition can not be resolved. The order of values for the prmoted properties are not saved. Missing type information causes errors within Mediation Flow Editor.

Building the mediation flow takes a long time. The message enrichment parameter values are not visible. Build issue with mediation modules when connected to Rational Team Concert New asserted type made in primitive: 'Set Message Type' are not propagated Breakpoints in a mediation flow do not cause execution to stop Process Center Compare Merge performance issues when IID developers update IID workspace by refreshing from PC. Test Client If modules don't propagate HTTP headers, the test case response will not come back. Output data from Cross Component Trace does not show in the test client or server logs view.

Some Fine Grain Trace values do not appear due to an exception. Fault test case reply failed. XML Mapping Mapping the root type definition is not copied and causes the 'type can not be resolved' warning. Exception while parsing transformed XML. Unwanted XML map warnings. The following sysroutes are included from other products: JR46571,IC92126, IC95725, and IC91205.

APAR Description Adapter WebSphere Adapters V7.5.0.X fix list for IBM Integration Designer V7.5.1 Assembly The default parameter name for the throw activity is translated and in particular language locales, Brazilian Portuguese, French, German, Japanese, Korean, a space is included in the translation, which breaks the Java™ identifier rule. Business Process When adding a new Assign activity in the BPEL and choosing the Assign from/to variable under Properties Details, click '+' to expand a complex data type, the top level of the data type will be chosen instead of letting user traverse down the expanded list, to get to the desired element.

Deployment The custom callback handler is a selected list and a custom callback handler can not be put into the UI. Mediation Flow When a subflow property is promoted to the main flow, its property type is not correctly determined.

It always returns as a string type. 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. Type filter condition with root /body cannot be removed when the MFC editor is re-opened. Failure to correctly migrate Custom Mediation (Java) that contain try-catch clause. Dynamic terminals and its connecting wires of a Custom Mediation maybe missing after the flow is converted to the new mediation flow format. In mediation flow, got CWZMU0089E error in Service Invoke, created with Message Enrichment mode for an operation with complex type Process Center The test client may try to invoke a module contained in a Process App on a server that does not contain any Process Apps and report 'module not found'. For example, it may try to start a test on a messaging cluster member instead of an app target cluster member.

An Out Of Memory Error may occur during the building of the workspace when there are a large number of annotations in the generated schema files. Refresh and Publish from IID to Process Center takes a long time when there are a large number of Process Apps/Toolkits, Snapshots or BPD/AISs. Project Build When starting up IID on a workspace with certain types of artifacts, re-indexing takes place that may take a while to complete. This reindex occurs during every start-up on the workspace. XML Mapping 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.

V8.0.1

Was not found in the XML Schema.' The XSL Transformation engine encounters an exception during initialization. The XML Mapping Editor allows the user to specify some XSLT generation options from the Generation tab in the Properties view. The options in the Generation tab are translated for the user when running in a National Language other then English.

A problem occurs when the generation option stored for the map file takes the literal translation. This translation then propagates itself into the generated XSLT file which is an error. The options that get propagated into the generated XSLT file should only be in English, otherwise the XSL Transformation engine will encounter exceptions during initialization When editing an XML Map file within the XML map editor, error markers may appear on the file after saving. This problem only occurs when the input and/or output of the XML Map is referencing an XSD schema inlined within a WSDL, and the map was authored in a previous release to 7.5.1. The error markers that result from this problem have the following message: 'The schema.xsd input uri is not resolved.' XML Map SMO path migration fails for RPC style WSDL complex types. The namespaces declared on an element that is being moved are not copied to the target element.