Showtime! Moving to production
You're at the point where it is time to put your brand new Account Management application into production and open it up for enterprise use. To accomplish this you can use the same Account Management Cluster — QA pattern created earlier or if organizational processes dictate, you can simply clone it and create a new pattern with a new name. Nothing about the makeup of the pattern will change. In fact, in order to deploy your Account Management cluster environment into production, you only need to make two familiar changes:
- The application binaries should be retrieved from a different repository.
- The data source should be configured to refer to a different database instance.
This means you simply change the configuration data at deploy time as you have done previously.
Figure 25. Deploying the pattern to production
This is all it takes to move your application environment from quality assurance into a production environment! Once the deployment process is complete and the virtual system started, you can access the WebSphere Application Server administration console just like you did for previously deployments and you can manage the virtual system in WebSphere CloudBurst in the same manner as you managed virtual systems deployed on the VMware ESX platform.
Not only is the end-user experience consistent with respect to creating and deploying patterns for different platforms, the experience is the same when managing the resultant virtual systems regardless of the type of infrastructure on which the virtual machines are hosted.
How does it feel? You have moved an Account Management application from development to test to quality assurance and finally into production. Each migration action was little more than a combination of drag-and-drop actions paired with tweaks to deploy-time configuration data. In addition, each time you performed a migration task in minutes.