IBM WebSphere Business Modeler Advanced Version 6.1.1
Interim Fix 5 Readme
© Copyright International Business Machines Corporation 2008. All rights reserved.
This is an interim fix for IBM® WebSphere Business Modeler® Advanced Version 6.1.1.
This read-me file contains the following topics:
Installing the interim fix
To install the interim fix from a local repository
1. Download the 6.1.1-WB-ModelerAdv-MultiOS-IF0000005.zip file.
2. Extract the downloaded ZIP file into a temporary directory.
3. To open IBM Installation Manager, go to your Start > IBM Installation Manager > IBM Installation Manager.
IBM Installation Manager opens.
4. On the menu bar, go to File > Preferences.
5. In the left navigation panel, click Repositories.
6. In the Repositories panel, click Add Repository.
The Add Repository dialog box opens.
7. Click the Browse button.
8. Navigate to the directory where you have downloaded and unzipped the interim fix files.
9. Select repository.config.
10. Click Open.
11. Click OK.
The Add Repository dialog box closes.
12. In the Preferences window, click OK.
13. Follow the instructions below to apply the interim fix to your IBM WebSphere Business Modeler package.
To complete the installation of the IBM WebSphere Business Modeler interim fix
1. Go to Start > All Programs > IBM Installation Manager > IBM Installation Manager.
The IBM Installation Manager opens.
2. Click Update.
The Update Packages wizard starts.
3. Select the WebSphere Business Modeler package.
4. Click Next.
Installation Manager searches for updates in its repositories and the predefined update sites for WebSphere Business Modeler. If you do not have the files for the interim fix in a local repository, Installation Manager will download the required files.
5. On the Updates page, select Version 6.1.1.005.
6. Click Next.
The License page opens, displaying the list of licenses for the updates you selected.
7. Click each item to review the license agreement text.
8. If you agree to the terms of the license agreements, click I accept the terms of the license agreements.
9. Click Next.
The summary page opens.
10. Click Update.
Installation Manager installs the interim fix.
11. After the installation finishes, click Finish.
The Update Packages wizard closes. You have successfully installed the interim fix.
12. Close IBM Installation Manager.
Note: Before using WebSphere Business Modeler in a language other than English, you must first install the language you want to use. The interim fixes for WebSphere Business Modeler 6.1 include the national language support files that are required for installing additional languages.
If you are using WebSphere
Business
Modeler 6.1 without any interim fixes installed, you need to install an interim
fix before you can install additional languages. After installing the interim
fix, run the Modify Packages wizard
from the IBM Installation Manager
start page and select the languages to install.
If you are already using WebSphere Business Modeler 6.1.1, you can run the Modify Packages wizard to install
additional languages either before or after applying any fixes.
Fixes included in this interim fix
This is a cumulative interim fix for IBM WebSphere Business Modeler Advanced Version 6.1.1.
Fixes included in the interim fix 5
The table below describes fixes contained in this interim
fix, including the PMR number and APAR identifier for each fix.
|
PMR Number |
Related APAR Identifier |
Description |
|
52308,6X8,760 |
JR30584 |
Corrects version and edition labels. |
Fixes included in the interim fix 4
The table below describes fixes contained in this interim
fix, including the PMR number and APAR identifier for each fix.
|
PMR Number |
Related APAR Identifier |
Description |
|
|
JR29545 |
Enabled publishing from Modeler 6.1.1 to the publishing server 6.1.2. |
Fixes included in the interim fix 3
The table below describes fixes contained in this interim
fix, including the PMR number and APAR identifier for each fix.
|
PMR Number |
Related APAR Identifier |
Description |
|
|
JR28567 |
Made default values defined in a Business item parent of a Business item instance available during simulation. |
|
51012,6X8,760 |
JR28681 |
Allowed versioning to detect an incoming add, as well as an outgoing delete, for elements that have renamed and then deleted from the Project tree. |
|
38826,756,000 |
JR29056 |
Produced consistent content for Reports that are generated and exported to DOCX or PDF format. |
|
51351,6X8,760 |
JR29077 |
Corrected the display of elements listed in the Remove associations dialog, which is accessible through the Process editor context menu, when in swimlane layout. |
|
|
JR29236 |
Fixed collision handling of Business item states during XML import. |
|
|
JR29270 |
Fixed failure to import WSDL which leads to incorrect generation of BPEL Reference partners. |
|
|
JR29495 |
Corrected handling of ID and name collisions if user chooses to overwrite existing on import. |
Fixes included in the interim fix 2
The table below describes fixes contained in this interim
fix, including the PMR number and APAR identifier for each fix.
|
PMR Number |
Related APAR Identifier |
Description |
|
80096,442,000 57392,033,000 |
JR28422, JR28641 |
Resolved a problem with auto-layout which adds extraneous white space between elements. |
|
83875,442,000 |
JR28582 |
Resolved a problem
where data cannot be associated with the output
branch of a decision when the other branch is a split connection. |
|
50957,6X8,760 |
JR28570 |
Corrected a problem that occurs in basic modeling mode where a process cannot be saved after updating a connection. |
|
83356,442,000 |
JR28579 |
Corrected a problem with table truncation when exporting to Microsoft Word (.docx) format. |
|
77162,033,000 |
JR28674 |
Allowed users to modify the order of inputs and outputs for business rule and human tasks from the context menu. |
|
00917,090,838 |
JR28677 |
Corrected a problem that arises when performing an export to WebSphere Integration Developer on a model that contains imported business services. |
|
50967,6X8,760 |
JR28707 |
Corrected a problem with the display of connections between diagram elements. |
|
32835,650,758 |
JR28710 |
Resolved a product failure that occurred after associating a task with a global repository that has previously been associated with a local repository. |
|
67857,033,000 |
JR28775 |
Corrected a problem with importing a WebSphere Business Modeler project in which a human task escalation has been deleted. |
|
28748,550,000 |
JR28855 |
Allowed the publishing of processes that have the proportional resizing attribute selected in the diagram printing setup preferences. |
This interim fix includes the following fixes, all of which are associated with APAR JR29000:
- Corrects errors in .xsd files that are introduced when the associated business service objects are exported from WebSphere Business Modeler.
- Ensures that a unique XPDL activity is generated for each reference to a global element to avoid errors when importing the process to FileNet P8.
- Allows the importing of projects containing processes with simulations.
Fixes included in the interim fix 1
The table below describes fixes contained in this interim
fix, including the PMR number and APAR identifier for each fix.
|
PMR Number |
Related APAR Identifier |
Description |
|
80624,442,000 |
JR28466 |
Fixed an issue that had occurred when switching to swimlane view and applying auto-layout. |
|
69305,033,000 |
JR28418 |
Corrected a problem with checking out a project or element from a Rational ClearCase repository. |
|
46396,019,866 |
JR28358 |
Enabled versioning of queries in CVS and Rational ClearCase repositories. |
|
78858,999,706 |
JR28392 |
Introduced an informative error message returned when a versioning repository server error had occurred due to access control restrictions. |
|
80096,442,000 |
JR28422 |
Removed extraneous white space displayed after applying auto-layout in a swimlane layout. |
|
50965,6X8,760 |
JR28501 |
Corrected text display issues in diagrams exported from WebSphere Business Modeler 6.0.2.1. |
|
50660,6X8,760 |
JR28563 |
Ensured that label display preferences settings persist after other default preferences are modified. |
This interim fix also includes the following fixes associated with APAR JR28638:
- Fixed problems with displaying a published process diagram in swimlane layout by classifier if a classifier has been deleted. Swimlanes for which the classifier is unavailable are not displayed in the process diagram.
- Corrected a problem where the Synchronization view shows all elements in a project as having outgoing uncommitted changes after a catalog is renamed.
- Corrected a problem where a new element was not visible in the Synchronize view after another element in the same catalog has been renamed but not committed.
- Corrected a problem where selecting a renamed element in the Synchronize view and committing it would commit all outgoing changes within the same catalog that are currently visible in the Synchronize view.
- Enabled cutting and pasting an annotation object from within a process diagram.
- Implemented a new user message returned when you attempt to commit, share, or update elements to a repository for which you do not have write access.
- Corrected a synchronization error condition that had occurred when a shared catalog has been renamed in the repository by one user, and another user with a local catalog with the same name performs an Overwrite and Update From Repository action.
- Fixed a mismatch between the classifier icon displayed in the Synchronize view and the icon displayed in the Project Tree view.
- Added an option to the FileNet export to transform basic type single-property business items into data fields.
- Ensured that changing the icon of a business item shared between projects updates the icon dynamically in the Process editor.
- Allowed working in a swimlane layout based on a deleted element without causing an error.
- Allowed exporting certain business items as data fields.
Product notes
These product notes include the following topics:
- Exporting certain business items as data fields
- Changes to modeling in FileNet Business Process Manager mode
- Re-importing business services imported from WSDL after applying interim fix 2
Exporting certain business items as data fields
By default, the FileNet Business Process Manager export now exports business items that
have a single basic-type attribute as data fields. The export continues to
export business items that have
- More than one attribute, or
- Complex-type (business items) attributes as XML data
fields.
You can disable this option by removing the
checkmark from the Transform business items with single basic attributes
into data fields checkbox on the export options
page. If you disable this option, the export exports all business items,
including business items with single basic-type attributes, as XML data fields.
For example, let’s say that there is a process
that contains a Customer business item that has one attribute called Id and the attribute is an Integer. If you export
the process with the option enabled and then open the resulting XPDL in FileNet Process Designer, there will be a Customer data field. If you export the process with the option disabled,
there will be a Customer XML data field instead.
With the option enabled, the export removes the
attribute and sets the data field to the type of the business item attribute.
In the XPDL, the data field looks like this:
<DataField Id="Customer" IsArray="FALSE"
Name="Customer">
<DataType>
<BasicType
Type="INTEGER"/>
</DataType>
</DataField>
With the option disabled, the export creates a definition that
refers to the XML schema. In the XPDL, the XML data field looks like this:
<DataField Id="Customer" IsArray="FALSE"
Name="Customer">
<DataType>
<DeclaredType
Id="xml"/>
</DataType>
<fn:Field ElementName="Customer"
SchemaName="Schema_name"/>
</DataField>
Note that enabling or disabling this option does not affect Businessitems.xsd. The schema
contains the same definition for the data field. The difference is that with
the option enabled, the XPDL does not reference the schema.
Changes to modeling in FileNet Business Process Manager mode
Previously, in the FileNet Business
Process Manager mode, you modeled data flow separately from the control
flow. In other words, to pass data from one task to another, you had to
1. Link the first
task to a repository to output the data, and then
2. Link the
repository to the second task to input data.
After applying the interim fix 1, you can attach business items
that have a single basic-type attribute to a control flow. You no longer need
to pass the business item from a task to a repository to another task.
If the business
item has more than one attribute or an attribute that is of a complex type
(another business item), you must continue to use a repository to pass it from
one task to another.
Re-importing business services imported from WSDL after applying interim fix 2
This interim fix resolved a problem that had occurred when performing the IBM WebSphere Integration Developer export on a model containing business services imported from WSDL.
If you are encountering this problem before applying this interim fix
1. Apply the interim fix.
2. Re-import the business service into IBM WebSphere Business Modeler.
3. Reference the newly imported business service in a process model.
Subsequent export of the model to WebSphere Integration Developer will succeed without error.