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 week starts in the beautiful town Prague with Social Connections VI. I met great people and first of all i want to thank the organisation team for this great event.
At the end we made the traditional image with all attendees.
I enjoyed two very delicious dinners and had great discussions around IBM ICS, met old and new friends. After years of tweets, forum entries and virtual talks i finally met Martin in person and had an entertaining evening with him and Sjaak.
Big thanks to Oliver Heinz who made fantastic photos of prague, us and around the event. All pictures in this blog posts are made by him.
My session “Script it!
This time i made a session without support of Klaus or Sharon, but i was happy with the result and i hope that some attendees will help to get the IBMCNX Community scripts more complete.
And for everyone the offer again, you see the different kinds of persistent Skype group chats, if you want to join, send me a short message.
During this week we heared several announcements:
I see forward to Social Connections VII and hope to meet lots of you there!
As preparation for Social Connections VI in Prague next week i redesigned the “Administration Scripts for IBM Websphere“.
- all scripts are moved to a subfolder with DMGR/bin (folder name: ibmcnx)
- tested in multinode environments
- added some classes everybody can use for his own scripts
- adding policies to libraries (personal and communities) are using search now
- documentation of all jvm settings of each application server
- create a file with all documentation in one step
- create cluster members for additional nodes
Sharon created a document with the content of all of our presentations and collected several tipps all around connections and community scripts. She will share this next time. We started to share parts of this document and more documentations (installation, usage) for scripts and IBM Connections on:
The new version can be downloaded from:
IBM released a tech document on friday with title: Search fails with the error CLFRW0060E: Input-output exception.
This document solves one of my problems i had in a demo environment since two weeks. I traced the environment, checked j2ee roles, reinstalled CR3 and 4, redeployed search and activities, but i always got an error, when the search wants to access the activities seed list.
So what happened? I want to show the /search/serverStatus page in a course and for this i want to remove all warnings and errors. When you don’t set SEARCH_SEEDLIST_TIMEOUT, you get a warning, that the variable is not set.
So i had set this to 150 and checked the serverStatus page and all was green. So i thought everything is ok and didn’t check the documentation to this. After some hours the search was broken, with the error mentioned above. When i checked the Seedlist URL with the browser everything was ok, when the search wants to access it i got the Input-output exception.
When you read the tech document, you see that SEARCH_SEEDLIST_TIMEOUT is needed in miliseconds! So i had set it to 0.15 seconds and this is too less for activities, all other applications were ok. After reading the document i remembered setting this value and increased it to 15000 and voila the search builds perfectly and all errors are gone.
I learned again that i should read the documentation and that search/serverStatus does not validate the variables, it only checks that that the variable is present. Maybe this should be made as a feature request?
In the trace you see login data and that search can’t access the url, but not that the request timed out.