2. Client Helper Libraries and Configuration

The FilteredPush libraries for php clients can be checked out from the sourceforge svn:

Clients must be configured (via edits to fp/FPConfig.php) to use the network components. Edit this file and set the X509_CERTIFICATE, PRIVATE_KEY and NETWORK_FACADE properties.

X509_CERTIFICATE should be set to the file path of the certificate (pem file) containing the public key for the client and PRIVATE_KEY should be set to the file path of the pem file containing the client's private key. Set the NETWORK_FACADE property to either FPLiteFacade (for FP-Lite deployments) or FPMediumFacade (for FP-Medium deployments).

The rest of the defaults should work with the default single-node deployment of FilteredPush. A summary of all the configuration options can be found below:

• RDFHANDLER_ENDPOINT - the url for the annotation webservice, used for creating new identification annotation rdf/xml
• FPNODE_ENDPOINT - this is the AccessPoint SOAP webservice as part of FP-Medium (for an FP-Lite deployment the default can be used for now)
• SPARQLPUSH_SERVER - sparqlpush server uri
• SPARQLPUSH_CLIENT - sparqlpush client uri
• DS - the dataset that fuseki was started with in the startup script
• SPARQL_ENDPOINT - the uri to the fuseki endpoint
• RESULT_XSLT - the xsl for styling query results and the annotations shown on the Annotations tab in Symbiota (on the Occurrence Record form).
• X509_CERTIFICATE - the pem file (newcert.pem from the example above) that contains the public key for this client
• PRIVATE_KEY - the pem file used by this client (privkey.pem) for signing the rdf/xml
• NETWORK_FACADE - Current network implementation to use (see classes/fp/facades), choices are FPLiteFacade and FPMediumFacade

Once configured, we can deploy the fp directory containing the config and the libraries in FP-PHP-Library/fp to /usr/share/php. Clients (such as Symbiota and Morphbank) will use these libraries when interacting with both FP-Medium and FP-Lite