Danish Fisheries Agency: Fishery Service Client
=================

Fishery Service Client can be used to report sales notes and landing declarations to The Danish Fisheries Agency.
Fishery Service Client sends xml documents encrypted and secured to the Danish Fisheries Agency backend: Fishery Service.

Fishery Service Client supports two modes: File mode and service mode. 

In file mode it is possible to place xml-files in a folder. The Fishery Service Client will pick up the files and send 
them to the Fishery Service backend using secure SOAP Web Services.
In service mode, the Fishery Service Client exposes a local SOAP web service that developers can integrate to.
The Fishery Service Client will then, transparently for the developer, forward xml documents to the Fishery Service using encrypted and secure SOAP Web Services.

A comprehensive User Guide is available at https://fiskeristyrelsen.dk/erhvervsfiskeri/indberetning-og-foering-af-logbog/indberetning-af-fisk/nye-indberetningskrav/

To run the client enter in the directory:
Prerequisites:
	-Configure "naturerhverv.properties" with your own keystore information.
	-Remember that wssec.xml and nes-trust.jks are needed and the path to them should be configured in "naturerhverv.properties")

Filemode:
	(replace version number "2.0.0" with your version)
	java -jar wssec-fs-client-2.0.0.jar 

Service mode:
	(replace version number "2.0.0" with your version) 
	(hosted on http://localhost:9000/FisheryService, wsdl: http://localhost:9000/FisheryService?wsdl))
  	java -jar wssec-fs-client-2.0.0.jar -S

Changelog:  01-10-2018: Added support for sending landing declarations. The client now supports both landing declaration and sales notes.
      		05-02-2014: Changing logging from simple to log4j. Adding audit log.
      		25-11-2013: Changing directory read procedure.
      		04-03-2013: Adding simple logging sl4j-log framework to distribution.
      		15-01-2013: Configuration and password resolver now also usable for production.
      		19-09-2012: If an SOAP exception (HTTP 500 ) is received the application running correctly.