CN115509548B - A method for deploying and using multiple SaaS applications in a single organization - Google Patents
A method for deploying and using multiple SaaS applications in a single organization Download PDFInfo
- Publication number
- CN115509548B CN115509548B CN202211360080.2A CN202211360080A CN115509548B CN 115509548 B CN115509548 B CN 115509548B CN 202211360080 A CN202211360080 A CN 202211360080A CN 115509548 B CN115509548 B CN 115509548B
- Authority
- CN
- China
- Prior art keywords
- service
- application
- unit
- applications
- metadata
- 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.)
- Active
Links
- 238000000034 method Methods 0.000 title claims abstract description 27
- 230000008520 organization Effects 0.000 title claims description 9
- 238000000638 solvent extraction Methods 0.000 claims abstract description 30
- 238000010276 construction Methods 0.000 claims description 18
- 238000005457 optimization Methods 0.000 claims description 9
- 230000008569 process Effects 0.000 claims description 5
- 238000010586 diagram Methods 0.000 description 3
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 230000004075 alteration Effects 0.000 description 1
- 210000000056 organ Anatomy 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/70—Software maintenance or management
- G06F8/71—Version control; Configuration management
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Computer Security & Cryptography (AREA)
- Stored Programmes (AREA)
Abstract
The invention discloses a single-organization multi-SaaS same-application deployment and use method, which comprises an application component layer, a combined service layer and a SaaS platform application center layer, wherein the application component layer is used for constructing a plurality of layered components based on tenant service requirements and an application layered model, the combined service layer is used for constructing tenant application deployment service stations based on functional data partitioning rules, the SaaS platform application center layer is used for constructing reconstruction of functional data based on tenant application deployment service stations through service functional requirement partitioning, new application data among units are obtained, a plurality of units are arranged in tenants, and the units are used for processing personalized requirements among the units through configuration. Thereby satisfying the functions that different usage objects use under the same and different scenes and supporting the use of multiple identical applications inside a set of organizations and units.
Description
Technical Field
The invention relates to the technical field of application deployment, in particular to a single-organization multi-SaaS same-application deployment and use method.
Background
The administrative system of the traditional organ units has lower working efficiency, each unit not only needs to develop system software and deploy hardware equipment, but also needs professional IT personnel to maintain the system software and hardware, has high cost and insufficient safety, cannot fully exert the application cooperation of each unit, and cannot efficiently serve local city construction and social economic construction.
There is an urgent need to support the existing deployment of multiple identical applications in the SaaS platform application center, where the functions of the identical applications are differentiated, so as to satisfy the functions of different objects used in the same and different scenes, and support the use of multiple identical applications in a set of organizations and units, and through role authority division, partial function data sharing and independent personality function data.
Disclosure of Invention
The invention provides a single-organization multi-SaaS same-application deployment and use method, which aims to solve the problems that in the prior art, the work efficiency of a traditional administrative system of the administrative unit is low, each unit is required to develop system software and deploy hardware equipment, professional IT personnel are required to maintain the system software and hardware, the cost is high, the safety is insufficient, the cooperative use of the application of each unit cannot be fully exerted, and the application software of each unit cannot be used for efficiently serving local city construction and social economic construction. There is an urgent need for supporting existing deployment of multiple identical applications in a SaaS platform application center, where the functions of the identical applications are differentiated, so as to satisfy functions of different objects used in the same and different scenes, and support the above problems of using multiple identical applications in a set of organizations and units, dividing by role authority, sharing part of functional data, and independent personalized functional data.
In order to achieve the above purpose, the present invention provides the following technical solutions:
a single organization multi-SaaS same-application deployment comprises an application component layer, a combined service layer and a SaaS platform application center layer;
the application component layer is used for constructing a plurality of layered components based on tenant service requirements and an application layered model;
the combined service layer is used for constructing tenant application deployment service stations based on the functional data partitioning rules;
the SaaS platform application center layer is used for deploying a service station based on tenant application, dividing a plurality of layered components through service function requirements to construct reconstruction of the function data, and obtaining new application data of each unit, wherein the tenant has a plurality of units, and the units process updated service requirements among the units.
The application component layer comprises an application dividing unit, a relation determining unit and a component constructing unit;
the application dividing unit is used for carrying out service demand analysis on applications of different units and acquiring service components to be developed according to service demand analysis results;
The relation determining unit is used for analyzing the dependency relation between the service components to be developed and the service of the application layering model and determining the hierarchy of the service components to be developed in the application layering model;
the component construction unit is used for dividing the unit application components into a plurality of layered components according to the dependency relationship between the unit application components, storing the layered components in a component library, and updating the corresponding application layered model.
The combined service layer comprises a business service unit, a service matching unit and a configuration metadata unit;
The business service unit is used for carrying out service analysis on the layered components, extracting a business function group to be built into abstract application from the service analysis, and carrying out semantic description on the business function group;
the service matching unit is used for acquiring service function descriptions of the same semantics of the service function group and the layering assembly according to the semantic descriptions of the service function group, and constructing abstract application according to the service function descriptions;
The configuration metadata unit is used for constructing a tenant application deployment service station based on the function data partitioning rule by taking the construction of the abstract application as a starting point and configuring the metadata of the application under the framework of the abstract application.
The multi-SaaS application deployment layer comprises a construction hierarchy unit, a configuration unit and a deployment unit;
The construction hierarchy unit is used for analyzing the application business abstraction hierarchy to be constructed based on the tenant application deployment service station to obtain a corresponding analysis result;
The configuration unit is used for selecting abstract applications, configuring unit metadata, matching the service requirements of each unit with the existing abstract applications, and selecting abstract applications matched with the unit requirements;
The deployment unit is used for driving metadata based on role authority division and business function requirement division to generate SaaS applications of each unit to replace original unit applications.
The deployment unit comprises a signing protocol subunit;
The method comprises the steps of acquiring SaaS applications of each unit, registering the applications, further configuring metadata information, signing a tenant grade protocol based on signing protocol subunits according to requirements of each unit on component performance, selecting corresponding service grades for each service in the applications by each unit, and calling each service component in each unit application after the tenant grade protocol signing is completed, wherein one service component meeting corresponding performance requirements and a lower layer service component on which the service component depends are selected from a plurality of deployed service components providing the same function according to the signed tenant grade protocol to provide business services for the corresponding units.
A single organization multiple SaaS same application usage method, comprising:
s101, constructing a plurality of layering components based on tenant service requirements and an application layering model;
s102, constructing a tenant application deployment service station based on a functional data partitioning rule;
s103, based on tenant application deployment service stations, a plurality of layered components are divided through service function requirements to construct reconstruction of the function data, and new application data of each unit is obtained, wherein the tenant has a plurality of units, and the units perform updated inter-unit service requirement processing.
Wherein, the step S101 includes:
s1011, carrying out service demand analysis on applications of different units, and acquiring a service component to be developed according to service demand analysis results;
S1012, analyzing the dependency relationship between the service components to be developed and the service of the application layering model, and determining the hierarchy of the service components to be developed in the application layering model;
s1013, dividing the application components into a plurality of layered components according to the dependency relationship among the application components of each unit, storing the layered components in a component library, and updating the corresponding application layered model.
Wherein, the step S102 includes:
S1021, carrying out service analysis on the layered components, extracting a service function group to be constructed into abstract application from the service analysis, and carrying out semantic description on the service function group;
S1022, acquiring service function descriptions of the same semantics of the service function group and the layering assembly according to the semantic descriptions of the service function group, and constructing abstract application according to the service function descriptions;
S1023, based on the functional data partitioning rule, constructing an abstract application as a starting point, configuring metadata of the application under the framework of the abstract application, and constructing a tenant application deployment service station.
Wherein, the step S103 includes:
s1031, analyzing an application business abstraction layer to be constructed based on a tenant application deployment service station to obtain a corresponding analysis result;
s1032, selecting abstract application according to the corresponding analysis result, configuring unit metadata, matching the business requirement of each unit with the existing abstract application, and selecting abstract application matched with the unit requirement;
And S1033, driving the metadata based on role authority division and business function requirement division to generate SaaS applications of each unit, and replacing the original unit applications.
Wherein, after the step S1033, the method includes:
The method comprises the steps of acquiring SaaS applications of each unit, registering the applications, further configuring metadata information, signing a tenant grade protocol based on signing protocol subunits according to requirements of each unit on component performance, selecting corresponding service grades for each service in the applications by each unit, and calling each service component in each unit application after the tenant grade protocol signing is completed, wherein one service component meeting corresponding performance requirements and a lower layer service component on which the service component depends are selected from a plurality of deployed service components providing the same function according to the signed tenant grade protocol to provide business services for the corresponding units.
Compared with the prior art, the invention has the following advantages:
A single-organization multi-SaaS same-application deployment method comprises an application component layer, a combined service layer and a SaaS platform application center layer, wherein the application component layer is used for constructing a plurality of layered components based on tenant service requirements and an application layered model, the combined service layer is used for constructing tenant application deployment service stations based on functional data partitioning rules, the SaaS platform application center layer is used for constructing reconstruction of functional data of the layered components through service functional requirements and role authority partitioning based on the tenant application deployment service stations, and new application data of each unit is obtained, wherein tenants have a plurality of units, and the units are used for processing updated inter-unit service requirements. Therefore, functions of different use objects used under the same and different scenes are met, a plurality of same applications are supported to be used in a set of organizations and units, and the functions of sharing part of functional data and independent personalized functional data are realized through business functional requirement division and role authority division.
Additional features and advantages of the invention will be set forth in the description which follows, and in part will be obvious from the description, or may be learned by practice of the invention. The objectives and other advantages of the invention will be realized and attained by the structure particularly pointed out in the written description and claims thereof as well as the appended drawings.
The technical scheme of the invention is further described in detail through the drawings and the embodiments.
Drawings
The accompanying drawings are included to provide a further understanding of the invention and are incorporated in and constitute a part of this specification, illustrate the invention and together with the embodiments of the invention, serve to explain the invention. In the drawings:
FIG. 1 is a block diagram of a single organization multiple SaaS common application deployment in an embodiment of the invention;
FIG. 2 is a layer structure diagram of an application component for single organization multiple SaaS with application deployment in an embodiment of the present invention;
fig. 3 is a combined service layer structure diagram of single organization multi-SaaS and application deployment in the embodiment of the invention.
Detailed Description
The preferred embodiments of the present invention will be described below with reference to the accompanying drawings, it being understood that the preferred embodiments described herein are for illustration and explanation of the present invention only, and are not intended to limit the present invention.
The embodiment of the invention provides single-organization multi-SaaS same-application deployment, which comprises an application component layer, a combined service layer and a SaaS platform application center layer;
the application component layer is used for constructing a plurality of layered components based on tenant service requirements and an application layered model;
the combined service layer is used for constructing tenant application deployment service stations based on the functional data partitioning rules;
the SaaS platform application center layer is used for deploying a service station based on tenant application, constructing functional data reconstruction by dividing a plurality of layered components through business function requirements and role authority, and acquiring new application data of each unit, wherein the tenant has a plurality of units, and the updated business requirements among the units are processed by the plurality of units.
The technical scheme comprises the working principle that the application component layer is used for constructing a plurality of layered components based on tenant service requirements and an application layered model, the combined service layer is used for constructing tenant application deployment service stations based on functional data partitioning rules, the SaaS platform application center layer is used for constructing reconstruction of functional data of the layered components through service function requirement partitioning and role authority partitioning based on the tenant application deployment service stations, and new application data of each unit is obtained, wherein a tenant has a plurality of units, and the units are used for processing updated inter-unit service requirements. Therefore, functions of different use objects used under the same and different scenes are met, a plurality of same applications are supported to be used in a set of organizations and units, and the functions of sharing part of functional data and independent personalized functional data are realized through business functional requirement division and role authority division.
The method comprises the steps that new application data of each unit are obtained, different sites are isolated in a tenant mode, a plurality of units can be arranged in the tenant, and then the units can be configured to process personalized requirements among the units.
The technical scheme has the advantages that the application component layer is used for constructing a plurality of layered components based on tenant service requirements and an application layered model, the combined service layer is used for constructing tenant application deployment service stations based on functional data partitioning rules, the SaaS platform application center layer is used for constructing reconstruction of functional data by partitioning the layered components through role authorities and service functional requirements based on tenant application deployment service stations, new application data of each unit is obtained, wherein tenants have a plurality of units, and the units are used for processing updated inter-unit service requirements. Therefore, functions of different use objects used under the same and different scenes are met, a plurality of same applications are supported to be used in a set of organizations and units, and the functions of sharing part of functional data and independent personalized functional data are realized through business functional requirement division and role authority division.
In another embodiment, the application component layer comprises an application dividing unit, a relation determining unit and a component constructing unit;
the application dividing unit is used for carrying out service demand analysis on applications of different units and acquiring service components to be developed according to service demand analysis results;
The relation determining unit is used for analyzing the dependency relation between the service components to be developed and the service of the application layering model and determining the hierarchy of the service components to be developed in the application layering model;
the component construction unit is used for dividing the unit application components into a plurality of layered components according to the dependency relationship between the unit application components, storing the layered components in a component library, and updating the corresponding application layered model.
The technical scheme comprises the working principle that the application dividing unit is used for carrying out business requirement analysis on applications of different units and obtaining service components to be developed according to business requirement analysis results, the relation determining unit is used for analyzing the dependency relation between the service components to be developed and services of the application layering model and determining the level of the service components to be developed in the application layering model, and the component constructing unit is used for dividing the service components to be developed into a plurality of layering components according to the dependency relation among the application components of each unit, storing the layering components in a component library and updating the corresponding application layering model.
The technical scheme has the advantages that the application dividing unit is used for carrying out business requirement analysis on applications of different units and obtaining service components to be developed according to business requirement analysis results, the relation determining unit is used for analyzing the dependence relation between the service components to be developed and services of the application layering model and determining the level of the service components to be developed in the application layering model, and the component constructing unit is used for dividing the dependence relation among the application components of each unit into a plurality of layering components, storing the layering components in a component library and updating the corresponding application layering model. Therefore, the influence on service consumption resources and service quality caused by the hierarchical relationship when various services are in the same hierarchy and different hierarchies is reduced.
In another embodiment, the combined service layer comprises a business service unit, a service matching unit and a configuration metadata unit;
The business service unit is used for carrying out service analysis on the layered components, extracting a business function group to be built into abstract application from the service analysis, and carrying out semantic description on the business function group;
the service matching unit is used for acquiring service function descriptions of the same semantics of the service function group and the layering assembly according to the semantic descriptions of the service function group, and constructing abstract application according to the service function descriptions;
The configuration metadata unit is used for constructing a tenant application deployment service station based on the function data partitioning rule by taking the construction of the abstract application as a starting point and configuring the metadata of the application under the framework of the abstract application.
The service matching unit is used for acquiring service function descriptions of the same semantics of the service function groups and the layered components according to the semantic descriptions of the service function groups, constructing abstract applications according to the service function descriptions, and configuring metadata units are used for configuring metadata of the applications under the framework of the abstract applications based on functional data partitioning rules with the abstract applications being constructed as starting points, and constructing tenant application deployment service stations.
The technical scheme has the advantages that the service unit is used for carrying out service analysis on a plurality of layered components, extracting a service function group to be built into abstract application from the service analysis, carrying out semantic description on the service function group, the service matching unit is used for obtaining service function description of the same semantics of the service function group and the layered components according to the semantic description of the service function group, building the abstract application according to the service function description, the configuration metadata unit is used for constructing the abstract application based on the function data partitioning rule, taking the abstract application as a starting point, configuring metadata of the application under the framework of the abstract application, and constructing the tenant application deployment service station. The security of the SaaS service can be ensured, and meanwhile, the service in the same hierarchy has a calling relationship.
In another embodiment, the multi-SaaS application deployment layer comprises a construction hierarchy unit, a configuration unit and a deployment unit;
The construction hierarchy unit is used for analyzing the application business abstraction hierarchy to be constructed based on the tenant application deployment service station to obtain a corresponding analysis result;
The configuration unit is used for selecting abstract applications, configuring unit metadata, matching the service requirements of each unit with the existing abstract applications, and selecting abstract applications matched with the unit requirements;
The deployment unit is used for driving metadata based on role authority division and business function requirement division to generate SaaS applications of each unit to replace original unit applications.
The technical scheme comprises the working principle that the construction hierarchy unit is used for analyzing an application service abstraction hierarchy to be constructed based on a tenant application deployment service station to obtain a corresponding analysis result, the configuration unit is used for selecting abstract applications, configuring unit metadata, matching the service requirements of each unit with the existing abstract applications, selecting abstract applications matched with the unit requirements, and the deployment unit is used for driving the metadata based on role authority division and service function requirement division to generate each unit of SaaS applications to replace the original unit applications.
The technical scheme has the advantages that the construction level unit is used for analyzing the application business abstraction level to be constructed based on the tenant application deployment service station to obtain a corresponding analysis result, the configuration unit is used for selecting abstract applications, configuring unit metadata, matching the business requirements of each unit with the existing abstract applications, selecting abstract applications matched with the unit requirements, and the deployment unit is used for driving the metadata based on role authority division and business function requirement division to generate each unit of SaaS applications to replace the original unit applications. The configurable and isolated application is ensured by using metadata of each unit, and the application at the logic level is changed into a truly executable application through service deployment.
In another embodiment, the deployment unit includes an endorsement protocol subunit;
The method comprises the steps of acquiring SaaS applications of each unit, registering the applications, further configuring metadata information, signing a tenant grade protocol based on signing protocol subunits according to requirements of each unit on component performance, selecting corresponding service grades for each service in the applications by each unit, and calling each service component in each unit application after the tenant grade protocol signing is completed, wherein one service component meeting corresponding performance requirements and a lower layer service component on which the service component depends are selected from a plurality of deployed service components providing the same function according to the signed tenant grade protocol to provide business services for the corresponding units.
The technical scheme comprises the working principle that after the SaaS application of each unit is obtained, the application is registered, metadata information is further configured, according to requirements of each unit on component performance, a tenant grade protocol is signed by each unit based on a signing protocol subunit, corresponding service grades are selected for each service in the application, after the tenant grade protocol is signed, each service component in each unit application is called, wherein one service component meeting corresponding performance requirements and a lower layer service component on which the service component depends are selected from a plurality of deployed service components providing the same function according to the signed tenant grade protocol to provide service for the corresponding unit.
The technical scheme has the advantages that after the SaaS application of each unit is obtained, the application is registered, metadata information is further configured, according to requirements of each unit on component performance, a tenant grade protocol is signed based on a signing protocol subunit, each unit selects a corresponding service grade for each service in the application, after the tenant grade protocol is signed, each service component in each unit application is called, wherein one service component meeting corresponding performance requirements and a lower layer service component on which the service component depends are selected from a plurality of deployed service components providing the same function according to the signed tenant grade protocol to provide service for the corresponding unit. Therefore, the functions of different use objects used in the same scene and different scenes are met, a plurality of same applications are supported to be used in a set of organizations and units, and the functions of sharing part of functional data and independent personalized functional data are realized through role authority division.
In another embodiment, a method for multi-SaaS co-application use of a single organization includes:
s101, constructing a plurality of layering components based on tenant service requirements and an application layering model;
s102, constructing a tenant application deployment service station based on a functional data partitioning rule;
s103, based on tenant application deployment service stations, a plurality of layered components are divided through service function requirements to construct reconstruction of the function data, and new application data of each unit is obtained, wherein the tenant has a plurality of units, and the units perform updated inter-unit service requirement processing.
The technical scheme comprises the working principle that a plurality of layered components are built based on tenant service requirements and an application layered model, a tenant application deployment service station is built based on functional data partitioning rules, the functional data are built through the service functional requirement partitioning of the layered components through reconstruction of the functional data, and new application data of each unit are obtained, wherein a tenant has a plurality of units, and the updated inter-unit service requirements are processed by the plurality of units.
The tenant application uses services in the combined service layer without knowing the specific implementation of the services, the services of the combined service layer operate through the services of the application component layer, and the services of the SaaS platform application center layer realize business processes by receiving the call of the services of the combined service layer. Meanwhile, the service in the same hierarchy has a calling relationship. In addition, there are various dependencies between services of different layers and between services of the same layer.
The technical scheme has the advantages that a plurality of layered components are built based on tenant service requirements and application layered models, a tenant application deployment service station is built based on functional data partitioning rules, the tenant application deployment service station is used for building reconstruction of functional data through service functional requirement partitioning of the layered components, new application data of each unit are obtained, wherein a tenant has a plurality of units, and the units are used for processing updated inter-unit service requirements. Therefore, the influence on service consumption resources and service quality caused by the hierarchical relationship when various services are in the same hierarchy and different hierarchies is reduced.
In another embodiment, the step S101 includes:
s1011, carrying out service demand analysis on applications of different units, and acquiring a service component to be developed according to service demand analysis results;
S1012, analyzing the dependency relationship between the service components to be developed and the service of the application layering model, and determining the hierarchy of the service components to be developed in the application layering model;
s1013, dividing the application components into a plurality of layered components according to the dependency relationship among the application components of each unit, storing the layered components in a component library, and updating the corresponding application layered model.
The technical scheme comprises the working principles of carrying out business demand analysis on applications of different units, obtaining service components to be developed according to business demand analysis results, analyzing the dependency relationship between the service components to be developed and services of an application layering model, determining the level of the service components to be developed in the application layering model, dividing the service components into a plurality of layering components according to the dependency relationship among the application components of each unit, storing the layering components in a component library, and updating the corresponding application layering model.
The technical scheme has the advantages that business demand analysis is conducted on applications of different units, service components to be developed are obtained according to business demand analysis results, the dependence relationship between the service components to be developed and services of the application layering model is analyzed, the level of the service components to be developed in the application layering model is determined, the service components are divided into a plurality of layering components according to the dependence relationship among the application components of each unit, the layering components are stored in a component library, and meanwhile the corresponding application layering model is updated. Therefore, the functions of different use objects used in the same scene and different scenes are met, a plurality of same applications are supported to be used in a set of organizations and units, and the functions of sharing part of functional data and independent personalized functional data are realized through role authority division.
In another embodiment, the step S102 includes:
S1021, carrying out service analysis on the layered components, extracting a service function group to be constructed into abstract application from the service analysis, and carrying out semantic description on the service function group;
S1022, acquiring service function descriptions of the same semantics of the service function group and the layering assembly according to the semantic descriptions of the service function group, and constructing abstract application according to the service function descriptions;
S1023, based on the functional data partitioning rule, constructing an abstract application as a starting point, configuring metadata of the application under the framework of the abstract application, and constructing a tenant application deployment service station.
The technical scheme comprises the working principles of carrying out service analysis on a plurality of layered components, extracting a service function group to be built into abstract application from the service analysis, carrying out semantic description on the service function group, obtaining service function description of the same semantics of the service function group and the layered components according to the semantic description of the service function group, building the abstract application according to the service function description, and configuring metadata of the application under the framework of the abstract application based on a function data partitioning rule with the abstract application as a starting point to build a tenant application deployment service station.
The technical scheme has the advantages that service analysis is conducted on a plurality of layered components, a service function group to be built for abstract application is extracted from the service analysis, semantic description is conducted on the service function group, service function descriptions of the same semantics of the service function group and the layered components are obtained according to the semantic description of the service function group, abstract application is built according to the service function descriptions, abstract application is built based on function data partitioning rules, metadata of the application is configured under the framework of the abstract application, and tenant application deployment service stations are built. The security of the SaaS service can be ensured, and meanwhile, the service in the same hierarchy has a calling relationship.
In another embodiment, the step S103 includes:
s1031, analyzing an application business abstraction layer to be constructed based on a tenant application deployment service station to obtain a corresponding analysis result;
s1032, selecting abstract application according to the corresponding analysis result, configuring unit metadata, matching the business requirement of each unit with the existing abstract application, and selecting abstract application matched with the unit requirement;
And S1033, driving the metadata based on role authority division and business function requirement division to generate SaaS applications of each unit, and replacing the original unit applications.
The technical scheme comprises the working principle that an application business abstraction layer to be constructed is analyzed based on a tenant application deployment service station to obtain a corresponding analysis result, abstract applications are selected according to the corresponding analysis result, unit metadata are configured, business requirements of each unit are matched with the existing abstract applications, abstract applications matched with the unit requirements are selected, metadata are driven based on role authority division and business function requirement division, and SaaS applications of each unit are generated to replace the original unit applications.
The method comprises the steps of selecting abstract applications meeting business requirements from all units of SaaS applications, obtaining the abstract applications, analyzing corresponding unit requirements, constructing new abstract applications, deploying the selected abstract applications based on related service instances in an application layering model, analyzing various functional requirements and non-functional requirements of the units, configuring variable points in the abstract applications, describing the variable points through metadata, wherein the description comprises UI metadata, service metadata, data metadata, authority metadata and functional metadata, and driving all the units of applications to operate by using the metadata.
The SaaS service provided by the tenant application deployment service station comprises m different types of multi-unit SaaS applications, wherein the number of instances of each type of SaaS application is determined according to unit services, t unit services are provided, each unit service relates to different SaaS applications, n types of resources can be selected, the types and the number of the finally used services are related to deployment strategies, the SaaS applications are combined and optimized through an optimized deployment scheme, and the combined and optimized formula is as follows:
wherein F (m) represents a combined optimization fitness function, V (m) represents a unit metadata set used by an individual m, V represents an element in the unit metadata set, e g(v) represents a corresponding cost value of type g (V); representing the highest cost value in the current jth data set; representing the lowest cost value in the current jth data set;
And obtaining the consumption of the SaaS application on the server node resources by obtaining the combined optimization fitness function, and carrying out combined optimization on the deployment strategy according to the consumption of the resources, thereby meeting the service requirements of each government unit on the application software.
The technical scheme has the advantages that the service station is deployed on the basis of tenant applications to analyze the application business abstraction level to be constructed to obtain a corresponding analysis result, abstract applications are selected according to the corresponding analysis result, unit metadata are configured, business requirements of each unit are matched with the existing abstract applications, abstract applications matched with the unit requirements are selected, metadata are driven on the basis of role authority division and business function requirement division, and SaaS applications of each unit are generated to replace the original unit applications. The configurable and isolated application is ensured by using metadata of each unit, and the application at the logic level is changed into a truly executable application through service deployment.
In another embodiment, the step S1033 includes:
The method comprises the steps of acquiring SaaS applications of each unit, registering the applications, further configuring metadata information, signing a tenant grade protocol based on signing protocol subunits according to requirements of each unit on component performance, selecting corresponding service grades for each service in the applications by each unit, and calling each service component in each unit application after the tenant grade protocol signing is completed, wherein one service component meeting corresponding performance requirements and a lower layer service component on which the service component depends are selected from a plurality of deployed service components providing the same function according to the signed tenant grade protocol to provide business services for the corresponding units.
The working principle of the technical scheme is that according to the business requirements of each unit, business matching is carried out in the corresponding abstract application, one abstract application is selected, the abstract application is registered in the abstract application system, relevant information corresponding to the unit is filled in, and the relevant information is processed to form partial metadata information;
The method comprises the steps of acquiring SaaS applications of each unit, registering the applications and further configuring metadata information, signing a tenant grade protocol for each service in the applications based on signing protocol subunits according to requirements of each unit on component performance, and calling each service component in each unit application after the tenant grade protocol signing is completed, wherein one service component meeting corresponding performance requirements and a lower layer service component on which the service component depends are selected from a plurality of deployed service components providing the same functions according to the signed tenant grade protocol to provide business services for the corresponding units;
The SaaS application of each unit is driven by unit metadata with the abstract application as a starting point, the abstract application is pulled out of a service framework of the application, the specific difference of each unit is described by using metadata, and the metadata types used for describing the application of each unit comprise functional metadata, page metadata and style metadata.
The technical scheme has the advantages that after the SaaS application of each unit is obtained, the application is registered, metadata information is further configured, according to requirements of each unit on component performance, a tenant grade protocol is signed based on a signing protocol subunit, each unit selects a corresponding service grade for each service in the application, after the tenant grade protocol is signed, each service component in each unit application is called, wherein one service component meeting corresponding performance requirements and a lower layer service component on which the service component depends are selected from a plurality of deployed service components providing the same function according to the signed tenant grade protocol to provide service for the corresponding unit. The configurable and isolated application is ensured by using metadata of each unit, and the application at the logic level is changed into a truly executable application through service deployment.
It will be apparent to those skilled in the art that various modifications and variations can be made to the present invention without departing from the spirit or scope of the invention. Thus, it is intended that the present invention also include such modifications and alterations insofar as they come within the scope of the appended claims or the equivalents thereof.
Claims (4)
1. A single-organization multi-SaaS same-application deployment is characterized by comprising an application component layer, a combined service layer and a SaaS platform application center layer;
the application component layer is used for constructing a plurality of layered components based on tenant service requirements and an application layered model;
the combined service layer is used for constructing tenant application deployment service stations based on the functional data partitioning rules;
The SaaS platform application center layer is used for deploying a service station based on tenant application, dividing a plurality of layered components through service function requirements to construct reconstruction of function data, and acquiring new application data among units, wherein the tenant has a plurality of units, and the units process service requirements among units through configuration;
the combined service layer comprises a business service unit, a service matching unit and a configuration metadata unit;
The business service unit is used for carrying out service analysis on the layered components, extracting a business function group to be built into abstract application from the service analysis, and carrying out semantic description on the business function group;
the service matching unit is used for acquiring service function descriptions of the same semantics of the service function group and the layering assembly according to the semantic descriptions of the service function group, and constructing abstract application according to the service function descriptions;
The configuration metadata unit is used for constructing a tenant application deployment service station based on the functional data partitioning rule by taking the construction of the abstract application as a starting point and configuring the metadata of the application under the framework of the abstract application;
The SaaS platform application center layer comprises a construction hierarchy unit, a configuration unit and a deployment unit;
The construction hierarchy unit is used for analyzing the application business abstraction hierarchy to be constructed based on the tenant application deployment service station to obtain a corresponding analysis result;
The configuration unit is used for selecting abstract applications, configuring unit metadata, matching the service requirements of each unit with the existing abstract applications, and selecting abstract applications matched with the unit requirements;
the deployment unit is used for driving metadata based on role authority division and business function requirement division to generate SaaS applications of each unit so as to replace the original unit applications;
The method comprises the steps of selecting abstract applications meeting business requirements from all units of SaaS applications, obtaining the abstract applications, analyzing corresponding unit requirements, and constructing new abstract applications, deploying the selected abstract applications based on related service instances in an application layering model, analyzing various functional requirements and non-functional requirements of the units, configuring variable points in the abstract applications, describing the variable points through metadata, wherein the description comprises UI metadata, service metadata, data metadata, authority metadata and functional metadata;
The SaaS service provided by the tenant application deployment service station comprises a plurality of different types of multi-unit SaaS applications, wherein the number of instances of each type of SaaS application is determined according to unit services, t unit services are provided, each unit service relates to different SaaS applications, n types of resources are selected, the types and the number of the finally used services are related to deployment strategies, the SaaS applications are combined and optimized through an optimized deployment scheme, and the combined and optimized formula is as follows:
Wherein, Representing a combined optimization fitness function; A unit metadata set representing the usage of the individual m; Representing elements in a unit metadata set; Representation type Corresponding cost values of (a); representing the highest cost value in the current jth data set; representing the lowest cost value in the current jth data set;
acquiring consumption of the SaaS application on the server node resources by acquiring a combined optimization fitness function, and carrying out combined optimization on the deployment strategy according to the consumption of the resources;
the deployment unit comprises a signing protocol subunit;
The method comprises the steps of acquiring SaaS applications of each unit, registering the applications, further configuring metadata information, signing a tenant grade protocol based on signing protocol subunits according to requirements of each unit on component performance, selecting corresponding service grades for each service in the applications by each unit, and calling each service component in each unit application after the tenant grade protocol signing is completed, wherein one service component meeting corresponding performance requirements and a lower layer service component on which the service component depends are selected from a plurality of deployed service components providing the same function according to the signed tenant grade protocol to provide business services for the corresponding units.
2. The single-organization multi-SaaS-like application deployment of claim 1, wherein the application component layer comprises an application partitioning unit, a relationship determining unit and a component constructing unit;
The application dividing unit is used for carrying out tenant service demand analysis on the applications of different units and acquiring service components to be developed according to service demand analysis results;
The relation determining unit is used for analyzing the dependency relation between the service components to be developed and the service of the application layering model and determining the hierarchy of the service components to be developed in the application layering model;
the component construction unit is used for dividing the unit application components into a plurality of layered components according to the dependency relationship between the unit application components, storing the layered components in a component library, and updating the corresponding application layered model.
3. A method for using multiple SaaS applications of a single organization, comprising:
s101, constructing a plurality of layering components based on tenant service requirements and an application layering model;
s102, constructing a tenant application deployment service station based on a functional data partitioning rule;
S103, based on tenant application deployment service stations, constructing reconstruction of functional data by dividing a plurality of layered components through service functional requirements, and obtaining new application data of each unit, wherein the tenant has a plurality of units, and the plurality of units process updated service requirements among the units;
the step S102 includes:
S1021, carrying out service analysis on the layered components, extracting a service function group to be constructed into abstract application from the service analysis, and carrying out semantic description on the service function group;
S1022, acquiring service function descriptions of the same semantics of the service function group and the layering assembly according to the semantic descriptions of the service function group, and constructing abstract application according to the service function descriptions;
S1023, based on the functional data partitioning rule, constructing an abstract application as a starting point, configuring metadata of the application under the framework of the abstract application, and constructing a tenant application deployment service station;
the step S103 includes:
s1031, analyzing an application business abstraction layer to be constructed based on a tenant application deployment service station to obtain a corresponding analysis result;
s1032, selecting abstract application according to the corresponding analysis result, configuring unit metadata, matching the business requirement of each unit with the existing abstract application, and selecting abstract application matched with the unit requirement;
S1033, driving metadata based on role authority division and business function requirement division, and generating SaaS applications of each unit to replace the original unit applications;
The method comprises the steps of selecting abstract applications meeting business requirements from all units of SaaS applications, obtaining the abstract applications, analyzing corresponding unit requirements, and constructing new abstract applications, deploying the selected abstract applications based on related service instances in an application layering model, analyzing various functional requirements and non-functional requirements of the units, configuring variable points in the abstract applications, describing the variable points through metadata, wherein the description comprises UI metadata, service metadata, data metadata, authority metadata and functional metadata;
The SaaS service provided by the tenant application deployment service station comprises a plurality of different types of multi-unit SaaS applications, wherein the number of instances of each type of SaaS application is determined according to unit services, t unit services are provided, each unit service relates to different SaaS applications, n types of resources are selected, the types and the number of the finally used services are related to deployment strategies, the SaaS applications are combined and optimized through an optimized deployment scheme, and the combined and optimized formula is as follows:
Wherein, Representing a combined optimization fitness function; A unit metadata set representing the usage of the individual m; Representing elements in a unit metadata set; Representation type Corresponding cost values of (a); representing the highest cost value in the current jth data set; representing the lowest cost value in the current jth data set;
acquiring consumption of the SaaS application on the server node resources by acquiring a combined optimization fitness function, and carrying out combined optimization on the deployment strategy according to the consumption of the resources;
the step S1033 includes:
The method comprises the steps of acquiring SaaS applications of each unit, registering the applications, further configuring metadata information, signing a tenant grade protocol based on signing protocol subunits according to requirements of each unit on component performance, selecting corresponding service grades for each service in the applications by each unit, and calling each service component in each unit application after the tenant grade protocol signing is completed, wherein one service component meeting corresponding performance requirements and a lower layer service component on which the service component depends are selected from a plurality of deployed service components providing the same function according to the signed tenant grade protocol to provide business services for the corresponding units.
4. The method of using multiple SaaS recited in claim 3, wherein said step S101 comprises:
s1011, carrying out service demand analysis on applications of different units, and acquiring a service component to be developed according to service demand analysis results;
S1012, analyzing the dependency relationship between the service components to be developed and the service of the application layering model, and determining the hierarchy of the service components to be developed in the application layering model;
s1013, dividing the application components into a plurality of layered components according to the dependency relationship among the application components of each unit, storing the layered components in a component library, and updating the corresponding application layered model.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211360080.2A CN115509548B (en) | 2022-11-02 | 2022-11-02 | A method for deploying and using multiple SaaS applications in a single organization |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211360080.2A CN115509548B (en) | 2022-11-02 | 2022-11-02 | A method for deploying and using multiple SaaS applications in a single organization |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN115509548A CN115509548A (en) | 2022-12-23 |
| CN115509548B true CN115509548B (en) | 2024-12-03 |
Family
ID=84512385
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202211360080.2A Active CN115509548B (en) | 2022-11-02 | 2022-11-02 | A method for deploying and using multiple SaaS applications in a single organization |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN115509548B (en) |
Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101794226A (en) * | 2010-03-08 | 2010-08-04 | 山东大学 | Service software construction method and system adapting to multiple business abstraction levels |
Family Cites Families (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US9104514B2 (en) * | 2011-01-11 | 2015-08-11 | International Business Machines Corporation | Automated deployment of applications with tenant-isolation requirements |
| US11030164B2 (en) * | 2018-01-18 | 2021-06-08 | Sap Se | Artifact deployment for application managed service instances |
| CN109191008A (en) * | 2018-09-30 | 2019-01-11 | 江苏农牧科技职业学院 | A kind of micro services frame system for fish quality supervisory systems |
| US10999408B2 (en) * | 2019-04-05 | 2021-05-04 | Sap Se | Automated cloud computing tenant deployment service |
| CN112748910B (en) * | 2021-01-27 | 2024-03-19 | 山东省城市商业银行合作联盟有限公司 | System, method and equipment for product assembly research and development based on SaaS mode |
-
2022
- 2022-11-02 CN CN202211360080.2A patent/CN115509548B/en active Active
Patent Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101794226A (en) * | 2010-03-08 | 2010-08-04 | 山东大学 | Service software construction method and system adapting to multiple business abstraction levels |
Also Published As
| Publication number | Publication date |
|---|---|
| CN115509548A (en) | 2022-12-23 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110088749B (en) | Method, system and medium for automatic ontology generation | |
| CN104537155B (en) | Bullet train Fast design method and system | |
| CN101796795B (en) | Distributed system | |
| CN112241321A (en) | Computing power scheduling method and device based on Kubernetes | |
| CN112667860A (en) | Sub-graph matching method, device, equipment and storage medium | |
| CN107391744A (en) | Data storage, read method, device and its equipment | |
| CN112906206A (en) | Digital twin model construction method and device | |
| CN117294727B (en) | Cloud edge end collaborative management method based on cloud primordia and container technology | |
| CN112035516B (en) | Processing method and device for operator service, intelligent workstation and electronic equipment | |
| CN112799782A (en) | Model generation system, method, electronic device, and storage medium | |
| WO2018222488A1 (en) | Non-linear systems and methods for destination selection | |
| Smirnov et al. | Domain ontologies integration for virtual modelling and simulation environments | |
| CN110069321A (en) | Business containerization operation method, equipment, storage medium and device | |
| CN116249967A (en) | Mark-driven scheduling of computing resources for function execution | |
| CN115509548B (en) | A method for deploying and using multiple SaaS applications in a single organization | |
| CN115617331A (en) | Service arranging method, service arranging device, storage medium and electronic equipment | |
| CN109343947A (en) | A resource scheduling method and device | |
| CN112162731B (en) | Data expansion method, device, storage medium and electronic device | |
| US20100005469A1 (en) | Method and System for Defining One Flow Models with Varied Abstractions for Scalable lean Implementations | |
| CN113056725B (en) | Information processing system and information processing method | |
| CN110515611B (en) | Document number generation method | |
| CN109800015A (en) | A kind of data configuration management method, equipment and computer readable storage medium | |
| CN117806951A (en) | Intelligent scheduling method and related equipment applied to distributed operation of test cases | |
| CN104267967A (en) | Method and device for generating program codes of software | |
| CN116009843A (en) | Resource management and arrangement method and system based on private cloud platform |
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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |