band Applications Designer/Administration Tools Data Source Bean Builder Security Administration CLI Browser Batch Configuration Mib Browser TL1 Browser Device List Client Framework Application Client Applet Client Configuration Services Device Configuration API Configuration Client API Task Processing Task Manipulation Result Handling Combined Task Audit Rollback Tasks Protocol Services CORBA Audit Details Framework Services Pending Task Transaction Logging Authorization and Devices Communication Scheduler Authentication Backup Figure 11.1 Overview of AdventNet configuration management server. OSS for Telecom Networks CMS is customizable for specialised requirements and increasing diversity of the infrastructure. CMS is future-proof because its functionality can be extended by the connection of other products via software interfaces. Customization and extensibil- ity features include: Standards-based framework: Built over a scalable server framework that is based on standard technologies such as XML, EJB, JMS, JFC, JDBC, LDAP and HTTP. Customizable client: The clients are also developed over a generic AdventNet Client Framework that allows customization of the client software. Integration of new and proprietary protocols. Developer tools: Developer tools provide support through the entire lifecycle, from customizing and testing through to deployment and support. Figure 11.1 provides an overview of the AdventNet CMS. On the deployment architecture, if a configuration management solution requires management of less than 10 000 elements, and only modest frequency and complexity of the configuration tasks, then the single server architecture is most suitable (see Figure 11.2). In the single server architecture, the middle tier of the management solution, the servers, built on the CMS, is deployed to run in one Java Virtual Machine (JVM) process. This could be deployed on a Java Runtime Environment (JRE) or in a J2EE server environment, such as WebLogic or JBoss. Other OSS, NMS, EMS (North bound Interfaces) SNMP, COR