IBM WebSphere Business Services Fabric - Fixpack 6.1.0.1 Release Notes

 

Purpose of this release. 1

Prerequisites for installation. 1

Installing this fix pack. 1

Documentation. 1

Technical Support 1

Contacting IBM Software Support 1

Purpose of this release

This release updates the version of Derby that Fabric requires.

Prerequisites for installation

IBM WebSphere Business Services Fabric 6.1.

Installing this fix pack

The following steps protect you from the remote possibility that the database created by the previous version is not compatible with the newer version that is being installed.

To install this fix pack:

1.      Publish all your changelist to BSR.

2.      Install the fixo

3.      Create a new workspace

4.      Replicate your Fabric project.

Note: Fixo installs the derby jars into the WID_HOME/runtime/bi_v6/derby folder and creates a backup of the original jars to a directory called derby.orig.

Documentation

Visit the IBM WebSphere Services Fabric Information Center at

http://publib.boulder.ibm.com/infocenter/dmndhelp/v6r1mx/index.jsp, for available documentation.

Technical Support

Contacting IBM Software Support

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

  • Following the steps described in the product documentation
  • Looking for related documentation in the online help
  • Looking 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.