Tag Archives: docs

IBM Docs editing not working due to duplicate account error

When you get an error when trying to edit a document and the log file of the server shows the following error:

2/12/15 15:34:06:712 CST] 0000016f ConcordDocSer E  Have no permission on this file in repository

                 com.ibm.concord.spi.exception.RepositoryAccessException: Exception occurred with error code: CLFAD1000, message: Have no permission on this file in repository, and additional data: {“docUri”:”8d23a756-f1cf-4aa8-ad51-85e9a07e1ad3″,”repo_err_code”:”DuplicateUserAccount”,”repo_err_msg”:”EJPVJ9070E: Unable to logon the user with the J2EE principal wasadmin”,”repo_http_status”:403}

 

then the cause is that indeed the wasadmin is in the files database twice and the the system therefore is unable to find out which is the one to be used. To solve this you have to sync the member table of the database to have the invalid user(s) removed:

1. Start the wsadmin client.

 

Go to <WAS_HOME>\profiles\<DMGR>\bin>

./wsadmin.sh -lang jython -user <admin_user_id> -password <admin_password> -port <SOAP_CONNECTOR_ADDRESS Port>

 

2. Start the Files script with the following command: 

 

execfile(“filesAdmin.py”)

 

3. Use the following command to synchronize the internal IDs of the Files users:

 

FilesMemberService.syncAllMembersByExtId( {“updateOnEmailLoginMatch”: “true“ })

 

This should remove all duplicate users and IBM Docs should be working now.

Disable UAC in Windows when installing IBM Docs 1.0.7

I lately saw a lot of installations of IBM Docs 1.0.7 fail when using the new Graphical Installation Interface. Most of them failed while executing the remote jobs. The Remote Job Manager of WebSphere does the installation on the remote servers (the Docs installation is done centrally and distributing all components to the corresponding servers).  To do so, the User Account Control (UAC) of Windows must be disabled, since otherwise the installer will trigger the Windows warnings asking, if you really, really, really want to do something – except, that this pop up will not show up. Consequently the installation step will fail, as Windows does not allow this step to be done.

While this is very important it seems to be missed very easily.  Here you can find it in the installation instructions:

http://www-01.ibm.com/support/knowledgecenter/SSFHJY_1.0.7/deploy/configuring_windows_systems.dita

If you cannot disable UAC in your environment, then you will have to use the script based installation.

How to integrate IBM Docs 1.0.7 with IBM Connections 5.0 CCM CR2 (Filenet Libraries in Connections)

IBM Connections CCM integrates IBM Connections Communities with Filenet libraries, allowing users to store files hierarchically and add further features such as file types and approval process to it.  IBM Docs is able to integrate into those libraries to all user to view and edit files collaboratively. How to do this is unfortunately at the moment not very well documented in the IBM Docs knowledge center (this will be changed in the near future). Therefore I have created a Step by Step guide that will help you to install IBM Docs 1.0.7 on a IBM Connections 5.0 CCM CR2 system including the integration with Filenet Libraries.

You can find the guide on Greenhouse. Greenhouse is IBMs collaboration demonstration platform available to everyone, demonstrating solutions such as Sametime, Portal, Connections, Docs, Forms and many more (you will have to sign up, though).

Here the direct link to the guide:

https://greenhouse.lotus.com/files/app#/file/3116002b-81d3-4fbf-875d-9e3a139f4855

Installation errors with IBM Docs 1.0.7 regarding Remote Installation steps

If you get errors when installing IBM Docs on Windows such as: INFO Not all remote installation jobs complete successfully! followed by a rollback of the installation then make sure, you are using Powershell version 2.0 and not 1.0. You can check that by starting the powershell and entering $PSVersionTable . If it does show Version 1.0 you can find Version 2 here.

IBM Docs 1.0.7 was just released

Update: The part number has changed and is now: CN54LML.

 

Very quietly IBM Docs 1.0.7 was released just now, alongside with Connections 5.0 CR2. You can find it using part number CN30NML.

Here is the updated link to the Knowledge Center:

http://www-01.ibm.com/support/knowledgecenter/SSFHJY_1.0.7/welcome/ibmdocs_1.0.7.html

New things in IBM Docs 1.07 are the centralised graphical installer, the completely rewritten editor for documents, integration with Sametime, Filenet as well as CCM Libraries.

If you have version 1.0.6 installed: This is a MANDATORY install. 😉

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.

IBM Docs: Conversion server unable to find NFS share

If you have set up IBM Docs and are sharing the files using NFS with the Conversion Server of IBM Docs, you may see some errors that the Conversion server is unable to find the shared directory even though in the file browser you can clearly go there and see all files. The Viewer and the Docs application will tell you that the Conversion server took too much time to respond.

This can be due to the fact, that the Conversion Server is started as a Windows Server with local system authority, while the binding of the NFS server is done with the user you are logged in. As the shares are only available to the user that mapped it, IBM Docs and the Conversion server are unable to see it.

To solve that, you need to map it with the local system.  This technet entry shows how to do it:

http://blogs.technet.com/b/sfu/archive/2010/05/26/accessing-nfs-shares-through-an-application.aspx

Once you did the changes IBM Conversion server should be able to access the files in the shared NFS folders.

IBM Docs entitlement – Limit access to IBM Docs in a IBM Connections environment

An IBM Docs question that comes up a lot is:  Is it possible to limit people accessing IBM Docs?  Meaning: If I have 10000 users in IBM Connections – can I roll out IBM Docs in a first step to a subset of 2500?

The answer is: Yes, that is possible. It’s call IBM Docs entitlement and can be easily set in the WebSphere Application Server WebConsole.  In the IBM Docs Wiki is documented how (in this case for Version 1.0.5 for IBM Docs):  http://www-10.lotus.com/ldd/docswiki.nsf/xpDocViewer.xsp?lookupName=Installing+and+deploying+IBM+Docs+1.0.5+documentation#action=openDocument&res_title=Enabling_IBM_Docs_entitlement_id105&content=pdcontent