This Readme document contains information about the installation of this package and about restrictions in support of IBM CMIS, Version 3.0.4 Interim Fix 8.
Readme file for:
IBM CMIS. This interim fix contains IBM CMIS APARs.
Product or component release:
Version 3.0.4.0
Update name:
Interim Fix 8
IBM CMIS build number:
cmis-fncs-installer304.008.066
IBM CMIS Fix ID:
Publication date:
October 7, 2019
Last modified date:
October 7, 2019
Additional documentation for IBM CMIS 3.0.4.0 can be found at : https://www.ibm.com/support/knowledgecenter/en/SSEUEX_3.0.4/KC_ditamaps/contentnavigator.htm
Known problems, restrictions, and solutions that affect
administration and usage of interim fixes are documented as
techdocs in the product support knowledge base. Use the following
link to query the product support knowledge base by searching for
the product and version number: https://www.ibm.com/support/home.
This interim fix includes the following known problem:
Additional Known problems and restrictions are contained in the 3.0.4.0 Release Notes at https://www.ibm.com/support/knowledgecenter/en/SSEUEX_3.0.4/com.ibm.eucrelnotes.doc/eucrm003.htm
The official statements for hardware and software support for IBM CMIS are provided as part of the hardware and software requirements for IBM Content Navigator, Version 3.0.4.0.
For complete details about the hardware and software requirements for IBM Content Navigator, IBM CMIS see Software Product Compatibility Reports.
The following information and steps apply to IBM CMIS. To install the interim fix, perform the steps below using the interim fix executable. When you install an interim fix, you can run the installation wizard or run a silent installation. This interim fix can be installed as an update to IBM CMIS Version 3.0.4.0 or later.
The interim fix installation program updates the files in the directory where IBM CMIS is installed. After the installation program completes successfully, restart the web application server and redeploy the IBM CMIS web application to apply the changes from the interim fix.
For more information about installing IBM CMIS, Version 3.0.4.0, see https://www.ibm.com/support/knowledgecenter/en/SSEUEX_3.0.4/com.ibm.installingeuc.doc/eucmis000.htm.
To install IBM CMIS, Version 3.0.4 Interim Fix 8:
Install the interim fix by running the installation wizard or
by running a silent installation:
Important: Do not enter line breaks in the
command that you enter to start the installation program.
AIX
At a command prompt, change to the directory where you downloaded the interim fix and enter one of the following commands:
Linux
At a command prompt, change to the directory where you downloaded the interim fix and enter one of the following commands:
Linux for System z
At a command prompt, change to the directory where you downloaded the interim fix and enter one of the following commands:
Windows
At a command prompt, change to the directory where you downloaded the interim fix and enter one of the following commands:
Open the IBM CMIS Configuration and Deployment tool, click File > Open Deployment Profile, select the target deployment profile and click Open.
Run the "Configure IBM CMIS for <repository type>" task. For more instructions, see the topic, https://www.ibm.com/support/knowledgecenter/en/SSEUEX_3.0.4/com.ibm.installingeuc.doc/eucde070.htm.
Run the "Build the Web Application" task. For more instructions, see the topic, https://www.ibm.com/support/knowledgecenter/en/SSEUEX_3.0.4/com.ibm.installingeuc.doc/eucde096.htm.
Run the "Deploy the Web Application" task.
For more instructions, see the topic, https://www.ibm.com/support/knowledgecenter/en/SSEUEX_3.0.4/com.ibm.installingeuc.doc/eucde098.htm
Stop the IBM CMIS web application server.
Clear the application server cache:
For IBM WebSphere Application Server: Delete the following folders:
Delete the cmis folder from the temp temporary directory.
For example, on Microsoft Windows, delete the cmis folder from the following directory: \IBM\WebSphere\AppServer\profiles\AppSrv01\temp\ServerName Node01\server1.
Delete the subfolders in the wstemp directory. This folder is different from the temp folder. Do not delete the wstemp folder itself.
For example, on Windows, delete the subfolders in following directory: \IBM\WebSphere\AppServer\profiles\AppSrv01\wstemp.
For Oracle WebLogic Server: Delete the cmis folder from the tmp temporary directory.
For example, on Windows, delete the cmis folder from the following directory: \Oracle\Middleware\user_projects\domains\base_domain\servers\AdminServer\tmp\_WL_user.
Start the IBM CMIS web application server.
Verify that the correct version of the software is deployed to the web application server. For more information, see the topic, "Verifying your deployment" in the information center: https://www.ibm.com/support/knowledgecenter/SSEUEX_3.0.4/com.ibm.installingeuc.doc/eucup031.htm.
When you uninstall the interim fix, you also uninstall IBM CMIS.
The interim fix for IBM CMIS uninstallation program removes the program and all applied fixes. You cannot remove only the interim fix.
The fixes that were provided in previous IBM CMIS Version 3.0.4
Interim Fixes are combined in this fix. Please refer to the readme
for IBM Content Navigator and IBM CMIS Version 3.0.4 Interim Fix 7
available on IBM Fix Central information about previous IBM CMIS
APARs.
PJ45812 Query fails when aliasing a property where the alias and property names are the same.
(IBM CMIS users) IBM CMIS for FileNet Content Manager query fails
when aliasing a property where the alias and property names are
the same. With this fix, the query runs successfully even when the
alias and property names are the same.
(IBM CMIS users) The PathModelCreate tool fails to create the IBM
CMIS data model in IBM Content Manager repository. With this fix,
PathModelCreate tool creates the data model successfully.
IO27028 WAS server cannot control the class loading order which causes some nodes to fail in cluster.
(IBM CMIS users) IBM CMIS for FileNet Content Manager webservice binding fails when deployed to a WebSphere cluster. This is because Websphere cannot control the class loading order which causes some cluster nodes to fail. With this fix, only one class is downloaded and this prevents the class loading order issue that caused the failure.
(IBM CMIS users) IBM CMIS for OnDemand throws a NullPointerException occurs when clicking on Unfiled link on a repository containing document(s).
PJ45690 An error occurs when modifying ACL of objects.
(IBM CMIS users) IBM CMIS for FileNet Content Manager throws an error when ACL on a document is modified. With this fix, this issue does not occur.
PJ45649 IBM CMIS Web Service Binding fails with an exception.
(IBM CMIS users) Web Service Binding fails with an exception for both IBM CMIS for Content Manager and IBM CMIS for FileNet Content Manager (Versions 1 and 2), on Linux. With this fix, this issue is resolved.
IO26847 IBM CMIS for Content Manager OnDemand does not support ODWEK SSL configuration and non-default installation location.
(IBM CMIS users) The parameter ODWEK_INSTALL_DIR allows ODWEK, when installed at a non-default location, to access to its native libraries. The ODSSL parameters are to configure the SSL communication between ODWEK and the Content Manager OnDemand server. With this fix, both these parameters are supported.
IO26425 IBM CMIS web services cannot be deployed.
(IBM CMIS users) IBM CMIS web services cannot be deployed in a Linux environment with an IBM WebSphere Network Deployment application server that is configured to use Java v1.8. With this fix, the web service are deployed successfully.
IO26629 ClassNotFoundException occurs with IBM CMIS for FileNet Content Manager.
(IBM CMIS users) IBM CMIS for FileNet Content Manager writes an 'class not found' exception in the IBM CMIS and FileNet Content Engine log files if the Social Collaboration Search Indexing Extension (add-on) is not found on the object store. With this fix, this exception which is not required to be captured is not logged to the IBM CMIS and FileNet Content Engine log files.
(IBM CMIS users) The call to setACL() method of the CmisObject class causes all ACEs for a document to be deleted, in IBM CMIS for FileNet Content Manager v1.1. With this fix, the setAcl() method will retain all the ACEs applied for the document.
(IBM CMIS users) IBM CMIS for Content Manager creates a new version of a document if the document's attributes are updated even though the document's content is not. With this fix, a new version of the document is not created when only the attributes are updated.
http://www.ibm.com/legal/copytrade.shtml
INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some jurisdictions do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you.
This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice.
Other company, product, or service names may be trademarks or service marks of others.
The license agreement for this product refers you to this file for details concerning terms and conditions applicable to third party software code included in this product, and for certain notices and other information IBM must provide to you under its license to certain software code. The relevant terms and conditions, notices and other information are provided or referenced below. Please note that any non-English version of the licenses below is unofficial and is provided to you for your convenience only. The English version of the licenses below, provided as part of the English version of this file, is the official version.
Notwithstanding the terms and conditions of any other agreement you may have with IBM or any of its related or affiliated entities (collectively "IBM"), the third party software code identified below are "Excluded Components" and are subject to the following terms and conditions: