Configuring the WFS Engine

16.2 Configuring the WFS Engine

This topic focuses on the WFS-specific configuration and deployment actions.

Before following steps in this topic, be sure you understand the information in Deploying and Configuring Spatial Web Services and have performed any necessary operations.

Parent topic: Web Feature Service (WFS) Support

16.2.1 Editing the WFSConfig.xml File

In the Service Configuration tab of the WFS administration console, “uncomment” and modify as needed. Consider the following:

The logging levels can be OFF, SEVERE, WARNING, INFO (the default), CONFIG, FINE, FINER, FINEST, or ALL. The default value is INFO.

size_limit specifies an approximate maximum amount to write (in MB) to any one file. If the value is zero, then there is no limit. The default value is 10

file_count specifies how many output files to cycle through. The default value is 10.
Proxy configuration allows you to control URLs generated by the Spatial Web Services server. A useful scenario is when an HTTP Proxy Server receives requests from users and passes them to WebLogic Server, to control and protect access to a server on a private network
Optionally, uncomment the wfs_query_timeout element to specify the query timeout value, which is used when a server-side locking API is called. The value can be a non-negative integer, and its unit is seconds. The default value is 10 seconds.
Optionally, uncomment the wfs_lock_expiry element to configure the default WFS lock expiry value, which is the expiration time in minutes for WFS locks, if lock expiry value is not explicitly specified in GetFeatureWithLock or LockFeature requests. The default value is 4 minutes.
Optionally, uncomment gml_consider_coordinate_axis_sequence_ordering and set it to the value 1 if the spatial reference system (SRS) should be checked for whether ordinates need to be reversed for x,y coordinates when generating the GML.
The wfs_xsd_loc_url, wfs_ex_xsd_loc_url, and gml3_xsd_loc_url elements are deprecated and not used anymore.

Parent topic: Configuring the WFS Engine

16.2.2 Data Source Setup for the WFS Engine

Note:

In release 19c and earlier, can only have one WFS instance configured; but in release 21c and later, each database schema can be configured as a WFS instance. For information about updating a WFS instance from a release before 21c to release 21c (or later), see Updating a WFS Instance from an Oracle Database for a Release Before 21c to Release 21c or Later.

To set up a data source for the WFS Engine:

Perform the steps explained in Adding a WebLogic Data Source.
Configure the database schema following the step depending on your database version.
For Release 19c and Earlier:

Each database can have only one schema configured for WFS, which corresponds to one data source in WebLogic Server. However, you can have multiple data sources configured for WFS in WebLogic. Each data source can be accessed through a different URL, where the last part of the URL corresponds to the data source name configured in WebLogic Server. The following is an example link with a WLS data source name wfsdata1:
```
http://localhost:80/oraclespatial/wfs/wfsdata1?service=WFS& version=1.0.0&request=GetCapabilities
```
For Release 21c and Later:

Run the following command using the same user previously configured as a WLS data source:
```
Execute mdsys.sdo_wfs_process.init;
```
Effective with Oracle Database release 21c, each database can have multiple schemas configured for WFS. Each data source can be accessed through a different URL, where the last part of the URL corresponds to the data source name configured in WebLogic Server. The following is an example link with a WLS data source name wfsdata1:
```
http://localhost:80/oraclespatial/wfs/wfsdata1?service=WFS&version=1.0.0&request=GetCapabilities
```

After the WFS Engine is deployed and data source is created, you can test the deployment with WFS Engine test queries, such as one of these GetCapabilities queries:

For WFS 1.0.0:

http://<machine-name:port>/oraclespatial/wfs/<data source name>?request=GetCapabilities&service=WFS&version=1.0.0

For WFS 1.1.0:

http://<machine-name:port>/oraclespatial/wfs/<data source name>?request=GetCapabilities&service=WFS&version=1.1.0

Parent topic: Configuring the WFS Engine