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 utility from the <runtime_sandbox>/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 <runtime_sandbox>/extensions/global/entities directory.

By default, when you run the entitydeployer target, all the log messages are printed to the<runtime_sandbox>/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 utility from the <runtime_sandbox>/bin directory. For example:

./deployer.sh -t updateERD

Note: By default, during entity deployment or dbverify, the SQL statements generated by dbverify are applied to the database. To prevent dbverify from generating IndexAdds SQL statements for dropped indexes, ensure that you list the names of those dropped indexes in the following file within your customization source.

files/extensions/schemagenerator/indexes_not_created.txt

In an extracted DTK runtime, the corresponding location is:

<runtime>/extensions/schemagenerator/indexes_not_created.txt.

Ensure that each index is listed in this file in a separate line, and the Index Name from the corresponding entity XML is specified.