deploying and managing ip over wdm networks - Index of

for thresholds configuration, performance data collection configuration, threshold
crossing events, and QoS parameters configuration.
The ILOG Rule tool was used for collecting the alarms and finding their
root causes. In the same process, it was used for finding the service impacts of
the alarms and creating new alarms for the affected subnetwork connections.
9.11 Summary
Technologies and Tools 181
The WINMAN project aimed to develop an integrated solution for interdomain
network management. In order to create an open and standardized solution,
a component-based system architecture was selected.
A lot of effort was spent selecting the most appropriate tools for such system
development. Moreover, in many cases, more than one tool was selected to
demonstrate and suggest more than one development option.
In the operating systems area, the system was developed on a Windows
2000 operating system, which proved to be more simple and portable than other
options. It was ported also to a UNIX environment.
For the development language, the system development was done on two
object-oriented languages: Java and C++. Both languages proved to be valid
solutions, and our suggestion is to use the one that is more comfortable for the
development team.
As far as the middleware, two middleware tools were used for communicating
between the system components, CORBA and XML. XML proved to be
more helpful in describing the object, while CORBA was more helpful in mapping
the operations. Therefore our recommendation is to use XML only as a
descriptive language and to use the CORBA interfaces for negotiating between
the software components.
With respect to databases, the decision was to use a relational database, as
it is the standard in the industry to choose a simple freeware database and to
support an open interface. In this way, the WINMAN solution is database independent
and can be run with any relational database.
For the external interfaces, two protocols were used for communicating
between the systems. CaSMIM was used for communicating between the
NMSs, and MTNM was used for communicating between the NMS and the
EMS. This proved to be the right approach because the CaSMIM is more connection
and service oriented and MTNM is more equipment and configuration
oriented.
The GUI used Java as its display tool because of constrains that HTML
has in creating dynamic objects. The system did not support a Web client;
therefore, the right conclusion was to use the Java capabilities in drawing
dynamic views and receiving dynamic commands from the operator. All of the