IBM WebSphere Business Modeler Interim Fix Readme Template

===================================================================================
IBM WebSphere Business Modeler Advanced Version 6.1.1
Interim Fix 3 Readme
===================================================================================

This is an interim fix for IBM^® WebSphere Business Modeler^® Advanced Version 6.1.1.

Installing the interim fix
Fixes included in this interim fix
Product notes

Installing the interim fix

There are two ways to install WebSphere Business Modeler interim fixes. Using one method, you download the required files to a local repository, and then use the IBM Installation Manager Update Packages wizard to install the files from the repository. Using the other method, you use the IBM Installation Manager Update Packages wizard to automatically download and install the required files from an IBM download site.

To install the interim fix from a local repository, complete the following steps:

1. Download the 6.1.1-WB-ModelerAdv-MultiOS-IF0000003.zip file.

2. Double-click the downloaded 6.1.1-WB-ModelerAdv-MultiOS-IF0000003.zip file, and extract the files into a temporary directory.

3. Open Installation Manager from your Start menu by selecting IBM Installation Manager > IBM Installation Manager.

4. From the Installation Manager start page, go to File > Preferences.

5. Click Repositories.

6. Click Add Repository… on the Repositories page.

7. Using the browse button, locate the directory where you have downloaded and unzipped the files for the interim fix.

8. Select repository.config, and click Open.

9. Click OK to close the Add Repository window.

10. Follow the instructions below to apply the interim fix to your WebSphere Business Modeler package.

To update your WebSphere Business Modeler package with the new interim fix, complete the following steps:

1. Open Installation Manager from your Start menu by selecting IBM Installation Manager > IBM Installation Manager.

2. From the Installation Manager start page, click Update Packages to start the Update Packages wizard.

3. Select the WebSphere Business Modeler package and 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.

4. On the Updates page, select the “Version 6.1.1.003” update and click Next.

5. On the License page, the list of licenses for the updates you selected is displayed; click each item to display the license agreement text.

6. If you agree to the terms of the license agreements, click I accept the terms of the license agreements.

7. Click Next to continue.

8. On the Summary page, click Update to install the update. The interim fix is now installed.

9. Click Finish to close the Update Packages wizard.

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 will need to install an interim fix before you can install additional languages. After installing the 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 WebSphere Business Modeler Advanced Version 6.1.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
	JR28567	Makes the default values defined in a business item parent of a business item instance available during simulation.
51012,6X8,760	JR28681	Allows project versioning to detect incoming adds and outgoing deletes for elements that have been renamed and then deleted from the Project Tree.
38826,756,000	JR29056	Produces consistent content for reports that are generated and exported to DOCX or PDF format.
51351,6X8,760	JR29077	Corrects the display of elements listed in the Remove Associations window, which is accessible from the Process editor context menu when working in swimlane layout.
	JR29236	Fixes collision handling of business item states during XML import.
	JR29270	Fixes a failure in the WSDL import which leads to incorrect generation of BPEL reference partners.
	JR29495	Corrects the handling of identifier and name collisions if the user chooses to overwrite existing elements on import.

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
80096,442,000 57392,033,000	JR28422, JR28641	Resolves a problem with auto-layout which adds extraneous white space between elements.
83875,442,000	JR28582	Resolves a problem where data can not be associated with the output branch of a decision when the other branch is a split connection.
50957,6X8,760	JR28570	Corrects a problem that occurs in basic modeling mode where a process cannot be saved after updating a connection.
83356,442,000	JR28579	Corrects a problem with table truncation when exporting to Microsoft Word (.docx) format.
77162,033,000	JR28674	Allows users to modify the order of inputs and outputs for business rule and human tasks from the context menu.
00917,090,838	JR28677	Corrects a problem that arises when performing an export to WebSphere Integration Developer on a model that contains imported business services.
50967,6X8,760	JR28707	Corrects a problem with the display of connections between diagram elements.
32835,650,758	JR28710	Resolves a product failure that occurs after associating a task with a global repository that has previously been associated with a local repository.
67857,033,000	JR28775	Corrects a problem with importing a WebSphere Business Modeler project in which a human task escalation has been deleted.
28748,550,000	JR28855	Allows 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 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
80624,442,000	JR28466	Fixes an issue that arises when switching to swimlane view and applying autolayout.
69305,033,000	JR28418	Corrects a problem with checking out a project or element from a Rational ClearCase repository.
46396,019,866	JR28358	Enables versioning of queries in CVS and Rational ClearCase repositories.
78858,999,706	JR28392	Introduces an informative error message that is returned when a versioning repository server error has occurred due to access control restrictions.
80096,442,000	JR28422	Removes extraneous white space that is displayed after applying auto-layout in swimlane layout.
50965,6X8,760	JR28501	Corrects text display issues that arise in diagrams that are exported from WebSphere Business Modeler 6.0.2.1.
50660,6X8,760	JR28563	Ensures that label display preferences settings persist after other default preferences are modified.

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

Fixes 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.
Corrects a problem where the Synchronization view shows all elements in a project as having outgoing uncommitted changes after a catalog is renamed.

Corrects a problem where a new element is not visible in the Synchronize view after another element in the same catalog has been renamed but not committed.
Corrects a problem where selecting a renamed element in the Synchronize view and committing it will commit all outgoing changes within the same catalog that are currently visible in the Synchronize view.
Enables you to cut and paste an annotation object from within a process diagram.
Implements a new user message that is returned when you attempt to commit, share, or update elements to a repository for which you do not have write access.
Corrects a synchronization error condition arising 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.
Fixes a mismatch between the classifier icon that is displayed in the Synchronize view and the icon that is displayed in the Project Tree view.
Adds an option to the FileNet export to transform basic type single-property business items into data fields.
Ensures that changing the icon of a business item shared between projects updates the icon dynamically in the Process editor.
Allows you work in a swimlane layout that is based on a deleted element without causing an error.
Allows you to export certain business items as data fields.

Product notes

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 have complex-type (business items) attributes as XML data fields.

You can disable this option by removing the check mark from the Transform business items with single basic attributes into data fields check box in 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, say 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 is a Customer data field. If you export the process with the option disabled, there is 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:

</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:

</DataType>

<fn:Field ElementName="Customer" SchemaName="Schema_name"/>

</DataField>

Note that the Businessitems.xsd is not affected by the whether the option is enabled or disabled. 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 FileNet Business Process Manager mode, you modeled data flow separately from the control flow. That is, to pass data from one task to another, you linked the first task to a repository to output the data and then linked the repository to the second task to input data.

However, when you apply Interim Fix 1, you can now 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 it has 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.

Business services imported into WebSphere Business Modeler from wsdl should be reimported after applying interim fix 2.

This interim fix resolves a problem that arises when performing a WebSphere Integration Developer export on a model containing business services that have been imported from wsdl.

If you encounter this problem before applying this fix, you will need to apply the fix, then re-import the business service into WebSphere Business Modeler, and reference the newly imported business service in a process model. Subsequent export of the model to WebSphere Integration Developer will succeed without error.