The Next Generation Zenworks Architecture - Novell ZENWORKS 10 CONFIGURATION MANAGEMENT SP3 - MIGRATION GUIDE 10.3 30-03-2010 Migration Manual

eDirectory is the key requirement as the object store for all users' workstations and ZENworks
objects
Novell ConsoleOne
All access to the eDirectory environment is via the NetWare Core Protocol
The product is cross-platform and supports services running on Linux, NetWare, and Windows

2.1.2 The Next Generation ZENworks Architecture

Novell ZENworks 10 Configuration Management features a three-tier architecture, commonly
known as Services-Oriented Architecture (SOA). This architecture separates the components,
making the product far more modular. Now the various tiers can be updated independently, making
it easier to change business logic or add new modules.
With Novell ZENworks 10 Configuration Management, the server-side infrastructure consists of
two tiers (see Figure 2-2). The first is the data model, and the second comprises the file system (to
store actual files), the database (for storing ZENworks information), and the optional identity store,
which allows user-based resource management. With the release of ZENworks 10 Configuration
Management, Novell eDirectory and Microsoft* Active Directory* are supported natively as user
sources for user identity information.
ZENworks 10 Three-Tier Architecture
Figure 2-2
Database Identities
Persistence
Business Logic
Web Services
In the new architecture, Novell ZENworks 10 Configuration Management has been decoupled from
eDirectory, which is no longer a key requirement for the product to function. You no longer need to
manage a directory in order to provide systems management services. This does not mean that you
cannot benefit from integrating ZENworks 10 Configuration Management with your existing
eDirectory environment. In fact, you can continue to use your existing directory infrastructure for
user identity information, but you do not need to extend the schema or install the product on a server
that runs eDirectory.
Another major architectural change is the way that the client and server communicate with each
other (see Figure 2-3). You continue to run a Novell ZENworks agent (ZENworks Adaptive Agent)
on the managed device, but the bulk of the work (logic and workload) happens on the server side. As
seen in Figure 2-3, the client initiates communications with the server side (the Web server on the
ZENworks 10 Configuration Management Primary Server), but the server can also communicate
Differences between ZENworks 10 Configuration Management and Traditional ZENworks
®
is required to manage the ZENworks infrastructure
File System
Data
Model
(NCP )
TM TM
15