The network element type defines how a given network element will be displayed. The network element type is specified by setting the value of the attribute type in the business object. This attribute can be set programatically using IltNetworkElement.TypeAttribute or through XML.
How To Set the Network Element Type Using the API
IltNetworkElement ne = new IltNetworkElement("NE1");
ne.setType (IltNetworkElement.Type.NMW);
or
IlpObject ne = ...;
ne.setAttributeValue(IltNetworkElement.TypeAttribute, IltNetworkElement.Type.NMW);
How to Set the Network Element Type Using XML
<addObject id="NE1">
<class>ilog.tgo.model.IltNetworkElement</class>
<attribute name="name">NE1</attribute>
<attribute name="type">NMW</attribute>
</addObject>
Depending on the nature of the application, a network element can be represented by a bitmap image, a symbol, or a shape. The following sections introduce the various types of representations available:
Pictorial Representation
In its pictorial representation, the network element base is a bitmap drawing, which is composed of individual graphic objects. This drawing is meant to be realistic, as you can see in Figure 4.2:
Figure 4.2 Pictorial Representations of a Terminal
Several predefined bases are available for shelf-based equipment, terminals, and mobile phone access network elements. JViews TGO includes a number of predefined network element images. Table 4.1 through Table 4.8 show these drawings and the corresponding network element type name.
Table 4.1 IP Network Elements
Network Element Type |
Representation |
IP_ComputerFlat | |
IP_ComputerTower | |
IP_Database | |
IP_Desktop | |
IP_Equipment | |
IP_Firewall | |
IP_Firewall2 | |
IP_InkjetPrinter | |
IP_Laptop | |
IP_Laptop2 | |
IP_LaserPrinter | |
IP_Mainframe | |
IP_Mainframe2 | |
IP_Mainframe3 | |
IP_Modem | |
IP_Modem2 | |
IP_Network | |
IP_Network2 | |
IP_Network3 | |
IP_PDA | |
IP_Printer | |
IP_Printer2 | |
IP_Router | |
IP_Router2 | |
IP_Router3 | |
IP_SatelliteAntenna | |
IP_Server | |
IP_Server2 | |
IP_Terminal | |
IP_Terminal2 | |
Table 4.2 Office Network Elements
Network Element Type |
Representation |
Office_ComputerFlat | |
Office_ComputerTower | |
Office_Desktop | |
Office_Fax | |
Office_Fax2 | |
Office_InkjetPrinter | |
Office_Laptop | |
Office_Laptop2 | |
Office_LaserPrinter | |
Office_Modem | |
Office_Modem2 | |
Office_PDA | |
Office_Phone | |
Office_Phone2 | |
Office_Printer | |
Office_Printer2 | |
Office_Server | |
Office_Server2 | |
Office_Terminal | |
Office_Terminal2 | |
Table 4.3 SAN Network Elements
Network Element Type |
Representation |
SAN_CartridgeSystem | |
SAN_Database | |
SAN_Disk | |
SAN_DoubleDatabase | |
SAN_FiberChannelSwitch | |
SAN_FiberChannelSwitch2 | |
SAN_Modem | |
SAN_Modem2 | |
SAN_Router | |
SAN_Router2 | |
SAN_Router3 | |
SAN_ServerExternalDisk | |
SAN_ServerInternalDisk | |
SAN_SingleDatabase | |
SAN_TapeDrive | |
SAN_TripleDatabase | |
Table 4.4 Telecom Network Elements
Network Element Type |
Representation |
Telecom_Database | |
Telecom_Lighthouse | |
Telecom_Mainframe | |
Telecom_Mainframe2 | |
Telecom_Mainframe3 | |
Telecom_MD | |
Telecom_MD2 | |
Telecom_NMW | |
Telecom_Server | |
Telecom_Server2 | |
Telecom_Terminal | |
Telecom_Terminal2 | |
Table 4.5 Wireless Network Elements
Network Element Type |
Representation |
Wireless_Antenna | |
Wireless_Antenna2 | |
Wireless_BSC | |
Wireless_BSC2 | |
Wireless_BTS | |
Wireless_BTS2 | |
Wireless_HLR | |
Wireless_MobilePhone | |
Wireless_MSC | |
Wireless_MSC2 | |
Wireless_Satellite | |
Wireless_SatelliteAntenna | |
JViews TGO also provides a pictorial representation for clusters. A cluster network element is an abstraction of a network element that is made up of two or more distinct subcomponents such as other network elements that can be (and often are) managed as standalone telecom objects. Clusters can be co-located or distributed, depending on how their subcomponents are organized (either within a managed area or spread across different areas). As with the new partial network elements concept, it is possible to represent wholy-owned clusters (that is, all the subcomponents are managed by the user), or partially-owned clusters (only some of the subcomponents are managed by the user).
Table 4.6 Cluster Network Elements
Network Element Type |
Representation |
Cluster_Colocated | |
Cluster_Distributed | |
You can create custom network element types by providing a bitmap image or a vector drawing. This process is detailed in Customizing Network Element Types in the Styling documentation.
Symbolic Representation
In the symbolic representation, network elements can be used for components, nodes or clusters. These objects are represented differently depending on which aspect of the OSS application you consider, for example, the data plane of physical managed telecom objects, the control and management planes or the logical managed telecom objects. The default type corresponding to the default symbolic network element representation is simply called NE (for Network Element). Figure 4.3 illustrates an NE type network element: here, an add-drop multiplexer with a capacity of OC192.
Figure 4.3 Symbolic Representation of NE Type Network Element
Symbolic information for NE type network elements consists of an icon representing the function of the equipment corresponding to the network element and a string representing the family of the equipment.
Table 4.7 Symbolic Representations of Nodes, Components and Clusters
Network Element Type |
Representation |
Description |
Node |
NE | |
A network element is an abstraction of a physical managed telecom object unit on the data plane, such as a router or a computer. |
Control_Element | |
A control element is an abstraction of a physical managed telecom object unit on the control plane. |
Management_Element | |
A management element is an abstraction of a physical managed telecom object unit on the management plane. |
NE_Logical | |
A logical network element is an abstraction of a non-physical managed telecom object such as a service or a software component. |
Component |
NE_Component | |
An NE component is an abstraction of a physical managed telecom object that is part of a network element, such as a network card attached to a router. |
Control_Component | |
A control component is an abstraction of a physical managed telecom object that is part of a network element, on the control plane. |
Management_Component | |
A management component is an abstraction of a physical managed telecom object that is part of a network element, on the management plane. |
NEComponent_Logical | |
A logical NE component is an abstraction of a non-physical managed telecom object that is part of a logical network element, such as a software element or a logical processor. |
Cluster |
NE_Cluster | |
An NE cluster is an abstraction of a physical managed telecom object that is made up of two or more distinct subcomponents such as other network elements that can be (and often are) managed as standalone telecom objects. |
Control_Cluster | |
A control cluster is an abstraction of a physical managed telecom object that is made up of two or more distinct subcomponents, on the control plane. |
Management_Cluster | |
A management cluster is an abstraction of a physical managed telecom object that is made up of two or more distinct subcomponents, on the management plane. |
NECluster_Logical | |
A logical NE cluster is an abstraction of a non-physical managed telecom object made up of two or more subcomponents such as other services or software components that can be (and ofter are) managed as standalone telecom objects |
Shape Representation
In this representation, the network element base is depicted by a geometric shape that symbolizes the network element type (or function class). The center of the base can contain an icon that further defines the representation of the network element function. Several predefined shapes are provided as types of the network element.
JViews TGO includes a limited number of network element shapes that can be used to build iconic network elements. Table 4.8 gives the available shapes and the corresponding network element type name.
Table 4.8 Network Element Shapes
Network Element Type |
Shape |
Shape_CellShape | |
Shape_Circle | |
Shape_CircleSmall | |
Shape_Diamond | |
Shape_Hexagon | |
Shape_HexagonFlat | |
Shape_HexagonSmall | |
Shape_Octogon | |
Shape_Oval | |
Shape_OvalSmall | |
Shape_Pentagon | |
Shape_PentagonBottom | |
Shape_PentagonLeft | |
Shape_PentagonRight | |
Shape_PentagonTop | |
Shape_Rectangle | |
Shape_RectangleSmall | |
Shape_RoundSquare | |
Shape_Square | |
Shape_Transceiver | |
Shape_TransceiverBottom | |
Shape_TransceiverLeft | |
Shape_TransceiverRight | |
Shape_TransceiverTop | |
Shape_Trapezoid | |
Shape_TrapezoidBottom | |
Shape_TrapezoidLeft | |
Shape_TrapezoidRight | |
Shape_TrapezoidTop | |
Shape_Triangle | |
Shape_TriangleBottom | |
Shape_TriangleLeft | |
Shape_TriangleRight | |
Shape_TriangleTop | |
The API that enables developers to include new network element shapes corresponding to new types of network element is detailed in Customizing Network Element Types in the Styling documentation.