Example 2: Transfer from z/OS to Windows through TIBCO Accelerator on Linux

This example describes a file sent from a platform server on z/OS to a platform server on Windows, through TIBCO Accelerator installed on two platform servers on Linux.

The following figure illustrates the example:

The transfer takes two important steps:
  • First, you have to configure the routing table on the TIBCO Accelerator client (SystemB) to enter the addresses of the TIBCO Accelerator server (SystemC) and the final destination, which is the platform server responder (SystemD). For more information, see Configuring the TIBCO Accelerator Client.
    Note: If the final destination is the TIBCO Accelerator server itself, no routing table entry is required, as shown in Example 1. It is only required when the platform server responder is a different machine than the TIBCO Accelerator server.

  • Next, you have to configure the platform server initiator (SystemA), to enter the information of the TIBCO Accelerator client (SystemB). This configuration is done by referencing the routing table that has been configured earlier. For more information on how to initiate file transfers on a platform server from a z/OS machine, see TIBCO Managed File Transfer Platform Server for z/OS documentation.

A TIBCO Accelerator server can send a file to any TIBCO MFT Platform Server responder with version 7.0 or lower. This includes TIBCO MFT Platform Server on Windows, UNIX, z/OS, and IBM i machines.

If you want further assistance for this example, contact TIBCO Technical Support.