===================================================================================
IBM®
WebSphere® Business Modeler Advanced Version 6.0.1
Interim Fix 7 Readme
===================================================================================
© Copyright International Business Machines Corporation 2006. All rights reserved.
This is an interim fix for WebSphere Business Modeler Advanced Version 6.0.1.
Attention:
Once you install WebSphere Business Modeler Interim Fix 6 or above, you can no longer publish projects to WebSphere Business Modeler Publishing Server Version 6.0.1. For more information, see the product notes. |
Installing the interim fix
Fixes included in this interim fix
Product notes
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 Advanced Version 6.0.1.
This interim fix includes the following fixes. The PMR number and APAR identifier associated with each fix have been included.
PMR Number | Related APAR Identifier |
Description |
39323,531,864 | JR23700 | Corrects the publishing layout settings so that you can view the organization information for projects in WebSphere Business Modeler Publishing Server Version 6.0.2. |
81623,227,000 | JR25000 | In custom reports that use the process procedure data source, ensures that the correct description is included for activities that precede a global process. |
31615,499,000 | JR24460 | Corrects a misspelled word in the "Scope" section of the Process Procedure report template. |
This interim fix includes the following fixes. The PMR number and APAR identifier associated with each fix have been included.
PMR Number | Related APAR Identifier |
Description |
JR24787 | 12043,999,000 | In custom reports that use the process procedure data source, ensures that the procedure section contains the correct step descriptions. |
JR24843 | 03434,019,866 | Fixes the problem that generated an error message of "Unable to create part" when organizing process model elements by classifier in swimlane layout. For further information, see the product notes. |
This interim fix includes the following fixes, both of which are associated with APAR JR24964.
This interim fix also includes the updates required for publishing projects to WebSphere Business Modeler Publishing Server Version 6.0.2. All of these updates are associated with APAR JR24962.
This interim fix includes the following fixes. The PMR number and APAR identifier associated with each fix have been included.
PMR Number | Related APAR Identifier |
Description |
08842,000,724 | JR23983 | Corrects the display of while loop contents. This fix is required by the fix provided by IBM WebSphere Business Modeler Publishing Server Version 6.0.1 Interim Fix 4. |
72748,L6Q,000 | JR24374 | Corrects a failure to publish projects containing an ampersand (&). |
59328,010,678 | JR24649 | Corrects the display of process models in swimlane layout when the role names that contain a comma (,). For further information, see the product notes. |
This interim fix includes the following fixes. The PMR number and APAR identifier associated with each fix have been included.
PMR Number | Related APAR Identifier |
Description |
03407,49R,000 | JR24340 | In a team environment with a repository, allows you to create a WebSphere Business Modeler element with the same name as a deleted element in the same workspace. |
13282,756,000 | JR24315 | For simulations with subprocesses that contain loops with notification elements, ensures that the simulation results do not create an extra broadcast message. |
53404,766,766 | JR24514 | Ensures that the correct Korean characters appear as typed in input boxes in the Attributes view. |
72053,379,000 | JR24565 | Corrects the behavior of the start time for recurring intervals changing unexpectedly in timetables when a start date is changed in the Beginning on field. |
81919,057,649 | JR24104 | Corrects the behavior that caused a critical simulation error when running a simulation for the first time using step simulation with the default simulation settings. |
08359,756,000 | JR24420 | Allows the probabilities in a simulation with an inclusive multiple-choice decision node to add up to more than 100% for all of the branches. |
02774,033,000 | JR24430 | When specifying a Johnson distribution, ensures that a zero is not appended to a number entered in the Gamma field. |
31586,499,000 | JR24458 | When using the Expression Builder for modeling intermediate or advanced queries that reference a role requirement, corrects the term text displayed in the Expression text and Expression Tree views. |
13478,756,000 | JR24078 | Ensures that selecting the black-and-white print setting generates a black-and-white print preview and printed model. |
26435,999,724 | JR24343 | In a team environment with a repository, ensures that when elements are dragged and dropped from one catalog to another in the Project Tree view, the workspace synchronizes properly. |
This interim fix includes the following fixes, all of which are associated with APAR JR24619. For further information about the first two fixes, see the product notes.
This interim fix includes the following fixes. The PMR number and APAR identifier 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. |
80604,69C,760 | JR24059 | Allows changes made in the Attributes view of a process in WebSphere Process Server mode to persist. |
86383,180,000 | JR24084 | Allows exported business measures models to be imported into WebSphere Business Monitor. |
86389,180,000 | JR24085 | Corrects the tagging of URIs in exported XMI files that previously caused WebSphere Business Monitor errors. |
00246,999,000 | JR24093 | Ensures correct analysis results for the process elapsed duration and the working and resource durations of processes. |
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. |
93590,999,000 | JR24252 | Corrects a regression that occurred when a simulation with the maximum number of simultaneous tasks was run. |
This interim fix includes the following fixes, all of which are associated with APAR JR24286:
This interim fix includes the following fixes. The PMR number and APAR identifier associated with each fix have been included.
PMR Number | Related APAR Identifier |
Description |
91281,999,000 | JR23739 | Corrects the creation of duplicate metrics when you create a single metric. |
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. |
12017,756,000 | JR23860 | Allows propagation of changes made to probability values in the simulation viewer. |
93461,019,866 | JR23963 | Corrects uniqueness errors reported on WSDL import. |
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 fixes, all of which are associated with APAR JR24040:
This interim fix includes the following fixes. The PMR number and APAR identifier 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 number and APAR identifier associated with each fix have been included.
PMR Number | Related APAR Identifier |
Description |
73505,005,00 | JR23291 | Corrects calculation of Process Cost in the Activity Cost Aggregated Dynamic Analysis |
39236,531,864 | JR23567 | Enables the migration of role availability from Version 4.2.4. |
39312,531,864 | JR23614 | Removes the tilde (~) from names that are truncated during import from Version 4.2.4 and replaces it 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. |
39375,531,864 | JR23616 | Improves import performance from Version 4.2.4 for large models. |
07445,800,624 | JR23679 | Corrects import behavior that propagated errors caused by corrupted 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 take advantage of the new features of and performance enhancements in WebSphere Business Modeler Publishing Server Version 6.0.2, you must install WebSphere Business Modeler Version V6.0.1 Interim Fix 6 or above. You can now run WebSphere Business Modeler Publishing Server V6.0.2 on Linux distributions. Other benefits of the new WebSphere Business Modeler Publishing Server release include security enhancements, user interface improvements, and the treatment of Web addresses as hyperlinks.
If you have a process model with role names that contain a comma (,), you might have had problems with the display of its diagram in swimlane mode. For example, the assignment of the swimlanes might have been incorrect. The fix (JR24649) provided in Interim Fix 5 makes it easy to correct these problems. However, the Interim Fix 5 product notes contained incorrect instructions for fixing these swimlane layout display problems. Use the following instructions instead.
Note:
Although the fix JR24843 eliminates an error message of "Unable to create part" when you organize process model elements by classifier in swimlane layout, you might see a missing line below the last swimlane header (left column) when you open a process model that you created before this interim fix. You can correct this swimlane layout display problem using the following instructions.
To correct swimlane layout display problems, complete the following steps:
Once you have specified the time required for resources and assigned the resources to tasks, a simulation waits for the required resources to be available before it calculates the working duration for a task. You can now specify that the working duration for a task ends only when the last resource assigned to the task is done. The default behavior is for the working duration to equal the time allotted for a task.
To change your simulation configuration preferences to extend the working duration for tasks until the last resource assigned to each task is done, complete the following steps:
If you have a process model with a large number of nested processes and possible cases, identifying the static cases might cause WebSphere Business Modeler to hang or run out of memory. Updates to the business modeling preferences give you options for analyzing a process model that has a large number of possible cases without generating these problems.
Navigate to the business modeling preferences for dynamic analysis by clicking Window > Preferences, and then clicking Business Modeling > Dynamic Analysis.
Problem history:
Fix: When you install WebSphere Business Modeler as a set of Eclipse plug-ins with WebSphere Integration Developer, you must specify the ...\rwd\eclipse directory as the location for your installation.
If you have installed WebSphere Business Modeler in its own folder, you can correct the configuration by completing the following steps:
To make the interim fix changes take effect, complete the following steps: