Browse Prior Art Database

Technique for Implementing Connected Topologies within an IBM LAN Netview Start Network

IP.com Disclosure Number: IPCOM000111460D
Original Publication Date: 1994-Feb-01
Included in the Prior Art Database: 2005-Mar-26
Document File: 2 page(s) / 120K

Publishing Venue

IBM

Related People

Shrader, TJ: AUTHOR

Abstract

Disclosed is a solution for allowing connections between network topologies in the IBM LAN NetView* Start (Start) product or other network configuration products. Start provides users with the ability to represent and configure nodes within a network. Topologies allow users to subdivide their nodes and corresponding connections into smaller groups, rather than putting them all into one network container object. This disclosure presents one way of allowing the user to connect the topology.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 45% of the total text.

Technique for Implementing Connected Topologies within an IBM LAN
Netview Start Network

      Disclosed is a solution for allowing connections between
network topologies in the IBM LAN NetView* Start (Start) product or
other network configuration products.  Start provides users with the
ability to represent and configure nodes within a network.
Topologies allow users to subdivide their nodes and corresponding
connections into smaller groups, rather than putting them all into
one network container object.  This disclosure presents one way of
allowing the user to connect the topology.

      Within a topology container, different icons represent nodes
with different functionalities in their respective views.  For
example, a node defined with only database client functionality would
appear as a database client icon in the database view of the topology
and as a null node (workstation with a not symbol over it) in the LAN
and 3270 views, as well as any other functional views besides the
database view.  Connections between a database client and server
(appearing as an arrow from the client to the server and labeled with
the connection type, such as NETBIOS) would also appear in the
database view, while LAN and 3270 connections would not.  The current
scheme works well when a user can contain all nodes within the same
topology, but if the user needs to connect a node between two
topologies, additional topology connection icons would need to be
added to the current set.

      Two topology connection icons would need to be added.  The
first would represent an outgoing connection, and it could look like
a wide arrow going into an open doorway.  The second icon would
represent an incoming connection, and it could look like a wide arrow
coming from an open doorway.  Users could drag and drop these icons
from a template folder onto the target topologies.  The outgoing icon
would have the attributes of the icon (node) and topology name of the
corresponding incoming icon in the different topology.  The incoming
icon would have the attributes of the icon (node) and topology name
of the corresponding outgoing icon as well as the connections that
were made to the outgoing icon.  These attributes would be
automatically filled in when the outgoing icon was defined, since
Start would know which connections were made to the outgoing icon, as
well as how it was defined.  (Note that the term icon can be used
interchangeably with the term object in this description, since in
this case, the icon is just a display representative of the object.)

      If other specialized topology attributes existed, they could be
added to the attribute definition of the topology connection objects
to insure that the "addresses" of the to and from topologies are
properly defined.

      For example, the user can define node NODE1 with LAN Requester
functionality and create a LAN connection between it and an outgoing
topology connection object, labeled...