TIBCO Collaborative Information Manager 8.0.1 Hotfix 01 is now available
Article ID: KB0105035
Updated On:
| Products | Versions |
|---|---|
| TIBCO Collaborative Information Manager | - |
| Not Applicable | - |
Description
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/8.0.1/hotfix-01/ 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 8.0.1 Hotfix 01 are:
GDSN-154
The migration Wizard from the Configurator did not show the GDSN option selected by default.
GDSN-158
Migration failed with errors related to the database migration and dependent file migration.
GDSN-159
GDSN directories (plugins and props) did not get copied to the MQ_HOME\lib directory.
GDSN-72
Configurator Add-on plugin Installer failed to merge FileWatcher.xml.
CIM-8590
Dropdowns did not appear correctly in the Basic Mode of the Mass Update screen.
CIM-8593
Mass update failed on an external Tangosol server with a Class Not Found exception.
CIM-8594
If the repository contained a drop-down constraint with spaces in the drop-down items, Mass update reported that the record was modified even though it was not.
GDSN-148
A JavaScript error was displayed while adding a related record through search.
CIM-8575
The ONLINE text indexing mode did not allow indexing of specific repositories only. Instead, it synchronized all the repositories. Single records of an unwanted repository were indexed leading to an unpredictable server index state and subsequent search results.
To fix this, add the following property to the “Repository” category of the ConfigValues.xml file:
<ConfValue description="Repository Indexing List" isHotDeployable="true" name="Repository Indexing List" propname="com.tibco.cim.search.RepositoryOnlineList" sinceVersion="8.0.1" visibility="Advanced">
<ConfList>
<ConfListString value="PERSON"/>
<ConfListString value="COUNTERPARTY"/>
</ConfList>
</ConfValue>
CIM-8574
The Data Quality Netrics setup was not fault tolerant. To fix this,add the following property to the “Repository” category of the
ConfigValues.xml file:
<ConfValue listDefault="" name="Netrics Server Connection List" description="The List of Netrics Servers for a fault tolerant and/or load balanced setup” propname="netrics.servers.connection" sinceVersion="8.0.1" visibility="Advanced">
<ConfList>
<ConfListString value="server_hostname_1:5051"/>
<ConfListString value="server_hostname_2:5052"/>
</ConfList>
</ConfValue>
Note: If any Netrics Server is restarted in the fault tolerant setup,
run the textIndexMigration utility.
CIM-8587
On synchronizing a record with a transformation rulebase selected, the following error was displayed at EvaluateRulebase stage:
"Wrong value specifed for Relationship name ='Contains':
AppplyRulebase failed:Wrong value specifed for Relationship name
='Contains': (Undefined) RUL-4608: (Undefined)
<br>RUL-4608: (Undefined)"
GDSN-171
On the SA2 Retailer side, when the Withdraw checkbox was selected and already published products were synchronized, the Submit or Cancel button was not displayed on the workitem page.
CIM-8598
The cache-server.sh file started the JVM with a Max Memory of 4GB irrespective of the memory passed by the user.
CIM-8602
All cache server instances used a common store.
Note: The cache-server.sh and cache-server.cmd accept another argument - cache store directory. Usage details of the cache server start up script are as follows:
cache-server.sh <max memory in MB> <cache store directory path>
For example:
cache-server.sh 1024 /home/cimuser/cachestore/instance1
Directory specified as cache store must already exist. Pass a separate directory path for each cache server instance. Both <max memory in MB> and <cache store directory path> are mandatory.
CIM-8601
Migration from 6.1.3 to 7.x to 8.0.1 resulted in the System Operations and Query Tool menu options not being displayed for the tadmin user.
GDSN-176
CIM Add-On Plugin Installer (through configurator) did not update the plugins and prop folders and some files from $MQ_HOME/config.
GDSN-160
The following error was displayed during association:
CAT-1017:Invalid attribute definition for attribute PROD_COLOR_DESC.
GDSN-182
Button alignment was not correct in the Record Notification workitem page on the retailer side.
GDSN-184
"Null" was populated in the "Reason for change" column of the Record Notification workitem page.
GDSN-155
CIM2CIM: Synchronization events do not have the event ID in the Event Details page.
GDSN-188
On clicking the "View Unclassified Records" link from Synchronization Approval > Browse page, a database error was displayed.
CIM-8609
With cross catalog relationships,the match-merge workflow failed at the GetRecord activity when the was set to true in the MergeRecord activity.
GDSN-185
On 1Sync, when the quantity field was modified for a child record, the following exception was thrown:
JAV-8001: Unexpected error. Class: 'com.tibco.mdm.ui.repository.record. QuickViewServlet' and method name: 'service'. Additional information: java.lang.ClassCastExc
CIM-8615
When records are imported using relationshipAttributes with cacheServer as ActiveSpaces it used to fail in Extractrelationship occasionally.
CIM-8607
When records with a relationship were imported without mapping relationship attributes, and a record query web service was called to return relationship data of an imported record, relationshipAttributes were not a part of the response file.
CIM-8586
When adding a record with relationship with exsisting record using web service. The related record status becomes Unconfirmed.
GDSN-56
For an Enterprise of type "datapool", an error is displayed when a company profile is created and the supported catalog format is selected.
CIM-8618
On creating a record, the Oracle sequence was incremented by 2 due to Relationship Validation.
CIM-8620
Repository import did not create relationship as expected when multiple data sources with a primary data source and common key were used.
CIM-8622
Printing tangosol size in debug mode causes tangosol performance to degrade. size is printed only in debug mode but when users try to debug an issue, they encounter this problem.
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/8.0.1/hotfix-01/ 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 8.0.1 Hotfix 01 are:
GDSN-154
The migration Wizard from the Configurator did not show the GDSN option selected by default.
GDSN-158
Migration failed with errors related to the database migration and dependent file migration.
GDSN-159
GDSN directories (plugins and props) did not get copied to the MQ_HOME\lib directory.
GDSN-72
Configurator Add-on plugin Installer failed to merge FileWatcher.xml.
CIM-8590
Dropdowns did not appear correctly in the Basic Mode of the Mass Update screen.
CIM-8593
Mass update failed on an external Tangosol server with a Class Not Found exception.
CIM-8594
If the repository contained a drop-down constraint with spaces in the drop-down items, Mass update reported that the record was modified even though it was not.
GDSN-148
A JavaScript error was displayed while adding a related record through search.
CIM-8575
The ONLINE text indexing mode did not allow indexing of specific repositories only. Instead, it synchronized all the repositories. Single records of an unwanted repository were indexed leading to an unpredictable server index state and subsequent search results.
To fix this, add the following property to the “Repository” category of the ConfigValues.xml file:
<ConfValue description="Repository Indexing List" isHotDeployable="true" name="Repository Indexing List" propname="com.tibco.cim.search.RepositoryOnlineList" sinceVersion="8.0.1" visibility="Advanced">
<ConfList>
<ConfListString value="PERSON"/>
<ConfListString value="COUNTERPARTY"/>
</ConfList>
</ConfValue>
CIM-8574
The Data Quality Netrics setup was not fault tolerant. To fix this,add the following property to the “Repository” category of the
ConfigValues.xml file:
<ConfValue listDefault="" name="Netrics Server Connection List" description="The List of Netrics Servers for a fault tolerant and/or load balanced setup” propname="netrics.servers.connection" sinceVersion="8.0.1" visibility="Advanced">
<ConfList>
<ConfListString value="server_hostname_1:5051"/>
<ConfListString value="server_hostname_2:5052"/>
</ConfList>
</ConfValue>
Note: If any Netrics Server is restarted in the fault tolerant setup,
run the textIndexMigration utility.
CIM-8587
On synchronizing a record with a transformation rulebase selected, the following error was displayed at EvaluateRulebase stage:
"Wrong value specifed for Relationship name ='Contains':
AppplyRulebase failed:Wrong value specifed for Relationship name
='Contains': (Undefined) RUL-4608: (Undefined)
<br>RUL-4608: (Undefined)"
GDSN-171
On the SA2 Retailer side, when the Withdraw checkbox was selected and already published products were synchronized, the Submit or Cancel button was not displayed on the workitem page.
CIM-8598
The cache-server.sh file started the JVM with a Max Memory of 4GB irrespective of the memory passed by the user.
CIM-8602
All cache server instances used a common store.
Note: The cache-server.sh and cache-server.cmd accept another argument - cache store directory. Usage details of the cache server start up script are as follows:
cache-server.sh <max memory in MB> <cache store directory path>
For example:
cache-server.sh 1024 /home/cimuser/cachestore/instance1
Directory specified as cache store must already exist. Pass a separate directory path for each cache server instance. Both <max memory in MB> and <cache store directory path> are mandatory.
CIM-8601
Migration from 6.1.3 to 7.x to 8.0.1 resulted in the System Operations and Query Tool menu options not being displayed for the tadmin user.
GDSN-176
CIM Add-On Plugin Installer (through configurator) did not update the plugins and prop folders and some files from $MQ_HOME/config.
GDSN-160
The following error was displayed during association:
CAT-1017:Invalid attribute definition for attribute PROD_COLOR_DESC.
GDSN-182
Button alignment was not correct in the Record Notification workitem page on the retailer side.
GDSN-184
"Null" was populated in the "Reason for change" column of the Record Notification workitem page.
GDSN-155
CIM2CIM: Synchronization events do not have the event ID in the Event Details page.
GDSN-188
On clicking the "View Unclassified Records" link from Synchronization Approval > Browse page, a database error was displayed.
CIM-8609
With cross catalog relationships,the match-merge workflow failed at the GetRecord activity when the was set to true in the MergeRecord activity.
GDSN-185
On 1Sync, when the quantity field was modified for a child record, the following exception was thrown:
JAV-8001: Unexpected error. Class: 'com.tibco.mdm.ui.repository.record. QuickViewServlet' and method name: 'service'. Additional information: java.lang.ClassCastExc
CIM-8615
When records are imported using relationshipAttributes with cacheServer as ActiveSpaces it used to fail in Extractrelationship occasionally.
CIM-8607
When records with a relationship were imported without mapping relationship attributes, and a record query web service was called to return relationship data of an imported record, relationshipAttributes were not a part of the response file.
CIM-8586
When adding a record with relationship with exsisting record using web service. The related record status becomes Unconfirmed.
GDSN-56
For an Enterprise of type "datapool", an error is displayed when a company profile is created and the supported catalog format is selected.
CIM-8618
On creating a record, the Oracle sequence was incremented by 2 due to Relationship Validation.
CIM-8620
Repository import did not create relationship as expected when multiple data sources with a primary data source and common key were used.
CIM-8622
Printing tangosol size in debug mode causes tangosol performance to degrade. size is printed only in debug mode but when users try to debug an issue, they encounter this problem.
Issue/Introduction
TIBCO Collaborative Information Manager 8.0.1 Hotfix 01 is now available
Environment
Product: TIBCO Collaborative Information Manager
Version: 8.0.1
OS: All
--------------------
Feedback
Yes
No
Powered by
