ing username and password and then initialises the common socket connection and the GenericSocket connection. Communication between the server side (FE server versus BE server) and the client side (FE server versus Java client) occurs through a common connection which uses either TCP socket or RMI. User-written modules can also use the common connection. 11.2.13 NAR Packager Any application developed in AdventNet's Management Builder development envir- onment can be integrated with CMS using the (NAR) file. The NAR file contains the 11 Configuration Management resources and details that are needed for integration with CMS. It is beyond the scope of this book to explain how this works. 11.2.14 MIB Browser CMS comes equipped with an SNMP MIB browser module. This module permits loading of MIBs, MIB browsing, walking through the MIB tree, searching MIBs and performing all other SNMP-related functions. It is possible to view and manipulate the data available through an SNMP agent in a managed device through the MIB browser. More details on the MIB browser are given in Chapter 4. 11.2.15 Working with Batch Configuration Task information includes details such as task name, description, protocol used by the task and task attributes. Task details are viewed in the Batch Configuration panel as shown in Figure 11.22. Task Details Task Details Task Name RouteDelete Task Description This task deletes the Protocols TELNET Rollback Document Data Sources Proutedeletedatasour Attributes Command Command Argum Prompt enable $UserInput$P config terminal no ip route $ Close Figure 11.22 Defining details of a new task in CSM. OSS for Telecom Networks T ask Audit Details Task History Task Name Last Executed Time Dec 06,2001 06:27:25 PM Device Na Start Time Finish Time Rollback S Task Status suresh Associated Devices Dec 06,20. Dec 06,2001 No Rollbac Success Close Figure 11.23 Task audit details or task history. 11.2.15.1 Viewing Task History We can differentiate between a task defined in the abstract and an instance of a task that was 