Category Archives: IBM Connections

Force the creation of thumbnails for all files in Connections with File Viewer

When installing the File Viewer for IBM Connections (which is free in case you did not know), then it will create thumbnails for a quick preview for all files uploaded from now on. You might have a large number of files already in the system though. To enforce the creation of thumbnails for all existing files in the Files application of IBM Connections you need to do the following steps (for IBM Docs / File Viewer 1.0.7 you will have to install iFix 2 first, which you can find in FixCentral):

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:

 

FilesThumbnailService.generateForAllFiles()


Now all thumbnail will be created (can take some time depending on the amount of Files in your Connections environment).

Installing IBM Connections 5.0, CR2 and IBM Docs on Linux – Guides

My colleague Charles Price has created two guides covering the installation of IBM Connections 5.0, CR2 and IBM Docs on Linux. While I have created guides like that before, I have always done them on Windows, as Linux is, for me at least, a different kind if beast that I have so far avoided as much as I can. 😉

Here you go:

Installation guide IBM Connections 5.0 on Linux

Installation guide IBM Connections 5.0 CR2 on Linux

Installation guide IBM Docs 1.0.7 on IBM Connections 5.0 CR2 on Linux 

 In the last one I especially like the two topics of upgrading CCM for Docs as well as the description on how to configure either NFS or CIFS shares.

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

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.

How to disable automatic LTPA Key generation in WebSphere

When setting up SSO between WebSphere and Domino the automatic LTPA key generation must be turned off. These are the steps on how to do this:

 

  1. Log into the WebSphere Application Server Integrated Solutions Console as an administrator, expand Security, and select Global Security.
  2. Click LTPA in the Authentication section and then, in the Key generation section, click Key set groups.
  3. Select NodeLTPAKeySetGroup in the table and, in the Key generation section, un-check the Automatically generate keys check box, if is already checked.
  4. Click OK to save the changes.

Problems creating CCM Domain in Connections 4.5

Today I had some issues creating the CCM P8 Domain, getting errors while creating the domain as well as some access errors.  Here I found the proper solution posted by Shil P:

http://www-10.lotus.com/ldd/lcforum.nsf/869c7412fe5d56b7852569fa007826e3/fa22392acbe67b7d85257c0000618306?OpenDocument

1. Stop Connections JVM. Nodeagent and Dmgr can remain up (unless you want to clear TEMP and WSTEMP files).

2. Remove all files and directories contained WITHIN …\IBM\Connections\Data\Shared\CCM. Do not delete the CCM directory itself.
3. Delete the dminfo.properties file from …\IBM\Websphere\AppServer\Profiles\Dmgr\bin
4. Drop and recreate the IBM Connections Content Manager database via dbWizard.
5. Start Connections JVM
6. Run ..\ccmDomainTool>createGCD.bat
7. Run ..\ccmDomainTool>createObjectStore.bat

The main culprit seemed to have been a improper dminfo.properties.  Deleting it solved the problems.

Adding IBM Connections / WebSphere Applications to Windows Services

When installing IBM Connections on Windows only the Deployment Manager is added as a windows service during the installation. Parts like the node agent or later on the Connections clusters are not added.  To do so you need to run the following command from /WebSphere/AppServer/bin :

WASService.exe -add SERVICENAME -servername SERVERNAME -profilePath “C:\IBM\WebSphere\AppServer\profiles\AppSrv01” -stopArgs “-user wasadmin -password password” -userid windowsadmin -password password -startType automatic

SERVICENAME

This a freely chosen name for the service.

SERVERNAME

This the name of the specific server that needs to be stopped (such as nodeagent).  To find out the names you can go to /WebSphere/AppServer/profiles/AppSrv01/bin and run serverstatus.bat -all . This will list all servers including the running status.

profilePath

Edit it to fit your environment.

stopArgs

These are necessary to be able to not just start the service, but to also stop it. It will provide the WAS admin credentials during the stop process. Enter your own wasadmin user ID / password.

userid

This user has to be a windows user that has the right to start and stop services.  Once the service is created you can change it in the service setting in the Services list from Windows to local system account.

startType

This defines whether this service is started automatically at booting or not.

Files Plugin for Lotus Notes does not upload documents

If you are using the Files Plugin Lotus Notes from the Greenhouse Solutions Catalog, you may be finding yourself being able to see and download all files in IBM Connections Files repository, but when trying to upload a file though, you might get an error message like that:

A problem with the server was encountered.

 

To solve that problem you need to add one line to Lotus Notes plugin-customization.ini:

com.ibm.documents.connector.service/ENABLE_SSL=true

Then save the ini-files, restart the Notes Client and the upload should be working now.

The plugins-customization.ini can be found in your Notes install directory/framework/rcp in Windows.  Mac user right click the Notes.app icon and choose “Show package content”. Then they go to Contents/MacOS/rpc/ .