title: WMQ FTE in a Distributed Environment
body: <p>QMGR A has an MFT agent called AgentA. 
  QMGR B has an MFT agent called AgentB.
  QMGR C has an MFT agent called AgentC.
  These are all MFT Server deployments, not "client".</p>
  
  <p>QMGR A and B are members of an MQ cluster, called FTECluster</p>
  
  <p>QMGR C connects to QMGR B via a simple sender/receiver pair (outside the cluster).</p>
  
  <p>MFT users on the server where QMGR A runs want to send a file FROM that server to the server where QMGR C runs.</p>
  
  <p>QMGR B is the designated Coordination Qmgr, so if, when connected there via the explorer, I create a transfer, using </p>
  
  <p>QMGRA as the source and
  QMGRC as the destination, will I always expect that the agent will encounter a 2087 error (which is what I'm getting), that the target remote queue is not known?  Or is there some "extra" setup than needs to be performed to acquaint QMGRA with QMGRC by way of QMGRB?</p>
  
  <p>The application is this: I have enclave based queue managers (QMGRA) that are behind a DMZ (the gateway, QMGR B), and would like to move files for external partners to those inside/outside the enclave via MFT, not unlike we use queues to move messages from overlapping clusters or from queue managers in /out of the cluster to those out/in of an adjoining cluster.  OR, to permit file transfers BETWEEN MFT users INSIDE the enclave, so that the traffic is not paraded out onto the DMZ for internal transfers.  </p>
  
  <p>If this is not possible, then we'll have to have MFT transfers that are created between clients on internal enclave servers, thru DMZ based MFT servers, and out/in to the external customer base, AND have internal agent/servers on designated enclave queue managers, for the purpose of exchanging files internally.</p>