Update¶

Hint - no Internet access

If the server on which you want to update the components does not have Internet access, use another server with Internet access for logging on to the SEAL Systems delivery platform and downloading the folder and packages. Then, copy the downloaded files to the server on which you want to update.

Update to 1.2.0¶

Notes (1.2.0)¶

Version 1.2.0 of Local Spooler is a breaking change to previous versions. The SEAL NATS message broker has been introduced to improve the message handling and has to be installed before updating to Local Spooler 1.2.0.

With Local Spooler 1.2.0, the MongoDB service has been replaced by a newer incompatible version. Therefore, the data stored in MongoDB has to be exported before the update and imported again after the update. For how to do this, refer to the SEAL-specific MongoDB documentation.

The v2 REST routes have been deactivated. Now, only v3 with authentication is supported. For this, easyPRIMA as of version 1.7.0 is required.

With Local Spooler 1.2.0, the JOBNAME and USERNAME parameters are stored in the job as jobName and userName. To guarantee that the job and user names are displayed correctly at the printer, which is important especially when using 3rd-party pickup printing systems or secure printing with a PIN, make sure you will soon update to printer templates from March 2022 or later.

Before the Update (1.2.0)¶

Stop Local Spooler due to updating a running system will not work properly.
Export the data stored in MongoDB, refer to the SEAL-specific MongoDB documentation.
Update the MongoDB service to the version 4.4.7, refer to the SEAL-specific MongoDB documentation.
Install the SEAL NATS message broker, refer to the SEAL NATS documentation.

After the Update (1.2.0)¶

Start Local Spooler.
Import the MongoDB data exported before, refer to the SEAL-specific MongoDB documentation.
Add the keys relevant for the seal-plossys-message-relay service which is the connection to SEAL NATS. The relevant key is at least BROKER_SERVERS.
If you have customized JOB_MAX_POSTPONED_COUNT for seal-controller, set the same value with JOB_MAX_POSTPONED_COUNT for seal-convert-dispatcher.
After updating to Local Spooler 1.2.0, you have to open the ports with the script. For more information, refer to Open the Firewall Ports.
The following service keys used for IPP and SAP notifications are to be set for the seal-co-notifier instead of the seal-job-notifier service:

Update to 1.1.0¶

Notes (1.1.0)¶

With Local Spooler 1.1.0, the MongoDB service has been replaced by a newer incompatible version. Therefore, the data stored in MongoDB has to be exported before the update and imported again after the update. For how to do this, refer to the SEAL-specific MongoDB documentation.

Before the Update (1.1.0)¶

Uninstall Relay Server 1.0.0
Export the data stored in MongoDB, refer to the SEAL-specific MongoDB documentation.
Update the MongoDB service to the new version, refer to the SEAL-specific MongoDB documentation.

After the Update (1.1.0)¶

Import the MongoDB data exported before, refer to the SEAL-specific MongoDB documentation.
Check the keys for the cooperation with MongoDB. They are the same as for PLOSSYS 5. For more information, refer to the PLOSSYS 5 documentation.

Update Local Spooler¶

In a browser, log on to the SEAL Systems delivery platform with your logon data:

https://delivery.sealsystems.de

Hint - logon data

You receive the logon data from your Technical Project Manager at SEAL Systems.
Download the Local Spooler - 1.2.0.489 - rpm folder. It is saved as Local Spooler - 1.2.0.489 - rpm.zip.
Extract Local Spooler - 1.2.0.489 - rpm.zip.
Switch to the Local Spooler - 1.2.0.489 - rpm directory and start the installation of the packages:
```
sudo sh install.sh
```
Start Local Spooler:
```
plossys service start
```