ubuntu changing dash to bash

$ sudo update-alternatives --install /bin/sh sh /bin/bash 100
update-alternatives: using /bin/bash to provide /bin/sh (sh) in auto mode.

$ sudo update-alternatives --install /bin/sh sh /bin/dash 200
update-alternatives: using /bin/dash to provide /bin/sh (sh) in auto mode.

$ sudo update-alternatives --config sh
There are 2 choices for the alternative sh (providing /bin/sh).

Selection Path Priority Status
------------------------------------------------------------
* 0 /bin/dash 2 auto mode
1 /bin/bash 1 manual mode
2 /bin/dash 2 manual mode

Press enter to keep the current choice[*], or type selection number: 1
update-alternatives: using /bin/bash to provide /bin/sh (sh) in manual mode.

Advertisements

WebSphere Application Server Script Library

I found some pre-defined jython scripts in the WAS installed dir I didn’t know existed… 😉

/scriptLibraries/

E.g. performance tunning.

$ cd /scriptLibraries/perfTuning/V70


$ ../../../bin/wsadmin.sh -f applyPerfTuningTemplate.py -clusterName MDM -templateFile ./peak.props -username -password
WASX7209I: Connected to process "dmgr" on node centos6i386CellManager01 using SOAP connector; The type of process is: DeploymentManager
WASX7303I: The following options are passed to the scripting environment and are available as arguments that are stored in the argv variable: "[-clusterName, MDM, -templateFile, ./peak.props]"

Completed parsing parameters...
templateFile - ./peak.props
clusterName - MDM

Resolving cluster targets...

Applying server level tuning parameters for server:
----------------------------------------------------------------------
Cell: centos6i386Cell01 Type: DISTRIBUTED
Node: centos6i386Node01 Platform: linux
Version: 7.0.0.21
Server: mdmsrv01 Type: APPLICATION_SERVER
----------------------------------------------------------------------

Applying tuning parameters using property based configuration...
Log File : /usr/IBM/WebSphere/AppServer/v70/profiles/AppSrv01/logs/perfTuning.log
Template File : /usr/IBM/WebSphere/AppServer/v70/scriptLibraries/perfTuning/V70/./peak.props
NOTE: Please consult the report.log file to review results of property
based configuration.

Applying additional tuning parameters via normal wsadmin processing...

Applying Datasource tuning parameters to Default Datasource

Applying Datasource tuning parameters to DefaultEJBTimerDataSource

Applying Datasource tuning parameters to PLANTSDB

Applying Datasource tuning parameters to PLANTSDBNonJTA

Server level tuning complete!

Applying server level tuning parameters for server:
----------------------------------------------------------------------
Cell: centos6i386Cell01 Type: DISTRIBUTED
Node: centos6i386Node01 Platform: linux
Version: 7.0.0.21
Server: mdmsrv02 Type: APPLICATION_SERVER
----------------------------------------------------------------------

Applying tuning parameters using property based configuration...
Log File : /usr/IBM/WebSphere/AppServer/v70/profiles/AppSrv01/logs/perfTuning.log
Template File : /usr/IBM/WebSphere/AppServer/v70/scriptLibraries/perfTuning/V70/./peak.props
NOTE: Please consult the report.log file to review results of property
based configuration.

Applying additional tuning parameters via normal wsadmin processing...

Applying Datasource tuning parameters to Default Datasource

Applying Datasource tuning parameters to DefaultEJBTimerDataSource

Applying Datasource tuning parameters to PLANTSDB

Applying Datasource tuning parameters to PLANTSDBNonJTA

Server level tuning complete!

Applying cluster level tuning parameters for cluster:
----------------------------------------------------------------------
Cluster: MDM Type: APPLICATION_SERVER
----------------------------------------------------------------------

Applying Datasource tuning parameters to Default Datasource

Applying Datasource tuning parameters to PLANTSDB

Applying Datasource tuning parameters to PLANTSDBNonJTA

Cluster level tuning complete!

Saving the configuration changes...
NOTE: Server may require restart for all tuning changes to take effect.
Script completed!

Plenty of other goodies in here.

DB2 V9.5 Fedora 16 x86_64

Fedora 16
# yum install libaio* libaio*.i686 compat* compat*.i686 nfs-utils

Ubuntu 12.04
# sudo apt-get install ia32-libs libaio-dev libaio1 nfs-common

# groupadd -g 2000 db2iadm1
# groupadd -g 2001 db2fadm1
# groupadd -g 2002 dasadm1

# useradd -u 2001 -g db2iadm1 -m -d /db2home/db2inst1 db2inst1
# useradd -u 2002 -g db2fadm1 -m -d /db2home/db2fenc1 db2fenc1
# useradd -u 2003 -g dasadm1 -m -d /home/dasusr1 dasusr1

# passwd db2inst1
# passwd db2fenc1
# passwd dasusr1

IBM WebSphere Application Server v7 on Fedora 16

First uncomment ip6 out of /etc/hosts and add your hostname/domainname

# cat /etc/hosts
127.0.0.1   arbitrary arbitrary.some.network.com localhost localhost.localdomain localhost4 localhost4.localdomain4

#::1         localhost localhost.localdomain localhost6 localhost6.localdomain6

 

Install the following rpms

# yum install compat-* ksh gtk2 gtk2-engines libXp libXmu libXtst pam rpm-build elfutils elfutils-libs libXft

Link ksh, this is for IHS

 # ln -s /bin/ksh /usr/bin/ksh

Enable verbose GC logging in WebSphere

Application servers > WebSphere_Portal > Process Definition > Java Virtual Machine

Generic JVM arguments

-Xverbosegclog:${SERVER_LOG_ROOT}/verbosegc.log,7,5000

 

-Xverbosegclog:[DIR_PATH][FILE_NAME],X,Y
Where:

[DIR_PATH] is the directory where the file should be written
[FILE_NAME] is the name of the file to write the logging to
X is the number of files to write to
Y is the number of GC cycles a file should contain