Image component model based on data integration process and construction method

Abstract

The invention discloses a graphical component model based on a data integration process and a construction method. The component model comprises an Adapter component design unit, a logic agent unit, an icon unit, an attribute item design unit, an attribute expansion unit, a configuration agent design unit, a message body design unit, a rule design unit, a table mapping unit, a message template unit and an affiliated parameter design unit; the Adapter component design unit is used for newly adding an Adapter component and maintaining an existing Adapter component; the attribute item design unit controls execution of different attributes of the Adapter component through different attribute items; and the rule design unit defines various service rules to perform cleaning and conversion service processing on the message. According to the method, a standardized development process and an implementation method are combined with functions provided by the system, so that the information integration requirement is quickly met, the time cost is saved, the system stability is reliably guaranteed, and the time loss caused by technical research and technical development is reduced.

Description

Technical Field

[0001] The present invention relates to the technical field of software development components, and in particular to a graphical component model based on a data integration process and a construction method thereof. Background Art

[0002] Component development in software design refers to dividing the software system into independent, reusable components, each of which implements a specific function or service. This approach helps improve the maintainability, scalability and reusability of the software.

[0003] Existing EAI technology mainly focuses on the development and implementation of specific required functions, lacks the reuse and monitoring management of the interface implementation process, has a large development workload, and has high technical requirements for system users. At the same time, traditional EAI integration platforms generally save configuration information based on configuration files, and the implementation process basically requires a lot of secondary development to meet; and in actual application scenarios, EDI processing often needs to be linked with EAI processing. Traditional EDI application systems mainly focus on the sending, receiving and parsing functions of EDI. The application of EDI to business systems is mainly achieved through specific development, which increases the complexity and implementation cycle of EDI docking. Therefore, this solution proposes a graphical component model and construction method based on data integration process to solve the above problems. Summary of the invention

[0004] The purpose of the present invention is to provide a graphical component model and construction method based on data integration process to solve the problems raised in the above background technology.

[0005] To achieve the above object, the present invention provides the following technical solutions: a graphical component model based on a data integration process, the component model comprising an adapter component design unit, a logic agent unit, an icon unit, an attribute item design unit, an attribute extension unit, a configuration agent design unit, a message body design unit, a rule design unit, a table mapping unit, a message template unit and an attached parameter design unit;

[0006] The Adapter component design unit is used to add new Adapter components and maintain existing Adapter components;

[0007] The logic proxy unit is used for logic processing of the Adapter component;

[0008] The icon unit is used to display the Adapter component in process design and process monitoring;

[0009] The attribute item design unit controls the execution of different attributes of the Adapter component through different attribute items;

[0010] The attribute extension unit adds personalized attribute settings for the Adapter component;

[0011] The configuration agent design unit is used to control the communication settings of the components;

[0012] The message body design unit is used for message processing type design in the Adapter component scope;

[0013] The rule design unit defines various business rules for the messages received from the system through the UI to perform cleaning and conversion business processing on the messages;

[0014] The table mapping unit is used to map the relationship between the Adapter component and the database table;

[0015] The message template unit is used to define and organize the data transmission format between Adapter components;

[0016] The auxiliary parameter design unit is used to enhance the flexibility and configurability of the component by defining optional and additional parameters.

[0017] Preferably, the component content designed by the Adapter component design unit includes a component list and component basic information.

[0018] Preferably, each line of information in the component list represents a component, and the component list is used to add, import and export components.

[0019] Preferably, the component basic information includes component category, category name, component ID and component name;

[0020] The component classification is used to find and manage components during process design;

[0021] The classification name is used for component classification, and components are divided into system components, platform components and ERP components according to different functions;

[0022] The component ID is used to maintain the uniqueness of the component;

[0023] The component name marks the component information so that the user can intuitively understand the function of the component.

[0024] Preferably, the naming of the component ID is composed of a component category and an identifier in the category, and the personalized developed components are uniformly named starting with UDF_.

[0025] Preferably, when different Adapter components have the same logical processing functions, the same logical proxy class is used.

[0026] Preferably, the configuration agent design will affect the page display items when opening the configuration agent for each corresponding component in the process definition.

[0027] Preferably, the message body of the Adapter component scope includes inbound, outbound and response, and the design content of the message body includes message category, message version, processing direction and message body structure, and a component controls different message bodies and logical rules of components through message categories, and different versions of the same message category of a component have different message bodies and logical rules, each scope has a processing direction, and the processing direction determines the parsing or generation of data, and the message body structure is customized by inputting a message, and a fixed message template is used for component mapping.

[0028] A method for constructing a graphical component model based on a data integration process is used to construct the graphical component model. The method comprises the following steps:

[0029] S1, first create a new Adapter component or maintain an existing Adapter component;

[0030] S2, create or modify component logic proxy;

[0031] S3, set the properties of the component, including configuring the request address, request method, character set, and Content Type;

[0032] S4, expand the attributes of the component;

[0033] S5,design the configuration agent settings for each component;

[0034] S6, design the message body of the component, including message category, message version, processing direction and message body structure;

[0035] S7, design component rules, perform data conversion and data cleaning on the collection in MongoDb through SQL rules, Xpath rules or Java rules, and prepare the message data body for the outbound message;

[0036] S8, design component table mapping, message templates and associated parameters.

[0037] Preferably, when the component rules are designed, in the corresponding rules, the SQL rules complete the conversion of the message content in mongodb through SQL data;

[0038] Java rules complete the conversion of message content in mongoDb through rule-constrained code, and also complete external interactive verification of data through code;

[0039] XPath rules process data in the XML message body using XPath syntax.

[0040] Technical effects and advantages of the present invention:

[0041] (1) The present invention uses standardized development processes and implementation methods combined with the functions provided by the system to quickly adapt to the information integration needs, which not only saves time costs, but also reliably guarantees system stability and reduces the time loss caused by technical research and development;

[0042] (2) The present invention adopts a mode of actively adapting and matching the collection and message structure of existing messages, saving the need for information integration to transform a large number of related business systems, and utilizing existing IT resource investments to reduce cost investment during the construction process. The invention adopts an open architecture to continuously improve and enrich the model during the continuous integration process, so that the construction cost and management cost can be continuously shortened during the digital integration process by reusing the previous components and rules. BRIEF DESCRIPTION OF THE DRAWINGS

[0043] Figure 1 It is a schematic diagram of the component list and component basic information function area of ​​the present invention.

[0044] Figure 2 A schematic diagram of the functional areas of the message body designed for the components of the present invention.

[0045] Figure 3 It is a schematic diagram of the usage scenario of the components of the present invention in process design.

[0046] Figure 4 It is a schematic diagram of the UI model of the component application of the present invention. DETAILED DESCRIPTION

[0047] The following will be combined with the drawings in the embodiments of the present invention to clearly and completely describe the technical solutions in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.

[0048] Embodiment 1, the present invention provides as follows Figure 1-3 A graphical component model based on a data integration process is shown, including an adapter component design unit, a logic agent unit, an icon unit, an attribute item design unit, an attribute extension unit, a configuration agent design unit, a message body design unit, a rule design unit, a table mapping unit, a message template unit and an attached parameter design unit;

[0049] The Adapter component design unit is used to add new Adapter components and maintain existing Adapter components;

[0050] It should be noted that different new Adapter components are added to meet the diversity, complexity and reusability of components during process design;

[0051] Maintaining and adjusting existing components is a vital part of the software development life cycle. It is of great significance to ensure the stability, performance and security of the system. The following is a specific analysis of the reasons for maintaining and adjusting existing components:

[0052] 1. Fix vulnerabilities and errors: As the system is used, some unforeseen vulnerabilities or errors will be discovered. Regular maintenance is performed to promptly discover and fix these problems to prevent them from affecting the stability of the system and user experience.

[0053] 2. Adapt to business changes: The business needs of an enterprise will change with changes in the market environment and internal strategies. Maintaining existing components ensures that they can adapt to these changes and meet new business needs.

[0054] 3. Improve performance: With the growth of data volume and the increase of users, the original components will have performance bottlenecks. Through optimization and adjustment, the processing capacity and response speed of components can be improved to maintain the efficient operation of the system.

[0055] 4. Enhanced security: Software security is an ongoing process, and new security threats continue to emerge. Regularly update and maintain components to patch known security vulnerabilities and enhance the system's protection capabilities.

[0056] 5. Improve compatibility: Technology upgrades may cause existing components to be incompatible with new hardware or software. Maintenance work ensures that components are consistent with the latest technical standards to avoid compatibility issues.

[0057] 6. Optimize user experience: User needs and expectations change over time. Improve the user interface and interaction process by maintaining and adjusting existing components to provide more user-friendly services.

[0058] 7. Reduce costs: Timely maintenance reduces downtime caused by system failures, reduces repair costs and potential business losses. At the same time, optimizing component performance also reduces energy consumption and operating costs.

[0059] 8. Support regulatory compliance: Changes in laws and regulations require the system to be adjusted accordingly. Maintaining existing components ensures that the system meets the latest compliance requirements and avoids legal risks.

[0060] 9. Promote technological innovation: During the maintenance process, opportunities to improve existing components will be discovered and new technologies and methods will be introduced, thus promoting technological innovation and product upgrades.

[0061] 10. Extend system life: Extend the service life of the system through regular maintenance and upgrades, and postpone expensive full replacement or reconstruction projects.

[0062] In general, maintaining and adjusting existing components is a key measure to ensure the long-term stable operation of the system. It not only helps to solve current problems, but also prepares for future challenges and maintains the competitiveness and sustainable development of the system.

[0063] Specifically, the component content designed by the Adapter component design unit includes a component list and component basic information.

[0064] Furthermore, each line of information in the component list represents a component, and the component list is used to add, import, and export components;

[0065] The basic information of components includes component category, category name, component ID and component name;

[0066] Component classification is used to find and manage components during process design;

[0067] The classification name is used to classify components, and components are divided into system components, platform components, and ERP components according to different functions;

[0068] The component ID is used to maintain the uniqueness of the component. The component ID is named by the component category and the identifier in the category. The personalized components are uniformly named starting with UDF_. The component ID remains unique in the entire component market and is used as the only identifier during the process.

[0069] The component name marks the component information so that users can intuitively understand the function of the component.

[0070] The logic proxy unit is used for the logic processing of the Adapter component. When different Adapter components have the same logic processing functions, they use the same logic proxy class.

[0071] Specifically, each component will complete a certain logic processing function, which is implemented through the component's logic proxy class. Different components use the same logic proxy class when their logic processing functions are the same. For example, the proxy class of the component jdbc out supports the component's need to complete the addition, deletion, and modification operations to the specified database through JDBC.

[0072] Icon units are used to display Adapter components in process design and process monitoring;

[0073] The attribute item design unit controls the execution of different attributes of the Adapter component through different attribute items;

[0074] It should be noted that each component controls the execution of the component through different properties. The property item design will affect the [adapter property information] of the corresponding component in the process definition. For example: RESTful JSON Client component, the property item design is used to configure the request address, request method, character set and Content Type properties to facilitate sending requests.

[0075] The attribute extension unit adds personalized attribute settings for the Adapter component;

[0076] It should be noted that each component not only has common properties to control the execution of the component, but also adds personalized extended property settings for specific components. This design will affect the [adapter advanced settings] of the corresponding component in the process definition.

[0077] The configuration proxy design unit is used to control the communication settings of the component. The configuration proxy design affects the page display items when opening the configuration proxy for each corresponding component in the process definition;

[0078] It should be noted that the configuration proxy settings of each component are designed, and the configuration proxy is used to control the communication-related settings of the component. This design will affect the page display items when opening the configuration proxy for each corresponding component in the process definition.

[0079] The message body design unit is used to design the message processing type of the Adapter component scope;

[0080] Specifically, the message body of the Adapter component scope includes inbound, outbound and response. The design content of the message body includes message category, message version, processing direction and message body structure. A component controls different message bodies and logical rules through message categories. Different versions of the same message category of a component have different message bodies and logical rules. Each scope has a processing direction, which determines the parsing or generation of data. The message body structure is customized by inputting messages, and the message template is fixed for component mapping.

[0081] The rule design unit defines various business rules for the messages received from the system through the UI to perform cleaning and conversion business processing on the messages;

[0082] The table mapping unit is used to map the relationship between the Adapter component and the database table;

[0083] It should be noted that in front-end development, components obtain data from the back-end and display it. At this time, the component's properties (props) and state (state) will be mapped to the back-end data model fields.

[0084] The message template unit is used to define and organize the data transmission format between Adapter components. These message templates are used for API requests and responses, message queues, and communication between microservices.

[0085] The accessory parameter design unit is used to enhance the flexibility and configurability of a component by defining optional and additional parameters. The accessory parameters are used to control the behavior, style, and functionality of a component.

[0086] It should be noted that the principles for designing auxiliary parameters include: flexibility, auxiliary parameters should allow users to customize the behavior and appearance of components according to different needs; simplicity, avoid redundant auxiliary parameters to prevent the use of components from becoming complicated, design commonly used parameters as required parameters, and set seldom used parameters as auxiliary parameters; default values, provide default values ​​for auxiliary parameters so that the component can still work normally when these parameters are not provided; type safety, ensure that the types of auxiliary parameters are clear, and reduce errors during use; clear documentation, provide clear documentation for each auxiliary parameter, including its function, type, default value and example.

[0087] Example 2, reference Figure 4 As shown, the component application UI model is provided with three message processing endpoints and three operation points. The processing endpoints are respectively recorded as input, output and response. The operation points include proxy configuration, exception configuration and operation. When input is performed, the output of the previous processing endpoint is used as the input of the next processing endpoint. Conversely, when responding, the output response of the next processing endpoint is used as the input response of the previous processing endpoint. At the same time, any component of the component application UI model can set the exception handling configuration.

[0088] In the third embodiment, the present invention provides a method for constructing a graphical component model based on a data integration process, which is used to construct the graphical component models of the first and second embodiments. The construction method includes the following steps:

[0089] S1, first create a new Adapter component or maintain an existing Adapter component;

[0090] S2, create or modify component logic proxy;

[0091] S3, set the properties of the component, including configuring the request address, request method, character set, and Content Type;

[0092] S4, expand the attributes of the component;

[0093] S5,design the configuration agent settings for each component;

[0094] S6, design the message body of the component, including message category, message version, processing direction and message body structure;

[0095] S7, design component rules, perform data conversion and data cleaning on the collection in MongoDb through SQL rules, Xpath rules or Java rules, and prepare the message data body for the outbound message;

[0096] Specifically, when designing component rules, in the corresponding rules, SQL rules complete the conversion of message content in MongoDB through SQL data;

[0097] Java rules complete the conversion of message content in mongoDb through rule-constrained code, and also complete external interactive verification of data through code;

[0098] XPath rules process data in the XML message body using XPath syntax.

[0099] S8, design component table mapping, message templates and associated parameters.

[0100] It should be noted that during the processing, the component model uses the following processing flow: Adatper service (input) - Conversion service (data analysis) - Rule service - Conversion service (data generation) - Adapter service (output) to complete the message processing using the parameter configuration in each step, so that the UI of the entire message processing process can be adjusted online in real time and dynamically.

[0101] Finally, it should be noted that the above is only a preferred embodiment of the present invention and is not intended to limit the present invention. Although the present invention has been described in detail with reference to the aforementioned embodiments, it is still possible for those skilled in the art to modify the technical solutions described in the aforementioned embodiments or to make equivalent substitutions for some of the technical features therein. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of the present invention should be included in the protection scope of the present invention.

Claims

1. A graphical component model based on data integration process, characterized in that: The component model includes an adapter component design unit, a logic agent unit, an icon unit, an attribute item design unit, an attribute extension unit, a configuration agent design unit, a message body design unit, a rule design unit, a table mapping unit, a message template unit and an attached parameter design unit; The Adapter component design unit is used to add new Adapter components and maintain existing Adapter components; The logic proxy unit is used for logic processing of the Adapter component; The icon unit is used to display the Adapter component in process design and process monitoring; The attribute item design unit controls the execution of different attributes of the Adapter component through different attribute items; The attribute extension unit adds personalized attribute settings for the Adapter component; The configuration agent design unit is used to control the communication settings of the components; The message body design unit is used for message processing type design in the Adapter component scope; The rule design unit defines various business rules for the messages received from the system through the UI to perform cleaning and conversion business processing on the messages; The table mapping unit is used to map the relationship between the Adapter component and the database table; The message template unit is used to define and organize the data transmission format between Adapter components; The auxiliary parameter design unit is used to enhance the flexibility and configurability of the component by defining optional and additional parameters.

2. According to claim 1, a graphical component model based on data integration process is characterized in that: The component content designed by the Adapter component design unit includes a component list and component basic information.

3. The graphical component model based on data integration process according to claim 2 is characterized in that: Each line of information in the component list represents a component, and the component list is used to add, import and export components.

4. The graphical component model based on data integration process according to claim 2 is characterized in that: The component basic information includes component category, category name, component ID and component name; The component classification is used to find and manage components during process design; The classification name is used for component classification, and components are divided into system components, platform components and ERP components according to different functions; The component ID is used to maintain the uniqueness of the component; The component name marks the component information so that the user can intuitively understand the function of the component.

5. The graphical component model based on data integration process according to claim 4 is characterized in that: The naming of the component ID is composed of the component category and the identifier in the category, and the personalized developed components are uniformly named starting with UDF_.

6. The graphical component model based on data integration process according to claim 1 is characterized in that: When different Adapter components have the same logical processing functions, they use the same logical proxy class.

7. The graphical component model based on data integration process according to claim 1 is characterized in that: The configuration agent design will affect the page display items when the configuration agent is opened for each corresponding component in the process definition.

8. The graphical component model based on data integration process according to claim 1 is characterized in that: The message body of the Adapter component scope includes inbound, outbound and response. The design content of the message body includes message category, message version, processing direction and message body structure. A component controls different message bodies and logical rules of components through message categories. Different versions of the same message category of a component have different message bodies and logical rules. Each scope has a processing direction, which determines the parsing or generation of data. The message body structure is customized by inputting messages, and the message template is fixed for component mapping.

9. A method for constructing a graphical component model based on a data integration process, used to construct the graphical component model according to any one of claims 1 to 8, characterized in that: The construction method comprises the following steps: S1, first create a new Adapter component or maintain an existing Adapter component; S2, create or modify component logic proxy; S3, set the properties of the component, including configuring the request address, request method, character set, and Content Type; S4, expand the attributes of the component; S5,design the configuration agent settings for each component; S6, design the message body of the component, including message category, message version, processing direction and message body structure; S7, design component rules, perform data conversion and data cleaning on the collection in MongoDb through SQL rules, Xpath rules or Java rules, and prepare the message data body for the outbound message; S8, design component table mapping, message templates and associated parameters.

10. A method for constructing a graphical component model based on a data integration process according to claim 9, characterized in that: When the component rules are designed, in the corresponding rules, the SQL rules complete the conversion of the message content in mongodb through SQL data; Java rules complete the conversion of message content in mongoDb through rule-constrained code, and also complete external interactive verification of data through code; XPath rules process data in the XML message body using XPath syntax.

Images