 Task Start Time Jan 02,2002 03:27:55 PM Attribute Name Finish Time Retries Status 1.3.6.1.2.1.1.5.0 Jan 02,2002 03 Success Close Figure 11.13 Attribute audit details in CSM. 11.2.5 Using the ConfigClient The AdventNet implementation is fundamentally a client-server model. The CMS is the server product which complements the configuration management clients, "ConfigClients". When the application requests a task-based operation, the ConfigClient commu- nicates with the CMS through RMI or TCP and sends the XML code for the task. The CMS sends the result of the operation to the application through the ConfigClient after processing the task. To perform a task-based operation, the instance of ConfigClient must be obtained. The user application must register itself with the ConfigClient to get the result of operation performed by the task. When the client is registered, the ConfigClient returns a unique ID which is used to obtain the result of the operation. The ConfigClient class allows an applet or user application to communicate with CMS. Before that communication can begin, a particular method must be used to get the ConfigClient instance. The ConfigClient class is extended by the NMSConfigClient and defaultConfigClient classes. The NMSConfigClient uses the NMSSession and the Back End-Front End (BE-FE) Client Architecture. The defaultConfigClient opens a new session by estab- lishing a new socket connection between the client and CMS. To use the NMSConfigClient as the implementation class, it must be run in the configuration client JVM. It is also possible to run code in a different JVM, and there is a particular class that is to be used in order to do this. OSS for Telecom Networks When a combined task is executed, it may be desirable to inform some users of the result of task execution. Alternatively, suppose the combined task comprises three interdependent sub-tasks, then it may then be desirable that the second task should not be executed if the first task fails, and so on. An API is provided to allow such opera