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.
I created a folder on my Mac to put all needed stuff for the Docker images to it:
Missing command history on Linux is a little problem when using command line utilities like wsadmin, db2, sqlplus and so on.
I found a solution for this today.
You can use rlwrap to get command history for all applications on the console and it is possible to recall and edit the commands. Rlwrap uses readline.
Installation on CentOS:
yum install readline-static gcc make
tar -xvzf rlwrap-0.41.tar.gz
Call rlwrap with wsadmin:
rlwrap -r /opt/IBM/WebSphere/AppServer/profiles/Dmgr01/bin/wsadmin.sh -lang jython -username wasadmin -password password
rlwrap and db2
rlwrap -r db2
Use rlwrap everytime with alias
alias db2='rlwrap -r db2'
alias wsadmin='cd $WAS_HOME/profiles/$DMGR/bin;rlwrap -r ./wsadmin.sh -lang jython'
This year i attended the ICON UK in Brighton. I enjoyed it very much to speak in front of a great audience and to meet friends and “lotus” guys again.
You can review my session slides here.
I extended some scripts from socconv and add a short part jython introduction.
Klaus Bild provided two scripts for setting Connections Admins through jython and wsadmin.
I want to add one detail, when you want to add multiple Admins, then you can use pipe | as delimiter.
First line would be
Thanks Klaus, i like to set the admins through a script, because fixpack installations often set the j2ee roles to default.
Because i had several issues with automated renewed ssl and ltpa keys on my websphere servers, i found this article on the blog of Mitch Cohen: http://www.curiousmitch.com/2009/06/disabling-automatic-ltpa-key-generation-in-was-or-how-to-stopsso-between-was-and-domino-from-breaking/
Perhaps this is interesting for more people.