Skip to main content

Requirements for Remote Administration using the WebSphere MQ Explorer - Middleware News

Requirements for Remote Administration using the WebSphere MQ Explorer - Middleware News

Ensure that you have satisfied the following requirements before trying to use the WebSphere MQ Explorer to do remote administration. Verify that:
  1. The WebSphere MQ server and client is installed on the local and the remote machine.
  2. A command server is running for every queue manager.
  3. A TCP/IP listener exists for every queue manager. This can be the WebSphere MQ listener or the inetd daemon as appropriate for your operating system environment.
  4. The server-connection channel, called SYSTEM.ADMIN.SVRCONN, exists on every remote queue manager. This channel is mandatory for every remote queue manager being administered.
  • Create the channel using the following MQSC command:
    DEFINE CHANNEL(SYSTEM.ADMIN.SVRCONN) CHLTYPE(SVRCONN)    .
  • The userID of the initiator must be a member of the "mqm" group on the local and remote machine. The model queue SYSTEM.MQEXPLORER.REPLY.MODEL must exists on every queue manager.
  • Create the queue using the following MQSC command: DEFINE QMODEL(SYSTEM.MQEXPLORER.REPLY.MODEL)

Using the WebSphere MQ Explorer for Remote Administration

Satisfy all of the requirements for Remote Administration and then you can use the WebSphere MQ to do administration tasks on your local and remote queue managers.

To show a remote queue manager, right click the WebSphere MQ Explorer Queue Manager folder, select Show/Hide, then select the Add button on the Add Queue Manager screen(see Figure 1 then type:
  • The name of the remote queue manager and press the Next button.
  • Select the Specify connection details radio button(see Figure 2).
  • Type the host name or IP address of the remote queue manager and listener port and press the Finish button.

Reasons for Remote Administration failures:

  1. The Command server is not running on remote queue manager. Message AMQ4042 will be issued.
  2. The Listener is not running on remote queue manager. Message AMQ4043 will be issued.
  3. The SYSTEM.ADMIN.SVRCONN is not defined on remote queue manager. Message AMQ4043 will be issued.
  4. The security check failed on remote queue manager. Message AMQ4043 will be issued.
  5. Prior releases of WebSphere MQ for z/OS (v5.3 and v5.3.1) do not provide this function and any attempt to remotely administer a queue manager will fail. The WebSphere MQ V6.0 product has been enhanced to support the remote administration of a z/OS queue manager using the WebSphere MQ Explorer on Windows and Linux Intel.
  6. Code page conversion failures can cause problems. Message AMQ4043 will be issued. For more information, see technote: Remote Administration through WebSphere MQ Explorer "Show Queue Manager" Fails AMQ4043
  7. The SYSTEM.MQEXPLORER.REPLY.MODEL is not defined on remote queue manager and you are using the V6.0 WebSphere MQ Explorer. Message AMQ4400 will be issued.
  8. The Client attachment feature is not installed on WebSphere MQ for z/OS. The CHIN joblog will contain message CSQX260E. To connect to the z/OS queue manager using the SYSTEM.ADMIN.SVRCONN channel, you need to have the Client Attachment feature installed, which is FMID JMS6007 for WebSphere MQ for z/OS 6.0.0.

    Note:
    In WebSphere MQ V7 for z/OS you can create five “free” client attachments for use with MQ Explorer. These attachments must use the channel name SYSTEM.ADMIN.SVRCONN, which is the default channel name used by the MQ Explorer.

    To use the free client attachments, you must first alter the SYSTEM.ADMIN.SVRCONN channel definition and set the maximum instances (MAXINST) attribute to 5 or less. You should also ensure that your server-connection channel is secured by the usual means.
Labels:

Comments

Post a Comment

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 ...
143 comments
Read more

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...
5 comments
Read more

Installing IBM Integration Bus on Linux - Middleware News

Before you begin Check the readme.html file for any updates to these installation instructions; see the product readmes web page. Check that you have enough memory and disk space; see IBM Integration Bus system requirements. Check that you have completed any prerequisite steps; see Preparing the system. If you are using Red Hat Linux 6.5 with WebKitGTK version webkitgtk.x86_64 1.2.6-5.el6, complete the steps in the following topic to work around problems with the Eclipse SWT browser: IBM Integration Toolkit on RedHat 6.5 crashes with "JVM terminated. Exit code=160" error. If you are using Red Hat Linux 6.x or 7.x, you might need the GTK2 32-bit drivers installed on Linux; for more information, see IBM Integration Toolkit on Linux becomes unresponsive after opening a DFDL or XSD file. If you are using Red Hat Linux 7.1, complete the steps in the following topic to work around problems with the Eclipse SWT browser: Internal web browser in IBM Integration Toolkit ...
19 comments
Read more