The Transfer Object Server (TOS) is responsible for initiating, controlling, and monitoring all user requested data transfers, and accepting and processing requests from the client API. When the TOS activates a data transfer, it sends a message to the initiating DTS agent, telling it to transfer the data. The TOS is then responsible for processing progress and status messages that are returned from the initiating agent.
The TOS optimizes those requests by making the most efficient use of network resources, it manages hops (intermediate nodes), fanouts, and broadcasts. The TOS uses any available network topology information that it obtains from the NOS, and instructs the DTS agent on the sending machine to perform the data transfer. The TOS also lets applications monitor and control the transfers that are submitted.
You can connect to the TOS through the client API and can create filter objects, transfer objects, and can transfer group objects. You set object properties to define your data transfer requirements. You can then call the transfer group objects ACTIVATE method to perform the transfers you have defined. The TOS stores all these objects persistently in its own local object repository that is named the Transfer Object Repository (TOR).
Note: It is possible to perform agent-to-agent transfers without the TOS, using the DTS command-line interface.
The TOS directly accesses the MDB from its TOR and uses NOS to get information from WorldView, also part of the MDB. It uses the network object properties that are returned from the NOS to make decisions about the best way to transfer your data.
DTS uses the four-phase optimization for transferring your data in the most efficient way. The TOS is responsible for carrying out Phases 3 and 4 of the optimization process, Duplicate Transfer Resolution, and Transfer Mechanism Selection, respectively.
|
Copyright © 2014 CA Technologies.
All rights reserved.
|
|