EP3992782B1 - Service de rétention de configuration pour serveurs d'application web - Google Patents

Service de rétention de configuration pour serveurs d'application web Download PDF

Info

Publication number
EP3992782B1
EP3992782B1 EP21204626.2A EP21204626A EP3992782B1 EP 3992782 B1 EP3992782 B1 EP 3992782B1 EP 21204626 A EP21204626 A EP 21204626A EP 3992782 B1 EP3992782 B1 EP 3992782B1
Authority
EP
European Patent Office
Prior art keywords
addon
file
software package
software
configuration file
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
EP21204626.2A
Other languages
German (de)
English (en)
Other versions
EP3992782A1 (fr
Inventor
Devashish Biswas
Nikita Jain
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
SAP SE
Original Assignee
SAP SE
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by SAP SE filed Critical SAP SE
Publication of EP3992782A1 publication Critical patent/EP3992782A1/fr
Application granted granted Critical
Publication of EP3992782B1 publication Critical patent/EP3992782B1/fr
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00—Arrangements for software engineering
    • G06F8/60—Software deployment
    • G06F8/65—Updates
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00—Arrangements for software engineering
    • G06F8/60—Software deployment
    • G06F8/61—Installation
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/90—Details of database functions independent of the retrieved data types
    • G06F16/95—Retrieval from the web
    • G06F16/951—Indexing; Web crawling techniques
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/90—Details of database functions independent of the retrieved data types
    • G06F16/95—Retrieval from the web
    • G06F16/955—Retrieval from the web using information identifiers, e.g. uniform resource locators [URL]
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/90—Details of database functions independent of the retrieved data types
    • G06F16/95—Retrieval from the web
    • G06F16/958—Organisation or management of web site content, e.g. publishing, maintaining pages or automatic linking
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00—Arrangements for software engineering
    • G06F8/70—Software maintenance or management
    • G06F8/71—Version control; Configuration management
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44—Arrangements for executing specific programs
    • G06F9/445—Program loading or initiating
    • G06F9/44505—Configuring for program initiating, e.g. using registry, configuration files

Definitions

  • Software platforms are used by organizations to provide a variety of computing services. For example, a software platform can provide business intelligence services to client devices (e.g., as a web service). Software platforms, and associated software programs, need to store configuration information. In some situations, the stored configuration information is overwritten during a software upgrade, such as when the software platform is upgraded. This can result in service disruptions (e.g., the associated software programs may not operate until the configuration information is restored).
  • the configuration information is manually restored after a software platform is upgraded.
  • configuration files can be manually edited by an administrator. This manual procedure may need to be performed for each instance of the software platform (e.g., the software platform may be installed on a number of servers).
  • US 9 652 214 B1 describes systems and methods to provide pluggable extensions of software applications.
  • the plugin application package is received for deployment.
  • the plugin application package includes configuration data comprising various definitions for the deployment of the plugin application.
  • the configuration data of a host software application is updated with at least a part of the configuration data of the plugin application.
  • the host application is reconfigured based on the updated host configuration data to refer to the plugin application.
  • One or more plugin services provided by the plugin application are exposed through the reconfigured host application, to handle corresponding user requests.
  • US 2013/145349 A1 describes updating agent software which controls an agent, including how the agent adds instrumentation to an application and how the agent process data from the instrumentation.
  • a current configuration file and an updated configuration file are evaluated in view of rules, to create a merged configuration file.
  • the files include metadata entries.
  • the rules can include: delete a current configuration file, not merge a current configuration file with an updated configuration file, overwrite a current configuration file with an updated configuration file, delete a metadata entry, prefer an entry in the configuration file over a corresponding entry in the updated configuration file, and prefer an entry in the updated configuration file over the corresponding entry in the configuration file.
  • Customized entries in the current configuration file can be maintained if appropriate. Entries which are not maintained are kept in the merged configuration file as inline comments for documentation.
  • the configuration information for the addon software package can be preserved separately (e.g., independent of the common configuration file) and used later to restore the addon configuration information if needed.
  • an addon presence file is used to store an entry for the addon software package. The entry identifies another file containing the configuration information for the addon software package.
  • the addon presence file can be checked for the entry of the addon software package.
  • the configuration information for the addon software package can be added back to the common configuration file using the preserved configuration information (e.g., from an addon configuration file).
  • the configuration information for the addon software package can be preserved separately (e.g., independent of the common configuration file) and used later to restore the addon configuration information if needed.
  • an addon presence file is used to store an entry for the addon software package. The entry identifies another file containing the configuration information for the addon software package. If the main software platform is upgraded resulting in the common configuration file being overwritten or replaced, then the addon configuration information can be added back to the common configuration file using the preserved configuration information for the addon software package.
  • the technologies for retaining configuration information can be used for software such as web applications that run on a computer server.
  • a client device running a web browser can access software (e.g., a web application, which could be a mobile web application) running on a computer server via the web browser.
  • the technologies can also be applied to other types of software applications that run on computing devices and that store configuration information in common configuration files used by other software applications or that otherwise have their configuration information overwritten during a software upgrade.
  • a software platform is installed on a server.
  • the software platform uses a common configuration file to store its configuration settings.
  • the common configuration file may also be used by other software applications, such as addon applications that extend the functionality or otherwise work with the software platform.
  • addon applications When an addon application is installed, it will also store at least a portion of its configuration settings in the same common configuration file used by the software platform.
  • a problem can occur when the software platform is upgraded. Specifically, upgrading the software platform will overwrite the common configuration file. When this happens, the addon applications will no longer work (their configuration settings are no longer present in the common configuration file).
  • the addon applications are mobile web applications
  • clients will not be able to run the addon applications (e.g., they may receive an error message when trying to access the mobile web applications via a web browser).
  • the configuration settings for the addon applications have to be manually added back to the common configuration file (e.g., by a system administrator), which may also have to be performed for each of multiple servers. This can be a time consuming and error prone process. It can also result in significant service disruption.
  • configuration information for addon software packages can be retained in files that are separate from the common configuration file.
  • these files can be automatically checked (e.g., as part of the upgrade process and/or by other automated computer processes) to determine if there are any addon software packages that are currently installed, and if so their configuration information can be added back to the common configuration file from the separate files.
  • This automated process saves time, prevents errors (e.g., that may occur with a manual process), and reduces the chances of a service disruption (e.g., reduces the chance that an addon will not be available after the upgrade).
  • Table 1 depicts a number of example installation scenarios.
  • the installation order column depicts the order of installing and/or upgrading a main software platform along with an addon software package.
  • the second column indicates whether the installation order will result in a problem due to the common configuration file being replaced, or whether there will be no issues (either the common configuration has not been replaced or the addon configuration information has been added back to the common configuration file).
  • the technologies described herein can be applied to automatically resolve the problem. For example, the row with "Platform + Addon + Platform" indicates that the main software platform has been installed, followed later by installation of an addon software package, followed later by an upgrade of the main software platform. This scenario will result in the common configuration file being overwritten.
  • the automated technologies described herein for retaining configuration information can fully automate the process of retaining configuration information for addon software packages during main software platform upgrades.
  • automated computer processes e.g., retention services, content comparison services, and/or other software processes
  • the automated technologies can be performed on each of a number of computing devices (e.g., for each server of a cluster).
  • the main software platform can be any type of computer software package.
  • the main software platform can be a business intelligence platform, such as the BusinessObjects TM Business Intelligence platform provided by SAP ® .
  • the main software platform is installed on multiple computing devices (e.g., front-end components installed one or more web app servers and back-end components installed on one or more back-end servers).
  • the main software platform comprises a mobile client application that is installed on a web app server. The mobile client application is accessed by a client device via a web browser.
  • the main software platform uses a common configuration file to store at least some of its configuration information (e.g., configuration values, configuration settings, default values, etc.).
  • the common configuration file can be installed on the server when the main software platform is installed.
  • the main software platform is upgraded (e.g., when a new version of the main software platform is installed, when the main software platform is reinstalled, when components of the main software platform are upgraded, or when performing other upgrading procedures)
  • the common configuration file is replaced.
  • the content of the common configuration file can be replaced, or the entire common configuration file can be overwritten. In other words, upgrading of the main software platform will overwrite the common configuration file, either replacing the content or installing a new common configuration file.
  • the addon software package is any type of computer software package that operates with the main software platform.
  • the addon software package provides additional software features or functionality to the main software platform.
  • the addon software package can be a data visualization and analytics addon package that is an addon to a business intelligence platform.
  • One example of an addon software package is the SAP Lumira ® data visualization and analytics software addon for the Businessobjects TM Business Intelligence platform provided by SAP ® .
  • the addon software package is installed on multiple computing devices (e.g., multiple web app servers).
  • the addon software package provides an extension to a mobile client application and is accessed by client devices via a web browser.
  • the addon software package stores its configuration information in the common configuration file along with configuration information from other applications, such as the main software platform and/or other addon software packages.
  • the addon software package also uses an addon presence file. For example, when the addon software package is installed, an entry is added to the addon presence file. The entry indicates that the addon software package is installed and also indicates the location of an addon configuration file.
  • the addon configuration file (which can also be installed when the addon software package is installed) stores configuration information for the addon software package.
  • the addon presence file and/or addon configuration file can also be created or modified when the addon software package is upgraded.
  • the common configuration file stores configuration information (e.g., configuration values, configuration settings, default values, etc.) for various applications, including the main software platform and the addon software package.
  • the common configuration file can be installed with the main software platform or at another time.
  • the common configuration file is replaced (e.g., overwritten) when the main software platform is upgraded.
  • the common configuration file can be any type of file that is capable of storing configuration information within a computer system.
  • the common configuration file can be an extensible markup language (XML) file, a comma-separated value file, a spreadsheet file, a flat-file database file, or another type of file that stores configuration information.
  • XML extensible markup language
  • the addon presence file indicates which addon software packages are installed and the location of their respective configuration files.
  • the addon presence file can be created when the main software platform is installed, when the first addon software package is installed, or at another time.
  • the addon presence file can be any type of file that is capable of storing addon information within a computer system.
  • the addon presence file can be an extensible markup language (XML) file, a comma-separated value file, a spreadsheet file, a flat-file database file, or another type of file that stores information about addon software packages.
  • XML extensible markup language
  • the addon presence file stores an entry for the addon software package that comprises an indication of a source file and an indication of a target file.
  • the source file is the location (e.g., file name, path, etc.) of the addon configuration file for the addon software package.
  • the target file is the location (e.g., file name, path, etc.) of the common configuration file where the configuration information will be copied to when the main software platform is updated.
  • the Lumira addon software package there is an entry (identified by the "addon name” element) for the Lumira addon software package.
  • the entry also identifies a source file "lumxMobileWeb.xml,” which is the addon configuration file for the Lumira addon software package, and a target file “web.xml,” which is the common configuration file for the main software platform.
  • configuration information can be added back to the web.xml file when the main software platform is updated. Specifically, in this example, when the main software platform is updated (replacing the web.xml file), the configuration information from the lumxMobileWeb.xml file can be added back to the web.xml file.
  • the addon configuration file contains configuration information for the addon software package.
  • the addon configuration file can be created when the addon software package is installed, or at another time.
  • the addon configuration file can be any type of file that is capable of storing configuration information within a computer system.
  • the addon configuration file can be an extensible markup language (XML) file, a comma-separated value file, a spreadsheet file, a flat-file database file, or another type of file that stores configuration information for addon software packages.
  • XML extensible markup language
  • the Lumira addon software package there is configuration information for the Lumira addon software package (including the .lumx file format used by Lumira).
  • the configuration information includes information about URLs and corresponding executable components of the Lumira addon software package that allows a client device to access the Lumira addon package (which is running on a web app server) using a web browser.
  • environments can be provided for retaining configuration information for software applications running on servers (e.g., running on web application servers).
  • the environments can comprise various types of computing resources (e.g., software resources, server computers, database systems, cloud computing resources, networking resources, and/or other types of computing resources).
  • FIG. 1 is a diagram depicting an example environment 100 for retaining configuration information for software applications during upgrades.
  • the example environment 100 includes a client device 110.
  • the client device 110 can be a phone, tablet, laptop computer, desktop computer, or another type of computing device.
  • the client device 110 runs software that accesses the web app (application) server 120.
  • the client device 110 runs web browser software that accesses web applications (e.g., mobile web applications) provided by the web app server 120.
  • web applications e.g., mobile web applications
  • the example environment 100 also includes a back end server 140 and a database 150.
  • additional software resources e.g., main platform software components
  • the database 150 can provide database resources to the software running on the back end server 140 and/or web app server 120.
  • a main software platform 122 is installed on the web app server 120.
  • the main software platform 122 can be any type of computer software package.
  • the main software platform 122 can be a business intelligence platform.
  • one or more components of the main software platform 122 are installed on the web app server 120 (e.g., front end software components) and one or more other components of the main software platform 122 are installed on the back end server 140 (e.g., back end software components).
  • An addon software package 124 is also installed on the web app server 120.
  • the addon software package 124 is any type of computer software package that operates with the main software platform 122.
  • the addon software package 124 provides additional software features or functionality to the main software platform 122.
  • the addon software package 124 can be a data visualization and analytics addon package to a business intelligence platform.
  • the web app server 120 stores a number of files.
  • One of the files is a common configuration file 130.
  • the common configuration file 130 contains configuration settings for the main software platform 122 as well as any addon software packages that are associated with the main software platform 122, such as addon software package 124.
  • the common configuration file 130 is installed along with the main software platform 122.
  • the addon presence file 132 contains information indicating which addon software packages are installed along with details indicating how their respective configuration information can be restored (e.g., identifying addon configuration files).
  • the addon presence file 132 is generated the first time an addon software package is installed on the web app server 120 (e.g., upon installing addon software package 124).
  • the addon configuration file 134 contains configuration information for the addon software package 124. In some implementations, the addon configuration file 134 is generated when the addon software package 124 is installed.
  • configuration information can be retained during software upgrades.
  • the main software platform 122 is installed on the web app server 120 along with the common configuration file 130.
  • the addon software package 124 is installed on the web app server 120 as an addon to the main software platform 122.
  • Installation of the addon software package 124 involves adding configuration information for the addon software package 124 to the common configuration file 130.
  • the addon presence file 132 is created (if it does not already exist) and an entry is added to the addon presence file 132 indicating that the addon software package 124 has been installed.
  • the entry in the addon presence file 132 also identifies the addon configuration file 134 as containing configuration information for the addon software package 124.
  • the entry in the addon presence file 132 can also identify the common configuration file 130 (e.g., as the target file where the configuration information is to be restored).
  • the main software platform 122 may be upgraded (e.g., to a new version).
  • the common configuration file 130 is replaced (e.g., a new common configuration file could be installed or the contents of the common configuration file may be rewritten).
  • the addon presence file 132 is checked (e.g., triggered by the upgrade of the main software platform 122) to see if there are any addon software package entries.
  • the configuration information from the addon configuration file 134 is added to the common configuration file 130. In this way, the configuration information for the addon software package 124 is retained after the upgrade of the main software platform 122 is performed.
  • the example environment 100 depicts an example implementation of the web app server 120 and associated computing resources.
  • the technologies described herein can be implemented in other computing environments.
  • client devices that connect to the web app server 120 to utilize the main software platform 122 and/or the addon software package 124 (e.g., as remote web applications accessible via web browsers).
  • web app servers there may be any number of web app servers.
  • there can be a plurality of web app servers e.g., in a server cluster) where each web app server contains its own copy of the main software platform 122, the addon software package 124, the common configuration file 130, the addon presence file 132, and the addon configuration file 134.
  • some implementations may have just a single server that performs the functions of the web app server 120, and that could also perform functions of the back end server 140 and/or database 150.
  • Figure 2 is a diagram depicting an example web app server 120 along with example scenarios during which configuration information is retained. Specifically, this diagram depicts what happens during installation and upgrade of the various software programs and their associated files.
  • an initial installation of the main software platform 122 is performed.
  • the common configuration file 130 is installed, as depicted at 212.
  • the addon software package 124 is installed. As part of the installation of the addon software package 124, the configuration information for the addon software package 124 is added to the common configuration file 130, ad depicted at 222. In addition, as part of the installation of the addon software package 124, an entry for addon software package 124 is added to the addon presence file 132, as depicted at 224.
  • the addon presence file 132 may already exist (e.g., installed earlier as part of the initial installation 210) or it could be created at the time the addon software package 124 is installed.
  • the addon configuration file 134 is installed, as depicted at 226. After the addon installation at 220, the addon software package 124 will be available for use by client devices (e.g., by client device 110 running a web browser).
  • the main software platform 122 is upgraded.
  • the common configuration file 130 is replaced, as depicted at 232.
  • the addon presence file 132 is checked to see if it has any addon software package entries, as depicted at 234.
  • the configuration information for the addon software package 124 is added, from the addon configuration file 134, to the common configuration file 130, as depicted at 236.
  • a separate software process e.g., a retention service
  • the addon software package 124 may be upgraded.
  • the entry for the addon software package 124 in the addon presence file 132 can be checked and/or edited (e.g., by a separate software process, which can be called a content comparison service).
  • the upgraded addon software package 124 may include an additional addon configuration file (e.g., in addition to addon configuration file 134), and the entry for the addon software package 124 can be edited to include the additional addon configuration file. Upgrading the addon software package 124 can also result in editing of the addon configuration file 134 (e.g., with new and/or different configuration settings).
  • methods can be provided for retaining configuration information for software applications running on servers (e.g., running on web application servers).
  • software applications running on servers (e.g., running on web application servers).
  • hardware and/or software elements can perform operations to automatically add configuration information for currently installed addon software packages back into a common configuration file when a main software platform is upgraded.
  • Figure 3 is a flowchart depicting an example process 300 for retaining configuration information when a main software platform is upgraded.
  • an addon software package is deployed to a web application server running a main software platform.
  • the main software platform uses a common configuration file.
  • configuration information for the addon software package is added to the common configuration file.
  • an entry for the addon software package is added to an addon presence file.
  • the entry indicates that the addon software package is installed.
  • the entry can also indicate a source of configuration information for the addon software package (e.g., a separate file that stores the configuration information for use when the main software platform is upgraded).
  • the entry can also indicate a target file (e.g., an indicator for the common configuration file) where the configuration information for the addon software package will be added after the main software platform is upgraded.
  • an addon configuration file is installed.
  • the addon configuration file contains configuration information for the addon software package.
  • the addon configuration file is separate from the common configuration file.
  • the main software platform is upgraded (e.g., a new major or minor version is installed).
  • a number of operations are performed.
  • the operations include replacing the common configuration file.
  • the common configuration file can be overwritten when the main software platform is upgraded.
  • the configuration information of the addon software package that was previously present in the common configuration file is no longer present.
  • the operations also include, at 350, detecting the entry of the addon software package in the addon presence file. For example, source and target file identifiers can be obtained from the addon presence file.
  • the operations also include, at 360, in response to detecting the entry in the addon presence file, adding configuration information from the addon configuration file to the common configuration file.
  • a retention service is executed as part of the upgrade process for the main software platform.
  • the retention service (a software program) checks the addon presence file for addon software package entries (e.g., performs the operation depicted at 350), and if any entries are detected, the retention service adds configuration information from respective addon presence files back to the common configuration file (e.g., performs the operation depicted at 360).
  • the retention service can be executed on each of a number of servers (e.g., on each server of a cluster) when the main software platform is upgraded on each server.
  • FIG. 4 is a flowchart depicting an example process 400 for upgrading an addon software package.
  • an upgraded addon software package is installed on a web application server running a main software platform.
  • the main software platform and the addon software package use a common configuration file.
  • an addon presence file is checked to determine if there is an entry for the addon software package. If an entry is found, then at 430 the entry is modified. Modification of the entry for the addon software package in the addon presence file can include modifying the source and/or target file indicators, adding new source and/or target file indicators (e.g., the upgraded addon software package could add an additional configuration file), or making other changes.
  • the installation process can also comprise adding files (e.g., adding a new configuration file for the addon software package), modifying files (e.g., modifying an existing configuration file for the addon software package), and/or performing other installation operations.
  • a content comparison service is executed as part of the upgrade process for the addon software package.
  • the content comparison service (a software program) checks the addon presence file for an entry associated with the addon software package. If an entry is found, then the content comparison service updates the entry if needed (e.g., if the upgraded addon software package contains a new entry that is different from the existing entry).
  • the content comparison service can be executed on each of a number of servers (e.g., on each server of a cluster) when an addon software package is upgraded on each server.
  • FIG. 5 depicts a generalized example of a suitable computing system 500 in which the described innovations may be implemented.
  • the computing system 500 is not intended to suggest any limitation as to scope of use or functionality, as the innovations may be implemented in diverse general-purpose or special-purpose computing systems.
  • the computing system 500 includes one or more processing units 510, 515 and memory 520, 525.
  • this basic configuration 530 is included within a dashed line.
  • the processing units 510, 515 execute computer-executable instructions.
  • a processing unit can be a general-purpose central processing unit (CPU), processor in an application-specific integrated circuit (ASIC) or any other type of processor.
  • ASIC application-specific integrated circuit
  • FIG. 5 shows a central processing unit 510 as well as a graphics processing unit or co-processing unit 515.
  • the tangible memory 520, 525 may be volatile memory (e.g., registers, cache, RAM), non-volatile memory (e.g., ROM, EEPROM, flash memory, etc.), or some combination of the two, accessible by the processing unit(s).
  • volatile memory e.g., registers, cache, RAM
  • non-volatile memory e.g., ROM, EEPROM, flash memory, etc.
  • the memory 520, 525 stores software 580 implementing one or more innovations described herein, in the form of computer-executable instructions suitable for execution by the processing unit(s).
  • a computing system may have additional features.
  • the computing system 500 includes storage 540, one or more input devices 550, one or more output devices 560, and one or more communication connections 570.
  • An interconnection mechanism such as a bus, controller, or network interconnects the components of the computing system 500.
  • operating system software provides an operating environment for other software executing in the computing system 500, and coordinates activities of the components of the computing system 500.
  • the tangible storage 540 may be removable or non-removable, and includes magnetic disks, magnetic tapes or cassettes, CD-ROMs, DVDs, or any other medium which can be used to store information in a non-transitory way and which can be accessed within the computing system 500.
  • the storage 540 stores instructions for the software 580 implementing one or more innovations described herein.
  • the input device(s) 550 may be a touch input device such as a keyboard, mouse, pen, or trackball, a voice input device, a scanning device, or another device that provides input to the computing system 500.
  • the input device(s) 550 may be a camera, video card, TV tuner card, or similar device that accepts video input in analog or digital form, or a CD-ROM or CD-RW that reads video samples into the computing system 500.
  • the output device(s) 560 may be a display, printer, speaker, CD-writer, or another device that provides output from the computing system 500.
  • the communication connection(s) 570 enable communication over a communication medium to another computing entity.
  • the communication medium conveys information such as computer-executable instructions, audio or video input or output, or other data in a modulated data signal.
  • a modulated data signal is a signal that has one or more of its characteristics set or changed in such a manner as to encode information in the signal.
  • communication media can use an electrical, optical, RF, or other carrier.
  • program modules include routines, programs, libraries, objects, classes, components, data structures, etc. that perform particular tasks or implement particular abstract data types.
  • the functionality of the program modules may be combined or split between program modules as desired in various embodiments.
  • Computer-executable instructions for program modules may be executed within a local or distributed computing system.
  • system and “device” are used interchangeably herein. Unless the context clearly indicates otherwise, neither term implies any limitation on a type of computing system or computing device. In general, a computing system or computing device can be local or distributed, and can include any combination of special-purpose hardware and/or general-purpose hardware with software implementing the functionality described herein.
  • Fig. 6 depicts an example cloud computing environment 600 in which the described technologies can be implemented.
  • the cloud computing environment 600 comprises cloud computing services 610.
  • the cloud computing services 610 can comprise various types of cloud computing resources, such as computer servers, data storage repositories, database resources, networking resources, etc.
  • the cloud computing services 610 can be centrally located (e.g., provided by a data center of a business or organization) or distributed (e.g., provided by various computing resources located at different locations, such as different data centers and/or located in different cities or countries).
  • the cloud computing services 610 are utilized by various types of computing devices (e.g., client computing devices), such as computing devices 620, 622, and 624.
  • the computing devices e.g., 620, 622, and 624
  • the computing devices e.g., 620, 622, and 624) can utilize the cloud computing services 610 to perform computing operators (e.g., data processing, data storage, and the like).
  • Computer-readable storage media are tangible media that can be accessed within a computing environment (one or more optical media discs such as DVD or CD, volatile memory (such as DRAM or SRAM), or nonvolatile memory (such as flash memory or hard drives)).
  • computer-readable storage media include memory 520 and 525, and storage 540.
  • the term computer-readable storage media does not include signals and carrier waves.
  • the term computer-readable storage media does not include communication connections, such as 570.
  • any of the computer-executable instructions for implementing the disclosed techniques as well as any data created and used during implementation of the disclosed embodiments can be stored on one or more computer-readable storage media.
  • the computer-executable instructions can be part of, for example, a dedicated software application or a software application that is accessed or downloaded via a web browser or other software application (such as a remote computing application).
  • Such software can be executed, for example, on a single local computer (e.g., any suitable commercially available computer) or in a network environment (e.g., via the Internet, a wide-area network, a local-area network, a client-server network (such as a cloud computing network), or other such network) using one or more network computers.
  • any of the software-based embodiments can be uploaded, downloaded, or remotely accessed through a suitable communication means.
  • suitable communication means include, for example, the Internet, the World Wide Web, an intranet, software applications, cable (including fiber optic cable), magnetic communications, electromagnetic communications (including RF, microwave, and infrared communications), electronic communications, or other such communication means.

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • General Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Databases & Information Systems (AREA)
  • Data Mining & Analysis (AREA)
  • Computer Security & Cryptography (AREA)
  • Stored Programmes (AREA)

Claims (15)

  1. Un procédé, mis en oeuvre par un ou plusieurs dispositifs informatiques, pour la conservation ou encore rétention (retention) automatisée d'informations de configuration, le procédé comprenant le fait de :
    déployer un progiciel complément (add-on software package) (124) sur un serveur d'applications web (120), sachant que le serveur d'applications web (120) exécute une plate-forme logicielle principale (122), sachant que la plate-forme logicielle principale (122) et le progiciel complément (124) utilisent un fichier de configuration partagé ou encore commun (common) (130) ; et sachant que le progiciel complément (124) ajoute des informations de configuration au fichier de configuration commun (130), sachant que le progiciel complément (124) est configuré pour fonctionner avec la plate-forme logicielle principale (122) et pour fournir des caractéristiques ou des fonctionnalités logicielles supplémentaires à la plate-forme logicielle principale (122) ;
    ajouter une entrée pour le progiciel complément (124) à un fichier de présence de complément (addon presence file) (132) ;
    installer un fichier de configuration de complément (134) qui contient des informations de configuration pour le progiciel complément (124) :
    lors de la mise à niveau de la plate-forme logicielle principale (122) :
    remplacer le fichier de configuration commun (130) ;
    détecter l'entrée pour le progiciel complément (124) à partir du fichier de présence de complément (132) ; et
    en réponse à la détection de l'entrée pour le progiciel complément (124), ajouter des informations de configuration du fichier de configuration de complément (134) au fichier de configuration commun (130),
    sachant que le fichier de configuration commun (130), le fichier de configuration de complément (134) et le fichier de présence de complément (132) sont stockés sur le serveur d'application web (120).
  2. Le procédé d'après la revendication 1, sachant que le fichier de configuration commun (130) stocke des informations de configuration pour la plate-forme logicielle principale (122), le progiciel complément (124), et tout progiciel complément supplémentaire.
  3. Le procédé d'après l'une quelconque des revendications précédentes, sachant que le fait d'ajouter l'entrée pour le progiciel complément (124) au fichier de présence de complément (132) comprend le fait de :
    ajouter un indicateur de fichier source qui indique l'emplacement du fichier de configuration de complément (134) ; et de
    ajouter un indicateur de fichier cible qui indique l'emplacement du fichier de configuration commun (130).
  4. Le procédé d'après l'une quelconque des revendications précédentes, comprenant en outre le fait de :
    lors de la mise à niveau de la plate-forme logicielle principale (122), exécuter automatiquement un service de rétention de complément (addon retention service) qui détecte l'entrée pour le progiciel complément (124) et ajoute les informations de configuration du fichier de configuration de complément (134) au fichier de configuration commun (130).
  5. Le procédé d'après l'une quelconque des revendications précédentes, sachant que le procédé est répété pour chacun d'une pluralité de serveurs d'applications web (120) ; et/ou.
    sachant que le serveur d'applications web (120) fournit des applications web pour un ou plusieurs dispositifs clients (110).
  6. Le procédé d'après l'une quelconque des revendications précédentes, comprenant en outre le fait de :
    mettre en oeuvre le procédé pour un ou plusieurs progiciels complément supplémentaires, sachant que chacun des un ou plusieurs progiciels complément supplémentaires présente son entrée respective dans le fichier de présence de complément (132), et son fichier de configuration de complément (134) respectif.
  7. Le procédé d'après l'une quelconque des revendications précédentes, comprenant en outre le fait de :
    ajouter un ou de plusieurs fichiers de configuration de complément supplémentaires pour le progiciel complément (124) au fichier de présence de complément (132) ;
    lors de la mise à niveau de la plate-forme logicielle principale (122) :
    détecter un ou plusieurs fichiers de configuration de complément supplémentaires pour le progiciel complément (124) dans le fichier de présence de complément (132) ; et
    en réponse à la détection d'un ou de plusieurs fichiers de configuration de complément supplémentaires pour le progiciel complément (124), ajouter des informations de configuration provenant d'un ou de plusieurs fichiers de configuration de complément supplémentaires au fichier de configuration commun (130).
  8. Le procédé d'après l'une quelconque des revendications précédentes, sachant que l'ajout de l'entrée pour le progiciel complément (124) au fichier de présence de complément (132) est effectué en réponse à la détermination que le fichier de présence de complément (132) ne contenait pas l'entrée pour le progiciel complément (124), et/ou
    sachant que les informations de configuration pour le progiciel complément (124) comprennent des informations de mappage de localisateur uniforme de ressource (URL), à un exécutable du progiciel complément (124).
  9. Le procédé d'après l'une quelconque des revendications précédentes, comprenant en outre le fait de :
    recevoir, par l'intermédiaire d'une connexion réseau, une demande d'accès au progiciel complément (124) émanant d'un dispositif client (110) ; et
    en réponse à la réception de la demande, d'exécuter le progiciel complément (124) à l'aide des informations de configuration du fichier de configuration commun (130).
  10. Un dispositif informatique comprenant :
    un processeur ; et
    une mémoire ;
    le dispositif informatique configuré, via des instructions exécutables par ordinateur, pour effectuer des opérations de conservation ou encore rétention (retention) automatisée d'informations de configuration, les opérations comprenant le fait de :
    déployer un progiciel complément (add-on software package) (124) dispositif informatique, sachant que le dispositif informatique exécute une plate-forme logicielle principale (122), sachant que la plate-forme logicielle principale (122) et le progiciel complément (124) utilisent un fichier de configuration partagé ou encore commun (common) (130) ; et sachant que le progiciel complément (124) ajoute des informations de configuration au fichier de configuration commun (130), sachant que le progiciel complément (124) est configuré pour fonctionner avec la plate-forme logicielle principale (122) et pour fournir des caractéristiques ou des fonctionnalités logicielles supplémentaires à la plate-forme logicielle principale (122) ;
    ajouter une entrée pour le progiciel complément (124) à un fichier de présence de complément (addon presence file) (132) ;
    installer un fichier de configuration de complément (134) qui contient des informations de configuration pour le progiciel complément (124) :
    lors de la mise à niveau de la plate-forme logicielle principale (122) :
    remplacer le fichier de configuration commun (130) ;
    détecter l'entrée pour le progiciel complément (124) à partir du fichier de présence de complément (132) ; et
    en réponse à la détection de l'entrée pour le progiciel complément (124), ajouter des informations de configuration du fichier de configuration de complément (134) au fichier de configuration commun (130),
    sachant que le fichier de configuration commun (130), le fichier de configuration de complément (134) et le fichier de présence de complément (132) sont stockés sur le serveur d'application web (120).
  11. Le dispositif informatique d'après la revendication 10, sachant que le fichier de configuration commun (130) stocke des informations de configuration pour la plate-forme logicielle principale (122), le progiciel complément (124), et tout progiciel complément supplémentaire.
  12. Le dispositif informatique d'après l'une quelconque des revendications de 10 à 11, sachant que le fait d'ajouter l'entrée pour le progiciel complément (124) au fichier de présence de complément (132) comprend le fait de :
    ajouter un indicateur de fichier source qui indique l'emplacement du fichier de configuration de complément (134) ; et de
    ajouter un indicateur de fichier cible qui indique l'emplacement du fichier de configuration commun (130).
  13. Le dispositif informatique d'après l'une des revendications de 10 à 12, les opérations comprenant en outre le fait de :
    lors de la mise à niveau de la plate-forme logicielle principale (122), exécuter automatiquement un service de rétention de complément (addon retention service) qui détecte l'entrée pour le progiciel complément (124) et ajoute les informations de configuration du fichier de configuration de complément (134) au fichier de configuration commun (130).
  14. Le dispositif informatique d'après l'une quelconque des revendications de 10 à 13, sachant que les informations de configuration pour le progiciel complément (124) comprennent des informations de mappage de localisateur uniforme de ressource (URL), à un exécutable du progiciel complément (124).
  15. Un ou plusieurs supports de stockage lisibles par ordinateur stockant des instructions exécutables par ordinateur pour l'exécution sur un ou plusieurs dispositifs informatiques pour mettre en oeuvre le procédé d'après l'une des revendications de 1 à 9.
EP21204626.2A 2020-10-27 2021-10-26 Service de rétention de configuration pour serveurs d'application web Active EP3992782B1 (fr)

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
US17/081,699 US11194568B1 (en) 2020-10-27 2020-10-27 Configuration retention service for web application servers

Publications (2)

Publication Number Publication Date
EP3992782A1 EP3992782A1 (fr) 2022-05-04
EP3992782B1 true EP3992782B1 (fr) 2023-07-26

Family

ID=78621661

Family Applications (1)

Application Number Title Priority Date Filing Date
EP21204626.2A Active EP3992782B1 (fr) 2020-10-27 2021-10-26 Service de rétention de configuration pour serveurs d'application web

Country Status (2)

Country Link
US (1) US11194568B1 (fr)
EP (1) EP3992782B1 (fr)

Family Cites Families (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7406695B2 (en) * 2003-01-17 2008-07-29 Sap Aktiengesellschaft Automatically upgradeable extension of software
US8607223B2 (en) * 2006-07-28 2013-12-10 International Business Machines Corporation Creating multiplatform customized install packages for software installation
US20150205489A1 (en) * 2010-05-18 2015-07-23 Google Inc. Browser interface for installed applications
US8316349B2 (en) * 2010-05-27 2012-11-20 Microsoft Corporation Deployment script generation and execution
US9336027B2 (en) * 2010-12-17 2016-05-10 Sap Se System and method for modular business applications
US8612516B2 (en) * 2011-11-28 2013-12-17 Wyse Technology Inc. Deployment of a driver or an application on a client device having a write-filter
US20130145361A1 (en) * 2011-12-01 2013-06-06 International Business Machines Corporation Discovering and installing web application plugins
US8752015B2 (en) * 2011-12-05 2014-06-10 Ca, Inc. Metadata merging in agent configuration files
US9652214B1 (en) * 2015-12-18 2017-05-16 Sap Se Pluggable extension of software applications
US10579966B1 (en) * 2016-06-24 2020-03-03 Intuit Inc. Adapting a shared project build platform to a developer plugin

Also Published As

Publication number Publication date
EP3992782A1 (fr) 2022-05-04
US11194568B1 (en) 2021-12-07

Similar Documents

Publication Publication Date Title
US11467816B1 (en) Method and system of running an application
US8327351B2 (en) Application modification framework
US9910651B2 (en) System for developing, testing, deploying, and managing applications in real-time
US8667031B2 (en) Reuse of shared metadata across applications via URL protocol
US10185626B2 (en) Automatic application error detection and rollback
US8583613B2 (en) On demand data conversion
US20130054812A1 (en) System and method for dynamically assembling an application on a client device
US8843360B1 (en) Client-side localization of network pages
US8627284B2 (en) Managed system extensibility
US11169792B2 (en) Method and apparatus for generating patch
US20160335079A1 (en) Zero down-time deployment of new application versions
US20160344847A1 (en) Systems and Methods for Managing and Publishing Managed Content
US20190102477A1 (en) Novel metadata relationships in a configuration management database
US20080209400A1 (en) Approach for versioning of services and service contracts
CN113760306B (zh) 安装软件的方法、装置、电子设备及存储介质
US7934221B2 (en) Approach for proactive notification of contract changes in a software service
CN111107133A (zh) 差异包的生成方法、数据更新方法、装置和存储介质
EP3992782B1 (fr) Service de rétention de configuration pour serveurs d'application web
CN112597134A (zh) 分布式配置中心的配置方法、装置、电子设备和介质
US9342530B2 (en) Method for skipping empty folders when navigating a file system
US8880586B2 (en) Metadata subscription registry
CN110928639B (zh) 一种Windows虚拟化镜像分层管理方法及装置
US20140033196A1 (en) Method and system for determining the eligibility for deploying protected content
EP3001311A1 (fr) Procédé pour convertir automatiquement les applications Web en plusieurs plates-formes
US20140013195A1 (en) Content reference in extensible markup language documents

Legal Events

Date Code Title Description
PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE APPLICATION HAS BEEN PUBLISHED

AK Designated contracting states

Kind code of ref document: A1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: REQUEST FOR EXAMINATION WAS MADE

17P Request for examination filed

Effective date: 20220929

RBV Designated contracting states (corrected)

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

GRAP Despatch of communication of intention to grant a patent

Free format text: ORIGINAL CODE: EPIDOSNIGR1

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: GRANT OF PATENT IS INTENDED

INTG Intention to grant announced

Effective date: 20230215

GRAS Grant fee paid

Free format text: ORIGINAL CODE: EPIDOSNIGR3

GRAA (expected) grant

Free format text: ORIGINAL CODE: 0009210

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE PATENT HAS BEEN GRANTED

AK Designated contracting states

Kind code of ref document: B1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

REG Reference to a national code

Ref country code: CH

Ref legal event code: EP

REG Reference to a national code

Ref country code: IE

Ref legal event code: FG4D

REG Reference to a national code

Ref country code: DE

Ref legal event code: R096

Ref document number: 602021003786

Country of ref document: DE

REG Reference to a national code

Ref country code: LT

Ref legal event code: MG9D

REG Reference to a national code

Ref country code: NL

Ref legal event code: MP

Effective date: 20230726

REG Reference to a national code

Ref country code: AT

Ref legal event code: MK05

Ref document number: 1592711

Country of ref document: AT

Kind code of ref document: T

Effective date: 20230726

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: NL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20230726

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: GR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20231027

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: IS

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20231126

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: SE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20230726

Ref country code: RS

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20230726

Ref country code: PT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20231127

Ref country code: NO

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20231026

Ref country code: LV

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20230726

Ref country code: LT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20230726

Ref country code: IS

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20231126

Ref country code: HR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20230726

Ref country code: GR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20231027

Ref country code: FI

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20230726

Ref country code: AT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20230726

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: FR

Payment date: 20231026

Year of fee payment: 3

Ref country code: DE

Payment date: 20231020

Year of fee payment: 3

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: PL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20230726

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: ES

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20230726

REG Reference to a national code

Ref country code: DE

Ref legal event code: R097

Ref document number: 602021003786

Country of ref document: DE

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: SM

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20230726

Ref country code: RO

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20230726

Ref country code: ES

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20230726

Ref country code: EE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20230726

Ref country code: DK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20230726

Ref country code: CZ

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20230726

Ref country code: SK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20230726

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: IT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20230726

Ref country code: MC

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20230726

PLBE No opposition filed within time limit

Free format text: ORIGINAL CODE: 0009261

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: NO OPPOSITION FILED WITHIN TIME LIMIT

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: LU

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20231026

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: LU

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20231026

26N No opposition filed

Effective date: 20240429