This lesson describes how to define how to encrypt and protect the contents of your source and JDBC property file.
In database migrations, the source database is most often a production database; therefore the contents defined within the source JDBC properties files should be encrypted so that its username and password are not known. Our example source and destination JDBC property files are the following:
Encrypting the Source Property File
Use the following GenRocket command line option to encrypt the file source.config.property file:
- genrocket -ef source.config.property
An encrypted version of source.config.property will be created as:
When GenRocket sees '.gref' at the end of a file, it will recognize the file to be a GenRocket encrypted file.
You may if you would like, encrypt the dest.config.property file as well.