ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » Installation Check List

Post new topic  Reply to topic
 Installation Check List « View previous topic :: View next topic » 
Author Message
JosephGramig
PostPosted: Thu Apr 03, 2008 10:10 am    Post subject: Installation Check List Reply with quote

Grand Master

Joined: 09 Feb 2006
Posts: 1244
Location: Gold Coast of Florida, USA

Here is a Re-post of an installation check list I've put together for those who don't want to use the Wizard.


  • Check the OS for the proper maintenance level
  • Create all groups and IDs (mqm, wmbadmin and db2 instance if this will be a full install)
  • Create the file systems for DB2, WMQ and WMB
  • Install DB2 (DB2 Run-Time Client V9.1 FP3)
  • Check DB2 for the proper maintenance level (fix 15 for DB2 8 (64bit). Or DB2 9 FP 3 64 bit))
  • Prereq xlC needs version 8.0.0.4 and above (DB2 V9)
  • Install WMQ (for Linux, please check for the proper order)
  • Apply maintenance to WMQ
  • Create the QMGR (check your parameters before creating the QMGR)
  • Check and update the mqs.ini and qm.ini files for correct and additional stanzas
  • Update the QMGR objects to the Company standard to secure it
  • Create the listener with the correct port (?)
  • Update the boot strap scripts to start and stop DB2 and WMQ (level 2)
  • Install all the WMB software (for AIX that is CM, Broker and UNS)
  • Apply maintenance to WMB
  • Configure the service ID's profile for WMB (wmb)
  • Update (cp /opt/IBM/mqsi/6.1/ODBC64/V5.2/odbc64.ini /var/mqsi/odbc/)
  • create the broker database
  • Test database connectivity and create/drop a table to verify
  • create the broker (check params)
  • create the CM (check params)
  • Update the /etc/config.conf file to write and roll the WMB runtime logs
  • Update the WMB logs directory to have the sticky bit for group ownership
  • Touch the WMB log file to create it with the correct ownership and permissions
  • Start the CM
  • Verify the CM log entries
  • Start the Broker
  • Verify the Broker log entries
  • create ACL - required for the Toolkit to connect
  • Connect a Toolkit to the CM -
    /opt/ibm/MessageBrokersToolkit/6.1/eclipse/eclipse
    com.ibm.etools.msgbroker.tooling.ide -DDomainAware=0
  • Create an execution group (optional)
  • IBM Installation Manager - update toolkit
  • Create a simple flow
  • Create any requirements of the simple flow (like queues)
  • Deploy the simple flow
  • Verify the deployment by checking the Broker runtime logs
  • Test the flow
  • Install Support Packs like the SaveQmgr


I've mix a couple of OS' here so you will need to sort out what applies to you. The maintenance levels and prereq's will have changed, so be sure you research the current ones (and prereq's for a dependent product could be higher).
_________________
Joseph
Administrator - IBM WebSphere MQ (WMQ) V6.0, IBM WebSphere Message Broker (WMB) V6.1 & V6.0
Solution Designer - WMQ V6.0
Solution Developer - WMB V6.1 & V6.0, WMQ V5.3


Last edited by JosephGramig on Wed Sep 17, 2008 3:21 am; edited 1 time in total
Back to top
View user's profile Send private message AIM Address
PeterPotkay
PostPosted: Fri Apr 04, 2008 11:55 am    Post subject: Reply with quote

Poobah

Joined: 15 May 2001
Posts: 7722

Thanks for posting this again Joseph.

Have you ever done a 6.* Broker on a UNIX system on a hardware cluster? I'm trying to figure out if there are any unique ID requirements so things will work the same as the Broker fails over from Node A to Node B.


I looked in the Info Center, the Installation Guide and Support Pack IC91 but havent found anything about requiring the UUIDs having to be the same for the mqm ID or for the WMB and DB2 Service Accounts between Node A and B. Will this be required?
_________________
Peter Potkay
Keep Calm and MQ On
Back to top
View user's profile Send private message
jefflowrey
PostPosted: Fri Apr 04, 2008 7:32 pm    Post subject: Reply with quote

Grand Poobah

Joined: 16 Oct 2002
Posts: 19981

PeterPotkay wrote:
I looked in the Info Center, the Installation Guide and Support Pack IC91 but havent found anything about requiring the UUIDs having to be the same for the mqm ID or for the WMB and DB2 Service Accounts between Node A and B. Will this be required?


It's a very good idea.
_________________
I am *not* the model of the modern major general.
Back to top
View user's profile Send private message
JosephGramig
PostPosted: Tue Aug 26, 2008 9:52 am    Post subject: Reply with quote

Grand Master

Joined: 09 Feb 2006
Posts: 1244
Location: Gold Coast of Florida, USA

Sorry for the late response, YES.

In general, all IDs and Groups that are on more then one machine should have the same UID and GID to avoid trouble.

In the case of HA, definitely because they will swing the mount point to the recovering machine.... so they must match...

AIX HACMP is managing this stuff for you.
Back to top
View user's profile Send private message AIM Address
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » Installation Check List
Jump to:  



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
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.