Revision 7262
Added by ben leinfelder about 12 years ago
| docs/user/metacat/source/dataone.rst | ||
|---|---|---|
| 176 | 176 |
private key that is used to authenticate this node within DataONE. |
| 177 | 177 |
|
| 178 | 178 |
.. Note:: |
| 179 |
For Tier 2 deployments and above, the Metacat Member Node must have Apache configured to request |
|
| 180 |
client certificates. Detailed instructions are included at the end of this chapter. |
|
| 181 | 179 |
|
| 180 |
For Tier 2 deployments and above, the Metacat Member Node must have Apache configured to request |
|
| 181 |
client certificates. Detailed instructions are included at the end of this chapter. |
|
| 182 |
|
|
| 182 | 183 |
The ``Enable DataONE Services`` checkbox allows the administrator to decide whether to |
| 183 | 184 |
turn on synchronization with the DataONE network. When this box is unchecked, the |
| 184 | 185 |
DataONE Coordinating Nodes will not attempt to synchronize at all, but when checked, |
| ... | ... | |
| 217 | 218 |
Once these parameters have been properly set, us the ``Register`` button to |
| 218 | 219 |
request to register with the DataONE Coordinating Node. This will generate a |
| 219 | 220 |
registration document describing this Metacat instance and send it to the |
| 220 |
Coordinating Node registration service, which will return a unique Node Identifier |
|
| 221 |
which will be recorded by Metacat. At that point, all that remains is to wait for |
|
| 221 |
Coordinating Node registration service. At that point, all that remains is to wait for |
|
| 222 | 222 |
the DataONE administrators to approve the node registration. Details of the approval |
| 223 | 223 |
process can be found on the `DataONE web site`_. |
| 224 | 224 |
|
| ... | ... | |
| 306 | 306 |
|
| 307 | 307 |
.. _CNReplication.setReplicationPolicy: http://releases.dataone.org/online/d1-architecture-1.0.0/apis/CN_APIs.html#CNReplication.setReplicationPolicy |
| 308 | 308 |
|
| 309 |
|
|
| 310 |
Generating DataONE System Metadata |
|
| 311 |
---------------------------------- |
|
| 312 |
When a Metacat instance becomes a Member Node, System Metadata must be generated for the existing content. |
|
| 313 |
This can be invoked in the Replication configuration screen of the Metacat administration interface. Initially, |
|
| 314 |
Metacat instances will only need to generate System Metadata for their local content (the ``localhost`` entry). |
|
| 315 |
In cases where Metacat has participated in replication with other Metacat servers, it may be useful to generate System Metadata |
|
| 316 |
for those replica records as well. Please consult both the replication partner's administrator and the DataONE administrators before |
|
| 317 |
generating System Metadata for replica content. |
|
| 318 |
|
|
| 319 |
.. figure:: images/screenshots/screen-dataone-replication.png |
|
| 320 |
:align: center |
|
| 321 |
|
|
| 322 |
The replication configuration screen for generating System Metadata. |
|
| 323 |
|
|
| 309 | 324 |
Apache configuration details |
| 310 | 325 |
---------------------------- |
| 311 | 326 |
These Apache directives are crucial for Metacat to function as a Tier 2+ Member Node |
Also available in: Unified diff
update MN registration screen shot and amend instructions that say a nodeId will be assigned during registration.
add section about generating SM for a new Member Node that has existing Metacat data.