CN101458628A - Program edition management method - Google Patents
Program edition management method Download PDFInfo
- Publication number
- CN101458628A CN101458628A CNA2008102386133A CN200810238613A CN101458628A CN 101458628 A CN101458628 A CN 101458628A CN A2008102386133 A CNA2008102386133 A CN A2008102386133A CN 200810238613 A CN200810238613 A CN 200810238613A CN 101458628 A CN101458628 A CN 101458628A
- Authority
- CN
- China
- Prior art keywords
- flow
- template
- name
- flow process
- application
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000007726 management method Methods 0.000 title claims abstract description 27
- 230000002452 interceptive effect Effects 0.000 claims abstract description 6
- 238000000034 method Methods 0.000 claims description 82
- 230000008569 process Effects 0.000 claims description 72
- 230000009471 action Effects 0.000 claims description 17
- 230000000977 initiatory effect Effects 0.000 claims description 9
- 230000009897 systematic effect Effects 0.000 claims description 4
- 238000012217 deletion Methods 0.000 claims description 3
- 230000037430 deletion Effects 0.000 claims description 3
- 239000007858 starting material Substances 0.000 claims description 3
- 238000006243 chemical reaction Methods 0.000 claims description 2
- 230000004044 response Effects 0.000 abstract description 11
- 238000012986 modification Methods 0.000 abstract description 3
- 230000004048 modification Effects 0.000 abstract description 3
- 230000008859 change Effects 0.000 description 5
- 238000005516 engineering process Methods 0.000 description 4
- 230000003993 interaction Effects 0.000 description 4
- 238000011161 development Methods 0.000 description 3
- 239000000047 product Substances 0.000 description 2
- 230000005540 biological transmission Effects 0.000 description 1
- 230000015572 biosynthetic process Effects 0.000 description 1
- 238000004891 communication Methods 0.000 description 1
- 238000000151 deposition Methods 0.000 description 1
- 238000010586 diagram Methods 0.000 description 1
- 239000012467 final product Substances 0.000 description 1
- 238000012423 maintenance Methods 0.000 description 1
- 238000012545 processing Methods 0.000 description 1
- 238000012546 transfer Methods 0.000 description 1
Images
Abstract
The invention relates to an application program version management on flow platform in Unicom SOA platform and Mobile EOMS system, especially provides a program version management method based on J2EE+MVC+SOA architecture. The invention can solve the version upgrading problem adopting new and old coexistence and step by step replacing modes, specially, each flow instance can record own all information of human-machine interactive operation interface, and a response address can be generated by the mode of full path when the response links are generated, thereby avoiding generating affect for the existing flow caused by the new modification and improving the management efficiency.
Description
Technical field
(Service-Oriented Architecture Based: Service-Oriented Architecture) (the electronics operation management system: the version management of application program on the flowsheet platform in system Electric Operation Management System), (Java2 enterprise-level development platform+Model-View-Controller model-view-controller+SOA Service-Oriented Architecture Based: Service-Oriented Architecture) architecture provides a kind of program edition management method to be based on J2EE+MVC+SOA specifically for platform and mobile EOMS to the present invention relates to the SOA of UNICOM.
Background technology
Increasingly mature along with the SOA technology, in order to reach the needs of quick response enterprises business demand, more and more enterprises begins to build the SOA system of oneself.Can realize the free layout of operation flow in the SOA system neatly, thus the variation of response service demand fast, and the while also can provide the channel of free communication for the connection between the different business systems.Each business procedure that is combined in together in order to satisfy certain business demand is called operation flow; Each operation flow can change in the process of implementation inevitably, all provides time-based version management function in order to adapt to the at present main SOA product of this variation, thereby makes and do not influence each other in system version new and old edition flow process during upgrading.The flow instance that has promptly started before upgrading still can circulate according to legacy version, and the new flow instance that starts in upgrading back just can be enabled new version.
Though provide for perfect version management technology at flow template itself at the SOA product; But in the function aspect the man-machine interaction also a little less than the relative thin.Under the SOA framework, the logical data of software separates with application data.Needing people's participation in man-machine interaction's flow process, need provide interactive interface for operating personnel, is exactly our said list usually.List submits to background application to preserve the application data of user's input, list and flow process are relatively independent, when the business demand change system is upgraded (the list element of someone-machine interactive interface changes) so, how to guarantee that the consistance of list and background program and the integrality of system data are the problems of a reality, specifically, be exactly how to allow before upgrading start flow example, and the new flow instance that produces is with new list operation still with original list operation.Simply say to be exactly how to finish the version management problem of application program under the SOA framework.
Relevant noun is explained as follows:
EOMS Electric Operation Maintenance System, electronics operation dimension
Protecting system
SOA Service-Oriented Architecture, Service-Oriented Architecture Based:
J2EE Java2 enterprise edition, Java2 enterprise-level development platform
MVC Model-View-Controller, model-view-controller
Struts Java web application Development Framework of increasing income
Context Root web application access context root
Trigger in the Trigger database technology is based upon on the specific database table;
When changing, the data in the table can be performed.
A class among the Hashmap Java has realized " key-value " corresponding quick access.
API Application Programming Interface, application programming connects
Mouthful
Action handles the java class of web page operation action in web application.
Summary of the invention
A kind of program edition management method of the present invention is when change takes place business demand, can guarantee the continuity of the Application Program Interface that flow process is mutual and the consistance of data.Flow instance before the business change still can be finished up to all flow processs according to original application interface operation, and new flow instance then circulates with new application interface.
The technical solution adopted for the present invention to solve the technical problems is:
At first, safeguard a application list, be used for being kept at the information of all application programs of moving on the SOA platform, comprise Context Root and other explanation of application.The list structure that is used is as follows:
| Field name | Explanation | Type | Major key |
| APP_ID | Application program ID | Character | Y |
| APP_NAME | Application name | Character | N |
| APP_PATH | Use the path | Character | N |
| (context?Root) | |||
| SORT_ID | -ordering number | Numeral | N |
Application architecture adopts the Struts MVC framework of increasing income, and system is referred to as an Action for each flow template provides a unified responder.The i.e. Action of the corresponding response service logical process of flow template, Action defines following method, is used for responding the difference action of man-machine interaction:
The realization flow template management function realizes classification and response Action management to each flow process.Provide unified management, application program, flow process classified information and the pairing Action of interactive program address under the logging template to all flow processs on the platform.
| Field name | Explanation | Type | Major key |
| TEMPLATE_NAME | The flow template name | Character | Y |
| TEMPLATE_DISPLAY_NAME | The flow template Chinese name | Character | N |
| APPLICATION_ID | Owning application ID | Character | N |
| APPLICATION_NAME | The owning application name | Numeral | N |
| TEMPLATE_TYPE_ID | The flow process Sort Code | Character | N |
| TEMPLATE_TYPE | The flow process systematic name | Character | N |
| FORM_URL | Action address (relative address in the application program) | Character | N |
| SUB_TEMPLATE_NAME | Sub-process name (if having a plurality of) with CSV | Character | N |
Flow process filing function.This function mainly be used for when flow process is initiated, writing down each flow instance the situation that is provided with of corresponding flow template, and the user can inquire about according to the filing situation and forms the pairing Action of each flow tasks when generating task list, thereby makes can find correct responder when the user operates.
Its list structure is as follows:
| Field name | Explanation | Type | Major key |
| PIID | Flow instance number | Character | Y |
| TITLE | Task name | Character | N |
| starter | Flow process promoter | Character | N |
| Start_time | Flow process is initiated the time | Date | N |
| End_time | The flow process concluding time | Date | N |
| FLAG | State marks (1 finishes, in 0 circulation) | Numerical value | N |
| TEMPLATE_NAME | The flow template name | Character | N |
| TEMPLATE_DISPLAY_NAME | The flow template Chinese name | Character | N |
| APPLICATION_ID | Owning application ID | Character | N |
| APPLICATION_NAME | The owning application name | Numeral | N |
| TEMPLATE_TYPE_ID | The flow process Sort Code | Character | N |
| TEMPLATE_TYPE | The flow process systematic name | Character | N |
| FORM_URL | Action address (relative address in the application program) | Character | N |
Disposal route when flow process is initiated.In flow process initiation process, at first according to the current situation that is provided with of flow template name query drainage journey template, comprise all the elements that affiliated application, template Chinese name and Action address etc. are provided with in 1.3, content is saved as Hashmap variable (Key is a field name, and Value is a field value); Secondly, utilize content in the API Hashmap variable that platform provides to be set to the Custom Attributes (customer property) of flow instance; At last, convert the content among the Hashmap to the Insert operation together with the instance number (PIID) of flow instance and other relevant information and be inserted in the 1.4 described tables, flag is set to 0 under the initial situation.
Disposal route when flow process finishes.In order to preserve the operational efficiency of SOA platform, flow setting is deletion automatically after finishing; Simultaneously, be provided with the table shown in 1.4, and initiate in the operation related content of flow instance has been saved in this table in 1.5 described flow processs in order conveniently to inquire the flow process of having finished; Just the flag that writes down when flow process is initiated is masked as 0 (not finishing), will identify update (renewal) so and be 1 when flow process is finished and get final product.
Task list and generation method.For convenience the user handles and query task or flow instance, and application program provides corresponding task query interface, comprise Pending tasks, do task, flow process that I initiate, finish task dispatching.The formation of task list comprises two parts content, and a part is need be the content of user's displaying, and another part is the response address that system will point to when the user need check or handle task.The generation method of response address has two kinds in the present invention, and a kind of is that attribute (customerproperties) according to flow process self combines, Pending tasks, do task, flow process that I initiate all is in this way to generate; Another kind method is that Query Result combines from the table described in 1.4, finishes task list and promptly generates with method.
Jump to task at task list when the user clicks task name and handle the interface, link is with the form performance of complete trails.The response address (form_url) that comprises server address (containing port), application program Root Context, flow process; Other content is with the form transmission of required parameter (Request Parameter), comprises Parm (current node name), PIID (flow instance number), PPIID (father's flow process number), state several partial contents such as (flow process current states); Wherein the value of state is different in different list interface, is waiting at Pending tasks, to do the flow process that task is finished, I initiate be started; In finishing task list, do not have the state attribute, represent with parm=view.Be a link example of a Pending tasks tabulation below:
http://192.168.200.120：9080/eoms/cirAttemper/cirAttemperAction.do？parm＝sgddyzddd&tkiid＝xxx&piid＝xxxx&ppiid＝xxxxx&displayName＝nnnn&state＝waiting
A kind of program edition management method of the present invention is to absorb the flow template thoughts of management, adopts new and old coexistence, progressively alternative solves the edition upgrading problem.Briefly be exactly new example operation new procedures, old example moves old program.On the specific implementation, each flow instance all writes down the full detail of the man-machine interaction's operation interface of oneself, and the form with complete trails generates response address when generating response chains, thereby avoids new modification that existing flow process is exerted an influence.
Description of drawings
Fig. 1 is the method flow diagram of a kind of program edition management method of the present invention.
Embodiment
Below in conjunction with the drawings and specific embodiments a kind of program edition management method of the present invention is further described.
A kind of program edition management method may further comprise the steps:
A, safeguard a application list, be used for being kept at the information of all application programs of moving on the SOA platform;
B, system provide a unified responder for each flow template;
C, provide unified management, application program, flow process classified information and the pairing address of interactive program under the logging template to all flow processs on the platform;
D, write down each flow instance the situation that is provided with of corresponding flow template, and the user can inquire about according to the filing situation and forms the pairing responder of each flow tasks when generating task list;
Application architecture adopts the Struts MVC framework of increasing income.
Secondly in flow process initiation process,,, utilize content in the API Hashmap variable that platform provides to be set to the Custom Attributes of flow instance at first according to the current situation that is provided with of flow template name query drainage journey template; At last, instance number and other the relevant information conversion operations of the content among the Hashmap together with flow instance is inserted in the following table, flag is set to 0 under the initial situation.
| Field name | Explanation | Type | Major key |
| PIID | Flow instance number | Character | Y |
| TITLE | Task name | Character | N |
| starter | Flow process promoter | Character | N |
| Start_time | Flow process is initiated the time | Date | N |
| End_time | The flow process concluding time | Date | N |
| FLAG | State marks (1 finishes, in 0 circulation) | Numerical value | N |
| TEMPLATE_NAME | The flow template name | Character | N |
| TEMPLATE_DISPLAY_NAME | The flow template Chinese name | Character | N |
| APPLICATION_ID | Owning application ID | Character | N |
| APPLICATION_NAME | The owning application name | Numeral | N |
| TEMPLATE_TYPE_ID | The flow process Sort Code | Character | N |
| TEMPLATE_TYPE | The flow process systematic name | Character | N |
| FORM_URL | Action address (relative address in the application program) | Character | N |
When flow process finishes, flow setting is deletion automatically after finishing; Related content with flow instance is saved in the top table simultaneously; To identify update when flow process is finished is 1.
When certain part (being the responder of certain flow process) of system is found to change, at first, develop a new handling procedure and dispose a new Action address, be distributed under the same application package (identical context Root) with original program; Secondly, revise the menu links that corresponding flow template is initiated operation, purpose is to allow the responder of flow process of new initiation navigate to new Action address; At last, revise the Action location value of corresponding template in the flow template administration module, flow template just can be provided with new attribute for new example when flow process is initiated like this.
When total system need be upgraded, then need new and old two edition systems and deposit and adopt different apply names, keep operation simultaneously; Revise the application program ID of all templates under the native system simultaneously at the flow template administration module.The existence of old application program can guarantee the normal circulation of original flow instance, finally finishes until flow process; The final user is shielded old application inlet, expose new application program address, guarantee that new flow instance uses new application to initiate; Thereby guaranteed the bumpless transfer of flow instance in the new and old application.
The processing of data consistency in the escalation process.In order to keep the consistance of data in new and old two databases, in the database that the disposable whole importings of original all data are new, in the legacy data storehouse, create a update/delete trigger in the corresponding table simultaneously, when update or delete operation takes place in the legacy data table, trigger, thus make legacy data modification can with the data sync in the new database.
Withdrawing from of former application program.After when one section of new-old system parallel running, As time goes on, can be fewer and feweri from the flow instance that former application program is initiated, after all use all flow instances (the flow process Custom Attributes that is provided with when initiating by flow process identifies) of former application driven to execute, the life cycle of former application program also just is through with, and promptly it can be stopped or unloading.
Generation task Query List function.The content that this part is described can be used as the part in each application program, also can be used as an independent application program and exists; When depositing as a single utility program, other program embeds the function that this part is described by the mode of interface integrated (directly calling link).Other content also can suitably be expanded if desired.
Pending tasks: this function is used for inquiring about and handling the task that the active user receives.Task shows the user with the form of tabulation, and list content comprises the promoter, initiation time, pending time of task name, template name, flow process etc.
Done task: this function is used for the task of the flow process that inquiring user once participated in and want the implementation status of the flow process of closing with task.The main contents list content comprises promoter, initiation time, the task deadline of task name, template name, flow process.
The flow process that I initiate: be used for inquiring about the flow process that the active user initiates.List content comprises task name, template name, initiation time etc.
Finish task: this module is finished for flow process inquiry of having finished and the function of checking the flow process details.List content comprises task name, template name, initiation time, concluding time, promoter etc.
Above-described embodiment, the present invention embodiment a kind of more preferably just, the common variation that those skilled in the art carries out in the technical solution of the present invention scope and replacing all should be included in protection scope of the present invention.
Claims (4)
1, a kind of program edition management method may further comprise the steps:
A, safeguard a application list, be used for being kept at the information of all application programs of moving on the SOA platform;
B, system provide a unified responder for each flow template;
C, provide unified management, application program, flow process classified information and the pairing address of interactive program under the logging template to all flow processs on the platform;
D, write down each flow instance the situation that is provided with of corresponding flow template, and the user can inquire about according to the filing situation and forms the pairing responder of each flow tasks when generating task list.
2, a kind of program edition management method according to claim 1 is characterized in that, described application architecture adopts the Struts MVC framework of increasing income.
3, a kind of program edition management method according to claim 1, it is characterized in that, described in flow process initiation process, at first according to the current situation that is provided with of flow template name query drainage journey template, secondly, utilize content in the API Hashmap variable that platform provides to be set to the Custom Attributes of flow instance; At last, instance number and other the relevant information conversion operations of the content among the Hashmap together with flow instance is inserted in the following table, flag is set to 0 under the initial situation.
4, a kind of program edition management method according to claim 1 is characterized in that, when described flow process finishes, flow setting is deletion automatically after finishing; Related content with flow instance is saved in the top table simultaneously; When flow process is finished, be 1 with identification renewal.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CNA2008102386133A CN101458628A (en) | 2008-12-17 | 2008-12-17 | Program edition management method |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CNA2008102386133A CN101458628A (en) | 2008-12-17 | 2008-12-17 | Program edition management method |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN101458628A true CN101458628A (en) | 2009-06-17 |
Family
ID=40769504
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CNA2008102386133A Pending CN101458628A (en) | 2008-12-17 | 2008-12-17 | Program edition management method |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN101458628A (en) |
Cited By (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102004947A (en) * | 2009-08-31 | 2011-04-06 | Sap股份公司 | Transforming service oriented architecture models to service oriented infrastructure models |
| CN103473101A (en) * | 2013-09-18 | 2013-12-25 | 北京思特奇信息技术股份有限公司 | Seamless version upgrading method and seamless version upgrading system |
| CN107066294A (en) * | 2017-03-17 | 2017-08-18 | 深圳市邦华电子有限公司 | One kind application installation method, device and a kind of intelligent terminal |
| CN113778515A (en) * | 2021-11-09 | 2021-12-10 | 北京世纪好未来教育科技有限公司 | Method and device for determining program package change information |
| CN115361435A (en) * | 2022-07-13 | 2022-11-18 | 阿里巴巴（中国）有限公司 | Data processing method |
-
2008
- 2008-12-17 CN CNA2008102386133A patent/CN101458628A/en active Pending
Cited By (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102004947A (en) * | 2009-08-31 | 2011-04-06 | Sap股份公司 | Transforming service oriented architecture models to service oriented infrastructure models |
| CN102004947B (en) * | 2009-08-31 | 2016-07-06 | Sap欧洲公司 | Conversion Services Oriented Achitecture model is service-oriented infrastructure model |
| CN103473101A (en) * | 2013-09-18 | 2013-12-25 | 北京思特奇信息技术股份有限公司 | Seamless version upgrading method and seamless version upgrading system |
| CN103473101B (en) * | 2013-09-18 | 2016-11-23 | 北京思特奇信息技术股份有限公司 | A kind of seamless version upgrading method and system |
| CN107066294A (en) * | 2017-03-17 | 2017-08-18 | 深圳市邦华电子有限公司 | One kind application installation method, device and a kind of intelligent terminal |
| CN113778515A (en) * | 2021-11-09 | 2021-12-10 | 北京世纪好未来教育科技有限公司 | Method and device for determining program package change information |
| CN113778515B (en) * | 2021-11-09 | 2022-03-04 | 北京世纪好未来教育科技有限公司 | Method and device for determining program package change information |
| CN115361435A (en) * | 2022-07-13 | 2022-11-18 | 阿里巴巴（中国）有限公司 | Data processing method |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US9256413B2 (en) | Automatic identification of services | |
| CN111027921B (en) | Service processing method and device, electronic equipment and storage medium | |
| US10373217B2 (en) | Order management system with decoupling of fulfillment flow from fulfillment topology | |
| US9773216B2 (en) | Workflow sharing | |
| US9043750B2 (en) | Automated generation of two-tier mobile applications | |
| US8630969B2 (en) | Systems and methods for implementing business rules designed with cloud computing | |
| CN102255752A (en) | Configuration management system and method of server cluster | |
| CN104133772A (en) | Automatic test data generation method | |
| CN104216912A (en) | Method and device for achieving non-intrusive service form workflow | |
| CN102810057A (en) | Log recording method | |
| CN102819767A (en) | Complaining and suggesting system and method based on intelligent mobile communication equipment | |
| CN102436473A (en) | Menu management device and menu management method | |
| CN101625738A (en) | Method and device for generating context-aware universal workflow application | |
| US20130067456A1 (en) | Application configuration framework for enterprise resource planning application installation | |
| CN102355499B (en) | Cloud computing system | |
| CN101661584A (en) | Dynamic order workflow template instantiator tracking system | |
| CN103077024A (en) | Device and method for supporting customization and running of software-as-a-service (SaaS) application processes | |
| CN104572068A (en) | Catalog driven order management for rule definition | |
| CN102222278A (en) | Operation process customizing method and device | |
| CN106843871B (en) | A kind of design system and design method of domain model frame | |
| CN101458628A (en) | Program edition management method | |
| CN101661583A (en) | Dynamic order workflow template instantiator tracking system | |
| CN110764752A (en) | System and method for realizing graphical service arrangement of Restful service based on micro-service architecture | |
| CN105573774A (en) | Application parameter managing and configuring method | |
| CN102215264A (en) | Method and device for supporting multi-tenancy data and service customized running |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C02 | Deemed withdrawal of patent application after publication (patent law 2001) | ||
| WD01 | Invention patent application deemed withdrawn after publication |
Open date: 20090617 |