Data Reindex Web Service

Overview

Fusion Registry contains an index for each Provision Agreement which has data registered against it. The index holds the details on what series exist in the source data, so as new series are added or old ones removed, the index should be rebuilt.

The following table lists the data store type, along with the reindex strategy.

Store	Reindex Strategy
In Memory Database (Fusion Store)	Automatic on data load. Manual Reindex is not required
Registry Managed Database	Automatic on data load. Manual Reindex is only required if series have been manually edited in the database
Mapped Data Store	Automatic when mapped Dataflow is Reindex . If the mapped store is backed by a Fusion Cache, then it will hold a full copy of the dataset in memory. In this condition, and where the data is externally managed, a reindex should be performed whenever the source data changes in order to reflect the change in the Registry.
Externally Managed Database	Reindex when series are added or removed
External File or URL	Reindex when series are added or removed

Re-Index Web Service

Entry Point	/ws/secure/reindexProvision
Access	Restricted to Server Admin
Http Method	POST

The POST Body is a JSON object which contains the URN of the Provision Agreement to reindex:

{
 URN : "ProvisionURN"
}

Response

HTTP 200 with a JSON Response:

{
 Success : true
}