The manageprofiles command now uses the same parameters as the WebSphere Process Server.
Fabric is now included in the IBM WebSphere Dynamic Process Edition core offering.
Business user experience and tooling enhancements:

The user interface for governing system changes and Inbox functions have moved from the Fabric administration console to the Business Space. The Business Space allows business user to manage business services, business service policies and business vocabulary.
Governance functions have been integrated with the WebSphere Process Server.

Consumability and ease of use improvements and support:

Product installation has been simplified to support network deployments.
Business services can now be reused across multiple composite business applications.
Message context extractor is now configurable.

Platform and system support has been expanded to include:

RHEL on Series p and z/OS 1.10
Oracle 11g

Language support now includes:

Czech, Hungarian, and Polish
Support for bi-directional text

Support for industry content packs has been expanded to include:

The new Product Lifecycle Management Content Pack
Enhancements to the existing Telecom Operations Content Pack
Enhanced business service templates, schemas and additional service interfaces in Billing, Inventory, Fulfillment and Assurance

2.0 Documentation

Visit the IBM WebSphere Business Process Management Version 6.2 information at http://publib.boulder.ibm.com/infocenter/dmndhelp/v6r2mx/index.jsp, for the most current Fabric documentation.

3.0 Contents of this release

The Fabric Tool Pack includes the following applications and components.

WebSphere Integration Developer (WID). WID is used to assemble and integrate composite services.
Business Services Composition Studio (a plug-in to WID). Composition Studio is used to assemble business services, create business policies, and simulate dynamic assembly of business services. Composition Studio is packaged as an Eclipse plug-in that adds an additional perspective to WID called Business Services.
Unit Test Environment (UTE). The UTE allows you to build and execute business services on your desktop. The Unit Test Environment contains all Foundation Pack components.

4.0 Prerequisites for installation

Refer to the IBM Business Services Tool Pack Installation Guide 6.2 for details.

5.0 Installing this product

Refer to the IBM Business Services Tool Pack Installation Guide 6.2 for details.

Important:

You must update WID before updating the Tool Pack. If you update the Tool Pack first, the WID update will fail.

To update WID, follow the instructions provided in the WID documentation. During a WID update, you might receive warning messages that state the Fabric is not at the correct level. After updating WID, update the Tool Pack. Be sure to exit WID before installing the Tool Pack.

Note:

Composition Studio plugins and features will be rolled back to the previous version but profile (Ears) will not be rolled backed.

6.0 Known limitations, problems, and workarounds

6.1 If you cannot log into Web Tools after an install and everything worked

This happens because the logon functionality generates a SQL that contains a DB2 defined "UPPER" function. This "UPPER" function does not work if the system date is set to a date earlier than when the database was installed. If the date is reset to the current date, everything should work fine.

6.2 To see Business Variables in Business Space

To see Business Variables in Business Space, you must map users or groups to roles in the Fabric_Catalog application by following these steps:

1. Expand Applications on the left panel of the WPS console.

2. Click the Enterprise Applications link.

3. Click the Fabric_Catalog application link.

4. In the Detail Properties section, click Security role to user/group mapping.

5. Assign the same groups/users to the Fabric Administrators role (ONLY in the Fabric_Catalog application, NOT in the Fabric_Tools application) that you assigned to the Administrator role in the Business Space Manager application.

6.3 Composition Studio projects should not be exported using Project Interchange, or otherwise moved between workspaces

Project Interchange exports do not include the database that belongs to the project and do not package the replicated database that is associated with a workspace. Attempting to import a Composition Studio project from a Project Interchange will cause Composition Studio plug-ins to start incorrectly.

If Composition Studio encounters errors or failures due to a missing database, Composition Studio will not be usable until the missing resources are supplied or until the broken project is removed from the workspace.

Instead of moving Fabric Projects between workspaces, create a new Fabric Project in a new workspace.

6.4 Test connection fails when using secure port (https)

(Internal tracking code WFC-3021)

To use a https connection to connect to a Fabric Repository, you need to import the WPS certificate into your WID truststore, using the following steps.

1. In IE6, browse to the Fabric login page, using https
2. Accept the certificate (select Yes on the popup).
3. Double click the lock icon at the bottom right of the browser.
4. Click on the Details tab then click Copy to File...
5. Select Base-64 encoded X.509 (.CER), then choose file and click Finish
6. cd to your WID jre security dir ({WID_ROOT}/jdk/jre/lib/security/)
7. Backup the cacerts file
8. Open a shell in the directory WID_ROOT}/jdk/jre/bin
9. Run the command:
keytool -import -alias fabric-catalog -file <PATH_TO_FILE_IN_STEP_5> -keystore cacerts

You need to know the cacerts password (the default is changeit).

6.5 Engine doesn't authenticate to fire CBEs

(Internal tracking code WFC-2363)

If you want security on your CBE bus, then all of your other applications (not Fabric) that access it have to authenticate. Therefore, you have two options: enable "everyone" to fire events (not a desirable option on a production system), or make your applications authenticate to the server.

For instructions on how to implement authentication go to http://publib.boulder.ibm.com/infocenter/dmndhelp/v6r2mx/index.jsp

6.6 When using Informix v10.10

(Internal tracking code WFC-3128)

Note the following while using Informix v10.10.

1) Use "DBAcess" utility to create the database. Before invoking this utility, ensure that the variables DB_LOCALE, CLIENT_LOCALE and SERVER_LOCALE are set to "en_us.utf8". If these are not set, it might lead to exceptions.

java.io.IOException: Code-set conversion function failed due to illegal sequence or invalid value.

Also, ensure that the connect string (or database url) has the DB_LOCALE connection property explicitly set. For example,

jdbc:informix-sqli://9.121.181.23:1526/fabricdb:INFORMIXSERVER=myinformix;DB_LOCALE=en_us.utf8

2) Database should be created in logging mode
sql> CREATE DATABASE dbname WITH LOG
You can also use buffered log. If database is non-logging, such exceptions will be encountered at runtime

java.sql.SQLException: "Transactions not supported"

6.7 Database limitations for large artifacts

(Internal tracking code WFC-3266)

The maximum supported artifact size is 1 Gb. See methods setContent(InputStream stream, boolean closeInput, long size) in package com.ibm.tyto.artifact.Artifact.

6.8 Reduce the risks of running into a Derby lock timeout.

(Internal tracking codes WFC-4648)

This workaround reduces the risks of running into a Derby lock timeout by reducing the isolation level used in WebSphere, on the database where the lock may occur (most probably BPEDB).

The workaround reduces the isolation level from:
4 "TRANSACTION_REPEATABLE_READ" (in DB2 terminology "Read Stability" = RS)
to
2 "TRANSACTION_READ_COMMITTED" (in DB2 terminology "Cursor Stability" = CS)

To apply this workaround you need to add a custom property for the appropriate data source. Make the setting on the admin console, after installing the driver and before running the tests, by using the following steps:

On the admin console, navigate to:
Resources > JDBC > Data sources > BPEDataSourceDerby > Custom properties > new
For name, enter (case exactly as shown): webSphereDefaultIsolationLevel
For Value, enter: 2
Save the changes. The new isolation level will be effective after restarting the server.

Note: To undo this setting, delete this custom property and restart the server again.

6.9 Web Service exceptions are not handled correctly in SCA

(Internal tracking code WFC-4120)

Fabric SDK service exceptions are not always handled correctly by the SCA portion of WPS. Install WPS iFix PK75548 to correct this exception handling error.

7.0 Technical support

Contacting IBM Software Support

If you encounter a problem with this product, first try the following actions:

Follow the steps described in the product documentation
Look for related documentation in the online help
Look up error messages in the message reference

If you cannot resolve your problem by any of the preceding methods, contact IBM Technical Support.

Purchase of IBM WebSphere Application Server entitles you to one year of telephone support under the Passport Advantage^® program. For details about Passport Advantage, visit the Passport Advantage^® page.

The number for Passport Advantage members to call for WebSphere Application Server support is 1-800-426-7378. Have the following information available when you call:

Your contract or Passport Advantage number.
Your WebSphere Application Server version and revision level, plus any installed fixes.
Your operating system name and version.
Your database type and version.
Basic topology data: how many machines are running, how many application servers, and so on.
Any error or warning messages that are related to your problem.