Object Model

The object model explains how DTS is object-oriented (OO). Object-oriented means that to use the services available, you create objects (instantiate), configure them (set properties), and call functions (methods) associated with those objects. The DTS object model consists of a set of object classes that reference and interact with one another. To use DTS, ensure that you can do the following:

Connect to an object server
Create (instantiate) objects of the appropriate classes
Set the properties of the objects to requisite values
Call object methods

A brief description of each of the classes that DTS supports follows:

DTContainer

Overrides DTS properties for a list of DTMachine objects. You can treat several DTMachine objects as a single entity using DTContainers, when it comes to DTS network topology administration and configuration. This object contains a full set of DTS properties and references to one or more DTMachine objects.

DTDynamicContainer

Contains the same properties as the DTContainer class but also has an additional property: a range of addresses or a subnet that defines the members of the container. All agents whose IP address is in this range become members of the dynamic container. Dynamic containers let a user create routes between machines and a dynamic container.

DTFilter

Specifies how to read or write data, and any processing to perform on the data before or after the transfer. For instance, you can use filters like binary read, compression, decompression, binary write, and so forth.

DTInterface

Represents a communications interface on a computer.

DTLink

Represents a direct DTS communications link between one DTMachine (or DTContainer) and another. The link object creates specific routes through the DTS enterprise.

Each object server (Network, Transfer and Schedule) maintains objects of particular classes specific to the function of the server. Local object repositories (databases) store these objects persistently; one repository exists for each object server.

DTMachine

Defines a computer in the enterprise. If the computer has multiple communications interfaces fitted and available for DTS to use, then this object references one or more DTInterface objects.

DTMachineGroup

Represents a logical grouping of computers. This object references DTMachine objects or other DTMachineGroup objects.

DTSchedule

Specifies when a transfer should occur. This object references one or more DTTransferGroup objects. This object may also reference one or more calendars.

DTTransfer

Defines a single data transfer from one computer to another. Among other things, this object contains references to DTFilter objects.

DTTransferGroup

Defines a group of transfers that are to be controlled together. It references one or more DTTransfer objects.

Note: The NOS uses the MDB as its persistent object store. DTS utilizes the network information already stored in the MDB.