Installing the interim fix

Use the software update function to install WebSphere Business Modeler interim fixes.

To install the interim fix, complete the following steps:

1. Download the 6.0.2.1-WB-ModelerAdv-IF0000003.zip file.
2. Double-click the downloaded 6.0.2.1-WB-ModelerAdv-IF0000003.zip file, and extract the files into a temporary directory. The rest of these instructions assume that you extracted the files to C:\temp\.
3. In WebSphere Business Modeler, click Help > Software Updates > Find and Install. A wizard opens.
4. Select Search for new features to install, and click Next.
5. On the "Update sites to visit" page, click New Local Site. The Browse for Folder window opens.
6. In the Browse for Folder window, navigate to C:\temp\6.0.2.1-WB-ModelerAdv-IF0000003, and click OK. You return to the wizard, and the site that you specified is included in the Sites to include in search list.
7. Select the site that you just added.
8. On the Search Results page, click Select All to select both the product and the documentation features.
9. On the Feature License page, read the license agreement for the feature that you are installing. To accept the agreement, click I accept the terms in the license agreement.
10. On the Install Location page, click Finish. During the installation, you must confirm that you want to install an unsigned feature.
11. 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.2.1.

Fixes included in Interim Fix 3

This interim fix includes the following fixes. The PMR number and APAR identifier associated with each fix are included.

PMR Number	Related APAR Identifier	Description
25329,756,000	JR26217	Corrects problem with long save and import time when a cycle exists in a process model
01582,033,000	JR26325	Corrects problem with truncation in the Process procedure reports column heading
00002,I00,760	JR26353	Corrects a problem where an error message is incorrectly displayed after renaming an element with a single parenthesis when working in swimlane layout
	JR26377	Allows manual ordering of elements in the project tree and allows user to save ordering
62755,442,000	JR26392	Adds user friendly messages for exceptions that are surfacing to the end user during and after import action failure.
54509,L6Q,000	JR26478	Fixes problem with the Process procedure report when double quotes are used
55269,070,724	JR26570	Improves error messages TEN06510E and TEN06520E by adding quotes to indicate replaceable strings
64595,442,000	JR26582	Removes the copy action from the context menu in the project tree for predefined queuries

This interim fix includes the following fixes, all of which are associated with APAR JR26643.

• Corrects problem with missing x-axis information in chart generation
• Corrects problem with extra characters appended to category labels in charts
• Fixes button icons on the Welcome pages in a plug-in installation of the product
• Ensures that Hindi numbers are displayed in reports when running the product in Arabic
• Corrects code generated for the count function in a WPS export
• Synchronizes the measurement unit set in the general preferences for Report designer, and the unit reported for static text field via the attributes view for the Report designer
• Corrects regression with incorrect display of page numbers in generated reports

Fixes included in Interim Fix 2

This interim fix includes the following fixes. The PMR number and APAR identifier associated with each fix are included.

PMR Number	Related APAR Identifier	Description
41333,999,000	JR26319	Corrects process validation error when exporting for WPS.
49208,442,000	JR26347	Adds ability to auto-layout and maintain swimlane order.

This interim fix includes the following fixes, all of which are associated with APAR JR26381.

• Corrects check-out error from a repository when a user defined catalog has the same name as a default catalog.
• Allows the application of a report style master to a Crystal report template
• Allows the application of a report style master to a Predefined report
• Corrects a Report generation problem when parameters have been previously associated to a deleted page of a Report template
• Ensures Web service bindings are exported during a WebSphere process server
• Corrects BPEL variable name generation when input and/or output elements are of the same data type
• Eliminates exceptions when auto-layout is selected and performing a swimlane re-order

Fixes included in Interim Fix 1

This interim fix includes the following fixes. The PMR number and APAR identifier associated with each fix are included.

PMR Number	Related APAR Identifier	Description
65749,999,706	JR25993	Corrects failure to authenticate with a Publishing server when using long user ID and password combinations.
55048,999,000	JR26020	Corrects the ability to create expressions using simple type objects imported through Business service object import.
71850,033,000	JR26054	Enables scaling of SVG diagrams exported from Modeler's Process editor and embedded into a custom report.
71812,033,000	JR26092	Prevents a maximum path exception from occuring while attempting to perform Input and output paths static analysis on a connector in a process diagram.
04091,070,724	JR26101	Prevents a WebSphere process server export failure when attempting to reconcile duplicate inputs and outputs on import from a WSDL.
24835,756,000	JR26114	Adds missing references to SVG shapes of Business services on export to Monitoring toolkit.
25329,756,000	JR26217	Suppresses path cycle analysis to improve save and import times.

This interim fix includes the following fixes, all of which are associated with APAR JR26169.

• Corrects the default format type for a Business item's maximum attribute added to a report template.
• Removes a set of invalid diagram-related data fields for Process statistics, Process details and Process specification predefined queries and data sources.
• Corrects the calculation of the value for the number of Organization units in a Task statistics report.
• Removes the ability to generate the predefined Process procedure report for a Process catalog, in accordance with design specification.
• Adds missing Service catalog data to a generated Service specification predefined report template.
• Corrects the calculation of the value for the number of Bulk resources in a Service statistics report.
• Eliminates an exception when generating a Task by roles report on a process with a role requirement that does not have its role value set.
• Corrects the names shown in generated Service details and Task details reports for requirements, resources and roles.
• Prevents customized Report templates and Style masters from being marked as different from repository in CVS synchronization view, when one of these committed elements is simply opened and closed.
• Corrects a percentage formatting problem with premature rounding at the incorrect decimal place in generated reports.
• Corrects an issue with elements, such as ellipses, not printing in the header of generated reports.
• Corrects an issue with the missing display of process diagrams in generated and exported Process summary reports.
• Corrects failures in Modeler simulation and analysis when using Turkish currency.
• Corrects the timestamp on attachments for published elements.
• Includes National language support translation updates and fixes.
• Corrects inconsistent display of New context menu items in Report designer after the Fields view has been closed.
• Corrects the display and input of value representing midnight in time fields.
• Corrects a failure in the ability to add parameters to a report template that has been checked out using Team support.
• Adds "Decimal" to the list of formatters in the Field tab of the Attributes view for a report template
• Corrects an assignment issue when modifying Start time for a Timetable element.
• Corrects the default value in the Documentation's tab description field of an import Business service object
• Eliminates default parameter values in the Enter parameter values dialog when generating a predefined report.
• Corrects loss of associated data when importing a WSDL containing in-line types.
• Adds migration consideration for predefined report templates introduced in Version 6.
• Corrects the content generated using a Crystal report template.
• Corrects display of item names in Service details and Task details reports.
• Corrects a regression in generating Process level detail predefined report on processes containing a subprocess.
• Corrects missing content in printed output from the report generation preview dialog.

Product notes

Delay when testing connection to Crystal Reports server

When testing the connection to a Crystal Reports server from the Preferences page, it might take several minutes for the connection test to complete.

Delay when selecting fields for Crystal Reports report template

When creating a new Crystal Reports report template using Detailed Process Data Source as the data source, you might experience a significant delay when selecting fields to display in the report template. On the Select Fields page of the Report template wizard, if you select all available fields using the >> button, it will take several minutes for the Fields to Display list to populate.

To avoid this delay, consider individually selecting fields that you want to display using the > button instead of selecting all the available fields at once using the >> button.

Close Report Designer before deleting Crystal Reports report template

If you delete a Crystal Reports report template from the project tree while the report template is open in the Report Designer, the deletion will not complete. Even though the report template will not appear in the project tree, the associated files will not be deleted and you will not be able to create a new report template with the same name as the deleted report template.

To avoid this situation, close the Report Designer before deleting a Crystal Reports report template.

Increase maxEdgesAndPaths to prevent maximum path exception

If you are experiencing a maximum path exception when performing Input and output paths static analysis on a connector in a process diagram, increase the value of maxEdgesAndPaths in the plugin.properties file contained in eclipse\plugins\com.ibm.btools.bom.analysis.statical. For larger processes, a good starting value is 160000. Note that it might take longer perform analysis on these larger processes.

Disabling path cycle analysis can improve performance

If you are experiencing long wait times when saving or importing, it might be due to the number of path cycles in your models and the time required to validate these path cycles. To improve performance, you can disable cycle path analysis by modifying the value of isCycleDetectionEnabled to "false" in the plugin.properties files found in the eclipse\plugins\com.ibm.btools.mode.bpel and eclipse\plugins\com.ibm.btools.mode.fdl folders.

Note: The detection of path cycles may have caused a lenghty validation messages to be generated and persisted on models created prior to interim fix 3. If you have applied the fix and restarted, the tool only executes the message trimming the first time after restarting. So, if you did not set the value to "false" then the existing messages will remain, however, they will be trimmed to reflect the value of maxCyclesToReport in the plugin properties files. If you wish to have the tool perform this start up processing again, remove the lines containing isBpelCycleMessagesTrimmed and isFdlCycleMessagesTrimmed from workspace.properties in your workspace directory under .metadata\.plugins\com.ibm.btools.blm.migration.workspace. Also, be aware that once the validation messages are removed, the diagram would have to be modified in a way to trigger the re-validation of path cycles, if path cycle detection is re-enabled.

Auto-layout can maintain swimlane order

Modeler now allows you to maintain swimlane order during auto-layout. The behavior is enabled through the ordering dialog, available through the context menu of an open process diagram. Previously, the OK button would only be enabled if you changed the order; now it is enabled when the state of the auto-layout button changes.

Manual ordering of elements in the project tree view

You can now manually sort items within the Project Tree view, for example, to reflect frequency of use or relative importance of items within a catalog.

By default, items in the Project Tree view are sorted alphabetically within a container or catalog. When this default mode is enabled, the sort button in the Project Tree toolbar is pressed.

To enable manual sorting, click the sort button in the Project Tree toolbar to deselect it. The default order of items will change to chronological ordering, with most recently created items appearing last in a given container. To change the order of items within a container, select the item and drag it to the desired position within that container.

To move an item to a different container, for example to move a business item from one data catalog to another data catalog, first drop the item onto the catalog or logical node where you want it to be. The item will appear last in the new container. Then drag and drop the item to the desired position within the container.

There is a fixed order for item types within a catalog. For example, within the Process catalog, processes always come before tasks. Even if the logical nodes are not visible, you cannot change the order of these item types. For example, within the process catalog, even if you cannot see the separate containers for processes and tasks, you will not be able to reorder a task before a process.

The sorting mode and order of items is maintained when the product is restarted, and when catalogs are imported and exported. However, the ordering of items is not maintained when using project versioning. A catalog that is checked in and out again will revert to default alphabetical ordering.

Link-to-editor setting maintained on product restart

As an option in the Project Tree view, you can choose whether the navigation view selection is linked to the active editor. This means that when you are editing an item in an editor, that item is highlighted in the Project Tree. This is enabled by clicking the link-to-editor button in the Project Tree toolbar. Starting with this interim fix, the state of the link-to-editor button is maintained when you shut down and restart the product.