Stopping and Starting the Queue Manager- IBM JMS Interface Development IBM FileNet 5.5.x Workflow


IBM JMS Interface DevelopmentCreating the AUD_CIOps Java Project, Error Log Location, IBM Certification Exams, Listener Authorities Stopping and Starting the Queue Manager- IBM JMS Interface Development IBM FileNet 5.5.x Workflow
0 Comments

Figure 3-149The wasadm Queue Manager is stopped

1. End all the activity of queue managers associated with the WebSphere MQ installation.

Figure 3-150The wasadm Queue manager default option is selected to stop Controlled

Select the type of Stop required and then click OK.

Figure 3-151The wasadm Queue Manager status is shown

a. Run the dspmq command to list the state of all the queue managers on the system.
Run either of the following commands from the installation that you are updating:
dspmq -o installation -o status
dspmq -a
dspmq -o installation -o status displays the installation name and status of all operational queue managers associated with all installations of all WebSphere MQ.

Figure 3-152The dspmq -o installation -o status command lists the state
dspmq -a displays the status of active queue managers associated with the installation from which the command is run.

b. Run the MQSC command, DISPLAY LSSTATUS(*) STATUS, to list the status of listeners associated with a queue manager:

echo “DISPLAY LSSTATUS(*) STATUS” | runmqsc QmgrName

Figure 3-153The status of the wasadm queue is confirmed

c. Stop any listeners associated with the queue managers, using the command:

endmqlsr -m QMgrName

Figure 3-154Any listeners for the wasadm Queue Manager are stopped

/opt/mqm/bin/mqconfig

Figure 3-155The configuration settings are checked

a) Restart the MQ wasadm Queue.

Figure 3-156The wasadm Queue Manager is restarted

Figure 3-157The Start Queue Manager for wasadm is confirmed by clicking OK

The status of the wasadm Queue Manager can be seen as highlighted in Figure 3-158.

Figure 3-158The active status of the restarted wasadm Queue Manager is displayed

Creating a Client Channel for Messaging

A custom Client Channel can be created for messaging based on a standard SYSTEM.DEF.SERVER template Object type, as shown in this section.

The CLIENT.wasadm Server Channel is created as a SYSTEM.DEF.SERVER object type.

Figure 3-159A new Server Channel is created as highlighted

Figure 3-160A new CLIENT.wasadm Server Channel is created and Next clicked

Figure 3-161The Local Transmission queue type is selected

Add the db2inst1 user to the mqm group:

usermod -a -G mqm db2inst1


Leave a Reply

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