Before installing 1Spatial Management Suite, ensure that the following prerequisites have been met (in accordance with the 1Spatial Management Suite Release Notes):
- The appropriate application servers have been configured
- The correct version of Java has been installed
- The database schemas have been set up (see Database Creation)
- Individual component requirements (as necessary)
Installation Package
Unpacking the installation
A single delivery file is provided that includes a zipped installation directory containing the components for which you are licensed along with an installer application.
Unzip the delivery file to an installation directory on your server. It is recommended that this is in a fixed and known location, as the installer produces configuration files and logs that may be useful for your records and will be used by future upgrades to the products.Do not unzip the files within the installation directory, as this is done by the installation application.
1Workflow
1Workflow always requires installation on WebLogic. For information about the 1Workflow WebLogic installation please refer to the 1SMS Installation Guide: WebLogic.
Config.properties file
The installation application reads and writes a config.properties file to record the settings for your installation. This file is a record of your current configuration.
The config.properties file will be written out to the installation directory.
Note: Passwords are encrypted in the config.properties file.
Note: It is important that this file is saved for future use as it will be used when any software upgrade is installed, ensuring that settings are maintained between versions.
Proxy, Load Balancer and Cloud Environments
If you are going to access 1SMS through a proxy, a load balancer or on a cloud environment, then the download URL for 1Exchange job packages may be different to the installed machine name.
Example: 1Exchange is installed on machine1.myCompany.local/1exchange, but proxy access is via 1sms.myCompany.com/1exchange.
To ensure the connection will work as expected, use the Address parameter in the Load Balancing section of the installer to specify the external service address to be used by clients for the download of job packages. For more information, see Load Balancing.
Go Publisher and Go Loader
1Exchange can be configured to use the Snowflake Products Go Loader and GO Publisher.
If using Snowflake as a pre-requisite:
-
You must configure Snowflake before beginning the 1SMS installation process.
-
Additionally, if you are going to utilise the conflict resolution process for any configured Snowflake products, please place each product's associated translation configuration XML file next to the installer with the following name
<product_name>_translationConfig.xml
FME Server can be used for additional conversion of the resulting GML through FME Adaptors (see 1Exchange admin section). Alternatively, FME Server can be used to convert directory from the Oracle data into the format your editing client requires.
Note: 1Exchange requires GO Loader Desktop v 1.8 and GO Publisher Desktop v 4.0.
Snowflake Security
For security purposes, it is recommended that you avoid exposing Snowflake products when deploying 1SMS in a cloud environment.
When installing 1Exchange, set the snowflake.callback.url property to an internal URL such as:
http://[host]:[port]/1exchange/rest
Doing so will ensure any traffic from Snowflake will not leave the network.
Note: The snowflake.callback.url must be set for Kubernetes based cloud deployments.
Note: If this parameter is not set, the URL will be taken from the URL 1Exchange was invoked by.
