Novell ZENWORKS LINUX MANAGEMENT 7.3 IR2, Administration Manual

Page: 491 / 684

Rolling Up Hardware Inventory 491
no
vd
ocx
(e
n)
7 Ja
nua
ry 201
0
2. The Sender moves the
.str
files from the
entmergedir
directory to the
entpushdir
directory, and compresses the files as a
.zip
file.
3. The Sender sends the
.zip
file from the
entpushdir
directory to the Receiver on the
ZENworks 7 Server Management or ZENworks 7 Desktop Management Inventory server.
4. The Receiver places the
.zip
files in the
/entpushdir/zipdir
directory.
5. The Receiver copies the
.zip
files to the
/entpushdir
directory and deletes the
.zip
files
from the
entpushdir\zipdir
directory.
6. The Receiver copies the
.zip
files to the database directory (
dbdir
) if a database is attached to
the Inventory server.
7. The Sender-Receiver logs the status in Novell eDirectory
TM
.
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 (
.str
) from the enterprise merge directory
(
entmergedir
) to the enterprise push directory (
entpushdir
).
The Sender compresses these
.str
files in the
\entpushdir
directory of the Inventory server
as a
.zip
file and then deletes the
.str
files. This
.zip
file is again compressed with the
.prp
file into a
.zip
file. The
.prp
file is an internal file containing information about the
.zip
file.
2. Based on the Discard Scan Data Time in the Inventory Service object properties of the
Receiver, the Sender deletes the compressed
.zip
files in the
\entpushdir
directory that were
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
.zip
files to the Receiver, with the oldest compressed files
sent first.
4. After transferring the
.zip
file, the Sender deletes the compressed files in the
\entpushdir
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.