Dismiss
InnovationQ will be updated on Sunday, Oct. 22, from 10am ET - noon. You may experience brief service interruptions during that time.
Browse Prior Art Database

Process for migrating a solution to a new version of a platform while maintaining the solution in production on an existing platform

IP.com Disclosure Number: IPCOM000236010D
Publication Date: 2014-Apr-02
Document File: 5 page(s) / 297K

Publishing Venue

The IP.com Prior Art Database

Abstract

Disclosed is a process for migrating a solution to a new version of a platform while maintaining an existing solution that is in production on an older version of the platform.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 24% of the total text.

Page 01 of 5

Process for migrating a solution to a new version of a platform while maintaining the solution in production on an existing platform

Developers of a solution that has been deployed into production and is in use have two different conflicting requirements in maintaining the respective solutions. On one hand, the developers must keep the solution in production, keep it available so users can access the solution, and must be able to respond quickly to rapidly changing business needs for the solution. New business requirements may arise that require changes that must be implemented in the short term. Currently, this need is handled by separating solution development into two or more stages to facilitate iterative development of a solution, so that the solution can be modified and tested while the existing version of the solution is in production and in use.

On the other hand, developers must also migrate the solutions to a newer version of the platform. As new versions of the platform are released, new features are made available that can be incorporated into existing solutions. Substantial changes in the platform can result in a long development cycle for the solution as it is migrated to the new platform.

Typically, the upgrade of a solution is incorporated into the usual maintenance process of the solution. However, while a solution is being migrated to a new

version of the platform, the existing solution that is currently in production still requires maintenance in a relatively short period. When the upgrade process is short and simple, it is easy to incorporate the upgrade while making other changes to the solution. When the upgrade process is long and complicated, the solution requires two separate and parallel development tracks, one involving modifications on the current platform version and another for migrating to the new platform version. The process is further complicated when there are multiple solutions in production. Upgrading the platform typically requires migrating all solutions to the new platform at the time the platform is upgraded. However, it can be useful to have one production environment with multiple solutions on different levels of the platform, so that not all solutions need to be upgraded at the same time.

In the past, this required having separate installations of each version of the platform on separate servers with separate content repositories (i.e. object stores). However, having separate installations of the platform requires duplicate resources, including extra servers and extra object stores, which increases expense and requires the

maintenance of additional servers and platform installations. This significantly increases the total cost in time and resources of upgrade.

To address these two business needs for solution development, a process has been developed to migrate a solution to a new version of the platform while maintaining an existing solution that is in production on an older version of...