Building database extensions

You can build the database extensions by rebuilding the entities.jar.

About this task

To build the extensions to your database, rebuild the entities.jar by running the deployer.sh (or deployer.cmd on Windows) utility from the <INSTALL_DIR>/bin directory. For example:

./deployer.sh -t entitydeployer

Note: Before building the database extensions, make sure that all the extension files are stored in the INSTALL_DIR/extensions/global/entities directory.

By default, when you run the entitydeployer target, all the log messages are printed to the <INSTALL_DIR>/logs/entitydeployer.log file. If you want to print the log messages in the log file as well as on the console, pass the -l info parameter when you run the entitydeployer target. For example:

./deployer.sh -t entitydeployer -l info

To update the ERD documentation, re-build the entities.jar by running the deployer.sh (or deployer.cmd on Windows) utility from the INSTALL_DIR/bin directory. For example:

./deployer.sh -t updateERD

Note: By default, when you run the entitydeployer target or InstallService script, the dbverify tool is also run, and the dbverify-generated SQLs are applied to the database.
  • To prevent dbverify from generating "IndexAdds" SQLs for dropped indexes, ensure that the dropped indexes are listed in the <INSTALL_DIR>/extensions/schemagenerator/indexes_not_created.txt file. Or, if the INDEXES_NOT_CREATED property in the <INSTALL_DIR>/properties/sandbox.cfg file is configured, add the list of dropped indexes to the file referenced by the property.
  • If you want to suppress the call to the dbverify tool again when you run InstallService script, override and set the NO_DBVERIFY property to true in the <INSTALL_DIR>/properties/sandbox.cfg file.

For deploying the database extensions, refer to Deploying Extensions.