2 Administering Oracle Spatial Studio

Administering Oracle Spatial Studio involves certain actions that must be performed before non-administrative users can work with spatial data.

If you are an administrative user of Spatial Studio, you must:

• Download the Oracle Spatial Studio application from Oracle Technical Resources (formerly called Oracle Technology Network) and install it.
• Set up a database schema to be the Spatial Studio schema, that is, to hold metadata for Spatial Studio.

  The Spatial Studio schema can be either an existing database schema in which Spatial Studio metadata will be added, or a newly created schema that will be used only for Spatial Studio.

• Configure the newly installed Spatial Studio application.

  When the installation and configuration actions are completed, users can connect to the database, start Spatial Studio, and use its features.

Note:

The Spatial Studio application can be downloaded in either of the following formats:

• Quick Start: A ready-to-run standalone application packaged in a zip file containing what you need to launch the Spatial Studio web application on your desktop. (You will still need to have JDK 8 64-bit, update 181 or later installed on your desktop, because no Java kit is bundled with this kit.)

  Quick Start is well suited for personal and development use.

• A WLS-optimized EAR (Enterprise Application aRchive) file. This .ear file can be deployed to an existing WebLogic Server domain administered by an organization's WLS or middleware administrator.

  This is the recommended installation and deployment method if you intend for multiple end users to access the same Spatial Studio web application.

A given person or database user can be both an administrative user and a non-administrative user, or can be only an administrative user or a non-administrative user.

• Prerequisites and Recommendations for Spatial Studio
  This section describes the prerequisites and recommendations that apply for using Spatial Studio.
• Downloading and Installing Spatial Studio
  Spatial Studio must be downloaded and installed before anyone can use it to perform interesting work on spatial data.
• Upgrading Spatial Studio
  This section describes the process to upgrade your existing Oracle Spatial Studio deployment to 24.1.0.
• Setting Up the Spatial Studio Metadata Schema
  You must set up a database schema to be the Spatial Studio schema, which will hold metadata used by the Spatial Studio application.
• Connection Requirements for Database Users of Spatial Studio
  This section describes the connection requirements for database users to work on Spatial Studio.
• Changing the Configuration Using the sgtech_config.json File
  This section describes the configuration of important properties in sgtech_config.json file.
• Recovery from Lost Master Key
  If you accidentally delete or replace the sgtech_config.json file, then the master key is lost and the Spatial Studio application will throw an error.
• Enabling IDCS as Identity Provider in Spatial Studio
  Starting from Oracle Spatial Studio Release 22.1.0, you can log into your Spatial Studio instance using users already managed by your own Oracle Cloud tenancy's IDCS identity domain.
• Mapping External User Principals to Built-In Spatial Studio Roles
  Spatial Studio supports mapping IDCS and other identity provider principals to the Spatial Studio built-in roles. This enables dynamically granting permissions to users by using custom groups, for instance.
• Moving the Spatial Studio Metadata Schema
  You can move your Spatial Studio metadata schema from one database to another.
• Using a CA-Signed SSL Certificate in the Quick Start Installation
  The Spatial Studio Quick Start installation typically comes with a self-signed certificate for handling SSL or HTTPS URL connection encryption.