TMF814 Network Simulator

TMF814 Network Simulator
A standalone, Java-based network simulator for testing

communication over the network management protocol TMF814.
Master of Science Thesis
LOUISA LUCIANI
MIKAEL RIEDEL
Chalmers University of Technology

University of Gothenburg
Department of Computer Science and Engineering
Gteborg, Sweden, September 2010
The Author grants to Chalmers University of Technology and University of Gothenburg
the non-exclusive right to publish the Work electronically and in a non-commercial
purpose make it accessible on the Internet.
The Author warrants that he/she is the author to the Work, and warrants that the Work
does not contain text, pictures or other material that violates copyright law.
The Author shall, when transferring the rights of the Work to a third party (for example a
publisher or a company), acknowledge the third party about this agreement. If the Author
has signed a copyright agreement with a third party regarding the Work, the Author
warrants hereby that he/she has obtained any necessary permission from this third party to
let Chalmers University of Technology and University of Gothenburg store the Work
electronically and make it accessible on the Internet.
TMF814 Network Simulator

A standalone simulator for testing communication over the network management protocol
TMF814.
LOUISA LUCIANI
MIKAEL RIEDEL
LOUISA LUCIANI, September 2010.

MIKAEL RIEDEL, September 2010.
Examiner: Sven-Arne Andreasson
Chalmers University of Technology

University of Gothenburg
SE-412 96 Gteborg
Sweden
Telephone + 46 (0)31-772 1000

Gteborg, Sweden September 2010
Abstract
This thesis covers the process of developing a network management system simu-
lator with support for northbound communication over the CORBA-based protocol
TMF814. The simulator allows the user to import real data from an existing net-
work management system. The user can view and configure the data through a GUI.
The simulator acts as a TMF814 server for clients on higher management network
levels. Much of the focus in this project lies on the architectures modularity, which
can be divided into three areas: a graphical user interface, a northbound interface
and a database interface.
The intention of the final product is to facilitate TMF814 integrations, but parts
of the code can be re-utilized for multiple purposes. Modules can be attached and
extracted to make custom solutions that require either processing or visualization
of network management data or simply TMF814 server functionality. Developing
the simulator has lead to a deeper understanding of the protocol and its under-
lying structures. Therefore, experiences and pitfalls that might be useful for the
prospective TMF814 developer are shared.
As the comprehensiveness of the protocol revealed itself during the course of the
project, we have a final deliverable with a small portion of the server side function-
ality implemented. Apart from the server implementation, the product parses client
data and visualizes it graphically. At the end, we have successfully built a mod-
ular and maintainable platform, although more testing is necessary before we can
verify correct behavior. We are also left questioning interoperability, abstraction,
maintainability and legal issues of the protocols underlying infrastructure.
Keywords: Fault Management, OSS, Operation Support Systems, Network Su-
pervision, Network Management
i
Preface
This document contains a masters thesis for the Department of Computer Sci-
ence and Engineering at Chalmers University of Technology. The thesis will be
conducted in cooperation with Global Service Delivery Center (GSDC), Ericsson.
We will specifically be working with GSDC OSS integration, a team in Gothen-
burg, Sweden that provides integration solutions, customizations and support of
Operations Support Systems.
ii
Vocabulary
AM - Accounting Management.
CM - Configuration Management.
CORBA - Common Object Request Broker Architecture.
DBI - Database Interface.
EMS - Element Management System.
EOS - Ericsson OSS Simulator, this is the product developed during this project.
Sometimes referred to as the simulator.
FCAPS - Fault, Configuration, Accounting, Performance, Security.
FM - Fault Management
ME - Managed Element, network element in TMF814.
MLSN - MultiLayerSubnetwork, subnetworks in TMF814.
MVC - Model View Controller.
NBI - North Bound Interface.
NMS - Network Management System.
Northbound - Communication to overlaying systems.
OMG - Object Management Group, founder of CORBA.
OSS - Operations Support System.
PM - Performance Management.
SBI - South Bound Interface.
SM - Security Management.
Southbound - Communication to underlying systems or equipment.
TL - Topological Link, a network link.
TMF - TeleManagement Forum.
iii
Contents
1 Introduction 1
1.1 Background . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
1.2 Problem description . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.3 Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
1.4 Objective . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
1.5 Scope . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
1.5.1 Demarcations . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
2 Research 6
2.1 Network Management . . . . . . . . . . . . . . . . . . . . . . . . . . 6
2.2 ServiceOn . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
2.3 CORBA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
2.3.1 Overview of the architecture . . . . . . . . . . . . . . . . . . 9
2.3.2 IDL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
2.3.3 GIOP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
2.3.4 Object Services . . . . . . . . . . . . . . . . . . . . . . . . . . 11
2.3.5 Competing Technologies . . . . . . . . . . . . . . . . . . . . . 13
2.3.6 Alternative ORBs . . . . . . . . . . . . . . . . . . . . . . . . 14
2.4 TMF814 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
2.4.1 Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
2.4.2 Entry-point when implementing . . . . . . . . . . . . . . . . . 17
3 Method 20
4 Design and Implementation 22
4.1 Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
iv
4.2 GUI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
4.3 Northbound Communication . . . . . . . . . . . . . . . . . . . . . . 25
5 Results 30
5.1 Test Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
6 Discussion 34
6.1 Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
6.2 Frameworks and Library choices . . . . . . . . . . . . . . . . . . . . 36
6.3 Design Choices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
6.4 Concept and Client Value . . . . . . . . . . . . . . . . . . . . . . . . 39
6.5 Future potential . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
7 Conclusion 41
References 42
Appendices 43
- Database Schema
- Test Results
- Requirement Specification
- Java-Doc
- User manual
v
1 Introduction
Mobile and fixed broadband access is increasing rapidly throughout the world.
End users demand the ability to stay connected to anyone, at any time, regard-
less of location with high speeds and dependability. Consequently, the providers of
network-infrastructure must be able to manage and supervise their equipment in an
efficient way. Operational Support Systems (OSS) provide tools for managing net-
works and network elements. Managing a network includes monitoring the network
to detect problems, retrieving performance and inventory data, and configuring the
resources.
1.1 Background
The communication between the OSS and the network elements, ie. requesting
data, is called Southbound Communication. Today, Network Management Sys-
tems are often distributed, so they must interact with each other and be managed
by higher level systems. The communication to the higher level systems is called
Northbound Communication. In 2005, Ericsson acquired a majority of Marconi
Corporation [1], whos key assets include a tool suite called ServiceOn that provides
management tools on both a network- and element-layer for different types of net-
works including optical and microwave [2]. It has multiple interfaces for both south-
bound and northbound communication. For northbound communication, TMF814
is one of the most promising protocols. TMF814 is a CORBA-based protocol specif-
ically designed for network management.
To begin looking at the background of TMF814, one must look at the history of
its underlying architecture, CORBA. Originally, there were remote procedure calls
(RPC) to handle distributed communication. In the early 90s, much of the existing
middleware was tied to specific languages and platforms, and more adaptability
and functionality was required as distributed computing became more prevalent [3].
Creating communication between heterogeneous environments was very difficult.
A middleware called Common Object Request Broker (CORBA) was developed
by Object Management Group (OMG) in 1991 [4]. CORBA was a distributed
architecture that made it possible to design and implement a distributed object
oriented system as a group of modular components where complexity could be
hidden behind layers of abstraction. Initially, only a mapping to C was provided.
In 1997, CORBA 2.0 was released with a C++ mapping, followed by a Java
mapping in 1999 [4]. Around this time, CORBA gained a sufficient amount of
popularity and a standardized protocol was provided. During CORBAs growth,
developers began criticizing the complexity of creating CORBA applications. This
was mainly due to the inconsistent, comprehensive and complex API. The platform
had a steep learning curve and caused long development processes and high fault
rates, which was too expensive for many companies. Microsoft chose to compete
with CORBA by producing DCOM (Distributed Component Object Model), but
1
DCOM was not a big success either as it was platform dependent. Eventually
DCOM lost popularity and Microsoft returned with .NET remoting, and also the
publication of SOAP, which used the popular XML as the encoding for remote
function calls [5]. This caused some fallbacks for OMG. Today CORBA is growing
in the real time and embedded systems development market, and is commonly
used for communication between components within a companys network. In the
mean time XML, SOAP, Web services, and service-oriented architectures are gaining
popularity.
In history, you often see large corporations cooperating on standards to promote

efficiency, a scenario that benefits all. In 1988, OSI/Network Management Forum
was founded by eight leading telecom companies of the time to advance the avail-
ability of network management products [6]. In 1998, They changed their name
to TeleManagement Forum, and began a commitment to OSS standards. Today,
members include people from 700 different companies in 185 different countries. Al-
though many solutions are still built upon proprietary and custom technologies, TM
Forum is regarded as the most authoritative source for standards and frameworks
in OSS.
2
1.2 Problem description
Today ServiceOn allows the user to create virtual nodes. However, it can only
communicate northbound over TMF814 if the node is physical. The GSDC OSS-
integrations team works with customizations, integration services and solutions de-
sign of the product and often, a solution specific script will be created or an ad-
justment in the system will be made for a service provider. In order to verify the
expected outcome, tests need to be performed on a physical network. Using physical
network elements for testing is considered too expensive, so GSDC often performs
the tests on-site prior to the installation. Because the clients are located across
the world and the team often has a very small time-limit to assure the promised
functionality, they can not afford unexpected results.
Not only is this process costly and inefficient, but visiting a client and not be-
ing able to proceed with the integration is both a loss for Ericsson and for the
clients. Also, different network elements differ in functionality, for instance, in the
types of alarms they can send and in their configuration possibilities. Because the
virtual nodes in ServiceOn are not perfect representations of physical network ele-
ments, they can not be used for testing new integrations. This is why GSDC has
expressed a need for a virtual network simulator that communicates TMF814. The
desired outcome is a standalone application that simulates an optical network and
a manager on the Network- and Element- Management layer, depicted in Figure 1.
The simulator should be able to communicate with higher management layers over
TMF814.
Figure 1: What the simulator should implement in correlation to the

management layers. (EOS is the name of the simulator)
3
1.3 Purpose
The purpose of this thesis from an academic perspective is to develop a deeper

understanding of modular architectures using principles from object oriented design
as well as gaining some insight into CORBA and the protocol TMF814. This thesis
will also cover our design process and experience upon building a large architec-
ture with multiple technologies. Knowledge will be gained throughout the entire
life cycle of the product development, from idea to requirement specification to im-
plementation and distribution of the simulator. Although efficiency and usability
are important, the focus will mostly lie on the stability and modularity of the im-
plementation. This is because several subcomponents within this project, such as
parsing a data from a client database, might be useful to extract and use in another
context.
1.4 Objective
In this project, a simulator for a network elements and a northbound interface

will be developed that complies with TMF814. The application must work on
Windows Vista OS.
Modularity Because of the large scale and potential of the project, our primary
goal is to build an architecture that is scalable. Modularity is a fundamental part
of object oriented design and in our case it is not difficult to see the need for
decomposition of highly cohesive but loosely coupled modules.
Abstraction The functionality of a module should be characterized by a con-

tractual interface that captures the behavior of the module and allows polymor-
phism, to facilitate creation of new modules. Encapsulation will allow the imple-
mentation to be modified easily without affecting other parts of the system.
Performance The simulator should be lightweight and perform well, as it will

mostly be used on single and dual-core hardware.
Value Because the simulator will be used for testing purposes, the value of the
simulator relies heavily on its similarity to real networks. The only way to assure
similarity to real networks and catch all unexpected cases is to actually read real
network data. Our implementation will therefore include an interface for this. To
increase reliability, we will perform tests and quality assurance reviews.
Usability The information provided by the simulator must be easily accessible

through a graphical user interface with a high level of usability.
Maintenance Our goal is to develop code that is easy to understand and manage
post-delivery, to allow for adjustment of the system according to evolving needs. We
will therefore provide clean code and documentation.
4
1.5 Scope
TMF814 contains 456 functions divided into 15 packages (also called managers).
Because of the comprehensive amount of functions available for TMF814, the scope
of the project will have to be limited a certain amount of functionality. Because
simulation of fault management is a priority for GSDC, a partial implementation
of FM is considered a mandatory part of the feature-complete beta. The second
priority is to include some inventory management and configuration functionality
which will make the simulator more useful. Specifically, the Ems, ManagedElement
and Equipment Manager packages will be in focus.
An interface for connecting more mangers will also be developed, so that, for
example, the FlowDomain or PerformanceManagement manger could be developed
and easily integrated in the future. The simulator will include a GUI that displays
the content of the simulator in a clear and useful way. It should be possible for
the user to configure the parameters of the network elements, to send alarms and
modify the setup of elements and links that are being simulated. The simulator
should be able to populate its own database with information from other databases,
e.g. from a service provider. This should be done through an interface developed
during this project.
1.5.1 Demarcations
This project will not include full support for the entire protocol. Within the
time frame that is given for this project it is not reasonable to implement the
entire functionality. Also, the protocol is comprehensive and covers much more than
Ericsson requires at the moment. In order to avoid a death march work schedule,
the focus will lie on the previously mentioned managers(Ems, ManagedElement
and Equipment Manager), with agility in mind. These demarcations reflect on the
telecommunication areas as follows:
FM, Fault Management will be covered, this is the highest priority for Ericsson
PM, Performance Management will not be implemented during this project,
but could be added in the future if a module is developed using the interface.
IM, Inventory Management will only partly be implemented
CM, Configuration Management will only partly be implemented
The simulator should only be able to communicate northbound, in other words,

not southbound to actual network elements. The project doesnt include mapping all
the different types of databases the different service providers might use. However,
it will include an interface so that it is possible in the future to build an adapter
for an alternative database structure.
5
2 Research
In the following section we will briefly cover the concept of network manage-
ment, to create a broader understanding of what the final product in this project
is intended to be used for. In order to create system requirements and understand
the needs of the OSS integrations team, an analysis of the current product portfo-
lio must be done, which is what section 2.2 will cover. Section 2.3 will cover the
distributed architecture used in this project - CORBA. Finally, the last section will
describe the structure of the protocol TMF814.
2.1 Network Management
Telecommunication providers require Operational Support Systems to manage

inventory of their network equipment, for configuring the components and for man-
aging faults in the network. Effective management of a network infrastructure is
necessary to ensure the quality of their services. Part of Ericssons Solutions portfo-
lio consists of Network Management solutions for telecommunication operators that
need to improve operation efficiency. Network management refers to the adminis-
tration and maintenance of network elements in a system, and is commonly divided
into 5 categories known as FCAPS - Fault, Configuration, Accounting, Performance
and Security defined by Open Systems Interconnection(OSI).
At Ericsson, the solutions provided are separated into the following categories:
Fault Management
Performance Management
Inventory Management
Trouble Management
Revenue Management
All these solutions can be integrated with each other in a single custom solution for
a client.
Fault management acts upon error detection notifications by tracing and identi-
fying faults, along with information such as their probable causes and their severity
rate. When an alarm is triggered a notification is sent northbound to the overlying
system that can be monitored by a system operator.
The solution provided for Performance Management collects, processes, and

presents performance data in reports. This is interesting for clients because mea-
surements of network capacity and usage statistics can help the provider maximize
network performance to ensure better availability, reliability and quality.
The solution for Inventory Management displays information of the entire net-
work infrastructure in a single framework. It allows the provider to configure the
6
inventory, to report functions to users, to perform process modeling and to create
processes. Operators require inventory management to take care of operational is-
sues and spare parts management, so that they can have an accurate overview of
the network.
Trouble management solutions provide a set of tools that help the provider iden-
tify areas for improvement and facilitate taking the right steps to achieve opera-
tional efficiency. Trouble management supports Trouble tickets (a notification that
something is wrong), change requests (CM and planned action), work orders, per-
formance indicator reports and escalation of service level agreements (SLAs).
To take a step deeper into how these services are implemented, one must look
at the access methods and standards used for the communication of these services.
The protocols used for network management generally have to support multi-vendor,
multi-technology communication. Several access methods support network device
management, with some of the most common methods being SNMP, Windows Man-
agement Instrumentation (WMI), CMIP and CORBA. The type of access method
used depends on the type of information the needs to be transferred, security, reli-
ability, speed and other priorities that the service requester has.
7
2.2 ServiceOn
ServiceOn is a portfolio of Element, Network and Service Management tools

developed by Ericsson (formerly Marconi, acquired 2005). It is a modular platform
that provides functionality according to the recommendations from the FCAPS
model [2]. ServiceOn can also be used to mediate data to a clients custom Network
Managements System. ServiceOn has the ability to manage a broad mix of Ericsson
products in many areas, including:
Broadband Access
Microwave
Optical
Metro Ethernet
In addition to these modules ServiceOn Element Manager can manage 3rd party
SNMP based equipment. For communication with the network elements several
protocols can be used. For instance, ServiceOn is capable of communicating over
SNMP, TCP/IP and CLNS with network elements. All known network elements are
stored in a database. As for northbound communication (or middleware), CORBA
is used. In other words, the communication between the Element Management
Layer the Network Management Layer and the Higher Management Layer uses
CORBA based protocols. Figure 2 outlines the communication between the different
Management layers.
Figure 2: ServiceOn System Platform
8
2.3 CORBA
2.3.1 Overview of the architecture
CORBA is a middleware architecture designed by OMG used to ensure language

and platform-independent interoperability between a servers objects and a clients
method calls. CORBA applications allow communication within the same address
space as well as between remote address spaces. It follows the object-based model
as opposed to a pure client/server model or service model, by providing the client
with an encapsulating object-oriented interface. The object oriented approach is
good for protocols where the client and server know exactly what to expect of each
other (strictly defined in the protocol), so interfaces can simplify the client and
server development.
Figure 3 illustrates how a Server and a client communicate over an Object Re-
quest Broker (ORB). The Stub and the Skeleton serve as proxies for clients and
servers respectively. The ORB is the middleware that handles communication de-
tails between distributed objects.
The ORB handles:
Finding the object implementation for the request

Preparing the object implementation to receive the request
Communicate the data making up the request
Figure 3: IDL files produce interfaces towards the ORB.
A request is issued using an object reference, an operation name and a set of

parameters. This request is performed within the application code using IDL stubs
as an interface. When the stub routine is called the object reference for the target
object is mapped to the object reference as represented by the ORB.
9
2.3.2 IDL
CORBA uses an interface definition language (OMG IDL) to specify interfaces.

An interface includes operations that servers promise to perform on behalf of clients.
There is a specified mapping from OMG IDL to most of the popular programming
languages, including Java. The transformation between CORBA IDL definitions
and the target programming language is automated by a CORBA IDL compiler.
These are the specific files that the compiler creates:
POA file. The POA file creates a piece of the ORB that manages the server-side
resources. Acronym for Portable Object Adapter. The POA file is also called
the server skeleton. A local servant extends this class and implements the
functionality. The POA can activate and deactivate the servant depending on
its usage.
Stub file. The client stub implements the Java interface.
Java interface. Java version of the IDL interface.
Helper file. Responsible for reading and writing the data type to CORBA
streams.
Holder file. Delegates to the methods in Helper for reading and writing.
Operations file. Contains the methods from the IDL file, which is shared by
both the stubs and the skeletons.
The POA files servant is responsible for executing the objects operation. It can
be activated and deactivated. The servant is encapsulated behind the interface and
thus visible only to the server.
CORBA also provides an alternative method of invocation, namely Dynamic

Invocation Interfaces (DII) [7]. DII provides an interface that allows requests to
be dynamically built (in other words at invocation time, but not at compile time).
DII was designed to enable requests to be issued by programs that were created
before the interfaces for the operations were designed. The server sides analogue to
the client sides DII is called DSI. Just like DII, the DSI allows an ORB to deliver
requests to an object implementation that does not have compile-time knowledge
of the type of the object it is implementing. The client making the request has no
idea whether the implementation is using the type-specific IDL skeletons or is using
the dynamic skeletons.
2.3.3 GIOP
In the OSI model, CORBA lies below a vendor-produced protocol (TMF814 in

our case), and above GIOP (General Inter-ORB Protocol), which in turn is above
the transport layer. Upon the request, the client uses the IDL stubs in the same
way that it would have used a call to a library function. When the stub routine is
10
called, the target object is mapped to the object references represented by the ORB.
The ORB is then responsible for locating the object implementation and routing
the request to that implementation, as well as returning any results back. GIOP
is an abstract protocol that allows for ORB interoperability, and can run on top
of virtually all transport-layer protocols. The Internet Inter-ORB protocol (IIOP)
is essentially GIOP that runs over TCP/IP. IIOP is incorporated in CORBA and
defined as the standard, so it will be the protocol rather than GIOP to look more
closely at.
IIOP defines a set of data formatting rules, called Common Data Representation
(CDR). Objects publish identities and locations through Object References, which
in IIOP are called Interoperable Object References (IOR). When a client wants to
access a CORBA object, it first obtains an IOR for that object. Using the IOR, the
client can then invoke methods on the object.
2.3.4 Object Services
Because of OMGs approach to keep components modular, some functionality

that is needed for building applications upon CORBA require domain-independent
interfaces, which OMG calls Object Services. Object Services include Naming,
Event Notification, Life Cycle and Persistence Services [7].
Naming Services allow a name to be bound to an object within a certain

naming context.
Event/Notification Services provide a facility for delivering event information.
Life Cycle Services include creation, deletion, copying and moving of objects.
Persistence Services provides management of CORBA objects persistent state.
The Naming Service acts as the first connection point when a client wants to
connect to a server. Since the IOR that is generated looks different each time the
server is started, it is important that the client has the newest version each time
it tries to establish a connection. The Naming Service provides the newest version
of the servers IOR-string and can give it to all clients that want to connect to the
server. If a server is restarted and thereby a new IOR-string is required the server
simply registers the new IOR-string at the NameService. The Naming Service then
replaces the old string with the new one. In this way the clients easily can access
the server with the latest version of the IOR-string.
To be able to handle many different servers on one single Naming Service, a tree
structure is used to guide the client to the objects that are relevant. This structure
resembles the structure of a file system. Naming Service employs a tree structure
of Naming Contexts (see Figure 4). Naming Contexts have a name of their own
and resemble directories in a file system, where they can be nested within each
other. Naming Contexts specifically employ name-value tuples, where names are
11
structures with an identifier attribute and a kind attribute and values are object
references. Names must be unique within a Naming Context (just like files within a
directory). Object references can exist directly in the root of the tree or within any
of the underlying Naming Contexts. The binding between a name and an object is
called a name binding. The server implementation is responsible for building this
tree. The binding of a name to an object is done using the bind operation defined
in the NamingContext Interface. To be able to resolve a name the client must know
the path of Naming Contexts and the final name it wants to resolve. The Objects
are also referred to as bindings, because they contain the IOR-string that is bound
to the actual server object. When resolving the IOR-string, the client can create
references to the server through the orb.
Figure 4: An illustration of the tree structure produced in Name Service.
Notification Services is an extension to Event Services, and is specifically de-

signed for decoupled messaging. For example, the parties involved do not have to
know about each other. One can simply subscribe to a channel that another party
broadcasts upon.
Notification Services defines three roles; the supplier, the event channel and
the consumer. The supplier pushes event data to the channel and the channel
pushes the data to consumers. The channel can also pull data from the supplier
and the consumer can pull event data from the event channel. The push and pull
functionality is built into the EventComm Module. The EventComm module defines
four interfaces. The interfaces PushConsumer, PushSupplier, PullConsumer and
PullSuplier. These interfaces include push or pull/try pull as well as a disconnect
12
function. An EventChannelFactory object is used to return an object reference
that supports the eventChannel interface, which in turn defines the administrative
operations:
ConsumerAdmin: a factory for adding consumers

SupplierAdmin: a factory for adding suppliers
An operation for destroying the channel.
The Event Notification Service specifies interfaces, and not implementation de-
tails. This is necessary to allow different implementations to provide different qual-
ities of service (QoS).
2.3.5 Competing Technologies
There are three common types of middleware [8]:
Remote Procedure Calls (RPC)

Message Oriented Middleware (MOM)
Object Request Brokers (ORB)
In Remote Procedure Calls the client makes calls to procedures running on re-
mote systems. In message oriented middleware, messages are sent to the client
which are stored until they are acted upon. Object Request middleware makes it
possible for applications to send objects and request services in an object-oriented
system. When Remote procedure calls use object oriented principles, the term
Remote Invocation or Remote Method Invocation is used.
Although web services are gaining popularity in the distributed technology mar-
ket, object-based distributed technologies have the niche of being designed for use
within an organization or a small number of collaborating organizations. Before a
client can communicate with a server, object based systems must know the initial
naming context, but they generally have the advantage of low verbosity and supe-
rior performance, both in bandwidth and processor usage compared to service-based
systems.
If we look at the distributed object-based technologies, three of the most domi-

nant competitors are:
CORBA - Common Object Request Broker Architecture CORBA is the

most widely used standard in the non-Windows Market.
.NET remoting is a standard developed by Microsoft
Java RMI - Remote Method Invocation Protocol is a standard developed
by Oracle (formerly Sun Microsystems, aquired 2009)
13
What the three have in common is that they provide an abstraction of complex
networking implementations so that the developer can concentrate on business logic
in an object oriented manner. They all provide interfaces that marshal the param-
eters and send them through a wire protocol to a remote system where an interface
resembles the marshaled parameters and calls a function that returns an object.
The three technologies differ in the way they handle invocation of objects,
garbage collection, security object identification and many other areas. They each
have a unique network protocol and their own set of component models. The most
relevant differences though are interoperability issues. While .NET Remoting can
be used for cross-platform communication, but is optimized for communication be-
tween .NET based applications [5]. Furthermore Java RMI, only complies with
servers and clients implemented in Java. The main disadvantage of CORBA how-
ever, is that being both language- and platform- independent, along with almost two
decades of new features [4] while maintaining backwards compatibility have led to
a large, complex system. This leads to an exhaustive amount of specifications, and
steep learning curve. Also, the interoperability of CORBA becomes questionable as
few vendors implement the entire functionality of the protocol.
The Internet Communications Engine, or ICE, was created by a small group of

influential CORBA developers [9], and is both simpler and smaller than CORBA.
Smaller, in this case, is a good thing, as few CORBA implementations have total
coverage of the protocol. ICE also has a strong performance advantage [10].
2.3.6 Alternative ORBs
ORB:s are available from a large number of commercial and non-commercial

organizations/vendors. Although OMG has defined standards in many areas for
example security services, it is up to the vendor to provide an implementation.
Usually, the implementations are simply a subset of the entire standard. Therefore,
vendors differ in the functionality they provide. Often, open source ORBs are less
complete, but using a commercial vendor is often an expensive alternative.
2.4 TMF814
TM Forum is one of the leading industry associations focused on IT for service

providers in the communications, media, defense and cloud service markets [11].
Several major companies and the leading developers in the industry collaborate to
develop standards. One of these standards is TMF814 Multi Technology Network
Management (MTNM). The protocol is specifically created for telecommunication
and supervision of equipment. It is comprehensive enough to satisfy all the members
of TM Forum by supporting all the different manufacturers, and their respective
equipment. The current version of this standard is TMF814 Multi Technology
Network Management Solution Set 3.5. It contains of the following documents that
14
can be found by members at TM Forum:
The Business Agreement - Document number TMF513

The Information Agreement - Document number TMF608
The Solution Set - Document number TMF814
The Implementation Statement - Document number TMF814A
The Solution Set document contains the interface (IDL files) for the protocol.
Therefore, an application that implements the MTNM Solution Set is said to sup-
port TMF814.
2.4.1 Structure
TMF814 is composed of multiple modules. Some of the bigger modules are man-
aged by a manager. The entry-point and the module that ties everything together
is called EmsSession. This module has the ability to provide the client with all the
other managers, if they are properly implemented.
Figure 5: Managers and modules for TMF814.
Figure 5 illustrates the different modules that build up the TMF814 structure.
EmsSessionFactory creates an EmsSession which is used to get access to the man-
agers. The managers inside the blue area, e.g. EmsMgr, ManagedElementMgr, Mul-
tiLayerSubnetworkMgr and GuiCutThrough, are mandatory managers and should
exist in all implementations. The other managers are optional. Modules that dont
have managers mostly contain data-structures and common data types. CORBA
15
modules (depicted in the orange area in Figure 5) are also found in the implemen-
tation code for TMF814.
2.4.1.1 EMS Manager

The EMS Manager represents the whole Element Management System.
The subnetworks and multilayer-routing areas, including network elements (Man-
agedElements in TMF814) and the links between elements (TopologicalLinks), can
be retrieved as lists by the client. This is the first step the client takes in order to
find out which elements the server controls. It is also possible to request all of the
alarms on the system (getAllEMSAndMEActiveAlarms and getAllEMSAndMEU-
nacknowledgeActiveAlarms), with some different functions to provide some basic
filtering. A total of six different functions can be used for alarms on equipment that
this manager controls. By using the correct function for the clients specific need,
the total amount of network traffic can be reduced. EMS Manager also includes
functions for managing, creating and deleting Topological Links (as they dont have
a manager of their own). This also applies to Alarm Severity Assignment Profile
(ASAP). The total amount of functions that this manager supports is 37, from which
5 are common functions that apply to all objects in this standard. A complete list
of functions can be found in Appendix D.
2.4.1.2 MultiLayerSubnetwork Manager

MultiLayerSubnetwork is a way of grouping the functionality for subnetworks,
which are called MultiLayerSubnetworks in TMF814. Each subnetwork may contain
multiple elements. A basic functionality that this manager provides is providing
the client with all the network elements within a specified subnetwork. All the
Subnetworks and Subnetwork connections (SNC), are created managed and deleted
from this manager. 19 functions are dedicated to management of SNCs in this
manager. Routing and Calls are also handled here. The total amount of functions
in this manager is 74, including the 5 common ones.
2.4.1.3 ManagedElement Manager

Each ManagedElement has several termination points, this is where actual con-
nections start or end. Termination points exist in different forms depending on the
equipment, but normally one ManagedElement consists of a set of Physical Termi-
nation Points (PTP) and a set of Floating Termination Points (FTP). PTPs and
FTPs are physical ports (that you can plug a cable into) on the ManagedElement.
Some equipment also has Contained Termination Points (CTP). CTPs are located
on a specific layer rate and are always contained inside a PTP or FTP. Most of
the functionality on this manager is devoted to terminations points, 25 of the total
40 functions. Other things that the manager handles are i.e. alarms on a specific
element, cross-connections within the element and grouping of termination points
(GTP).
16
2.4.1.4 EquipmentInventory Manager
Each Managed Element that is supervised by TMF814 can contain a different
setup of equipment. The equipment inventory manager provides the necessities to
model the different setups. Properties and placement are data that this manager
handles for each equipment-card inside the specific element. It also manages the
supported types of equipment in the different slots and holders, as well as the
replacements and upgrades that are needed on a managedElement. A total of 21
functions constitutes this manager.
2.4.2 Entry-point when implementing
The entry-point for TMF814 is, as previously mentioned, the EmsSessionFactory.

This is the object that the server registers in the Naming service, and thereby also
the object that the client asks for when trying to connect to the server through the
Naming service. When resolving object references in the Naming service TMF814
specifically requires the following NamingContext binding types:
Class (context binding)

Vendor (context binding)
EmsInstance (context binding)
Version (context binding)
EmsSessionFactory I (regular object binding)
Once the client has found the EmsSessionFactory, it invokes the operation getVer-
sion() to determine the exact version of TMF814 that the counterpart supports and
operates on. The set of functionality provided by the server differs between versions
mainly in the sense that later versions extend the protocol with more functional-
ity. When the version is known to the client, the client invokes getEmsSession().
This method creates a session between the server and the client. A user name and
password can be supplied as arguments to this method to increase security.
When a valid session has been created, it is up to the client to decide which
functions to use. If the client has support for and wants to use notifications to get
events pushed to itself from the server, the getEventChannel function can be called
from the session. This returns an event channel to the client, in which the server
can send events. According to the TMF814 protocol a push-driven model should
be used to minimize the stress on the server (which might be connected to multiple
clients simultaneously.
Figure 6 shows the traffic between a client and a server when the session is being
created. It is mainly composed of requests in coalition with the creation of the ses-
sion. Prior to the traffic depicted, the client had requested the EMSSessionFactory
from the NameService. Finally, the client can request whatever objects it wants. In
17
Figure 6: Example of how the client connects to the server. The blue
thread depicts the notification channel.
the case of figure 6 the client requests all subnetworks and their containing elements,
because it wants to draw the hierarchy-tree at session connection.
From the session it is possible to request different managers. The function get-
SupportedMangers() provides the client with a list of which managers the specific
18
server actually has implemented and thereby supports. All managers are returned
in a holder, Common IHolder. The client can, after retrieving this holder, narrow
the object to the specific manager that was requested. Figure 6 also shows the setup
of the event channel. This part is threaded and can thereby occur at any time in
aspect to getting subnetworks and elements.
Trying to use one function that is not yet implemented in the server will just
give an unknown CORBA exception or if the server is implemented well, return the
specific CORBA exception NOT IMPLEMENTED. The first one is a general excep-
tion. This occurs if the server does not throw an exception on each unimplemented
function. This exception can also mean that something unknown has happened
during this transaction of information between server and client. The latter is a
user exception which gives a hint to the client that the request was received, but
the function is simply not implemented yet.
19
3 Method
When developers have little or no experience with one or more of the funda-
mental technologies within a project, ideas that are initially formulated might con-
tain technical issues, conceptual flaws and/or implementation-related shortcomings.
The time it takes to implement certain things can be difficult to estimate. Also,
with vaguely specified requirements, the programmers must be able to have frequent
communication with end-users of the product and have the ability to change require-
ments as the problem is more understood and solutions are revealed. A project is
therefore naturally inclined to change throughout the development process.
Because the TMF814 is a fairly new competence-area for the GSDC OSS In-
tegrations team, and because this project is conducted by a small and agile team
of two, a linear process is not suitable. An iterative and incremental development
model is generally good for agility [12].
The process would consist of three major iterations:
First iteration. This iteration includes coding the underpinnings and setting the
architecture.
Feature-Complete Beta. The beta version includes all the major features re-
quired for user-testing.
Final product. This iteration includes final bug-fixes and adjustments based on
analysis of test results.
In each iteration, a design phase is followed by an implementation phase followed

by a testing phase. The first two iterations will have more emphasis on the design
phase, while the test phase will simply be a quality review. The final iteration
will use the design phase as an opportunity to receive feedback from the client in
order to make priorities about what should be added or changed before the product
is launched. The final test phase will include an acceptance test, but not unit
tests because of the time limitations. The acceptance test will be a tool for future
developers to grasp what is finished, what needs be fixed and what isnt part of the
final release.
Besides working incrementally, agility is achieved through the following method-

ology:
Frequent releases
Frequent communication with the client about needs
Maintainability is also important for this project, as the goal is to create a

platform for future products. Therefore, these parts are emphasized:
Transparency with the client about code and design choices
20
Documentation
Prioritizing simplicity and clarity in code
The project management process used in this project does not include pair-
programming, but rather separating tasks, communicating, and making design de-
cisions together. The benefit of pair-programming is a high quality code-review, but
the benefit of separating tasks is speed, which was an unfortunate necessity when
planning for a project with this scope and time-frame.
21
4 Design and Implementation
This section is separated into three individual parts : NBI, GUI, and the database,
because of their modularly, and independence of each other. In figure 7 the different
areas are color coded. The red part, NBI, could be replaced with another protocol-
interface without having to change anything in the database or in the GUI. The
same goes for the GUI and the database.
Figure 7: A simplified overview of the architecture of the simulator.
22
4.1 Data
This project involves simulating large amounts of network data, and naturally
requires a database to organize the data and handle relations between the content.
Our choice of database manager is MySQL, which, apart from taking the experi-
ence of the GSDC OSS Integrations team at Ericsson into consideration, has the
advantage of high availability [13].
A script client in Ericssons portfolio extracts database information from Ser-

viceOn servers and generates xml-files for each TMF function call. It does so by
making requests for data over the TMF814 protocol. The data received is thus
data that is accepted over the constraints of the protocol. By using the JavaScript
Client, a parser can then extract the XML information into attributes that can
be inserted into the internal database. Because access to the database is needed
from the parser, from the northbound controller as well as from the GUI, it is good
practice to wrap the JDBC function calls behind an interface.
Since the database interface contains all the functionality needed from both the
GUI and NBI, a large amount of functions have to be implemented. Writing all the
functions in a single class makes working with that class almost unfeasible. As the
file grew it was decided to split the class into multiple classes without disrupting
their interdependence. In this case, multiple inheritance would have been desirable,
but Java lacks support for this. In order to be able to split the implementation
into smaller files, chain inheritance is used. This is indeed an issue without a
perfect solution. The downside to chain-inheritance used in this manner is that
there might be an issue when adjusting dependent classes, and it abuses the nature
of Java. Nonetheless, the same maintainability issues exist in large classes as well.
Figure 8 shows how chain inheritance can look to solve this problem. The blue part
is an interface, while the green parts are classes. The file at the bottom of the chain
in Figure 8 implements the actual interface with all the functions. This file also
inherits implemented functions from the class above, which in turn inherits from
the class above itself, and works as a single access-point to all the functionality.
Figure 8: Chain inheritance.
23
In order to simulate TMF814 communication, and visualize it graphically data
that complies with the TMF814 standards is needed. If the database does not define
the correct constraints on the data, it is a risk that errors are not discovered until
the client system cannot decode the TMF814 function. Debugging this way involves
snooping the data traffic and does not always give an error message that can pinpoint
the direct source of the problem. The primary constraints to be implemented are
relational constraints.
Foreign keys prevent, for instance an alarm to be placed on a managedElement

that does not exist, which would be difficult to represent graphically. When a
managed Element is removed, all adjacent edges should be removed accordingly.
Certain attributes are expected, according to the standards, to be, for example
integers or values from a predefined list, although most attributes (such as owner)
are simply strings. The database will not provide completely fail-safe type-checking
as many of the attributes that pass through the protocol go under the generic type
Any. These attributes are simply placed into the database with the VARCHAR
type. Because the parser is extracting data that has been received over TMF814,
it is safe to assume in these cases that the received attribute-types are correct.
To summarize, the database will be strict on relational constraints but not type-
constraints. Figure 9 shows a simplified schema over the database showing only
tables and their relations.
Figure 9: The database architecture (only table names and their relations
are depicted). See appendix A for complete schema.
24
4.2 GUI
The functionality required for the project requires data access code, north-bound
communication code, and GUI code. In order to build a program that is as easy
to maintain as possible, a good software architecture is needed. In this project, the
data access code will be the center of the application, as it will go two ways: north-
bound over TMF814, and straight to the GUI. It is therefore appropriate to create
an interface between the database communication and the rest of the program.
GUI code can often be divided into data access code, logic code and presentation
code. The model-view-controller software architecture is one of the most quoted
architectures for graphical user interfaces and decouples the three types of code
included in the GUI. The decoupling makes the code easier to follow, requires less
copy-paste code, and makes small changes doable without having to change massive
amounts of code due to all the different dependencies. There is simply a function
call or and observable-observer relation between the blocks of code that one must
keep in mind when making changes.
There are several different libraries available for graph representation in Java,
and because these libraries are comprehensive and satisfactory for the need of this
project, three of the more popular ones was reviewed; LGPL, JUNG and Annas.
The choice to use JUNG (Java Universal Network/Graph Framework) was based
on the ease of its use for the purpose of simply generating an attractive editable
graph that contains node and edge information.
4.3 Northbound Communication
The decisions that must be made prior to the implementation of the north-
bound communication are what ORB to use, and what Services to use. In order to
avoid compatibility issues with TMF814 client programs within Ericssons portfolio,
OpenORB is used. Because every vendor adds extensions to the base CORBA
standards, interoperability problems can occur when IIOP is used to connect diverse
ORBs. OpenORB includes its own services including Notify (a Notification service)
and OpenORB Interoperable Naming Service (INS), which is a fully compliant
implementation of the persistent Naming Service, INS specified by OMG.
The first step in the implementation process of the NBI is to compile the TMF814
IDL files and include them in the Naming Service. Compilation can be done for
Java with Suns Java IDL (idlj). Then, we must initialize a CORBA connection.
Before running a CORBA application, the ORB must be started and a port number
must be given.
25
The sequence of actions performed in the connection consists of the following:
Initialize the orb object.
String [ ] args = new String [ ] { "-ORBInitRef " ,

" NameService = corbaloc ::1.2 @" +
" localhost :21234/ NameService " } ;
orb = ORB . init ( args , null ) ;
Reference to the root POA is retrieved and activated.
POA rootpoa = POAHelper . narrow (

orb . resolve_initial_references ( " RootPOA " ) ) ;
Because all Corba objects are generic, a function that looks like this are com-
mon after reference retrieval. The function narrow() is used to cast the object
reference to the correct type. Activating the root POA causes associated POAs
to start processing requests.
Instantiate the servant object.
Get the object reference associated with the servant. The object reference
contains an address, the name of the POA that created an object reference
and an object ID.
EmsSessionFactory_IPOAImp emsSF =
new EmsSessionFactory_IPOAImp ( ) ;
org . omg . CORBA . Object ref =
rootpoa . servant_to_reference ( emsSF ) ;
EmsSessionFactory_I emsSFRef =
EmsSessionFactory_IHelper . narrow ( ref ) ;
Obtain initial NamingContext and Register the servants with the Name-
Service.
Below you will find the syntax that the simulator uses to add the EMSSession-
Factory-object to the NamingService is shown. The model.getEmsName()
function returns the name of the system that the simulator simulates.
NamingContext ns = null , nc1 = null , nc2 = null ;
ns = NamingContextHelper . narrow (
orb . resolve_initial_references ( " NameService " ) ) ;
nc1 = ns . bind_new_context ( new NameComponent [ ] {

new NameComponent ( " TMF_MTNM " , " Class " ) } ) ;
nc2 = nc1 . bind_new_context ( new NameComponent [ ] {
new NameComponent ( " Ericsson " , " Vendor " ) } ) ;
26
new NameComponent (
model . getEmsName ( ) , " EmsInstance " ) } ) ;
new NameComponent ( "3.5" , " Version " ) } ) ;
nc2 . rebind ( new NameComponent [ ] {
new NameComponent ( model . getEmsName ( ) ,
" EmsSessionFactory_I " ) } , emsSFRef ) ;
Wait for invocation.
The initial communication between the client and the server begins with the
client requesting the is a() function. The function simply verifies that a CORBA
object is an instance of a class that implements the correct interface. It then requests
a list of the nameBindings in the Naming Context on which the operation is called
with the function list(). Once all the name bindings are listed, it can iterate through
them by requesting next one(). On each name binding, the operation resolve() is
used to return the reference bound to the specified name.
As expected (described in chapter 2.4.2), the client sent requests to resolve ref-
erences to the following names (id : kind) in their respective order:
Class (context binding)

Vendor (context binding)
EmsInstance (context binding)
Version (context binding)
EmsSessionFactory (regular object binding)
The client now has a reference to a TMF814 object. Because all the servant files
are initially empty, it is up to the developers to implement the desired functionality.
Once the client has a reference to EmsSessionFactory it will call the following
function which should return a reference to emsSession (by setting the parameter
emsSessionInterface):
getEmsSession ( String user , String password ,

NmsSession_I client ,
EmsSession_IHolder emsSessionInterface )
Now the client has a reference to emsSession which provides the all the session-
related functionality, including:
getManager ( String managerName ,

Common_IHolder managerInterface )
27
Which returns a reference to the given manager. As explained in section 2.4,
there are several managers in TMF814 that hold functionality for different parts of
the network. Now, which methods will be called, depends on how the client system
is developed and how it is used. The client might for example want to retrieve all
ManagedElements. The client would in that case request managedElementMgr and
call the function:
public void getAllManagedElements ( int howMany ,

ManagedElementList_THolder meList ,
ManagedElementIterator_IHolder meIt )
throws ProcessingFailureException {
As shown in the example function above, the function has no return value, but
rather parameters that expect content. The client defines a maximum number
of managedElements to retrieve by providing an int in the parameter howMany.
meList is where the server will place the list of ManagedElements, meIt will contain
the iterator that the client should use 1 if they were to decide that they want to
retrieve more.
The simulator would begin by retrieving all the managedElements from the
database. Then, it would create a list of objects of the type ManagedElement T
(specified by TMF814) by converting each attribute to the correct type and in-
stantiating the object. Because certain types have several layers of custom types,
creating the correct type can require up to a few hundred lines of code.
Then a new ManagedElementIterator is created. The reference to the iterator

is retrieved, which gives a handle to the object and the next n can be called with
howMany and meList as arguments. The code can be seen below:
it = new ManagedElementIterator_IPOAImp ( list , nbi , howMany ) ;
Object iterRef = poa . servant_to_reference ( it ) ;

meIt . value =
ManagedElementIterator_IHelper . narrow ( iterRef ) ;
meIt . value . next_n ( howMany , meList ) ;
nbi . managedElementIterators . add ( meIt . value ) ;
next n will then, depending on the integer value in howMany, remove a certain
amount of ManagedElements from its internal memory list and set: meList.value
= list. Now that the values meIt and meList are set by the server, the client will
receive these values.
1
The client retrieves more managedElements by calling next n(int howMany, ManagedEle-
mentList THolder meList)
28
The structure of the TMF814 interface implementation might seem slightly te-
dious, but the structure of the implementation will look similar for every object.
The only difference is the set of object types that builds up the element.
29
5 Results
The final product produced in this project is as planned a standalone OSS sim-
ulator. It can import foreign data from command-line as well as from the GUI (see
figure 10). Figure 10 to 14 shows some of the views in the simulator.
Figure 10: This is how the GUI looks when importing data from XML-
files.
30
Figure 11: An example on how the graph could look with seven managed
elements and seven links between them.
Figure 12: The Real Time Alarm View, showing alarms of different sever-
ity types.
31
Figure 13: This is the Termination Point view, showing all the TPs for
the selected managed element.
Figure 14: Showing the form for creating an alarm on the selected man-
aged element. This view is also used to alter and update alarms.
32
5.1 Test Results
In the final iteration, we produced an external acceptance test document (see

Appendix B). The document gives an overview of the functionality that works,
that still needs work and that has not yet been implemented. Note that the scope
of the functionality was altered as late as the final design phase. In the figure
15 below, you can see the proportions of finished, incomplete and unimplemented
functionality in final release of EOS. If we recognize all three parts of our project
as equally important, we have accomplished to implement 82 percent of the desired
functionality.
Figure 15: Finished, incomplete and unimplemented functionality ac-

cording to the Acceptance test for EOS in the third iteration. The
piecharts are separated by sections of the architecture.
Figure 16 shows the correspondence of finished, incomplete and unimplemented

functions in EMS Manager, ManagedElement Manager and MultilayerSubnetwork
Manager. Implementing the protocol entirely would mean implementing all the
functions in all the Managers.
Figure 16: Finished, incomplete and unimplemented functionality in

three of the managers in TMF814
33
6 Discussion
6.1 Problems
In this section, some of the complications experienced during the design and
implementation of EOS will be covered.
The first roadblock was discovering how to get a handle on the first object over
CORBA. As described in chapter 2.3, an object is requested from the server to
initialize the connection between the client and the server. The server should pro-
duce an IOR file for this object, but it is important that it is the right object. The
first object that should be requested is specified in the protocol, but finding spec-
ifications for this in the extensive documentation for TMF814 was not completely
effortless. After reading parts of the documentation, and capturing traffic between
the GUI client and a real system it eventually became clear that the first object
that the client will request from the server is EMSSessionFactory. The factory can
then produce an EMSSessions between the server and the client which is needed for
setting up a connection.
The next challenge was distributing the IOR information from the server to
the client that wants to connect. The simplest way of doing this the first time a
connection is being created is just to save the information to a file when the server
starts, and then point the client to this specific file. This is a fast way of testing your
connection in the beginning but of course this is not something that is sustainable for
larger systems. The solution for solving this so called Bootstrapping problem, that
is, how finding each other for the first time over a network is solved by NameService.
This service acts almost as a digital phone-book. If the name and path to the name
are known then the only thing left is to know were the NameService is located.
The service can handle several CORBA objects, and can be updated by the servers
to always have the newest IOR information stored. The location of the service is
public information that can be retrieved by any client.
The NameService has as described before a lot in comment with an ordinary

file-system. Unfortunately the service is not as advanced as a file-system, which
makes it challenging. With the right commands it is possible to:
search each NamingContext

add/bind objects to current NamingContext
add NamingContext to current NamingContext
update object information
remove/unbind object
remove NamingContext
The slightly limited functionality, compared to a regular file-system, makes it
34
a little bit harder to work with. The fact that NamingContexts are just Naming-
Contexts and not directories makes them a little bit different to work with. The
documentation regarding the used service from OpenORB is not up to date at the
time of writing and a lot of information is missing. Learning how to use this service
thereby requires try and fail before the correct syntax is found so that everything
complies with the TMF814 standard as described above.
A lesson that also was learned was that the protocol is strict about converting the
TMF814 objects to the right types. TMF814 has many of its own types, and most
of them are simple in nature, but a few contain several layers of custom data types.
Also programming for CORBA requires that you put your programming language
mentality behind, and think CORBA. Functions in TMF814 when compiled from
the IDL-files do not have a return types, something that Java normally has if values
are to be returned. The values are instead returned inside holders that are passed
along as arguments to the function. Its also important to remember that everything
is focused around the ORB. For example, one could normally create an object of
type Any with the following code:
Any a = new Any ( ) ;

a . insert_Value ( V v )
But CORBA requires the following:
any = nbi . getOrb ( ) . create_any ( ) ;

V_THelper . insert ( any , v ) ;
When working with a system that is dependent on input from another system,
the transition must be performed gracefully. Another fundamental issue experienced
during the course of this project was to actually have input data. The data used was
created by the previously mentioned Script Client that generated XML files. This
data was however not complete until the end of the project, which made it hard to
know exactly how the correct data could look and how it should be handled. Some
of the scripts that the Script Client uses had to be rewritten to work properly,
something that was outside the original scope but was necessary to be able to
retrieve real correct input data.
To be able to display all the data from the database in an efficient and user-
friendly way a lot of the models for standard objects had to be rewritten. Standard
cells in JTable do not change color depending on the value of the perceived severity
in the alarm table case. A custom model for displaying data had to be written.
Even third party libraries had to be rewritten to some extent to be able to get the
best result.
Since the architecture requires that northbound TMF814 should be a separate

part, the program loads all modules that implements NBI.java at startup, if no
interface is found then only the GUI- and database parts will be available to the
35
user. This proves that the different parts actually are modules. Other protocols
that looks almost like TMF814 could also be used as long as they implement the
given interface. The northbound interface for TMF814 is managed and developed
as a different project, which is loaded in to the simulator through dynamic loading
of classes in Java.
One other problem that occurred during this project was finding the exact way
that alarms should be created. Alarms are specified with the CORBA-specific type
Structured Event. The structure is defined and documented, but many of the fields
are built up with the type called Any. This type is basically a container for any other
type or object. This makes Javas type checking unable to verify that everything
inside the Any-object correct according to the CORBA structured event type. If
an alarm is created with faulty data in one of the Any-objects, errors will occur
on the client side, but the server will not be notified. Because the clients used for
testing were not implement during this project , it made troubleshooting very hard
and time consuming. It was not straightforward whether the clients implementation
was faulty, the version was different or our data was built the wrong way.
The software engineering method used was generally very good, but 4-5 iterations
would have been better for the scope of the project. This mostly because of the steep
learning curve in the beginning, which resulted in much of the massive functionality
being implemented in the final iteration. This led to a very relevant test phase being
left to be handle by those who choose to keep developing the product.
6.2 Frameworks and Library choices
The choice of programming language for this project is, as always, questionable.
Being a standalone product, the only initial restrictions on the language were ef-
fective communication means to large sets of data and CORBA-support. Ease of
access to the runtime environment as well as client competence (potential team
of future developers) also had an important role in the choice of language. With
multiple languages supporting the first two restrictions, a choice was made based
on the simplicity and competence factors. Nonetheless, Java has some limitations
that have effected our project. E.g. Java lacks multiple inheritance. When a single
class became too large to be manageable, and functions within the class were inter-
dependent, the only options are to simulate multiple inheritance. This is done by
allowing an interface to extend multiple interfaces, which in turn are implemented.
This would cause the library to be filled with twice as many files. A choice that
might seem best for the object-oriented fundamentalist, as well as for the architect,
but inconvenient for the developer.
In the industry, NoSQL databases are becoming more relevant alternatives to

classic relational databases because of their speed, agility and the fact that they
support a distributed architecture [14]. While speed is important in EOS (retriev-
ing thousands of contained terminations points can cause delay), neither agility or
36
distribution are arguments that are important enough in this project to choose a
non-relational storage type. NoSQL, requires that much of the logic that is handled
by databases is programmed on a higher level. Also, because this project requires
data from client SQL databases and is restricted by the standards of TMF814, the
data received is structured in a way that is appropriately placed in a relational
database. Because of the simple hierarchical nature of the data in TMF814, the re-
quirements needed for the project were supported in both PostgreSQL and MySQL,
and performance differences between the two are small enough that the choice of
MySQL in this project had no obvious negative impact.
Although using CORBA was not a active choice, it is indirectly a choice made by
TM Forum due to the fact that TMF814 is based upon CORBA, and it is interesting
to see how this architecture has effected the progress of the project. As mentioned
in chapter 2.3, CORBA has a steep learning curve because of the massive amount of
functionality to filter through before grasping the relevant information. Naturally,
documentation of this size rarely are up to date on every aspect, which was the case
for CORBA at the time of writing.
In chapter 2.3.1, we mentioned that the object oriented approach is good for
protocols where the client and server know exactly what to expect of each other
(strictly defined in the protocol), so interfaces can simplify the development. Our
experience is that this simplification refers to development in the long-term. Setting
up the CORBA connection and getting a handle on the first object is not a simple
process. TMF814, is not a small protocol, however the steep learning curve, and
the time it takes to initialize a connection would make it pointless to make a small
protocol based on CORBA. The advantage of using a CORBA based protocol is
that now when the setup is complete, the security and connection is encapsulated
from the developer and all we have to think about is implementing the methods. It
is as if the objects handled are local.
Another negative aspect experienced was the unnatural mapping to Java. Com-
piling the IDL files to java classes worked well, but the code was not what the Java
developer would naturally expect. One example was that all the functions had the
return type void. Instead of returning an object, the parameters of the function
contained values that the server had to set.
As mentioned previously, IIOP interoperability has not always been failsafe.

Basic ORB functions will work cross vendor, but because of extensions to the stan-
dards, a problem could arise in the future of the product due to this. Also, if the
TMF814 protocol changes, which it is prone to do, both the server and the client
must recompile their IDL files. Typically the server will crash if they have different
versions of the protocol.
The experience with TMF814 is that the specifications are well-written and fairly
well-structured, but that guides and tutorials are missing. Also, the type specifi-
cations cover the entire protocol, which forces the new developer to filter lots of
information before finding certain fundamental type descriptions and action de-
37
scriptions. There is a forum, but most of the active members discussed very specific
questions, and there was no thread for beginners. Type and action specifications is
really what defines the protocol, but the types defined can cause problems in their
mapping to some languages, in this case Java. There are no information about the
protocol available if you are not part of the forum, TM Forum.
The CORBA standard and TMF814 both have something in common. They
are complex, and comprehensive. In the case of CORBA, the promise of seamless
interoperability is threatened by incomplete ORB implementations. In the case of
TMF814, seamless interoperability is threatened by incomplete protocol implemen-
tations. This would not be an issue if the server and client were implemented by the
same developers, but that prerequisite and our experience with the time it takes to
implement a subset leaves us questioning the quality of the standard.
Legal limitations should also be taken into account. In April 2009, Sun and
Oracle announced an agreement regarding Oracles acquisition of Sun. Sun has
an early history of lawsuits, a privilege that the new owner knows how to take
advantage of. In August 2010, Oracle announced a patent infringement suit against
Google for 7 violations of Oracles Java-related intellectual property and a copy-
write infringement. Although the Java license is free and under a GPL license (apart
from the Enterprise and ME version), the license does not allow sub-setting or super-
setting (adding anything on top of the specification or implementing only parts of
the specification). In Googles case, it was mainly regarded their virtual machine for
Android called Dalvik, which Oracle claims contains customized JVM code. How
Oracle chooses to interpret deviation from the specification is not completely clear.
Does it include customizing libraries? Although this project does not deviate from
the license conditions, and will not be a consumer product, it is important to see
that there is a considerable degree of legal uncertainty that should be taken into
account.
Java is not the only technology in which a question of reliability arises. By buying
Sun, Oracle also acquired MySQL, an important competitor to their main product
- Oracle Database. With two competing technologies under the same company
the competition becomes threatened. Although Oracle has promised to continue
their support for MySQL, chances are that the open-source community contributing
code to the project might diminish. Therefore, the future remains uncertain. The
licensing policy of MySQL states that upon developing and distributing open source
applications under the GPL or OSI-Approved License, no fees must be paid. [13]
Again, developing a product for internal use is not affected by the license, but it is
important to bear in mind for future strategic decisions.
6.3 Design Choices
Once the project had gone on for a while, it became clear that some of the files
would become very large, making them almost impossible to work with. As men-
38
tioned earlier in chapter 4.1, Java does not support multiple inheritance. Splitting
up the implementation of the database interface for MySQL was really necessary to
make it workable. One could discuss if this is the correct way of solving the prob-
lem with respect to the Java best practices. In our case, not splitting up the file
would have resulted in a large file that grows linearly with the scope of the project.
Working with large files makes development inefficient. Its hard to find relevant
sections of code, and it can easily become unstructured.
When it comes to the GUI design and the general look and feel, it was decided
that the simulator should resemble the system that was simulated. This makes it
easier to use for someone who is familiar with ServiceOn. A tree to show structure
of subnetworks and elements, but with the big difference that TPs where moved
to a separate main-window. A managed element could have many thousands of
TPs, which would make it hard to use in an ordinary tree. Our solution to this
was to show TPs in a table instead, which makes it easier to use and work with.
The table handles large amount of data in an more efficient and user-friendly way.
Even the alarms are shown in a table in the main area. This area is the biggest
area, making it possible to show the most data here. This table was equipped with
filtering capabilities much like in SerivceOn to making it easier to find the specific
alarms. Regular expressions could be used for fast filtering on all the data in the
table.
To be able to meet the initial requirements regarding modularity and abstraction

interfaces were developed between the clear parts of the simulator. One interface
towards the database and one towards northbound communication. This means that
without changing anything in the program itself the database could be swapped for
another database, as long as the new one implements the interface. This is of course
true even for northbound communication. The simulator could handle many NBIs
at the same time, all because of the interface between the simulator and the actual
northbound communication. The simulator is even so modular that it handles
adding and removing NBIs without having to compile anything, as long as all NBIs
specified follows the interface.
6.4 Concept and Client Value
Initially, it was unclear as to which extent of value the product would generate.
Through frequent communication with Ericsson, this project has been able to take
shape into a useful framework. The simulator is a product which Ericsson will be
able to use internally for testing and perhaps externally. At times, only parts of the
product might be useful, for instance reading client data locally and displaying it
graphically. It can also be used simply to create objects and send it over TMF814.
Because the GSDC OSS Integration is composed of people with diverse developing
experience, certain members will be ready to use the product right away. However,
those who do not have the time or experience to customize our implementation
programmatically would appreciate a launch where more testing has been performed
39
to minimize the risk for unwanted surprises. Refining the current product with
the current available functionality for sales purposes would require 80-240 hours
of development depending on the requirements of the client. Because the learning
curve for development over CORBA is steep and bends, a loss of competence is
difficult to replace with documents and would therefore prolong the process.
6.5 Future potential
There is a massive amount of functionality that could be added to the final

product. The first step in continuing with the development of the simulator would
be to go through one more iteration to polish the current functionality. When this is
done, the developer in question might want to spend time on making the parser more
intelligent. The optimal parser would take in everything it could, and if an attribute
does not comply with the standard, it could give the user a choice as to whether or
not it should be imported. Error descriptions could be better. Because we never
know what kind of data the client system has, it is especially critical that the parser
is tested with multiple systems. When it comes to the graphical user interface the
next step to take would be to perform usability tests and undergo another iteration.
The Northbound interface code can be enhanced with more implemented functions.
However, as the results imply, implementing the entire TMF814 protocol would
take a long time. Also, extending the NBI with functionality means that extensions
must be made in the GUI and DBI accordingly (unless the intentions are to use the
NBI implementation independently).
40
7 Conclusion
One of the main purposes of this thesis was to develop a deeper understanding of
TMF814 and the surrounding protocols. We have gained experience throughout the
product cycle, and a summary would be that we have worked with a protocol which
requires lengthy development time in relation to the functionality achieved. Both
CORBA and TMF814 require a combination of theoretical experience, patience and
perseverance, but in the long run, a comprehensive middleware will be able to carry
the information necessary for Network Management.
The other main purpose with this project was to build a stable architecture.
Being able to attach and detach modules was something that we based the architec-
ture upon, and we can now see on the final product that we indeed have a modular
structure. Along with Modularity, we have built the implementation to be modified
easily without affecting other parts of the system, and thus achieved encapsula-
tion of the more complex logic. Although we have not had any problems with the
performance or the usability of our simulator, we have realized the importance of
testing. We have only run our implementation on three different laptops, with three
different sets of client data, towards three different clients. There is still much to
do before we can say anything about performance.
Usability testing always has a strong positive effect on the value of the product, so
this is also something that should be performed in the near future. Our main efforts
for maintainability involved clean code, open communication, comments, javadoc
and a manual. Through frequent communication with Ericsson we have adjusted
the product according to evolving needs and been able to produce a product that
can be and already is valuable to them in multiple ways. It is also a platform that
can be used for alternative purposes. We succeeded in importing and visualizing
real network data, which alone is useful when preparing for an integration. Having
a lightweight TMF814 implementation that the GSDC OSS Integrations can cus-
tomize and test upon is also an excellent way to build knowledge within the group
and prepare for a real solution.
41
References
[1] Ericsson forvarvar merparten av Marconis verksamhet inom telecommunika-
tion, http://www.ericsson.com/se/releases/20051025-1017516.shtml, accessed
on 2010-03-26.
[2] ServiceOn Element Manager Element Management Layer, Ericsson AB,
1/28701- FGC 101 0736 Uen Rev A 08/04/2009.
[3] George Coulouris,Jean Dollimore, Tim Kindberg. Distributed Systems Concepts
and Design, Pearson Education Limited, Harlow, England, 4 Edition, 2005.
[4] History of Corba, Object Management Group,
http://www.omg.org/gettingstarted/history of corba.htm, accessed on
2010-04-20.
[5] D. Esposito. Design and Develop Seamless Distributed Applications
for the Common Language Runtime, Microsoft Developer Network,
http://msdn.microsoft.com/en-us/magazine/cc188927.aspx, accessed on 2010-
05-07.
[6] TM Forum Milestones, TMForum, http://www.tmforum.org/Background/1086/home.html,
accessed on 2010-04-27.
[7] J. Rosenberger. Sams Teach Yoursef CORBA in 14 days, Sams Publishing,
1998.
[8] Middleware Resource Center, Defining Technology Inc.,
http://www.middleware.org, accessed on 2010-04-22.
[9] ICE official website, The Internet Communications Engine,
http://www.zeroc.com/, accessed on 2010-07-01.
[10] M. Henning. Choosing Middleware: Why Perfor-
mance and Scalability do (and do not) Matter, ZeroC,
http://www.zeroc.com/articles/IcePerformanceWhitePaper.pdf accessed
on 2010-06-29.
[11] TM Forum official website, TM Forum, http://www.tmforum.org/, accessed
on 2010-03-22.
[12] D. Sotirovski, Heuristics for iterative software development, Software, IEEE,
vol 18, issue 3, 2001, pages 66-73.
[13] P. DuBois. MySQL - The definitive guide to using, programming, and admin-
istering MySQL 4.1 and 5.0. Sams Publishing, Indianapolis, Indiana, USA, 3
Edition, 2005.
[14] NoSQL official website, NoSQL, http://nosql-database.org/, accessed on 2010-
07-02
42
Appendices
A - Database Schema
B - Test Results
C - Requirement Specification
D - Java-Doc
E - User manual
43
Appendix A Database Schema
Appendix B Test Result
Description P F N/A Comment
1.0 DATA
The parser has been tested on data created in the
simulator, extracted through the Script Client and
then parsed through the parser. Data from real
systems has been tested as far as we have got our
1.1 Parser hands on such data.
Import EMS information from xml-files produced by
the script-client through the command-line interface.
Import Subnetworks from xml-files produced by the
script-client through the command-line interface.
Import ManagedElement information from xml-files
produced by the script-client through the command- The script produces multiple files with MEs, one for
line interface each subnet.
Import Topological Link information from xml-files
produced by the script-client through the command-
line interface.
Import PTP information from xml-files produced by
the script-client through the command-line interface.
Import CTP information from xml-files produced by If you use the custom javascript, it will produce
the script-client through the command-line interface. several CTP files
Import All EMS and ME Alarm information from xml- The parsing works (But the Script Client cant
files produced by the script-client through the serialize structured events at the moment, but that
command-line interface. is outside of the scope for this project.)
Import Cross Connection information from xml-files
produced by the script-client through the command-
line interface.
Import SNC information from xml-files produced by
the script-client through the command-line interface. Not implemented in parser yet.
Data import can be performed from the GUI.
Warnings in GUI-import when a file is corrupt, or can
not be read.
Warnings in GUI-import when data does not comply
with TMF814 standards, for example, an alarm on a
managedElement that does not exist.
The GUI displays correctly how many objects were an object is not imported if a regular attribute is
imported into the database. wrong, but if one of the attributes that has several
values (such as additional Info) fails, the object is
STILL imported, and just skips the additionalInfo
and sends a warning.. but on the GUI it will say for
example 4 out of 5 objects were parsed.
Custom javascript for scriptclient that generates the javascript file for managedElement does not
correct xml file for corresponding info. handle the data optimally, this is because it
requests all subnetworks first, followed by all
managedelements under that parser. The xml data
produced by this is not parsed easily, so an quick
solution was to split the data into files for all
managedElements under a single subnetwork.
A popup should warn the user that the database

2.1 Panel File > new Project: should empty the database will be emptied!
File > save Configuration: should save debug level, A popup could appear afterwards saying
2.1.1 alarmorder to Config.java "Config.java has been saved"
A popup could appear afterwards saying
File > reset configuration: should reset Config.java "Config.java has been reset"
File > realign: should sync the GUI with the A popup could appear afterwards saying "EOS has
database content synchronized with the database"
MainView > RTAM: will display RTAMView
MainView > TP: will display all TPView
MainView > Map: will display MapView
Northbound Interface shows up if there is a zip file
in the NBI directory
NBI > connect
NBI > disconnect Not able to unregister the EMS from NameService
This works, but we have only one NBI to test on, it
NBI > connect all should work for multiple NBIs
Services > Start: should restart Notification and
Naming Services Only tested for the TMF814 interface
Services > Restart: Notification and Naming services
should be restarted TODO in MainController.java row 196
Services > Stop: Notification and Naming services
should be stopped TODO in mainController.java row 192
Implemented, but should be filled with meaningfull
Help > About page text
TODO in MainController.java row 235, also, change
Help > JavaDoc (for EOS) name from OSSSim to EOS
Help > JavaDoc (for TMF814) TODO in MainController.java row 244
Help > visit homepage and Help > visit TMForum
homepage
2.2
TreeView Ems name shows up in the treeView
Subnetworks show up in the treeView
ManagedElements show up in the treeView
ManagedElements with a heartbeat are green,
otherwise red
right-click on EMS > EMS info: lets you view and
configure EMS info
right-click on EMS > Create MultiLayerSubnetwork
right-click on EMS > Create Alarm/TCA
right-click on a MulitLayerSubnetwork > EMS info
right-click on an MulitLayerSubnetwork >
MultiLayerSubnetwork info
right-click on a MultiLayerSubnetwork > Create
Alarm/TCA
right-click on a MultiLayerSubnetwork > Delete
MultiLayerSubnetwork
right-click on a ManagedElement > EMS info
right-click on a ManagedElement >
MultiLayerSubnetwork info
right-click on a ManagedElemnet > ManagedElement
info
changing the name of a ManagedElement in the tree
updates the map
right-click on a ManagedElement > Create
Alarm/TCA
right-click on a ManagedElement > Create PTP/FTP
right-click on a ManagedElement > HeartBeat >
Disable/Enable (should change the connectionState)
right-click on a ManagedElement > Delete
ManagedElement (should also effect the map)
RTAM view lists all active alarms on EMS, Subnet the &%& separator should be removed from object
2.3 RTAM and ME name
double-click on an alarm lets you view and configure
alarm info
right-click on an alarm > Alarm Info: lets you view
and configure alarm info
right-click > Acknowledge and Unacknowledge alams Not implemented in GUI.
right-click > Delete Selected Alarms
RTAM view columns in relevant order: source of order defined in Config.java could be improved
alarm, severity, probable cause.. depending on client needs
column names in RTAM view are understandable and Can be improved depending on client wants and
relevant needs
perceivedSeverity generates different colored rows
Filtering on NT_Alarm or NT_TCA
Filter with either AND or OR between
Filter on ObjectType
Filter on AcknowledgeIndication
Filter on ServiceAffecting
Filter on Severity
Attributes with multiple values should display
content by holding the mouse over the field
2.4 When an ME is marked, all contained PTP/FTPs are

TPView listed in TP view
For each PTP/FTP, all potential CTP's are listed in TP
view
right-click > TP Info
right-click > ManagedElement Info
right-click > EMS Info
right-click > Create CTP
right-click > Create Alarm
2.5
MapView Scrolling zooms in and out
right-click on ManagedElement > ManagedElement
Info
right-click on ManagedElement > Delete
right-click on ManagedElement > Create Alarm
right-click on ManagedElement > Connection: should
change the connectionState, which should change
the icon color in the tree and map
right-click on TopologicalLink > TopologicalLink Info
right-click on TopologicalLink > Delete: should effect
both the map and tree
configuring the name of an ME in the graph changes
the name in the tree view
Transforming mode allows you to move the
background by dragging TODO in CustomEditingModalGraph row 72
Picking mode allows you to move the
managedElements and mark multiple ME's
Ctrl + left click on an ME centers it on the screen (in
Picking mode)
clicking on a Topological Link highlights it (in picking
mode)
Editing mode allows you to left-click on the field to if you press X instead of cancel, the icon will linger
create a new managedElement (it will not effect the database)
Dragging and dropping between two
managedElements creates a new topological Link
Dragging and dropping on a single managedElement
creates a topologicalLink that loops
2.6
Panels:co
mmon
Every time we chose "new _ " in a menu, a
respective panel will popup where you can provide
information
Adding a short number that is not predifined is not
Editing LayerRates written to the database
Editing Additional Info
Adding wrong attributes should give a warning or Data truncation should be displayed when data is
error message too long for column
Cancel: do nothing and close window
Restore: restore to original values, keep window
open
Save: Insert data in the database
Error message should be sent if trying to save
without primary key In debug window
In the lower left corner of the GUI three icons

represent the status of the following by changing
2.7 Status icon color:
the database connection
if Naming and Notification Services are running
connection to the northbound interface
3.0 NBI
3.1 GUI
Client Tree of EMS,MLSN,ME,PTP,CTP shows up in GUI
Simulator can be found by login in GUI Client
EMS Open EMS gives the same info as shown in simulator

Launch Network Data List on EMS shows a list of all
ME in simulator
Launching Monitor shows all alarms under the EMS Alarms not working, problem with structured
in simulator events
Launching MultilayerSubnetwork on EMS shows all
MLSN from simulator
Launching Link shows all the Topological links under
the EMS Not implemented in NBI
Launching SNC shows all SNCs under the EMS Not Implemented in GUI, model or NBI
EMS Capabilities shows all the functions supported Needs to be checked, but it shows whats
by the simulator programmed in the different mgrs.
Details show all the details as when connected to
MLSN the simulator for the given MLSN
Get Object get the info about the MLSN as shown in
the simulator at the moment
Lunch Network Data List shows a list of all the Mes
under this MLSN in simulator
Details shows all the details as when connected to
ME the simulator for the given ME
Get Object get the info about the ME as shown in the
simulator at the moment
ManagedElement Info shows a list with everything
related to the ME PTP/FTP and CTP works, but not alarms and TCA
PTP/FTP the simulator for the given TP
Get Object get the info about the TP as shown in the
simulator at the moment
CTP the simulator for the given CTP
Get Object get the info about the CTP as shown in
the simulator at the moment
1.2 Script
Client Script-results compared to data in Simulator
001-getAllEMSAndMEActiveAlarms No alarms work, problem with Structured Events
003-getAllTopLevelSubnetworkNames
004-getAllTopLevelSubnetworks
008-getEMS
016-getAllCrossConnections In DB but not implemented in NBI
017-getAllManagedElementNames
018-getAllManagedElements
020-getAllPTPs
022-getContainedCurrentTPs
CTP inside a SNC should be marked as InUse, we
024-getContainedInUseTPs lack this feature
026-getContainedPotentialTPs
137-getAllManagedElements
138-getAllManagedElementNames
143-getAllTopologicalLinks Not implemented in NBI
148-getSNCs Not implemented in NBI
150-getTopologicalLinks Not implemented in NBI
Instead of including all the functions in the different managers and mark all the unimplemented functions (which are many), we will list the
implemented and commenced managers below
EMSMgr:
Completed:
acknowledgeAlarms
getAllEMSAndMEActiveAlarms
getAllEMSAndMEUnacknowledgedActiveAlarms
getAllEMSSystemActiveAlarms
getAllEMSSystemUnacknowledgedActiveAlarms
getAllTopLevelSubnetworkNames
getAllTopLevelSubnetworks
getEMS
getCapabilities
Commenced:
setAdditionalInfo
setNativeEMSName
setOwner
setUserLabel
ManagedElementMgr: - (obs tp functions dont allow filtering on layerRate yet)
Completed:
getAllActiveAlarms
getAllFTPNames
getAllFTPs
getAllManagedElementNames
getAllManagedElements
getAllPTPNames
getAllPTPNamesWithoutFTPs
getAllPTPs
getAllPTPsWithoutFTPs
getContainedCurrentTPNames
getContainedCurrentTPs
getContainedInUseTPs
getContainedPotentialTPNames
getContainedPotentialTPs
getManagedElement
getTP
Commenced:
setAdditionalInfo
setNativeEMSName
setOwner
setUserLabel
MultiLayerSubnetworkMgr:
Completed:
getMultiLayerSubnetwork
Commenced:
setAdditionalInfo
setNativeEMSName
setOwner
setUserLabel
Appendix C Requirement Specification
Master thesis SRS document for TMF814
simulator
Ericsson Internal
REQUIREMENTS SPEC. 1 (36)
Prepared (also subject responsible if other) No.
EAB/ZA/MNO Mikael Riedel

Approved Checked Date Rev Reference
2010-03-17 PA1
TMF814 Simulator Software Requirements Specification
TMF814 Simulator
Mikael Riedel, Louisa Luciani

Ericsson Lindholmen
E-mail Louisa: louisa.luciani@ericsson.com

E-mail Mikael: mikael.riedel@ericsson.com
simulator
Ericsson Internal

2010-03-17 PA1
Contents
1 Introduction.......................................................................................... 6
1.1 Purpose.................................................................................... 6
1.2 Document Conventions ............................................................ 6
1.3 Intended Audience and Reading Suggestions .......................... 6
1.4 Stakeholders ............................................................................ 6
1.5 Definitions and Abbreviations ................................................... 7
2 Overall Description .............................................................................. 8
2.1 Product Perspective ................................................................. 8
2.2 Operating Environment............................................................. 8
2.3 Design and Implementation Constraints ................................... 8
2.4 Documentation ......................................................................... 8
3 Overview of the system ..................................................................... 10
3.1 System components............................................................... 10
3.2 System dependencies ............................................................ 10
4 Functional requirements ................................................................... 11
4.1 Model ..................................................................................... 11
4.1.1 Database storage ................................................................... 11
4.1.2 Save....................................................................................... 11
4.1.3 Load ....................................................................................... 11
4.1.4 New project ............................................................................ 11
4.2 Heart beat .............................................................................. 12
4.2.1 Heart beat behavior ................................................................ 12
4.2.2 Enable heart beat ................................................................... 12
4.2.3 Disable heart beat .................................................................. 12
4.3 Notification ............................................................................. 12
4.4 Active alarm list ...................................................................... 12
5 TMF 814 .............................................................................................. 13
5.1 Connect to GUI Client............................................................. 13
5.2 EMS manager ........................................................................ 13
5.2.1 Function: getAllEMSAndMEActiveAlarms............................... 13
5.2.2 Function: getAllEMSSystemActiveAlarms............................... 13
5.2.3 Function: getAllTopLevelSubnetworks.................................... 13
5.2.4 Function: getAllTopLevelSubnetworkNames .......................... 14
5.2.5 Function: getAllTopLevelTopologicalLinks.............................. 14
5.2.6 Function: getAllTopLevelTopolocigalLinkNames .................... 14
5.2.7 Function: getTopLevelTopologicalLink ................................... 14
5.2.8 Function: getEMS................................................................... 14
5.2.9 Function: acknowledgeAlarms................................................ 15
5.2.10 Function: createTopologicalLink ............................................. 15
5.2.11 Function: deleteTopologicalLink ............................................. 15
5.2.12 Function: getAllEMSAndMEUnacknowledgedActiveAlarms.... 15
5.2.13 Function: getAllEMSSystemUnacknowledgedActiveAlarms.... 15
5.2.14 Function: unacknowledgeAlarms............................................ 16
5.3 ManagedElement manager .................................................... 16
5.3.1 Function: getManagedElement............................................... 16
5.3.2 Function: getAllManagedElements ......................................... 16
simulator
Ericsson Internal

2010-03-17 PA1
5.3.3 Function: getAllManagedElementNames................................ 16

5.3.4 Function: getAllActiveAlarms .................................................. 16
5.3.5 Function: getAllUnacknowledgedActiveAlarms....................... 17
5.3.6 Function: getAllPTPs.............................................................. 17
5.3.7 Function: getAllPTPNames .................................................... 17
5.3.8 Function: getAllFTPs .............................................................. 17
5.3.9 Function: getAllFTPNames..................................................... 17
5.3.10 Function: getAllPTPsWithoutFTPs.......................................... 18
5.3.11 Function: getAllPTPNamesWithoutFTPs ................................ 18
5.3.12 Function: getContainedCurrentTPs ........................................ 18
5.3.13 Function: getContainedCurrentTPNames ............................... 18
5.3.14 Function: getContainedInUseTPs........................................... 18
5.3.15 Function: getContainedInUseTPNames ................................. 19
5.3.16 Function: getContainedPotentialTPs ...................................... 19
5.3.17 Function: getContainedPotentialTPNames ............................. 19
5.3.18 Function: getContainingTPs ................................................... 19
5.3.19 Function: getContainingTPNames.......................................... 20
5.3.20 Function: getContainingSubnetworkNames............................ 20
5.3.21 Function: getTP ...................................................................... 20
5.3.22 Function: setTPData............................................................... 20
5.3.23 Function: createGTP .............................................................. 21
5.3.24 Function: deleteGTP .............................................................. 21
5.3.25 Function: getGTP ................................................................... 22
5.3.26 Function: getAllGTPs.............................................................. 22
5.3.27 Function: getAllGTPNames .................................................... 22
5.3.28 Function: getContainingGTP .................................................. 22
5.3.29 Function: modifyGTP.............................................................. 22
5.3.30 Function: getPotentialFixedCCs ............................................. 23
5.3.31 Function: getAllCrossConnections.......................................... 23
5.3.32 Function: getAllFixedCrossConnections ................................. 23
5.3.33 Function: setGtpAlarmReportingOn........................................ 24
5.3.34 Function: setGtpAlarmReportingOff........................................ 24
5.3.35 Function: verifyTDMAssignment............................................. 24
5.4 Equipment .............................................................................. 25
5.4.1 Function: getAllEquipment...................................................... 25
5.4.2 Function: getAllEquipmentNames .......................................... 25
5.4.3 Function: getAllSupportedPTPs.............................................. 25
5.4.4 Function: getAllSupportedPTPNames .................................... 25
5.4.5 Function: getAllSupportingEquipment..................................... 25
5.4.6 Function: getAllSupportingEquipmentNames ......................... 26
5.4.7 Function: getContainedEquipment.......................................... 26
5.4.8 Function: getEquipment.......................................................... 26
5.4.9 Function: provisionEquipment ................................................ 26
5.4.10 Function: setAlarmReportingOff ............................................. 26
5.4.11 Function: setAlarmReportingOn ............................................. 26
5.4.12 Function: unprovisionEquipment ............................................ 27
5.4.13 Function: getSupportedEquipment ......................................... 27
5.4.14 Function: getSupportedEquipmentNames .............................. 27
5.4.15 Function: getSupportingEquipment......................................... 27
5.4.16 Function: getSupportingEquipmentNames ............................. 27
simulator
Ericsson Internal

2010-03-17 PA1
6 Nonfunctional requirements ............................................................. 28

6.1 ServiceOn resemblance ......................................................... 28
6.2 Nonfunctional requirements for TMF 814................................ 28
7 GUI ...................................................................................................... 28
7.1 Exit ......................................................................................... 28
7.2 Switching view........................................................................ 28
7.3 Resizing ................................................................................. 28
7.4 Menu ...................................................................................... 29
7.5 Map ........................................................................................ 29
7.5.1 Adding NE .............................................................................. 29
7.5.2 Moving NE.............................................................................. 29
7.5.3 Removing NE ......................................................................... 29
7.5.4 Adding TL............................................................................... 29
7.5.5 Removing TL.......................................................................... 29
7.5.6 More info on NE ..................................................................... 30
7.5.7 Showing alarms...................................................................... 30
7.5.8 Heart beat failure.................................................................... 30
7.6 RTM ....................................................................................... 30
7.6.1 Change color.......................................................................... 30
7.6.2 Sort on columns ..................................................................... 30
7.6.3 Filter ....................................................................................... 31
7.6.4 Save RTM-layout.................................................................... 31
7.6.5 Reset RTM-layout .................................................................. 31
7.7 Tree-view ............................................................................... 31
7.7.1 Change color.......................................................................... 31
7.7.2 Tree representation ................................................................ 31
7.7.3 Multiple selection.................................................................... 31
8 Extensibility requirements ................................................................ 32
8.1 TMF extension........................................................................ 32
8.2 NBI plug-in support................................................................. 32
8.3 Internal database.................................................................... 32
8.4 Database populator ................................................................ 32
9 Reliability............................................................................................ 32
9.1 Robustness ............................................................................ 32
10 Quality requirements ......................................................................... 33
10.1 Realistic data.......................................................................... 33
10.2 Usability.................................................................................. 33
10.3 Understandability.................................................................... 33
10.4 Resource consumption........................................................... 33
11 Maintainability .................................................................................... 34
11.1 Encapsulation......................................................................... 34
11.2 Consistency............................................................................ 34
11.3 Conciseness........................................................................... 34
11.4 Simplicity ................................................................................ 34
12 Summary ............................................................................................ 35
simulator
Ericsson Internal

2010-03-17 PA1
simulator
Ericsson Internal

2010-03-17 PA1
1 Introduction
1.1 Purpose
The purpose of this Software Requirements Specification is to provide a

description of the TMF814 Simulators functionality, and to serve as a product
validation check. It will also deepen the understanding and stand as ground
for rest of this project. Under the corresponding subheadings, an explanation
of the functionality will be provided, along with requirements that need to be
fulfilled such as data required for input and processing.
1.2 Document Conventions
In this document, every requirement statement has its own priority, which is
rated low, medium or high. Also a time estimation on each requirement which
helps when determining how much can be done in each iteration.
1.3 Intended Audience and Reading Suggestions
This document is mainly intended for Ericsson Solution Integrator, Solution

Architect and Support Engineers to understand the functionality of the
software. Begin with the overview sections and proceed through the sections
that are most pertinent to you as a reader.
1.4 Stakeholders
Requirements will be based on the expectations and needs of the

stakeholders of the software. The following are potential stakeholders:
GDSC OSS Integration
Interface implementers/Developers
Other Ericsson employees
Clients to Ericsson
The requirements specification will be created to comply with the needs of

GDSC OSS Integration, as they will be the primary consumer of this product.
To allow for future maintenance, additional functionality and adaptors, the
needs of future interface implementers and developers will be considered.
simulator
Ericsson Internal

2010-03-17 PA1
1.5 Definitions and Abbreviations
GUI Graphical User Interface
OO Object-Oriented
SRS Software Requirements Specification
CORBA Common Object Request Broker Architecture
TMF TeleManagement Forum
MTNM Multi Technology Network Management
TMF814 Protocol using CORBA specialized for MTNM communication.
TP Termination Point
TL Topological Link, is primarily an administrative object used to

convey a relationship between two TPs.
MLSN Multi Layer SubNetwork
TCA Threshold Crossing Alert
MLRA Multi Layer Routing Area
ASAP Alarm Severity Assignment Profile
EM Element Manager
EMS Element Management System

simulator
Ericsson Internal

2010-03-17 PA1
2 Overall Description
2.1 Product Perspective
The GSDC OSS-integrations team works with customizations, integration

services and solutions design of Network Management Systems. One of
these systems is ServiceOn and often, a solution specific script will be
created or an adjustment in the system will be made for the client. In order to
verify the expected outcome, tests need to be performed on a physical
network which is very expensive to have solely for testing purposes. This
often means that tests are performed on-site at clients. The objective of this
project is to create a standalone virtual network simulator that communicates
northbound over TMF814. This product will simulate an optical network that
can be interacted with through a GUI as well as through TMF814. The product
is intended to be used for testing purposes, and will provide a way to test
integrations in-house.
2.2 Operating Environment
The typical workstations the GSDC OSS Integration has are normal laptops.
All the laptops have Operating system Windows Vista, this will be the working
environment and also the aim for simulator, although the simulator will be
platform independent. The laptop will typically have one or two gigabyte
primary memory and a dual core processor with at least 1.5 GHz capacity.
A local database is needed for the simulator to store the information needed,
how to set it up will be included in the installation guide. By having a local
database to test against the simulator can run on the laptop even without a
real network connection.
2.3 Design and Implementation Constraints
The simulator and all the plug-ins should be written in Java. This will run on all
the computers used by GSDC Integrations and make it possible to continue
developing the simulator by GSDC personal even after this project has ended.
An open source database will be used to handle the possible big amount of
data. The choice has fallen on MySQL because its free, works well with java
and makes the setup on each computer simple.
2.4 Documentation
Deliverables include:
JavaDoc
simulator
Ericsson Internal

2010-03-17 PA1
A user manual
Design Document
Test Specification
Thesis (in depth description and analysis, as well as results)

simulator
Ericsson Internal

2010-03-17 PA1
3 Overview of the system

The program will be built according to the Model-View-Control architecture
(MVC). The model will contain the network data of the simulated OSS and
encapsulates an internal database. The view will display all the information in
the model, showing network elements, their correlation to each other and
specific information about each network element. How the information is
displayed depends on the selection of network elements and the functions
that are implemented and loaded. The controller receives input and makes
calls to the model. Because the controller handles all the logic, which is
preferably kept modular, it will consist of multiple classes. A main controller
will for instance handle general logic such as the menu system, while specific
windows will be able to communicate with their own controller class. Multiple
northbound interfaces will be able to be loaded at startup, given that they
follow the given NBI.
3.1 System components
Model
View
Control
Interface
Database
TMF814 implementation of NBI
3.2 System dependencies
The program is divided into the components above, where the model is the
central part. A graphical user interface that manipulates the model through
views and controllers exists locally. The model can also be changed and
interacted with through the northbound interface. The local GUI and the NBI
should have the same functionality, though there might be some limitations in
the NBI depending on the choice of protocol. If a new NBI is added to the
simulator, functionality might have to be added to the GUI accordingly. The
data in the database can be manipulated through either the GUI or the NBI.
simulator
Ericsson Internal

2010-03-17 PA1
4 Functional requirements
4.1 Model
4.1.1 Database storage
Priority: High Ericsson mandatory: No

Iteration: 1-2 Time estimate: 100
Description: The network representation, along with network elements and

all the at least the attributes required by the TMF814 functions should be
stored in a local database.
4.1.2 Save
Priority: Medium Ericsson mandatory: No

Iteration: 3 Time estimate: 3
Description: It should be possible to store the status of the different objects

and the content of the database to a file that should be able to start on
another computer running the simulator.
4.1.3 Load

Description: Connected to 4.1.2. The previous saved files from the simulator
should be able to load the same state properly so that the simulator-state is
exactly as when saved. This means clearing the database and populating it
with the correct data.
4.1.4 New project

Description: Creating a new project should clear the database and prepare it
for a new project. It should also clear any values on variables in the model.
simulator
Ericsson Internal

2010-03-17 PA1
4.2 Heart beat
4.2.1 Heart beat behavior
Priority: High Ericsson mandatory: Yes

Description: The simulator should be able to reproduce the behavior of the

heart beat function in ServiceOn systems. Internal alarms, or system alarms,
should be raised for each node that is simulated not to have working heart
beat.
4.2.2 Enable heart beat

Description: It should be possible to enable the heart beat functionality on

each network element. The default value for each network element should be
that heart beat is enabled. Enabling heart beat is done from the simulators
point of view and not from NBI.
4.2.3 Disable heart beat

Description: It should be possible to disable the heart beat functionality for

each network element. If heart beat is disabled for a network element an
internal alarm is raised for this element.
4.3 Notification

Iteration: 1 Time estimation: 24
Description: It should be possible to send messages (alarms) spontaneous

through the NBI interface, where the simulator acts as a client instead of a
server as will be the case for all the rest of the functionality.
4.4 Active alarm list

Iteration: 1 Time estimation: 16
simulator
Ericsson Internal

2010-03-17 PA1
Description: The possible to answer requests from the NBI. This means that
the simulator should react as a server. Exactly how it should react depends
on the exact implementation of the NBI, and for the TMF814 case it will be
discussed during chapter 5.
5 TMF 814
5.1 Connect to GUI Client
Priority: High Ericsson Mandatory: Yes

Description: It should be possible for the GUI Client to connect to the

simulator server.
5.2 EMS manager
5.2.1 Function: getAllEMSAndMEActiveAlarms

Description: When this function is used by a TMF-client the simulator should

return all the alarm associated to this EMS. Both alarms from the network
elements and internal alarm that the simulator has created by it self. Two
excluding lists are used two filter on probable cause and severity. Matches
against these lists are not to be returned. One list and one iterator for giving
next list, if length of result is larger than the given maximum length, are return.
5.2.2 Function: getAllEMSSystemActiveAlarms

Description: Related to requirement 5.2.1. Instead of returning alarms that

dont match the excluding lists from network elements and internal alarms,
only the internal alarms are returned that are associated to this specific EMS.
5.2.3 Function: getAllTopLevelSubnetworks

simulator
Ericsson Internal

2010-03-17 PA1
Description: This should return all the subnetworks that is associated with
the specific EMS. It should return the whole subnetwork-object. Return as a
list of subnetworks with the possibility of getting also an iterator depending on
have big the result is.
5.2.4 Function: getAllTopLevelSubnetworkNames

Description: Related to requirement 5.2.3. Instead of object it only returns

the names on the objects. Return as list with the possibility of an additional
iterator.
5.2.5 Function: getAllTopLevelTopologicalLinks

Description: Returns all Topological links between MLSN associated with the
EMS.
5.2.6 Function: getAllTopLevelTopolocigalLinkNames

Description: Related to 5.2.5. Returns only the name of each TL in the result
instead of the whole TL-object.
5.2.7 Function: getTopLevelTopologicalLink

Description: Should return the specific TL-object that is associated with the
name of a TL, given as input.
5.2.8 Function: getEMS

simulator
Ericsson Internal

2010-03-17 PA1
Description: This function should return all the stored information on the
specific EMS. Information should follow the standard and contain for example
name, version, owner, type and additional information.
5.2.9 Function: acknowledgeAlarms

Description: This function will change the status of the given alarms to
acknowledged. This goes for all alarms and TCA:s in the list.
5.2.10 Function: createTopologicalLink

Description: This creates a TL or a MLSN according to the given topological

data.
5.2.11 Function: deleteTopologicalLink

Description: This function should remove a topological link, matching should

be done via name.
5.2.12 Function: getAllEMSAndMEUnacknowledgedActiveAlarms

Description: This function is connected to the 5.2.1. The result is filtered

once before, making sure that only unacknowledged alarms is in the result.
5.2.13 Function: getAllEMSSystemUnacknowledgedActiveAlarms

Description: Related to 5.2.2. Acknowledged alarms are filtered out before

returning result.
simulator
Ericsson Internal

2010-03-17 PA1
5.2.14 Function: unacknowledgeAlarms

Description: This functionality means that the alarms in the given list should
change state to unacknowledged.
5.3 ManagedElement manager
5.3.1 Function: getManagedElement

Description: Should retrieve the entire object structures of the managed

element for the given managed element name.
5.3.2 Function: getAllManagedElements

Description: Should retrieve the entire object structures of all of the Managed
Elements.
5.3.3 Function: getAllManagedElementNames

Description: Should retrieve the names of all of the Managed Elements.

Related to getAllManagedElements, 5.3.2.
5.3.4 Function: getAllActiveAlarms
Priority: HIGH Ericsson mandatory: Yes

Description: Should retrieve all of the active alarms and TCAs for the
specified managed element. Alarms that are not reported by the ME to the
EMS should not be reported by this operation. Also, alarms which ASAP
assigned severity is NOTALARMED should not be reported by this
operation.
simulator
Ericsson Internal

2010-03-17 PA1
5.3.5 Function: getAllUnacknowledgedActiveAlarms

Description: Should retrieve all of the active alarms and TCAs (for the
specified managed element) that have not been acknowledged. Alarms that
are not reported by the ME to the EMS should not be reported by this
operation. Also, alarms which ASAP assigned severity is NOTALARMED
should not be reported by this operation.
5.3.6 Function: getAllPTPs

Description: Should retrieve the entire object structure of all of the PTPs and
FTPs on the specified Managed Element that contain one or more of the
NMS-specified PTP/FTP layer rates and that are capable of supporting one or
more of the NMS-specified connection layer rates. If there are no PTPs/FTPs
that match the layer constraints, an empty list is returned. A PTP/FTP will be
returned regardless of connectivity to other managed elements and
regardless of position in the subnetwork (both edgepoints of the subnetwork
and the PTPs/FTPs that are internal to the subnetwork are reported).
5.3.7 Function: getAllPTPNames

Description: This operation should have the same behavior as

getAllPTPs(), but instead of returning the entire object structures, this
operation returns their names.
5.3.8 Function: getAllFTPs

Description: This operation has exactly the same behaviour as getAllPTPs(),

but instead of returning both PTPs and FTPs it returns solely FTPs
5.3.9 Function: getAllFTPNames
Priority: Med Ericsson mandatory: No

simulator
Ericsson Internal

2010-03-17 PA1

getAllFTPs(), but instead of returning the entire object structures, this
5.3.10 Function: getAllPTPsWithoutFTPs

Description: This operation has exactly the same behavior as getAllPTPs(),

but instead of returning both PTPs and FTPs it returns solely PTPs
5.3.11 Function: getAllPTPNamesWithoutFTPs


getAllPTPsWithoutFTPs(), but instead of returning the entire object structures,
this operation returns their names.
5.3.12 Function: getContainedCurrentTPs
Priority: low Ericsson mandatory: No

Description: Should retrieve the "current" CTPs that are contained within a
given PTP, FTP or CTP, at specific layer rates. A "current" CTP is defined as
a CTP that is either cross-connectable or cross-connected,in the current
mapping configuration.
5.3.13 Function: getContainedCurrentTPNames


getContainedCurrentTPs(), but instead of returning the entire object
structures, this operation returns their names.
5.3.14 Function: getContainedInUseTPs
Priority: med Ericsson mandatory: No

simulator
Ericsson Internal

2010-03-17 PA1
Description: Should retrieve the "in use" CTPs that are contained within a
specific PTP, FTP or CTP, at specific layer rates. An "in use" CTP is defined
as a CTP that is used by an SNC in any state (including pending), either as a
CM end point or as an intermediate connection point, or a CTP that is
terminated and mapped.
5.3.15 Function: getContainedInUseTPNames


getContainedInUseTPs(), but instead of returning the entire object structures,
5.3.16 Function: getContainedPotentialTPs

Description: Retrieves all of the CTPs for a given TP that it is potentially

capable of supporting in all possible mapping configurations, at the specified
rates and that are contained by the specified termination point. The TP may
be a PTP, an FTP or a CTP. If the layerRateList is empty then contained
CTPs at all flexible and/or static LayerRates are returned.
5.3.17 Function: getContainedPotentialTPNames


getContainedPotentialTPs(), but instead of returning the entire object
structures, this operation returns their names.
5.3.18 Function: getContainingTPs

Description: Retrieves a list of the containing TPs given a CTP. This should
return an PTP or FTP where there is only one level of containment. In a case
of deeper containment this should return a list of CTPs and a PTP or FTP.
simulator
Ericsson Internal

2010-03-17 PA1
5.3.19 Function: getContainingTPNames


getContainingTPNames(), but instead of returning the entire object structures,
5.3.20 Function: getContainingSubnetworkNames

Description: Shouldreturn the list of subnetwork names that the Managed

Element supplied as an input parameter belongs to.
5.3.21 Function: getTP

Description: returns the termination point structure for the given TP name
(CTP, FTP or PTP). The termination point name must be explicit (a generic
endpoint specification may not be used in this case). The termination point
structure contains SD1-16 transmission parameters. The transmission
parameters returned will be the parameters in place on the actual termination
point on the NE. If there are no transmission parameters or the TP does not
actually exist on the NE, then transmissionParams will be empty. The field
transmissionParams will also be empty for "potential" ATM VP/VC CTPs.
5.3.22 Function: setTPData

Description: This service should allow the TMF GUI to set parameters on a
specified Termination Point (CTP, PTP or FTP). This operation is best effort
(except where specified otherwise for a particular parameter). The results of
the operation are returned so that the NMS is aware of what modifications
succeeded. If the source TP of a broadcast system is used as input, then the
entire multipoint system will be affected based on the new parameter values
for the source TP.
simulator
Ericsson Internal

2010-03-17 PA1
The tpMappingMode may be set with this operation. When the mode is set to
TM_TERMINATED_AND_AVAILABLE_FOR_MAPPING, the EMS will
terminate the specified CTP. In this case the EMS must create the specified
CTP on the NE if it does not actually exist. Setting the tpMappingMode of an
ATM VP or VC CTP can only be done if the CTP has been created. Note that
the tpMappingMode can be set only on the ingress and egress CTPs of an
ATM SNC since they are the only ones which may not be cross-connected.
No change to tpMappingMode or trafficDescriptors will take place if there is

any active cross connect (NE cross connect) using the CTP passed in
parameter.
The transmissionParams is a "delta" list that needs to be applied to the

specified TP, i.e. only a subset of the parameters may be specified in the list,
in which case only those should be applied in the NE. Transmission
parameters are used to associate a TCA profile with a TP using this service.
In this case there are potentially additional failure modes (see exceptions).
The assignment of a Transmission Descriptor (TMD) to a Termination Point

(TP) as egress or ingress TMD by using the TMD's name amounts to an
overwriting of the layered transmission parameters of the TP by the layered
transmission parameters of the TMD, and to an overwriting of the additional
info parameters of the TP by the "additional TP information" parameters of the
TMD.
5.3.23 Function: createGTP

Description: TMF GUI should be able to use this operation to request the
creation of a GTP. The it can either specify the list of CTPs comprising the
GTP (the list is placed in the listOfTPs parameter) or, in the case of
contiguous CTPs of the same layerRate, the NMS may list the first CTP (in
the initialCTPname parameter) and the number of following CTPs (in the
numberOfCTPs parameter). The NMS may also provide the EMS with the
flexibility to decide the list of CTPs by using the gtpEffort parameter. In this
flexible mode the EMS uses the listOfTPs parameter or the initialCTPname/
numberOfCTPs parameters to determine the total requested bandwidth but it
may return a GTP (newGTP parameter) with a different set of CTPs than
those indicated in the original createGTP request. Note that this mode allows
for the GTP components to be instantiated at a later time by the ME (e.g.,
upon detection of user's signal). Therefore the operation may successfully
return a newGTP with an empty listOfTPs attribute (to be updated at a later
time once the component CTPs are created in the ME).
5.3.24 Function: deleteGTP

simulator
Ericsson Internal

2010-03-17 PA1

Description: This operation should delete a GTP. An attempt to delete a

GTP that is involved in a cross connection or SNC should be rejected by the
EMS. This operation should be idempotent. If the service is called with the
name of a non-existent GTP, it should succeed.
5.3.25 Function: getGTP

Description: Should return the GTP structure for the given GTP name
5.3.26 Function: getAllGTPs

Description: Should retrieve all of the GTPs (on the given Managed Element)
that contain one or more TPs at the specified layer rates. If there are no GTPs
that match the layer constraints, an empty list is returned
5.3.27 Function: getAllGTPNames


getAllGTPs(), but instead of returning the entire object structures, this
5.3.28 Function: getContainingGTP

Description: Should return the name of the GTP containing a given CTP. If
the CTP is not contained in a GTP, the gtp output parameter is left empty.
5.3.29 Function: modifyGTP

Description: The modify GTP operation is used to add TPs to or delete TPs
from a GTP. For a given request, the NMS can only add or delete CTPs, not
simulator
Ericsson Internal

2010-03-17 PA1
both. It is not possible to add a CTP that is already involved in a cross

connection or SNC, or that is part of another GTP. Attempts to modify a GTP
that is involved in a cross connection (or SNC) should be rejected by the
EMS. The operation is best-effort, i.e., the EMS will add or delete as many of
the identified CTPs as possible. If the service is called with the name of a
non-existent GTP or CTP, it will fail. If the NMS created a GTP with gtpEffort
equal to EFFORT_SAME, this also implies that the EMS will not modify on its
own, i.e., the EMS will only modify the GTP if requested by the NMS via the
modifyGTP operation.
5.3.30 Function: getPotentialFixedCCs

Description: Should retrieve fixed connection schemes related to normal and

inverse multiplexing. A cross connection is identified as a fixed SNC using
additional information.
The operation takes as an input a TP and if this TP may be or is involved in a

multiplexing or inverse multiplexing scheme, it will report:
The TP containing the fixed layer.
the list of potential fixed cross connects that will exist if the containing TP's
clientConnectivity or serverConnectivity is set to "Connected" (i.e. If the
containing TP is set to multiplexing or inverse multiplexing).
If the clientConnectivity (resp. serverConnectivity) of the TP is currently set to

"Connected", the potentialCCList matches the list of active fixed cross
connects that involve its client TPs (resp. server TPs).
If the TP client layer (resp. server layer) is always fixed cross connected
(hard-wired), the potentialCCList always matches the list of active fixed cross
connects that involve the client TPs (resp. server TPs).
5.3.31 Function: getAllCrossConnections

Description: Should retrieve a list of the cross-connects for the specified

managed element at the specified layer rates. This operation returns cross-
connects between CTPs/FTPs and between GTPs
5.3.32 Function: getAllFixedCrossConnections

simulator
Ericsson Internal

2010-03-17 PA1
Description: Should have the exact same behaviour as

getAllCrossConnections, but returns only fixed cross connection object
structures.
5.3.33 Function: setGtpAlarmReportingOn
Priority: Low Ericsson mandatory: No

Description: Should enable (activate, or turn on) alarm reporting for a GTP.
The EMS sends an attribute value change notification in case of success.
5.3.34 Function: setGtpAlarmReportingOff

Description: Should disable (dectivate, or turn off) alarm reporting for a

GTP. The EMS sends an attribute value change notification in case of
success.
5.3.35 Function: verifyTDMAssignment

Description: This service verifies the egress and/or ingress TMD state of the
specified TP identified by tpName.
According to the requested transmission direction it checks whether a TMD is

assigned as egress and/or ingress TMD to the TP. If this is true it first verifies
the existence of the assigned TMD(s) and then compares the transmission
parameters of the TMD and TP, and the additional TP info parameters of the
TMD with the additional info parameters of the TP.
If a TMD parameter is not present as a TP parameter or is present but with a

different value, this is called a "parameter mismatch", and the TMD state will
take the value "mismatch". The service returns the current TMD state and all
mismatched transmission or additional TP info parameters of the TMD (which
should mostly be none) as its output.
simulator
Ericsson Internal

2010-03-17 PA1
5.4 Equipment
5.4.1 Function: getAllEquipment

Description: Should return all the information from the Managed Element or
the Equipment holder. It should match on the name, which is given. Returns a
list on Equipments or Holders that has a maximum length of how_many. If
more things exists an iterator should be able to give the rest.
5.4.2 Function: getAllEquipmentNames
Priority: high Ericsson mandatory: No

Description: Related to 5.4.1. Instead of returning the whole object only the
names of all equipment should be returned.
5.4.3 Function: getAllSupportedPTPs

Description: This should return all the PTPs/FTPs that are connected,
directly, to the given equipment. PTPs returned share their physical layer with
the given equipment, e.g. the port is physical on the equipment. Could be a
port, a connected fiber, connected wire etc. The FTPs that are returned are
those which are implemented by the physical circuitry supported by the
equipment and will include FTPs that are named from the specified
equipment. Returned as a list and an iterator, depending on how_many
variable.
5.4.4 Function: getAllSupportedPTPNames

Description: Connected to 5.4.3. Should only return a list on name instead of

actual objects.
5.4.5 Function: getAllSupportingEquipment

Description: Return the equipments and the equipment holders that is

supported by a specific equipment holder.
simulator
Ericsson Internal

2010-03-17 PA1
5.4.6 Function: getAllSupportingEquipmentNames

Description: Related to 5.4.5. Returns only the names instead of a list of

actual equipment or holders.
5.4.7 Function: getContainedEquipment

Description: Returns the equipments and the equipment holders that is

seated on a specific equipment holder. This differs from the getAllEquipment,
5.4.1, in the way that it ONLY looks at the next level in the containment
hierarchy. As input it takes the name of the equipment holder.
5.4.8 Function: getEquipment

Description: Returns the equipment or holder given the name of it.
5.4.9 Function: provisionEquipment

Description: This operation allows the NMS to permanently provision

equipment in an equipment holder in a Managed Element. The successful
result of this operation is the creation or update of the equipment object and
the creation of all its related objects such as Termination Points. The resulting
object will be returned. It requires that correct equipmentCreateData is given.
5.4.10 Function: setAlarmReportingOff

Description: This should disable the functionality for an equipment or holder

to report alarms. This do not effect TP alarms. EMS sends an attribute value
change notification in case of success.
5.4.11 Function: setAlarmReportingOn

simulator
Ericsson Internal

2010-03-17 PA1
Description: Related to 5.4.11.This function should turn on the possibility for

an equipment to report alarms. It only turns on alarms from the equipment or
holder, not for the TP. The EMS should send an attribute value change
notification when successful.
5.4.12 Function: unprovisionEquipment

Description: Related to 5.4.9. It should try to remove data instead of creating

a new Equipment. It first tries to set the equipment to
OUT_OF_SERVICE_BY_MAINTENANCE.
5.4.13 Function: getSupportedEquipment

Description: This should return all the equipment that is dependent on the
specific given equipment. Could be that a power pack supports several circuit
packs and then the circuit packs should be returned.
5.4.14 Function: getSupportedEquipmentNames

Description: Related to 5.4.13. This should only return the specific names
instead of the whole object.
5.4.15 Function: getSupportingEquipment

Description: Returns the equipment that supports a given piece of

equipment. Could be power source for the equipment, e.g. equipment that
needs to be there for the given equipment to work properly.
5.4.16 Function: getSupportingEquipmentNames

Description: Related to 5.4.15. Should only return the names and not whole
objects.
simulator
Ericsson Internal

2010-03-17 PA1
6 Nonfunctional requirements
6.1 ServiceOn resemblance

Description: The simulator should to some extend resemble the ServiceOn

system, when it comes to the GUI and the interactions that the simulator
supports.
6.2 Nonfunctional requirements for TMF 814
7 GUI
Skapa grafik
7.1 Exit

Description: It should be possible to close the simulator through the two

standardized ways, through File->Exit and when clicking the x button in the
upper-right corner.
7.2 Switching view

Description: Changing between Map and RTM view should be possible.
7.3 Resizing

Description: It should be possible to resize the simulator GUI.

simulator
Ericsson Internal

2010-03-17 PA1
7.4 Menu

Description: A menu containing standardized features as New, Save, Load,

Exit, About, Settings should exist.
7.5 Map
7.5.1 Adding NE

Description: By choosing the add NE in the toolbar it should be possible to

click wherever the NE should be placed.
7.5.2 Moving NE

Description: It should be possible to move a NE through drag and drop.
7.5.3 Removing NE

Description: When having the remove tool selected it should be possible to

remove a NE by clicking on it.
7.5.4 Adding TL

Description: It should be possible to add a topological link between two NE

with the draw TL tool
7.5.5 Removing TL

Description: It should be possible to remove a topological link by clicking on

it, if the remove tool is selected.
simulator
Ericsson Internal

2010-03-17 PA1
7.5.6 More info on NE

Description: By right-clicking on the NE a context-menu with more info and

options on the NE should be presented.
7.5.7 Showing alarms

Description: Alarms on a NE should be shown by changing the color of the

NE.
7.5.8 Heart beat failure

Description: Heart beat failure should be indicated by adding a small

lightning bolt on the NE.
7.6 RTM
7.6.1 Change color

Description: Should change color depending on status.
7.6.2 Sort on columns

Description: It should be possible to click on each column and sort on this

specific column. Clicking ones should sort descending, click again and it
should sort ascending.
simulator
Ericsson Internal

2010-03-17 PA1
7.6.3 Filter

Description: It should be possible to filter on State, Severity, Type, Domain

and time. Only alarms meeting the filters should be shown.
7.6.4 Save RTM-layout

Description: Should be possible to save the configuration of the layout for

RTM, this layout will automatically be loaded each time RTM is used.
7.6.5 Reset RTM-layout

Description: If the layout for RTM is resettled, then it should return to a

predefined state.
7.7 Tree-view
7.7.1 Change color

Description: Should change color depending on status.
7.7.2 Tree representation

Description: Sub-networks and network elements should visible in a tree,

with possibility to filter Map and RTM with the tree.
7.7.3 Multiple selection

simulator
Ericsson Internal

2010-03-17 PA1
Description: Should be possible to select multiple nodes, not only from the
same subnetwork. If a subnetwork is selected then it is assumed that all the
children of this node is also selected.
8 Extensibility requirements
8.1 TMF extension

Description: It should be possible to add the missing pieces of the TMF814

standard to make a complete coverage after this project.
8.2 NBI plug-in support

Description: Other north bound interfaces should be able to integrate plug-

ins given that the follow the NBI-interface.
8.3 Internal database

Description: Support for changing to another internal database should be

given. The other database has to be implemented in a wrapper following the
interface for internal database.
8.4 Database populator

Description: Different populators for different external sources should be

able to populate the database, given that they follow an given interface.
9 Reliability
9.1 Robustness

simulator
Ericsson Internal

2010-03-17 PA1
Description: The program should operate despite abnormalities in input,

calculations, etc. Fuzz-testing should be used to prove robustness.
10 Quality requirements
10.1 Realistic data

Description: The database should contain realistic network data that the
stakeholders find useful.
10.2 Usability

Description: The program should be practical to start-up and begin using.

The user interface should be easy to understand for people with some
knowledge when it comes to OSS.
10.3 Understandability

Description: Not only should the program itself be easy to use, but the
purpose of the final product should be clear with the stakeholders as well.
User documentation must therefore be clearly written, so that the value of this
program is easily understandable.
10.4 Resource consumption

Description: The program should not consume an undesirable amount of

memory or CPU.
simulator
Ericsson Internal

2010-03-17 PA1
11 Maintainability
11.1 Encapsulation

Description: When possible, functionality should be encapsulated
11.2 Consistency

Description: There should be consistency in indentations, comments and

variables.
11.3 Conciseness

Description: There should be a minimization of excessive or redundant

information or processing
11.4 Simplicity

Description: Although optimality is desirable, it should not override clear,

understandable code apart from if a function is run several times or effects the
performance in a measurable way.
simulator
Ericsson Internal

2010-03-17 PA1
12 Summary
The total amount of man-hours calculated for the requirements given in this
document are just a rough estimate. The actual time for each implementation
including preparations for each functionality and each requirement could differ
in both ways.
Total: 743 Man-Hours
Iteration 1: 262 Man-Hours
Total amount of Man-Hours that are assigned for designing and implementing
to this project is around 800-850 depending on some holidays. Some of the
features in iteration 3 will be parts of the development in earlier iterations so
the time will somewhat shift from this iteration to the earlier iterations.
This time is not including testing, nor is it including the documentation writing
at the end of the project.
simulator
Ericsson Internal

2010-03-17 PA1
Appendix D JavaDoc
Table Of Content
com.ericsson.eos........................................................................................................................... 5
Start .................................................................................................................................... 5
com.ericsson.eos.config ................................................................................................................ 6
AlarmTypes......................................................................................................................... 6
Config ................................................................................................................................. 7
com.ericsson.eos.controller......................................................................................................... 11
MainController .................................................................................................................. 11
RTAMController ................................................................................................................ 13
TPController...................................................................................................................... 16
TreeController................................................................................................................... 17
com.ericsson.eos.database......................................................................................................... 20
MySQLConnector ............................................................................................................. 20
MySQLDelete ................................................................................................................... 21
MySQLGetters .................................................................................................................. 24
MySQLInit ......................................................................................................................... 36
MySQLSetters .................................................................................................................. 37
MySQLUpdater ................................................................................................................. 50
XmlParser ......................................................................................................................... 58
com.ericsson.eos.debugger ........................................................................................................ 61
Debugger .......................................................................................................................... 61
com.ericsson.eos.dynamicLoader ............................................................................................... 64
DynamicLoader................................................................................................................. 64
com.ericsson.eos.helper.............................................................................................................. 66
InputChecker .................................................................................................................... 66
Splitter............................................................................................................................... 67
TreePathDivider................................................................................................................ 68
com.ericsson.eos.interfaces ........................................................................................................ 70
DBI.................................................................................................................................... 70
DebugInterface ............................................................................................................... 101
NBI.................................................................................................................................. 102
com.ericsson.eos.junitTests ...................................................................................................... 116
AllTests ........................................................................................................................... 116
GetterTester.................................................................................................................... 117
MySQLTest..................................................................................................................... 117
com.ericsson.eos.model............................................................................................................ 119
Model .............................................................................................................................. 120
ModelAlarm..................................................................................................................... 121
ModelCtp ........................................................................................................................ 127
ModelEms....................................................................................................................... 133
ModelHelper ................................................................................................................... 135
ModelInit ......................................................................................................................... 140
ModelMe ......................................................................................................................... 141
ModelMlsn ...................................................................................................................... 145
ModelPtp......................................................................................................................... 148
ModelSelection ............................................................................................................... 151
ModelTca ........................................................................................................................ 153
ModelTl ........................................................................................................................... 158
MyTableModel ................................................................................................................ 161
com.ericsson.eos.services ........................................................................................................ 163
NameService .................................................................................................................. 163
NotificationService .......................................................................................................... 164
com.ericsson.eos.view .............................................................................................................. 165
AboutPanel ..................................................................................................................... 166
EMSPanel....................................................................................................................... 167
MEPanel ......................................................................................................................... 168
MLSNPanel..................................................................................................................... 170
MainView ........................................................................................................................ 171
ParseStatusPanel ........................................................................................................... 174
StatusPanel .................................................................................................................... 175
TPPanel .......................................................................................................................... 176
TPView ........................................................................................................................... 179
TopoLinkPanel................................................................................................................ 182
TreeNodeIconRenderer .................................................................................................. 184
TreeView......................................................................................................................... 185
XkcdPanel....................................................................................................................... 188
com.ericsson.eos.view.alarm .................................................................................................... 190
AlarmAlarmPanel............................................................................................................ 190
AlarmTCAPanel .............................................................................................................. 194
NTAlarmView.................................................................................................................. 197
NTTCAView .................................................................................................................... 200
com.ericsson.eos.view.rtam ...................................................................................................... 204
CustomTableCellRenderer ............................................................................................. 204
RTAMAlarm .................................................................................................................... 205
RTAMFilter...................................................................................................................... 208
RTAMTCA ...................................................................................................................... 209
RTAMView...................................................................................................................... 212
com.ericsson.helper .................................................................................................................. 215
AlarmCreator .................................................................................................................. 215
NameExtractor................................................................................................................ 218
com.ericsson.nbiImp.................................................................................................................. 220
NBIImp............................................................................................................................ 220
TestStarter ...................................................................................................................... 229
com.ericsson.poaImp ................................................................................................................ 230
ASAPIterator_IPOAImp .................................................................................................. 233
BackupIdIterator_IPOAImp............................................................................................. 234
CCIterator_IPOAImp....................................................................................................... 235
CallAndTopLevelConnectionsAndSNCsIterator_IPOAImp............................................. 236
CallAndTopLevelConnectionsIterator_IPOAImp ............................................................ 237
Common_IPOAImp......................................................................................................... 238
CurrentMaintenanceOperationIterator_IPOAImp ........................................................... 239
EMSMgr_IPOAImp ......................................................................................................... 240
EProtectionGroupIterator_IPOAImp ............................................................................... 248
EmsSessionFactory_IPOAImp ....................................................................................... 249
EmsSession_IPOAImp ................................................................................................... 250
EquipmentInventoryMgr_IPOAImp ................................................................................. 252
EquipmentOrHolderIterator_IPOAImp ............................................................................ 257
EventIterator_IPOAImp................................................................................................... 258
FDFrIterator_IPOAImp.................................................................................................... 259
FDIterator_IPOAImp ....................................................................................................... 260
FlowDomainMgr_IPOAImp ............................................................................................. 261
GTPiterator_IPOAImp..................................................................................................... 270
GuiCutThroughMgr_IPOAImp ........................................................................................ 271
MFDFrIterator_IPOAImp................................................................................................. 273
MFDIterator_IPOAImp .................................................................................................... 274
MLSNPPIterator_IPOAImp ............................................................................................. 275
MLSNPPLinkIterator_IPOAImp ...................................................................................... 276
MLSNPPLinkMgr_IPOAImp............................................................................................ 277
MLSNPPMgr_IPOAImp .................................................................................................. 280
MaintenanceMgr_IPOAImp ............................................................................................ 282
ManagedElementIterator_IPOAImp................................................................................ 284
ManagedElementMgr_IPOAImp..................................................................................... 285
MultiLayerSubnetworkMgr_IPOAImp ............................................................................. 294
NamingAttributesIterator_IPOAImp ................................................................................ 312
NmsSession_IPOAImp ................................................................................................... 313
PMDataIterator_IPOAImp............................................................................................... 315
PMPIterator_IPOAImp .................................................................................................... 316
PerformanceManagementMgr_IPOAImp ....................................................................... 317
ProtectionGroupIterator_IPOAImp.................................................................................. 323
ProtectionMgr_IPOAImp................................................................................................. 324
SNCIterator_IPOAImp .................................................................................................... 328
Session_IPOAImp .......................................................................................................... 329
SoftwareAndDataMgr_IPOAImp..................................................................................... 330
SubnetworkIterator_IPOAImp......................................................................................... 332
TCAParameterProfileIterator_IPOAImp.......................................................................... 333
TCProfileIterator_IPOAImp............................................................................................. 334
TCProfileMgr_IPOAImp .................................................................................................. 335
TerminationPointIterator_IPOAImp................................................................................. 338
TopologicalLinkIterator_IPOAImp................................................................................... 339
TrafficDescriptorIterator_IPOAImp ................................................................................. 340
TrafficDescriptorMgr_IPOAImp....................................................................................... 341
TransmissionDescriptorIterator_IPOAImp ...................................................................... 343
TransmissionDescriptorMgr_IPOAImp ........................................................................... 344
Version_IPOAImp ........................................................................................................... 348
Index.......................................................................................................................................... 349
Package com.ericsson.eos
Class Summary
Start
The Class Start.
com.ericsson.eos
Class Start
java.lang.Object
|
+--com.ericsson.eos.Start
< Constructors > < Methods >
public class Start

extends java.lang.Object
The Class Start. This is the Entry-point for this simulator and all the including functionality.
Constructors
Start
public Start(java.lang.String arg)
Instantiates a new instance of the simulator.
Parameters:
arg - Parameter to tell which mode the program should start in, "install", "parse" or ""
Methods
main
public static void main(java.lang.String[] args)
The main method.
Parameters:
args - the arguments
Package com.ericsson.eos.config
Class Summary
AlarmTypes
The Class AlarmTypes.
Config
The Class Config.
com.ericsson.eos.config
Class AlarmTypes
java.lang.Object
|
+--com.ericsson.eos.config.AlarmTypes
public class AlarmTypes

The Class AlarmTypes. This is a class for handling templates for alarms, stored in AlarmTypes.xml. It
uses the same parser as the XmlParser class.
Constructors
AlarmTypes
public AlarmTypes(Model model)
Instantiates a new instance of this class. It tries to read from the alarm-files as soon as it is
created.
Parameters:
model - the model
Methods
getAlarmTypes
public java.util.ArrayList getAlarmTypes()
Gets the list of alarm types. This list has been parsed from the xml-file.
Returns:
the alarm types
setup
public void setup()
Setup. This function sets the parser and starts the parsing.
com.ericsson.eos.config
Class Config
java.lang.Object
|
+--java.util.Observable
|
+--com.ericsson.eos.config.Config
All Implemented Interfaces:
java.io.Serializable
public class Config

extends java.util.Observable
implements java.io.Serializable
The Class Config. This class handles the reading and storing of configuration data. It stores the
dedbuggLevel, table layouts, path to log-file and which mode to use at startup. This is where information
that needs to be stored that hasn't anything to do with the network should be stored. The config.conf,
which is the file used, is easy to alter with a normal text-editor.
Constructors
Config
public Config()
Instantiates a new Config-object. Default path to conf-file is config.conf Uses default values, but
tries to read values from the config-file, if other values are found they will be updated.
Config
public Config(java.lang.String file)
Instantiates a new config with a given path.
Parameters:
file - the path to the configuration file.
Methods
getDebugFile
public java.lang.String getDebugFile()
Gets the debug file.
Returns:
the debug file
getDebugLevel
public int getDebugLevel()
Gets the debug level.
Returns:
the debug level
getMode
public java.lang.String getMode()
Gets the mode.
Returns:
the mode
getNT_AlarmSortOrder
public java.lang.String[] getNT_AlarmSortOrder()
Gets the n t_ alarm sort order.
Returns:
the n t_ alarm sort order
getNT_TCASortOrder
public java.lang.String[] getNT_TCASortOrder()
Gets the n t_ tca sort order.
Returns:
the n t_ tca sort order
getPath
public java.lang.String getPath()
Gets the path.
Returns:
the path
reSetConfig
public void reSetConfig(boolean b)
Resets the config-file. Alternatively it stores the stored data to the file. If the parameter is true then
the values will be reset to default before storing the information.
Parameters:
b - the b
setDebugFile
public void setDebugFile(java.lang.String path)
Sets the debug file.
Parameters:
path - the new debug file
setDebugLevel
public void setDebugLevel(int debugLevel)
Sets the debug level.
Parameters:
debugLevel - the new debug level
setMode
public void setMode(java.lang.String str)
Sets the mode.
Parameters:
str - the new mode
setNT_AlarmSortOrder
public void setNT_AlarmSortOrder(java.lang.String[] list)
Sets the n t_ alarm sort order.
Parameters:
list - the new n t_ alarm sort order
setNT_TCASortOrder
public void setNT_TCASortOrder(java.lang.String[] list)
Sets the n t_ tca sort order.
Parameters:
list - the new n t_ tca sort order
setPath
public void setPath(java.lang.String path)
Sets the path.
Parameters:
path - the new path
Package com.ericsson.eos.controller
Class Summary
MainController
The Class MainController.
RTAMController
The Class RTAMController.
TPController
The Class TPController.
TreeController
The Class TreeController.
com.ericsson.eos.controller
Class MainController
java.lang.Object
|
+--com.ericsson.eos.controller.MainController
java.awt.event.ActionListener, java.awt.event.WindowListener, java.io.Serializable
public class MainController

implements java.awt.event.ActionListener, java.awt.event.WindowListener, java.io.Serializable
The Class MainController.
Constructors
MainController
public MainController(MainView mv)
Instantiates a new main controller.
Parameters:
mv - the mv
Methods
actionPerformed
public void actionPerformed(java.awt.event.ActionEvent ae)
windowActivated
public void windowActivated(java.awt.event.WindowEvent arg0)
windowClosed
public void windowClosed(java.awt.event.WindowEvent arg0)
windowClosing
public void windowClosing(java.awt.event.WindowEvent arg0)
windowDeactivated
public void windowDeactivated(java.awt.event.WindowEvent arg0)
windowDeiconified
public void windowDeiconified(java.awt.event.WindowEvent arg0)
windowIconified
public void windowIconified(java.awt.event.WindowEvent arg0)
windowOpened
public void windowOpened(java.awt.event.WindowEvent arg0)
Class RTAMController
java.lang.Object
|
+--com.ericsson.eos.controller.RTAMController
java.awt.event.ActionListener, java.awt.event.MouseListener,
javax.swing.event.TableColumnModelListener
public class RTAMController

implements java.awt.event.ActionListener, java.awt.event.MouseListener,
javax.swing.event.TableColumnModelListener
The Class RTAMController.
Constructors
RTAMController
public RTAMController(RTAMView view,
MainView mv)
Instantiates a new RTAM controller. Needs the RTAMView and MainView as parameters to be
able to update some of the status related stuff.
Parameters:
view - the view
mv - the mv
Methods
actionPerformed
columnAdded
public void columnAdded(javax.swing.event.TableColumnModelEvent arg0)
columnMarginChanged
public void columnMarginChanged(javax.swing.event.ChangeEvent arg0)
columnMoved
public void columnMoved(javax.swing.event.TableColumnModelEvent arg0)
columnRemoved
public void columnRemoved(javax.swing.event.TableColumnModelEvent arg0)
columnSelectionChanged
public void columnSelectionChanged(javax.swing.event.ListSelectionEvent arg0)
filterActionPerformed
public void filterActionPerformed(java.awt.event.ActionEvent evt)
Filter action performed. This creates a new Filter for the RTAMView.
Parameters:
evt - the evt
mouseClicked
public void mouseClicked(java.awt.event.MouseEvent me)
mouseEntered
public void mouseEntered(java.awt.event.MouseEvent arg0)
mouseExited
public void mouseExited(java.awt.event.MouseEvent arg0)
mousePressed
public void mousePressed(java.awt.event.MouseEvent e)
mouseReleased
public void mouseReleased(java.awt.event.MouseEvent e)
nt_AlarmActionPerformed
public void nt_AlarmActionPerformed(java.awt.event.ActionEvent evt)
Nt_ alarm action performed. Change to alarm-view.
Parameters:
evt - the evt
nt_TCAActionPerformed
public void nt_TCAActionPerformed(java.awt.event.ActionEvent evt)
Nt_ tca action performed. Change to TCA-view
Parameters:
evt - the evt
showAlarm
public void showAlarm(java.lang.String type,
java.lang.String notificationID)
Show alarm. This function request the information from the model about a specific alarm or tca.
The information is extracted and displayed in the NT_AlarmPanel or the NT_TCAPanel.
Parameters:
type - the type
notificationID - the notification id
Class TPController
java.lang.Object
|
+--com.ericsson.eos.controller.TPController
java.awt.event.ActionListener, java.awt.event.MouseListener, java.io.Serializable,
javax.swing.event.ListSelectionListener
public class TPController

implements java.awt.event.ActionListener, java.awt.event.MouseListener, java.io.Serializable,
javax.swing.event.ListSelectionListener
The Class TPController. This is the Controller for the Termination Point Main View.
Constructors
TPController
public TPController(TPView tp,
Model model,
MainView mv)
Instantiates a new TP controller. Need the views that is should interact with and also the model to
being able to update the information showed.
Parameters:
tp - the TPView
model - the Model
mv - the MainView
Methods
actionPerformed
mouseClicked
mouseEntered
mouseExited
mousePressed
mouseReleased
valueChanged
public void valueChanged(javax.swing.event.ListSelectionEvent lse)
Class TreeController
java.lang.Object
|
+--com.ericsson.eos.controller.TreeController
java.awt.event.ActionListener, java.awt.event.MouseListener, java.io.Serializable,
javax.swing.event.TreeSelectionListener
public class TreeController

implements java.awt.event.ActionListener, java.awt.event.MouseListener, java.io.Serializable,
javax.swing.event.TreeSelectionListener
The Class TreeController. This is the controller class for the tree-structure to the left in the simulator.
Constructors
TreeController
public TreeController(TreeView tv,
Model m,
MainController m2,
MainView mv,
ModelSelection mts)
Instantiates a new tree controller.
Parameters:
tv - the tv
m - the m
m2 - the m2
mv - the mv
mts - the mts
Methods
actionPerformed
addToCurrentNode
public void addToCurrentNode(java.lang.String name)
Adds the to current node.
Parameters:
name - the name
mouseClicked
mouseEntered
mouseExited
mousePressed
mouseReleased
removeCurrentNode
public void removeCurrentNode()
Removes the current node.
valueChanged
public void valueChanged(javax.swing.event.TreeSelectionEvent tse)
Package com.ericsson.eos.database
Class Summary
MySQLConnector
The Class MySQLConnector.
MySQLDelete
The Class MySQLDelete.
MySQLGetters
The Class MySQLGetters.
MySQLInit
The Class MySQLInit.
MySQLSetters
The Class MySQLSetters contains all the JDBC set-functions.
MySQLUpdater
The Class MySQLUpdater.
XmlParser
The Class XmlParser.
com.ericsson.eos.database
Class MySQLConnector
java.lang.Object
|
+--MySQLInit
|
+--MySQLGetters
|
+--MySQLSetters
|
+--MySQLUpdater
|
+--MySQLDelete
|
+--com.ericsson.eos.database.MySQLConnector
DBI, java.io.Serializable
< Constructors >
public class MySQLConnector

extends MySQLDelete
implements DBI, java.io.Serializable
The Class MySQLConnector.

Constructors
MySQLConnector
public MySQLConnector()
Instantiates a new MySQL connector (used for xmlParser connection).
MySQLConnector
public MySQLConnector(Model m)
Instantiates a new MySQL connector.
Parameters:
m - the model
Class MySQLDelete
java.lang.Object
|
+--MySQLInit
|
+--MySQLGetters
|
+--MySQLSetters
|
+--MySQLUpdater
|
+--com.ericsson.eos.database.MySQLDelete
Direct Known Subclasses:
MySQLConnector
public class MySQLDelete

extends MySQLUpdater
The Class MySQLDelete. This class handles all the delete functionality that the database supports. All the
SQL-code needed to remove objects from the database is found here. This is part of the
MySQL-inheritance chain.
Constructors
MySQLDelete
public MySQLDelete()
Methods
deleteAlarm
public void deleteAlarm(java.lang.String notificationId)
Deletes the alarm with the given notificationId.
Parameters:
notificationId - the notification id
deleteCTP
public void deleteCTP(java.lang.String ems,
java.lang.String me,
java.lang.String ptp,
java.lang.String ctp)
Delete ctp. Deletes the CTP that is specified.
Parameters:
ems - the name of the EMS
me - the name of the ME
ptp - the name of the PTP/FTP
ctp - the name of the CTP that should be deleted
deleteEms
public void deleteEms(java.lang.String ems)
Delete ems. If the EMS is deleted all objects referring to the EMS are also deleted. This function
should be used carefully.
Parameters:
deleteME
public void deleteME(java.lang.String ems,
java.lang.String me)
Delete me. Deletes the ManagedElement.
Parameters:
me - the name of the ME that should be deleted
deleteMLSN
public void deleteMLSN(java.lang.String ems,
java.lang.String mlsn)
Delete mlsn. This function deletes an MultiLayerSubnetwork, and all the elements under it.
Parameters:
mlsn - the name of the subnet that should be deleted
deletePTP
public void deletePTP(java.lang.String ems,
java.lang.String ptp)
Delete ptp. Deletes the PTP/FTP that is specified.
Parameters:
me - the name of the ME
ptp - the name and type of the PTP/FTP that should be deleted
deleteTCA
public void deleteTCA(java.lang.String notificationId)
Delete tca. Deletes the TCA with the given notificationId.
Parameters:
deleteTL
public void deleteTL(java.lang.String ems,
java.lang.String tlName)
Delete tl. Deletes the Topological Link that is specified.
Parameters:
tlName - the name of the TL that should be deleted.
Class MySQLGetters
java.lang.Object
|
+--MySQLInit
|
+--com.ericsson.eos.database.MySQLGetters
MySQLSetters
public class MySQLGetters

extends MySQLInit
The Class MySQLGetters.
Constructors
MySQLGetters
public MySQLGetters()
Methods
getActiveAlarms
public java.util.ArrayList getActiveAlarms(java.lang.String ems,
java.lang.String managedElement)
Returns all active alarms on the specified managedElement.
Parameters:
ems - the ems
managedElement - the managed element
Returns:
the active alarms
getActiveTCAs
public java.util.ArrayList getActiveTCAs(java.lang.String ems,
Returns all active TCAs given the specified managedElement.
Parameters:
ems - the ems
Returns:
the active tc as
getAdditionalInfo
public java.util.ArrayList getAdditionalInfo(int id)
Gets the additional info belonging to a given object name ID.
Parameters:
id - the id
Returns:
the additional info
getAlarm
public java.util.HashMap getAlarm(java.lang.String notificationID)
Gets the alarm with the specified notificationID.
Parameters:
Returns:
the alarm
getAllActiveAlarms
public java.util.ArrayList getAllActiveAlarms()
Returns all NT_Alarms.
Returns:
the all active alarms
getAllActiveAlarmsFiltered
public java.util.ArrayList getAllActiveAlarmsFiltered(java.lang.String[]
severityFilter,
java.lang.String[]
probCauseFilter)
Returns alarms that don't contain severity values from severityFilter and probable causes from
probCauseFinter.
Parameters:
severityFilter - the severity filter
probCauseFilter - the prob cause filter
Returns:
alarms filtered on severity and probable cause
getAllActiveTCAs
public java.util.ArrayList getAllActiveTCAs()
Returns all NT_TCA.
Returns:
the all active TCAs
getAllActiveTCAsFiltered
public java.util.ArrayList getAllActiveTCAsFiltered(java.lang.String[]
severityFilter,
java.lang.String[]
probCauseFilter)
Returns TCAs that don't contain severity values from severityFilter and probable causes from
probCauseFinter.
Parameters:
severityFilter - the severity filter
Returns:
alarms filtered on severity and probable cause
getAllAlarmParameterNames
public java.util.ArrayList getAllAlarmParameterNames()
gets all attribute-names associated with nt_alarm.
Returns:
the all alarm parameter names
public java.util.ArrayList getAllManagedElements()
gets all managedElements.
Returns:
all managedElements
public java.util.ArrayList getAllManagedElements(java.lang.String ems,
java.lang.String subnetwork)
Gets all managed elements.
Parameters:
ems - the ems
subnetwork - the subnetwork
Returns:
the all managed elements
getAllTCAParameterNames
public java.util.ArrayList getAllTCAParameterNames()
gets all attribute-names associated with nt_tca.
Returns:
the all tca parameter names
public java.util.ArrayList getAllTopLevelSubnetworks()
Returns information on all TopLevelSubnetworks.
Returns:
ArryList a list of hashmaps containing all info on topLevelSubnetworks.
getAllTopologicalLinks
public java.util.ArrayList getAllTopologicalLinks()
returns all topologicalLinks.
Returns:
all topologicalLinks
getCTP
public java.util.HashMap getCTP(java.lang.String ems,
Gets the object structure given the CTP's objectName.
Parameters:
ems - the ems
me - the me
ptp - the ptp
ctp - the ctp
Returns:
the cTP
public java.lang.String[] getContainedCurrentTPNames(java.lang.String ems,
java.lang.String tp,
short[] layerRate)
Retrieves the names of the Contained Current TPs filtered on the listed layer-rates. A current CTP
is defined as either cross-connectable or cross-connected, in the current mapping configuration
which can be seen in the attribute tpMappingmode (set to
TM_NEITHER_TERMINATED_NOR_AVAILABLE_FOR_MAPPING or TM_NA). This means all
potential CTPs except those that are Terminated and mapped.
Parameters:
ems - the ems
me - the me
tp - the tp
layerRate - the layer rate
Returns:
the contained current tp names
public java.util.ArrayList getContainedCurrentTPs(java.lang.String ems,
short[] layerRate)
Gets the object structures of all contained current CTPs filtered on the listed layer-rates. A current
CTP is defined as either cross-connectable or cross-connected, in the current mapping
configuration which can be seen in the attribute tpMappingmode (set to
TM_NEITHER_TERMINATED_NOR_AVAILABLE_FOR_MAPPING or TM_NA). This means all
potential CTPs except those that are Terminated and mapped.
Parameters:
ems - the ems
me - the me
tp - the tp
Returns:
the contained current tps
getContainedInUseTPNames
public java.lang.String[] getContainedInUseTPNames(java.lang.String ems,
short[] layerRate)
Gets the names of contained In-Use CTPs filtered on the listed layer-rates. An In-Use CTP is
defined as a CTP used in SNC (in any state) or a CTP that is terminated and mapped. These are
CTPs used in SNCs as well as well as the CTPs with attribute tpMappingmode =
TM_TERMINATED_AND_AVAILABLE_FOR_MAPPING.
Parameters:
ems - the ems
me - the me
tp - the tp
Returns:
the contained in use tp names
public java.util.ArrayList getContainedInUseTPs(java.lang.String ems,
short[] layerRate)
Gets the object structures of contained In-Use CTPs filtered on the listed layer-rates. An In-Use
CTP is defined as a CTP used in SNC (in any state) or a CTP that is terminated and mapped.
These are CTPs used in SNCs as well as well as the CTPs with attribute tpMappingmode =
TM_TERMINATED_AND_AVAILABLE_FOR_MAPPING.
Parameters:
ems - the ems
me - the me
tp - the tp
Returns:
the contained in use t ps
public java.lang.String[] getContainedPotentialTPNames(java.lang.String ems,
short[] layerRate)
Gets the name of all potential CTPs given the specified layerRates and level3Object.
Parameters:
ems - the ems
me - the me
tp - the tp
Returns:
the contained potential tp names
public java.util.ArrayList getContainedPotentialTPs(java.lang.String ems,
short[] layerRate)
gets all potential CTPs given the specified layerRates and level3Object.
Parameters:
ems - the ems
me - the me
tp - the tp
Returns:
the contained potential t ps
getEMSName
public java.lang.String getEMSName()
returns the name of the EMS.
Returns:
the name of the EMS
getEms
public java.util.HashMap getEms()
Returns the object structure of the EMS.
Returns:
all attributes of EMS
getLayerParameters
public java.util.ArrayList getLayerParameters(int id)
Gets the layer parameters belonging to the object with the given objectname ID.
Parameters:
id - the id
Returns:
the layer parameters
getLayerRate
public java.lang.String getLayerRate(short s)
Gets the layer rate name given a short value. most name-short mappings can be found in the
TMF814 documentation.
Parameters:
s - the s
Returns:
the layer rate
getManagedElement
public java.util.HashMap getManagedElement(java.lang.String ems,
java.lang.String name)
Returns managedElement object structure given the ems and managed element name.
Parameters:
ems - the ems
name - the ME name
Returns:
managedElement data
getObjectName
public java.util.HashMap getObjectName(int id)
Gets the object name given the ID.
Parameters:
id - the id
Returns:
the object name
getObjectNameID
public int getObjectNameID(java.lang.String lev1,
java.lang.String lev2,
java.lang.String lev4)
Gets the ID number associated with the name of the object. Structured as a hierarchy of four
levels with type&%&name values.
Parameters:
lev1 - the lev1
lev2 - the lev2
lev3 - the lev3
lev4 - the lev4
Returns:
the object name id
getPTP
public java.util.HashMap getPTP(java.lang.String ems,
Gets the PTP object structure given it's object name.
Parameters:
ems - the ems
me - the me
ptp - the ptp
Returns:
the pTP
getPTPNames
public java.lang.String[] getPTPNames(java.lang.String ems,
return all level3object names (ptp,ftp) given ems and managedElement.
Parameters:
ems - the ems
me - the me
Returns:
the pTP names
getPTPs
public java.util.ArrayList getPTPs(java.lang.String ems,
gets all the PTPs/FTPs object structures under a managed element.
Parameters:
ems - EMS that the system simulates.
me - The specific managed element.
Returns:
All the ptps in hashmap for wrapped in a arraylist.
getSubNodes
public java.util.ArrayList getSubNodes(java.lang.String subnet)
Returns all the managedElement names under a given subnetwork.
Parameters:
subnet - the subnet
Returns:
the subnode names (managedElements) of an EMS
getSubnetwork
public java.util.HashMap getSubnetwork(java.lang.String ems,
Gets the subnetwork object structure given the object name.
Parameters:
ems - the ems
mlsn - the mlsn
Returns:
the subnetwork
getSupportedRates
public java.util.HashMap getSupportedRates(int id)
Gets the supported rates belonging to the specified object name ID.
Parameters:
id - the id
Returns:
the supported rates
getTCA
public java.util.HashMap getTCA(java.lang.String notificationID)
Gets the TCA.
Parameters:
Returns:
the TCA
getTopologicalLink
public java.util.HashMap getTopologicalLink(int id)
Gets the topological link object structure given the objectName ID.
Parameters:
id - the id
Returns:
the topological link
getX733AdditionalInfo
public java.util.ArrayList getX733AdditionalInfo(java.lang.String id)
Gets the x733 additional info given a notificationID.
Parameters:
id - the id
Returns:
the x733 additional info
getX733MonitoredAttribute
public java.util.ArrayList getX733MonitoredAttribute(java.lang.String id)
Gets the x733 monitored attributes given a notificationID.
Parameters:
id - the id
Returns:
the x733 monitored attribute
Class MySQLInit
java.lang.Object
|
+--com.ericsson.eos.database.MySQLInit
MySQLGetters
public class MySQLInit

The Class MySQLInit. This class handles the connection to the database. User-name and password can
be found and changed here, but the standard user are set to eos.
Constructors
MySQLInit
public MySQLInit()
Methods
connect
public void connect()
Connects to the database using given username and password when interface was created.
disconnect
public void disconnect()
Disconnects from the database. Use connect() to get a connection again.
isActive
public boolean isActive()
Returns true if the connection is active.
Returns:
true, if is active
reset
public void reset(java.lang.String fileName)
Reset the database. This function clears all the data from the database, use carefully. The file that
is given should contain all the needed information to clear and rebuild the the structure again. In
the case of this simulator a file containing the structure that first erases everything is used followed
by a file for all the static data.
Parameters:
fileName - the file name of the sql file.
Class MySQLSetters
java.lang.Object
|
+--MySQLInit
|
+--MySQLGetters
|
+--com.ericsson.eos.database.MySQLSetters
MySQLUpdater
public class MySQLSetters

extends MySQLGetters
The Class MySQLSetters contains all the JDBC set-functions. It is part of an inheritance chain to
MySQLConnector.
Constructors
MySQLSetters
public MySQLSetters()
Methods
setAdditionalInfo
public boolean setAdditionalInfo(int objectNameID,
java.lang.String[] addInfo)
Sets initial Additional Information Used when creating a new object.
Parameters:
objectNameID - the object name id
addInfo - the add info
Returns:
true, if successful
setCTP
public java.lang.String setCTP(java.lang.String emsName,
java.lang.String meName,
java.lang.String ptpName,
java.lang.String ctpName,
java.lang.String userLabel,
java.lang.String nativeEMSName,
java.lang.String owner,
java.lang.String type,
java.lang.String connectionState,
java.lang.String tpMappingMode,
java.lang.String direction,
java.lang.String tpProtectionAssociation,
java.lang.String edgePoint,
java.lang.String ingressName,
java.lang.String egressName,
Creates a new CTP.
Parameters:
emsName - the ems name
meName - the me name
ptpName - the ptp name
ctpName - the ctp name
userLabel - the user label
nativeEMSName - the native ems name
owner - the owner
type - the type
connectionState - the connection state
tpMappingMode - the tp mapping mode
direction - the direction
tpProtectionAssociation - the tp protection association
edgePoint - the edge point
ingressName - the ingress name
egressName - the egress name
Returns:
the string
setCrossConnection
public java.lang.String setCrossConnection(java.lang.String active,
java.lang.String ccType,
java.lang.String node1Ems,
java.lang.String node1Me,
java.lang.String node1lev3,
java.lang.String[] additionalInfo)
Creates a CrossConnection.
Parameters:
active - the active
ccType - the cc type
node1Ems - the node1 ems
node1Me - the node1 me
node1lev3 - the node1lev3
additionalInfo - the additional info
Returns:
the string
setEMS
public java.lang.String setEMS(java.lang.String emsName,
java.lang.String emsVersion,
Creates a new EMS.
Parameters:
owner - the owner
emsVersion - the ems version
type - the type
additionalInfo - ("name"+ &%& +"val")
Returns:
the string
setLayerParameters
public java.lang.String setLayerParameters(java.lang.String lev1,
java.lang.String layer,
java.lang.String[] paramName,
java.lang.String[] paramVal)
Sets the layer parameters.
Parameters:
lev1 - the lev1
lev2 - the lev2
lev3 - the lev3
lev4 - the lev4
layer - the layer
paramName - the param name
paramVal - the param val
Returns:
the string
setManagedElement
public java.lang.String setManagedElement(java.lang.String emsName,
java.lang.String subnetName,
java.lang.String location,
java.lang.String version,
java.lang.String productName,
java.lang.String communicationState,
java.lang.String emsInSyncState,
java.lang.String[] supportedRates,
Creates a new ManagedElement.
Parameters:
subnetName - the subnet name
location - the location
version - the version
productName - the product name
communicationState - the communication state
emsInSyncState - the ems in sync state
owner - the owner
supportedRates - the supported rates
Returns:
the string
setNT_Alarm
public java.lang.String setNT_Alarm(java.lang.String notificationId,
java.lang.String emsName,
java.lang.String level2Object,
java.lang.String nativeEmsName,
java.lang.String objectType,
java.lang.String objectTypeQualifier,
java.lang.String emsTime,
java.lang.String neTime,
java.lang.String isClearable,
java.lang.String layerRate,
java.lang.String perceivedSeverity,
java.lang.String acknowledgeIndication,
java.lang.String nativeProbableCause,
java.lang.String probableCause,
java.lang.String probableCauseQualifier,
java.lang.String serviceAffecting,
java.lang.String additionalText,
java.lang.String rcaiIndicator,
java.lang.String[] x733AdditionalInfo,
java.lang.String x733BackedUpStatus,
java.lang.String x733BackupObject,
java.lang.String[]
x733CorrelatedNotifications,
java.lang.String x733EventType,
java.lang.String[]
x733MonitoredAttributes,
java.lang.String[]
x733ProposedRepairActions,
java.lang.String[] x733SpecificProblems,
java.lang.String x733TrendIndication,
java.lang.String[] affectedTPList)
Sets alarms of type NT_ALARM. Use "" for a value not used, do not use NULL.
Parameters:
level2Object - the level2 object
nativeEmsName - the native ems name
objectType - the object type
objectTypeQualifier - the object type qualifier
emsTime - the ems time
neTime - the ne time
isClearable - the is clearable
perceivedSeverity - the perceived severity
acknowledgeIndication - the acknowledge indication
nativeProbableCause - the native probable cause
probableCause - the probable cause
probableCauseQualifier - the probable cause qualifier
serviceAffecting - the service affecting
additionalText - the additional text
rcaiIndicator - the rcai indicator
x733AdditionalInfo - the x733 additional info
x733BackedUpStatus - the x733 backed up status
x733BackupObject - the x733 backup object
x733CorrelatedNotifications - the x733 correlated notifications
x733EventType - the x733 event type
x733MonitoredAttributes - the x733 monitored attributes
x733ProposedRepairActions - the x733 proposed repair actions
x733SpecificProblems - the x733 specific problems
x733TrendIndication - the x733 trend indication
affectedTPList - the affected tp list
Returns:
the string
setNT_TCA
public java.lang.String setNT_TCA(java.lang.String notificationId,
java.lang.String emsName,
java.lang.String granularity,
java.lang.String pmParameterName,
java.lang.String pmLocation,
java.lang.String thresholdType,
java.lang.String floatValue,
java.lang.String unit,
java.lang.String acknowledgeIndication)
Creates alarm of type NT_TCA.
Parameters:
granularity - the granularity
pmParameterName - the pm parameter name
pmLocation - the pm location
thresholdType - the threshold type
floatValue - the float value
unit - the unit
Returns:
the string
setObjectName
public boolean setObjectName(java.lang.String lev1,
java.lang.String lev4)
Creates a new objectName for any type of object. level1 contains the name of the EMS, level2
contains the name of the MultiLayerSubnetwork, ManagedElement or TopologicalLink, level3
contains the name of the PTP/FTP or CrossConnection and level 4 contains the name of CTP.
Parameters:
lev1 - the lev1
lev2 - the lev2
lev3 - the lev3
lev4 - the lev4
Returns:
true, if successful
setPTP
public java.lang.String setPTP(java.lang.String emsName,
Creates a new PTP/FTP.
Parameters:
owner - the owner
type - the type
Returns:
the string
setSupportedRates
public boolean setSupportedRates(int objectNameID,
java.lang.String[] supportedRates)
Sets the supported rates for a given ObjectName ID.
Parameters:
objectNameID - the object name id
Returns:
true, if successful
setTopLevelSubnetwork
public java.lang.String setTopLevelSubnetwork(java.lang.String emsName,
java.lang.String subnetworkType,
java.lang.String[]
supportedRates,
java.lang.String[]
additionalInfo)
Creates a new top level subnetwork.
Parameters:
owner - the owner
subnetworkType - the subnetwork type
Returns:
the string
setTopologicalLink
public java.lang.String setTopologicalLink(java.lang.String emsName,
java.lang.String tlName,
java.lang.String rate,
java.lang.String node1PTP,
java.lang.String node1ctp,
creates a new TopologicalLink.
Parameters:
tlName - the tl name
owner - the owner
rate - the rate
node1PTP - the node1 ptp
node1ctp - the node1ctp
Returns:
the string
setX733AdditionalInfo
public boolean setX733AdditionalInfo(java.lang.String notificationID,
java.lang.String[] x733AdditionalInfo)
Sets the x733 additional info.
Parameters:
Returns:
true, if successful
setX733MonitoredAttribute
public boolean setX733MonitoredAttribute(java.lang.String notificationID,
java.lang.String[]
x733MonitoredAttributes)
Sets the x733 monitored attribute.
Parameters:
Returns:
true, if successful
Class MySQLUpdater
java.lang.Object
|
+--MySQLInit
|
+--MySQLGetters
|
+--MySQLSetters
|
+--com.ericsson.eos.database.MySQLUpdater
MySQLDelete
public class MySQLUpdater

extends MySQLSetters
The Class MySQLUpdater. This class contains all the functions for updating data already in the database.
Constructors
MySQLUpdater
public MySQLUpdater()
Methods
concat
public java.lang.String concat(java.lang.String[] list)
Concat.
Parameters:
list - the list
Returns:
the string
updateCTP
public void updateCTP(java.lang.String emsName,
java.lang.String newCTPName,
java.lang.String[] transmissionParameters,
Update ctp.
Parameters:
newCTPName - the new ctp name
owner - the owner
type - the type
transmissionParameters - the transmission parameters
updateEMS
public void updateEMS(java.lang.String emsName,
java.lang.String newEmsName,
Update ems.
Parameters:
newEmsName - the new ems name
owner - the owner
type - the type
updateManagedElement
public void updateManagedElement(java.lang.String emsName,
java.lang.String newMeName,
Update managed element.
Parameters:
newMeName - the new me name
owner - the owner
updateMultiLayerSubnetwork
public void updateMultiLayerSubnetwork(java.lang.String level1Object,
java.lang.String newLevel2Object,
java.lang.String[] layerRate,
Update multi layer subnetwork.
Parameters:
newLevel2Object - the new level2 object
owner - the owner
updateNTAlarm
public java.lang.String updateNTAlarm(java.lang.String notificationId,
java.lang.String ems,
java.lang.String[]
java.lang.String[]
java.lang.String[]
Update nt alarm.
Parameters:
ems - the ems
Returns:
the string
updateNTTCA
public java.lang.String updateNTTCA(java.lang.String notificationId,
java.lang.String value,
Update nttca.
Parameters:
ems - the ems
value - the value
unit - the unit
Returns:
the string
updatePTP
public void updatePTP(java.lang.String emsName,
java.lang.String newPTPName,
Update ptp.
Parameters:
newPTPName - the new ptp name
owner - the owner
type - the type
updateTopologicalLink
public void updateTopologicalLink(java.lang.String emsName,
java.lang.String newTlName,
java.lang.String node1ptp,
Update topological link.
Parameters:
newTlName - the new tl name
owner - the owner
rate - the rate
node1ptp - the node1ptp
Class XmlParser
java.lang.Object
|
|
+--com.ericsson.eos.database.XmlParser
java.io.Serializable, java.lang.Runnable
< Fields > < Constructors > < Methods >

public class XmlParser
implements java.io.Serializable, java.lang.Runnable
The Class XmlParser.
Fields
cancel
public boolean cancel
The cancel.
Constructors
XmlParser
public XmlParser()
Instantiates a new xml parser. This is used from the command-line.
XmlParser
public XmlParser(java.lang.String path)
Instantiates a new xml parser given the path. This is used from the GUI.
Parameters:
path - the path
Methods
clearDB
public void clearDB()
Clear db.
countFiles
public int countFiles(java.lang.String type)
Count files.
Parameters:
type - the type
Returns:
the int
main
The main method.
Parameters:
run
public void run()
Package com.ericsson.eos.debugger
Class Summary
Debugger
Debugger is a class developed for testing purpose only.
com.ericsson.eos.debugger
Class Debugger
java.lang.Object
|
|
+--com.ericsson.eos.debugger.Debugger
DebugInterface, java.io.Serializable
public class Debugger

implements DebugInterface, java.io.Serializable
Debugger is a class developed for testing purpose only. This class can either print event messages to file,
screen(command-line), both or not print at all.
Constructors
Debugger
public Debugger(Config conf)
Instantiates a new debugger.
Parameters:
conf - the conf
Methods
changedConf
public void changedConf(Config conf)
Changed conf.
Parameters:
conf - the conf
getMessages
public java.lang.String[] getMessages()
Gets the messages.
Returns:
the messages
setDebugToFile
public void setDebugToFile(boolean bool)
setDebugToFile turns on the feature to store the different events that occurs to a file. The file can
be located at debugEOS.log.
Parameters:
bool - the new debug to file
setDebugToScreen
public void setDebugToScreen(boolean bool)
setDebugToScreen turns on the feature to print the different events that occurs to the standard
output. This is usually the command-line.
Parameters:
bool - the new debug to screen
setMessages
public void setMessages(java.lang.String[] messages)
Sets the messages.
Parameters:
messages - the new messages
write
public void write(java.lang.String str,
java.lang.Object o,
java.util.logging.Level level)
write handles all the incoming messages and events. This is the function that all "debugging"
events should use. By giving this function a good description of the event that occurs debugging
will hopefully be a lot easier. Time-stamp is automatically added.
Parameters:
str - The string that contains the message or describes the event that should be
logged/printed.
o - The object or class that logged the message. This is were the message originates from.
level - the level
Package com.ericsson.eos.dynamicLoader
Class Summary
DynamicLoader
Handles the loading of input modules dynamically
com.ericsson.eos.dynamicLoader
Class DynamicLoader
java.lang.Object
|
+--com.ericsson.eos.dynamicLoader.DynamicLoader
public class DynamicLoader

Handles the loading of input modules dynamically
Author:
emikrie, Mikael Riedel
Constructors
DynamicLoader
public DynamicLoader(Model m)
Instantiates a new dynamic loader.
Parameters:
m - the model
Methods
loadModules
public java.util.ArrayList loadModules()
Load modules. This function loads all the modules that are inside a Jar-file and that complies with
the NBI-interface from the folder NBI.
Returns:
the array list
Package com.ericsson.eos.helper
Class Summary
InputChecker
The Class InputChecker.
Splitter
The Class Splitter.
TreePathDivider
The Class TreePathDivider.
com.ericsson.eos.helper
Class InputChecker
java.lang.Object
|
+--com.ericsson.eos.helper.InputChecker
< Methods >
public class InputChecker

The Class InputChecker.
Methods
checkInteger
public static boolean checkInteger(java.lang.String str)
Check integer. Returns true if the string contains only a integer.
Parameters:
str - the str
Returns:
true, if successful
checkShort
public static boolean checkShort(java.lang.String str)
Check short. Returns true if the string contains only a short.
Parameters:
str - the str
Returns:
true, if successful
Class Splitter
java.lang.Object
|
+--com.ericsson.eos.helper.Splitter
< Methods >
public class Splitter

The Class Splitter.
Methods
extensionFinder
public static java.lang.String extensionFinder(java.lang.String filePath)
Extension finder. This takes a path and only returns the file Extension of the file the path is
pointing at.
Parameters:
filePath - the file path
Returns:
the string
removeHardParentheses
public static java.lang.String removeHardParentheses(java.lang.String str)
Removes the hard parentheses.
Parameters:
str - the str
Returns:
the string
removeParentheses
public static java.lang.String removeParentheses(java.lang.String str)
Removes the parentheses.
Parameters:
str - the str
Returns:
the string
splitParentheses
public static java.lang.String[] splitParentheses(java.lang.String str)
Split parentheses. Removes all parentheses and removes everything else as a list of strings.
Parameters:
str - the str
Returns:
the string[]
Class TreePathDivider
java.lang.Object
|
+--com.ericsson.eos.helper.TreePathDivider
< Methods >
public class TreePathDivider

The Class TreePathDivider.

Methods
getDepth
public static int getDepth(java.lang.String str)
Gets the depth
Parameters:
str - the str
Returns:
the depth
getLast
public static java.lang.String getLast(java.lang.String path)
Gets the last selected element
Parameters:
path - the path
Returns:
the last
getList
public static java.lang.String[][] getList(java.lang.String str)
Gets the list. returns a list of the tree path.
Parameters:
str - the str
Returns:
the list
Package com.ericsson.eos.interfaces
Interface Summary
DBI
The Interface DBI.
DebugInterface
The Interface DebugInterface.
NBI
This interface should be implemented by all classes that want to use the simulator for north-bound
communication.
com.ericsson.eos.interfaces
Interface DBI
< Methods >
public interface DBI
The Interface DBI.
Methods
connect
public void connect()
Connects to the database using given username and password when interface was created.
deleteAlarm
public void deleteAlarm(java.lang.String notificationId)
Delete alarm.
Parameters:
deleteCTP
Delete ctp.
Parameters:
ems - the ems
me - the me
ptp - the ptp
ctp - the ctp
deleteEms
Delete ems.
Parameters:
ems - the ems
deleteME
Delete me.
Parameters:
ems - the ems
me - the me
deleteMLSN
Delete mlsn.
Parameters:
ems - the ems
mlsn - the mlsn
deletePTP
Delete ptp.
Parameters:
ems - the ems
me - the me
ptp - the ptp
deleteTCA
public void deleteTCA(java.lang.String notificationId)
Delete tca.
Parameters:
deleteTL
Delete tl.
Parameters:
ems - the ems
disconnect
public void disconnect()
Disconnects from the database. Use connect() to get a connection again.
getActiveAlarms
public java.util.ArrayList getActiveAlarms(java.lang.String ems,
Retrieves all active EMS and ME active alarms on the specified managedElement.
Parameters:
ems - the ems
Returns:
an ArrayList of Alarms, as HashMaps containing the attributes and values.
getActiveTCAs
public java.util.ArrayList getActiveTCAs(java.lang.String ems,
Gets the active tc as.
Parameters:
ems - the ems
Returns:
the active tc as
getAdditionalInfo
Gets the additional info.
Parameters:
id - the id
Returns:
the additional info
getAlarm
Retrieves alarm information of a specified alarm.
Parameters:
Returns:
a HashMap containing the attributes and values of the specified alarm.
getAllActiveAlarms
Gets the all active alarms.
Returns:
the all active alarms
getAllActiveAlarmsFiltered
public java.util.ArrayList getAllActiveAlarmsFiltered(java.lang.String[]
serverityFilter,
java.lang.String[]
probCauseFilter)
Retrieves alarms that don't contain severity values from severityFilter and probable causes from
probCauseFinter.
Parameters:
serverityFilter - the serverity filter
Returns:
the all active alarms filtered
getAllActiveTCAs
Gets the all active tcas.
Returns:
the all active tcas
getAllActiveTCAsFiltered
public java.util.ArrayList getAllActiveTCAsFiltered(java.lang.String[]
serverityFilter,
java.lang.String[]
probCauseFilter)
Gets the all active tc as filtered.
Parameters:
Returns:
the all active tc as filtered
getAllAlarmParameterNames
public java.util.ArrayList getAllAlarmParameterNames()
Gets the all alarm parameter names.
Returns:
the all alarm parameter names
Retrieves the object structures of all managedElements.
Returns:
an ArrayList of Managed elements.
Gets the all managed elements.
Parameters:
ems - the ems
Returns:
getAllTCAParameterNames
public java.util.ArrayList getAllTCAParameterNames()
Gets the all tca parameter names.
Returns:
the all tca parameter names
Gets the all top level subnetworks.
Returns:
the all top level subnetworks
Gets the all topological links.
Returns:
the all topological links
getCTP
Gets the cTP.
Parameters:
ems - the ems
me - the me
ptp - the ptp
ctp - the ctp
Returns:
the cTP
short[] layerRate)
Gets the contained current tp names.
Parameters:
ems - the ems
me - the me
tp - the tp
Returns:
short[] layerRate)
Gets the contained current tps.
Parameters:
ems - the ems
me - the me
tp - the tp
Returns:
the contained current tps
short[] layerRate)
Gets the contained in use tp names.
Parameters:
ems - the ems
me - the me
tp - the tp
Returns:
short[] layerRate)
Gets the contained in use tps.
Parameters:
ems - the ems
me - the me
tp - the tp
Returns:
the contained in use tps
short[] layerRate)
Gets the contained potential tp names.
Parameters:
ems - the ems
me - the me
tp - the tp
Returns:
short[] layerRate)
Gets the contained potential tps.
Parameters:
ems - the ems
me - the me
tp - the tp
Returns:
the contained potential tps
getEMSName
public java.lang.String getEMSName()
Retrieves the EMS name.
Returns:
the EMS name.
getEms
Retrieves the EMS.
Returns:
a Hashmap of attributes.
getLayerParameters
Gets the layer parameters.
Parameters:
id - the id
Returns:
getLayerRate
Gets the layer rate.
Parameters:
s - the s
Returns:
the layer rate
getManagedElement
Retrieves the managedElement information for a given objectName.
Parameters:
ems - the ems
name - the name
Returns:
a Hashmap of attributes.
getObjectName
Retrieves the objectName that belongs to the given id.
Parameters:
id - the id
Returns:
a Hashmap containing the hierarchical structure of level and name values.
getObjectNameID
public int getObjectNameID(java.lang.String level1Object,
java.lang.String level4Object)
Retrieves the ID of the objectname given the name in the form of a hierarchical structure.
Parameters:
Returns:
the object name id
getPTP
Gets the pTP.
Parameters:
ems - the ems
me - the me
ptp - the ptp
Returns:
the pTP
getPTPNames
Gets the pTP names.
Parameters:
ems - the ems
me - the me
Returns:
the pTP names
getPTPs
Gets the pT ps.
Parameters:
ems - the ems
me - the me
Returns:
the pT ps
getSubNodes
public java.util.ArrayList getSubNodes(java.lang.String subnet)
Retrieves all ManagedElements under a given subnetwork.
Parameters:
subnet - the subnet
Returns:
an ArrayList of Names.
getSubnetwork
Gets the subnetwork.
Parameters:
ems - the ems
mlsn - the mlsn
Returns:
the subnetwork
getSupportedRates
Gets the supported rates.
Parameters:
id - the id
Returns:
the supported rates
getTCA
Gets the tCA.
Parameters:
Returns:
the tCA
getTopologicalLink
Gets the topological link.
Parameters:
id - the id
Returns:
the topological link
Gets the x733 additional info.
Parameters:
id - the id
Returns:
Gets the x733 monitored attribute.
Parameters:
id - the id
Returns:
isActive
public boolean isActive()
Checks if is active.
Returns:
true, if is active
reset
public void reset(java.lang.String fileName)
Resets database to default structure with empty tables.
Parameters:
fileName - the file name
setCTP
public java.lang.String setCTP(java.lang.String ems,
java.lang.String ctp,
Creates a new CTP.
Parameters:
ems - the ems
me - the me
ptp - the ptp
ctp - the ctp
owner - the owner
type - the type
Returns:
either null or an error message
setCrossConnection
public java.lang.String setCrossConnection(java.lang.String active,
java.lang.String ccType,
Creates a new CrossConnection.
Parameters:
active - the active
ccType - the cc type
Returns:
setEMS
public java.lang.String setEMS(java.lang.String ems,
Creates a new EMS.
Parameters:
ems - the ems
owner - the owner
type - the type
Returns:
setLayerParameters
public java.lang.String setLayerParameters(java.lang.String ems,
java.lang.String[] paramVal)
For a specified TP, a certain layer can be given several parameter names and values.
Parameters:
ems - the ems
me - the me
ptp - the ptp
ctp - the ctp
layer - the layer
paramVal - the param val
Returns:
setManagedElement
public java.lang.String setManagedElement(java.lang.String emsName,
Creates a new ManagedElement.
Parameters:
owner - the owner
Returns:
setNT_Alarm
public java.lang.String setNT_Alarm(java.lang.String notificationId,
java.lang.String[]
java.lang.String[]
java.lang.String[]
Creates a new NT_Alarm.
Parameters:
ems - the ems
me - the me
ptp - the ptp
ctp - the ctp
Returns:
setNT_TCA
public java.lang.String setNT_TCA(java.lang.String notificationId,
java.lang.String level2Obj,
java.lang.String floatValue,
Creates a new NT_TCA.
Parameters:
ems - the ems
level2Obj - the level2 obj
floatValue - the float value
unit - the unit
Returns:
setPTP
public java.lang.String setPTP(java.lang.String ems,
Creates a new PTP.
Parameters:
ems - the ems
me - the me
ptp - the ptp
owner - the owner
type - the type
Returns:
setTopLevelSubnetwork
public java.lang.String setTopLevelSubnetwork(java.lang.String ems,
java.lang.String multiLayerSN,
java.lang.String[] shorts,
Creates a new TopLevelSubnetwork.
Parameters:
ems - the ems
multiLayerSN - the multi layer sn
owner - the owner
shorts - the shorts
Returns:
setTopologicalLink
public java.lang.String setTopologicalLink(java.lang.String ems,
Creates a new TopologicalLink.
Parameters:
ems - the ems
owner - the owner
rate - the rate
Returns:
updateCTP
Changes attributes for the given CTP. null values leave the attributes unchanged.
Parameters:
owner - the owner
type - the type
updateEMS
Changes EMS attributes. null values leave the attributes unchanged.
Parameters:
emsName - The name of the EMS you are changing
owner - the owner
type - the type
java.lang.String oldMeName,
Changes attributes for the given Managed Element. null values leave the attributes unchanged.
Parameters:
oldMeName - The name of the Managed Element you are changing.
newMeName - Can be used to give the Managed Element a new name.
owner - the owner
public void updateMultiLayerSubnetwork(java.lang.String level1Object,
java.lang.String newLevel2Object,
Changes attributes for the given MultiLayerSubnetwork. null values leave the attributes
unchanged.
Parameters:
level2Object - The name of the Subnetwork you are changing.
newLevel2Object - Can be used to give the Subnetwork a new name.
owner - the owner
updateNTAlarm
public java.lang.String updateNTAlarm(java.lang.String notificationID,
java.lang.String[]
java.lang.String[]
java.lang.String[]
Update nt alarm.
Parameters:
Returns:
the string
updateNTTCA
Update nttca.
Parameters:
ems - the ems
value - the value
unit - the unit
Returns:
the string
updatePTP
java.lang.String PTPName,
java.lang.String[] tramsmissionParameters,
Changes attributes for the given PTP/FTP. null values leave the attributes unchanged.
Parameters:
PTPName - the pTP name
newPTPName - Can be used to give the Managed Element a new name.
owner - the owner
type - the type
tramsmissionParameters - the tramsmission parameters
java.lang.String oldTlName,
Update topological link.
Parameters:
oldTlName - the old tl name
owner - the owner
rate - the rate
Interface DebugInterface
< Methods >
public interface DebugInterface
The Interface DebugInterface.
Methods
setDebugToFile
public void setDebugToFile(boolean bool)
Sets the debug to file.
Parameters:
bool - the new debug to file
setDebugToScreen
public void setDebugToScreen(boolean bool)
Sets the debug to screen.
Parameters:
bool - the new debug to screen
write
public void write(java.lang.String message,
java.lang.Object from,
Write.
Parameters:
message - the message
from - the from
level - the level
Interface NBI
< Methods >
public interface NBI
This interface should be implemented by all classes that want to use the simulator for north-bound
communication.
Methods
acknowledgeAlarms
public java.util.ArrayList acknowledgeAlarms(java.util.ArrayList alarms,
java.util.ArrayList addInfo)
Acknowledge alarms.
Parameters:
alarms - the alarms
Returns:
the array list
debug
public void debug(java.lang.String str,
java.lang.Object o,
Debug.
Parameters:
str - the str
o - the o
level - the level
getActive
public boolean getActive()
Gets the active.
Returns:
the active
getAdditionalInfo
Parameters:
id - the id
Returns:
the additional info
getAlarms
public java.util.ArrayList getAlarms(java.lang.String[] severity,
java.lang.String[] probableCause)
Gets the alarms.
Parameters:
severity - the severity
Returns:
the alarms
getAllAlarms
public java.lang.String[] getAllAlarms()
Gets the all alarms.
Returns:
the all alarms
Returns:
Parameters:
ems - the ems
Returns:
getAllNodes
public java.lang.String[] getAllNodes()
Gets the all nodes.
Returns:
the all nodes
getAllTL
public java.lang.String[] getAllTL()
Gets the all tl.
Returns:
the all tl
getAllTopLevelSubnetworkLayerRates
public java.util.ArrayList getAllTopLevelSubnetworkLayerRates(int ems,
java.lang.String
subnet)
Gets the all top level subnetwork layer rates.
Parameters:
ems - the ems
subnet - the subnet
Returns:
the all top level subnetwork layer rates
Gets the all top level subnetworks.
Returns:
the all top level subnetworks
getCTP
Gets the cTP.
Parameters:
ems - the ems
me - the me
ptp - the ptp
ctp - the ctp
Returns:
the cTP
short[] layerRate)
Gets the contained current tp names.
Parameters:
ems - the ems
me - the me
tp - the tp
Returns:
short[] layerRate)
Gets the contained current t ps.
Parameters:
ems - the ems
me - the me
tp - the tp
Returns:
the contained current t ps
short[] layerRate)
Gets the contained in use tp names.
Parameters:
ems - the ems
me - the me
tp - the tp
Returns:
short[] layerRate)
Gets the contained in use t ps.
Parameters:
ems - the ems
me - the me
tp - the tp
Returns:
the contained in use t ps
short[] layerRate)
Gets the contained potential tp names.
Parameters:
ems - the ems
me - the me
tp - the tp
Returns:
short[] layerRate)
Gets the contained potential t ps.
Parameters:
ems - the ems
me - the me
tp - the tp
Returns:
the contained potential t ps
getEms
Gets the ems.
Returns:
the ems
getInterfaceName
public java.lang.String getInterfaceName()
This function should return the name that is associated with the NBI implementation, preferably the
name of the protocol. It will be used when displaying the different NBI:s in the GUI, and when to
choose which that should be active.
Returns:
The name of the NBI implementation.
getLayerParameters
public java.util.ArrayList getLayerParameters(int objectID)
Parameters:
objectID - the object id
Returns:
getManagedElement
Gets the managed element.
Parameters:
ems - the ems
me - the me
Returns:
the managed element
getNodes
public java.lang.String[] getNodes(java.lang.String node)
Gets the nodes.
Parameters:
node - the node
Returns:
the nodes
getObjectName
public java.util.HashMap getObjectName(int objectId)
Gets the object name.
Parameters:
objectId - the object id
Returns:
the object name
getPTP
Gets the pTP.
Parameters:
ems - the ems
me - the me
ptp - the ptp
Returns:
the pTP
getPTPs
Gets the pT ps.
Parameters:
ems - the ems
me - the me
Returns:
the pT ps
getSubnetwork
Gets the subnetwork.
Parameters:
ems - the ems
mlsn - the mlsn
Returns:
the subnetwork
getSubnodes
public java.lang.String[] getSubnodes(java.lang.String node)
Gets the subnodes.
Parameters:
node - the node
Returns:
the subnodes
getSupportedRates
Parameters:
id - the id
Returns:
the supported rates
getTL
public java.lang.String[] getTL(java.lang.String node)
Gets the tL.
Parameters:
node - the node
Returns:
the tL
getTopNode
public java.lang.String getTopNode()
Gets the top node.
Returns:
the top node
Gets the x733 additional info.
Parameters:
id - the id
Returns:
Gets the x733 monitored attribute.
Parameters:
id - the id
Returns:
notificate
public void notificate(org.omg.CosNotification.StructuredEvent se)
This function sends the alarm that is given through the channel that setupNotificationRoute()
setups. It is up to the receiving end to handle the alarm after it has passed through the NBI.
Parameters:
se - the se
sendAlarm
public void sendAlarm(java.util.HashMap alarm)
Send alarm.
Parameters:
alarm - the alarm
sendAttributeChanged
public void sendAttributeChanged(java.lang.String emsName,
java.lang.String notificationId,
java.lang.String edgePointRelated,
java.lang.String[] attributList)
Send attribute changed.
Parameters:
edgePointRelated - the edge point related
attributList - the attribut list
sendHeartBeat
public void sendHeartBeat(java.lang.String ems,
java.lang.String notificationID,
java.lang.String emsTime)
Send heart beat.
Parameters:
ems - the ems
me - the me
sendStateChanged
public void sendStateChanged(java.lang.String emsName,
Send state changed.
Parameters:
setActive
public void setActive(boolean bool)
Sets the active.
Parameters:
bool - the new active
setModel
public void setModel(Model model)
Sets the model.
Parameters:
model - the new model
setupNotificationRoute
public void setupNotificationRoute()
To be able to use notification, the implementation of NBI have to setup the communication to the
receiving end on it's own. This function will be run at startup for each found implementation of NBI
and will thereby secure a channel for forwarding alarms over the north bound interface.
unacknowledgeAlarms
public java.util.ArrayList unacknowledgeAlarms(java.util.ArrayList alarms,
Unacknowledge alarms.
Parameters:
alarms - the alarms
Returns:
the array list
updateEMS
Update ems.
Parameters:
owner - the owner
type - the type
Package com.ericsson.eos.junitTests
Class Summary
AllTests
GetterTester
MySQLTest
com.ericsson.eos.junitTests
Class AllTests
java.lang.Object
|
+--com.ericsson.eos.junitTests.AllTests
public class AllTests

Constructors
AllTests
public AllTests()
Methods
main
suite
public static junit.framework.Test suite()
Class GetterTester
java.lang.Object
|
+--com.ericsson.eos.junitTests.GetterTester
< Constructors >
public class GetterTester

Constructors
GetterTester
public GetterTester()
Class MySQLTest
java.lang.Object
|
+--junit.framework.Assert
|
+--junit.framework.TestCase
|
+--com.ericsson.eos.junitTests.MySQLTest
junit.framework.Test
public class MySQLTest

extends junit.framework.TestCase
Constructors
MySQLTest
public MySQLTest()
Methods
setUp
public void setUp()
Overrides:
setUp in class junit.framework.TestCase
tearDown
public void tearDown()
Overrides:
tearDown in class junit.framework.TestCase
testFilterCritical
public void testFilterCritical()
testFilterLOS
public void testFilterLOS()
testFilterWarning
public void testFilterWarning()
testNoCorrectFilter
public void testNoCorrectFilter()
Package com.ericsson.eos.model
Class Summary
Model
Model.java - Create a model object to get access to setters, getters, update and delete functions
for TMF814 object types.
ModelAlarm
The Class ModelAlarm.
ModelCtp
The Class ModelCtp.
ModelEms
The Class ModelEms.
ModelHelper
The Class ModelHelper.
ModelInit
The Class ModelInit.
ModelMe
The Class ModelMe.
ModelMlsn
The Class ModelMlsn.
ModelPtp
The Class ModelPtp.
ModelSelection
The Class ModelSelection.
ModelTca
The Class ModelTca.
ModelTl
The Class ModelTl.
MyTableModel
The Class MyTableModel.
com.ericsson.eos.model
Class Model
java.lang.Object
|
|
+--ModelInit
|
+--ModelHelper
|
+--ModelEms
|
+--ModelMe
|
+--ModelPtp
|
+--ModelCtp
|
+--ModelMlsn
|
+--ModelTl
|
+--ModelTca
|
+--ModelAlarm
|
+--com.ericsson.eos.model.Model
< Constructors >
public class Model

extends ModelAlarm
Model.java - Create a model object to get access to setters, getters, update and delete functions for
TMF814 object types. Part of the Model-View-Controller architecture for the GUI, and an access point to
TMF814 objects for the Northbound Interface NBI. Model.java communicates with the database through
the Database Interface DBI. Debug messages are created for all functions except for get functions.
Constructors
Model
public Model()
Instantiates a new model.
Class ModelAlarm
java.lang.Object
|
|
+--ModelInit
|
+--ModelHelper
|
+--ModelEms
|
+--ModelMe
|
+--ModelPtp
|
+--ModelCtp
|
+--ModelMlsn
|
+--ModelTl
|
+--ModelTca
|
+--com.ericsson.eos.model.ModelAlarm

Model
public class ModelAlarm

extends ModelTca
The Class ModelAlarm.
Constructors
ModelAlarm
public ModelAlarm()
Methods
acknowledgeAlarm
public java.lang.String acknowledgeAlarm(java.lang.String notificationId,
java.lang.String
acknowledgeIndication,
java.lang.String[]
x733AdditionalInfo)
Acknowledge or unacknowledge alarms.
Parameters:
Returns:
true if acknowledge/unacknowledge succeeded.
deleteAlarms
public void deleteAlarms(java.util.ArrayList list)
Delete alarms.
Parameters:
list - the list
getAlarm
Gets the alarm.
Parameters:
Returns:
the alarm
getAlarms
public java.util.ArrayList getAlarms(java.lang.String[] serverityFilter,
java.lang.String[] probCauseFilter)
Retrieves all alarms filtered on severity and probableCause.
Parameters:
Returns:
an ArrayList of HashMaps containing the attributes and values of the filtered alarms.
getAllActiveAlarms
Retrieves all EMS and ME active alarms.
Returns:
an ArrayList of HashMaps containing attributes and values.
getAllAlarmParameters
public java.util.ArrayList getAllAlarmParameters()
Retrieves all the attribute names of an alarm. used from the GUI.
Returns:
an arrayList of attribute names.
Retrieves X733 AdditionalInfo for the specified alarm.
Parameters:
id - the id
Returns:
Retrieves.
Parameters:
id - the id
Returns:
setNT_ALARM
public java.lang.String setNT_ALARM(java.lang.String notificationId,
java.lang.String clearable,
java.lang.String[] affectedTPList,
java.lang.String[]
java.lang.String[]
java.lang.String[]
Creates a new NT_Alarm.
Parameters:
ems - the ems
clearable - the clearable
Returns:
the string
updateAlarm
public java.lang.String updateAlarm(java.lang.String notificationID,
java.lang.String clearable,
java.lang.String[]
java.lang.String[]
java.lang.String[]
Change alarm attribute values.
Parameters:
clearable - the clearable
Returns:
the string
Class ModelCtp
java.lang.Object
|
|
+--ModelInit
|
+--ModelHelper
|
+--ModelEms
|
+--ModelMe
|
+--ModelPtp
|
+--com.ericsson.eos.model.ModelCtp

ModelMlsn
public class ModelCtp

extends ModelPtp
The Class ModelCtp.
Constructors
ModelCtp
public ModelCtp()
Methods
createCTP
public void createCTP(java.lang.String emsName,
Create a new CTP.
Parameters:
owner - the owner
type - the type
deleteCTP
Delete ctp.
Parameters:
ems - the ems
me - the me
ptp - the ptp
ctp - the ctp
getCTP
Gets the cTP.
Parameters:
ems - the ems
me - the me
ptp - the ptp
ctp - the ctp
Returns:
the cTP
short[] layerRate)
Get all Current TP names.
Parameters:
ems - the ems
me - the me
tp - the tp
Returns:
a list of names.
short[] layerRate)
Get all Current TPs.
Parameters:
ems - the ems
me - the me
tp - the tp
Returns:
an ArrayList of HashMaps containing the attributes and values.
short[] layerRate)
Get all InUseTPNames.
Parameters:
ems - the ems
me - the me
tp - the tp
Returns:
a list of names.
short[] layerRate)
Get all Contained InUse TPs.
Parameters:
ems - the ems
me - the me
tp - the tp
Returns:
short[] layerRate)
Get all Contained Potential TP Names.
Parameters:
ems - the ems
me - the me
tp - the tp
Returns:
a list of names.
short[] layerRate)
Gets the contained potential t ps.
Parameters:
ems - the ems
me - the me
tp - the tp
Returns:
updateCTP
java.lang.String[] layerParam,
Update ctp.
Parameters:
owner - the owner
type - the type
layerParam - the layer param
Class ModelEms
java.lang.Object
|
|
+--ModelInit
|
+--ModelHelper
|
+--com.ericsson.eos.model.ModelEms

ModelMe
public class ModelEms

extends ModelHelper
The Class ModelEms.
Constructors
ModelEms
public ModelEms()
Methods
deleteEms
Remove the EMS and all underlying objects.
Parameters:
ems - the ems
getEms
Retrieve the EMS information.
Returns:
a HashMap with attributes and values respectively.
getEmsName
public java.lang.String getEmsName()
Retrieve the EMS Name.
Returns:
A String representation of the EMS Name.
setEMS
public void setEMS(java.lang.String ems,
Set the EMS information. Used by the parser during system initialization.
Parameters:
ems - the ems
owner - the owner
type - the type
updateEMS
java.lang.String newEMSName,
Change EMS attribute values. Notifies NBI about changes.
Parameters:
newEMSName - the new ems name
owner - the owner
type - the type
Class ModelHelper
java.lang.Object
|
|
+--ModelInit
|
+--com.ericsson.eos.model.ModelHelper

ModelEms
public class ModelHelper

extends ModelInit
The Class ModelHelper.
Constructors
ModelHelper
public ModelHelper()
Methods
changing
public void changing(java.lang.String type)
Changing.
Parameters:
type - the type
createTransmissionParameters
public void createTransmissionParameters(java.lang.String emsName,
java.lang.String[] paramValue)
Creates the transmission parameters.
Parameters:
layer - the layer
paramValue - the param value
getAdditionalInfo
Parameters:
id - the id
Returns:
the additional info
getConf
public Config getConf()
Gets the conf.
Returns:
the conf
getDatabaseStatus
public boolean getDatabaseStatus()
Gets the database status.
Returns:
the database status
getDebug
public Debugger getDebug()
Gets the debug.
Returns:
the debug
getLayerParameters
Parameters:
id - the id
Returns:
getLayerRate
Gets the layer rate.
Parameters:
s - the s
Returns:
the layer rate
getNBI
public NBI getNBI(java.lang.String name)
Gets the nBI.
Parameters:
name - the name
Returns:
the nBI
getNBIs
public java.util.ArrayList getNBIs()
Gets the nB is.
Returns:
the nB is
getObjectName
Gets the object name.
Parameters:
id - the id
Returns:
the object name
getObjectNameId
public int getObjectNameId(java.lang.String level1Object,
Gets the object name id.
Parameters:
Returns:
the object name id
getObjectNameId
public int getObjectNameId(java.lang.String level1Object,
Gets the object name id.
Parameters:
Returns:
the object name id
getServiceStatus
public boolean getServiceStatus()
Gets the service status.
Returns:
the service status
getSupportedRates
Parameters:
id - the id
Returns:
the supported rates
printHashMap
public void printHashMap(java.util.HashMap temp)
Prints the hash map.
Parameters:
temp - the temp
resetDB
public void resetDB()
Reset db.
setDebugger
public void setDebugger(Debugger debug)
Sets the debugger.
Parameters:
debug - the new debugger
setServiceStatus
public void setServiceStatus(boolean bool)
Sets the service status.
Parameters:
bool - the new service status
Class ModelInit
java.lang.Object
|
|
+--com.ericsson.eos.model.ModelInit

ModelHelper
< Constructors >
public class ModelInit

The Class ModelInit.
Constructors
ModelInit
public ModelInit()
Instantiates a new model init.
Class ModelMe
java.lang.Object
|
|
+--ModelInit
|
+--ModelHelper
|
+--ModelEms
|
+--com.ericsson.eos.model.ModelMe

ModelPtp
public class ModelMe

extends ModelEms
The Class ModelMe.
Constructors
ModelMe
public ModelMe()
Methods
deleteME
Delete the managed element with the give ems- and me-name.
Parameters:
ems - the ems
me - the me
Retrieve all Managed Elements.
Returns:
Retrieve all Managed elements under the given subnetwork.
Parameters:
ems - the ems
Returns:
getManagedElement
Retrieve the managed Element with the given ems- and me-name.
Parameters:
ems - the ems
name - the name
Returns:
a Hashmap containing attributes and values.
getMeStatus
public int getMeStatus(java.lang.String node)
Retrieve the given managed element's communication state status.
Parameters:
node - the node
Returns:
1 if the communication state of the managed element is CS_AVAILABLE, 0 if it is
CS_UNAVAILABLE.
setManagedElement
public void setManagedElement(java.lang.String emsName,
Create a new ManagedElement.
Parameters:
owner - the owner
java.lang.String oldMeName,
Change ManagedElement attribute values. Notifies NBI about changes.
Parameters:
oldMeName - the old me name
newMeName - the new me name
owner - the owner
Class ModelMlsn
java.lang.Object
|
|
+--ModelInit
|
+--ModelHelper
|
+--ModelEms
|
+--ModelMe
|
+--ModelPtp
|
+--ModelCtp
|
+--com.ericsson.eos.model.ModelMlsn

ModelTl
public class ModelMlsn

extends ModelCtp
The Class ModelMlsn.
Constructors
ModelMlsn
public ModelMlsn()
Methods
deleteMLSN
Removes the multiLayerSubnetwork.
Parameters:
ems - the ems
mlsn - the mlsn
Retrieve all MultiLayerSubnetworks.
Returns:
getSubNodes
public java.util.ArrayList getSubNodes(java.lang.String ems)
Retrieves all the MultiLayerSubnetworkNames under the given ems.
Parameters:
ems - the ems
Returns:
an ArrayList of names.
getSubnetwork
Retrieves the MultiLayerSubnetwork with the given ems- and subnetwork-name.
Parameters:
ems - the ems
mlsn - the mlsn
Returns:
a HashMap containing attributes and values.
setMultiLayerSubnetwork
public void setMultiLayerSubnetwork(java.lang.String ems,
java.lang.String multiLayerSN,
java.lang.String[] layerRates,
Create a new MultiLayerSubnetwork.
Parameters:
ems - the ems
multiLayerSN - the multi layer sn
owner - the owner
layerRates - the layer rates
public void updateMultiLayerSubnetwork(java.lang.String ems,
java.lang.String subnet,
java.lang.String newSubnet,
Change MultiLayerSubnetwork attribute values. Notifies NBI about changes.
Parameters:
ems - the ems
subnet - the subnet
newSubnet - the new subnet
owner - the owner
Class ModelPtp
java.lang.Object
|
|
+--ModelInit
|
+--ModelHelper
|
+--ModelEms
|
+--ModelMe
|
+--com.ericsson.eos.model.ModelPtp

ModelCtp
public class ModelPtp

extends ModelMe
The Class ModelPtp.
Constructors
ModelPtp
public ModelPtp()
Methods
deletePTP
Delete the PTP/FTP.
Parameters:
ems - the ems
me - the me
ptp - the ptp
getPTP
Get PTP/FTP information.
Parameters:
ems - the ems
me - the me
ptp - the ptp
Returns:
getPTPNames
Retrieve all PTP/FTP Names.
Parameters:
ems - the ems
me - the me
Returns:
a list of Strings
getPTPs
Retrieve all PTP's and FTP's under the given ems- and an mename.
Parameters:
ems - the ems
me - the me
Returns:
setPTP
public void setPTP(java.lang.String emsName,
Creates a new PTP/FTP.
Parameters:
owner - the owner
type - the type
updatePTP
java.lang.String[] layerParam,
Change PTP/FTP attribute values. Notifies NBI about changes.
Parameters:
newPTPName - the new ptp name
owner - the owner
type - the type
layerParam - the layer param
Class ModelSelection
java.lang.Object
|
|
+--com.ericsson.eos.model.ModelSelection
public class ModelSelection

The Class ModelSelection.
Constructors
ModelSelection
public ModelSelection(java.lang.String type)
Instantiates a new model selection.
Parameters:
type - the type
Methods
getLastSelected
public java.lang.String getLastSelected()
Gets the last selected.
Returns:
the last selected
getLastSelectedLevel
public int getLastSelectedLevel()
Gets the last selected level.
Returns:
the last selected level
getSelectedPaths
public java.lang.String[] getSelectedPaths()
Gets the selected paths.
Returns:
the selected paths
setLastSelected
public void setLastSelected(java.lang.String lastSelected,
int level)
Sets the last selected.
Parameters:
lastSelected - the last selected
level - the level
setSelectedPaths
public void setSelectedPaths(java.lang.String[] selectedPaths)
Sets the selected paths.
Parameters:
selectedPaths - the new selected paths
Class ModelTca
java.lang.Object
|
|
+--ModelInit
|
+--ModelHelper
|
+--ModelEms
|
+--ModelMe
|
+--ModelPtp
|
+--ModelCtp
|
+--ModelMlsn
|
+--ModelTl
|
+--com.ericsson.eos.model.ModelTca

ModelAlarm
public class ModelTca

extends ModelTl
The Class ModelTca.
Constructors
ModelTca
public ModelTca()
Methods
createNT_TCA
public void createNT_TCA(java.lang.String notificationId,
Creates the n t_ tca.
Parameters:
ems - the ems
value - the value
unit - the unit
deleteTCAs
public void deleteTCAs(java.util.ArrayList list)
Delete tcas.
Parameters:
list - the list
getAllActiveTCAs
Gets the all active tcas.
Returns:
the all active tcas
getAllTCAParameters
public java.util.ArrayList getAllTCAParameters()
Gets the all tca parameters.
Returns:
the all tca parameters
getTCA
Gets the tCA.
Parameters:
Returns:
the tCA
getTCAs
public java.util.ArrayList getTCAs(java.lang.String[] serverityFilter,
java.lang.String[] probCauseFilter)
Gets the tC as.
Parameters:
Returns:
the tC as
updateNTTCA
Update nttca.
Parameters:
ems - the ems
value - the value
unit - the unit
Returns:
the string
Class ModelTl
java.lang.Object
|
|
+--ModelInit
|
+--ModelHelper
|
+--ModelEms
|
+--ModelMe
|
+--ModelPtp
|
+--ModelCtp
|
+--ModelMlsn
|
+--com.ericsson.eos.model.ModelTl

ModelTca
public class ModelTl

extends ModelMlsn
The Class ModelTl.
Constructors
ModelTl
public ModelTl()
Methods
deleteTL
Deletes the given topologicalLink.
Parameters:
ems - the ems
Retrieves all TopologicalLinks.
Returns:
getTopologicalLink
gets the TopologicalLink with the specified objectId. used in MapView.
Parameters:
id - the id
Returns:
setTopologicalLink
public void setTopologicalLink(java.lang.String emsName,
java.lang.String node1CTP,
Creates a new TopologicalLink.
Parameters:
owner - the owner
rate - the rate
node1CTP - the node1 ctp
java.lang.String oldTlName,
Changes the TopologicalLink.
Parameters:
oldTlName - the old tl name
owner - the owner
rate - the rate
Class MyTableModel
java.lang.Object
|
+--javax.swing.table.AbstractTableModel
|
+--javax.swing.table.DefaultTableModel
|
+--com.ericsson.eos.model.MyTableModel
java.io.Serializable, javax.swing.table.TableModel
public class MyTableModel

extends javax.swing.table.DefaultTableModel
The Class MyTableModel.
Constructors
MyTableModel
public MyTableModel()
Instantiates a new my table model.
MyTableModel
public MyTableModel(java.lang.Object[][] values,
java.lang.Object[] columns)
Instantiates a new my table model.
Parameters:
values - the values
columns - the columns
Methods
getColumnClass
public java.lang.Class getColumnClass(int columnIndex)
Overrides:
getColumnClass in class javax.swing.table.AbstractTableModel
isCellEditable
public boolean isCellEditable(int rowIndex,
int columnIndex)
Overrides:
isCellEditable in class javax.swing.table.DefaultTableModel
Package com.ericsson.eos.services
Class Summary
NameService
The Class NameService.
NotificationService
The Class NotificationService.
com.ericsson.eos.services
Class NameService
java.lang.Object
|
+--java.lang.Thread
|
+--com.ericsson.eos.services.NameService
java.lang.Runnable
public class NameService

extends java.lang.Thread
The Class NameService.
Constructors
NameService
public NameService()
Instantiates a new name service.
Methods
run
public void run()
Overrides:
run in class java.lang.Thread
com.ericsson.eos.services
Class NotificationService
java.lang.Object
|
+--java.lang.Thread
|
+--com.ericsson.eos.services.NotificationService
java.lang.Runnable
public class NotificationService

The Class NotificationService.
Constructors
NotificationService
public NotificationService()
Instantiates a new notification service.
Methods
run
public void run()
Overrides:
Package com.ericsson.eos.view
Class Summary
AboutPanel
The Class AboutPanel.
EMSPanel
The Class EMSPanel.
MEPanel
The Class MEPanel.
MLSNPanel
The Class MLSNPanel.
MainView
The Class MainView.
ParseStatusPanel
The Class ParseStatusPanel.
StatusPanel
The Class StatusPanel includes the area in the bottom right corner of the application that displays
the status of the database connection, the northbound connection and the connection with
notification and name-service.
TPPanel
The Class PTPPanel.
TPView
The Class TPPanel.
TopoLinkPanel
The Class TopoLinkPanel.
TreeNodeIconRenderer
The Class TreeNodeIconRenderer.
TreeView
This class generates the tree structure on the left side of the application window.
XkcdPanel
The Class XkcdPanel.
com.ericsson.eos.view
Class AboutPanel
java.lang.Object
|
+--java.awt.Component
|
+--java.awt.Container
|
+--javax.swing.JComponent
|
+--javax.swing.JPanel
|
+--com.ericsson.eos.view.AboutPanel
java.awt.MenuContainer, java.awt.image.ImageObserver, java.io.Serializable,
javax.accessibility.Accessible, javax.swing.TransferHandler.HasGetTransferHandler
< Constructors >
public class AboutPanel

extends javax.swing.JPanel
The Class AboutPanel.
Constructors
AboutPanel
public AboutPanel()
Instantiates a new about panel.
Class EMSPanel
java.lang.Object
|
|
|
|
|
+--com.ericsson.eos.view.EMSPanel
< Constructors >
public class EMSPanel

The Class EMSPanel.
Author:
emikrie
Constructors
EMSPanel
public EMSPanel(Model model,
java.awt.Dialog dialog)
Creates new form MEPanel.
Parameters:
model - the model
dialog - the dialog
EMSPanel
public EMSPanel(Model model,
java.awt.Dialog dialog,
java.lang.String type)
Instantiates a new eMS panel.
Parameters:
model - the model
dialog - the dialog
ems - the ems
owner - the owner
type - the type
Class MEPanel
java.lang.Object
|
|
|
|
|
+--com.ericsson.eos.view.MEPanel
< Constructors >
public class MEPanel

The Class MEPanel.
Constructors
MEPanel
public MEPanel(Model model,
Parameters:
model - the model
dialog - the dialog
ems - the ems
mlsn - the mlsn
MEPanel
public MEPanel(Model model,
java.lang.String mlsnId,
java.lang.String comState,
boolean sync,
java.lang.String owner)
Instantiates a mE panel.
Parameters:
model - the model
dialog - the dialog
ems - the ems
mlsnId - the mlsn id
comState - the com state
sync - the sync
owner - the owner
Class MLSNPanel
java.lang.Object
|
|
|
|
|
+--com.ericsson.eos.view.MLSNPanel
< Constructors >
public class MLSNPanel

The Class MLSNPanel.
Author:
emikrie
Constructors
MLSNPanel
public MLSNPanel(Model model,
java.lang.String ems)
Parameters:
model - the model
dialog - the dialog
ems - the ems
MLSNPanel
public MLSNPanel(Model model,
java.lang.String mlsnName,
Instantiates a new mLSN panel.
Parameters:
model - the model
dialog - the dialog
ems - the ems
mlsnName - the mlsn name
type - the type
owner - the owner
Class MainView
java.lang.Object
|
|
|
+--java.awt.Window
|
+--java.awt.Frame
|
+--javax.swing.JFrame
|
+--com.ericsson.eos.view.MainView
java.awt.MenuContainer, java.awt.image.ImageObserver, java.io.Serializable, java.util.Observer,
javax.accessibility.Accessible, javax.swing.RootPaneContainer,
javax.swing.TransferHandler.HasGetTransferHandler, javax.swing.WindowConstants
public class MainView

extends javax.swing.JFrame
implements java.util.Observer
The Class MainView.
Fields
treeWidth
public static int treeWidth
The tree width.
Constructors
MainView
public MainView(Model m)
Instantiates a new main view.
Parameters:
m - the m
Methods
getDebugFileMenu
public javax.swing.JCheckBoxMenuItem getDebugFileMenu()
Gets the debug file menu.
Returns:
the debug file menu
getGroup
public javax.swing.ButtonGroup getGroup()
Gets the group.
Returns:
the group
getMain
public javax.swing.JPanel getMain()
Gets the main.
Returns:
the main
getModel
public Model getModel()
Gets the model.
Returns:
the model
getModelTreeSelection
public ModelSelection getModelTreeSelection()
Gets the model tree selection.
Returns:
the model tree selection
getRTAMView
public RTAMView getRTAMView()
Gets the rTAM view.
Returns:
the rTAM view
getSelectedInTree
public java.lang.String[] getSelectedInTree()
Gets the selected in tree.
Returns:
the selected in tree
setSelectedInTree
public void setSelectedInTree(java.lang.String[] str)
Sets the selected in tree.
Parameters:
str - the new selected in tree
switchView
public void switchView(java.lang.String str)
Switch view.
Parameters:
str - the str
update
public void update(java.util.Observable arg0,
java.lang.Object arg1)
Class ParseStatusPanel
java.lang.Object
|
|
|
|
|
+--com.ericsson.eos.view.ParseStatusPanel
public class ParseStatusPanel

The Class ParseStatusPanel.
Constructors
ParseStatusPanel
public ParseStatusPanel(Model model,
java.awt.Dialog d)
Creates new form ParseStatusPanel.
Parameters:
model - the model
d - the d
Methods
print
public void print()
For each different type of element, this function prints the amount of elements that were imported
as well as the amount that failed on the top of the panel.
update
java.lang.Object mess)
Class StatusPanel
java.lang.Object
|
|
|
|
|
+--com.ericsson.eos.view.StatusPanel
public class StatusPanel

The Class StatusPanel includes the area in the bottom right corner of the application that displays the
status of the database connection, the northbound connection and the connection with notification and
name-service.
Constructors
StatusPanel
public StatusPanel(Model model)
Instantiates a new status panel.
Parameters:
model - the model
Methods
repaintStatus
public void repaintStatus()
Repaint status.
update
Class TPPanel
java.lang.Object
|
|
|
|
|
+--com.ericsson.eos.view.TPPanel
< Constructors >

public class TPPanel
The Class PTPPanel.
Author:
emikrie
Constructors
TPPanel
public TPPanel(Model model,
Instantiates a new pTP panel.
Parameters:
model - the model
dialog - the dialog
ems - the ems
me - the me
TPPanel
Parameters:
model - the model
dialog - the dialog
ems - the ems
me - the me
ptp - the ptp
TPPanel
java.lang.String mappingMode,
java.lang.String directionality,
java.lang.String protectionAssosiation,
java.lang.String edgePoint)
Parameters:
model - the model
dialog - the dialog
ems - the ems
me - the me
ptp - the ptp
ctp - the ctp
owner - the owner
type - the type
mappingMode - the mapping mode
directionality - the directionality
protectionAssosiation - the protection assosiation
Class TPView
java.lang.Object
|
|
|
|
|
+--com.ericsson.eos.view.TPView
public class TPView

The Class TPPanel.
Constructors
TPView
public TPView(Model model,
MainView mv,
ModelSelection mts)
Creates new form TPView.
Parameters:
model - the model
mv - the mv
mts - the mts
Methods
getCTPMenu
public javax.swing.JPopupMenu getCTPMenu()
Gets the cTP menu.
Returns:
the cTP menu
getCTPTable
public javax.swing.JTable getCTPTable()
Gets the cTP table.
Returns:
the cTP table
getMCS
public ModelSelection getMCS()
Gets the mCS.
Returns:
the mCS
getMPS
public ModelSelection getMPS()
Gets the mPS.
Returns:
the mPS
getMTS
public ModelSelection getMTS()
Gets the mTS.
Returns:
the mTS
getMenu
public javax.swing.JPopupMenu getMenu()
Gets the menu.
Returns:
the menu
getPTPTable
public javax.swing.JTable getPTPTable()
Gets the pTP table.
Returns:
the pTP table
setCtpModel
public void setCtpModel(javax.swing.table.DefaultTableModel ctp)
Sets the ctp model.
Parameters:
ctp - the new ctp model
setPtpModel
public void setPtpModel(javax.swing.table.DefaultTableModel ptp)
Sets the ptp model.
Parameters:
ptp - the new ptp model
update
Class TopoLinkPanel
java.lang.Object
|
|
|
|
|
+--com.ericsson.eos.view.TopoLinkPanel
public class TopoLinkPanel

The Class TopoLinkPanel.
Constructors
TopoLinkPanel
public TopoLinkPanel(Model model,
java.lang.String nodeAMe,
java.lang.String nodeZMe)
Instantiates a new topo link panel.
Parameters:
model - the model
dialog - the dialog
ems - the ems
nodeAMe - the node a me
nodeZMe - the node z me
TopoLinkPanel
public TopoLinkPanel(Model model,
java.lang.String topologicalLink,
java.lang.String[] startPoint,
java.lang.String[] stopPoint)
Instantiates a new topo link panel.
Parameters:
model - the model
dialog - the dialog
ems - the ems
topologicalLink - the topological link
owner - the owner
startPoint - the start point
stopPoint - the stop point
Methods
fixLR
public void fixLR()
Fix lr.
getCTPs
public java.lang.String[] getCTPs(java.lang.String ems,
Gets the cT ps.
Parameters:
ems - the ems
me - the me
ptp - the ptp
Returns:
the cT ps
getPTPs
public java.lang.String[] getPTPs(java.lang.String ems,
Gets the pT ps.
Parameters:
ems - the ems
me - the me
Returns:
the pT ps
Class TreeNodeIconRenderer
java.lang.Object
|
|
|
|
+--javax.swing.JLabel
|
+--javax.swing.tree.DefaultTreeCellRenderer
|
+--com.ericsson.eos.view.TreeNodeIconRenderer
javax.accessibility.Accessible, javax.swing.SwingConstants,
javax.swing.TransferHandler.HasGetTransferHandler, javax.swing.tree.TreeCellRenderer
public class TreeNodeIconRenderer

extends javax.swing.tree.DefaultTreeCellRenderer
The Class TreeNodeIconRenderer.
Constructors
TreeNodeIconRenderer
public TreeNodeIconRenderer(Model model)
Instantiates a new tree node icon renderer.
Parameters:
model - the model
Methods
getTreeCellRendererComponent
public java.awt.Component getTreeCellRendererComponent(javax.swing.JTree tree,
java.lang.Object value,
boolean sel,
boolean expanded,
boolean leaf,
int row,
boolean hasFocus)
Overrides:
getTreeCellRendererComponent in class javax.swing.tree.DefaultTreeCellRenderer
Class TreeView
java.lang.Object
|
|
|
|
|
+--com.ericsson.eos.view.TreeView
public class TreeView

This class generates the tree structure on the left side of the application window.
Constructors
TreeView
public TreeView(Model m,
MainController mc,
MainView mv)
Instantiates a new tree view.
Parameters:
m - the m
mc - the mc
mv - the mv
Methods
getMenuEMS
public javax.swing.JPopupMenu getMenuEMS()
Gets the menu ems.
Returns:
the menu ems
getMenuME
public javax.swing.JPopupMenu getMenuME()
Gets the menu me.
Returns:
the menu me
getMenuML
public javax.swing.JPopupMenu getMenuML()
Gets the menu ml.
Returns:
the menu ml
getRootNode
public javax.swing.tree.DefaultMutableTreeNode getRootNode()
Gets the root node.
Returns:
the root node
getSelectedNodeCount
public int getSelectedNodeCount()
Gets the selected node count.
Returns:
the selected node count
getSelectedNodes
public java.util.ArrayList getSelectedNodes()
Gets the selected nodes.
Returns:
the selected nodes
getTree
public javax.swing.JTree getTree()
Gets the tree.
Returns:
the tree
getTreeModel
public javax.swing.tree.DefaultTreeModel getTreeModel()
Gets the tree model.
Returns:
the tree model
getTreeView
public javax.swing.JScrollPane getTreeView()
Gets the tree view.
Returns:
the tree view
setHeartBeatMenu
public void setHeartBeatMenu(boolean bool)
Sets the heart beat menu.
Parameters:
bool - the new heart beat menu
update
Class XkcdPanel
java.lang.Object
|
+--com.ericsson.eos.view.XkcdPanel
java.awt.event.MouseListener
public class XkcdPanel

implements java.awt.event.MouseListener
The Class XkcdPanel.
Author:
emikrie
Constructors
XkcdPanel
public XkcdPanel()
Instantiates a new xkcd panel.
Methods
mouseClicked
public void mouseClicked(java.awt.event.MouseEvent arg0)
mouseEntered
mouseExited
mousePressed
public void mousePressed(java.awt.event.MouseEvent arg0)
mouseReleased
public void mouseReleased(java.awt.event.MouseEvent arg0)
Package com.ericsson.eos.view.alarm
Class Summary
AlarmAlarmPanel
This class.
AlarmTCAPanel
The Class AlarmTCAPanel.
NTAlarmView
This class creates the panel for creating and configuring an nt_alarm.
NTTCAView
The Class NTTCAView.
com.ericsson.eos.view.alarm
Class AlarmAlarmPanel
java.lang.Object
|
|
|
|
|
+--com.ericsson.eos.view.alarm.AlarmAlarmPanel
public class AlarmAlarmPanel

This class.
Constructors
AlarmAlarmPanel
public AlarmAlarmPanel()
Creates new form AlarmAlarmPanel.
AlarmAlarmPanel
public AlarmAlarmPanel(Model model,
java.lang.String level2,
Instantiates a new alarm alarm panel.
Parameters:
model - the model
ems - the ems
level2 - the level2
level3 - the level3
level4 - the level4
type - the type
AlarmAlarmPanel
public AlarmAlarmPanel(Model model,
java.lang.String nativeProbCause,
java.lang.String[] x733ProposedRepairActions,
java.lang.String[] x733CorrelatedNotifications,
java.lang.String[] x733MonitoredAttributes,
Instantiates a new alarm alarm panel.
Parameters:
model - the model
ems - the ems
level2 - the level2
level3 - the level3
level4 - the level4
nativeProbCause - the native prob cause
Methods
createAlarm
public boolean createAlarm()
Creates the alarm.
Returns:
true, if successful
fixLR
public void fixLR()
Fix lr.
reset
public void reset()
Reset.
setModel
public void setModel()
Sets the model.
setTemplate
public void setTemplate(java.lang.String type,
java.util.ArrayList alarmDef,
java.util.Date dateTime)
Sets the template.
Parameters:
type - the type
alarmDef - the alarm def
dateTime - the date time
Class AlarmTCAPanel
java.lang.Object
|
|
|
|
|
+--com.ericsson.eos.view.alarm.AlarmTCAPanel
public class AlarmTCAPanel

The Class AlarmTCAPanel.
Author:
emikrie
Constructors
AlarmTCAPanel
public AlarmTCAPanel(Model model,
Instantiates a new alarm tca panel.
Parameters:
model - the model
ems - the ems
level2 - the level2
level3 - the level3
level4 - the level4
type - the type
AlarmTCAPanel
public AlarmTCAPanel(Model model,
java.lang.String acknowledgedIndication)
Instantiates a new alarm tca panel.
Parameters:
model - the model
ems - the ems
level2 - the level2
level3 - the level3
level4 - the level4
value - the value
unit - the unit
acknowledgedIndication - the acknowledged indication
Methods
createAlarm
public void createAlarm()
Creates the alarm.
fixLR
public void fixLR()
Fix lr.
reset
public void reset()
Reset.
setModel
public void setModel()
Sets the model.
Class NTAlarmView
java.lang.Object
|
|
|
|
|
+--com.ericsson.eos.view.alarm.NTAlarmView
public class NTAlarmView

This class creates the panel for creating and configuring an nt_alarm.
Constructors
NTAlarmView
public NTAlarmView(Model model,
java.awt.Dialog d,
Instantiates a new nT alarm view.
Parameters:
model - the model
d - the d
ems - the ems
level2 - the level2
level3 - the level3
level4 - the level4
type - the type
NTAlarmView
public NTAlarmView(Model model,
java.awt.Dialog d,
java.lang.String nativeProbCause,
java.lang.String[] x733ProposedRepairActions,
java.lang.String[] x733CorrelatedNotifications,
java.lang.String[] x733MonitoredAttributes,
Instantiates a new nT alarm view.
Parameters:
model - the model
d - the d
ems - the ems
level2 - the level2
level3 - the level3
level4 - the level4
nativeProbCause - the native prob cause
Methods
setModel
public javax.swing.DefaultComboBoxModel setModel()
Sets the model.
Returns:
the default combo box model
Class NTTCAView
java.lang.Object
|
|
|
|
|
+--com.ericsson.eos.view.alarm.NTTCAView
public class NTTCAView

The Class NTTCAView.
Author:
emikrie
Constructors
NTTCAView
public NTTCAView(Model model,
java.awt.Dialog d,
Creates new form AlarmPanel.
Parameters:
model - the model
d - the d
ems - the ems
level2 - the level2
level3 - the level3
level4 - the level4
type - the type
NTTCAView
public NTTCAView(Model model,
java.awt.Dialog d,
java.lang.String pmThresholdType,
java.lang.String pmValue,
java.lang.String pmUnit,
Instantiates a new nTTCA view.
Parameters:
model - the model
d - the d
ems - the ems
level2 - the level2
level3 - the level3
level4 - the level4
pmThresholdType - the pm threshold type
pmValue - the pm value
pmUnit - the pm unit
Methods
setModel
public javax.swing.DefaultComboBoxModel setModel()
Sets the model.
Returns:
the default combo box model
Package com.ericsson.eos.view.rtam
Class Summary
CustomTableCellRenderer
The Class CustomTableCellRenderer.
RTAMAlarm
The Class RTAMAlarm.
RTAMFilter
The Class RTAMFilter.
RTAMTCA
The Class RTAMTCA.
RTAMView
The Class RTAMView.
com.ericsson.eos.view.rtam
Class CustomTableCellRenderer
java.lang.Object
|
|
|
|
+--javax.swing.JLabel
|
+--javax.swing.table.DefaultTableCellRenderer
|
+--com.ericsson.eos.view.rtam.CustomTableCellRenderer
javax.accessibility.Accessible, javax.swing.SwingConstants,
javax.swing.TransferHandler.HasGetTransferHandler, javax.swing.table.TableCellRenderer
public class CustomTableCellRenderer

extends javax.swing.table.DefaultTableCellRenderer
The Class CustomTableCellRenderer.
Constructors
CustomTableCellRenderer
public CustomTableCellRenderer(Model model)
Instantiates a new custom table cell renderer.
Parameters:
model - the model
Methods
getTableCellRendererComponent
public java.awt.Component getTableCellRendererComponent(javax.swing.JTable
table,
java.lang.Object obj,
boolean isSelected,
boolean hasFocus,
int row,
int column)
Overrides:
getTableCellRendererComponent in class javax.swing.table.DefaultTableCellRenderer
Class RTAMAlarm
java.lang.Object
|
|
|
|
|
+--com.ericsson.eos.view.rtam.RTAMAlarm
public class RTAMAlarm

The Class RTAMAlarm.

Constructors
RTAMAlarm
public RTAMAlarm(Model m,
RTAMView rtam)
Instantiates a new rTAM alarm.
Parameters:
m - the m
rtam - the rtam
Methods
getColumnNames
public java.lang.String[] getColumnNames()
Gets the column names.
Returns:
the column names
getMenu
Gets the menu.
Returns:
the menu
getModel
Gets the model.
Returns:
the model
getTable
public javax.swing.JTable getTable()
Gets the table.
Returns:
the table
getViewColumns
public java.lang.String[] getViewColumns()
Gets the view columns.
Returns:
the view columns
newFilter
public void newFilter(java.util.HashMap hm)
New filter.
Parameters:
hm - the hm
setColumnNames
public void setColumnNames(java.lang.String[] columnNames)
Sets the column names.
Parameters:
columnNames - the new column names
update
public void update(java.util.Observable o,
java.lang.Object arg)
Class RTAMFilter
java.lang.Object
|
|
|
|
|
+--com.ericsson.eos.view.rtam.RTAMFilter
public class RTAMFilter

The Class RTAMFilter.
Fields
acknowledgeIndication
public javax.swing.JComboBox acknowledgeIndication
The acknowledge indication.
serviceAffecting
public javax.swing.JComboBox serviceAffecting
The service affecting.
Constructors
RTAMFilter
public RTAMFilter(RTAMView rv)
Instantiates a new rTAM filter.
Parameters:
rv - the rv
Methods
getFilterData
public java.util.HashMap getFilterData()
Gets the filter data.
Returns:
the filter data
getMode
public java.lang.String getMode()
Gets the mode.
Returns:
the mode
Class RTAMTCA
java.lang.Object
|
|
|
|
|
+--com.ericsson.eos.view.rtam.RTAMTCA
public class RTAMTCA

The Class RTAMTCA.
Constructors
RTAMTCA
public RTAMTCA(Model m,
RTAMView rtam)
Instantiates a new rTAMTCA.
Parameters:
m - the m
rtam - the rtam
Methods
getColumnNames
public java.lang.String[] getColumnNames()
Gets the column names.
Returns:
the column names
getMenu
Gets the menu.
Returns:
the menu
getModel
Gets the model.
Returns:
the model
getTable
public javax.swing.JTable getTable()
Gets the table.
Returns:
the table
getViewColumns
public java.lang.String[] getViewColumns()
Gets the view columns.
Returns:
the view columns
newFilter
public void newFilter(java.util.HashMap hm)
New filter.
Parameters:
hm - the hm
setColumnNames
public void setColumnNames(java.lang.String[] columnNames)
Sets the column names.
Parameters:
columnNames - the new column names
update
public void update(java.util.Observable o,
java.lang.Object arg)
Class RTAMView
java.lang.Object
|
|
|
|
|
+--com.ericsson.eos.view.rtam.RTAMView
public class RTAMView

The Class RTAMView.
Constructors
RTAMView
public RTAMView(Model model,
MainView mv)
Instantiates a new rTAM view.
Parameters:
model - the model
mv - the mv
Methods
getController
public RTAMController getController()
Gets the controller.
Returns:
the controller
getModel
Gets the model.
Returns:
the model
getRTAMAlarm
public RTAMAlarm getRTAMAlarm()
Gets the rTAM alarm.
Returns:
the rTAM alarm
getRTAMTCA
public RTAMTCA getRTAMTCA()
Gets the rTAMTCA.
Returns:
the rTAMTCA
getSelectedMenu
public javax.swing.JPopupMenu getSelectedMenu()
Gets the selected menu.
Returns:
the selected menu
getSelectedTable
public javax.swing.JTable getSelectedTable()
Gets the selected table.
Returns:
the selected JTable
init
public void init()
Inits the.
newFilter
public void newFilter()
New filter.
switchView
public void switchView(java.lang.String str)
Switch view.
Parameters:
str - the str
Package com.ericsson.helper
Class Summary
AlarmCreator
The Class AlarmCreator.
NameExtractor
The Class NameExtractor.
com.ericsson.helper
Class AlarmCreator
java.lang.Object
|
+--com.ericsson.helper.AlarmCreator
public class AlarmCreator

The Class AlarmCreator.
Constructors
AlarmCreator
public AlarmCreator()
Methods
createNT_AlarmEvent
public static org.omg.CosNotification.StructuredEvent
createNT_AlarmEvent(java.util.HashMap al,
NBIImp
nbi)
Creates the n t_ alarm event.
Parameters:
al - the al
nbi - the nbi
Returns:
the structured event
createNT_Attribute_Value_Change
createNT_Attribute_Value_Change(java.lang.String ems,
java.lang.String[] attributList,
NBIImp nbi)
Creates the n t_ attribute_ value_ change.
Parameters:
ems - the ems
nbi - the nbi
Returns:
createNT_HeartBeatEvent
createNT_HeartBeatEvent(java.lang.String ems,
NBIImp nbi)
Creates the n t_ heart beat event.
Parameters:
ems - the ems
me - the me
nbi - the nbi
Returns:
createNT_State_Change
createNT_State_Change(java.lang.String ems,
java.lang.String[] attributList,
NBIImp
nbi)
Creates the n t_ state_ change.
Parameters:
ems - the ems
nbi - the nbi
Returns:
createNT_TCAEvent
createNT_TCAEvent(java.util.HashMap al,
NBIImp
nbi)
Creates the n t_ tca event.
Parameters:
al - the al
nbi - the nbi
Returns:
printProperty
public static void printProperty(org.omg.CosNotification.Property[] props)
Prints the property.
Parameters:
props - the props
com.ericsson.helper
Class NameExtractor
java.lang.Object
|
+--com.ericsson.helper.NameExtractor
< Methods >
public class NameExtractor

The Class NameExtractor.
Methods
getObject
public static java.lang.String[]
getObject(org.tmforum.mtnm.globaldefs.NameAndStringValue_T[] objectName)
Gets the object name in a list.
Parameters:
objectName - the object name
Returns:
the object
Package com.ericsson.nbiImp
Class Summary
NBIImp
The Class NBIImp.
TestStarter
The Class TestStarter.
com.ericsson.nbiImp
Class NBIImp
java.lang.Object
|
+--java.lang.Thread
|
+--com.ericsson.nbiImp.NBIImp
NBI, java.io.Serializable, java.lang.Runnable
public class NBIImp

implements NBI, java.io.Serializable
The Class NBIImp.
Fields
eventIterators
public java.util.ArrayList eventIterators
The event iterators.
managedElementIterators
public java.util.ArrayList managedElementIterators
The managed element iterators.
namingAttributesIterators
public java.util.ArrayList namingAttributesIterators
The naming attributes iterators.
subnetworkIterators
public java.util.ArrayList subnetworkIterators
The subnetwork iterators.
terminationPointIterators
public java.util.ArrayList terminationPointIterators
The termination point iterators.
Constructors
NBIImp
public NBIImp()
Instantiates a new nBI imp.
Methods
acknowledgeAlarms
public java.util.ArrayList acknowledgeAlarms(java.util.ArrayList alarms,
debug
public void debug(java.lang.String str,
java.lang.Object o,
getActive
public boolean getActive()
getAdditionalInfo
getAlarms
public java.util.ArrayList getAlarms(java.lang.String[] severity,
java.lang.String[] probableCause)
getAllAlarms
public java.lang.String[] getAllAlarms()
getAllNodes
public java.lang.String[] getAllNodes()
getAllTL
public java.lang.String[] getAllTL()
getAllTopLevelSubnetworkLayerRates
public java.util.ArrayList getAllTopLevelSubnetworkLayerRates(int ems,
java.lang.String
subnet)
getCTP
getChannel
public org.omg.CosNotifyChannelAdmin.EventChannel getChannel()
Gets the channel.
Returns:
the channel
getClient
public org.tmforum.mtnm.nmsSession.NmsSession_I getClient()
Gets the client.
Returns:
the client
short[] layerRate)
short[] layerRate)
short[] layerRate)
short[] layerRate)
short[] layerRate)
short[] layerRate)
getEms
getInterfaceName
public java.lang.String getInterfaceName()
getLayerParameters
public java.util.ArrayList getLayerParameters(int objectID)
getManagedElement
getNodes
public java.lang.String[] getNodes(java.lang.String node)
getObjectName
public java.util.HashMap getObjectName(int objectId)
getOrb
public org.omg.CORBA.ORB getOrb()
Gets the orb.
Returns:
the orb
getPOA
public org.omg.PortableServer.POA getPOA()
Gets the pOA.
Returns:
the pOA
getPTP
getPTPs
getSubnetwork
getSubnodes
public java.lang.String[] getSubnodes(java.lang.String node)
getSupportedRates
getTL
public java.lang.String[] getTL(java.lang.String node)
getTopNode
public java.lang.String getTopNode()
notificate
public void notificate(org.omg.CosNotification.StructuredEvent se)
run
public void run()
Overrides:
sendAlarm
public void sendAlarm(java.util.HashMap alarm)
sendAttributeChanged
public void sendAttributeChanged(java.lang.String ems,
sendHeartBeat
public void sendHeartBeat(java.lang.String ems,
java.lang.String emsTime)
sendStateChanged
public void sendStateChanged(java.lang.String emsName,
setActive
public void setActive(boolean bool)
setClient
public void setClient(org.tmforum.mtnm.nmsSession.NmsSession_I client)
Sets the client.
Parameters:
client - the new client
setModel
public void setModel(Model model)
setupNotificationRoute
public void setupNotificationRoute()
unacknowledgeAlarms
public java.util.ArrayList unacknowledgeAlarms(java.util.ArrayList alarms,
updateEMS
com.ericsson.nbiImp
Class TestStarter
java.lang.Object
|
+--com.ericsson.nbiImp.TestStarter
public class TestStarter

The Class TestStarter.
Constructors
TestStarter
public TestStarter()
Methods
main
The main method.
Parameters:
Package com.ericsson.poaImp
Class Summary
ASAPIterator_IPOAImp
The Class ASAPIterator_IPOAImp.
BackupIdIterator_IPOAImp
The Class BackupIdIterator_IPOAImp.
CCIterator_IPOAImp
The Class CCIterator_IPOAImp.
CallAndTopLevelConnectionsAndSNCsIterator_IPOAImp
The Class CallAndTopLevelConnectionsAndSNCsIterator_IPOAImp.
CallAndTopLevelConnectionsIterator_IPOAImp
The Class CallAndTopLevelConnectionsIterator_IPOAImp.
Common_IPOAImp
The Class Common_IPOAImp.
CurrentMaintenanceOperationIterator_IPOAImp
The Class CurrentMaintenanceOperationIterator_IPOAImp.
EMSMgr_IPOAImp
The Class EMSMgr_IPOAImp.
EProtectionGroupIterator_IPOAImp
The Class EProtectionGroupIterator_IPOAImp.
EmsSessionFactory_IPOAImp
The Class EmsSessionFactory_IPOAImp.
EmsSession_IPOAImp
The Class EmsSession_IPOAImp.
EquipmentInventoryMgr_IPOAImp
The Class EquipmentInventoryMgr_IPOAImp.
EquipmentOrHolderIterator_IPOAImp
The Class EquipmentOrHolderIterator_IPOAImp.
EventIterator_IPOAImp
The Class EventIterator_IPOAImp.
FDFrIterator_IPOAImp
The Class FDFrIterator_IPOAImp.
FDIterator_IPOAImp
The Class FDIterator_IPOAImp.
FlowDomainMgr_IPOAImp
The Class FlowDomainMgr_IPOAImp.
GTPiterator_IPOAImp
The Class GTPiterator_IPOAImp.
GuiCutThroughMgr_IPOAImp
The Class GuiCutThroughMgr_IPOAImp.
MFDFrIterator_IPOAImp
The Class MFDFrIterator_IPOAImp.
MFDIterator_IPOAImp
The Class MFDIterator_IPOAImp.
MLSNPPIterator_IPOAImp
The Class MLSNPPIterator_IPOAImp.
MLSNPPLinkIterator_IPOAImp
The Class MLSNPPLinkIterator_IPOAImp.
MLSNPPLinkMgr_IPOAImp
The Class MLSNPPLinkMgr_IPOAImp.
MLSNPPMgr_IPOAImp
The Class MLSNPPMgr_IPOAImp.
MaintenanceMgr_IPOAImp
The Class MaintenanceMgr_IPOAImp.
ManagedElementIterator_IPOAImp
The Class ManagedElementIterator_IPOAImp.
ManagedElementMgr_IPOAImp
The Class ManagedElementMgr_IPOAImp.
MultiLayerSubnetworkMgr_IPOAImp
The Class MultiLayerSubnetworkMgr_IPOAImp.
NamingAttributesIterator_IPOAImp
The Class NamingAttributesIterator_IPOAImp.
NmsSession_IPOAImp
The Class NmsSession_IPOAImp.
PMDataIterator_IPOAImp
The Class PMDataIterator_IPOAImp.
PMPIterator_IPOAImp
The Class PMPIterator_IPOAImp.
PerformanceManagementMgr_IPOAImp
The Class PerformanceManagementMgr_IPOAImp.
ProtectionGroupIterator_IPOAImp
The Class ProtectionGroupIterator_IPOAImp.
ProtectionMgr_IPOAImp
The Class ProtectionMgr_IPOAImp.
SNCIterator_IPOAImp
The Class SNCIterator_IPOAImp.
Session_IPOAImp
The Class Session_IPOAImp.
SoftwareAndDataMgr_IPOAImp
The Class SoftwareAndDataMgr_IPOAImp.
SubnetworkIterator_IPOAImp
The Class SubnetworkIterator_IPOAImp.
TCAParameterProfileIterator_IPOAImp
The Class TCAParameterProfileIterator_IPOAImp.
TCProfileIterator_IPOAImp
The Class TCProfileIterator_IPOAImp.
TCProfileMgr_IPOAImp
The Class TCProfileMgr_IPOAImp.
TerminationPointIterator_IPOAImp
The Class TerminationPointIterator_IPOAImp.
TopologicalLinkIterator_IPOAImp
The Class TopologicalLinkIterator_IPOAImp.
TrafficDescriptorIterator_IPOAImp
The Class TrafficDescriptorIterator_IPOAImp.
TrafficDescriptorMgr_IPOAImp
The Class TrafficDescriptorMgr_IPOAImp.
TransmissionDescriptorIterator_IPOAImp
The Class TransmissionDescriptorIterator_IPOAImp.
TransmissionDescriptorMgr_IPOAImp
The Class TransmissionDescriptorMgr_IPOAImp.
Version_IPOAImp
This class implements part of the TMF814 SS 3.5.
com.ericsson.poaImp
Class ASAPIterator_IPOAImp
java.lang.Object
|
+--org.omg.PortableServer.Servant
|
+--org.tmforum.mtnm.aSAP.ASAPIterator_IPOA
|
+--com.ericsson.poaImp.ASAPIterator_IPOAImp
org.omg.CORBA.portable.InvokeHandler, org.tmforum.mtnm.aSAP.ASAPIterator_IOperations
public class ASAPIterator_IPOAImp

extends org.tmforum.mtnm.aSAP.ASAPIterator_IPOA
The Class ASAPIterator_IPOAImp.
Constructors
ASAPIterator_IPOAImp
public ASAPIterator_IPOAImp()
Methods
destroy
public void destroy()
getLength
public int getLength()
next_n
public boolean next_n(int howMany,
org.tmforum.mtnm.aSAP.ASAPList_THolder aSAPList)
com.ericsson.poaImp
Class BackupIdIterator_IPOAImp
java.lang.Object
|
|
+--org.tmforum.mtnm.softwareAndDataManager.BackupIdIterator_IPOA
|
+--com.ericsson.poaImp.BackupIdIterator_IPOAImp
org.omg.CORBA.portable.InvokeHandler,
org.tmforum.mtnm.softwareAndDataManager.BackupIdIterator_IOperations
public class BackupIdIterator_IPOAImp

extends org.tmforum.mtnm.softwareAndDataManager.BackupIdIterator_IPOA
The Class BackupIdIterator_IPOAImp.
Constructors
BackupIdIterator_IPOAImp
public BackupIdIterator_IPOAImp()
Methods
destroy
getLength
next_n
org.tmforum.mtnm.softwareAndDataManager.BackupIdList_THolder backupList)
com.ericsson.poaImp
Class CCIterator_IPOAImp
java.lang.Object
|
|
+--org.tmforum.mtnm.subnetworkConnection.CCIterator_IPOA
|
+--com.ericsson.poaImp.CCIterator_IPOAImp
org.tmforum.mtnm.subnetworkConnection.CCIterator_IOperations
public class CCIterator_IPOAImp

extends org.tmforum.mtnm.subnetworkConnection.CCIterator_IPOA
The Class CCIterator_IPOAImp.
Constructors
CCIterator_IPOAImp
public CCIterator_IPOAImp()
Methods
destroy
getLength
next_n
org.tmforum.mtnm.subnetworkConnection.CrossConnectList_THolder ccList)
com.ericsson.poaImp
Class
java.lang.Object
|
|
+--org.tmforum.mtnm.callSNC.CallAndTopLevelConnectionsAndSNCsIterator_IPOA
|
+--com.ericsson.poaImp.CallAndTopLevelConnectionsAndSNCsIterator_IPOAIm
org.tmforum.mtnm.callSNC.CallAndTopLevelConnectionsAndSNCsIterator_IOperations
public class CallAndTopLevelConnectionsAndSNCsIterator_IPOAImp

extends org.tmforum.mtnm.callSNC.CallAndTopLevelConnectionsAndSNCsIterator_IPOA
The Class CallAndTopLevelConnectionsAndSNCsIterator_IPOAImp.
Constructors
public CallAndTopLevelConnectionsAndSNCsIterator_IPOAImp()
Methods
destroy
getLength
next_n
org.tmforum.mtnm.callSNC.CallAndTopLevelConnectionsAndSNCsList_THolder
callAndTopLevelConnectionsAndSNCsList)
com.ericsson.poaImp
Class CallAndTopLevelConnectionsIterator_IPOAImp
java.lang.Object
|
|
+--org.tmforum.mtnm.callSNC.CallAndTopLevelConnectionsIterator_IPOA
|
+--com.ericsson.poaImp.CallAndTopLevelConnectionsIterator_IPOAImp
org.tmforum.mtnm.callSNC.CallAndTopLevelConnectionsIterator_IOperations
public class CallAndTopLevelConnectionsIterator_IPOAImp

extends org.tmforum.mtnm.callSNC.CallAndTopLevelConnectionsIterator_IPOA
The Class CallAndTopLevelConnectionsIterator_IPOAImp.
Constructors
public CallAndTopLevelConnectionsIterator_IPOAImp()
Methods
destroy
getLength
next_n
org.tmforum.mtnm.callSNC.CallAndTopLevelConnectionsList_THolder
callAndTopLevelConnectionsList)
com.ericsson.poaImp
Class Common_IPOAImp
java.lang.Object
|
|
+--org.tmforum.mtnm.common.Common_IPOA
|
+--com.ericsson.poaImp.Common_IPOAImp
org.omg.CORBA.portable.InvokeHandler, org.tmforum.mtnm.common.Common_IOperations
public class Common_IPOAImp

extends org.tmforum.mtnm.common.Common_IPOA
The Class Common_IPOAImp.
Constructors
Common_IPOAImp
public Common_IPOAImp()
Methods
getCapabilities
public void getCapabilities(org.tmforum.mtnm.common.CapabilityList_THolder
capabilities)
setAdditionalInfo
public void
setAdditionalInfo(org.tmforum.mtnm.globaldefs.NameAndStringValue_T[]
objectName,
org.tmforum.mtnm.globaldefs.NVSList_THolder
additionalInfo)
setNativeEMSName
public void
setNativeEMSName(org.tmforum.mtnm.globaldefs.NameAndStringValue_T[]
objectName,
java.lang.String nativeEMSName)
setOwner
public void setOwner(org.tmforum.mtnm.globaldefs.NameAndStringValue_T[]
objectName,
setUserLabel
public void setUserLabel(org.tmforum.mtnm.globaldefs.NameAndStringValue_T[]
objectName,
boolean enforceUniqueness)
com.ericsson.poaImp
Class CurrentMaintenanceOperationIterator_IPOAImp
java.lang.Object
|
|
+--org.tmforum.mtnm.maintenanceOps.CurrentMaintenanceOperationIterator_IPOA
|
+--com.ericsson.poaImp.CurrentMaintenanceOperationIterator_IPOAImp
org.tmforum.mtnm.maintenanceOps.CurrentMaintenanceOperationIterator_IOperations

public class CurrentMaintenanceOperationIterator_IPOAImp
extends org.tmforum.mtnm.maintenanceOps.CurrentMaintenanceOperationIterator_IPOA
The Class CurrentMaintenanceOperationIterator_IPOAImp.
Constructors
public CurrentMaintenanceOperationIterator_IPOAImp()
Methods
destroy
getLength
next_n
org.tmforum.mtnm.maintenanceOps.CurrentMaintenanceOperationList_THolder
cMOList)
com.ericsson.poaImp
Class EMSMgr_IPOAImp
java.lang.Object
|
|
+--org.tmforum.mtnm.emsMgr.EMSMgr_IPOA
|
+--com.ericsson.poaImp.EMSMgr_IPOAImp
org.omg.CORBA.portable.InvokeHandler, org.tmforum.mtnm.emsMgr.EMSMgr_IOperations

public class EMSMgr_IPOAImp
extends org.tmforum.mtnm.emsMgr.EMSMgr_IPOA
The Class EMSMgr_IPOAImp.
Author:
emikrie
Constructors
EMSMgr_IPOAImp
public EMSMgr_IPOAImp()
Methods
acknowledgeAlarms
public void
acknowledgeAlarms(org.tmforum.mtnm.notifications.AlarmOrTCAIdentifier_T[]
acknowledgeIDList,
org.tmforum.mtnm.globaldefs.NameAndStringValue_T[] additionalInfo,
org.tmforum.mtnm.notifications.AlarmAndTCAIDList_THolder
failedAcknowledgeIDList)
assignASAP
public void assignASAP(org.tmforum.mtnm.globaldefs.NameAndStringValue_T[]
aSAPName,
org.tmforum.mtnm.globaldefs.NameAndStringValue_T[]
resourceName,
short layerRate,
additionalInfo)
createASAP
public void createASAP(org.tmforum.mtnm.aSAP.ASAPCreateModifyData_T
newASAPCreateData,
org.tmforum.mtnm.aSAP.ASAP_THolder newASAP,
additionalInfo)
createTopologicalLink
public void
createTopologicalLink(org.tmforum.mtnm.topologicalLink.TLCreateData_T
newTLCreateData,
org.tmforum.mtnm.topologicalLink.TopologicalLink_THolder newTopologicalLink)
deassignASAP
public void deassignASAP(org.tmforum.mtnm.globaldefs.NameAndStringValue_T[]
resourceName,
short layerRate,
additionalInfo)
deleteASAP
public void deleteASAP(org.tmforum.mtnm.globaldefs.NameAndStringValue_T[]
aSAPName,
additionalInfo)
deleteTopologicalLink
public void
deleteTopologicalLink(org.tmforum.mtnm.globaldefs.NameAndStringValue_T[]
topoLinkName)
getASAP
public void getASAP(org.tmforum.mtnm.globaldefs.NameAndStringValue_T[]
aSAPName,
org.tmforum.mtnm.aSAP.ASAP_THolder anASAP)
getASAPAssociatedResourceNames
public void
getASAPAssociatedResourceNames(org.tmforum.mtnm.globaldefs.NameAndStringValue_T[]
aSAPName,
int howMany,
org.tmforum.mtnm.globaldefs.NamingAttributesList_THolder nameList,
org.tmforum.mtnm.globaldefs.NamingAttributesIterator_IHolder nameIt)
getASAPbyResource
public void
getASAPbyResource(org.tmforum.mtnm.globaldefs.NameAndStringValue_T[]
resourceName,
short[] layerRateList,
int howMany,
org.tmforum.mtnm.aSAP.ASAPList_THolder aSAPList,
org.tmforum.mtnm.aSAP.ASAPIterator_IHolder
asapIt)
getAllASAPNames
public void getAllASAPNames(int howMany,
getAllASAPs
public void getAllASAPs(int howMany,
org.tmforum.mtnm.aSAP.ASAPList_THolder aSAPList,
org.tmforum.mtnm.aSAP.ASAPIterator_IHolder asapIt)
getAllEMSAndMEActiveAlarms
public void getAllEMSAndMEActiveAlarms(java.lang.String[]
excludeProbCauseList,
org.tmforum.mtnm.notifications.PerceivedSeverity_T[] excludeSeverityList,
int howMany,
org.tmforum.mtnm.notifications.EventList_THolder eventList,
org.tmforum.mtnm.notifications.EventIterator_IHolder eventIt)
getAllEMSAndMEUnacknowledgedActiveAlarms
public void getAllEMSAndMEUnacknowledgedActiveAlarms(java.lang.String[]
int howMany,
getAllEMSSystemActiveAlarms
public void
getAllEMSSystemActiveAlarms(org.tmforum.mtnm.notifications.PerceivedSeverity_T[]
excludeSeverityList,
int howMany,
getAllEMSSystemUnacknowledgedActiveAlarms
public void
getAllEMSSystemUnacknowledgedActiveAlarms(org.tmforum.mtnm.notifications.PerceivedS
excludeSeverityList,
int howMany,
getAllMLRAs
public void getAllMLRAs(int howMany,
org.tmforum.mtnm.multiLayerSubnetwork.SubnetworkList_THolder mLRAList,
org.tmforum.mtnm.multiLayerSubnetwork.SubnetworkIterator_IHolder sIt)
getAllMLSNPPLinks
public void getAllMLSNPPLinks(boolean sNPListRequested,
int howMany,
org.tmforum.mtnm.mLSNPPLink.MLSNPPLinkList_THolder mLSNPPLinkList,
org.tmforum.mtnm.mLSNPPLink.MLSNPPLinkIterator_IHolder mLSNPPLinkIt)
getAllMLSNPPLinksWithMLSNs
public void
getAllMLSNPPLinksWithMLSNs(org.tmforum.mtnm.globaldefs.NameAndStringValue_T[][]
mLRANames,
boolean sNPListRequested,
int howMany,
getAllMLSNPPLinksWithTNAs
public void getAllMLSNPPLinksWithTNAs(java.lang.String[] tNAList,
int howMany,
getAllMLSNPPLinksWithTP
public void
getAllMLSNPPLinksWithTP(org.tmforum.mtnm.globaldefs.NameAndStringValue_T[]
tPName,
int howMany,
getAllMLSNPPs
public void getAllMLSNPPs(boolean sNPListRequested,
int howMany,
org.tmforum.mtnm.mLSNPP.MLSNPPList_THolder
mLSNPPList,
org.tmforum.mtnm.mLSNPP.MLSNPPIterator_IHolder
mLSNPPIt)
getAllMLSNPPsWithTNA
public void getAllMLSNPPsWithTNA(java.lang.String[] tNAList,
int howMany,
mLSNPPList,
org.tmforum.mtnm.mLSNPP.MLSNPPIterator_IHolder mLSNPPIt)
getAllMLSNPPsWithTP
public void
getAllMLSNPPsWithTP(org.tmforum.mtnm.globaldefs.NameAndStringValue_T[] tPName,
int howMany,
mLSNPPList,
mLSNPPIt)
getAllTopLevelSubnetworkNames
public void getAllTopLevelSubnetworkNames(int howMany,
public void getAllTopLevelSubnetworks(int howMany,
org.tmforum.mtnm.multiLayerSubnetwork.SubnetworkList_THolder sList,
org.tmforum.mtnm.multiLayerSubnetwork.SubnetworkIterator_IHolder sIt)
getAllTopLevelTopologicalLinkNames
public void getAllTopLevelTopologicalLinkNames(int howMany,
getAllTopLevelTopologicalLinks
public void getAllTopLevelTopologicalLinks(int howMany,
org.tmforum.mtnm.topologicalLink.TopologicalLinkList_THolder topoList,
org.tmforum.mtnm.topologicalLink.TopologicalLinkIterator_IHolder topoIt)
getCapabilities
capabilities)
getEMS
public void getEMS(org.tmforum.mtnm.emsMgr.EMS_THolder emsInfo)
getTopLevelTopologicalLink
public void
getTopLevelTopologicalLink(org.tmforum.mtnm.globaldefs.NameAndStringValue_T[]
topoLinkName,
org.tmforum.mtnm.topologicalLink.TopologicalLink_THolder topoLink)
modifyASAP
public void modifyASAP(org.tmforum.mtnm.globaldefs.NameAndStringValue_T[]
aSAPName,
org.tmforum.mtnm.aSAP.ASAPCreateModifyData_T
aSAPModifyData,
org.tmforum.mtnm.aSAP.ASAP_THolder newASAP,
additionalInfo)
setAdditionalInfo
public void
objectName,
additionalInfo)
setNBI
public void setNBI(NBIImp nbi)
Sets the NBI imp. It only exists max one NBI per protocol at any given time, this nbi is given to this
manager under the given session by this function.
Parameters:
nbi - the new NBI imp. Used for debugging and logging, and to communicate with the
actual simulator.
setNativeEMSName
public void
objectName,
setOwner
objectName,
setUserLabel
objectName,
unacknowledgeAlarms
public void
unacknowledgeAlarms(org.tmforum.mtnm.notifications.AlarmOrTCAIdentifier_T[]
unacknowledgeIDList,
org.tmforum.mtnm.notifications.AlarmAndTCAIDList_THolder
failedunAcknowledgeIDList)
com.ericsson.poaImp
Class EProtectionGroupIterator_IPOAImp
java.lang.Object
|
|
+--org.tmforum.mtnm.protection.EProtectionGroupIterator_IPOA
|
+--com.ericsson.poaImp.EProtectionGroupIterator_IPOAImp
org.tmforum.mtnm.protection.EProtectionGroupIterator_IOperations
public class EProtectionGroupIterator_IPOAImp

extends org.tmforum.mtnm.protection.EProtectionGroupIterator_IPOA
The Class EProtectionGroupIterator_IPOAImp.
Constructors
EProtectionGroupIterator_IPOAImp
public EProtectionGroupIterator_IPOAImp()
Methods
destroy
getLength
next_n
org.tmforum.mtnm.protection.EProtectionGroupList_THolder
ePGPList)
com.ericsson.poaImp
Class EmsSessionFactory_IPOAImp
java.lang.Object
|
|
+--org.tmforum.mtnm.emsSessionFactory.EmsSessionFactory_IPOA
|
+--com.ericsson.poaImp.EmsSessionFactory_IPOAImp
org.tmforum.mtnm.emsSessionFactory.EmsSessionFactory_IOperations
public class EmsSessionFactory_IPOAImp

extends org.tmforum.mtnm.emsSessionFactory.EmsSessionFactory_IPOA
The Class EmsSessionFactory_IPOAImp. Entry point for TMF814.
Author:
emikrie
Constructors
EmsSessionFactory_IPOAImp
public EmsSessionFactory_IPOAImp()
Methods
getEmsSession
public void getEmsSession(java.lang.String user,
java.lang.String password,
org.tmforum.mtnm.nmsSession.NmsSession_I client,
org.tmforum.mtnm.emsSession.EmsSession_IHolder
emsSessionInterface)
getVersion
public java.lang.String getVersion()
setNBIImp
public void setNBIImp(NBIImp nbi)
Sets the NBI imp. The NBI is only needed for debugging purposes and logging in this class.
Parameters:
nbi - the new Instance of the NBI
com.ericsson.poaImp
Class EmsSession_IPOAImp
java.lang.Object
|
|
+--org.tmforum.mtnm.emsSession.EmsSession_IPOA
|
+--com.ericsson.poaImp.EmsSession_IPOAImp
org.tmforum.mtnm.emsSession.EmsSession_IOperations
public class EmsSession_IPOAImp

extends org.tmforum.mtnm.emsSession.EmsSession_IPOA
The Class EmsSession_IPOAImp.
Author:
emikrie
Constructors
EmsSession_IPOAImp
public EmsSession_IPOAImp()
Methods
associateSession
public void associateSession(org.tmforum.mtnm.nmsSession.NmsSession_I client)
Associate session.
Parameters:
client - the client
associatedSession
public org.tmforum.mtnm.session.Session_I associatedSession()
endSession
public void endSession()
getEventChannel
public void getEventChannel(org.omg.CosNotifyChannelAdmin.EventChannelHolder
eventChannel)
getManager
public void getManager(java.lang.String managerName,
org.tmforum.mtnm.common.Common_IHolder
managerInterface)
getSupportedManagers
public void
getSupportedManagers(org.tmforum.mtnm.emsSession.EmsSession_IPackage.managerNames_T
supportedManagerList)
ping
public void ping()
setNBIImp
public void setNBIImp(NBIImp nbi)
Sets the NBI imp. It only exists max one NBI per protocol at any given time, this nbi is given to this
session by this function.
Parameters:
nbi - the new NBI imp. Used for debugging and logging, and is sent to the manager that
needs it to perform specific tasks on the database.
com.ericsson.poaImp
Class EquipmentInventoryMgr_IPOAImp
java.lang.Object
|
|
+--org.tmforum.mtnm.equipment.EquipmentInventoryMgr_IPOA
|
+--com.ericsson.poaImp.EquipmentInventoryMgr_IPOAImp
org.tmforum.mtnm.equipment.EquipmentInventoryMgr_IOperations
public class EquipmentInventoryMgr_IPOAImp

extends org.tmforum.mtnm.equipment.EquipmentInventoryMgr_IPOA
The Class EquipmentInventoryMgr_IPOAImp.
Constructors
EquipmentInventoryMgr_IPOAImp
public EquipmentInventoryMgr_IPOAImp()
Methods
getAllEquipment
public void getAllEquipment(org.tmforum.mtnm.globaldefs.NameAndStringValue_T[]
meOrHolderName,
int howMany,
org.tmforum.mtnm.equipment.EquipmentOrHolderList_THolder eqList,
org.tmforum.mtnm.equipment.EquipmentOrHolderIterator_IHolder eqIt)
getAllEquipmentNames
public void
getAllEquipmentNames(org.tmforum.mtnm.globaldefs.NameAndStringValue_T[]
meOrHolderName,
int howMany,
getAllSupportedPTPNames
public void
getAllSupportedPTPNames(org.tmforum.mtnm.globaldefs.NameAndStringValue_T[]
equipmentName,
int howMany,
getAllSupportedPTPs
public void
getAllSupportedPTPs(org.tmforum.mtnm.globaldefs.NameAndStringValue_T[]
equipmentName,
int howMany,
org.tmforum.mtnm.terminationPoint.TerminationPointList_THolder tpList,
org.tmforum.mtnm.terminationPoint.TerminationPointIterator_IHolder tpIt)
getAllSupportingEquipment
public void
getAllSupportingEquipment(org.tmforum.mtnm.globaldefs.NameAndStringValue_T[]
ptpOrMfdName,
org.tmforum.mtnm.equipment.EquipmentOrHolderList_THolder eqList)
getAllSupportingEquipmentNames
public void
getAllSupportingEquipmentNames(org.tmforum.mtnm.globaldefs.NameAndStringValue_T[]
ptpOrMfdName,
org.tmforum.mtnm.globaldefs.NamingAttributesList_THolder nameList)
getCapabilities
capabilities)
getContainedEquipment
public void
getContainedEquipment(org.tmforum.mtnm.globaldefs.NameAndStringValue_T[]
equipmentHolderName,
org.tmforum.mtnm.equipment.EquipmentOrHolderList_THolder
equipmentOrHolderList)
getEquipment
public void getEquipment(org.tmforum.mtnm.globaldefs.NameAndStringValue_T[]
equipmentOrHolderName,
org.tmforum.mtnm.equipment.EquipmentOrHolder_THolder
equip)
getSupportedEquipment
public void
getSupportedEquipment(org.tmforum.mtnm.globaldefs.NameAndStringValue_T[]
equipmentName,
getSupportedEquipmentNames
public void
getSupportedEquipmentNames(org.tmforum.mtnm.globaldefs.NameAndStringValue_T[]
equipmentName,
getSupportingEquipment
public void
getSupportingEquipment(org.tmforum.mtnm.globaldefs.NameAndStringValue_T[]
equipmentName,
getSupportingEquipmentNames
public void
getSupportingEquipmentNames(org.tmforum.mtnm.globaldefs.NameAndStringValue_T[]
equipmentName,
provisionEquipment
public void provisionEquipment(org.tmforum.mtnm.equipment.EQTCreateData_T
equipmentCreateData,
org.tmforum.mtnm.equipment.Equipment_THolder
createdEquipment)
setAdditionalInfo
public void
objectName,
additionalInfo)
setAlarmReportingOff
public void
setAlarmReportingOff(org.tmforum.mtnm.globaldefs.NameAndStringValue_T[]
equipmentOrHolderName)
setAlarmReportingOn
public void
setAlarmReportingOn(org.tmforum.mtnm.globaldefs.NameAndStringValue_T[]
equipmentOrHolderName)
setNativeEMSName
public void
objectName,
setOwner
objectName,
setUserLabel
objectName,
unprovisionEquipment
public void
unprovisionEquipment(org.tmforum.mtnm.globaldefs.NameAndStringValue_T[]
equipmentName)
com.ericsson.poaImp
Class EquipmentOrHolderIterator_IPOAImp
java.lang.Object
|
|
+--org.tmforum.mtnm.equipment.EquipmentOrHolderIterator_IPOA
|
+--com.ericsson.poaImp.EquipmentOrHolderIterator_IPOAImp
org.tmforum.mtnm.equipment.EquipmentOrHolderIterator_IOperations
public class EquipmentOrHolderIterator_IPOAImp

extends org.tmforum.mtnm.equipment.EquipmentOrHolderIterator_IPOA
The Class EquipmentOrHolderIterator_IPOAImp.
Constructors
EquipmentOrHolderIterator_IPOAImp
public EquipmentOrHolderIterator_IPOAImp()
Methods
destroy
getLength
next_n
org.tmforum.mtnm.equipment.EquipmentOrHolderList_THolder
equipmentOrHolderList)
com.ericsson.poaImp
Class EventIterator_IPOAImp
java.lang.Object
|
|
+--org.tmforum.mtnm.notifications.EventIterator_IPOA
|
+--com.ericsson.poaImp.EventIterator_IPOAImp
org.tmforum.mtnm.notifications.EventIterator_IOperations
public class EventIterator_IPOAImp

extends org.tmforum.mtnm.notifications.EventIterator_IPOA
The Class EventIterator_IPOAImp.
Constructors
EventIterator_IPOAImp
public EventIterator_IPOAImp(java.util.ArrayList list,
NBIImp nbi,
int size)
Instantiates a new event iterator_ ipoa imp.
Parameters:
list - the list
nbi - the nbi
size - the size
Methods
destroy
getLength
next_n
org.tmforum.mtnm.notifications.EventList_THolder
eventList)
com.ericsson.poaImp
Class FDFrIterator_IPOAImp
java.lang.Object
|
|
+--org.tmforum.mtnm.flowDomainFragment.FDFrIterator_IPOA
|
+--com.ericsson.poaImp.FDFrIterator_IPOAImp
org.tmforum.mtnm.flowDomainFragment.FDFrIterator_IOperations
public class FDFrIterator_IPOAImp

extends org.tmforum.mtnm.flowDomainFragment.FDFrIterator_IPOA
The Class FDFrIterator_IPOAImp.
Constructors
FDFrIterator_IPOAImp
public FDFrIterator_IPOAImp()
Methods
destroy
getLength
next_n
org.tmforum.mtnm.flowDomainFragment.FDFrList_THolder
fdfrList)
com.ericsson.poaImp
Class FDIterator_IPOAImp
java.lang.Object
|
|
+--org.tmforum.mtnm.flowDomain.FDIterator_IPOA
|
+--com.ericsson.poaImp.FDIterator_IPOAImp
org.omg.CORBA.portable.InvokeHandler, org.tmforum.mtnm.flowDomain.FDIterator_IOperations
public class FDIterator_IPOAImp

extends org.tmforum.mtnm.flowDomain.FDIterator_IPOA
The Class FDIterator_IPOAImp.
Constructors
FDIterator_IPOAImp
public FDIterator_IPOAImp()
Methods
destroy
getLength
next_n
org.tmforum.mtnm.flowDomain.FDList_THolder fdList)
com.ericsson.poaImp
Class FlowDomainMgr_IPOAImp
java.lang.Object
|
|
+--org.tmforum.mtnm.flowDomain.FlowDomainMgr_IPOA
|
+--com.ericsson.poaImp.FlowDomainMgr_IPOAImp
org.tmforum.mtnm.flowDomain.FlowDomainMgr_IOperations
public class FlowDomainMgr_IPOAImp

extends org.tmforum.mtnm.flowDomain.FlowDomainMgr_IPOA
The Class FlowDomainMgr_IPOAImp.
Constructors
FlowDomainMgr_IPOAImp
public FlowDomainMgr_IPOAImp()
Methods
assignCPTPsToMFD
public void
assignCPTPsToMFD(org.tmforum.mtnm.globaldefs.NameAndStringValue_T[] mfdName,
org.tmforum.mtnm.globaldefs.NameAndStringValue_T[][] tpNames,
org.tmforum.mtnm.subnetworkConnection.TPDataList_THolder tpsToModify,
org.omg.CORBA.StringHolder errorReason)
associateCPTPsWithFlowDomain
public void
associateCPTPsWithFlowDomain(org.tmforum.mtnm.globaldefs.NameAndStringValue_T[]
fdName,
org.tmforum.mtnm.globaldefs.NameAndStringValue_T[][] cptpNames,
org.omg.CORBA.StringHolder
errorReason)
associateMFDsWithFlowDomain
public void
associateMFDsWithFlowDomain(org.tmforum.mtnm.globaldefs.NameAndStringValue_T[]
fdName,
org.tmforum.mtnm.globaldefs.NameAndStringValue_T[][] mfdNames,
errorReason)
createAndActivateFDFr
public void
createAndActivateFDFr(org.tmforum.mtnm.flowDomainFragment.FDFrCreateData_T
createData,
org.tmforum.mtnm.flowDomain.ConnectivityRequirement_T connectivityRequirement,
org.tmforum.mtnm.globaldefs.NameAndStringValue_T[][] aEnd,
org.tmforum.mtnm.globaldefs.NameAndStringValue_T[][] zEnd,
org.tmforum.mtnm.globaldefs.NamingAttributesList_THolder internalTPs,
org.tmforum.mtnm.flowDomainFragment.MatrixFlowDomainFragmentList_THolder
mfdfrs,
org.tmforum.mtnm.flowDomainFragment.FlowDomainFragment_THolder theFDFr,
org.tmforum.mtnm.globaldefs.NamingAttributesList_THolder
notConnectableCPTPList,
parameterProblemsTPList,
createFTP
public void createFTP(org.tmforum.mtnm.flowDomain.FTPCreateData_T createData,
org.tmforum.mtnm.subnetworkConnection.TPDataList_THolder
tpsToModify,
org.tmforum.mtnm.terminationPoint.TerminationPoint_THolder theFTP,
createFlowDomain
public void createFlowDomain(org.tmforum.mtnm.flowDomain.FDCreateData_T
createData,
org.tmforum.mtnm.globaldefs.NamingAttributesList_THolder assignedCPTPs,
org.tmforum.mtnm.flowDomain.FlowDomain_THolder
theFD,
createMFD
public void createMFD(org.tmforum.mtnm.flowDomain.MFDCreateData_T createData,
tpsToModify,
org.tmforum.mtnm.flowDomain.MatrixFlowDomain_THolder
theMFD,
deAssociateCPTPsFromFlowDomain
public void
deAssociateCPTPsFromFlowDomain(org.tmforum.mtnm.globaldefs.NameAndStringValue_T[]
fdName,
errorReason)
deAssociateMFDsFromFlowDomain
public void
deAssociateMFDsFromFlowDomain(org.tmforum.mtnm.globaldefs.NameAndStringValue_T[]
fdName,
org.tmforum.mtnm.globaldefs.NameAndStringValue_T[][] mfdNames,
errorReason)
deactivateAndDeleteFDFr
public void
deactivateAndDeleteFDFr(org.tmforum.mtnm.globaldefs.NameAndStringValue_T[]
fdfrName,
org.tmforum.mtnm.flowDomainFragment.FlowDomainFragment_THolder theFDFr,
deleteFTP
public void deleteFTP(org.tmforum.mtnm.globaldefs.NameAndStringValue_T[]
ftpName,
tpsToModify,
deleteFlowDomain
public void
deleteFlowDomain(org.tmforum.mtnm.globaldefs.NameAndStringValue_T[] fdName,
deleteMFD
public void deleteMFD(org.tmforum.mtnm.globaldefs.NameAndStringValue_T[]
mfdName,
tpsToModify,
getAllAssignableCPTPs
public void
getAllAssignableCPTPs(org.tmforum.mtnm.globaldefs.NameAndStringValue_T[]
mfdName,
int howMany,
org.tmforum.mtnm.terminationPoint.TerminationPointList_THolder cptpList,
org.tmforum.mtnm.terminationPoint.TerminationPointIterator_IHolder cptpIt)
getAllAssignedCPTPs
public void
getAllAssignedCPTPs(org.tmforum.mtnm.globaldefs.NameAndStringValue_T[]
mfdName,
int howMany,
getAllAssociatedMFDs
public void
getAllAssociatedMFDs(org.tmforum.mtnm.globaldefs.NameAndStringValue_T[]
tmdOrFdName,
int howMany,
org.tmforum.mtnm.flowDomain.MFDList_THolder
mfds,
org.tmforum.mtnm.flowDomain.MFDIterator_IHolder mfdIt)
getAllCPTPs
public void getAllCPTPs(org.tmforum.mtnm.globaldefs.NameAndStringValue_T[]
fdName,
org.tmforum.mtnm.flowDomain.CPTP_Role_T cptpRole,
int howMany,
getAllFDFrs
public void getAllFDFrs(org.tmforum.mtnm.globaldefs.NameAndStringValue_T[]
fdName,
int howMany,
short[] connectivityRateList,
org.tmforum.mtnm.flowDomainFragment.FDFrList_THolder
fdfrList,
org.tmforum.mtnm.flowDomainFragment.FDFrIterator_IHolder fdfrIt)
getAllFlowDomains
public void getAllFlowDomains(int howMany,
org.tmforum.mtnm.flowDomain.FDList_THolder
flowDomains,
org.tmforum.mtnm.flowDomain.FDIterator_IHolder
fdIt)
getAllSupportedMFDs
public void
getAllSupportedMFDs(org.tmforum.mtnm.globaldefs.NameAndStringValue_T[]
holderName,
int howMany,
org.tmforum.mtnm.flowDomain.MFDList_THolder
mfds,
org.tmforum.mtnm.flowDomain.MFDIterator_IHolder mfdIt)
getAllTopologicalLinksOfFD
public void
getAllTopologicalLinksOfFD(org.tmforum.mtnm.globaldefs.NameAndStringValue_T[]
flowDomainName,
int howMany,
getAssigningMFD
public void getAssigningMFD(org.tmforum.mtnm.globaldefs.NameAndStringValue_T[]
cptpName,
org.tmforum.mtnm.flowDomain.MatrixFlowDomain_THolder mfd)
getAssociatingFD
public void
getAssociatingFD(org.tmforum.mtnm.globaldefs.NameAndStringValue_T[] mfdName,
flowDomain)
getCapabilities
capabilities)
getFDFr
public void getFDFr(org.tmforum.mtnm.globaldefs.NameAndStringValue_T[]
fdfrName,
org.tmforum.mtnm.flowDomainFragment.FlowDomainFragment_THolder fdfr)
getFDFrRoute
public void getFDFrRoute(org.tmforum.mtnm.globaldefs.NameAndStringValue_T[]
fdfrName,
org.tmforum.mtnm.flowDomainFragment.FDFrRoute_THolder
route)
getFDFrsByUserLabel
public void getFDFrsByUserLabel(java.lang.String userLabel,
org.tmforum.mtnm.flowDomainFragment.FDFrList_THolder fdfrs)
getFDFrsWithTP
public void getFDFrsWithTP(org.tmforum.mtnm.globaldefs.NameAndStringValue_T[]
cptpName,
int howMany,
org.tmforum.mtnm.flowDomainFragment.FDFrList_THolder fdfrList,
org.tmforum.mtnm.flowDomainFragment.FDFrIterator_IHolder fdfrIt)
getFlowDomain
public void getFlowDomain(org.tmforum.mtnm.globaldefs.NameAndStringValue_T[]
fdName,
flowDomain)
getFlowDomainsByUserLabel
public void getFlowDomainsByUserLabel(java.lang.String userLabel,
org.tmforum.mtnm.flowDomain.FDList_THolder flowDomains)
getMFD
public void getMFD(org.tmforum.mtnm.globaldefs.NameAndStringValue_T[] mfdName,
org.tmforum.mtnm.flowDomain.MatrixFlowDomain_THolder mfd)
getTransmissionParams
public void
getTransmissionParams(org.tmforum.mtnm.globaldefs.NameAndStringValue_T[] name,
java.lang.String[] filter,
org.tmforum.mtnm.transmissionParameters.LayeredParameterList_THolder
transmissionParams)
modifyFDFr
public void modifyFDFr(org.tmforum.mtnm.globaldefs.NameAndStringValue_T[]
fdfrName,
org.tmforum.mtnm.flowDomainFragment.FDFrModifyData_T
fdfrModifyData,
org.tmforum.mtnm.flowDomain.ConnectivityRequirement_T
connectivityRequirement,
org.tmforum.mtnm.globaldefs.NamingAttributesList_THolder failedTPList,
parameterProblemsTPList,
org.tmforum.mtnm.flowDomainFragment.FlowDomainFragment_THolder newFDFr,
modifyFlowDomain
public void
modifyFlowDomain(org.tmforum.mtnm.globaldefs.NameAndStringValue_T[] fdName,
org.tmforum.mtnm.flowDomain.FDModifyData_T
fdModifyData,
modifiedFD,
org.omg.CORBA.StringHolder failedAttributes,
modifyMFD
public void modifyMFD(org.tmforum.mtnm.globaldefs.NameAndStringValue_T[]
mfdName,
org.tmforum.mtnm.flowDomain.MFDModifyData_T
mfdModifyData,
org.tmforum.mtnm.flowDomain.MatrixFlowDomain_THolder
newMFD,
org.omg.CORBA.StringHolder failedAttributes,
setAdditionalInfo
public void
objectName,
additionalInfo)
setNativeEMSName
public void
objectName,
setOwner
objectName,
setUserLabel
objectName,
unassignCPTPsFromMFD
public void
unassignCPTPsFromMFD(org.tmforum.mtnm.globaldefs.NameAndStringValue_T[]
mfdName,
com.ericsson.poaImp
Class GTPiterator_IPOAImp
java.lang.Object
|
|
+--org.tmforum.mtnm.terminationPoint.GTPiterator_IPOA
|
+--com.ericsson.poaImp.GTPiterator_IPOAImp
org.tmforum.mtnm.terminationPoint.GTPiterator_IOperations
public class GTPiterator_IPOAImp

extends org.tmforum.mtnm.terminationPoint.GTPiterator_IPOA
The Class GTPiterator_IPOAImp.
Constructors
GTPiterator_IPOAImp
public GTPiterator_IPOAImp()
Methods
destroy
getLength
next_n
org.tmforum.mtnm.terminationPoint.GTPlist_THolder
gtpList)
com.ericsson.poaImp
Class GuiCutThroughMgr_IPOAImp
java.lang.Object
|
|
+--org.tmforum.mtnm.guiCutThrough.GuiCutThroughMgr_IPOA
|
+--com.ericsson.poaImp.GuiCutThroughMgr_IPOAImp
org.tmforum.mtnm.guiCutThrough.GuiCutThroughMgr_IOperations
public class GuiCutThroughMgr_IPOAImp

extends org.tmforum.mtnm.guiCutThrough.GuiCutThroughMgr_IPOA
The Class GuiCutThroughMgr_IPOAImp.
Constructors
GuiCutThroughMgr_IPOAImp
public GuiCutThroughMgr_IPOAImp()
Methods
destroyGCT
public void destroyGCT(java.lang.String displayAddress)
getCapabilities
capabilities)
getGCTProfileInfo
public void
getGCTProfileInfo(org.tmforum.mtnm.guiCutThrough.GCTProfileInfo_THolder
gctProfileInfo)
launchGCT
public void launchGCT(org.tmforum.mtnm.globaldefs.NameAndStringValue_T[]
objectName,
java.lang.String gctContext,
userInfo,
java.lang.String displayAddress,
additionalInputInfo,
org.omg.CORBA.BooleanHolder closingEnabled,
additionalOutputInfo)
setAdditionalInfo
public void
objectName,
additionalInfo)
setNBI
Sets the nBI.
Parameters:
nbi - the new nBI
setNativeEMSName
public void
objectName,
setOwner
objectName,
setUserLabel
objectName,
com.ericsson.poaImp
Class MFDFrIterator_IPOAImp
java.lang.Object
|
|
+--org.tmforum.mtnm.flowDomainFragment.MFDFrIterator_IPOA
|
+--com.ericsson.poaImp.MFDFrIterator_IPOAImp
org.tmforum.mtnm.flowDomainFragment.MFDFrIterator_IOperations
public class MFDFrIterator_IPOAImp

extends org.tmforum.mtnm.flowDomainFragment.MFDFrIterator_IPOA
The Class MFDFrIterator_IPOAImp.
Constructors
MFDFrIterator_IPOAImp
public MFDFrIterator_IPOAImp()
Methods
destroy
getLength
next_n
org.tmforum.mtnm.flowDomainFragment.MatrixFlowDomainFragmentList_THolder
mfdfrList)
com.ericsson.poaImp
Class MFDIterator_IPOAImp
java.lang.Object
|
|
+--org.tmforum.mtnm.flowDomain.MFDIterator_IPOA
|
+--com.ericsson.poaImp.MFDIterator_IPOAImp
org.tmforum.mtnm.flowDomain.MFDIterator_IOperations
public class MFDIterator_IPOAImp

extends org.tmforum.mtnm.flowDomain.MFDIterator_IPOA
The Class MFDIterator_IPOAImp.
Constructors
MFDIterator_IPOAImp
public MFDIterator_IPOAImp()
Methods
destroy
getLength
next_n
org.tmforum.mtnm.flowDomain.MFDList_THolder mfdList)
com.ericsson.poaImp
Class MLSNPPIterator_IPOAImp
java.lang.Object
|
|
+--org.tmforum.mtnm.mLSNPP.MLSNPPIterator_IPOA
|
+--com.ericsson.poaImp.MLSNPPIterator_IPOAImp
org.tmforum.mtnm.mLSNPP.MLSNPPIterator_IOperations
public class MLSNPPIterator_IPOAImp

extends org.tmforum.mtnm.mLSNPP.MLSNPPIterator_IPOA
The Class MLSNPPIterator_IPOAImp.
Constructors
MLSNPPIterator_IPOAImp
public MLSNPPIterator_IPOAImp()
Methods
destroy
getLength
next_n
org.tmforum.mtnm.mLSNPP.MLSNPPList_THolder mLSNPPList)
com.ericsson.poaImp
Class MLSNPPLinkIterator_IPOAImp
java.lang.Object
|
|
+--org.tmforum.mtnm.mLSNPPLink.MLSNPPLinkIterator_IPOA
|
+--com.ericsson.poaImp.MLSNPPLinkIterator_IPOAImp
org.tmforum.mtnm.mLSNPPLink.MLSNPPLinkIterator_IOperations
public class MLSNPPLinkIterator_IPOAImp

extends org.tmforum.mtnm.mLSNPPLink.MLSNPPLinkIterator_IPOA
The Class MLSNPPLinkIterator_IPOAImp.
Constructors
MLSNPPLinkIterator_IPOAImp
public MLSNPPLinkIterator_IPOAImp()
Methods
destroy
getLength
next_n
org.tmforum.mtnm.mLSNPPLink.MLSNPPLinkList_THolder
mLSNPPLink)
com.ericsson.poaImp
Class MLSNPPLinkMgr_IPOAImp
java.lang.Object
|
|
+--org.tmforum.mtnm.mLSNPPLink.MLSNPPLinkMgr_IPOA
|
+--com.ericsson.poaImp.MLSNPPLinkMgr_IPOAImp
org.tmforum.mtnm.mLSNPPLink.MLSNPPLinkMgr_IOperations
public class MLSNPPLinkMgr_IPOAImp

extends org.tmforum.mtnm.mLSNPPLink.MLSNPPLinkMgr_IPOA
The Class MLSNPPLinkMgr_IPOAImp.
Constructors
MLSNPPLinkMgr_IPOAImp
public MLSNPPLinkMgr_IPOAImp()
Methods
assignSignallingController
public void
assignSignallingController(org.tmforum.mtnm.globaldefs.NameAndStringValue_T[]
mLSNPPLinkName,
java.lang.String
signallingControllerIdentifier)
deassignSignallingController
public void
deassignSignallingController(org.tmforum.mtnm.globaldefs.NameAndStringValue_T[]
mLSNPPLinkName)
disableSignalling
public void
disableSignalling(org.tmforum.mtnm.globaldefs.NameAndStringValue_T[]
mLSNPPLinkName)
enableSignalling
public void
enableSignalling(org.tmforum.mtnm.globaldefs.NameAndStringValue_T[]
mLSNPPLinkName)
getAvailableCapacity
public void
getAvailableCapacity(org.tmforum.mtnm.globaldefs.NameAndStringValue_T[]
mLSNPPLinkName,
short layerRate,
org.tmforum.mtnm.mLSNPPLink.AvailableCapacity_THolder availableCapacity)
getCapabilities
capabilities)
modifySignallingProtocolParameters
public void
modifySignallingProtocolParameters(org.tmforum.mtnm.globaldefs.NameAndStringValue_T
mLSNPPLinkName,
org.tmforum.mtnm.globaldefs.NVSList_THolder signallingParameters)
setAdditionalInfo
public void
objectName,
additionalInfo)
setNativeEMSName
public void
objectName,
setOwner
objectName,
setSignallingProtocolAndParameters
public void
setSignallingProtocolAndParameters(org.tmforum.mtnm.globaldefs.NameAndStringValue_T
mLSNPPLinkName,
java.lang.String
signallingProtocol,
org.tmforum.mtnm.globaldefs.NameAndStringValue_T[] signallingParameters)
setTNANameForMLSNPPLinkEnd
public void
setTNANameForMLSNPPLinkEnd(org.tmforum.mtnm.globaldefs.NameAndStringValue_T[]
mLSNPPLinkName,
org.tmforum.mtnm.mLSNPP.SNPTNAData_T[]
sNPTNADataList,
org.tmforum.mtnm.mLSNPP.SNPPTNAPair_T[]
sNPPTNAPairList,
java.lang.String aTNAName,
java.lang.String zTNAName,
java.lang.String aTNAGroupName,
java.lang.String zTNAGroupName,
org.tmforum.mtnm.mLSNPPLink.MultiLayerSNPPLink_THolder mLSNPPLink)
setUserLabel
objectName,
com.ericsson.poaImp
Class MLSNPPMgr_IPOAImp
java.lang.Object
|
|
+--org.tmforum.mtnm.mLSNPP.MLSNPPMgr_IPOA
|
+--com.ericsson.poaImp.MLSNPPMgr_IPOAImp
org.omg.CORBA.portable.InvokeHandler, org.tmforum.mtnm.mLSNPP.MLSNPPMgr_IOperations
public class MLSNPPMgr_IPOAImp

extends org.tmforum.mtnm.mLSNPP.MLSNPPMgr_IPOA
The Class MLSNPPMgr_IPOAImp.
Constructors
MLSNPPMgr_IPOAImp
public MLSNPPMgr_IPOAImp()
Methods
getCapabilities
capabilities)
getMLSNPP
public void getMLSNPP(org.tmforum.mtnm.globaldefs.NameAndStringValue_T[]
mLSNPPName,
org.tmforum.mtnm.mLSNPP.MultiLayerSNPP_THolder
theMLSNPP)
setAdditionalInfo
public void
objectName,
additionalInfo)
setNativeEMSName
public void
objectName,
setOwner
objectName,
setTNANameForMLSNPP
public void
setTNANameForMLSNPP(org.tmforum.mtnm.globaldefs.NameAndStringValue_T[]
mLSNPPName,
org.tmforum.mtnm.mLSNPP.SNPTNAData_T[]
sNPTNADataList,
org.tmforum.mtnm.mLSNPP.SNPPTNAPair_T[]
sNPPTNAPairList,
java.lang.String tNAName,
java.lang.String tNAGroupName,
org.tmforum.mtnm.mLSNPP.MultiLayerSNPP_THolder
mLSNPP)
setUserLabel
objectName,
com.ericsson.poaImp
Class MaintenanceMgr_IPOAImp
java.lang.Object
|
|
+--org.tmforum.mtnm.maintenanceOps.MaintenanceMgr_IPOA
|
+--com.ericsson.poaImp.MaintenanceMgr_IPOAImp
org.tmforum.mtnm.maintenanceOps.MaintenanceMgr_IOperations
public class MaintenanceMgr_IPOAImp

extends org.tmforum.mtnm.maintenanceOps.MaintenanceMgr_IPOA
The Class MaintenanceMgr_IPOAImp.
Constructors
MaintenanceMgr_IPOAImp
public MaintenanceMgr_IPOAImp()
Methods
getActiveMaintenanceOperations
public void
getActiveMaintenanceOperations(org.tmforum.mtnm.globaldefs.NameAndStringValue_T[]
tpOrMeName,
int howMany,
org.tmforum.mtnm.maintenanceOps.CurrentMaintenanceOperationList_THolder
currentMaintenanceOpeationList,
org.tmforum.mtnm.maintenanceOps.CurrentMaintenanceOperationIterator_IHolder
cmoIt)
getCapabilities
capabilities)
performMaintenanceOperation
public void
performMaintenanceOperation(org.tmforum.mtnm.maintenanceOps.CurrentMaintenanceOpera
maintenanceOperation,
org.tmforum.mtnm.maintenanceOps.MaintenanceOperationMode_T
maintenanceOperationMode)
setAdditionalInfo
public void
objectName,
additionalInfo)
setNativeEMSName
public void
objectName,
setOwner
objectName,
setUserLabel
objectName,
com.ericsson.poaImp
Class ManagedElementIterator_IPOAImp
java.lang.Object
|
|
+--org.tmforum.mtnm.managedElement.ManagedElementIterator_IPOA
|
+--com.ericsson.poaImp.ManagedElementIterator_IPOAImp
org.tmforum.mtnm.managedElement.ManagedElementIterator_IOperations
public class ManagedElementIterator_IPOAImp

extends org.tmforum.mtnm.managedElement.ManagedElementIterator_IPOA
The Class ManagedElementIterator_IPOAImp.
Constructors
ManagedElementIterator_IPOAImp
public ManagedElementIterator_IPOAImp(java.util.ArrayList list,
NBIImp nbi,
int size)
Instantiates a new managed element iterator_ ipoa imp.
Parameters:
list - the list
nbi - the nbi
size - the size
Methods
destroy
getLength
next_n
org.tmforum.mtnm.managedElement.ManagedElementList_THolder meList)
com.ericsson.poaImp
Class ManagedElementMgr_IPOAImp
java.lang.Object
|
|
+--org.tmforum.mtnm.managedElementManager.ManagedElementMgr_IPOA
|
+--com.ericsson.poaImp.ManagedElementMgr_IPOAImp
org.tmforum.mtnm.managedElementManager.ManagedElementMgr_IOperations
public class ManagedElementMgr_IPOAImp

extends org.tmforum.mtnm.managedElementManager.ManagedElementMgr_IPOA
The Class ManagedElementMgr_IPOAImp.
Constructors
ManagedElementMgr_IPOAImp
public ManagedElementMgr_IPOAImp()
Methods
createGTP
public void createGTP(java.lang.String userLabel,
boolean forceUniqueness,
org.tmforum.mtnm.globaldefs.NameAndStringValue_T[][]
listOfTPs,
initialCTPname,
int numberOfCTPs,
org.tmforum.mtnm.terminationPoint.GTPEffort_T gtpEffort,
additionalCreationInfo,
org.tmforum.mtnm.terminationPoint.GTP_THolder newGTP)
deleteGTP
public void deleteGTP(org.tmforum.mtnm.globaldefs.NameAndStringValue_T[]
gtpName)
getAllActiveAlarms
public void
getAllActiveAlarms(org.tmforum.mtnm.globaldefs.NameAndStringValue_T[] meName,
java.lang.String[] excludeProbCauseList,
int howMany,
getAllCrossConnections
public void
getAllCrossConnections(org.tmforum.mtnm.globaldefs.NameAndStringValue_T[]
managedElementName,
short[] connectionRateList,
int howMany,
org.tmforum.mtnm.subnetworkConnection.CrossConnectList_THolder ccList,
org.tmforum.mtnm.subnetworkConnection.CCIterator_IHolder ccIt)
getAllFTPNames
public void getAllFTPNames(org.tmforum.mtnm.globaldefs.NameAndStringValue_T[]
managedElementName,
short[] tpLayerRateList,
short[] connectionLayerRateList,
int howMany,
getAllFTPs
public void getAllFTPs(org.tmforum.mtnm.globaldefs.NameAndStringValue_T[]
managedElementName,
int howMany,
getAllFixedCrossConnections
public void
getAllFixedCrossConnections(org.tmforum.mtnm.globaldefs.NameAndStringValue_T[]
managedElementName,
int howMany,
org.tmforum.mtnm.subnetworkConnection.CrossConnectList_THolder ccList,
org.tmforum.mtnm.subnetworkConnection.CCIterator_IHolder ccIt)
getAllGTPNames
public void getAllGTPNames(org.tmforum.mtnm.globaldefs.NameAndStringValue_T[]
managedElementName,
int howMany,
getAllGTPs
public void getAllGTPs(org.tmforum.mtnm.globaldefs.NameAndStringValue_T[]
managedElementName,
int howMany,
org.tmforum.mtnm.terminationPoint.GTPlist_THolder
gtpList,
org.tmforum.mtnm.terminationPoint.GTPiterator_IHolder
gtpIt)
public void getAllManagedElementNames(int howMany,
public void getAllManagedElements(int howMany,
org.tmforum.mtnm.managedElement.ManagedElementList_THolder meList,
org.tmforum.mtnm.managedElement.ManagedElementIterator_IHolder meIt)
getAllPTPNames
public void getAllPTPNames(org.tmforum.mtnm.globaldefs.NameAndStringValue_T[]
managedElementName,
int howMany,
getAllPTPNamesWithoutFTPs
public void
getAllPTPNamesWithoutFTPs(org.tmforum.mtnm.globaldefs.NameAndStringValue_T[]
managedElementName,
int howMany,
getAllPTPs
public void getAllPTPs(org.tmforum.mtnm.globaldefs.NameAndStringValue_T[]
managedElementName,
int howMany,
getAllPTPsWithoutFTPs
public void
getAllPTPsWithoutFTPs(org.tmforum.mtnm.globaldefs.NameAndStringValue_T[]
managedElementName,
int howMany,
getAllUnacknowledgedActiveAlarms
public void
getAllUnacknowledgedActiveAlarms(org.tmforum.mtnm.globaldefs.NameAndStringValue_T[]
meName,
java.lang.String[]
int howMany,
getCapabilities
capabilities)
public void
getContainedCurrentTPNames(org.tmforum.mtnm.globaldefs.NameAndStringValue_T[]
tpName,
int howMany,
public void
getContainedCurrentTPs(org.tmforum.mtnm.globaldefs.NameAndStringValue_T[]
tpName,
int howMany,
public void
getContainedInUseTPNames(org.tmforum.mtnm.globaldefs.NameAndStringValue_T[]
tpName,
int howMany,
public void
getContainedInUseTPs(org.tmforum.mtnm.globaldefs.NameAndStringValue_T[]
tpName,
int howMany,
public void
getContainedPotentialTPNames(org.tmforum.mtnm.globaldefs.NameAndStringValue_T[]
tpName,
int howMany,
public void
getContainedPotentialTPs(org.tmforum.mtnm.globaldefs.NameAndStringValue_T[]
tpName,
int howMany,
getContainingGTP
public void
getContainingGTP(org.tmforum.mtnm.globaldefs.NameAndStringValue_T[] ctpName,
org.tmforum.mtnm.terminationPoint.GTP_THolder
gtp)
getContainingSubnetworkNames
public void
getContainingSubnetworkNames(org.tmforum.mtnm.globaldefs.NameAndStringValue_T[]
managedElementName,
org.tmforum.mtnm.globaldefs.NamingAttributesList_THolder subnetNames)
getContainingTPNames
public void
getContainingTPNames(org.tmforum.mtnm.globaldefs.NameAndStringValue_T[]
tpName,
org.tmforum.mtnm.globaldefs.NamingAttributesList_THolder tpNameList)
getContainingTPs
public void
getContainingTPs(org.tmforum.mtnm.globaldefs.NameAndStringValue_T[] tpName,
org.tmforum.mtnm.terminationPoint.TerminationPointList_THolder tpList)
getGTP
public void getGTP(org.tmforum.mtnm.globaldefs.NameAndStringValue_T[] gtpName,
org.tmforum.mtnm.terminationPoint.GTP_THolder gtp)
getManagedElement
public void
getManagedElement(org.tmforum.mtnm.globaldefs.NameAndStringValue_T[]
managedElementName,
org.tmforum.mtnm.managedElement.ManagedElement_THolder me)
getPotentialFixedCCs
public void
getPotentialFixedCCs(org.tmforum.mtnm.globaldefs.NameAndStringValue_T[]
inputTP,
org.tmforum.mtnm.globaldefs.NamingAttributes_THolder ContainingTP,
org.tmforum.mtnm.globaldefs.NamingAttributes_THolder potentialCCList)
getTP
public void getTP(org.tmforum.mtnm.globaldefs.NameAndStringValue_T[] tpName,
org.tmforum.mtnm.terminationPoint.TerminationPoint_THolder
tp)
modifyGTP
public void modifyGTP(org.tmforum.mtnm.globaldefs.NameAndStringValue_T[]
gtpName,
tpNames,
java.lang.String actionType,
org.tmforum.mtnm.terminationPoint.GTP_THolder
modifiedGTP)
setAdditionalInfo
public void
objectName,
additionalInfo)
setGtpAlarmReportingOff
public void
setGtpAlarmReportingOff(org.tmforum.mtnm.globaldefs.NameAndStringValue_T[]
gtpName)
setGtpAlarmReportingOn
public void
setGtpAlarmReportingOn(org.tmforum.mtnm.globaldefs.NameAndStringValue_T[]
gtpName)
setNBI
Sets the nBI.
Parameters:
nbi - the new nBI
setNativeEMSName
public void
objectName,
setOwner
objectName,
setTPData
public void setTPData(org.tmforum.mtnm.subnetworkConnection.TPData_T tpInfo,
org.tmforum.mtnm.terminationPoint.TerminationPoint_THolder modifiedTP)
setUserLabel
objectName,
verifyTMDAssignment
public void
verifyTMDAssignment(org.tmforum.mtnm.globaldefs.NameAndStringValue_T[] tpName,
org.tmforum.mtnm.terminationPoint.Directionality_T direction,
org.omg.CORBA.StringHolder tmdAssignmentState,
transmissionParams,
additionalTPInfo)
com.ericsson.poaImp
Class MultiLayerSubnetworkMgr_IPOAImp
java.lang.Object
|
|
+--org.tmforum.mtnm.multiLayerSubnetwork.MultiLayerSubnetworkMgr_IPOA
|
+--com.ericsson.poaImp.MultiLayerSubnetworkMgr_IPOAImp
org.tmforum.mtnm.multiLayerSubnetwork.MultiLayerSubnetworkMgr_IOperations
public class MultiLayerSubnetworkMgr_IPOAImp

extends org.tmforum.mtnm.multiLayerSubnetwork.MultiLayerSubnetworkMgr_IPOA
The Class MultiLayerSubnetworkMgr_IPOAImp.
Constructors
MultiLayerSubnetworkMgr_IPOAImp
public MultiLayerSubnetworkMgr_IPOAImp()
Methods
activateSNC
public void activateSNC(org.tmforum.mtnm.globaldefs.NameAndStringValue_T[]
sncName,
org.tmforum.mtnm.subnetworkConnection.GradesOfImpact_T
tolerableImpact,
org.tmforum.mtnm.multiLayerSubnetwork.EMSFreedomLevel_T emsFreedomLevel,
org.tmforum.mtnm.subnetworkConnection.SubnetworkConnection_THolder theSNC,
addConnections
public void addConnections(org.tmforum.mtnm.globaldefs.NameAndStringValue_T[]
callName,
org.tmforum.mtnm.subnetworkConnection.SNCCreateData_T[] connectionsToAdd,
boolean connectionRouteReArrangementAllowed,
org.tmforum.mtnm.subnetworkConnection.SubnetworkConnectionList_THolder
connectionList,
partialSNCs,
addRoute
public void addRoute(org.tmforum.mtnm.globaldefs.NameAndStringValue_T[]
sncName,
org.tmforum.mtnm.subnetworkConnection.RouteCreateData_T
createRoute,
tolerableImpact,
org.tmforum.mtnm.multiLayerSubnetwork.EMSFreedomLevel_T
emsFreedomLevel,
org.tmforum.mtnm.subnetworkConnection.RouteDescriptor_THolder theRoute,
checkValidSNC
public void
checkValidSNC(org.tmforum.mtnm.subnetworkConnection.SNCCreateData_T
createData,
org.tmforum.mtnm.subnetworkConnection.TPData_T[]
tpsToModify,
boolean considerResources,
org.omg.CORBA.BooleanHolder valid)
createAndActivateSNC
public void
createAndActivateSNC(org.tmforum.mtnm.subnetworkConnection.SNCCreateData_T
createData,
org.tmforum.mtnm.subnetworkConnection.GradesOfImpact_T tolerableImpact,
createModifiedSNC
public void
createModifiedSNC(org.tmforum.mtnm.globaldefs.NameAndStringValue_T[] sncName,
java.lang.String routeId,
org.tmforum.mtnm.subnetworkConnection.SNCModifyData_T SNCModifyData,
org.tmforum.mtnm.subnetworkConnection.ProtectionEffort_T
tolerableImpactEffort,
org.tmforum.mtnm.subnetworkConnection.SubnetworkConnection_THolder newSNC,
createSNC
public void createSNC(org.tmforum.mtnm.subnetworkConnection.SNCCreateData_T
createData,
tolerableImpact,
emsFreedomLevel,
createTPPool
public void
createTPPool(org.tmforum.mtnm.multiLayerSubnetwork.TPPoolCreateData_T
newTPPoolCreateData,
org.tmforum.mtnm.terminationPoint.TerminationPoint_THolder newTPPool)
deactivateAndDeleteSNC
public void
deactivateAndDeleteSNC(org.tmforum.mtnm.globaldefs.NameAndStringValue_T[]
sncName,
deactivateSNC
public void deactivateSNC(org.tmforum.mtnm.globaldefs.NameAndStringValue_T[]
sncName,
deleteSNC
public void deleteSNC(org.tmforum.mtnm.globaldefs.NameAndStringValue_T[]
sncName,
emsFreedomLevel)
deleteTPPool
public void deleteTPPool(org.tmforum.mtnm.globaldefs.NameAndStringValue_T[]
tpPoolName)
establishCall
public void establishCall(org.tmforum.mtnm.callSNC.CallCreateData_T
callCreateData,
org.tmforum.mtnm.subnetworkConnection.SNCCreateData_T[]
connectionCreateDataList,
java.lang.String routeGroupsNumber,
org.tmforum.mtnm.callSNC.CallAndTopLevelConnectionsAndSNCs_THolder
callAndTopLevelConnectionsAndSNCs,
org.tmforum.mtnm.subnetworkConnection.SNCCreateDataList_THolder
sNCsNotCreated,
partialSNCs,
org.omg.CORBA.StringHolder callErrorReason)
getAllCallIdsWithSNPPOrTNAName
public void
getAllCallIdsWithSNPPOrTNAName(org.tmforum.mtnm.globaldefs.NameAndStringValue_T
sNPPOrTNAName,
org.tmforum.mtnm.callSNC.CallIdList_THolder callIdList)
getAllCallIdsWithTP
public void
getAllCallIdsWithTP(org.tmforum.mtnm.globaldefs.NameAndStringValue_T[] tPName,
org.tmforum.mtnm.callSNC.CallIdList_THolder
callIdList)
getAllCallsAndTopLevelConnections
public void
getAllCallsAndTopLevelConnections(org.tmforum.mtnm.globaldefs.NameAndStringValue_T[
subnetName,
int howMany,
callAndTopLevelConnectionsList,
org.tmforum.mtnm.callSNC.CallAndTopLevelConnectionsIterator_IHolder
callAndTopLevelConnectionsIt)
getAllCallsAndTopLevelConnectionsAndSNCs
public void
getAllCallsAndTopLevelConnectionsAndSNCs(org.tmforum.mtnm.globaldefs.NameAndStringV
subnetName,
int howMany,
callAndTopLevelConnectionsAndSNCsList,
org.tmforum.mtnm.callSNC.CallAndTopLevelConnectionsAndSNCsIterator_IHolder
callAndTopLevelConnectionsAndSNCsIt)
getAllCallsAndTopLevelConnectionsAndSNCsWithME
public void
getAllCallsAndTopLevelConnectionsAndSNCsWithME(org.tmforum.mtnm.globaldefs.NameAndS
subnetName,
org.tmforum.mtnm.globaldefs.NameAndStringValue_T[] meName,
int howMany,
getAllCallsAndTopLevelConnectionsAndSNCsWithTP
public void
getAllCallsAndTopLevelConnectionsAndSNCsWithTP(org.tmforum.mtnm.globaldefs.NameAndS
subnetName,
org.tmforum.mtnm.globaldefs.NameAndStringValue_T[] tPName,
int howMany,
getAllCallsAndTopLevelConnectionsWithME
public void
getAllCallsAndTopLevelConnectionsWithME(org.tmforum.mtnm.globaldefs.NameAndStringVa
subnetName,
org.tmforum.mtnm.globaldefs.NameAndStringValue_T[] meName,
int howMany,
callAndTopLevelConnectionsList,
org.tmforum.mtnm.callSNC.CallAndTopLevelConnectionsIterator_IHolder
callAndTopLevelConnectionsIt)
getAllEdgeMLSNPPLinks
public void
getAllEdgeMLSNPPLinks(org.tmforum.mtnm.globaldefs.NameAndStringValue_T[]
subnetName,
int howMany,
getAllEdgePointNames
public void
getAllEdgePointNames(org.tmforum.mtnm.globaldefs.NameAndStringValue_T[]
subnetName,
int howMany,
getAllEdgePoints
public void
getAllEdgePoints(org.tmforum.mtnm.globaldefs.NameAndStringValue_T[]
subnetName,
int howMany,
getAllFixedSubnetworkConnectionNames
public void
getAllFixedSubnetworkConnectionNames(org.tmforum.mtnm.globaldefs.NameAndStringValue
subnetName,
int howMany,
getAllFixedSubnetworkConnectionNamesWithTP
public void
getAllFixedSubnetworkConnectionNamesWithTP(org.tmforum.mtnm.globaldefs.NameAndStrin
tpName,
short[]
connectionRateList,
int howMany,
getAllFixedSubnetworkConnections
public void
getAllFixedSubnetworkConnections(org.tmforum.mtnm.globaldefs.NameAndStringValue_T[]
subnetName,
int howMany,
sncList,
org.tmforum.mtnm.subnetworkConnection.SNCIterator_IHolder sncIt)
getAllFixedSubnetworkConnectionsWithTP
public void
getAllFixedSubnetworkConnectionsWithTP(org.tmforum.mtnm.globaldefs.NameAndStringVal
tpName,
int howMany,
sncList,
getAllInternalMLSNPPLinks
public void
getAllInternalMLSNPPLinks(org.tmforum.mtnm.globaldefs.NameAndStringValue_T[]
subnetName,
int howMany,
getAllMLSNPPLinks
public void
getAllMLSNPPLinks(org.tmforum.mtnm.globaldefs.NameAndStringValue_T[]
subnetName,
int howMany,
getAllMLSNPPs
public void getAllMLSNPPs(org.tmforum.mtnm.globaldefs.NameAndStringValue_T[]
subnetName,
int howMany,
mLSNPPList,
mLSNPPIt)
public void
getAllManagedElementNames(org.tmforum.mtnm.globaldefs.NameAndStringValue_T[]
subnetName,
int howMany,
public void
getAllManagedElements(org.tmforum.mtnm.globaldefs.NameAndStringValue_T[]
subnetName,
int howMany,
org.tmforum.mtnm.managedElement.ManagedElementList_THolder meList,
org.tmforum.mtnm.managedElement.ManagedElementIterator_IHolder meIt)
getAllSubnetworkConnectionNames
public void
getAllSubnetworkConnectionNames(org.tmforum.mtnm.globaldefs.NameAndStringValue_T[]
subnetName,
int howMany,
getAllSubnetworkConnectionNamesWithTP
public void
getAllSubnetworkConnectionNamesWithTP(org.tmforum.mtnm.globaldefs.NameAndStringValu
tpName,
int howMany,
getAllSubnetworkConnections
public void
getAllSubnetworkConnections(org.tmforum.mtnm.globaldefs.NameAndStringValue_T[]
subnetName,
int howMany,
sncList,
getAllSubnetworkConnectionsWithTP
public void
getAllSubnetworkConnectionsWithTP(org.tmforum.mtnm.globaldefs.NameAndStringValue_T[
tpName,
int howMany,
sncList,
getAllSubordinateMLSNs
public void
getAllSubordinateMLSNs(org.tmforum.mtnm.globaldefs.NameAndStringValue_T[]
subnetName,
int howMany,
org.tmforum.mtnm.multiLayerSubnetwork.SubnetworkList_THolder
subordinateMLSNsList,
org.tmforum.mtnm.multiLayerSubnetwork.SubnetworkIterator_IHolder subnetIt)
getAllSubordinateRAidsWithConnection
public void
getAllSubordinateRAidsWithConnection(org.tmforum.mtnm.globaldefs.NameAndStringValue
subnetName,
org.tmforum.mtnm.globaldefs.NameAndStringValue_T[] connection,
java.lang.String routeType,
org.tmforum.mtnm.multiLayerSubnetwork.RoutePerRouteType_THolder
routePerRouteType)
getAllTPPoolNames
public void
getAllTPPoolNames(org.tmforum.mtnm.globaldefs.NameAndStringValue_T[]
subnetworkName,
int howMany,
getAllTPPools
public void getAllTPPools(org.tmforum.mtnm.globaldefs.NameAndStringValue_T[]
subnetworkName,
int howMany,
getAllTopologicalLinkNames
public void
getAllTopologicalLinkNames(org.tmforum.mtnm.globaldefs.NameAndStringValue_T[]
subnetName,
int howMany,
public void
getAllTopologicalLinks(org.tmforum.mtnm.globaldefs.NameAndStringValue_T[]
subnetName,
int howMany,
getAssociatedTP
public void getAssociatedTP(org.tmforum.mtnm.globaldefs.NameAndStringValue_T[]
tpName,
getBackupRoutes
public void getBackupRoutes(org.tmforum.mtnm.globaldefs.NameAndStringValue_T[]
sncName,
boolean includeHigherOrderCCs,
additionalInfo,
org.tmforum.mtnm.subnetworkConnection.RouteList_THolder routeList)
getCall
public void getCall(org.tmforum.mtnm.globaldefs.NameAndStringValue_T[]
callName,
org.tmforum.mtnm.callSNC.Call_THolder theCall)
getCallAndTopLevelConnections
public void
getCallAndTopLevelConnections(org.tmforum.mtnm.globaldefs.NameAndStringValue_T[]
callName,
java.lang.String callId,
org.tmforum.mtnm.callSNC.CallAndTopLevelConnections_THolder
callAndTopLevelConnections)
getCallAndTopLevelConnectionsAndSNCs
public void
getCallAndTopLevelConnectionsAndSNCs(org.tmforum.mtnm.globaldefs.NameAndStringValue
callName,
org.tmforum.mtnm.callSNC.CallAndTopLevelConnectionsAndSNCs_THolder
callAndTopLevelConnectionsAndSNCs)
getCapabilities
capabilities)
getConnectionsAndRouteDetails
public void getConnectionsAndRouteDetails(java.lang.String callID,
org.tmforum.mtnm.globaldefs.NameAndStringValue_T[] mLRAName,
java.lang.String sNPOrSNPPID,
boolean mLSNPPLinkRequested,
java.lang.String routeType,
org.tmforum.mtnm.callSNC.SNCAndRouteList_THolder connectionAndRouteList)
getIntendedRoute
public void
getIntendedRoute(org.tmforum.mtnm.globaldefs.NameAndStringValue_T[] sncName,
additionalInfo,
org.tmforum.mtnm.subnetworkConnection.Route_THolder route)
getMLSNPPLink
public void getMLSNPPLink(org.tmforum.mtnm.globaldefs.NameAndStringValue_T[]
mLSNPPLinkName,
org.tmforum.mtnm.mLSNPPLink.MultiLayerSNPPLink_THolder theMLSNPPLink)
getMultiLayerSubnetwork
public void
getMultiLayerSubnetwork(org.tmforum.mtnm.globaldefs.NameAndStringValue_T[]
subnetName,
org.tmforum.mtnm.multiLayerSubnetwork.MultiLayerSubnetwork_THolder subnetwork)
getRoute
public void getRoute(org.tmforum.mtnm.globaldefs.NameAndStringValue_T[]
sncName,
org.tmforum.mtnm.subnetworkConnection.Route_THolder
route)
getRouteAndTopologicalLinks
public void
getRouteAndTopologicalLinks(org.tmforum.mtnm.globaldefs.NameAndStringValue_T[]
sncName,
org.tmforum.mtnm.subnetworkConnection.Route_THolder route,
org.tmforum.mtnm.topologicalLink.TopologicalLinkList_THolder
topologicalLinkList)
getSNC
public void getSNC(org.tmforum.mtnm.globaldefs.NameAndStringValue_T[] sncName,
org.tmforum.mtnm.subnetworkConnection.SubnetworkConnection_THolder snc)
getSNCsByUserLabel
public void getSNCsByUserLabel(java.lang.String userLabel,
sncList)
getTPGroupingRelationships
public void
getTPGroupingRelationships(org.tmforum.mtnm.globaldefs.NameAndStringValue_T[]
tpName,
int howMany,
getTPPool
public void getTPPool(org.tmforum.mtnm.globaldefs.NameAndStringValue_T[]
tPPoolName,
org.tmforum.mtnm.terminationPoint.TerminationPoint_THolder tPPool,
org.omg.CORBA.IntHolder numberOfMembers,
org.omg.CORBA.IntHolder numberOfIdleMembers,
org.omg.CORBA.StringHolder descriptionOfUse)
getTopologicalLink
public void
getTopologicalLink(org.tmforum.mtnm.globaldefs.NameAndStringValue_T[]
topoLinkName,
org.tmforum.mtnm.topologicalLink.TopologicalLink_THolder topoLink)
modifyCall
public void modifyCall(org.tmforum.mtnm.globaldefs.NameAndStringValue_T[]
callName,
org.tmforum.mtnm.callSNC.CallModifyData_T
callModifyData,
org.tmforum.mtnm.callSNC.Call_THolder modifiedCall)
modifyDiversityAndCorouting
public void
modifyDiversityAndCorouting(org.tmforum.mtnm.globaldefs.NameAndStringValue_T[]
callName,
org.tmforum.mtnm.callSNC.Diversity_T
callDiversity,
org.tmforum.mtnm.callSNC.RouteGroupInfo_T[] routeGroupInfoList,
boolean
connectionRouteReArrangementAllowed,
java.lang.String routeGroupsNumber,
org.tmforum.mtnm.globaldefs.NVSList_THolder additionalInfo,
org.tmforum.mtnm.callSNC.CallAndTopLevelConnections_THolder
callAndTopLevelConnections)
modifySNC
public void modifySNC(org.tmforum.mtnm.globaldefs.NameAndStringValue_T[]
sncName,
org.tmforum.mtnm.subnetworkConnection.SNCModifyData_T
SNCModifyData,
tolerableImpact,
org.tmforum.mtnm.subnetworkConnection.ProtectionEffort_T
tolerableImpactEffort,
emsFreedomLevel,
tpsToModify,
org.tmforum.mtnm.subnetworkConnection.SubnetworkConnection_THolder newSNC,
modifyTPPool
public void modifyTPPool(org.tmforum.mtnm.globaldefs.NameAndStringValue_T[]
tPPoolName,
containedMembers,
java.lang.String actionType,
org.tmforum.mtnm.terminationPoint.TerminationPoint_THolder modifiedTPPool)
releaseCall
public void releaseCall(org.tmforum.mtnm.globaldefs.NameAndStringValue_T[]
callName,
remainingSNCs,
removeConnections
public void
removeConnections(org.tmforum.mtnm.globaldefs.NameAndStringValue_T[] callName,
org.tmforum.mtnm.globaldefs.NameAndStringValue_T[][] connectionNamesList,
sNCsNotDeleted,
removeRoute
public void removeRoute(org.tmforum.mtnm.globaldefs.NameAndStringValue_T[]
sncName,
additionalInfo)
setAdditionalInfo
public void
objectName,
additionalInfo)
setIntendedRoute
public void
setIntendedRoute(org.tmforum.mtnm.globaldefs.NameAndStringValue_T[] sncName,
additionalInfo)
setNBI
Sets the nBI.
Parameters:
nbi - the new nBI
setNativeEMSName
public void
objectName,
setOwner
objectName,
setRoutesAdminState
public void
setRoutesAdminState(org.tmforum.mtnm.globaldefs.NameAndStringValue_T[]
sncName,
org.tmforum.mtnm.subnetworkConnection.RouteNameAndAdminStateList_THolder
routeNameAndAdminStateList,
org.tmforum.mtnm.subnetworkConnection.SNCState_THolder sncState)
setUserLabel
objectName,
swapSNC
public void swapSNC(org.tmforum.mtnm.globaldefs.NameAndStringValue_T[]
nameOfSNCtoBeDeactivated,
nameOfSNCtoBeActivated,
emsFreedomLevel,
tolerableImpact,
tpsToModify,
org.tmforum.mtnm.subnetworkConnection.SNCState_THolder
stateOfActivatedSNC,
switchRoute
public void switchRoute(org.tmforum.mtnm.globaldefs.NameAndStringValue_T[]
sncName,
tolerableImpact,
additionalInfo,
org.tmforum.mtnm.subnetworkConnection.SNCState_THolder
sncState,
com.ericsson.poaImp
Class NamingAttributesIterator_IPOAImp
java.lang.Object
|
|
+--org.tmforum.mtnm.globaldefs.NamingAttributesIterator_IPOA
|
+--com.ericsson.poaImp.NamingAttributesIterator_IPOAImp
org.tmforum.mtnm.globaldefs.NamingAttributesIterator_IOperations
public class NamingAttributesIterator_IPOAImp

extends org.tmforum.mtnm.globaldefs.NamingAttributesIterator_IPOA
The Class NamingAttributesIterator_IPOAImp.
Constructors
NamingAttributesIterator_IPOAImp
public NamingAttributesIterator_IPOAImp(java.util.ArrayList list,
NBIImp nbi,
int size)
Instantiates a new naming attributes iterator_ ipoa imp.
Parameters:
list - the list
nbi - the nbi
size - the size
Methods
destroy
getLength
next_n
nameList)
com.ericsson.poaImp
Class NmsSession_IPOAImp
java.lang.Object
|
|
+--org.tmforum.mtnm.nmsSession.NmsSession_IPOA
|
+--com.ericsson.poaImp.NmsSession_IPOAImp
org.tmforum.mtnm.nmsSession.NmsSession_IOperations
public class NmsSession_IPOAImp

extends org.tmforum.mtnm.nmsSession.NmsSession_IPOA
The Class NmsSession_IPOAImp.
Constructors
NmsSession_IPOAImp
public NmsSession_IPOAImp()
Methods
alarmLossOccurred
public void alarmLossOccurred(java.lang.String startTime,
java.lang.String notificationId)
associatedSession
endSession
eventLossCleared
public void eventLossCleared(java.lang.String endTime)
eventLossOccurred
public void eventLossOccurred(java.lang.String startTime,
java.lang.String notificationId)
ping
public void ping()
com.ericsson.poaImp
Class PMDataIterator_IPOAImp
java.lang.Object
|
|
+--org.tmforum.mtnm.performance.PMDataIterator_IPOA
|
+--com.ericsson.poaImp.PMDataIterator_IPOAImp
org.tmforum.mtnm.performance.PMDataIterator_IOperations
public class PMDataIterator_IPOAImp

extends org.tmforum.mtnm.performance.PMDataIterator_IPOA
The Class PMDataIterator_IPOAImp.
Constructors
PMDataIterator_IPOAImp
public PMDataIterator_IPOAImp()
Methods
destroy
getLength
next_n
org.tmforum.mtnm.performance.PMDataList_THolder
pmDataList)
com.ericsson.poaImp
Class PMPIterator_IPOAImp
java.lang.Object
|
|
+--org.tmforum.mtnm.performance.PMPIterator_IPOA
|
+--com.ericsson.poaImp.PMPIterator_IPOAImp
org.tmforum.mtnm.performance.PMPIterator_IOperations
public class PMPIterator_IPOAImp

extends org.tmforum.mtnm.performance.PMPIterator_IPOA
The Class PMPIterator_IPOAImp.
Constructors
PMPIterator_IPOAImp
public PMPIterator_IPOAImp()
Methods
destroy
getLength
next_n
org.tmforum.mtnm.performance.PMPList_THolder pmpList)
com.ericsson.poaImp
Class PerformanceManagementMgr_IPOAImp
java.lang.Object
|
|
+--org.tmforum.mtnm.performance.PerformanceManagementMgr_IPOA
|
+--com.ericsson.poaImp.PerformanceManagementMgr_IPOAImp
org.tmforum.mtnm.performance.PerformanceManagementMgr_IOperations
public class PerformanceManagementMgr_IPOAImp

extends org.tmforum.mtnm.performance.PerformanceManagementMgr_IPOA
The Class PerformanceManagementMgr_IPOAImp.
Constructors
PerformanceManagementMgr_IPOAImp
public PerformanceManagementMgr_IPOAImp()
Methods
clearPMData
public void clearPMData(org.tmforum.mtnm.performance.PMTPSelect_T[]
pmTPSelectList,
org.tmforum.mtnm.performance.PMTPSelectList_THolder
failedTPSelectList)
createTCAParameterProfile
public void
createTCAParameterProfile(org.tmforum.mtnm.globaldefs.NameAndStringValue_T[]
managedElementName,
short layerRate,
boolean forceUniqueness,
org.tmforum.mtnm.performance.TCAParameter_T[] listOfTCAParameter,
org.tmforum.mtnm.performance.TCAParameterProfile_THolder tcaParameterProfile)
deleteTCAParameterProfile
public void
deleteTCAParameterProfile(org.tmforum.mtnm.globaldefs.NameAndStringValue_T[]
tcaParameterProfileName)
disablePMData
public void disablePMData(org.tmforum.mtnm.performance.PMTPSelect_T[]
pmTPSelectList,
failedTPSelectList)
disableTCA
public void disableTCA(org.tmforum.mtnm.performance.PMTPSelect_T[]
pmTPSelectList,
failedTPSelectList)
enablePMData
public void enablePMData(org.tmforum.mtnm.performance.PMTPSelect_T[]
pmTPSelectList,
failedTPSelectList)
enableTCA
public void enableTCA(org.tmforum.mtnm.performance.PMTPSelect_T[]
pmTPSelectList,
failedTPSelectList)
getAllCurrentPMData
public void getAllCurrentPMData(org.tmforum.mtnm.performance.PMTPSelect_T[]
pmTPSelectList,
java.lang.String[] pmParameters,
int howMany,
org.tmforum.mtnm.performance.PMDataList_THolder pmDataList,
org.tmforum.mtnm.performance.PMDataIterator_IHolder pmIt)
getAllPMPNames
public void getAllPMPNames(org.tmforum.mtnm.globaldefs.NameAndStringValue_T[]
tpOrMeName,
int howMany,
getAllPMPs
public void getAllPMPs(org.tmforum.mtnm.globaldefs.NameAndStringValue_T[]
tpOrMeName,
int howMany,
org.tmforum.mtnm.performance.PMPList_THolder pmpList,
org.tmforum.mtnm.performance.PMPIterator_IHolder pmpIt)
getAllTCAParameterProfileNames
public void
getAllTCAParameterProfileNames(org.tmforum.mtnm.globaldefs.NameAndStringValue_T[]
meName,
int howMany,
tcaParameterProfileNames,
getAllTCAParameterProfiles
public void
getAllTCAParameterProfiles(org.tmforum.mtnm.globaldefs.NameAndStringValue_T[]
meName,
int howMany,
org.tmforum.mtnm.performance.TCAParameterProfileList_THolder
tcaParameterProfileList,
org.tmforum.mtnm.performance.TCAParameterProfileIterator_IHolder
tcaParameterProfileIt)
getCapabilities
capabilities)
getHistoryPMData
public void getHistoryPMData(java.lang.String destination,
java.lang.String userName,
java.lang.String password,
org.tmforum.mtnm.performance.PMTPSelect_T[]
pmTPSelectList,
java.lang.String startTime,
java.lang.String endTime,
boolean forceUpload)
getHoldingTime
public void getHoldingTime(org.tmforum.mtnm.performance.HoldingTime_THolder
holdingTime)
getMEPMcapabilities
public void
getMEPMcapabilities(org.tmforum.mtnm.globaldefs.NameAndStringValue_T[] meName,
short layerRate,
org.tmforum.mtnm.performance.PMParameterList_THolder pmParameterList)
getProfileAssociatedTPs
public void
getProfileAssociatedTPs(org.tmforum.mtnm.globaldefs.NameAndStringValue_T[]
profileName,
int howMany,
org.tmforum.mtnm.globaldefs.NamingAttributesList_THolder tpNames,
getTCAParameterProfile
public void
getTCAParameterProfile(org.tmforum.mtnm.globaldefs.NameAndStringValue_T[]
tcaParameterProfileName,
org.tmforum.mtnm.performance.TCAParameterProfile_THolder tcaParameterProfile)
getTCATPParameter
public void
getTCATPParameter(org.tmforum.mtnm.globaldefs.NameAndStringValue_T[] tpName,
short layerRate,
org.tmforum.mtnm.performance.TCAParameters_THolder tcaParameter)
getTPHistoryPMData
public void getTPHistoryPMData(org.tmforum.mtnm.performance.PMTPSelect_T[]
pmTPSelectList,
java.lang.String startTime,
java.lang.String endTime,
int howMany,
org.tmforum.mtnm.performance.PMDataList_THolder
pmDataList,
org.tmforum.mtnm.performance.PMDataIterator_IHolder pmIt)
setAdditionalInfo
public void
objectName,
additionalInfo)
setNativeEMSName
public void
objectName,
setOwner
objectName,
setTCAParameterProfile
public void
setTCAParameterProfile(org.tmforum.mtnm.globaldefs.NameAndStringValue_T[]
tcaParameterProfileName,
org.tmforum.mtnm.performance.TCAParameter_T[] listOfTCAParameter,
int howMany,
org.tmforum.mtnm.performance.TCAParameterProfile_THolder tcaParameterProfile,
org.tmforum.mtnm.globaldefs.NamingAttributesList_THolder failedTPList,
setTCAParameterProfilePointer
public void
setTCAParameterProfilePointer(org.tmforum.mtnm.globaldefs.NameAndStringValue_T[]
tpName,
org.tmforum.mtnm.globaldefs.NameAndStringValue_T[] addTCAParameterProfile,
org.tmforum.mtnm.globaldefs.NameAndStringValue_T[] removeTCAParameterProfile)
setTCATPParameter
public void
setTCATPParameter(org.tmforum.mtnm.globaldefs.NameAndStringValue_T[] tpName,
org.tmforum.mtnm.performance.TCAParameters_THolder tcaParameters)
setUserLabel
objectName,
com.ericsson.poaImp
Class ProtectionGroupIterator_IPOAImp
java.lang.Object
|
|
+--org.tmforum.mtnm.protection.ProtectionGroupIterator_IPOA
|
+--com.ericsson.poaImp.ProtectionGroupIterator_IPOAImp
org.tmforum.mtnm.protection.ProtectionGroupIterator_IOperations
public class ProtectionGroupIterator_IPOAImp

extends org.tmforum.mtnm.protection.ProtectionGroupIterator_IPOA
The Class ProtectionGroupIterator_IPOAImp.
Constructors
ProtectionGroupIterator_IPOAImp
public ProtectionGroupIterator_IPOAImp()
Methods
destroy
getLength
next_n
org.tmforum.mtnm.protection.ProtectionGroupList_THolder
pgpList)
com.ericsson.poaImp
Class ProtectionMgr_IPOAImp
java.lang.Object
|
|
+--org.tmforum.mtnm.protection.ProtectionMgr_IPOA
|
+--com.ericsson.poaImp.ProtectionMgr_IPOAImp
org.tmforum.mtnm.protection.ProtectionMgr_IOperations
public class ProtectionMgr_IPOAImp

extends org.tmforum.mtnm.protection.ProtectionMgr_IPOA
The Class ProtectionMgr_IPOAImp.
Constructors
ProtectionMgr_IPOAImp
public ProtectionMgr_IPOAImp()
Methods
getAllEProtectionGroups
public void
getAllEProtectionGroups(org.tmforum.mtnm.globaldefs.NameAndStringValue_T[]
meName,
int howMany,
org.tmforum.mtnm.protection.EProtectionGroupList_THolder epgpList,
org.tmforum.mtnm.protection.EProtectionGroupIterator_IHolder epgpIt)
getAllNUTTPNames
public void
getAllNUTTPNames(org.tmforum.mtnm.globaldefs.NameAndStringValue_T[] pgName,
int howMany,
getAllPreemptibleTPNames
public void
getAllPreemptibleTPNames(org.tmforum.mtnm.globaldefs.NameAndStringValue_T[]
pgName,
int howMany,
getAllProtectedTPNames
public void
getAllProtectedTPNames(org.tmforum.mtnm.globaldefs.NameAndStringValue_T[]
pgName,
int howMany,
getAllProtectionGroups
public void
getAllProtectionGroups(org.tmforum.mtnm.globaldefs.NameAndStringValue_T[]
meName,
int howMany,
org.tmforum.mtnm.protection.ProtectionGroupList_THolder pgList,
org.tmforum.mtnm.protection.ProtectionGroupIterator_IHolder pgpIt)
getCapabilities
capabilities)
getContainingPGNames
public void
getContainingPGNames(org.tmforum.mtnm.globaldefs.NameAndStringValue_T[]
pTPName,
org.tmforum.mtnm.globaldefs.NamingAttributesList_THolder pgNameList)
getEProtectionGroup
public void
getEProtectionGroup(org.tmforum.mtnm.globaldefs.NameAndStringValue_T[]
ePGPname,
org.tmforum.mtnm.protection.EProtectionGroup_THolder eProtectionGroup)
getProtectionGroup
public void
getProtectionGroup(org.tmforum.mtnm.globaldefs.NameAndStringValue_T[] pgName,
org.tmforum.mtnm.protection.ProtectionGroup_THolder protectionGroup)
performProtectionCommand
public void
performProtectionCommand(org.tmforum.mtnm.protection.ProtectionCommand_T
protectionCommand,
org.tmforum.mtnm.globaldefs.NameAndStringValue_T[] reliableSinkCtpOrGroupName,
org.tmforum.mtnm.globaldefs.NameAndStringValue_T[] fromTp,
org.tmforum.mtnm.globaldefs.NameAndStringValue_T[] toTp,
org.tmforum.mtnm.protection.SwitchData_THolder switchData)
retrieveESwitchData
public void
retrieveESwitchData(org.tmforum.mtnm.globaldefs.NameAndStringValue_T[]
ePGPName,
org.tmforum.mtnm.protection.ESwitchDataList_THolder eSwitchDataList)
retrieveSwitchData
public void
retrieveSwitchData(org.tmforum.mtnm.globaldefs.NameAndStringValue_T[]
reliableSinkCtpOrGroupName,
org.tmforum.mtnm.protection.SwitchDataList_THolder switchData)
setAdditionalInfo
public void
objectName,
additionalInfo)
setNativeEMSName
public void
objectName,
setOwner
objectName,
setUserLabel
objectName,
com.ericsson.poaImp
Class SNCIterator_IPOAImp
java.lang.Object
|
|
+--org.tmforum.mtnm.subnetworkConnection.SNCIterator_IPOA
|
+--com.ericsson.poaImp.SNCIterator_IPOAImp
org.tmforum.mtnm.subnetworkConnection.SNCIterator_IOperations
public class SNCIterator_IPOAImp

extends org.tmforum.mtnm.subnetworkConnection.SNCIterator_IPOA
The Class SNCIterator_IPOAImp.
Constructors
SNCIterator_IPOAImp
public SNCIterator_IPOAImp()
Methods
destroy
getLength
next_n
sncList)
com.ericsson.poaImp
Class Session_IPOAImp
java.lang.Object
|
|
+--org.tmforum.mtnm.session.Session_IPOA
|
+--com.ericsson.poaImp.Session_IPOAImp
org.omg.CORBA.portable.InvokeHandler, org.tmforum.mtnm.session.Session_IOperations
public class Session_IPOAImp

extends org.tmforum.mtnm.session.Session_IPOA
The Class Session_IPOAImp.
Constructors
Session_IPOAImp
public Session_IPOAImp()
Methods
associatedSession
endSession
ping
public void ping()
com.ericsson.poaImp
Class SoftwareAndDataMgr_IPOAImp
java.lang.Object
|
|
+--org.tmforum.mtnm.softwareAndDataManager.SoftwareAndDataMgr_IPOA
|
+--com.ericsson.poaImp.SoftwareAndDataMgr_IPOAImp
org.tmforum.mtnm.softwareAndDataManager.SoftwareAndDataMgr_IOperations
public class SoftwareAndDataMgr_IPOAImp

extends org.tmforum.mtnm.softwareAndDataManager.SoftwareAndDataMgr_IPOA
The Class SoftwareAndDataMgr_IPOAImp.
Constructors
SoftwareAndDataMgr_IPOAImp
public SoftwareAndDataMgr_IPOAImp()
Methods
abortMEBackup
public void abortMEBackup(org.tmforum.mtnm.globaldefs.NameAndStringValue_T[]
managedElementName)
backupME
public void backupME(org.tmforum.mtnm.globaldefs.NameAndStringValue_T[]
managedElementName)
getBackupList
public void getBackupList(org.tmforum.mtnm.globaldefs.NameAndStringValue_T[][]
managedElementNameList,
int howMany,
org.tmforum.mtnm.softwareAndDataManager.BackupIdList_THolder backupList,
org.tmforum.mtnm.softwareAndDataManager.BackupIdIterator_IHolder backupIt)
getCapabilities
capabilities)
getMEBackupStatus
public void
getMEBackupStatus(org.tmforum.mtnm.globaldefs.NameAndStringValue_T[]
managedElementName,
org.tmforum.mtnm.softwareAndDataManager.BackupStatus_THolder backupStatus)
setAdditionalInfo
public void
objectName,
additionalInfo)
setNativeEMSName
public void
objectName,
setOwner
objectName,
setUserLabel
objectName,
com.ericsson.poaImp
Class SubnetworkIterator_IPOAImp
java.lang.Object
|
|
+--org.tmforum.mtnm.multiLayerSubnetwork.SubnetworkIterator_IPOA
|
+--com.ericsson.poaImp.SubnetworkIterator_IPOAImp
org.tmforum.mtnm.multiLayerSubnetwork.SubnetworkIterator_IOperations
public class SubnetworkIterator_IPOAImp

extends org.tmforum.mtnm.multiLayerSubnetwork.SubnetworkIterator_IPOA
The Class SubnetworkIterator_IPOAImp.
Constructors
SubnetworkIterator_IPOAImp
public SubnetworkIterator_IPOAImp(java.util.ArrayList list,
NBIImp nbi,
int size)
Instantiates a new subnetwork iterator_ ipoa imp.
Parameters:
list - the list
nbi - the nbi
size - the size
Methods
destroy
getLength
next_n
org.tmforum.mtnm.multiLayerSubnetwork.SubnetworkList_THolder subnetworkList)
com.ericsson.poaImp
Class TCAParameterProfileIterator_IPOAImp
java.lang.Object
|
|
+--org.tmforum.mtnm.performance.TCAParameterProfileIterator_IPOA
|
+--com.ericsson.poaImp.TCAParameterProfileIterator_IPOAImp
org.tmforum.mtnm.performance.TCAParameterProfileIterator_IOperations
public class TCAParameterProfileIterator_IPOAImp

extends org.tmforum.mtnm.performance.TCAParameterProfileIterator_IPOA
The Class TCAParameterProfileIterator_IPOAImp.
Constructors
TCAParameterProfileIterator_IPOAImp
public TCAParameterProfileIterator_IPOAImp()
Methods
destroy
getLength
next_n
org.tmforum.mtnm.performance.TCAParameterProfileList_THolder
tcaParameterProfileList)
com.ericsson.poaImp
Class TCProfileIterator_IPOAImp
java.lang.Object
|
|
+--org.tmforum.mtnm.trafficConditioningProfile.TCProfileIterator_IPOA
|
+--com.ericsson.poaImp.TCProfileIterator_IPOAImp
org.tmforum.mtnm.trafficConditioningProfile.TCProfileIterator_IOperations
public class TCProfileIterator_IPOAImp

extends org.tmforum.mtnm.trafficConditioningProfile.TCProfileIterator_IPOA
The Class TCProfileIterator_IPOAImp.
Constructors
TCProfileIterator_IPOAImp
public TCProfileIterator_IPOAImp()
Methods
destroy
getLength
next_n
org.tmforum.mtnm.trafficConditioningProfile.TCProfileList_THolder
tcProfileList)
com.ericsson.poaImp
Class TCProfileMgr_IPOAImp
java.lang.Object
|
|
+--org.tmforum.mtnm.trafficConditioningProfile.TCProfileMgr_IPOA
|
+--com.ericsson.poaImp.TCProfileMgr_IPOAImp
org.tmforum.mtnm.trafficConditioningProfile.TCProfileMgr_IOperations
public class TCProfileMgr_IPOAImp

extends org.tmforum.mtnm.trafficConditioningProfile.TCProfileMgr_IPOA
The Class TCProfileMgr_IPOAImp.
Constructors
TCProfileMgr_IPOAImp
public TCProfileMgr_IPOAImp()
Methods
createTCProfile
public void
createTCProfile(org.tmforum.mtnm.trafficConditioningProfile.TCProfileCreateData_T
newTCProfileCreateData,
org.tmforum.mtnm.trafficConditioningProfile.TCProfile_THolder newTCProfile)
deleteTCProfile
public void deleteTCProfile(org.tmforum.mtnm.globaldefs.NameAndStringValue_T[]
tcProfileName)
getAllTCProfiles
public void getAllTCProfiles(int howMany,
org.tmforum.mtnm.trafficConditioningProfile.TCProfileList_THolder
tcProfileList,
org.tmforum.mtnm.trafficConditioningProfile.TCProfileIterator_IHolder
tcProfileIt)
getCapabilities
capabilities)
getTCProfile
public void getTCProfile(org.tmforum.mtnm.globaldefs.NameAndStringValue_T[]
tcProfileName,
org.tmforum.mtnm.trafficConditioningProfile.TCProfile_THolder tcProfile)
getTCProfileAssociatedTPs
public void
getTCProfileAssociatedTPs(org.tmforum.mtnm.globaldefs.NameAndStringValue_T[]
tcProfileName,
int howMany,
modifyTCProfile
public void modifyTCProfile(org.tmforum.mtnm.globaldefs.NameAndStringValue_T[]
tcProfileName,
org.tmforum.mtnm.trafficConditioningProfile.TCProfileCreateData_T
tcProfileModifyData,
org.tmforum.mtnm.trafficConditioningProfile.TCProfile_THolder
modifiedTCProfile,
setAdditionalInfo
public void
objectName,
additionalInfo)
setNativeEMSName
public void
objectName,
setOwner
objectName,
setUserLabel
objectName,
com.ericsson.poaImp
Class TerminationPointIterator_IPOAImp
java.lang.Object
|
|
+--org.tmforum.mtnm.terminationPoint.TerminationPointIterator_IPOA
|
+--com.ericsson.poaImp.TerminationPointIterator_IPOAImp
org.tmforum.mtnm.terminationPoint.TerminationPointIterator_IOperations
public class TerminationPointIterator_IPOAImp

extends org.tmforum.mtnm.terminationPoint.TerminationPointIterator_IPOA
The Class TerminationPointIterator_IPOAImp.
Constructors
TerminationPointIterator_IPOAImp
public TerminationPointIterator_IPOAImp(java.util.ArrayList list,
NBIImp nbi,
int size)
Instantiates a new termination point iterator_ ipoa imp.
Parameters:
list - the list
nbi - the nbi
size - the size
Methods
destroy
getLength
next_n
com.ericsson.poaImp
Class TopologicalLinkIterator_IPOAImp
java.lang.Object
|
|
+--org.tmforum.mtnm.topologicalLink.TopologicalLinkIterator_IPOA
|
+--com.ericsson.poaImp.TopologicalLinkIterator_IPOAImp
org.tmforum.mtnm.topologicalLink.TopologicalLinkIterator_IOperations
public class TopologicalLinkIterator_IPOAImp

extends org.tmforum.mtnm.topologicalLink.TopologicalLinkIterator_IPOA
The Class TopologicalLinkIterator_IPOAImp.
Constructors
TopologicalLinkIterator_IPOAImp
public TopologicalLinkIterator_IPOAImp()
Methods
destroy
getLength
next_n
org.tmforum.mtnm.topologicalLink.TopologicalLinkList_THolder topoLinkList)
com.ericsson.poaImp
Class TrafficDescriptorIterator_IPOAImp
java.lang.Object
|
|
+--org.tmforum.mtnm.trafficDescriptor.TrafficDescriptorIterator_IPOA
|
+--com.ericsson.poaImp.TrafficDescriptorIterator_IPOAImp
org.tmforum.mtnm.trafficDescriptor.TrafficDescriptorIterator_IOperations
public class TrafficDescriptorIterator_IPOAImp

extends org.tmforum.mtnm.trafficDescriptor.TrafficDescriptorIterator_IPOA
The Class TrafficDescriptorIterator_IPOAImp.
Constructors
TrafficDescriptorIterator_IPOAImp
public TrafficDescriptorIterator_IPOAImp()
Methods
destroy
getLength
next_n
org.tmforum.mtnm.trafficDescriptor.TrafficDescriptorList_THolder
trafficDescList)
com.ericsson.poaImp
Class TrafficDescriptorMgr_IPOAImp
java.lang.Object
|
|
+--org.tmforum.mtnm.trafficDescriptor.TrafficDescriptorMgr_IPOA
|
+--com.ericsson.poaImp.TrafficDescriptorMgr_IPOAImp
org.tmforum.mtnm.trafficDescriptor.TrafficDescriptorMgr_IOperations
public class TrafficDescriptorMgr_IPOAImp

extends org.tmforum.mtnm.trafficDescriptor.TrafficDescriptorMgr_IPOA
The Class TrafficDescriptorMgr_IPOAImp.
Constructors
TrafficDescriptorMgr_IPOAImp
public TrafficDescriptorMgr_IPOAImp()
Methods
createTrafficDescriptor
public void
createTrafficDescriptor(org.tmforum.mtnm.trafficDescriptor.TDCreateData_T
newTDCreateData,
org.tmforum.mtnm.trafficDescriptor.TrafficDescriptor_THolder
newTrafficDescriptor)
deleteTrafficDescriptor
public void
deleteTrafficDescriptor(org.tmforum.mtnm.globaldefs.NameAndStringValue_T[]
descriptorName)
getAllTrafficDescriptorNames
public void getAllTrafficDescriptorNames(int howMany,
getAllTrafficDescriptors
public void getAllTrafficDescriptors(int howMany,
org.tmforum.mtnm.trafficDescriptor.TrafficDescriptorList_THolder
trafficDescList,
org.tmforum.mtnm.trafficDescriptor.TrafficDescriptorIterator_IHolder
trafficDescIt)
getAssociatedCTPs
public void
getAssociatedCTPs(org.tmforum.mtnm.globaldefs.NameAndStringValue_T[]
trafficDescriptorName,
int howMany,
getCapabilities
capabilities)
getTrafficDescriptor
public void
getTrafficDescriptor(org.tmforum.mtnm.globaldefs.NameAndStringValue_T[]
tdName,
org.tmforum.mtnm.trafficDescriptor.TrafficDescriptor_THolder td)
setAdditionalInfo
public void
objectName,
additionalInfo)
setNativeEMSName
public void
objectName,
setOwner
objectName,
setUserLabel
objectName,
com.ericsson.poaImp
Class TransmissionDescriptorIterator_IPOAImp
java.lang.Object
|
|
+--org.tmforum.mtnm.transmissionDescriptor.TransmissionDescriptorIterator_I
|
+--com.ericsson.poaImp.TransmissionDescriptorIterator_IPOAImp
org.tmforum.mtnm.transmissionDescriptor.TransmissionDescriptorIterator_IOperations

public class TransmissionDescriptorIterator_IPOAImp
extends org.tmforum.mtnm.transmissionDescriptor.TransmissionDescriptorIterator_IPOA
The Class TransmissionDescriptorIterator_IPOAImp.
Constructors
TransmissionDescriptorIterator_IPOAImp
public TransmissionDescriptorIterator_IPOAImp()
Methods
destroy
getLength
next_n
org.tmforum.mtnm.transmissionDescriptor.TransmissionDescriptorList_THolder
transmissionDescList)
com.ericsson.poaImp
Class TransmissionDescriptorMgr_IPOAImp
java.lang.Object
|
|
+--org.tmforum.mtnm.transmissionDescriptor.TransmissionDescriptorMgr_IPOA
|
+--com.ericsson.poaImp.TransmissionDescriptorMgr_IPOAImp
org.tmforum.mtnm.transmissionDescriptor.TransmissionDescriptorMgr_IOperations

public class TransmissionDescriptorMgr_IPOAImp
extends org.tmforum.mtnm.transmissionDescriptor.TransmissionDescriptorMgr_IPOA
The Class TransmissionDescriptorMgr_IPOAImp.
Constructors
TransmissionDescriptorMgr_IPOAImp
public TransmissionDescriptorMgr_IPOAImp()
Methods
createTransmissionDescriptor
public void
createTransmissionDescriptor(org.tmforum.mtnm.transmissionDescriptor.TMDCreateData_
newTMDCreateData,
org.tmforum.mtnm.transmissionDescriptor.TransmissionDescriptor_THolder
newTransmissionDescriptor)
deleteTransmissionDescriptor
public void
deleteTransmissionDescriptor(org.tmforum.mtnm.globaldefs.NameAndStringValue_T[]
transmissionDescriptorName)
getAllTransmissionDescriptorNames
public void getAllTransmissionDescriptorNames(int howMany,
getAllTransmissionDescriptors
public void getAllTransmissionDescriptors(int howMany,
org.tmforum.mtnm.transmissionDescriptor.TransmissionDescriptorList_THolder
transmissionDescList,
org.tmforum.mtnm.transmissionDescriptor.TransmissionDescriptorIterator_IHolder
transmissionDescIt)
getAssociatedTPs
public void
getAssociatedTPs(org.tmforum.mtnm.globaldefs.NameAndStringValue_T[]
transmissionDescriptorName,
int howMany,
getCapabilities
capabilities)
getTransmissionDescriptor
public void
getTransmissionDescriptor(org.tmforum.mtnm.globaldefs.NameAndStringValue_T[]
tmdName,
org.tmforum.mtnm.transmissionDescriptor.TransmissionDescriptor_THolder tmd)
modifyTransmissionDescriptor
public void
modifyTransmissionDescriptor(org.tmforum.mtnm.globaldefs.NameAndStringValue_T[]
tmdName,
org.tmforum.mtnm.transmissionDescriptor.TMDModifyData_T tmdModifyData,
org.tmforum.mtnm.transmissionDescriptor.TransmissionDescriptor_THolder
modifiedTransmissionDescriptor,
org.tmforum.mtnm.globaldefs.NamingAttributesList_THolder failedMEList,
org.tmforum.mtnm.globaldefs.NamingAttributesList_THolder failedTPsMFDsList,
errorReason)
setAdditionalInfo
public void
objectName,
additionalInfo)
setNativeEMSName
public void
objectName,
setOwner
objectName,
setTMDAssociation
public void
setTMDAssociation(org.tmforum.mtnm.globaldefs.NameAndStringValue_T[] tmdName,
org.tmforum.mtnm.transmissionDescriptor.TPorMFDorFDFr_THolder tPorMFDorFDFr)
setUserLabel
objectName,
validateTMDAssignmentToObject
public void
validateTMDAssignmentToObject(org.tmforum.mtnm.globaldefs.NameAndStringValue_T[]
objectName,
objectAssignmentState,
transmissionParams,
org.tmforum.mtnm.globaldefs.NVSList_THolder additionalTPInfo)
com.ericsson.poaImp
Class Version_IPOAImp
java.lang.Object
|
|
+--org.tmforum.mtnm.mtnmVersion.Version_IPOA
|
+--com.ericsson.poaImp.Version_IPOAImp
org.omg.CORBA.portable.InvokeHandler, org.tmforum.mtnm.mtnmVersion.Version_IOperations
public class Version_IPOAImp

extends org.tmforum.mtnm.mtnmVersion.Version_IPOA
This class implements part of the TMF814 SS 3.5.
Constructors
Version_IPOAImp
public Version_IPOAImp()
Methods
getVersion
public java.lang.String getVersion()
Returns the version of the Solution Set of the TMF idl-files upon which this interface is build.
Returns:
The version number of the Solution Set of TMF814.
INDEX
A C
abortMEBackup ... 330 cancel ... 59
acknowledgeAlarm ... 122 changedConf ... 61
acknowledgeAlarms ... 103 changing ... 135
acknowledgeAlarms ... 221 checkInteger ... 66
acknowledgeAlarms ... 241 checkShort ... 67
acknowledgeIndication ... 208 checkValidSNC ... 296
actionPerformed ... 12 clearDB ... 59
actionPerformed ... 13 clearPMData ... 317
actionPerformed ... 16 columnAdded ... 13
actionPerformed ... 18 columnMarginChanged ... 14
activateSNC ... 295 columnMoved ... 14
addConnections ... 295 columnRemoved ... 14
addRoute ... 295 columnSelectionChanged ... 14
addToCurrentNode ... 18 concat ... 51
alarmLossOccurred ... 314 connect ... 36
assignASAP ... 241 connect ... 70
assignCPTPsToMFD ... 262 countFiles ... 60
assignSignallingController ... 278 createAlarm ... 193
associateCPTPsWithFlowDomain ... 262 createAlarm ... 196
associatedSession ... 251 createAndActivateFDFr ... 262
associatedSession ... 314 createAndActivateSNC ... 296
associatedSession ... 329 createASAP ... 241
associateMFDsWithFlowDomain ... 262 createCTP ... 128
associateSession ... 251 createFlowDomain ... 263
AboutPanel ... 166 createFTP ... 263
AboutPanel ... 166 createGTP ... 286
AlarmAlarmPanel ... 190 createMFD ... 263
AlarmAlarmPanel ... 190 createModifiedSNC ... 296
AlarmAlarmPanel ... 191 createNT_AlarmEvent ... 216
AlarmAlarmPanel ... 192 createNT_Attribute_Value_Change ... 216
AlarmCreator ... 215 createNT_HeartBeatEvent ... 217
AlarmCreator ... 215 createNT_State_Change ... 217
AlarmTCAPanel ... 194 createNT_TCA ... 155
AlarmTCAPanel ... 195 createNT_TCAEvent ... 218
AlarmTCAPanel ... 196 createSNC ... 296
AlarmTypes ... 6 createTCAParameterProfile ... 318
AlarmTypes ... 6 createTCProfile ... 336
AllTests ... 116 createTopologicalLink ... 242
AllTests ... 116 createTPPool ... 297
ASAPIterator_IPOAImp ... 233 createTrafficDescriptor ... 341
ASAPIterator_IPOAImp ... 233 createTransmissionDescriptor ... 345
createTransmissionParameters ... 136
B CallAndTopLevelConnectionsAndSNCsIterator_IPOAIm
... 236
backupME ... 330 CallAndTopLevelConnectionsAndSNCsIterator_IPOAIm
BackupIdIterator_IPOAImp ... 234 ... 236
BackupIdIterator_IPOAImp ... 234 CallAndTopLevelConnectionsIterator_IPOAImp
... 237
... 237
CCIterator_IPOAImp ... 235
CCIterator_IPOAImp ... 235
Common_IPOAImp ... 238
Common_IPOAImp ... 238
Config ... 7
Config ... 7
Config ... 7
... 239
... 240
CustomTableCellRenderer ... 204
CustomTableCellRenderer ... 205 D
deactivateAndDeleteFDFr ... 264
deactivateAndDeleteSNC ... 297
deactivateSNC ... 297
deassignASAP ... 242
deassignSignallingController ... 278
deAssociateCPTPsFromFlowDomain ... 263
deAssociateMFDsFromFlowDomain ... 263
debug ... 103
debug ... 221
deleteAlarm ... 22
deleteAlarm ... 70
deleteAlarms ... 122
deleteASAP ... 242
deleteCTP ... 22
deleteCTP ... 71
deleteCTP ... 128
deleteEms ... 22
deleteEms ... 71
deleteEms ... 133
deleteFlowDomain ... 264
deleteFTP ... 264
deleteGTP ... 286
deleteME ... 23
deleteME ... 71
deleteME ... 141
deleteMFD ... 264
deleteMLSN ... 23
deleteMLSN ... 71
deleteMLSN ... 145
deletePTP ... 23
deletePTP ... 72
deletePTP ... 148
deleteSNC ... 297
deleteTCA ... 23
deleteTCA ... 72
deleteTCAParameterProfile ... 318
deleteTCAs ... 155
deleteTCProfile ... 336
deleteTL ... 24
deleteTL ... 72
deleteTL ... 158
deleteTopologicalLink ... 242
deleteTPPool ... 297
deleteTrafficDescriptor ... 342
deleteTransmissionDescriptor ... 345
destroy ... 233
destroy ... 234
destroy ... 235
destroy ... 236
destroy ... 237
destroy ... 240
destroy ... 249
destroy ... 257
destroy ... 259
destroy ... 260
destroy ... 261
destroy ... 270
destroy ... 274
destroy ... 275
destroy ... 276
destroy ... 277
destroy ... 285
destroy ... 313
destroy ... 315
destroy ... 316
destroy ... 323
destroy ... 328 G
destroy ... 333
destroy ... 334 getActive ... 103
destroy ... 335 getActive ... 221
destroy ... 338 getActiveAlarms ... 25
destroy ... 339 getActiveAlarms ... 73
destroy ... 340 getActiveMaintenanceOperations ... 283
destroy ... 344 getActiveTCAs ... 25
destroyGCT ... 271 getActiveTCAs ... 73
disablePMData ... 318 getAdditionalInfo ... 25
disableSignalling ... 278 getAdditionalInfo ... 73
disableTCA ... 318 getAdditionalInfo ... 103
disconnect ... 36 getAdditionalInfo ... 136
disconnect ... 72 getAdditionalInfo ... 221
DBI ... 70 getAlarm ... 25
Debugger ... 61 getAlarm ... 73
Debugger ... 61 getAlarm ... 122
DebugInterface ... 101 getAlarms ... 104
DynamicLoader ... 64 getAlarms ... 122
DynamicLoader ... 64 getAlarms ... 222
getAlarmTypes ... 6
getAllActiveAlarms ... 26
E getAllActiveAlarms ... 74
enablePMData ... 318 getAllActiveAlarms ... 123
enableSignalling ... 278 getAllActiveAlarms ... 286
enableTCA ... 319 getAllActiveAlarmsFiltered ... 26
endSession ... 251 getAllActiveAlarmsFiltered ... 74
endSession ... 314 getAllActiveTCAs ... 26
endSession ... 329 getAllActiveTCAs ... 74
establishCall ... 298 getAllActiveTCAs ... 156
eventIterators ... 220 getAllActiveTCAsFiltered ... 26
eventLossCleared ... 314 getAllActiveTCAsFiltered ... 74
eventLossOccurred ... 314 getAllAlarmParameterNames ... 27
extensionFinder ... 67 getAllAlarmParameterNames ... 75
EMSMgr_IPOAImp ... 240 getAllAlarmParameters ... 123
EMSMgr_IPOAImp ... 241 getAllAlarms ... 104
EMSPanel ... 167 getAllAlarms ... 222
EMSPanel ... 167 getAllASAPNames ... 243
EMSPanel ... 168 getAllASAPs ... 243
EmsSession_IPOAImp ... 250 getAllAssignableCPTPs ... 264
EmsSession_IPOAImp ... 251 getAllAssignedCPTPs ... 265
EmsSessionFactory_IPOAImp ... 249 getAllAssociatedMFDs ... 265
EmsSessionFactory_IPOAImp ... 250 getAllCallIdsWithSNPPOrTNAName ... 298
EProtectionGroupIterator_IPOAImp ... 248 getAllCallIdsWithTP ... 298
EProtectionGroupIterator_IPOAImp ... 249 getAllCallsAndTopLevelConnections ... 298
EquipmentInventoryMgr_IPOAImp ... 252 getAllCallsAndTopLevelConnectionsAndSNCs
EquipmentInventoryMgr_IPOAImp ... 253 ... 299
EquipmentOrHolderIterator_IPOAImp ... 257 getAllCallsAndTopLevelConnectionsAndSNCsWithME
EquipmentOrHolderIterator_IPOAImp ... 257 ... 299
EventIterator_IPOAImp ... 258 getAllCallsAndTopLevelConnectionsAndSNCsWithTP
EventIterator_IPOAImp ... 258 ... 299
getAllCallsAndTopLevelConnectionsWithME ...
F 299
getAllCPTPs ... 265
filterActionPerformed ... 14 getAllCrossConnections ... 286
fixLR ... 183 getAllCurrentPMData ... 319
fixLR ... 193 getAllEdgeMLSNPPLinks ... 300
fixLR ... 197 getAllEdgePointNames ... 300
FDFrIterator_IPOAImp ... 259 getAllEdgePoints ... 300
FDFrIterator_IPOAImp ... 259 getAllEMSAndMEActiveAlarms ... 243
FDIterator_IPOAImp ... 260 getAllEMSAndMEUnacknowledgedActiveAlarms
FDIterator_IPOAImp ... 260 ... 243
FlowDomainMgr_IPOAImp ... 261 getAllEMSSystemActiveAlarms ... 244
FlowDomainMgr_IPOAImp ... 261 getAllEMSSystemUnacknowledgedActiveAlarms
... 244
getAllEProtectionGroups ... 324
getAllEquipment ... 253
getAllEquipmentNames ... 253 getAllTCAParameters ... 156
getAllFDFrs ... 265 getAllTCProfiles ... 336
getAllFixedCrossConnections ... 287 getAllTL ... 105
getAllFixedSubnetworkConnectionNames ... getAllTL ... 222
300 getAllTopLevelSubnetworkLayerRates ... 105
getAllFixedSubnetworkConnectionNamesWithTP getAllTopLevelSubnetworkLayerRates ... 222
... 301 getAllTopLevelSubnetworkNames ... 246
getAllFixedSubnetworkConnections ... 301 getAllTopLevelSubnetworks ... 27
getAllFixedSubnetworkConnectionsWithTP ... getAllTopLevelSubnetworks ... 75
301 getAllTopLevelSubnetworks ... 105
getAllFlowDomains ... 265 getAllTopLevelSubnetworks ... 146
getAllFTPNames ... 287 getAllTopLevelSubnetworks ... 222
getAllFTPs ... 287 getAllTopLevelSubnetworks ... 246
getAllGTPNames ... 287 getAllTopLevelTopologicalLinkNames ... 246
getAllGTPs ... 288 getAllTopLevelTopologicalLinks ... 246
getAllInternalMLSNPPLinks ... 301 getAllTopologicalLinkNames ... 304
getAllManagedElementNames ... 288 getAllTopologicalLinks ... 28
getAllManagedElementNames ... 302 getAllTopologicalLinks ... 76
getAllManagedElements ... 27 getAllTopologicalLinks ... 159
getAllManagedElements ... 27 getAllTopologicalLinks ... 305
getAllManagedElements ... 75 getAllTopologicalLinksOfFD ... 266
getAllManagedElements ... 75 getAllTPPoolNames ... 304
getAllManagedElements ... 104 getAllTPPools ... 304
getAllManagedElements ... 104 getAllTrafficDescriptorNames ... 342
getAllManagedElements ... 142 getAllTrafficDescriptors ... 342
getAllManagedElements ... 142 getAllTransmissionDescriptorNames ... 345
getAllManagedElements ... 222 getAllTransmissionDescriptors ... 345
getAllManagedElements ... 222 getAllUnacknowledgedActiveAlarms ... 289
getAllManagedElements ... 288 getASAP ... 242
getAllManagedElements ... 302 getASAPAssociatedResourceNames ... 242
getAllMLRAs ... 244 getASAPbyResource ... 243
getAllMLSNPPLinks ... 244 getAssigningMFD ... 266
getAllMLSNPPLinks ... 302 getAssociatedCTPs ... 342
getAllMLSNPPLinksWithMLSNs ... 244 getAssociatedTP ... 305
getAllMLSNPPLinksWithTNAs ... 245 getAssociatedTPs ... 346
getAllMLSNPPLinksWithTP ... 245 getAssociatingFD ... 266
getAllMLSNPPs ... 245 getAvailableCapacity ... 278
getAllMLSNPPs ... 302 getBackupList ... 331
getAllMLSNPPsWithTNA ... 245 getBackupRoutes ... 305
getAllMLSNPPsWithTP ... 245 getCall ... 305
getAllNodes ... 105 getCallAndTopLevelConnections ... 305
getAllNodes ... 222 getCallAndTopLevelConnectionsAndSNCs ...
getAllNUTTPNames ... 325 306
getAllPMPNames ... 319 getCapabilities ... 238
getAllPMPs ... 319 getCapabilities ... 246
getAllPreemptibleTPNames ... 325 getCapabilities ... 254
getAllProtectedTPNames ... 325 getCapabilities ... 266
getAllProtectionGroups ... 325 getCapabilities ... 272
getAllPTPNames ... 288 getCapabilities ... 279
getAllPTPNamesWithoutFTPs ... 288 getCapabilities ... 281
getAllPTPs ... 289 getCapabilities ... 283
getAllPTPsWithoutFTPs ... 289 getCapabilities ... 289
getAllSubnetworkConnectionNames ... 303 getCapabilities ... 306
getAllSubnetworkConnectionNamesWithTP ... getCapabilities ... 320
303 getCapabilities ... 325
getAllSubnetworkConnections ... 303 getCapabilities ... 331
getAllSubnetworkConnectionsWithTP ... 303 getCapabilities ... 336
getAllSubordinateMLSNs ... 304 getCapabilities ... 342
getAllSubordinateRAidsWithConnection ... 304 getCapabilities ... 346
getAllSupportedMFDs ... 266 getChannel ... 223
getAllSupportedPTPNames ... 253 getClient ... 223
getAllSupportedPTPs ... 254 getColumnClass ... 162
getAllSupportingEquipment ... 254 getColumnNames ... 206
getAllSupportingEquipmentNames ... 254 getColumnNames ... 210
getAllTCAParameterNames ... 27 getConf ... 136
getAllTCAParameterNames ... 75 getConnectionsAndRouteDetails ... 306
getAllTCAParameterProfileNames ... 319 getContainedCurrentTPNames ... 28
getAllTCAParameterProfiles ... 320 getContainedCurrentTPNames ... 76
getContainedCurrentTPNames ... 106 getFDFr ... 267
getContainedCurrentTPNames ... 129 getFDFrRoute ... 267
getContainedCurrentTPNames ... 223 getFDFrsByUserLabel ... 267
getContainedCurrentTPNames ... 290 getFDFrsWithTP ... 267
getContainedCurrentTPs ... 29 getFilterData ... 209
getContainedCurrentTPs ... 77 getFlowDomain ... 267
getContainedCurrentTPs ... 106 getFlowDomainsByUserLabel ... 267
getContainedCurrentTPs ... 129 getGCTProfileInfo ... 272
getContainedCurrentTPs ... 223 getGroup ... 172
getContainedCurrentTPs ... 290 getGTP ... 292
getContainedEquipment ... 254 getHistoryPMData ... 320
getContainedInUseTPNames ... 29 getHoldingTime ... 320
getContainedInUseTPNames ... 77 getIntendedRoute ... 306
getContainedInUseTPNames ... 107 getInterfaceName ... 108
getContainedInUseTPNames ... 130 getInterfaceName ... 224
getContainedInUseTPNames ... 224 getLast ... 69
getContainedInUseTPNames ... 290 getLastSelected ... 152
getContainedInUseTPs ... 30 getLastSelectedLevel ... 152
getContainedInUseTPs ... 77 getLayerParameters ... 31
getContainedPotentialTPNames ... 30 getLayerRate ... 32
getContainedPotentialTPNames ... 130 getLength ... 233
getContainedPotentialTPs ... 31 getLength ... 236
getContainingGTP ... 291 getLength ... 260
getContainingPGNames ... 326 getLength ... 261
getContainingSubnetworkNames ... 291 getLength ... 271
getContainingTPNames ... 291 getLength ... 274
getContainingTPs ... 292 getLength ... 275
getController ... 212 getLength ... 276
getCTP ... 28 getLength ... 277
getCTPMenu ... 179 getLength ... 323
getCTPs ... 183 getLength ... 328
getCTPTable ... 180 getLength ... 333
getDatabaseStatus ... 136 getLength ... 334
getDebug ... 137 getLength ... 335
getDebugFile ... 8 getLength ... 338
getDebugFileMenu ... 172 getLength ... 339
getDebugLevel ... 8 getLength ... 340
getDepth ... 69 getLength ... 344
getEms ... 31 getList ... 69
getEms ... 79 getMain ... 172
getEms ... 108 getManagedElement ... 32
getEMS ... 246 getManagedElement ... 142
getEmsName ... 134 getManagedElement ... 225
getEMSName ... 31 getManagedElement ... 292
getEMSName ... 78 getManager ... 252
getEmsSession ... 250 getMCS ... 180
getEProtectionGroup ... 326 getMEBackupStatus ... 331
getEquipment ... 254 getMenu ... 180
getEventChannel ... 251 getMenu ... 206
getMenu ... 210 getSelectedTable ... 213
getMenuEMS ... 186 getServiceStatus ... 139
getMenuME ... 186 getSNC ... 307
getMenuML ... 186 getSNCsByUserLabel ... 307
getMEPMcapabilities ... 320 getSubnetwork ... 34
getMessages ... 62 getSubnetwork ... 82
getMeStatus ... 142 getSubnetwork ... 110
getMFD ... 268 getSubnetwork ... 146
getMLSNPP ... 281 getSubnetwork ... 226
getMLSNPPLink ... 306 getSubnodes ... 111
getMode ... 8 getSubnodes ... 226
getMode ... 209 getSubNodes ... 34
getModel ... 173 getSubNodes ... 81
getModel ... 206 getSubNodes ... 146
getModel ... 210 getSupportedEquipment ... 255
getModel ... 213 getSupportedEquipmentNames ... 255
getModelTreeSelection ... 173 getSupportedManagers ... 252
getMPS ... 180 getSupportedRates ... 34
getMTS ... 180 getSupportedRates ... 82
getMultiLayerSubnetwork ... 307 getSupportedRates ... 111
getNBI ... 137 getSupportedRates ... 139
getNBIs ... 138 getSupportedRates ... 226
getNodes ... 109 getSupportingEquipment ... 255
getNodes ... 225 getSupportingEquipmentNames ... 255
getNT_AlarmSortOrder ... 8 getTable ... 207
getNT_TCASortOrder ... 8 getTable ... 210
getObject ... 219 getTableCellRendererComponent ... 205
getObjectName ... 32 getTCA ... 35
getObjectName ... 138 getTCAParameterProfile ... 321
getObjectName ... 225 getTCAs ... 156
getObjectNameId ... 138 getTCATPParameter ... 321
getObjectNameId ... 139 getTCProfile ... 336
getObjectNameID ... 33 getTCProfileAssociatedTPs ... 336
getObjectNameID ... 80 getTL ... 111
getOrb ... 225 getTL ... 226
getPath ... 9 getTopLevelTopologicalLink ... 247
getPOA ... 225 getTopNode ... 111
getPotentialFixedCCs ... 292 getTopNode ... 226
getProfileAssociatedTPs ... 321 getTopologicalLink ... 35
getProtectionGroup ... 326 getTopologicalLink ... 82
getPTP ... 33 getTopologicalLink ... 159
getPTP ... 80 getTopologicalLink ... 308
getPTP ... 110 getTP ... 292
getPTP ... 149 getTPGroupingRelationships ... 308
getPTP ... 225 getTPHistoryPMData ... 321
getPTPNames ... 33 getTPPool ... 308
getPTPNames ... 81 getTrafficDescriptor ... 342
getPTPNames ... 149 getTransmissionDescriptor ... 346
getPTPs ... 34 getTransmissionParams ... 268
getPTPs ... 81 getTree ... 187
getPTPs ... 110 getTreeCellRendererComponent ... 185
getPTPs ... 149 getTreeModel ... 187
getPTPs ... 184 getTreeView ... 187
getPTPs ... 226 getVersion ... 250
getPTPTable ... 181 getVersion ... 348
getRootNode ... 186 getViewColumns ... 207
getRoute ... 307 getViewColumns ... 211
getRouteAndTopologicalLinks ... 307 getX733AdditionalInfo ... 35
getRTAMAlarm ... 213 getX733AdditionalInfo ... 83
getRTAMTCA ... 213 getX733AdditionalInfo ... 112
getRTAMView ... 173 getX733AdditionalInfo ... 123
getSelectedInTree ... 173 getX733AdditionalInfo ... 226
getSelectedMenu ... 213 getX733MonitoredAttribute ... 35
getSelectedNodeCount ... 187 getX733MonitoredAttribute ... 83
getSelectedNodes ... 187 getX733MonitoredAttribute ... 112
getSelectedPaths ... 152 getX733MonitoredAttribute ... 123
getX733MonitoredAttribute ... 226
GetterTester ... 117 M
GetterTester ... 117
GTPiterator_IPOAImp ... 270 main ... 5
GTPiterator_IPOAImp ... 270 main ... 60
GuiCutThroughMgr_IPOAImp ... 271 main ... 116
GuiCutThroughMgr_IPOAImp ... 271 main ... 229
managedElementIterators ... 220
modifyASAP ... 247
I modifyCall ... 308
init ... 214 modifyDiversityAndCorouting ... 309
isActive ... 37 modifyFDFr ... 268
isActive ... 83 modifyFlowDomain ... 268
isCellEditable ... 162 modifyGTP ... 292
InputChecker ... 66 modifyMFD ... 269
modifySignallingProtocolParameters ... 279
L modifySNC ... 309
modifyTCProfile ... 337
launchGCT ... 272 modifyTPPool ... 309
loadModules ... 65 modifyTransmissionDescriptor ... 346
mouseClicked ... 14
mouseClicked ... 16
mouseClicked ... 18
mouseClicked ... 189
mouseEntered ... 14
mouseEntered ... 17
mouseEntered ... 18
mouseEntered ... 189
mouseExited ... 15
mouseExited ... 17
mouseExited ... 19
mouseExited ... 189
mousePressed ... 15
mousePressed ... 17
mousePressed ... 19
mousePressed ... 189
mouseReleased ... 15
MainController ... 11
MainController ... 11
MaintenanceMgr_IPOAImp ... 282
MaintenanceMgr_IPOAImp ... 282
MainView ... 171
MainView ... 172
ManagedElementIterator_IPOAImp ... 284
ManagedElementIterator_IPOAImp ... 284
ManagedElementMgr_IPOAImp ... 285
ManagedElementMgr_IPOAImp ... 285
MEPanel ... 168
MEPanel ... 169
MEPanel ... 169
MFDFrIterator_IPOAImp ... 273
MFDFrIterator_IPOAImp ... 274
MFDIterator_IPOAImp ... 274
MFDIterator_IPOAImp ... 275
MLSNPanel ... 170
MLSNPanel ... 170
MLSNPanel ... 171
MLSNPPIterator_IPOAImp ... 275
MLSNPPIterator_IPOAImp ... 276
MLSNPPLinkIterator_IPOAImp ... 276
MLSNPPLinkIterator_IPOAImp ... 277
MLSNPPLinkMgr_IPOAImp ... 277
MLSNPPLinkMgr_IPOAImp ... 278
MLSNPPMgr_IPOAImp ... 280
MLSNPPMgr_IPOAImp ... 280
Model ... 120
Model ... 120 N
ModelAlarm ... 121
ModelAlarm ... 121 namingAttributesIterators ... 220
ModelCtp ... 127 newFilter ... 207
ModelCtp ... 127 newFilter ... 211
ModelEms ... 133 newFilter ... 214
ModelEms ... 133 next_n ... 233
ModelHelper ... 135 next_n ... 234
ModelHelper ... 135 next_n ... 235
ModelInit ... 140 next_n ... 237
ModelInit ... 141 next_n ... 238
ModelMe ... 141 next_n ... 240
ModelMe ... 141 next_n ... 249
ModelMlsn ... 145 next_n ... 258
ModelMlsn ... 145 next_n ... 259
ModelPtp ... 148 next_n ... 260
ModelPtp ... 148 next_n ... 261
ModelSelection ... 151 next_n ... 271
ModelSelection ... 152 next_n ... 274
ModelTca ... 153 next_n ... 275
ModelTca ... 154 next_n ... 276
ModelTl ... 158 next_n ... 277
ModelTl ... 158 next_n ... 285
MultiLayerSubnetworkMgr_IPOAImp ... 294 next_n ... 313
MultiLayerSubnetworkMgr_IPOAImp ... 295 next_n ... 315
MySQLConnector ... 20 next_n ... 316
MySQLDelete ... 21 next_n ... 333
MySQLDelete ... 22 next_n ... 334
MySQLGetters ... 24 next_n ... 335
MySQLGetters ... 24 next_n ... 339
MySQLInit ... 36 next_n ... 340
MySQLInit ... 36 next_n ... 341
MySQLSetters ... 37 next_n ... 344
MySQLSetters ... 38 notificate ... 112
MySQLTest ... 117 notificate ... 227
MySQLTest ... 117 nt_AlarmActionPerformed ... 15
MySQLUpdater ... 50 nt_TCAActionPerformed ... 15
MySQLUpdater ... 50 NameExtractor ... 218
MyTableModel ... 161 NameService ... 163
MyTableModel ... 162 NameService ... 163
MyTableModel ... 162 NamingAttributesIterator_IPOAImp ... 312
NamingAttributesIterator_IPOAImp ... 312
NBI ... 102
NBIImp ... 220
NBIImp ... 221
NmsSession_IPOAImp ... 313
NmsSession_IPOAImp ... 313
NotificationService ... 164
NotificationService ... 164
NTAlarmView ... 197
NTAlarmView ... 198
NTAlarmView ... 199
NTTCAView ... 200
NTTCAView ... 201
NTTCAView ... 202
P S
performMaintenanceOperation ... 283 sendAlarm ... 112
performProtectionCommand ... 326 sendAlarm ... 227
ping ... 252 sendAttributeChanged ... 113
ping ... 314 sendAttributeChanged ... 227
ping ... 329 sendHeartBeat ... 113
print ... 175 sendHeartBeat ... 227
printHashMap ... 139 sendStateChanged ... 114
printProperty ... 218 sendStateChanged ... 228
provisionEquipment ... 255 serviceAffecting ... 208
ParseStatusPanel ... 174 setActive ... 114
ParseStatusPanel ... 175 setActive ... 228
PerformanceManagementMgr_IPOAImp ... 317 setAdditionalInfo ... 38
PerformanceManagementMgr_IPOAImp ... 317 setAdditionalInfo ... 239
PMDataIterator_IPOAImp ... 315 setAdditionalInfo ... 247
PMDataIterator_IPOAImp ... 315 setAdditionalInfo ... 256
PMPIterator_IPOAImp ... 316 setAdditionalInfo ... 269
PMPIterator_IPOAImp ... 316 setAdditionalInfo ... 272
ProtectionGroupIterator_IPOAImp ... 323 setAdditionalInfo ... 279
ProtectionGroupIterator_IPOAImp ... 323 setAdditionalInfo ... 281
ProtectionMgr_IPOAImp ... 324 setAdditionalInfo ... 283
ProtectionMgr_IPOAImp ... 324 setAdditionalInfo ... 293
setAdditionalInfo ... 310
R setAdditionalInfo ... 321
setAdditionalInfo ... 327
releaseCall ... 309 setAdditionalInfo ... 331
removeConnections ... 310 setAdditionalInfo ... 337
removeCurrentNode ... 19 setAdditionalInfo ... 343
removeHardParentheses ... 68 setAdditionalInfo ... 346
removeParentheses ... 68 setAlarmReportingOff ... 256
removeRoute ... 310 setAlarmReportingOn ... 256
repaintStatus ... 176 setClient ... 228
reset ... 37 setColumnNames ... 207
reset ... 83 setColumnNames ... 211
reset ... 193 setCrossConnection ... 40
reset ... 197 setCrossConnection ... 85
reSetConfig ... 9 setCTP ... 39
resetDB ... 140 setCTP ... 84
retrieveESwitchData ... 326 setCtpModel ... 181
retrieveSwitchData ... 327 setDebugFile ... 9
run ... 60 setDebugger ... 140
run ... 163 setDebugLevel ... 9
run ... 164 setDebugToFile ... 62
run ... 227 setDebugToFile ... 102
RTAMAlarm ... 205 setDebugToScreen ... 62
RTAMAlarm ... 206 setDebugToScreen ... 102
RTAMController ... 13 setEMS ... 40
RTAMController ... 13 setEMS ... 85
RTAMFilter ... 208 setEMS ... 134
RTAMFilter ... 208 setGtpAlarmReportingOff ... 293
RTAMTCA ... 209 setGtpAlarmReportingOn ... 293
RTAMTCA ... 210 setHeartBeatMenu ... 188
RTAMView ... 212 setIntendedRoute ... 310
RTAMView ... 212 setLastSelected ... 153
setLayerParameters ... 41
setLayerParameters ... 86
setManagedElement ... 42
setMessages ... 62
setMode ... 9
setModel ... 114
setModel ... 193
setModel ... 197
setModel ... 200
setModel ... 203
setModel ... 228 setTopologicalLink ... 49
setMultiLayerSubnetwork ... 147 setTopologicalLink ... 93
setNativeEMSName ... 239 setTopologicalLink ... 160
setNativeEMSName ... 247 setTPData ... 294
setNativeEMSName ... 256 setup ... 7
setNativeEMSName ... 269 setUp ... 118
setNativeEMSName ... 273 setupNotificationRoute ... 115
setNativeEMSName ... 279 setupNotificationRoute ... 228
setNativeEMSName ... 281 setUserLabel ... 239
setNBI ... 247 setUserLabel ... 323
setNBIImp ... 250 setUserLabel ... 343
setNBIImp ... 252 setUserLabel ... 347
setNT_Alarm ... 43 setX733AdditionalInfo ... 49
setNT_Alarm ... 88 setX733MonitoredAttribute ... 50
setNT_ALARM ... 124 showAlarm ... 15
setNT_AlarmSortOrder ... 10 splitParentheses ... 68
setNT_TCA ... 45 subnetworkIterators ... 221
setNT_TCA ... 90 suite ... 116
setNT_TCASortOrder ... 10 swapSNC ... 311
setObjectName ... 46 switchRoute ... 312
setOwner ... 239 switchView ... 174
setOwner ... 248 switchView ... 214
setOwner ... 256 Session_IPOAImp ... 329
setOwner ... 269 Session_IPOAImp ... 329
setOwner ... 273 SNCIterator_IPOAImp ... 328
setOwner ... 279 SNCIterator_IPOAImp ... 328
setOwner ... 281 SoftwareAndDataMgr_IPOAImp ... 330
setOwner ... 284 SoftwareAndDataMgr_IPOAImp ... 330
setOwner ... 293 Splitter ... 67
setOwner ... 311 Start ... 5
setOwner ... 322 Start ... 5
setOwner ... 327 StatusPanel ... 175
setOwner ... 331 StatusPanel ... 176
setOwner ... 337 SubnetworkIterator_IPOAImp ... 332
setOwner ... 343 SubnetworkIterator_IPOAImp ... 332
setOwner ... 347
setPath ... 10
setPTP ... 47
setPTP ... 91
setPTP ... 150
setPtpModel ... 181
setRoutesAdminState ... 311
setSelectedInTree ... 173
setSelectedPaths ... 153
setServiceStatus ... 140
setSignallingProtocolAndParameters ... 279
setSupportedRates ... 47
setTCAParameterProfile ... 322
setTCAParameterProfilePointer ... 322
setTCATPParameter ... 322
setTemplate ... 194
setTMDAssociation ... 347
setTNANameForMLSNPP ... 282
setTNANameForMLSNPPLinkEnd ... 280
setTopLevelSubnetwork ... 48
setTopLevelSubnetwork ... 92
T U
tearDown ... 118 unacknowledgeAlarms ... 115
terminationPointIterators ... 221 unacknowledgeAlarms ... 228
testFilterCritical ... 118 unacknowledgeAlarms ... 248
testFilterLOS ... 118 unassignCPTPsFromMFD ... 270
testFilterWarning ... 118 unprovisionEquipment ... 257
testNoCorrectFilter ... 118 update ... 174
treeWidth ... 172 update ... 175
TCAParameterProfileIterator_IPOAImp ... 333 update ... 176
TCAParameterProfileIterator_IPOAImp ... 333 update ... 181
TCProfileIterator_IPOAImp ... 334 update ... 188
TCProfileIterator_IPOAImp ... 334 update ... 207
TCProfileMgr_IPOAImp ... 335 update ... 211
TCProfileMgr_IPOAImp ... 335 updateAlarm ... 126
TerminationPointIterator_IPOAImp ... 338 updateCTP ... 51
TerminationPointIterator_IPOAImp ... 338 updateCTP ... 94
TestStarter ... 229 updateCTP ... 132
TestStarter ... 229 updateEMS ... 52
TopoLinkPanel ... 182 updateEMS ... 95
TopologicalLinkIterator_IPOAImp ... 339 updateEMS ... 229
TopologicalLinkIterator_IPOAImp ... 339 updateManagedElement ... 52
TPController ... 16 updateManagedElement ... 95
TPController ... 16 updateManagedElement ... 144
TPPanel ... 176 updateMultiLayerSubnetwork ... 53
TPPanel ... 178 updateNTAlarm ... 54
TPView ... 179 updateNTAlarm ... 97
TPView ... 179 updateNTTCA ... 56
TrafficDescriptorIterator_IPOAImp ... 340 updateNTTCA ... 99
TrafficDescriptorIterator_IPOAImp ... 340 updateNTTCA ... 157
TrafficDescriptorMgr_IPOAImp ... 341 updatePTP ... 57
TrafficDescriptorMgr_IPOAImp ... 341 updatePTP ... 100
TransmissionDescriptorIterator_IPOAImp ... updatePTP ... 151
343 updateTopologicalLink ... 58
TransmissionDescriptorIterator_IPOAImp ... updateTopologicalLink ... 101
344 updateTopologicalLink ... 161
TransmissionDescriptorMgr_IPOAImp ... 344
TransmissionDescriptorMgr_IPOAImp ... 345 V
TreeController ... 17
TreeController ... 18 validateTMDAssignmentToObject ... 347
TreeNodeIconRenderer ... 184 valueChanged ... 17
TreeNodeIconRenderer ... 184 valueChanged ... 19
TreePathDivider ... 68 verifyTMDAssignment ... 294
TreeView ... 185 Version_IPOAImp ... 348
TreeView ... 186 Version_IPOAImp ... 348
W
windowActivated ... 12
windowClosed ... 12
windowClosing ... 12
windowDeactivated ... 12
windowDeiconified ... 12
windowIconified ... 12
windowOpened ... 12
write ... 63
write ... 102
X
XkcdPanel ... 188
XkcdPanel ... 188
XmlParser ... 58
XmlParser ... 59
XmlParser ... 59
Appendix E User Manual
Master thesis User Manual document for
Ericsson OSS Simulator
Ericsson Internal
USER MANUAL 1 (28)

2010-09-13 PA1
EOS User Manual
TMF814 Simulator
Louisa Luciani, Mikael Riedel

Ericsson Lindholmen
E-mail Louisa: louisa.luciani@ericsson.com

E-mail Mikael: mikael.riedel@ericsson.com
Ericsson Internal
USER MANUAL 2 (28)

2010-09-13 PA1
Contents
1 Introduction.......................................................................................... 4
1.1 Purpose.................................................................................... 4
1.2 Intended Audience and Reading Suggestions .......................... 4
1.3 Definitions and Abbreviations ................................................... 4
2 Overall Description .............................................................................. 6
2.1 Product Perspective ................................................................. 6
2.2 Operating Environment............................................................. 6
2.3 Design and Implementation Constraints ................................... 6
3 Overview of the system ....................................................................... 7
3.1 System components................................................................. 7
3.2 System dependencies .............................................................. 8
4 Installation............................................................................................ 9
4.1 Database.................................................................................. 9
4.2 ORB ....................................................................................... 12
4.3 EOS ....................................................................................... 13
5 Uninstall.............................................................................................. 14
5.1 Database................................................................................ 14
5.2 ORB ....................................................................................... 14
5.3 EOS ....................................................................................... 14
6 Update................................................................................................. 15
6.1 Database................................................................................ 15
6.2 ORB ....................................................................................... 15
6.3 EOS ....................................................................................... 15
7 Launching........................................................................................... 16
8 Adding objects ................................................................................... 17
8.1 EMS ....................................................................................... 17
8.2 MLSN ..................................................................................... 17
8.3 ME.......................................................................................... 17
8.4 PTP/FTP ................................................................................ 18
8.5 CTP........................................................................................ 18
8.6 TL........................................................................................... 18
8.7 Alarm...................................................................................... 19
8.8 TCA........................................................................................ 19
9 Removing objects .............................................................................. 20
9.1 EMS ....................................................................................... 20
9.2 MLSN ..................................................................................... 20
9.3 ME.......................................................................................... 20
9.4 PTP/FTP ................................................................................ 20
9.5 CTP........................................................................................ 20
9.6 TL........................................................................................... 21
9.7 Alarm...................................................................................... 21
9.8 TCA........................................................................................ 21
10 Updating objects................................................................................ 22
10.1 EMS ....................................................................................... 22
Ericsson Internal
USER MANUAL 3 (28)

2010-09-13 PA1
10.2 MLSN ..................................................................................... 22

10.3 ME.......................................................................................... 22
10.4 PTP/FTP ................................................................................ 22
10.5 CTP........................................................................................ 22
10.6 TL........................................................................................... 22
10.7 Alarm...................................................................................... 23
10.8 TCA........................................................................................ 23
11 NorthBound ........................................................................................ 24
11.1 Starting services..................................................................... 24
11.2 Connect.................................................................................. 24
12 Import data ......................................................................................... 25
12.1 Command-Line....................................................................... 25
12.2 Through EOS GUI .................................................................. 25
13 Layout ................................................................................................. 26
14 Debug.................................................................................................. 27
14.1 Levels..................................................................................... 27
14.2 Log to file................................................................................ 27
15 Database............................................................................................. 28
15.1 Backup ................................................................................... 28
15.2 Restore .................................................................................. 28
Ericsson Internal
USER MANUAL 4 (28)

2010-09-13 PA1
1 Introduction
1.1 Purpose
The purpose of this User Manual is to provide the user

of the TMF814 Simulator with all the needed
information to quickly and efficient setup and start
using the simulator. It will also give a good overview of
what the simulator are capable of doing. Under the
corresponding subheadings, an explanation of the
functionality will be provided, along with instructions
and is some cases also pictures describing how to
perform this functionality.
1.2 Intended Audience and Reading Suggestions
This document is mainly intended for Ericsson Solution

Integrator, Solution Architect and Support Engineers to
understand the functionality of the software. Begin with
the overview sections and proceed through the
sections that are most pertinent to you as a reader.
1.3 Definitions and Abbreviations
GUI Graphical User Interface
TMF TeleManagement Forum
MTNM Multi Technology Network Management
TMF814 Protocol using CORBA specialized for

MTNM communication.
CTP Contained Termination Point
PTP Physical Termination Point
FTP Floating Termination Point
TP Termination Point
TL Topological Link.
MLSN Multi Layer Sub Network
TCA Threshold Crossing Alert

Ericsson Internal
USER MANUAL 5 (28)

2010-09-13 PA1
ME Managed Element
EMS Element Management System

Ericsson Internal
USER MANUAL 6 (28)

2010-09-13 PA1
2 Overall Description
2.1 Product Perspective
The GSDC OSS-integrations team works with

customizations, integration services and solutions
design of Network Management Systems. One of
these systems is ServiceOn and often, a solution
specific script will be created or an adjustment in the
system will be made for the client. In order to verify the
expected outcome, tests need to be performed on a
physical network which is very expensive to have
solely for testing purposes. This often means that tests
are performed on-site at clients. The objective of this
project is to create a standalone virtual network
simulator that communicates northbound over
TMF814. This product will simulate an optical network
that can be interacted with through a GUI as well as
through TMF814. The product is intended to be used
for testing purposes, and will provide a way to test
integrations in-house.
2.2 Operating Environment
The typical workstations the GSDC OSS Integration has are

normal laptops. All the laptops have Operating system Windows
Vista, this was the working environment and also the aim for
simulator, although the simulator are platform independent. The
laptop will typically have one or two gigabyte primary memory and
a dual core processor with at least 1.5 GHz capacity.
2.3 Design and Implementation Constraints
The simulator and all the plug-ins are written in Java. This will run
on all the computers used by GSDC Integrations and make it
possible to continue developing the simulator by GSDC personal
even after this project has ended.
An open source database will be used to handle the possible big

amount of data. The choice has fallen on MySQL because its free,
works well with java and makes the setup on each computer
simple.
Ericsson Internal
USER MANUAL 7 (28)

2010-09-13 PA1
3 Overview of the system

The program is built according to the Model-View-Control
architecture (MVC). The model contains the network data of the
simulated OSS and encapsulates an internal database. The view
displays all the information in the model, showing network
elements, their correlation to each other and specific information
about each network element. The controller receives input and
makes calls to the model. Because the controller handles all the
logic, which is preferably kept modular, it will consist of multiple
classes. A main controller will for instance handle general logic
such as the menu system, while specific windows are able to
communicate with their own controller class. Multiple northbound
interfaces are able to be loaded at startup, given that they follow
the given NBI.
3.1 System components
GUI
Interface
Database
TMF814 implementation of NBI
Figure 1, GUI main parts

Ericsson Internal
USER MANUAL 8 (28)

2010-09-13 PA1
3.2 System dependencies
The program is divided into the components above, where the

model is the central part. A graphical user interface that
manipulates the model through views and controllers exists locally.
The model can also interacted with through the northbound
interface. The local GUI and the NBI should have the same
functionality, though there might be some limitations in the NBI
depending on the choice of protocol. If a new NBI is added to the
simulator, functionality might have to be added to the GUI
accordingly. The data in the database can be manipulated through
either the GUI or the NBI.
Ericsson Internal
USER MANUAL 9 (28)

2010-09-13 PA1
4 Installation
To install and use this simulator three different parts most be
installed on the system. The first two parts have to be installed
before the last part.
4.1 Database
The simulator has support for MySQL database. MySQL version 5

or higher is required.
To install MySQL download the binary file, i.e. mysql-5.1.45-

win32.msi.
For the latest version check
http://www.mysql.com/downloads/mysql/
Follow the instructions in the installation-guide, remember your

root-password, this is needed when you need to do any big
changes to your MySQL-installation.
Choose to configure the database. If you want to register leave the

registration box checked, otherwise uncheck this option.
When the database is configured correctly and is up and running

open the MySQL Command-Line client from the start menu. Use
your root password to login.
When that is finish run this command to create a user for the
simulator:
-> GRANT ALL ON eosdb.* TO 'eos@'localhost' IDENTIFIED BY

'pass';
Also run the command below to verify that the needed access has
been assigned:
Ericsson Internal
USER MANUAL 10 (28)

2010-09-13 PA1
-> show grants for 'eos'@'localhost';

+---------------------------------------------------------------------------------------
---------------------+
| Grants for eos@localhost |
+---------------------------------------------------------------------------------------
---------------------+
| GRANT USAGE ON *.* TO 'eos'@'localhost' IDENTIFIED BY
PASSWORD
'*196BDEDE2AE4F84CA44C47D54D78478C7E2BD7B7' |
| GRANT ALL PRIVILEGES ON `eosdb`.* TO 'eos'@'localhost'
|
+---------------------------------------------------------------------------------------
---------------------+
2 rows in set (0.00 sec)
The important thing in the second result is that it should say

GRANT ALL for eosdb.*. This means that the user is created in a
correct way and the database is now ready to be used.
After point 4.2, when the simulator has been run with the flag
-install, use these commands in the MySQL CL to verify the
structure of the database:
-> use eosdb;
-> show tables;
The result should look like this:

Ericsson Internal
USER MANUAL 11 (28)

2010-09-13 PA1
+------------------------+
| Tables_in_eosdb |
+------------------------+
| additionalinfo |
| ccurrenttp |
| crossconnection |
| ctp |
| ems |
| layerparameters |
| layerrate |
| managedelement |
| nt_alarm |
| nt_tca |
| objectname |
| ptp |
| severity |
| supportedrate |
| toplevelsubnetwork |
| topologicallink |
| x733additionalinfo |
| x733monitoredattribute |
+------------------------+
18 rows in set (0.07 sec)

Ericsson Internal
USER MANUAL 12 (28)

2010-09-13 PA1
4.2 ORB
All the packages needed to get a working ORB could be found

inside OpenORB.zip.
Extract content of zip to i.e. c:\OpenORB\
It should now contain the following folders:

- EvaluatorUtility
- NamingService
- NotificationService
- OpenORB
- PersistentStateService
- tools
- TransactionService
These 7 packages could also be downloaded from OpenORBs

official homepage:
http://openorb.sourceforge.net/downloads.html
Note that the latest version are hosted on another link, that could
be found on the above page:
http://sourceforge.net/projects/openorb/files/
When the package are unpacked in i.e. c:\OpenORB\ it is time to

set some environment variables.
To set an environment variable in Vista do this:
- Open start menu
- Right-click on computer, choose Properties.
- Choose Advanced System Settings, click continue on

the UAC.
- Click on Environment Variables.
- Under System variables, click on new to create a

new vaiable.
There are two variables needed, the first one is JAVA_HOME

which should point to the folder where your java installation is.
Inside this path you should see bin folder.
One example of how the path could look:
C:\Program Files\Java\jdk1.6.0_18
Ericsson Internal
USER MANUAL 13 (28)

2010-09-13 PA1
If you already have a path for the JAVA_HOME variable then you
dont need to do this.
The second variable that is required is the TCOO_HOME variable.

This one should point to the OpenORB installation, that is to the
folder that the content of the zip file is extracted, i.e. c:\OpenORB\
Now all files needed by the ORB are installed. Only one thing
remains, that is to tell your java-installation to use OpenORB as
ORB for CORBA connections instead of the internal, not fully
developed ORB. This is done by running a simple script.
- Open CMD.
- Move to the ORB installation:

i.e. cd c:\OpenORB\
- Execute this command:

java jar .\OpenOrb\lib\openorb_orb-1.4.0.jar
This now creates a file named orb.properties inside the root of your
java installation. If this file now exists the ORB is correctly installed
and ready to use by any Java application.
4.3 EOS
Put the downloaded eos_X.X.jar in a folder on a path where you

wish to have EOS installed.
Open cmd and move to the location of the jar file.
Run this command:
Java jar eos_X.X.jar install
X.X has to be changed to the version corresponding to the jar file.
Two files and a folder will be added to the path of the EOS jar file.
EOS is now ready to be used.

Ericsson Internal
USER MANUAL 14 (28)

2010-09-13 PA1
5 Uninstall
5.1 Database
MySQL has a built in uninstaller that can be used if the database

should be uninstalled.
If problems occur and a removal of the database seems like the

only option it is important to make sure that all files and all
configurations are removed before the database is reinstalled.
5.2 ORB
To completely remove the OpenORB installation from your

computer there are some steps that has to be done.
Remove the folder where all the files are.
Remove the environment variable TCOO_HOME.
Remove the orb.properties from JAVA_HOME
5.3 EOS
Since this simulator doesnt really change any system setting the
only thing needed is to remove the file that has been extracted. If
everything is stored in one specific folder, i.e. c:\eos\ and no other
program are installed there, then the whole folder could be
removed to the trash-bin.
Ericsson Internal
USER MANUAL 15 (28)

2010-09-13 PA1
6 Update
Updating of the software is something that might have to be done
from time to time. The part that will be updated most is EOS.
6.1 Database
If the change-log for EOS tells anything about updating the

database program then this should be done by removing the
installation and then installing the new one. Remember to grant
access for the new user as in the installation part. Also run the
simulator with the install flag to create the needed structure
inside the database.
6.2 ORB
The ORB hasnt been changed very much the last couple of
years, so a change here isnt very likely. If something should be
updated then just exchange the packages inside TCOO_HOME.
6.3 EOS
If it is only a minor update, then its enough to just replace the

eos_X.X.jar file with the newer one. However if the changes are
bigger, i.e. if something is changed on the northbound interface
then the simulator has to be started with the install flag first:
Java jar eos_X.X.jar install
(X.X is the version of your downloaded file)

Ericsson Internal
USER MANUAL 16 (28)

2010-09-13 PA1
7 Launching
EOS could be launched in different ways. The simplest way after
installation is to use the eos.bat file. This is just a batch file
containing the needed information.
An alternative way is to start EOS through the command-line. EOS

is started as a normal java program inside a jar-file. Change the
directory in cmd to where the simulator is located with the cd
command. Then use:
Java jar eos.jar

for launching the program in normal mode
Java jar eos.jar install

to extract all the needed files and prepare the simulator to run in
normal mode.
Java jar eos.jar parse

to enter parsing mode. This is a command-line interface to parse
XML-files produced by the Script Client.
Ericsson Internal
USER MANUAL 17 (28)

2010-09-13 PA1
8 Adding objects
This section describes how to add different objects from the GUI.
8.1 EMS
EMS is the system that should be simulated, it could also be seen

as an NMS, but under this simulator both goes under EMS. They
contain the same information, and since the simulator operates
over both management layers and have the functionality of both of
them, they go under the same name.
To add an EMS to an empty system just right-click in the tree-

window and choose new EMS. In the panel that pops up fill in at
least name. The other fields are optional.
This is the only way to create an EMS from the GUI.
8.2 MLSN
MLSN are subnets for being able to manage a large amount of

MEs. The can only be added in the left tree and having created the
EMS first is a requirement.
Right-click somewhere in the white area or on the EMS to bring up

the menu for EMS. Click on Create MultiLayerSubnetwork.
In the popup only Subnet is required to be filled, this name has to
be unique on the EMS. Other fields are optional. LayerRate
requires a short, and will automatically fill in the name of the layer
if it is predefined. The database contains 306 predefined names.
Names of layers that are not predefined will only show as LR, over
the protocol only the short is sent so the name is only for making it
easier to see exactly which layer it is.
8.3 ME
Managed Elements are the lowest level in the tree to the left. They
are also the nodes in the MAP-view. MEs could be created from
the tree by right-clicking on the specific MLSN that is should be
part of and choose Create ManagedElement.
MEs could also be created from the MAP-view by changing to

editing mode in the map menu and then clicking somewhere on
the graph where no node already are. If the node is created from
the map, it has to be put into one of the available MLSN.
Ericsson Internal
USER MANUAL 18 (28)

2010-09-13 PA1
The name of the ME has to be unique on EMS level, which means

that its not allowed to have to MEs with the same name but in
different subnets.
8.4 PTP/FTP
The highest level of TerminationPoints. They could contain the

exact same data and are only differed by the type ptp or ftp. They
are created on a ME and at the moment this could only be done
from the tree to the left.
A ptp/ftp is made unique by the EMS, ME and the type-name tuple.
The fields for Traffic Descriptor is not used by Ericsson at the

moment, but the TMF814 protocol still allows this information.
If Transmission Parameters should be added it should be in the

form of a short in the first field describing which layer rate, a string
for name in the middle field and then an optional filed for value.
The combination of these values has to be unique.
When a ptp or ftp has been added it can be found under TP as

main-view.
8.5 CTP
A ctp is a contained termination-point that has to have a parent TP.

This could be another ctp or in the end a ftp or ptp. The
combination of EMS, ME, parent and ctp-name makes the ctp
unique.
Ctps are added in the TP main-view by right-clicking on an ftp or

ptp and choosing Create CTP. If the ctp is nested it should hold
all the ctps in the ctp-name. ctp1/ctp2/ctp3.
The information stored for ctps doesnt differ from ptps or ftps.
8.6 TL
Topological Links can only be added and viewed from the MAP-
view. By choosing the editing mode in the menu and left-clicking
on one node in the graph and dragging to another. If two nodes
are successfully selected a popup window will appear with the
information that could be stored on each TL. The name of the TL
has to be unique on the EMS.
Ericsson Internal
USER MANUAL 19 (28)

2010-09-13 PA1
8.7 Alarm
Alarms can be added from all the objects that can through alarms
just by right-clicking on them and choosing Create Alarm. There
are not a name for each alarm that makes it unique but instead the
combination of ObjectName, LayerRate, ProbableCause and
ProbableCauseQualifier. No values are needed to be filled in, as
long as the alarm is unique according to previous mentioned fields.
8.8 TCA
Resembles alarms in that way that they can be added from the
same points. From the menus just choose Create TCA instead of
alarm. A TCA is made unique by
Ericsson Internal
USER MANUAL 20 (28)

2010-09-13 PA1
9 Removing objects
By removing an object it will be removed from the database. This
means that it cant be undone. The simulator do not yet warn about
this everywhere, so keep it in mind, and do not just click for the fun
of it.
9.1 EMS
Removing the ems, that is removing all the information that is

simulated could be done in different ways. The first way is from the
menu -> File -> New Project. This will erase everything and give
you the opportunity to start from scratch. The database could also
be wiped clean, which means that all the information will
disappear. This is done from the menu -> Database -> Clear.
None of them warns at the moment and all data will be lost.
9.2 MLSN
MLSN could be removed by right-clicking on them in the left tree.
Removing a subnet will remove everything that is underneath the

subnet, which is MEs, TPs, TL connected to any ME in the subnet
and of course all the information about the subnet itself. Removing
a MLSN will however warn you about what the consequences are.
9.3 ME
ME could be removed by either right-clicking in the MAP-view on a

node and choose Delete Vertex or just by right-clicking in the tree
structure on the desired ME and choose Delete
ManagedElement.
Trying to delete a ME will warn the user.
9.4 PTP/FTP
PTPs and FTPs are removed from the table in TP-view by right-
clicking on the and choosing Remove TP. Warning will be
displayed.
9.5 CTP
CTPs are removed just as PTPs and FTPs.

Ericsson Internal
USER MANUAL 21 (28)

2010-09-13 PA1
9.6 TL
Topological Links can only be removed from the MAP-view, this

because this is the only view in the GUI where they are displayed.
By right-clicking on the link and choosing Delete Edge XX.
Warning will be displayed.
9.7 Alarm
Alarms can be deleted from the Real Time Alarm Monitor view. By
right-clicking on the alarm or alarms and choosing Delete selected
alarms. Many alarms can be deleted at ones. This is done without
any waring.
9.8 TCA
TCAs are deleted in the same way as alarms.

Ericsson Internal
USER MANUAL 22 (28)

2010-09-13 PA1
10 Updating objects
All objects found by the GUI are easy to update. This means that
to simulate two almost identical situations any of the value could
easily be change for the second run and you dont need to set up
everything from scratch again.
10.1 EMS
Just right-click on the EMS or somewhere where no objects are in

the tree view. In the menu choose to show EMS info. The same
window for create the EMS is showed, but the bottom right button
now says update. Change the values that you want to change and
then click update. The information will be stored in the database
directly.
10.2 MLSN
Right-click on the MLSN in the tree-view. Choose Subnetwork

info. The rest is done exactly as in the EMS case.
10.3 ME
Right-click on the ME in the tree-view. Choose ManagedElement

info. The rest is done exactly as in the EMS case.
10.4 PTP/FTP
Right-click on the PTP/FTP in the TP main view. Choose TP info.

The rest is done exactly as in the EMS case.
10.5 CTP
Right-click on the CTP in the TP main view. Choose CTP info.

The rest is done exactly as in the EMS case.
10.6 TL
Right-click on the link between two MEs in the map main view.
Choose TopologicalLink info. The rest is done exactly as in the
EMS case.
Ericsson Internal
USER MANUAL 23 (28)

2010-09-13 PA1
10.7 Alarm
Double-click on an alarm in the Real Time Alarm Monitor, or right-

click and choose Alarm info. The rest is done in the same way as
the EMS case.
10.8 TCA
This is done exactly as in the alarm case, but for the table of
TCAs.
Ericsson Internal
USER MANUAL 24 (28)

2010-09-13 PA1
11 NorthBound
To be able to use TMF814 the NameService and the
NotificationService has to be running. The services are normally
started by running two scripts, but EOS gives the possibility to
interact with the service from the GUI instead.
11.1 Starting services
To start the two services needed for the CORBA connection

choose Services in the menu and click on start. After a few
seconds the menu-dropdown will disappear and the status icon in
the bottom right corner will turn green (this is the icon with S for
Services). The service runs as a separate Java-thread and only
on instance of EOS on each computer can start this service,
otherwise you will get two services binding to the same port, port
21234 for NameSerivce. This is not allowed by the Java Virtual
Machine so the second EOS instance will be closed. Problems
with connecting could have to do with that this port is already
occupied. Make sure it isnt if having problem.
11.2 Connect
To connect the actual northbound interface the services has to be

running, otherwise a message will be displayed in the log-window
depending on debug-settings.
One other requirement is that at least one implementation of the

interface has to be found in the NBI directory. If no implementation
could be found at startup, the NBI option in the menu will not be
displayed. If one or more implementations are present they will be
listed under the NBI menu.
To connect to a specific interface just hover the interface and

select to connect. Another way to connect interfaces is to use the
connect all option. This will connect all of the found
implementation one after one.
When one or more implementations are connected, that is has a

binding in the NameService and are ready to be used the status-
icon in the bottom right corner will become green. The icon looks
like an arrow pointing upwards for Northbound communication.
Ericsson Internal
USER MANUAL 25 (28)

2010-09-13 PA1
12 Import data
To be able to use real and accurate data it is possible to import
data directly to the database through a parser that uses our
database interface. This parser is just in beta version and some
error-messages might not show enough information. The parser
uses the information from the Script Client. The Script Client has
some known problem to produce xml-files for some types, i.e.
Alarms. Importing data will be done through a TMF-agent in the
future, but as of now the parser is the only way to import much
data.
12.1 Command-Line
The command-line parser can be used to import specific parts of

the data, or all data depending on the choices the user does. To
start the cl-parser just add a flag to the the launch of the eos.jar
file:
Java jar eos.jar parse
This will not start EOS in normal mode but in the cl-parse mode.
Just follow the instructions inside the parser.
When the parsing is done just run the simulator again, this time
without the flag parse.
12.2 Through EOS GUI
For convenience, it is also possible to import data from the Script

Client from the GUI when running the simulator in normal mode.
This is an easy to use extension of the parser that only imports as
much as possible from a given directory (where the xml-files are).
This feature requires that the database is empty before the
parsing begins. Clearing the database could also be done from
the EOS GUI.
The database features could be found under the menu Database.

Ericsson Internal
USER MANUAL 26 (28)

2010-09-13 PA1
13 Layout
EOS has to some extent the possibility to save layouts. By this we
mean to save the appearance of the program. The layout could be
restored to a default state. To save and restore the layout use the
menu options for Save configuration and Reset configuration in
the File menu.
The parts of the layout that will be stored by using the save option
is which main-view should be the starting view (it takes the
current), in which order should the columns appear in Alarm and
TCA tables and what should the debug level be.
The settings are stored in the config.conf file that could be found
in the root, where eos.jar is located.
Ericsson Internal
USER MANUAL 27 (28)

2010-09-13 PA1
14 Debug
Debugging is mainly for showing what is happening, a very good
tool when something goes wrong. In the menu under Debug it is
possible to set which level of debugging should be applied. The
debug-messages are show in the status window in the bottom.
14.1 Levels
The levels follows the following pattern:
1 = All
2 = Finer
3 = Fine
4 = Config
5 = Info
6 = Severe
Off = Off
Depending on how much information the user whishes to see this

level could be adjusted between these values.
14.2 Log to file
Logging to file is a feature to log all messages to a file called

debugEOS.log. If another name for the file is wanted, this has to
be changed in the config.conf file. The file will be found in the root,
where eos.jar can be found.
Ericsson Internal
USER MANUAL 28 (28)

2010-09-13 PA1
15 Database
MySQL has some tools, that isnt developed by this project and
are not normally used by the simulator, but that could be very
good to know about. I.e. it is very easy to backup and restore the
entire database with one of the tools. By taking a backup of the
entire database all the needed information about a scenario are
stored to a file. This file could be restored on another computer or
later in time on the same computer to restore the same network
setup.
15.1 Backup
To backup the database a tool called MySQLDump can be used.

This program makes a dump of the database, without any special
flags it dumps both structure and contents of the database.
The syntax for using MySQLDump is:
mysqldump -u root -p -h localhost eosdb > eosdb.sql
This requires that MySQL bin-folder is part of the systempath,

otherwise the absolute path has to be used to run MySQLDump.
C:\prog.SQL\bin\mysqldump -u root -p -h localhost eosdb >

eosdb.sql
The result will be a single file, named eosdb.sql containing all the
information in the database.
15.2 Restore
If you have a backup-file from an EOS-database it could be

imported to restore to that exact state. This is done by simply
running this command:
mysql -h localhost -u root -p eosdb < eosdb.sql
Note that this uses the ordinary MySQL and not MySQLDump.
Good to know is also that this will erase everything in the
database right now, so if something important is in the database
just take a backup first, to another filename than the one that you
want to load.

TMF814 Network Simulator

Uploaded by

Copyright:

Available Formats

TMF814 Network Simulator

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

TMF814 Network Simulator

Uploaded by

Copyright:

Available Formats

TMF814 Network Simulator

A standalone, Java-based network simulator for testing

Chalmers University of Technology

TMF814 Network Simulator

LOUISA LUCIANI, September 2010.

Examiner: Sven-Arne Andreasson

Chalmers University of Technology

Department of Computer Science and Engineering

CORBA - Common Object Request Broker Architecture.

DBI - Database Interface.

EMS - Element Management System.

FCAPS - Fault, Configuration, Accounting, Performance, Security.

ME - Managed Element, network element in TMF814.

MLSN - MultiLayerSubnetwork, subnetworks in TMF814.

MVC - Model View Controller.

NBI - North Bound Interface.

NMS - Network Management System.

Northbound - Communication to overlaying systems.

OMG - Object Management Group, founder of CORBA.

OSS - Operations Support System.

SBI - South Bound Interface.

Southbound - Communication to underlying systems or equipment.

TL - Topological Link, a network link.

TMF - TeleManagement Forum.

1.2 Problem description . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

2.1 Network Management . . . . . . . . . . . . . . . . . . . . . . . . . . 6

2.3.1 Overview of the architecture . . . . . . . . . . . . . . . . . . 9

2.3.4 Object Services . . . . . . . . . . . . . . . . . . . . . . . . . . 11

2.3.5 Competing Technologies . . . . . . . . . . . . . . . . . . . . . 13

2.3.6 Alternative ORBs . . . . . . . . . . . . . . . . . . . . . . . . 14

2.4.2 Entry-point when implementing . . . . . . . . . . . . . . . . . 17

4 Design and Implementation 22

4.3 Northbound Communication . . . . . . . . . . . . . . . . . . . . . . 25

5.1 Test Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

6.2 Frameworks and Library choices . . . . . . . . . . . . . . . . . . . . 36

6.3 Design Choices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

6.4 Concept and Client Value . . . . . . . . . . . . . . . . . . . . . . . . 39

6.5 Future potential . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

In history, you often see large corporations cooperating on standards to promote

Figure 1: What the simulator should implement in correlation to the

The purpose of this thesis from an academic perspective is to develop a deeper

In this project, a simulator for a network elements and a northbound interface

Abstraction The functionality of a module should be characterized by a con-

Performance The simulator should be lightweight and perform well, as it will

Usability The information provided by the simulator must be easily accessible

The simulator should only be able to communicate northbound, in other words,

2.1 Network Management

Telecommunication providers require Operational Support Systems to manage

The solution provided for Performance Management collects, processes, and

ServiceOn is a portfolio of Element, Network and Service Management tools

Figure 2: ServiceOn System Platform

2.3.1 Overview of the architecture

CORBA is a middleware architecture designed by OMG used to ensure language

Finding the object implementation for the request

Figure 3: IDL files produce interfaces towards the ORB.

A request is issued using an object reference, an operation name and a set of

CORBA uses an interface definition language (OMG IDL) to specify interfaces.

CORBA also provides an alternative method of invocation, namely Dynamic

In the OSI model, CORBA lies below a vendor-produced protocol (TMF814 in

2.3.4 Object Services