Upgrading to Oracle Spatial Studio 22.1

Oracle Spatial Studio provides no-code access to spatial data preparation, analysis and visualization. It allows you to work with data already in Oracle Datadata or load from common spatial and non-spatial formats. Non-spatial data can be prepared by address geocoding or coordinate indexing and then used for spatial analysis and mapping. Results may be shared as interactive maps as well as GeoJSON endpoints for progammatic integration. An overview of new features in Spatial Studio 22.1 can be found here.

The following explains the steps to upgrade an existing Spatial Studio deployment to version 22.1.

Part 1 - Prepare for Upgrade

1. Stop all Spatial Studio instances.

2. Make a full backup of the following artifacts:

1.1 Repository database schema

1.2 Working-directory, typically ~/.sgtech

1.3 sgtech_config.json configuration file, typically located in the working-directory

3. Download Spatial Studio 22.1 from the Spatial Studio downloads page and upload to the host to be upgraded

Part 2 - Upgrade Spatial Studio Deployment

There are two scenarios for upgrading: in-place, when upgrading an existing host; and out-of-place, when deploying to a new host. In both cases, the upgraded Spatial Studio deployment uses the existing repository database schema.

In-place upgrade

1. If upgrading from Spatial Studio 20.x then skip this step. If upgrading from Spatial Studio 19.x or earlier, then remove all pre-cached tiles by deleting the cache subfolder from Spatial Studio's working-directory

i.e., rm -R ~/.sgtech/cache

2. Redeploy the app

2.1 If EAR deployment, follow the instructions of your application server to delete the old deployment version, deploy the new version and start the application.

2.2 If Quick Start, rename the old Quick Start folder, expand the downloaded ZIP file and execute start.sh (Linux) or start.cmd (Windows).

Out-of-place upgrade

1. Create the working-directory in new host

i.e., mkdir ~/.sgtech

2. To preserve the master_seed property, copy over the sgtech_config.json configuration file from old host into the new host's working-directory

i.e., cp old/sgtech_config.json ~/.sgtech

If master_seed is lost, all Connection passwords will be broken. If this occurs, proceed with the upgrade, then log into the upgraded Spatial Studio instance later and edit each connection to re-connect.

3. Deploy the app

3.1 If EAR deployment, follow the instructions of your application server to deploy the new version and start the application.

3.2 If Quick Start, simply expand the downloaded ZIP file and execute start.sh (Linux) or start.cmd (Windows).

Upon starting Spatial Studio 22.1, the repository database schema will automatically be upgraded. This should be completed within a couple of minutes.

Part 3 - If upgrading from Spatial Studio 20.x or ealier, refresh Dataset statistics

◉ You must refresh statistics for all Datasets if upgrading from Spatial Studio 20.x or ealier.

◉ If you have a small number of Datasets, you can go to the Datasets page and select Update statistics from the action menu for each dataset:

◉ Alternatively, if you have access to Bash shell, you can update all statistics using an automation script.

    ◉ Download the script and unzip update_datasets.sh

    ◉ Log into Studio as admin, and generate an Access Token with read-write permissions as explained in this post.

    ◉ Execute the script, passing the OAuth URL of the upgraded host and the Access Token

i.e. (token abbreviated for simplicity), ./update_datasets.sh http://mystudio:8080/spatialstudio/oauth/v1 eyJ0e...xwgg

    ◉ Wait for the script to complete the updates, then delete the Access Token from Spatial Studio.

Source: oracle.com