The classes that the NOS maintains are the following:
A machine object represents any computer that is part of a DTS domain, or, any machine where you have installed a DTS server, agent, or both. Machine objects define properties associated with the actual computer, like name and description, and properties defining transmission settings to use during data transfer. If a computer has more than one communications interface, the machine object may reference one or more interface objects. DTMachine is a virtual, extended superclass with real subclasses of host, workstation, and unclassified TCP. So, when using DTMachine, you do not need to know whether a specific computer is classified as a host, workstation, or unclassified TCP object.
The MDB does not provide or contain the DTMachine class. The NOS provides the DTMachine. DTMachine exists to ease the use of objects in the MDB that represent computers, and to extend those objects such that they contain many DTS service-specific properties. The properties of machine objects affect how a data transfer is performed, and you can modify these properties to meet your needs. For example, you can modify the appropriate property to limit the rate of data transfers out of a machine, specify the protocols available on the machine, or indicate that a machine is available for receiving a broadcast data transfer.
A machine group object consists of a logical grouping of computers, other machine group objects, or both. You can establish these objects. Machine group objects let users and administrators create their own unique, logical, view of a DTS domain. Machine group objects are independent of the defined network topology and do not affect transfer routes through the network.
A machine container object defines a common set of transfer properties for a number of machine objects. These properties include the protocol and other communication settings the computers use during a data transfer. Administrators can use machine container objects to establish properties for a group of machine objects, by placing the machine objects into a container object and then setting the properties of the machine container object.
The Dynamic container class (DTDynamicContainer) functions much like the DTContainer class but 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 users create routes between machines and a dynamic container. A dynamic container stores objects whose addresses change over time, for example, machines that use DHCP or dial-up connections. When you view DTS objects in WorldView, if the DTS object you select is a dynamic container, then Class field shows DTDynamicContainer and a second tab (Membership) appears next to the Object Details tab. That tab lets you view and modify the individual addresses and address ranges belonging to the dynamic container.
Note: DTS WorldView dynamic container membership only supports IPv4 address ranges.
A link object defines a DTS communications link between two different machine or machine container objects. DTS administrators define these links that identify source and destination computers, with a common set of transfer properties associated with the link. Links define fixed data transfer routes through the enterprise.
An interface object defines a physical interface associated with a particular computer. You can associate specific protocol characteristics with the interface. By assigning a priority property to the interface, users can specify the order for evaluating the interfaces when determining the route and properties to use for a transfer. Interfaces associated with the responding computer are sequentially compared to those of the initiating computer until an interface with matching characteristics is found.
|
Copyright © 2014 CA Technologies.
All rights reserved.
|
|