CN202736109U - High-concurrency enterprise concentrated application system - Google Patents
High-concurrency enterprise concentrated application system Download PDFInfo
- Publication number
- CN202736109U CN202736109U CN 201220127022 CN201220127022U CN202736109U CN 202736109 U CN202736109 U CN 202736109U CN 201220127022 CN201220127022 CN 201220127022 CN 201220127022 U CN201220127022 U CN 201220127022U CN 202736109 U CN202736109 U CN 202736109U
- Authority
- CN
- China
- Prior art keywords
- module
- layer
- data
- client
- concurrency
- 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.)
- Expired - Lifetime
Links
Landscapes
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
A high-concurrency enterprise concentrated application system has a network structure mode mainly adopting a B/S structure coupled with a browser plug-in, and a desktop client program. The system comprises the following two parts. One is a client unit running on a client computer. The other is a server unit running on a server terminal. Furthermore, the server unit is divided into three layers, a presenting layer for information presenting and interaction, a business layer for business processing, and a data layer for data accessing. The client unit and the server unit significantly optimize a cluster deploying mode and support high concurrency by using the advantages of a cluster in the resource expansion aspect. Information presenting and business separation support clients of a plurality of platforms. Furthermore, by means of the optimization of the cluster deploying mode, the system has the processing capability in a high-concurrency condition enhanced.
Description
Technical field
The utility model belongs to a kind of high concurrent, centralized enterprise application architecture system architecture technical field.
Background technology
At present, enterprises service framework and the hierarchy of skill are between the various different platforms of following the J2EE framework, and compatibility still is short of, and the information products that enterprise backend is used each other can't be compatible, enterprises or the outside awkward situation that is difficult to intercommunication that exists.
The utility model content
The purpose of this utility model provides in order to overcome the defective that above-mentioned prior art exists between a kind of different platform that allows the various J2EE of following frameworks just, there is good compatibility, the information products that solve in the past enterprise backend use each other can't be compatible, enterprises or outside high concurrent, the application architecture system of centralized enterprise that is difficult to the awkward situation of intercommunication.
The purpose of this utility model is achieved by the following technical solution.
A kind of high concurrent concentration of enterprises application system, the utility model feature be, comprises that following two interconnect altogether four-layer structure of part, namely is client tier, presentation layer, operation layer, data Layer from top to bottom; Client tier includes administration interface module and subscriber interface module;
Presentation layer disposes respectively: configuration subsystem module, WEB application module, resource management module;
Operation layer disposes respectively: Service Processing Module, flow engine module, exchange files module, file server module;
Data Layer disposes the business datum library module;
Described four layers syndeton is: the administration interface module is connected with the configuration subsystem module; Subscriber interface module is connected with WEB application module, resource management module, file server module respectively; The configuration subsystem module is connected with Service Processing Module;
The WEB application module is connected with Service Processing Module, flow engine module, exchange files module respectively;
Service Processing Module, flow engine module are connected with the business datum library module respectively, and the flow engine module also is connected with subscriber interface module; The exchange files module also is connected with file server module.
: be Java 2 Platform Enterprise Edition (Java 2 Platform, Enterprise Edition), the J2EE core is one group of technical manual and guide, the various components that wherein comprises, service architecture and the hierarchy of skill, common standard and specification are all arranged, allow between the different platform of the various J2EE of following frameworks, have good compatibility, the information products that solve in the past enterprise backend use each other can't be compatible, enterprises or the outside awkward situation that is difficult to intercommunication.
Clustering: cluster (cluster) technology is a kind of newer technology, pass through Clustering, can obtain in the relatively high income aspect performance, reliability, the dirigibility paying in the situation of lower cost, its task scheduling then is the core technology in the group system.This paper has carried out brief discussion with regard to problems such as the definition of group system, development trend, task schedulings.Cluster be one group separate, by the interconnected computing machine of express network, they have consisted of a group, and are managed with the pattern of triangular web.When client and cluster interacted, cluster similarly was an independently server.Cluster configuration is for improving availability and scalability.
Pattern: the MVC framework is the abbreviation of " Model-View-Controller ", and translator of Chinese is " model-view-controller ".The MVC application program always is comprised of these three parts.Event (event) causes Controller to change Model or View, perhaps changes simultaneously both.As long as Controller has changed data or the attribute of Models, the View of all dependences can upgrade automatically.Similarly, as long as Controller has changed View, View can obtain data and refresh oneself from potential Model.
Network structure pattern of the present utility model mainly adopts the B/S structure, and is auxiliary with browser plug-in, desktop client simultaneously.System comprises following two parts, and the client unit that runs on client computer has run on the server unit of server end.Wherein, server unit is divided into again 3 layers: responsible information presents and the mutual layer that represents, and is responsible for the operation layer of business processing, and the data Layer of responsible data access.Representing of information and separating of business, the client of support kinds of platform.By the mode of this layering, separate focus, the basic function by orlop realization data progressively makes progress, and successively encapsulates, and is aided with at last the client tier of the superiors, realizes concrete business function.Every layer Each performs its own functions, and can expand.Lower floor only to the upper strata as seen, the upper strata is invisible to lower floor.Deployment way is disposed by cluster, and client unit and server unit have carried out a large amount of optimizations to the clustered deploy(ment) pattern, take full advantage of cluster support in the advantage aspect the resource expansion high concurrent, also so that the concurrent processing ability can expand.This hierarchy is not mutually isolation, and it organically combines, thereby realized the separation focus by unified framework and interface mode.
As shown in Figure 1,4 of system layers of structure are specific as follows:
1) client tier
Client tier is the form of expression of user interface, is the nearest one deck of main body applications distances user, and it is responsible for that data, service logic are converted into the element that the user can identify and presents to the user by browser.
The interface is divided into two classes, and a class is the interface that domestic consumer uses, main finishing service correlation function.Another kind of is the used administration interface of keeper, mainly links to each other the configuration of completion system environment, service environment with configuration-system.
User interface can be carried out data interaction by mode and the flow engine client of remote interface.By the use of these interfaces, can obtain easily the relevant various information of flow process, such as: suggestion information, circulation record, action button etc.
The interactive mode client tier is mainly undertaken alternately by the interface that the mode such as page synchronization request, Ajax Asynchronous Request and background application service provide, and uses packaged assembly that data are loaded, and represents to the user in close friend's mode.
Presentation layer
Presentation layer is responsible for presenting of data, is the tie that connects business, data and user interface.
Presentation layer mainly is made of web application module, resource management module and configuration subsystem.The Web application module mainly is responsible for and user interface interaction, user's request is forwarded on business processing mould, official document Switching Module piece or the flow engine module, after finishing again return data to user interface.Configuration subsystem mainly provides the realization to the configuration feature of system, and carries out alternately with administrator interfaces.Resource management module mainly is responsible for the required static resource in some interfaces is processed, and what assisted user was met represents.
Presentation layer also provides presentation of data by various other modes (such as general-purpose interface etc.) for other operation system except for the user provides presentation of data.
On the interactive mode, be to assemble query object by the reading system configuration information for presenting of data, provide various data sources, business rule, control data and operation, the assembling at completing user interface etc.Finish the representing of customizing messages, assembly work with interface assembly.
Operation layer
Operation layer is that main body is used abstract to service concept or system concept, also is responsible for persistence and the inquiry of data.Realize by the standard of introducing enterprise's application facet, guarantee versatility, consistance and the ease for use of operation layer.
Operation layer is mainly by Service Processing Module, the flow engine module, and the exchange files module, and file server forms.Service Processing Module mainly is responsible for the business processing of non-process, and the flow engine module is responsible for the process business processing, and the exchange files module is responsible for carrying out exchange files with external system, and file server then is responsible for the processing of file type data.
Mapping relations type database is come with mapping mechanism in the interactive mode aspect, makes it reach the purpose of object based programming.Finish various data manipulations by the entity object after the mapping, comprise instantiation, deletion, modification and the query manipulation of entity object, and provide support for local and remote calling.Then undertaken alternately by the mode of interface for the file type data.
Data Layer
The most concrete form of expression of data has been recorded in the realization that data Layer is used the bottom as main body, also is simultaneously the carrier behind the data persistence.
This layer be main to be adopted relevant database to realize that additions and deletions to structural data change to look into, adopt the mode of file to carry out access for unstructured data.
To the management of data, be the managerial ability of utilizing relevant database powerful to structural data, be stored in business datum in the database and manage the whole life cycle of these data.
The beneficial effects of the utility model are, by adopting the structure annexation of native system, the various components that wherein comprises, service architecture and the hierarchy of skill, common standard and specification are all arranged, allow between the different platform of the various J2EE of following frameworks, have good compatibility, the information products that solve in the past enterprise backend use each other can't be compatible, enterprises or the outside awkward situation that is difficult to intercommunication.The utility model client unit and server unit have carried out a large amount of optimizations to the clustered deploy(ment) pattern, take full advantage of cluster and support high concurrent in the advantage aspect the resource expansion.Representing of information and separating of business, the client of support kinds of platform.In addition, utilize the optimization to the clustered deploy(ment) pattern, the enhancing system is in processing power high and that give.
Description of drawings
Fig. 1 is the utility model structural representation.
Embodiment
A kind of high concurrent concentration of enterprises application system, the utility model feature be, comprises that following two interconnect altogether four-layer structure of part, namely is client tier, presentation layer, operation layer, data Layer from top to bottom; Client tier includes administration interface module and subscriber interface module;
Presentation layer disposes respectively: configuration subsystem module, WEB application module, resource management module;
Operation layer disposes respectively: Service Processing Module, flow engine module, exchange files module, file server module;
Data Layer disposes the business datum library module;
Described four layers syndeton is: the administration interface module is connected with the configuration subsystem module; Subscriber interface module is connected with WEB application module, resource management module, file server module respectively; The configuration subsystem module is connected with Service Processing Module;
The WEB application module is connected with Service Processing Module, flow engine module, exchange files module respectively;
Service Processing Module, flow engine module are connected with the business datum library module respectively, and the flow engine module also is connected with subscriber interface module; The exchange files module also is connected with file server module.
See Fig. 1, system is as follows in this specific embodiments of four layers:
1) client tier
Such as Fig. 1, client has been used the front-end technology exploitation commonly used such as HTML, JS, Flash, css.Wherein JS has partly used two very popular framework: JQuery of industry and EXT, by using these frameworks, for the front end html page provides the powerful ability that represents, provide technical foundation for realizing that high-quality user experiences, also provide higher extendability and maintainability for using main body.The flow engine client can be carried out data interaction by mode and the engine backstage of JSON-RPC.
On the interactive mode, client tier from background application service acquisition business datum, and uses JQuery plug-in unit, EXT assembly that data are loaded by modes such as page request, Ajax Asynchronous Request, represents to the user in close friend's mode.Use the JSON-RPC mode to obtain flow data, flow process button etc. from flow engine.
Presentation layer
Such as Fig. 1, presentation layer has mainly used the Tapestry framework based on the Java technology.This framework is different from traditional MVC framework, and it is the application development framework of a cover component-based.By using the Tapestry can be easily with page assembly, thereby improve the reusability of code, promoted development efficiency.
Presentation layer also provides presentation of data by modes such as WebService for other operation system.WebService is a kind of Web technology of the WSDL of use descriptive language.Use WebService can make application system and other external systems carry out smoothly exchanges data.
DWR is an engine, can be open to the JavaScript code the method for server end Java object, and make front end JS can call easily the method that background service provides.
On the interactive mode, mainly the page assembly by Tapestry provides calling service control.Finish encapsulation and the operation of page data with the automatic Loading mechanism of Tapestry.Use the DWR technology to expose the business service interface to browser end.Use WebService and flow engine to carry out data interaction, finish establishment and the maintenance of flow process.
Operation layer
Such as Fig. 1, EJB is enterprise's application standard of Java technology.By the introducing of EJB, can make application system carry out to provide various service for application program alternately with database very easily.
Can make application system carry out data interaction with database easily by Entity Bean and the Session Bean that uses EJB.EJB can be converted into relevant database (Oracle etc.) OO Java entity, makes java applet clog-freely carry out reading and operating of data according to OO mode, has simplified the operation of data.
Use Entity Bean mapping relations type database, make it reach the purpose of object based programming.Finish the operation of entity object by Session Bean, comprise instantiation, deletion, modification and the query manipulation of entity object.For local and remote calling provides support.
In addition, come management document with file server.Download and the upload function of various templates, electronic government documents etc. can be provided for the correlation module of presentation layer.
Data Layer
Such as Fig. 1, this layer be main to be adopted relevant database Oracle to realize that additions and deletions to structural data change to look into, adopt the mode of file to carry out access for unstructured data.
In addition, utilize the Oracle managerial ability powerful to structural data, be stored in business datum in the database and manage the whole life cycle of these data.For unstructured data, then utilize file server that it is managed.Both combinations provide the data storage service that can satisfy various demands for operation layer.
Claims (1)
1. one kind high concurrent concentration of enterprises application system is characterized in that, comprises that following two interconnect altogether four-layer structure of part, namely is client tier, presentation layer, operation layer, data Layer from top to bottom; Client tier includes administration interface module and subscriber interface module;
Presentation layer disposes respectively: configuration subsystem module, WEB application module, resource management module;
Operation layer disposes respectively: Service Processing Module, flow engine module, exchange files module, file server module;
Data Layer disposes the business datum library module;
Described four layers syndeton is: the administration interface module is connected with the configuration subsystem module; Subscriber interface module is connected with WEB application module, resource management module, file server module respectively; The configuration subsystem module is connected with Service Processing Module;
The WEB application module is connected with Service Processing Module, flow engine module, exchange files module respectively;
Service Processing Module, flow engine module are connected with the business datum library module respectively, and the flow engine module also is connected with subscriber interface module; The exchange files module also is connected with file server module.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN 201220127022 CN202736109U (en) | 2012-03-30 | 2012-03-30 | High-concurrency enterprise concentrated application system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN 201220127022 CN202736109U (en) | 2012-03-30 | 2012-03-30 | High-concurrency enterprise concentrated application system |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN202736109U true CN202736109U (en) | 2013-02-13 |
Family
ID=47661787
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN 201220127022 Expired - Lifetime CN202736109U (en) | 2012-03-30 | 2012-03-30 | High-concurrency enterprise concentrated application system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN202736109U (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102646232A (en) * | 2012-03-30 | 2012-08-22 | 云南远信科技有限公司 | High concurrence enterprise integrated application system |
| CN111160702A (en) * | 2019-11-28 | 2020-05-15 | 武汉兴图新科电子股份有限公司 | Total security resource integration presentation system |
-
2012
- 2012-03-30 CN CN 201220127022 patent/CN202736109U/en not_active Expired - Lifetime
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102646232A (en) * | 2012-03-30 | 2012-08-22 | 云南远信科技有限公司 | High concurrence enterprise integrated application system |
| CN111160702A (en) * | 2019-11-28 | 2020-05-15 | 武汉兴图新科电子股份有限公司 | Total security resource integration presentation system |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110989983B (en) | Zero-coding application software rapid construction system | |
| CN102646232A (en) | High concurrence enterprise integrated application system | |
| CN101777004B (en) | Method and system for realizing BPEL sub-process multiplexing based on template in service-oriented environment | |
| CN103441900B (en) | Centralized cross-platform automatization test system and control method thereof | |
| CN101847100B (en) | Method for expanding software application and device | |
| Zhang et al. | Research on lightweight MVC framework based on spring MVC and mybatis | |
| US20140007040A1 (en) | Service model-oriented software operation platform and operation method thereof | |
| CN101196926A (en) | Database access platform and access method thereof | |
| CN101291253B (en) | Man-machine command interaction method for network management terminal based on graphical interface | |
| JP2020109613A (en) | Smart irrigation area e-platform based on four-layered architecture and data processing method | |
| CN102810070A (en) | High-performance professional ability packaging process engine and process control method thereof | |
| CN103678135A (en) | System and method for achieving cross-process and cross-thread debugging in large-data environment | |
| CN101909082A (en) | Model-driven grid portal configuration system and method | |
| CN101533262A (en) | Method for realizing associative simulation of machine and control system based on service | |
| Smid et al. | Case study on data communication in microservice architecture | |
| CN103279343A (en) | Technical framework system based on distributed large website development | |
| CN101604240A (en) | A kind of design method of purchase-sell-stock management system based on MVC | |
| CN101158894A (en) | Dynamically automatic adapting programming system and method in modular soft software system | |
| CN202736109U (en) | High-concurrency enterprise concentrated application system | |
| CN113094039B (en) | Automatic code generation system based on database table | |
| CN114168117A (en) | Credit low-code development tool based on designer and storage device | |
| US20190121620A1 (en) | Extensible javascript-based data visualization toolkit | |
| CN114546415B (en) | Cloud platform big data storage optimization analysis system | |
| Huang et al. | Research on improved MVC design pattern based on struts and XSL | |
| CN101097525A (en) | Method for realizing integrated translate and edit surroundings under three layers structure |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C14 | Grant of patent or utility model | ||
| GR01 | Patent grant | ||
| CX01 | Expiry of patent term |
Granted publication date: 20130213 |
|
| CX01 | Expiry of patent term |