...
Elasticsearch 7.2.1 -> 7.9.3. Elasticsearch 7.2.1 needs to be replaced by version 7.9.3. To do this, version 7.2.1 needs to be uninstalled and version 7.9.3 installed an configured as follows:
Stop the Elasticsearch 7.2.1 service.
If the data directory is located inside the installation path of Elasticsearch 7.2.1, move it outside and/or make a backup.
Backup the <elasticsearch>\config\elasticsearch.yml and <elasticsearch>\config\built-in.usr files.
Uninstall Elasticsearch 7.2.1.
Install Elasticsearch 7.9.3 as described here: Installation Guide Version 7.0
Before you start the service:
- Transfer custom settings from the backed-up elasticsearch.yml file to the newly installed file.
- Copy / move the backed-up built-in.usr file to the new <elasticsearch>\config folder.
- If needed, move the data directory to the desired location.
- Make sure the "path.data" property points to the (moved) data directory of Elasticsearch 7.9.3.
Start the service and check that the cluster state is green and contains the yuuvis RAD indices.
...
- For Oracle DBs only:
- A new connection property needs to be added to the core-service jdbc connection string
- Open the file <core-service>\standalone\configuration\standalone-full-ha.yml
- Naviagte to the line "<subsystem xmlns="urn:jboss:domain:datasources:5.0">" and there to "<datasource jndi-name="java:/JASDB"..."
- Add a new line under the line "<connection-url>" and write the following: <connection-property name="CatalogOptions">0</connection-property>
- It should now look like this:
- The oracle schema name configuration is removed from the file jas-deployment.xml.
The oracle schema was configurable inside this file by providing a 'use-db-schema' property for the step 'setup-dataaccess'. This property is not used any more and the jas-deployment.xml file is overwritten by the setup on update.
By default, the oracle schema name is equal to the upper case user name and this is now used automatically.
If you have the case / the requirement, that the schema name is different from the upper case user name, please configure it as follows:- Open the file <core-service>\standalone\configuration\standalone-full-ha.yml
- Naviagte to the line "<subsystem xmlns="urn:jboss:domain:datasources:5.0">" and there to "<datasource jndi-name="java:/JASDB"..."
- Add the following new line under the line beginning with "<connection-property": <new-connection-sql>ALTER SESSION SET current_schema=schemaname</new-connection-sql>
Replace 'schemaname' with the name of the schema. (Do not use any quotation marks.)
It should now look like this:
- A new connection property needs to be added to the core-service jdbc connection string
...
- As described in What Is New 7.0 (Removed Features) two functional rights have been deprecated and removed and must be deleted from all roles of a project in the role management in the designer prior to activating it to a 7.x system.
- When checking (validating) a schema in the designer you will see the following validation errors:
- To resolve this, open the "functional rights" view of the affected roles. Uncheck all roles under the "Miscellaneous" section:
Save the project. It can now be activated to a 7.x system.
Note title Warning Do not use this project for 6.x (or below) systems anymore. The removed rights were used by e.g. the management-studio and you might not be able to access it anymore if these rights are missing.
- When checking (validating) a schema in the designer you will see the following validation errors:
- As described in What Is New 7.0 (Removed Features) the deprecated methods GET /api/bpm/process (get "My processes") and GET /api/bpm/process/user (get processes for a certain user, if requester has administrative rights) have been removed.
If they have been used in the project (client scripts, workflow scripts, custom microservices, etc.), their replacement /api/bpm/processes (for "My processes") must be used instead, and corresponding methods in core-service for administrative purposes.
The same applies to the deprecated and removed parameters, as also described in What Is New 7.0
- As described in What Is New 7.0 (Removed Features) ETL configurations using an XML file as the data source (extraction part) will not be supported anymore. Also, the execution of scripts is not possible anymore. Different to version 6.x even already existing configurations will not function anymore. Please preapre an import routine using external tools like talend-jobs or alike before upgrading.
...