Middleware management method and device

Abstract

The present invention provides a middleware management method and device, which belongs to the field of financial technology or other technical fields. The middleware management method includes: determining the core resource data and auxiliary resource data corresponding to the middleware; determining resource sorting data according to the auxiliary resource data and the core resource data; sorting the corresponding middleware according to the resource sorting data, and processing the sorted middleware in sequence. The present invention can perform concurrent centralized management of a large number of middleware, improve the efficiency of operation and maintenance management, and optimize the concurrent management mode.

Description

Technical Field

[0001] The present invention relates to the field of financial technology, and in particular to a middleware management method and device. Background Art

[0002] Traditional enterprise WEB middleware has been widely used in transaction systems in financial industries such as banking and insurance, and is a basic component of many business systems in the financial industry, such as IBM's WebSphere Application SERVER (hereinafter referred to as WAS).

[0003] At present, this type of traditional enterprise-level WEB middleware can only be managed by its supporting management console (such as IE browser) after it is installed on a PC server. Common management operations mainly include starting and stopping the middleware process. At the same time, the middleware (such as IBM WAS) must be managed. In addition to manually logging into its management console, you must also remember all kinds of necessary configuration information of the WEB middleware software, such as security management features, general operating environment, SERVER name and port of external services, etc.

[0004] The above scenario is the current daily management scenario for WEB middleware deployed on a PC server. In actual production operation and maintenance, operation and maintenance personnel are usually responsible for several, dozens or even hundreds of WEB middlewares. Therefore, this management method has the following disadvantages:

[0005] 1. Manual operation is time-consuming and inefficient. In the scenario of managing dozens or even dozens of middlewares, the only way to operate them is to log in to the management console of the middlewares one by one manually. This is a very inefficient method. It is impossible to start and stop multiple WEB middlewares concurrently, which wastes a lot of management time.

[0006] 2. Complicated operation and heavy workload. The operation configuration information of most WEB middleware is basically different. When implementing operation management through their respective management consoles, operation and maintenance personnel must remember the configuration information of dozens or even dozens of WEB middleware environments. They cannot view important configurations at a glance and must carefully check and confirm them one by one during the operation, wasting a lot of energy.

[0007] 3. It is impossible to dynamically monitor the application load of the WEB middleware and the load capacity of the host PC server in real time and adjust the concurrency management strategy accordingly. In manual management of middleware, it is difficult to dynamically start and stop the middleware according to the usage load of core resources such as the host server's CPU or memory and the business weight of the WEB middleware itself. It can only be operated in sequence, without considering the impact on business applications. Summary of the invention

[0008] The main purpose of the embodiments of the present invention is to provide a middleware management method and device to automatically perform concurrent centralized management on a large number of middleware, improve operation and maintenance management efficiency, and optimize the concurrent management mode.

[0009] In order to achieve the above object, an embodiment of the present invention provides a middleware management method, including:

[0010] Determine the core resource data and auxiliary resource data corresponding to the middleware;

[0011] Determine resource ranking data according to the auxiliary resource data and the core resource data;

[0012] The corresponding middleware is sorted according to the resource sorting data, and the sorted middleware is processed in sequence.

[0013] The embodiment of the present invention further provides a middleware management device, including:

[0014] A resource determination module, used to determine the core resource data and auxiliary resource data corresponding to the middleware;

[0015] A resource sorting data module, used to determine resource sorting data based on auxiliary resource data and core resource data;

[0016] The middleware processing module is used to sort the corresponding middleware according to the resource sorting data and process the sorted middleware in sequence.

[0017] An embodiment of the present invention further provides a computer device, comprising a memory, a processor, and a computer program stored in the memory and running on the processor, wherein the processor implements the steps of the middleware management method when executing the computer program.

[0018] The embodiment of the present invention further provides a computer-readable storage medium on which a computer program is stored. When the computer program is executed by a processor, the steps of the middleware management method are implemented.

[0019] The middleware management method and device of the embodiment of the present invention first determine the resource sorting data according to the auxiliary resource data and core resource data corresponding to the middleware, then sort the corresponding middleware according to the resource sorting data, and process the sorted middleware in sequence. It can concurrently and centrally manage a large number of middleware, improve the operation and maintenance management efficiency, and optimize the concurrent management mode. BRIEF DESCRIPTION OF THE DRAWINGS

[0020] In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings required for use in the description of the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.

[0021] Figure 1 is a flow chart of a middleware management method in an embodiment of the present invention;

[0022] Figure 2 is a schematic diagram of concurrent scheduling in an embodiment of the present invention;

[0023] Figure 3 is a schematic diagram of a remote probe in an embodiment of the present invention;

[0024] Figure 4 is a structural block diagram of a middleware management device in an embodiment of the present invention;

[0025] Figure 5 It is a structural block diagram of a computer device in an embodiment of the present invention. DETAILED DESCRIPTION

[0026] The following will be combined with the drawings in the embodiments of the present invention to clearly and completely describe the technical solutions in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.

[0027] Those skilled in the art will appreciate that the embodiments of the present invention may be implemented as a system, device, apparatus, method or computer program product. Therefore, the present disclosure may be specifically implemented in the following forms, namely: complete hardware, complete software (including firmware, resident software, microcode, etc.), or a combination of hardware and software.

[0028] It should be noted that the middleware management method and device of the present invention can be used in middleware management scenarios in the financial field, and can also be used in any field other than the financial field. The embodiment of the present invention does not limit the application field of the middleware management method and device.

[0029] In view of the fact that the prior art is limited by the limitations of the software product itself, currently each WEB middleware can only be managed manually and individually, and it is impossible to achieve automated, large-scale concurrent centralized management, resulting in low management efficiency. The embodiments of the present invention provide a middleware management method and device, which can concurrently manage multiple WEB middlewares and dynamically adjust the concurrent management strategy according to the real-time status of the WEB middleware and the differences in business applications, thereby improving operation and maintenance management efficiency, optimizing the concurrent management mode, and reducing the occurrence of human omissions.

[0030] Figure 1 It is a flow chart of the middleware management method in an embodiment of the present invention. Figure 2 Schematic diagram of concurrent scheduling in an embodiment of the present invention. Figure 1 and Figure 2 As shown, the middleware management method includes:

[0031] S101: Determine core resource data and auxiliary resource data corresponding to the middleware.

[0032] Figure 3 Schematic diagram of a remote probe in an embodiment of the present invention. Figure 3 As shown, before executing S101, it also includes: obtaining core resource data, auxiliary resource data, application type, application level, application load quantity and configuration file corresponding to the middleware through a remote probe.

[0033] The role of the probe is to capture the information of the enterprise WEB middleware, which mainly includes three aspects: the key configuration (configuration file) of the enterprise WEB middleware itself, the application information deployed on it, and the running dynamics of the host server resources of the WEB middleware. The information obtained by the probe detection is the main determinant of the concurrency management strategy in the concurrent scheduling Concurrency Mgmt.

[0034] To construct a remote probe, first clarify the probe selection and what kind of probe to use; secondly, clarify the content of the probe detection, that is, what information related to the WEB middleware needs to be detected by the probe; finally, clarify the location of the probe detection, that is, where to detect and obtain information related to the WEB middleware. The construction of the probe is completed step by step according to the above three steps, which is described in detail as follows:

[0035] ① Probe selection: Design and construct dedicated probes based on the type and version of the WEB middleware host operating system. Determine the probe type based on the operating system type (such as AIX system, WINDOWS system and LINUX system), the operating system programming language (such as python language and java language, etc.), and the operating system-specific scripting language (such as vbs script, powershell script of WINDOWS system and shell script of LINUX system). Taking IBM WAS middleware as an example, the middleware is deployed on a Linux server, and shell scripts are used to implement the construction of the probe.

[0036] ② Detection content: refers to the content that the probe needs to detect from the WEB middleware, mainly including three aspects:

[0037] a. The configuration information (configuration file) of the WEB middleware itself. The configuration information of different types of middleware will be slightly different, generally including the installation and operation user, installation path, operating environment, external service name and external port of the WEB middleware.

[0038] b. Information about applications deployed on the WEB middleware, including the application type, application level, and load quantity of the deployed applications. The application type can be determined by judging whether the application belongs to an important portal application such as online banking or a system used by internal OA. The influence and business classification of different types of applications are very different. The load quantity refers to the number of applications deployed on the WEB middleware. A WEB middleware may deploy multiple lightweight WEB applications, or only one complex and important large-scale WEB application.

[0039] c. The resources of the WEB middleware on the host server refer to the CPU usage rate, memory data, IO read and write data, or other system resource usage load of the operating system on which the WEB middleware process depends.

[0040] ③ Detection location: After clarifying the probe detection content, it is necessary to determine the source of the probe information based on the detection content, that is, from which configuration file or parameter file of the WEB middleware does the probe obtain information, from which command result does it obtain information, from which related system does it obtain basic information, etc.

[0041] Taking IBM WAS middleware as an example, the probe construction process deployed on the Linux operating system is as follows:

[0042] 1. Probe selection: The WEB middleware is deployed on the Linux operating system, and the more common bash shell script is selected for probe construction.

[0043] 2. Detection content: The content that IBM WAS middleware needs to detect is as follows:

[0044] a. Configuration information of the WEB middleware itself: The configuration information of the WAS middleware that needs to be detected includes: installation user<INSTALL_USER> , Installation path<INSTALL_PATH> , Summary Path<PROFILE_PATH> 、Middleware external service name<WAS_SERVER_NAME> , Middleware external port<WAS_SERVER_PORT> , middleware status<WAS_SERVER_STATUS> And WAS security management features<WAS_SECURTY_USER> .

[0045] b. Application information deployed on the WEB middleware: application type and application level, which respectively represent the weight and impact of business applications. Usually, applications are divided into types and levels within the organization based on multiple dimensions such as external services and data importance. The number of application loads refers to the number of applications deployed on the IBM WAS middleware.

[0046] c. Resources of WEB middleware on the host server: IBM WAS middleware process, that is, the operating system resources consumed by the corresponding Java process, such as CPU usage, memory data or IO read and write data.

[0047] Detection location: Taking IBM WAS middleware as an example, the specific location information of the detection content is as follows:

[0048] a. Configuration information of the WEB middleware itself: You can obtain basic configuration information such as the installation user, installation path, and summary path of WAS by running the IBM WAS process or searching the IBM WAS required installation path keyword IBM / WebSphere / AppServer through the directory.

[0049] In one embodiment, the method further includes: determining a configuration file of the middleware according to basic configuration information of the middleware.

[0050] For example, the corresponding external service name, external port and security management characteristics can be obtained according to the following three WAS configuration files ProfileRegistry.xml, serverindex.xml and security.xml.

[0051] b. Application information deployed on WEB middleware: Application type or application level is generally obtained from the CMDB (Configuration Management Database) or other similar application repositories within the enterprise, or can be specified by user definition. The number of applications deployed by WAS middleware can be obtained through the following channels:<WAS_PROFILE_PATH> / config / cells / <CELL_NAME> / applications.

[0052] c. Resources of the WEB middleware on the host server: The corresponding real-time CPU usage, real-time memory data, or real-time IO read and write data can be obtained through the operating system (OS) commands top, vmstat, and iostat.

[0053] S102: Determine resource sorting data according to the auxiliary resource data and the core resource data.

[0054] There are WEB middlewares that deploy the same application in all kinds of applications. A non-basic application will be distributed and deployed on multiple WEB middlewares. There may be several, dozens, dozens or even hundreds of WEB middlewares deployed on the same application to achieve distributed deployment and load balancing. Although multiple basic applications share one WEB middleware, and the importance and external service weight of the basic application are relatively low, in view of system redundancy and backup considerations, there will be 1-2 WEB middlewares that deploy the same multiple basic applications. Multiple WEB middlewares that deploy the same application can be called isomorphic middlewares. Therefore, the decision factor considered by the present invention is for multiple isomorphic middlewares that deploy the same application.

[0055] In the specific implementation, the corresponding core resource data and auxiliary resource data are first determined according to the middleware application. For example, when the application is online banking, the core resource data is the CPU usage rate, and the auxiliary resource data is the memory data and IO read-write data; at this time, the CPU usage rate is adjusted according to the memory data and IO read-write data to determine the resource sorting data.

[0056] The selection of system core resources depends on the characteristics of the application. When the characteristics of the application are inclined towards computing and real-time processing, the core resource data is the CPU usage rate, and the auxiliary resource data is the memory data and IO read / write data. When the characteristics of the application are inclined towards IO processing and file processing, the core resource data is the IO read / write data, and the auxiliary resource data is the memory data and CPU usage rate, etc.

[0057] S103: Sort the corresponding middleware according to the resource sorting data, and process the sorted middleware in sequence.

[0058] During specific implementation, the resource sorting data corresponding to the middleware may be sorted in ascending order to determine the resource sorting data of the middleware.

[0059] In one embodiment, processing the sorted middleware in sequence includes:

[0060] The sorted middleware are processed in sequence according to the middleware configuration files.

[0061] Among them, the configuration file determined according to the configuration information of the WEB middleware itself is used to encapsulate and implement specific management operations, and the application information deployed on the WEB middleware and the resources of the host system are used to make subsequent scheduling decisions for concurrent management.

[0062] In specific implementation, the processing of WEB middleware at least includes starting and stopping. The processing operation is generally encapsulated based on the middleware function, and then pushed to the WEB middleware host server for execution through network protocols such as HTTP and FTP, and the background daemon thread is awakened in real time to monitor the execution status of the management operation. Take IBM WAS middleware as an example:

[0063] Startup is<WAS_PROFILE_PATH> / bin / startServer.sh performs function encapsulation;

[0064] Stop is right<WAS_PROFILE_PATH> / bin / stopServer.sh performs function encapsulation.

[0065] Figure 1 The execution subject of the middleware management method shown can be a computer. Figure 1 It can be seen from the process shown that the middleware management method of the embodiment of the present invention first determines the resource sorting data according to the auxiliary resource data and core resource data corresponding to the middleware, and then sorts the corresponding middleware according to the resource sorting data, and processes the sorted middleware in turn. It can perform concurrent and centralized management of large quantities of middleware, improve operation and maintenance management efficiency, and optimize the concurrent management mode.

[0066] In one embodiment, sorting the corresponding middleware according to the resource sorting data further includes: sorting the corresponding middleware according to the application type sorting data, the application level sorting data, the application load sorting data and the resource sorting data.

[0067] The centralized concurrent management operation of the WEB middleware is realized by encapsulating using the multithreading technology. The present invention realizes the concurrent operation of a large number of WEB middlewares by using the threading multithreading technology of the Python language.

[0068] In the scenario of managing a large number of WEB middleware, concurrent management is not performed in a simple order from first to last or according to the initial order selected by the user. The specificity of different WEB middleware should be fully considered for concurrent management scheduling. The present invention mainly considers the differences in business applications deployed by WEB middleware (including application level application type, application level application load) and the real-time load of host system resources. The scheduling strategy of concurrent queues can be summarized from high to low priority as follows: give priority to the application type or application level of business applications, make decisions within the same application type based on the application load of the middleware deployment, and finally make fine adjustments based on the real-time load of host system resources to generate resource sorting data.

[0069] In one embodiment, it also includes: determining application type sorting data and application intermediate sorting data according to the application type corresponding to the middleware.

[0070] In specific implementation, there are huge differences between different types of business applications. Usually, the definition of application types is defined and planned by the CMDB configuration management database. In the present invention, application types are specifically divided into the following four categories:

[0071] Category A applications (non-basic applications): important external service applications, such as online banking, mobile banking, ATM systems, etc.

[0072] Category B applications (non-basic applications): backend management systems for important external service applications involving important customer information, such as personal customer marketing and bank card auxiliary management.

[0073] Category C applications (non-basic applications): important enterprise basic systems, such as human resources systems and financial management systems.

[0074] Class D applications (basic applications): internal OA systems, such as attendance systems, etc.

[0075] In the above classification, Class A and Class B applications are extremely important business applications. In order to ensure business response speed and sufficient core resources of the host, there are generally no multiple applications competing for resources. Usually, only one Class A business application or Class B business application is deployed on a WEB middleware; at the same time, a distributed deployment is adopted, and a load balancing architecture is used through multiple WEB middlewares. Although Class C applications are not external service applications, they are also important basic systems, so they will also adopt an architecture similar to Class A applications or Class B applications. Class D applications are the applications with the largest number and the widest distribution, but because the importance of the applications is relatively low, multiple applications are usually deployed on one WEB middleware, and a load balancing architecture will also be adopted, that is, multiple identical applications will also be deployed on another WEB middleware in a set of environments with the same architecture.

[0076] In the concurrent application management of the present invention, adjustment is first performed according to the application type, so the application type sorting data is: Class A applications are in the first echelon of the concurrent queue, followed by Class B applications, Class C applications, and finally Class D applications.

[0077] In one embodiment, determining the application intermediate sorting data according to the application type corresponding to the middleware includes:

[0078] When the application type corresponding to the middleware is a basic application, determining the intermediate sorting data as application response sorting data;

[0079] When the application type corresponding to the middleware is a non-basic application, it is determined that the intermediate sorting data is application load sorting data.

[0080] In specific implementation, according to the above application classification, for non-basic applications (including Class A applications, Class B applications, and Class C applications), only one application is deployed on the WEB middleware, and the number of application loads is the same; while for basic applications (Class D applications), multiple lightweight WEB applications are generally deployed on the WEB middleware, and the number of load applications is different. Therefore, non-basic applications (including Class A applications, Class B applications, and Class C applications) and basic applications (Class D applications) need to be considered separately.

[0081] In one embodiment, it further includes:

[0082] 1. Determine application response sorting data according to application response data corresponding to the middleware.

[0083] In specific implementation, if non-basic applications (including Class A applications, Class B applications, and Class C applications) are deployed on the WEB middleware, and the data sorting decision cannot be made by the application load quantity within the same application level, the sorting data in the concurrent queue can be further subdivided and adjusted according to the response data, or the sorting data of different applications in the same category of applications can be adjusted by the user. For example, online banking and ATM are both Class A applications. If both online banking and ATM have further external response data, and the external response data of online banking is greater than the external response data of ATM, then the position of the WEB middleware where the online banking is located in the concurrent queue is before the ATM; if there is no such more detailed application division within the enterprise, the user can adjust it by himself or without adjustment. Therefore, the application response data corresponding to the middleware can be sorted in order from large to small to determine the application response sorting data of the middleware.

[0084] 2. Determine the application load sorting data according to the number of application loads corresponding to the middleware.

[0085] During specific implementation, after adjusting the concurrent queues according to different categories of business applications, the sorting in the concurrent queues can be further adjusted according to the number of application loads deployed on the WEB middleware.

[0086] If basic applications (class D applications) are deployed on the WEB middleware, scheduling decisions can be made based on the number of loads deployed on the middleware. Multiple lightweight WEB applications are usually deployed on the WEB middleware where the basic applications are located. The management operation time of the WEB middleware depends on the number of deployed applications. The more applications are deployed on the WEB middleware, the longer the waiting time for management operations. In addition, class D applications do not require extremely high external response speeds. In order to reduce the waiting time for management operations and improve user experience, the operation waiting time of the WEB middleware of class D applications can be balanced as much as possible. If the WEB middleware with many deployed applications is placed at the back end of the concurrent queue, the waiting time for its own management operations is also long, which is not conducive to user experience. Therefore, for the WEB middleware with multiple class D applications deployed, the number of application loads corresponding to the middleware can be sorted in order from large to small to determine the application load sorting data of the middleware. For example, if there are multiple WEB middlewares that are both OA applications, and 4 applications are deployed on one WEB middleware, and 6 applications are deployed on another WEB middleware, then the WEB middleware that deploys 6 applications will be adjusted to the front of the WEB middleware that deploys 4 applications.

[0087] In summary, for the middleware that has deployed Class D applications, the priority decision of the concurrent queue is made according to the number of application loads detected by the remote probe. The more applications are deployed, the higher their priority is in the concurrent queue within the same type of applications.

[0088] In summary, the specific process of the embodiment of the present invention is as follows:

[0089] 1. Determine the application type sorting data according to the application type corresponding to the middleware.

[0090] 2. Determine application response sorting data based on application response data corresponding to the middleware.

[0091] 3. Determine the application load sorting data according to the number of application loads corresponding to the middleware.

[0092] 4. Determine the core resource data and auxiliary resource data corresponding to the middleware.

[0093] 5. Determine resource sorting data based on auxiliary resource data and core resource data.

[0094] 6. When the application type corresponding to the middleware is a basic application, the corresponding middleware is sorted according to the application type sorting data, application response sorting data and resource sorting data; when the application type corresponding to the middleware is a non-basic application, the corresponding middleware is sorted according to the application type sorting data, application load sorting data and resource sorting data.

[0095] 7. Process the sorted middleware in sequence according to the middleware configuration file.

[0096] In summary, the middleware management method of the embodiment of the present invention adopts a customized remote probe to automatically detect the key configuration, application load and system load of the WEB middleware, realizes the centralized management of multiple WEB middleware through concurrent technology, and can dynamically and flexibly adjust the concurrent management mode according to the specificity and load of the WEB application in the concurrent centralized management. Compared with the traditional WEB middleware management mode, the present invention overcomes the disadvantage of only being able to manually manage one WEB middleware, realizes automation and batch management, greatly improves the work efficiency of WEB middleware management, and saves a lot of manpower and time costs.

[0097] Based on the same inventive concept, an embodiment of the present invention further provides a middleware management device. Since the principle of solving the problem by the device is similar to that of the middleware management method, the implementation of the device can refer to the implementation of the method, and the repeated parts will not be repeated.

[0098] Figure 4 is a structural block diagram of the middleware management device in an embodiment of the present invention. Figure 4 As shown, the middleware management device includes:

[0099] A resource determination module, used to determine the core resource data and auxiliary resource data corresponding to the middleware;

[0100] A resource sorting data module, used to determine resource sorting data based on auxiliary resource data and core resource data;

[0101] The middleware processing module is used to sort the corresponding middleware according to the resource sorting data and process the sorted middleware in sequence.

[0102] In summary, the middleware management device of the embodiment of the present invention first determines the resource sorting data according to the auxiliary resource data and core resource data corresponding to the middleware, and then sorts the corresponding middleware according to the resource sorting data, and processes the sorted middleware in sequence. It can concurrently and centrally manage a large number of middleware, improve the operation and maintenance management efficiency, and optimize the concurrent management mode.

[0103] The embodiment of the present invention also provides a specific implementation of a computer device capable of implementing all the steps in the middleware management method in the above embodiment. Figure 5 is a block diagram of a computer device in an embodiment of the present invention, see Figure 5 , the computer equipment specifically includes the following contents:

[0104] Processor (processor) 501 and memory (memory) 502.

[0105] The processor 501 is used to call the computer program in the memory 502. When the processor executes the computer program, all steps in the middleware management method in the above embodiment are implemented. For example, when the processor executes the computer program, the following steps are implemented:

[0106] Determine the core resource data and auxiliary resource data corresponding to the middleware;

[0107] Determine resource ranking data based on auxiliary resource data and core resource data;

[0108] The corresponding middleware is sorted according to the resource sorting data, and the sorted middleware is processed in sequence.

[0109] In summary, the computer device of the embodiment of the present invention first determines the resource sorting data according to the auxiliary resource data and core resource data corresponding to the middleware, and then sorts the corresponding middleware according to the resource sorting data, and processes the sorted middleware in sequence. It can concurrently and centrally manage a large number of middleware, improve the operation and maintenance management efficiency, and optimize the concurrent management mode.

[0110] The embodiment of the present invention also provides a computer-readable storage medium capable of implementing all the steps in the middleware management method in the above embodiment. The computer-readable storage medium stores a computer program. When the computer program is executed by a processor, all the steps in the middleware management method in the above embodiment are implemented. For example, when the processor executes the computer program, the following steps are implemented:

[0111] Determine the core resource data and auxiliary resource data corresponding to the middleware;

[0112] Determine resource ranking data based on auxiliary resource data and core resource data;

[0113] The corresponding middleware is sorted according to the resource sorting data, and the sorted middleware is processed in sequence.

[0114] In summary, the computer-readable storage medium of the embodiment of the present invention first determines the resource sorting data according to the auxiliary resource data and core resource data corresponding to the middleware, and then sorts the corresponding middleware according to the resource sorting data, and processes the sorted middleware in sequence, so as to perform concurrent centralized management of a large number of middleware, improve the efficiency of operation and maintenance management, and optimize the concurrent management mode.

[0115] The specific embodiments described above further illustrate the objectives, technical solutions and beneficial effects of the present invention in detail. It should be understood that the above description is only a specific embodiment of the present invention and is not intended to limit the scope of protection of the present invention. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of the present invention should be included in the scope of protection of the present invention.

[0116] Those skilled in the art may also understand that the various illustrative logical blocks, units, and steps listed in the embodiments of the present invention may be implemented by electronic hardware, computer software, or a combination of the two. In order to clearly demonstrate the interchangeability of hardware and software, the various illustrative components, units, and steps described above have generally described their functions. Whether such functions are implemented by hardware or software depends on the specific application and the design requirements of the entire system. Those skilled in the art may use various methods to implement the described functions for each specific application, but such implementation should not be understood as exceeding the scope of protection of the embodiments of the present invention.

[0117] The various illustrative logic blocks, or units, or devices described in the embodiments of the present invention can be implemented or operated by a general-purpose processor, a digital signal processor, an application-specific integrated circuit (ASIC), a field programmable gate array or other programmable logic device, a discrete gate or transistor logic, a discrete hardware component, or any combination of the above. The general-purpose processor can be a microprocessor, and optionally, the general-purpose processor can also be any conventional processor, controller, microcontroller or state machine. The processor can also be implemented by a combination of computing devices, such as a digital signal processor and a microprocessor, a plurality of microprocessors, one or more microprocessors combined with a digital signal processor core, or any other similar configuration.

[0118] The steps of the method or algorithm described in the embodiments of the present invention can be directly embedded in hardware, a software module executed by a processor, or a combination of the two. The software module can be stored in a RAM memory, a flash memory, a ROM memory, an EPROM memory, an EEPROM memory, a register, a hard disk, a removable disk, a CD-ROM, or other storage media of any form in the art. Exemplarily, the storage medium can be connected to the processor so that the processor can read information from the storage medium and can write information to the storage medium. Optionally, the storage medium can also be integrated into the processor. The processor and the storage medium can be arranged in an ASIC, and the ASIC can be arranged in a user terminal. Optionally, the processor and the storage medium can also be arranged in different components in the user terminal.

[0119] In one or more exemplary designs, the above functions described in the embodiments of the present invention can be implemented in hardware, software, firmware or any combination of the three. If implemented in software, these functions can be stored on a computer-readable medium, or transmitted in the form of one or more instructions or codes on a computer-readable medium. Computer-readable media include computer storage media and communication media that facilitate the transfer of computer programs from one place to another. The storage medium can be any available medium that can be accessed by any general or special computer. For example, such computer-readable media can include but are not limited to RAM, ROM, EEPROM, CD-ROM or other optical disk storage, disk storage or other magnetic storage devices, or any other medium that can be used to carry or store program codes in the form of instructions or data structures and other forms that can be read by general or special computers, or general or special processors. In addition, any connection can be appropriately defined as a computer-readable medium, for example, if the software is transmitted from a website site, server or other remote resource through a coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL) or wirelessly, such as infrared, wireless and microwave, it is also included in the defined computer-readable medium. The disk and disc include compact disk, laser disk, optical disk, DVD, floppy disk and blue-ray disk. Disks usually copy data magnetically, while discs usually copy data optically with lasers. The above combination can also be included in computer readable media.

Claims

1. A middleware management method, characterized in that: include: Determine the core resource data and auxiliary resource data corresponding to the middleware; Determine resource sorting data according to the auxiliary resource data and the core resource data; Sorting the corresponding middleware according to the resource sorting data, and processing the sorted middleware in sequence; Wherein, sorting the corresponding middleware according to the resource sorting data further includes: The corresponding middleware is sorted according to the application type sorting data, the application level sorting data, the application load sorting data and the resource sorting data.

2. The middleware management method according to claim 1, characterized in that: Also includes: The application type sorting data and the application intermediate sorting data are determined according to the application type corresponding to the middleware.

3. The middleware management method according to claim 2, characterized in that: Determining the application intermediate sorting data according to the application type corresponding to the middleware includes: When the application type corresponding to the middleware is a basic application, determining that the application intermediate sorting data is application response sorting data; When the application type corresponding to the middleware is a non-basic application, it is determined that the application intermediate sorting data is application load sorting data.

4. The middleware management method according to claim 3, characterized in that: Also includes: Determine the application response sorting data according to the application response data corresponding to the middleware; The application load sorting data is determined according to the number of application loads corresponding to the middleware.

5. The middleware management method according to claim 1, characterized in that: The sorted middleware is processed in sequence including: The sorted middleware are processed in sequence according to the middleware configuration files.

6. The middleware management method according to claim 5, characterized in that: Also includes: The configuration file of the middleware is determined according to the basic configuration information of the middleware.

7. A middleware management device, characterized in that: include: A resource determination module, used to determine the core resource data and auxiliary resource data corresponding to the middleware; A resource sorting data module, used to determine resource sorting data according to the auxiliary resource data and the core resource data; A middleware processing module, used to sort the corresponding middleware according to the resource sorting data, and process the sorted middleware in sequence; Wherein, sorting the corresponding middleware according to the resource sorting data further includes: The corresponding middleware is sorted according to the application type sorting data, the application level sorting data, the application load sorting data and the resource sorting data.

8. A computer device comprising a memory, a processor, and a computer program stored in the memory and running on the processor, characterized in that: When the processor executes the computer program, the steps of the middleware management method according to any one of claims 1 to 6 are implemented.

9. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the steps of the middleware management method according to any one of claims 1 to 6 are implemented.

Images