Community written guides on OpenNTF wiki

In the collaboration community, a.k.a yellowverse, the need for step-by-step product guides, installation, tuning, etc… has always been present, not because the official documentation is bad, but because if you follow it, you have to jump from a place to another in order to finish the installation of a product. See for example the installation of Connections where the Knowledge Base tells you “install DB2” and points you to the DB2 KB, then “install WAS” and points you to the WAS KB, and so on.

In the past those kind of guides have been produced, but only because an individual, an IBMer or a community member, felt the need for that and wrote the guide; there are several examples for Connections, Sametime, Docs, … The problem is that those guides were spread in several different places and either you knew where to find it or it was very difficult to do so.

In recent times there has been discussions about this topic between community members and HCL, and we told them that this kind of guides is really needed and asked for help in producing those documents

OpenNTF has decided to take the lead on this topic and provide a place where to store all the community-produced guides.
The process is this: one or more people write the guide, submit it to HCL for review and once gotten the HCL approval the guide will be published in the OpenNTF Wiki.

The first guide is available: Installing Domino on Docker, written by Daniel Nashed and Thomas Hampel and curated by me. You can find it here
Watch that space because other guides will be published there.

If anyone in the community wants to contribute, or already has produced something, get in touch with me or Graham Acres of OpenNTF and we will help you in the publication of the guide.

IBM Connections change file owner. How to get the list of all the files of a user

In Connections 6 CR5 there is the possibility of changing the owner of one or more files. To do that you need to build a list of file IDs and put it in a text file that then will be used by the wsadmin command to change ownership of those files.

The problem is to find a quick way to get the list of all the files owned by a user. Here is a quick way to do that. Thanks to Adam Gartenberg for the tip.

Step 1: Log in to Connections through a browser as an admin
Step 2: Get the user id of the user’s files for which you would like to transfer ownership.   You can do this by going to the user’s profile, the id will be in the URL of the page, for example you’ll get a url that looks like this:
Step 3: Use this API call, substitute the UUID for the user who’s files you want to transfer for the string and type that into the address control in the browser
In the above URL snippet, that will get you a feed of the first page of 500 files.  If there are less than 500 files, it will get you all of the files, if there are more than 500 files, you will need to run it for each multiple of 500 files there are in the user’s library, where you will have to increment the page parameter for each successive page, note the default page number is 1, so if there are less than 501 files, you can omit the page number parameter.
So you may have to run this a number of times depending on the number of files in the user’s library.  And if you must, create a new file for each page.
Step 4: Save the feed file and as I mentioned add an .xml extension. The feed file comes back in a less than readable and easily parseable form (using Linux command line tools that is).

Now, since I am on Windows I do not have natively the Linux command line tools, so I installed a Ubuntu bash shell in Windows ( see here for how to do that ). You have then to install tidy on that. I issued the following commands sudo apt update then sudo apt install tidy

Step 5: Now in the Linux shell type this command:
tidy -xml library-feed-page-1.xml | grep “<td:uuid>”  | tr -d ”  ” | tr  ‘\>’  ‘ \>’ | tr ‘\<\/’ ‘ \<\/’ | awk ‘{print $2}’ | tee just-the-ids.txt

you will get as result a text file called just-the-ids.txt that contains the list of all the files owned by the user you selected before

Sametime 10 Limited use is available

Sametime 10 Limited Use has shipped.

You can find it on Passport Advantage with the P/N CJ5A1ML

This first version contains the IBM Sametime Community Server V10.0 Windows (32 bit only) , as it was for Sametime 9, in a couple of weeks should ship a new version with the Community server 10 64 bit

Easter egg in Verse on Premises

At Engage I met with Dan Dumont, from the Verse team in HCL, and he told me what is the Easter egg in VoP.

Open your mail, then in the search bar type “I am an easter egg” then press Ctrl+Alt+Enter

A reversed Verse logo will appear scrolling at the bottom of the screen

Now if you press the space bar, it will start shooting yellow spots across the screen, the goal is to hit the faces in the ITM bar at the top 🙂

Press Esc to stop.

High Usage Views and publishing statistics to New Relic. Bug in Domino 10.0.1

I found a bug, or better an incompatibility between two new features of Domino 10.

If you enable the High Usage Views feature, it will break the publishing of the statistics to New Relic.
Looking in the log you will find an error like this one

[16D4:0090-11B0] 26/03/2019 07:32:23,23 StatPubFlushPostData> Failed to POST metric data using URI: ‘’; Unable to load specified URL.

I had confirmation from Support that this is a bug and it will be fixed in Domino 10.0.2

“Hello Roberto,
Greetings !
We have confirmed with our development team that Fix for this issue will be in 10.0.1 FP2. Hopefully Domino 10.0.1FP2 will be released in june.”

I will be speaking at the ISBG Meeting

The agenda for the ISBG Meeting that will happen in Stockholm on June 11 and 12 has been published here

I will speak about installing Domino on Docker. Hope to see many of you there!

Error ADMN0022E (Access is denied because of insufficient or empty credentials) when working with WAS ISC

I have a Connection environment installed for a customer and I have always started and stopped the servers using the ISC.

All of a sudden I could not do that anymore and got the ADMN0022E error in the SystemOut.log. I had to start and stop servers and nodeagent manually from the command line.

A quick check with my friend Andrea Fontana gave me the solution. For whatever reason the administrator credentials in the file soap.client.props, located in profiles/Dmgr01/properties were blank.

I filled in the correct values, synced the nodes and the problem was solved