===================================================================================
IBM® WebSphere® Business Modeler Advanced Version 6.0
Interim Fix 3 Readme
===================================================================================

© Copyright International Business Machines Corporation. 2004, 2005. All rights reserved. 

This is a interim fix for WebSphere Business Modeler Advanced Version 6.0. 

Installing the interim fix
Fixes included in this interim fix

Installing the interim fix

The following information describes how to apply this interim fix to your WebSphere Business Modeler installation.

To install the interim fix, complete the following steps:

  1. Download the 6.0-WB-ModelerAdv-IF0000003.zip file.
  2. Double-click the downloaded 6.0-WB-ModelerAdv-IF0000003.zip file, and extract the files into a temporary directory.  The rest of these instructions assume that the files have been extracted to C:\temp\.
  3. Start WebSphere Business Modeler.
  4. Click Help > Software Updates > Find and Install. The Install/Update wizard opens.
  5. Select Search for new features to install and click Next.
  6. On the Update sites to visit page, click New Local Site. The Browse for folder window opens.
  7. In the Browse for folder window, navigate to C:\temp\6.0-WB-ModelerAdv-IF0000003. Click OK. You return to the wizard, and the site that you specified is included in the Sites to include in search list.
  8. Select the site that you have just added and click Next.
  9. On the Search Results page, click Select All.
  10. Click Next.
  11. On the Feature License page, read the license agreement for the feature you are installing. When are you are finished, accept the agreement by clicking I accept the terms in the license agreement, and then click Next.
  12. Click Finish on the Install Location page.
  13. Follow the on-screen instructions to complete the installation. During the installation, you must confirm that you want to install an unsigned feature.
  14. When you are asked if you want to restart the workbench, click Yes.

The interim fix is now installed.

Fixes included in this interim fix

This is a cumulative interim fix for WebSphere Business Modeler Advanced Version 6.0. In addition to the most recent fixes, it includes the fixes from all of the previous WebSphere Business Modeler Advanced Version 6.0 interim fixes.

Fixes included in Interim Fix 3

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
35896,300,624 JR22943 Enables display of broken references of organizations and classifiers in editors and views, allowing you to locate and correct broken references.
JR23127 Enables the generation of predefined reports for sample ABC project.
35896,300,624 JR23185 Improves error detection during migration allowing the migration to continue processing.
07313,800,624 JR23202 Reduces the risk of out of memory errors during the generation of predefined process reports.

Fixes included in Interim Fix 2

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
06720,756,000 JR23041 Correct a problem for generating a report from the process editor for the customer process model.
07980,999,000 JR23071 Correct display of elements in report diagram being filled with solid black after performing generate and export report from process editor.
JR23110 Further correction for line wrap of long strings in reports.

Fixes included in Interim Fix 1

This interim fix includes the following fixes, all of which are associated with APAR JR23014:

Product notes

Problematic scenarios related to report generation.

Scenario 1

  1. Create a project with a process with an ampersand character in the name.
  2. Generate a Process details report.
Result: Report generation fails with message "Export failed and no file generated".

Circumvention: Rename the process and remove the ampersand.

Scenario 2

  1. Create a project with a default process.
  2. Create a classifier and value.
  3. Reference the classifier value in the process.
  4. Export the process only.
  5. Import the process (project) into a new project. Note, there will be a broken reference in the classifier tab, error markers in the Project tree, and validation errors in the error view.
  6. Generate a Process details report.
Result: Report generation fails with message "Export failed and no file generated".

Circumvention: Fix the broken references via the attributes view or specification page. Beware of the caveats of Scenario 2 and Scenario 3.

Alternate Scenario 2

Perform Scenario 2 but instead of exporting/importing the process, delete the classifier value to create a broken reference on the process.

Scenario 3

  1. Create a project with a default process.
  2. Create a classifier and value.
  3. Reference the classifier value in the process.
  4. Export the process only.
  5. Import the process (project) into a new project. Note, there will be a broken reference in the classifier tab, error markers in the Project tree, and validation errors in the error view.
  6. Fix the broken reference via the classifier tab of the process' attributes view, by removing the entry.
  7. Generate the Process details report. Note, the report is generated.
  8. Try to delete the process.
Result: The process is not deleted.

Circumvention: Restart modeler and perform the delete action. Note, the import action may also fail, as described in the results, if the import includes the same process which was imported in step 1.

Alternate Scenario 3

Perform Scenario 3 but instead of exporting/importing the process, delete the classifier value to create a broken reference on the process.

Scenario 4

  1. Create a project with a default process.
  2. Create a classifier and value.
  3. Reference the classifier value in the process.
  4. Export the entire project.
  5. Import the project into a new project.
  6. Generate the Process details report. Note, the report is generated.
  7. Try to delete the process.
Result: The process is not deleted.

Circumvention: Restart modeler and perform the delete action. Note, the import action may also fail, as described in the results, if the import includes the same process which was imported in step 1.

Alternate Scenario 4

Perform Scenario 4 but do not export/import the project.

Restrictions on naming metrics, counters, and stopwatches in business measures editor

When you are creating business measures models, you should avoid using the predefined names indicated in the following list when naming metrics, counters, and stopwatches in global processes or in local processes and loops. If you use one of these names, errors can occur during import, export, or versioning of a project.

Setting values for complex attributes in situation events

If you have a situation event with a complex attribute (for example, an attribute whose type is a business item), you can set the values of the complex attribute after adding the situation event to a business measure such as a KPI. To do this, complete the following steps:

  1. Right-click the attribute and select Add instance value.
  2. Enter a name for the instance.
  3. Expand the instance and enter a value or calculation for each attribute by right-clicking the Attribute calculation cell and clicking the button that is displayed.

Limitation on sharing workspaces between WebSphere Business Modeler Basic and WebSphere Business Modeler Advanced

If you upgrade from WebSphere Business Modeler Basic to WebSphere Business Modeler Advanced, you should not use the same workspace, or projects will not behave as expected. Instead, if you want to use a project that you modeled in WebSphere Business Modeler Basic after upgrading to WebSphere Business Modeler Advanced, you should export the project from the Basic workspace and then import it into Advanced, or use versioning to access the project from the different workspaces.