The functionality described in this article is available in meshIQ Manage versions 11 and greater.
For a quick overview of what's new or changed, visit the meshIQ Highlights page for a version-by-version breakdown.  

Jump to Section:
Version 11.2 and Earlier
Version 12.x and Later

Version 11.2 and Earlier

You can export remote IBM MQ, TIBCO EMS, Kafka, ACE/IIB, and Solace connections to allow them to be imported later as needed.  Consider exporting and importing as a way to pass connections between people or make them available for new users.

Import remote manager configurations

Export remote manager configurations

About exported passwords

Remote manager configurations are imported and exported on the remote manager connections window, in the form of .json files. The name of the window depends on the product (technology) for which you are managing remote connections. Currently supported products are listed below. (The links lead to instructions on how to create remote managers manually.)  

Remote Queue Manager Connections (IBM MQ)
Remote EMS Connections (TIBCO)
Remote Kafka Manager Connections
Remote IIB/ACE Manager Connections
Remote Solace Manager Connections
Remote RabbitMQ Manager Connection

Import remote manager configurations

1. From the workgroup server’s pop-up menu, select Create > Remote Queue Managers. The Remote Queue Manager Connections window opens. The name of the menu option and window vary based on the product (IBM, Kafka, TIBCO EMS, IIB/ACE, or Solace).
   
2. Click Import. The Import Remote Queue Manager Connections dialog opens.
   
3. Click Choose File.

Import files must have the .json file name extension. You must import a remote manager definition file for the product that matches your selection on the workgroup server’s pop-up menu (IBM, Kafka, TIBCO EMS, IIB/ACE, or Solace). 

4. Navigate to the .json file from which you want to import remote manager definitions. Double-click the file, or click it once and click Open. The file name is included on the dialog, and the Instance Name and Queue Manager Name for each remote manager in the file are listed. 
   
5. Verify the managers that you want to import. You can click Clear to clear all selections, or select and clear checkboxes individually.
6. Click Import to import all selected managers. The imported records are displayed on the remote managers dialog:
   
7. Click OK to close the window and return to the Workspace dashboard. You can also reverse the import process by clicking Undo. 

Export remote manager configurations

1. From the workgroup server’s pop-up menu, select Create > Remote Queue Managers. The Remote Queue Manager Connections window opens. The name of the menu option and window vary based on the product (IBM, Kafka, TIBCO EMS, IIB/ACE, or Solace).
2. Select the remote manager or managers that you want to export the definition of.
   
3. Click Export. 
4. The export file is downloaded through your browser. It is named exported_remote_queue_manager_connections(<unique identifier>).json. 
   
5. Double-click the file to open and view it:
   

About exported passwords

In version 11.2, the password fields below are null in the export file.

ACE/IIB

"keyStorePassw": "null",
"record.password": "null",
"trustStorePassw": "null",

RabbitMQ

"keyStorePassw": "null",
"record.password: "null",
"record.trustStorePassw: "null",
"password": "null",
"sslKeyStorePassw": "null",
"sslKeyStorePrivatePassw": "null",
"sslTrustStorePassw": "null",

Kafka

For connections, KSQL, MDS, and schema

"keyStorePass": "null",
"password": "null",
"trustStorePass": "null",
"token": "null",

TIBCO EMS

"userPassword": null,
"sslPassword": null,

IBM MQ

"password": "null",
"sshPassword": "null",
"sslKeyPassPhrase": "null",
"sslKeyStorePassword": "null",

Solace

      "password": null,
      "keyStorePassw": null,
      "keyStorePrivatePassw": null,
      "trustStorePassw": null,

JCSMP:
          "sslTrustStorePassword": null,
          "password": null,
          "keyStorePassword": null,
          "keyStorePrivatePassword": null,
          "oAuth2AccessToken": null,

_______________________________________________________________________________________________________________

Version 12.x and Later

You can export remote IBM MQ, TIBCO EMS, Kafka, ACE/IIB, Solace and RabbitMQ connections to allow them to be imported later as needed. Consider exporting and importing as a way to pass connections between people or make them available for new users.

Import Remote Manager Configurations

Export Remote Manager Configurations

About Exported Passwords

Remote manager configurations are imported and exported on the remote manager connections window, in the form of .json files. The name of the window depends on the product (technology) for which you are managing remote connections. Currently supported products are listed below. (The links lead to instructions on how to create remote managers manually.)  

Remote Queue Manager Connections (IBM MQ)
Remote EMS Connections (TIBCO)
Remote Kafka Manager Connections
Remote IIB/ACE Manager Connections
Remote Solace Manager Connections
Remote RabbitMQ Manager Connection

Import Remote Manager Configurations

1. Select the node into which you want to import a connection, then from the Selected menu, click Manage Connections.
   
2. The Remote * Manager Connections window opens. The exact name of the window will vary depending on the product (IBM MQ, Kafka, TIBCO EMS, IIB/ACE, Solace, or RabbitMQ).
   (This example uses an IBM MQ Queue Manager.)
   
3. Click Import. The Import Remote Queue Manager Connections dialog opens.
   
4. Click Choose File.
   Import files must have a .json file name extension. When importing connections, you can only import them into the nodes you have selected (IBM, Kafka, TIBCO EMS, IIB/ACE, Solace, or RabbitMQ). If you attempt to import connections associated with other node types, a warning message appears prompting you to change the node of the imported connections.
   
   
5. Navigate to the .json file containing the remote manager definitions. Double-click the file, or select it and click Open.
   The file name appears in the dialog, and the Instance Name and Queue Manager Name of the remote manager(s) from the file are listed.

6. If you want to modify the connection details, click the Edit button. The Change Queue Manager Connection dialog opens.
   Make the necessary changes and click Ok.
   

7. Verify the managers you want to import.

   • If the file contains multiple connections, you can click Clear to unselect all entries, or manually select/deselect connections using the checkboxes.

8. Click Import to import all selected connections.
   The imported records appear in the Remote Managers dialog.
   
9. To undo the import, click the Undo button.
   (Note: Only the most recent action can be undone.)
10. Click OK to close the window and return to the Workspace Dashboard.

Export Remote Manager Configurations

1. Select the node into which you want to export a connection, then from the Selected menu, click Manage Connections.
2. The Remote * Manager Connections window opens. The exact name of the window will vary depending on the product (IBM MQ, Kafka, TIBCO EMS, IIB/ACE, Solace, or RabbitMQ).
   (This example uses an IBM MQ Queue Manager.)
3. Select the remote manager or managers whose definitions you want to export.
   

4. Click Export from the Selected menu.
   
   The export file is downloaded through your browser. It is named:
   exported_remote_queue_manager_connections(<unique identifier>).json

5. Double-click the file to open and view its contents.

About Exported Passwords

The password fields below are null in the export file.

IBM MQ

"password": "null",
"sshPassword": "null",
"sslKeyPassPhrase": "null",
"sslKeyStorePassword": "null",

TIBCO EMS

"userPassword": null,
"sslPassword": null,

Kafka

For connections, KSQL, MDS, and schema

"keyStorePass": "null",
"password": "null",
"trustStorePass": "null",
"token": "null",

ACE/IIB

"keyStorePassw": "null",
"record.password": "null",
"trustStorePassw": "null",

Solace

      "password": null,
      "keyStorePassw": null,
      "keyStorePrivatePassw": null,
      "trustStorePassw": null,

JCSMP:
          "sslTrustStorePassword": null,
          "password": null,
          "keyStorePassword": null,
          "keyStorePrivatePassword": null,
          "oAuth2AccessToken": null,

RabbitMQ

"keyStorePassw": "null",
"record.password: "null",
"record.trustStorePassw: "null",
"password": "null",
"sslKeyStorePassw": "null",
"sslKeyStorePrivatePassw": "null",
"sslTrustStorePassw": "null",