WebSphere
During troubleshooting of WebSphere Application Server it is necessary to enable traces and see more detailed log messages.
Enabling these traces is very annoying, because you need to follow long click paths within the Integrated Solution Console (ISC).
This week I installed IBM Connections 5.5CR1 on a Windows Server. I used WebSphere Application Server 8.5.5.9 and everything ran pretty smooth, but the Connections install itself ended in an error after all applications were successfully installed.
Last Update: Read in about 1 min
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.
Last Update: Read in about 3 min
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.
Last Update: Read in about 5 min
Within the fixlist of the new released CR3 of IBM Connections 5 there are several new configuration options mentioned. One of the interesting ones for me is the mobile update parameter AllowRemoveAccount. The default value is “false” and your Connections environment still works before, but what’s changed when you set this to true?
The official documentation is already uptodate and shows us:
When you set this option to true, accounts can be removed from a mobile device without requiring the user to login and without any authorization check. The user is asked to confirm the deletion of an account before it is removed.
Last Update: Read in about 3 min
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
cd rlwrap-0.41
./configure
make
make install
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
vim ~/.bash_profile
export WAS_HOME=/opt/IBM/WebSphere/AppServer
export DMGR=Dmgr01
alias db2='rlwrap -r db2'
alias wsadmin='cd $WAS_HOME/profiles/$DMGR/bin;rlwrap -r ./wsadmin.sh -lang jython'
Last Update: Read in about 1 min