Page History

...

1. Edit /etc/exports to allow machineB to see the data archive on machineA (for more information, type "man exports")

   Code Block
   title machineA: /etc/exports
   /Users/me/filemgr/data/archive -network=10.0.0.0 -mask=255.255.255.0

2. Restart the NFS service on machineA

   No Format
   sudo nfsd restart

3. Mount the remote file system on machineB (for more information, type "man mount")

   No Format
   sudo mkdir -p /net/machineA sudo mount -t nfs machineA:/Users/me/filemgr/data/archive /net/machineA

4. Create a symbolic link on machineA

   No Format
   sudo ln -s /Users/me/filemgr/data/archive /net/machineA

5. Edit product-types.xml to use the symbolic link

   Code Block
   title machineA: product-types.xml
   ... <type id="urn:MyProdTypeId" name="MyProdTypeName"> <repository path="file:///net/machineA"/> ...

6. The FileManager should now return file paths that are reachable by machineB.

Wiki MarkupIf your products were already previously ingested, you must update the {{\[FileLocation\]}} metadata element for your ingested products. There are several ways to update the catalog with the new NFS file location:

• Re-ingest, making sure the repository path in product-types.xml uses the NFS mount.
• Re-ingest, using a different Versioner, which gives the NFS mount as final file location.
• MetadataBasedProductMover. Run the following locally on machineA:

  No Format
  java -Djava.ext.dirs=../lib org.apache.oodt.cas.filemgr.tools.MetadataBasedProductMover \ --fileManagerUrl http://localhost:9000 \ --typeName MyProdTypeName \ --pathSpec /net/machineA/[Filename]

...