Local BOF registry file

Repository BOF (TBO / SBO modules in the docbase) is what production uses. For a local app-server JVM you can point DFC at a properties file so a type loads your TBO class from the classpath instead. That is a development override, not a deploy mechanism.

JVM flag

-Ddfc.development.bof.registry_file=/path/to/bof.registry_file.properties

The value is the properties file, not a directory. Put the file where the application server can read it. Restart that JVM after you change the flag or the file.

File format

One line per type (or module). Left side is the Documentum type name. Right side is type, plus the fully qualified TBO class:

custom_document=type,com.example.bof.tbo.CustomDocumentTBO

The type name must exist in the docbase. The class must be on that JVM’s classpath (your TBO jar). Compile the jar however you normally do (jar cvf custom-bof.jar …) and add it next to DFC.

Do not put customer type names or employer package prefixes in public notes. Use placeholders like custom_document and com.example….

Not the repository registry

This flag does not install a TBO into the docbase. Other clients (DA, another appserver, jobs) still use whatever module is registered in the repository. For a real deploy, install the BOF module (Composer / DAR / dmc_module) and drop the JVM override.