Monitor WebSphere with ELK and Nagios

Worked a lot with the ELK stack for log management and Nagios for system monitoring in the last months and like both solutions a lot.

They are very flexible and customizable to match almost every customer environment. So the natural next step was to combine both solutions to build a very powerful system monitoring and management solution for WebSphere servers (IBM Connections/IBM Sametime).


Read more

managed-settings.xml issue after IBM Sametime 9 upgrade

I manage all our Sametime client settings through managed-settings.xml and I love the simplicity.

But recently I updated our IBM Sametime environment to Version 9 and the managed settings stopped working.

So I enabled the debugging parameters in and looked at the trace:

"org.xml.sax.SAXParseException: Premature end of file."

Mhmh, not very specific, sounds like a prob with the xml but I used the same xml without any problems with version 8.5.1

So I checked to open the file via Webbrowser, worked. As this wasn’t my first issue after the upgrade I was just about to change my job and become a gardener. OK, I opened up my webbrowser for a last time and wanted to check the settings again when a green light enlightened me:

Screen 2013-10-25 at 09.58.52


Oh man, of course, I enabled “Redirect TCP to SSL” after the upgrade but forgot to change the “Sametime update site URL” accordingly. The browser has no issue with the http link and just was redirected to https, but the Notes/Sametime client doesn’t like this and throws the error.

Guess what, changing the link to https solved the issue, happy bunny 🙂

Change default SIP listening port – IBM Sametime Client

Quick tip.

Want  to change the default SIP listening port of your IBM Sametime Client? Browse to
and open preferences.ini.

In there you will find:

# Default SIP Preferences


Change listening port, restart Notes, done.

Thanks to Claudio for providing me this info!

Start Sametime TURN Server as Windows Service

Since Ver. 8.5.2 Sametime provides video communications across NATed networks or firewall via the TURN server when direct peer-to-peer communications are not possible. Unfortunately this “server” is only a java program which has to be started manually and which will be closed when you log out the server.

Workaround is to create a windows service which will start the TURN server as local system account:
Read more