Rapid Fire let you deploy your changes while your users are busy. It performs the
following steps in order to change a production file:
- Create a shadow library to store the new file.
- Create the new file in the shadow library.
- Generate a RPG program for copying the data from the production to the shadow library.
- Start journaling for the original file in the production library.
- Copy data from the production to the shadow library using a batch job. Your users keep on working and do not have to leave the application.
- While the copy job is active, a second Rapid Fire batch job receives changes of the copied data from the journal.
- When all records a copied, the changes are applied to the data in the shadow library.
When Rapid Fire starts applying the changes from the journal, you reached the point when you
can ask your users to leave the application in order to install the new file. That takes just
a few minutes, since all you have to do is moving some objects:
- Ensure that nobody can change the production file any longer.
- End the Rapid Fire copy job.
- Move the old file from the production library to a backup library.
- Move the new file from the shadow to the production library.
