Product

Platform

Operating system

Error

Symptoms

The default behaviour for Prinergy (1.1 and current 2.0 ) is to have all job daemons run on the Primary Prinergy Server. There are situations where this is not desirable. It is possible to configure the Prinergy system so that job daemons are hosted on Secondary Servers.

Cause

Solution

Steps to follow to have a secondary server as a job daemon host:

1. The JobDaemonNodeList registry key needs to be modified. It is located in:

HKEY_LOCAL_MACHINE\SOFTWARE\Creo\Araxi\X.Y.Z.BLDMN\Default\System (where X.Y.Z is the release and MN is the Build number)

on the Primary Prinergy server.

By default, the JobDaemonNodeList value will contain the Primary Prinergy Server.

2. Edit this value using regedit or regedt32, adding the Secondary Servers you want to have as Job Daemon Nodes as follows

Primary;Secondary1;Secondary2;Secondary3

3) Save your changes and exit the registry editor.

NOTES

a. This a semicolon delimited list

b. You do not need to keep the Primary as a job daemon node

c. Do NOT put a blank before or after any semicolon

Additional Info:

Jobs that are created with their job folder on a node that IS NOT in the JobDaemonNodeList will have their job daemon running on one of the servers in the JobDaemonNodeList (assignment is done in a round robin method). But jobs that are created with their job folder on a node that IS in the JobDaemonNodeLIst will always have their job daemon running on the same node on which their job folder is located.

So, for example, jobs that have their job folder located on a tertiary node or on Secondary 4 will have their job daemons running on one of the machines in the JobDaemonNodeList. A job that has its job folder on Secondary1, 2, 3 or the Primary, will have its job daemon running on the SAME machine as the job folder (so folder on Secondary1, daemon runs on Secondary1).

Permanent fix:

See also

Keywords

daemon, job manager or job folders

Technical contact(s)

Simon Chen

Submitted by

Date submitted