Release Phase Recommendations
The release phase involves propagating the now validated system onto the production hardware.
Propagate Test Bed Optimizations to Production Systems
Propagating the system artifacts and configuration onto the production hardware and starting it up to process is a relatively straightforward process. However, in practice, there are things to consider regarding performance during this phase that can be easily missed:
Verify that platform optimizations are propagated. During implementation and verification, it is common to implement any number of platform level performance optimizations.
For example, when using an isolated adapter such as HTTP on Internet Information Server (IIS), there are a number of common performance optimizations that can be used such as increasing the number of processes in IIS in which the adapters will run. Any such performance optimizations found before release must be tracked and propagated to the production environment as well.
Set up and automate data backup, log shipping, data retention configurations, and purging tasks. As part of certification for production, the frequency at which databases are backed up and purged (for example, the BizTalk Tracking database and BAM database) is key to sustainability so those settings must be migrated to production they don’t already exist there.
See Also
Project Planning Recommendations by Phase
Requirements Phase Recommendations
Design Phase Recommendations
Implementation Phase Recommendations
Verification Phase Recommendations