About Prinergy servers

A Prinergy system can include different types of servers, which can store jobs, input files, and JTPs.

Types of servers

The Prinergy system can include several types of servers.

The primary server is the main server in a Prinergy system. There is only one primary server in a Prinergy system. It contains all Prinergy Server software components, including the Oracle database. The primary server coordinates requests from the Prinergy client software (Workshop) and maintains the database.
Secondary servers are servers that run the Prinergy Server software but are not the primary server and do not have the Oracle database. You can potentially add any number of secondary servers to your Prinergy system.
Tertiary servers are file servers. They are part of the Prinergy system but are not running the Prinergy Server software. Tertiary servers can store jobs and input files.

Third-party tertiary storage

Kodak does not qualify or test specific third-party storage solutions to be used with Prinergy Workflow systems as tertiary job homes or remote storage. it is the responsibility of the customer's system administrator and IT department to establish and support connectivity between third-party storage solutions and other systems on the network. Kodak is unable to assist with networking questions or troubleshoot issues associated with third-party solutions.

Note: Issues related to read/write and/or network performance will be investigated by testing with jobs located within job homes on platforms provided by Kodak.

Storing jobs and input files on servers

Prinergy servers can store jobs or input files. Storing some or all jobs on servers other than the primary server increases the performance of the primary server.
When you share and designate a folder to store jobs, it is called a <job volume>. The server then becomes a <job home>.
When you share and designate a folder to store input files, it is called an <input volume>.

The name of a job volume usually uses the following format:

Windows: The job volume must start with AraxiVolume_, usually AraxiVolume_<server name>_<drive letter>, such as AraxiVolume_SERVER1_G.
Mac: Jobs on <server name drive letter> Drive, such as Jobs on Server1 G Drive.

Running JTPs on servers

A secondary server can run some or all JTPs to facilitate distributed processing. It is possible to have multiple active instances of certain JTPs, depending on your Prinergy licensing agreement. For example, a system could have multiple instances of the Normalizer JTP active on different Prinergy servers in order to simultaneously process multiple jobs.
CPU-intensive tasks, such as rendering final output, are good candidates for distribution onto secondary servers. Other typical uses include designating a secondary server as the InSite software server or the Archiver software server in your Prinergy system.

How Prinergy accesses servers

The Araxi service—and its user account—enables Prinergy to automatically start and restart software components on all servers in the system. When the Prinergy server starts, you must log on to the server and start the Araxi service.
The Araxi service is a Windows operating system service that monitors and restarts any Prinergy component that terminates unexpectedly. It does this within the context of groups. For example, if a process with a particular group number terminates unexpectedly and is going to be restarted, other processes with the same group number are also stopped and restarted.
Every server in the Prinergy system must have a user account with an identical user name and password so that the Araxi and AraxiBackupManager services can access every server, including tertiaries.

The default user name of this account is ARAXI.
You can change the user name and password, but both the user name and password must be the same on every server in the system. If you change the user name or password, make sure you change them on every Prinergy server.
You can change the password to increase system security—for example, if an unauthorized user discovers the password.

Important: Limit knowledge of the Araxi service account password to authorized users only. Users who log on to the system using the Araxi service account have administrative access to the Prinergy system. For example, they can edit user accounts and system settings.

Configuring Windows Server 2016 & 2019 Prinergy servers

By default, Prinergy servers running Windows Server 2016 or 2019 are shipped with SMB1 disabled and SMB 2 and 3 enabled. For best performance, all Prinergy servers and tertiary servers should be running Windows Server 2016 or 2019. If any of the tertiary servers are not running Windows Server 2016 or 2019, SMB1 may need to be enabled. If this is not done, this can cause file access/transfer issues. For assistance in enabling SMB1, contact your local support representatives.

Space shortcuts

Page tree