October 7, 2016 | Written by: IBM Cloud
Share this post:
Almost every IT operations manager groans when forced to migrate to a new software version. No matter how convinced they are about the need to migrate, they worry about the business risks associated with a migration gone wrong.
With support ending for Java SE 6, migrating to WebSphere Application Server Version 9.0 (WAS V9) from an older version has become a necessity for businesses. Along with this necessity comes the task of moving applications to the newer version while ensuring high availability and disaster recovery in the face of potential migration issues.
This is where IBM PureApplication comes into play. The IBM PureApplication WAS V9 pattern helps automate the WAS configurations required to move and run an application during migration. But first, let’s dive into the process of migrating.
How will you move applications to WAS V9?
To get a version change into production, IT needs to take the following steps:
Each step needs the right infrastructure and environment for developers and testers to work on. During migration, existing applications need parallel environments — both old and new — to manage new development upgrades and production fixes.
These steps are multiplied when you have hundreds of applications and developers working in parallel. Imagine transitioning 100 applications to a new software version. It would mean setting up the environments 300 times for the first three steps pictured above. You could be doing it 600 times for a single iteration! Multiply that by the number of developers and testers who may need their own environments. The transition can soon become a nightmare.
Setting up consistent configurations
It doesn’t stop there. Each of the deployment steps needs an environment with consistent configurations. You need to set up a database, WAS server, application code, networking and all the dependencies without any variation in configuration during each phase. If you don’t, you could end up with inaccurate results impacting production.
Migration at the push of a button with UrbanCode Deploy and PureApplication
In the scenario above, you need an expert who can track the status of all 100 applications at each stage. UrbanCode Deploy (UCD) can do this for you at the push of a button. It can give you visibility into each step with notifications that ensure all permissions, dependencies and decisions are addressed quickly — and that no change goes unnoticed.
PureApplication with the WAS V9 pattern is our other hero in this example It can help with the consistent configuration of WAS at each stage, simplifying enterprise-grade service requirements such as high availability, disaster recovery, scaling, caching, monitoring and license management. No more waiting for various servers and teams to set things up. With PureApplication patterns, just click a button to set up the full-stack environment.
UCD automates and audits the three steps of application deployment, minimizing errors. The PureApplication WAS V9 pattern automatically manages the infrastructure deployment with enterprise-level services:
Environment infrastructures can be deployed on a hybrid cloud with integrated systems, local existing hardware (on premises), on the cloud (off premises) or in any combination. Options include:
- In the cloud: IBM PureApplication Service on SoftLayer, at IBM cloud data centers worldwide
- In your private cloud as a pre-built, pre-integrated system: IBM Bluemix Local System and PureApplication System (Power)
- On your private hardware infrastructure: IBM PureApplication Software
With the combination of WAS V9, PureApplication and UCD, there is little reason for IT operations managers to stress about WAS migrations.
To learn more about the new IBM Bluemix Local System, the newly renamed version of PureApplication System on Intel x86, check out the announcement from Bill Karpovich, general manager of IBM’s Cloud Platform.
For more information on the WAS V9 pattern for Bluemix Local System and PureApplication, check out this blog post.