This issue may now be addressed upon your convenience @martin-kuba
- The OpenAPI custom web services are available in the GitHub repository:
- https://github.com/SDI4Apps/openapi
- The repository is a Maven Java repository with two target profiles 'remote' and 'local'
- The project compiles to the single distributable openapi.war
- The project depends on three databases being present on the host
- The project depends on settings in profile-specific settings files that are excluded from the repository for obvious security reasons.
- The settings file defines database connection parameters as well as paths to file locations used by the OpenAPI custom web services
- The OpenAPI indexer cron-job task is available in the GitHub repository:
- https://github.com/SDI4Apps/cronindexer.git
- The repository is a Maven Java repository with two target profiles 'remote' and 'local'
- The project compiles to the single executable Jar file 'cronindexer.jar' that includes all dependent libraries to be self-contained.
- The project depends on one database being present on the host
- The project depends on settings in two profile-specific settings files that are excluded from the repository for obvious security reasons.
- The settings file defines database connection parameters as well as paths to file locations used by the OpenAPI custom web services
- The JAR depends on GDAL/OGR being installed on the host server
- The JAR should be executed as a CRON job, every 5 minutes at the outset
- The JAR must be executed setting paths to shared JNI libraries as well as extending the classpath to include 'gdal.jar'
- The executable class is eu.sdi4apps.ftgeosearh
This example shows how the invocation of the cron JAR is done on the 'main' platform server
java -Djava.library.path=/usr/lib/jni/ -cp "cronindexer.jar:/usr/lib/jni/*.so:/usr/share/java/gdal.jar" eu.sdi4apps.ftgeosearch.CronJob
- The JavaScript library is available in the GitHub repository
- https://github.com/SDI4Apps/s4a.js
- The repository is managed using NPM
- The build system is Grunt
- The compiled distribution files are included in the repository (possibly bad practice) under the folder
/dist/
- The library should be available under the path
cdn on the
This issue may now be addressed upon your convenience @martin-kuba
This example shows how the invocation of the cron JAR is done on the 'main' platform server
java -Djava.library.path=/usr/lib/jni/ -cp "cronindexer.jar:/usr/lib/jni/*.so:/usr/share/java/gdal.jar" eu.sdi4apps.ftgeosearch.CronJob/dist/cdnon the