I often install IBM Connections on localised operating systems, so normally DB2 control center get started with a non-english language.
Interface language in DB2 control center can be changed through environment variable DB2LANG. After setting DB2LANG=EN and restart db2cc i get a english interface.
Your email address will not be published. Required fields are marked with *
Today i read a question in the IBM Connections Forum about setting the EMPLOYEE_EXTENDED role to all users in a Connections deployment.
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.
yum install readline-static gcc make
tar -xvzf rlwrap-0.41.tar.gz
cd rlwrap-0.41
./configure
make
make install
rlwrap -r /opt/IBM/WebSphere/AppServer/profiles/Dmgr01/bin/wsadmin.sh -lang jython -username wasadmin -password password
rlwrap -r db2
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'
After skripting jdbc and j2ee on WebSphere i was interested to fasten the DB2 configuration after a Connections installation.
There are two ways to get valid source xml-Files for automatic maintenance in DB2. I use automatic maintenance, because i can set a maximum backup time and how many dumps of one database should be stored. DB2 deletes old backups (which i have in a filebackup each night) automatically.
You can’t script this settings directly,
IBM
provides
two system calls for this: sysproc.automaint_set_policyfile
and sysproc.automaint_set_policy.
I use the file variant here, because i think it easier to handle files than blob content.