Business Objects and Data Sources > Network Elements > Representation of Network Elements in a Network > 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 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:

images/picnode224.gif

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 
images/IP_ComputerFlat35.gif  
IP_ComputerTower 
images/IP_ComputerTower36.gif  
IP_Database 
images/IP_Database37.gif  
IP_Desktop 
images/IP_Desktop38.gif  
IP_Equipment 
images/IP_Equipment39.gif  
IP_Firewall 
images/IP_Firewall40.gif  
IP_Firewall2 
images/IP_Firewall241.gif  
IP_InkjetPrinter 
images/IP_InkjetPrinter42.gif  
IP_Laptop 
images/IP_Laptop43.gif  
IP_Laptop2 
images/IP_Laptop244.gif  
IP_LaserPrinter 
images/IP_LaserPrinter45.gif  
IP_Mainframe 
images/IP_Mainframe46.gif  
IP_Mainframe2 
images/IP_Mainframe247.gif  
IP_Mainframe3 
images/IP_Mainframe348.gif  
IP_Modem 
images/IP_Modem49.gif  
IP_Modem2 
images/IP_Modem250.gif  
IP_Network 
images/IP_Network51.gif  
IP_Network2 
images/IP_Network252.gif  
IP_Network3 
images/IP_Network353.gif  
IP_PDA 
images/IP_PDA54.gif  
IP_Printer 
images/IP_Printer55.gif  
IP_Printer2 
images/IP_Printer256.gif  
IP_Router 
images/IP_Router57.gif  
IP_Router2 
images/IP_Router258.gif  
IP_Router3 
images/IP_Router359.gif  
IP_SatelliteAntenna 
images/IP_SatelliteAntenna60.gif  
IP_Server 
images/IP_Server61.gif  
IP_Server2 
images/IP_Server262.gif  
IP_Terminal 
images/IP_Terminal63.gif  
IP_Terminal2 
images/IP_Terminal264.gif  

Table 4.2 Office Network Elements 
Network Element Type 
Representation 
Office_ComputerFlat 
images/Office_ComputerFlat187.gif  
Office_ComputerTower 
images/Office_ComputerTower188.gif  
Office_Desktop 
images/Office_Desktop189.gif  
Office_Fax 
images/Office_Fax190.gif  
Office_Fax2 
images/Office_Fax2191.gif  
Office_InkjetPrinter 
images/Office_InkjetPrinter192.gif  
Office_Laptop 
images/Office_Laptop193.gif  
Office_Laptop2 
images/Office_Laptop2194.gif  
Office_LaserPrinter 
images/Office_LaserPrinter195.gif  
Office_Modem 
images/Office_Modem196.gif  
Office_Modem2 
images/Office_Modem2197.gif  
Office_PDA 
images/Office_PDA198.gif  
Office_Phone 
images/Office_Phone199.gif  
Office_Phone2 
images/Office_Phone2200.gif  
Office_Printer 
images/Office_Printer201.gif  
Office_Printer2 
images/Office_Printer2202.gif  
Office_Server 
images/Office_Server203.gif  
Office_Server2 
images/Office_Server2204.gif  
Office_Terminal 
images/Office_Terminal205.gif  
Office_Terminal2 
images/Office_Terminal2206.gif  

Table 4.3 SAN Network Elements 
Network Element Type 
Representation 
SAN_CartridgeSystem 
images/SAN_CartridgeSystem207.gif  
SAN_Database 
images/SAN_Database208.gif  
SAN_Disk 
images/SAN_Disk209.gif  
SAN_DoubleDatabase 
images/SAN_DoubleDatabase210.gif  
SAN_FiberChannelSwitch 
images/SAN_FiberChannelSwitch211.gif  
SAN_FiberChannelSwitch2 
images/SAN_FiberChannelSwitch2212.gif  
SAN_Modem 
images/SAN_Modem213.gif  
SAN_Modem2 
images/SAN_Modem2214.gif  
SAN_Router 
images/SAN_Router215.gif  
SAN_Router2 
images/SAN_Router2216.gif  
SAN_Router3 
images/SAN_Router3217.gif  
SAN_ServerExternalDisk 
images/SAN_ServerExternalDisk218.gif  
SAN_ServerInternalDisk 
images/SAN_ServerInternalDisk219.gif  
SAN_SingleDatabase 
images/SAN_SingleDatabase220.gif  
SAN_TapeDrive 
images/SAN_TapeDrive221.gif  
SAN_TripleDatabase 
images/SAN_TripleDatabase222.gif  

Table 4.4 Telecom Network Elements 
Network Element Type 
Representation 
Telecom_Database 
images/Telecom_Database163.gif  
Telecom_Lighthouse 
images/Telecom_Lighthouse164.gif  
Telecom_Mainframe 
images/Telecom_Mainframe165.gif  
Telecom_Mainframe2 
images/Telecom_Mainframe2166.gif  
Telecom_Mainframe3 
images/Telecom_Mainframe3167.gif 
Telecom_MD 
images/Telecom_MD168.gif 
Telecom_MD2 
images/Telecom_MD2169.gif 
Telecom_NMW 
images/Telecom_NMW170.gif 
Telecom_Server 
images/Telecom_Server171.gif 
Telecom_Server2 
images/Telecom_Server2172.gif 
Telecom_Terminal 
images/Telecom_Terminal173.gif 
Telecom_Terminal2 
images/Telecom_Terminal2174.gif 

Table 4.5 Wireless Network Elements 
Network Element Type 
Representation 
Wireless_Antenna 
images/Wireless_Antenna175.gif  
Wireless_Antenna2 
images/Wireless_Antenna2176.gif  
Wireless_BSC 
images/Wireless_BSC177.gif  
Wireless_BSC2 
images/Wireless_BSC2178.gif  
Wireless_BTS 
images/Wireless_BTS179.gif 
Wireless_BTS2 
images/Wireless_BTS2180.gif 
Wireless_HLR 
images/Wireless_HLR181.gif 
Wireless_MobilePhone 
images/Wireless_MobilePhone182.gif 
Wireless_MSC 
images/Wireless_MSC183.gif 
Wireless_MSC2 
images/Wireless_MSC2184.gif 
Wireless_Satellite 
images/Wireless_Satellite185.gif 
Wireless_SatelliteAntenna 
images/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 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 
images/ClusterColocated149.gif 
Cluster_Distributed 
images/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). Figure 4.3 illustrates an NE type network element: here, an add-drop multiplexer with a capacity of OC192.

images/symbnode225.gif

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 
images/NE151.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 
images/ControlNE152.png  
A control element is an abstraction of a physical managed telecom object unit on the control plane. 
Management_Element 
images/ManagementNE153.png  
A management element is an abstraction of a physical managed telecom object unit on the management plane. 
NE_Logical 
images/NE_Logical154.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 
images/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 
images/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 
images/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 
images/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 
images/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 
images/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 
images/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 
images/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. 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 
images/Shape_CellShape.gif 
Shape_Circle 
images/Shape_Circle2.gif 
Shape_CircleSmall 
images/Shape_CircleSmall3.gif 
Shape_Diamond 
images/Shape_Diamond4.gif 
Shape_Hexagon 
images/Shape_Hexagon5.gif 
Shape_HexagonFlat 
images/Shape_HexagonFlat6.gif 
Shape_HexagonSmall 
images/Shape_HexagonSmall7.gif 
Shape_Octogon 
images/Shape_Octogon8.gif 
Shape_Oval 
images/Shape_Oval9.gif 
Shape_OvalSmall 
images/Shape_OvalSmall10.gif 
Shape_Pentagon 
images/Shape_Pentagon11.gif 
Shape_PentagonBottom 
images/Shape_PentagonBottom12.gif 
Shape_PentagonLeft 
images/Shape_PentagonLeft13.gif 
Shape_PentagonRight 
images/Shape_PentagonRight14.gif 
Shape_PentagonTop 
images/Shape_PentagonTop15.gif 
Shape_Rectangle 
images/Shape_Rectangle16.gif 
Shape_RectangleSmall 
images/Shape_RectangleSmall17.gif 
Shape_RoundSquare 
images/Shape_RoundSquare18.gif 
Shape_Square 
images/Shape_Square19.gif 
Shape_Transceiver 
images/Shape_Transceiver20.gif 
Shape_TransceiverBottom 
images/Shape_TransceiverBottom21.gif 
Shape_TransceiverLeft 
images/Shape_TransceiverLeft22.gif 
Shape_TransceiverRight 
images/Shape_TransceiverRight23.gif 
Shape_TransceiverTop 
images/Shape_TransceiverTop24.gif 
Shape_Trapezoid 
images/Shape_Trapezoid25.gif 
Shape_TrapezoidBottom 
images/Shape_TrapezoidBottom26.gif 
Shape_TrapezoidLeft 
images/Shape_TrapezoidLeft27.gif 
Shape_TrapezoidRight 
images/Shape_TrapezoidRight28.gif 
Shape_TrapezoidTop 
images/Shape_TrapezoidTop29.gif 
Shape_Triangle 
images/Shape_Triangle30.gif 
Shape_TriangleBottom 
images/Shape_TriangleBottom31.gif 
Shape_TriangleLeft 
images/Shape_TriangleLeft32.gif 
Shape_TriangleRight 
images/Shape_TriangleRight33.gif 
Shape_TriangleTop 
images/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.