1Spatial Management Suite components require access to a database to store configuration data.
Note: Depending on the components being installed, an Oracle, SQL Server or PostgreSQL database can be used. Please refer to the individual component chapters for clarification.
Users and schemas must be created in advance of product installation, during which you will be prompted for database locations, schema names and passwords.
Note: If you are using a PostgreSQL database, it is recommended that you create these as databases in which the public schema will be used to create the tables.
The following table suggests name for the schemas to provide consistency, but for security purposes, does not suggest a password.
|
Schema |
Use |
Suggested name |
|---|---|---|
|
For specific 1Spatial Management Suite products |
||
|
1Plan Repository |
Storing configuration for 1Plan as well as all job metadata |
sms_plan |
|
1Exchange Repository |
Stores 1Exchange configuration and job package metadata |
sms_exchange |
|
1Generalise Repository |
Stores 1Generalise configuration |
sms_generalise |
|
1Exchange GO Loader database |
GO Loader is a component used by 1Exchange and normally it is given its own schema |
sms_goloader |
|
1Exchange GO Publisher database |
GO Publisher is another component used by 1Exchange and again it is normally is given its own schema |
sms_gopublisher |
|
1Integrate Repository |
Stores the repository of 1Integrate rules and is used to store data validation sessions |
sms_integrate |
|
1Workflow Repository |
Stores the configuration for the 1Workflow component |
sms_workflow |
|
For all 1Spatial Management Suite products |
||
|
Feature data |
The main location of the feature data being managed by 1SMS. This value is used by 1Transact to make calls to Oracle Workspace Manager and is the main schema from which data will be read from and written to by 1Exchange. Note: During 1Exchange configuration (see 1Exchange Product Configuration ), GO Publisher and GO Loader products can override this in order to read and write from different schemas within the same database. |
Note: This usually already exists and will be site-specific. Tables to be managed must be version-enabled. |
|
Security schema |
Storage space for security tokens created when users log on to applications |
sms_security |
|
JMS schema |
Storage space for the database persisted JMS messages for 1Exchange, 1Generalise, 1Transact, and 1Integrate. |
sms_messaging |
Configuring Oracle
All necessary tables will be created within the schemas.
Normally, all schemas are created in the same database instance, and the GO Loader and GO Publisher schemas must be in the same instance as the feature data. The database location is prompted whenever the schema user name or password is prompted.
This database location must be in the jdbc thin client format: jdbc:oracle:thin:@[hostname]:[port]:[service_name]
Configuring PostgreSQL
All necessary tables will be created within the databases, with the exception of JMS.
Connect to the JMS database and create a table within it using the following SQL:
\c sms_jms_store
CREATE TABLE mstransact_wlstore(
id INTEGER NOT NULL PRIMARY KEY,
type INTEGER NOT NULL,
handle INTEGER NOT NULL,
record BYTEA NOT NULL);
