CN115827094A - SaaS application loading method, device, equipment and storage medium - Google Patents

SaaS application loading method, device, equipment and storage medium Download PDF

Info

Publication number
CN115827094A
CN115827094A CN202211524680.8A CN202211524680A CN115827094A CN 115827094 A CN115827094 A CN 115827094A CN 202211524680 A CN202211524680 A CN 202211524680A CN 115827094 A CN115827094 A CN 115827094A
Authority
CN
China
Prior art keywords
loading
application
template
target
saas application
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
Application number
CN202211524680.8A
Other languages
Chinese (zh)
Inventor
吴骏业
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Shanghai Pudong Development Bank Co Ltd
Original Assignee
Shanghai Pudong Development Bank Co Ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Shanghai Pudong Development Bank Co Ltd filed Critical Shanghai Pudong Development Bank Co Ltd
Priority to CN202211524680.8A priority Critical patent/CN115827094A/en
Publication of CN115827094A publication Critical patent/CN115827094A/en
Pending legal-status Critical Current

Links

Images

Landscapes

  • Stored Programmes (AREA)

Abstract

The invention discloses a SaaS application loading method, a SaaS application loading device, saaS application loading equipment and a SaaS application loading storage medium. The method comprises the following steps: building a loading template matched with each SaaS application according to a loading configuration instruction of an application provider, wherein the loading template comprises a loading flow of the SaaS application; when a subscription instruction of an application user is received, determining a target SaaS application and a target loading template according to the subscription instruction; and loading the target SaaS application according to the target loading template so that the application user uses the loaded target SaaS application. By pre-constructing the loading template matched with each SaaS application, when a subscription instruction of an application user to the target SaaS application is received, the application can be loaded according to the target loading template matched with the target SaaS application without manual loading operation, so that the application loading efficiency is improved.

Description

SaaS application loading method, device, equipment and storage medium
Technical Field
The invention relates to the technical field of data processing, in particular to a SaaS application loading method, device, equipment and storage medium.
Background
The cloud-as-a-Service-SaaS (Software-as-a-Service-SaaS) architecture is a set of architecture principles and design modes based on cloud native technology, and aims to maximally strip off non-Service code parts in SaaS application, so that cloud implementation takes over a large number of original non-functional characteristics in the application, services are not disturbed by non-functional Service interruption, and the cloud-as-a-Service-SaaS architecture has the characteristics of light weight, quickness and high automation.
The cloud native SaaS application generally provides multi-tenant services based on a hybrid multi-tenant mode, and with the development of a cloud native technology, the deployment and tenant loading complexity of the cloud native SaaS service continuously increases, and particularly, when an application provider receives subscription requests of different tenants and the same application is subscribed by the different tenants, the application loading operation needs to be manually and repeatedly performed, so that the application loading efficiency is significantly reduced.
Disclosure of Invention
The invention provides a method, a device, equipment and a storage medium for loading SaaS applications, which are used for loading the SaaS applications.
According to a first aspect of the present invention, there is provided a SaaS application loading method, including: the method comprises the steps that a loading template matched with each SaaS application is built according to a loading configuration instruction of an application provider, wherein the loading template comprises a loading flow of the SaaS application;
when a subscription instruction of an application user is received, determining a target SaaS application and a target loading template according to the subscription instruction;
and loading the target SaaS application according to the target loading template so that the application user uses the loaded target SaaS application.
According to another aspect of the present invention, there is provided a SaaS application loading apparatus including: the system comprises a loading template acquisition module, a loading template acquisition module and a loading module, wherein the loading template acquisition module is used for constructing a loading template matched with each SaaS application according to a loading configuration instruction of an application provider, and the loading template comprises a loading flow of the SaaS application;
the target loading template determining module is used for determining a target SaaS application and a target loading template according to a subscription instruction when the subscription instruction of an application user is received;
and the application loading module is used for loading the target SaaS application according to the target loading template so that the application user can use the loaded target SaaS application.
According to another aspect of the present invention, there is provided an electronic apparatus including:
at least one processor; and
a memory communicatively coupled to the at least one processor; wherein,
the memory stores a computer program executable by the at least one processor, the computer program being executable by the at least one processor to enable the at least one processor to perform the method according to any of the embodiments of the invention.
According to another aspect of the present invention, there is provided a computer-readable storage medium having stored thereon computer instructions for causing a processor to execute a method according to any one of the embodiments of the present invention.
According to the technical scheme of the embodiment of the invention, the loading template matched with each SaaS application is constructed in advance, so that when a subscription instruction of an application user to the target SaaS application is received, the application can be loaded according to the target loading template matched with the target SaaS application without manual loading operation, and the application loading efficiency is improved.
It should be understood that the statements in this section do not necessarily identify key or critical features of the embodiments of the present invention, nor do they necessarily limit the scope of the invention. Other features of the present invention will become apparent from the following description.
Drawings
In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the drawings needed to be used in the description of the embodiments will be briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present invention, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without creative efforts.
Fig. 1 is a flowchart of a SaaS application loading method according to an embodiment of the present invention;
fig. 2 is a flowchart of a SaaS application loading method according to a second embodiment of the present invention;
fig. 3 is a schematic structural diagram of a SaaS application loading apparatus according to a third embodiment of the present invention;
fig. 4 is a schematic structural diagram of an electronic device according to a fourth embodiment of the present invention.
Detailed Description
In order to make the technical solutions of the present invention better understood, the technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
It should be noted that the terms "first," "second," and the like in the description and claims of the present invention and in the drawings described above are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used is interchangeable under appropriate circumstances such that the embodiments of the invention described herein are capable of operation in sequences other than those illustrated or described herein. Furthermore, the terms "comprises," "comprising," and "having," and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed, but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus.
Example one
Fig. 1 is a flowchart of a SaaS application loading method provided in an embodiment of the present invention, where the method is applicable to a case of loading a SaaS application, and the method may be executed by a SaaS application loading apparatus, and the apparatus may be implemented in a form of hardware and/or software. As shown in fig. 1, the method includes:
and step S101, constructing a loading template matched with each SaaS application according to a loading configuration instruction of an application provider.
Optionally, before acquiring a loading template matched with each SaaS application according to a loading configuration instruction of an application provider, the method further includes: receiving a SaaS application deployment instruction of an application provider, wherein the application deployment instruction comprises a deployment template type; calling an original deployment template according to the type of the deployment template; judging whether the deployment instruction contains deployment configuration parameters or not, if so, configuring the original deployment template by adopting the deployment configuration parameters to obtain a deployment template matched with the SaaS application, and otherwise, directly taking the original deployment template as the deployment template matched with the SaaS application; and testing the deployment template in a specified environment, and deploying the matched SaaS application according to the deployment template under the condition of determining that the test is passed.
Optionally, before receiving the SaaS application deployment instruction of the application provider, the method further includes: receiving a login request of an application provider, wherein the login request comprises a user identity; and when the application provider is determined to be a legal user according to the user identity, providing a specified environment for the application provider.
Specifically, the application provider may be an Independent Software developer (ISV), and the ISV has an access right of the system platform after being registered on the system platform. Therefore, in this embodiment, when the system platform receives a login request of an application provider, because the login request includes a user identity, it may be determined whether the provider sending the login request is a registered user according to the user identity, and if the provider is determined to be a registered user, it may be determined that the application provider is a valid user, where the user identity may be a name of the application provider, a code at the time of registration, or a contact manner, and a specific type of the user identity is not limited in this embodiment. And in the case that the user is determined to be a legal user, a specified environment for template testing, such as a sandbox environment or the like, is provided online for the application provider.
In addition, when it is determined that the application provider is a valid user, an instruction receiving interface for the valid user may be opened, that is, the application provider is allowed to deploy the SaaS application on the system platform, and an original deployment template for each SaaS application, for example, an original virtual machine deployment template or an original database deployment template, is configured on the system platform. Therefore, when the SaaS application deployment instruction of the provider is received through the instruction receiving interface, the original deployment template is called according to the deployment template type because the deployment template type is included in the instruction. For example, when an application provider wants to perform application deployment on the virtual machine 1 on the system platform, the system platform may send a SaaS application deployment instruction for the virtual machine 1 through the instruction receiving interface, and the system platform calls an original deployment template corresponding to the virtual machine 1 from a pre-stored original deployment template according to the application deployment instruction. When it is determined that the application deployment instruction further includes configuration parameters for the original deployment template, the original deployment template may be configured individually according to the application deployment instruction, the configuration parameters may specifically be a model of the virtual machine 1, resources occupied by deployment, and the like, the deployment template matched with the virtual machine 1 is obtained according to a result of the individual configuration, and when the application deployment instruction does not include the deployment configuration parameters, the obtained original deployment template is directly used as the deployment template matched with the virtual machine 1. After the deployment template matched with the virtual machine 1 is determined, the deployment template matched with the virtual machine 1 needs to be tested by adopting a specified environment previously allocated to an application provider, so as to test the availability of the deployment template, and a specific manner for testing the availability of the deployment template is not the focus of the present application, and therefore, details are not repeated in the present embodiment.
When it is determined that the deployment template matched with the virtual machine 1 passes the test, the deployment template includes a specific deployment flow of the virtual machine 1, so that the virtual machine 1 can be deployed on the system platform with reference to the specific deployment flow. Of course, in the present embodiment, only the deployment manner when the SaaS application is the virtual machine 1 is described as an example, and the deployment manner of other SaaS applications is substantially the same as that described above, and details thereof are not described again in the present embodiment. And the format of the SaaS application may include: a git code repository format, a mirror image format, a jar package format, or the like, and a specific format of the SaaS application deployed on the system platform is not limited in this embodiment.
Optionally, the building of a loading template matched with each SaaS application according to a loading configuration instruction of an application provider includes: extracting the type of the loading template and the loading configuration parameters contained in the loading configuration instruction; calling an original loading template according to the type of the loading template; and configuring the original loading template according to the loading configuration parameters to construct a loading template matched with the SaaS application.
When the deployment of each SaaS application on the system platform is completed, a loading configuration instruction of an application provider may also be received, and an original configuration template for each application, for example, an original virtual machine loading template or an original database deployment template, is configured on the system platform. Therefore, when a loading configuration instruction of a supplier is received through the instruction receiving interface, because the loading configuration instruction includes the loading template type and the loading configuration parameters, an original loading template can be called according to the loading template type, for example, when the application supplier wants to construct a loading template matched with the virtual machine 1, an original loading template corresponding to the virtual machine 1 can be called from the system platform according to the loading configuration instruction, the original loading template is configured according to the loading configuration parameters, and the loading configuration parameters include personalized parameters such as a loading address, resources occupied by loading and the like, so that a loading template matched with the virtual machine 1 is obtained according to a personalized configuration result, and a loading flow of the virtual machine 1 is included in the loading template. Of course, in the present embodiment, the loading template of the virtual machine 1 is merely obtained by way of example, and the manner of obtaining the loading template of another SaaS application is substantially the same, and the details thereof are not repeated in the present embodiment.
It should be noted that, in this embodiment, after the loading template matched with each SaaS application is obtained, the loading template matched with each SaaS application needs to be tested by using the specified environment previously allocated to the application provider, so as to test the availability of the loading template. And under the condition that the loading template matched with each SaaS application passes the test, storing each loading template on the system platform.
Step S102, when a subscription instruction of an application user is received, determining a target SaaS application and a target loading template according to the subscription instruction.
Optionally, determining the target SaaS application and the target loading template according to the subscription instruction includes: extracting the application type contained in the subscription instruction; and determining a target SaaS application according to the application type, and taking a loading template matched with the target SaaS application as a target loading template.
When an application user needs to rent the SaaS application deployed on the system platform, a subscription instruction may be sent to the system platform, and the subscription instruction includes an application type of the SaaS application to be rented, so that a target SaaS application may be determined according to the application type, for example, when the target SaaS application is a virtual machine 1, a loading template matched with the virtual machine 1 is already stored on the system platform, and thus the loading template matched with the virtual machine 1 is directly used as the target loading template.
It should be noted that the subscription instruction may include multiple application types, that is, an application user may rent multiple SaaS applications on the system platform at the same time, and the system platform may determine multiple target SaaS applications and target loading templates corresponding to the target SaaS applications when acquiring the subscription instruction including the multiple application types. In the embodiment, a plurality of target SaaS applications and target loading templates matched with the target SaaS applications can be determined simultaneously by receiving one subscription instruction of an application user. A plurality of target SaaS applications and target loading templates can be determined simultaneously through one subscription instruction sent by an application user, and therefore the loading efficiency of the SaaS applications is further improved.
And step S103, loading the target SaaS application according to the target loading template so that the application user can use the loaded target SaaS application.
Optionally, loading the target SaaS application according to the target loading template includes: extracting a loading process in the target loading template; and loading the target SaaS application according to the extracted loading flow.
In this embodiment, after the target SaaS application and the target loading template are determined, the target SaaS application may be loaded according to a loading flow in the target loading template. And when the number of the determined target loading templates is multiple, the corresponding target SaaS application can be loaded in parallel according to each target loading template, and the loading of each target SaaS application is not influenced mutually.
According to the embodiment of the invention, the loading template matched with each SaaS application is constructed in advance, so that when a subscription instruction of an application user to the target SaaS application is received, the application can be loaded according to the target loading template matched with the target SaaS application without manual loading operation, and the application loading efficiency is improved.
Example two
Fig. 2 is a flowchart of a SaaS application loading method according to a second embodiment of the present invention, where this embodiment mainly specifically describes loading of a target SaaS application according to a target loading template.
As shown in fig. 2, the method includes:
step S201, a loading template matched with each SaaS application is constructed according to a loading configuration instruction of an application provider.
Optionally, before acquiring a loading template matched with each SaaS application according to a loading configuration instruction of an application provider, the method further includes: receiving a SaaS application deployment instruction of an application provider, wherein the application deployment instruction comprises a deployment template type; calling an original deployment template according to the type of the deployment template; judging whether the deployment instruction contains deployment configuration parameters or not, if so, configuring the original deployment template by adopting the deployment configuration parameters to obtain a deployment template matched with the SaaS application, and otherwise, directly taking the original deployment template as the deployment template matched with the SaaS application; and testing the deployment template in a specified environment, and deploying the matched SaaS application according to the deployment template under the condition of determining that the test is passed.
Optionally, before receiving the SaaS application deployment instruction from the application provider, the method further includes: receiving a login request of an application provider, wherein the login request comprises a user identity; and when the application provider is determined to be a legal user according to the user identity, providing a specified environment for the application provider.
Optionally, the building of a loading template matched with each SaaS application according to a loading configuration instruction of an application provider includes: extracting the type of the loading template and the loading configuration parameters contained in the loading configuration instruction; calling an original loading template according to the type of the loading template; and configuring the original loading template according to the loading configuration parameters to construct a loading template matched with the SaaS application.
Step S202, when a subscription instruction of an application user is received, a target SaaS application and a target loading template are determined according to the subscription instruction.
Optionally, determining the target SaaS application and the target loading template according to the subscription instruction includes: extracting the application type contained in the subscription instruction; and determining a target SaaS application according to the application type, and taking a loading template matched with the target SaaS application as a target loading template.
In step S203, a loading flow in the target loading template is extracted.
Specifically, in the present embodiment, after the target loading template is obtained, since the target loading template includes the specific loading flow of the matched SaaS application, the specific operation step of loading the SaaS application is specifically included in the loading flow, for example, the loading flow included in the loading template for the virtual machine 1 is: operation 1 determines a load address of an application user; operation 2 allocates a corresponding loading resource for the loading address; operation 3 acquires a virtual machine 1 which is deployed on a system platform in advance; operation 4 loads virtual machine 1 at the load address using the load resource. Of course, this embodiment is merely an example, and the loading flow included in each target loading template is not limited.
It should be noted that when it is determined that the number of the target loading templates is multiple, the loading flows in the target templates may be extracted respectively, for example, when the target loading template 1 corresponding to the virtual machine 1 is obtained, and simultaneously the target loading template 2 corresponding to the database is also obtained, the loading flow for the virtual machine 1 in the target loading template 1 and the loading flow for the virtual machine 2 in the target template 2 may be extracted simultaneously, and the two flows do not interfere with each other and are executed in parallel, so that the extraction efficiency of the loading flows is improved.
And step S204, loading the target SaaS application according to the extracted loading flow so that an application user can use the loaded target SaaS application.
After the loading flows in the target loading templates are extracted, the target SaaS application may be loaded according to the extracted loading flows, for example, when the loading flows extracted in the loading template 1 for the virtual machine 1 are: operation 1 determines a load address of an application user; operation 2 allocates a corresponding loading resource for the loading address; operation 3 acquires a virtual machine 1 which is deployed on a system platform in advance; operation 4 loads virtual machine 1 at the load address using the load resource. The system platform automatically loads the virtual machine 1 in the sequence from operation 1 to operation 4 without the operation of the application provider, so that the application user rents the loaded virtual machine 1. And even under the condition that a plurality of application users subscribe to the virtual machine 1 at the same time, the system platform can automatically load the applications for different application users according to the extracted loading flow without manually repeating the loading operation by an application supplier, thereby improving the efficiency of application loading.
In the present embodiment, when a plurality of target SaaS applications are provided, the loading flows corresponding to the target SaaS applications are acquired, and the loading flows can be executed independently in parallel when the loading is performed, so that the loading of the corresponding target SaaS applications can be performed automatically, and the loading flows can be executed independently, thereby further shortening the loading time of the target SaaS applications and further improving the loading efficiency of the target SaaS applications.
According to the embodiment of the invention, the loading template matched with each SaaS application is constructed in advance, so that when a subscription instruction of an application user to the target SaaS application is received, the application can be loaded according to the target loading template matched with the target SaaS application, manual loading operation is not needed, and the application loading efficiency is improved.
EXAMPLE III
Fig. 3 is a schematic structural diagram of a SaaS application loading apparatus according to a third embodiment of the present invention. As shown in fig. 3, the apparatus includes: a loading template acquisition module 310, a target loading template determination module 320, and an application loading module 330.
The loading template acquiring module 310 is configured to construct a loading template matched with each SaaS application according to a loading configuration instruction of an application provider, where the loading template includes a loading flow of the SaaS application;
the target loading template determining module 320 is configured to determine a target SaaS application and a target loading template according to a subscription instruction when the subscription instruction of an application user is received;
and the application loading module 330 is configured to load the target SaaS application according to the target loading template, so that an application user uses the loaded target SaaS application.
Optionally, the apparatus further includes an application deployment module, configured to receive a SaaS application deployment instruction of an application provider, where the application deployment instruction includes a deployment template type;
calling an original deployment template according to the type of the deployment template;
judging whether the deployment instruction contains deployment configuration parameters or not, if so, configuring the original deployment template by adopting the deployment configuration parameters to obtain a deployment template matched with the SaaS application, and otherwise, directly taking the original deployment template as the deployment template matched with the SaaS application;
and testing the deployment template in a specified environment, and deploying the matched SaaS application according to the deployment template under the condition of determining that the test is passed.
Optionally, the apparatus further includes an identity verification module, configured to receive a login request of the application provider, where the login request includes a user identity;
and when the application provider is determined to be a legal user according to the user identity, providing a specified environment for the application provider.
Optionally, the loading template obtaining module is configured to extract a type of the loading template and loading configuration parameters included in the loading configuration instruction;
calling an original loading template according to the type of the loading template;
and configuring the original loading template according to the loading configuration parameters to construct a loading template matched with the SaaS application.
Optionally, the target loading template determining module is configured to extract an application type included in the subscription instruction;
and determining a target SaaS application according to the application type, and taking a loading template matched with the target SaaS application as a target loading template.
Optionally, the application loading module is configured to extract a loading process in the target loading template;
and loading the target SaaS application according to the extracted loading flow.
Optionally, the format of the SaaS application includes: git code repository format, mirror format or jar package format.
The SaaS application loading device provided by the embodiment of the invention can execute the SaaS application loading method provided by any embodiment of the invention, and has the corresponding functional module and beneficial effect of the execution method.
Example four
FIG. 4 shows a schematic block diagram of an electronic device 10 that may be used to implement an embodiment of the invention. Electronic devices are intended to represent various forms of digital computers, such as laptops, desktops, workstations, personal digital assistants, servers, blade servers, mainframes, and other appropriate computers. The electronic device may also represent various forms of mobile devices, such as personal digital assistants, cellular phones, smart phones, wearable devices (e.g., helmets, glasses, watches, etc.), and other similar computing devices. The components shown herein, their connections and relationships, and their functions, are meant to be exemplary only, and are not meant to limit implementations of the inventions described and/or claimed herein.
As shown in fig. 4, the electronic device 10 includes at least one processor 11, and a memory communicatively connected to the at least one processor 11, such as a Read Only Memory (ROM) 12, a Random Access Memory (RAM) 13, and the like, wherein the memory stores a computer program executable by the at least one processor, and the processor 11 can perform various suitable actions and processes according to the computer program stored in the Read Only Memory (ROM) 12 or the computer program loaded from a storage unit 18 into the Random Access Memory (RAM) 13. In the RAM 13, various programs and data necessary for the operation of the electronic apparatus 10 can also be stored. The processor 11, the ROM 12, and the RAM 13 are connected to each other via a bus 14. An input/output (I/O) interface 15 is also connected to the bus 14.
A number of components in the electronic device 10 are connected to the I/O interface 15, including: an input unit 16 such as a keyboard, a mouse, or the like; an output unit 17 such as various types of displays, speakers, and the like; a storage unit 18 such as a magnetic disk, optical disk, or the like; and a communication unit 19 such as a network card, modem, wireless communication transceiver, etc. The communication unit 19 allows the electronic device 10 to exchange information/data with other devices via a computer network such as the internet and/or various telecommunication networks.
The processor 11 may be a variety of general and/or special purpose processing components having processing and computing capabilities. Some examples of processor 11 include, but are not limited to, a Central Processing Unit (CPU), a Graphics Processing Unit (GPU), various specialized Artificial Intelligence (AI) computing chips, various processors running machine learning model algorithms, a Digital Signal Processor (DSP), and any suitable processor, controller, microcontroller, or the like. The processor 11 executes the respective methods and processes described above, such as the SaaS application loading method.
In some embodiments, the SaaS application loading method may be implemented as a computer program tangibly embodied in a computer-readable storage medium, such as storage unit 18. In some embodiments, part or all of the computer program may be loaded and/or installed onto the electronic device 10 via the ROM 12 and/or the communication unit 19. When the computer program is loaded into RAM 13 and executed by processor 11, one or more steps of the SaaS application loading method described above may be performed. Alternatively, in other embodiments, the processor 11 may be configured to perform the SaaS application loading method by any other suitable means (e.g., by means of firmware).
Various implementations of the systems and techniques described here above may be implemented in digital electronic circuitry, integrated circuitry, field Programmable Gate Arrays (FPGAs), application Specific Integrated Circuits (ASICs), application Specific Standard Products (ASSPs), system on a chip (SOCs), load programmable logic devices (CPLDs), computer hardware, firmware, software, and/or combinations thereof. These various embodiments may include: implemented in one or more computer programs that are executable and/or interpretable on a programmable system including at least one programmable processor, which may be special or general purpose, receiving data and instructions from, and transmitting data and instructions to, a storage system, at least one input device, and at least one output device.
A computer program for implementing the methods of the present invention may be written in any combination of one or more programming languages. These computer programs may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus, such that the computer programs, when executed by the processor, cause the functions/acts specified in the flowchart and/or block diagram block or blocks to be performed. A computer program can execute entirely on a machine, partly on a machine, as a stand-alone software package partly on a machine and partly on a remote machine or entirely on a remote machine or server.
In the context of the present invention, a computer-readable storage medium may be a tangible medium that can contain, or store a computer program for use by or in connection with an instruction execution system, apparatus, or device. A computer readable storage medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. Alternatively, the computer readable storage medium may be a machine readable signal medium. More specific examples of a machine-readable storage medium would include an electrical connection based on one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.
To provide for interaction with a user, the systems and techniques described here can be implemented on an electronic device having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to a user; and a keyboard and a pointing device (e.g., a mouse or a trackball) by which a user may provide input to the electronic device. Other kinds of devices may also be used to provide for interaction with a user; for example, feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user may be received in any form, including acoustic, speech, or tactile input.
The systems and techniques described here can be implemented in a computing system that includes a back-end component (e.g., as a data server), or that includes a middleware component (e.g., an application server), or that includes a front-end component (e.g., a user computer having a graphical user interface or a web browser through which a user can interact with an implementation of the systems and techniques described here), or any combination of such back-end, middleware, or front-end components. The components of the system can be interconnected by any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include: local Area Networks (LANs), wide Area Networks (WANs), blockchain networks, and the internet.
The computing system may include clients and servers. A client and server are generally remote from each other and typically interact through a communication network. The relationship of client and server arises by virtue of computer programs running on the respective computers and having a client-server relationship to each other. The server can be a cloud server, also called a cloud computing server or a cloud host, and is a host product in a cloud computing service system, so that the defects of high management difficulty and weak service expansibility in the traditional physical host and VPS service are overcome.
It should be understood that various forms of the flows shown above may be used, with steps reordered, added, or deleted. For example, the steps described in the present invention may be executed in parallel, sequentially, or in different orders, and are not limited herein as long as the desired result of the technical solution of the present invention can be achieved.
The above-described embodiments should not be construed as limiting the scope of the invention. It should be understood by those skilled in the art that various modifications, combinations, sub-combinations and substitutions may be made in accordance with design requirements and other factors. Any modification, equivalent replacement, and improvement made within the spirit and principle of the present invention should be included in the protection scope of the present invention.

Claims (10)

1. A SaaS application loading method is characterized by comprising the following steps:
the method comprises the steps that a loading template matched with each SaaS application is built according to a loading configuration instruction of an application provider, wherein the loading template comprises a loading flow of the SaaS application;
when a subscription instruction of an application user is received, determining a target SaaS application and a target loading template according to the subscription instruction;
and loading the target SaaS application according to the target loading template so that the application user uses the loaded target SaaS application.
2. The method according to claim 1, wherein before acquiring the loading template matching each SaaS application according to the loading configuration instruction of the application provider, the method further comprises:
receiving a SaaS application deployment instruction of an application provider, wherein the application deployment instruction comprises a deployment template type;
calling an original deployment template according to the deployment template type;
judging whether the deployment instruction contains deployment configuration parameters or not, if so, configuring the original deployment template by adopting the deployment configuration parameters to obtain a deployment template matched with the SaaS application, otherwise, directly taking the original deployment template as the deployment template matched with the SaaS application;
and testing the deployment template in a specified environment, and deploying the matched SaaS application according to the deployment template under the condition of determining that the test is passed.
3. The method of claim 2, wherein before receiving the SaaS application deployment instruction of the application provider, the method further comprises:
receiving a login request of an application provider, wherein the login request comprises a user identity;
and when the application provider is determined to be a legal user according to the user identity, providing the specified environment for the application provider.
4. The method according to claim 1, wherein the building of the loading template matched with each SaaS application according to the loading configuration instruction of the application provider comprises:
extracting a loading template type and loading configuration parameters contained in the loading configuration instruction;
calling an original loading template according to the type of the loading template;
and configuring the original loading template according to the loading configuration parameters to construct a loading template matched with the SaaS application.
5. The method of claim 1, wherein determining a target SaaS application and a target loading template according to the subscription instruction comprises:
extracting the application type contained in the subscription instruction;
and determining the target SaaS application according to the application type, and taking a loading template matched with the target SaaS application as the target loading template.
6. The method of claim 1, wherein the loading the target SaaS application according to the target loading template comprises:
extracting a loading process in the target loading template;
and loading the target SaaS application according to the extracted loading flow.
7. The method according to any of claims 1 to 6, wherein the format of the SaaS application comprises: git code repository format, mirror format or jar package format.
8. A SaaS application loading apparatus, comprising:
the system comprises a loading template acquisition module, a loading template acquisition module and a loading module, wherein the loading template acquisition module is used for constructing a loading template matched with each SaaS application according to a loading configuration instruction of an application provider, and the loading template comprises a loading flow of the SaaS application;
the target loading template determining module is used for determining a target SaaS application and a target loading template according to a subscription instruction when the subscription instruction of an application user is received;
and the application loading module is used for loading the target SaaS application according to the target loading template so that the application user can use the loaded target SaaS application.
9. An electronic device, characterized in that the electronic device comprises:
at least one processor; and
a memory communicatively coupled to the at least one processor; wherein,
the memory stores a computer program executable by the at least one processor, the computer program being executable by the at least one processor to enable the at least one processor to perform the method of any one of claims 1-7.
10. A computer-readable storage medium storing computer instructions for causing a processor to perform the method of any one of claims 1-7 when executed.
CN202211524680.8A 2022-11-30 2022-11-30 SaaS application loading method, device, equipment and storage medium Pending CN115827094A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202211524680.8A CN115827094A (en) 2022-11-30 2022-11-30 SaaS application loading method, device, equipment and storage medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202211524680.8A CN115827094A (en) 2022-11-30 2022-11-30 SaaS application loading method, device, equipment and storage medium

Publications (1)

Publication Number Publication Date
CN115827094A true CN115827094A (en) 2023-03-21

Family

ID=85533280

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202211524680.8A Pending CN115827094A (en) 2022-11-30 2022-11-30 SaaS application loading method, device, equipment and storage medium

Country Status (1)

Country Link
CN (1) CN115827094A (en)

Similar Documents

Publication Publication Date Title
CN108304201B (en) Object updating method, device and equipment
CN113220573B (en) Test method and device for micro-service architecture and electronic equipment
CN115373861B (en) GPU resource scheduling method and device, electronic equipment and storage medium
CN112506581A (en) Method and device for rendering small program, electronic equipment and readable storage medium
CN114389969A (en) Client test method and device, electronic equipment and storage medium
CN115168130A (en) Chip testing method and device, electronic equipment and storage medium
CN112423024A (en) Video transcoding method and device, computer equipment and storage medium
CN107045452B (en) Virtual machine scheduling method and device
CN116301997A (en) Upgrading method, device, equipment and medium of controller
CN115827094A (en) SaaS application loading method, device, equipment and storage medium
CN112307379A (en) Page generation method, device and equipment
CN112395081A (en) Resource online automatic recovery method, system, server and storage medium
CN113535187B (en) Service online method, service updating method and service providing method
CN111258879A (en) Service test scheduling method and device based on page acquisition and intelligent terminal
CN112667498B (en) Server building method, device, computer equipment and readable storage medium
CN115484149B (en) Network switching method, network switching device, electronic equipment and storage medium
CN113656268B (en) Performance test method and device for business service, electronic equipment and storage medium
CN116723061B (en) Cloud resource charging method and device, electronic equipment and storage medium
CN108132990B (en) Method and device for replacing APP built-in picture and storage medium
CN113590483B (en) Use case operation method and device
CN117806702A (en) Target software acquisition method and device, electronic equipment and storage medium
CN114564133A (en) Application program display method, device, equipment and medium
CN115801763A (en) File transmission method and device, electronic equipment and storage medium
CN116166545A (en) Test environment creation method, test environment creation device, medium and electronic device
CN114281436A (en) Applet communication method, apparatus, device and storage medium

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