SYSTEM AND METHOD FOR SERVER MIGRATION SYNCHRONIZATION

• US 20140201716A1
• Filed: 03/17/2014
• Published: 07/17/2014
• Est. Priority Date: 09/30/2006
• Status: Active Grant

• Current Assignee: Liberty Peak Ventures, LLC (Dominion Harbor Enterprises, LLC)
• Original Assignee: American Express Travel Related Services Company, Inc. (American Express Company)
• Inventors: Alger, James, Reza, Masood, Romanowski, Judy, Wright, Lora L., Treger, Jerold R.
• Granted Patent: US 9,495,283 B2
• Time in Patent Office: Days
• US Class Current: 717/124
• CPC Class Codes: G06F 11/3664 Environments for testing or debugging software
• CPC Class Codes: G06F 11/368 for test version control, e.g. updating test cases to a new software version
• CPC Class Codes: G06F 11/3684 for test design, e.g. generating new test cases
• CPC Class Codes: G06F 11/3688 for test execution, e.g. scheduling of test suites
• CPC Class Codes: G06F 11/3696 Methods or tools to render software testable
• CPC Class Codes: G06F 8/60 Software deployment
• CPC Class Codes: G06F 8/71 Version control security arrangements therefor G06F21/57; Configuration management
• CPC Class Codes: G06F 9/44505 Configuring for program initiating, e.g. using registry, configuration files

Abstract

A system and method for managing the migration of software components among test servers that form a distributed software test environment to ensure that the software components in each of the test servers represent a production environment except for software components being tested. The system further ensures that component changes rolled out into production are not overridden when multiple update requests are made for the same component.

Claims

1. A method comprising:

replacing, by a software component migration computer-based system, a previous version of a test component with a production component in each of a plurality of test environments; and

flagging, by the computer-based system, a second package that uses a software component such that the production component is implemented in the second package rather than the test component.

2. The method of claim 1, wherein a first package comprises the test component.

3. The method of claim 1, wherein the test component comprises a modification of the software component.

4. The method of claim 1, wherein a test sequence for the first package comprises the plurality of test environments in which the test component is to be tested and an order in which the test component is to be tested in the test environments.

5. The method of claim 1, wherein each of the plurality of test environments includes a previous version of the test component.

6. The method of claim 1, further comprising labeling, by the computer-based system and in response to completion of a test sequence, the test component as the production component.

7. The method of claim 1, further comprising testing, by the computer-based system, the test component in accordance with a test sequence.

8. The method of claim 1, wherein the replacing occurs before testing any further modification of the software component in any of the plurality of test environments.

9. The method of claim 1, further comprising controlling, by the computer-based system, a time at which the test component is tested in one of the test environments, in order to avoid attempting to test two packages at a same time.

10. The method of claim 1, further comprising prohibiting, by the computer-based system, testing of the test component in a test environment while the test environment is testing another package that contains a version of the test component.

11. The method of claim 1, further comprising testing, by the computer-based system, the first package in the test environment at least one of before and after testing of the second package that contains a version of the test component.

12. The method of claim 1, wherein each package has a respective priority level, and wherein the order of testing is based on the respective priority levels of the packages.

13. The method of claim 1, further comprising notifying, by the computer-based system, an owner of the test component that a modification of the test component exists.

14. The method of claim 1, further comprising updating, by the computer-based system and in response to a successful test sequence, the status of the test component from a test status to a production status.

15. The method of claim 1, further comprising altering, by the computer-based system, the order in which the test component is to be tested.

16. The method of claim 1, further comprising associating, by the computer-based system, a status indicator with the first package that indicates that the first package at least one of:

is currently being tested at the test environment, is being held while awaiting testing at the test environment, is in the process of migrating to the test environment, and has successfully completed testing and that its test component has been adopted as standard software in place of a previous version of the test component.

17. The method of claim 1, wherein the test component of the first package has been adopted as standard software in place of a previous version of the test component.

18. The method of claim 1, further comprising:

defining, by the computer based system, the first package comprising a test component; and

defining, by the computer based system, the test sequence for the package.

19. A system comprising:

a software component migration processor,

a tangible, non-transitory memory configured to communicate with the processor,

the tangible, non-transitory memory having instructions stored thereon that, in response to execution by the processor, cause the processor to perform operations comprising;

replacing, by the processor, a previous version of a test component with a production component in each of a plurality of test environments; and

flagging, by the processor, a second package that uses a software component such that the production component is implemented in the second package rather than the test component.

20. An article of manufacture including a non-transitory, tangible computer readable storage medium having instructions stored thereon that, in response to execution by a software component migration computer-based system, cause the computer-based system to perform operations comprising:

replacing, by the computer-based system, a previous version of a test component with a production component in each of a plurality of test environments; and

flagging, by the computer-based system, a second package that uses a software component such that the production component is implemented in the second package rather than the test component.