Update to nJAMS Server 5.2, while upgrading Elasticsearch 6 to 7ΒΆ
When you are on nJAMS Server 5.1 using Elasticsearch 6, the following steps have to be executed in order to update to nJAMS Server 5.2, while upgrading Elasticsearch 6.4 / 6.8 to 7.16:
Caution
Before starting, make sure that your current Elasticsearch 6 cluster is ready to be updated to version 7, i.e., that all indexes are version 6 indexes.
- Stop Indexer and stop Data Provider(s) of your current nJAMS Server 5.1 instance
- Upgrade Elasticsearch cluster 6.4 / 6.8 to version 7.16
- Deploy nJAMS Server 5.1 ES 7 package. This step is required to have a valid running nJAMS Server 5.1 instance with ES 7.
- Optional - Re-index Elasticsearch Indexes from format v6 to v7
- Update to nJAMS Server 5.2 by using nJAMS installer
Upgrade procedure step by step:
(A) Stop Indexer and Data Provider(s): | |
---|---|
|
|
(B) Upgrade Elasticsearch Cluster to version 7.16: | |
|
|
(C) Deploy nJAMS Server 5.1 ES 7 package: | |
Your nJAMS Server 5.1 instance is now running with upgraded Elasticsearch cluster. |
|
(D) Optional - Re-index existing indexes: | |
This step is optional. You can re-index the indexes from Elasticsearch format v6 into v7. If you just want to search for process executions, filtered by time or domain object, you can skip this step. If you want to be able to search for event data of the past like payload, stacktrace, activity duration, etc., you have to re-index all existing indexes. Please refer to chapter How to re-index existing indexes for more informaton. |
|
(E) Update nJAMS Server 5.1 to 5.2: | |
nJAMS Server 5.2 is ready to continue processing log messages. |