Metacat

create docid-guid mapping during replication if it does not exist. we were [incorrectly] assuming that there would be SM coming with the document info that would fill this information in, but for traditional non-MN Metacat deployments there is no SM to provide a mapping. In this case we use the docid as the guid.

stream the replication "update" response rather than building up a complete list in a stringbuffer. prompted by findings on t he CN: https://redmine.dataone.org/issues/3141

remove unused "dataonelogger"

remove possibility for infinite loop in case data replication is not configured for the server and a data file is encountered (yikes!)

added logging debug statements to see where the replication timeout might be occurring.

only look up the client timeout property once, not every time we make a call
https://redmine.dataone.org/issues/3078

configurable replication client timeout
https://redmine.dataone.org/issues/3078

stack trace the HZ put exception during CN-CN replication

additional debugging statements for CONCURRENT_MAP_PUT error during CN-CN replication.

instead of generating SM and ORE maps during dataone configuration/MN registration, moved this all to the replication admin screen where we can target generation for specific nodes. That way it's more controlled as to when and where we generate DataONE required content....