BA, RMI, TL1 Database Server CORBA Socket Applet Client RDBMS Back-end Module Front-end Module CORBA Socket Application Client Network Element Management (Mediation) Module Network Element Figure 11.2 Single server architecture. 11 Configuration Management A highly scalable CMS is one in which: a large number of clients are accessing management data from the NOC a large number of elements are being managed there is high frequency and complexity of configuration tasks there is tight integration - and much communication - with northbound NMS/ OSS/provisioning systems. In this case, a Distributed Server Architecture is most suitable (see Figure 11.3). CMS seeks to help developers to leverage many technologies. CMS supports proto- cols such as TL1, XML and SNMP out-of-the-box. It also has an interface that facili- tates the integration of other management protocols. Java and associated technologies are emerging as important means for building network management solutions for server- and client-side applications. Reasons for this trend include ease-of-use and the shortening of development cycles. More tools are becoming available to network management developers as the industry grows. Table 11.1 gives an overview of the technologies on which CMS is based. Other Applications OSS, NMS, EMS, (North bound Interfaces) JMX, XML, CORBA, TL1, SNMP, RMI Application Client Mediation Primary Server 1 Server 1 Server Applet Client Standby Mediation Server n Server n Server Mediation Tier Client Tier Scalability Load Balancing Firewall Support Configurable Deployment Thin client model Multi-Protocol Fail-over Hundreds of clients CORBA Support Server Tier RDBMS Main Mode Standby (Fail-over) Mode Managed Systems Database Tier Figure 11.3 Distributed server architecture. OSS for Telecom Networks Table 11.1 Technologies supported by CMS. Standard Version(s) Key benefits technology supported EJB simplifies the development of scalable and transactional middleware components. The EJB facilitates building deployable components where the c