|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
 |
|
Installation Notes for MQ 7;WMB 6.1; Oracle XE Server/Client |
« View previous topic :: View next topic » |
Author |
Message
|
eugen |
Posted: Sun Jun 19, 2011 10:26 pm Post subject: Installation Notes for MQ 7;WMB 6.1; Oracle XE Server/Client |
|
|
Novice
Joined: 28 Dec 2010 Posts: 22
|
Hey! This is probably well known by A LOT of people, but when I faced this problem the very first time, I haven't found any good info. Suppose you want to start with the broker and need a fast way to install it so that you could develop and start learning stuff.
This is the probably a "dirty" way to do it (I am more then sure that good admins will do a much better job), but it will get you started. This is done in a MoinMoin way (wiki engine - server) that I am running locally.
''' '''' --> means highlighted text
{{{ }}} --> means actual code to run.
'''Install CentOS 64 bit ''' (default user to be created is mqbrkr)
'''Install Oracle XE Server'''
{{{
rpm -ivf oracle-xe-univ-10.2.0.1-1.0.i386.rpm
}}}
'''Create the database user''':
{{{
/etc/init.d/oracle-xe configure
}}}
Port 8080
Listener Port 1521
Choose a password
Go to http://<SERVER_HOST>:8080/apex, log in as "sys" and the password from previous step.
Add a user : OracleUser
'''Install Oracle XE Client'''
{{{
rpm -ivf oracle-xe-client-10.2.0.1-1.0.i386.rpm
}}}
'''Edit iptables'''
{{{
gedit /etc/sysconfig/iptables
}}}
-A RH-Firewall-1-INPUT -m state --state NEW -m tcp -p tcp --dport 8080 -j ACCEPT
-A RH-Firewall-1-INPUT -m state --state NEW -m tcp -p tcp --dport 1521 -j ACCEPT
-A RH-Firewall-1-INPUT -m state --state NEW -m tcp -p tcp --dport 1440 -j ACCEPT
-A RH-Firewall-1-INPUT -m state --state NEW -m tcp -p tcp --dport 2440 -j ACCEPT
''' restart iptables'''
{{{
/etc/init.d/iptables restart
}}}
Get the '''latest release of MQ7''' (mine is 7.0.1.3) - unzip it to a random folder, further called $MQ7_Folder
{{{
/usr/sbin/setenfornce 0
}}}
{{{
yum install compat-libstdc++-33.x86_64
yum install libstdc++.so.5
}}}
{{{
yum install libXmu.so.6
}}}
'''Create user mqm and group mqm'''
{{{
cd $MQ7_Folder
}}}
{{{
./mqlincence.sh (accept the licence)
}}}
'''Install WMQ7'''
(the order of files is important plz do install them in the same order as here)
{{{
rpm -ivf MQSeriesRuntimeXXXXX
rpm -ivf MQSeriesServerXXXX
rpm -ivf MQSeriesSDKXXXXX
rpm -ivf MQSeriesJavaXXX
rpm -ivf MQSeriesClientXXXX
rpm -ivf MQSeriesJREXXX
rpm -ivf MQSeriesEclipseSDK33
rpm -ivf MQSeriesConfigXXXX
rpm -ivf MQSeriesManXXXXX
}}}
'''mqbrkr to mqm group'''
{{{
/usr/sbin/usermod -a -G mqm mqbrkr
}}}
'''Reboot'''
'''Test WMQ Instalattion'''
Display Version:
{{{
dspmqver
}}}
{{{
crtmqm TestQueueManager
}}}
{{{
crtmqm TestQueueManager
}}}
{{{
strmqm TestQueueManager
}}}
{{{
endmqm TestQueueManager
}}}
{{{
dltmqm TestQueueManager
}}}
'''Create group mqbrkrs'''
Put mqbrkr in mqbrkrs group
{{{
/usr/sbin/usermod -a -G mqbrkrs mqbrkr
}}}
'''Install WMB 6.1.0.9'''
{{{
./setulinuxx64 -console
}}}
{{{
chown -R mqbrkr:mqbrkrs /opt/ibm/mqsi
}}}
'''Play with the brokers database'''
{{{
cp /opt/ibm/mqsi/6.1/ODBC32/V5.3/odbc64.ini /home/mqbrkr/
}}}
{{{
chown mqm:mqbrkrs /home/mqbrkr/odbc64.ini
}}}
{{{
chown mqbrkr:mqbrkrs /usr/lib/oracle
}}}
'''Edit Profile'''
{{{
gedit /opt/ibm/mqsi/6.1/bin/mqsiprofile
}}}
Add these lines:
{{{
export ODBCINI=/home/mqbrkr/odbc32.ini
LD_LIBRARY_PATH=/usr/lib/oracle/xe/app/oracle/product/10.2.0/client/lib/:${LD_LIBRARY_PATH}
LD_LIBRARY_PATH=/opt/ibm/mqsi/6.1/ODBC32/V5.3/lib/:${LD_LIBRARY_PATH}
LANG=en_US.utf-8
LC_ALL=en_US.utf-8
export MQSI_THREAD_STACK_SIZE=20000000
export _JAVA_OPTIONS=Xmso1048576
}}}
'''Configure odbc64.in'''
{{{
gedit /home/mqbrkr/odbc64.ini
}}}
Add these lines:
{{{
[ODBC]
;# To turn on ODBC trace set Trace=1
Trace=1
TraceOptions=3
TraceFile=/opt/ibm/mqsi/6.1/logs/odbctrace64.out
TraceDll=/opt/ibm/mqsi/6.1/ODBC64/V5.3/lib/odbctrac.so
InstallDir=/opt/ibm/mqsi/6.1/ODBC64/V5.3
UseCursorLib=0
IANAAppCodePage=4
UNICODE=UTF-8
[WMBDB]
Driver=/opt/ibm/mqsi/6.1/ODBC64/V5.3/lib/UKor23.so
Description=DataDirect 5.3 64bit Oracle Wire Protocol
HostName=192.168.1.125
PortNumber=1521
SID=xe
CatalogOptions=0
EnableStaticCursorsForLongData=0
ApplicationUsingThreads=1
EnableDescribeParam=1
OptimizePrepare=1
WorkArounds=536870912
ProcedureRetResults=1
ColumnSizeAsCharacter=17
}}}
{{{
mkdir /opt/ibm/mqsi/6.1/logs
}}}
{{{
chown -R mqbrkr:mqbrkrs /opt/ibm/mqsi/6.1/logs
}}}
{{{
gedit /home/mqbrkrs .bash_profile
}}}
Add this line (without quotes) :
". /opt/ibm/mqsi/6.1/bin/./mqsiprofile"
{{{
touch /opt/ibm/mqsi/6.1/logs/broker.log
}}}
{{{
chown root:mqbrkrs /opt/ibm/mqsi/6.1/logs/broker.log
}}}
{{{
chmod 640 /opt/ibm/mqsi/6.1/logs/broker.log
}}}
'''Create Queue mamanger'''
{{{
crtmqm -u WMBQM.DLQ WMBQM
crtmqm -u QueueManagerV.DLQ QueueManagerV
}}}
'''Start Queue Manageer'''
{{{
strmqm WMBQM
strmqm QueueManagerV
}}}
{{{
runmqsc QueueManagerV
DEFINE LISTENER ( LISTENER ) TRPTYPE ( TCP ) PORT ( 1440 )
DEFINE CHANNEL ( CHANNEL1 ) CHLTYPE ( SVRCONN ) SSLCAUTH ( OPTIONAL )
START LISTENER ( LISTENER )
START CHANNEL ( CHANNEL1 )
}}}
'''Create UserName Server'''
{{{
mqsicreateusernameserver -i mqbrkr -a mqbrkr -q WMBQM
}}}
'''Create Configuration manager'''
{{{
mqsicreateconfigmgr cmV -i mqbrkr -a mqbrkr -q QueueManagerV -s WMBQM
}}}
'''Create the actual broker'''
{{{
mqsicreatebroker brokerV -i mqbrkr -a bluered -q QueueManagerV -n WMBDB -u OracleUser -p bluered -s WMBQM
}}}
I use this on a Virtual Machine, so every time I start it up I need a way to fire up the broker. I use a small script for that:
Put this in a WMBStartUp.sh :
#! /bin/sh
mqsistart cmV
mqsistart brokerV
echo "START LISTENER ( LISTENER )" | runmqsc QueueManagerV
echo "START CHANNEL ( CHANNEL1 )" | runmqsc QueueManagerV
Hopefully it will work. It did for me
Let me know if you have any issues, will try to help if I can.
Cheers,
Eugene. |
|
Back to top |
|
 |
smdavies99 |
Posted: Mon Jun 20, 2011 12:01 am Post subject: |
|
|
 Jedi Council
Joined: 10 Feb 2003 Posts: 6076 Location: Somewhere over the Rainbow this side of Never-never land.
|
A few points.
Why don't you use yum to install the WMQ RPM's. Then the wmq dependencies (ie the missing rpm's) will be automatically installed.
Then you could create a ym repository with the WMQ base kit and the fix pack rpms and then install both the base and fixpack in one operation.
you can increase the reusability by putting a lot of the commands into a script. This is especially true for the WMQ Queue Manager setup. I have a script that sets up my broker QMGRS including the Listeners etc.
Lastly, you have missed the bit in the WMQ docs about setting the Linux Kernel Params. _________________ WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
Back to top |
|
 |
eugen |
Posted: Mon Jun 20, 2011 12:29 am Post subject: |
|
|
Novice
Joined: 28 Dec 2010 Posts: 22
|
Yup, every single point makes sense.
1. Install WMQ RPM's - makes sense, slipped from me probably
2. Yum repository - didn't even had that in mind, but good point.
3. I did not want to include commands into one script, I like to be verbose.
4. Linux Kernel Params - will have to read on those..
Thx for the review! |
|
Back to top |
|
 |
smdavies99 |
Posted: Mon Jun 20, 2011 4:20 am Post subject: |
|
|
 Jedi Council
Joined: 10 Feb 2003 Posts: 6076 Location: Somewhere over the Rainbow this side of Never-never land.
|
eugen wrote: |
3. I did not want to include commands into one script, I like to be verbose.
|
The more verbose you are the more chance you have of making mistakes.
Consider these points.
is the procedure Audiable
is it repeatable with the minimum change to make mistaked or even miss critical steps out.
is it measurable?
your 'verbose' process would fail my Installability test. the FOSS ./make configure ./make;./make install type of process would as well.
The place for verbosity (IMHO) is inside the scripts that you put together to make the 'Ease of Use' criteria much higher.
Two last points
1)you could add is to build the CentOS system using a kickstart file. This will improve the consistency.
With careful post install scripting you could save a lot of time in the long run.
2) look at adding a 'user' section to the syslog.conf. Set the target output directory to be one that the broker admin can read the wmbevent.log file. On many Linux systems, the /var/log/messages file is not world readable. How will the broker admins use it? _________________ WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
Back to top |
|
 |
lancelotlinc |
Posted: Mon Jun 20, 2011 4:29 am Post subject: |
|
|
 Jedi Knight
Joined: 22 Mar 2010 Posts: 4941 Location: Bloomington, IL USA
|
|
Back to top |
|
 |
|
|
 |
|
Page 1 of 1 |
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|
|
|