1Exchange Product Configuration
The Products configuration process allows you to define an Exchange Product. Multiple products can be created, each referencing a GO Publisher Project (.gpp) and a GO Loader Project (.glp) and (optionally) each reading and writing to a different database schema.
Note: In this instance, a Product refers to a configuration file that defines the way that data is published and imported using GO Loader and GO Publisher. For more information please refer to Snowflake documentation.
In turn, these Products are used when configuring Exchange Policies in the 1Exchange administration page (see Exchange Policies).
Note: 1Exchange requires GO Loader Desktop v 1.8 and GO Publisher Desktop v 4.0.
Note: A set of GO Loader and GO Publisher Products can be configured at install time. Any additional products must be configured using this process.
Policy configuration will still need to be performed for these products (including any from the installation process), via the admin page (see Managing Exchange Policies).
In order to perform the product configuration, you will require the following:
Perform 1Exchange Product Configuration
(WebLogic)
-
Launch the Installation Wizard.
-
On the Wizard Options screen, select 1Exchange Product Configuration and click Next to proceed.
-
Enter all required parameters (see 1Exchange Configuration Parameters).
-
Click Configure to begin the configuration.
-
Click Finish once complete.
Note: If more than one Exchange product is required, run the installer again and provide a different product name and different configuration files.
Perform 1Exchange Product Configuration
(Wildfly)
- Open the relevant Command-Line Interpreter (e.g Windows PowerShell) within the .jar directory.
-
Type java -jar [Installation_Filename] -o exchange ] -product
- This will now install the relevant 1Exchange Products for your installation of 1SMS.
1Exchange Configuration Parameters
General |
Translation Config |
(optional) An XML file that specifies translation between GML and Oracle schema and is required to allow conflict resolution.
If this is not specified, any conflict resolution jobs (created when an exchange package tries to modify a feature that has already been modified since the data was extracted) cannot be uploaded.
|
translationConfig.xml |
Product Name |
The name to be given to the GO Loader/GO Publisher product.
Note: This should be a name that is meaningful for the data being loaded, as it will appear in a drop-down list during Policy configuration (see Managing Exchange Policies).
|
|
Feature Schema
Note: These parameters can be used to override the schema from which to read and write the data. If the schema for this product has not previously been set via the installer (or manually via the config.properties file), these parameters will be pre-populated by the Feature Schema settings previously entered into the "Common Settings" section of the installer.
|
JDBC Connection String |
The connection details of the schema in the form jdbc:oracle:thin:
@[hostname]:[port]:[service_name]
|
|
User |
|
|
Password |
|
|
GO Loader |
Project File |
The location of the GO Loader project file (.glp) that has been configured to load the uploaded GML into the feature database tables.
Please contact 1Spatial support for information on creating and configuring this file.
|
|
Schema Folder |
The folder containing the GML Schemas (.xsd) that describe the feature data to be uploaded by GO Loader.
|
|
GO Publisher |
Project File |
The location of the GO Publisher project file (.gpp) that has been configured to extract GML from the feature database tables.
Please contact 1Spatial support for information on creating and configuring this file.
|
|
Schema Folder |
The folder containing the GML Schemas (.xsd) that describe the feature data to be extracted by GO Publisher.
Note: This should be the same Schema Folder specified for the GO Loader configuration
|
|
Root Schema |
Root schema, relative to the Schema folder above.
|
|
Feature Relations |
When loading by reference, an XML file containing the relation between feature classes.
Please contact 1Spatial support for information on creating and configuring this file.
|
|