Dynamic software version selection

• US 8,595,715 B2
• Filed: 12/31/2010
• Issued: 11/26/2013
• Est. Priority Date: 12/31/2010
• Status: Expired due to Fees

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Ward, David G., Webb, Simon J.
• Primary Examiner(s): Dao, Thuy
• Assistant Examiner(s): Luu, Cuong V
• Application Number:
  US12/982,970
• Publication Number:
  US 20120174124A1
• Time in Patent Office: 1,061 Days
• Field of Search: None
• US Class Current: 717/170
• CPC Class Codes: G06F 8/65 Updates security arrangements therefor G06F21/57
• CPC Class Codes: G06F 8/71 Version control security arrangements therefor G06F21/57; Configuration management
• CPC Class Codes: G06F 9/44521 Dynamic linking or loading; Link editing at or after load time, e.g. Java class loading
• CPC Class Codes: G06F 9/44536 Selecting among different versions

Abstract

Dynamic software version selection is performed by associating a binding library with a software component. The binding library comprises a loader component and a binding component, wherein the loader component serves as an intermediary between the software component and the binding component, and the binding component comprises software component-side logic. Dynamic software version selection further comprises logic in the loader component that decides to load a library from the binding component into memory of a processing device, and selecting by the loader component, a desired version of the requested library, where the desired version of the library is selected from at least two versions of the library associated with the binding component of the binding library. Still further, dynamic software version selection comprises loading the desired version of the library into memory of a computer processing system without requiring that the associated software component restart.

Claims

1. A processor-implemented method of performing dynamic software version selection, comprising:

executing a software component of a middleware application on a processing device;

associating a binding library with the software component, the binding library comprising a loader component and a binding component, where;

the loader component serves as an intermediary between the software component and the binding component; and

the binding component comprises software component-side logic;

utilizing the binding library to interface with a remote server of the middleware application across a network environment;

utilizing a program version table to store specific library versions for corresponding programs utilized by the software component;

receiving an updated version of a library of the binding component;

storing the updated version in the program version table;

recognizing a trigger by the loader component to load a different library from the binding component into memory of the processing device by receiving an application programming interface call from the software component;

selecting by the loader component, a desired version of the requested library based upon a value of a library version variable associated with the program version table, where the desired version of the library is selected from at least two versions of the library associated with the binding component of the binding library; and

loading the desired version of the library into memory of the processing device by;

logically disconnecting from the middleware application;

unloading a previously loaded library;

loading the updated version of the library; and

reconnecting to the middleware application, without restarting the middleware application.

2. The method according to claim 1, further comprising:

receiving by the loader component, software component program interface calls from the software component;

forwarding the received calls to corresponding software component programming interfaces of the desired version of the library loaded into memory.

3. The method according to claim 1, wherein selecting by the loader component, a desired version of the requested library, comprises:

selecting by the loader component, the desired version of the requested library, using a file system symbolic link.

4. The method according to claim 1, wherein selecting by the loader component, a desired version of the requested library, comprises:

selecting by the loader component, the desired version of the requested library, using a control file that directs the selection.

5. The method according to claim 1, further comprising:

utilizing a library version table to identify versions of the library; and

storing a library version variable that tracks the current version of the library;

wherein;

selecting by the loader component, a desired version of the requested library, comprises;

reading, by the loader component, the value of the library version variable; and

selecting the desired version of the library based upon the value of the library version variable.

6. The method according to claim 1, further comprising:

updating the binding component of the binding library with an updated version of the library without changing a loader component of the binding library;

loading the updated version of the library via the loader component, wherein the software component does not shutdown during the loading, the loading comprising;

disconnecting a previous library version of the binding component; and

connecting the updated version of the library; and

forwarding calls by the loader component, from the software component to the loaded, updated version of the library.

7. The method of claim 1, wherein recognizing a trigger by the loader component to load a different library from the binding component into memory of processing device comprises:

receiving a disconnect call from the software component; and

receiving a connect call from the software component.

8. The method of claim 1, wherein recognizing a trigger by the loader component to load a different library from the binding component into memory of processing device comprises:

receiving any call from the software component.

9. The method of claim 1, further comprising:

updating a shared library version table that stores the names and versions of libraries available in the binding component; and

updating the shared program version table that stores a plurality of applications and a corresponding library version number for each application;

wherein;

the updates for the shared library version table and the shared program are received from the remote server such that the remote server controls when migration should begin for library versions.

10. A computer program product to perform dynamic software version selection, comprising:

a tangible computer readable storage memory having computer readable program code embodied therewith, the computer readable program code comprising;

computer readable program code configured to execute a software component of a middleware application on a processing device;

computer readable program code configured to associate a binding library with the software component, the binding library comprising a loader component and a binding component, where;

the loader component serves as an intermediary between the software component and the binding component; and

the binding component comprises software component-side logic;

computer readable program code configured to utilize the binding library to interface with a remote server of the middleware application across a network environment;

computer readable program code configured to utilize a program version table to store specific library versions for corresponding programs utilized by the software component;

computer readable program code configured to receive an updated version of a library of the binding component;

computer readable program code configured to store the updated version in the program version table;

computer readable program code configured to recognizing a trigger by the loader component to load a different library from the binding component into memory of the processing device by receiving an application programming interface call from the software component;

computer readable program code configured to select by the loader component, a desired version of the requested library based upon a value of a library version variable associated with the program version table, where the desired version of the library is selected from at least two versions of the library associated with the binding component of the binding library; and

computer readable program code configured to load the desired version of the library into memory of the processing device using;

computer readable program code configured to logically disconnect from the middleware application;

computer readable program code configured to unload a previously loaded library;

computer readable program code configured to load the updated version of the library; and

computer readable program code configured to reconnect to the middleware application, without restarting the middleware application.

11. The computer program product according to claim 10, further comprising:

computer readable program code configured to receive by the loader component, software component program interface calls from the software component;

computer readable program code configured to forward the received calls to corresponding software component programming interfaces of the desired version of the library loaded into memory.

12. The computer program product according to claim 10, wherein the computer readable program code configured to select by the loader component, a desired version of the requested library, comprises:

computer readable program code configured to select by the loader component, the desired version of the requested library, using a file system symbolic link.

13. The computer program product according to claim 10, wherein the computer readable program code configured to select by the loader component, a desired version of the requested library, comprises:

computer readable program code configured to select by the loader component, the desired version of the requested library, using a control file that directs the selection.

14. The computer program product according to claim 10, further comprising:

computer readable program code configured to utilize a library version table to identify versions of the library; and

computer readable program code configured to store a library version variable that tracks the current version of the library;

wherein;

the computer readable program code configured to select by the loader component, a desired version of the requested library, comprises;

computer readable program code configured to read, by the loader component, the value of the library version variable; and

computer readable program code configured to select the desired version of the library based upon the value of the library version variable.

15. The computer program product according to claim 10, further comprising:

computer readable program code configured to update the binding component of the binding library with an updated version of the library without changing a loader component of the binding library;

computer readable program code configured to load the updated version of the library via the loader component, wherein the software component does not shutdown during the loading, the loading comprising;

computer readable program code configured to disconnect a previous library version of the binding component; and

computer readable program code configured to connect the updated version of the library; and

computer readable program code configured to forward calls by the loader component, from the software component to the loaded, updated version of the library.

16. The computer program product of claim 10, wherein the computer readable program code configured to recognize a trigger by the loader component to load a different library from the binding component into memory of processing device comprises:

computer readable program code configured to receive a disconnect call from the user software component; and

computer readable program code configured to receive a connect call from the user software component.

17. The computer program product of claim 10, wherein the computer readable program code configured to recognize a trigger by the loader component to load a different library from the binding component into memory of processing device comprises:

computer readable program code configured to receive any call from the software component.

18. The computer program product of claim 10, further comprising computer readable program code configured to migrate internal state data structures from their present form to a new form as required by a newly loaded binding component.

19. The computer program product of claim 18, further comprising providing the logic needed to perform the migration by each version of the binding component.

20. The computer program product of claim 10, further comprising:

computer readable program code configured to update a shared library version table that stores the names and versions of libraries available in the binding component; and

computer readable program code configured to update the shared program version table that stores a plurality of applications and a corresponding library version number for each application;

wherein;

the updates for the shared library version table and the shared program are received from the remote server such that the remote server controls when migration should begin for library versions.