...
All of these services can be deployed in a web container such as Tomcat or Jetty. Alternately, they can be deployed in an OSGi container such as Karaf. Deployment and configuration instructions are available in the associated README files.
Solr Indexing
The solr indexer uses Fedora's fcr:transform service the LDPath service to convert RDF documents to JSON. A default transformation program can be specified in the service configuration (e.g. default or myTransformation). It is also possible to override the default transformation program by assigning an RDF property to particular documents: <> indexing:hasIndexingTransformation "specialTransform". Furthermore, one can choose to index only certain documents from the repository. By identifying certain documents as <> a indexing:Indexable and enabling the indexable.predicate configuration value, only those resources will be indexed. (For Tomcat/Jetty-deployed applications, this can be enabled by setting JAVA_OPTS="-Dfcrepo.onlyIndexableObjects=true")
...
The triplestore indexing service runs just like the Solr Indexing service, pushing all changes from the repository into an external triplestore. Both Fuseki, Sesame and Sesame BlazeGraph have been used successfully with this service. Like with the Solr Indexing service, it is possible to identify certain objects as "Indexable" by setting an rdf:type as indexing:Indexable. (One must also enable this filtering, as described above).
...
By sending a GET request to the reindexing service, you will retrieve a short summary of its usage.Anchor
Serialization Service
The serialization service allows objects in Fedora to be written to a specified disk location in any MIME type Fedora supports. One can decide whether or not to include binaries in the serialization, but keep in mind that they may take up a considerable amount of disk space.
...