Installing WebSphere Message Broker 8 on Linux64bits

Uploaded the following files and unpacked them

Preparing the machine for installation

WebSphere Message Broker can be installed in any environment. WebSphereMessage Broker Explorer and WebSphere Message Broker Toolkit can beinstalled only in Windows 32-bit/64-bit and Linux 32-bit/64-bit operatingsystems. In addition to these, additional components such as WebSphereMessage Broker ODBC Database Extender can be installed.

Adding RedHat DVD as RepositoryWhen we try out a new linux OS its always a pain to download and install allthe software and add packages we needs on that. Its even worse if you don’thave an unlimited connection. But actually most of the software we need isalready there in the CD/DVD in which the operating system comes with. Sohow do we install from the DVD then rather than from the internet?For this you need to add the DVD as a repository so that rpm client picks upthe rpm from the DVD and wont go to internet for it.The Procedure and Files to be modified is a bit different for each OS so i willcover Red Hat Linux in this post.In RHEL the repo list is maintained in the folder /etc/yum.repos.d/ . So letscreate a new file in this directory , say lets call it rhel-cd.repo.The Contents of this file should be as follows:

12345

[rhel-cd]name=Red Hat Enterprise Linux $releasever - $basearch - CDbaseurl=file:///media/RHEL/Server/enabled=1gpgcheck=0

First line ([rhel-cd]) should be an unique value ie no two repo file should havethe same value or it will show a warning.

Name can be anything it is for the user to identify it when its shown though therpm interface.

Remove packagekit-media.repo.

Install 32-bit libraries

We are using Linux 64-bit operating system. Few of the WMB 8.0 componentsare 32-bit applications and needs 32-bit libraries. So it is important to installthese 32-bit libraries before starting installation.If your Linux Operating System is REDHAT - 64 bit Operating System, theninstall the required libraries as shown below.# yum install ld-linux.so.2# yum install libgcc_s.so.1

Installing WMQ 7.5

[root@localhost wmq75]# rpm -ivh MQSeriesRuntime-7.5.0-0.x86_64.rpmMQSeriesServer-7.5.0-0.x86_64.rpm MQSeriesJava-7.5.0-0.x86_64.rpmMQSeriesJRE-7.5.0-0.x86_64.rpmPreparing… ########################################### [100%]1:MQSeriesRuntime ###########################################[ 50%]2:MQSeriesServer ###########################################[100%]3:MQSeriesJRE ########################################### [ 50%]4:MQSeriesJava ###########################################[100%]

[root@localhost wmq75]# cat /etc/passwdmqm:x:495:502::/var/mqm:/bin/bash

A good idea is to test that we have access to both mq commands:

[mqm@localhost ~]$ dspmqverName: WebSphere MQVersion: 7.5.0.0Level: p000-L120604BuildType: IKAP – (Production)Platform: WebSphere MQ for Linux (x86-64 platform)Mode: 64-bitO/S: Linux 2.6.32-279.el6.x86_64InstName: Installation1InstDesc:InstPath: /opt/mqmDataPath: /var/mqmPrimary: NoMaxCmdLevel: 75

Install MQ Explorer

[root@localhost wmq75]# rpm -ivh MQSeriesExplorer-7.5.0-0.x86_64.rpmPreparing… ########################################### [100%]

1:MQSeriesExplorer ########################################### [100%]

Additional settings for installing WebSphere MQon Linux systemsAdditional settings for installing WebSphere® MQ on Linux systems

Installation DVD

Ensure that you have the correct 32-bit or 64-bit Server DVD. If you want toinstall the 64-bit Server, you must mount the 64-bit Server DVD.

Shell interpreter

Ensure that /bin/sh is a valid shell interpreter compatible with the Bourne shell,otherwise the post-installation configuration of WebSphere MQ does notcomplete successfully. If the shell was not installed with RPM, you might see aprerequisites failure of /bin/sh when you try to install WebSphere MQ. Thefailure is because the RPM tables do not recognize that a valid shellinterpreter is installed. If the failure occurs, you can reinstall the /bin/sh shellusing RPM, or specify the RPM option --nodeps to disable dependencychecking during installation of WebSphere MQ.

Kernel configuration

WebSphere MQ uses System V IPC resources, in particular shared memoryand semaphores.

The minimum configuration for WebSphere MQ for these resources is asfollows:kernel.msgmni = 1024kernel.shmmni = 4096kernel.shmall = 2097152kernel.shmmax = 268435456kernel.sem = 500 256000 250 1024fs.file-max = 524288

If you plan to run more than one queue manager of moderate size on theserver, increase fs.file-max.

To view the kernel parameters for your system, enter the following commands:cat /proc/sys/kernel/msgmnicat /proc/sys/kernel/shmmnicat /proc/sys/kernel/shmallcat /proc/sys/kernel/shmmaxcat /proc/sys/kernel/semcat /proc/sys/fs/file-max

Each of these commands returns the value of the corresponding kernelparameter. For example, cat /proc/sys/kernel/msgmni returns the valueforkernel.msgmni. If any of the values is less than the minimum value, youneed to increase it to at least the minimum value.

To add or alter these values, log on as a user with root authority. Open the file/etc/sysctl.conf with a text editor, then add or change the following entries to

the values shown:kernel.msgmni = 1024kernel.shmmni = 4096kernel.shmall = 2097152kernel.shmmax = 268435456kernel.sem = 500 256000 250 1024fs.file-max = 524288

Then save and close the file.

To load these sysctl values immediately, enter the command:sysctl -p

If you do not issue the sysctl -p command, the new values are loaded whenthe system is rebooted.

Maximum open files

If the system is heavily loaded, you might need to increase the maximumpossible number of open files. If your distribution supports the proc file systemyou can query the current limit by issuing the following command: cat/proc/sys/fs/file-max.

To report on the current maximum, and in-use, number of file descriptors foryour system, enter the following commands:/sbin/sysctl fs.file-max/sbin/sysctl fs.file-nr

If you are using a pluggable security module such as PAM (PluggableAuthentication Module), ensure that this module does not unduly restrict thenumber of open files for the mqm user. To report the maximum number ofopen file descriptors per process for the mqm user, login as the mqm user andenter:ulimit -n

For a standard WebSphere MQ queue manager, set the nofile value to 10240or more for the mqm user. To set the maximum number of open file descriptorsfor processes running under the mqm user, add the following to the file,/etc/security/limits.conf:mqm hard nofile 10240mqm soft nofile 10240

Maximum processes

A running WebSphere MQ queue manager consists of a number of threadprograms. Each connected application increases the number of threadsrunning in the queue manager processes. It is normal for an operating systemto limit the maximum number of processes which a user runs. The limitprevents operating system failures due to an individual user or subsystemcreating too many processes. You must ensure that the maximum number ofprocesses which the mqm user is allowed to run is sufficient. The number ofprocesses must include the number of channels and applications whichconnect to the queue manager.

The following calculation is useful when determining the number of processesfor the mqm user:maximum processes = 2048 + maximum WebSphere MQ connections +maximum WebSphere MQ channels

You can use the PAM_limits security module to control the number ofprocesses which users run. You can configure the maximum number ofprocesses for themqm user as follows.mqm hard nproc 4096mqm soft nproc 4096

For more details on how to configure the PAM_limits security module type:man limits.conf

Configuring sudo AccessLog in to the system as the root user.

Run the nano to edit the /etc/sudoers file. This file defines the policiesapplied by the sudo command.# nano /etc/sudoers

Find the lines in the file that grant sudo access to users in the group mqmwhen enabled.## Allows people in group wheel to run all commands

# %mqm ALL=(ALL) ALL

Remove the comment character (#) at the start of the second line. Thisenables the configuration option.Save your changes and exit the editor.Add the user you created to the mqm group using the usermod command.# usermod -aG mqm USERNAME ---> mqserver

Test that the updated configuration allows the user you created to runcommands using sudo.Use the su to switch to the new user account that you created.# su USERNAME -

Use the groups to verify that the user is in the mqm group.$ groups

USERNAME mqm

Use the sudo command to run the whoami command. As this is the first timeyou have run a command using sudo from this user account the bannermessage will be displayed. You will be also be prompted to enter thepassword for the user account.$ sudo whoami

Running MQ Explorer

Logout - login

Issue the mqsiprofile command:

. install_dir/bin/mqsiprofile

You must include the period and space preceding the location for thisinvocation to work correctly. Add this command to your login profile if you wantit to be run at the start of every session.

This command accesses additional scripts that you have copied to thecommon/profiles directory, therefore the environment is initialized for runtimecomponents and other resources such as databases.

OK, lets edit .bashrc of USERNAME as follows:

# User specific aliases and functions#load MQ environment. /opt/mqm/bin/setmqenv -s

#Load MQSI (WMB) environment. /opt/ibm/mqsi/8.0.0.1//bin/mqsiprofile

I use FREENX to connect to my Linux Server’s Gnome Desktop.Anyway, however you connect to your dekstop you can run MQ Explorer ifinstalled using the RPM by running to /opt/mqm/bin/MQExplorer

Installing WebSphere Message Broker 8

Then ran chmod 750 on WMB install folders so I can run installersudo ./setupLinux64.bin

USERNAME@localhost messagebroker_ia_runtime1]# sudo ./setuplinuxx64Preparing to install…Extracting the JRE from the installer archive…Unpacking the JRE…Extracting the installation resources from the installer archive…Configuring the installer for this system’s environment…Launching installer…Graphical installers are not supported by the VM. The console mode will be usedinstead…===============================================================================Select language—————1- Deutsch->2- English3- Español4- Français5- Italiano6- Português (Brasil)Select language by number:

Follow instructions, I chose to install on

Default Install Folder: /opt/ibm/mqsi/8.0.0.1[User]/opt/ibm/mqsi/8.0.0.1/IBM_WebSphere_Message_Broker_InstallLog.log[Debug] /var/mqsi/WMB_8001_installer_debug.logmqbrkrs:x:501:

[root@localhost wmb8]# cat /etc/groupYou can see the new group has been created.We then continue on and the installer completes.

We need to add USERNAME and mqm to the mqbrkrs group.

Logout - login

Installing WebSphere Message Broker Explorer in consolemode on LinuxYou can install WebSphere® Message Broker Explorer using the installationwizard in console mode on Windows and Linux.Use the following steps to install the WebSphere Message Broker Explorerusing the console mode on Linux. If you encounter any problems during theinstallation process, you can view the install logMBExplorer_install.log.Typethe following command on a command line to run a console install:sudo<cd_rom>/MBExplorer/install.bin -i console1. Select the language that you want to use for the installation process by

typing the number next to the language and press Enter. The installeruses the term "locale" rather than "language". Alternatively, press Enter toaccept the default language.

2. Read the software license agreement and type 1 to accept the terms ofthe license. Press Enter.

3. Type the name of the product installation directory for the WebSphereMessage Broker Explorerand press Enter. Alternatively, press Enter toaccept the default location. The default installation directory for theWebSphere Message Broker Explorer on Linux systemsis/opt/IBM/MBExplorer. If the product installation directory already existsbecause you have previously installed the WebSphere Message BrokerExplorer, you can either refresh the existing installation or select a newproduct directory.

4. Confirm that the install location is correct, and press Enter to continue.5. Read the Pre-Installation Summary information and press Enter to install

the WebSphere Message Broker Explorer. Wait while the files areinstalled.

6. On the Installation Complete panel, press Enter to exit the consoleinstaller.

You can now use the WebSphere Message Broker Explorer. To use theWebSphere Message Broker Explorer you must start the WebSphere MQExplorer. To start the WebSphere MQ Explorer, open a command shell inwhich the mqsiprofile command has not been run and enter thestrmqcfgcommand, or run /usr/bin/strmqcfg.

Websphere Message Broker – Node for log4jInstallation procedure:1) Unzip the iam3.zip file and extract these three jar files:

• Log4jLoggingNode_v1.2.jar• jakarta-oro-2.0.4.jar• log4j-1.2.8.jar

2) Copy all three files to the /var/mqsi/shared-classes for each broker.

In addition copy the Log4jLoggingNode_v1.2.jar file to/opt/ibm/mqsi/8.0.1/jplugin.

3) Ensure that the broker has access to the files. For example, on Unixsystems, you may want make these files group- and world-readable (via achmod 755 command).

Installing Message Broker ToolkitYou really do need MBTK installed. Both for development and administrationpurposes.

Remove packagekit-media.repo.

# sudo yum install libstdc++.so.6# sudo yum install gtk2.i686# sudo yum install libXtst.i686# sudo yum install xulrunner.i686

Unzip and untar the the three install disk sets.I presume you are using a shell within g an X11 session

if running ./installToolkit.sh does nothing on REDHAT, then run Nothing to do[USERNAME@localhost disk1]# sudo ./installToolkit.sh

Websphere Message Broker – Node for log4j

Installation procedure:

1) Unzip the iam3.zip file and extract the Log4jLoggingPlugin_v1.1.zipfile.

2) Unzip this file into the /opt/ibm/WMBT800/plugins.

3) You need to restart your toolkit in order to make the new node show upin the palette ( under Construction ). If this does not work it might benecessary to restart the toolkit a second time or restart is with the – cleanoption.

Install Firefox 211. Download the product

You can download the latest version of Firefox for free from here:

http://www.firefox64bit.com/firefox.en-US.linux-x86_64.tar.bz2

2. Uninstall any old versions

If you have any previous versions of Firefox, then uninstall thembefore you install the new version. Don't worry about losing yoursettings and extensions, they will be saved and transferred to the newversion. Technically there is no need need to uninstall older versionsas Firefox will write over old versions and retain your settings. Howeverbased on feedback from my subscribers there appears to be fewerproblems if you uninstall first.

There is no need to uninstall Internet Explorer. In fact, it's surprisinglydifficult to do so as it is so closely integrated into the Windowsoperating system. Just don't do it. Besides you may need it to viewsome non standards compliant web sites.

3. Install Firefox

# tar xjvf firefox.en-US.linux-x86_64.tar.bz2

# mv firefox/ /usr/lib64/firefox

# alternatives –install /usr/bin/firefox firefox /usr/lib64/firefox/firefox 1

# alternatives –config firefox

There are 1 program which provide 'firefox'.

Selection Command———————————————–

1 /usr/lib64/firefox/firefox

Enter to keep the current selection[+], or type selection number: 1

Configuring the web user interface serverTo enable access to broker resources through the web user interface,configure the WebSphere® Message Broker web user interface server.

To configure a web user interface server, complete the following steps:Configure the properties relating to the HTTP or HTTPS port to be used,and enable the web user interface server, by using the WebSphereMessage Broker Explorer or the mqsichangeproperties command.If youare using the WebSphere Message Broker Explorer, complete thefollowing steps:

In the MQ Explorer - Navigator view, navigate to IBMWebSphere MQ > Brokers, right-click your broker name,and select Properties.Select the WebAdmin tab.Enable the web user interface and set the port to use for yourchosen protocol.

If you are using HTTP, set Enabled to true, set Enabled SSL to false, andenter a value for the HTTP Port.If you are using HTTPS, set Enabled to true, set Enabled SSL to true, andenter a value for the HTTPS Port.To set additional parameters for the HTTPS protocol, you must use thecommand-line interface. For more information, see Parameter values for thewebadmin component.

To review your changes, click Apply; to close the Propertieswindow, click OK. You can also confirm the changes byexamining recent Change Notification entries in theAdministration Log view.

If you are using the mqsichangeproperties command, completethe following steps:Configure the properties relating to the HTTP or HTTPS port tobe used.

If you are using HTTP, run the following command:mqsichangeproperties brokerName -b webadmin -oHTTPConnector -n port -v portValue

brokerName is the name of your brokerportValue is the HTTP port value that you want to use for the

web user interface

If you are using HTTPS, run the following command:mqsichangeproperties brokerName-b webadmin -o HTTPSConnector -n port,keystoreFile,keystorePass-v portValue,fileName,password

brokerName is the name of your broker.portValue is the HTTPS port value that you want to use for the web user

interface.fileName is your keystore file.password is the password for the keystore file.

For more information about the properties that can be set for theHTTPConnector and HTTPSConnector objects, see Parameter values for the

webadmin component.Confirm that the properties are set correctly.

If you are using HTTP, run the following command:mqsireportproperties brokerName-b webadmin -o HTTPConnector -a

If you are using HTTPS, run the followingcommand:

mqsireportproperties brokerName-b webadmin -o HTTPSConnector -a

This command produces a response similar to thisexample (for the HTTPConnector):

HTTPConnectoruuid='HTTPConnector'address=''port='7054'allowTrace=''maxPostSize=''acceptCount=''compressableMimeTypes=''compression=''connectionLinger=''connectionTimeout=''maxHttpHeaderSize=''maxKeepAliveRequests=''maxThreads=''minSpareThreads=''noCompressionUserAgents='restrictedUserAgents=''socketBuffer=''tcpNoDelay=''enableLookups='false'

Enable the web user interface server for the broker:To enable the web user interface, and to use HTTP

as the communication protocol between the brokerand the web user interface server, run the followingcommand on a WebSphere Message Brokercommand line, where brokerName is the name of yourbroker:

mqsichangeproperties brokerName-b webadmin -o server -n enabled,enableSSL -v true,false

To enable the web user interface, and to useHTTPS as the protocol for communication betweenthe broker and the web user interface server, run thefollowing command:

mqsichangeproperties brokerName-b webadmin -o server -n enabled,enableSSL -v true,trueFor more information about the properties of the web user interface server,see Parameter values for the webadmin component.

Confirm that the web user interface component isenabled by running the mqsireportproperties command, asshown in the following example.

mqsireportproperties brokerName -b webadmin -o server -aThis command produces a response similar to this

example:server=''uuid='server'enabled='true'enableSSL='true'

To ensure that the changes take effect, restart the broker. For moreinformation, see Starting and stopping a broker.

Create a web user account by using the mqsiwebuseradmincommand. For more information, see Managing web user accounts.

Enabling and disabling the web user interfaceYou can enable and disable the web user interface by using themqsichangeproperties command.

All new brokers that are created in WebSphere Message Broker Version8.0.0.1 or later have the web user interface assigned to port 4414, which isenabled by default. As a result, the web user interface is enabledautomatically when a new broker is created.

You can disable the web user interface by using the mqsichangepropertiescommand to change the enabled property of the webadmin component tofalse; by default, it is set to true. For example:mqsichangeproperties MB8BROKER -b webadmin -o server -n enabled -vfalse

You can change this property either when the broker is stopped or while it isrunning. If you make changes while the broker is running, they take effectwhen the broker is restarted.

You can also change the port number for the web user interface by using themqsichangeproperties command; for example:mqsichangeproperties MB8BROKER -b webadmin -o HTTP[S]Connector-n port -v new port

You can change this property only when the broker is running, and the changetakes effect when the broker is restarted. Alternatively, you can use theMessage Broker Explorer to enable or disable the web user interface, and tochange the port number to which it is assigned.

For brokers that were created in WebSphere Message Broker Version8.0.0.0, the web user interface is enabled in V8.0.0.1 only if you enabled it inV8.0.0.0. If you created brokers in V8.0.0.0 and did not enable the web userinterface, it remains disabled for those brokers in V8.0.0.1. The web userinterface is not enabled automatically for brokers that are migrated fromWebSphere Message Broker Version 6.1 or V7 to V8.0.0.1.

Accessing the web user interfaceYou can access broker resources by logging on to the web user interface.

All new brokers that are created in WebSphere Message Broker Version8.0.0.1 or later have the web user interface assigned to port 4414, which isenabled by default. As a result, the web user interface is enabledautomatically when a new broker is created.

You can disable and enable the web user interface by using themqsichangeproperties command to change the enabledproperty of thewebadmin component to false or true. For more information, see Enabling anddisabling the web user interface.

When you have configured a web user interface server to be used byWebSphere Message Broker, open the web user interface in a web browser:

o Use the following URL:protocol://serverAddress:port/where:protocol has the value http or https, depending on whetheryou are using an HTTP or an HTTPS connector objecto serverAddress identifies the web user interface server addressspecified for the HTTP or HTTPS connector object; for example127.0.0.1o port identifies the port that you specified for the HTTP orHTTPS connector object in the preceding steps (by default the portis 4414)

Enter your user ID and password and then click Log in to log on to thesystem. Users have permissions granted to them according to their role, soadministrators and web users can have different access to brokerresources based on their role. The web interface is tailored to your role, soyou see only the options that are available to you based on thepermissions that have been assigned to your role. For more informationabout roles, see Role-based security. For information about creating useraccounts, see Managing web user accounts.

A window opens, in which you can view and administer your brokerresources. The Navigator view is displayed on the left side of the window(unless it has been hidden), and the content that is displayed on the rightside of the window varies according to the resource that has been selectedin the Navigator view.