ch03.htm

this describes managing multivendor networks

MPE operating system.</P>
<P>The HP implementation of CDE supports a variety of capabilities, including session
management, window management, object/folder management, a full set of productivity
tools and network services, and a set of GUI toolkits. CDE provides a set of policies
and protocols for exchanging data between applications, and a file manager for manipulating
objects.</P>
<P>Beyond improving the basic PC interface, HP's VUE pushes into the more traditional
area of terminal interfaces. Here, by combining the graphical capabilities of X Terminals
with its own implementation of X Window, VUE lays the foundation for a distributed
computing environment that supports multiple systems and graphics terminals. Therefore,
given the graphical, client/server foundation of VUE, HP's PC integration approach
moves from a novel PC integration strategy to a networkwide standard for user/application
interfaces.
<H3><A NAME="Heading13"></A><FONT COLOR="#000077">Office Automation</FONT></H3>
<P>The core product in HP's office automation package is HP Open DeskManager, which
resides on an HP 3000 and uses HP's TurboIMAGE database system to maintain its structure
and information. HP Open DeskManager provides office automation functions over a
wide area encompassing different processing nodes (systems) and nonlocal users. HP
Open DeskManager offers these features:

<UL>
	<LI><I>Electronic mail.</I> HP Open DeskManager provides a strong client/server-based
	electronic messaging system that integrates several commonly-used clients (such as
	Microsoft Mail and Lotus cc:Mail) into an HP 3000 messaging backbone. The system
	includes its own text editor, supports the native HP 3000 line editor, and can import
	or export files created by HP Word or any other program that can process standard
	text files.<BR>
	<BR>
	
	<LI><I>Calendar/scheduling.</I> HP Open DeskManager provides an electronic calendar
	that includes to-do list processing and schedules meetings with other users. (This
	scheduling capability also includes finding common free times for all target participants).
	Users can also choose to deploy Microsoft's Schedule+ calendaring package as a front
	end.<BR>
	<BR>
	
	<LI><I>Filing. </I>HP Open DeskManager can organize files or documents into folders
	that are placed in filing cabinets. This capability accommodates a range of functions,
	such as setting up an information database or simply filing inbound and outbound
	mail in a highly organized fashion.
</UL>

<P>HP Open DeskManager's unique interpretive language, combined with its capability
of altering screen contents, enables customization of the product at almost any level.
New commands and functions can be implemented to expand (or redefine) the role of
the product.</P>
<P>Although HP Open DeskManager is a stand-alone product, it is also part of HP's
NewWave Office strategy. As part of the bigger picture, Open DeskManager provides
a core set of services on an HP 3000 computer that can be joined by other services
such as HP Resource Sharing and HP Networked PC Management.</P>
<P>HP Open DeskManager can be used to provide electronic mail services to terminal
users, while still allowing for future growth to PC clients and an electronic mail
server backbone. The HP 3000-based messaging backbone is often more robust and easier
to manage than PC-LAN- based e-mail systems, especially in a larger environment.
Open DeskManager can be used to migrate to this enterprise messaging environment,
while retaining an existing investment in PC messaging applications. The latest release
can support both HP and non-HP user interfaces. Clients supported include Lotus cc:Mail,
Microsoft Mail, HP NewWave Mail, and HP Advance Mail; these clients are all included
in the basic package. HP is also planning to add support for additional Windows and
Macintosh clients. Connectivity with other e-mail systems, including X.400, the Internet,
EDI network, and products such as Digital's ALL-IN-ONE and IBM's PROFS, is provided
through available gateways. PC users access the system through either terminal emulation
or one of the aforementioned front-end clients.
<H2><A NAME="Heading14"></A><FONT COLOR="#000077">Network Architecture</FONT></H2>
<P>Because the HP line of computers does not yet share a common set of connectivity
guidelines, the networking architecture of HP machines is quite diverse. This is
not to say that the computers have no common ground for connectivity (in fact, they
have several); rather, each line must be analyzed for its own relative merits. HP
calls its network architecture AdvanceNet (see Figure 3.6). <B></B></P>

<P><A HREF="javascript:if(confirm('http://docs.rinet.ru:8080/MuNet/ch03/03fig06.gif  \n\nThis file was not retrieved by Teleport Pro, because it was redirected to an invalid location.  You should report this problem to the site\'s webmaster.  \n\nDo you want to open it from the server?'))window.location='http://docs.rinet.ru:8080/MuNet/ch03/03fig06.gif'" tppabs="http://docs.rinet.ru:8080/MuNet/ch03/03fig06.gif"><B>FIG. 3.6</B></A> <I>Sample HP AdvanceNet Network</I>
</P>

<P>For example, while the HP 3000 Series 900 requires an IEEE 802.3 (or Ethernet)
LAN, the HP 1000, HP 9000, and HP 3000 CISC computers support the IEEE 802.3 LAN
as an option. In supporting the IEEE 802.3 standard, HP can use a ThickLAN backbone
(conforming to the IEEE 10BASE5 standard) while also supporting ThinLAN (IEEE 10BASE2)
coaxial segments. This implementation is compatible with Digital's Ethernet backbone
and ThinWire coaxial segments. In HP terminology, however, attachments to the LAN
are made via Medium Attachment Units (MAUs) instead of transceivers.</P>
<P>When all of the various models are connected to a common LAN, they can communicate
with one another using either HP's Networking Services products (NS/1000, NS/3000,
or NS/9000) or via TCP/IP (TCP/IP products are available from HP and from third-party
companies).</P>
<P>Although the IEEE 802.3 LAN is the preferred methodology for system-to-system
network- ing (with or without the use of third-party bridges to address WANs), an
older product--<SUB> </SUB>Distributed Services (DS)--is often used with HP 1000
computers. In a nutshell, DS provides HDLC-type point-to-point links between HP 3000
and the older HP 1000 systems. Although DS is no longer an option for the HP 3000s,
it remains available on HP 1000s.</P>
<P>To integrate PCs into the mainstream LAN, HP provides several different PC strategies:

<UL>
	<LI><I>HP StarLAN.</I> This is the traditional 1-Mbps star-topology LAN. In this
	case, a bridge interfaces the star's hub with the ThickLAN (via a MAU).<BR>
	<BR>
	
	<LI><I>HP StarLAN-10.</I> An improved and faster (10 Mbps) version of the StarLAN.
	In this implementation, the star's hub can attach directly to the ThickLAN (via a
	MAU).<BR>
	<BR>
	
	<LI><I>ThinLAN hub.</I> A similar product to Digital's ThinWire repeaters. The ThinLAN
	hub attaches to the ThickLAN (via a MAU) and provides multiple ThinWire segments.
</UL>

<P>HP uses two solutions to provide connectivity to IBM and Digital. For IBM connectivity,
HP provides combined hardware/software products for its computer lines to implement
bisynchronous and SNA SDLC links to IBM systems. For Digital Equipment connectivity,
HP provides DEC-resident software that implements HP's NS within a VAX. In this scenario,
the HP equipment and Digital equipment must reside on the same physical LAN.</P>
<P>HP also produces a variety of X.25 interface devices. The majority of these devices
implement bridges between asynchronous connections (to computers or terminals) and
the X.25 network.</P>

<P>To connect terminals to the system, HP employs several approaches (see Figure
3.7).</P>

<P><A HREF="javascript:if(confirm('http://docs.rinet.ru:8080/MuNet/ch03/03fig07.gif  \n\nThis file was not retrieved by Teleport Pro, because it was redirected to an invalid location.  You should report this problem to the site\'s webmaster.  \n\nDo you want to open it from the server?'))window.location='http://docs.rinet.ru:8080/MuNet/ch03/03fig07.gif'" tppabs="http://docs.rinet.ru:8080/MuNet/ch03/03fig07.gif"><B>FIG. 3.7</B></A> <I>HP Terminal Server Connections</I></P>

<P>Terminals attach directly to HP 1000, HP 9000 and HP 3000 CISC machines via asynchronous
serial links to ports (of varying levels of intelligence) integrated into the main
system hardware.</P>

<P>For the HP 3000 Series 900, terminals connect to DTCs via asynchronous serial
links, and the DTC, in turn, connects to the IEEE 802.3 LAN. Each DTC can support
up to 48 direct-connect lines. This approach is remarkably similar to Digital's terminal
server approach, with these exceptions:

<UL>
	<LI>A DTC provides access to the HP 3000 Series 900 only. If a DTC-attached terminal
	must access a different type of HP computer, it must use some form of networking
	service or be used with a TS8 (as explained later).<BR>
	<BR>
	
	<LI>For a DTC to be fully functional (for example, for one terminal be able to access
	multiple Series 900s), it must be controlled by an OpenView DTC Manager (a PC attached
	to the LAN and running the HP management software).
</UL>

<P>The TS8 terminal server is used for terminal access to LAN-based HP computers.
The TS8 provides asynchronous attachment for up to eight terminals (or printers)
using the TCP/IP TELNET protocol. The value of a TS8 is directly related to the types
of hosts in the network and the networking services that are available:

<UL>
	<LI>For the HP 9000 running TCP/IP, terminals attached to the TS8 can directly access
	that computer.<BR>
	<BR>
	
	<LI>For the HP 3000 Series 900, an additional TS8 (or multiple TS8s) must be attached
	to DTCs. The terminal attached to the first TS8 is routed through the second TS8
	into the DTC and then into the Series 900 host.<BR>
	<BR>
	
	<LI>For all other cases, the HP host must also have one or more TS8s attached directly
	to its asynchronous ports. A terminal directly attached to a TS8 then is routed to
	a host-based TS8 that converts the traffic back to an asynchronous serial connection.
</UL>

<CENTER>
<P>
<HR>
<A HREF="ch02.htm" tppabs="http://docs.rinet.ru:8080/MuNet/ch02/ch02.htm"><IMG SRC="previous.gif" tppabs="http://docs.rinet.ru:8080/MuNet/button/previous.gif" WIDTH="128" HEIGHT="28"
ALIGN="BOTTOM" ALT="Previous chapter" BORDER="0"></A><A HREF="ch04.htm" tppabs="http://docs.rinet.ru:8080/MuNet/ch04/ch04.htm"><IMG
SRC="next.gif" tppabs="http://docs.rinet.ru:8080/MuNet/button/next.gif" WIDTH="128" HEIGHT="28" ALIGN="BOTTOM" ALT="Next chapter"
BORDER="0"></A><A HREF="index-2.htm" tppabs="http://docs.rinet.ru:8080/MuNet/index.htm"><IMG SRC="contents.gif" tppabs="http://docs.rinet.ru:8080/MuNet/button/contents.gif" WIDTH="128"
HEIGHT="28" ALIGN="BOTTOM" ALT="Contents" BORDER="0"></A> <BR>
<BR>
<BR>


<P>&#169; <A HREF="javascript:if(confirm('http://docs.rinet.ru:8080/MuNet/copy.htm  \n\nThis file was not retrieved by Teleport Pro, because it was deleted using Teleport Pro\'s Delete command.  \n\nDo you want to open it from the server?'))window.location='http://docs.rinet.ru:8080/MuNet/copy.htm'" tppabs="http://docs.rinet.ru:8080/MuNet/copy.htm">Copyright</A>, Macmillan Computer Publishing. All
rights reserved.
</CENTER>


</BODY>

</HTML>