This hot fix can be downloaded from the SFDC Customer Portal Web UI, using your username and password for support.tibco.com.  Once logged on you can find the hotfix under Download Menu :
AvailableDownloads/BusinessWorks/Plugins/WebSphere_MQ/7.7.0/hotfix-01

Listed below is a summary of updates included. Please refer to the associated read me document for any additional information.

======================================================================
Closed Issues in 7.7.0_hotfix01

    BWMQ-655 - MQ Put activity performance issue.  In circumstances where there is high
            latency between the plugin platform and the MQ server the API calls to verify a pooled 
            connection, open a destination, put a message, close a destination and return the 
            connection to the pool can slow the execution of a put significantly.  To address that 
            a flag has been placed on all the applicable activities called "Pool Activity".  Use of 
            this feature will result in the a pool of connections being established at the activity level 
            where the destinations used by the activity are kept open.  By default the pool will contain
            a maximum of 30 connections.  The following parameters can be overridden via TRA 
            environment entries:
            GenericKeyedObjectPool.Config.maxTotal     : default 30
            GenericKeyedObjectPool.Config.maxWait     : default 30 seconds
            GenericKeyedObjectPool.Config.maxIdle     : default 10
            
            This feature cannot be used with activities which participate in an XA transaction.
            If the activity uses a connection which is defined to be pooled, the pooling config will be 
            ignored because it is being pooled at a higher level in the activity.
            Using this feature can have impacts on the number of server connections created.  It 
            is recommended to use flow limiting to control connection consumption where necessary.
       
    BWMQ-677  Subscription Name field is not always enabled when Durable subscription is
            selected.   
            
======================================================================