Tag Archives: ibm

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:


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. 😉

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:


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


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


This a freely chosen name for the service.


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.


Edit it to fit your environment.


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.


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.


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:


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/ .

Population of Connections Database Field DisplayName if this entry does not exist in LDAP

Today I noticed in a customer installation that nowhere in the LDAP a usable displayname (aka “Martti Garden”) was available.  My collegue Barbara Koch helped me out solving this:  The attributes surname (sn) as well as givenname (givenname) were available to I had to compute the display name.


So I edited the profiles_functions.js and added the following function:


// Function to compute the displayname from given name and surname


// Get the content of the “sn” field as a string

var surname = work.getString(“sn”);

// Get the content of the “givenname” field as a string

var vorname = work.getString(“givenname”);

// If both entries are not empty

if (vorname != null && nachname != null) {

// return first name and last name separated by a space

return vorname + ” ” + nachname;

// otherwise


else {

// return the content of the “cn” field as a string, if it is empty it will return NULL

return work.getAttribute(“cn”);



Now I had to edit the map_dbrepos_from_source.properties and mapped the function to the diplayname field:


Now I ran the populate_from_dn_file script and had the Displayname showed correctly in IBM Connections.

Social File Sharing: IBM Connections vs. MS SharePoint

A collegue brought the following great comparison of Social File Sharing in IBM Connections and MS SharePoint to my attention.  While it is done cleary from IBMs point of view I still can’t believe that SharePoint could be that “unsocial” when it comes to it’s greatest strength: files and documents.  If you are using MS SharePoint feel free to comment and show me what the colleague is overseeing. 😉

Here the video in English:

Here the video in German:



Resetting WAS-Admin Password when the Browser Console does not work anymore

If you have to reset the WAS Admin password without using the web interface  (e.g. if you cannot log in anymore for various reasons) here is how you reset a forgotten WAS-Admin password:

1. Go to your WAS-Profile/bin directory using a command prompt (in IBM Connections case this would be ../(washome)/AppServer/profiles/DMGR/bin )
2.  Type the following command: wsadmin -conntype NONE and hit Enter
3.  Then you should be in the wsadmin prompt.  You now enter:  $AdminTask changeFileRegistryAccountPassword {-userId <wpsadmin-UserID> -password <new-password-for-wpsadmin>} Then hit Enter.
4.  Now the new password is stored temporarily.  So finalize the changes type $AdminConfig save followed by Enter. 

Restart WAS and you should be able to login using the new password.

Sometime you just need to disable the WAS application security to disable the federated repositories.  This is done in a similar fashion:

1. Go to your WAS-bin directory using a command prompt (in IBM Connections case this would be ../(washome)/AppServer/profiles/DMGR/bin )
2.  Type the following command: wsadmin -conntype NONE and hit Enter
3.  Then you should be in the wsadmin prompt.  You now enter the simple command: securityoff Then hit Enter.
4.  To finalize the changes type $AdminConfig save followed by Enter.

Restart WAS and you can log into the console using any username without a password.


Lotus Notes displays wrong calendar week

Under certain circumstances it is possible, that Lotus Notes will display the wrong calendar week.  This is due to different counting of calendar weeks in e.g. Europe and U.S. (in Europe weeks starting on Monday in the US on sundays).  In my case this happened, when I set my Mac OS Lion to English and thus to an American Environment.  For example the last week of this year is displayed as calendar week 53 as can be seen in the following screenshot:


To fix this and have the correct week shown we must set the calendar week counting to ISO standard.  To do so go to the preference pane and open Calendar and To Do followed by Regional Settings.  Now you can switch the radio button on the bottom from “Use my operating system regional setting” to “always use ISO standard“.


After clicking OK switching back to the calendar show that the week number has changed to week 52: