Description:
============
Introduction
============


Hotfixes are cumulative. This hotfix contains all previous hotfixes for

TIBCO ActiveMatrix BusinessWorks(TM) Plug-in for WebSphere MQ 7.4.0.



================================================================================

Affected Files for 7.4.0_hotfix03

The following files are installed by this hotfix. Note that some

files are
platform-specific and are installed only on that platform.

All Platforms:

{TIBCO_HOME}\release_notes directory:
   - TIB_bwpluginmq_7.4.0_HF-003_readme.txt

{TIBCO_HOME}/bw/plugins/lib/palettes directory:
   - bwmqPlugin.jar




======================================================================
Closed Issues in 7.4.0_hotfix03

BWMQ-259    Field "responsetimemillisec" in the Output Tab of "WMQ Get" Palette is invalid.  Note that
    this change was in the hotfix 02 deliverable, but the update to the readme was missed so it is
    included here for completeness.

BWMQ-300   Listener does not close connections correctly in response to being activated and deactivated.
    When under heavy load the engine will repeatedly start and stop the listener.  If the listener is
    interrupted in the middle of a get it may not correctly return its connection to the pool.

BWMQ-301    Customers require a way to commit coordinate multiple queue operations outside of XA.
    A flag called "Commit Via Syncpoint Activity" has been added to the multi-message tab of the get and
    put activities.  It is mutually exclusive with the "Explicit Syncpoint" flag and will disable that
    option when checked.  A new activity called the "Syncpoint Activity" has been added to the palette
    to permit all the resources which currently exist in an MQ unit of work to be committed or
    backed out.


BWMQ-308    WMQ plugin: new activity 'WebSphere MQ SyncPoint Activity' and new feature
    'Commit Via Syncpoint Activity' in MultiMessage Tab in Put / Get activities.  This flag allows the
    WebSphere MQ unit of work to be committed or rolled back in a separate activity called "WMQ Commit".

    Some important notes regarding the use of this flag:

    -do not mix the commit activity with XA transactions.  The commit activity is intended to assist
    with unit of work management without the use of an XA transaction.

    -if a process is managing a unit of work via the commit activity across several activities, but
    some other activities are not participating in the unit of work, then use a different connection
    for the non-participants.

    -all activities involved in a unit of work must use the same connection resource.

    -activities for which the "Commit Via SyncPoint Activity" is on which do not encounter a
    sync-point activity will be rolled back at the end of the process.
    
 




================================================================================


====================
Obtaining the Hotfix
====================


To download hotfix 03, go to ftp://mft.tibco.com.

You may access the site using your FTP/SFTP client of choice, command-line FTP, or HTTPS (at https://mft.tibco.com).

You will be prompted for your userid and password, the same as required to open a Service Request.

                  Select Available_Downloads
                  Select BusinessWorks
                  Select Plugins
                  Select WebSphere_MQ
                  Select 7.4.0
                  Select hotfix-03

You should then be able to see and download the files.

                  TIB_bwpluginmq_7.4.0.md5
                  TIB_bwpluginmq_7.4.0_HF-003.zip
                  TIB_bwpluginmq_7.4.0_HF-003_readme.txt        

Specific instructions for applying this hotfix are contained in the readme file.