===================================================================================
IBM® WebSphere® Business Modeler Basic Version 6.0.1
Interim Fix 3 Readme
===================================================================================
© Copyright International Business Machines Corporation 2006. All rights reserved.
This is an interim fix for WebSphere Business Modeler Basic Version 6.0.1.
Installing the interim fix
Fixes included in this interim fix
To install the interim fix, complete the following steps:
The interim fix is now installed.
This is a cumulative interim fix for WebSphere Business Modeler Basic Version 6.0.1.
This interim fix includes the following fixes. The PMR and APAR numbers associated with each fix have been included.
PMR Number | Related APAR Identifier |
Description |
07439,800,624 | JR23833 | Corrects the behavior of open but unmodified processes being reported as changed when a team member synchronizes the project. |
14273,756,000 | JR24103 | Allows process names to appear correctly when you export diagrams for different processes to PDF. |
01467,999,000 | JR24153 | Ensures that diagrams are included in process summary reports. |
This interim fix includes the following fixes, both of which are associated with APAR JR24286:
This interim fix includes the following fixes. The PMR and APAR numbers associated with each fix have been included.
PMR Number | Related APAR Identifier |
Description |
14547,693,693 | JR23748 | Corrects a failure in query creation. |
09035,756,000 | JR23859 | Corrects layout problems in complex process diagrams. See product notes for further instructions related to this fix. |
39417,531,864 | JR23981 |
Corrects a problem with project checkouts from CVS repository leading to a "Cannot check out unknown project" error |
This interim fix includes the following fix, which is associated with APAR JR24040:
This interim fix includes the following fixes. The PMR and APAR numbers associated with each fix have been included.
PMR Number | Related APAR Identifier |
Description |
39326,531,864 | JR23617 | Corrects the display of organizations after publishing. Intended for use with interim fix 1 for WebSphere Business Modeler Publishing Server Version 6.0.1. |
84042,999,000 | JR23694 | Corrects the sorting behavior of Project Tree elements after publishing. Intended for use with interim fix 1 for WebSphere Business Modeler Publishing Server Version 6.0.1. |
39377,531,864 | JR23701 | Allows the importing of graphic formats other than JPEG after customizing a process summary report. |
This interim fix includes the following fixes, all of which are associated with APAR JR23894:
This interim fix includes the following fixes. The PMR and APAR numbers associated with each fix have been included.
PMR Number | Related APAR Identifier |
Description |
39236,531,864 | JR23567 | Enables the migration of role availability from Version 4.2.4. |
39312,531,864 | JR23614 |
Replaces the tilde (~) from names that are truncated during import from Version 4.2.4 and replaces them with an underscore (_). |
39312,531,864 | JR23615 | Prevents the creation of elements beginning with the tilde (~) character. Existing elements that begin with a tilde must be manually changed. |
07445,800,624 | JR23679 | Corrects import behavior that propagated errors caused by corrupted models. |
39375,531,864 | JR23616 | Improves import performance from Version 4.2.4 for large models. |
JR23666 | Corrects the display and printing of process detail catalogs when a project has multiple data catalogs. | |
JR23665 | Updates to translated GUI for the Korean language. | |
JR23681 | Enables alignment icons in report designer. | |
39377,531,864 | JR23702 | Allows use of relative graphic paths in reports. |
14547.693.693 | JR23747 | Corrects behavior of the starts-with query function. |
This interim fix includes the following fixes, all of which are associated with APAR JR23796:
To make the interim fix changes take effect, complete the following steps:
The installation instructions recommend that you create a new folder to hold the WebSphere Integration Developer features. This statement refers to the WebSphere Business Modeler features that you are installing into WebSphere Integration Developer. The release notes additionally state that this recommendation be taken as mandatory.
However, it is no longer recommended that you create a new folder. Instead, it is recommended that you accept whichever folder is presented to you as the default installation location. The creation of a new folder has been found to cause configuration issues that stop WebSphere Business Modeler from functioning properly. In particular, a new folder causes the Modeler perspective and functionality to become inaccessible. If you have installed WebSphere Business Modeler into its own folder, you can correct the configuration by completing the following steps: