Try OpenEdge Now
skip to main content
Managing ABL Applications
R-code Features and Functions : Database CRCs and time stamps : CRC versus time stamp validation : CRC-based deployment
CRC-based deployment
Using CRC validation, if you deploy r-code, you only have to compile the procedures against a database with the same basic structure as the end-user database. It does not matter when or where the database was created. If you make schema changes to an existing database, you can distribute the newly compiled r-code to end users, along with a data definition files to install the schema changes.
The flexibility of CRC-based deployment makes it easier to distribute a new version of an existing application.
To deploy an application update based on CRC validation:
1. Install a copy of the production database from the target site in your development environment.
2. Create an incremental data definition file that captures the difference between your development database and the production copy. For information about creating an incremental data definition file, see OpenEdge Data Management: Database Administration.
3. Apply the incremental data definition file to your copy of the production database.
4. Recompile all procedures affected by the schema changes against your copy of the production database.
5. Apply the incremental data definition file to the original production database (on site). The CRC for the original production database should now be identical to the production copy, but probably not identical to your development database.
6. Distribute the new r-code files (from Step 4) to the updated production site.
The steps for CRC-based deployment are essentially the same as those for time stamp-based deployment, but you gain these advantages:
*You are not required to encrypt and give end users source code.
*End users do not have to compile your source code.
*You do not have to send a copy of a new database to end users.
*End users do not have to dump and reload all their data into your new database.