IBM MQ Console: Adding a remote queue manager - CD only

You can use the IBM® MQ Console to administer a queue manager running on a remote system.

Before you begin

You must prepare the queue manager on the remote system so that it can be administered remotely, see step 1, 2, 3, and 4 of Adding a remote queue manager to the IBM MQ Console by using the command line - LTS only.
You must also enable remote connections from the IBM MQ Console. For more information, see Configuring remote queue manager connection behavior.

About this task

You use a client connection definition table (CCDT) in JSON format to specify the remote connection details. You can create a JSON CCDT by using a text editor (see step 5 of Adding a remote queue manager to the IBM MQ Console by using the command line - LTS only) or you can create one by using the IBM MQ Console.

Alternatively, you can create the CCDT from the IBM MQ Console by specifying connection details directly as you add the remote queue manager.

You can also connect a remote queue manager to the IBM MQ Console by using the command line for all of the required tasks (in addition to preparing the remote queue manager and creating a CCDT). See Adding a remote queue manager to the IBM MQ Console by using the command line - LTS only.

Attention: if you receive the following messages:

MQWB2026E: The request to connect to the remote queue manager 'rqmgr-qmgr_name' failed with the error message:
'JMSCC0051: The property 'JMS_IBM_MQMD_AccountingToken' should be set using type '[B', not 'java.lang.Object'.'

you are attempting to pass a java.lang.Object to the accounting token, when a java object type byte[] is expected.

Procedure

To add a remote queue manager by specify an existing CCDT:
1. From the Home page, click Connect remote queue manager.
2. Specify the name of the remote queue manager.
3. Optionally, specify a unique name for the queue manager. If you do not specify a unique name, the actual name is used with the prefix "remote-" added.
4. Ensure that Connect using a JSON CCDT is selected.
5. Click Browse and select the file containing the JSON CCDT that you want to use.
6. Click Next to move to the user page and optionally specify a username and password to connect to the remote queue manager. If you do not specify this information, then authentication information is taken from the remote connection configuration file.
7. Click Next to move to the Certificate page. If your CCDT specifies "transmissionSecurity" information, this is information is used. You can optionally paste a certificate (as a base64 encoded public key) and this is added to the global trust store.
  
  The certificate is temporarily stored in WLP_USER_DIR/generated.crts/uniqueName-qmgrName.crt before it is added to the trust store. When the connection is successfully added, the certificate is deleted from this location.
8. Click Next to view the summary page. You can use the Back button to revisit previous pages and make corrections. If you are happy with the information, click Connect to connect to the remote queue manager.
To add a remote queue manager and specify connection information manually:
1. From the Home page, click Connect remote queue manager.
2. Specify the name of the remote queue manager.
3. Optionally, specify a unique name for the queue manager. If you do not specify a unique name, the actual name is used with the prefix "remote-" added.
4. Select Manual Entry.
5. Enter the name of the client connection channel that the connection will use.
6. Specify the name of the host where the remote queue manager is running. If remote MQ installations are detected, the host names are displayed and you can select the host of the remote queue manager that you want to connect to. In some network configurations, it is not possible to detect remote MQ instances. In this case, add the host name and port manually.
7. Click Next to move to the user page and optionally specify a username and password to connect to the remote queue manager. If you do not specify this information, then authentication information is taken from the remote connection configuration file.
8. Click Next to move to the Certificate page. You can select an SSL CipherSpec from the drop-down list. You can optionally paste a certificate (as a base64 encoded public key) and this is added to the global trust store.
  
  The certificate is temporarily stored in WLP_USER_DIR/generated.crts/uniqueName-qmgrName.crt before it is added to the trust store. When the connection is successfully added, the certificate is deleted from this location.
9. Click Next to view the summary page. You can use the Back button to revisit previous pages and make corrections. If you are happy with the information, click Connect to connect to the remote queue manager.
The connection information that you specified is written to CCDT file in your web directory. The path is WLP_USER_DIR/generated.ccdt/ccdt-uniqueName.

Results

The remote queue manager appears in the remote queue manager list in the IBM MQ Console. Provided that the connection is successful, you can administer the objects of the remote queue manager in the same way that you work with the objects of a local queue manager.