Privatization deployment method and device, equipment and storage medium

Abstract

The embodiment of the application provides a private deployment method, device, equipment and storage medium, which can be applied to a local server. The local server obtains data packets corresponding to different service services developed by the private deployment architecture from a remote server and stores the data packets in the local server. According to different customization requirement information, the package name information of different data packets and the file name information corresponding to the adapter layer are referenced in the configuration file, the aggregation of different service services is realized, the private deployment is realized, and the server does not need to be re-deployed for each data packet, so that the difficulty of private deployment is effectively reduced. Moreover, the configuration file can be changed according to the customization requirement, so that personalized customization is realized, and the use requirement of a user is met.

Description

Technical Field

[0001] This application relates to the field of computer technology, and in particular to a private deployment method, apparatus, device and storage medium. Background Technology

[0002] SaaS (Software-as-a-Service) systems are typically deployed on cloud servers. However, for information security reasons or when users need to customize content, they usually deploy the system on a private server, i.e., perform private deployment.

[0003] However, due to the sheer size of SaaS systems, which often comprise multiple subsystems (i.e., business services) developed by different developers or vendors, deploying these subsystems with varying development standards to private servers during private deployment is a massive undertaking. Existing private deployment solutions typically involve manually migrating each subsystem to a private server, resulting in high labor costs and a large number of private servers required by the user. Furthermore, the differing standards of the subsystems make it difficult to achieve personalized customization during private deployment, thus failing to meet user needs. Summary of the Invention

[0004] This application provides a private deployment method, apparatus, device, and storage medium, which solves the problem of difficulty in achieving personalized customization during the private deployment process, facilitates rapid private deployment, and meets users' customization needs.

[0005] In a first aspect, embodiments of this application provide a private deployment method applied to a local server. The local server is used to transmit data with a remote server. The remote server stores data packets developed based on the private deployment architecture. The data packets correspond to business services. The private deployment architecture includes an adapter layer, an application layer, a domain layer, and a basic implementation layer. The adapter layer is used to provide business service interfaces and receive business service requests. The business service interfaces include at least one of client interfaces, hardware interfaces, and open interfaces. The application layer is used to process business service requests. The domain layer is used to encapsulate business implementation logic and execute the corresponding business implementation logic according to the business request. The basic implementation layer is used to configure business services in response to the processing of business service requests, or to call database interfaces or other business services in response to the execution of business implementation logic.

[0006] Private deployment methods include:

[0007] Based on the preset customized requirements information, determine the required business services and obtain the data packets corresponding to the business services from the remote server;

[0008] Obtain the packet name information corresponding to the data packet, which corresponds to the storage path of the data packet on the local server;

[0009] Based on the storage path, obtain the filename information corresponding to the adapter layer in the data packet;

[0010] Based on the customized requirements, add package name and file name information to the generated configuration file to reference and aggregate business services corresponding to the customized requirements.

[0011] Secondly, embodiments of this application also provide a private deployment apparatus, applied in a local server, the local server being used for data transmission with a remote server, the remote server storing data packets developed using the private deployment architecture provided in the above embodiments, the apparatus comprising:

[0012] The data packet acquisition module is configured to determine the required business service based on preset customized requirement information, and obtain the data packet corresponding to the business service from the remote server;

[0013] The first information acquisition module is configured to acquire the packet name information corresponding to the data packet, and the packet name information corresponds to the storage path of the data packet on the local server;

[0014] The second information acquisition module is configured to acquire the file name information corresponding to the adapter layer in the data packet based on the storage path;

[0015] The aggregation service module is configured to add package name and file name information to the generated configuration file based on customized requirements, so as to reference and aggregate business services corresponding to the customized requirements based on the configuration file.

[0016] Thirdly, embodiments of this application also provide a private deployment device, including:

[0017] One or more processors;

[0018] Memory, used to store one or more programs;

[0019] When one or more programs are executed by one or more processors, the one or more processors implement the private deployment method as described in the above embodiments.

[0020] Fourthly, embodiments of this application also provide a storage medium storing computationally executable instructions, which, when executed by a processor, are used to perform the privatization deployment method as described in the above embodiments.

[0021] This embodiment of the application obtains data packets corresponding to different business services developed using the aforementioned private deployment architecture from a remote server and stores them on a local server. Based on different customization requirements, the configuration file references the packet name information of different data packets and the file name information corresponding to the adapter layer, thereby aggregating different business services and achieving private deployment. This eliminates the need for redeployment on the server for each data packet, effectively reducing the difficulty of private deployment. Furthermore, the configuration file can be modified according to customization needs to achieve personalized customization and meet user requirements. Attached Figure Description

[0022] Figure 1 A schematic diagram of the private deployment architecture provided in the embodiments of this application;

[0023] Figure 2 A flowchart illustrating the private deployment method provided in this application embodiment;

[0024] Figure 3 A schematic diagram illustrating the addition of relevant information to the configuration file provided in this application embodiment;

[0025] Figure 4 A flowchart illustrating a private deployment method provided in another embodiment of this application;

[0026] Figure 5 A flowchart illustrating a private deployment method provided in yet another embodiment of this application;

[0027] Figure 6 This is a schematic diagram of the structure of the privatization deployment device provided in the embodiments of this application;

[0028] Figure 7 This is a schematic diagram of the structure of a private deployment device provided in an embodiment of this application. Detailed Implementation

[0029] The present application will now be described in further detail with reference to the accompanying drawings and embodiments. It should be understood that the embodiments described herein are for illustrative purposes only and not for limiting the scope of the application. Furthermore, it should be noted that, for ease of description, only the parts relevant to the present application are shown in the accompanying drawings, not the entire structure.

[0030] It should be noted that in this document, relational terms such as first and second are used only to distinguish one entity, operation, or object from another entity, operation, or object, and do not necessarily require or imply any such actual relationship or order between these entities, operations, or objects.

[0031] The private deployment method provided in this application is executed by a server. In application scenarios involving private deployment, it is typically necessary to deploy the business services included in the SaaS system on a private server, such as cloud screen services and information dissemination services. Below, a local server is used as the private server, while a remote server serves as the server providing the business services of the SaaS system. Data can be transferred between the local server and the remote server.

[0032] The remote server's storage contains data packages corresponding to business services, developed based on a private deployment architecture. These data packages are application packages developed by developers according to the private deployment architecture to implement the business service functions. Data packages corresponding to different business services are uploaded to the remote server as part of the SaaS system, thereby providing users with a variety of business service options.

[0033] Figure 1 A schematic diagram of the private deployment architecture provided in the embodiments of this application, as shown below. Figure 1 As shown, taking the data package corresponding to the meeting service as an example, this data package, developed based on a private deployment architecture, includes an adapter layer (meet-adapter.jar), an application layer (meet-app.jar), a domain layer (meet-domain.jar), and an infrastructure layer (meet-infrastructure.jar). Among them, meet-adapter.jar, meet-app.jar, meet-domain.jar, and meet-infrastructure.jar are the JAR files (a type of computer file) in the data package corresponding to each layer in the architecture.

[0034] The adapter layer provides business service interfaces and receives business service requests. These interfaces include at least one of client interfaces, hardware interfaces, and open interfaces. For example, the adapter layer provides an HTTP interface (a type of client interface). The server can receive business requests sent by clients through the HTTP interface. In a conference service, for instance, if a client initiates a request to retrieve the number of attendees, the server can receive this request through the HTTP interface, process the request, and then return the result to the client.

[0035] The application layer handles business service requests and assembles the components in the domain layer to complete specific business services. The domain layer encapsulates the business implementation logic, which includes components or entities that implement business operations within the business service. For example, in the address book service, business operations might include components or entities in the domain layer that implement operations such as saving and modifying contact information, thereby responding to business requests and executing the corresponding business implementation logic.

[0036] The implementation layer forms the foundation for all other layers. It handles business service requests and configures them. For example, in response to a request to save contact information, it saves the contact information to the database. The implementation layer also handles the execution of business logic by calling database interfaces for data transmission. For instance, when modifying contact information, it calls the database interface to retrieve the information. Furthermore, it handles the execution of other business logic by calling other services. For example, when providing meeting services, if a client needs to add participants, it can call the address book service to retrieve contact information and invite other clients to the meeting.

[0037] Figure 2 A flowchart of the private deployment method provided in the embodiments of this application is shown below. Figure 2 As shown, the method includes the following steps:

[0038] Step S110: Based on the preset customized requirements information, determine the required business services and obtain the data packets corresponding to the business services from the remote server.

[0039] Customized requirements information refers to the information of business services that need to be deployed on the local server based on personalized customization requirements. The local server determines the required business services based on the customized requirements information, and then sends a request to the remote server to obtain the corresponding data packets from the remote server.

[0040] For example, a local server can initiate a request to obtain data packets. After receiving the request, the local server establishes a connection with the remote server to transmit data, thereby enabling the local server to obtain the corresponding data packets.

[0041] After obtaining the corresponding data packet on the local server, the local server stores the data packet in the corresponding storage on the local server. For example, a new folder can be created in the storage to store the data packet, and the folder name corresponds to the packet name. For example, after obtaining the data packet corresponding to the conference service, the local server can store the data packet corresponding to the conference service in a folder named com.maxhub.platform.

[0042] Step S120: Obtain the packet name information corresponding to the data packet. The packet name information corresponds to the storage path of the data packet on the local server.

[0043] After obtaining the data packet, the corresponding packet name information is also obtained. This packet name information includes the packet name of the data packet. It can be inferred that the packet name information corresponds to the storage path of the data packet on the local server. The local server can determine the storage path of the data packet based on the packet name information, and call the data packet based on the storage path to provide the relevant functions of the corresponding business service. For example, the local server calls the data packet corresponding to the address book service to provide the client with functions such as modifying contact information.

[0044] Step S130: Obtain the filename information corresponding to the adapter layer in the data packet according to the storage path.

[0045] Taking the data packet corresponding to the meeting service as an example, this data packet includes an adapter layer (meet-adapter.jar), an application layer (meet-app.jar), a domain layer (meet-domain.jar), and an infrastructure layer (meet-infrastructure.jar). In the location where the data packet is stored, the local server retrieves the filename information of the adapter layer, such as "meet-adapter." That is, this filename information corresponds to the filename of the adapter layer's JAR file. The local server calls the corresponding business service based on the JAR file referenced in the configuration file. It should be noted that the files in the data packet corresponding to the adapter layer, application layer, etc., can also be WAR files.

[0046] Step S140: Based on the customized requirements, add package name information and file name information to the generated configuration file.

[0047] The customized requirements information specifies the business services that need to be deployed on the local server, such as conferencing services. Therefore, as... Figure 3As shown, the configuration file contains some information. The configuration file generated by the local server includes corresponding package name information (such as com.maxhub.platform) and file name information (such as meet-adapter). This allows the local server to reference and aggregate business services corresponding to customized requirements based on the configuration file. It is conceivable that by adding or deleting package name information and corresponding adapter layer file name information in the configuration file, the personalized customization of the business services provided by the local server can be achieved.

[0048] As can be seen from the above solution, for data packets developed with a private deployment architecture, the local server can add the corresponding packet name and file name information to the configuration file, thereby aggregating multiple business services. Moreover, it can arbitrarily combine or split business services to form aggregators of business services. This not only enables the rapid combination of business services on demand to complete private deployment, but also meets users' personalized customization needs for private deployment, thereby improving the user experience.

[0049] Figure 4 A flowchart of a private deployment method provided in another embodiment of this application is shown. In one embodiment, when the number of business services to be deployed on the local server increases, the private deployment method further includes:

[0050] Step S210: When a business service corresponding to the customized requirement information is added, an update data packet is obtained from the remote server according to the changed customized requirement information, and the update data packet is stored.

[0051] Step S220: Add the corresponding package name and file name information to the configuration file.

[0052] Understandably, when additional business services are needed on the local server, the local server can determine an update data package based on the changed customization requirements. This update data package corresponds to the new business service that needs to be added to the local server. Therefore, the local server retrieves the corresponding update data package from the remote server and stores it in its local storage. Furthermore, the local server adds the package name and file name information of this update data package to its configuration file to aggregate the added business service into existing business services, facilitating local server invocation and better enabling private deployment.

[0053] Figure 5 A flowchart of a private deployment method provided in another embodiment of this application is provided. In one embodiment, when the number of business services required to be deployed on the local server is reduced, the private deployment method further includes:

[0054] Step S310: When the number of business services corresponding to the customized demand information decreases, determine the deletion data packet corresponding to the business service to be deleted based on the changed customized demand information.

[0055] Step S320: Delete the packet name information and file name information corresponding to the deleted data packet in the configuration file.

[0056] Similarly, when the number of business services provided by the local server needs to be reduced, the local server can determine which data packets to delete based on the changed customization requirements. These deleted data packets correspond to the business services that need to be removed from the local server's configuration file. Therefore, the local server deletes the packet name and file name information corresponding to this deleted data packet from its configuration file. This removes the business services that need to be deleted from the aggregated business services, preventing the local server from calling the services to be deleted based on the configuration file, thus facilitating the management of the aggregated business services. It should be considered that the user could choose whether to delete the corresponding data packets.

[0057] In one embodiment, if the configuration file does not include a business service called by the local server, the local server makes a remote call. That is, if the local server does not reference the corresponding business service in the configuration file, then the business service is determined to be a remote business service.

[0058] For remote business services, the local server needs to determine the remote server that can provide the service and then invoke the service from that remote server. For example, to determine the remote server corresponding to a remote business service, the local server can use ZooKeeper to locate the corresponding remote server.

[0059] ZooKeeper is a distributed application coordination service used for cluster management. When a server needs to access a business service, ZooKeeper can provide service discovery, that is, determine the server node that can provide the business service.

[0060] Therefore, when the local server determines that the business service being called is a remote business service, the local server can use ZooKeeper to identify the remote server providing the remote business service, and then call the business service from the remote server over the network.

[0061] It should be noted that after identifying the remote server that can provide the remote service, the local server can also send a request to obtain the corresponding service data packet. After obtaining the corresponding data packet, the service can be added to the configuration file to enable the invocation of the service.

[0062] In one embodiment, when a configuration file contains a business service that the local server needs to call, the local server makes the call locally. That is, the local server references and aggregates the corresponding business service in the configuration file. Therefore, when the local server needs to call the business service, in response to the call instruction for the business service, the local server determines the storage path of the data packet corresponding to the business service in the local server's memory, and calls the business service from that storage path.

[0063] For example, the conferencing service is added to the configuration file. When the local server needs to call the conferencing service, it can obtain the package name information of the conferencing service from the configuration file. This allows it to determine that the data packet corresponding to the conferencing service is stored in a folder named com.maxhub.platform, and thus determine the storage path of the corresponding data packet. This enables the local server to call the conferencing service according to the corresponding storage path, thereby realizing the local server's local call to the business services provided locally.

[0064] Figure 6 This is a schematic diagram of the structure of a privatization deployment apparatus provided in an embodiment of this application. The apparatus is used to execute the privatization deployment method provided in the above embodiment and has corresponding functional modules and beneficial effects for executing the method. As shown in the figure, the apparatus includes:

[0065] The data packet acquisition module 201 is configured to determine the required business service based on preset customized requirement information, and obtain the data packet corresponding to the business service from the remote server;

[0066] The first information acquisition module 202 is configured to acquire the packet name information corresponding to the data packet, and the packet name information corresponds to the storage path of the data packet on the local server;

[0067] The second information acquisition module 203 is configured to acquire filename information corresponding to the adapter layer in the data packet according to the storage path;

[0068] The aggregation service module 204 is configured to add package name and file name information to the generated configuration file based on customized requirements information, so as to reference and aggregate business services corresponding to the customized requirements information according to the configuration file.

[0069] Based on the above embodiments, the aggregation service module 204 is further configured as follows:

[0070] When a business service corresponding to the customized requirement information is added, an updated data packet is obtained from the remote server based on the changed customized requirement information, and the updated data packet is stored.

[0071] Add the corresponding package name and file name information to the configuration file.

[0072] Based on the above embodiments, the aggregation service module 204 is further configured as follows:

[0073] When the number of business services corresponding to the customized requirements information decreases, the deletion data package corresponding to the business services that need to be deleted is determined based on the changed customized requirements information.

[0074] Remove the packet name and file name information corresponding to the deleted data packet from the configuration file.

[0075] Based on the above embodiments, a service invocation module is also included, which is configured as follows:

[0076] If the configuration file does not contain the first business service called by the local server, the first business service is determined to be a remote business service.

[0077] Identify the remote server corresponding to the remote business service, and call the remote business service from the remote server.

[0078] Based on the above embodiments, the service invocation module is further configured as follows:

[0079] The system uses ZooKeeper to locate the remote server corresponding to the remote business service and then calls the remote business service from the remote server over the network.

[0080] Based on the above embodiments, the service invocation module is further configured as follows:

[0081] When the configuration file contains the first business service called by the local server, in response to the call instruction for the first business service, the storage path of the data packet corresponding to the first business service on the local server is determined.

[0082] Based on the storage path, invoke the first business service.

[0083] Based on the above embodiments, the filename information includes the filename of the JAR file corresponding to the adapter layer in the data packet, so that the local server can call the corresponding business service according to the JAR file referenced in the configuration file.

[0084] It is worth noting that in the above-described embodiments of the privatization deployment device, the various units included are only divided according to functional logic, but are not limited to the above division, as long as the corresponding functions can be achieved; in addition, the specific names of each functional unit are only for easy differentiation and are not used to limit the scope of protection of this application.

[0085] Figure 7This is a schematic diagram of the structure of a privatization deployment device provided in an embodiment of this application. This device can be used to execute the privatization deployment method provided in the above embodiments, possessing corresponding functional modules and beneficial effects. As shown in the figure, the device includes a processor 301, a memory 302, an input device 303, and an output device 304. The number of processors 301 in the device can be one or more; the figure shows one processor 301 as an example. The processor 301, memory 302, input device 303, and output device 304 in the device can be connected via a bus or other means; the figure shows a connection via a bus as an example. The memory 302, as a computer-readable storage medium, can be used to store software programs, computer-executable programs, and modules, such as the program instructions / modules corresponding to the privatization deployment method in the embodiments of this application. The processor 301 executes various functional applications and data processing of the device by running the software programs, instructions, and modules stored in the memory 302, thereby realizing the above-mentioned privatization deployment method.

[0086] The memory 302 may primarily include a program storage area and a data storage area. The program storage area may store the operating system and applications required for at least one function; the data storage area may store data created based on the use of the terminal device. Furthermore, the memory 302 may include high-speed random access memory and non-volatile memory, such as at least one disk storage device, flash memory device, or other non-volatile solid-state storage device. In some instances, the memory 302 may further include memory remotely located relative to the processor 310, which can be connected to the terminal device via a network. Examples of such networks include, but are not limited to, the Internet, corporate intranets, local area networks, mobile communication networks, and combinations thereof.

[0087] Input device 303 can be used to receive input numeric or character information, such as routing messages. Output device 304 can be used to send information for interaction with the server.

[0088] This application also provides a computer program product, which includes a computer program that, when executed by a processor, is used to implement the relevant operations in the private deployment method provided in any embodiment of this application, and has corresponding functions and beneficial effects.

[0089] Those skilled in the art will understand that embodiments of this application may be provided as methods, systems, or computer program products.

[0090] Therefore, this application may take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this application may take the form of a computer program product embodied on one or more computer-readable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code. This application is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of this application. It should be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can 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, produce an implementation for the process... Figure 1 One or more processes and / or boxes Figure 1 The computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to operate in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The functions specified in one or more boxes. 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, thereby providing instructions that execute on the computer or other programmable apparatus for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0091] In a typical configuration, a computing device includes one or more processors (CPUs), input / output interfaces, a network interface, and memory. Memory may include non-persistent memory in computer-readable storage media, such as random access memory (RAM) and / or non-volatile memory, such as read-only memory (ROM) or flash RAM. Memory is an example of a computer-readable storage medium.

[0092] Computer-readable storage media include both permanent and non-permanent, removable and non-removable media, which can store information by any method or technology. Information can be computer-executable instructions, data structures, program modules, or other data. Examples of computer storage media 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 technologies, CD-ROM, digital versatile optical disc (DVD) or other optical storage, magnetic tape, magnetic magnetic disk storage or other magnetic storage devices, or any other non-transfer medium that can be used to store information accessible by a computing device.

[0093] It should also be noted that the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such process, method, article, or apparatus. Unless otherwise specified, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element.

[0094] Note that the above are merely preferred embodiments and the technical principles employed in this application. Those skilled in the art will understand that this application is not limited to the specific embodiments described herein, and various obvious changes, readjustments, and substitutions can be made without departing from the scope of protection of this application. Therefore, although this application has been described in detail through the above embodiments, this application is not limited to the above embodiments, and may include many other equivalent embodiments without departing from the concept of this application, the scope of which is determined by the scope of the appended claims.

Claims

1. A private deployment method, applied to a local server, wherein the local server transmits data with a remote server, characterized in that, The remote server stores data packets corresponding to business services developed based on a private deployment architecture. The private deployment architecture includes an adapter layer, an application layer, a domain layer, and an infrastructure layer. The adapter layer provides business service interfaces and receives business service requests. The business service interfaces include at least one of client interfaces, hardware interfaces, and open interfaces. The application layer processes the business service requests. The domain layer encapsulates business implementation logic and executes the corresponding business implementation logic according to the business request. The basic implementation layer is used to configure business services in response to the processing of the business service request, or to call database interfaces or other business services in response to the execution of the business implementation logic. The private deployment method includes: Based on the preset customized requirements information, determine the required business services, and obtain the data packets corresponding to the business services from the remote server; Obtain the packet name information corresponding to the data packet, wherein the packet name information corresponds to the storage path of the data packet on the local server; Based on the storage path, obtain the filename information corresponding to the adapter layer in the data packet; Based on the customized requirements information, add the package name information and the file name information to the generated configuration file, so as to reference and aggregate the business services corresponding to the customized requirements information according to the configuration file; When the business service corresponding to the customized requirement information is added, an update data packet is obtained from the remote server according to the changed customized requirement information, and the update data packet is stored. Add the package name information and file name information corresponding to the update data package to the configuration file; When the number of business services corresponding to the customized requirement information decreases, the deletion data packet corresponding to the business service that needs to be deleted is determined based on the changed customized requirement information; Delete the packet name information and file name information corresponding to the deleted data packet from the configuration file.

2. The privatization deployment method according to claim 1, characterized in that, Also includes: When the configuration file does not contain the first business service called by the local server, the first business service is determined to be a remote business service. Determine the remote server corresponding to the remote service, and invoke the remote service from the remote server.

3. The privatization deployment method according to claim 2, characterized in that, The step of determining the remote server corresponding to the remote service and invoking the remote service from the remote server includes: The remote server corresponding to the remote business service is located using ZooKeeper, and the remote business service is invoked from the remote server via the network.

4. The privatization deployment method according to claim 1, characterized in that, Also includes: When the configuration file contains a first business service called by the local server, in response to the call instruction for the first business service, the storage path of the data packet corresponding to the first business service in the local server is determined. Based on the storage path, the first business service is invoked.

5. The privatization deployment method according to claim 1, characterized in that, The filename information includes the filename of the JAR file corresponding to the adapter layer in the data packet, so that the local server can call the corresponding business service based on the JAR file referenced in the configuration file.

6. A private deployment device, applied in a local server, wherein the local server transmits data with a remote server, characterized in that, The remote server stores data packets corresponding to business services developed based on a private deployment architecture. The private deployment architecture includes an adapter layer, an application layer, a domain layer, and an infrastructure layer. The adapter layer provides business service interfaces and receives business service requests. The business service interfaces include at least one of client interfaces, hardware interfaces, and open interfaces. The application layer processes the business service requests. The domain layer encapsulates business implementation logic and executes the corresponding business implementation logic according to the business request. The basic implementation layer is used to configure business services in response to the processing of the business service request, or to call database interfaces or other business services in response to the execution of the business implementation logic. The privatization deployment device includes: The data packet acquisition module is configured to determine the required business service based on preset customized requirement information, and acquire the data packet corresponding to the business service from the remote server; The first information acquisition module is configured to acquire the packet name information corresponding to the data packet, wherein the packet name information corresponds to the storage path of the data packet on the local server; The second information acquisition module is configured to acquire the file name information corresponding to the adapter layer in the data packet according to the storage path; The aggregation service module is configured to add the package name information and the file name information to the generated configuration file according to the customized requirement information, so as to reference and aggregate the business services corresponding to the customized requirement information according to the configuration file; The aggregation service module is also configured as follows: When the business service corresponding to the customized requirement information is added, an update data packet is obtained from the remote server according to the changed customized requirement information, and the update data packet is stored. Add the package name information and file name information corresponding to the update data package to the configuration file; When the number of business services corresponding to the customized requirement information decreases, the deletion data packet corresponding to the business service that needs to be deleted is determined based on the changed customized requirement information; Delete the packet name information and file name information corresponding to the deleted data packet from the configuration file.

7. A private deployment device, characterized in that, include: One or more processors; Memory, used to store one or more programs; When one or more of the programs are executed by one or more of the processors, the one or more of the processors implement the privatization deployment method as described in any one of claims 1-5.

8. A storage medium storing computer-executable instructions, characterized in that, The computer-executable instructions, when executed by a processor, are used to perform the privatization deployment method as described in any one of claims 1-5.

Images