A start up softswitch company was going after the midsize service provider market and decided to differentiate their product from the competition by shipping an EMS with their product. After considering several options, they elected to develop their EMS using NetMan technology as it was a fully J2EE based solution. The initial version of the EMS had "configuration" and "security" modules and because NetMan had pre-built components, they were able to develop their EMS in a short period of time.
Subsequently, they started trials at large service providers as well. One of the RFPs from a large ILEC had a requirement that the "EMS should handle 500,000 OIDs and up to 200 traps/sec". In addition, the ILEC required that EMS be fault tolerant and highly available.
Since "the response to the RFP" was due in a short period of time, the company had concerns whether their existing EMS, which was built to address the midsize market, was capable of serving the large ILECs and meet the requirements outlined in the RFP. There was no time to build another EMS and moreover it would be waste of money to have EMSs for different markets. They contacted Dhyan and were relieved to find out that since their existing EMS was based on NetMan, which was J2EE compliant, it could meet the requirements mentioned in the RFP with a few modifications (as an example, their existing EMS, which had MySQL as the database, had to be replaced by an Oracle database so that it could support the ILECs scalability requirements). Since NetMan supported application servers such as JBOSS, they were able to meet the high availability requirements specified in the RFP by deploying the EMS in a cluster configuration.