GO Loader Aviation 1.2 is here! Take a look at what's new.
Skip to end of metadata
Go to start of metadata

Welcome

Audience:

This document is intended for technical users who wish to set up and configure a WFS service for end users.

System Requirements:

Before using GO Publisher WFS, please ensure that your system meets the Minimum Hardware and Software Requirements.

The following will apply to users upgrading to version 4.0.0 or later:

  1. WFS Query url has changed. E.g: ../GOPublisherWFS? to ../GOPublisherWFS/wfs?
  2. The HSQL DB needs to be removed to allow for an automated upgrade:
    1. New column (ENDPOINT) is required to support stored queries on multiple services
    2. This is needed even if you don’t use Stored Queries

To delete an existing query store you first need to locate the HSQL file, the location of which is documented here. The query store will be prefixed with the name of your deployed WAR file. Once located you can delete the wfs-storedqueries files related to your WAR file.

Setting up Your WFS

If you have yet to do so, then you can get familiar with WFS basics by reading an Introduction to WFS.

Deployment Options

There are three deployment options for the WFS.

The config store is a directory used to supply the GO Publisher WFS Application war file with the GO Publisher project, schemas, units dictionary and srs translation dictionary. It is seperated from the war file to allow for changing configuration without having to do an undeploy and redeploy.

 

Option One: File System based config store 

This option is the more common deployment, it involves storing the config in a file system *on the server*.

It allows you to interact with the config directly, without needing to use a RESTful API.

Pros:

  • Setup is simpler as there are less components
  • More secure as you need access to the file system
  • Easier to configuration manage using a tool such as Puppet

Cons:

  • Need to provide access to the file system
  • Dynamic deployment (changing config) requires system access

 

 

Option Two: Config store and WFS on the same Application Server 

This option is suitable if you want to interact with the Config Store using a RESTful API.

 

Pros:

  • Dynamic deployment is easier

 

Cons:

    • Setup is more complex, due to having to include App Server security.
Option Three: Config store and WFS on separate Application Servers 

This option is suitable if you want to interact with the Config Store using a RESTful API.

 

Pros:

  • Isolation of components
  • Gives ability to horizontally scale GO Publisher WFS separately from the Config Store
  • Dynamic deployment is easier

 

Cons:

  • Extra App Server to manage
  • Setup is more complex, due to having to include App Server security.

 

 

 

 

Advance Settings

Advanced WFS Configuration using GO Publisher section includes advanced concepts for:

  • Security
  • Stored queries
  • RESTful services

Provide managed access to your data by Setting up a RESTful WFS service 

Further Reading

After setting up your WFS, see the GO Publisher WFS User Guide for the operations available for use with GO Publisher WFS and how your WFS can be used within client applications. Examples of the WFS operations supported by GO Publisher WFS are provided.


Next Steps

  1. Check out the GO Publisher WFS Prerequisites.
  2. Configure your WFS settings following this page GO Publisher Desktop WFS Configuration.
  3. Deploy your application by following the GO Publisher WFS Deployment Steps.

Dive Deeper!

Navigate around the product documentation using the tree structure below or on the left hand side panel.

You can also search this documentation space using the search box below: