Example 2: z/OS to UNIX Using TIBCO Accelerator for Windows



As you can see in Example 2, more operations are performed than in Example 1. This diagram demonstrates sending a file from a z/OS MFT Platform Server (SystemA) to a Linux MFT Platform Server system (SystemD). Both of these servers do not have the TIBCO Accelerator technology contained in them and therefore must pass the transfer to TIBCO MFT Platform Server for Windows server running the TIBCO Accelerator service.

When conducting TIBCO Accelerator transfers of this kind, you must configure a TIBCO Accelerator Routing Table on the TIBCO Accelerator Client that the Platform Server Initiator connects to. The TIBCO Accelerator Client needs the connectivity information for the destination TIBCO Accelerator Server that connects to the Platform Server Responder.

Note:

If your final destination is the TIBCO Accelerator Server itself, no routing table entry is needed. It is only required when the Platform Server Responder is a different machine than the TIBCO Accelerator Server.

Example 1 shows the Platform Server Responder on the same machine as the TIBCO Accelerator Server; therefore, no routing table updates are needed. Example 2 shows the Platform Server Responder on a different machine as the TIBCO Accelerator Server; therefore, the routing table must be updated.

Procedure

  1. To configure the routing table, open Windows Explorer and navigate to the following folder: <PlatformServer_Install>\TIBCO\MFT Platform Server\RSTunnel\
  2. Double-click the file RSTunnelConfig.exe. The following window is displayed:


  3. Click Configure the RocketStream Accelerator (Set Debugging Options can only be used when instructed by TIBCO Technical Support.) The following window is displayed:


  4. Click Configure TIBCO Accelerator Routing Table. You can see an example setup.


  5. Select the first row. Click Edit. The following window is displayed:
    1. Define the Destination Host (the IP of the server that is the final destination for your file being transferred: the Responder) and the Gateway Host (the remote TIBCO Accelerator Server that is initially receiving your file transfer before passing it off to the Destination Host).
    2. If required, edit the default ports used for the various protocols TIBCO Accelerator provides. As shown in the screenshot above, the Routing Table is configured with the IP addresses of SystemC and SystemD.
    3. When you are done, click Save.
      Note: You are then presented with a warning that the RocketStream Tunnel service must be restarted for the changes to take effect.
    4. Stop and start TIBCO Accelerator from your Server Properties window or you can open your Services window and restart MFT Platform Server.
    5. Close the Configure RocketStream Routing Table window.
      The routing table is configured on the TIBCO Accelerator Client defining what ports is used when sending files with the various protocols TIBCO Accelerator offers.
  6. If multiple network cards are available, at this time, define the port and IP address your Client binds to. By default, the client listens on port 9099. If you must change the default port number, click Configure RocketStream Client (see figure in Step3). The following window is displayed:


  7. If your server has multiple network cards, define the IP adapter address you want the TIBCO Accelerator Client to bind to; otherwise, leave the Bind to IP Adapter Address field.

  8. When you are done, click Save and close the window.
    If your TIBCO Accelerator Client would ever be switching roles and acting as a TIBCO Accelerator Server in the future, configure the TIBCO Accelerator Server ports and IP address to bind to at this time by clicking the Configure RocketStream Server button (see figure in Step3). The following window is displayed:
    Note: Unless you want to change the default ports being used by the server or you must bind to a specific IP address because multiple network cards are installed on the system, you can leave these settings alone.


    This completes configuring TIBCO Accelerator Client and TIBCO Accelerator Server.

    For more information on how to initiate file transfers on a platform server for z/OS or UNIX, see TIBCO Managed File Transfer Platform Server for z/OS, and TIBCO Managed File Transfer Platform Server for UNIX documentation.

    A TIBCO Accelerator Server can send a file to any MFT Platform Server responder with version 7.0 or lower. This includes TIBCO MFT Platform Server for Windows, UNIX, z/OS, and AS/400 (System i) servers. This concludes configuring the necessary steps needed for our Example 2 diagram. If you need further assistance for this example, contact TIBCO Technical Support.