CN108810164A - Device supporting SaaS application flow customization and operation as required - Google Patents
Device supporting SaaS application flow customization and operation as required Download PDFInfo
- Publication number
- CN108810164A CN108810164A CN201810713926.3A CN201810713926A CN108810164A CN 108810164 A CN108810164 A CN 108810164A CN 201810713926 A CN201810713926 A CN 201810713926A CN 108810164 A CN108810164 A CN 108810164A
- Authority
- CN
- China
- Prior art keywords
- flow
- tenant
- component
- context
- information
- 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.)
- Withdrawn
Links
- 238000000034 method Methods 0.000 claims abstract description 50
- 230000008569 process Effects 0.000 claims abstract description 34
- 238000002955 isolation Methods 0.000 claims abstract description 13
- 238000013507 mapping Methods 0.000 claims abstract description 5
- 238000013506 data mapping Methods 0.000 claims description 12
- 230000015572 biosynthetic process Effects 0.000 claims description 5
- 230000008859 change Effects 0.000 claims description 5
- 238000003786 synthesis reaction Methods 0.000 claims description 5
- 230000008878 coupling Effects 0.000 abstract description 3
- 238000010168 coupling process Methods 0.000 abstract description 3
- 238000005859 coupling reaction Methods 0.000 abstract description 3
- 238000010276 construction Methods 0.000 abstract description 2
- 230000008447 perception Effects 0.000 description 5
- 238000011161 development Methods 0.000 description 4
- 238000005516 engineering process Methods 0.000 description 4
- 238000007689 inspection Methods 0.000 description 4
- 230000003993 interaction Effects 0.000 description 3
- 230000008520 organization Effects 0.000 description 2
- 238000012545 processing Methods 0.000 description 2
- 238000013396 workstream Methods 0.000 description 2
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000000052 comparative effect Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000004044 response Effects 0.000 description 1
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/06—Protocols specially adapted for file transfer, e.g. file transfer protocol [FTP]
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q30/00—Commerce
- G06Q30/06—Buying, selling or leasing transactions
- G06Q30/0601—Electronic shopping [e-shopping]
- G06Q30/0621—Item configuration or customization
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q30/00—Commerce
- G06Q30/06—Buying, selling or leasing transactions
- G06Q30/0645—Rental transactions; Leasing transactions
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/51—Discovery or management thereof, e.g. service location protocol [SLP] or web services
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/56—Provisioning of proxy services
Landscapes
- Business, Economics & Management (AREA)
- Engineering & Computer Science (AREA)
- Accounting & Taxation (AREA)
- Finance (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Marketing (AREA)
- Economics (AREA)
- Development Economics (AREA)
- Strategic Management (AREA)
- Physics & Mathematics (AREA)
- General Business, Economics & Management (AREA)
- General Physics & Mathematics (AREA)
- Theoretical Computer Science (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
- Stored Programmes (AREA)
Abstract
The invention discloses a device and a method for supporting SaaS application flow customization and operation as required. The invention also discloses a method for supporting the SaaS application flow to be customized and operated as required, which supports the loose coupling of the flow construction and the business service, developers only need to develop the basic business service, and the device supports tenants to arrange complex business flows, can automatically acquire the current flow information and realize the flow variable access and drive of the business flows; the mapping and isolation of the multi-tenant process are realized, a process engine is shared by a plurality of tenants, the tenant processes are not interfered with each other, and software resources are fully utilized.
Description
Technical field
The present invention relates to SaaS platform running technologies fields, more particularly to a kind of support SaaS application flow on-demand customizations
And the device of operation.
Background technology
SaaS(Software-as-a-Service)It is the running software pattern that software service is provided based on internet,
SaaS applications are deployed on unified server by SaaS operators, and by way of lease, software clothes are provided to terminal user
Business.The server hardware of terminal user, network security are eliminated compared to traditional software exploitation and buying pattern, SaaS patterns
The expenditure that equipment and software upgrading are safeguarded, terminal user only needs the demand lease service according to itself, according to the content of lease
Expense is paid with the time.
SaaS applications usually introduce workflow, to support the on-demand customization of operation flow, improve the adaptability of SaaS applications.
But in the SaaS application environments leased single example, the operation flow of different tenants needs that operation is isolated, and is independent of each other more;
Also, different tenants have the same operation flow different demands, and the even same tenant, business demand is often
Be constantly it is changed, such as:Flow initialization of variable, task execution sequence, task attribute setting etc..Existing workflow
Engine there is no multi-tenant and the on-demand customization of method support process.
Jbpm is the workflow development frame of industry prevalence, need not be independent using Embedded workflow development platform
Workflow server, reduce hardware input;Jbpm be 100%java realize, realize to greatest extent it is cross-platform, across data
The support in library;Jbpm is easy to secondary development and extension as Open Source Workflow frame comparative maturity.But Jbpm
Engine is unaware of the presence of tenant, can not effectively identify role of the same name under multiple tenants, user name etc., this makes work
Flowing engine can not be according to role, user's driving, distributed tasks;In addition, task in each tenant's operation flow and theirs is mutual
The start-stop condition of ordinal relation, flow and task and the description to each task, including flow variable acquisition and write-back all
It is not quite similar, the description of traditional workflow task is difficult to meet the on-demand of multi-tenant with the development scheme that business service is mutually bound
Customized demand.
The loose coupling of operation flow and business service exploitation can be realized by meeting the engine of Bpel specifications, but corresponding one
It is a little to realize technology(Such as activebpel), based on service-oriented Technical Architecture, only support web services combination, do not support still
Task with interface type cannot achieve the participation of human task;What is more important, conventional operation stream engine do not have tenant's
Concept cannot be distinguished the flow of different tenants, can not achieve isolation, need to invent the work under a kind of new multi-tenant environment
Engine is flowed, to support the on-demand customization, flow deployment and flow of multi-tenant operation flow to execute.
Invention content
The purpose of the present invention is exactly to solve the above-mentioned problems, to provide a kind of support SaaS application flows on-demand customization and fortune
Capable device, decouples operation flow and business service, supports tenant to including the service logic including human task
Autonomous layout;The flow of layout is created and is executed by the present apparatus, meets the need that operation is isolated in tenant and business quickly changes
It asks.
To achieve the goals above, the present invention adopts the following technical scheme that:
A kind of device for supporting the on-demand customization of SaaS application flows and operation, including tenant perceives proxy module, flow describes group
Part, flow data image module, execution manager and original workflow engine, the execution manager include flow deployment group
Part, flow create component and process flow operation component;
The tenant perceives proxy module for obtaining the corresponding tenant's contextual information Context of current tenant;
The flow describe component for flow nodes information, control structure information, relevant role and user in operation flow,
The description of flow nodes and business service mapping relations;
It includes workflow defining file that the flow, which describes component,(.jbdl.xml file)With workflow interfacing file
(WorkFlow_interface.xml);The workflow defining file uses jpdl as process description language, the work
Stream interface file uses xml as description language;
The workflow defining file is used for flow nodes information in operation flow, control structure information, relevant role and uses
The description at family, flow nodes and business service mapping relations.
The workflow interfacing file reads flow nodes and business service mapping relations, institute at runtime for workflow
It includes that interface, key service name, key operation name and the flow variable serviced in SaaS applications reads rule to state map information
Then.
The flow data image module is used for according to the Context of tenant, by the relevant procedure information of tenant, role,
User is identified, the image of implementation process data and isolation;
The execution manager perceives proxy module for parsing subscription request message, with tenant and interacts the current tenant's of acquisition
Context, and call flow data mapping module, with the request of responding process, the request of the flow includes flow deployment, stream
The establishment and execution of journey example;
The flow deployment component is used to interact the Context for obtaining current tenant, call flow with tenant's perception proxy module
Data mapping module receives flow description information that flow data image module synthesizes, with tenant's feature;Dispose the stream
Journey, and the isolation of implementation process;
The flow creates component for creating workflow instance, preserves the Context of tenant;The workflow instance creates
Metadata Service is called to obtain according to the Context of current tenant's information acquisition tenant, the Context of tenant in operation system
Workflow interfacing information, workflow interfacing information inspection create when meeting the condition of workflow instance establishment at this time, if full
It is sufficient then obtain flow variable and read rule, and workflow instance is created, the basis as flow data image module;
The process flow operation component is used to interact the Context for obtaining current tenant, call flow with tenant's perception proxy module
Component is described, the procedure information with tenant's feature of flow data image module synthesis is obtained, organization flow parameter executes
Corresponding tenant's service;Tenant's service execution finishes, and call flow describes component, obtains the Service Source of change, write-back flow
Information;
The original workflow engine is used to receive the order for executing manager, executes corresponding operation.
A method of it supporting the on-demand customization of SaaS application flows and operation, specifically comprises the following steps:
Step(1):Tenant perceives proxy module according to tenant's essential information, accesses the database for preserving tenant's information, acquirement is worked as
The Context information of the corresponding tenant of preceding tenant;
Step(2):The workflow defining file that flow describes component uses jpdl as process description language, workflow interfacing text
Part uses xml as description language;The workflow interfacing file realizes that workflow reads corresponding information at runtime, including
Interface, key service name, key operation name and the flow variable serviced in SaaS applications reads rule;
Step(3):Execute manager(EM)Subscription request message is parsed, current tenant's information is obtained, mould is acted on behalf of with tenant's perception
Block interaction obtains the Context of current tenant, and call flow data mapping module makes the request of flow(Flow deployment, stream
The establishment and execution of journey example);
Step(4):Flow data image module(PDM)Realize tenant's flow data image module:By Executive Manager
Tenant's Context processing obtained by flow relevant information that analysis tenant request obtains will according to tenant Context
The relevant procedure information of tenant is marked with unique ID, the image of implementation process data and isolation;
Step(5):Original workflow engine is directly interacted with workflow database, can complete the deployment of flow, and flow is real
Example creates and executes operation.
The step(3)Include the following steps:
Step(3-1):Flow disposes component:Flow deployment operation is completed, perceiving proxy module with tenant interacts the current rent of acquisition
Family Context, call flow data mapping module receive flow that flow data image module synthesizes, with tenant's feature
Description information;And then workflow engine disposes the flow;Because flow is that tenant is peculiar, the workflow after deployment is realized
Isolation;
Step(3-2):Flow creates component:Operation system is according to current tenant's information acquisition tenant Context, according to tenant
Context calls Metadata Service to obtain workflow interfacing information, whether meets work at this time according to the inspection of workflow interfacing information
Make the condition that stream example creates, flow variable is obtained if meeting and reads rule, and creates workflow instance, preserves tenant
Context, the basis as flow data image module;
Step(3-3):Process flow operation component:Process flow operation operation is completed, the establishment of flow instance, the execution of flow are included;With
Tenant perceives proxy module interaction and obtains current tenant Context, and call flow data mapping module receives flow data image
The procedure information with tenant's feature of module synthesis, then calls workflow engine to create the flow instance for the tenant
Or execute the task of tenant request.
Beneficial effects of the present invention:
1, the loose coupling of support process construction and business service, developer need to only develop basic service logic, without paying close attention to stream
The relevant technologies of journey.
2, the operation flow for supporting tenant's layout more complicated, flow tasks can be web services, Java nodes, zone boundary
The human task etc. in face, the relevant flow variable read-write rule of task can be with on-demand customization.
3, tenant can increase flow, change or release flow, the change of quick response tenant's business demand on demand.
4, unified flow executes manager, automatic to obtain current process information, drives the wound of SaaS applied business flows
It builds and runs.
5, flow executes manager and uniformly obtains application state, realizes the flow variable access of operation flow.
6, flow data image module active obtaining and current tenant's information is injected, realizes the image of multi-tenant flow data
And isolation.
7, it is the shared use of multiple tenants to realize the same flow engine, and tenant's flow does not interfere with each other, makes full use of soft
Part resource.
Description of the drawings
Fig. 1 is a kind of device for supporting the on-demand customization of SaaS application flows and operation;
Wherein, 201, tenant perceives proxy module, 202, flow component described, 203, execute manager, 204, flow data reflects
As module, 205, original workflow engine, 2031, flow dispose component, 2032, flow create component, 2033, process flow operation
Component.
Specific implementation mode
The invention will be further described with embodiment below in conjunction with the accompanying drawings.
As shown in Figure 1, mould is acted on behalf of in a kind of device for supporting the on-demand customization of SaaS application flows and operation, including tenant's perception
Block 201, flow describe component 202, flow data image module 204, execute manager 203 and original workflow engine 205,
The execution manager 203 includes flow deployment component 2031, flow establishment component 2032 and process flow operation component 2033.
The tenant perceives proxy module 201 for obtaining the corresponding tenant's contextual information of current tenant(Context).
It includes workflow defining file that the flow, which describes component 202,(.jbdl.xml file)With workflow interfacing file
(WorkFlow_interface.xml);The workflow defining file uses jpdl as process description language, the work
Stream interface file uses xml as description language.Wherein, workflow interfacing file is read accordingly at runtime for workflow
Information, including the interface that is serviced in SaaS applications, key service name, key operation name and flow variable read rule.
The flow data image module 204 is according to tenant Context, by the relevant procedure information of tenant, role, user
It is identified, the image of implementation process data and isolation.
The execution manager 203 includes flow deployment component 2031, flow establishment component 2032 and process flow operation component
2033;The execution manager 203 is responsible for parsing subscription request message, and perceiving proxy module 201 with tenant interacts acquisition currently
The Context of tenant, and call flow data mapping module 204 is with the request of responding process(Flow deployment, flow instance
It creates and executes).
The flow disposes component 2031, perceives proxy module 201 with tenant first and interacts the current tenant of acquisition
Context, call flow data mapping module 204 receive that flow data image module 204 synthesizes, with tenant's feature
Flow description information;Then, the flow, and the isolation of implementation process are disposed.
The flow creates component 2032, and operation system is according to current tenant's information acquisition tenant Context, according to tenant
Context calls Metadata Service to obtain workflow interfacing information, whether meets work at this time according to the inspection of workflow interfacing information
Make the condition that stream example creates, flow variable is obtained if meeting and reads rule, and creates workflow instance, preserves tenant
Context, the basis as flow data image module.
The process flow operation component 2033 perceives proxy module 201 with tenant and interacts the current tenant of acquisition first
Context, call flow describe component 202, obtain the flow with tenant's feature of 204 synthesis of flow data image module
Information, organization flow parameter execute corresponding tenant's service;Secondly, tenant's service execution finishes, and call flow describes component
202, obtain the Service Source of change, write-back procedure information.
The original workflow engine 205 is responsible for interacting with execution manager, completes respective operations.
A method of it supporting the on-demand customization of SaaS application flows and operation, specifically comprises the following steps:
Step(1):Tenant perceives proxy module 201 according to tenant's essential information, accesses the database for preserving tenant's information, takes
Obtain the corresponding tenant Context information of current tenant;
Step(2):The workflow defining file that flow describes component 202 uses jpdl as process description language, and workflow connects
Mouth file uses xml as description language;The workflow interfacing file realizes that workflow reads corresponding information at runtime,
Interface, key service name, key operation name and the flow variable serviced in being applied including SaaS reads rule;
Step(3):Execute manager 203(EM)Subscription request message is parsed, current tenant's information is obtained, generation is perceived with tenant
The Context that the interaction of module 201 obtains current tenant is managed, and call flow data mapping module 204 makes the request of flow(Stream
Journey deployment, the establishment and execution of flow instance);
Step(4):Flow data image module 204(PDM)Realize the image of tenant's flow data:By Executive
Tenant's Context processing obtained by flow relevant information that Manager analysis tenant requests obtain, according to tenant
The relevant procedure information of tenant is marked with unique ID, the image of implementation process data and isolation by Context;
Step(5):Original workflow engine 205 is interacted with manager is executed, and completes respective operations.
The step(3)Include the following steps:
Step(3-1):Flow disposes component 2031:Flow deployment operation is completed, interacts and obtains with tenant's perception proxy module 201
Current tenant Context, call flow data mapping module 204, receive 204 synthesis of flow data image module, have
The flow description information of tenant's feature;And then workflow engine disposes the flow;Because flow is that tenant is peculiar, after deployment
Workflow realize isolation;
Step(3-2):Flow creates component 2032:Operation system is according to current tenant's information acquisition tenant Context, according to rent
Whether family Context calls Metadata Service to obtain workflow interfacing information, met at this time according to the inspection of workflow interfacing information
The condition that workflow instance creates obtains flow variable if meeting and reads rule, and creates workflow instance, preserves tenant
Context, the basis as flow data image module;
Step(3-3):Process flow operation component 2033:Process flow operation operation is completed, includes the establishment of flow instance, flow is held
Row;Proxy module 201 is perceived with tenant and interacts the current tenant Context of acquisition, and call flow data mapping module 204 receives
The procedure information with tenant's feature that flow data image module 204 synthesizes, then calling workflow engine establishment to be directed to should
The flow instance of tenant or the executing tenant request of the task.
Above-mentioned, although the foregoing specific embodiments of the present invention is described with reference to the accompanying drawings, not protects model to the present invention
The limitation enclosed, those skilled in the art should understand that, based on the technical solutions of the present invention, those skilled in the art
The various modifications or changes that can be made need not be made the creative labor still within protection scope of the present invention.
Claims (1)
1. a kind of device for supporting the on-demand customization of SaaS application flows and operation, characterized in that including tenant perceive proxy module,
Flow describes component, flow data image module, executes manager and original workflow engine, and the execution manager includes stream
Journey disposes component, flow creates component and process flow operation component;The tenant perceives proxy module for obtaining current tenant couple
The tenant's contextual information Context answered;The flow describes component for flow nodes information, control structure in operation flow
The description of information, relevant role and user, flow nodes and business service mapping relations;The flow data image module
For the Context according to tenant, the relevant procedure information of tenant, role, user are identified, implementation process data
Image and isolation;The execution manager perceives proxy module for parsing subscription request message, with tenant and interacts acquisition currently
The Context of tenant, and call flow data mapping module, with the request of responding process, the request of the flow includes flow
Deployment, the establishment and execution of flow instance;The flow deployment component, which is used to perceive proxy module with tenant, interacts acquisition currently
The Context of tenant, call flow data mapping module receive that flow data image module synthesizes, with tenant's feature
Flow description information;Dispose the flow, and the isolation of implementation process;The flow creates component and is used to create workflow instance,
Preserve the Context of tenant;The process flow operation component, which is used to perceive proxy module with tenant to interact, obtains current tenant's
Context, call flow describe component, obtain the procedure information with tenant's feature of flow data image module synthesis, group
Process parameter is knitted, corresponding tenant's service is executed;Tenant's service execution finishes, and call flow describes component, obtains the clothes of change
Business resource, write-back procedure information;Original workflow engine is interacted with manager is executed, and completes respective operations.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201810713926.3A CN108810164A (en) | 2018-06-29 | 2018-06-29 | Device supporting SaaS application flow customization and operation as required |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201810713926.3A CN108810164A (en) | 2018-06-29 | 2018-06-29 | Device supporting SaaS application flow customization and operation as required |
Publications (1)
Publication Number | Publication Date |
---|---|
CN108810164A true CN108810164A (en) | 2018-11-13 |
Family
ID=64073996
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
CN201810713926.3A Withdrawn CN108810164A (en) | 2018-06-29 | 2018-06-29 | Device supporting SaaS application flow customization and operation as required |
Country Status (1)
Country | Link |
---|---|
CN (1) | CN108810164A (en) |
Cited By (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN109656997A (en) * | 2018-12-14 | 2019-04-19 | 广东飞企互联科技股份有限公司 | Industry internet big data service platform system and method for servicing |
CN111045802A (en) * | 2019-11-22 | 2020-04-21 | 中国联合网络通信集团有限公司 | Redis cluster component scheduling system and method and platform device |
CN111192100A (en) * | 2018-11-14 | 2020-05-22 | 中兴通讯股份有限公司 | Workflow scheduling method, device and system |
CN112488655A (en) * | 2020-12-04 | 2021-03-12 | 杭州电子科技大学 | Business process dynamic customization system and method based on multi-tenant mode |
CN116974527A (en) * | 2023-09-18 | 2023-10-31 | 浩鲸云计算科技股份有限公司 | Pluggable page expansion method and system based on low-code front-end component |
-
2018
- 2018-06-29 CN CN201810713926.3A patent/CN108810164A/en not_active Withdrawn
Cited By (8)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN111192100A (en) * | 2018-11-14 | 2020-05-22 | 中兴通讯股份有限公司 | Workflow scheduling method, device and system |
WO2020098352A1 (en) * | 2018-11-14 | 2020-05-22 | 中兴通讯股份有限公司 | Workflow scheduling method, apparatus, and system |
CN109656997A (en) * | 2018-12-14 | 2019-04-19 | 广东飞企互联科技股份有限公司 | Industry internet big data service platform system and method for servicing |
CN111045802A (en) * | 2019-11-22 | 2020-04-21 | 中国联合网络通信集团有限公司 | Redis cluster component scheduling system and method and platform device |
CN111045802B (en) * | 2019-11-22 | 2024-01-26 | 中国联合网络通信集团有限公司 | Redis cluster component scheduling system and method and platform equipment |
CN112488655A (en) * | 2020-12-04 | 2021-03-12 | 杭州电子科技大学 | Business process dynamic customization system and method based on multi-tenant mode |
CN116974527A (en) * | 2023-09-18 | 2023-10-31 | 浩鲸云计算科技股份有限公司 | Pluggable page expansion method and system based on low-code front-end component |
CN116974527B (en) * | 2023-09-18 | 2023-12-15 | 浩鲸云计算科技股份有限公司 | Pluggable page expansion method and system based on low-code front-end component |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
CN108810164A (en) | Device supporting SaaS application flow customization and operation as required | |
CN103077024B (en) | A kind of device and method supporting the on-demand customization of SaaS application flow and operation | |
Wettinger et al. | Unified invocation of scripts and services for provisioning, deployment, and management of cloud applications based on TOSCA | |
Breitenbücher et al. | Integrated cloud application provisioning: interconnecting service-centric and script-centric management technologies | |
US20090125366A1 (en) | Method and system for dynamic adaptation of workflows | |
CN104317591A (en) | OSGi (open service gateway initiative)-based web interface frame system and web business processing method thereof | |
CN111488151B (en) | Page interaction method and device among Android modules | |
Daniel et al. | Distributed orchestration of user interfaces | |
KR20130037995A (en) | Method for configuring business logic of multi-tenant application | |
Lascu et al. | Automatic deployment of component-based applications | |
US20200366743A1 (en) | Megamodel driven process enactment | |
Brabra et al. | Toward higher-level abstractions based on state machine for cloud resources elasticity | |
Amor et al. | Malaca: A component and aspect-oriented agent architecture | |
US20070006121A1 (en) | Development activity recipe | |
CN110908767B (en) | Automatic parameter deployment method and device | |
Kyryk et al. | Infrastructure as Code and Microservices for Intent-Based Cloud Networking | |
Chelliah et al. | Architectural Patterns: Uncover essential patterns in the most indispensable realm of enterprise architecture | |
Haja et al. | Location, proximity, affinity–the key factors in FaaS | |
CN112418796B (en) | Sub-process task node activation method and device, electronic equipment and storage medium | |
CN113032004B (en) | Method, apparatus and program product for managing development jobs in a development environment | |
Schmid et al. | Domain-Oriented Customization of Service Platforms: Combining Product Line Engineering and Service-Oriented Computing. | |
US20090293064A1 (en) | Synchronizing shared resources in an order processing environment using a synchronization component | |
Kroiß | From backend to frontend: Case study on adopting Mmcro frontends from a single page ERP application monolith | |
Srinivasmurthy et al. | Web2exchange: A model-based service transformation and integration environment | |
Almeida et al. | A component-based adaptation approach for multi-cloud applications |
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 | ||
WW01 | Invention patent application withdrawn after publication |
Application publication date: 20181113 |
|
WW01 | Invention patent application withdrawn after publication |