Understanding The Components Involved In The Inventory Roll-Up; Understanding The Sender - Novell ZENWORKS LINUX MANAGEMENT 7.3 IR2 - ADMINISTRATION GUIDE 02-12-2010 Administration Manual

2. The Sender moves the
directory, and compresses the files as a
3. The Sender sends the
ZENworks 7 Server Management or ZENworks 7 Desktop Management Inventory server.
4. The Receiver places the
5. The Receiver copies the
from the
entpushdir\zipdir
6. The Receiver copies the
the Inventory server.
7. The Sender-Receiver logs the status in Novell eDirectory
34.4 Understanding the Components Involved in
the Inventory Roll-Up
The Sender on the Inventory servers transfer the scan files from the ZENworks 7.3 Linux
Management Inventory server to the ZENworks 7 Server Management or ZENworks 7 Desktop
Management Inventory server. The following sections contain more information:
Section 34.4.1, "Understanding the Sender," on page 491
Section 34.4.2, "Understanding the Compressed Scan Data File," on page 492

34.4.1 Understanding the Sender

The Sender is a Java component that runs on any ZENworks 7.3 Linux Management server. The
Sender is a service loaded by the ZEN Loader.
The flow of information from the Sender in the roll-up of inventory information is as follows:
1. The ZEN Loader starts the Sender on the Inventory server. At the time specified in the Roll-Up
Schedule, the Sender moves the scan data files (
( ) to the enterprise push directory (
entmergedir
The Sender compresses these
as a file and then deletes the
.zip
file into a file. The
.zip
2. Based on the Discard Scan Data Time in the Inventory Service object properties of the
Receiver, the Sender deletes the compressed
created earlier than the specified discard scan data time. This removes unwanted scan
information being sent in the roll-up.
3. The Sender sends the compressed
sent first.
4. After transferring the
directory.
If the Sender is unable to connect to the Receiver, the Sender retries to connect after 10 seconds. The
time interval increases exponentially by a factor of 2. After 14 retries, the Sender stops trying to
connect to the Receiver. The Sender retries for approximately 23 hours before it discontinues trying.
The Sender does not process any other information while it is establishing the connection.
files from the
.str entmergedir
file.
.zip
file from the
.zip entpushdir
files in the
.zip /entpushdir/zipdir
files to the
.zip /entpushdir
directory.
files to the database directory (
.zip
files in the
.str
files. This
.str
file is an internal file containing information about the
.prp
.zip
files to the Receiver, with the oldest compressed files
.zip
file, the Sender deletes the compressed files in the
.zip
directory to the
directory to the Receiver on the
directory.
directory and deletes the
) if a database is attached to
dbdir
.
TM
) from the enterprise merge directory
.str
).
entpushdir
directory of the Inventory server
\entpushdir
file is again compressed with the
.zip
files in the
\entpushdir
Rolling Up Hardware Inventory 491
entpushdir
files
.zip
.prp
file.
.zip
directory that were
\entpushdir