Description:
The hotfix can be downloaded from the TIBCO Support ftp server, support-ftp.tibco.com. Please use your eSupport username and password to access the server. After connecting, go to /available_downloads/CollaborativeInformationManager/7.0.0/hotfix-09/  to download the hotfix.
This .tar file also has the Readme file inside. Please untar the file and look for the Readme file for Instruction on how to apply the hotfix.

The defects fixed in CIM 7.0.0 Hotfix 9 are:

1-93B1F7
When WebSphere MQ was used as the JMS provider, during inbound message processing, the SYSTEM.JMS.ND.SUBSCRIBER.QUEUE queue got filled up by the CIM queue manager. After this, messages were sent to the SYSTEM.DEAD.LETTER.QUEUE queue. When this happened, the only solution was to bring down the CIM servers, stop the MQ Publish\Subscribe broker, and then clear the SYSTEM.JMS.ND.SUBSCRIBER.QUEUE queue. This happened because of incorrect active subscriber information which caused message flooding.

To fix this, you can now set the MQSeries Subscription store for CIM topics by setting the following property in the $MQ_HOME/config/bus.prop
file. The MQSeries Subscription store for CIM specifies where WebSphere MQ stores data relating to active JMS subscriptions.

martquest.queue.cluster.MQSeriesCluster.clusterLiaison.clusteredQMgr.LocalhostQMgr.connFactory.mqSubStore

Valid values for this property are 0(QUEUE), 1(BROKER), or 2(MIGRATE). The default is 2(MIGRATE).

IBM recommends that you minimize the risk of this issue. For more information, refer to the following sites:
1) http://publib.boulder.ibm.com/infocenter/wasinfo/v5r1//index.jsp?
topic=/com.ibm.websphere.base.doc/info/aes/ae/umj_ptcfmcp.html
2) http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1//index.jsp?
topic=/com.ibm.websphere.base.doc/info/aes/ae/umj_ptcfmcp.html

1-96NEXB
For a cross-catalog relationship, when the same productid was imported twice in same batch, the relationship was lost.

1-92OCSE
During incoming message processing, if the file system (the one on which MQ_COMMON_DIR was located) failed, messages were lost and these
messages could not be recovered using the Message Recovery utility. This has been fixed by introducing a new property,
com.tibco.queue.locationToSaveFailureMessages. See the Installation section (step 10) for details on configuring the property.

1-95YZ49  
After running Purge workflow and tibcocrontab.sh it was not clearing enough space from commondir file system. This has been fixed.