×

Synchronization of configuration changes between applications and their platforms

  • US 9,336,208 B2
  • Filed: 03/14/2013
  • Issued: 05/10/2016
  • Est. Priority Date: 09/28/2012
  • Status: Active Grant
First Claim
Patent Images

1. A computer implemented method for synchronizing between middleware configurations and application configurations, the method comprising:

  • receiving a first middleware state variable from a middleware component;

    processing, at a synchronization module at least stored in memory, the first middleware state variable to determine at least one application state variable that depends on a value of the first middleware state variable and corresponds to an online edition of at least one software application that relies upon the middleware component;

    sending one or more changes corresponding to the at least one application state variable to an offline edition of the at least one software application;

    determining whether the one or more changes in the at least one application state variable result in one or more other changes in the middleware component;

    receiving a change in configurations of the middleware component;

    storing the change or information thereof into the first middleware state variable of the middleware component at a first location of the memory of a computing system;

    triggering one or more operations within the synchronization module;

    obtaining, at a middleware listener module, the one or more changes corresponding to the change or information thereof of and including at least a topology change in the middleware component;

    storing the one or more changes at a second location of the memory of the computer system;

    determining, at a forward mapping module, whether or not the at least one software application is to receive the one or more changes;

    determining, at the forward mapping module, whether or not the one or more changes are affected by the change or information thereof of the middleware component;

    transmitting the one or more changes to the offline edition of the at least one software application at least by performing a forward mapping operation with the forward mapping module when the at least one software application is to receive the one or more changes;

    applying the one or more changes to the offline edition of the at least one software application;

    determining, at a reverse mapping module, one or more implied changes corresponding to the one or more changes to the offline edition of the at least one software application and storing the one or more implied changes as the one or more other changes at a third location of the memory;

    transmitting the one or more other changes to an application listener module for the middleware component;

    performing a reverse mapping for the one or more other changes for the middleware component into one or more middleware configuration changes;

    storing the one or more middleware configuration changes at a fourth location of the memory;

    transmitting the one or more middleware configuration changes to the middleware component;

    preparing the offline edition of the at least one software application at least by applying the one or more middleware configuration changes to the middleware component;

    creating runtime data, which change while the offline edition and the one or more middleware configuration changes are being applied, for the online edition of the at least one software application and storing the runtime data at a fifth location of the memory;

    applying patch transformations to the runtime data stored at the fifth location of the memory;

    shutting down the online edition of the at least one software application;

    designating the offline edition of the at least one software application as a new online edition of the at least one software application; and

    restarting the new online edition of the at least one software application.

View all claims
  • 1 Assignment
Timeline View
Assignment View
    ×
    ×