Story #2720: KNB, LTER, PISCO, ESA, SANPARKS roll out
Extend Metacat's GenerateSystemMetadata to target specific replication targets
We will be generating SystemMetdata in phases depending on which replication targets are registered and synched with the CNs.
First wave: serverLocation=1 (home server, the objects all originated on this server).
N-waves: serverLocation=2...n (when the MN comes online and is synched with the CN. Then we can generate our copies of the SM for the replicas we house for the other MN).
#1 Updated by Ben Leinfelder over 10 years ago
- Status changed from New to In Progress
The class now accepts serverLocation param. How we call this on any particular deployment should probably be investigated. I'm leaning toward ant build, but this requires a source checkout on the server rather than a packed binary distribution.
#3 Updated by Ben Leinfelder over 10 years ago
- Status changed from In Progress to Closed
Both System Metadata and ORE generation have been taken out of the dataone registration/configuration workflow and are now available at any time on a per-replica host basis in the replication configuration screen