GOOD STUFF NOVELL! My only comment is GET YOU A$$ES IN GEAR AND GET IT OUT FASTER!!!!!!!! LIKE TRY MID 1997....(Hint - JUNE!!!!)
Joe...
=====================================================================
April 7, 1997
Alpha
Moab makes its move
Will an updated architecture strengthen NetWare's role as an
application server platform?
By Jeff Symoens
For its next major release of IntranetWare, code-named Moab, Novell
has designed key improvements to the core operating system that show
promise in making the product more suitable as a distributed application
server. Although it's too early to tell, based on the alpha version I tested,
whether Moab enhancements can slow the onslaught of Microsoft's
Windows NT Server, Novell is definitely on the right track.
The alpha release of Moab (due to ship late this year or early next year)
focuses chiefly on technological improvements to the processor, memory,
and communications subsystems of the OS. The planned feature set of
the final version of the product will include a number of other elements,
including the much-anticipated Java Virtual Machine for NetWare.
The Java Virtual Machine will allow the operating system to run
Java-based applications on the server -- a great improvement over the
current NetWare Loadable Module (NLM) architecture.
Novell intends to offer integrated support for CORBA and Internet
Inter-ORB Protocol as an operating system service. Support for these
two standards will be critical to the success of a distributed application
architecture based on Java.
NetWare is often dismissed as a distributed application server because
of its current memory architecture. The product's lack of a good
fault-tolerant, protected-memory model allows misbehaving NLMs at
times to bring down the server. On the other hand, Windows NT and
various Unix implementations are more resistant to poorly written
programs.
Moab addresses this shortcoming in NetWare, and it's about time.
Novell has redesigned the NetWare memory model, allowing
applications to isolate themselves in protected memory and take
advantage of virtual memory. The result of this new model should serve
to produce a more fault-tolerant server that makes more efficient use of
memory, thus reducing the overall memory requirements.
One feature currently lacking in the alpha release is an option to kill
suspended threads or applications. Both Windows NT and Unix
implementations offer this capability.
In addition to an improved memory model, Moab introduces a unified
OS kernel, which can be run on either uniprocessor or multiprocessor
servers.
The new kernel has some unique features. I was able to take additional
processors offline and bring them back online without shutting down the
server.
The new multiprocessor kernel allows administrators to manually
distribute each application's share of the processors. For example, it can
give a CPU-intensive application more access to the processors.
Goodbye NetWare/IP
Novell has long been criticized for its use of NetWare/IP, which
encapsulates IPX packets over TCP/IP, in lieu of native TCP/IP
implementation. Moab will fix that by offering support for Native IP.
However, in the alpha I tested, Native IP is supported only on Windows
95 and Windows NT platforms running Novell's 32-bit clients.
In its current implementation, I found the Native IP support a bit
cumbersome; I had to specify the IP address of a preferred server each
time I attempted to log in to the network. This is necessary because IP
does not support the use of Service Advertising Protocol, which is used
to resolve a server's network address.
However, Novell is working to fix that issue by supporting Service
Location Protocol (SLP). SLP does for IP what Service Advertising
Protocol (SAP) does for IPX; namely, it allows clients to map host
addresses for network services.
Another way to solve the IP problem is through Novell's integration of
Dynamic Host Configuration Protocol (DHCP) and DNS into Novell
Directory Services (NDS). I ran into some snags getting these features
running in time for this review, so I haven't seen their effects on the new
product.
I ran into another problem with the native IP implementation on my
Windows NT machine -- I was unable to access NetWare resources
through their NDS object names. For example, I had to map NetWare
volumes using server-based identification -- as opposed to providing the
NDS context name.
Novell is expanding the use of NDS as a network directory information
provider. NetWare will continue to provide access to the directory
through Lightweight Directory Access Protocol (LDAP) via its LDAP
Services for NDS add-on product. (See "Novell brings LDAP to NDS,"
Jan. 27.)
One thing is clear, though: NetWare is moving toward a more resilient
architecture to make it a stronger distributed application server platform.
In addition, Novell's commitment to Java as a server-side development
environment and support for native IP also moves the platform in a more
open direction; this should be good for developers. The question is
whether Novell can move fast enough to revitalize its third-party
development community and subsequently deter orders for Windows NT
Server. Your actions will determine the answer.
Jeff Symoens is a senior analyst at the InfoWorld Test Center. You
can write to him at jeff_symoens@infoworld.com.
In this alpha version
Native IP-based networking
Updated multiprocessing kernel
Memory Protection and Virtual Memory features
NDS integration for DHCP/DNS
Support for NDS and SAP with WinSock 2
Updated IntranetWare Client for Windows 95
Updated IntranetWare Client for Windows NT
Workstation Manager
Planned enhancements
Novell Storage System
Novell Replication Services
Novell Distributed Print Services
Java Virtual Machine
New installation process
THE BOTTOM LINE
Moab, alpha
The next major release of IntranetWare promises to tighten up loose
ends in NetWare's architecture and provide a better distributed
application server platform.
Pros: New multiprocessor kernel; better protected-memory
architecture; native IP client support; tighter network services integration
with Novell Directory Services.
Cons: Alpha version offers good insight for direction, but it's too early to
tell.
Novell Inc., Provo, Utah; (800) 453-1267, (801) 861-7000; fax: (801)
228-7077; novell.com.
Price: Not announced.
Platform: Intel-based servers.
Ship date: Late 1997 or early 1998.
Copyright c 1997 by InfoWorld Publishing Company
====================================================================== |
