Web application architecture

To visualize the network, multiple Web clients (both Network Hop View and Network Views GUIs) connect to a single Dashboard Application Services Hub (DASH) server. The Tivoli Netcool/OMNIbus Web GUI also connects to the DASH server to enable Web-based viewing and interacting with alerts held in the ObjectServer.

The following figure shows how topology and event information is displayed in Network Manager.

Figure 1. Visualization architecture
 1  Topology transferred to NCIM
The Topology manager, ncp_model sends the topology to NCIM.
 2  The Topology Visualization Web application accesses the topology
The topology is accessed by the Topology Visualization Web application running within Dashboard Application Services Hub.
 3  Topology lookup performed by the Event Gateway
Topology data from NCIM cache is made available to the Event gateway, ncp_g_event.
 4  Event enrichment and root cause analysis
Using topology data from NCIM cache, the Event Gateway performs relevant topology lookup operations to enrich events from the ObjectServer. The Event Gateway then sends relevant event to the RCA plug-in to perform root cause analysis on events, as configured.
 5  Events requested from the ObjectServer
The Web GUI requests the latest set of events from the ObjectServer. Any changes that the user makes to events using the Web GUI are sent back to the ObjectServer.
 6  Multiple client/server connections
Each Web GUI server can have multiple Web GUI clients connected to it.
 7  Event information requested
The Topology Visualization Web application requests event information from the Web GUI application.
 8  Events sent to topology visualization Web clients
The Dashboard Application Services Hub server sends topology maps to Network Hop View and Network Views clients on demand. The topology maps include device status information, that is, the severity of the highest alert affecting a given device, calculated from ObjectServer events.