Dynamic release control of software application version changes

• US 8,918,775 B1
• Filed: 07/12/2013
• Issued: 12/23/2014
• Est. Priority Date: 07/12/2013
• Status: Active Grant

• Current Assignee: CA, Inc. (d/b/a CA Technologies) (Broadcom, Inc.)
• Original Assignee: CA, Inc. (d/b/a CA Technologies) (Broadcom, Inc.)
• Inventors: Carpenter, Robert L., Gulasky, Gary R.
• Primary Examiner(s): Khatri, Anil
• Application Number:
  US13/940,777
• Time in Patent Office: 529 Days
• Field of Search: 717168-175, 709/203
• US Class Current: 717/168
• CPC Class Codes: G06F 8/65 Updates security arrangements therefor G06F21/57
• CPC Class Codes: G06F 9/44505 Configuring for program initiating, e.g. using registry, configuration files

Abstract

Dynamic release control is performed by identifying a plurality of software application instances installed on a mainframe system, identifying a compatibility level for each software application instance, designating a common execution level based upon a lowest one of the identified compatibility levels, configuring each software application instance to conform to the common execution level, receiving a software update indication that at least one software application instance has been updated and performing a compatibility level switch across the plurality of software application instances after receiving the software update indication if a lowest one of the compatibility levels is different from the common execution level by adjusting the common execution level based upon the lowest one of the compatibility levels and by reconfiguring each software application instance to operate in a mode that constrains the corresponding software application instance to conform to the adjusted common execution level.

Claims

1. In a mainframe system, a machine-executable process for performing dynamic release control, the process comprising:

identifying a plurality of software application instances installed on a mainframe system;

identifying, for each of the plurality of software application instances, a compatibility level, wherein;

each identified compatibility level corresponds with execution characteristics of an associated one of the software application instances;

each identified compatibility level is obtained by communicating with a registration component integrated with the associated one of the software application instances; and

information obtained from the registration component is programmed by a developer of the associated one of the software application instances;

designating a common execution level based upon a lowest one of the identified compatibility levels;

configuring each of the plurality of software application instances to operate in a mode that constrains the corresponding software application instance to conform to the common execution level;

receiving a software update indication that at least one of the plurality of software application instances has been updated to a version that has a new compatibility level, where each updated software application instance, when executed, continues to conform to the common execution level after the corresponding update; and

performing a compatibility level switch across the plurality of software application instances after receiving the software update indication if a lowest one of the compatibility levels is different from the common execution level by;

adjusting the common execution level based upon the lowest one of the compatibility levels; and

reconfiguring each of the plurality of software application instances to operate in a mode that constrains the corresponding software application instance to conform to the adjusted common execution level.

2. The process of claim 1 further comprising:

identifying a plurality of subcomponents for each software application instance;

wherein;

identifying, for each of the plurality of software application instances, a compatibility level, further comprises;

identifying a compatibility level of each subcomponent of the software application instance; and

identifying a lowest compatibility level among the identified plurality of subcomponents; and

establishing the compatibility level of the software application instance as the identified lowest compatibility level among the identified plurality of subcomponents.

3. The process of claim 1 further comprising:

identifying at least one software application dependency associated with a corresponding one of the plurality of software application instances; and

identifying a compatibility level for each identified software application dependency;

wherein;

identifying, for each of the plurality of software application instances, a compatibility level, further comprises;

establishing the compatibility level of the software application instance based upon the compatibility level among the software application instance and each identified software application dependency.

4. The process of claim 1, wherein:

performing a compatibility level switch across the plurality of software application instances comprises automatically executing the compatibility switch after receiving the software update indication if a lowest one of the compatibility levels is different from the common execution level.

5. The process of claim 1, further comprising:

providing a graphical user interface that allows a user to selectively control when the compatibility level switch is performed.

6. The process of claim 1, wherein:

identifying, for each of the plurality of software application instances, a compatibility level, further comprises;

receiving a communication from the corresponding software application instance identifying its compatibility level.

7. The process of claim 1, further comprising:

storing for each of the plurality of software application instances that has been updated at least once or has at least one pending update ready for installation, an installation library comprising;

a backout file in order to restore the software application instance back to a previous version;

a backout policy flow requirement to direct a restore of the software application instance back to a previous version;

an upgrade policy flow to direct an update to a new version of the software application instance; and

a capability pending file that stores the capabilities available for a compatibility level that is higher than the common execution level.

8. The process of claim 7, further comprising:

automatically verifying that the backout file, the backout policy flow requirements and the upgrade policy requirements are in place on the mainframe system to support an implemented upgrade of a software application instance before performing the compatibility level switch.

9. The process of claim 1, wherein:

performing a compatibility level switch across the plurality of software application instances comprises;

executing at least one policy rule that determines when to perform the compatibility switch.

10. A computer-readable storage device that stores machine-executable program code for performing dynamic release control, wherein the program code instructs a processor to:

identify a plurality of software application instances installed on a mainframe system;

identify, for each of the plurality of software application instances, a compatibility level, wherein;

each identified compatibility level corresponds with execution characteristics of an associated one of the software application instances;

each identified compatibility level is obtained by communication with a registration component integrated with the associated one of the software application instances; and

information obtained from the registration component is programmed by a developer of the associated one of the software application instances;

designate a common execution level based upon a lowest one of the identified compatibility levels;

configure each of the plurality of software application instances to operate in a mode that constrains the corresponding software application instance to conform to the common execution level;

receive a software update indication that least one of the plurality of software application instances has been updated to a version that has a new compatibility level, where each updated software application instance, when executed, continues to conform to the common execution level after the corresponding update; and

perform a compatibility level switch across the of software application instances after receiving the software update indication if a lowest one of the compatibility levels is different from the common execution level by;

adjust the common execution level based upon the lowest one of the compatibility levels; and

reconfigure each of the plurality of software application instances to operate in a mode that constrains the corresponding software application instance to conform to the adjusted common execution level.

11. The computer-readable storage device of claim 10 further comprising machine-executable program code to identify a plurality of subcomponents for each software application instance;

wherein;

the machine-executable program code to identify, for each of the plurality of software application instances, a compatibility level, further comprises machine-executable program code to;

identify a compatibility level of each subcomponent of the software application instance;

identify a lowest compatibility level among the identified subcomponents; and

establish the compatibility level of the software application instance as the identified lowest compatibility level among the identified subcomponents.

12. The computer-readable storage device of claim 10 further comprising machine-executable program code to:

identify at least one software application dependency associated with a corresponding one of the plurality of software application instances; and

identify a compatibility level for each identified software application dependency;

wherein;

the machine-executable program code to identify, for each of the plurality of software application instances, a compatibility level, further comprises machine-executable program code to establish the compatibility level of the software application instance based upon the compatibility level among the software application instance and each identified software application dependency.

13. The computer-readable storage device of claim 10, wherein:

the machine-executable program code to perform a compatibility level switch across the plurality of software application instances comprises the machine-executable program code to automatically execute the compatibility switch after receiving the software update indication if a lowest one of the compatibility levels is different from the common execution level.

14. The computer-readable storage device of claim 10, further comprising the machine-executable program code to:

provide a graphical user interface that allows a user to selectively control when the compatibility level switch is performed.

15. The computer-readable storage device of claim 10, wherein:

the machine-executable program code to identify, for each of the plurality of software application instances, a compatibility level, further comprises machine-executable program code to receive a communication from the corresponding software application instance identifying its compatibility level.

16. The computer-readable storage device of claim 10, further comprising the machine-executable program code to:

store for each of the plurality of software application instances that has been updated at least once or has at least one pending update ready for installation, an installation library comprising;

a backout file in order to restore the software application instance back to a previous version;

a backout policy flow requirement to direct a restore of the software application instance back to a previous version;

an upgrade policy flow to direct an update to a new version of the software application instance; and

a capability pending file that stores the capabilities available for a compatibility level that is higher than the common execution level.

17. The computer-readable storage device of claim 16, further comprising the machine-executable program code to:

automatically verify that the backout file, the backout policy flow requirements and the upgrade policy requirements are in place on the mainframe system to support an implemented upgrade of a software application instance before performing the compatibility level switch.

18. The computer-readable storage device of claim 10, wherein the machine-executable program code to perform a compatibility level switch across the software application instances comprises:

the machine-executable program code to execute at least one policy rule that determines when to perform the compatibility switch.