===================================================================================
IBM® WebSphere® Business Integration (BI) Workbench
TM Version 4.2.4 - Patch24 - Readme File
===================================================================================
© Copyright International Business Machines Corporation. 2002, 2006. All rights reserved.
The BI Workbench v4.2.4 - Patch24 requires a previous installation of the full version of BI Workbench 4.2.4 Fix Pack3
Important note: Make sure to close the IBM WBI Toolset - System Manager before installing BI Workbench 4.2.4 Patch24, and before starting BI Workbench for the first time, after the BI Workbench 4.2.4 Patch24 has been installed.
Important note: When you attempt opening an existing organization using BI Workbench v4.2.4 - Patch24, a data conversion will take place and the organization file will be updated. For any organization opened or created using BI Workbench v4.2.4 - Patch24, this organization must not be opened again using previous versions of BI Workbench, such as BI Workbench v4.2.4 Fix Pack2.
Known Anomalies:
The process
model complexity for FDL export, or expansion of process for analysis, is bound by the
following equation:
t * sn
< 30,000
That is to say ( t * s to the power of n ), where:
t = average number of tasks per process
s = average number of sub-processes per process
n = average number of nested levels
The recommended free memory is 1 GB.
New Updates:
Added the SM Business Object Name combo box in the WBI Collaboration Applications dialog box. This combo box allows you to specify the name of a Business Object and associate it with the current collaboration application. Upon export of the process to FDL file, the SM Business Object Name will be one of the parameters pertaining to this collaboration application.
Added validation to the Workbench Server validation, in order to report duplication of employees roles. Correction steps are described. This update fixes the problem related to PMR 37590,531,864.
The FDL file can be exported to WebSphere MQ Workflow 3.6
BI Workbench supports IBM WebSphere Business Integration Toolset - System Manager version 4.3
The user interface items related to Corticon integration can be shown or hidden: A new preference is added to the Preferences dialog box to show/hide the following items:
When importing FDL file: In case an unqualified UPES is used by a task, the UPES name is stored as "Unqualified," and is added to the system.
Any missing business measures metrics are checked during the business measure validation. A new type of error (Business Measure without metric) is added to the Business Measures Validation report.
The User name of an employee can include a dash "-" character
A user-defined "FMCINTERNALNOOP" application (NOOP program) is exported in the FDL file.
The BI Workbench integrates with Corticon Studio V2.8
The FDL file can be exported to WebSphere MQ Workflow 3.5
The Organization file name length can be up to 80 bytes.
The following must be considered while defining the MQ Workflow Name for a Task object:
BI Workbench - UML Modeler supports exporting UML Models to all Rational® XDE™ 2003 builds.
The BI Workbench supports now the integration with the IBM WBI Toolset 4.2.1.1 Fix Pack, IBM WBI Toolset 4.2.2, and IBM WBI Toolset 4.2.2.1 Fix Pack.
The Currencies data cannot be imported now using the Import Data feature.
A specific FDL file can be now exported for z/OS™ and OS/390® platforms to comply with the requirements of these platforms. This can be done by selecting a new check box named FDL for the mainframe OS/390 in the Export FDL Options dialog box. This check box appears only when you select to export the FDL file for MQ Workflow v3.3.2 SP3 or WebSphere MQ Workflow v3.4 from the Workflow Engine dialog box.
The Node name can be up to 35 bytes, but it will be truncated to 32 bytes in the exported FDL file.
The Entry Point text box, in the Applications dialog box, is validated to hold a maximum of 32 bytes.
The decimal precision for currencies exchange rate can be up to seven decimal places.
The Working Directory for an application is not mandatory any more. However, it must be defined, if the organization FDL file is planned to be imported to IBM MQ Workflow Buildtime.
The Service text box in the Applications dialog box must be defined, in order to allow definition of other text boxes in this tab.
The Task name can be up to 235 bytes.
The Process name can be up to 235 bytes.
The External Process name (in the E-Commerce editing mode) can be up to 235 bytes.
When using BI Workbench on a system locale that is not supported, then the organization will be opened as read only.
The exported Simulation results can include now up to 32,000 jobs instead 16,300 jobs by using a new enhanced exporting tool.
The Time Between Jobs option in the Simulation Setup dialog box is now validated so that it does not exceed one year.
Fixed bugs:
ِAPAR JR23292 Fixed the bug that caused the FDL export to miss mappings from source (input structure) to global container, when the field names are different.
APAR JR23143 Fixed the documentation bug related to the limitation of process model complexity for FDL export, or expansion of process for analysis. Check the Known Anomalies section above for details.
APAR JR22595 Fixed the bug that caused long expressions to be truncated when model is exported to the Monitor XML.
APAR JR22269 Fixed the bug that caused employees not to be exported in Monitor XML, due to a huge organization units structure.
APAR JR22153 Fixed the bug that caused the Sundays and Mondays to appear as non-working Calendar days in some locales, such as English Australian Locale.
APAR JR22035: Fixed the bug that caused the import of FDL file to create corrupted connectors records for the 'FMCINTERNALNOOP' activity.
APAR JR21794: Fixed the bug that caused the export/import of BPM XML or the export of structures as XSD to fail when the current Windows user does not have administrative privileges over the machine.
APAR JR19404 The user can select the notes type (Basic Description or MQ Description) to be exported/imported with XML files.
APAR JR19756 Fixed the bug that causes the Analysis reports to display # values in some cells when working on a user locale that uses a decimal sign for numbers (for example, comma) that is different from the default decimal sign used by the current system locale.
APAR JR19992 Fixed the bug that caused BI Workbench fail to open when launched from the System Manager.
APAR JR19993 Fixed the following: 1- The bug that caused huge cycle time value to appear in the PC Times sheet of the Process Summary report. 2- The bug that caused the process time to be calculated based on the Standard Calendar while another calendar is assigned to the organization.
APAR JR20062 Fixed the bug that caused the Business Measures dialog box not to list locations whose names are segments of other existing locations.
APAR JR20063 1- Fixed the bug that caused the BI Workbench not to import the entire CSV file, if the any of the file data includes special characters, such as è, ò, é, ë. 2- Fixed the bug that caused BI Workbench to crash while importing Employees file to an organization that contains huge number of roles.
APAR JR20104 Fixed the bug that caused the BI Workbench 4.2.4 Fix Pack1 HotFix not to be installed on Windows 98.
APAR JR20105 Fixed the bug that caused the Underscore character not to be accepted in the System Group name.
APAR JR20116 Fixed the bug that prevented using dots in the Number text box in the Functions dialog box and the Business Rules dialog box.
APAR JR20158: Fixed the bug that caused BI Workbench to crash while working on the Data Fields Metrics dialog box in an organization that contains multiple copies of data structures.
APAR JR20149: Fixed the bug that caused the order of items in the Data Structures Tree to be lost, when using the Import Processes feature.
APAR JR20135: Fixed the bug that caused existence of duplicate roles upon repeating the import of employees file.
APAR JR20134: Fixed the bug that caused BI Workbench not to accept negative values for the Initial value field in the Data tab of the Task object dialog box.
APAR JR20186 Fixed the bug that caused changing the initial values of the global container, the input container, or the output container in the Task object dialog box, when the corresponding initial values in the Process Info dialog box were changed.
APAR JR20322 Fixed the bug that caused the Documentation Reports of LOV process (displayed in the LOV editing mode) to display unsorted tables with distorted headers. Also, fixed the bug that caused the Information Flow report to show improper data in the tables.
APAR JR20321 Fixed the bug that caused the creation of, and the inability to delete, duplicate records for previously deleted metrics or expressions used in business measures.
APAR JR20376 Fixed the bug that caused BI Workbench to crash on Windows XP SP2.
APAR JR20385 Fixed the bug that caused the incompletion of some simulation jobs due to the definition of a repetition value for one or more sub-processes.
APAR JR20418 Fixed the bug that caused automatic export of the 'Vocabulary_Structure' data structure, and the 'INTERNALCORTICONAPPLICATION' application in the FDL file, regardless they are being used or not. Those items are now exported in the FDL file, only if they are used by one or more of the diagram objects.
APAR JR20473 Fixed the bug that caused the UPES version 3.5 not to be shown in the the Servers dialog Box, and caused the System version 3.5 not to be exported in FDL file.
APAR JR20502 Fixed the bug the caused the exported FDL to contain expressions numbers that are formatted according to the locale settings. Any expression numbers are now exported unformatted, regardless of the locale settings.
APAR JR20574 Fixed the bug that caused the loss of business measure data after updating a business measure that uses a predefined metric.
APAR JR20734 The process Valid From time is exported in FDL after being converted to its UTC TimeZone equivalent, for compatibility with MQ Workflow.
APAR JR20760 Fixed the bug that caused the exported BI Monitor XML file not to include the multiple states of an activity specified in the business measure Locations dialog box.
APAR JR20959 Fixed the bug that caused the duplication of "MESSAGE_LAYER_REFRESH_INTERVAL" attribute in the Operation section of the Domain, System Group, or System in the exported FDL file.
PMR 54018,180,000 Fixed the error that occurs when exporting the FDL file, in case no employee password exists. A default password "password" is included in the exported FDL file.
PMR 60368,379,000 Explicitly stated in the documentation that the simulation is based on the working duration of the process tasks.
PMR 21137,180,000 Fixed the bug that caused the MQWorkflow validation report to issue a warning of duplication when a choice has the same name of a task.
PMR 55747,379,000: Modified the Export FDL Options dialog box to allow selecting multiple sub-processes to be exported in an FDL file. A List box is added to enable the user to select multiple sub-processes for export (instead of having to select all sub-processes, which might include sub-processes not planned to be exported).
PMR 81642,999,000 Added to the documentation definitions of R-Blocked Duration, in both the Jobs and Activity simulation tables.