|
Java Low Level PMI APIs (JPMI)
|
Java application developers can implement and deploy Java SEM
applications for TMN FCAPS functionality.
|
|
OSS/J Quality of Service(QoS) APIs
|
SEM application developers will have the choice of using SEM OSS/J
implementation to achieve functionality such as performance monitoring
and fault monitoring in wireless telecom networks.
|
|
x86 PMI C++ libraries
|
This new feature will let C++ SEM application developers to implement
and deploy X86 based SEM applications and interact with SEM server
running on a SPARC(R) server to achieve OSS functionality.
|
|
64 bit PMI libraries
|
Used for developing 64 bit SEM applications
|
|
Enhanced tracing/logging in daemon processes
|
Aids in debugging customer specific problems
|
|
Reduced Cost of Ownership
|
New services can be implemented on top of the Solstice Enterprise
Manager infrastructure without modification to existing applications or the infrastructure itself. These services can then be distributed across a range of servers and low cost clients, minimizing the need for additional expense.
|
|
Core MIS process broken up into three constituent parts.
|
Allows for improved performance and trouble shooting of MIS processes.
|
|
Support for Solaris 10
|
SEM users can now take advantage of features in the most advanced
operating system available.
|
|
Scalable/Hierarchical MIS to MIS connectivity
|
This feature allows for almost unlimited scalability. By using MIS instances as hierarchical building blocks, a customer can create a management framework for an untold number of network elements.
|
|
3GPP now Supported with SEM
|
This allows SEM 5.1 users to adopt the popular 3GPP protocol for
management of their networks.
|
|
Rapid Service Creation and Management
|
Readily manage large, complex, global installations, adding and placing Management resources whenever -- and wherever -- they are required.
|
|
Secure Operational Management
|
Management policies can be securely implemented to lock out undesired or disruptive actions, and applications, features within applications, and devices or services can be restricted to management by authorized operators only.
|
|
Protocol independence
|
Standards-based, legacy, or proprietary devices can be managed from the same common foundation -- without requiring any modifications to existing applications or infrastructure.
|
