Upload a new version of a document with IBM Docs 1.0.6

One of the new features of IBM Docs version 1.0.6 is, that you are now able to upload a new version of a document, even if the Document is “owned” by IBM Docs. To enable the “Upload new version”-button again you need to enable this feature though. Which steps you need to do depends on where you are in the installation, since the steps for enabling the upload new version feature are different depending on whether you enable it before you install the IBM Docs extension plug-in, before you upgrade the plug-in, or after you install or upgrade the plug-in.

 

To enable before installing IBM Docs extension plug-in:
1. Log in to the system where you installed IBM Connections, with the user who runs the Deployment Manager process.
2. Extract the installation package to a directory.
3. Open a command prompt and then go to the IBMDocsExt4IC_Install_Package/installer directory.
4. Copy the response file that you created to the current directory.
5. Rename the response file cfg.properties and add the following parameter under section [ICExt]:
enable_upload_new_version=true
6. Save the file.
7. Run the silent installation file:
Linux: ./install.sh
Windows: install.bat

 
To enable before upgrading IBM Docs extension plug-in:
1. Log in to the system where you installed IBM Connections, with the user who runs the Deployment Manager process.
2. Extract the upgrade package to a directory.
3. Open a command prompt and go to the DocsLCExtension/installer directory.
4. Copy the response file that you created to the target folder.
5. Rename the response file cfg.properties and add the following parameter under section [ICExt]:
enable_upload_new_version=true
6. Save the file.
7. Run the silent upgrade file:
Linux: ./upgrade.sh -installRoot
Windows: upgrade.bat -installRoot

 
To enable after installing or upgrading the IBM Docs extension plug-in:
1. Locate the IBM Connections Deployment Manager.
2. Log in to the system where you installed IBM Connections, with the user who runs the Deployment Manager process.
3. Find the configuration file “files-config.xml” in one of the following locations:
Windows: In the LotusConnections-config folder
Linux: Usually in /opt/IBM/WebSphere/AppServer/profiles/Dmgr01/config/cells/$CELLNAME/LotusConnections-config
4. Edit files-config.xml, changing the section that contains <objectType id=”00000000-00000-0000-0001-00000000000000″> to the following:
<actionControl>
<objectType id=”00000000-00000-0000-0001-00000000000000″>
<actions>
<action enabled=”true” name=”uploadNewVersion”>
</action>
<action enabled=”true” name=”download”/>
<action enabled=”false” name=”downloadEmptyFile”/>
<action enabled=”true” name=”restoreVersion”>
</action>
</actions>
</objectType>
</actionControl>
5. Save the file.
6. Log in to the IBM Connections Deployment Manager administrator console.
7. Synchronize all nodes.
8. Restart the Connections clusters that run the Files and Community applications.

Once you decide to work with a document offline and intend to upload a new version later it is advised, though, to lock the file in Connections Files to prevent others working on it online and their changes being consequently overwritten by uploading the new version.