Editing the TEDNODE.PROPERTIES File

If an External Subscriber server is not set up as a Subscriber object in any eDirectory tree, you can place a TEDNODE.PROPERTIES file on that server so that it can perform Subscriber functions. The TEDNODE.PROPERTIES file must be placed in the ZENWORKS\PDS\TED directory on the server.

A sample of the TEDNODE.PROPERTIES file is located at the root of the ZENworks for Servers Companion CD.

Following is the required format of the file, including comments on some of the entries. Note that the information on the right side of an = symbol is only an example and not the required value for that line. However, the examples are intended to show the correct syntax for the values.

Line Content Comments

workingdir = d:\ted\tran

Subscriber's working directory

io.input = 100

Receive rate in bytes per second

io.output = -1

Send rate in bytes per second

variable1 = vol=sys:

Define the variable "vol" with the value "sys:"

variable1.description = Destination Volume

A description of the variable's function

console.level = 6

Message level for the server's console

log.level = 1

Message level for log file

log.days = 1

Number of days to save log file entries

log.path = d:\\ted\\tran\\log.txt

Path for log file and log file name

workorder.timeout = 0

Number of seconds to wait for reply from the Distributor before dropping connection; 0 = wait forever

workorder.concurrent = 0

Concurrent Distributions

email.level = 0

Message level for e-mail

smtp.host = email.novell.com

Location of SMTP host

snmp.level = 0

Message level for SNMP traps

email.target1 = johndoe@novell.com

E-mail address for the messages

For the remaining TEDNODE.PROPERTIES file entries, remove the # symbol from a line to enable it. This will make that line effective for the schedule type if is listed under. However, do not remove the # symbol from the first line for a schedule type because it is only a description that indicates the schedule type. You can change the default values that are listed.

Note that the following sample has the Daily schedule enabled because the appropriate # symbols have been removed.

Line Content

# Yearly schedule and associated keys (with default values specified)
#schedule.type=yearly
#schedule.month=1
#schedule.day=1
#schedule.begin.hour=8
#schedule.begin.minute=0
#schedule.end.hour=17
#schedule.end.minute=0
#schedule.random=false

# Monthly schedule and associated keys (with default values specified)
#schedule.type=monthly
#schedule.day=1
#schedule.begin.hour=8
#schedule.begin.minutes=0
#schedule.end.hour=17
#schedule.end.minute=0
#schedule.random=false

# Daily schedule and associated keys (with default values specified)
schedule.type=daily
schedule.days=Monday,Tuesday,Wednesday,Thursday,Friday,Saturday,Sunday
schedule.begin.hour=8
schedule.begin.minutes=0
schedule.end.hour=17
schedule.end.minute=0
schedule.repeat.days=0
schedule.repeat.hours=0
schedule.repeat.minutes=0
schedule.random=false

# Immediate schedule and associated keys (with default values specified)
#schedule.type=immediately
#schedule.repeat.days=0
#schedule.repeat.hours=0
#schedule.repeat.minutes=0

# Interval schedule and associated keys (with default values specified)
#schedule.type=interval
#schedule.repeat.hours=0
#schedule.repeat.minutes=0

# Never schedule and associated keys (with default values specified)
#schedule.type=never

# Time schedule and associated keys (with default values specified)
#schedule.type=time
#schedule.date.year=2001
#schedule.date.month=1
#schedule.date.day=1
#schedule.begin.hour=8
#schedule.begin.minutes=0