Revision 6989
Added by Matt Jones about 12 years ago
dataone.rst | ||
---|---|---|
158 | 158 |
registers with the DataONE Coordinating Nodes (when you click 'Register' at the |
159 | 159 |
bottom of this form), the Node Identifier is automatically set. **It is critical that |
160 | 160 |
you not change the Node Identifier**, as that will break the connection with the |
161 |
DataONE network. The ability to edit this field is only provided for the rare case
|
|
161 |
DataONE network. Changing this field should only happen in the rare case
|
|
162 | 162 |
in which a new Metacat instance is being established to act as the provider for an |
163 | 163 |
existing DataONE Member Node, in which case the field can be edited to set it to |
164 | 164 |
the value of a valid, existing Node Identifier. |
... | ... | |
167 | 167 |
proper operation of the node. To act as a Member Node in DataONE, you must obtain |
168 | 168 |
an X.509 certificate that can be used to identify this node and allow it to securely |
169 | 169 |
communicate using SSL with other nodes and client applications. This certificate can |
170 |
either be obtained from the DataONE Certificate Authority, or from a commercial
|
|
171 |
provider of certificates. Once you have the certificate in hand, use a tool such
|
|
170 |
be obtained from the DataONE Certificate Authority.
|
|
171 |
Once you have the certificate in hand, use a tool such |
|
172 | 172 |
as ``openssl`` to determine the exact subject distinguished name in the |
173 | 173 |
certificate, and use that to set the Node Subject field. Set the Node |
174 | 174 |
Certificate Path to the location on the system in which you stored the |
175 |
certificate file. |
|
175 |
certificate file. Be sure to protect the certificate file, as it contains the |
|
176 |
private key that is used to authenticate this node within DataONE. |
|
176 | 177 |
|
177 |
The ``Synchronize`` checkbox allows the administrator to decide whether to turn on
|
|
178 |
synchronization with the DataONE network. When this box is unchecked, the DataONE
|
|
179 |
Coordinating Nodes will not attempt to synchronize at all, but when checked, then
|
|
180 |
DataONE will periodically contact the node to synchrnize all metadata content. |
|
178 |
The ``Enable DataONE Services`` checkbox allows the administrator to decide whether to
|
|
179 |
turn on synchronization with the DataONE network. When this box is unchecked, the
|
|
180 |
DataONE Coordinating Nodes will not attempt to synchronize at all, but when checked,
|
|
181 |
then DataONE will periodically contact the node to synchrnize all metadata content.
|
|
181 | 182 |
To be part of the DataONE network, this box must be checked as that allows |
182 | 183 |
DataONE to receive a copy of the metadata associated with each object in the Metacat |
183 | 184 |
system. The switch is provided for those rare cases when a node needs to be disconnected |
... | ... | |
191 | 192 |
hour (such as ``11``) and the ``Minutes`` field to a concrete value like``15``, |
192 | 193 |
which would change the schedule to synchronize at 11:15 am daily. |
193 | 194 |
|
195 |
The Replication section is used to configure replication options for the node |
|
196 |
overall and for objects stored in Metacat. The ``Accept and Store Replicas`` |
|
197 |
checkbox is used to indicate that the administrator of this node is willing to allow |
|
198 |
replica data and metadata from other Member Nodes to be stored on this node. We |
|
199 |
encourage people to allow replication to their nodes, as this increases the |
|
200 |
scalability and flexibility of the network overall. The three "Default" fields set |
|
201 |
the default values for the replication policies for data and metadata on this node |
|
202 |
that are generated when System Metadata is not available for an object (such as when |
|
203 |
it originates from a client that is not DataONE compliant). The ``Default Number of |
|
204 |
Replicas`` determines how many replica copies of the object should be stored on |
|
205 |
other Member Nodes. A value of 0 or less indicates that no replicas should be |
|
206 |
stored. In addition, you can specify a list of nodes that are either preferred for |
|
207 |
use when choosing replica nodes, or that are blocked from use as replica nodes. |
|
208 |
This allows Member Nodes to set up bidirectional agreements with partner nodes to |
|
209 |
replicate data across their sites. The values for both ``Default Preferred Nodes`` |
|
210 |
and ``Default Blocked Nodes`` is a comma-separated list of NodeReference identifiers |
|
211 |
that were assigned to the target nodes by DataONE. |
|
212 |
|
|
194 | 213 |
Once these parameters have been properly set, us the ``Register`` button to |
195 | 214 |
request to register with the DataONE Coordinating Node. This will generate a |
196 | 215 |
registration document describing this Metacat instance and send it to the |
Also available in: Unified diff
Updated configuration documentation in admin guide for Metacat DataONE section. Changed links in configuration utility to point at the Admin guide.