CN104809537A - Workflow realization method used for business intelligent analysis platform - Google Patents
Workflow realization method used for business intelligent analysis platform Download PDFInfo
- Publication number
- CN104809537A CN104809537A CN201410042787.8A CN201410042787A CN104809537A CN 104809537 A CN104809537 A CN 104809537A CN 201410042787 A CN201410042787 A CN 201410042787A CN 104809537 A CN104809537 A CN 104809537A
- Authority
- CN
- China
- Prior art keywords
- module
- engine
- workflow
- bundle
- service
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Landscapes
- Stored Programmes (AREA)
Abstract
The invention provides a workflow realization method used for a business intelligent analysis platform. According to the similarity of business logic functions, a workflow engine in the business intelligent analysis platform is divided into a plurality of mutually-independent loose coupling data processing sub-engines and one main engine for workflow management so as to reduce coupling between data processing modules in a workflow and improve reusability of the workflow, wherein the main engine realizes management and scheduling of the workflow through jBPM. Meanwhile, with the reference of plug-in idea and package share idea in OSGi standard, each engine module is designed to be a plug-in piece according with the OSGi standard to keep independence of each module, so that hot plug and dynamic update of the module are realized, and expandability of the workflow is improved; and meanwhile, interaction between the modules is realized through a package sharing mechanism to enable the modules to cooperate cooperatively to realize a complete workflow.
Description
Technical field
The invention belongs to the sub-technology of business intelligence analysis platform, be mainly used in the realization of the workflow in business intelligence analysis platform.
Background technology
■ known technology
● business intelligence analysis platform
Business intelligence, English is Business Intelligence, is abbreviated as BI.Business intelligence is understood to that by data transformations existing in enterprise be knowledge usually, helps enterprise to make the instrument of wise business business decision.
The workflow of Intellectual analysis platform is made up of a series of data processing module, comprising: the parts such as data mining, ETL, on-line analytical processing.
●OSGi
OSGi technology is the dynamic modeling system towards Java.OSGi technology provides and allows application program to use refining, the reusable and standardization primitive of component construction that can cooperate.These assemblies can be assembled in an application and deployment.Assembly represents one group of independently functional module, it is a high cohesion, the system of low coupling, and what encapsulate function realizes details, only expose the interface that outside can be called, the access of external system to component detail isolated by this separate class loader of giving the credit to OSGi.
●jBPM
JBPM be one increase income, pure Java, multiple business procedure management (BPM) workflow engine performing flow process language of the support of lightweight, additionally provide development stream simultaneously, the stream that maps out the work, perform the function such as workflow, management work stream task, control work flows, provide technical support for enforcement engine controls multiple subtask.
■ prior art
In existing business analysis platform, for simple service logic, workflow is generally the invoked procedure of simple algorithm; For the service logic of complexity, existing workflow generally adopts the way of dividing and rule: by a complete flow process according to the similarity of professional ability, be divided into some modules, as: the report form showing module etc. of data preprocessing module, data.The processing sequence of each module according to data be simply connected in series, the output of a upper module is as the input of next module, and module collaborate realizes a complete workflow.
As can be seen from the above technical solutions, in the workflow of existing business analysis platform, there are following two large shortcomings:
1. the coupling between data processing module is higher, and data handling procedure is only suitable for special scenes or particular data.When data change or scene changes, need to do larger change to enforcement engine, overlapping development and test, workload is large.
2., when adding new sub-capacity operation flow process, need to revise whole total working flow process, again develop, Capacity extension is poor.
Summary of the invention
The shortcoming that the present invention be directed to workflow existence in existing business intelligence platform proposes.The present invention, by reducing the coupling between data processing module, makes the dependence of workflow to scene little, to strengthen the versatility of workflow in different scene.Adopt the present invention can strengthen the extensibility of workflow, realize dynamic interpolation and the unloading of data processing module.Fashionable when there being new data-handling capacity to add, only need add corresponding sub-process module and self statement; When old module does not re-use, only module need be unloaded, and not affect the normal operation of other modules.
The present invention is achieved through the following technical solutions: according to the similarity of logic of business functions, workflow engine in business intelligence platform is split, form multiple separate sub-engine modules of loose coupling data processing and a leading engine module for management process, described leading engine module realizes management to workflow and scheduling by jBPM, described sub-engine modules is designed to meet the plug-in unit of OSGi specification to keep the independence of module, achieve the hot plug of module and dynamically update, realize between module by bag shared mechanism mutual, each module cooperative cooperation is made to realize a complete workflow.
Preferred version of the present invention is: described leading engine module is an independently bundle, the method bag of jBPM is added in bundle engineering, the API that so just can call jBPM provides carries out the parsing and execution etc. of flow process, make leading engine module have management and perform the ability of flow process, main flow administration module is also designed with communications portion, obtain flow definition by network or database or other modes, interface section is used for carrying out alternately with other sub-process module bundle.
Another preferred version of the present invention is: described sub-process module is an independently bundle, in OSGi specification, service centre is that all bundle can the class of registration service wherein, after registration service, as long as the bundle registering this service is in state of activation, other bundle all can use this service, by the bag shared mechanism of OSGI framework, the interface that leading engine exposes is introduced in sub-engine, and realize this interface by the implement mode of java, each sub-process is allowed to realize this interface, and the service of oneself is registered to above-mentioned OSGi service centre in the mode of interface name, other bundle can use this service to process data, achieve and service is separated with realization.
Specific implementation of the present invention comprises following job step:
1. be integrated with the design of the leading engine module of jBPM.
In OSGi specification, independently module will be called bundle.Bundle represents one group of independently functional module, and it is a high cohesion, the system of low coupling, and what encapsulate function realizes details, only exposes the interface that outside can be called.In the present invention main flow administration module is designed to an independently bundle, the method bag of jBPM is added in bundle engineering, the API that so just can call jBPM provides carries out the parsing of flow process and execution etc., makes leading engine module have management and performs the ability of flow process.Meanwhile, primary module is also designed with communications portion, can obtain flow definition, support various ways by network or database or other modes; Interface section is then for carrying out with other sub-process module bundle alternately.The design of this module is divided into the following steps again:
1) design of leading engine module bundle: first realize start and the stop method in bundle in Activator class, is respectively the method called when bundle starts and stops; Then the information such as the title of bundle and version specified by the manifest file revising bundle.
2) jBPM's is integrated: wrapped by the engineering jar of jBPM, and join in the dependence of the leading engine bundle just now designed, the flow processing API that can call jBPM manages flow process.
3) design of interface: define an engineservice interface, and the run method that definition one is empty wherein, joined in the derivation bag of bundle by the bag comprising engineservice interface, interface is exposed can be called by other bundle and realize.
4) design of communications portion: by servlet from Network Capture flow definition, or obtain flow definition by JDBC from database.
2. the design of data processing sub-process module.
Sub-process module is the real module possessing data-handling capacity, and each sub-process module possesses different data-handling capacities.Each sub-process module is designed to an independently bundle respectively.
In OSGi specification, service centre is that all bundle can the class of registration service wherein, and after registration service, as long as the bundle registering this service is in state of activation, other bundle all can use this service.Invention defines a unified interface, each sub-process is allowed to realize this interface, and the service of oneself is registered to above-mentioned OSGi service centre in the mode of interface name, other bundle can use this service to process data, achieve and service are separated with realization.When the newly-increased sub-process of needs, be also designed to a bundle, and the interface of definition before realizing, by service registry to service centre.Achieve the dynamic interpolation of ability sub-process, improve extensibility.The design of data processing sub-process module is divided into following a few part:
1) design of sub-engine modules bundle: identical with leading engine bundle, also will realize start and stop class and add and amendment manifest file.
2) registration of serving: the registerService API by OSGi framework in the start method in Activator class carries out service registry, register name is the interface class title of leading engine.Like this can by service registry when bundle starts, namely other bundle can be called by getservice.
3) realization of serving: namely realize the EngineService interface defined in leading engine bundle.The realization of service is the specific implementation of the data-handling capacity that sub-engine provides.By the bag shared mechanism of OSGI framework, introduce the interface that leading engine exposes in sub-engine, and realize this interface by the implement mode of java, the service be registered in like this in service centre has just had corresponding specific implementation.
3. use jBPM to come scheduling and the execution of manage workflow.
In business platform, the mode of metadata is adopted to describe the definition of flow process.Have the description to the various information of flow process and definition in metadata, comprise the node of flow process, input that internodal redirect order, node perform and output etc., be stored in the metadata defined file of XML format.Metadata definition meets jPDL language format, and the flow definition that jPDL and jBPM uses and descriptive language, the API that can call jBPM carries out resolving and running.Operationally flow definition is loaded into internal memory, in internal memory, records complete srvice instance and the environmental variance of implementation, and complete all operations and implementation.
Utilize the point spread mechanism of jBPM, realize the service of calling sub-process module in flow performing process.Because sub-engine node is different from the ordinary node of jBPM, the present invention extends the node type in jPDL, has rewritten the metadata analysis mode of sub-engine node, has added parameter field and type field.Parameter field defines input and the output of sub-engine node, type field is then for representing different sub-engine nodes, according to the value of type field, leading engine is selected to start corresponding sub-process bundle, sub-process bundle is by service registry in start-up course, and main flow bundle can obtain service to carry out the process of data.The management of a flow process is divided into following a few part:
1) parsing of flow definition: flow definition meets jPDL form, flow definition is resolved to flow process class ProcessDefinition class by the API that directly calling jBPM provides, and is loaded into product process example ProcessInstance in internal memory and performs.
2) execution of flow process and scheduling: the signal method calling jBPM performs flow process, by connect and redirect carrys out the operation order of scheduling flow between each node.
3) the calling of sub-engine: the node type of expansion jPDL, realizes User-defined Node.Because the field of User-defined Node is different from ordinary node, read and the write method also needing rewrite node to resolve, these two modes are methods of the metadata for parse node in jBPM, utilize the extends mechanism of java to expand.When flow process jumps to the User-defined Node of expansion, the value of parameter and type field can be parsed, start corresponding sub-engine bundle, and the parameter needed for being performed by sub-engine is imported into, finally can obtain in OSGi service centre the service that sub-engine bundle provides.
Accompanying drawing explanation
Fig. 1 is the design structure diagram of the leading engine module in one embodiment of the invention
Fig. 2 is the design structure diagram of sub-engine modules in one embodiment of the invention and interface
Fig. 3 is the complete implementation schematic diagram of a workflow in one embodiment of the invention
Fig. 4 is point process schematic of the workflow XM in one embodiment of the invention
Fig. 5 is the bundle schematic diagram of OSGi framework registration in one embodiment of the invention
Fig. 6 is the report engine execution result exploded view in one embodiment of the invention
Embodiment
Below in conjunction with accompanying drawing, the embodiment of the present invention is elaborated: the present embodiment is lower premised on technical solution of the present invention to be implemented, and give detailed embodiment and specific operation process, but protection scope of the present invention is not limited to following embodiment.
This example is an application scenarios of platform, temperature applications.Scene is, according to the rock gas sales volume in each month over the years, calculate the relation of rock gas sales volume and temperature, thus doping the sales volume situation that later rock gas divides in not same month, the Work flow metadata of this application is defined as: the sub-engine node of start node->ETL engine node->Report-> end node.
Implement the job step of scene to comprise: during the design of leading engine, the design of sub-engine, the Equinox that engine bundle added to OSGi framework realize, point spread, process of analysis, the execution start node of leading engine, perform ETL node, perform Report node, perform end node, return execution result.
The design of step one leading engine.
(1) be first the design of leading engine bundle.The framework of leading engine module is as shown in accompanying drawing l, if the java IDE for developing supports newly-built plug-in unit engineering, then can a direct newly-built OSGi plug-in unit engineering, and at this moment automatically can generate Activator class and manifest file.If common java engineering can only be created, then need manually to add activator appliance class Activator and manifest file.Newly-built META-INF file in engineering, wherein newly-built MANIFEST.MF file, need in file to comprise with F information:
// rear description corresponding to attribute, then the activator appliance class Activator of bundle is realized, Activator class comprises start and stop method, because leading engine has communications portion, so need to inject servlet service in the start method when bundle starts in OSGi container, there is httpservice for registering web services in the service bag of OSGi, comprising servlet; Service is cancelled in stop method.This completes the design of leading engine module bundle form.
(2) jBPM's is integrated.Because jBPM is the Workflow Management System of a lightweight, in the dependence directly in leading engine engineering, add the method bag of jBPM.Call the flow metadata definition of the parseXmlInputStream method parsing XML format of jBPM, and generate processdefinition class, regeneration flow instance processinstance class is loaded in internal memory, calls signal method and performs.
(3) design of interface.Defining interface Engineservice and method run to be achieved.In the Export-Package of manifest, add the package at interface place, interface can be exposed and realize for other bundle.
(4) design of communications portion.In start method, register servlet service before, directly obtain flow definition information by doGet and the doPost method of httpServlet alternately with platform herein.If obtain flow definition from database, directly use JDBC, obtained by sql statement.
The design of the sub-engine of step 2.Comprise two sub-engines in this enforcement use-case, ETL engine and the sub-engine of Report, the function of ETL engine for carry out pre-service to data, as imported data, line-break cleaning, statistics, field type conversion etc.; The function of the sub-engine of Report is that input data are carried out visual presentation by the form of form.To ETL engine and the sub-engine of Report be joined in workflow, need its code to transform, transform the bundle mode of OSGi as, below for ETL engine.
(1) first, ETL engine is transform as a plug-in unit engineering, this process is similar with the bundle form design process of leading engine, repeats no more.The design architecture of sub-engine and interface as shown in Figure 2, notes adding in the Import-Package of manifest the interface that leading engine exposes, i.e. org.tseg.engine.service.
(2) then, realize concrete service, namely realize the interface that leading engine exposes.By Interface realization and the implements mode of java grammer, realize the run method in interface, call concrete ETL ability algorithm in run method and carry out data processing, during the result processed should define with metadata to return results type consistent.
The transformation of the sub-engine of Report and the similar of ETL, repeat no more herein.
Engine adds in the Equinox realization of OSGi framework by step 3.First in order line, start Equinox service, pass through-jar org.eclipse.osgi (Hou Jia version number) .jar order and start.After starting service, by ordering the fullpath of the catalogue at install+bundle place, as:
Install D: //bundles/et1_1.0.0.201306211600.jar, the bundle needed for being performed by engine installs successively, checks bundle installation situation after installation by order ss.After bundle installation in this enforcement use-case as shown in Figure 5.
The point spread of step 4 leading engine.After completing the design of sub-engine, need to carry out point spread at leading engine.
First revise the node.types.xml file of jBPM, add wherein the new node type service-node that adds and service-node corresponding realize class, as follows:
<node-type element＝″service-node″class＝″org.tseg.engine.impl.serviceNode″/>
That then revises node realizes class, node class needs the defined Node class of extends jBPM, wherein comprise heavy read, write and execute method, because the metadata field of definition ordinary node of User-defined Node is different, rewrite the metadata description that read and write method reads in node, comprise parameter and type field, be respectively the execution desired parameters of sub-engine and sub-engine type.Execute method is the manner of execution of node, call in execute method sub-engine service and obtain return results the expansion that can complete node.
Step is afterwards the entire flow step of workflow, and the complete implementation of flow process as shown in Figure 3.
Step 5 process of analysis.When starting most, first leading engine starts, and the communication module in leading engine is first mutual with business intelligence platform.Flow definition meta data file is obtained by servlet and database.Leading engine module calls jBPM API after obtaining the definition of this metadata resolves product process example and starts to perform, and the interface module of leading engine is own simultaneously shares to interface in OSGi framework.
Step 6 performs start node.The metadata definition fragment of start node is as follows:
<start-state name=" beginning " gx=" 192 " gy=" 177 " >
<transition name=" beginning to ETL " to=" ETL "/>
</start-state>
Wherein namely start-state represents start node, and name and some other label list understand some attribute informations of node.Flow performing is using start node as entrance.First enter start node, if there are some to need to start to perform in flow process the data or parameter that just need to input, can introduce at start node.In this application example, without the need to the data pre-entered, therefore start node undefined operation.Flow process, according to the description of the transition label of start node, jumps to next node, i.e. ETL node.
Step 7 performs ETL engine node.The metadata definition fragment of ETL node is as follows:
Type field is sub-engine indications, type is " ETL " herein, corresponding start ETL engine, the input field in the parameter label in metadata definition for pass to sub-engine perform needed for parameter, output field is the result name that returns of sub-engine and data type.There is provided service registry by oneself during sub-engine start, data processing is carried out in the leading engine service of calling, and the data processing in this application scenarios comprises importing random length, line-break cleaning and statistics etc.After data handling procedure completes, in this application scenarios, result returns and writes in datapath variable, and the result returned is character string type, for generating the absolute path of destination file.
Step 8 performs the sub-engine node of Report.The metadata definition fragment of Report node is as follows:
The metadata structure of sub-engine is similar, type is " Report " herein, the sub-engine of corresponding startup Report, start the sub-engine of Report and registration service, data processing is carried out in the leading engine service of calling, Report node in this application scenarios processes the data file under dataPath path, and generating report forms form is shown.After data handling procedure completes, result returns and writes in result variable, and the result returned is binary type, for generating the binary representation of destination file.
Step 9 performs end node.The metadata definition fragment of end node is as follows:
<end-state name=" end " gx=" 455 " gy=" 436 "/>
Flow performing terminates automatically to end node, the flow process context of preservation and some status informations is deleted from internal memory.
Step 6 is the implementation of procedure Procedure example to step 9, and the implementation of a flow instance as shown in Figure 4.
Step 10 returns execution result.Result, after flow performing completes, is passed to platform by http message mode by leading engine.
After returning execution result, whole workflow terminates.Execution result can be shown in front-end platform, and result as shown in Figure 6.
From the transformation of sub-engine with dynamically add last flow performing to and complete result and return, fully illustrate the high independence of each module of workflow, and there is very strong extensibility.
Claims (3)
1. the workflow implementation method for business intelligence analysis platform, it is characterized in that: the workflow engine in business intelligence platform is split, form multiple separate sub-engine modules of loose coupling data processing and a leading engine module for management process, described leading engine module realizes management to workflow and scheduling by jBPM, described sub-engine modules is designed to meet the plug-in unit of OSGi specification to keep the independence of module, achieve the hot plug of module and dynamically update, realize between module by bag shared mechanism mutual, each module cooperative cooperation is made to realize a complete workflow.
2. a kind of workflow implementation method for business intelligence analysis platform as claimed in claim 1, it is characterized in that described leading engine module is an independently bundle, the method bag of jBPM is added in bundle engineering, the API that so just can call jBPM provides carries out the parsing and execution etc. of flow process, make leading engine module have management and perform the ability of flow process, main flow administration module is also designed with communications portion, obtain flow definition by network or database or other modes, interface section is used for carrying out alternately with other sub-process module bundle.
3. a kind of workflow implementation method for business intelligence analysis platform as claimed in claim 1, it is characterized in that described sub-process module is an independently bundle, in OSGi specification, service centre is that all bundle can the class of registration service wherein, after registration service, as long as the bundle registering this service is in state of activation, other bundle all can use this service, by the bag shared mechanism of OSGI framework, the interface that leading engine exposes is introduced in sub-engine, and realize this interface by the implement mode of java, each sub-process is allowed to realize this interface, and the service of oneself is registered to above-mentioned OSGi service centre in the mode of interface name, other bundle can use this service to process data, achieve and service is separated with realization.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201410042787.8A CN104809537A (en) | 2014-01-27 | 2014-01-27 | Workflow realization method used for business intelligent analysis platform |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201410042787.8A CN104809537A (en) | 2014-01-27 | 2014-01-27 | Workflow realization method used for business intelligent analysis platform |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN104809537A true CN104809537A (en) | 2015-07-29 |
Family
ID=53694346
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201410042787.8A Pending CN104809537A (en) | 2014-01-27 | 2014-01-27 | Workflow realization method used for business intelligent analysis platform |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN104809537A (en) |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107729305A (en) * | 2017-10-10 | 2018-02-23 | 中国航发控制系统研究所 | Conference materials automatic generation method based on database and front end Display Technique |
| CN110839079A (en) * | 2019-11-15 | 2020-02-25 | 深圳前海微众银行股份有限公司 | BI node execution method, device, equipment and medium in workflow system |
| CN113568683A (en) * | 2021-08-05 | 2021-10-29 | 京东科技控股股份有限公司 | Method and device for dynamically expanding asset data stream processing service assembly |
Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103164476A (en) * | 2011-12-16 | 2013-06-19 | 中国移动通信集团公司 | Execution method and execution device of applying metadata to describe files in business intelligence (BI) |
-
2014
- 2014-01-27 CN CN201410042787.8A patent/CN104809537A/en active Pending
Patent Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103164476A (en) * | 2011-12-16 | 2013-06-19 | 中国移动通信集团公司 | Execution method and execution device of applying metadata to describe files in business intelligence (BI) |
Non-Patent Citations (3)
| Title |
|---|
| 吕璐: "BI PAAS中执行引擎的研究和实现", 《中国优秀硕士学位论文全文数据库信息科技辑》 * |
| 江志雄 等: "元数据驱动的BI-PAAS的设计与实现", 《计算机工程与应用》 * |
| 江志雄 等: "基于并行机制的商务智能系统BI-PaaS", 《计算机应用》 * |
Cited By (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107729305A (en) * | 2017-10-10 | 2018-02-23 | 中国航发控制系统研究所 | Conference materials automatic generation method based on database and front end Display Technique |
| CN107729305B (en) * | 2017-10-10 | 2020-10-09 | 中国航发控制系统研究所 | Automatic conference material generation method based on database and front-end display technology |
| CN110839079A (en) * | 2019-11-15 | 2020-02-25 | 深圳前海微众银行股份有限公司 | BI node execution method, device, equipment and medium in workflow system |
| CN110839079B (en) * | 2019-11-15 | 2022-02-08 | 深圳前海微众银行股份有限公司 | BI node execution method, device, equipment and medium in workflow system |
| CN113568683A (en) * | 2021-08-05 | 2021-10-29 | 京东科技控股股份有限公司 | Method and device for dynamically expanding asset data stream processing service assembly |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US8560372B2 (en) | Compiling workflows into instructions for a state correlation engine | |
| CN107038242B (en) | Block chain-oriented global intelligent contract service data analysis method | |
| US8374987B2 (en) | Stateful, continuous evaluation of rules by a state correlation engine | |
| CN1866283B (en) | System and method for implementing regular system triggering | |
| CN108876619B (en) | Processing method, device, equipment and medium based on block chain intelligent contract | |
| US20150121155A1 (en) | Performing customized deployment scenarios in shared environments | |
| CN106648682B (en) | A kind of dynamic data general framework of embedded system exploitation | |
| CN103180826A (en) | Managing data set objects in a dataflow graph that represents a computer program | |
| CN109582289B (en) | Method, system, storage medium and processor for processing rule flow in rule engine | |
| CN112860260B (en) | Web-based cross-platform application construction tool and method in college scene | |
| CN112463211A (en) | System architecture transformation method compatible with multiple development architectures and system architecture | |
| CN107809332A (en) | Compound interface configures and compound interface call method, device | |
| CN106603583A (en) | Micro-service network building method | |
| CN110825457A (en) | Method and device for processing business in business engine, storage medium and electronic equipment | |
| US20080115135A1 (en) | Supporting ETL Processing in BPEL-Based Processes | |
| US8234303B2 (en) | Single parse, diagram-assisted import into a unified modeling language based meta-model | |
| CN104809537A (en) | Workflow realization method used for business intelligent analysis platform | |
| CN115759955A (en) | Business process execution engine based on block chain | |
| US8874622B2 (en) | Flexible order of authoring for data integration solutions | |
| Rademacher et al. | Specific model-driven microservice development with interlinked modeling languages | |
| CN102193802A (en) | Method for converting models with model subsets of same base class structure | |
| CN103455337A (en) | Method for using dynamic library under Android development environment | |
| Zhao et al. | The design of E-commerce system architecture based on Struts2, Spring and Hibernate | |
| CN102385516B (en) | Method for designing reconfigurable radio frequency identification (RFID) middleware based on cloud server | |
| US8522198B2 (en) | Model-operative pattern representation harvesting using an automated exemplar-directed approach |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| WD01 | Invention patent application deemed withdrawn after publication | ||
| WD01 | Invention patent application deemed withdrawn after publication |
Application publication date: 20150729 |