All posts by Martti Garden

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):


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:

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


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.

Two Mac OS terminal commands to remember

I just upgraded to Mac OS Mountain Lion and I had to use my two favorite terminal commands and thought I’d share them with you, even though you can easily find them in the internet.

First: Since OS X Lion Apple decided to hide the Library folder from the user.  Since for example the Lotus Notes Data folder is located there from time to time I need to access it.  To see it permanently you need to open the terminal and run the following command:

sudo chflags nohidden ~/Library

You will need to provide your admin password.

This will set the access rights so the Library folder is visible again. But be warned, this only lasts until you “repair” the disc / file permission using the disc utility. That will reset the folder to be hidden. Just rerun the command then.

The second one is regarding the fabulous Time Machine.  Whenever your near your Time Capsule or do your backups regulary when time machine is enabled, then everything is fine. But once you are on the road the Time Machine starts making backups on your local hard drive until you reach your home again. While this is very smart in regards of file history, this can be bad when you have a SSD with limited room left.  To turn of the local backups you need to run this command:

sudo tmutil disablelocal

Here, too, you will have to provide your admin password after firing the command.

Ein kleiner Blog entdeckt die Welt…

So, nun ist es soweit: Nachdem ich innerhalb meiner Firma, der IBM, bereits seit vielen Jahren blogge, habe ich mich entschieden dies auch öffentlich zu tun.  Ich befasse mich beruflich insbesondere sehr viel mit den Themen Social Media und Mobile.  Diese beiden Themen werden daher auch einen Großteil der Blogeinträge ausmachen.  Dabei werde ich auch häufiger technische Details, sowie “best practices” bei Installationen von IBM Connections beschreiben. Aber auch Themen die mich persönlich interessieren und berühren werden ihren Platz hier finden.

So, nun aber genug der einleitenden Worte und los geht’s!