Part 1 – Bill of Materials- IBM JMS Interface Development IBM FileNet 5.5.x Workflow-3


IBM JMS Interface DevelopmentIBM Certification Exams Part 1 – Bill of Materials- IBM JMS Interface Development IBM FileNet 5.5.x Workflow-3
0 Comments

Listing 3-1The installation list of IBM MQ Series 9.2.5.0 components

Figure 3-12The current root User file limits are displayed as FAIL

The current root User limits need to be increased!

nofile (-Hn) 4096 files

and nofile (-Sn) 1024 files

These two limits need to be increased to 10240.

The root user limits can be changed as follows:

vi /root/.bashrc

ulimit -u unlimited

Also, the settings in /etc/security/limits.conf need to be edited.

Log in to the computer as the root user or as a user with sudo permissions.

Go to the /etc/security directory.

Open the limits.conf file for editing.

Add the following lines to the file:

@root soft nofile 10240

@root hard nofile 16384

* soft nofile 10240

* hard nofile 16384

Save and close the file.

Restart the computer for the changes to take effect.

Figure 3-13The /etc/security/limits.conf file is edited to fix the Limits FAIL

NoteAfter changing the limits, the ecmukdemo6 system requires a reboot.

Set the MQ Series as the primary installation:

cd /opt/mqm/bin

/opt/mqm/bin/setmqinst -i -p /opt/mqm

147 of 147 tasks have been completed successfully.

‘Installation1’ (/opt/mqm) set as the primary installation.

(base) [root@ECMUKDEMO6 bin]#

Figure 3-14The /etc/security/limits.conf file is edited to fix the Limits FAIL

7) env gives the following MQ-related environment variables.

(base) [root@ECMUKDEMO6 mqm]# . /opt/mqm/bin/setmqenv -s
(base) [root@ECMUKDEMO6 mqm]# env
MQ_INSTALLATION_NAME=Installation1
HOSTNAME=ECMUKDEMO6
OLDPWD=/opt/mqm/bin
CLASSPATH=/opt/mqm/java/lib/com.ibm.mq.jar:/opt/mqm/java/lib/com.ibm.mqjms.jar:/opt/mqm/java/lib/com.ibm.mq.allclient.jar:/opt/mqm/samp/wmqjava/samples:/opt/mqm/samp/jms/samples
MQ_INSTALLATION_PATH=/opt/mqm
PWD=/opt/mqm
HOME=/root
MQ_JAVA_INSTALL_PATH=/opt/mqm/java
MQ_DATA_PATH=/var/mqm
MQ_JAVA_DATA_PATH=/var/mqm
MANPATH=/opt/mqm/man:/usr/share/man
MQ_ENV_MODE=64
MQ_JRE_PATH=/opt/mqm/java/jre64/jre
PATH=/opt/mqm/bin:/root/miniconda3/bin:/root/miniconda3/condabin:/usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/opt/GO/go/bin:/root/.dotnet/tools:/root/bin:/opt/GO/go/bin
MQ_JAVA_LIB_PATH=/opt/mqm/java/lib64
(base) [root@ECMUKDEMO6 mqm]#
Listing 3-2The MQ-related environment variables

8) Launch the MQ Explorer.

Figure 3-15The MQ Explorer program is loaded

9) The MQ Explorer GUI is shown in Figure 3-16.

Figure 3-16The IBM MQ Explorer GUI is displayed using ./MQExplorer
NoteThe message displayed in Figure 3-16:
With this installation, existing local queue managers are displayed automatically in the Navigator view. However, the current user is not a member of the ‘mqm’ group and is therefore not authorized to use MQ control commands. The user will not be able to perform local queue manager operations such as create, start, stop and delete. To add a remote queue manager, right-click ‘Queue Managers’, and select ‘Add Remote Queue Manager’.

10) So, we must add wasadm as a member of the mqm group:

usermod -a -G mqm wasadm
Add mqm to the mqm group:
usermod -a -G mqm mqm
NoteThis must be done for the mqm user; otherwise, the wasadm Q Manager create will fail with an error message.

11) Log out and then log back in as wasadm for the changes to take effect.

Figure 3-17The Linux root user is logged out


Leave a Reply

Your email address will not be published. Required fields are marked *