Web-component Enterprise Application architecture with flexible assembly

Flexible assembly of Web Components enterprise Application Architecture I. Issues and OBJECTIVES

b/S architecture of Web enterprise application is more and more popular, in order to solve the flexible business needs and business processes of enterprise users, to develop different business applications as Web components, to realize the flexible configuration and deployment of user's business processing interface and business process, and to design enterprise Web Component application architecture based on SOA service idea.

The core idea is: (1) User interface can be assembled

The user's business interface can be formed by an administrator or by itself in a dynamically configured way, called a view. A user can use different views to deal with different business, or to design their own personalized views to meet the needs of personalization. (2) Business process can be assembled

Business processes are not immutable and can be adjusted, optimized and re-engineered to meet flexible business needs and business changes. Business processes are designed and configured on-line to support new business processes without any code-level development. (3) Service

Based on the idea of SOA, web-based functions (such as Users, roles, permissions, organization, single sign-on, logs, etc.) and business components open front-end services or back-end Web services for use by other components, avoiding duplication of resources wasted on development. Ii. Solutions-Modular Web application Architecture

Layered design of modular application architecture

(1) Enterprise business components and components management

Enterprise business components may include the following elements:

• A set of UI interface and business processing logic: For the user's business operations, can be configured to the user's business view;
• Front-end services: implemented in JavaScript, other components invoke the service, implementing the business functions provided by the component, such as invoking the mapping service of the map component, realizing the drawing of the map component;
• Back-end Web services, such as compute services, basic services (get user roles, etc...) ), business services, process services, etc., such Web services can be connected to the ESB for unified management;
• Service dependent and initialization parameters: services of other components on which the component depends (including front-end and background services for runtime monitoring and detection), and initialization parameter configuration generated by the component instance;

The physical form of the component: War, EAR, jar package, deployed in the application server;

The components are low-coupling, communicating through the messaging service.

Component management includes the following basic features:

• Component registration, inputting the basic information of the deployed components, such as name, version, description, services provided (including front-end and background services), dependent services, initialization parameters of components, etc.
• Component condition monitoring: monitor the running state of components and the running state of dependent services;
• Component authorization: A component can authorize a role or user, and a privileged person can consume components, such as invoking Component Services, configuring component UI to views, and so on;

(2) Communication between components

Between components implements real-time/near-real-time communication between component front-end UI through a messaging service. The message service is based on WebSocket technology (for the push of both the front and back of the message) and the message middleware technology (for messaging) implementations, such as open source message middleware activemq. The same view Tounnes (including multi-screen view) components provide a way to communicate between topics topic subscriptions.

Component UI Communication Process

(3) User interface configuration

can also be called view configuration, through the View Configuration tool, the user view of the design, such as menus, toolbars, interface layout, style, component UI size position and initialization parameters, view for usability detection (there is a component depends on the service), the views are saved. The user enters and switches different views through the view portal and processes their business within the view. (4) View run frame

Provides a view and a running container for its components, which are responsible for the common basic functions of the view (such as login and exit, view switching, style switching, etc.) and provide an interface for communication between components (supporting front-end communication and interaction between components). (5) Business process customization

There are many end-to-end processes within the enterprise, some of which are intrinsic, some are new, and others need to be constantly optimized. Dynamically configure the process based on the user view, specifying the person who handles the process task and the desired view, and associating it with the process instance number and business ID number at the bottom of the business data.

The user view configures a common process component UI for process initiation, process task handling, view monitoring, and more.

Web-component Enterprise Application architecture with flexible assembly