A spatial engine provides access to a service that can perform spatial operations, one of the available spatial engines is for Oracle Spatial.
Namespace
urn:com.cohga.server.spatial.geotools#1.0
Tags
spatialengine
Properties
Name |
Type |
Required |
Description |
id |
string |
yes |
Unique identifier |
dbtype |
'oracle' |
yes |
The name of the driver to use, in this case Oracle |
host |
string |
yes |
The hostname or ip address of the Oracle server |
port |
number |
yes |
The port number that the Oracle instance is running on |
database |
string |
no |
The database parameter for the connection url |
username |
string |
yes |
The userid used when connecting to the database |
password |
string |
yes |
The password used when connecting to the database |
schema |
string |
no |
The schema used when connecting to the database |
Sub-tags
None
Content
None
Notes
No connection pool configuration is provided with this driver, the driver manages the connection pooling itself.
If database
starts with '(' then the format of the connection url will be
jdbc:oracle:thin:@database
If database
starts with '/' then the format of the connection url will be
jdbc:oracle:thin:@//host:portdatabase
else the format of the connection url will be
jdbc:oracle:thin:@host:port:database
Examples
<spatial:spatialengine id="oracle"> <dbtype>oracle</dbtype> <host>oradev</host> <port>1521</port> <user>gis</user> <passwd>hak0rz</passwd> <schema>GIS</schema> </spatial:spatialengine>
<spatial:spatialengine id="sdbeos"> <dbtype>oracle</dbtype> <host>sdbeos</host> <port>1521</port> <database>staging</database> <user>data_viewer</user> <passwd>ENCSSJKXUMJBMTPGEJFGCXCQFXJJZUTMJZJ</passwd> <schema>ASSETS</schema> </spatial:spatialengine>