runtime by defin- ing tasks and subsequently executing them on the required devices. Requests between client and server are handled by a separate session called ConfigSession. This session 11 Configuration Management Task & Template Configuration Datasource Configuration Device List Configuration Server Config Config Upload Session Client Parser Configuration Task Audit Details Rollback Configuration Execution Figure 11.21 Batch configuration architecture. is responsible for communication with the CMS and is started at the same time as the server. The tasks created are stored in the database. All tasks currently configured in the server are displayed when the user selects the "Batch Configuration" node in the client tree. The user can perform task-related operations using the "Configura- tion Operations" menu. Communication with the server is handled by ConfigSession, which is initiated when the client appears. All classes which need to communicate with the CMS implement a particular common interface. The batch configuration module is built on the model/view/controller (MVC) architecture. Figure 11.21 illustrates the batch configuration architecture. The batch configuration user interface is available as a customizable and plug- gable application. The module can be customised using a bean builder IDE. OSS for Telecom Networks 11.2.12.3 Framework API The NMS user interface API class provides APIs for handling custom views and client tree functionalities from within the Java client framework. These API methods can be accessed only within the same JVM as that of the Java client. The NMS user interface API provides many static methods which can be used to handle various custom view functionalities and perform tree operations. The custom view APIs can be used for creating custom views under a specified parent node of any panel. Operations such as adding, modifying, removing and renaming custom views can be performed using methods of this API. There are also methods for creating temporary custom views. Client tree node