Tag Archives: websphere

Better logstash filter to analyze SystemOut.log and some more

Last week I wrote a post about Using Docker and ELK to Analyze WebSphere Application Server SystemOut.log, but i wasn’t happy with my date filter and how the websphere response code is analyzed. The main problem was, that the WAS response code is not always on the beginning of a log message, or do not end with “:” all the time.

I replaced the used filter (formerly 4 lines with match) with following code:

grok {
        # was_shortname need to be regex, because numbers and $ can be in the word
        match => ["message", "\[%{DATA:wastimestamp} %{WORD:tz}\] %{BASE16NUM:was_threadID} (?<was_shortname>\b[A-Za-z0-9\$]{2,}\b) %{SPACE}%{WORD:was_loglevel}%{SPACE} %{GREEDYDATA:message}"]
        overwrite => [ "message" ]
        #tag_on_failure => [ ]
grok {
        # Extract the WebSphere Response Code
        match => ["message", "(?<was_responsecode>[A-Z0-9]{9,10})[:,\s\s]"]
        tag_on_failure => [ ]


Using Docker and ELK to Analyze WebSphere Application Server SystemOut.log

I often get SystemOut.log files from customers or friends to help them analyzing a problem. Often it is complicated to find the right server and application which generates the real error, because most WebSphere Applications (like IBM Connections or Sametime) are installed on different Application Servers and Nodes. So you need to open multiple large files in your editor, scroll each to the needed timestamps and check the lines before for possible error messages.

Klaus Bild showed on several conferences and in his blog the functionality of ELK, so I thought about using ELK too. I started to build a virtual machine with ELK Stack (Elasticsearch, Logstash & Kibana) and imported my local logs and logs i got mailed. This way is cool to analyze your environment, but adding just some SystemOut.logs from outside is not the best way. It’s hard to remove this stuff after analyzing from a ELK instance.

Then I found a tutorial to install ELK with Docker, there is even a great Part 2 of this post, which helps us installing an ELK Cluster. Just follow this blog posts, install Docker and Docker-compose. It’s really fast deployed. In my case i do not use flocker, it’s enough to use a local data container for the elasticsearch data.

Why do I use Docker instead of a virtual machine? It’s super easy to just drop the data container and begin with an empty database.

My setup

I created a folder on my Mac to put all needed stuff for the Docker images to it:

mkdir elk
cd elk


New OpenNTF.org project: Administration Scripts for WebSphere

I started a new project on OpenNTF for the collection of scripts we created to speed up and simplify WebSphere and Connections Administration.

Link to this project: Administration Scripts for WebSphere

In the moment most of documentation is only as comment in these scripts. Descriptions can be found in Github and Slideshare.


  • J2EE Security Role Backup and Restore
  • Set initial Security Roles for Connections Applications (Author: Klaus Bild)


When you want to start with this collection, copy the jython script to your Deployment Manager bin-folder ($WAS_HOME/profiles/Dmgr01/bin) and call the scripts with wsadmin.sh -f scriptname

I will create more documentation in the next days. Please use the slideshare documents and icon uk presentation to begin using and coding jython.


I will presentate some of these scripts on 50. Dannotes on Thursday 28th November in Korsør.

WebSphere Application Server on Ubuntu 12.04 64 Bit

I’m really impressed of the WAS 8 installation. Install Manager can handle multiple repositories, so you can install the core package and updates in one step. That’s lots faster than installing WAS 7, Update Installer and the fixes.

Yes i know Ubuntu is unsupported for WebSphere Application Server, but i like the simple install and update process. So i use it on about 80 % of my linux testsystems and i have no problems when installing IBM Domino, WebSphere, DB2 or Connections.

Additional software for Ubuntu

I added the following packages to Ubuntu and use x-forward for installing IM and WAS.

Relink /bin/sh

dpkg-reconfigure dash

Install Firefox and SSH

apt-get install firefox
apt-get install openssh-server

Add 32 Bit Libraries for Install Manager

apt-get install libxtst6
apt-get install ia32-libs

Uninstall AppArmor

apt-get remove --purge apparmor*

Profile Manager

After WebSphere installation the profiles manager starts automatically and it WORKS! I can configure profiles on a 64 Bit Linux through it.

Service install

Installing the services on Ubuntu works too with the wasservice.sh command, which fails on WAS 7.

cd /opt/IBM/WebSphere/AppServer/bin

./wasservice.sh \
  -add Dmgr \
  -serverName dmgr \
  -profilePath /opt/IBM/WebSphere/AppServer/profiles/Dmgr01\
  -wasHome /opt/IBM/WebSphere/AppServer \
  -stopArgs "-username adminaccount -password password"

./wasservice.sh \
  -add nodeagent \
  -serverName nodeagent \
  -profilePath /opt/IBM/WebSphere/AppServer/profiles/AppSrv01 \
  -wasHome /opt/IBM/WebSphere/AppServer \
  -stopArgs "-username   adminaccount -password password"

I always install services for deployment manager and the nodeagents. The automatic start of my application servers i configure through the ISC and the Monitoring Policy.

I do this, because i had several issues when starting the application servers through init or windows service and the servers work in a cluster.

When you want to stop your application servers automatically on reboots, you should register a init-Skript and remove the start tasks in /etc/rcx.d for these application server services.

Started WebSphere 8 Download

I read today the requirements for IBM Connections 4.5, which will be released on 29th of march. On point there is WebSphere Application Server V8.0.0.5 for Network Deployment.

WebSphere Application Server V8 must be installed through Install Manager, so you have to download 4 packages for the server core and 4 packages for supplements. After this the fixes for, what do you think you many data will it be?

You will download more than 10 GB of Software only for WebSphere Installation! 6.x GB for V8 and about 5 GB for fixes.

Here the Software (with some DB2 stuff):