...
Solr Indexing
The solr indexer uses fedoraFedora's fcr:transform 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")
...
This will reindex both Solr and the external triplestore, starting at the /objects node in fedoraFedora. To start at the root node in fedoraFedora, you would POST to localhost:9080/reindexing/, while to start at the node /a/b/c/d, you would POST to localhost:9080/reindexing/a/b/c/d
...
The serialization service allows objects in fedora Fedora to be written to a specified disk location in any MIME type fedora 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.
When this service is enabled, it will write any new or changed object's description to disk. It listens to fedora Fedora and only operates on objects that have been created, modified or deleted. If an object was created before this service was enabled and is unchanged, it will not be written to disk. This service exposes an activemq queue for initiating serialization of fedora Fedora objects that might not otherwise get written to disk.
If an object is deleted from fedoraFedora, the serialized description and/or binary will be removed as well.
For more details see: https://github.com/fcrepo4-exts/fcrepo-camel-toolbox/tree/master/fcrepo-serialization