Page History

The File Manager

This self guided tutorial is intended for first time users.

...

.
├── bin
│   ├── convert_map
│   ├── filemgr
│   ├── filemgr-client
│   ├── migrate_xml_policy
│   └── query-tool
├── etc
│   ├── filemgr.properties
│   ├── logging.properties
│   └── mime-types.xml
├── lib
│   └── *.jar
├── logs
│  
└── policy
|   ├── REMOVE.log
└── policy
 cmd-line-actions.xml
|   ├── cmd-line-options.xml
|   ├── core
|    │   ├── elements.xml
|   │   ├── product-type-element-map.xml
|   │   └── product-types.xml
|   |
|   ├── trace 
|   |   ├── elements.xml
|   |   ├── product-type-element-map.xml 
|   | │   └── product-types.xml
|   |
|   ├── geo
|    │|   ├── elements.xml
|   | │   ├── product-type-element-map.xml
|   | │   └── product-types.xml
|    │|
|    (additional policy sub subdirectoriesdirectories)
└── run

Please note, if you are using version 0.3 of OODT or earlier, the policy directory will look like this (with no subdirectoriessub directories):

└── policy
    ├── elements.xml
    ├── product-type-element-map.xml
    └── product-types.xml

...

• filemgr : file manager (startup/shutdown) script
• filemgr-client : file manager client interface script
• query-tool : catalog query tool
• convert_map : ???
• script
• query-tool : catalog query toolmigrate_xml_policy : ???

Configuring and Running the File Manager

...

$ cd /usr/local/oodt/cas-filemgr/bin
$ ./filemgr --help
Usage: ./filemgr {start|stop|restart|status}
$ ./filemgr start

...

The filemgr should be up and running, however, some WARNING messages will may appear, complaining about configuration.

If you get a java.net.BindException exception, make sure that no other service is running on port 9000. This is the port for an xml-rpc RPC interface that will be used for transferring data files into a repository.

There's also a new directory - file in the /usr/local/oodt/run directory. It The file contains a file with the filemgr process id. This is typical for *nix service house keeping. It is done to try and avoid running multiple filemgr services.

...

Server side metadata is generated by using java classes and the extractors that will be used are configured in the product-types.xml file in the chosen policy directory. For this example configuration, you should have /usr/local/oodt/cas-filemgr/policy/coreoodt as the policy directory, unless you're running version 0.3 or earlier of OODT, in which case you should have /usr/local/oodt/cas-filemgr/policy as the policy directory.

...

For the GenericFile type find the <metExtractors> key. It's specifying some extractors to use for server side metadata extraction, namely: CoreMetExtractor, MimeTypeExtractor, FinalFileLocationExtractor. For more details about metadata and extractors see the following page: http://oodt.apache.org/components/maven/metadata/user/basic.html Metadata Extractors.

If you're feeling curious, check out the other xml files in the /usr/local/oodt/cas-filemgr/policy subdirectories to get a better feel for how we define product types and elements. For a discussion of best practices w.r.t File Manager Policy, the reader is referred to Everything you want to know about File Manager Policy

...