CN101630247A - BPEL-based data exchange process treatment method and treatment system - Google Patents
BPEL-based data exchange process treatment method and treatment system Download PDFInfo
- Publication number
- CN101630247A CN101630247A CN200910013199A CN200910013199A CN101630247A CN 101630247 A CN101630247 A CN 101630247A CN 200910013199 A CN200910013199 A CN 200910013199A CN 200910013199 A CN200910013199 A CN 200910013199A CN 101630247 A CN101630247 A CN 101630247A
- Authority
- CN
- China
- Prior art keywords
- bpel
- submodule
- data
- task
- monitoring
- 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
Images
Landscapes
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
The invention relates to a BPEL-based data exchange process treatment method, comprising the following steps: step 11, establishing task instances and constructing parameters required by BPEL instances; step12, establishing the BPEL instances; step 13, executing the data exchange process according to a predetermined BPEL model; step14, executing the BPEL instances and judging whether the execution is completed, if no, returning to the step 13, if yes, completing the BPEL instances and the task instances. The invention also relates to a BPEL-based data exchange process treatment system, a BPEL-based data exchange breaking point continuous transfer treatment method and treatment system and a BPEL-based data exchange dynamic monitoring treatment method and system. The invention has good function expandability; the deployment strategy is more flexible; component services can be independently deployed and the degree of dependence on the special servers which operate the entire data treatment flow is reduced.
Description
Technical field
The present invention relates to the data integration field, particularly relate to a kind of flow process, breakpoint transmission of the data exchange process based on BPEL, the disposal route and the disposal system of dynamic monitoring.
Background technology
Enterprise for realize data resource share with the data of integrating the separate sources that often needs to be distributed among different regions, the network domains, form logically or physically integrated, this demand has promoted the development of data integration technology and product.At present, mainly adopt the integrated and integrated two class integration modes of physics data of logic of data in the data integration field, the logic of data is integrated, and what be meant is that mode by the construction logic view will distribute, heterogeneous data source combines virtually, the for example federal mode data integration of data, corresponding product has IBM Wii, Sybase DI etc.; The physics of data is integrated to be meant by making up data exchange process, the mode that distributes, data in the heterogeneous data source are moved to intended target with need ground is realized data integration, shared, for example data center, the data integration of data warehouse mode, corresponding product has Oracle DataExchange, OWB, Talend etc.
Data exchange process mainly is meant to realizing each dispersion in the enterprise, integrated and the data interaction, the treatment scheme that comprise steps such as extraction, transmission, loading that make up of the physics of data among the different kinds of information system.For can realize distributing, the interconnection and interflow of data between the heterogeneous data source, provide timely, accurate, consistent data to enterprise information system, data exchange process need solve following key issue: the cross-domain transmission of data, the route of data, increment data capturing, conversion between the different data format, data cleansing and data load etc.
Available data exchange process treatment technology can be divided into message based process processing and handle two kinds based on the process of ETTL engine by execution and monitor mode.
1, message based process is handled.
This mode is a flow process control core with particular message middleware or ESB, based on configuration mode definition of data exchange process, with mode transfer process status information, flow process control information and the business datum of message route.Finish data flow control and monitoring by transmission of messages and processing capacity that message-oriented middleware provides.Data pick-up, conversion, loading rely on ETL (Extraction, Transformation Loading) engine and finish.
But, adopt the data exchange system of this mode to need ETL engine and transmission of messages assembly close-coupled, so function expansion difficulty.Mode based on the message exchange service data need be changed repeatedly data layout.Such as, need earlier the data that extract to be converted to the XML formatted data and attach on message and send.Therefore under the bigger situation of single exchange data volume, system performance is descended fast.
2, handle based on the process of ETTL engine:
ETTL (Extraction, Transformation, Transportation, and Loading) engine is a data flow Control Engine of having expanded data-transformation facility on the ETL engine.This mode is a flow process control core with the ETTL engine, utilizes ad hoc structure model definition data exchange process, and the ETTL engine is based on the execution of model definition control data exchange process.The data pipe of business datum through making up between source end and destination data source handled, transmission.The ETTL engine directly is responsible for the monitoring of data flow.
Because needing the ETTL engine to resolve based on the predefined data exchange model, this mode carries out or generating code compiling execution, systemic-function expansion (such as the support of expansion to the specific type of data source) not only needs to provide the functional module of correspondence, also need to expand the ETTL engine and realize, face function expansion situation of difficult equally.In addition, data exchange process model definition and deployment all need be finished based on the exploitation deployment tool of specialty, not only need the user to possess data integration domain-specific knowledge but also process relative complex.
As seen, available data exchange process processing mode can solve most of exchanges data problems, but stride multiple domain facing, striding physical isolation or gateway isolates, when data exchange process makes up under the complex data environment that back end is more and network environment is relatively poor, have deficiencies such as system is difficult to be expanded, and deployment way underaction and flow definition are convenient inadequately.
Summary of the invention
Technical matters to be solved by this invention provides based on the procedure processing method of BPEL exchanges data and disposal system, and this method and system has easy expansion, disposes characteristics such as flexible.
The present invention also provides a kind of breakpoint transmission disposal route and disposal system based on the BPEL exchanges data, and this method and system has easy expansion, disposes characteristics such as flexible.
The present invention also provides a kind of dynamic monitoring disposal route and disposal system based on the BPEL exchanges data, and this method and system has easy expansion, disposes characteristics such as flexible.
A kind of procedure processing method based on the BPEL exchanges data of the present invention comprises;
Preferably, making up BPEL example desired parameters is specially:
Required start-up parameter data in step 111, the structure exchange flow process;
Preferably, carrying out the BPEL example is specially:
Structural parameters in step 141, the parsing BPEL example, the local definition structure parameter group of formation component;
Preferably, described local definition structure parameter group is a multiway tree shape structure, the root node of multiway tree shape structure is DE Params, and non-root node is parameter group Group, and each parameter group Group comprises base attribute, extended attribute Property tabulation and child node Group.
A kind of process disposal system of the present invention based on the BPEL exchanges data, comprise task engine module, BPEL engine modules, reach the Component service module, described task engine module comprises task instances establishment submodule, described BPEL engine modules comprises that the BPEL example is created submodule and execution finishes to judge submodule, and described Component service module comprises the assembly implementation sub-module;
Described task instances is created submodule, is used for the creation task example, makes up BPEL example desired parameters;
Described BPEL example is created submodule, is used to create the BPEL example, carries out data exchange current journey by predetermined BPEL model;
Described assembly implementation sub-module is used to carry out the BPEL example;
Described execution finishes to judge submodule, is used to judge whether carry out and finishes, and as not, starts described BPEL example and creates submodule; In this way, finish BPEL example and task instances.
Preferably, described task instances establishment submodule comprises start-up parameter construction unit and SOAP parameter start unit;
Described start-up parameter construction unit is used for making up the required start-up parameter data of exchange flow process;
Described SOAP parameter start unit is used to define the BPEL relevant episode, creates the BPEL flow process and starts required soap message.
Preferably, described assembly implementation sub-module comprises structural parameters group generation unit and carries out correct judging unit:
Structural parameters group generation unit is used for resolving the structural parameters of BPEL example, the local definition structure parameter group of formation component;
Carry out correct judging unit, be used for carrying out the BPEL example, judge whether correct execution, in this way, return execution journal by parameter group; As not, return abnormal information.
A kind of breakpoint transmission disposal route based on the BPEL exchanges data of the present invention comprises:
Step 81, creation task example make up BPEL example desired parameters;
Step 82, establishment BPEL example;
Step 83, carry out data exchange process by predetermined BPEL model;
Structural parameters in step 84, the parsing BPEL example, the local definition structure parameter group of formation component;
Step 85, judge whether parameter group comprises breakpoint, in this way, resolve breakpoint information, start assembly recovers to carry out; As not, carry out the BPEL example.
Preferably, making up BPEL example desired parameters is specially:
Required start-up parameter data in step 811, the structure exchange flow process;
Step 812, definition BPEL relevant episode are created the BPEL flow process and are started required soap message.
Preferably, carrying out the BPEL example is specially:
Step 842, carry out the BPEL example, judge whether correct execution, in this way, return execution journal by parameter group; As not, return abnormal information.
A kind of breakpoint transmission disposal system of the present invention based on the BPEL exchanges data, comprise task engine module, BPEL engine modules, reach the Component service module, described task engine module comprises task instances establishment submodule, described BPEL engine modules comprises BPEL example establishment submodule and BPEL model submodule, and described Component service module comprises that the structural parameters group generates submodule and breakpoint is judged submodule;
Described task instances is created submodule, is used for the creation task example, makes up BPEL example desired parameters;
Described BPEL example is created submodule, is used to create the BPEL example;
Described BPEL model submodule is used for carrying out data exchange current journey by predetermined BPEL model;
Described structural parameters group generates submodule, is used for resolving the structural parameters of BPEL example, the local definition structure parameter group of formation component;
Described breakpoint is judged submodule, is used to judge whether parameter group comprises breakpoint, in this way, resolves breakpoint information, and start assembly recovers to carry out; As not, carry out the BPEL example.
Preferably, described task instances establishment submodule comprises start-up parameter construction unit and SOAP parameter start unit;
Described start-up parameter construction unit is used for making up the required start-up parameter data of exchange flow process;
Described SOAP parameter start unit is used to define the BPEL relevant episode, creates the BPEL flow process and starts required soap message.
Preferably, described BPEL engine modules also comprises carries out the correct submodule of judging, is used for carrying out the BPEL example by parameter group, judges whether correct execution, in this way, returns execution journal; As not, return abnormal information.
A kind of dynamic monitoring disposal route based on the BPEL exchanges data of the present invention comprises:
Step 141, obtain the status data of current task engine, be saved in the monitoring return data object, implement monitoring;
Preferably, the status data that obtains the current task engine is specially:
Step S1411, search the task engine of current application from JMX Server;
Step S1412, obtain the task engine status data and return monitoring return data object.
Preferably, the status data that obtains the current task example is specially:
Step S1421, search the task instances of corresponding current monitoring flow process from JMX Server;
Step S1422, obtain the task instances status data and return monitoring return data object.
Preferably, the securing component status data of serving current execution is specially:
Step S1431, search the current serviced component example that is moving from JMX Server based on example ID;
Step S1432, securing component service current status data return monitoring return data object.
A kind of dynamic monitoring disposal system of the present invention based on the BPEL exchanges data, comprise: system monitoring module, task engine module, and Component service module, described system monitoring module comprises monitoring return data object preservation submodule and supervisor console submodule, described task engine module comprises task engine state data acquisition submodule and task instances state data acquisition submodule, and described serviced component module comprises Component service state data acquisition submodule;
Described task engine state data acquisition submodule is used to obtain the status data of current task engine, sends to described monitoring return data object and preserves submodule;
Described task instances state data acquisition submodule is used to obtain the status data of current task example, sends to described monitoring return data object and preserves submodule;
Described Component service state data acquisition submodule is used for the status data that securing component is served current execution, sends to described monitoring return data object and preserves submodule;
Described monitoring return data object is preserved submodule, is used to preserve the data that receive and arrives monitoring return data object;
Described supervisor console submodule is used for monitoring return data object is implemented monitoring.
Preferably, described system monitoring module comprises that also task engine searches submodule, is used for searching from JMXServer the task engine of current application, sends to described task engine state data acquisition submodule.
Preferably, described system monitoring module comprises that also task instances searches submodule, is used for searching from JMXServer the task instances of corresponding current monitoring flow process, sends to described task instances state data acquisition submodule.
Preferably, described system monitoring module comprises that also the serviced component example searches submodule, is used for searching the current serviced component example that is moving based on example ID from JMX Server, sends to Component service state data acquisition submodule.
Compared with prior art, the present invention has the following advantages:
The present invention has improved the extensibility of systemic-function on the advantages characteristic basis that has kept available data exchange processing mode, a kind of mode that defines, revises data exchange process easily is provided.Deployment strategy is more flexible, and Component service can independently be disposed, and has reduced the degree of dependence to the private server of moving whole flow chart of data processing.
Description of drawings
In order to be illustrated more clearly in the technical scheme among the utility model embodiment, to do to introduce simply to the accompanying drawing of required use among prior art and the embodiment below, apparently, accompanying drawing in describing below only is embodiment more of the present utility model, for those of ordinary skills, under the prerequisite of not paying creative work, can also obtain other accompanying drawing according to these accompanying drawings.
Fig. 1 a is the data exchange process disposal system synoptic diagram that the present invention is based on BPEL;
Fig. 1 b is a multiway tree structural representation of the present invention;
Fig. 2 is the procedure processing method process flow diagram that the present invention is based on the BPEL exchanges data;
Fig. 3 is the process disposal system synoptic diagram that the present invention is based on the BPEL exchanges data;
Fig. 4 is the breakpoint transmission process flow figure that the present invention is based on the BPEL exchanges data;
Fig. 5 is the breakpoint transmission disposal system synoptic diagram that the present invention is based on the BPEL exchanges data;
Fig. 6 is the dynamic monitoring process flow figure that the present invention is based on the BPEL exchanges data;
Fig. 7 is the dynamic monitoring disposal system synoptic diagram that the present invention is based on the BPEL exchanges data;
Fig. 8 is a data exchange processing schematic flow sheet of the present invention;
Fig. 9 is another synoptic diagram of data exchange processing flow process of the present invention.
Embodiment
For above-mentioned purpose of the present invention, feature and advantage can be become apparent more, the present invention is further detailed explanation below in conjunction with the drawings and specific embodiments.
Core design thought of the present invention is based on BPEL (Business Process Execution Language) definition of data exchange process, data procedures is handled and monitor mode is a core with the BPEL engine, adopt and explain that carrying out predefine is the exchanges data BPEL procedural model of XML form, collaborative call exchanges data Component service mode and move, adopt this mode to make that not only the system flow control and management is powerful, and stride multiple domain facing, striding physical isolation or gateway isolates, when data exchange process makes up under the complex data environment that back end is more and network environment is relatively poor, system easily expands, and deployment way is flexible and flow definition is convenient.
BPEL is that a kind of XML Web Services coordinates control (Orchestration) language, and by IBM, BEA and Microsoft united customization in 2002.A typical BPEL treatment scheme is to handle the XML document that the graphical edit tool of needs utilization is created out by business analysis personnel (being not the software developer) according to detailed process.The BPEL defined file can be explained and carry out that the BPEL engine can trigger processing procedure by Web Services interface issue BPEL flow process or according to flow definition by the BPEL engine.
BPEL allows to use Web service assembly exploitation complicated service flow process, supports complete flow process control structure, as: circulation and condition, variable, distribute data value, definition error handling procedure or the like.The BPEL standard is brought up to a unprecedented degree with the interoperability and the portability of flow process.Interoperability makes the operation flow that operates on the different business flow engine can be mutual each other, and with the service interaction of a plurality of suppliers and the platform issue of increasing income, flow process exploitation deployment mode that BPEL is provided and flow performing control function are applied to and can make the data flow exploitation in the data exchange system, revise and dispose more flexible.
In order to make system have good framework and extensibility, and can be complete integrated with the BPEL flow process, the present invention proposes a kind of service construction model based on assembly, the data processing module of function opposite independent in the system is encapsulated as the functional module plug-in unit of loose coupling, definition is based on the data interaction interface of WSDL (Web ServiceDescription Language) interface specification, and provides BPEL to call with the form of Component service.
Referring to Fig. 1 a,, comprise task engine module 11, BPEL engine modules 12, functional module service module 13 and system monitoring module 14 for the present invention is based on the data exchange process disposal system of BPEL.
Functional module service module 13 has encapsulated the Component service of data processing function in the exchanges data flow process (such as data pick-up, data load, data transmission, data-switching etc.).The functional module service is made up of functional module plug-in unit and Component service two parts.The functional module plug-in unit comprise a complete data processing function (such as: data pick-up), the Component service that Component service is described definition based on WSDL calls common interface-ComponentService and exchanges data BPEL model is integrated.A step in the individual feature assembly corresponding data exchange flow process BPEL model.No. one time functional module calls the corresponding step running example of implementation, and the step running example is the part of task instances.
The plug-in unit of functional module plug-in services module 13 can be divided into predefine plug-in unit and self-defined plug-in unit.The predefine plug-in unit comprises feature card commonly used in the exchanges data flow process.Self-defined plug-in unit refers to the custom feature plug-in unit of user based on specific plug-in Design Mode and oneself realization of interface definition.This structure Design makes under the definition special screne during exchanges data flow process, and the user can be quicker, expanding system function more easily, reduced complexity and development amount.
Based on WSDL (Web Service Description Language) Component service interface definition.
The all component service is all integrated based on common services interface-ComponentService and exchanges data BPEL model.Component service interface definition, ComponentService comprise two interface definition: execute, and assembly starts runnable interface, and input start-up parameter and BPEL relevant episode are returned execution journal.
Carry out the request formal definition.
Compensate, the abnormal compensating Processing Interface, handle the flow process step take place unusual after, the application scenarios of the continuous step that has run succeeded before needing rollback to handle.For example: comprise steps A, B, C, D that order is carried out in the flow process, needing unusually to occur rollback to handle, then need to call successively the activity that the compensate interface reduction of C, B, A step has been finished, compensate according to specific logic when carrying out the C node.
Compensation request formal definition.
Required parameter definition, instId keeps between task instances and the BPEL example relevant episode of incidence relation (Correlation Sets) information one to one.(relevant episode is one group of specific data that BPEL is used for association and demarcates a BPEL example.) params, transmitting assembly starts the parameter of carrying out desired data.Parameters data structure is defined as DEParams.
Serviced component starts, monitor data transmission structure-DEParams definition
Referring to Fig. 1 b, transmit different-format in order to satisfy between task engine and the various serviced component, dissimilar startups, the mutual needs of monitor data, the flow monitoring data transmission structure is defined as based on XML form multiway tree shape structure.Group names), extended attribute Property tabulation and its child node Group it is DEParams that the root of parameter tree connects node definition, and non-root node is parameter group Group, and each Group comprises base attribute (name:.Property is key-value pair＜Key, Value〉form.
The functional module of system monitoring module 14 supervisory system task engines, task, Component service real-time running state.System monitoring module 14 is to be the framework that application program is implanted management function with JMX (Java Management Extensions).JMX is standard set agency and service, and the user can use these to act on behalf of the pragmatic existing management of kimonos in any java application.Mbeans (Managed beans) is the substantial definition of monitored object, and all monitored objects must be followed design of JMX predefine and interface definition pattern.Monitoring server (JMX Mbeans Server) is a core, all monitored modules (task engine, task, Component service) are defined as Mbeans, corresponding relation between monitoring agent maintenance task engine, task, the Component service Mbeans is for the monitoring caller provides Mbeans registration, cancellation and monitoring function.
By above-mentioned data exchange process disposal system based on BPEL, the present invention also discloses a kind of data exchange process disposal route based on BPEL.The core processing process of exchanges data flow process mainly comprises following three parts.
1, exchanges data implementation.
This process is the operational process of exchanges data flow process, comprises instance management, and flow process control and execution are returned the log information processing mode and carried out subprocess.Relate to task engine module 11, BPEL engine modules 12 and Component service module 13.
Referring to Fig. 2, the procedure processing method that the present invention is based on the BPEL exchanges data is shown, may further comprise the steps.
Step S201, task engine module 11 creation task examples make up the required start-up parameter data of each step in the exchange flow process;
Step S202, task engine module 11 definition BPEL relevant episode are created BPEL flow startup soap message;
Step S203, task engine module 11 specify BPEL flow services address to send the SOAP request in the BPEL engine;
Step S204, BPEL module 12 are created the BPEL example and are started;
Step S205, BPEL module 12 are carried out data exchange current journey, invocation component service by predetermined with the BPEL model;
Step S206, Component service module 13 are resolved the DEParams structural parameters, the local definition structure parameter group of formation component;
Step S207, Component service module 13 start assemblies are carried out, and return the BPEL execution result after finishing;
Step S208, BPEL engine modules 12 judge whether correct execution, in this way, forward step S209 to; As not forwarding step S210 to;
Step S209, BPEL engine modules 12 calling task engine service are returned execution journal, forward step S211 to;
Step S210, BPEL engine modules 12 calling task engine service are returned abnormal information;
Step S211, task engine module 11 handle and the persistence assembly is carried out return message;
Step S212, BPEL engine modules 12 judge to carry out whether finish, forward step S213 in this way to, as not, return step S205;
Step S213, BPEL engine modules 12 calling task engine service, Returning process implementation log information finishes the BPEL example;
Step S214, task engine module 11 are handled and persistence flow performing return message, and example ends task.
It is a kind of based on BPEL data exchange processing system that the present invention also provides.Referring to Fig. 3, this system comprises task engine module 11, BPEL engine modules 12, reaches Component service module 13, task engine module 11 comprises task instances establishment submodule 111, BPEL engine modules 12 comprises that the BPEL example is created submodule 121 and execution finishes to judge submodule 122, and Component service module 13 comprises assembly implementation sub-module 131.
Task instances is created submodule 111 creation task examples, makes up BPEL example desired parameters; The BPEL example is created submodule 121 and is created the BPEL example, carries out data exchange current journey by predetermined BPEL model; Assembly implementation sub-module 131 is carried out the BPEL example; Carry out and finish to judge that submodule 122 judges whether to carry out end,, start described BPEL example and create submodule as not; In this way, finish BPEL example and task instances.
Wherein, task instances is created submodule 111 and is comprised start-up parameter construction unit and SOAP parameter start unit, and the start-up parameter construction unit makes up required start-up parameter data in the exchange flow process; SOAP parameter start unit definition BPEL relevant episode is created the BPEL flow process and is started soap message.
Wherein, assembly implementation sub-module 131 comprises structural parameters group generation unit and carries out correct judging unit: structural parameters group generation unit is resolved the structural parameters in the BPEL example, the local definition structure parameter group of formation component; Carry out correct judging unit and carry out the BPEL example, judge whether correct execution, in this way, return execution journal by parameter group; As not, return abnormal information.
2, breakpoint transmission processing procedure.
This process index was carried out the process that the breakpoint recovery tasks is carried out according to after make a mistake in the exchange process Processing tasks implementation termination or manual the time-out from last time.Relate to module task engine module 11, BPEL engine modules 12 and Component service module 13 are arranged.
Referring to Fig. 4, the breakpoint transmission disposal route that the present invention is based on the BPEL exchanges data is shown, concrete steps are following steps.
Step S401, task engine module 11 creation task examples make up the required start-up parameter data of each step in the exchange flow process;
Step S402, task engine module 11 definition BPEL relevant episode are created the BPEL flow process and are started soap message;
Step S403, task engine module 11 specify BPEL flow services address to send the SOAP request in the BPEL engine;
Step S404, BPEL module 12 are created the BPEL example and are started;
Step S405, BPEL module 12 are carried out data exchange current journey, invocation component service by predetermined with the BPEL model;
Step S406, Component service module 13 are resolved the DEParams structural parameters, the local definition structure parameter group of formation component;
Step S407, Component service module 13 judge whether to comprise breakpoint, forward step S409 in this way to; As not, forward step S408 to;
Step S408, Component service module 13 start assemblies are normally carried out, and return the BPEL execution result after finishing;
Step S409, Component service module 13 are resolved the BPEL breakpoint information, and start assembly is replied and carried out, and returns the BPEL execution result after finishing;
Step S410, BPEL engine modules 12 judge whether correct execution, in this way, forward step S411 to; As not forwarding step S412 to;
Step S411, BPEL engine modules 12 calling task engine service are returned execution journal, forward step S411 to;
Step S412, BPEL engine modules 12 calling task engine service are returned abnormal information;
Step S413, task engine module 11 handle and the persistence assembly is carried out return message;
Step S414, BPEL engine modules 12 judge to carry out whether finish, forward step S415 in this way to, as not, return step S405;
Step S415, BPEL engine modules 12 calling task engine service, Returning process implementation log information finishes the BPEL example;
Step S416, task engine module 11 are handled and persistence flow performing return message, and example ends task.
The present invention also provides a kind of breakpoint transmission disposal system based on the BPEL exchanges data.Referring to Fig. 5, comprise task engine module 11, BPEL engine modules 12, reach Component service module 13, task engine module 11 comprises task instances establishment submodule 111, BPEL engine modules 12 comprises BPEL example establishment submodule 121, BPEL model submodule 123 and carries out the correct submodule 124 of judging that Component service module 13 comprises that the structural parameters group generates submodule 132 and breakpoint judgement submodule 133
Task instances is created submodule 111 creation task examples, makes up BPEL example desired parameters; The BPEL example is created submodule 121 and is created the BPEL example; BPEL model submodule 123 is carried out data exchange current journey by predetermined BPEL model; The structural parameters group generates the structural parameters that submodule 132 is resolved in the BPEL example, the local definition structure parameter group of formation component; Breakpoint judges submodule 133 judges whether parameter group comprises breakpoint, in this way, resolves breakpoint information, and start assembly recovers to carry out; As not, carry out the BPEL example.Carry out correct judgement submodule 124 and carry out the BPEL example, judge whether correct execution, in this way, return execution journal by parameter group; As not, return abnormal information.
Wherein, task instances establishment submodule 111 comprises start-up parameter construction unit and soap message start unit; The start-up parameter construction unit makes up required start-up parameter data in the exchange flow process; Soap message start unit definition BPEL relevant episode is created the BPEL flow process and is started required soap message.
3, flow process dynamic monitoring process
This process refers to that the dynamic monitoring data exchange process handles the process of real-time status information, and purpose is to use the family to carry out and the real-time status information of data processing from supervisor console graphic interface monitor data exchange process.Relating to the core system module has: system monitoring module 14, task engine module 11 and Component service module 13.
Referring to Fig. 6, the dynamic monitoring disposal route that the present invention is based on the BPEL exchanges data is shown, concrete steps are following steps.
Step S601, system monitoring module 14 are searched the task engine of current application from JMX Server;
Step S602, task engine module 11 are obtained the task engine status data and are returned;
Step S603, system monitoring module 14 are preserved data to monitoring return data object;
Step S604, system monitoring module 14 are searched the task instances of corresponding current monitoring flow process from JMX Server;
Step S605, task engine module 11 are obtained the task instances status data and are returned;
Step S606, system monitoring module 14 are preserved data to monitoring return data object;
Step S607, task engine module 11 are searched the current serviced component example that is moving based on example ID from JMX Server;
Step S608, serviced component module 13 securing components service current status data return;
Step S609, task engine module 11 are preserved data to monitoring return data object;
Step S610, task engine module 11 are returned the monitor data object to supervisor console and are shown.
The present invention also provides a kind of flow process dynamic monitoring system based on the BPEL exchanges data.Referring to Fig. 7, comprise: system monitoring module 14, task engine module 11, and Component service module 13, system monitoring module 14 comprises that monitoring return data object is preserved submodule 141, supervisor console submodule 142, task engine searches submodule 143 and task instances is searched submodule 144, task engine module 11 comprises task engine state data acquisition submodule 111 and task instances state data acquisition submodule 112, and serviced component module 13 comprises Component service state data acquisition submodule 131.
Task engine is searched submodule 143 is searched current application from JMX Server task engine, send to task engine state data acquisition submodule 111, task engine state data acquisition submodule 111 obtains the status data of current task engine, sends to monitoring return data object and preserves submodule 141;
Task instances is searched submodule 144 is searched corresponding current monitoring flow process from JMX Server task instances, send to task instances state data acquisition submodule 112, task instances state data acquisition submodule 112 obtains the status data of current task example, sends to monitoring return data object and preserves submodule 141;
The serviced component example is searched submodule 145 and is searched the current serviced component example that is moving based on example ID from JMX Server, occur to Component service state data acquisition submodule 131, Component service state data acquisition submodule 131 securing components are served the status data of current execution, send to monitoring return data object and preserve submodule 141.
Monitoring return data object preservation submodule 141 is preserved the data that receive and is arrived monitoring return data object, 142 pairs of monitoring of supervisor console submodule return data object enforcement monitoring.
Enumerate an embodiment below.
The exchanges data from data source A to data source B is finished in certain data exchange processing requirements of process.Comprising the step that three orders are carried out in the data exchange process, is respectively data pick-up, data transmission and data load (as shown in Figure 8).The data pick-up step is responsible for the data of needs exchange are extracted from data source A, and converts the data of XML form to; Data transmission step sends to the appointment destination with the XML formatted data that extracts; The data load step detects after the XML data that transmit data load in destination data source B.
Definition of data exchange flow process can be divided into following three steps:
1, create the functional module plug-in unit: this data exchange process is handled and need be used two types plug-in unit, is ETL functional module (being responsible for finishing data pick-up and data load step) respectively; Transfer function assembly (being responsible for data transmission step).
2, definition BPEL model: create exchanges data BPEL model (patterned structures of model is described) based on selected functional module plug-in unit and ComponentService interface definition.
3, create the exchanges data task: create the exchanges data task of corresponding service logic, related BPEL model definition makes up each step and carries out required start-up parameter.
Exchanges data core processing process can be divided into following three steps (incidence relation between BPEL model, functional module and the process step is as shown in Figure 9):
BPEL engine calling ETL functional module is served, and imports the start-up parameter of corresponding data extraction step into, starts the ETL assembly.After the data pick-up process is complete execution result returned task instances and handle, BPEL engine calling transfer function Component service is subsequently imported the start-up parameter of corresponding data transmitting step into, starts the Transport assembly.After data transmission procedure is complete execution result is returned task instances and handle, BPEL engine calling ETL functional module is served subsequently, imports the start-up parameter of corresponding data load step into, starts the ETL assembly.
The present invention has improved the extensibility of systemic-function on the advantages characteristic basis that has kept available data exchange processing mode, a kind of mode that defines, revises data exchange process easily is provided.Deployment strategy is more flexible, and Component service can independently be disposed, and has reduced the degree of dependence to the private server of moving whole flow chart of data processing.
The above only is a preferred implementation of the present invention; should be understood that; for those skilled in the art; under the prerequisite that does not break away from the principle of the invention; can also make some improvements and modifications; also can above-mentioned embodiment make up, these technical schemes of improving, retouching and being combined to form also should be considered as protection scope of the present invention.
Claims (21)
1, a kind of procedure processing method based on the BPEL exchanges data is characterized in that, comprises;
Step 11, creation task example make up BPEL example desired parameters;
Step 12, establishment BPEL example;
Step 13, carry out data exchange current journey by predetermined BPEL model;
Step 14, execution BPEL example judge whether to carry out and finish, and as not, return step 13; In this way, finish BPEL example and task instances.
2, the method for claim 1 is characterized in that, makes up BPEL example desired parameters and is specially:
Required start-up parameter data in step 111, the structure exchange flow process;
Step 112, definition BPEL relevant episode are created the BPEL flow process and are started required soap message.
3,, carrying out the BPEL example is specially:
Structural parameters in step 141, the parsing BPEL example, the local definition structure parameter group of formation component;
Step 142, carry out the BPEL example, judge whether correct execution, in this way, return execution journal by parameter group; As not, return abnormal information.
4, method as claimed in claim 3, it is characterized in that, described local definition structure parameter group is a multiway tree shape structure, the root node of multiway tree shape structure is DE Params, non-root node is parameter group Group, and each parameter group Group comprises base attribute, extended attribute Property tabulation and child node Group.
5, a kind of process disposal system based on the BPEL exchanges data, it is characterized in that, comprise task engine module, BPEL engine modules, reach the Component service module, described task engine module comprises task instances establishment submodule, described BPEL engine modules comprises that the BPEL example is created submodule and execution finishes to judge submodule, and described Component service module comprises the assembly implementation sub-module;
Described task instances is created submodule, is used for the creation task example, makes up BPEL example desired parameters;
Described BPEL example is created submodule, is used to create the BPEL example, carries out data exchange current journey by predetermined BPEL model;
Described assembly implementation sub-module is used to carry out the BPEL example;
Described execution finishes to judge submodule, is used to judge whether carry out and finishes, and as not, starts described BPEL example and creates submodule; In this way, finish BPEL example and task instances.
6, system as claimed in claim 5 is characterized in that, described task instances is created submodule and comprised start-up parameter construction unit and SOAP parameter start unit;
Described start-up parameter construction unit is used for making up the required start-up parameter data of exchange flow process;
Described SOAP parameter start unit is used to define the BPEL relevant episode, creates the BPEL flow process and starts required soap message.
7, system as claimed in claim 5 is characterized in that, described assembly implementation sub-module comprises structural parameters group generation unit and carries out correct judging unit:
Structural parameters group generation unit is used for resolving the structural parameters of BPEL example, the local definition structure parameter group of formation component;
Carry out correct judging unit, be used for carrying out the BPEL example, judge whether correct execution, in this way, return execution journal by parameter group; As not, return abnormal information.
8, a kind of breakpoint transmission disposal route based on the BPEL exchanges data is characterized in that, comprising:
Step 81, creation task example make up BPEL example desired parameters;
Step 82, establishment BPEL example;
Step 83, carry out data exchange process by predetermined BPEL model;
Structural parameters in step 84, the parsing BPEL example, the local definition structure parameter group of formation component;
Step 85, judge whether parameter group comprises breakpoint, in this way, resolve breakpoint information, start assembly recovers to carry out; As not, carry out the BPEL example.
9, method as claimed in claim 8 is characterized in that, makes up BPEL example desired parameters and is specially:
Required start-up parameter data in step 811, the structure exchange flow process;
Step 812, definition BPEL relevant episode are created the BPEL flow process and are started required soap message.
10, method as claimed in claim 8 is characterized in that, carries out the BPEL example and is specially:
Step 842, carry out the BPEL example, judge whether correct execution, in this way, return execution journal by parameter group; As not, return abnormal information.
11, a kind of breakpoint transmission disposal system based on the BPEL exchanges data, it is characterized in that, comprise task engine module, BPEL engine modules, reach the Component service module, described task engine module comprises task instances establishment submodule, described BPEL engine modules comprises BPEL example establishment submodule and BPEL model submodule, and described Component service module comprises that the structural parameters group generates submodule and breakpoint is judged submodule;
Described task instances is created submodule, is used for the creation task example, makes up BPEL example desired parameters;
Described BPEL example is created submodule, is used to create the BPEL example;
Described BPEL model submodule is used for carrying out data exchange current journey by predetermined BPEL model;
Described structural parameters group generates submodule, is used for resolving the structural parameters of BPEL example, the local definition structure parameter group of formation component;
Described breakpoint is judged submodule, is used to judge whether parameter group comprises breakpoint, in this way, resolves breakpoint information, and start assembly recovers to carry out; As not, carry out the BPEL example.
12, system as claimed in claim 11 is characterized in that, described task instances is created submodule and comprised start-up parameter construction unit and SOAP parameter start unit;
Described start-up parameter construction unit is used for making up the required start-up parameter data of exchange flow process;
Described SOAP parameter start unit is used to define the BPEL relevant episode, creates the BPEL flow process and starts required soap message.
13, system as claimed in claim 11 is characterized in that, described BPEL engine modules also comprises carries out the correct submodule of judging, is used for carrying out the BPEL example by parameter group, judges whether correct execution, in this way, returns execution journal; As not, return abnormal information.
14, a kind of dynamic monitoring disposal route based on the BPEL exchanges data is characterized in that, comprising:
Step 141, obtain the status data of current task engine, be saved in the monitoring return data object, implement monitoring;
Step 142, obtain the status data of current task example, be saved in the monitoring return data object, implement monitoring;
Step 143, securing component are served the status data of current execution, are saved in the monitoring return data object, implement monitoring.
15, method as claimed in claim 14 is characterized in that, the status data that obtains the current task engine is specially:
Step S1411, search the task engine of current application from JMX Server;
Step S1412, obtain the task engine status data and return monitoring return data object.
16, method as claimed in claim 14 is characterized in that, the status data that obtains the current task example is specially:
Step S1421, search the task instances of corresponding current monitoring flow process from JMX Server;
Step S1422, obtain the task instances status data and return monitoring return data object.
17, method as claimed in claim 14 is characterized in that, the status data that securing component is served current execution is specially:
Step S1431, search the current serviced component example that is moving from JMX Server based on example ID;
Step S1432, securing component service current status data return monitoring return data object.
18, a kind of dynamic monitoring disposal system based on the BPEL exchanges data, it is characterized in that, comprise: system monitoring module, task engine module, and Component service module, described system monitoring module comprises monitoring return data object preservation submodule and supervisor console submodule, described task engine module comprises task engine state data acquisition submodule and task instances state data acquisition submodule, and described serviced component module comprises Component service state data acquisition submodule;
Described task engine state data acquisition submodule is used to obtain the status data of current task engine, sends to described monitoring return data object and preserves submodule;
Described task instances state data acquisition submodule is used to obtain the status data of current task example, sends to described monitoring return data object and preserves submodule;
Described Component service state data acquisition submodule is used for the status data that securing component is served current execution, sends to described monitoring return data object and preserves submodule;
Described monitoring return data object is preserved submodule, is used to preserve the data that receive and arrives monitoring return data object;
Described supervisor console submodule is used for monitoring return data object is implemented monitoring.
19, system as claimed in claim 18 is characterized in that, described system monitoring module comprises that also task engine searches submodule, is used for searching from JMX Server the task engine of current application, sends to described task engine state data acquisition submodule.
20, system as claimed in claim 18, it is characterized in that, described system monitoring module comprises that also task instances searches submodule, is used for searching from JMX Server the task instances of corresponding current monitoring flow process, sends to described task instances state data acquisition submodule.
21, system as claimed in claim 18, it is characterized in that, described system monitoring module comprises that also the serviced component example searches submodule, is used for searching the current serviced component example that is moving based on example ID from JMX Server, sends to Component service state data acquisition submodule.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN200910013199A CN101630247A (en) | 2009-08-11 | 2009-08-11 | BPEL-based data exchange process treatment method and treatment system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN200910013199A CN101630247A (en) | 2009-08-11 | 2009-08-11 | BPEL-based data exchange process treatment method and treatment system |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN101630247A true CN101630247A (en) | 2010-01-20 |
Family
ID=41575366
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN200910013199A Pending CN101630247A (en) | 2009-08-11 | 2009-08-11 | BPEL-based data exchange process treatment method and treatment system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN101630247A (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102508908A (en) * | 2011-11-11 | 2012-06-20 | 北京用友政务软件有限公司 | Method for acquiring subordinate financial business data and system for acquiring subordinate financial business data |
| CN105493047A (en) * | 2013-09-28 | 2016-04-13 | 迈克菲股份有限公司 | Merging multiple system trees over a data exchange layer |
-
2009
- 2009-08-11 CN CN200910013199A patent/CN101630247A/en active Pending
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102508908A (en) * | 2011-11-11 | 2012-06-20 | 北京用友政务软件有限公司 | Method for acquiring subordinate financial business data and system for acquiring subordinate financial business data |
| CN102508908B (en) * | 2011-11-11 | 2015-04-08 | 北京用友政务软件有限公司 | Method for acquiring subordinate financial business data and system for acquiring subordinate financial business data |
| CN105493047A (en) * | 2013-09-28 | 2016-04-13 | 迈克菲股份有限公司 | Merging multiple system trees over a data exchange layer |
| US10205798B2 (en) | 2013-09-28 | 2019-02-12 | Mcafee, Llc | Merging multiple system trees over a data exchange layer |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US8626877B2 (en) | Method and system for implementing a global information bus in a global ecosystem of interrelated services | |
| US8065657B2 (en) | Exchange infrastructure system and method | |
| US7401131B2 (en) | Method and system for implementing improved containers in a global ecosystem of interrelated services | |
| CN107391142B (en) | Application splitting method and device | |
| CN101427220A (en) | Componentized automatic provisioning and management of computing environments for computing utilities | |
| CN102208081A (en) | Method for making business process management (BPM) application to be suitable for being used by multi-tenancy (MT) usages and apparatus thereof | |
| CN105446819A (en) | Service connection system and design method therefor | |
| EP1506478B1 (en) | Exchange infrastructure system and method | |
| CN100466554C (en) | Communication adaptation layer system and method for obtaining the network element information | |
| CN101630247A (en) | BPEL-based data exchange process treatment method and treatment system | |
| CN103064688A (en) | Workflow universal service method and system | |
| CN113157737B (en) | Service instance association relation dynamic construction system | |
| CN110516130A (en) | Metadata processing method and device, storage medium, electronic device | |
| Van Lessen et al. | An execution engine for semantic business processes | |
| CN109327529A (en) | Distributed Scans method and system | |
| KR20010039172A (en) | Interworking method between workflow system and legacy system | |
| US20230018479A1 (en) | Method, system, medium, and server for operation management of electronic devices | |
| CN116796297A (en) | Identity generation system, method and related equipment | |
| CN113961635A (en) | Interface proxy method for equipment business and parameter query system | |
| CN101340453A (en) | Dynamic evolution method based on system structure in service cooperation | |
| CN114064702A (en) | Penetrating type data query method and system based on micro-service calling | |
| Mannava et al. | An adaptive design pattern for invocation of synchronous and asynchronous web services in autonomic computing systems | |
| Peng et al. | An agent system for application initialization in an integrated manufacturing environment |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C12 | Rejection of a patent application after its publication | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20100120 |