Updating SEAL Elastic Stack¶

Overview¶

The update consists of a server and a client part which you have to update separately.

Server:

The server part includes Elasticsearch and Kibana. You have to update it on the management server.
Client:

The client part contains Filebeat. You have to update it on the PLOSSYS 5 server.

Elasticsearch is set up as a separate service like Kibana and Filebeat.

Therefore the directory structure of Elasticsearch changes.
The content of the current database is transferred automatically during the update.
The name of the corresponding service changes from elasticsearch to seal-elasticsearch.

We strongly recommend you to

back up the Elasticsearch database as described in Source System: Creating Complete Snapshots/Backups and
make screenshots of the dashboards and indices in the discover view.

This allows a quick overview whether the update succeeded.

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 SEAL Elastic Stack - 7.17.3.250 - msi folder. It is saved as SEAL Elastic Stack - 7.17.3.250 - msi.zip.
Extract SEAL Elastic Stack - 7.17.3.250 - msi.zip.
In a PowerShell (Administrator), change to the SEAL Elastic Stack - 7.17.3.250 - msi\server directory and start installing the packages:
```
cd "SEAL Elastic Stack - 7.17.3.250 - msi\server"
```
```
Set-ExecutionPolicy Bypass -Scope Process -Force; .\install.ps1
```

Open the required firewall ports for necessesary services:

Set-ExecutionPolicy Bypass -Scope Process -Force; .\firewall.ps1

Change to the configuration directory of seal-elasticsearch:

cd "C:\ProgramData\SEAL Systems\config\seal-elasticsearch"

In an editor, compare the new elasticsearch.yml configuration file to the old elasticsearch.yml.install-bak configuration file.

Add your customer-specific changes, e. g. path.repo or xpack.security.enabled.

For details on the general configuration, see Configuring Elasticsearch.
Change to the common configuration directory:
```
cd "C:\ProgramData\SEAL Systems\config"
```
In an editor, compare the new kibana.yml configuration file to the old kibana.yml.install-bak configuration file.

Add your customer-specific changes, e. g. elasticsearch.username or elasticsearch.password.
Make sure that path.data is set. Uncomment the corresponding line or enter the following line in the kibana.yml file, if necessary:
```
path.data: "${ProgramData}/SEAL Systems/data/seal-kibana"
```
Hint - path.data setting moved

In preparation for future versions, path.data is now set in the kibana.yml file instead of the service configuration.

For details on the general configuration, see Configuring Kibana.
Start Elasticsearch:
```
start-service seal-elasticsearch
```
Start Kibana:
```
start-service seal-kibana
```
Caution - long duration

If you start Kibana for the first time after the update this may take very long. Do not stop the starting process, just wait until it is finished.
Update the necessary database configuration as described in Configuration via Script.

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 SEAL Elastic Stack - 7.17.3.250 - msi folder. It is saved as SEAL Elastic Stack - 7.17.3.250 - msi.zip.
Extract SEAL Elastic Stack - 7.17.3.250 - msi.zip.
In a PowerShell (Administrator), change to the SEAL Elastic Stack - 7.17.3.250 - msi\client directory and start installing the packages:
```
cd "SEAL Elastic Stack - 7.17.3.250 - msi\client"
```
```
Set-ExecutionPolicy Bypass -Scope Process -Force; .\install.ps1
```

Change to the configuration directory:

cd "C:\ProgramData\SEAL Systems\config"

In an editor, compare the new filebeat.yml configuration file to the old filebeat.yml.install-bak configuration file and add your customer-specific changes.
Start SEAL Filebeat:
```
start-service seal-filebeat
```

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 SEAL Elastic Stack - 7.17.3.250 - msi folder. It is saved as SEAL Elastic Stack - 7.17.3.250 - msi.zip.
Extract SEAL Elastic Stack - 7.17.3.250 - msi.zip.
In a PowerShell (Administrator), change to the SEAL Elastic Stack - 7.17.3.250 - msi\client-p4 directory and start installing the packages:
```
cd "SEAL Elastic Stack - 7.17.3.250 - msi\client-p4"
```
```
Set-ExecutionPolicy Bypass -Scope Process -Force; .\install.ps1
```

Change to the configuration directory:

cd "C:\ProgramData\SEAL Systems\config"

In an editor, compare the new filebeat-p4-accounting.yml configuration file to the old filebeat-p4-accounting.yml.install-bak configuration file and add your customer-specific changes.

Start SEAL Filebeat:

start-service seal-p4-accounting-filebeat

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 SEAL Elastic Stack - 7.17.3.250 - msi folder. It is saved as SEAL Elastic Stack - 7.17.3.250 - msi.zip.
Extract SEAL Elastic Stack - 7.17.3.250 - msi.zip.
In a PowerShell (Administrator), change to the SEAL Elastic Stack - 7.17.3.250 - msi\client-operator directory and start installing the packages:
```
cd "SEAL Elastic Stack - 7.17.3.250 - msi\client-operator"
```
```
Set-ExecutionPolicy Bypass -Scope Process -Force; .\install.ps1
```

Change to the configuration directory:

cd "C:\ProgramData\SEAL Systems\config"

In an editor, compare the new filebeat-operator.yml configuration file to the old filebeat-operator.yml.install-bak configuration file and add your customer-specific changes.
Start SEAL Filebeat:
```
start-service seal-operator-filebeat
```

Use your screenshots to check, whether the database content has been transferred successfully.
- If so, delete the old database directory. You have to delete it manually, as it not deleted by uninstalling the old elasticsearch service:
```
rmdir  "C:\ProgramData\Elastic\Elasticsearch\data\nodes"
```
- If not, you have to
  - delete the corrupted indices manually and
  - restore the data from the backup made before updating
    
    For details on the restoration, see Target system: Complete Recovery from a Full Backup.
Then check again, whether the database is ok.
Several configuration files are transferred automatically and saved in the new directory structure and named *.imported.

Check the configuration parameters mentioned in this documentation for correctness. The old and new configuration files differ especially under Windows.

For details on the configuration, see Configuring Elasticsearch.