Skip to main content

Websphere Message Broker (WMB) v7 Quick Reference - Middleware News

Websphere Message Broker (WMB) v7 Quick Reference

Settings up Command environment:
Run mqsiprofile script

Running Commands:
Commands must be lower case
Component names case sensitive
=================================================================
Start/Stop/Delete Broker:
Start: mqsistart BrokerName
Stop: mqsistop BrokerName
.q after name stops associated queue manager
.i after name stops immediately
Delete: mqsideletebroker BrokerName [options]
Note: Broker must be stopped before it can be deleted
=================================================================

Start/Stop/Delete Configuration Manager:
Start: mqsistart ConfigMgrName

Stop: mqsistop ConfigMgrName
.q after name stops associated queue manager
Delete: mqsideleteconfigmgr [ConfigMgrName] [options]
.n flag to delete configuration repository
-w flag deletes all files in the configuration manager.s work path

Start/Stop/Delete UserNameServer:
Start: mqsistart UserNameServer
Stop: mqsistop UserNameServer

.q after name stops associated queue manager
Delete: mqsideleteusernameserver [options]
.q after name deletes associated queue manager
.w after name deletes all files in the work path associated with the User Name Server
=================================================================

Specifying Username and password:
You can specify the following flags along with the commands
.i userid
.a password
If you leave, -a flag black; it will prompt you for password.
=================================================================

Changing Broker
mqsichangebroker BrokerName [options]
-s . User Name Server queue manager name
-j . Enable publish/subscribe for the broker
-d . Disable publish/subscribe for the broker
-t . Run the broker as a trusted MQ application
-n . Stop running the broker as a trusted MQ application
-g . Configuration timeout . maximum time for response from an execution group
-k . Configuration delay timeout . maximum time for response from a broker
=================================================================

Changing Configuration Manager
mqsichangeconfigmgr [ConfigMgrName] [options]
-s . User Name Server queue manager name
-j . Maximum Java virtual machine heap size in megabytes. The default is 128.
Changing User name server
mqsichangeusernameserver [options]
-r . Refresh interval being the amount of time before the User Name Server interrogates
the security subsystem for changes to users or groups
-g . The name of the authentication data source
-j . Indicates use of a data source containing users and group information instead of
using the operating system
-o . Indicates use of the operating system users and group information
Note: before executing above change commands, the respective component must be
stopped.
=================================================================

Execution Groups:
Create: mqsicreatexecutiongroup [options]
Delete: mqsideleteexecutiongroup [options]
-i host
-p port number of the Configuration Manager-q Config Manager QM
-q queue manager of Configuration Manager
-b Broker name
.e Execution group name
-w timeout
- v tracefile name

Start: mqsistartmsgflow [options]
Stop: mqsistopmsgflow[options]
-i host
-p port number of the Configuration Manager-q Config Manager QM
-q queue manager of Configuration Manager
-b Broker name
.e Execution group name
-m specific flow within the execution group
-w timeout
- v tracefile name

Report message flow statistics: mqsireportflowstats broker_name [options]
-e ExecutionGroupName
-f MessageFlow
-a Specify that the command modifies archive accounting and statistics collection.
-s Specify that the command modifies snapshot accounting and statistics collection.
-g Specifies that the command applies to all execution groups that belong to the broker.
-j Specifies that the command applies to all message flows that belong to the execution
group.
=================================================================

Change message flow statistics: mqsichangeflowstats [options]
-e ExecutionGroupName
-f MessageFlow
-a Specify that the command modifies archive accounting and statistics collection.
-s Specify that the command modifies snapshot accounting and statistics collection.
-g Specifies that the command applies to all execution groups that belong to the broker.
-j Specifies that the command applies to all message flows that belong to the execution
group.
-o OutputFormat; usertrace/xml
Deploy:
=================================================================

mqsideploy [options]
-p port number of the Configuration Manager
-q queue manager of Configuration Manager
-b Broker
-e Execution Group
-a BAR file
-w Timeout
Listing resources
mqsilist [options]
- a List all the components
- brokerName The name of the broker for which you want to list resources
Made by: Joseph Amrith Raj
- e egName selects an execution group within a broker
=================================================================

Security Commands
Create ACL: mqsicreateaclentry ConfigmgrName [options]
List ACL entries: mqsilistaclentries [options]
Delete ACL entries: mqsideleteaclentries [options]
-g GroupName The local group to which this entry refers
-u UserName The user name to which this entry refers
-m MachineName The name of the machine from which a specified user can connect.
-a The specified user name can be on any machine.
-x AccessLevel
F: Full control
D: Deploy
E: Edit
V: View
-b Broker
-e ExeGroup, You must specify the b flag if you specify this flag.
-s Subscription The object is a subscription object, and its name is specified as a
parameter.
-r The object refers to the root topic.
-t The object refers to the main topology.
-p The object refers to the "allresources" resource type
=================================================================

Backup/Restore Commands
Backup: mqsibackupconfigmgr ConfigMgrName .d DirPath [options]
Restore: mqsirestoreconfigmgr ConfigMgrName .d DirPath .a ArchiveName [options]
-w WorkPath Specifies the path for the Configuration Manager repository
=================================================================

Problem Determination
Trace
Report Trace: mqsireporttrace [options]
Change Trace: mqsichangetrace [options]
-componentName The name of a broker, a Configuration Manager, or the fixed name
User Name Server;
-e egName The label of the execution group for which a report is required. This option is
valid only if you have specified a broker as the component.
-f messageFlow The label of the message flow for which a report is required. This option is
valid only if you have specified a broker as the component, and an execution group.
-u Derive report information from the user trace.
-t Derive report information from the service trace.
-b Request a report for agent function.
-n Report the setting of the Trace node switch.
Read Trace: mqsireadlog BrkName [options] .o Output_file
-e Egroup
-o Outputfilename
-f Read the log file directly from the file system
-u Read the log contents from the user trace log.
-t Read the log contents from the service trace log.
Format Trace: mqsiformatlog .i input_file -o Output_file
=================================================================

Publish/subscribe commands
Add, remove, and list MQ publish/subscribe broker network
Add: mqsijoinmqpubsub Broker_name [options]
-p ParentQueueManagerName, The name of the queue manager that hosts
the WebSphere MQ Publish/Subscribe broker to which this WebSphere Message
Broker broker is to be joined
=================================================================

Remove: mqsiclearmqpubsub Broker_name [options]
-n NeighborQueueManagerName, The name of the queue manager that hosts
the WebSphere MQ Publish/Subscribe broker for which the association as a neighbor is
being removed.
List: mqsilistmqpubsub Broker_name

=================================================================
Database commands
CreateDB:
(windows) mqsicreatedb DBName [options]
-i ServiceUserID, The user ID under which the DatabaseInstanceMgr service runs
-a ServicePassword, The password for the ServiceUserID
-p PortNumber, The TCP/IP port number that this component will use on the local
machine
-e DbType
-u DbUserID, An additional user name that requires access to the database that is
created by this command.
(unix/Linux) mqsi_setupdatabase [options]
-Database_Home_Directory, The name of the directory in which the database is (or will
be) installed
Change user ID andpassword information
mqsisetdbparms BrokerName [options]
-n ResourceName or AdapterName
-u UserId or EISUserId
-p Password
-d This parameter deletes the user ID and password pair for this resource from the registry.
-a Specify this parameter to process the mqsisetdbparms command when the broker
itself is running.
=================================================================

Comments

adsrerrapop

Popular posts from this blog

IBM Websphere MQ interview Questions Part 5

MQ Series: - It is an IBM web sphere product which is evolved in 1990’s. MQ series does transportation from one point to other. It is an EAI tool (Middle ware) VERSIONS:-5.0, 5.1, 5.3, 6.0, 7.0(new version). The currently using version is 6.2 Note: – MQ series supports more than 35+ operating systems. It is platform Independent. For every OS we have different MQ series software’s. But the functionality of MQ series Default path for installing MQ series is:- C: programfiles\BM\clipse\SDK30 C: programfiles\IBM\WebsphereMQ After installation it will create a group and user. Some middleware technologies are Tibco, SAP XI. MQ series deals with two things, they are OBJECTS, SERVICES. In OBJECTS we have • QUEUES • CHANNELS • PROCESS • AUTHENTICATION • QUERY MANAGER. In SERVICES we have LISTENERS. Objects: – objects are used to handle the transactions with the help of services. QUEUE MANAGER maintains all the objects and services. QUEUE: – it is a database structure

IBM Websphere MQ Reason code list / mq reason codes / websphere mq error codes / mq error messages

Reason code list ================= The following is a list of reason codes, in numeric order, providing detailed information to help you understand them, including: * An explanation of the circumstances that have caused the code to be raised * The associated completion code * Suggested programmer actions in response to the code * 0 (0000) (RC0): MQRC_NONE * 900 (0384) (RC900): MQRC_APPL_FIRST * 999 (03E7) (RC999): MQRC_APPL_LAST * 2001 (07D1) (RC2001): MQRC_ALIAS_BASE_Q_TYPE_ERROR * 2002 (07D2) (RC2002): MQRC_ALREADY_CONNECTED * 2003 (07D3) (RC2003): MQRC_BACKED_OUT * 2004 (07D4) (RC2004): MQRC_BUFFER_ERROR * 2005 (07D5) (RC2005): MQRC_BUFFER_LENGTH_ERROR * 2006 (07D6) (RC2006): MQRC_CHAR_ATTR_LENGTH_ERROR * 2007 (07D7) (RC2007): MQRC_CHAR_ATTRS_ERROR * 2008 (07D8) (RC2008): MQRC_CHAR_ATTRS_TOO_SHORT * 2009 (07D9) (RC2009): MQRC_CONNECTION_BROKEN * 2010 (07DA) (RC2010): MQRC_DATA_LENGTH_ERROR * 2011 (07DB) (RC2011): MQRC_DYNAMIC_Q_NAME_ERROR * 2012 (07DC) (RC201

IBM WebSphere MQ – Common install/uninstall issues for MQ Version on Windows - Middleware News

Creating a log file when you install or uninstall WebSphere MQ WebSphere MQ for Windows is installed using the Microsoft Installer (MSI). If you install the MQ server or client through launchpad , MQPARMS or setup.exe , then a log file is automatically generated in %temp% during installation. Alternatively you can supply parameters on the installation MSI command msiexec to generate a log file, or enable MSI logging system-wide (which generates MSI logs for all install and uninstall operations). If you uninstall through the Windows Add/Remove programs option, no log file is generated. You should either uninstall from the MSI command line and supply parameters to generate a log file, or enable MSI logging system-wide (which generates MSI logs for all install and uninstall operations). For details on how to enable MSI logging, see the following article in the WebSphere MQ product documentation: Advanced installation using msiexec For details on how to enable system-w