CN117421036A

CN117421036A - Component management method, device, electronic equipment and computer readable storage medium

Info

Publication number: CN117421036A
Application number: CN202311395361.6A
Authority: CN
Inventors: 李游城
Original assignee: Ping An Life Insurance Company of China Ltd
Current assignee: Ping An Life Insurance Company of China Ltd
Priority date: 2023-10-25
Filing date: 2023-10-25
Publication date: 2024-01-19

Abstract

The application relates to the technical field of financial science and technology, and provides a component management method, a device, electronic equipment and a computer readable storage medium, wherein the method comprises the following steps: acquiring a system configuration file; determining a plurality of dependency profiles from a system configuration file; performing first traversal processing on the plurality of dependency description files to obtain a plurality of configuration parameter information; performing second traversal processing on the configuration parameter information to obtain a plurality of component resource packages; sequentially comparing the elements of each component resource package with a preset resource merging strategy; under the condition that the elements of the component resource packages meet the resource merging strategy, merging the corresponding component resource packages; and under the condition that the elements of the component resource packages do not meet the resource merging strategy, feeding back the resource package marks of the corresponding component resource packages to a preset monitoring server. Through the technical scheme, the maintenance process of the component resource package is simplified, and the maintenance cost is reduced.

Description

Component management method, device, electronic equipment and computer readable storage medium

Technical Field

Embodiments of the present disclosure relate to, but are not limited to, the technical field of financial technology, and in particular, to a component management method, device, electronic apparatus, and computer readable storage medium.

Background

In current financial systems, such as banking systems, insurance systems, or securities systems, various components are increasingly utilized to implement system functions; the system realizes project modularization, wherein all components are managed mainly through a dependency manager; the base component and the business component each generate a dependency description file that typically contains multiple components. The basic components generally comprise service-independent components such as a bullet box, a list and the like; the service components typically include components related to the service such as login, authentication, etc. A plurality of basic components and a plurality of business components are introduced into a project, codes of all components under a dependent configuration file are combined into a static file when the project is packaged, but resource package files are not combined, so that a plurality of resource package files exist, the process of processing the resource package files at the later stage is relatively complicated, and the maintenance cost is high.

Disclosure of Invention

The following is a summary of the subject matter described in detail herein. This summary is not intended to limit the scope of the claims.

In order to solve the problems mentioned in the background art, embodiments of the present application provide a method, an apparatus, an electronic device, and a computer readable storage medium for managing components, which simplify a maintenance process of a component resource package and reduce maintenance cost.

In a first aspect, an embodiment of the present application provides a component management method, including:

acquiring a system configuration file;

determining a plurality of dependency profiles from the system configuration file;

performing first traversal processing on the plurality of dependency description files to obtain a plurality of configuration parameter information, wherein the configuration parameter information corresponds to the dependency description files one by one;

performing second traversal processing on the configuration parameter information to obtain a plurality of component resource packages, wherein the component resource packages are in one-to-one correspondence with the configuration parameter information;

sequentially comparing the elements of each component resource package with a preset resource merging strategy;

under the condition that the elements of the component resource packages meet the resource merging strategy, merging the corresponding component resource packages; and under the condition that the elements of the component resource package do not meet the resource merging strategy, feeding back the resource package mark of the corresponding component resource package to a preset monitoring server.

According to some embodiments of the present application, the determining a plurality of dependency profiles from the system configuration files includes:

performing file type analysis processing on the system configuration file to obtain file type information and file configuration information;

Extracting a plurality of class description files from the system configuration file according to the file type information;

and screening a plurality of dependency description files from the plurality of class description files according to the file configuration information.

According to some embodiments of the present application, in a case where the element of the component resource package meets the resource merging policy, the merging processing of the corresponding component resource package includes:

feeding back the corresponding component resource package to a preset client under the condition that the number of sub-elements of the elements in the component resource package is not more than a preset array length threshold;

and carrying out combination processing on the corresponding component resource packages in the client to obtain a combined resource package.

According to some embodiments of the present application, in a case where the element of the component resource package does not satisfy the resource merge policy, feeding back a resource package label of the corresponding component resource package to a preset monitoring server, where the method includes:

feeding back the corresponding component resource package to a preset client under the condition that the number of the sub-elements of the elements in the component resource package is larger than a preset array length threshold;

and forwarding the corresponding component resource package to the monitoring server based on the client.

According to some embodiments of the present application, after the merging processing is performed on the component resource packages in the client to obtain a merged resource package, the method further includes:

acquiring resource package request information;

analyzing and processing the resource package request information to obtain resource package path information and resource package name information;

and extracting the corresponding component resource package from the combined resource package according to the resource package path information and the resource package name information.

According to some embodiments of the present application, when the element of the component resource package does not satisfy the resource merge policy, the method further includes, after feeding back a resource package label of the corresponding component resource package to a preset monitoring server, the method further includes:

performing attribute analysis processing on the resource package mark of the component resource package based on the monitoring server to obtain resource package attribute information;

compressing the corresponding component resource package based on the resource package attribute information to obtain a component resource compressed package;

the target database address is obtained, and the component resource compression packet is forwarded to the target database according to the target database address.

According to some embodiments of the present application, the performing a first traversal process on the plurality of dependency description files to obtain a plurality of configuration parameter information includes:

Acquiring configuration mark information, wherein the configuration mark information comprises mark type information;

searching the plurality of dependent description files based on the mark type information to obtain a plurality of file parameter information;

and performing configuration information screening processing on the plurality of file parameter information to obtain a plurality of configuration parameter information.

In a second aspect, an embodiment of the present application further provides a component management apparatus, where the apparatus includes:

the first processing module is used for acquiring a system configuration file;

the second processing module is used for determining a plurality of dependency description files from the system configuration files;

the third processing module is used for performing first traversal processing on the plurality of the dependency description files to obtain a plurality of configuration parameter information, wherein the configuration parameter information corresponds to the dependency description files one by one;

the fourth processing module is used for performing second traversal processing on the configuration parameter information to obtain a plurality of component resource packages, wherein the component resource packages are in one-to-one correspondence with the configuration parameter information;

a fifth processing module, configured to compare elements of each component resource package with a preset resource merging policy in sequence;

a sixth processing module, configured to, when the element of the component resource packet meets the resource merging policy, merge the corresponding component resource packet; and under the condition that the elements of the component resource package do not meet the resource merging strategy, feeding back the resource package mark of the corresponding component resource package to a preset monitoring server.

In a third aspect, an embodiment of the present application further provides an electronic device, including: a memory, a processor and a computer program stored on the memory and executable on the processor, the processor implementing the component management method as described in the first aspect above when executing the computer program.

In a fourth aspect, embodiments of the present application further provide a computer-readable storage medium storing computer-executable instructions for performing the component management method according to the first aspect above.

According to the component management method provided by the embodiment of the application, the component management method has at least the following beneficial effects: in the process of component management, firstly, acquiring a system configuration file; then determining a plurality of dependency description files from the system configuration files; then, performing first traversal processing on the plurality of dependent description files to obtain a plurality of configuration parameter information, wherein the configuration parameter information corresponds to the dependent description files one by one; then, performing second traversal processing on the plurality of configuration parameter information to obtain a plurality of component resource packages, wherein the component resource packages correspond to the configuration parameter information one by one; sequentially comparing the elements of each component resource package with a preset resource merging strategy; under the condition that the elements of the component resource packages meet the resource merging strategy, merging the corresponding component resource packages; and under the condition that the elements of the component resource packages do not meet the resource merging strategy, feeding back the resource package marks of the corresponding component resource packages to a preset monitoring server. Through the technical scheme, the maintenance process of the component resource package is simplified, and the maintenance cost is reduced.

Drawings

The accompanying drawings are included to provide a further understanding of the technical aspects of the present application, and are incorporated in and constitute a part of this specification, illustrate the technical aspects of the present application and together with the examples of the present application, and not constitute a limitation of the technical aspects of the present application.

FIG. 1 is a flow chart of a component management method provided by one embodiment of the present application;

FIG. 2 is a specific flow chart of step S200 provided in one embodiment of the present application;

FIG. 3 is a specific flowchart of step S610 provided in one embodiment of the present application;

FIG. 4 is a specific flowchart of step S620 provided in one embodiment of the present application;

FIG. 5 is a specific flow chart of a component management method provided in another embodiment of the present application;

FIG. 6 is a specific flow chart of a component management method provided in another embodiment of the present application;

FIG. 7 is a specific flowchart of step S300 provided in one embodiment of the present application;

FIG. 8 is a schematic diagram of a component management apparatus provided in one embodiment of the present application;

fig. 9 is a schematic diagram of an electronic device provided in an embodiment of the present application.

Detailed Description

In order to make the objects, technical solutions and advantages of the present application more apparent, the present application will be further described in detail with reference to the accompanying drawings and examples. It should be understood that the specific embodiments described herein are for purposes of illustration only and are not intended to limit the present application.

It should be noted that although functional block division is performed in the apparatus schematic and logical order is shown in the flowchart, in some cases, the steps shown or described may be performed in a different order than block division in the apparatus or in the flowchart. The terms first, second and the like in the description and in the claims and in the above-described figures, are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order.

It is noted that unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this application belongs. The terminology used herein is for the purpose of describing embodiments of the present application only and is not intended to be limiting of the present application.

The embodiment of the application can acquire and process the related data based on the artificial intelligence technology. Among these, artificial intelligence (Artificial Intelligence, AI) is the theory, method, technique and application system that uses a digital computer or a digital computer-controlled machine to simulate, extend and extend human intelligence, sense the environment, acquire knowledge and use knowledge to obtain optimal results.

AI is a new technical science to study, develop theories, methods, techniques and application systems for simulating, extending and expanding human intelligence; artificial intelligence is a branch of computer science that attempts to understand the nature of intelligence and to produce a new intelligent machine that can react in a manner similar to human intelligence, research in this field including robotics, language recognition, image recognition, natural language processing, and expert systems. Artificial intelligence can simulate the information process of consciousness and thinking of people. Artificial intelligence is also a theory, method, technique, and application system that utilizes a digital computer or digital computer-controlled machine to simulate, extend, and expand human intelligence, sense the environment, acquire knowledge, and use knowledge to obtain optimal results.

Artificial intelligence infrastructure technologies generally include technologies such as sensors, dedicated artificial intelligence chips, cloud computing, distributed storage, big data processing technologies, operation/interaction systems, mechatronics, and the like. The artificial intelligence software technology mainly comprises a computer vision technology, a robot technology, a biological recognition technology, a voice processing technology, a natural language processing technology, machine learning/deep learning and other directions.

The artificial intelligence is AI, which is the theory, method, technique and application system that uses digital computer or the machine controlled by digital computer to simulate, extend and expand the human intelligence, sense the environment, acquire knowledge and use knowledge to obtain the best result.

The server related to the artificial intelligence technology can be an independent server, or can be a cloud server for providing cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, content delivery networks (Content Delivery Network, CDNs), basic cloud computing services such as big data and artificial intelligence platforms, and the like.

The application provides a method, a device, electronic equipment and a computer readable storage medium for managing components, wherein in the process of managing components, a system configuration file is firstly acquired; then determining a plurality of dependency description files from the system configuration files; then, performing first traversal processing on the plurality of dependent description files to obtain a plurality of configuration parameter information, wherein the configuration parameter information corresponds to the dependent description files one by one; then, performing second traversal processing on the plurality of configuration parameter information to obtain a plurality of component resource packages, wherein the component resource packages correspond to the configuration parameter information one by one; sequentially comparing the elements of each component resource package with a preset resource merging strategy; under the condition that the elements of the component resource packages meet the resource merging strategy, merging the corresponding component resource packages; and under the condition that the elements of the component resource packages do not meet the resource merging strategy, feeding back the resource package marks of the corresponding component resource packages to a preset monitoring server. Through the technical scheme, the maintenance process of the component resource package is simplified, and the maintenance cost is reduced.

The embodiment of the application provides a component management method, which relates to the technical field of financial science and technology. The component management method provided by the embodiment of the application can be applied to a terminal, a server side and software running in the terminal or the server side. In some embodiments, the terminal may be a smart phone, tablet, notebook, desktop, etc.; the server side can be configured as an independent physical server, a server cluster or a distributed system formed by a plurality of physical servers, and a cloud server for providing cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, CDNs, basic cloud computing services such as big data and artificial intelligent platforms and the like; the software may be an application or the like that implements the component management method, but is not limited to the above form.

The subject application is operational with numerous general purpose or special purpose computer system environments or configurations. For example: personal computers, server computers, hand-held or portable devices, tablet devices, multiprocessor systems, microprocessor-based systems, set top boxes, programmable consumer electronics, network PCs, minicomputers, mainframe computers, distributed computing environments that include any of the above systems or devices, and the like. The application may be described in the general context of computer-executable instructions, such as program modules, being executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types. The application may also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules may be located in both local and remote computer storage media including memory storage devices.

It should be noted that, in each specific embodiment of the present application, when related processing is required according to user information, user behavior data, user history data, user location information, and other data related to user identity or characteristics, permission or consent of the user is obtained first, and the collection, use, processing, and the like of these data comply with related laws and regulations and standards. In addition, when the embodiment of the application needs to acquire the sensitive personal information of the user, the independent permission or independent consent of the user is acquired through a popup window or a jump to a confirmation page or the like, and after the independent permission or independent consent of the user is explicitly acquired, necessary user related data for enabling the embodiment of the application to normally operate is acquired.

Embodiments of the present application are further described below with reference to the accompanying drawings.

As shown in fig. 1, fig. 1 is a flowchart of a component management method provided in one embodiment of the present application, including, but not limited to, steps S100 to S620.

Step S100, acquiring a system configuration file;

step S200, determining a plurality of dependency description files from a system configuration file;

Step S300, performing first traversal processing on a plurality of dependency description files to obtain a plurality of configuration parameter information, wherein the configuration parameter information corresponds to the dependency description files one by one;

step S400, performing second traversal processing on the configuration parameter information to obtain a plurality of component resource packages, wherein the component resource packages correspond to the configuration parameter information one by one;

step S500, sequentially comparing the elements of each component resource package with a preset resource merging strategy;

step S610, under the condition that the elements of the component resource packages meet the resource merging strategy, merging the corresponding component resource packages;

step S620, feeding back the resource package mark of the corresponding component resource package to a preset monitoring server under the condition that the elements of the component resource package do not meet the resource merging strategy.

In the process of managing the components, firstly, acquiring a system configuration file; then determining a plurality of dependency description files from the system configuration files; then, performing first traversal processing on the plurality of dependent description files to obtain a plurality of configuration parameter information, wherein the configuration parameter information corresponds to the dependent description files one by one; then, performing second traversal processing on the plurality of configuration parameter information to obtain a plurality of component resource packages, wherein the component resource packages correspond to the configuration parameter information one by one; sequentially comparing the elements of each component resource package with a preset resource merging strategy; under the condition that the elements of the component resource packages meet the resource merging strategy, merging the corresponding component resource packages; and under the condition that the elements of the component resource packages do not meet the resource merging strategy, feeding back the resource package marks of the corresponding component resource packages to a preset monitoring server. Through the technical scheme, the maintenance process of the component resource package is simplified, and the maintenance cost is reduced.

Notably, financial project componentization manages all components primarily by relying on a financial manager; the base component and the business component each generate a dependency description file; a dependency description file typically contains multiple components. The basic components generally comprise service-independent components such as a bullet box, a list and the like; the service components include components related to the service such as login, authentication, etc. Introducing a plurality of basic components and a plurality of business components into a financial project, and when the financial project is packaged, the codes of all the components under a dependent configuration file are required to be combined into a static file, but the resource package files are not combined, so that a plurality of resource file packages exist; no matter the component maintainer adds, deletes and updates the resource file package, for the financial project, the resource package needs to be confirmed to be newly added, deleted and updated, and then corresponding operation is performed, so that high maintenance cost and easy misoperation are brought. Through the technical scheme, a plurality of component resource packages can be obtained through performing second traversal processing on the plurality of configuration parameter information in sequence, wherein the component resource packages correspond to the configuration parameter information one by one, then elements of each component resource package are compared with a preset resource merging strategy in sequence, under the condition that the elements of the component resource packages meet the resource merging strategy, the corresponding component resource packages are merged, under the condition that the elements of the component resource packages do not meet the resource merging strategy, the resource package marks of the corresponding component resource packages are fed back to a preset monitoring server, maintenance processes of the component resource packages are simplified, and maintenance cost is reduced.

Notably, the dependency description file is primarily used to describe versions, names, code, resources, etc. of the various components; the component needs to use the resources in the resource package file, and obtains the corresponding resource content through the resource package path and the resource name; the method comprises the steps of reading the resource content of a component, needing to be transmitted into a resource package name and a resource name, packaging, merging the resource packages of all components into a resource package, and renaming the resource into a format of 'resource package_resource name' in the process of merging the resources so as to obtain the resource content. By the technical scheme, development efficiency can be improved, development difficulty is reduced, misoperation is reduced, no matter the resource package is added, deleted or updated, no modification is needed for a business party; and also makes the configuration more flexible.

In the process of managing the component, firstly, a system configuration file is acquired, then a plurality of dependency description files are determined from the system configuration file, and then a first traversal process is performed on the plurality of dependency description files to obtain a plurality of configuration parameter information; then, performing second traversal processing on the configuration parameter information to obtain a plurality of component resource packages; then sequentially comparing the elements of each component resource package with a preset resource merging strategy; under the condition that the elements of the component resource packages meet the resource merging strategy, merging the corresponding component resource packages; and under the condition that the elements of the component resource packages do not meet the resource merging strategy, feeding back the resource package marks of the corresponding component resource packages to a preset monitoring server. The monitoring server may be a monitoring server.

It is noted that the system configuration file includes a plurality of dependency description files, a first traversing process is performed on the plurality of dependency description files to obtain a plurality of configuration parameter information, a second traversing process is performed on the plurality of configuration parameter information to obtain a plurality of component resource packages, finally, the component resource packages are compared with a preset resource merging strategy, and then, corresponding operation processing can be performed on the component resource packages according to a comparison result.

In some embodiments, as shown in fig. 2, the step S200 may include, but is not limited to, step S210, step S220, and step S230.

Step S210, carrying out file type analysis processing on a system configuration file to obtain file type information and file configuration information;

step S220, extracting a plurality of class description files from the system configuration file according to the file type information;

step S230, a plurality of dependency description files are screened out from a plurality of class description files according to the file configuration information.

In the process of determining a plurality of dependency description files from a system configuration file, firstly, performing file type analysis processing on the system configuration file to obtain file type information and file configuration information; extracting a plurality of class description files from the system configuration file according to the file type information; and finally, screening a plurality of dependency description files from the plurality of class description files according to the file configuration information.

Notably, the file type information and the file configuration information can be obtained by analyzing and processing the types of the files in the system configuration file; because the file type of the class description file is fixed, a plurality of class description files can be extracted from the system configuration file according to the file type information, and finally a plurality of dependency description files are screened from the plurality of class description files according to the file configuration information.

In some embodiments, as shown in fig. 3, the step S610 may further include, but is not limited to, step S611 to step S612.

Step S611, feeding back the corresponding component resource package to a preset client under the condition that the number of sub-elements of the elements in the component resource package is not more than a preset array length threshold;

step S612, the corresponding component resource packages are combined in the client to obtain combined resource packages.

It should be noted that, when the elements of the component resource package meet the resource merging policy, in the process of merging the corresponding component resource package, if the number of sub-elements of the elements in the component resource package is not greater than the preset array length threshold, feeding back the corresponding component resource package to the preset client; and then, carrying out combination processing on the corresponding component resource package in the client to obtain the corresponding combination resource package.

It should be noted that the preset array length threshold may be set according to the actual situation, and the threshold is not fixed. And feeding back the corresponding component resource package to a preset client under the condition that the number of sub-elements of the elements in the component resource package is not more than a preset array length threshold value, and preparing for combining the subsequent component resource packages. The corresponding component resource packages are combined in the client, so that the maintenance cost can be well saved, and the component maintenance process is simplified.

In some embodiments, as shown in fig. 4, the step S620 may further include, but is not limited to, step S621 and step S622.

Step S621, feeding back the corresponding component resource package to a preset client under the condition that the number of sub-elements of the elements in the component resource package is larger than a preset array length threshold;

step S622, forwarding the corresponding component resource package to the monitoring server based on the client.

It should be noted that, when the number of sub-elements of the elements in the component resource package is greater than the preset array length threshold, in the process of feeding back the corresponding component resource package to the preset client, the corresponding component resource package is fed back to the preset client, and then the client can forward the corresponding component resource package to the corresponding monitoring server; and the component resource packages are uniformly managed based on the monitoring server, so that the development efficiency is improved, and the development difficulty is reduced.

In some embodiments, as shown in fig. 5, after the step S612 is performed, steps S613 to S615 may be further included, but are not limited to.

Step S613, obtaining resource package request information;

step S614, analyzing and processing the resource package request information to obtain resource package path information and resource package name information;

step S615, extracting the corresponding component resource package from the combined resource package according to the resource package path information and the resource package name information.

It should be noted that, after the corresponding component resource packages are combined in the client to obtain the combined resource packages, the resource package request information can also be obtained, and then the resource package request information is analyzed to obtain the resource package path information and the resource package name information; and finally, extracting the corresponding component resource package from the combined resource package according to the resource package path information and the resource package name information, thereby realizing the stable and rapid extraction of the component resource package.

Notably, the component resource packages can be determined from the consolidated resource packages based on the resource package path information and the resource package name information; for an insurance query system, firstly acquiring insurance information query request information, and further determining corresponding resource package request information through the insurance information query request information; then analyzing and processing the resource package request information to obtain resource package path information and resource package name information; and finally, extracting a corresponding component resource package from the combined resource package according to the resource package path information and the resource package name information, and realizing insurance information query operation based on the corresponding component resource package.

In some embodiments, as shown in fig. 6, step S623, step S624, and step S625 may be included after step S622 is performed.

Step S623, performing attribute analysis processing on the resource package mark of the component resource package based on the monitoring server to obtain resource package attribute information;

step S624, compressing the corresponding component resource package based on the resource package attribute information to obtain a component resource compressed package;

step S625, the target database address is obtained, and the component resource compression package is forwarded to the target database according to the target database address.

It should be noted that, after forwarding the corresponding component resource package to the monitoring server based on the client, the monitoring server may perform attribute analysis processing on the resource package label of the component resource package to obtain resource package attribute information; and finally, compressing the corresponding component resource package based on the resource package attribute information. By the technical scheme, the selected component resource package can be compressed to obtain the component resource compressed package; then, a target database address is obtained, and the component resource compression packet is forwarded to a target database according to the target database address; in the insurance system, insurance area information is of little concern to an underwriter, so that related component resource packages with the function of insurance area information inquiry can be compressed, system storage intervals occupied by components are reduced, the system is ensured to have higher storage intervals, and the system can be ensured to operate efficiently; and finally, forwarding the obtained component resource compression packet to a target database for storage processing so as to facilitate subsequent component calling processing.

In some embodiments, as shown in fig. 7, the step S300 may further include, but is not limited to, step S310, step S320, and step S330.

Step S310, configuration mark information is obtained, wherein the configuration mark information comprises mark type information;

step S320, searching and processing the plurality of dependency description files based on the mark type information to obtain a plurality of file parameter information;

step S330, performing configuration information screening processing on the plurality of file parameter information to obtain a plurality of configuration parameter information.

In the process of performing a first traversal process on the plurality of dependency description files to obtain a plurality of configuration parameter information, configuration mark information is firstly obtained, wherein the configuration mark information comprises mark type information; then searching the plurality of dependency description files based on the mark type information to obtain a plurality of file parameter information; and finally, carrying out configuration information screening processing on the plurality of file parameter information to obtain a plurality of configuration parameter information. Because the file parameter information carries the mark type information, a plurality of dependent description files can be searched based on the mark type information to obtain corresponding file parameter information; and finally, carrying out configuration information screening processing on the plurality of file parameter information to obtain a plurality of configuration parameter information.

In addition, as shown in fig. 8, an embodiment of the present application further provides a component management apparatus 10, including:

a first processing module 100, configured to obtain a system configuration file;

a second processing module 200 for determining a plurality of dependency profiles from the system configuration file;

the third processing module 300 is configured to perform a first traversal process on the plurality of dependency description files to obtain a plurality of configuration parameter information, where the configuration parameter information corresponds to the dependency description files one by one;

a fourth processing module 400, configured to perform a second traversal process on the plurality of configuration parameter information to obtain a plurality of component resource packages, where the component resource packages are in one-to-one correspondence with the configuration parameter information;

a fifth processing module 500, configured to compare elements of each component resource package with a preset resource merging policy in sequence;

a sixth processing module 600, configured to, when an element of the component resource package meets a resource merging policy, merge the corresponding component resource package; and under the condition that the elements of the component resource packages do not meet the resource merging strategy, feeding back the resource package marks of the corresponding component resource packages to a preset monitoring server.

The specific implementation of the component management apparatus 10 is substantially the same as the specific embodiment of the component management method described above, and will not be described herein.

In addition, as shown in fig. 9, an embodiment of the present application further provides an electronic device 700, including: memory 720, processor 710, and computer programs stored on memory 720 and executable on processor 710.

Processor 710 and memory 720 may be connected by a bus or other means.

The non-transitory software programs and instructions required to implement the component management methods of the above embodiments are stored in the memory 720, and when executed by the processor 710, the component management methods of the above embodiments are performed, for example, the method steps S100 to S620 in fig. 1, the method steps S210 to S230 in fig. 2, the method steps S611 to S612 in fig. 3, the method steps S621 to S622 in fig. 4, the method steps S613 to S615 in fig. 5, the method steps S623 to S625 in fig. 6, and the method steps S310 to S330 in fig. 7 described above are performed.

The above described apparatus embodiments are merely illustrative, wherein the units illustrated as separate components may or may not be physically separate, i.e. may be located in one place, or may be distributed over a plurality of network elements. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

Furthermore, an embodiment of the present application provides a computer-readable storage medium storing computer-executable instructions that are executed by a processor 710 or a controller, for example, by the processor 710 in the above-described device embodiment, which may cause the processor 710 to perform the component management method in the above-described embodiment, for example, to perform the method steps S100 to S620 in fig. 1, the method steps S210 to S230 in fig. 2, the method steps S611 to S612 in fig. 3, the method steps S621 to S622 in fig. 4, the method steps S613 to S615 in fig. 5, the method steps S623 to S625 in fig. 6, and the method steps S310 to S330 in fig. 7 described above.

The embodiments described above may be combined, and modules with the same names may be the same or different between different embodiments.

The foregoing describes certain embodiments of the present application, other embodiments being within the scope of the following claims. In some cases, the actions or steps recited in the claims can be performed in a different order than in the embodiments and still achieve desirable results. Furthermore, the processes depicted in the accompanying drawings do not necessarily have to be in the particular order shown, or sequential order, to achieve desirable results. In some embodiments, multitasking and parallel processing are also possible or may be advantageous.

All embodiments in the application are described in a progressive manner, and identical and similar parts of all embodiments are mutually referred, so that each embodiment mainly describes differences from other embodiments. In particular, for apparatus, devices, computer readable storage medium embodiments, the description is relatively simple as it is substantially similar to method embodiments, with reference to the section of the method embodiments being relevant.

The apparatus, the device, the computer readable storage medium and the method provided in the embodiments of the present application correspond to each other, and therefore, the apparatus, the device, the non-volatile computer storage medium also have similar beneficial technical effects as those of the corresponding method, and since the beneficial technical effects of the method have been described in detail above, the beneficial technical effects of the corresponding apparatus, device, and computer storage medium are not described here again.

In the 90 s of the 20 th century, improvements to one technology could clearly be distinguished as improvements in hardware (e.g., improvements to circuit structures such as diodes, transistors, switches, etc.) or software (improvements to the process flow). However, with the development of technology, many improvements of the current method flows can be regarded as direct improvements of hardware circuit structures. Designers almost always obtain corresponding hardware circuit structures by programming improved method flows into hardware circuits. Therefore, an improvement of a method flow cannot be said to be realized by a hardware entity module. For example, a programmable logic device (Programmable Logic Device, PLD) (e.g., field programmable gate array (Field Programmable Gate Array, FPGA)) is an integrated circuit whose logic function is determined by the programming of the device by a user. A designer programs to "integrate" a digital system onto a PLD without requiring the chip manufacturer to design and fabricate application-specific integrated circuit chips. Moreover, nowadays, instead of manually manufacturing integrated circuit chips, such programming is mostly implemented by using "logic compiler" software, which is similar to the software compiler used in program development and writing, and the original code before the compiling is also written in a specific programming language, which is called hardware description language (Hardware Description Language, HDL), but not just one of the hdds, but a plurality of kinds, such as ABEL (Advanced Boolean Expression Language), AHDL (Altera Hardware Description Language), confluence, CUPL (Cornell University Programming Language), HDCal, JHDL (Java Hardware Description Language), lava, lola, myHDL, PALASM, RHDL (Ruby Hardware Description Language), etc., VHDL (Very-High-Speed Integrated Circuit Hardware Description Language) and Verilog are currently most commonly used. It will also be apparent to those skilled in the art that a hardware circuit implementing the logic method flow can be readily obtained by merely slightly programming the method flow into an integrated circuit using several of the hardware description languages described above.

The controller may be implemented in any suitable manner, for example, the controller may take the form of, for example, a microprocessor or processor and a computer readable medium storing computer readable program code (e.g., software or firmware) executable by the (micro) processor, logic gates, switches, application specific integrated circuits (Application Specific Integrated Circuit, ASIC), programmable logic controllers, and embedded microcontrollers, examples of which include, but are not limited to, the following microcontrollers: ARC 625D, atmel AT91SAM, microchip PIC18F26K20, and Silicone Labs C8051F320, the memory controller may also be implemented as part of the control logic of the memory. Those skilled in the art will also appreciate that, in addition to implementing the controller in a pure computer readable program code, it is well possible to implement the same functionality by logically programming the method steps such that the controller is in the form of logic gates, switches, application specific integrated circuits, programmable logic controllers, embedded microcontrollers, etc. Such a controller may thus be regarded as a kind of hardware component, and means for performing various functions included therein may also be regarded as structures within the hardware component. Or even means for achieving the various functions may be regarded as either software modules implementing the methods or structures within hardware components.

The system, apparatus, module or unit set forth in the above embodiments may be implemented in particular by a computer chip or entity, or by a product having a certain function. One typical implementation is a computer. In particular, the computer may be, for example, a personal computer, a laptop computer, a cellular telephone, a camera phone, a smart phone, a personal digital assistant, a media player, a navigation device, an email device, a game console, a tablet computer, a wearable device, or a combination of any of these devices.

For convenience of description, the above devices are described as being functionally divided into various units, respectively. Of course, the functions of each unit may be implemented in the same piece or pieces of software and/or hardware when implementing the embodiments of the present application.

It will be appreciated by those skilled in the art that embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present embodiments may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, embodiments of the present application may take the form of a computer program product on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) having computer-usable program code embodied therein.

The present description is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the application. It will be understood that each flow and/or block of the flowchart illustrations and/or block diagrams, and combinations of flows and/or blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

In one typical configuration, a computing device includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.

The memory may include volatile memory, random Access Memory (RAM), and/or nonvolatile memory, such as Read Only Memory (ROM) or Flash memory (Flash RAM), among others, in a computer readable medium. Memory is an example of computer-readable media.

Computer readable media, including both non-transitory and non-transitory, removable and non-removable media, may implement information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, or other data. Examples of storage media for a computer include, but are not limited to, phase change memory (PRAM), static Random Access Memory (SRAM), dynamic Random Access Memory (DRAM), other types of Random Access Memory (RAM), read Only Memory (ROM), electrically Erasable Programmable Read Only Memory (EEPROM), flash memory or other memory technology, compact disc read only memory (CD-ROM), digital Versatile Disks (DVD) or other optical storage, magnetic cassettes, magnetic tape disk storage or other magnetic storage devices, or any other non-transmission medium, which can be used to store information that can be accessed by a computing device. Computer-readable Media, as defined herein, does not include Transitory computer-readable Media (transmission Media), such as modulated data signals and carrier waves.

It should also be noted that the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one … …" does not exclude the presence of other like elements in a process, method, article or apparatus that comprises the element.

In the embodiments of the present application, "at least one" means one or more, and "a plurality" means two or more. "and/or", describes an association relation of association objects, and indicates that there may be three kinds of relations, for example, a and/or B, and may indicate that a alone exists, a and B together, and B alone exists. Wherein A, B may be singular or plural. The character "/" generally indicates that the context-dependent object is an "or" relationship. "at least one of the following" and the like means any combination of these items, including any combination of single or plural items. For example, at least one of a, b and c may represent: a, b, c, a and b, a and c, b and c or a and b and c, wherein a, b and c can be single or multiple.

Embodiments of the application may be described in the general context of computer-executable instructions, such as program modules, being executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types. Embodiments of the application may also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules may be located in both local and remote computer storage media including memory storage devices.

All embodiments in the application are described in a progressive manner, and identical and similar parts of all embodiments are mutually referred, so that each embodiment mainly describes differences from other embodiments. In particular, for system embodiments, since they are substantially similar to method embodiments, the description is relatively simple, as relevant to see a section of the description of method embodiments.

The foregoing is merely exemplary and is not intended to limit the present application. Various modifications and changes may be made to the present application by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc. which are within the spirit and principles of the present application are intended to be included within the scope of the claims of the present application.

Claims

1. A component management method, comprising:

acquiring a system configuration file;

2. The component management method of claim 1, wherein the determining a plurality of dependency profiles from the system configuration file comprises:

and screening a plurality of dependency description files from a plurality of class description files according to the file configuration information.

3. The component management method according to claim 1, wherein, in a case where the element of the component resource package satisfies the resource merge policy, performing the merge processing on the corresponding component resource package includes:

4. The method for managing components according to claim 1, wherein, in the case where the elements of the component resource packages do not meet the resource merge policy, feeding back the resource package label of the corresponding component resource package to a preset monitoring server, includes:

5. A method for managing components according to claim 3, wherein after said combining the component resource packages in the client to obtain a combined resource package, the method further comprises:

acquiring resource package request information;

6. The component management method according to claim 1, wherein, when the element of the component resource package does not meet the resource merge policy, the method further includes, after feeding back a resource package label of the corresponding component resource package to a preset monitoring server:

A target database address is obtained, and the component resource compression package is forwarded to a target database according to the target database address.

7. The component management method according to claim 1, wherein the performing a first traversal process on the plurality of dependency description files to obtain a plurality of configuration parameter information includes:

searching a plurality of dependent description files based on the mark type information to obtain a plurality of file parameter information;

and carrying out configuration information screening processing on the plurality of file parameter information to obtain a plurality of configuration parameter information.

8. A component management apparatus, comprising:

the first processing module is used for acquiring a system configuration file;

9. An electronic device, comprising: memory, a processor and a computer program stored on the memory and executable on the processor, characterized in that the processor implements the component management method according to any one of claims 1 to 7 when executing the computer program.

10. A computer-readable storage medium storing computer-executable instructions for performing the component management method according to any one of claims 1 to 7.