Client-server architecture is a computing model in which the server is programmed to manage most of the services and resources requested by the client. Using a client-server architecture guarantees the transmission of jobs between one RIP station and a remote RIP station by sharing the same local network.
What is a Client-Server architecture?
In the example above, the Servers process the Client's requests. Once a request is accepted, the 3 Servers start working on it to send back an accurate reply to the Client.
Client-Server Architecture in CalderaRIP
Client-Server Architecture in CalderaRIP
In the example above, a user is an additional graphical interface to the default Caldera user and can be included in some package licenses. In this way, several operators can use CalderaRIP at the same time. You can purchase Users as much as you want. At least 1 graphical interface is included (1 Caldera) in the RIP package.
Based on the example above, we can see that:
Acts as a key Server: It drives locally "CalderaJet" and "CalderaCutter 1". It can also act as a Client if it drives CalderaJet 1, 2, 3, 4 plus CalderaCutter 2 through User
1, User 2, or User 3.
Info
It is important to note that with CalderaRIP, a workstation can be both a Client and a Server.
Drive local devices
Acts as a server for CalderaJet 3 and CalderaJet 4.
Advantages of using Client-Server architecture with CalderaRIP
This model allows you to:
- Control the whole production on one single workstation
- Apply shared calculations in case of big data processing and job duplicates
Good to know
It is possible to make your servers share the same rasterization calculations if you have identical tasks that must be treated simultaneously. Shared calculations in a Client/Server architecture allow you to make servers work in parallel to complete their tasks.
This method can be used in database replication and big data processing. For example, it is possible to apply parallel rasterization calculations for multiple print jobs for faster completion of tasks. - Share a Caldera license between multiple workstations (learn more by clicking here)
- Add a new printer by installing the driver on the right computer
- Drive the printer from another RIP station by changing a few IP settings
Client/Server Considerations
- Network: Make sure that all Caldera stations communicate with each other through the first Ethernet controller (usually eth0 on Linux or en0 on Mac OSX). Incorrect configuration could lead to RPC connection failures and difficulties initializing the printers' modules.
- Printer drivers: It would be advantageous to install all printers on all Caldera servers. In case one of the Caldera stations fails, the printing can continue after changing a few IP addresses.
-
EasyMedia: Maintains backups of all media profiles as they have to be present on the server and the client computers.
Recommendation
It is also possible to create a custom driver in ServerAdmin, which allows you to maintain a backup of your settings.
- Power-up sequence: It is advised to have the printers, cutters, and network sharing active before starting the RIP with the KeyServer. After the KeyServer is up and running, you will have to power on the other workstations (servers) in order to be able to start the remote Caldera RIP(s) on the KeyServer.