CN113821271A - Method and system for expanding connector of service application integration platform - Google Patents
Method and system for expanding connector of service application integration platform Download PDFInfo
- Publication number
- CN113821271A CN113821271A CN202111080058.8A CN202111080058A CN113821271A CN 113821271 A CN113821271 A CN 113821271A CN 202111080058 A CN202111080058 A CN 202111080058A CN 113821271 A CN113821271 A CN 113821271A
- Authority
- CN
- China
- Prior art keywords
- connector
- template
- data
- integration platform
- connection
- 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
- 230000010354 integration Effects 0.000 title claims abstract description 106
- 238000000034 method Methods 0.000 title claims abstract description 31
- 238000005538 encapsulation Methods 0.000 claims abstract description 29
- 238000006243 chemical reaction Methods 0.000 claims abstract description 10
- 238000004806 packaging method and process Methods 0.000 claims abstract description 6
- 238000011161 development Methods 0.000 claims description 19
- 238000004891 communication Methods 0.000 claims description 6
- 238000005516 engineering process Methods 0.000 claims description 4
- 239000008186 active pharmaceutical agent Substances 0.000 description 7
- 230000018109 developmental process Effects 0.000 description 5
- 230000008569 process Effects 0.000 description 4
- 238000012545 processing Methods 0.000 description 3
- 230000008859 change Effects 0.000 description 2
- 210000001520 comb Anatomy 0.000 description 2
- 238000010276 construction Methods 0.000 description 2
- 230000005540 biological transmission Effects 0.000 description 1
- 230000007547 defect Effects 0.000 description 1
- 238000010586 diagram Methods 0.000 description 1
- 238000002474 experimental method Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000003032 molecular docking Methods 0.000 description 1
- 230000008672 reprogramming Effects 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/445—Program loading or initiating
- G06F9/44505—Configuring for program initiating, e.g. using registry, configuration files
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/54—Interprogram communication
- G06F9/543—User-generated data transfer, e.g. clipboards, dynamic data exchange [DDE], object linking and embedding [OLE]
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Stored Programmes (AREA)
Abstract
The invention relates to a method and a system for expanding a connector of a service application integration platform, wherein the connector is respectively used for connecting an application system and the service application integration platform, and the method comprises the following steps: performing system connection, data integration and data adjustment in a preset attribute configuration template, a connection realization template, a core function template and a data encapsulation module, compiling and packaging programs output by the modules, and uploading the compiled and packaged programs to a registered and customized connector in a service application integration platform; the attribute configuration template is used for configuring the connection information of the connector; a connection implementation template for configuring connection logic of the connector; the core function template is used for configuring the operation function inside the connector; and the data encapsulation module is used for configuring data format conversion logic of the connector. Compared with the prior art, the method and the system can meet various integration scenes of enterprises, are more flexible to implement and wider in application range, can also carry out low-code configuration, and improve the implementation efficiency.
Description
Technical Field
The present invention relates to the field of connector configuration technologies, and in particular, to a method and a system for extending a connector of a service application integration platform.
Background
In recent years, enterprises pay high attention to informatization construction, the informatization construction is penetrated into all aspects of enterprise operation management, and all aspects of enterprise operation management are met by continuously constructing new business applications and tamping business application foundations. However, since these business applications are built in different periods and different teams, different technical platforms, different development methods, different interface standards and different deployment methods are adopted for each business application, which brings a serious challenge and high cost to the integration of the whole IT architecture of the enterprise in the future. Therefore, an iPaaS integration platform is required to be built to solve the problem of integration and communication among different business application systems in an enterprise.
The iPaaS integration platform is an enterprise-level integration platform, and can efficiently realize integration between service applications, wherein the most core functional module is a service application connector, and can be conveniently connected to various application systems (for example, a commonly-used database connector, a file connector, an API connector, an application system connector, and the like) only with abundant connectors.
In various iPaaS integrated platforms at present, only some standard and mainstream connectors are provided, which mainly include: mainstream database connectors (MySQL, Oracle, SQLServer, MongoDB, etc.), API connectors (Restful connectors, WebService connectors, HTTP connectors, etc.), file connectors, FTP connectors, message queue connectors, cache connectors, mainstream commerce suite connectors (SAP connectors, Oracle ERP connectors, etc.), mainstream cloud SaaS application connectors (Salesforce connectors, etc.).
The above platform-standard connectors can be satisfied in most of the integration scenarios of the enterprise, but cannot be well satisfied in some more customized integration requirements, for example:
1) enterprises generally have a plurality of customized development systems, the technical architectures of the systems may be different, the situation that some systems are used in non-mainstream technical architectures exists, and an iPaaS integrated platform does not provide a standard connector;
2) similarly, the bottom database storage used by these custom-developed systems may also be different, and some non-mainstream database situations for the systems may also exist, and the iPaaS integration platform does not provide a standard database connector;
enterprises can purchase some product software, such as an OA system, manufacturers of the product software can provide some integrated SDK packages or APIs at many times, but the SDK packages or APIs provided by different manufacturers are different, and an iPaaS integrated platform cannot provide a standard OA system connector;
with the development of informatization, the trend of cloud SaaS applications will become more and more obvious in the future, in recent years, many enterprises have selected to use cloud SaaS applications in part of business scenes, such as CRM, expense reimbursement scenes and the like, the integration access of various SaaS applications is also important to be considered by the enterprises, and an iPaaS integration platform also cannot provide a standard connector.
Disclosure of Invention
The invention aims to provide a connector expansion method and a connector expansion system for a business application integration platform, which aim to overcome the defects that the connector with the existing platform standard in the prior art can be met in the process of meeting most of integration scenes of enterprises, but cannot be well met in the process of meeting some more customized integration requirements.
The purpose of the invention can be realized by the following technical scheme:
a method for extending a connector of a service application integration platform, wherein the connector is respectively used for connecting an application system and the service application integration platform, and the method comprises the following steps:
receiving external data, performing system connection, data integration and data adjustment in a preset attribute configuration template, a connection realization template, a core function template and a data encapsulation module, compiling and packaging programs output by the attribute configuration template, the connection realization template, the core function template and the data encapsulation module, uploading the compiled and packaged programs to a service application integration platform, and registering a customized connector in the service application integration platform according to the packaged data;
the attribute configuration template is used for configuring the connection information of the connector;
the connection implementation template is used for configuring the connection logic of the connector;
the core function template is used for configuring the operation function of the connector;
and the data encapsulation module is used for configuring data format conversion logic of the connector.
Further, the connection information includes an application system address, an application system user name, and an application system password.
Further, the connection logic of the configuration connector includes a configuration communication protocol, a configuration connection mode and/or a code type of the configuration connection logic.
Further, configuring the operational functionality of the connector includes configuring a desired operational functionality in the connector.
Further, the data format conversion logic is configured to convert a format of data in the application system into a data format of the service application integration platform.
Further, after receiving the packed data, the service application integration platform performs dynamic compilation by using a Maven technology.
Further, the registering customized connector specifically includes: the name of the connector, the classification to which the connector belongs and the enable-disable state of the connector are configured.
Further, the connector extension method further includes: and selecting the configuration data of other connectors which are configured in advance, and locally modifying one or more of the attribute configuration template, the connection realization template, the core function template and the data encapsulation module of the selected other connectors according to the connector configuration required by the current application system to obtain the connector data required by the current application system.
The invention also provides a connector extension system of the service application integration platform, wherein the connector is respectively used for connecting the application system and the service application integration platform, and the system comprises:
the integration platform server is configured to deploy and run the business application integration platform, and a customized connector is registered in the business application integration platform;
the self-development connector is configured to integrate an external application system, performs system connection, data integration and data adjustment in a preset attribute configuration template, a connection realization template, a core function template and a data encapsulation module, packages programs output by the attribute configuration template, the connection realization template, the core function template and the data encapsulation module and uploads the packaged programs to a service application integration platform;
the attribute configuration template is used for configuring the connection information of the connector;
the connection implementation template is used for configuring the connection logic of the connector;
the core function template is used for configuring the operation function of the connector;
the data encapsulation module is used for configuring data format conversion logic of the connector;
the low-code configuration client is configured to select configuration data of other configured connectors from the self-development connectors, locally modify one or more of the attribute configuration template, the connection realization template, the core function template and the data encapsulation module of the selected other connectors according to the configuration of the connectors required by the current application system, acquire connector data required by the current application system, compile and package the connector data through the self-development connectors, and upload the compiled and packaged connector data to the service application integration platform.
Furthermore, the integrated platform server, the self-development connector and the low-code configuration client are all computers, and the integrated platform server, the self-development connector and the low-code configuration client are all in the same communication network.
Compared with the prior art, the invention has the following advantages:
(1) the invention provides an expansion method of a customized connector, which can be used for configuring the connector in a customized manner according to the specific requirements of an application system; for the configuration scheme of the connector, in the prior art, code programming is mostly carried out by writing programs for a single application system, and the program is packaged, and for different application systems, reprogramming is needed, so that the configuration scheme has the advantages of large workload, low efficiency and high cost;
the invention proposes that firstly, a template is adopted to configure a connector, and necessary basic code files are automatically created; then the specific configuration of the connector is divided into an attribute configuration template, a connection realization template, a core function template and a data encapsulation module, and the function modules can be expanded and developed according to a specific demand scene, so that the configuration is more flexible, and the code processing amount can be reduced; if a large number of similar application systems are encountered, if the prior art is adopted, each application system needs to develop a connector independently, but the technical scheme of the invention only needs to adjust the configuration of a functional module according to different points, for example, the address of the application system only needs to modify an attribute configuration template.
(2) The invention can satisfy various integration scenes of enterprises on the whole, and has more flexible realization and wider application range; the system integration can be configured in a low-code mode, so that the implementation efficiency of the system integration is improved, the requirement on personnel is reduced, namely, the requirement on understanding all codes of a program is not needed, and the local connection logic or configuration is modified, so that the enterprise cost is reduced.
(3) The system integration is configured in a low-code mode through the connector, the change of the integration requirement can be completed in a short time, the external change can be responded very quickly, and the self competitiveness of an enterprise is improved.
Drawings
Fig. 1 is a schematic flowchart of a method for extending a connector of a service application integration platform according to an embodiment of the present invention;
fig. 2 is a schematic structural diagram of a connector extension system of a service application integration platform provided in an embodiment of the present invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the embodiments of the present invention clearer, the technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are some, but not all, embodiments of the present invention. The components of embodiments of the present invention generally described and illustrated in the figures herein may be arranged and designed in a wide variety of different configurations.
Thus, the following detailed description of the embodiments of the present invention, presented in the figures, is not intended to limit the scope of the invention, as claimed, but is merely representative of selected embodiments of the invention. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
Example 1
The embodiment provides a connector extension method for a service application integration platform, wherein connectors are respectively used for connecting an application system and the service application integration platform, and the method comprises the following steps:
receiving external data, adjusting the data in a preset attribute configuration template, a connection realization template, a core function template and a data encapsulation module, compiling and packaging the data output by the attribute configuration template, the connection realization template, the core function template and the data encapsulation module, uploading the data to a service application integration platform, and registering a customized connector in the service application integration platform according to the packaged data;
the following describes each template item and the subsequent data processing specifically:
1. template item
Each template project is essentially a plurality of program code templates and is a plurality of basic code files necessary for creating connectors
Specific connector projects (such as OA system connectors) are created based on the template projects, the created connector projects comprise the following functional modules by default, and then the functional modules can be developed in an extension mode according to specific requirement scenarios:
the attribute configuration template is used for configuring the connection information of the connector, and the connection information comprises an application system address, an application system user name and an application system password or other related connection information;
equivalently, based on the attribute configuration template, the configuration items of the added connectors can be expanded, for example, the configuration items of the OA connectors may include: configuration attributes such as an OA system address, an OA system user name and an OA system password;
the connection implementation template is used for configuring the connection logic of the connector, and the connection logic comprises a configuration communication protocol, a configuration connection mode and/or a configuration connection logic code type and the like;
equivalently, based on the connection implementation template, the connection logic of the implementation connector can be expanded and developed, for example, the connection logic of the OA connector can be implemented, and the connection of the OA system can be implemented based on some configuration items of the OA system;
the core function template is used for configuring the operation functions of the connector, and the required operation functions are configured in the connector; the data interface logic may be used for performing interface transmission on data between the application system and the service application integration platform, and the like;
equivalently, based on the template, core functionality in the implementation connector can then be developed according to the specific demand scenario, for example, in an OA connector: acquiring data of a functional module in the OA system, updating the data of the functional module in the OA system, acquiring API operation provided by a standard in the OA system and the like;
the data encapsulation module is used for configuring data format conversion logic of the connector, and the data format conversion logic is used for converting the format of data in the application system into the data format of the service application integration platform;
equivalently, based on the data encapsulation module, after the connector executes the operation, the final returned data format is in accordance with the specification of the iPaaS integration platform, for example, a standard API provided by OA is called in OA connection, the returned XML format is finally converted into the JSON format through the data encapsulation module to be output, and the JSON format is in accordance with the specification of the iPaaS integration platform.
2. Data processing procedure after template configuration
After all data logics of the customized connector are realized, compiling and packaging connector items (for example, packaging the connector items into Jar files), uploading the Jar files to a service application integration platform (in the embodiment, an iPaaS platform) and issuing the Jar files, wherein the issuing can realize a scheme of dynamic compiling and dependence through technologies such as Maven and the like, and realize dependence integration of a code bottom layer;
finally, basic information such as the name of the custom-developed connector, the category of the connector, the start/stop state of the connector and the like is registered in an service application integration platform (iPaaS platform), and then the custom-developed connector can be selected and used in the iPaaS integration platform.
In addition, after the solution proposed in this embodiment is adopted, the following connector configuration method may be further included: and selecting the configuration data of other connectors which are configured in advance, and locally modifying one or more of the attribute configuration template, the connection realization template, the core function template and the data encapsulation module of the selected other connectors according to the connector configuration required by the current application system to obtain the connector data required by the current application system.
As shown in fig. 2, this embodiment further provides a connector extension system of a service application integration platform, where the connectors are respectively used to connect an application system and the service application integration platform, and the system includes:
1) the integration platform server is configured to deploy and run a business application integration platform, and a customized connector is registered in the business application integration platform;
the integration platform server side at least comprises a computer server used for deploying the service application integration platform;
2) the self-development connector is configured to acquire external data, adjust the data in a preset attribute configuration template, a connection realization template, a core function template and a data encapsulation module, compile and package data output by the attribute configuration template, the connection realization template, the core function template and the data encapsulation module and upload the compiled and packaged data to a service application integration platform;
the attribute configuration template is used for configuring the connection information of the connector;
a connection implementation template for configuring connection logic of the connector;
the core function template is used for configuring data docking logic of the connector;
the data encapsulation module is used for configuring data format conversion logic of the connector;
the self-development connector at least comprises a development computer, is provided with a development environment and is used for expanding and developing the customized connector, and can be connected with the service application integration platform server through a network for publishing;
3) the low-code configuration client is configured to select configuration data of other configured connectors from the self-development connectors, locally modify one or more of attribute configuration templates, connection realization templates, core function templates and data encapsulation modules of the selected other connectors according to the configuration of the connectors required by the current application system, acquire connector data required by the current application system, compile and package the connector data through the self-development connectors, and upload the compiled and packaged connector data to the service application integration platform;
the low-code configuration client comprises at least one computer, and is required to be in network intercommunication with the iPaaS integration platform server for configuring the integration scene by using the low-code of the customized connector.
In the embodiment, the steps for implementing the customization process are described in detail below in the case of customizing the connector on the iPaaS integration platform.
Example 1 (database connector)
In step 100, a user analyzes specific system integration requirements and combs general system integration scenes and schemes;
in step 101, according to the scenario and the scheme combed in step 100, it is determined whether a standard connector of an iPaaS integration platform can meet the integration requirement, and since the iPaaS integration platform provides a standard database connector, the connector does not need to be customized;
in step 110, the system is integrated with low code configuration directly in the iPaaS integration platform using standard database connectors.
Example 2(OA system connector)
As shown in fig. 1, in step 100, the user analyzes specific system integration requirements and combs general system integration scenarios and schemes;
in step 101, according to the scenario and the scheme combed in step 100, it is determined whether a standard connector of the iPaaS integration platform can meet the integration requirement, and since different enterprises use different OA systems, the iPaaS integration platform does not provide a standard OA system connector, and thus the OA system connector needs to be customized;
in step 102, a technical developer creates a connector project of the OA system based on a connector template provided by the iPaaS integration platform;
in step 103, according to the configuration requirement of the OA system, customizing and developing the configuration items of the OA system connector, including the configuration items of the OA system connection address, the OA system user name, the OA system password and the like;
in step 104, according to the relevant attributes configured in step 103, customizing and developing the connection logic of the OA system, so as to enable the OA system to be accessed from the iPaaS integration platform;
in step 105, this is the most core and the most complex process of the customized connector, and according to the specific integration scenario, the core function in the OA system connector is customized and developed, for example, data of the OA system function is acquired, data of the OA system function is updated, a standard API provided by the OA system is called, and the like;
in step 106, the data returned by the core function realized in step 105 is converted into a standard format required by an iPaaS integrated platform;
in step 107, after the steps 102-106, the customization of the OA system connector is completed, and then the connector item is compiled and packaged to generate a corresponding deployment file, such as a Jar package;
in step 108, the deployment file generated in step 107 is uploaded to an iPaaS integration platform and released, so that the dependence of a code bottom layer is realized;
in step 109, the name, the belonging category, and the like of the OA system connector are configured in the iPaaS integration platform, and the registration of the OA system connector is completed;
in step 110, OA system integration is configured in low code using OA system connectors directly in the iPaaS integration platform.
The foregoing detailed description of the preferred embodiments of the invention has been presented. It should be understood that numerous modifications and variations could be devised by those skilled in the art in light of the present teachings without departing from the inventive concepts. Therefore, the technical solutions available to those skilled in the art through logic analysis, reasoning and limited experiments based on the prior art according to the concept of the present invention should be within the scope of protection defined by the claims.
Claims (10)
1. A method for extending a connector of a service application integration platform, wherein the connector is respectively used for connecting an application system and the service application integration platform, the method comprises the following steps:
receiving external data, performing system connection, data integration and data adjustment in a preset attribute configuration template, a connection realization template, a core function template and a data encapsulation module, compiling and packaging programs output by the attribute configuration template, the connection realization template, the core function template and the data encapsulation module, uploading the compiled and packaged programs to a service application integration platform, and registering a customized connector in the service application integration platform according to the packaged data;
the attribute configuration template is used for configuring the connection information of the connector;
the connection implementation template is used for configuring the connection logic of the connector;
the core function template is used for configuring the operation function of the connector;
and the data encapsulation module is used for configuring data format conversion logic of the connector.
2. The method as claimed in claim 1, wherein the connection information includes an application system address, an application system user name and an application system password.
3. The method according to claim 1, wherein the connection logic for configuring the connector comprises configuring a communication protocol, configuring a connection mode and/or configuring a code type of the connection logic.
4. The method of claim 1, wherein configuring the operational functionality of the connector comprises configuring the desired operational functionality in the connector.
5. The method of claim 1, wherein the data format conversion logic is configured to convert a format of data in the application system into a data format of the service application integration platform.
6. The method as claimed in claim 1, wherein the service application integration platform performs dynamic compilation by using a Maven technology after receiving the packed data.
7. The method for extending a connector of a service application integration platform according to claim 1, wherein the registered customized connector specifically comprises: the name of the connector, the classification to which the connector belongs and the enable-disable state of the connector are configured.
8. The connector extension method for service application integration platform according to claim 1, further comprising: and selecting the configuration data of other connectors which are configured in advance, and locally modifying one or more of the attribute configuration template, the connection realization template, the core function template and the data encapsulation module of the selected other connectors according to the connector configuration required by the current application system to obtain the connector data required by the current application system.
9. A connector extension system of a service application integration platform, wherein the connectors are respectively used for connecting an application system and the service application integration platform, and the system comprises:
the integration platform server is configured to deploy and run the business application integration platform, and a customized connector is registered in the business application integration platform;
the self-development connector is configured to integrate an external application system, performs system connection, data integration and data adjustment in a preset attribute configuration template, a connection realization template, a core function template and a data encapsulation module, packages programs output by the attribute configuration template, the connection realization template, the core function template and the data encapsulation module and uploads the packaged programs to a service application integration platform;
the attribute configuration template is used for configuring the connection information of the connector;
the connection implementation template is used for configuring the connection logic of the connector;
the core function template is used for configuring the operation function of the connector;
the data encapsulation module is used for configuring data format conversion logic of the connector;
the low-code configuration client is configured to select configuration data of other configured connectors from the self-development connectors, locally modify one or more of the attribute configuration template, the connection realization template, the core function template and the data encapsulation module of the selected other connectors according to the configuration of the connectors required by the current application system, acquire connector data required by the current application system, compile and package the connector data through the self-development connectors, and upload the compiled and packaged connector data to the service application integration platform.
10. The system of claim 9, wherein the service end of the integration platform, the self-development connector and the low-code configuration client are all computers, and the service end of the integration platform, the self-development connector and the low-code configuration client are all in the same communication network.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111080058.8A CN113821271A (en) | 2021-09-15 | 2021-09-15 | Method and system for expanding connector of service application integration platform |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111080058.8A CN113821271A (en) | 2021-09-15 | 2021-09-15 | Method and system for expanding connector of service application integration platform |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN113821271A true CN113821271A (en) | 2021-12-21 |
Family
ID=78922538
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202111080058.8A Pending CN113821271A (en) | 2021-09-15 | 2021-09-15 | Method and system for expanding connector of service application integration platform |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113821271A (en) |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108282519A (en) * | 2017-12-29 | 2018-07-13 | 深圳中兴网信科技有限公司 | Interface realizing method, Interface for System based on middleware |
| CN112068808A (en) * | 2020-08-13 | 2020-12-11 | 中国航空无线电电子研究所 | General processing system for multi-bus data conversion of avionics system |
| CN112114980A (en) * | 2020-08-31 | 2020-12-22 | 深圳市紫金支点技术股份有限公司 | Middleware implementation method, intelligent terminal and storage medium supporting cross-platform service |
| CN112464595A (en) * | 2020-12-14 | 2021-03-09 | 中国电子科技集团公司第十四研究所 | Cross-platform communication middleware visual modeling method |
-
2021
- 2021-09-15 CN CN202111080058.8A patent/CN113821271A/en active Pending
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108282519A (en) * | 2017-12-29 | 2018-07-13 | 深圳中兴网信科技有限公司 | Interface realizing method, Interface for System based on middleware |
| CN112068808A (en) * | 2020-08-13 | 2020-12-11 | 中国航空无线电电子研究所 | General processing system for multi-bus data conversion of avionics system |
| CN112114980A (en) * | 2020-08-31 | 2020-12-22 | 深圳市紫金支点技术股份有限公司 | Middleware implementation method, intelligent terminal and storage medium supporting cross-platform service |
| CN112464595A (en) * | 2020-12-14 | 2021-03-09 | 中国电子科技集团公司第十四研究所 | Cross-platform communication middleware visual modeling method |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11948003B2 (en) | System and method for automated production and deployment of packaged AI solutions | |
| CN107370786B (en) | General information management system based on micro-service architecture | |
| US20200004598A1 (en) | Server kit and methods therefor | |
| US11922564B2 (en) | Generative content system that supports location-based services and methods therefor | |
| US20200004759A1 (en) | Generative content system and methods therefor | |
| CN110825362A (en) | Low-code application software development system and method | |
| KR101314949B1 (en) | Integration environment generator | |
| CN114115852A (en) | Visual service arranging method, device, equipment and medium | |
| CN111147555A (en) | Heterogeneous resource mixed arrangement method | |
| CN113094028B (en) | Windows desktop program development system, method and related components | |
| CN110764752A (en) | System and method for realizing graphical service arrangement of Restful service based on micro-service architecture | |
| CN113467972B (en) | Communication interface construction method and device, computer equipment and storage medium | |
| CN112199164A (en) | Method for ensuring container mirror image consistency | |
| CN114217887A (en) | Micro-service arranging method, micro-service executing method, micro-service arranging device and micro-service executing server | |
| CN114912897A (en) | Workflow execution method, workflow arrangement method and electronic equipment | |
| CN102375743B (en) | SOA(Service-Oriented Architecture) system development method based on model and template | |
| CN111427576A (en) | Method, device, storage medium and terminal for configuring application program interface | |
| CN112558930B (en) | Software generation system and method for container service | |
| CN109388406A (en) | Convert method and device, the storage medium, electronic device of java code | |
| CN115202663A (en) | Data processing method, device and storage medium | |
| CN111683005A (en) | Internet of things intelligent gateway equipment and construction method thereof | |
| CN113821271A (en) | Method and system for expanding connector of service application integration platform | |
| Miranda et al. | Enough about standardization, let's build cloud applications | |
| CN114237760B (en) | Method for packaging industrial mechanism model into container mirror image and publishing web service | |
| CN109857374A (en) | The development approach and device of mobile application |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |