Update System for JAR and Script Files for Application Servers

Abstract

This invention relates to a system (1) that automatically updates jar and script files located on application servers by running a command from Linux. System (1) is designed to apply jar files and database (DB) script files by running only one command. In this way, changes do not have to be made manually.

Description

1 TARIFF Update System for JAR and Script Files for Application Servers Technical Area This invention enables the updating of jar and script files located on application servers. It relates to a system that provides this automatically via a command run on Linux. 5 State of the Art Updating JAR and script files on application servers today. This is done manually. A JAR file error occurs when it runs on the application server. It gives an error, and if it's malfunctioning, a new JAR file is being prepared to fix this error. and is manually copied to the application server. Besides that, many 10 The configuration (config) file needs to be updated manually. Nowadays, instead of performing these kinds of manual steps, all the steps can be automated. Structures that can do this are needed. Patent application number TR2018 / 03915, which is included in the prior art. In the document, methods and arrangements for processing post-script files are described. 15 This is explained. However, the relevant application document states that the application servers contain... Update jar and script files automatically via a command run on Linux. A structure that provides this kind of service is not described. In conclusion, solutions that address the needs described above are relevant to the subject. Due to its inadequacy, it has become necessary to make improvements in the relevant technical field. 20 Brief Description of Find The invention was created by drawing inspiration from existing situations and overcoming the aforementioned drawbacks. It aims to solve the problem. The purpose of this invention is to protect jar and script files located on application servers. a 25 that automatically updates itself via a command run on Linux. It is the establishment of the system. 2 The system stores JAR files and database script files in a single file. It is designed to be implemented by executing the command. This way, changes cannot be made manually. It does not have to be done that way. It is prepared by the support team. The corrective content includes zip, jar, and script files, and This corrective content is applied automatically via a tool. Script and jar files 5 when implemented, in the vehicle's database or network elements (NE - network element) It is essential that it does not cause any disruption. Customers are responsible for the implemented corrective measures. The status of content and ongoing processes is monitored through log and status files. They can see it. Corrective content files are version-specific to the application server and It contains the content cumulatively. 10 The corrective content Zip file example in the system will be as follows: Hotfix-22.2.0.1.zip The first three steps are the same as the MCP version for the jar and script files to be executed. should be. The last digit of the corrective content zip file is the version of the corrective content zip file: 15 It expresses. The MCP payload names will be as follows: MCP-22.2.0.0.1045.qcow Therefore, the zip file only acts as corrective content when it matches the MCP version. available. When a new fix is ​​released, a new fix containing all the fixes will be available. A content file is created. Reverting from a new update to an older version. Rollback operations are possible. A zip file can contain multiple JAR files and scripts. It may contain files. These files are then individually routed to their respective environments using a loop. It is applied. The structural and characteristic features and all the advantages of the invention are given in the figures below and 25 This becomes clearer thanks to the detailed explanation written with references to these figures. This will be understood as such, and therefore the evaluation will also take these forms and detailed explanations into account. This should be done taking that into consideration. Ways to Help Understand the Discovery 3 Figure 1 is a schematic representation of the system that is the subject of the invention. Figure 2 shows the operational structure of the application module included in the system that is the subject of the invention. It is a flowchart. Explanation of Part References 1. System 5 2. Application (Apply) module 3. Update (Upgrade) module 4. Rollback Module 5. Remove module 6. Reporting module 10 Detailed Description of Find In this detailed description, the preferred configurations of the system (1) that is the subject of the invention are: This explanation is provided solely to facilitate a better understanding of the subject. This invention enables the updating of jar and script files located on application servers. It is related to a system (1) that provides automatically with a command run on Linux. 15 The system (1) only stores jar files and database script files. It is designed to be implemented by running a single command. This allows changes to be made. It doesn't have to be done manually. It's prepared by the support team. The corrective content includes zip, jar, and script files, and This corrective content is applied automatically via a tool. Script and jar files 20 when implemented, in the vehicle's database or network elements (NE - network element) It is essential that it does not cause any disruption. Customers are responsible for the implemented corrective measures. The status of content and ongoing processes is monitored through log and status files. They can see it. Corrective content files are version-specific to the application server and It contains the content cumulatively. 25 The example of the corrective content Zip file in the system (1) will be as follows: 4 Hotfix-22.2.0.1.zip The first three steps are the same as the MCP version for the jar and script files to be executed. should be. The last digit of the corrective content zip file indicates the version of the corrective content zip file. It expresses. 5 The MCP payload names will be as follows: MCP-22.2.0.0.1045.qcow Therefore, the zip file only acts as corrective content when it matches the MCP version. available. When a new fix is ​​released, a new fixer containing all the fixes will be available. A content file is created. Reverting from a new content update to an older version is possible. Rollback operations are possible. A zip file can contain multiple JAR files and scripts. It may contain files. These files are then individually routed to their respective environments using a loop. It is applied. The system that is the subject of the invention, the schematic representation of which is given in Figure 1 (1);  15 that uploads a new corrective content zip file to the system (1) and application module that implements the necessary updates (2),  Updates previously applied corrective content zip files and the system (1) Update module that upgrades the version (3),  Undo that reverts a previously applied corrective content zip file. module (4), 20  A removal module that reverts a previously applied corrective content zip file. (5) and  Provides information about the currently applied jar and scrip files in the system (1). reporting module (6) It includes. 25 Application module (2), in the apply operation performed;  Identifying virtual machines (VMs),  -s in the command <side>the party specified by the parameter (e.g., primary) or detection of secondary virtual machines,  the information of these virtual machines<base_directory> to the / vms-side directory writing  Creating the CC directory,  if on a virtual machine<base_directory> If the / CC directory does not exist, this creation of the series 5  Checking the ZIP file, <lcm_directory> the corrective content zip file located in the directory Comparison of the version with the current installation version (1) in the system,  If the versions are the same, copy the zip file to the respective virtual machines.  Alarm management, 10  Generating an alarm during the corrective content process,  When the process is complete, the alarm is sent to the database in one row. adding and deleting this line also removes the alarm.  Applying the hotfix,  corrective content zip file<base_directory> / CC removed, 15  The jar and script files are ordered according to the fixOrdering file inside. implementation  status log,  the status of the process<base_directory> to the / CC / status.json file saving (example: JSON) 20  Implementation of files,  jar files<base_directory> / <release_version> / <ne_key> / jars / and <base_directory> / <load_version> Copying to the / shared / jars / directories and updating the JVM configuration file (jvm.cfg),  Executing precommands for script files, 25 copying the files to the specified target directories and the final commands (postcommand) execution  After the operations, the relevant network element (NE) is restarted. initiation It is configured to perform its operations. 30 Update module (3), during upgrade operation;  md5sum comparison,  Reading the md5sum values ​​of the files in status.json, 6  Replace the files that are different from the new corrective content zip file. implementation  cleaning up remaining files,  Removal of jar and script files remaining from the previous version It is configured to perform its operations. 5 The rollback module (4) is used in the rollback operation;  Using the information in the status.json file,  previously applied jar files<jars_directory> deletion from ' and Updating jvm.cfg  The "removecommands" commands taken from the readme for script files are 10 operation It is configured to perform its operations. The lifting module (5) is used in the remove operation;  Deleting the status.json and zip files, <base_directory> / cc / status.json and corrective content 15 Removing zip files  Cleaning up the applied files,  Complete removal of jar and script files from the system (1)  Network element restart,  After all cleaning processes are completed, the network element will restart at 20 initiation It is configured to perform its operations. The reporting module (6) is used in the report operation;  By reading the status.json file, it can be determined which corrective content zip files belong to which files. Reporting of application to virtual machines 25 It is configured to perform the operation. The application module (2) whose working structure is presented in the form of a flowchart in Figure 2; 7  Check if the corrective content zip file exists.  If the corrective content zip file is missing, no action will be taken and the process will continue. termination,  If there is a corrective content zip file, the zip file should be uploaded to virtual machines (VMs – virtual machine) transfer, 5  The database (DM) of the virtual machine to which the zip file is transferred is virtual checking if it has a machine,  If the virtual machine being migrated is the database machine, the jar or zip file must be on the network. Checking whether it is applicable to network elements (NE). 10  If the jar or zip file is not applicable to network elements, the process... termination,  If a jar or zip file can be applied to network elements, the jar file can be routed through the network. checking whether it is suitable for the position,  If the JAR file is not suitable for the network element, the process will be terminated. 15  If the jar file is suitable for the network element, the jar file can be placed on the network element. implementation, sequentially restarting the network element instances and the process termination,  If the virtual machine being migrated is the database machine, there is nothing in the zip file. Checking if there is a script file, 20  If the zip file contains any script files, data will be transferred to the virtual machine. Applying the base script changes and terminating the process,  If there are no script files in the zip file, restarting will help. checking if it is necessary,  If a restart is not necessary, the process will be terminated. 25  If a restart is necessary, the databases will be restarted sequentially. initiation and termination of the process It is configured to perform the transaction steps. The development and implementation of the feature offered by the system (1) is done through Ansible playbooks and This was done systematically using Python code. The process took 30 days. For automation and effective operation of the system (1), the following steps are required: It has been followed up: Automation with Ansible Playbooks 8  Ansible (Automation Tool) is used in application and management processes. A repeatable, safe and fast solution has been provided in the system (1).  Playbook Configuration (Script Configuration): Corrective content (zip) Ansible is used to distribute the jar and script files in the directory to the relevant servers. A playbook (script sequence) has been designed. 5  Role-Based Deployment: Each network element and database Separate tasks have been defined and roles assigned. This allows for corrective action. The content has been implemented in the correct environment and order.  Seamless Deployment: In command sequences, scripts and to avoid any interruption in the system (1) during the application of jar files 10 The necessary checks have been carried out. For example, the system's (1) workload or dependency Users were monitored and a suitable schedule was ensured.  State Tracking: Ansible logs (records) the application process during operation. by creating status files and status files, both success and failure statuses can be recorded. He recorded it. 15 Creating and Controlling Status.json Files with Python A status.json file that holds JAR and script files applied to virtual machines using Python. The file is created. The status.json file contains the following information:  vm_name (virtual machine name)  cc_zip_file (corrective content zip file) 20  rg_side (backup side)  ne_name (network element name)  status  ne_key (network element key)  applied_scripts and applied_jar files 25< / side>

Claims

9 REQUESTS 1. Updating JAR and script files located on application servers in Linux It is a system (1) that automatically provides the command that runs through it. its feature;  Uploads a new corrective content zip file to the system (1) 5 and application module that implements the necessary updates (2),  Updates previously applied corrective content zip files and the system (1) Update module that upgrades the version (3),  Undo that reverts a previously applied corrective content zip file. module (4), 10  A removal module that reverts a previously applied corrective content zip file. (5) and  Provides information about the currently applied jar and scrip files in the system (1). reporting module (6) It includes. 15 2. The system mentioned in accordance with claim 1 is (1), and its feature is; the implemented apply In the (implementation) operation;  Identifying virtual machines (VMs),  -s in the command <side>the party specified by the parameter (e.g., primary) or detection of secondary virtual machines, 20  the information of these virtual machines<base_directory> to the / vms-side directory writing  Creating the CC directory,  if on a virtual machine<base_directory> If the / CC directory does not exist, this creation of the series 25  Checking the ZIP file, <lcm_directory> the corrective content zip file located in the directory Comparison of the version with the current installation version (1) in the system,  If the versions are the same, copy the zip file to the respective virtual machines.  Alarm management, 30  Generating an alarm during the corrective content process,  When the process is complete, the alarm is sent to the database in one row. adding and deleting this line also removes the alarm.  Applying the hotfix,  corrective content zip file<base_directory> / Removing it below CC,  According to the fixOrdering file inside, the jar and script files are 5 respectively. implementation  status log,  the status of the process<base_directory> to the / CC / status.json file saving (example: JSON)  Implementation of files, 10  jar files<base_directory> / <release_version> / <ne_key> / jars / and <base_directory> / <load_version> Copying to the / shared / jars / directories and updating the JVM configuration file (jvm.cfg),  Executing precommands for script files, Copying the files to the specified target directories and the last commands 15 (postcommand) execution  After the operations, the relevant network element (NE) is restarted. initiation application module (2) which is configured to perform its operations It includes. 20 3. The system mentioned in accordance with claim 1 is (1), and its feature is upgrade. in the operation;  md5sum comparison,  Reading the md5sum values ​​of the files in status.json,  The files that differ from the new corrective content zip file should be re-uploaded. implementation  cleaning up remaining files,  Removal of jar and script files remaining from the previous version Update module (3) configured to perform its operations It includes. 30 4. The system mentioned in accordance with claim 1 is (1), and its feature is; 11  Using the information in the status.json file,  previously applied jar files<jars_directory> deletion from ' and Updating jvm.cfg  "removecommands" taken from the readme for script files operation 5 Undo module (4) which is configured to perform its operations It includes.

5. The system mentioned in accordance with claim 1 is (1), and its feature is;  Deleting the status.json and zip files, <base_directory> / cc / status.json and corrective content 10 Removing zip files  Cleaning up the applied files,  Complete removal of jar and script files from the system (1)  Network element restart,  After all cleaning operations are completed, the network element will restart at 15 initiation The removal module (5) is configured to perform its operations. It includes.

6. The system mentioned in accordance with claim 1 is (1), and its feature is;  By reading the status.json file, it can be determined which corrective content zip files belong to which 20 reporting that it was applied to virtual machines It includes the reporting module (6) which is configured to perform the operation.

7. The system mentioned in accordance with claim 1 is (1), and its feature is;  Check if the corrective content zip file exists.  If the corrective content zip file is missing, no action will be taken and the process will continue for 25 days. termination,  If there is a corrective content zip file, the zip file should be uploaded to virtual machines (VMs – (virtual machine) transfer, 12  The database (DM) of the virtual machine to which the zip file is transferred is virtual checking if it has a machine,  If the virtual machine being migrated is the database machine, the jar or zip file must be on the network. Checking whether it is applicable to network elements (NE). 5  If the jar or zip file is not applicable to network elements, the process... termination,  If a jar or zip file can be applied to network elements, the jar file can be routed through the network. checking whether it is suitable for the position,  If the JAR file is not suitable for the network element, the process will be terminated. 10  If the jar file is suitable for the network element, the jar file can be placed on the network element. implementation, sequentially restarting the network element instances and the process termination,  If the virtual machine being migrated is the database machine, there is nothing in the zip file. Checking if there is a script file, 15  If the zip file contains any script files, data will be transferred to the virtual machine. Applying the base script changes and terminating the process,  If there are no script files in the zip file, restarting will help. checking if it is necessary,  If a restart is not necessary, the process will be terminated. 20  If a restart is necessary, the databases will be restarted sequentially. initiation and termination of the process application module (2) which is configured to perform its operations It includes.< / side>

Images