Enterprise network internal heterogeneous system data integration method

Abstract

The invention relates to the field of heterogeneous system data interaction and utilization, in particular to an enterprise network internal heterogeneous system data integration method. The method comprises the following steps: an application system applies for an integration service and a time token to an integration center; after the integration center system receives the time token, comparison is carried out according to the latest data storage time of the integration center, and the size of a timestamp to be requested is judged according to a timestamp value set by the integration center; if the timestamp is smaller than the time token, the integration center switches over the service, and the integration center does not request data, the service can be switched to the target system, the integration service is provided through the target system, and the communication stability is improved; after the target application system prepares data, the standard integration service of the integration center is called, and the enterprise integration data transmission requirement is met; the target application system provides a service, responds to a request of the source application system and returns correct data; and the application system receives data returned by the target system, and returns a state value to the target application system to provide service after calling is finished.

Description

Technical Field

[0001] The present invention relates to the field of heterogeneous system data interaction and utilization, and in particular to a heterogeneous system data integration method within an enterprise network. Background Art

[0002] There are multiple application systems in the enterprise network, which were built at different times and for different applications. In this network environment, data interaction and utilization are difficult. Different system bases and data organization methods make data interaction and utilization extremely difficult, which often leads to inconsistent data after data integration. Multiple parties need to implement similar functions, which reduces efficiency. It is necessary to solve the stable communication and efficient sharing between heterogeneous systems. Therefore, the above two problems must be solved for the interaction and utilization of the enterprise network within the enterprise.

[0003] There are many existing methods for data interaction and utilization. Common methods include database synchronization, microservices, data buses, etc. For the needs of data interaction and utilization within enterprise networks, data integration methods usually have the following problems: a) Data interaction lacks sharing. When different systems have the same data needs, multiple similar data services need to be provided separately for different systems, and service sharing is impossible; b) Lack of redundancy and stability. When the systems are synchronized, the available status of each system is inconsistent, resulting in inconsistent data and impractical use; c) It is difficult to balance real-time and access efficiency. If real-time calculations are performed, data access efficiency may be affected; e) Data conversion is not convenient enough, because the construction time of each system is different, and the data expression and constraints are different in different systems, which makes data difficult to share and use. Summary of the invention

[0004] Purpose of the invention: A method for integrating internal data of an enterprise network is proposed to realize the interaction and utilization of internal data of the enterprise network, and to improve the communication stability and data sharing capability of heterogeneous systems.

[0005] Technical solution:

[0006] A method for transmitting data within an enterprise network is provided, comprising:

[0007] The application system applies for integration services and time tokens to the integration center. After receiving the time token, the integration center system compares it with the latest stored data time of the integration center and determines the size of the timestamp to be requested based on the timestamp value set by the integration center.

[0008] If the timestamp is less than the time token, the integration center transfers the service. If the integration center has no request data, the service can be transferred to the target system, and the integration service can be provided through the target system to increase communication stability.

[0009] After the target application system prepares the data, it calls the standard integration service of the integration center to meet the enterprise integration data transmission requirements;

[0010] The target application system provides services, responds to requests from the source application system, and returns correct data.

[0011] The application system receives the data returned by the target system, and returns the status value to the target application system to provide services after the call is completed.

[0012] Furthermore, after the call is completed and the status value is returned to the target application system to provide services, the method further includes:

[0013] After receiving the target system end status value, the target application system calls the integration center to receive data service and synchronizes the latest data value to the integration center data center;

[0014] The integration center receives the service, obtains the original integration token through authentication, and synchronizes the data value to the integration center data center.

[0015] Furthermore, the method further comprises:

[0016] If the timestamp is greater than the time token, the integration center calls the asynchronous service based on the request characteristics and provides standard integration requirement services if it is a large data volume request.

[0017] Furthermore, the method further comprises:

[0018] In the enterprise integration center system on the integration center server of the enterprise network, register the system to be connected to the enterprise integration and assign the integration unique identification ID;

[0019] The application system accessing the integration center is ready to provide integrated services, meets the integration center access specifications, and submits a request to access the integration center;

[0020] The integration center tests that the integrated service meets the requirements for registering the integrated service;

[0021] The integration center sets up integrated data and sets up automatic data conversion matrix and data matrix according to the data requirements of different application systems.

[0022] The integration center standardizes and converts multi-system reference data and provides standard services.

[0023] The application system applies for integration services and generates a time token, and submits the request to the integration center.

[0024] Furthermore, the integration center provides intelligent data conversion programs and provides standard verification, encryption, and sharable integration services.

[0025] Furthermore, the integration center tests that the integrated service meets the requirements for registering the integrated service, including:

[0026] Test active and passive services to ensure that the services are available and meet the requirements. Then register the integrated service and assign a service ID, which contains the registration system information.

[0027] Furthermore, the time token includes registration system information, registration service information, time synchronization information of request data, conversion information, and user information.

[0028] Beneficial effects:

[0029] 1) The present invention manages the service registration and data registration of the integration center, establishes the association between services and data, simplifies the management of integrated services and ensures data security, and the data source cannot be accessed by system-irrelevant services. 2) A data matrix and a corresponding data conversion matrix are established, and one-to-one management is established to automatically manage data references and format conversions to meet the use requirements and rule requirements of heterogeneous systems. 3) By using one-time time tokens to serve data and quickly retrieve data response status, invalid operations are avoided and a basis for transfer services is provided. 4) After the target application system provides services, the receiving service of the integration center is called back, and the asynchronous synchronization data and data registration information are sent to the integration center, realizing the repair of the data path, thereby ensuring the stability of data transmission and communication and access efficiency.

[0030] The integration method provided by the present invention is simple to implement and easy to deploy. It can be used as a system and provide an interactive interface to provide data transmission services for other business systems. The method can also be directly used to build an integrated system. The method provides a means for the control of internal integration standardization of an enterprise, provides standardized data integration for the enterprise's data when it flows on the network, and meets the security, stability and performance guarantees. The data transmission business within the enterprise is integrated to improve the overall data sharing and utilization of the enterprise information system. BRIEF DESCRIPTION OF THE DRAWINGS

[0031] Figure 1 The present invention is a flow chart of a method for integrating heterogeneous system data within an enterprise network. DETAILED DESCRIPTION

[0032] The enterprise integration center system is built through the Web service model. The heterogeneous system data integration method adopts the dual response of the integration center and the application system to achieve the effect of dual-machine hot standby. The integration service registration and data registration are separated to ensure data security and simplify data management. The integration center standard service tool is built to enable the application system to focus on the business implementation scenario. The accessibility and consistency of data integration are achieved through the integration status token control. Figure 1 As shown, the integration process is divided into the following steps:

[0033] The first step is to access the integration center source list in the enterprise integration center system on the integration center server of the enterprise network, register the system to be connected to the enterprise integration, and assign the integration unique identification ID. The business system uses this interface to set the receiving user and integration identification of the data file to be transferred.

[0034] In the second step, the application system connected to the integration center is ready to provide integrated services. It can inject return value types and other information into the token to meet the integration center access specifications, interface specifications and data specifications, and submit a request to access the integration center.

[0035] In the third step, the integration center tests the application system integration services that need to be connected, including active services and passive services, to ensure that the services are available. Once they meet the requirements, the integration services are registered and a service ID is assigned, which contains the registration system information.

[0036] Step 4: The integration center sets up the integrated data registration tool, and sets up the automatic data conversion matrix and data matrix according to the data requirements of different application systems. The data matrix includes the application system and data dimensions. The data conversion matrix includes the original data format of the application system data source and the target format of the target application system data source, as well as the conversion tool.

[0037] The fifth step is that the integration center standardizes and converts the referenced data of multiple systems and provides standard services. The integration center provides intelligent data conversion tools and standard verification, encryption, user organization, file storage and other sharable public services. The integration center provides standard services for application systems that apply for services. After the application system calls the public services, it can meet the network data transmission requirements and data reference requirements.

[0038] Step 6: While logged in, the application system applies for integration services and generates a time token, submitting the request to the integration center. The time token may include multiple information, such as registration system information, registration service information, time synchronization information of the requested data, conversion information, user information, etc.

[0039] In the seventh step, the application system applies for the integration service and time token to the integration center. After receiving the time token, the integration center system compares it with the latest stored data time of the integration center and determines the size of the timestamp to be requested based on the timestamp value set by the integration center. If the timestamp is smaller than the time token, the process proceeds to step nine. If the timestamp is larger than the time token, the process proceeds to step eight.

[0040] In the eighth step, the integration center calls asynchronous services based on the request characteristics, and provides standard integration requirement services if it is a large data volume request. Large data volume requests can be identified during registration. Big data includes two types, one is a large number of data records, and the other is unstructured data. The integration center provides standard tools and responds to requests in an asynchronous manner. The second token of the integration center is updated and encapsulated into the header of the returned data block message, which can realize the application system service callback. When the integration system service is called back, the data exchange system executes the token service related to this call.

[0041] The ninth step is to transfer the service from the integration center. If the integration center does not have the request data, it can transfer the service to the target system and provide integrated services through the target system to increase communication stability. If the integration center does not obtain the request data normally according to the time token information, it will jump the service to the target application system through internal tools.

[0042] In the tenth step, the target application system receives the service request, accepts the application system ID, application system service request address, requesting user, etc., and calculates the request data.

[0043] In the eleventh step, the target application system provides services, responds to the source application system request, and returns the correct data. It obtains the requested service information, executes the request, and responds on behalf of the integration center service. It is completely black-box and has no intervention on the requester, meeting the enterprise integration data delivery requirements in a timely manner.

[0044] In the twelfth step, the application system receives the data returned by the target system, and returns the status value to the target application system to provide services after the call is completed. Return the call completion status.

[0045] In the thirteenth step, after receiving the target system end status value, the target application system calls the integration center to receive the data service and synchronizes the latest data value to the integration center data center.

[0046] In the fourteenth step, the integration center receives the service, obtains the original integration token, passes the authentication, and synchronizes the data value to the integration center data center. The integrated system data center failed to respond to the request this time because the system failed to provide the requested data. The target system synchronizes the data to the integrated system data again, updates the latest data, and can meet the next application system request, achieving the system communication stability requirements.

[0047] The heterogeneous system data integration method adopts the dual response mode of the integration center and the application system to achieve the effect of dual-machine hot standby, adopts the separation mode of integration service registration and data registration to ensure data security and simplify data management, builds standard service tools for the integration center, and the application system focuses on business implementation scenarios, and achieves the accessibility and consistency of data integration through integrated status token control.

[0048] The system integrates the standard public tools and token generation tools of the system center, which do not require frequent upgrades. The system uses the construction mode of Web applications to support rapid upgrades. This implementation method can adapt to the characteristics of rapid changes in production line scenarios.

[0049] Embodiment 1:

[0050] Taking the procurement management platform and financial system or archive system of a research institute as an example, the research institute needs to transfer procurement data to the application system through the enterprise network, so the research institute deploys the procurement management platform to be responsible for the procurement data publishing service of data file publishing, and builds and registers multiple business systems in the integrated system center, and uses the java application framework to build data integration services and tools for data integration according to the method of the present invention, and develops a method that can meet the implementation scheme of the present invention and provides it to various applications. Now, take this scenario as an example to illustrate the implementation process of the method:

[0051] In the first step, in the financial system data integration system, the purchaser submits the purchase data, and the purchase data request specifies the purchase system or archive system that needs to receive the data according to the project requirements. After completing the data sending process, the financial data publishing service sends the data token and data to the integration system service that needs to receive the design data. The token contains verification information, provides data import and interface, and receives the published purchase data in the data center. The data is stored in the data matrix definition, and the integration center system authorizes the systems and services that can access this data.

[0052] In the second step, the service specified by the financial system that needs to receive the procurement data uses the pre-defined interface service to receive the procurement data of the integrated system, and obtains the procurement data from the integration center system through authenticated users and encryption methods.

[0053] The third step is when a failure occurs during data synchronization, and the integrated system data center fails to correctly synchronize procurement data. The integrated center system calls the common jump method and encryption method to send the target service request to the procurement management platform. The procurement system checks the legitimacy of the request.

[0054] The fourth step is that after the procurement management platform calculates the results, it directly calls the financial system service that the integrated system jumps to and obtains the return value status.

[0055] In the fifth step, after the procurement management platform obtains the callback status token, it calls the integrated system center write service and transmits the calculation results to the integrated system data center.

[0056] In the sixth step, after the procurement system requests the platform to obtain the callback status, it calls the integrated system center write service and transmits the calculation results to the integrated system data center.

Claims

1. A method for transmitting data within an enterprise network, characterized in that: include: The application system applies for integration services and time tokens to the integration center. After receiving the time token, the integration center system compares it with the latest stored data time of the integration center and determines the size of the timestamp to be requested based on the timestamp value set by the integration center. If the timestamp is less than the time token, the integration center transfers the service. If the integration center has no request data, the service can be transferred to the target system, and the integrated service can be provided through the target system to increase communication stability; After the target application system prepares the data, it calls the standard integration service of the integration center to meet the enterprise integration data transmission requirements; The target application system provides services, responds to requests from the source application system, and returns correct data; The application system receives the data returned by the target system, and returns the status value to the target application system to provide services after the call is completed.

2. The method according to claim 1, characterized in that After the call is completed and the status value is returned to the target application system to provide services, the method further includes: After receiving the target system end status value, the target application system calls the integration center to receive data service and synchronizes the latest data value to the integration center data center; The integration center receives the service, obtains the original integration token through authentication, and synchronizes the data value to the integration center data center.

3. The method according to claim 1, characterized in that The method further comprises: If the timestamp is greater than the time token, the integration center calls the asynchronous service based on the request characteristics and provides standard integration requirement services if it is a large data volume request.

4. The method according to claim 1, characterized in that: The method further comprises: In the enterprise integration center system on the integration center server of the enterprise network, register the system to be connected to the enterprise integration and assign the integration unique identification ID; The application system accessing the integration center is ready to provide integrated services, meets the integration center access specifications, and submits a request to access the integration center; The integration center tests that the integrated service meets the requirements for registering the integrated service; The integration center sets up integrated data and sets up automatic data conversion matrix and data matrix according to the data requirements of different application systems; The integration center standardizes and converts multi-system reference data and provides standard services; The application system applies for integration services and generates a time token, and submits the request to the integration center.

5. The method according to claim 4, characterized in that The integration center provides intelligent data conversion programs and provides standard authentication, encryption, and sharable integration services.

6. The method according to claim 4, characterized in that The Integration Center tests that the integrated service meets the requirements for registering the integrated service, including: Test active and passive services to ensure that the services are available and meet the requirements. Then register the integrated service and assign a service ID, which contains the registration system information.

7. The method according to claim 1, characterized in that The time token includes registration system information, registration service information, time synchronization information of request data, conversion information, and user information.

8. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the method according to any one of claims 1 to 7 is implemented.

Images