How to Install WebSphere MQv7.1 in Solaris 10

I had installedVirtualBoxin my Windows 7 and then importedOracle Solaris 10 VM for VirtualBox as Appliance. This is the prerequisite for the below Installation.

You can downloadIBM WebSphere MQ v7.1 for Solaris x86 64bit evaluation copy.Usually you need around 300 MB free for a Server Installation in /opt mount.

You have to Install Guest Additions for VirtualBox to enable shared folders between guest and host operating system which is required for transferring Installation files to Solaris 10 from Windows 7.

Once the shared folder is created and mapped to Windows 7 through Devices menu you can mount the shared folder in Solaris 10 using the below command

mount -F vboxfs <shared folder name> /mnt/shared

Solaris 10 introduces the concept of zones to the operating system. The main file system is known as the global zone. Within this zone, you can create one or more additional non-global zones. A zone that has its own self-contained file system (one that is not shared with that of the global zone) is known as a whole root non-global zone. A zone that shares part of its file system with the global zone is known as a sparse root non-global zone.

On Solaris 10, WebSphere MQ can be installed into the system’s global zone, or into a whole root non-global zone. You cannot install WebSphere MQ into a sparse root non-global zone. By default you will login to a Global Zone.

Solaris 10 zones – it’s a virtualization technology which allows you to create isolated and secure environments for running applications. For end-users these environments look just like separate abstract machines with Solaris 10 installed on them. Inside each zone, all the processes don’t see anything happening in all the other zones on a system. Isolation is done on such a level that processes of one zone can’t see or affect processes of any other zone.

You can list the zones in a Solaris machine by the below command
solaris# zoneadm list -vc

STEPS TO BE FOLLOWED FOR INSTALLATION

1. Create WebSphere MQ File Systems

The installation directory for the WebSphere MQ product code is /opt/mqm. Working data is stored in /var/mqm.

2. Create a file system for Product code

Install WebSphere MQ for Solaris in /opt/mqm.

**Creating file System in Solaris 10 is described in another blog which I will post the link

For installation purpose we will continue with Directory structures

3. Create a file system for the working Data

Before you install WebSphere MQ for Solaris, create and mount a file system called/var/mqm.

You can also create separate file systems for your log data (/var/mqm/log) and error files (/var/mqm/errors).

4. Set up and create the userid and Group

Both the user ID and the group ID must be set to mqm. The mqm user ID owns the directories and files that contain the resources associated with the product.

# groupadd mqm

# useradd -g staff -G mqm -s /bin/bash -d /export/home/mqm -m mqm

# passwd mqm

bash-3.2# passwd mqm

New Password:

passwd: The password must contain at least 1 numeric or special character(s).

Please try again

New Password:

Re-enter new Password:

passwd: password successfully changed for mqm

If you want to run administration commands, for example crtmqm (create queue manager) or strmqm (start queue manager), your user ID must be a member of the mqm group.

5. Create Project for Group mqm

If you are using Solaris 10, You must change the default resource limits for each zone WebSphere MQ will be installed in. To set new default limits for all users in the mqm group, set up a project for the mqm group in each zone.

To find out if you already have a project for the mqm group, log in as root and

enter the following command:

project -l

If you do not already have a group.mqm project defined, enter the following

command:

projadd -c "WebSphere MQ default settings" -K "process.max-file-descriptor=(basic,10000,deny)" -K "project.max-shm-memory=(priv,4GB,deny)" -K "project.max-shm-ids=(priv,1024,deny)" -K "project.max-sem-ids=(priv,1024,deny)" group.mqm

** It’s a smart idea to run pwck (passwd check) whenever you make a change to the /etc/passwd file (as when adding or changing a user). This program will identify any problems with the passwd file. If it doesn’t tell you anything, then you are in good shape.

6. Perform Kernel Configuration

Before installation, review the system's configuration. To do this type the following command:

sysdef -i

To change the values, add a set parameter = value line to the /etc/system file.

set shmsys:shminfo_shmmax = 4294967295

set shmsys:shminfo_shmseg = 1024

set shmmin:shminfo_shmmin = 1

set shmsys:shminfo_shmmni = 1024

set semsys:seminfo_semmni = 1024

set semsys:seminfo_semaem = 16384

set semsys:seminfo_semvmx = 32767

set semsys:seminfo_semmap = 1026

set semsys:seminfo_semmns = 16384

set semsys:seminfo_semmsl = 100

set semsys:seminfo_semopm = 100

set semsys:seminfo_semmnu = 2048

set semsys:seminfo_semume = 256

set msgsys:msginfo_msgmni = 50

set msgsys:msginfo_msgmap = 1026

set msgsys:msginfo_msgmax = 4096

set msgsys:msginfo_msgmnb = 4096

7. Increase the system soft limit for the number of file descriptors

**A file descriptor is an object that a process uses to read or write to an open file and open network sockets.Operating Systems place limits on the number of file descriptors that a process may open.

Solaris has a low default system soft limit for the number of file descriptors.

To avoid this problem you can increase the system soft limit for the number of file descriptors as follows:

Edit the /etc/system file

Change the value of the system soft limit to match the system hard limit (1024) by adding:

set rlim_fd_cur=1024

8. gunzip and untar the Installer

Execute the below commands from /opt/mqm

gunzip CI50XML.tar.Z

tar -xvf CI50XML.tar

9. Run the mqlicense.sh script to accept the license.

./mqlicense.sh -text_only

Press Enter to continue viewing the license agreement, or

enter "1" to accept the agreement, "2" to decline it, "3"

to print it, "4" to read non-IBM terms, or "99" to go back

to the previous screen.

1

Agreement accepted: Proceed with install.

10. Run the following command

pkgadd -d. (including the dot at the end shows current directory)

This displays the list of all packages

Select the option 'all'

bash-3.2# pkgadd -d.

The following packages are available:
1 mqm WebSphere MQ for Solaris
(x86_64) 7.1.0.0

Select package(s) you wish to process (or 'all' to process
all packages). (default: all) [?,??,q]: all

You do not appear to have a /var/mqm filesystem

mounted. It is recommended that you create and

mount separate /var/mqm and /var/mqm/log

filesystems before installation.

Continue installation? [y,n,q] : y

Package will be installed in "/opt/mqm"

Is this OK? [y,n,?,q] y

1) WebSphere MQ Server

2) Man pages

3) Sample programs

4) WebSphere MQ Client libraries (including Java, JMS and Web Services support)

5) IBM (c) Java runtime for Solaris(TM)

6) IBM (c) Global Security Kit for WebSphere MQ

7) WebSphere MQ Extended Transactional Client

8) Spanish message catalog

9) French message catalog

10) German message catalog

11) Japanese message catalog

12) Italian message catalog

13) Brazilian Portuguese message catalog

14) Traditional Chinese message catalog

15) Simplified Chinese message catalog

16) Korean message catalog

17) Russian message catalog

18) Hungarian message catalog

19) Polish message catalog

20) Czech message catalog

Enter options to be installed [1-20,all,q,?] 1, 2, 3, 4, 5, 6, 7

... Finally you will get this message and then all is well

Installation of <mqm> was successful.

11. To verify the WebSphere MQ Version

bash-3.2# pkginfo | grep -i mqm
application mqm WebSphere MQ for Solaris

Reference for the HA setup: click here