Update¶

Hint - no Internet access

If the server on which you want to install SEAL Operator/SEAL Print Client does not have Internet access, use another server with Internet access for logging on to the SEAL Systems delivery platform and downloading the folder. Then, copy the downloaded zip file to the server on which you want to install SEAL Operator/SEAL Print Client.

Hint - configuration

The configuration in Consul etc. and the customer certificates set during the installation are not overwritten when updating.

Update To 1.3.0¶

Before the Update (1.3.0)¶

With SEAL Operator/SEAL Print Client 1.3.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.

After the Update (1.3.0)¶

With SEAL Operator/SEAL Print Client 1.3.0, the MongoDB service has been replaced by a newer incompatible version. Therefore, the MongoDB data exported before updating has to be re-imported. For how to do this, refer to the SEAL-specific MongoDB documentation.

Update To 1.2.0¶

Before the Update (1.2.0)¶

With SEAL Operator/SEAL Print Client 1.2.0, the version of seal-consul-agent was increased from 0.9.3 to 1.7.4, which has an incompatible database structure. Therefore, the data stored in Consul has to be exported before the update and imported again after the update.

Before updating SEAL Operator/SEAL Print Client, export the Consul data. For more information about exporting the data, refer to Administrate the System Configuration.
Remove all files from the /opt/seal/data/seal-consul-agent directory.

After the Update (1.2.0)¶

After the update, start seal-consul-agent, refer to Administrate Services.
Import the data exported before the update, refer to Administrate the System Configuration.

Update SEAL Operator/SEAL Print Client¶

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 Operator - 1.3.1.258 - rpm folder. It is saved as Operator - 1.3.1.258 - rpm.zip.
Extract Operator - 1.3.1.258 - rpm.zip.
Switch to the Operator - 1.3.1.258 - rpm directory and start the installation of the packages contained there:
```
cd "Operator - 1.3.1.258 - rpm"
```
```
sudo sh install.sh
```

Update the node-p4rest Service¶

The following steps are only required if the PLOSSYS netdome connector is used in your installation.

Execute the following steps on the server on which the PLOSSYS netdome system has been installed:

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 node-p4rest-5.3.2-405.x86_64.rpm file from the SEAL Systems delivery platform. It is saved as node-p4rest-5.3.2-405.x86_64.rpm.

Install node-p4rest-5.3.2-405.x86_64.rpm.

RHEL:

sudo yum install node-p4rest-5.3.2-405.x86_64.rpm

SUSE:

sudo zypper install node-p4rest-5.3.2-405.x86_64.rpm

Hint - configuration

The system variables set during the installation are not overwritten when updating.

After the Update (5.3.2)¶

After the update the following configuration entries need to be updated:

The configuration entry ID_PROVIDER_CERT has to be removed.
The configuration entry AUTH_ISSUER_URL has to be added.

Manually Steps After Updating the SEAL Operator/SEAL Print Client Server to 1.3.0¶

With SEAL Operator/SEAL Print Client 1.3.0, the MongoDB service has been replaced by a newer incompatible version. Therefore, the MongoDB data exported before updating has to be re-imported. For how to do this, refer to the SEAL-specific MongoDB documentation.