Network element types

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 programmatically 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.

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 the following figure:
picnodea.gif
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. The following tables show these drawings and the corresponding network element type name.
IP network elements 
Network Element Type
Representation
IP_ComputerFlat
IP_ComputerFlat.gif
IP_ComputerTower
IP_ComputerTower.gif
IP_Database
IP_Database.gif
IP_Desktop
IP_Desktop.gif
IP_Equipment
IP_Equipment.gif
IP_Firewall
IP_Firewall.gif
IP_Firewall2
IP_Firewall2.gif
IP_InkjetPrinter
IP_InkjetPrinter.gif
IP_Laptop
IP_Laptop.gif
IP_Laptop2
IP_Laptop2.gif
IP_LaserPrinter
IP_LaserPrinter.gif
IP_Mainframe
IP_Mainframe.gif
IP_Mainframe2
IP_Mainframe2.gif
IP_Mainframe3
IP_Mainframe3.gif
IP_Modem
IP_Modem.gif
IP_Modem2
IP_Modem2.gif
IP_Network
IP_Network.gif
IP_Network2
IP_Network2.gif
IP_Network3
IP_Network3.gif
IP_PDA
IP_PDA.gif
IP_Printer
IP_Printer.gif
IP_Printer2
IP_Printer2.gif
IP_Router
IP_Router.gif
IP_Router2
IP_Router2.gif
IP_Router3
IP_Router3.gif
IP_SatelliteAntenna
IP_SatelliteAntenna.gif
IP_Server
IP_Server.gif
IP_Server2
IP_Server2.gif
IP_Terminal
IP_Terminal.gif
IP_Terminal2
IP_Terminal2.gif
Office network elements 
Network Element Type
Representation
Office_ComputerFlat
Office_ComputerFlat.gif
Office_ComputerTower
Office_ComputerTower.gif
Office_Desktop
Office_Desktop.gif
Office_Fax
Office_Fax.gif
Office_Fax2
Office_Fax2.gif
Office_InkjetPrinter
Office_InkjetPrinter.gif
Office_Laptop
Office_Laptop.gif
Office_Laptop2
Office_Laptop2.gif
Office_LaserPrinter
Office_LaserPrinter.gif
Office_Modem
Office_Modem.gif
Office_Modem2
Office_Modem2.gif
Office_PDA
Office_PDA.gif
Office_Phone
Office_Phone.gif
Office_Phone2
Office_Phone2.gif
Office_Printer
Office_Printer.gif
Office_Printer2
Office_Printer2.gif
Office_Server
Office_Server.gif
Office_Server2
Office_Server2.gif
Office_Terminal
Office_Terminal.gif
Office_Terminal2
Office_Terminal2.gif
SAN network elements 
Network Element Type
Representation
SAN_CartridgeSystem
SAN_CartridgeSystem.gif
SAN_Database
SAN_Database.gif
SAN_Disk
SAN_Disk.gif
SAN_DoubleDatabase
SAN_DoubleDatabase.gif
SAN_FiberChannelSwitch
SAN_FiberChannelSwitch.gif
SAN_FiberChannelSwitch2
SAN_FiberChannelSwitch2.gif
SAN_Modem
SAN_Modem.gif
SAN_Modem2
SAN_Modem2.gif
SAN_Router
SAN_Router.gif
SAN_Router2
SAN_Router2.gif
SAN_Router3
SAN_Router3.gif
SAN_ServerExternalDisk
SAN_ServerExternalDisk.gif
SAN_ServerInternalDisk
SAN_ServerInternalDisk.gif
SAN_SingleDatabase
SAN_SingleDatabase.gif
SAN_TapeDrive
SAN_TapeDrive.gif
SAN_TripleDatabase
SAN_TripleDatabase.gif
Telecom network elements 
Network Element Type
Representation
Telecom_Database
Telecom_Database.gif
Telecom_Lighthouse
Telecom_Lighthouse.gif
Telecom_Mainframe
Telecom_Mainframe.gif
Telecom_Mainframe2
Telecom_Mainframe2.gif
Telecom_Mainframe3
Telecom_Mainframe3167.gif
Telecom_MD
Telecom_MD168.gif
Telecom_MD2
Telecom_MD2169.gif
Telecom_NMW
Telecom_NMW170.gif
Telecom_Server
Telecom_Server171.gif
Telecom_Server2
Telecom_Server2172.gif
Telecom_Terminal
Telecom_Terminal173.gif
Telecom_Terminal2
Telecom_Terminal2174.gif
Wireless network elements 
Network Element Type
Representation
Wireless_Antenna
Wireless_Antenna.gif
Wireless_Antenna2
Wireless_Antenna2.gif
Wireless_BSC
Wireless_BSC.gif
Wireless_BSC2
Wireless_BSC2.gif
Wireless_BTS
Wireless_BTS179.gif
Wireless_BTS2
Wireless_BTS2180.gif
Wireless_HLR
Wireless_HLR181.gif
Wireless_MobilePhone
Wireless_MobilePhone182.gif
Wireless_MSC
Wireless_MSC183.gif
Wireless_MSC2
Wireless_MSC2184.gif
Wireless_Satellite
Wireless_Satellite185.gif
Wireless_SatelliteAntenna
Wireless_SatelliteAntenna186.gif
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 wholly 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).
Cluster network elements
Network Element Type
Representation
Cluster_Colocated
ClusterColocated149.gif
Cluster_Distributed
ClusterDistributed150.gif
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). The following figure illustrates an NE type network element: here, an add-drop multiplexer with a capacity of OC192.
symbnodea.gif
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.
Symbolic representations of nodes, components and clusters 
Network Element Type
Representation
Description
Node
NE
NE.png
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
ControlNE.png
A control element is an abstraction of a physical managed telecom object unit on the control plane.
Management_Element
ManagementNE.png
A management element is an abstraction of a physical managed telecom object unit on the management plane.
NE_Logical
NE_Logical.png
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
NEComponent155.gif
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
ControlComponent156.gif
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
ManagementComponent157.gif
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
NEComponent_Logical158.gif
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
NECluster159.gif
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
ControlCluster160.gif
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
ManagementCluster161.gif
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
NECluster_Logical162.gif
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. The following table gives the available shapes and the corresponding network element type name.
Network element shapes 
Network Element Type
Shape
Shape_CellShape
Shape_CellShape.gif
Shape_Circle
Shape_Circle2.gif
Shape_CircleSmall
Shape_CircleSmall3.gif
Shape_Diamond
Shape_Diamond4.gif
Shape_Hexagon
Shape_Hexagon5.gif
Shape_HexagonFlat
Shape_HexagonFlat6.gif
Shape_HexagonSmall
Shape_HexagonSmall7.gif
Shape_Octogon
Shape_Octogon8.gif
Shape_Oval
Shape_Oval9.gif
Shape_OvalSmall
Shape_OvalSmall10.gif
Shape_Pentagon
Shape_Pentagon11.gif
Shape_PentagonBottom
Shape_PentagonBottom12.gif
Shape_PentagonLeft
Shape_PentagonLeft13.gif
Shape_PentagonRight
Shape_PentagonRight14.gif
Shape_PentagonTop
Shape_PentagonTop15.gif
Shape_Rectangle
Shape_Rectangle16.gif
Shape_RectangleSmall
Shape_RectangleSmall17.gif
Shape_RoundSquare
Shape_RoundSquare18.gif
Shape_Square
Shape_Square19.gif
Shape_Transceiver
Shape_Transceiver20.gif
Shape_TransceiverBottom
Shape_TransceiverBottom21.gif
Shape_TransceiverLeft
Shape_TransceiverLeft22.gif
Shape_TransceiverRight
Shape_TransceiverRight23.gif
Shape_TransceiverTop
Shape_TransceiverTop24.gif
Shape_Trapezoid
Shape_Trapezoid25.gif
Shape_TrapezoidBottom
Shape_TrapezoidBottom26.gif
Shape_TrapezoidLeft
Shape_TrapezoidLeft27.gif
Shape_TrapezoidRight
Shape_TrapezoidRight28.gif
Shape_TrapezoidTop
Shape_TrapezoidTop29.gif
Shape_Triangle
Shape_Triangle30.gif
Shape_TriangleBottom
Shape_TriangleBottom31.gif
Shape_TriangleLeft
Shape_TriangleLeft32.gif
Shape_TriangleRight
Shape_TriangleRight33.gif
Shape_TriangleTop
Shape_TriangleTop34.gif
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.

How to retrieve a network type image through the API

You can retrieve the URL path of the image used by a network element type by calling IltSettings.GetValue (Object), where the Object argument is the access key to the icon renderer factory for the network element type. When the network element is rendered using an image, its default renderer factory is an IltNEImageBaseRendererFactory object. The getSourceImageName method on this object points to the image location inside the image repository service (the IltDefaultImageRepository object, accessible from IlpContext).
The following code retrieves the URL path in the distribution package for the image used by the IP_ComputerFlat network element type:
IltNEImageBaseRendererFactory rf = (IltNEImageBaseRendererFactory)IltSettings.GetValue("NetworkElement.Type.IP_ComputerFlat.Renderer"); 
Replace the IP_ComputerFlat type name with the name of any network element type to retrieve the image associated with that network element type.