re used to set the task and attribute information for the task. To provide SNMP- specific details, the SNMP-specific class SNMPTaskGenerator can be used. This class is an extension of the TaskGenerator class and defines specific methods for SNMP- related functions. The ConfigClient instance is obtained and the attributes set. Creating SNMPv3 tasks involves special considerations due to particular features of SNMPv3, especially security features. Once task information and attributes are set, the task is converted to XML format and saved. Once the task is saved, the result of the saved operation can be handled SO that the ConfigClient instance receives the desired result. OSS for Telecom Networks Creation of Telnet, TFTP and TL1 tasks is similar to the creation of SNMP tasks. 11.2.4.1 Executing Tasks Having created a task, it will at some point be necessary to execute the task. Once the task has been defined by setting the task and attribute level information, the task is stored in a particular directory. To execute a task, the task should be associated with a set of devices which are given in a device list. It is over these devices that the task will be executed. A method of the ConfigClient API class is used to execute tasks. In associating devices with a task, the devices attributes can be set using the methods in the Device class. For example, to execute an SNMP task or TFTP task, the devices are defined as shown below. The Device method takes as string inputs the host on which the task must be executed and the port through which the config- uration must be accomplished. For example, for an SNMP task, devices are defined as shown in Figure 11.6. Once device properties are defined, the task is associated with devices. Next, the task XML code is generated and passed as an argument to the ConfigClient API's method that will execute the task. The result of task execution can be obtained using the audit trail. The methods in the classes DeviceAudit, AttributeAudit and TaskAudit can be used to discover the device, at