Products | Versions |
---|---|
TIBCO Collaborative Information Manager | - |
Not Applicable | - |
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-08/ 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 8 are:
1-91YBG3
Adding a record with a cross-catalog relationship through a JMS message failed with a NullPointerException in the SaveRecord Activity. This has
been fixed.
1-91YBIJ
Rulebase constraints did not work correctly when the WORKITEM context variable was used. This has been fixed.
1-8IAT08
Pagination did not work in Subset by search when filtered records had a blank PRODUCTIDEXT. This has been fixed.
1-9297LJ
The record attributes were not accessible in rulebase constraint through the relationship_record link. This has been fixed.
1-92ALXE
Rulebase operators, such as lt and eq, did not work when used with an attribute of type CUSTOM DECIMAL. This has been fixed.
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-93B1F7
When WebSphere MQ is used as the JMS provider,SYSTEM.JMS.ND.SUBSCRIBER.QUEUE was getting filled up in the CIM Queue Manager
Now, the MQSeries Subscription store can be connected to MQ Event Broker. To do this, specify the following property in $MQ_HOME/config/queue.prop:
martquest.queue.cluster.MQSeriesCluster.clusterLiaison.clusteredQMgr.
LocalhostQMgr.connFactory.mqSubStore
The value for this property will be 0(QUEUE) or 1(BROKER) or 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