Install lifekeeper with MQ

1, Create two network card in VM
   Enabled in yast

2, Add in /etc/hosts
lk1:
192.168.3.170   lk1.site lk1
192.168.3.171   lk1.site
192.168.3.172   lk2
192.168.3.174   lk      #VIP

lk2:
192.168.3.172   lk2.site lk2
192.168.3.173   lk2.site
192.168.3.170   lk1
192.178.3.174   lk  #VIP

3, Install lifekeeper:
mount de.img /mnt/ -t iso9660 -o loop=/dev/loop0
cd /mnt
sh setup

? 安装程序首先会显示检测到的操作系统版本：
Your system appears to be running Red Hat Enterprise Linux <版本号 >
? 提示是否安装LifeKeeper Distribution Enabling Package for Red Hat软件包时选择“ Y ” :
The LifeKeeper Distribution Enabling Package for Red Hat will now be installed. This package is needed in order for LifeKeeper to run properly.
? 接着提示安装Java运行环境，选择“ Y ” :
You will need to install the Java Runtime Environment v1.4.1 on this system if you wish to administer LifeKeeper using the LifeKeeper GUI. You should ensure that the PATH variable in the /etc/default/LifeKeeper file contains the path to your java binary.
? 在提示是否创建SCSI设备节点时选择“ Y ”
Do you wish to create additional SCSI disk device nodes (/dev/sd*)and SCSI generic device nodes (/dev/sg*)y
? 在提示是否在启动文件中加入optionsscsi_mod max_scsi_luns=255时，选择“ N ”
? 对于提示是否安装IPS软件包时选择“ N ”
? 对于提示是否安装CCISS软件包时选择“ N ”
? 对于提示是否安装HADR时选择“ N ”
? 对于提示是否安装HANFS时选择“ N ”
? 最后是安装许可管理软件包，之后会询问是否在此时安装软件许可，回答“ n ”，
我们将在后面单独安装。


4. install rpm package:
rpm -ivh *.rpm
rpm -ivh steeleye-lkNAS-5.0.0-1.noarch.rpm

lk1:/home/jliu/pkg # rpm -qa|grep stee
steeleye-lkSuSE-6.1.1-2
steeleye-lkLIC-6.1.1-2
steeleye-lkIP-6.1.1-2
steeleye-lkMQS-6.2.1-1
steeleye-lk-6.1.1-2
steeleye-lkHLP-6.1.1-2
steeleye-lkMAN-6.1.1-2
steeleye-lkNAS-5.0.0-1
steeleye-lkGUI-6.1.0-5
steeleye-lkRAW-6.1.1-2

5, Start lk:
/opt/LifeKeeper/bin/lkstart
/opt/LifeKeeper/bin/lkGUIserver start ----Only run it in first time
/opt/LifeKeeper/bin/lkGUIapp  -----Start the GUI

6, Configure the resource in lk:
Refer to case3821/LifeKeeperforlinux.pdf   -IP
Refer to case3821/LKNAS.pdf                -NAS

7, Install the MQ
  Install all of package in    "WebSphere MQ for Linux x86-64 V6.0.1 - German English International Spanish French Italian Japanese Korean Portuguese Brazilian Chinese Simplified Chinese Traditional (C87RUML)"
rpm -ivh


8,First, locate the mq 6.0 software then upgrade to mq 6.0.2.3. Before you can install mq you will need to create user mqm and group mqm with user mqm being member of group mqm. Then run the crtMQ01.ksh script on one of the nodes in the cluster. This script must be run as root to create the queue manager. Next, run linkMQ01.ksh (should be run as
mqm) on the remaining nodes in the cluster to "link" the queue manager so that it will run on any node in the cluster. You will note in the scripts that we are creating separate data and log file systems for the queue manager (MQ01) and these should be on NAS mounts to emulate our environment.  When you are ready, we can discuss configuring the resources and creating hierarchies in LifeKeeper.  

9. when attempting to create an MQSeries resource in LifeKeeper, your team is encountering an error regarding no valid server connection channel found.  The queue manager (after being created using the “HA” crtmqm scripts ), must be manually started on the LK node you are trying to create the resource on.  It is important to note that the qmgr can not be started unless the data and log mounts are on the same node AND you must never start the qmgr if the data and log mounts are mounted on more than one node as this will cause corruption that will crash the queue manager.  With the queue manager running, when you go back and attempt to create the MQ resource in LK, it will find the default svrconn channel which you can choose and move forward in the resource creation process.  Also note that you will have to create and start a listener process for the queue manager and set the “control” parm for this listener to (QMGR) so that it starts and stops when the qmgr starts and stops.  During the LK setup process, you should elect NOT to have LK manage the listener.  If necessary, we could do a webex (or other type of web session) where I can walk your team thru the MQ and LK stuff they will need to configure to get a QMgr running and an MQ resource set up.

Manually run strmqm
/opt/mqm/bin/strmqm SANDMQ01

ADD following in qm.ini:
      mq1:/data/mqm_ha/mq01/data/qmgrs/MQ01 # vi qm.ini
Channels:
   MaxChannels=20
   MaxActiveChannels=100
TCP:
   Port=1414

Define listener:
mqm@mq1:/opt/mqm/bin> ./runmqsc MQ01
5724-H72 (C) Copyright IBM Corp. 1994, 2005.  ALL RIGHTS RESERVED.
Starting MQSC for queue manager MQ01.


define listener(mq01.listener) trptype(tcp) port(1414)
     1 : define listener(mq01.listener) trptype(tcp) port(1414)
AMQ8626: Webphere MQ listener created.
start listener(mq01.listener)
     2 : start listener(mq01.listener)
AMQ8021: Request to start WebSphere MQ Listener accepted.
end

DEFINE QLOCAL（QNAME） DEFPSIST（YES） REPLACE

dis queue(*)