===================================================================================
IBM® WebSphere® Business Integration Modeler Advanced Edition Version 5.1.1.1 - Readme File
===================================================================================

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

WebSphere Business Integration Modeler Advanced Edition Version 5.1.1.1 requires a previous installation of WebSphere Business Integration Modeler Advanced Edition Version 5.1.1

The following information is taken from the About this release section of the WebSphere Business Integration Modeler Advanced Edition Version 5.1.1.1 Release notes, supplemented with a list of PMRs and their related APARs addressed with this release.  You can find additional release-specific information can be found in the Release notes section of the product documentation, which you can download from www.ibm.com/software/integration/wbimodeler/library/.

Table of Contents

Backward compatibility
Language support and globalization
Additional function
PMR and APAR fixes

Backward compatibility

The following describes compatibility issues between this and any previous versions of the product.

For information on migrating from WebSphere® Business Integration Workbench Version 4.2.4, see Migrating from WebSphere Business Integration Workbench 4.2.4 to Business Integration Modeler in the full documentation.

Process models created with a Beta release of the product are compatible only with the Beta release that was used to create them. They are not compatible with this release of the product.

Do not install IBM® WebSphere Business Integration Modeler Advanced Edition on top of the Trial Edition. Uninstall the Trial Edition first.

Language support and globalization

The following are the language support and globalization notes for the product.

Untranslated contents in this release

This fix pack contains numerous additions and changes to functionality for which no translated text is provided, particularly in the Simulation and Dynamic Analysis components. When you use Business Integration Modeler in a language other than English, some text on the user interface will appear in English rather than in the selected language. In addition, text that has been updated in the user interface in this version has been updated only in English; translated text appears as it did in Version 5.1.1.

The help system in Business Integration Modeler Version 5.1.1.1 is provided in English only. Documentation that has been added or updated in this version to cover new and existing functions of the tool does not appear in a translated version. It is recommended that you install the English language help system for 5.1.1.1. If you want to continue to have access to translated versions of the 5.1.1 help system, you can also install a stand-alone version of the translated help system for that release. You can download translated versions of the 5.1.1 help system from the Business Integration Modeler library Web site, http://www-306.ibm.com/software/integration/wbimodeler/library/ .

Bidirectional language support

Because of limitations in the underlying framework upon which Business Integration Modeler is based, support for bidirectional mirroring is imperfect. The process editor cannot create right-to-left diagrams, and not all windows and menus mirror properly, though the majority of them do.

The Preview Dialog window for reports and diagrams does not correctly display or print process diagrams, structure diagrams, or structure definition diagrams if those diagrams have elements that contain bidirectional text, such as Arabic. To print diagrams that contain bidirectional text, you must do the following:
  1. Export the diagram to a Scalable Vector Graphics (SVG) or JPG file.
    Note: SVG format produces better quality output than JPG format.
  2. Open the diagram in a compatible viewer. Some possible SVG viewers are Adobe SVG Viewer, available at www.adobe.com/svg/, and Corel SVG Viewer, available at www.corel.com/svgviewer/
  3. Print the report or diagram from the SVG viewer that you have chosen.

To print reports with diagrams that contain bidirectional text, you must do the following:

  1. Export the report to an SVG or HTML file.
    Note: HTML reports still use SVG diagrams
  2. Open the report in a compatible viewer. Some possible SVG viewers are Adobe SVG Viewer, available at www.adobe.com/svg/, and Corel SVG Viewer, available at www.corel.com/svgviewer/
  3. Print the report from the viewer that you have chosen.
Note: When printing large diagrams from SVG, printing behavior depends on the SVG viewer you have chosen. For example, Batik viewer scales large diagrams to fit on a single page. Other SVG viewers print only the first page of the diagram. You cannot print multiple pages of a diagrams.

Delimited text import and export

A project that was exported as delimited text under one set of locale settings can only be imported back into Business Integration Modeler when running under the same locale settings. Additionally, the delimited text file is encoded and decoded using the ANSI code page that is present on the system at the time. A file can only be imported if the code page on the importing system is the same as the one that was used to produce the file.

For example, if you export a project to delimited text while running under an English locale you can only import it on a computer running under an English locale. The delimited text sample that comes with Business Integration Modeler was created on an English machine so it can only be imported if your computer is also running under an English locale.

Display of numerals in the report preview dialog

Numerals are displayed in the report preview dialog using the Arabic digits, 0,1,2,3,4,5,6,7,8, and 9, in all locales.

National language enablement

Business Integration Modeler is enabled to work in the following languages:

Modeler supports each of the languages mentioned above, with the following exceptions:

Retention of localized element names

The names of project elements do not change when the project is loaded in another locale. For example, if you create a project in Japanese, and then change your locale to English, the project created under the Japanese continues to display the names of elements in Japanese. If you encounter problems with the way characters in the product display, ensure that the default locale of your computer matches the locale that project was created in.

Additional function

The following functions are new additions to Business Integration Modeler that did not appear in previous versions.

Changing icons

When you change an icon that you have associated to a model element, the Change Icon window now displays the available icons at a glance. For more information, see Changing icons in the full documentation.

Dynamic Analysis

In this release, the following new features have been added:

Expression Builder

A number of small changes to the Expression Builder have been made in this release. For example, the process name now appears only once in the expression. For more information, see Creating expressions.

Importing and Exporting

You now have the ability to choose whether or not to create a simulation profile when you import an .org file. If you choose not to create the simulation profile then simulation information in the original model, such as the choice decision percentage values, is not migrated.

Profile Analysis

This release includes simulation profile analysis features, which enable you to analyze simulation profiles before you run a simulation. The following types of simulation profile analysis are provided:

You can enable the matching of process case names between profile and dynamic analysis. If you do this, all case names generated in profile analysis and dynamic analysis will correspond to the same process cases. For more information, see Enabling case name matching in the full documentation.

Reports and Printing

This release includes the following changes to reporting and printing features:

Repositories

You can now mark global and local repositories as "unique." By doing this, you specify that no two items in the repository can have the same value. For example, you can mark a repository unique if it is being used to store IDs, orders, or invoices. For more information, see Creating repositories in the full documentation.

Simulation

You can now use DB2 to capture simulation results, as well as Cloudscape (provided as the default). For more information, see Set up DB2 database in the full documentation.

Numerous changes have been made to the simulation Attributes View.

Performance improvements have been made to dynamic analysis functions.

Simulation Control Panel

This release includes the following changes to the Simulation Control Panel:

PMR and APAR fixes:

The following PMRs and APARs have been addressed in this release of the product:

PMR Number Related APAR Identifier Description
00336,122,000

JR20427

The check-in and check-out performance of the team support function has been improved.
04657,999,760 Not Applicable Problems with updating timetables have been fixed.
06153,999,766 Not Applicable Problems with simulation have been fixed.
06427,122,000 JR20661 Automatic element resizing behavior in the process editor has been improved.
07029,122,000 JR20623 Reports are now available to provide working duration path time of process paths based on simulation data.
07030,122,000 JR20622 Reports are now available to provide cost and time by business case.
07032,122,000 JR20581 Probabilities displayed in the dynamic analysis Process Instances Summary report have been fixed.  New Process Cases Summary and Process Resource Allocation analyses have been added.
07043,122,000 JR20582 New options are now available for printing models.
07081,122,000 JR20578 Performance of simulation snapshot creation has been improved.
07112,122,000 JR20624 Analyses have been updated to improve consistent use of units of measure.
07113,122,000 JR20625 You are now prompted to save any changes you make in the Attributes view of a simulation snapshot before running the simulation from the control panel.
07143,122,000 JR20654 The token threshold limit has been increased.
07151,122,000 JR20648 Migration of Phi objects no longer appends numbers to the object names.
07261,122,000 JR20644 Migration documentation has been updated with information on migrating transfer durations.
35045,499,000 JR20674 The handling of importing a corrupt ZIP file has been improved.  If you import a corrupt ZIP file, the rest of the folder now remains accessible without requiring you to restart the product.
36086,010,678 JR20615 The release notes have been updated to indicate that only Business Integration Modeler views should be used to carry out Business Integration Modeler tasks.
70032,69C,760 JR20807 The documentation on BPEL mode constraints has been updated.
71641,999,000 Not Applicable You can now migrate organizations created with Workbench 4.2.4 Fix Pack 3
86061,422,000 JR20485 Performance of report generation has been improved.