CN117270880A - Plug-in service privatization deployment method, device, computer equipment and storage medium - Google Patents
Plug-in service privatization deployment method, device, computer equipment and storage medium Download PDFInfo
- Publication number
- CN117270880A CN117270880A CN202311085310.3A CN202311085310A CN117270880A CN 117270880 A CN117270880 A CN 117270880A CN 202311085310 A CN202311085310 A CN 202311085310A CN 117270880 A CN117270880 A CN 117270880A
- Authority
- CN
- China
- Prior art keywords
- plug
- service
- determining
- newly added
- attribute object
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 47
- 238000004590 computer program Methods 0.000 claims description 15
- 230000006870 function Effects 0.000 description 14
- 235000010627 Phaseolus vulgaris Nutrition 0.000 description 6
- 244000046052 Phaseolus vulgaris Species 0.000 description 6
- 238000010586 diagram Methods 0.000 description 6
- 238000007726 management method Methods 0.000 description 5
- 238000004891 communication Methods 0.000 description 4
- 238000011161 development Methods 0.000 description 4
- 230000008569 process Effects 0.000 description 4
- 238000004458 analytical method Methods 0.000 description 3
- 238000012360 testing method Methods 0.000 description 3
- 238000012795 verification Methods 0.000 description 3
- 230000008859 change Effects 0.000 description 2
- 238000013500 data storage Methods 0.000 description 2
- 238000005516 engineering process Methods 0.000 description 2
- 230000003993 interaction Effects 0.000 description 2
- 238000012545 processing Methods 0.000 description 2
- 230000003068 static effect Effects 0.000 description 2
- OKTJSMMVPCPJKN-UHFFFAOYSA-N Carbon Chemical compound [C] OKTJSMMVPCPJKN-UHFFFAOYSA-N 0.000 description 1
- 230000001413 cellular effect Effects 0.000 description 1
- 230000000295 complement effect Effects 0.000 description 1
- 238000004883 computer application Methods 0.000 description 1
- 229910021389 graphene Inorganic materials 0.000 description 1
- 238000009434 installation Methods 0.000 description 1
- 239000004973 liquid crystal related substance Substances 0.000 description 1
- 238000012423 maintenance Methods 0.000 description 1
- 238000013507 mapping Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000008447 perception Effects 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/65—Updates
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/70—Software maintenance or management
- G06F8/71—Version control; Configuration management
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/445—Program loading or initiating
- G06F9/44521—Dynamic linking or loading; Link editing at or after load time, e.g. Java class loading
- G06F9/44526—Plug-ins; Add-ons
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Computer Security & Cryptography (AREA)
- Stored Programmes (AREA)
Abstract
The application relates to a plug-in service privatization deployment method, a device, computer equipment and a storage medium. The method comprises the following steps: firstly, obtaining a plug-in service requirement of a user, then determining a new plug-in based on the plug-in service requirement, then loading the new plug-in and determining a plug-in attribute object, and finally updating a service deployment version based on the plug-in attribute object. That is, when the software product used by the third party user needs the personalized update function, the corresponding plug-in service of the software product needs to be privately deployed, and the update of the service deployment version is completed by determining the newly added plug-in and the attribute object thereof according to the personalized requirement, instantiating and replacing the container.
Description
Technical Field
The present invention relates to the field of computer application technologies, and in particular, to a method and apparatus for privating and deploying plug-in services, a computer device, and a storage medium.
Background
In this rapidly evolving digital age today, software as a service (Software as a Service, saaS) has become a common choice for businesses and individuals in the field of cloud computing. In the SaaS mode, the software provider is responsible for the installation, configuration, maintenance of the software and security of the data, and the user only needs to access and use the software through a web browser or mobile application.
In government, medical, hotel and other industries, the internal products are not externally open, so that the software used is often required to have strong security and privacy, especially in terms of the product requirements of the security products. In the related art, aiming at different security product capability requirements of different enterprises, functions are usually developed according to the security product capability requirements and placed in a service, service privately deployed is performed on site for users, and when the user update requirements exist, the functions in the service are modified and redeployed. However, the method puts all functions in the same service, so that the service volume is overlarge, not all functions are suitable for all users, and great trouble is caused to subsequent upgrading and version management.
Therefore, there is a need in the related art for a way to improve the efficiency of service privatization deployment and ensure the stability of software service usage.
Disclosure of Invention
In view of the foregoing, it is desirable to provide a plug-in service privating deployment method, device, computer apparatus, and computer readable storage medium that can improve the efficiency of service privating deployment and ensure the stability of software service usage.
In a first aspect, the present application provides a plug-in service privatization deployment method. The method comprises the following steps:
obtaining plug-in service requirements of a user;
determining a newly added plug-in based on the plug-in service requirement;
loading the newly added plugin and determining an plugin attribute object;
and updating the service deployment version based on the plug-in attribute object.
Optionally, in an embodiment of the present application, the determining a new add-on based on the add-on service requirement includes:
determining a plug-in configuration based on the plug-in service requirements;
and determining a newly added plug-in based on the plug-in configuration.
Optionally, in an embodiment of the present application, the updating the service deployment version based on the plug-in attribute object includes:
and loading the plug-in attribute object into a new container corresponding to the new service deployment version, copying the plug-in attribute object in the history container corresponding to the history service deployment version into the new container, and replacing the history container by using the new container.
Optionally, in an embodiment of the present application, loading the plug-in attribute object into a new container corresponding to a new service deployment version includes:
and adding an identification prefix to the plug-in attribute object corresponding to the newly added plug-in, registering the plug-in attribute object into a container corresponding to the service deployment version, and updating the plug-in environment.
Optionally, in an embodiment of the present application, after loading the add-on plug-in and determining a plug-in attribute object, the method further includes:
checking the security of the newly added plug-in, and determining whether the newly added plug-in is tampered;
and checking the starting state of the newly added plug-in, and determining whether the newly added plug-in is not started.
Optionally, in an embodiment of the present application, the method further includes:
creating a new plug-in based on the plug-in service requirement, wherein the plug-in service requirement at least comprises a device type and a device ID;
and generating a security certificate according to the newly added plug-in and uploading the security certificate to the cloud.
Optionally, in an embodiment of the present application, the creating a new add-on based on the add-on service requirement includes:
determining a required common component based on the plug-in service requirements;
and creating the newly added plug-in according to the unified plug-in specification, the plug-in description and the required public components.
In a second aspect, the present application further provides a plug-in service privatized deployment apparatus. The device comprises:
the plug-in service requirement determining module is used for obtaining the plug-in service requirement of the user;
the plug-in service requirement is used for determining a plug-in service requirement;
the plug-in attribute object determining module is used for loading the newly added plug-in and determining a plug-in attribute object;
and the service deployment version updating module is used for updating the service deployment version based on the plug-in attribute object.
In a third aspect, the present application also provides a computer device. The computer device comprises a memory storing a computer program and a processor executing the steps of the method according to the various embodiments described above.
In a fourth aspect, the present application also provides a computer-readable storage medium. The computer readable storage medium has stored thereon a computer program which, when executed by a processor, implements the steps of the method described in the above embodiments.
The plug-in service privatization deployment method, the device, the computer equipment and the storage medium comprise the steps of firstly, obtaining plug-in service requirements of users, then, determining a newly added plug-in based on the plug-in service requirements, then, loading the newly added plug-in and determining a plug-in attribute object, and finally, updating a service deployment version based on the plug-in attribute object. That is, when the software product used by the third party user needs the personalized update function, the corresponding plug-in service of the software product needs to be privately deployed, and the update of the service deployment version is completed by determining the newly added plug-in and the attribute object thereof according to the personalized requirement, instantiating and replacing the container.
Drawings
FIG. 1 is an application environment diagram of a plug-in service privatization deployment method in one embodiment;
FIG. 2 is a flow diagram of a plug-in service privatization deployment method in one embodiment;
FIG. 3 is a schematic diagram of a plug-in server, a plug-in client, and a user's actual interaction process in one embodiment;
FIG. 4 is a block diagram of a plug-in service privatization deployment device in one embodiment;
fig. 5 is an internal structural diagram of a computer device in one embodiment.
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.
The plug-in service privatization deployment method provided by the embodiment of the application can be applied to an application environment shown in fig. 1. Wherein the terminal 102 communicates with the server 104 via a network. The data storage system may store data that the server 104 needs to process. The data storage system may be integrated on the server 104 or may be located on a cloud or other network server. The terminal 102 may be, but not limited to, various personal computers, notebook computers, smart phones, tablet computers, internet of things devices, and portable wearable devices, where the internet of things devices may be smart speakers, smart televisions, smart air conditioners, smart vehicle devices, and the like. The portable wearable device may be a smart watch, smart bracelet, headset, or the like. The server 104 may be implemented as a stand-alone server or as a server cluster of multiple servers.
In one embodiment of the present application, it should be noted that the plug-in service privatization deployment method of the present application is applicable to all plug-in service privatization deployment situations, that is, a new function, an update function configuration, a delete function, and the like of a software service, and correspondingly includes a new plug-in, an update plug-in, a delete plug-in, and the like. The following description will be mainly made with respect to the newly added functions.
In one embodiment, as shown in fig. 2, a plug-in service privatization deployment method is provided, and the method is applied to the server in fig. 1 for illustration, and includes the following steps:
s201: and obtaining the plug-in service requirement of the user.
In the embodiment of the application, first, a plug-in service requirement proposed by a third party user is obtained, where the plug-in service requirement may be a new function added, a function changed, a function deleted, etc. in a software product. And obtaining the plug-in service requirement of the corresponding software update, which is proposed by the user, through a software product update request initiated by the third party user through the terminal.
S203: and determining a new plug-in based on the plug-in service requirement.
In this embodiment of the present application, after obtaining a plug-in service requirement, a plug-in service update requirement, which may be specifically a plug-in service configuration requirement or a plug-in service requirement description, is determined by analyzing the plug-in service requirement, an existing plug-in list is obtained from a plug-in service end according to the plug-in service configuration requirement or the plug-in service requirement description, and a corresponding newly added plug-in is determined in combination with the plug-in service requirement.
S205: and loading the newly added plugin and determining a plugin attribute object.
In the embodiment of the application, after determining the newly added plugin, a corresponding plugin package is loaded from a plugin server, and a plugin attribute object contained in the plugin package is determined. The plug-in attribute objects refer to a plurality of bean objects managed in a Spring IOC container, spring is used as a main Java Web development framework, the framework is a lightweight non-invasive application framework, the complexity of enterprise application development can be solved, the IOC refers to control inversion, and the object creation and the calling process between the objects are managed by the Spring. Typically, the bean object is created by the configuration metadata provided to the container, in this embodiment of the present application, that is, the plug-in attribute object is created by plug-in configuration information, optionally, may include a unique plug-in tag plug-in-id, a plug-in description, a plug-in version, and the like, according to these information, the bean object is correspondingly created, and a bean label is assigned to the bean object, including a unique plug-in tag plug-in-id, a Class attribute Class, and the like, and different plug-in configuration information corresponds to different Class attribute classes.
S207: and updating the service deployment version based on the plug-in attribute object.
In the embodiment of the application, after determining the plug-in attribute object, an empty container corresponding to a new service deployment version is created according to the comparison between the newly added plug-in and the history plug-in, the plug-in attribute object is loaded in the empty container, other history plug-in attribute objects are copied into the empty container, a complete new container is obtained, the history container corresponding to the history service deployment version is replaced, and the update of the service deployment version is completed.
In the above plug-in service privatization deployment method, firstly, the plug-in service requirement of the user is obtained, then, a new plug-in is determined based on the plug-in service requirement, then, the new plug-in is loaded, a plug-in attribute object is determined, and finally, a service deployment version is updated based on the plug-in attribute object. That is, when the software product used by the third party user needs the personalized update function, the corresponding plug-in service of the software product needs to be privately deployed, and the update of the service deployment version is completed by determining the newly added plug-in and the attribute object thereof according to the personalized requirement, instantiating and replacing the container.
In one embodiment of the present application, the determining the new add-on based on the add-on service requirement includes:
s301: and determining a plug-in configuration based on the plug-in service requirements.
S303: and determining a newly added plug-in based on the plug-in configuration.
In one embodiment of the present application, first, after obtaining a plug-in service requirement of a user, determining a plug-in configuration based on the plug-in service requirement, specifically, analyzing the plug-in service requirement, determining a plug-in configuration contained therein, that is, relevant configuration information of the plug-in service requirement, which may include plug-in pin-id, plug-in description, a public component to which a plug-in service version needs to be used, and so on. And then determining a new plug-in based on the plug-in configuration, specifically, matching the appropriate plug-ins in the plug-in server based on the corresponding relevant configuration information obtained by analysis and determination, uniformly returning to a plug-in list, and determining the new plug-in to be updated based on the selection information in the plug-in configuration.
In this embodiment, by determining the plug-in configuration based on the plug-in service requirement and determining the newly added plug-in based on the plug-in configuration, the corresponding newly added plug-in can be accurately obtained based on the plug-in configuration information, and efficiency is improved.
In one embodiment of the present application, the updating the service deployment version based on the plug-in attribute object includes:
and loading the plug-in attribute object into a new container corresponding to the new service deployment version, copying the plug-in attribute object in the history container corresponding to the history service deployment version into the new container, and replacing the history container by using the new container.
In one embodiment of the present application, after determining the plug-in attribute object, comparing the newly added plug-in version with the history plug-in version, creating a new container corresponding to the new service deployment version based on the Spring application framework according to the comparison result, setting the version number to 2, loading the plug-in attribute object corresponding to the newly added plug-in registered in the Spring IOC container into the new container, copying other history plug-in attribute objects in the history container corresponding to the history service deployment version into the new container, obtaining a complete new container, and then replacing the history container with the new container and changing the version number to 1.
In this embodiment, by loading the plug-in attribute object into the new container corresponding to the new service deployment version, copying the plug-in attribute object in the history container corresponding to the history service deployment version into the new container, and replacing the history container with the new container, the service deployment version update can be completed without perception of the user, and the efficiency of service privatization deployment and the experience of the user are improved.
In one embodiment of the present application, the loading the plug-in attribute object into the new container corresponding to the new service deployment version includes:
and adding an identification prefix to the plug-in attribute object corresponding to the newly added plug-in, registering the plug-in attribute object into a container corresponding to the service deployment version, and updating the plug-in environment.
In one embodiment of the application, after determining the plug-in attribute object, a custom class loader is used to add an identification prefix uniform resource identifier (Uniform Resource Identifier, URI) to all plug-in attribute objects corresponding to the plug-in package, and the plug-in attribute object is reversely registered in a Spring IOC container corresponding to the service deployment version, so as to update the context environment of the plug-in, i.e. add an identification prefix to the tag of the plug-in attribute object, and update the request path of the plug-in attribute object into a form of uri+plug-in tag-id+request mapping.
In this embodiment, by adding the identifier prefix to the plug-in attribute object corresponding to the newly added plug-in, registering the plug-in attribute object in the container corresponding to the service deployment version, and updating the plug-in environment, the Spring parent-child container can be facilitated to complement the attribute bean object and instantiate.
In one embodiment of the present application, after loading the new add-on plug-in and determining the plug-in attribute object, the method further includes:
s401: and checking the security of the newly added plug-in, and determining whether the newly added plug-in is tampered.
S403: and checking the starting state of the newly added plug-in, and determining whether the newly added plug-in is not started.
In one embodiment of the present application, the loading of the new add-on plug-in and determining the plug-in attribute object further includes two tests, one is to test the security of the new add-on plug-in, determine whether the new add-on plug-in is tampered with, and the other is to test the start-up state of the new add-on plug-in, and determine whether the new add-on plug-in is not started. Specifically, when a new add-on plug-in is loaded, that is, when a corresponding plug-in package is acquired, a corresponding security certificate is acquired at the same time, a local security certificate is generated based on the obtained plug-in package, whether the plug-in package is tampered or not is determined by comparing whether the plug-in package is identical to the security certificate, only the new add-on plug-in package which is not tampered meets the security requirement, in addition, an HTTP request is initiated, whether the new add-on plug-in package is not started or not is determined based on returned data, when the new add-on plug-in package returns to 404, the new add-on plug-in package is not started, and only the new add-on plug-in package which is not started can be used for updating the service deployment version.
In this embodiment, by checking the security and the start state of the newly added plug-in, it is determined whether the newly added plug-in is tampered and not started, so that the newly added plug-in is not tampered by people and the service deployment version update is smoothly executed.
In one embodiment of the present application, the method further comprises:
s501: and creating a new plug-in based on the plug-in service requirement, wherein the plug-in service requirement at least comprises a device type and a device ID.
S503: and generating a security certificate according to the newly added plug-in and uploading the security certificate to the cloud.
In one embodiment of the application, after obtaining the plug-in service requirement proposed by the third party user, developing a new plug-in based on the plug-in service requirement, and following a unified plug-in package template during development to realize the plug-in service requirement, uploading the developed new plug-in to a plug-in service end, and uniformly managing the plug-in service end. The plug-in service requirement at least comprises a device type and a device ID used by a third party user, wherein the device type and the device ID are recorded in newly-added plug-in attribute information for plug-in management. And generating a dedicated security certificate according to the developed newly-added plug-in and uploading the dedicated security certificate to a cloud plug-in server for security verification of the newly-added plug-in.
In this embodiment, a new add-on plug-in is created based on a plug-in service requirement, where the plug-in service requirement at least includes a device type and a device ID, and a security certificate is generated according to the new add-on plug-in and uploaded to the cloud, so that the new add-on plug-in can be developed based on a unified plug-in package template, and all plug-ins are uniformly managed through a plug-in server, so that functions of uploading, updating, deleting plug-in packages at any time and any place are realized.
In one embodiment of the present application, the creating a new add-on based on the add-on service requirement includes:
s601: the required common components are determined based on the plug-in service requirements.
S603: and creating the newly added plug-in according to the unified plug-in specification, the plug-in description and the required public components.
In one embodiment of the application, after obtaining a plug-in service requirement, a public component required to be used by a plug-in service version is determined based on requirement information, namely plug-in service information, then a new plug-in is developed according to unified plug-in specifications, namely unified plug-in package templates, plug-in descriptions and required public components, a unique plug-in-ID is set for the new plug-in based on equipment type and equipment ID, and after development is completed, the plug-in is uploaded to a plug-in service side and is unified and managed by the plug-in service side.
In the embodiment, the public components are determined based on the plug-in service requirement, and the newly added plug-in is created according to the unified plug-in specification, the plug-in description and the required public components, so that the structure of the plug-in can be unified, and the plug-in service side can conveniently manage all the plug-ins in a unified manner.
In the following, a specific embodiment is used to describe the actual interaction process between the plug-in client and the plug-in server and the user terminal, as shown in fig. 3, first, the user sends a software product update request through the user terminal, S301 is executed, and the plug-in client obtains the plug-in service requirement of the user. After that, S303-S305 are executed, a plug-in configuration is determined based on the plug-in service requirement, and a new plug-in is determined based on the plug-in configuration. Specifically, the plug-in client analyzes the plug-in service requirement, determines the plug-in configuration contained in the plug-in service requirement, sends corresponding relevant configuration information obtained based on analysis determination to the plug-in server, matches the appropriate plug-in the plug-in server by the plug-in server, uniformly returns a plug-in list, and then determines a newly added plug-in to be updated by the plug-in client based on selection information in the plug-in configuration, namely user selection.
And then, executing S307, checking the security of the newly added plug-in, determining whether the newly added plug-in is tampered, specifically, acquiring a security certificate corresponding to the newly added plug-in from a plug-in server, generating a local security certificate based on the newly added plug-in locally by a plug-in client, comparing the two security certificates to determine whether the security certificates are the same, and determining whether a plug-in package is tampered. After that, execution, S309, checks the start-up status of the new add-on, and determines whether the new add-on is not started.
Finally, executing S311, loading the plug-in attribute object into a new container corresponding to the new service deployment version, copying the plug-in attribute object in the history container corresponding to the history service deployment version into the new container, and replacing the history container with the new container.
Meanwhile, the plug-in client also executes S313 and S315, a new plug-in is created based on the plug-in service requirement, the plug-in service requirement at least comprises a device type and a device ID, and a security certificate is generated according to the new plug-in and uploaded to the cloud.
It should be understood that, although the steps in the flowcharts related to the embodiments described above are sequentially shown as indicated by arrows, these steps are not necessarily sequentially performed in the order indicated by the arrows. The steps are not strictly limited to the order of execution unless explicitly recited herein, and the steps may be executed in other orders. Moreover, at least some of the steps in the flowcharts described in the above embodiments may include a plurality of steps or a plurality of stages, which are not necessarily performed at the same time, but may be performed at different times, and the order of the steps or stages is not necessarily performed sequentially, but may be performed alternately or alternately with at least some of the other steps or stages.
Based on the same inventive concept, the embodiment of the application also provides a plug-in service privatization deployment device for realizing the above mentioned plug-in service privatization deployment method. The implementation of the solution provided by the device is similar to the implementation described in the above method, so the specific limitation in the embodiments of the one or more plug-in service privately deployed devices provided below may refer to the limitation of the plug-in service privately deployed method hereinabove, and will not be repeated herein.
In one embodiment, as shown in fig. 4, a plug-in service privatization deployment apparatus 400 is provided, comprising: a plugin service requirement determination module 401, a new plugin determination module 403, a plugin attribute object determination module 405, and a service deployment version update module 407, wherein:
the plug-in service requirement determining module 401 is configured to obtain a plug-in service requirement of a user.
The add-on plug-in determining module 403 is configured to determine an add-on plug-in based on the plug-in service requirement.
And the plug-in attribute object determining module 405 is configured to load the newly added plug-in and determine a plug-in attribute object.
A service deployment version updating module 407, configured to update a service deployment version based on the plug-in attribute object.
In one embodiment of the present application, the add-on plug-in determining module is further configured to:
determining a plug-in configuration based on the plug-in service requirements;
and determining a newly added plug-in based on the plug-in configuration.
In one embodiment of the present application, the service deployment version update module is further configured to:
and loading the plug-in attribute object into a new container corresponding to the new service deployment version, copying the plug-in attribute object in the history container corresponding to the history service deployment version into the new container, and replacing the history container by using the new container.
In one embodiment of the present application, the service deployment version update module is further configured to:
and adding an identification prefix to the plug-in attribute object corresponding to the newly added plug-in, registering the plug-in attribute object into a container corresponding to the service deployment version, and updating the plug-in environment.
The plug-in service privatization deployment device further comprises a plug-in verification module.
In one embodiment of the present application, the plug-in verification module is configured to:
checking the security of the newly added plug-in, and determining whether the newly added plug-in is tampered;
and checking the starting state of the newly added plug-in, and determining whether the newly added plug-in is not started.
The plug-in service privatization deployment device also comprises a plug-in management module.
In one embodiment of the present application, the plug-in management module is configured to:
creating a new plug-in based on the plug-in service requirement, wherein the plug-in service requirement at least comprises a device type and a device ID;
and generating a security certificate according to the newly added plug-in and uploading the security certificate to the cloud.
In one embodiment of the present application, the plug-in management module is further configured to:
determining a required common component based on the plug-in service requirements;
and creating the newly added plug-in according to the unified plug-in specification, the plug-in description and the required public components.
The various modules in the plug-in service privatized deployment device described above may be implemented in whole or in part by software, hardware, and combinations thereof. The above modules may be embedded in hardware or may be independent of a processor in the computer device, or may be stored in software in a memory in the computer device, so that the processor may call and execute operations corresponding to the above modules.
In one embodiment, a computer device is provided, which may be a terminal, and the internal structure of which may be as shown in fig. 5. The computer device includes a processor, a memory, a communication interface, a display screen, and an input device connected by a system bus. Wherein the processor of the computer device is configured to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system and a computer program. The internal memory provides an environment for the operation of the operating system and computer programs in the non-volatile storage media. The communication interface of the computer device is used for carrying out wired or wireless communication with an external terminal, and the wireless mode can be realized through WIFI, a mobile cellular network, NFC (near field communication) or other technologies. The computer program, when executed by a processor, implements a plug-in service privatization deployment method. The display screen of the computer equipment can be a liquid crystal display screen or an electronic ink display screen, and the input device of the computer equipment can be a touch layer covered on the display screen, can also be keys, a track ball or a touch pad arranged on the shell of the computer equipment, and can also be an external keyboard, a touch pad or a mouse and the like.
It will be appreciated by those skilled in the art that the structure shown in fig. 5 is merely a block diagram of some of the structures associated with the present application and is not limiting of the computer device to which the present application may be applied, and that a particular computer device may include more or fewer components than shown, or may combine certain components, or have a different arrangement of components.
In one embodiment, a computer device is provided, comprising a memory and a processor, the memory having stored therein a computer program, the processor implementing the steps of the method embodiments described above when the computer program is executed.
In one embodiment, a computer-readable storage medium is provided, on which a computer program is stored which, when executed by a processor, implements the steps of the method embodiments described above.
In an embodiment, a computer program product is provided, comprising a computer program which, when executed by a processor, implements the steps of the method embodiments described above.
It should be noted that, user information (including but not limited to user equipment information, user personal information, etc.) and data (including but not limited to data for analysis, stored data, presented data, etc.) referred to in the present application are information and data authorized by the user or sufficiently authorized by each party.
Those skilled in the art will appreciate that implementing all or part of the above described methods may be accomplished by way of a computer program stored on a non-transitory computer readable storage medium, which when executed, may comprise the steps of the embodiments of the methods described above. Any reference to memory, database, or other medium used in the various embodiments provided herein may include at least one of non-volatile and volatile memory. The nonvolatile Memory may include Read-Only Memory (ROM), magnetic tape, floppy disk, flash Memory, optical Memory, high density embedded nonvolatile Memory, resistive random access Memory (ReRAM), magnetic random access Memory (Magnetoresistive Random Access Memory, MRAM), ferroelectric Memory (Ferroelectric Random Access Memory, FRAM), phase change Memory (Phase Change Memory, PCM), graphene Memory, and the like. Volatile memory can include random access memory (Random Access Memory, RAM) or external cache memory, and the like. By way of illustration, and not limitation, RAM can be in the form of a variety of forms, such as static random access memory (Static Random Access Memory, SRAM) or dynamic random access memory (Dynamic Random Access Memory, DRAM), and the like. The databases referred to in the various embodiments provided herein may include at least one of relational databases and non-relational databases. The non-relational database may include, but is not limited to, a blockchain-based distributed database, and the like. The processors referred to in the embodiments provided herein may be general purpose processors, central processing units, graphics processors, digital signal processors, programmable logic units, quantum computing-based data processing logic units, etc., without being limited thereto.
The technical features of the above embodiments may be arbitrarily combined, and all possible combinations of the technical features in the above embodiments are not described for brevity of description, however, as long as there is no contradiction between the combinations of the technical features, they should be considered as the scope of the description.
The above examples only represent a few embodiments of the present application, which are described in more detail and are not to be construed as limiting the scope of the present application. It should be noted that it would be apparent to those skilled in the art that various modifications and improvements could be made without departing from the spirit of the present application, which would be within the scope of the present application. Accordingly, the scope of protection of the present application shall be subject to the appended claims.
Claims (10)
1. A method for privatizing and deploying a plug-in service, the method comprising:
obtaining plug-in service requirements of a user;
determining a newly added plug-in based on the plug-in service requirement;
loading the newly added plugin and determining an plugin attribute object;
and updating the service deployment version based on the plug-in attribute object.
2. The method of claim 1, wherein the determining a new add-on based on the add-on service requirements comprises:
determining a plug-in configuration based on the plug-in service requirements;
and determining a newly added plug-in based on the plug-in configuration.
3. The method of claim 1, wherein updating a service deployment version based on the plug-in attribute object comprises:
and loading the plug-in attribute object into a new container corresponding to the new service deployment version, copying the plug-in attribute object in the history container corresponding to the history service deployment version into the new container, and replacing the history container by using the new container.
4. The method of claim 3, wherein loading the plug-in attribute object into a new container corresponding to a new service deployment version comprises:
and adding an identification prefix to the plug-in attribute object corresponding to the newly added plug-in, registering the plug-in attribute object into a container corresponding to the service deployment version, and updating the plug-in environment.
5. The method of claim 1, wherein after loading the add-on plug-in and determining a plug-in attribute object, further comprises:
checking the security of the newly added plug-in, and determining whether the newly added plug-in is tampered;
and checking the starting state of the newly added plug-in, and determining whether the newly added plug-in is not started.
6. The method according to claim 1, wherein the method further comprises:
creating a new plug-in based on the plug-in service requirement, wherein the plug-in service requirement at least comprises a device type and a device ID;
and generating a security certificate according to the newly added plug-in and uploading the security certificate to the cloud.
7. The method of claim 6, wherein creating a new add-on based on the add-on service requirements comprises:
determining a required common component based on the plug-in service requirements;
and creating the newly added plug-in according to the unified plug-in specification, the plug-in description and the required public components.
8. A plug-in service privatization deployment apparatus, the apparatus comprising:
the plug-in service requirement determining module is used for obtaining the plug-in service requirement of the user;
the plug-in service requirement is used for determining a plug-in service requirement;
the plug-in attribute object determining module is used for loading the newly added plug-in and determining a plug-in attribute object;
and the service deployment version updating module is used for updating the service deployment version based on the plug-in attribute object.
9. A computer device comprising a memory and a processor, the memory storing a computer program, characterized in that the processor implements the steps of the method of any of claims 1 to 7 when the computer program is executed.
10. A computer readable storage medium, on which a computer program is stored, characterized in that the computer program, when being executed by a processor, implements the steps of the method of any of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202311085310.3A CN117270880A (en) | 2023-08-25 | 2023-08-25 | Plug-in service privatization deployment method, device, computer equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202311085310.3A CN117270880A (en) | 2023-08-25 | 2023-08-25 | Plug-in service privatization deployment method, device, computer equipment and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN117270880A true CN117270880A (en) | 2023-12-22 |
Family
ID=89215026
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202311085310.3A Pending CN117270880A (en) | 2023-08-25 | 2023-08-25 | Plug-in service privatization deployment method, device, computer equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN117270880A (en) |
-
2023
- 2023-08-25 CN CN202311085310.3A patent/CN117270880A/en active Pending
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US10540173B2 (en) | Version control of applications | |
| US9501762B2 (en) | Application recommendation using automatically synchronized shared folders | |
| US10367824B2 (en) | Policy management, enforcement, and audit for data security | |
| US9703834B2 (en) | Topological query in multi-tenancy environment | |
| US20140129457A1 (en) | An interactive organizational decision-making and compliance facilitation portal | |
| US11733990B2 (en) | Generating software artifacts from a conceptual data model | |
| US11237749B2 (en) | System and method for backup data discrimination | |
| US11171835B2 (en) | Automated generation of an information technology asset ontology | |
| US10719488B2 (en) | Configurable provider for layered repository | |
| CN114218156A (en) | Data export method, data export device, computer equipment and storage medium | |
| CN112434004A (en) | Data migration method and device for heterogeneous system, computer equipment and storage medium | |
| CN116048609A (en) | Configuration file updating method, device, computer equipment and storage medium | |
| CN117270880A (en) | Plug-in service privatization deployment method, device, computer equipment and storage medium | |
| US11222133B1 (en) | User programmatic interface for supporting data access control in a database system | |
| CN114756293A (en) | Service processing method, device, computer equipment and storage medium | |
| CN115118612A (en) | Resource quota management method and device, computer equipment and storage medium | |
| US20170318120A1 (en) | Dynamic document access control in a content management system | |
| CN109977659A (en) | Weblogic automatically creates method, system, device and the storage medium of local user | |
| CN114528045B (en) | Plug-in operation method, device, computer equipment and storage medium | |
| CN115510130A (en) | Report generation method and device, computer equipment and storage medium | |
| CN114237677A (en) | Hot updating method and device for application updating file and computer equipment | |
| CN116909684A (en) | Deployment method and device of low-code application, computer equipment and storage medium | |
| CN117032779A (en) | Application version switching method, device, computer equipment and storage medium | |
| CN115987557A (en) | Inter-cluster calling method and device, computer equipment and storage medium | |
| CN118363567A (en) | Software application modularized application method and device and computer equipment |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |