anagement station, the information model and the security and access control mechanisms for sharing management information EJB, Enterprise Java Beans; JAXP?; JNDI, Java Naming and Directory Interface; JFC, Java Foundation Classes; JSP, Java Server Pages; SAX,?; XSLT,?; ODBMS,? 11.2.1 Product Installation Cycle CMS offers a development environment to encourage the use of CMS as a platform on which a management solution can be built. AdventNet uses the concept of the "Configuration Management Experience" to explain how the complete product life- cycle needs of a management solution can be realised using the product. These lifecycle needs are captured in five steps (see Figure 11.4): 1. rebranding the management solution 2. customizing mediation services 3. customizing management services 4. integration and testing 5. packaging and deployment. 1. Rebranding: The application can be rebranded to display the name of the user's company, the name of its product and its logos. 11 Configuration Management Step 2 Step 3 Customizing Customizing Mediation Services Management Services Step 1 Step 4 Integration & Re-branding Testing Step 5 Packaging & Deployment Craft Interface Single Server Distributed Application on J2EE/JRE Server on as NAR J2EE/JRE Figure 11.4 Five steps in the "CMS experience". 2. Customizing mediation services: Southbound protocol services enable support for a number of southbound management protocols in the configuration man- agement system. While CMS supports standard management protocols out-of- the-box, developers can add a custom protocol provider in order to support any other protocol. Such support is often added during the implementation project, which is carried out in conjunction with an SI, for example, when it is discovered that the network critically relies on some old piece of network equipment that does not understand SNMP or any widely known management protocol. When this occurs, it usually does not pose a problem for an experienced OSS vendor or SI with a track record of implementing OSSs.