Interface management method, interface governance system, and storage medium for storing computer-executable program for interface management

Abstract

One embodiment of the present invention provides an interface management method comprising the steps of: registering, on an interface governance platform, information related to an interface related to an application solution of a computing system; receiving data related to the interface from the computing system through the interface governance platform; and, on the basis of the registered information related to the interface, monitoring the received data related to the interface or managing the computing system.

Description

Interface management method, interface governance system, and storage medium storing a computer-executable program for managing the interface

[0001] The following disclosure relates to an interface management method, an interface governance system, and a storage medium storing a computer-executable program for managing an interface.

[0002]

[0003] Based on computing systems, various information exchanges are taking place between companies, or between numerous application systems within a company.

[0004] While computing systems are increasingly cloud-based, there are also a significant number of on-premise systems within companies. The transition from traditional on-premise systems to cloud systems is rapidly occurring.

[0005] When the types of computers are different in a heterogeneous computing system, a system can be built that can interface with the connected computing systems through interfaces such as APIs (Application Programming Interfaces).

[0006] However, these system linkage systems had problems in that their application principles, implementation methods, and management standards could differ from each other and were difficult to monitor.

[0007] Identifying problems or failures through administrators in these system linkages can be time-consuming and difficult to manage as it can cause problems with the currently running computing system, making it difficult to verify solutions.

[0008] In addition, as the computing system resources within the company increase, the above problems may recur due to the interface with the existing computing system, making it difficult to take accurate and reliable measures for these recurring problems.

[0009]

[0010] The disclosed embodiment is intended to solve the above problems, and provides a method for managing the interface of computing systems, an interface governance system, and a storage medium for storing a computer-executable program for managing the interface of computer systems, which can easily manage the interface of interconnected computing systems and easily verify the accuracy of the management results.

[0011] The disclosed embodiment provides a method for managing an interface of computing systems, an interface governance system, and a storage medium storing a computer-executable program for managing the interface of computer systems, for developing an interface for seamlessly transmitting and receiving data between different computing systems.

[0012] The disclosed embodiment provides a method for managing the interface of computing systems, an interface governance system, and a storage medium storing a computer-executable program for managing the interface of computer systems, which can quickly identify and easily manage failures between connected computing systems.

[0013] The disclosed embodiment provides a method for managing an interface of computing systems capable of accurately and reliably handling repetitive failures of connected computing systems, an interface governance system, and a storage medium storing a computer-executable program for managing the interface of computer systems.

[0014] The disclosed embodiment provides a method for managing an interface capable of efficiently performing interface design, construction, management, operation and maintenance, an interface governance system, and a storage medium storing a computer-executable program for managing interfaces of computer systems.

[0015]

[0016] The disclosed embodiment provides an interface management method, including the steps of: registering interface-related information related to an application solution of a computing system in an interface governance platform; receiving data related to the interface from the computing system through the interface governance platform, wherein the data related to the interface includes log data; and monitoring the received interface-related data or managing the computing system based on the registered interface-related information; wherein the monitoring or managing step includes: generating work-related interface monitoring information from the log data based on pre-stored interface-related reference information; and providing the work-related interface monitoring information through a user interface.

[0017] The above monitoring or managing step includes: a step of registering reference information of an interface related to an application solution of the computing system; a step of generating interface identification information based on the reference information of the interface; and a step of providing a definition document for constructing the interface.

[0018] The above monitoring or managing step includes: providing a user interface (UI) for managing an interface related to an application solution of the computing system; verifying the authority of a user accessing the user interface; and requesting development of the interface in response to an interface application request from the user.

[0019] The above monitoring or managing step includes a step of providing a screen for creating a mapping definition for interface creation based on reference information of a stored interface; and a step of creating the interface based on the mapping definition and the reference information.

[0020] The receiving step includes: a step of obtaining collector setting information set by a user input; and a step of receiving log data for at least one step included in an interface-related process of the integrated solution using a log collector selected based on the obtained collector setting information; and the monitoring or managing step includes a step of performing computing system monitoring using the collected log data.

[0021] The step of monitoring or managing includes a step of generating at least one of monitoring information or management setting information corresponding to a business manager based on the log data; and a step of providing at least one of the monitoring information or management setting information through a user interface.

[0022] The step of monitoring or managing includes a step of detecting a failure of at least one of the computing system or interface from the log data based on predefined failure determination criteria information; and a step of providing at least one of failure information or a failure action guide according to the detected failure.

[0023] The above monitoring or managing step includes: a step of detecting a failure occurring through an interface of the computing system; a step of applying preset notification rules and templates to the detected failure; and a step of transmitting a notification for a failure to which the preset notification rules and templates are applied.

[0024] The above monitoring or managing step includes, when a failure of the computing system is detected, a step of providing a failure handling guide based on failure information about the detected failure; a step of handling the failure based on the failure handling guide; and a step of registering the details of the action taken for the handled failure and the evaluation details of the failure handling guide.

[0025] The step of monitoring or managing includes: a step of acquiring at least one object for an interface service component of the integrated solution; and a step of providing a linkage service for the integrated solution based on at least one object for the interface service component.

[0026] The receiving step includes a step of receiving monitoring data for a computing system from a distributed agent adapter that provides a distributed interface solution different from the interface provided by an integrated solution installed on at least one computing system among an on-premise computing system and a cloud computing system; and the monitoring or managing step includes a step of monitoring the at least one computing system using the received monitoring data; wherein the distributed agent adapter transmits a message between a first computing system and a second computing system that are linked with the integrated solution.

[0027] The disclosed embodiment provides an interface governance system, comprising: a database for storing data; and a processor for processing the data, wherein the processor registers interface-related information related to an application solution of a computing system in an interface governance platform, receives data related to the interface from the computing system through the interface governance platform, wherein the data related to the interface includes log data, and generates work-related interface monitoring information from the log data based on pre-stored interface-related reference information, and provides the work-related interface monitoring information through a user interface.

[0028] The disclosed embodiment provides a computer-executable program for managing an interface, which performs the steps of: registering interface-related information related to an application solution of a computing system in an interface governance platform; receiving data related to the interface from the computing system through the interface governance platform; wherein the data related to the interface includes log data; and generating work-related interface monitoring information from the log data based on pre-stored interface-related reference information; and providing the work-related interface monitoring information through a user interface.

[0029]

[0030] According to the disclosed embodiment, by constructing an interface connecting computing systems, data can be easily transmitted and received between different computing systems.

[0031] According to the disclosed embodiment, it is possible to easily manage the interfaces of interconnected computing systems and easily verify the accuracy of the management results.

[0032] According to the disclosed embodiment, failures between interconnected computing systems can be quickly identified and easily managed.

[0033] According to the disclosed embodiment, recurring failures between interconnected computing systems can be accurately and reliably addressed.

[0034] According to the disclosed embodiment, interface design, construction, management, operation and maintenance can be performed efficiently.

[0035]

[0036] Figure 1 is a conceptual diagram of an interface governance system according to an embodiment.

[0037] Figure 2 is a detailed diagram illustrating one embodiment of the interface governance platform mentioned above.

[0038] Figure 3 is a conceptual diagram illustrating an architecture for managing the interface of a computing system using the interface governance platform exemplified above.

[0039] Figure 4 is a conceptual diagram illustrating examples of functions of a distributed agent adapter according to an embodiment.

[0040] FIG. 5 is a diagram disclosing an example of managing interface-related data transmitted from a computing system based on an interface governance platform according to an embodiment.

[0041] FIG. 6 is a diagram disclosing an example of a method for managing an interface of a computing system according to an embodiment.

[0042] Figure 7 is a diagram disclosing the interface governance platform of the present invention.

[0043] Figure 8 is a drawing disclosing the reference information management module of the present invention.

[0044] FIG. 9 is a drawing showing a user interface (UI) screen provided by the interface management method of the present invention.

[0045] FIG. 10 is a drawing showing a user interface (UI) screen provided by the interface management method of the present invention.

[0046] FIG. 11 is a drawing showing a user interface (UI) screen for requesting an interface provided by the interface management method of the present invention.

[0047] Figure 12 is a drawing disclosing an interface definition template related to the present invention.

[0048] Figure 13 is a flowchart disclosing an interface management method of the present invention.

[0049] Figure 14 is a diagram showing an interface governance platform of the present invention.

[0050] Figure 15 is a drawing disclosing the life cycle management module of the present invention.

[0051] Figure 16 is a drawing illustrating the life cycle management process of the interface of the present invention.

[0052] Figure 17 is a drawing showing a user interface (UI) screen provided by the interface management method of the present invention.

[0053] FIG. 18 is a drawing showing a user interface (UI) screen provided by the interface management method of the present invention.

[0054] Figure 19 is a flowchart disclosing an interface management method of the present invention.

[0055] Figure 20 is a drawing that discloses the interface governance platform of the present invention.

[0056] Figure 21 is a drawing disclosing a specification definition module of the present invention.

[0057] Figure 22 is a drawing disclosing the development automation module of the present invention.

[0058] Figure 23 is a drawing showing an interface mapping definition of the present invention.

[0059] Figure 24 is a drawing showing reference information stored in the interface information storage of the present invention.

[0060] Figure 25 is a drawing showing information on objects for each interface service component of the present invention.

[0061] Figure 26 is a flowchart disclosing an interface management method of the present invention.

[0062] FIG. 27 is a diagram showing an example of an interface governance system collecting log data according to an embodiment.

[0063] FIG. 28 is a diagram disclosing an example of generating log data for at least one step included in an interface-related process according to an embodiment.

[0064] FIG. 29 is a drawing disclosing an example of a user interface (UI) for collector connection information according to an embodiment.

[0065] FIG. 30 is a drawing disclosing an example of a user interface (UI) for collector performance information according to an embodiment.

[0066] Figure 31 is a flowchart showing an example of an interface management method according to an embodiment for collecting log data.

[0067] FIG. 32 is a diagram disclosing an example of an interface governance system according to an embodiment providing interface monitoring information.

[0068] FIG. 33 is a diagram disclosing another example of an interface governance system according to an embodiment providing interface monitoring information.

[0069] FIG. 34 is a drawing disclosing an example of a user interface (UI) for log data collected based on an integrated solution according to an embodiment.

[0070] FIG. 35 is a drawing disclosing an example of a user interface (UI) for interface mapping information according to an embodiment.

[0071] FIG. 36 is a drawing disclosing an example of a user interface (UI) for work-related interface monitoring information according to an embodiment.

[0072] FIG. 37 is a diagram disclosing another example of a user interface (UI) for work-related interface monitoring information according to an embodiment.

[0073] Figure 38 is a flowchart disclosing an example of an interface management method according to an embodiment providing interface monitoring information.

[0074] FIG. 39 is a diagram disclosing an example of an interface governance system according to an embodiment providing monitoring and management setting information through a user interface (UI).

[0075] FIG. 40 is a diagram disclosing another example of an interface governance system according to an embodiment providing monitoring and management setting information through a user interface (UI).

[0076] FIG. 41 is a diagram disclosing an example of a user interface (UI) for aggregated information according to an embodiment.

[0077] FIG. 42 is a drawing disclosing an example of a user interface (UI) for interface status information according to an embodiment.

[0078] FIG. 43 is a diagram disclosing an example of a user interface (UI) for resource monitoring information according to an embodiment.

[0079] FIG. 44 is a diagram disclosing an example of a user interface (UI) for performance monitoring information according to an embodiment.

[0080] FIG. 45 is a diagram disclosing an example of a user interface (UI) for transaction monitoring information according to an embodiment.

[0081] FIG. 46 is a diagram disclosing an example of a user interface (UI) for message details according to an embodiment.

[0082] FIG. 47 is a diagram disclosing an example of a user interface (UI) for adapter backlog monitoring information according to an embodiment.

[0083] FIG. 48 is a diagram disclosing an example of a user interface (UI) for adapter queue monitoring information according to an embodiment.

[0084] FIG. 49 is a diagram disclosing an example of a user interface (UI) for channel status information according to an embodiment.

[0085] FIG. 50 is a drawing disclosing an example of a user interface (UI) for user information according to an embodiment.

[0086] FIG. 51 is a drawing disclosing an example of a user interface (UI) for responsible interface information according to an embodiment.

[0087] FIG. 52 is a drawing disclosing an example of a user interface (UI) for interface group information according to an embodiment.

[0088] FIG. 53 is a diagram disclosing an example of a user interface (UI) for system information according to an embodiment.

[0089] FIG. 54 is a drawing disclosing an example of a user interface (UI) for interface information according to an embodiment.

[0090] Figure 55 is a flowchart disclosing an example of an interface management method according to an embodiment that provides monitoring and management setting information through a user interface (UI).

[0091] FIG. 56 is a diagram disclosing an example of an interface governance system according to an embodiment providing fault detection and solutions.

[0092] FIG. 57 is a diagram disclosing another example of an interface governance system according to an embodiment providing fault detection and solutions.

[0093] FIG. 58 is a drawing disclosing an example of a user interface (UI) for notification information according to an embodiment.

[0094] Figure 59 is a flowchart showing an example of an interface management method according to an embodiment of the present invention converting a data format.

[0095] Figure 60 is a drawing that discloses the interface governance platform of the present invention.

[0096] Figure 61 is a drawing illustrating a notification rule setting screen of the present invention.

[0097] Figure 62 is a drawing illustrating a duplicate notification suppression rule setting screen of the present invention.

[0098] Figure 63 is a drawing illustrating a notification message template management screen of the present invention.

[0099] Figure 64 is a flowchart disclosing an interface management method of the present invention.

[0100] Figure 65 is a drawing that discloses the interface governance platform of the present invention.

[0101] Figure 66 is a drawing explaining a method for handling a failure of the present invention.

[0102] Figure 67 is a drawing explaining a failure processing screen of the present invention.

[0103] Figure 68 is a drawing explaining the disability statistics screen of the present invention.

[0104] Figure 69 is a drawing explaining a monitoring screen for a failure processing situation of the present invention.

[0105] Figure 70 is a flowchart disclosing an interface management method of the present invention.

[0106] Figure 71 is a drawing disclosing an example of an interface governance system according to an embodiment providing an integrated solution linkage service.

[0107] Figure 72 is a drawing disclosing another example of an interface governance system according to an embodiment providing an integrated solution linkage service.

[0108] Figure 73 is a flowchart disclosing an example of an interface management method according to an embodiment performing a transition between integrated solutions.

[0109] Figure 74 is a flowchart disclosing an example of an interface management method according to an embodiment performing an upgrade of an integrated solution.

[0110] Figure 75 is a flowchart disclosing an example of an interface management method according to an embodiment providing an integrated solution linkage service.

[0111] Figure 76 is a diagram disclosing an example of an interface governance system according to an embodiment managing a distributed interface solution.

[0112] FIG. 77 is a diagram disclosing another example of an interface governance system according to an embodiment managing a distributed interface solution.

[0113] FIG. 78 is a drawing disclosing an example of a distributed agent adapter providing a distributed interface solution according to an embodiment.

[0114] Figure 79 is a drawing disclosing an example of a standalone configuration of a distributed agent adapter according to an embodiment.

[0115] FIG. 80 is a diagram disclosing an example of an HA configuration of a distributed agent adapter according to an embodiment.

[0116] Figure 81 is a flowchart disclosing an example of an interface management method according to an embodiment providing an integrated solution linkage service.

[0117]

[0118] Figure 1 is a conceptual diagram of an interface governance system according to an embodiment.

[0119] An example of the disclosed embodiment may provide a control system (100) that provides an interface governance platform (10000).

[0120] The interface governance platform (10000) illustrated can collect, monitor, and manage interface information from various computing systems. The control system (100) can control and manage the interface governance platform (10000).

[0121] In this example, the interface governance platform (10000) can be connected to an external cloud system or an on-premises system via an API, etc.

[0122] When a distributed agent adapter (10) is installed in a cloud system or an on-premise system, it can distribute data communication between each system or perform protocol conversion for data communication between each system.

[0123] The distributed agent adapter (10) can process data according to conditions set by the installed computing system. The distributed agent adapter's (10) own log data resulting from data processing can be transmitted to the interface governance platform (10000) and used for monitoring interface data.

[0124] The interface governance platform (10000) can monitor interfaces and communication status between systems based on relevant information, such as interfaces received from each system's solution or distributed agent adapter (10). Based on the monitored results, the interface governance platform (10000) can take action on failures in related computing systems and remotely manage those computing systems.

[0125] Detailed examples of this are disclosed below.

[0126] The interface governance platform (10000) can access a configuration repository that stores interface components of computing systems or application solutions within those systems.

[0127] To this end, the interface governance platform (10000) can collect data from computing systems or application solutions within those systems through standard APIs or custom APIs provided by those systems.

[0128] The interface governance platform (10000) can monitor information within the computer system or information related to the interface of the system through additional log data, etc., even if the computing system solution does not provide such data.

[0129] The interface governance platform (10000) can be utilized for interface monitoring and fault handling, service automation creation, service recycling, service verification, etc. through the technology of accessing the repository of related information settings such as interfaces of computing systems.

[0130] To this end, the interface governance platform (10000) may include a standardization module that standardizes and manages the interface, or a monitoring module that monitors the system through the interface.

[0131] Below, an embodiment of an interface governance platform (10000) capable of managing a system through an interface is described in detail.

[0132]

[0133] Figure 2 is a detailed diagram illustrating one embodiment of the interface governance platform mentioned above.

[0134] The interface governance platform (10000) may include an interface standardization module (1000) and an interface monitoring module (2000).

[0135] The interface standardization module (1000) can manage information obtained from interfaces based on interface application principles, interface implementation methods, or interface management standards, etc., according to a management system for interfaces with connected computing systems. Here, generalizing information obtained from interfaces according to a management system is referred to as interface standardization.

[0136] Standardization of interfaces can be accomplished based on various linking technologies for managing interfaces and naming conventions for identifying multiple interfaces.

[0137] The interface standardization module (1000) can manage a connected interface and a computing system through the interface based on standardized information obtained from the interface.

[0138] The interface standardization module (1000) can manage standardized information, i.e., reference information, collected from the interface.

[0139] For example, the method of connection between interfaces, the rules defining the interfaces, and the structure, type, or arrangement of data transmitted and received across the interfaces vary from interface to interface. The interface standardization module (1000) can store such reference information for each interface and manage it as standardized information.

[0140] The interface standardization module (1000) can provide an interface definition screen that provides a mapping design for the interfaces each computing system wishes to build. This allows the computing system to automatically create interfaces, test the created interfaces, and manage the lifecycle of the created interfaces.

[0141] The interface standardization module (1000) may include modules such as a reference information management module (1100), a specification definition module (1200), a life cycle management module (1300), and a development automation module (1400). Each module included in the interface standardization module (1000) will be described below.

[0142] Meanwhile, the interface monitoring module (2000) can monitor a computing system connected through a standardized or registered interface.

[0143] The interface monitoring module (2000) can collect log data collected from various applications by the cloud system's application integration solution via a standard API. Similarly, the interface monitoring module (2000) can collect log data collected from various applications by the on-premises system's application integration solution via a standard API.

[0144] The interface monitoring module (2000) can receive data that cannot be collected by the integrated solution of each system from the log processor of the cloud system or the log processor of the on-premise system.

[0145] Distributed agent adapters in cloud systems or on-premises systems can complement the limitations of standard interfaces and implement customized interface functions through distributed transactions.

[0146] The interface monitoring module (2000) according to the embodiment can monitor interface-related data provided by the integrated solution of each system. In addition, the interface monitoring module (2000) can monitor interface-related data not provided by the integrated solution or separate log data collected by the distributed agent adapter from the log processor.

[0147] An embodiment of the interface monitoring module (2000) can provide statistical information on collected log data. Furthermore, the interface monitoring module (2000) can learn the collected information through machine learning to identify abnormal behavior and provide information on failures to the interface manager.

[0148] In this drawing, an example of an interface monitoring module (2000) is disclosed including a log collection module (2100), a control module (2200), a failure notification module (2300), etc. The interface monitoring module (2000) is described in detail below.

[0149] The control system (100) may include a computer server (110) having at least one processor and a storage or database (120), which may be used to control and manage the interface governance platform (10000).

[0150] In this way, the interface governance platform (10000) can standardize and manage the design of the computing system's interfaces. Therefore, the interface governance platform (10000) systematically manages the computing system through the interface. Furthermore, even when additional computing system resources are built, the interface governance platform (10000) can enhance the computing system's performance and management efficiency through the interface it manages.

[0151]

[0152] Figure 3 is a conceptual diagram illustrating an architecture for managing the interface of a computing system using the interface governance platform exemplified above.

[0153] When expanding internal computing systems and connecting internal and external computing systems, there may be multiple interfaces between computing systems.

[0154] When integrating application systems within a company (Enterprise Application Integration (EAI),) interfaces between internal systems may be required. For example, for on-premise systems, an EAI system like SAP Process Orchestration (SAP PO) may be used. For cloud systems, an EAI system like SAP's Integration Suite (SAP IS) or IBM Sterling may be used.

[0155] Even in cases where large-scale data linkage is required, such as real-time data streaming platforms, various interfaces can be used.

[0156] Computing systems, such as cloud systems or on-premise systems, can be interconnected through various system interfaces (I / F).

[0157] As mentioned, an interface can be an interface between systems within the management network, or an interface between an internal system and an external system.

[0158] For example, the interface being illustrated could be an interface between on-premises systems, or an interface between an integrated system of an on-premises system and a cloud system.

[0159] An example of an interface governance platform (10000) to be disclosed may include an interface standardization module (1000) that standardizes and registers and manages interfaces of various application solutions input through APIs, and a monitoring module (2000) that collects, converts, aggregates, and statistically processes information transmitted from interfaces.

[0160]

[0161] In the example of this drawing, the integration solution (22) of the on-premise system can collect interface data from various computing systems within the system. The integration solution (22) of the on-premise system can receive interface data from various types of legacy systems within the on-premise system. The legacy systems can be connected to other systems through the integration solution (22).

[0162] The integrated solution (22) may include a log processor, which may collect data related to the interfaces of individual systems within the on-premises system. The integrated solution (22) may collect log data for standardized interfaces, including interface data transmitted by legacy systems and applications. A log processor installed within the integrated solution (22) or separately may collect non-standardized interface data.

[0163] In addition, the integrated solution (22) or the log processor within the integrated solution (22) can transmit interface-related log data and non-standardized interface data of the on-premise system to the interface governance platform (10000). For example, non-standardized interface-related data may not be provided by the integrated solution (22), but may be collected separately within the solution for monitoring, or may include at least one of the additional information required for monitoring stored in the computer system.

[0164] Meanwhile, the on-premises system may separately include a distributed agent adapter (12). The distributed agent adapter (12) can perform data conversion for data that the integrated solution (22) cannot perform. The distributed agent adapter (12) can supplement the processing of interface data that the integrated solution (22) cannot support or perform extended data processing.

[0165] When a distributed agent adapter (12) is installed in an on-premise system, the distributed agent adapter (12) can act as a hub for interface data within the on-premise system and can also perform tasks related to security or authentication.

[0166] The distributed agent adapter (12) can generate additional self-monitoring log data related to the above data processing within the on-premises system. Furthermore, the distributed agent adapter (12) can transmit the generated self-monitoring data to the interface governance platform (10000). This will be described in detail below.

[0167]

[0168] cloud system

[0169] The integrated solution (25) for the cloud system can receive interface data from various software installed within the cloud. In this example, the cloud system is a cloud system that provides SaaS software.

[0170] The integrated solution (25) can collect standardized interface data of application systems installed within cloud systems as well as SaaS software.

[0171] When a log processor is installed in the integrated solution (25) of a cloud system, the log processor can collect data generated in the processes of the integrated solution (25) in relation to the interfaces (I / F) of various solutions within the cloud system. For example, the log processor can generate non-standardized interface data generated during the process of executing software as log data.

[0172] Likewise, data related to non-standardized interfaces may not be provided by the integrated solution (25), but may be collected separately within the solution for monitoring, or may include at least one of the additional information required for monitoring stored in the computer system.

[0173] And the integrated solution (25) and the log processor within the integrated solution (25) can each transmit interface data and interface-related data of the cloud system to the interface governance platform (10000).

[0174] Meanwhile, a distributed agent adapter (15) may also be installed separately in the cloud system. The distributed agent adapter (15) of the cloud system can distribute and transform data from systems that the integrated solution (25) cannot process. The distributed agent adapter (15) can transmit its own log data generated during distributed processing to the interface governance platform (10000).

[0175] If a distributed agent adapter (15) is installed in a cloud system, the distributed agent adapter (15) can support data processing or protocol conversion of interface data that goes beyond the specified functional constraints of the integrated solution (25) of the cloud system.

[0176] With the recent shift to cloud systems, there are also cases of integration between heterogeneous systems, such as integration of cloud systems and on-premise systems.

[0177] In such cases, a distributed agent adapter (12, 15) installed in an on-premises or cloud system can transmit and receive data related to the interface with an integrated solution or distributed agent adapter of another system. The example in this drawing illustrates that a distributed agent adapter (15) of a cloud system and a distributed agent adapter of a third-party cloud system or on-premises system can transmit and receive data related to the interface.

[0178] Likewise, an integrated solution or distributed agent adapter (15) can transmit self-monitoring data related to collected interfaces or distributed processed data to the interface governance platform (10000). Detailed examples of distributed agent adapters are described below.

[0179]

[0180] The interface governance platform (10000) can collect, manage, and monitor standardized interface data of these systems or non-standardized separate interface-related data, even when multiple systems are combined.

[0181] For example, the interface standardization module (1000) of the interface governance platform (10000) can manage the reference information of the interface.

[0182] The interface standardization module (1000) can register and manage each interface using the standard information of the interface I / F of a cloud system or on-premise system.

[0183] The interface standardization module (1000) can register a new interface and test it, or automate services for interface management.

[0184] And the interface standardization module (1000) can provide various automation tools that can automatically manage the interfaces being managed, and can comprehensively manage the process of interface creation, management, operation, disposal, etc.

[0185] The interface monitoring module (2000) can perform monitoring, such as processing statistics on data collected in relation to the interface (interface I / F) of a cloud system or an on-premise system.

[0186] The interface monitoring module (2000) includes a collector hub that can collect various data related to the interface and can convert or statistically process the collected data.

[0187] The interface monitoring module (2000) can provide a dashboard to the administrator to monitor the status of real-time or specific time monitoring.

[0188] And the interface monitoring module (2000) can provide a function to check for system failures, etc. and recover them through the interface of a cloud system or on-premise system based on the data being monitored.

[0189] The interface governance platform (10000) can provide services related to integration, construction, management, and monitoring of multiple computing systems.

[0190] An interface governance platform (10000) such as the embodiment can manage systems in an integrated manner without requiring personnel to reside in the computing system for system integration and operation.

[0191]

[0192] FIG. 4 is a diagram conceptually illustrating examples of functions of a distributed agent adapter according to an embodiment.

[0193] In this diagram, the cloud system is illustrated at the top and the on-premise system is illustrated at the bottom.

[0194] Typically, cloud systems can generate events based on open APIs. Application services (e.g., SaaS services) provided by cloud systems can generate standardized interface events on the cloud system.

[0195] Meanwhile, when providing SaaS services, etc. in a cloud system, a third party using the cloud system may use the application (3 rd You can install, modify, and run a third-party app, and interface-related data may also be generated accordingly.

[0196] To collect or transmit these standardized interface events, an interface-related integration solution may be installed in the cloud system, and a separate distributed agent adapter (10) may also be installed.

[0197] Examples of SaaS-type integrated solutions in cloud systems include SAP's SuccessFactors, Concur, and Ariba, and examples of integrated solutions provided by cloud systems include SAP's Integration Suite.

[0198] Meanwhile, on-premise systems can be equipped with integrated solutions that can manage applications installed on each resource. Examples of integrated solutions installed on on-premise systems include SAP's Process Orchestration and Microsoft's Biztalk.

[0199] When a distributed agent adapter (10) according to an embodiment is installed in an on-premise system (indicated by A in this drawing), it can provide a hub technology that can link and integrate various computing systems.

[0200] Additionally, the distributed agent adapter (10) may receive various messages related to the interface of another computing system, or conversely, transmit various messages related to the interface of another computing system.

[0201] The distributed agent adapter (10) has a queuing function for messages transmitted between systems, so that when transmitting (indicated by B in this drawing) or receiving (indicated by C in this drawing) messages between systems, the safety of transmission and reception can be guaranteed, and large amounts of data can be processed efficiently.

[0202] In addition, the distributed agent adapter (10) may also provide the function of an adapter application that complements the technical limitations of an integrated solution for a cloud system or an on-premise system (indicated by D in the drawing). Here, it is shown that the distributed agent adapter (10) installed in a cloud system can perform the function of an adapter application, but the distributed agent adapter (10) can also perform the function when installed in an on-premise system.

[0203] As exemplified, the distributed agent adapter (10) can be distributed and installed in each system, thereby reducing the load on processing events or log data occurring in various interfaces and having the effect of distributing actual resources.

[0204] The interface governance platform (10000) can manage the status of an installed distributed agent adapter (10) and can also register the distributed agent adapter (10) in a cloud or on-premise system. A distributed agent adapter installed in a cloud or on-premise system can be registered and managed.

[0205] Additionally, when a problem occurs in the managed system or risk management is required, when an emergency response is required due to a system problem, or when system improvement or regular maintenance is required, the computing system can be managed in an integrated and efficient manner without additional human resource investment.

[0206] Below, specific embodiments of an interface governance platform (10000) capable of integrating and efficiently managing homogeneous or heterogeneous computing systems and functional modules included in the platform (10000) are disclosed.

[0207]

[0208] FIG. 5 is a diagram disclosing an example of managing interface-related data transmitted from a computing system based on an interface governance platform according to an embodiment.

[0209] The interface governance platform (10000) can receive interface-related data or requests from application solutions (26, 27, 28, 29) installed on various computing systems.

[0210] Application solutions (26, 27, 28, 29) may be integrated solutions installed in a cloud or on-premises system, log processors installed within or separately, or distributed agent adapters, as exemplified. For convenience, they are referred to herein as application solutions (26, 27, 28, 29).

[0211] The interface governance platform (10000) can be linked with application solutions (26, 27, 28, 29), and the interface governance platform (10000) can also receive interface reference information held by the client's computing system. For example, the linkage information received by the interface governance platform (10000) may include system management information held by the client's computing system, personnel information of employees for user authentication, or approval system information required for establishing an interface with the computing system.

[0212] The interface governance platform (10000) may include an interface standardization module (1000) and an interface monitoring module (2000).

[0213] A client using application solutions 1 (26) to application solutions n (27) can request the interface governance platform (10000) to develop or create interfaces (I / F) related to various application solutions.

[0214] The control system (100) may include at least one server (110) and a storage device (120), such as a storage or database, that stores various data including interface data.

[0215] The control system (100) can control the interface standardization module (1000) of the interface governance platform (10000). The interface standardization module (1000) reviews and approves requests for development or creation of interfaces (I / F) transmitted to the interface governance platform (10000) based on reference information or clients.

[0216] Under the control of the control system (100), the interface standardization module (1000) can manage and generate reference information for the interface of the computing system.

[0217] As an example, a client may develop application solution 1 and request development, modification or creation of related interfaces if necessary.

[0218] The interface standardization module (1000) can receive, approve or reject development, changes or creation of such interfaces, or manage the interfaces.

[0219] As another example, if a developer of a client's application solution n requests development of a new interface, the operator of application solution n may approve or reject application solution n based on the interface standardization module (1000).

[0220] In this way, not only the administrator of the control system, but also the administrator of other computing systems can access the interface governance platform (10000) and perform interface management, such as approving the creation, change, management, or disposal of interfaces based on the interface standardization module (10000).

[0221] Meanwhile, the interface monitoring module (2000) of the interface governance platform (10000) can collect interface data generated by application solutions A (28) to Z (29) of the computing system or log data related thereto.

[0222] For example, application solutions A (28) to Z (29) may include EAI solutions for each computing system, or may be distributed agent adapters that generate their own log data when performing distributed data processing.

[0223] The interface monitoring module (2000) can receive and monitor interface data or log data transmitted by various solutions within the system, such as EAI solutions.

[0224] Therefore, if a problem such as a failure occurs in a developed and registered interface or a problem is predicted based on real-time status, a proactive response can be taken.

[0225] The following examples provide detailed examples of developing, managing, monitoring, and responding to failures of interfaces, as well as user interfaces provided by the interface governance platform (10000).

[0226]

[0227] FIG. 6 is a diagram disclosing an example of a method for managing an interface of a computing system according to an embodiment.

[0228] Interface-related information related to the application solution of the computing system is registered in the interface governance platform (S110).

[0229] The computing system comprises at least one on-premises system or at least one cloud system. The application solution may include an integrated solution related to the interface of the computing system.

[0230] Interface information for the development, creation, and approval of interfaces for various application solutions can be registered on the interface governance platform.

[0231] Through the above interface governance platform, data related to the interface is received from the computing system (S120).

[0232] Standardized interface-related data can be received from integrated solutions in computing systems. Standardized interface-related data refers to interface data that conforms to the prescribed format and content of data transmitted and received by the integrated solution.

[0233] Meanwhile, interface-related log data can be received from the integrated solution, a log processor installed within the integrated solution, or a separately installed log processor. For data not provided by the integrated solution itself, interface-related log data can be received from a log processor installed within the integrated solution or separately from the integrated solution. Alternatively, information stored in a storage location on the computing system can be received from the log processor.

[0234] If a separate distributed agent adapter is installed within the computing system, the distributed agent adapter performs distributed data processing, including data collection, transformation, and processing, separately from the computing system's data processing. The distributed agent adapter may generate its own log data resulting from the distributed processing described above. The interface governance platform may receive log data directly from the distributed agent adapter or, through the integrated solution, receive log data transmitted by the distributed agent adapter to the integrated solution.

[0235] Meanwhile, data about various computing systems required for interface management may also be received.

[0236] Based on the registered interface-related information, data related to the received interface is monitored or the computing system is managed (S130).

[0237] Interfaces registered in the above interface governance platform can be monitored based on data related to the received interface.

[0238] Data related to the interface may be received from an integrated solution for each computing system, a log processor installed within the integrated solution or installed separately, or a distributed agent adapter.

[0239] Administrators can take action and manage the computing system or application solution in case of anomalies in the monitoring results of interface-related data through the interface governance platform.

[0240] Therefore, the design, construction, management, operation and maintenance of these interfaces can be performed easily and efficiently.

[0241] Detailed examples of this are disclosed below.

[0242]

[0243] According to the disclosed embodiment, it is possible to easily manage the interfaces of interconnected computing systems and easily verify the accuracy of the management results.

[0244] According to the disclosed embodiment, failures between interconnected computing systems can be quickly identified and easily managed.

[0245] According to the disclosed embodiment, recurring failures between interconnected computing systems can be accurately and reliably addressed.

[0246] According to the disclosed embodiment, interface design, construction, management, operation and maintenance can be performed efficiently.

[0247]

[0248] Within a company, interfaces can be built and operated between various systems. These interfaces play a crucial role in connecting different systems and data, facilitating seamless information exchange. However, developing and operating interfaces between various systems can present challenges, including standardization, visibility, and development efficiency.

[0249] To address these issues, the present invention provides a system for standardizing interface construction within a company by registering standard information, such as interface IDs, naming conventions, and linking patterns. This system allows for the visual management of standard information required for interface construction during the development and operation stages, providing automated guidance to enhance development productivity and quality, and facilitates construction, maintenance, and monitoring.

[0250]

[0251] Figure 7 is a diagram disclosing the interface governance platform of the present invention.

[0252] The interface governance platform (10000) may include an interface standardization module and an interface monitoring module.

[0253] The interface standardization module may include a reference information management module (1100) and a development automation module (1400), and the interface monitoring module may include a control module (2200). While the modules related to the present invention will be described herein, reference will be made to the aforementioned embodiments for other components.

[0254] The reference information management module (1100) can register and manage reference information related to interfaces required for constructing and managing interfaces. In one embodiment, the reference information management module (1100) can collect reference information from related systems (e.g., SAP PO, etc.). Based on the collected reference information, the reference information management module (1100) can automate interface development through the development automation module (1400) and monitor it through the control module (2200). A detailed description of the reference information management module (1100) will be provided below.

[0255] The development automation module (1400) can be utilized to build automated services based on the above standardization information. Services that can be automated include a construction development item creation service, a testing service, and a standardization verification service for previously developed service information. In other words, the development automation module (1400) can automate various services based on the above-described standardization information.

[0256] In one embodiment, the interface governance platform enables interfaces to be built in a standardized manner even during the development phase based on registered reference information. That is, because the interface governance platform can manage the various reference information required for interface construction, as described in the aforementioned embodiment, interfaces can be built in a standardized manner even during the development phase, if necessary.

[0257] In one embodiment, the interface governance platform can provide interface application guidance based on registered standard information. Similarly, the interface governance platform can provide users with guidance on information required for interface management. For example, the interface governance platform can provide users with guidance on standard information that must be registered for interface management. The guidance provided by the interface governance platform can include methods for creating interface lists, progress management, and methods for creating interface mapping specifications. Furthermore, the interface governance platform can provide a function for uploading or downloading the provided guidance in Excel format by area. Furthermore, for clients that do not have an internal interface management system, the interface governance platform can directly manage their interfaces. This allows the interface governance platform to intuitively and systematically manage input methods and service construction procedures through the provided guidance.

[0258] The control module (2200) can provide the aforementioned reference information, etc., as information based on the interface's task name and utilize it as matching information. More specifically, the control module (2200) can provide matching information between the interface name used (understood) by the task manager and the interface object name developed in the actual integrated solution system. The control module (2200) can provide the interface history performed through the matching information. Here, the interface history can include monitoring log information, which will be described later.

[0259] The interface standardization system established in this way provides easy and quick access to the baseline information required for interface construction across various stages, including development, operation, and maintenance, and enables developers to build interfaces in a unified manner. Furthermore, the provision of automated guidance can improve developer productivity and contribute to maintaining development quality. Furthermore, building a standardized interface can facilitate problem prevention and monitoring during the operational phase.

[0260] Therefore, the present invention can provide a technology that manages the construction and operation of internal corporate interfaces in an efficient and standardized manner. This can contribute to improving the efficiency and quality of overall corporate system development and operation.

[0261]

[0262] Figure 8 is a drawing disclosing a reference information management module of the present invention.

[0263] The reference information management module (1100) may include an interface reference information management unit (1101), an interface identification information generation unit (1102), a naming rule provision unit (1103), an integrated solution provision unit (1104), and a standardization linkage pattern provision unit (1105). At this time, the units included in the reference information management module (1100) are distinguished to explain the functions performed by the reference information management module (1100), and are not limited to the names of the components.

[0264] The standard information management unit (1101) can register and manage standard information required for the construction and management of interfaces. Here, the standard information may briefly include interface identification information, interface naming rules, linkage patterns, etc.

[0265] More specifically, the reference information managed by the reference information management unit (1101) may include target system information, interface information, and a linkage message structure. Here, the target system information may include the target system's management code information, target system name, target system type, target system IP information, linkage protocol information, connection information, and person in charge information.

[0266] Interface information may include a group name based on the business criteria, technical information (e.g., synchronous or asynchronous information, link direction information, etc.). Additionally, the link message structure may include a source message structure and a target message structure.

[0267] In one embodiment, the reference information management unit (1101) can collect reference information through API integration with a system that manages interface component information. Here, the interface component corresponds to information that is matched with the reference information. Furthermore, the integrated systems may include a system that manages a target system, a human resources information system, and an electronic approval system. In one embodiment, the reference information management unit (1101) can collect the management code, name, administrator, IP information, and system type of the target system from the system that manages the target system. In one embodiment, the target system within the client company can directly synchronize information through integration with the interface governance platform of the present invention. By utilizing the reference information, the interface governance platform can maintain consistency in system identification among managers.

[0268] In addition, the standard information management unit (1101) can collect information on personnel-related tasks (user information, internal ID, phone number, email information, etc.) by linking with the human resources information system. At this time, SSO (Single Sign On) authentication may be required for the human resources information system to access the interface governance platform. In addition, the standard information management unit (1101) can be linked with an electronic approval system. In other words, the interface governance platform can collect interface service component information to be matched with the standard information by linking with an integrated solution such as SAP PO / IS.

[0269] The interface identification information generation unit (1102) can generate interface identification information reflecting the nature or technical characteristics of the task. In one embodiment, the interface identification information generation unit (1102) can generate an ID as the interface identification information. Through this, the interface ID can serve as the interface's target identification information for communication with the relevant task manager.

[0270] The naming rule provision unit (1103) can provide naming rules for each component development item for interface construction. Here, the naming rules provided by the naming rule provision unit (1103) can apply commonly used naming rules to maintain consistency and prevent confusion.

[0271] In one embodiment, the naming rule providing unit (1103) can automatically assign naming rules to interface service component objects. Here, the interface service component objects can correspond to the development components of the integrated solution. Accordingly, the naming rule providing unit (1103) can assign naming rules to the target system code, data type name, message type name, interface service name, and mapping object name that converts the message structure, which are components that constitute the interface service. In addition, the naming rule providing unit (1103) can code and add additional information, such as linkage direction, synchronous / asynchronous processing method (for example, S is provided as an abbreviation when the processing method is synchronous, and A is provided as an abbreviation when the processing method is asynchronous), and linkage protocol. Accordingly, readability in terms of monitoring and operation management can be improved. In other words, if a naming rule is provided according to the service component of the interface when registering the interface, there is an advantage in that the characteristics of the service component of the interface can be intuitively known with only the code value during later development.

[0272] The integrated solution provider (1104) can provide an optimal EAI solution based on at least one of data size, transaction volume, and data characteristics. For a description of the EAI solution, refer to the above description. Furthermore, the EAI solution provider (1104) can select at least one EAI solution from among the provided solutions.

[0273] The standardized linkage pattern providing unit (1105) can provide standardized linkage patterns according to linkage protocol information, conversion information, and message transmission method for each target system. At this time, the standardized linkage pattern refers to a standardized form of a data exchange method between systems, and the main types of standardized linkage patterns can include synchronous linkage, asynchronous linkage, 1:1 (one-to-one) linkage, 1:N (one-to-many) linkage, etc. In addition, the standardized linkage pattern providing unit (1105) can select the most appropriate linkage pattern among the provided linkage patterns.

[0274] In one embodiment, the interface governance platform can use the generated interface ID, provided interface naming rules, linkage patterns, and reference information described above in the development automation module (1400) and control module (2200) described below. In this case, the interface governance platform can register and manage the standardization information in a database.

[0275]

[0276] FIG. 9 is a drawing showing a user interface (UI) screen provided by the interface management method of the present invention.

[0277] The interface governance platform can provide a user interface (UI) screen to enable building and operating interfaces between various systems, as in the above-described embodiments.

[0278] In this drawing, the user interface screen may include an interface application status (30), an interface application list (31), and an interface definition list (32).

[0279] Additionally, the user interface screen can be sorted by icons such as application modification, application closure, review completion, review rejection, operation transfer request, acceptance, acceptance rejection, developer acceptance, developer rejection, development / disposal completion, testing completion, and operation transfer completion. This allows for management of the interface lifecycle, as described below.

[0280] More specifically, a method for managing interfaces of computing systems of an interface governance platform (hereinafter, referred to as the interface management method) can provide various search methods through interface application status (30). In one embodiment, the interface application status (30) can include the interface application status as a search term based on at least one of a search term, a solution, an application date, a progress stage, a progress status, an application type, and a project name. Accordingly, a user can search the interface application status (32) based on at least one of the search terms.

[0281] In addition, the interface management method can manage the interface creation process through an interface application list (31). The interface application list (31) can include an application order number, CSR number, application type, solution name, progress stage, progress status, project name, applicant name, application date and time, and reviewer name.

[0282] Additionally, the interface management method can manage the generation of interface IDs through an interface definition list (32). The interface definition list (32) can include an interface ID, an interface name, a source system ID, and a target system ID. In this case, the interface definition list (32) corresponds to an actual interface list.

[0283] Afterwards, when selecting an interface, the interface management method can provide a detailed information screen for the selected interface. This will be described later.

[0284]

[0285] FIG. 10 is a drawing showing a user interface (UI) screen provided by the interface management method of the present invention.

[0286] The interface management method may provide a detailed information screen for a selected interface. Here, the detailed information screen for the interface may include interface application information (33), interface definition information (34), and interface history information (35).

[0287] In one embodiment, a user can input N (where N is a natural number) pieces of interface definition information (34) together with one interface application information (33). That is, when applying for an interface, N interfaces can be applied for at once. That is, the interface management method can receive one piece of interface application information (33) containing N pieces of definition information.

[0288] In one embodiment, interface application information (33) may include basic application information of a company requesting interface construction. For example, interface application information (33) may include company name, application type, application number, CSR number, reviewer name, urgency, solution name, completion request date, application title, project name, application details, etc.

[0289] In one embodiment, a user can select the definition information he or she wants to check from the interface application details through the interface details screen. Here, the user can correspond to an administrator on the interface governance platform. Accordingly, the interface management method can provide definition information (34) of the selected interface. Here, the interface definition information (34) can include design definition details of the interface. For example, the interface definition information (34) can include source system information, definition information, and target system information. At this time, the interface definition information (34) can include the target system to be linked, the linking protocol method, the processing method, the transmission mode, the transmission cycle, the transmission size, and the mapping specifications. In this way, the interface management method of the present invention can efficiently construct interfaces within a company by managing the classification of the source system and target system of the interface, the system ID, the system name, the linking method, and the definition information. In addition, the interface management method can manage the interface construction procedure and life cycle by managing interface application information (33) and definition information (34), and can improve interface design document update and history management, interface construction standardization, and productivity.

[0290] In one embodiment, the interface history information (35) may include history information of the selected interface. For example, the interface history information (35) may include a number, a progress stage, a progress status, a processor ID, a processor name, processing content, and a processing date and time.

[0291]

[0292] FIG. 11 is a drawing showing a user interface (UI) screen for requesting an interface provided by the interface management method of the present invention.

[0293] In one embodiment, a user can apply for a new interface through the interface governance platform. To do so, the user can create a definition document through the user interface provided by the interface governance platform.

[0294] The user interface for creating a definition document may include interface definition document name, definition document ID, management ID, solution type, internal / external linkage information, module name, source system information, target system information, processing method, transfer mode, transfer cycle, number of occurrences, data size, DB linkage processing conditions, Web Service URL, source FTP directory, target FTP directory, and an attachment file input window.

[0295] At this time, the user can select internal or external from the internal / external linkage information (36) and then select the source system and the target system. Thereafter, the user can select the target system of the source system (37) and the target system of the target system (38). To this end, the user can select the search button (37, 38) to display the target system search pop-up window (39). When the user interface receives an input signal from the user to select the search button, the target system search pop-up window (39) is displayed, and the target system can be searched through the major classification, minor classification, and search word settings. Thereafter, the target system can be applied to the source system or the target system through data search and application.

[0296] When a definition document written in this manner is submitted to the interface governance platform, the interface governance platform can build an interface based on the submitted definition document format.

[0297]

[0298] FIG. 12 is a drawing disclosing an interface definition template related to the present invention.

[0299] As in the above-described embodiment, the interface management method can manage the creation of interface IDs through a list of interface definitions so as to build and operate an interface between systems of the present invention.

[0300] To this end, this drawing explains an example of a definition template.

[0301] In one embodiment, the definition template may be, for example, an Interface Mapping Specification. The Interface Mapping Specification may include an interface name, an interface overview, a mapping specification author, a mapping specification authoring date, an interface ID, an interface group ID, an interface type, a number of transmissions, a host module, a transmission type, an interface mode, a record unit size, and a standard type. It may also include information about a source system and a target system. The information about the source system and the target system may include a system ID, a system name, a system manager's name and contact information, and information about a system connection pattern. In addition, the mapping information for a request message and a response message (or an async callback message) of the source system and the target system may each be included.

[0302] Furthermore, the information included in the definition template of this drawing is merely an example and is not limited thereto. In particular, it is understood that necessary information, such as which requests are linked to which responses, the format and structure of each message, and the protocol used, may be included to implement the operation of the interface.

[0303] Accordingly, by using definition templates such as this drawing, the interface governance platform can ensure consistent interactions between different systems.

[0304]

[0305] Figure 13 is a flowchart disclosing an interface management method of the present invention.

[0306] In one embodiment, the interface management method can register reference information of an interface related to an application solution of a computing system (S210).

[0307] Here, the computing system may include at least one on-premises system or at least one cloud system, and the application solution may include an integrated solution related to the computing system's interface. Furthermore, the interface's reference information may include target system information, interface information, and linked message structure information. In this case, the interface management method may be linked with the computing system to register the reference information. For details, please refer to the details described above in FIGS. 6 and 8.

[0308] In one embodiment, the interface management method can generate interface identification information based on interface reference information (S220).

[0309] In one embodiment, the interface management method may generate an interface ID as identification information based on the interface's reference information. Here, the interface ID may serve as the interface's target identification information for communication with the relevant business manager. In this case, the interface ID may be automatically generated as an ID that can represent the interface's characteristic information. For more information, please refer to the details described above in FIG. 8.

[0310] In one embodiment, the interface management method may provide a definition document for constructing an interface (S230).

[0311] In one embodiment, the interface management method may provide a definition document for constructing an interface. Here, the interface definition document information may include interface design definition details. For example, the interface definition document information may include source system information, definition information, and target system information. In this case, the interface definition document information may include a linked target system, a linked protocol method, a processing method, a transmission mode, a transmission cycle, a transmission size, and a mapping specification. For this purpose, please refer to the contents described above in FIGS. 9 to 12 .

[0312] In this way, when a standardization system for interface construction is systematized based on interface identification information and definition documents, such as the interface management method of the present invention, convenience can be provided to users in terms of interface construction, maintenance, and monitoring.

[0313]

[0314] The interface governance platform manages interfaces used to integrate and connect various IT systems and processes within a company or organization, effectively managing the entire lifecycle of interconnection and integration between interfaces. This is explained in detail below.

[0315]

[0316] Figure 14 is a diagram disclosing the interface governance platform of the present invention.

[0317] The interface governance platform (10000) may include an interface standardization module and an interface monitoring module (2000). The interface standardization module may include a lifecycle management module (1300) and a development automation module (1400). This description focuses on modules related to the present invention, but for other components, reference is made to the aforementioned embodiments.

[0318] The lifecycle management module (1300) can comprehensively manage the lifecycle procedures of interface application, acceptance, review, construction, testing, operation, and disposal. To this end, the lifecycle management module (1300) can provide a user interface (UI) screen accessible to applicants, recipients / reviewers, EAI operators, and EAI developers. Furthermore, the lifecycle management module (1300) can provide a user interface (UI) screen that can manage roles and permissions for each task manager according to the procedure. A detailed description of the lifecycle management module (1300) will be provided below.

[0319] The lifecycle management module (1300) can provide information for automating service construction to the development automation module (1400). That is, the lifecycle management module (1300) supports integration with continuous integration (CI) and continuous deployment (CD) tools, and can provide information to the development automation module (1400) that allows for automatic testing and deployment of interface changes. In one embodiment, the lifecycle management module (1300) can transmit information on linking with an EAI solution to the development automation module (1400) for interface automation development. An embodiment in which the development automation module (1400) automates service construction based on the information provided will be described below.

[0320] The interface monitoring module (2000) can collect information on the application, acceptance, review, construction, testing, operation, and disposal of interfaces from the lifecycle management module (1300). At this time, the interface monitoring module (2000) can utilize the baseline information collected through the lifecycle management module (1300) to provide monitoring information that can be utilized from the perspective of the business manager. Similarly, the interface monitoring module (2000) can provide the collected monitoring information to the lifecycle management module (1300) to determine whether an interface that is no longer in use is a target for disposal.

[0321] The interface monitoring module (2000) can convert the collected information and perform statistical processing. In particular, the interface monitoring module (2000) can be linked with the lifecycle management module (1300) to provide information on interfaces to be discarded. The interface monitoring module (2000) can detect unused interfaces based on the monitored data and provide information on candidates for discarding to the lifecycle management module (1300). In one embodiment, the interface monitoring module (2000) can request the lifecycle management module (1300) to discard the interface when the interface's lifecycle ends or is no longer needed.

[0322] In addition, the interface monitoring module (2000) can detect that there is no log record or data that the interface has been used for a preset period of time or longer, and provide it to the lifecycle management module (1300) as a candidate for disposal. In addition, a business manager can request the lifecycle management module (1300) to dispose of an interface as needed. Accordingly, the user of the lifecycle management module (1300) can perform the interface disposal procedure after approval. At this time, the lifecycle management module (1300) can safely remove data and resources related to the disposed interface and, if necessary, store records related to the disposal. In other words, the function of directly disabling or deleting the interface to be disposed of can be performed directly through the integrated solution, and the interface governance platform can store the management and history of the procedures related to the disposal of the interface.

[0323] Through this, the interface governance platform can effectively support the organization's IT integration and increase the efficiency and stability of related tasks.

[0324]

[0325] Figure 15 is a diagram disclosing a life cycle management module of the present invention.

[0326] The lifecycle management module (1300) can manage the lifecycle procedures of interface application, reception, review, construction, testing, operation, and disposal. In one embodiment, the lifecycle management module (1300) can include a user interface provision unit (1301), an authority verification unit (1302), an interface application management unit (1303), an interface development unit (1304), an interface testing unit (1305), and an interface management unit (1306). Here, it is obvious that the units included in the lifecycle management module (1300) are not physical structures, but are intended to distinguish the functions performed by the lifecycle management module (1300).

[0327] The user interface provider (1301) can provide a user interface screen for interface management to interface-related task managers. Here, interface-related task managers may include interface applicants, receivers / reviewers, and EAI developers. However, interface-related task managers are arbitrarily categorized by their roles, and it is understood that different task managers may perform the corresponding roles depending on the client company that actually operates the interface. For example, in a small company, a single task manager may perform multiple roles. Specifically, in a large company, the receiver, reviewer, EAI operator, and EAI developer may be separate personnel, and the EAI operator may assign interface construction to the EAI developer. In contrast, in a small company, the receiver, reviewer, EAI operator, and EAI developer may all be the same person. However, in this specification, task managers are categorized based on their roles.

[0328] Here, the "Interface Applicant" represents the field or business manager requesting interface construction, while the "Receipt / Reviewer" represents the EAI development reviewer. The "EAI Developer" represents the person responsible for actually operating and developing the EAI. Therefore, after the EAI development reviewer approves the requested interface, the interface to be built can be assigned to the EAI operation developer.

[0329] The user interface screen provided by the user interface provision unit (1301) of the life cycle management module (1300) will be described later.

[0330] The authorization verification unit (1302) can verify the authorization of a task manager accessing the aforementioned user interface. More specifically, the user interface provided by the lifecycle management module (1300) can be accessed by interface applicants, recipients / reviewers, EAI operators, and EAI developers. At this time, the authorization verification unit (1302) can determine whether the information accessed by each task manager on the user interface screen is appropriate. Thereafter, the authorization verification unit (1302) can provide information to the task manager only if the information accessed by the task manager is authorized.

[0331] In one embodiment, the lifecycle management module (1300) can manage the interface construction process by linking with the electronic approval system and a Change Service Request (CSR). At this time, the authorization verification unit (1302) can be linked with the process payment module (1307) of the electronic approval system to perform the electronic approval system's payment approval process during the application and approval process for interface construction and operation.

[0332] The interface application management unit (1303) can process and review interface applications, starting with new interface applications. More specifically, a new interface can be requested through the interface application management unit (1303). Furthermore, in one embodiment, the interface application management unit (1303) can request a new interface linkage through an applicant. At this time, the interface application management unit (1303) can initially verify the consistency of the mapping definition when the applicant creates and saves the mapping definition. For a description of the mapping definition, please refer to the above-described embodiment.

[0333] In addition, when a new interface is applied for, the interface application management unit (1303) can "accept" or "reject" the interface application through the receiver for each integrated solution (e.g., EAI solution, ETL solution, etc.). Thereafter, the interface application management unit (1303) can "review" or "reject" the interface application after reviewing the mapping definition for interface development through the reviewer. In one embodiment, the interface application management unit (1303) can review the mapping definition for interface development through the reviewer and then approve the necessary application request. In addition, the interface application management unit (1303) can assign an appropriate EAI developer after reviewing the mapping definition through the reviewer.

[0334] Additionally, the interface application management unit (1303) can initiate interface change procedures when changes occur while the interface is being operated in an actual operating environment. More specifically, the interface application management unit (1303) can request interface changes based on changes in interface requirements and, similar to the aforementioned embodiment, change the interface through acceptance and review.

[0335] In one embodiment, when an interface is assigned through the interface application management unit (1303), the interface development unit (1304) may review and provide feedback on the interface mapping definition document and then proceed with interface development through an EAI developer. At this time, the opinions and history of the review and feedback on the mapping definition document may be recorded in the mapping definition document.

[0336] The interface development unit (1304) can actually build an interface that has passed the review. The interface development unit (1304) can apply an automated construction level to the interface based on the interface's linking method and compliance with standardization. Here, the automated construction level indicates the scope of the development elements. The scope of the automated development elements may vary depending on the degree of standardization of the interface. For example, the interface service development component may include various objects that define data types, message types, message-to-message mapping conversions, service interfaces, and the relationships between them. In this case, the interface development unit (1304) can partially automatically generate and utilize at least one of the interface service development elements depending on the degree of standardization.

[0337] At this time, the interface development unit (1304) can build the interface using external development tools. Furthermore, the interface development unit (1304) can automatically build the interface using the aforementioned development automation module. An example of automatically building the interface will be described below.

[0338] The interface test unit (1305) can verify and modify the constructed interface through multiple test cases. At this time, the interface test unit (1305) can monitor the performance of the constructed interface, perform error logging and management, security audits, etc. In addition, the interface test unit (1305) can request verification of the interface through the applicant of the target system. In other words, the interface test unit (1305) can request verification from the applicant, and the business managers of both target systems can transmit and receive data through the constructed interface to perform verification of the target test system.

[0339] The interface transfer unit (1306) can transfer an interface to be used in an actual operating environment once the interface passes the test. At this time, the interface transfer unit (1306) can reflect the interface built into the operating system after confirmation by the interface applicant.

[0340] In this way, when managing an interface through the lifecycle management module (1300) of the interface governance platform, it is possible to easily create connections between various services, applications, and systems through the interface, and to systematically and systematize the management and maintenance of the interface.

[0341]

[0342] Figure 16 is a drawing illustrating a lifecycle management process of the interface of the present invention.

[0343] As described above, applicants, recipients / reviewers, EAI operators, and EAI developers can manage the lifecycle of an interface through the user interface screens provided by the lifecycle management module.

[0344] The "Applicant" represents the field or business person applying for interface construction, the "Receipt / Reviewer" represents the EAI development reviewer, and the "EAI Developer" represents the person responsible for actually operating the EAI and developing the interface for the target system. Please refer to the explanations above for details.

[0345] Looking at the process, the applicant can request the receptionist / reviewer to build a new interface.

[0346] The receptionist / reviewer can review the application based on the application information for the interface requested by the applicant. Specifically, the receptionist / reviewer can accept or reject the application based on the interface application information. At this time, the receptionist / reviewer can review the application with the relevant business manager for each integrated solution. Once the interface application is received, the receptionist / reviewer can review the mapping definition for interface development and then assign the interface development to an EAI developer. At this time, the receptionist / reviewer can review the mapping definition against the linkage standard criteria.

[0347] However, after an interface development request is assigned to an EAI developer, the EAI developer can review and provide feedback on the mapping definition. At this time, the EAI developer can review and provide feedback on the mapping definition to develop the actual interface. For example, the EAI developer can review the mapping definition for SQL errors, missing file storage location information, etc. At this time, the EAI developer can provide review feedback on the mapping definition to the applicant, and the applicant can then revise the mapping definition based on the EAI developer's feedback.

[0348] EAI developers can build interfaces tailored to their requirements. They can determine the level of automation (the scope of development elements) based on the integration method and compliance with standards. Furthermore, EAI developers can request validation (testing) of the built interface from the applicant.

[0349] Applicants can verify interfaces. After verifying the interfaces, they can request the EAI developer to transfer the interface operations. This allows the EAI developer to reflect (transfer) the approved interfaces to the operating system.

[0350] If changes occur while using a transferred interface, the applicant can re-apply for interface changes. Similarly, the applicant can submit an interface change request to the receiver / reviewer. The receiver / reviewer will review the interface change request and request an interface change from the EAI developer (the process of assigning a developer). The EAI developer can then reflect the changes in the interface.

[0351]

[0352] FIG. 17 is a drawing showing a user interface (UI) screen provided by the interface management method of the present invention.

[0353] In one embodiment, the interface governance platform may provide a user interface (UI) screen for managing the interface.

[0354] This diagram illustrates the user interface screens provided by the lifecycle management module. The user interface screens may include an interface summary (40), interface status (41), an integrated solution graph (42), interface application status (number of interfaces, 43), a shortcut icon (44), an interface application list (45), and notices (46).

[0355] The interface summary (40) can indicate the number of internal interfaces, external interfaces, internal systems, and external systems, and the number of interfaces currently being applied for.

[0356] Interface status (41) is a graph showing the number of interfaces of each target system.

[0357] The Integrated Solution Graph (42) represents the number of new interfaces for each integrated solution. Here, the number of new interfaces for each integrated solution represents the number of new interfaces generated for each integrated solution each month.

[0358] The interface application status (43) can indicate the number of interfaces for the interface application status. For example, it can indicate the number of interfaces awaiting review / receipt, the number of interfaces under development / testing, and the number of interfaces transferred to operation.

[0359] Shortcut icons (44) may include icons for requesting a new interface application, requesting a change to the interface, requesting a system inquiry, and requesting a system registration. Users can directly access the corresponding function by selecting the corresponding icon.

[0360] The interface application list (45) can display a list of current interface application status. The interface application list can display the interface application type (new or changed), solution type, project name, applicant name, progress stage, and progress status.

[0361] Notice (46) may indicate a notice that the interface governance platform wishes to convey to the user.

[0362] This allows users of the interface governance platform to manage the interface lifecycle from a single screen.

[0363]

[0364] FIG. 18 is a drawing showing a user interface (UI) screen provided by the interface management method of the present invention.

[0365] This diagram illustrates the user interface screens provided by the lifecycle management module.

[0366] The user interface screen may include an interface operation status (47) and an interface list (48).

[0367] Here, the interface operation status (47) can support a search function through various filters.

[0368] The interface list (48) represents a list of interfaces currently being managed. The interface list (48) may represent, for each interface, an operation record, interface status, solution name, internal / external classification, module, group name, interface ID, interface management ID, interface name, source system ID and source system name, target system ID and target system name.

[0369] At this time, users can easily request interface changes or cancellations through the user interface screen. Users can also set up and remove interface groups through the user interface screen. Furthermore, the interface governance platform can provide a list of interfaces included in the user interface screen as an Excel file.

[0370] The user interface screens provided by the lifecycle management module can support effective interface management. This allows users to easily access interface information and quickly perform necessary management tasks.

[0371]

[0372] Figure 19 is a flowchart disclosing an interface management method of the present invention.

[0373] The interface management method of the present invention can provide a user interface (UI) for managing an interface related to an application solution of a computing system (S310).

[0374] The user interface provided here corresponds to a screen that comprehensively manages the lifecycle of an interface: application, acceptance, review, construction, testing, operation, and disposal. For more information, please refer to the details described in Figure 14.

[0375] The interface management method of the present invention can confirm the authority of a user accessing the user interface (S320).

[0376] The user interface provided by the interface management method can offer various functions for managing the interface. In this case, the interface management method can grant different permissions depending on the user accessing the management screen. For more information, please refer to the details described in Figure 15.

[0377] The interface management method of the present invention can request development of an interface according to a user's interface application request (S330).

[0378] At this time, the interface management method can receive interface application information from a user requesting interface development. Based on the interface application information, the interface management method can approve or reject interface development.

[0379] In one embodiment, when interface development is requested, a mapping definition document for interface development may be reviewed. For a description of the mapping definition document, see the above.

[0380] In one embodiment, when the development of an interface is completed, verification may be requested from each computing system associated with the developed interface. Thereafter, the interface management method may transmit and receive data with the computing systems.

[0381]

[0382] Figure 20 is a diagram disclosing the interface governance platform of the present invention.

[0383] The interface governance platform (10000) may include a specification definition module (1200) to provide a mapping design for the interfaces each computing system wishes to build. Furthermore, the interface governance platform (10000) may include a development automation module (1400) to enable the computing system to automatically create interfaces and test the created interfaces. While the modules related to the present invention will be described herein, reference will be made to the aforementioned embodiments for other components.

[0384] The specification definition module (1200) may include a user interface provision unit (1201), a specification definition unit (1202), and a validity verification unit (1203) to manage the interface mapping definition document.

[0385] The development automation module (1400) may include an interface generation unit and a testing unit for automated interface generation. The development automation module (1400) may automatically generate objects for each component of an interface service corresponding to a designed mapping definition. At this time, the development automation module (1400) may automatically generate code and settings among the interface components according to the mapping definition. For example, the development automation module (1400) may generate automated code from the mapping definition. In addition, the development automation module (1400) may support version management and synchronization of components.

[0386] Additionally, the development automation module (1400) can perform tests to verify the generated interface service, thereby proactively identifying errors or problems in the service. For example, the development automation module (1400) can verify the service by simulating test scenarios and use cases for the designed interface.

[0387] Through this, the interface governance platform (10000) of the present invention enables efficient interface management through integration of development functions for designing and building interfaces and operational functions for verifying and distributing interfaces.

[0388]

[0389] Figure 21 is a drawing disclosing a specification definition module of the present invention.

[0390] The specification definition module (1200) may include a user interface provision unit (1201), a specification definition unit (1202), and a validity verification unit (1203) for managing the interface mapping definition document. Here, it is obvious that the units included in the specification definition module (1200) are not physical configurations, but rather are for distinguishing the functions performed by the specification definition module.

[0391] The user interface provision unit (1201) may provide a user interface (UI) for the screen for writing a mapping definition document for interface construction. At this time, the user interface provision unit (1201) may be identical to or different from the user interfaces of the other modules described above. In other words, the configuration provided by the user interface provision unit (1201) may be a configuration implemented solely by the specification definition module (1200) or a configuration implemented jointly with other modules.

[0392] Here, the mapping definition corresponds to the design document for the developer to develop the interface. At this time, the user interface provider (1201) can configure the mapping definition creation screen by utilizing the reference information or meta information stored in the interface information repository. In one embodiment, the user can easily map data elements within the mapping definition using a drag-and-drop interface on the mapping definition creation screen provided by the user interface provider (1201).

[0393] In one embodiment, the user interface provider (1201) may provide users with templates for predefined mapping definitions. In particular, the user interface provider may provide templates for major interface types. This allows users to intuitively and easily create interface mapping definitions.

[0394] The specification definition unit (1202) can define message structures, map input data, and define functions. For example, the specification definition unit (1202) can visualize the data structure of a message. Furthermore, the specification definition unit (1202) can define connection and conversion rules between different data structures. Furthermore, the specification definition unit (1202) can support users in directly defining specific conversion logic or validation logic. This allows users to easily define and manage complex message structures and conversion rules.

[0395] The validation unit (1203) can verify the validity of input data and store the mapping definition. More specifically, the validation unit (1203) can verify the validity in real time and provide error messages when a user inputs data or mapping rules. In one embodiment, the mapping definition whose validity has been verified by the validation unit (1203) can be stored in the interface information storage. At this time, the validation unit (1203) can automatically save the user's work content to prevent data loss. In addition, the validation unit (1203) can provide the user with an error report on problematic portions after validation. This ensures data accuracy and consistency and prevents errors or problems in advance.

[0396] This allows for integrated management and tracking of information and mapping rules for interfaces.

[0397]

[0398] Figure 22 is a drawing disclosing the development automation module of the present invention.

[0399] The development automation module (1400) may include an interface creation unit (1401) and a test unit (1402) for automated creation of interfaces. As described above, the units included in the development automation module (1400) are intended to distinguish the functions performed by the development automation module and are not physical structures.

[0400] The interface creation unit (1401) can create interface service components based on the interface mapping definition information created through the standard information and meta information stored in the interface information repository and the specification definition module. In addition, the interface creation unit (1401) can manage interface version information.

[0401] In one embodiment, the interface creation unit (1401) may verify whether an actual service exists before creating an interface service. To this end, the interface creation unit (1401) may verify the interface's naming rules. At this time, the interface creation unit (1401) may provide a screen for confirming the interface name through the user interface provision unit.

[0402] Additionally, the interface creation unit (1401) can link with an application solution to check whether the corresponding interface service has been created and the version information of the interface. At this time, the interface creation unit (1401) can utilize an API to link with an application solution of another computing system to check whether the corresponding application service has been created and the version information of the interface. To this end, the interface creation unit (1401) can access the application solution configuration repository.

[0403] That is, the development automation module (1400) can access a repository that manages version information such as source code, settings, and documents using application solution configuration repository access technology. For example, the development automation module (1400) can manage read or write permissions for the configuration repository by user or group, and can manage API keys or access tokens used when programmatically accessing the configuration repository.

[0404] In one embodiment, the interface generation unit (1401) can automatically generate objects for each interface service component if the corresponding interface has not been generated. In particular, the interface generation unit (1401) can automatically generate objects of interface service components in an associated order based on an input signal in which a user selects a button through the user interface provision unit.

[0405] In one embodiment, each object of an interface service component includes association relationship information and precedence relationship information. Accordingly, the interface generation unit (1401) can apply different automatic object generation ranges according to the degree of standardization for each storage type based on at least one of the association relationship information and precedence relationship information of the object.

[0406] Afterwards, the interface creation unit (1401) can provide a screen for confirming interface creation information through the user interface unit.

[0407] The test unit (1402) may provide a test screen for verifying the generated interface service. At this time, the test unit (1402) may provide a test screen for verifying the generated interface service through the user interface provision unit. In one embodiment, the test unit (1402) may perform a test data generation function, a test data transmission function, a transmission result collection function, and a test result information provision function. More specifically, the test data generation function may provide a function for editing test data.

[0408] In one embodiment, the test data transmission function and the transmission result collection function can be linked with the application solution to transmit test data to the application and collect the results. More specifically, the test unit (1402) can compare and verify the result data transmitted through the newly constructed interface with existing data. For example, the test unit (1402) can verify the data of the newly constructed interface with the existing data when a new integrated solution is introduced without changing the existing target system, when the existing integrated solution is converted to the new integrated solution, or when the integrated solution is upgraded.

[0409] The interface governance platform can implement and manage the integration between application solutions and other systems or services using the embodiments described above.

[0410]

[0411] Figure 23 is a drawing showing an interface mapping definition of the present invention.

[0412] As described above, the interface governance platform can provide a mapping definition screen for interface creation.

[0413] Here, the mapping definition screen can provide the definition ID, definition expert information, interface list, and mapping ss definition items.

[0414] The mapping definition specification may include, for the mapping definition ID, whether the requested data is standardly applicable, whether the provided data is standardly applicable, the name of the mapping definition author, the mapping definition registration date, the name of the requesting layout manager, the name of the provided layout manager, a layout description, and layout classification information. In particular, the standardly applicable nature of the requested and provided data can be determined based on the metadata of the corresponding sent and received messages, thereby providing a standardized processing method that allows the service proxy to be used to send and receive messages.

[0415] Additionally, the interface list may include, for the interface ID, an interface name, interface classification information, a providing system ID, a providing system name, a providing module name, service status information, a final start date, Tx type information, a requesting system ID, a requesting system name, and a requesting module name.

[0416] A mapping definition entry can include a sender / receiver identification code, layout type, field sequence number, level, Java package name, field name, Korean field name, occurrence count, data type, length, field description, etc. Users can save a mapping definition entry by entering mapping definition information into the fields included in the mapping definition entry.

[0417] Based on this information, XML files and VOs (Value Objects) can be automatically generated. Automatically generating XML files means automatically generating an XML structure based on user input of certain parameters or settings. Furthermore, automatic VO generation refers to the ability to automatically generate VO classes based on the schema of a database table or information from other data sources.

[0418] The mapping definition document allows comparison of available object metadata and version management of object metadata. Here, "object" can represent each object created for each interface component described above. The present invention utilizes the metadata of these objects to compare each object and manage the version of object metadata.

[0419]

[0420] Figure 24 is a diagram showing reference information stored in the interface information storage of the present invention.

[0421] The interface governance platform can configure a screen for writing a mapping definition document by utilizing the reference information stored in the interface information repository for interface creation.

[0422] This drawing shows the reference information stored in the interface information repository for this purpose.

[0423] For example, an interface governance platform may provide an interface information screen. The interface information screen may include an interface ID, basic information about the interface ID, information about the requesting system, and information about the providing system.

[0424] Basic information about an interface ID may include the interface's service status, interface type information, subject module information, Tx type information, definition ID, interface classification, sub module information, layout classification information, etc.

[0425] The requested system information and the provided system information may each include a system name, system module information, system sub-module information, system manager name, transmission protocol information, program name, system function name (operation), etc. In addition, each may include a requester ID of the requesting system and a provider ID of the providing system.

[0426] The interface governance platform can automatically create objects of interface service components through interface reference information or meta information and mapping definitions.

[0427] At this time, information about objects for each interface service component can be stored and managed through ESR (Enterprise Service Repository) registration. The object's ESR information will be described later.

[0428]

[0429] Figure 25 is a diagram showing information on objects for each interface service component of the present invention.

[0430] This drawing is a drawing that contains ESR / ID information for each object of the interface service component for interface automation generation.

[0431] For example, an interface object may include ESR information such as layout namespace information, consumer namespace information, provider namespace information, consumer request data type, provider request data type, consumer response data type, provider response data type, consumer request message type, provider request message type, consumer response message type, provider response message type, requester service interface name, provider service interface name, request message mapping information, response message mapping information, and operation mapping information.

[0432] Additionally, the interface object may include ID information, configuration scenario ID, configuration scenario description, integration configuration description, provider component ID, provider interface name, provider interface namespace, sender component ID, sender interface name, sender interface namespace, and sender channel name.

[0433] Defining ESR and ID namespaces as described above prevents object and service duplication and allows for organized management. ESR and ID information, as shown in this diagram, can aid interface automation by ensuring object uniqueness within the namespace and providing an organized structure.

[0434]

[0435] Figure 26 is a flowchart disclosing an interface management method of the present invention.

[0436] In one embodiment, the interface management method may provide a screen for creating a mapping definition for interface creation based on reference information of a stored interface (S410).

[0437] Here, the mapping definition corresponds to the design document used by developers to develop the interface. At this time, the user interface provider can configure the mapping definition creation screen by utilizing the reference information or meta information stored in the interface information repository. For details, refer to the details described above in Figures 2 and 21.

[0438] In one embodiment, the interface management method can create an interface based on a mapping definition document and reference information (S420).

[0439] More specifically, the interface management method can verify the naming convention of the interface's services. Furthermore, the interface management method can verify the version information of objects according to the components of the interface's services. In one embodiment, the interface management method can automatically generate the objects in an associated order based on an input signal. In one embodiment, the interface management method can provide a test screen for verifying the generated interface. For details, refer to the contents described above with reference to FIGS. 3, 5, and 22.

[0440]

[0441] FIG. 27 is a diagram showing an example of an interface governance system collecting log data according to an embodiment.

[0442] In the illustrated example, the interface governance system (10000) may include an interface monitoring module. The interface monitoring module may include a log collection module (2100). While the modules related to the present invention will be described herein, reference will be made to the embodiment of FIG. 2 described above for other components.

[0443] The interface governance platform (10000) can receive log data for at least one step included in the interface-related process (300) of the integrated solution (26) from the log generator (50) for the integrated solution (26). In one embodiment, the integrated solution (26) can be installed in a cloud system or an on-premise system to collect interface-related log data of multiple computing systems within the system, and a detailed embodiment thereof is described above with reference to FIG. 3. For example, according to the present invention, when the integrated solution (26) includes an EAI solution of the computing system, the interface governance system (10000) can extract monitoring log data of the EAI solution performing the interface. The integrated solution (26) can link multiple computing systems through the interface and store the performance history as log data. The interface governance system (10000) can extract the corresponding log data stored in the storage (70) of the integrated solution (26) through methods such as direct access, access through a standard API, or access through a log collection agent (60).

[0444] Additionally, the integrated solution (26) can store monitored log data in a repository (70) within the integrated solution (26). In this case, the logging method, logging scope, and log format can be implemented in various ways depending on the integrated solution (26), and the log data provision method and technology can be implemented in various forms.

[0445] The log generator (50) can generate log data for at least one step included in the interface-related process (300) of the integrated solution (26). In one embodiment, the logging generator (50) can be configured to determine whether to generate log data for each step included in the process, the logging level, and the performance role for each step. Here, the logging level can indicate the degree, type, and detail of an event for which log data is generated, depending on at least one of the type of process or the importance of the task. In addition, the performance role for each step can include source information for each step of the process for which log data was generated, such as location information for each step of the process for which log data was generated, and the time at which the log data was generated.

[0446] In one embodiment, the logging generator (50) can determine whether to apply a logging function to each step based on global and local rule conditions. Here, the global rule may include variables that affect the overall logging of the process, such as variables for a basic logging policy. In addition, the local rule may include detailed variables for logging for each step. In one embodiment, based on the priorities of the global and local rules, the local rule may be applied with priority over the global rule.

[0447] In one embodiment, a log generator (50) may be applied within an interface-related process (300), and log data may be generated for each step included in the process (300). A detailed embodiment thereof is described below.

[0448] In one embodiment, the log generator (50) may generate log data that the integrated solution (26) cannot provide in a standard manner. That is, in addition to the log data that the integrated solution (26) can provide, the log generator (50) may generate log data that the integrated solution (26) cannot provide. In this case, the log data may be stored in a storage (70) within the integrated solution (26).

[0449] In one embodiment, whether the log generator (50) is applied may be determined depending on the type of the integrated solution (26). That is, the log generator (50) may not generate the corresponding log data depending on the type of the integrated solution (26). For example, if the type of the integrated solution (26) is SAP PO and custom log data is not required, the log generator (50) may not be applied.

[0450] In one embodiment, a log collection agent (60) included in the integrated solution (26) can access a storage (70) to extract and collect log data that the integrated solution (26) cannot provide in a standard manner. That is, among the entire log data collected for at least one step included in the interface-related process (300), log data that the integrated solution (26) cannot provide in a standard manner can be extracted and collected by the log collection agent (60).

[0451] Therefore, according to the present invention, information can be supplemented additionally to the monitoring log provided by the integrated solution (26).

[0452] In other words, according to the present invention, if log data exists in the storage (70) within the integrated solution (26), but the log data cannot be provided by the integrated solution (26) in a standard manner, a separate log collection agent (60) can access the storage (70) of the integrated solution (26) to extract and collect the log data.

[0453] In one embodiment, if the log data can be provided by the integrated solution (26) in a standard manner, the log data can be extracted without the log collection agent (60) if a general standard API (80) that can access the storage (70) is provided. Therefore, according to the present invention, the limitations of the monitoring function provided by the integrated solution (26) as a default can be expanded and supported through the log generator (50) and the log collection agent (60). In addition, log data for at least one step included in the process (300), i.e., specialized monitoring additional information, can be logged to provide information defined by the user.

[0454] In one embodiment, the log collection agent (60) may be installed in the integrated solution (26) in a deployable form, and in this case, the extracted log data may be provided to the log collection module (2100) in the form of a web service.

[0455] The log collection module (2100) may include a collector generation unit (2101), a storage-linked collector (2102), an API-linked collector (2103), an agent-linked collector (2104), and a message queue (2105). At this time, the components included in the log collection module (2100) are distinguished to explain the functions performed by the log collection module (2100), and are not limited to the names of the components.

[0456] The collector creation unit (2101) may obtain collector setting information set by user input and, based on the obtained collector setting information, may generate at least one of a storage-linked collector (2102), an API-linked collector (2103), or an agent-linked collector (2104). In one embodiment, the collector setting information may include at least one of collector connection information for an integrated solution (26) or collector execution information for a log collector, which will be described in detail below.

[0457] In one embodiment, the collector generation unit (2101) may determine whether to generate a collector depending on the type of the integrated solution (26). In addition, in one embodiment, the collector generation unit (2101) may generate at least one collector based on collector setting information depending on the type of the integrated solution (26).

[0458] The storage linkage collector (2102) can access the storage (70) within the integrated solution (26) to collect log data. In one embodiment, when the log data to be collected is large in volume, the storage linkage collector (2102) can directly access the storage (70) to collect the log data. This can achieve improved log collection efficiency.

[0459] The API linkage collector (2103) can collect log data through linkage with the standard API (80) provided by the integrated solution (26). In this case, the log data collected through the standard API (80) may include log data that can be provided by the integrated solution (26). Here, the log data that can be provided by the integrated solution (26) may be referred to as log data standardized by the integrated solution (26) or a term having an equivalent technical meaning.

[0460] The agent linkage collector (2104) can collect log data through linkage with the log collection agent (60). In this case, the log data collected through the log collection agent (60) may include log data that the integrated solution (26) cannot provide. Here, the log data that the integrated solution (26) cannot provide may be referred to as log data not standardized by the integrated solution (26) or a term having an equivalent technical meaning.

[0461] The message queue (2105) can store collected log data. That is, according to the present invention, a large amount of log data can be stably secured through the message queue (2105).

[0462] In one embodiment, the interface monitoring module may perform computing system monitoring using log data. In one embodiment, the interface monitoring module may detect computing system-related failures using the log data and perform computing system failover. In one embodiment, the interface monitoring module may generate interface-related monitoring information of the computing system using the log data.

[0463] In this example, the interface governance platform (10000) may be connected to an external cloud system or an on-premise system via an API or the like. In one embodiment, the interface governance platform (10000) may be controlled and managed by a control system (100). The control system (100) may include a computer server (110) having at least one processor and a storage or database (120), and may be used to control and manage the interface governance platform (10000).

[0464]

[0465] FIG. 28 is a diagram disclosing an example of generating log data for at least one step included in an interface-related process according to an embodiment.

[0466] In one embodiment, the interface-related process (300) may include various steps depending on the integrated solution (26). This drawing illustrates a case where the interface-related process (300) includes steps 1 through 6 (41, 42, 43, 44, 45, 46). Additionally, a log generator may be applied to at least one step of the interface-related process (300).

[0467] When an HTTPS request message is received from a sender, a first step (301) may be performed to create an original message by defining a variable corresponding to the HTTPS request message. In this case, the log generator (51) installed for the first step (301) may create the original message corresponding to the first step (301) as log data.

[0468] Additionally, a second step (302) may be performed to determine whether an error exists in the original message. If no error exists in the original message, a third step (303) may be performed to generate a mapping conversion message between the interfaces that each computing system of the transmitting node and the receiving node (receiver) wants to construct based on the original message. In this case, the log generator (52) installed for the third step (303) may generate a mapping conversion message corresponding to the third step (303) as log data.

[0469] Additionally, a fourth step (304) of generating a response original message based on the mapping transformation message may be performed. Here, the generated response original message may be transmitted to the receiving node. Additionally, the log generator (53) installed for the fourth step (304) may generate the response original message corresponding to the fourth step (304) as log data.

[0470] On the other hand, if an error exists in the original message, a fifth step (305) for correcting the error may be performed. In one embodiment, a sixth step (306) for adjusting the error may be performed according to a correction result value for the error set via the user interface. In this case, the log generator (54) installed for the sixth step may generate an error message for the error corresponding to the sixth step (306) as log data.

[0471] In one embodiment, log data generated through the log generator for each step can be collected by the log collection agent (60).

[0472]

[0473] FIG. 29 is a drawing disclosing an example of a user interface (UI) for collector connection information according to an embodiment.

[0474] In one embodiment, the collector generation unit (2101) of the interface governance platform (10000) may provide a user interface (UI) for setting collector connection information (61) of a log collector for the integrated solution (26) as in the above-described embodiment. That is, a user may set connection properties for the integrated solution (26) through the user interface for the collector connection information (61).

[0475] The collector connection information (61) may include connection information for the integrated solution (26) of the log collector. In one embodiment, the collector connection information (61) may include a connection ID (62) and connection parameters (63) of the log collector for the integrated solution (26). The connection ID (62) may include a connection ID of the log collector used when the log collector calls a standard API (80) provided by the integrated solution (26).

[0476] The connection parameter (63) may include information indicating an access method to the integrated solution (26). For example, the connection parameter (62) may include passwd, user, client, lang, and sysnr. passwd may include a user password. For example, passwd may be set to 0128 by a user input. user may include a user name. For example, user may be set to ney by a user input. client may include a client number. For example, client may be set to 800 by a user input. lang may include a system language. For example, lang may be set to EN, which represents English, by a user input. sysnr may include a system number. For example, sysnr may be set to 00 by a user input.

[0477] In addition, the information included in the connection parameters (62) of this drawing is only one example and is not limited thereto, and of course, various access method information may be included.

[0478] Accordingly, using collector connection information such as this drawing, the interface governance platform (10000) can provide smooth connection to an integrated solution (26) for each log collector.

[0479]

[0480] FIG. 30 is a drawing disclosing an example of a user interface (UI) for collector performance information according to an embodiment.

[0481] In one embodiment, the collector generation unit (2101) of the interface governance platform (10000) may provide a user interface (UI) for setting collector performance information (71) of a log collector for an integrated solution (26) as in the above-described embodiment. That is, a user may set log data collection information of a log collector through a user interface for collector performance information (71).

[0482] Collector performance information (71) may include information on which log data to collect and in what manner, and information on the collection status. In one embodiment, the collector performance information (71) may include a collector type (72), a connection ID (73), an instance key (74), activation information (75), a task interval (76), task information (81), a task status (82), an execution time (83), a processing time (84), and a task result message (85) of a log collector for an integrated solution (26).

[0483] The collector type (72) may indicate the type of log collector and the type of log data collected by the log collector. For example, the collector type (72) may be set to AAE Msg Log Collector by user input.

[0484] The connection ID (73) may include the connection ID of the log collector for the integrated solution (26). For example, the connection ID (73) may be set to POS.WS by user input. That is, the type of each collector may be matched with the connection ID of the log collector.

[0485] The instance key (74) may include an instance key for the integrated solution (26). For example, the instance key (74) may be set to POS / AAEMLCS by user input.

[0486] Activation information (75) may include information on whether the corresponding log collector is activated. For example, activation information (75) may be set to 'Yes', indicating that the corresponding log collector is activated by user input.

[0487] The work interval (76) may include the log collection execution interval of the log collector. For example, the work interval (76) may be set to 10 ms by user input.

[0488] The task information (81) may include information on whether the log collector is performing log collection. For example, the task information (81) may indicate 'Yes', indicating that the log collector is performing log collection.

[0489] The task status (82) may include information on whether the log collector's log collection was successful. For example, the task status (82) may indicate 'success', indicating that the log collector successfully collected the log.

[0490] The execution time (83) may include the log collection time of the corresponding log collector. For example, the execution time (83) may indicate 2023 / 07 / 06 09:55:51, which is the time when the corresponding log collector collected the log.

[0491] The processing time (84) may include the time taken by the log collector to collect logs. For example, the processing time (84) may represent 16 ms, which is the time taken by the log collector to collect logs.

[0492] The execution result message (85) may include an execution result message according to whether the log collector's log collection was successful. For example, the execution result message (85) may indicate 'Success', which is an execution result message indicating that the log collector succeeded in log collection.

[0493] In addition, the information included in the collector performance information (71) of this drawing is only one example and is not limited thereto, and of course, various access method information may be included.

[0494] Accordingly, using collector connection information such as this drawing, the interface governance platform (10000) can provide smooth log collection for an integrated solution (26) for each log collector.

[0495]

[0496] Figure 31 is a flowchart showing an example of an interface management method according to an embodiment for collecting log data.

[0497] Collector setting information set by user input is acquired (S510). In one embodiment, the collector setting information may include at least one of collector connection information for the integrated solution or collector performance information for the log collector.

[0498] In one embodiment, log data may be generated by a log generator for at least one step involved in an interface-related process of the integrated solution. For this purpose, please refer to the descriptions in FIGS. 29 and 30 .

[0499] Using a log collector selected based on the collector setting information, log data for at least one step included in an interface-related process of the integrated solution is received (S520).

[0500] In one embodiment, if the size of log data collected by the log collector is greater than a threshold, the log collector may be used to directly access a repository included in the integrated solution to collect the log data.

[0501] In one embodiment, based on the type of log collector selected based on the collector configuration information, at least one of standardized log data or non-standardized log data from a log collection agent included in the integrated solution may be received via an API provided by the integrated solution. In one embodiment, the received log data may be stored in a message queue. For this purpose, please refer to the details described above in FIGS. 27 and 28.

[0502] Computing system monitoring is performed using the collected log data (S530). In one embodiment, the log data can be used to detect computing system-related failures and perform computing system failover. In another embodiment, the log data can be used to generate monitoring information related to the computing system's interface. For more information, please refer to the details described in FIGS. 2 and 3.

[0503]

[0504] FIG. 32 is a diagram disclosing an example of an interface governance system according to an embodiment providing interface monitoring information.

[0505] In the illustrated example, the interface governance system (10000) may include an interface standardization module and an interface monitoring module. The interface monitoring module may include a log collection module (2100). Additionally, the interface standardization module may include a reference information management module (1100). While the modules related to the present invention will be described herein, reference will be made to the embodiment of FIG. 2 described above for other components.

[0506] In one embodiment, the integrated solution may transmit data between a transmitting system and a receiving system, and log data may represent records related to such transmission. In one embodiment, the integrated solution may be installed in a cloud system or an on-premise system and provide interface-related log data of various computing systems within the system. The log collection module (2100) of the interface monitoring module may receive log data from the integrated solution. For a detailed example of this, please refer to the description above in FIG. 3.

[0507] The log collection module (2100) can acquire log data for the interface of the computing system. In one embodiment, the log collection module (2100) can convert the log data into a standardized format.

[0508] Additionally, the log collection module (2100) can generate work-related interface monitoring information from log data based on interface-related reference information pre-stored in the reference information management module (1100). In one embodiment, the log collection module (2100) can generate work-related interface monitoring information based on interface mapping information between interface-related reference information and development object information included in the log data.

[0509] Additionally, the log collection module (2100) may provide work-related interface monitoring information via a user interface. In one embodiment, the work-related interface monitoring information may include at least one of transaction information, interface statistical information, or error information.

[0510] In this example, the interface governance platform (10000) may be connected to an external cloud system or an on-premise system via an API or the like. In one embodiment, the interface governance platform (10000) may be controlled and managed by a control system (100). The control system (100) may include a computer server (110) having at least one processor and a storage or database (120), and may be used to control and manage the interface governance platform (10000).

[0511]

[0512] FIG. 33 is a diagram disclosing another example of an interface governance system according to an embodiment providing interface monitoring information.

[0513] The log collection module (2100) may include a message queue (2105), a standardization conversion unit (2106), a transaction information generation unit (2107), an interface statistics information generation unit (2108), an error information generation unit (2109), an interface matching unit (2110), and a user interface processing unit (2111). The reference information management module (1100) may include an interface information storage unit (1110). At this time, the components included in the log collection module (2100) and the reference information management module (1100) are distinguished to explain the functions performed by the log collection module (2100) and the reference information management module (1100), and are not limited to the names of the components.

[0514] The standardization conversion unit (2106) can convert the format of log data acquired from the message queue (2105) into a standardized format based on the interface reference information included in the interface information storage (1110). In one embodiment, the standardization conversion unit (2106) can convert various types of log data corresponding to different types of integrated solutions into unified information. In one embodiment, the standardization conversion unit (2106) can standardize the log data into a certain format based on interface reference information such as message information of the log data, start time and end time of transmission of the log data, and size of the log data.

[0515] The transaction information generation unit (2107) can generate transaction information for an interface from log data. In one embodiment, the log data may include transaction information, system-related data, and performance-related data. For example, the transaction information may include the number of transactions occurring by time zone and the transaction processing results.

[0516] The interface statistics generation unit (2108) can generate interface statistics from log data. In one embodiment, the interface statistics can be generated by dividing them by period, interface, work group, and resource.

[0517] The error information generation unit (2109) can generate error information for an interface from log data. In one embodiment, the error information may include interface error information, system error information, error codes, and error messages contained in the log data. In one embodiment, the error information may include the results of indexing, classifying, or performing error pattern analysis on the error-related log data described above. In one embodiment, the error information may include the maximum number of transactions, the minimum number of transactions, the average processing time, the transaction volume, the transaction trend, and the transaction size for transactions with abnormal patterns.

[0518] The interface matching unit (2110) can map log data and interface reference information. In one embodiment, the interface matching unit (2110) can map interface reference information contained in the interface information storage (1110) and development objects contained in log data corresponding to the interface reference information. According to the present invention, the user's information utilization can be improved by matching log data from a technical perspective with interface reference information from a business perspective. A detailed embodiment thereof is described below.

[0519] The user interface processing unit (2111) can provide work-related interface monitoring information based on the mapping results, based on user input via the user interface. According to the present invention, work-related monitoring information can be utilized for work through various analysis and statistical information based on log data. In other words, according to the present invention, log data acquired from the integrated solution can be processed into meaningful data, namely interface monitor information. Detailed embodiments of this are described below.

[0520]

[0521] FIG. 34 is a drawing disclosing an example of a user interface (UI) for log data collected based on an integrated solution according to an embodiment.

[0522] In one embodiment, the integrated solution may provide a user interface (UI) for a message monitoring screen (86) based on log data. The message monitoring screen (86) may include a list of log data (87).

[0523] Log data (87) may include interface type (Interface), interface namespace (Interface Namespace), message processing status (Status), start time (Start Time), end time (End Time), integration scenario (Integration Scenario), sender component (Sender Component), and receiver component (Receiver Component). In one embodiment, at least one of the information included in the log data (87) may be used to enable more intuitive understanding of the log data through meaningful code standardization with the interface service component object name.

[0524] The interface type may indicate an interface related to the corresponding log data. In one embodiment, the interface type may be named according to the characteristics of the interface. In one embodiment, the interface type may be determined based on at least one of an interface ID, an interface name, a transmitting system code, a receiving system code, a processing method code, or a message direction (e.g., inbound, outbound). For example, the interface type may be expressed in a code format such as '[I / FID]_[interface name][transmitting system code][receiving system code]_[processing method code][Outbound / Inbound direction]'.

[0525] An interface namespace can be expressed in the form of a Uniform Resource Locator (URL) as an identifier for an interface object. In one embodiment, the interface namespace can be determined based on at least one of the company domain name, business module name, or target system code for the corresponding interface. For example, the interface namespace can be expressed as 'http: / [company domain name] / [business module name] / [target system code]' for the corresponding interface.

[0526] The message processing status can indicate the message transmission status of an interface. For example, the message processing status can be "Delivered" when the interface receives a message from a sending system and ultimately delivers the message to the receiving system, the target system.

[0527] In one embodiment, the notation information according to the message processing method and status may be displayed as follows.

[0528] “TO_BE_DELIVERED”: This is a processing status within the messaging system. In one embodiment, the messaging system may refer to a messaging queue within an integrated solution.

[0529] “DELIVERING”: The message is being delivered from the messaging system to the target system.

[0530] “DELIVERED”: The message has successfully reached the target system.

[0531] “HOLDING”: This is the message status when the preceding message cannot be delivered in a sequential processing message.

[0532] “NON_DELIVERED”: A normal message processing attempt was made, but the message delivery failed.

[0533] “FAILED”: The message was reprocessed up to the maximum number of times using the message processing policy, but ultimately could not be delivered.

[0534] “WAITING” The message has been attempted to be sent at least once but has failed, and is currently waiting for another attempt.

[0535] The start time is the time when the integrated solution begins performing the interface to transmit data. For example, the start time can be expressed as '2023.07.10 1:50:55:701 PM,' which is when the integrated solution begins performing the interface. The end time can be expressed as '2023.07.10 1:55:56:279 PM,' which is when the integrated solution ends performing the interface.

[0536] An integration scenario can represent a message flow where applications interconnect and communicate to perform a specific process (e.g., a business process). In one embodiment, an integration scenario can be determined based on the type of a sending component, a receiving component, and an interface. The sending component can represent a sending system that generates events to transmit data. The receiving component can represent a receiving system that receives data. The combination of these components determines the name of the integration scenario.

[0537] In one embodiment, the log collection module (2100) of the interface governance platform (10000) may receive log data (87) from the integrated solution as described above. In one embodiment, the log data (87) received from the integrated solution may be stored in a message queue (2105).

[0538] In addition, the information included in the log data (87) of this drawing is only one example and is not limited thereto, and it is obvious that information on various log data may be included.

[0539]

[0540] FIG. 35 is a drawing disclosing an example of a user interface (UI) for interface mapping information according to an embodiment.

[0541] In one embodiment, the user interface processing unit (2111) of the interface governance platform (10000) may provide a user interface (UI) for an interface mapping pattern screen (90) for performing matching between interface reference information and log data as in the embodiment described above.

[0542] The interface mapping pattern screen (90) may include interface mapping information. In one embodiment, the interface mapping pattern screen (90) may include interface reference information (91), a log data mapping pattern (92), and an interface mapping result (93).

[0543] The interface reference information (91) may include interface information based on the interface's business name. In one embodiment, the interface reference information (91) may include an interface ID, business-related interface content, and a business group. In this case, the interface ID may include an identifier for identifying the corresponding interface. For example, the interface ID may be represented as 'FRP_PP0650'. In addition, the business-related interface content may include interface content related to the corresponding business process. For example, the business-related interface content may be represented as '(SAP->SmartERP) BT Request'. In addition, the business group may include a business group related to the business process for the corresponding interface. For example, the business group may be represented as 'Group Sales Management'.

[0544] In one embodiment, the interface reference information (91) may include some information having a representative nature related to the work among the entire interface reference information, and in this case, the some information may be referred to as a reference information key or a term having an equivalent technical meaning.

[0545] In one embodiment, interface reference information (91) can be searched based on interface ID, interface content, and work group selected based on user input.

[0546] The log data mapping pattern (92) may include development object information contained in the log data. In one embodiment, the log data mapping pattern (92) may include a transmission namespace, a transmission interface, a transmission business system, a reception namespace, a reception interface, and a reception business system for the log data. In one embodiment, development object information may be added to the log data mapping pattern (92) by user input.

[0547] The interface mapping result (93) may include a mapping result between interface reference information (91) and a log data mapping pattern (92). In one embodiment, the interface mapping result (93) may match development object information included in the log data with interface information based on the task name of the corresponding interface.

[0548] In addition, the information included in the interface mapping pattern screen (90) of this drawing is only one example and is not limited thereto, and of course, various access method information may be included.

[0549]

[0550] FIG. 36 is a drawing disclosing an example of a user interface (UI) for work-related interface monitoring information according to an embodiment.

[0551] In one embodiment, the user interface processing unit (2111) of the interface governance platform (10000) may provide a user interface (UI) for an interface status screen (94) for providing work-related interface monitoring information through the user interface as in the embodiment described above.

[0552] The interface status screen (94) may include work-related interface monitoring information. In one embodiment, the work-related interface monitoring information may be generated based on interface mapping information. In one embodiment, the interface status screen (94) may include a search field (95), transaction processing status information (96), transaction volume information (97), and interface history information (98).

[0553] The search field (95) can perform a search based on the execution time, task group, system, and interface ID selected based on user input. In one embodiment, the search field (95) can perform a search based on the message type, interface name, transmitting system, receiving system, and processing method of the log data selected based on user input.

[0554] Transaction processing status information (96) can indicate the number of successful and failed transactions for each business group. For example, transaction processing status information (96) can indicate the number of successful transactions (5,264) and the number of failed transactions (994) for the B2B business group in the form of a bar graph.

[0555] Transaction volume information (97) may represent transaction volume over a period of time for each business group. Here, transaction volume may represent the size of interface messages. For example, transaction volume information (97) may represent the transaction volume for a B2B business group for an annual average and the transaction volume for a period average in the form of a bar graph.

[0556] Interface detail information (98) may include information such as interface ID, work-related interface name, work group, transmitting system, transmitting work system, receiving system, receiving work system, transaction processing status, average response time, and average volume. In one embodiment, interface detail information (98) may be generated based on interface reference information. For example, interface name, work group, transmitting system, transmitting work system, receiving system, and receiving work system included in interface reference information may be added to interface detail information (98).

[0557] In one embodiment, work-related interface monitoring information including the above-described error information may be added to the interface status screen (94) and provided to the user.

[0558] Therefore, according to the present invention, by matching technical log data with business-related interface reference information, the user can be provided with work-related interface monitoring information, thereby improving the user's information utilization. Furthermore, the information included in the interface status screen (94) of this drawing is merely an example and is not limited thereto. It should be understood that various access method information may be included.

[0559]

[0560] FIG. 37 is a diagram disclosing another example of a user interface (UI) for work-related interface monitoring information according to an embodiment.

[0561] In one embodiment, the user interface processing unit (2111) of the interface governance platform (10000) may provide a user interface (UI) for a real-time interface history screen (101) for providing work-related interface monitoring information through the user interface as in the embodiment described above.

[0562] The real-time interface history screen (101) may include work-related interface monitoring information. In one embodiment, the work-related interface monitoring information may include a search field (102), transaction occurrence trend information (103), interface history information (104), message information (105), and an update field (106).

[0563] The search field (102) can perform a search based on the execution time, task group, system, and interface ID selected based on user input. In one embodiment, the search field (102) can perform a search based on the message type, interface name, transmitting system, receiving system, and processing method of the log data selected based on user input.

[0564] Transaction occurrence trend information (103) may include at least one of the number of transactions or transaction volume by time zone for the corresponding day of the selected execution time. Here, transaction volume may indicate the size of interface messages for the corresponding day. Additionally, the number of transactions may include the number of transactions for the corresponding day and the number of transactions for the previous day. In one embodiment, the transaction occurrence trend information (103) may be represented in the form of a bar graph or a line graph.

[0565] Interface history information (104) may include information such as interface ID, work-related interface name, work group, sending system, sending work system, receiving system, receiving work system, transaction processing status, average response time, and average volume.

[0566] Message information (105) may include message information for interface details selected from interface details information (104). In one embodiment, message information (105) may include interface ID, interface name, message status, business group, sending system, sending business system, consumer system ID (Con. Sys. ID), receiving system, receiving business system, message type, processing method, error message, start time, end time, sending processing time, receiving processing time, processing time, provider execution time, response time, transaction volume, sending message ID, and receiving message ID.

[0567] The update field (106) can update transaction occurrence trend information (103), interface history information (104), and message information (105) based on the search conditions of the search field (102). In one embodiment, the update field (106) can determine whether to update based on user input. In one embodiment, the update field (106) can automatically perform updates at preset intervals (e.g., every 10 seconds).

[0568] In addition, the information included in the real-time interface details screen (101) of this drawing is only one example and is not limited thereto, and of course, various access method information may be included.

[0569]

[0570] Figure 38 is a flowchart disclosing an example of an interface management method according to an embodiment providing interface monitoring information.

[0571] Obtain log data for the interface of the computing system (S610). In one embodiment, the log data may be received from an integrated solution. For details, refer to the contents described above in FIGS. 32 to 34.

[0572] Based on pre-stored interface-related reference information, work-related interface monitoring information is generated from log data (S620). In one embodiment, the format of the log data can be converted to a standardized format based on the pre-stored interface-related reference information.

[0573] In one embodiment, at least one of transaction information, interface statistical information, or error information for an interface may be generated from log data. In one embodiment, based on pre-stored interface-related reference information, work-related interface monitoring information may be generated from at least one of transaction information, interface statistical information, or error information for the interface.

[0574] In one embodiment, task-related interface monitoring information corresponding to log data may be generated based on matching information between pre-stored interface-related reference information and log data. For this purpose, please refer to the details described above in FIGS. 35 and 36.

[0575] Work-related interface monitoring information is provided via a user interface (S630). In one embodiment, the work-related interface monitoring information may include at least one of transaction processing status information, transaction volume information, or interface history information. For more information, please refer to the details described above in FIG. 36.

[0576]

[0577] FIG. 39 is a diagram disclosing an example of an interface governance system according to an embodiment providing monitoring and management setting information through a user interface (UI).

[0578] In the illustrated example, the interface governance system (10000) may include an interface monitoring module. The interface monitoring module may include a log collection module (2100) and a control module (2200). While the modules related to the present invention will be described herein, reference will be made to the embodiment of FIG. 2 described above for other components.

[0579] The log collection module (2100) can acquire log data for an interface of a computing system. In one embodiment, the log data can include log data converted into a standardized format.

[0580] The control module (2200) can generate at least one of monitoring information or management setting information corresponding to a task manager based on log data.

[0581] In one embodiment, the monitoring information may include at least one of interface monitoring information for an interface, system monitoring information for a computing system, or error monitoring information for at least one of the computing system or interface. Detailed embodiments thereof are described below. In one embodiment, the management configuration information may include at least one of a role permission, a task permission, or a management target corresponding to a task manager for log data. Detailed embodiments thereof are described below.

[0582] The control module (2200) may provide at least one of monitoring information or management setting information via a user interface. In one embodiment, at least one of the monitoring information or management setting information may be provided based on at least one of the role authority or work authority of the task manager.

[0583] Here, role permissions can represent access rights to user interface screens granted to a task manager based on user type.

[0584] For example, user types can be categorized as administrators, developers, and general users. Administrators are responsible for the overall management and operation of computing systems and interfaces, granting roles and permissions to task managers, and managing various configuration parameters. Developers are responsible for monitoring the computing system and its overall interfaces. Typically, EAI managers are assigned the developer role, representing those who actually operate and develop EAI. General users have access to interfaces, target systems, and business group-level interfaces, as well as personalized dashboards, depending on their specific tasks. Therefore, field users and target system operators / developers can all be considered general users. The role of task manager is arbitrarily categorized by job role, and it's understandable that different task managers may perform the role depending on the company's size, staffing status, and client companies.

[0585] For example, the control module (2200) may provide monitoring information and management setting information to an administrator based on the administrator's role authority. Furthermore, the control module (2200) may provide monitoring information to an EAI manager based on the EAI manager's role authority. Furthermore, the control module (2200) may provide at least one monitoring target included in the monitoring information to the field manager and the system manager based on their role authority.

[0586] Additionally, work permissions may indicate the assigned work authority for computing systems and interfaces, depending on the user's assigned work. For example, the control module (2200) may provide monitoring information corresponding to the assigned interface and system, based on the assigned work authority of the field worker and system manager.

[0587] In this example, the interface governance platform (10000) may be connected to an external cloud system or an on-premise system via an API or the like. In one embodiment, the interface governance platform (10000) may be controlled and managed by a control system (100). The control system (100) may include a computer server (110) having at least one processor and a storage or database (120), which may be used to control and manage the interface governance platform (10000). For further details, please refer to the descriptions given in FIGS. 1 to 3 .

[0588]

[0589] FIG. 40 is a diagram disclosing another example of an interface governance system according to an embodiment providing monitoring and management setting information through a user interface (UI).

[0590] In one embodiment, the control module (2200) may include an interface aggregate information provider (2201), an interface statistical information provider (2202), an interface history information provider (2203), a system information provider (2204), a performance information provider (2205), a transaction information provider (2206), an error management information provider (2207), a message queue information provider (2208), a channel information provider (2209), a setting management information provider (2210), an authority information provider (2211), and a collector information provider (2212). Detailed embodiments thereof are described below.

[0591] The interface aggregate information provider (2201) can provide administrators with interface status and aggregate information centered on task grouping. For example, the interface aggregate information provider (2201) can provide information on message queues, number of occurrences, number of errors, and message backlog status.

[0592] The interface statistics information provider (2202) can provide users with interface statistics information in the form of personalized monitoring. For example, the interface statistics information provider (2202) can provide users with statistics and status information based on the interface they are responsible for.

[0593] The interface history information provider (2203) can provide real-time interface history information for an interface. In one embodiment, the interface history information provider (2203) can provide real-time transaction history information for an interface. For more information, please refer to the above-described content.

[0594] The system information provision unit (2204) may provide resource monitoring information of a computing system. For example, the system information provision unit (2204) may include CPU information, memory information, and thread information of the computing system.

[0595] The performance information provider (2205) may provide performance monitoring information for an interface. In one embodiment, the performance information provider (2205) may provide interface processing performance information. In one embodiment, the interface processing performance information may be used to select optimization targets for each interface.

[0596] The transaction information provider (2206) may provide transaction monitoring information. In one embodiment, the transaction information provider (2206) may provide various information, including transaction occurrence trends for the interface.

[0597] The error management information provider (2207) can provide error information. In one embodiment, the error management information provider (2207) can provide a management function for handling error messages for an interface. In one embodiment, the error information can include error types, error history, and error processing details. In addition, the error management information provider (2207) can provide a failure search function that can search the failure history.

[0598] The message queue information provider (2208) may provide message queue status management information. In one embodiment, the message queue information provider (2208) may provide at least one of adapter backlog monitoring information and adapter queue monitoring information. In one embodiment, the message queue information provider (2208) may provide information about a message queue that stores log data collected from the integrated solution.

[0599] The channel information provider (2209) can provide channel status information. In one embodiment, the channel information provider (2209) can provide status information of connection channels with the target system.

[0600] The configuration management information provider (2210) can provide dynamically applicable parameter configuration information through a configuration management screen. In one embodiment, the configuration management information provider (2210) can provide configuration management information regarding work groups, error codes, etc.

[0601] The authority information provider (2211) can provide configuration information granting authority and management targets to each task manager. In one embodiment, the authority information provider (2211) can provide configuration information regarding the task group, target system, and interface managed by the task manager. In one embodiment, the authority information provider (2211) can provide configuration information regarding notification message rules.

[0602] The collector information provider (2212) can provide collector connection information for the collector collecting log data. For more information, refer to the above-described information.

[0603] At this time, the components included in the control module (2200) are distinguished to explain the functions performed by the control module (2200) and are not limited to the names of the components.

[0604] Therefore, according to the present invention, personalized information for each task manager can be provided in the form of a monitoring dashboard. According to the present invention, a user interface screen that is convenient from the perspective of the task manager can be provided, compared to the technical and complex user interface (UI) provided by existing integrated solutions. Furthermore, according to the present invention, analysis screen information including various monitoring information and management setting information generated using log data can be provided. In one embodiment, the analysis screen information can be provided in various graph forms. Furthermore, according to the present invention, monitoring information can be analyzed, recognized, and detected, providing convenience and speed to the task manager.

[0605]

[0606] FIG. 41 is a diagram disclosing an example of a user interface (UI) for aggregated information according to an embodiment.

[0607] In one embodiment, the control module (2200) of the interface governance platform (10000) may provide a user interface (UI) for the aggregate screen (200).

[0608] The aggregate screen (200) may include aggregate information about the administrator's system and interface. In one embodiment, the aggregate screen (200) may include system aggregate information (201), interface processing result information (202), and interface queue waiting information (203). In one embodiment, the aggregate screen (200) may be displayed when login is performed with administrator authority.

[0609] System aggregate information (201) may include queue information for legacy connections, threads, and computing systems. In one embodiment, system aggregate information (201) may include status information for GPU usage, memory occupancy, GC work ratio, and EJB sessions. For example, legacy connections may include the number of legacy connections that are normally connected and the number of legacy connections that have encountered errors. For example, threads may indicate the number of normal or loaded states based on criteria such as processing time, and message queues may indicate message queue status information associated with interfaces of major main systems, such as ERP.

[0610] Interface processing result information (202) may indicate processing results for each interface group. For example, interface processing result information (202) may indicate the number of successful processing, failed processing, and failed action counts for the corresponding interface. Here, the number of failed actions may indicate the number of times the task manager has completed processing errors in a failed interface.

[0611] The interface queue waiting information (203) may indicate the number of queue waiting cases for the interface. For example, the interface queue waiting information (203) may indicate the number of normal waiting cases, the number of delayed waiting cases, and the number of congested waiting cases of the queue waiting case of the corresponding interface. Here, the number of normal waiting cases may indicate the number of cases in which the queue waiting time is less than a first threshold value (e.g., 100%) compared to the average over a certain period (e.g., 7 days). The number of delayed waiting cases may indicate the number of cases in which the queue waiting time is greater than the first threshold value and less than the second threshold value (e.g., 200%) compared to the average over a certain period. The number of congested waiting cases may indicate the number of cases in which the queue waiting time is greater than the second threshold value compared to the average over a certain period.

[0612] In addition, the information included in the summary screen (200) of this drawing is only one example and is not limited thereto, and of course, various types of information may be included.

[0613]

[0614] FIG. 42 is a drawing disclosing an example of a user interface (UI) for interface status information according to an embodiment.

[0615] In one embodiment, the control module (2200) of the interface governance platform (10000) may provide a user interface (UI) for the interface status screen (204).

[0616] The interface status screen (204) may include interface status information of a user. In one embodiment, the interface status screen (204) may include interface information (205) and error status information (206) of the user in charge. In one embodiment, the interface status screen (204) may be displayed when a login is performed with the authority of a task manager. In one embodiment, the interface status information may be retrieved based on the execution time selected by the user input and the system the user is in charge of.

[0617] The responsible interface information (205) may include the transmitting system, receiving system, server, interface processing result (e.g., success, failure, progress), average response time, maximum response time, and average volume.

[0618] Error status information (206) may include error type, error code, processing status, error occurrence time, interface ID, interface name, work group, transmitting system, transmitting work system, receiving system, and receiving work system for the interface.

[0619] In addition, the information included in the interface status screen (204) of this drawing is only one example and is not limited thereto, and of course, various types of information may be included.

[0620]

[0621] FIG. 43 is a diagram disclosing an example of a user interface (UI) for resource monitoring information according to an embodiment.

[0622] In one embodiment, the control module (2200) of the interface governance platform (10000) may provide a user interface (UI) for the resource monitoring screen (207).

[0623] The resource monitoring screen (207) may include resource monitoring information for at least one of the computing system or interface. In one embodiment, the resource monitoring screen (207) may include memory usage (208), CPU usage (209), thread usage (210), GC work ratio (211), EJB sessions (212), and database usage (213). In one embodiment, the resource monitoring information may indicate at least one of application thread pool usage or system thread pool usage. In one embodiment, the resource monitoring information may be expressed in the form of a graph.

[0624] Memory usage (208) may represent memory usage. In one embodiment, memory usage (208) may represent memory changes over a period of time (e.g., 30 minutes). CPU usage (209) may represent CPU usage. In one embodiment, CPU usage (209) may represent CPU changes over a period of time. Thread usage (210) may represent thread usage. In one embodiment, thread usage (210) may represent thread changes over a period of time. GC work ratio (211) may represent GC work usage. EJB sessions (212) may represent the number of EJB sessions. Database usage (213) may represent usage for at least one of a database or a disk.

[0625] In addition, the information included in the resource monitoring screen (207) of this drawing is only one example and is not limited thereto, and of course, various types of information may be included.

[0626]

[0627] FIG. 44 is a diagram disclosing an example of a user interface (UI) for performance monitoring information according to an embodiment.

[0628] In one embodiment, the control module (2200) of the interface governance platform (10000) may provide a user interface (UI) for the performance monitoring screen (214).

[0629] The performance monitoring screen (214) may include performance monitoring information for at least one of the computing system or interfaces. In one embodiment, the performance monitoring screen (214) may include response times by group (215), response times by interface (216), and message information (217). In one embodiment, the performance monitoring screen (214) may be queried based on execution times, task groups, systems, and interface IDs selected by user input.

[0630] The group response time (215) can represent the average response time for each work group.

[0631] The interface-specific response time (216) may represent the average response time for each interface and interface ID. In one embodiment, the interface-specific response time (216) may represent the average response time for a certain period (e.g., search period, previous month).

[0632] Message information (217) may include message information about interface details. In one embodiment, message information (217) may include interface ID, interface name, message status, business group, sending system, sending business system, consumer system ID (Con. Sys. ID), receiving system, receiving business system, message type, processing method, error message, start time, end time, sending processing time, receiving processing time, processing time, provider execution time (P. execution time), response time, transaction volume, sending message ID, and receiving message ID.

[0633] Here, the consumer system ID may represent the actual consumer system ID of the message if the interface is a common interface with multiple consumers. The send processing time may represent the time from the time the message enters the integrated solution system from the consumer system to the time it leaves the provider system. The receive processing time may represent the time from the time the message enters the integrated solution system from the provider system to the time it leaves the consumer system in the case of a synchronous interface. The processing time may represent the sum of the send processing time and the receive processing time. The provider execution time may represent the time it takes for the provider system to process the message in the case of a synchronous interface. The response time may represent the sum of the processing time and the provider execution time.

[0634] In addition, the information included in the performance monitoring screen (215) of this drawing is only one example and is not limited thereto, and of course, various types of information may be included.

[0635]

[0636] FIG. 45 is a diagram disclosing an example of a user interface (UI) for transaction monitoring information according to an embodiment.

[0637] In one embodiment, the control module (2200) of the interface governance platform (10000) may provide a user interface (UI) for the transaction monitoring screen (218).

[0638] The transaction monitoring screen (218) may include transaction information for at least one of the computing systems or interfaces. In one embodiment, the transaction monitoring screen (218) may include monitoring summary information (219), transaction volume (220), number of failed transactions (221), and message information (222).

[0639] Monitoring summary information (219) may represent transaction summary information. In one embodiment, monitoring summary information (219) may include the total number of transactions, the number of successful transactions, the number of failed transactions, the number of ongoing transactions, the failure occurrence rate, and the total transaction volume.

[0640] Transaction volume (220) may represent transaction volume over a period of time for each business group. Here, transaction volume may represent the size of interface messages. In one embodiment, transaction volume (220) may represent the sum of interface message sizes.

[0641] The number of failed transactions (221) may represent the number of failed transactions over a period of time for each business group. In one embodiment, the number of failed transactions (221) may represent the sum of the number of failed interface messages.

[0642] Message information (222) may include interface ID, interface name, message status, business group, sending system, sending business system, consumer system ID (Con. Sys. ID), receiving system, receiving business system, message type, processing method, error message, start time, end time, sending processing time, receiving processing time, processing time, provider execution time (P. execution time), response time, transaction volume, sending message ID, and receiving message ID. For this, refer to the above-mentioned content.

[0643] In addition, the information included in the transaction monitoring screen (218) of this drawing is only one example and is not limited thereto, and of course, various types of information may be included.

[0644]

[0645] FIG. 46 is a diagram disclosing an example of a user interface (UI) for message details according to an embodiment.

[0646] In one embodiment, the control module (2200) of the interface governance platform (10000) may provide a user interface (UI) for a message detail screen (242).

[0647] The message detail screen (242) may include message detail information of a transaction message. In one embodiment, the message detail screen (242) may include a message ID (243), message meta information (244), message content (245), and processing log information (246).

[0648] Message ID (243) may include a message ID for a transaction message included in the message information, if the corresponding transaction message is selected. Here, message ID (243) may include a unique message ID assigned to the transaction. For example, if the selected transaction message corresponds to a transmission message, message ID (243) may include the transmission message ID. Additionally, if the selected transaction message corresponds to a reception message, message ID (243) may include the reception message ID.

[0649] Message meta information (244) may include interface meta information for a message when the corresponding transaction message is selected. In one embodiment, message meta information (244) may include message status, start time, end time, sending system, receiving system, message type, outbound business system, outbound namespace, outbound interface, inbound business system, inbound namespace, and inbound interface.

[0650] Additionally, the message content (245) may provide message data for each processing step of the message by version. In one embodiment, the message content (245) may include version information and message details. In one embodiment, the message content (245) may include the contents of a transmitted message or a received message depending on the type of the message, i.e., whether it is a transmitted message or a received message.

[0651] The processing log information (246) may include detailed log information for the corresponding transaction processing within the integrated solution. In one embodiment, the processing log information (246) may include log processing status, log processing time, and detailed log information. In one embodiment, the processing log information (246) may include a transmission processing log or a reception processing log depending on the type of the corresponding message, i.e., whether it is a transmission message or a reception message. In addition, the information included in the transaction monitoring screen (218) of this drawing is only one example and is not limited thereto, and various types of information may be included.

[0652]

[0653] FIG. 47 is a diagram disclosing an example of a user interface (UI) for adapter backlog monitoring information according to an embodiment.

[0654] In one embodiment, the control module (2200) of the interface governance platform (10000) may provide a user interface (UI) for the adapter backlog monitoring screen (223).

[0655] The adapter backlog monitoring screen (223) may include adapter backlog monitoring information for at least one of the computing systems or interfaces. In one embodiment, the adapter backlog monitoring screen (223) may include transmitting component information (224) and receiving component information (225). In one embodiment, the adapter backlog monitoring information may be queried by a server and component based on user input.

[0656] Transmission component information (224) may include a server, a component, a business system, a monitoring status, an EOIO (Exactly once in order), an error-included processing backlog, and an error-free processing backlog. Here, the monitoring status may indicate whether monitoring is performed through a CCMS (Computing Center Management System). The EOIO may indicate the number of messages of an interface pattern that are processed in order at one time. The error-included processing backlog may indicate the number of processed messages including the number of messages that are errors. The error-free processing backlog may indicate the number of processed messages that do not include the number of messages that are errors.

[0657] The receiving component information (225) may include servers, components, business systems, monitoring status, EOIO, processing backlogs with and without errors, and processing backlogs without errors. For more information, please refer to the above description.

[0658] In addition, the information included in the adapter backlog monitoring screen (223) of this drawing is only one example and is not limited thereto, and of course, various types of information may be included.

[0659]

[0660] FIG. 48 is a diagram disclosing an example of a user interface (UI) for adapter queue monitoring information according to an embodiment.

[0661] In one embodiment, the control module (2200) of the interface governance platform (10000) may provide a user interface (UI) for the adapter queue monitoring screen (226).

[0662] The adapter queue monitoring screen (226) may include adapter queue monitoring information (227) for at least one of the computing systems or interfaces.

[0663] Adapter queue monitoring information (227) may include a server, a server node, an adapter queue, the number of queue entries, the number of threads allocated and executed, and the maximum number of threads. Here, the number of queue entries may indicate the number of messages entered into the adapter queue. The number of threads allocated and executed may indicate the number of messages allocated to and executing threads. The maximum number of threads may indicate the maximum number of threads allocated to the adapter queue.

[0664] In addition, the information included in the adapter queue monitoring screen (226) of this drawing is only one example and is not limited thereto, and of course, various types of information may be included.

[0665]

[0666] FIG. 49 is a diagram disclosing an example of a user interface (UI) for channel status information according to an embodiment.

[0667] In one embodiment, the control module (2200) of the interface governance platform (10000) may provide a user interface (UI) for a channel status monitoring screen (228).

[0668] The channel status monitoring screen (228) may include channel status monitoring information (229) for at least one of the computing systems or interfaces. In one embodiment, the channel status monitoring information (229) may be queried based on a server, connection channel, channel status, adapter type, connection direction, and component by user input.

[0669] In one embodiment, channel states may include error, warning, ok, stopped, and unknown. Here, error may indicate the state of a channel in which an error occurred. Warning may indicate the state of an inactive channel. OK may indicate the state of a normally operating channel. Stopped may indicate the state of a channel that is stopped. Unknown may indicate the state of a channel whose state is unknown.

[0670] In addition, the information included in the channel status monitoring screen (228) of this drawing is only one example and is not limited thereto, and of course, various types of information may be included.

[0671]

[0672] FIG. 50 is a drawing disclosing an example of a user interface (UI) for user information according to an embodiment.

[0673] In one embodiment, the control module (2200) of the interface governance platform (10000) may provide a user interface (UI) for a user information screen (230).

[0674] The user information screen (230) may include user information (231) for at least one of the computing systems or interfaces. In one embodiment, when a user is added, the user information screen (230) may additionally activate a user information addition screen for the added user. In one embodiment, an account password change screen for the user may additionally be activated. In one embodiment, the user information screen (230) may be provided to an administrator.

[0675] User information (231) may include a user ID, user name, user type, user status, company, department, company phone number, personal phone number, email, messenger ID, and employee number. In this case, the user type of each user may indicate either an administrator or a user.

[0676] In one embodiment, user information (231) can be directly entered by the user. Furthermore, in one embodiment, user information (231) can be automatically registered and synchronized with the client's human resources information system via the provided API. In one embodiment, other Single Sign On (SSO) authentication may be supported for user information (231).

[0677] In addition, the information included in the user information screen (230) of this drawing is only one example and is not limited thereto, and of course, various types of information may be included.

[0678]

[0679] FIG. 51 is a drawing disclosing an example of a user interface (UI) for responsible interface information according to an embodiment.

[0680] In one embodiment, the control module (2200) of the interface governance platform (10000) may provide a user interface (UI) for the responsible interface screen (232).

[0681] The responsible interface screen (232) may include responsible interface information for at least one of the computing systems or interfaces. In one embodiment, the responsible interface screen (232) may include user account information (233), a responsible system (234), and a responsible interface (235). In one embodiment, the responsible interface screen (232) may be provided to administrators and users.

[0682] User account information (233) may include user IDs and user names for administrators and users.

[0683] The responsible interface (235) may include information on the responsible interface for which the user selected from the user account information (233) is responsible. In one embodiment, the responsible interface (235) may include a work group, interface information, interface ID, responsible information, a transmitting system, and a receiving system for the responsible interface for which the user is responsible. In one embodiment, the interface for which the user is responsible may be added or deleted through the responsible interface (235). In one embodiment, if the user is not an administrator, system-related interfaces registered with the responsibility setting permission for the user may be searched and added.

[0684] The responsible system (234) may include information about the responsible system for which the user selected from the user account information (233) is responsible. In one embodiment, the responsible system (234) may include system information and work systems. In one embodiment, the systems for which the user is responsible may be added or deleted through the responsible system (234). In one embodiment, if the user is not an administrator, the systems registered with the user's responsible setting permission may be searched and added.

[0685] In addition, the information included in the responsible interface screen (232) of this drawing is only one example and is not limited thereto, and of course, various types of information may be included.

[0686]

[0687] FIG. 52 is a drawing disclosing an example of a user interface (UI) for interface group information according to an embodiment.

[0688] In one embodiment, the control module (2200) of the interface governance platform (10000) may provide a user interface (UI) for the interface group screen (236).

[0689] The interface group screen (236) may include interface group information (237) for at least one of the computing systems or interfaces. In one embodiment, the interface group screen (236) may be provided to an administrator.

[0690] Interface group information (237) may include a work group for the interface, whether it is in use, creation date, modification date, and registrant. Here, the work group may include a work group related to a work process for the corresponding interface. The use may indicate whether the corresponding interface group is in use. The creation date may indicate the creation date of the interface group. The modification date may indicate the modification date of the group name, whether it is in use, and the group description of the interface group.

[0691] In addition, the information included in the interface group screen (236) of this drawing is only one example and is not limited thereto, and of course, various types of information may be included.

[0692]

[0693] FIG. 53 is a diagram disclosing an example of a user interface (UI) for system information according to an embodiment.

[0694] In one embodiment, the control module (2200) of the interface governance platform (10000) may provide a user interface (UI) for the system information screen (238).

[0695] The system information screen (238) may include system information (239) about at least one of the computing systems or interfaces. In one embodiment, the system information screen (238) may be provided to an administrator.

[0696] System information (239) may include a system name, system type, person in charge setting, whether in use, creation date, modification date, and registrant. In one embodiment, the system type may be selected from among SAP module, SAP-based 3rd party, or legacy system.

[0697] In one embodiment, the assignee setting may indicate whether or not the system's task assignee is permitted. In this case, for systems where the assignee setting is not permitted, the assigned interface and assigned system for the user cannot be added to the assigned interface screen.

[0698] In one embodiment, system information (239) can be added or modified on the system information screen (238). When system information (239) is added, the business system of the corresponding system can be set. In this case, the business system to which the corresponding system belongs can be registered. For example, the business system can include metadata such as the business system of SAP PO.

[0699] In addition, the information included in the system information screen (238) of this drawing is only one example and is not limited thereto, and of course, various types of information may be included.

[0700]

[0701] FIG. 54 is a drawing disclosing an example of a user interface (UI) for interface information according to an embodiment.

[0702] In one embodiment, the control module (2200) of the interface governance platform (10000) may provide a user interface (UI) for the interface information screen (240).

[0703] The interface information screen (240) may include interface information (241) for at least one of the computing systems or interfaces. In one embodiment, the interface information screen (240) may be provided to an administrator.

[0704] Interface information (241) may include interface information based on the interface's business name. In one embodiment, interface information (241) may include a business group, interface ID, interface name, importance, usage status, creation date, modification date, and registrant. In this case, the business group may include a business group related to the business process for the corresponding interface. The interface ID may include an identifier for identifying the corresponding interface. Additionally, the interface name may include interface content related to the corresponding business process.

[0705] In one embodiment, interface information may be added through user input. In this case, the interface information to be added may include a business group, interface ID, interface name, importance, response time, availability, interface description, sending system, receiving system, mapping specifications, and functional specifications when the interface is added. Here, the mapping specifications may include a generation cycle, message type, processing method, sending program, receiving program, and mapping document. The message type may be selected as either synchronous or asynchronous. The processing method may be selected as an interface processing method, including on-demand, batch, real-time, or near real-time. The interface information (241) may be directly input by the user as described above, but may also be provided through internal linkage with a reference information management module.

[0706] In addition, the information included in the interface information screen (240) of this drawing is only one example and is not limited thereto, and of course, various types of information may be included.

[0707]

[0708] Figure 55 is a flowchart disclosing an example of an interface management method according to an embodiment that provides monitoring and management setting information through a user interface (UI).

[0709] Obtain log data for the interface of the computing system (S710). In one embodiment, the log data may be formatted into a standardized format. For details, refer to the description in FIG. 39.

[0710] At least one of monitoring information or management setting information corresponding to a task manager is generated based on log data (S720). In one embodiment, monitoring information including at least one of interface monitoring information for an interface, system monitoring information for a computing system, or error monitoring information for at least one of a computing system or an interface may be generated based on the log data. In one embodiment, management setting information including at least one of role authority, task authority, or management target corresponding to a task manager for log data may be generated based on input from the task manager. For this, please refer to the contents described above in FIGS. 39 and 40.

[0711] At least one of the monitoring information or management setting information is provided via the user interface (S730). In one embodiment, at least one of the monitoring information or management setting information may be provided based on at least one of the role authority or work authority of the task manager. For this, please refer to the details described above in FIGS. 39 and 40.

[0712]

[0713] FIG. 56 is a diagram disclosing an example of an interface governance system according to an embodiment providing fault detection and solutions.

[0714] In the illustrated example, the interface governance system (10000) may include an interface monitoring module. The interface monitoring module may include a log collection module (2100) and a fault notification module (2300). While the modules related to the present invention will be described herein, reference will be made to the embodiment of FIG. 2 described above for other components.

[0715] The log collection module (2100) can acquire log data for an interface of a computing system. In one embodiment, the log data can include log data converted into a standardized format.

[0716] The failure notification module (2300) can detect a failure of at least one of the computing system or interfaces from the log data based on predefined failure determination criteria information. In one embodiment, the failure notification module (2300) can detect a failure of at least one of the computing system or interfaces by comparing the log data values ​​with a threshold value based on the failure determination criteria information. Thus, according to the present invention, real-time failure detection is possible based on log data.

[0717] In one embodiment, the fault notification module (2300) can detect an abnormality symptom in at least one of the computing system or interface based on statistical information about log data. In one embodiment, the fault notification module (2300) can detect an abnormality symptom in at least one of the computing system or interface by comparing the amount of change in the log data with a threshold value. Thus, according to the present invention, a fault can be prevented by predicting an abnormality symptom based on changes in the log data.

[0718] Additionally, the failure notification module (2300) may provide at least one of failure information or failure action guides based on at least one of the failure or abnormal symptoms. In one embodiment, the failure notification module (2300) may obtain failure action information through user input. A detailed embodiment thereof is described below.

[0719] In this example, the interface governance platform (10000) may be connected to an external cloud system or an on-premise system via an API or the like. In one embodiment, the interface governance platform (10000) may be controlled and managed by a control system (100). The control system (100) may include a computer server (110) having at least one processor and a storage or database (120), which may be used to control and manage the interface governance platform (10000). For further details, please refer to the descriptions given in FIGS. 1 to 3 .

[0720]

[0721] FIG. 57 is a diagram disclosing another example of an interface governance system according to an embodiment providing fault detection and solutions.

[0722] In one embodiment, the interface governance system (10000) may include a log collection module (2100) and a failure notification module (2300). At this time, the components included in the log collection module (2100) and the failure notification module (2300) are distinguished to explain the functions performed by the log collection module (2100) and the failure notification module (2300), and are not limited to the names of the components.

[0723] The log collection module (2100) may include a message queue (2105) and a standardization conversion unit (2106). The message queue (2105) may store collected log data. The standardization conversion unit (2106) may convert the format of the log data into a standardized format.

[0724] The failure notification module (2300) may include a failure detection unit (2301), an abnormality symptom detection unit (2302), a guide provision unit (2303), a notification provision unit (2304), a failure action management unit (2305), and a failure information storage unit (2306).

[0725] The fault detection unit (2301) can determine whether at least one of the computing system or interfaces is faulty based on log data formatted in a standardized format. In one embodiment, the fault detection unit (2301) can determine whether there is a fault based on predefined fault determination criteria information. For example, the fault determination criteria information may include CPU usage, interface processing results, error message information, resource usage, thread threshold values, data size, transaction volume, etc.

[0726] In one embodiment, the failure detection unit (2301) can determine whether a failure exists based on whether the interface succeeds or fails. In one embodiment, the failure detection unit (2301) can determine whether a failure exists based on whether log data contains a business-critical error. In one embodiment, the failure detection unit (2301) can determine whether a failure exists based on whether resource usage exceeds a threshold. For example, the failure detection unit (2301) can determine that a failure has occurred if resource usage exceeds a threshold.

[0727] The anomaly detection unit (2302) can detect an anomaly in at least one computing system or interface based on statistical information about log data. In one embodiment, the anomaly detection unit (2302) can detect an anomaly based on the amount of change in the monitoring target of the log data. For example, the anomaly detection unit (2302) can detect an anomaly based on transaction occurrence trends, transaction pattern changes, error patterns, interfaces, message queues, and resource changes.

[0728] In one embodiment, the abnormal symptom detection unit (2302) may determine that an abnormal symptom exists if the change amount of the monitoring target is greater than a threshold value. In one embodiment, the abnormal symptom detection unit (2302) may determine that an abnormal symptom exists if the change amount of the monitoring target deviates from a preset pattern. In one embodiment, the change amount of the monitoring target may be learned and accumulated as statistical information through machine learning and stored in the failure information storage unit (2306).

[0729] The guide provider (2303) may provide failover guidance based on detected failures or abnormal symptoms. In one embodiment, the guide provider (2302) may provide failover guidance based on the failover hit rate for previous failover history. That is, according to the present invention, previous failover history can be reused for fault resolution. In one embodiment, previous failover history may be learned and accumulated through machine learning and stored in the failure information repository (2306).

[0730] The notification provider (2304) may provide at least one of fault information or a fault action guide via a notification. In one embodiment, the fault information may include the fault type, fault cause, and fault details. Additionally, the fault action guide may include measures to resolve the fault, user evaluations of the corresponding action guide, and a fault action hit rate based on the results of the corresponding action guide.

[0731] The failover management unit (2305) can obtain the results of the user's failover actions. In one embodiment, the failover management unit (2305) can reflect the user's evaluation and status of the failover completion in the corresponding failover guide. A detailed example of this is described below.

[0732]

[0733] FIG. 58 is a drawing disclosing an example of a user interface (UI) for notification information according to an embodiment.

[0734] In one embodiment, the notification provision unit (2304) of the interface governance platform (10000) may provide a user interface (UI) for the notification screen (190).

[0735] The notification screen (190) may include fault information. In one embodiment, the notification screen (190) may include fault confirmation information (191) and notification content information (192).

[0736] Fault confirmation information (191) may include fault information provided as an alert. In one embodiment, the fault confirmation information (191) may include the occurrence time, alert title, confirmation status information, and confirmation time. In one embodiment, the alert title may include an interface message error based on a server identifier and interface name.

[0737] Notification content information (192) may include a notification title and notification content. In one embodiment, the notification content may include server and client identifiers, a work group, an interface name, a sending system, a receiving system, a message ID, an error occurrence time, an error message, an error code, and an error type.

[0738] In one embodiment, the notification screen (190) may include alarm information regarding various information such as fault information, CPU, memory, thread status, etc. In addition, the information included in the fault screen (190) of this drawing is only one example and is not limited thereto, and it is obvious that information regarding various fault information may be included.

[0739]

[0740] Figure 59 is a flowchart showing an example of an interface management method according to an embodiment of the present invention converting a data format.

[0741] Obtain log data for the interface of the computing system (S810). In one embodiment, the log data may be formatted into a standardized format. For details, refer to the contents described above in FIGS. 56 and 57.

[0742] Based on predefined fault determination criteria information, a fault in at least one of the computing system or interfaces is detected from log data (S820). In one embodiment, a fault in at least one of the computing system or interfaces can be detected by comparing the value of monitoring information for the log data with a threshold value. In one embodiment, prior to step S730, an abnormal symptom in at least one of the computing system or interfaces can be detected based on statistical information about the log data. For this purpose, please refer to the contents described above in FIGS. 56 and 57.

[0743] At least one of failure information or failure action guide is provided based on the detected failure (S830). In one embodiment, at least one of the failure information or failure action guide may be determined based on at least one of the detected failure or abnormal symptoms, and at least one of the failure or abnormal symptoms may be provided.

[0744] In one embodiment, the failover guide may be determined based on a failover hit rate based on previous failovers for the failover guide.

[0745] In one embodiment, after step S730, failover information corresponding to at least one of the failure information and the failover guide may be acquired, and a failover hit rate for the failover guide may be determined based on the failover information. For this purpose, please refer to the descriptions in FIGS. 56 to 58 .

[0746]

[0747] Figure 60 is a diagram disclosing the interface governance platform of the present invention.

[0748] The interface governance platform (10000) may include a failure notification module (2300) to provide functionality for identifying and recovering failures (including errors) through the interface of a cloud system or on-premise system based on monitored data. While the module related to the present invention will be described herein, reference will be made to the aforementioned embodiments for other components.

[0749] The failure notification module (2300) may include a notification management screen provision unit (2301), a failure detection unit (2302), and a notification generation unit (2303). Here, it is obvious that the units included in the failure notification module (2300) are not physical components, but are intended to distinguish the functions performed by the specification definition module.

[0750] The notification management screen provider (2301) can provide a notification setting function via the notification management screen. More specifically, the notification management screen provider (2301) can provide a notification rule setting function, a notification message template management function, and a duplicate notification suppression rule setting function. A detailed description of these will be provided later via the notification management screen.

[0751] The fault detection unit (2302) can receive fault information from a connected computing system. At this time, the fault detection unit can determine whether a fault exists based on the fault information. If a fault is determined, the fault detection unit (2302) can transmit the fault information to the notification generation unit (2303).

[0752] The notification generation unit (2303) can apply a notification duplication removal rule based on the received fault information.

[0753] Additionally, the notification generating unit (2303) can apply notification rules.

[0754] The notification generation unit (2303) can apply a notification message template to generate a notification.

[0755] Afterwards, the notification generation unit (2303) can load a notification message to which a template is applied into the notification message queue to generate a notification.

[0756] Afterwards, the notification message loaded in the notification message queue can be delivered to the linkage module container (2400).

[0757] The notification message transmitted to the linkage module container (2400) may be transmitted to at least one of an email notification module (2401), an SMS notification module (2402), an SNS notification module (2403), and other notification modules (2404) in a preset manner to notify the user of an interface failure in real time. At this time, the linkage module container may select the most appropriate notification method according to the user's situation and needs and transmit the failure information.

[0758] Through this, the interface governance platform (10000) of the present invention can quickly identify recurring failures in connected computing systems. In particular, through the filtering and rules described below, unnecessary notifications can be reduced and only important notifications can be delivered quickly and accurately. This allows users to accurately and reliably address recurring failures in connected computing systems.

[0759]

[0760] Figures 61 to 63 are diagrams illustrating the notification management screens provided by the aforementioned failure notification module. The screens for setting notification rules, setting duplicate notification suppression rules, and managing notification message templates are described, respectively.

[0761]

[0762] Figure 61 is a drawing explaining the notification rule setting screen of the present invention.

[0763] This diagram illustrates the notification rule configuration screen provided by the fault notification module. Here, notification rules can indicate the conditions under which notifications will be sent. For example, a notification rule can be set to send a notification when a specific system's CPU usage exceeds 90%. The notification rule can also define whether notifications should be sent only to specific users or groups, or in different ways based on varying levels of severity.

[0764] For example, the sequence for generating a notification for an interface failure associated with a specific work group is as follows:

[0765] (1) You can add a notification rule name. For example, you can set a notification rule name such as “Human Resources Management.”

[0766] (2) You can set the notification method. For example, you can set “Email” and “SMS.”

[0767] (3) You can set a notification message template for each notification method.

[0768] (4) You can set recipients for each notification message. For example, you can search for and add personnel related to human resources.

[0769] (5) You can set the type of failure you wish to receive notifications for. For example, if you want to receive failure information for an interface related to human resources management, you can select "Error."

[0770] (6) Associated target interfaces can be set. Associated target interfaces can be selected individually, either on an interface-by-interface basis or on a target system-by-system basis. Furthermore, rules can be applied based on other fault types and levels defined within the interface governance platform. Here, the fault type can refer to the aforementioned fault types. For example, the fault level can indicate the severity of the aforementioned notification level and can be applied as one of INFO, FATAL, ERROR, or WARN.

[0771] The fault notification module may provide an Add button for adding a notification rule and a Delete button for deleting a notification rule. In one embodiment, a notification rule may be added upon receiving input from a user selecting the Add button. For example, the notification rules may include a GC Work Ratio abnormality notification, an EJB Session abnormality notification, etc. Here, the GC Work Ratio indicates the ratio of how frequently or how long the GC (Garbage Collection) operates. The GC Work Ratio abnormality notification corresponds to a notification that occurs when the GC operation ratio exceeds a certain threshold. In addition, the EJB Session is a session bean of the component-based architecture of the Java Enterprise Edition platform, and the EJB Session abnormality notification corresponds to a notification that occurs when abnormal behavior related to the EJB session is detected.

[0772] Similarly, the failure notification module can delete a selected notification rule upon receiving an input signal in which the user selects an added notification rule and selects a delete button.

[0773] The fault notification module can store rule filters for selected notification rules. The fault notification module receives user input for each notification rule and its corresponding rule filter, and maps and stores the notification rules and their corresponding rule filters.

[0774] At this time, the failure notification module can provide the following rule filter types for the notification rule: Message Error, Memory, Thread, CPU, Adapter Queue, Abap Queue, Channel Status, GC Work Ratio, EJB Session, etc. The provided notification types are merely examples, and the failure notification module can of course provide different notification types depending on the failure. The user can select one of the provided rule filter types as the rule filter for the notification rule. Accordingly, the failure notification module can set a rule filter for each notification type.

[0775] In one embodiment, the fault notification module can add or delete notification methods for a selected notification rule through a user interface provided as shown in this drawing. Furthermore, the fault notification module can add or delete recipients for a selected notification rule through a user interface provided as shown in this drawing.

[0776] Accordingly, users can select alarm rules, add or delete alarm methods, and add or delete recipients for alarm rules through the user interface provided through the interface governance platform.

[0777]

[0778] Figure 62 is a drawing explaining a duplicate notification suppression rule setting screen of the present invention.

[0779] Repeatedly sending the same notifications to users when the same failure occurs repeatedly is inefficient. Therefore, the present invention can be designed to identify the type or pattern of failure and suppress duplicate failure notifications for a preset period of time.

[0780] The fault notification module may provide an Add button for adding a duplicate notification suppression rule and a Delete button for deleting a duplicate notification suppression rule. In one embodiment, a duplicate notification suppression rule may be added upon receiving an input signal from the user selecting the Add button. For example, the duplicate notification suppression rule may suppress duplicate notifications for Garbage Collection (GC) and Enterprise JavaBeans Session Duplicate Notification (EJB Session). For example, if a certain memory threshold is exceeded, a GC notification may be issued multiple times.

[0781] Similarly, the failure notification module can delete a selected duplicate notification suppression rule upon receiving an input signal in which a user selects an added duplicate notification suppression rule and selects a delete button.

[0782] The fault notification module can store rule filters for selected duplicate notification suppression rules. The fault notification module can receive user input for duplicate notification suppression rules and their corresponding rule filters, and map and store the duplicate notification suppression rules and their corresponding rule filters.

[0783] Here, the fault notification module can provide rule filter types for duplicate notification suppression rules, such as Message Error, Memory, Thread, CPU, Adapter Queue, Abap Queue, Channel Status, GC Work Ratio, and EJB Session. Users can select one of the provided rule filter types as a rule filter for the duplicate notification suppression rule. Accordingly, the fault notification module can set rule filters for each notification type.

[0784] Additionally, the fault notification module can set a deduplication interval for messages filtered by the rule filter. Accordingly, the fault notification module can avoid sending a notification to the user if a fault occurs according to the set rule within the set deduplication interval.

[0785] Through this, the efficiency of failure management of computing systems can be improved by reducing unnecessary notifications.

[0786]

[0787] Figure 63 is a drawing illustrating a notification message template management screen of the present invention.

[0788] In one embodiment, notification messages should be designed to enable users to clearly understand the issue upon receiving the notification. Therefore, the notification management screen provider may provide a notification message template management function. For example, the template should include key information such as the type of failure, time of occurrence, location of occurrence, and severity of the failure.

[0789] To this end, the notification message template management screen may provide an Add button for adding a notification template in the first area and a Delete button for deleting a notification template. Additionally, the notification message template management screen may provide a Template Edit screen for entering a title for a notification message, entering content, and saving the content in the second area.

[0790] Accordingly, the user can input and save the title and content of the notification template, and the interface governance module can notify the system of a failure using the notification template saved by the user.

[0791]

[0792] Figure 64 is a flowchart disclosing an interface management method of the present invention.

[0793] In one embodiment, an interface management method can detect a failure occurring through an interface of a computing system (S910). The interface management method can receive failure information from a connected computing system. Based on the received failure information, the interface management method can determine whether a failure exists, and if a failure is determined, can apply a notification rule to the failure information. For details, refer to FIGS. 1 to 5 and FIG. 60.

[0794] In one embodiment, the interface management method may apply preset notification rules and templates to a detected fault (S920). If a fault is determined based on received fault information, the interface management method may apply preset notification rules. Here, the preset notification rules are characterized by including notification rules and duplicate notification suppression rules. When the notification rules are applied to a fault, a notification message template for generating a notification corresponding to the fault may be applied to the fault information. In addition, the preset notification rules and templates are characterized by being input by a user. For this purpose, refer to FIGS. 61 to 63.

[0795] In one embodiment, the interface management method can transmit a notification for a fault to which preset notification rules and templates are applied (S930). The interface management method can temporarily store the fault to which the preset notification rules and templates are applied in a notification message queue. Thereafter, the interface management method can transmit a notification message corresponding to the fault loaded in the notification message queue to the linkage module container according to a preset cycle and a preset method. Refer to FIG. 60 for details.

[0796]

[0797] Figure 65 is a diagram disclosing the interface governance platform of the present invention.

[0798] The interface governance platform (10000) may include a failure notification module (2300) and an AI module to provide functions for managing failures and accumulating action history to enhance the stability and efficiency of the system in a company. This description focuses on modules related to the present invention, but for other components, reference is made to the aforementioned embodiments.

[0799] The fault notification module (2300) may include a user interface provision unit (2304), a fault detection unit (2302), and a fault processing unit (2305). Here, it is obvious that the units included in the fault notification module (2300) are not physical components, but are intended to distinguish the functions performed by the specification definition module.

[0800] The user interface provider (2304) may provide a user interface screen for fault management. The user interface provider (2304) may include screens for fault statistics information, fault handling procedure management, and fault handling search services. For details on the fault statistics information, fault handling procedure management, and fault handling search service screens included in the user interface screen, please refer to FIGS. 39 to 64.

[0801] The fault detection unit (2302) can automatically register fault information when a fault occurs in a connected computing system. At this time, the fault detection unit (2302) can transmit the fault information to the AI ​​module to determine whether a fault exists. If the fault detection unit (2302) determines a fault, it can transmit the fault information to the notification generation unit. For more information, please refer to the details described above in FIGS. 39 to 64.

[0802] The AI ​​module (2500) can determine whether a failure has occurred based on failure information received from the failure detection unit. At this time, the AI ​​module (2500) can store information such as the cause of the failure, the details of the measures taken, and the recovery time in a database when a failure occurs. At this time, the AI ​​module (2500) can search for a failure measure if the received failure information is determined to be a failure. For example, the AI ​​module (2500) can search for a failure measure based on the type of failure included in the failure information. In particular, the AI ​​module (2500) can collect the failure information received from the failure detection unit and the failure measure information processed thereafter by the failure processing unit, and then learn the data through machine learning.

[0803] In one embodiment, the AI ​​module (2500) can use the collected information to predict the cause or type of a failure using a classification algorithm such as Logistic Regression, Decision Trees, Random Forest, or Support Vector Machines. In addition, the AI ​​module can use a regression algorithm such as Linear Regression, Ridge Regression, Lasso Regression, or Polynomial Regression to predict the time of failure occurrence or duration. In addition, the AI ​​module (2500) can use a clustering algorithm such as K-Means or Hierarchical Clustering to group failures with similar characteristics. In addition, the AI ​​module (2500) can use a time series analysis algorithm such as ARIMA or LSTM to predict the pattern or frequency of failure occurrence.

[0804] Based on learned data, when a first fault of the same type occurs, the AI ​​module (2500) can provide a first fault action with the highest hit rate (the hit rate will be described later) corresponding to the first fault as a fault handling guide. In this case, the fault handling guide may include a fault search function and an API linkage service function, as described later. In this case, the guide may include a hit rate.

[0805] In one embodiment, the AI ​​module (2500) may provide a failure handling guide including a hit rate to the user through a user interface.

[0806] The fault handling unit (2305) can resolve the fault using the methods included in the fault handling guide received via the AI ​​module. Alternatively, the user can review the fault handling guide and take action to actually resolve the fault.

[0807] In one embodiment, the fault handling unit (2305) may receive input from the user regarding the action to be taken regarding the fault. Specifically, the user may perform actions to resolve the fault and then input the action details through the user interface. Furthermore, the user may input an evaluation of the fault handling guide received from the AI ​​module (2500). This will be described in detail in the drawings below.

[0808] The fault processing unit (2305) can transmit the received action details and the evaluation details from the user to the AI ​​module (2500).

[0809] The AI ​​module (2500) can compare the fault handling guide provided to the fault handling unit with the action details received from the fault handling unit and the evaluation details from the user.

[0810] At this time, the AI ​​module (2500) can update the hit rate based on the method initially provided in the troubleshooting guide and the degree of resolution of the received action. To this end, the AI ​​module (2500) can collect and analyze the action details and scores for the action entered by the user.

[0811] Additionally, in one embodiment, the AI ​​module (2500) can perform natural language processing (NLP). For example, a user may input natural language as an evaluation for the fault handling guide. In this case, the AI ​​module (2500) can process the input natural language and reflect it in the hit rate included in the fault handling guide.

[0812] Here, the hit rate may represent the probability that the first failure will be resolved with the first action for the first failure. The AI ​​module (2500) may learn the first action for the first failure, the received action details, and the user evaluation history, and index and store information about the first failure, the hit rate for the first action for the first failure, and the actual user action details for the first failure. At this time, the AI ​​module (2500) may perform the indexing using major keywords related to the failure message.

[0813] Additionally, if the AI ​​module (2500) includes a new action (e.g., a second failure action) in the action details and evaluation details received from the failure processing unit (2305), the AI ​​module (2500) may register the second failure action as a solution to the first failure. Similarly, the AI ​​module (2500) may index and store the second failure action details for the first failure and the user evaluation details for the second failure action.

[0814] Accordingly, if the first fault is reported again in the future, the AI ​​module (2500) can provide a fault handling guide with a higher accuracy rate. In this case, the AI ​​module (2500) can utilize a deep learning-based recommendation system to provide a fault handling guide based on the accuracy rate through classification and indexing by fault type.

[0815]

[0816] Figure 66 is a drawing explaining a method for handling a failure of the present invention.

[0817] This drawing is a drawing that sequentially explains the operation method of the above-described failure notification module (2300) and AI module (2500).

[0818] In one embodiment, the fault notification module (2300) may provide a user interface screen to the user to provide information related to the fault.

[0819] When a failure notification module (2300) detects a failure, it can transmit the received failure information to the AI ​​module (2500).

[0820] The AI ​​module (2500) can determine whether a failure exists based on the received failure information. At this time, the AI ​​module (2500) can determine whether a failure exists by learning from the database maintained by the interface governance platform. The algorithm that the AI ​​module (2500) uses to determine whether a failure exists is described above.

[0821] The AI ​​module (2500) can provide users with troubleshooting guidance for identified troubleshooting issues. In one embodiment, for troubleshooting issues that do not require direct action from the user (e.g., when a troubleshooting method with a 100% resolution rate and 100% accuracy exists), the AI ​​module (2500) can provide users with troubleshooting guidance and automatically handle the troubleshooting issue through the troubleshooting notification module (2300). In this case, the troubleshooting issues that are automatically handled are limited to preset troubleshooting issues.

[0822] Users can review the fault handling guide and register the details of the fault handling and the evaluation of the fault handling guide on the user interface screen provided by the fault notification module (2300). The AI ​​module (2500) can reflect the details of the fault handling performed by the user in the fault handling results and hit rate. Based on the received information, the AI ​​module (2500) can index the fault type and use it as reference material for the next fault report.

[0823] At this time, the AI ​​module (2500) can provide users with external linkage API services. The AI ​​module (2500) can provide a standard API that collects various failure information from linked target systems as well as integrated solutions, and accumulates and utilizes solutions to respond to failures.

[0824]

[0825] Below, we will describe the following: a fault handling screen that handles a fault that has occurred, a fault statistics screen that displays fault statistics, and a fault handling status monitoring screen that provides a service for searching for fault remedies. As described above, if a problem occurs in an interface at the business level, it is referred to as a fault. If a fault occurs and causes a problem in at least one specific system or operation, it can also be referred to as a fault. Therefore, in the following examples, the term "fault" will be used.

[0826]

[0827] Figure 67 is a drawing explaining a failure processing screen of the present invention.

[0828] This drawing illustrates a fault handling screen provided by the fault notification module. The user interface provider described above can provide a fault handling screen like this drawing to the user.

[0829] Additionally, the fault handling screen may include fault type, fault history, and fault handling details.

[0830] Each failure type may include, for example, DB_Error, FILE_Error, and SOAP_Error.

[0831] A fault history may include at least one fault information. Here, the fault information may include a fault type, fault code, processing status, fault occurrence time, interface ID, interface name, fault group, sending system name, etc.

[0832] Additionally, the fault handling screen may include a fault search function that can search fault history based on fault occurrence time, fault group, system name, interface ID, fault code, processing status, fault message, and fault level.

[0833] Additionally, the fault handling screen may include fault handling details. These details may include a processing status, a fault message, and a fault handling details input window. Users can directly enter action details in the processing status, fault message, and fault handling details.

[0834] In one embodiment, a user may select at least one fault information contained in a fault history and then input a fault handling history. That is, the fault notification module may store fault handling history for multiple retrieved fault histories.

[0835] Afterwards, the failure notification module can transmit the failure processing details entered by the user to the AI ​​module.

[0836]

[0837] Figure 68 is a drawing explaining the disability statistics screen of the present invention.

[0838] This drawing illustrates a failure statistics screen provided by the failure notification module. The user interface provider described above can provide a failure analysis screen like this drawing to the user.

[0839] The failure statistics screen may include a failure type-specific occurrence distribution graph, a failure type-specific occurrence trend graph, a failure code-specific processing information graph, and failure code-specific detailed information. At this time, the failure statistics screen may output a failure type-specific occurrence distribution graph, a failure type-specific occurrence trend graph, a failure code-specific processing information graph, and failure code-specific detailed information based on a set period (e.g., one month, one week, one day, or a pre-set period).

[0840] The occurrence distribution graph by failure type corresponds to a graph that shows the percentage of the total proportion of whether the failure type is messaging, data, or default. In addition, the occurrence trend by failure type corresponds to a graph of the number of occurrences by date for the error types of messaging, data, and default. In addition, the processing information by failure code corresponds to a graph of the number of processing times for failure codes (e.g., JCO_001, TRAN_002, ETC_000, MAP_001, MSG_005, etc.). In addition, the detailed information by failure code may indicate each failure code for each failure type (messaging, data, default) and include the number of occurrences and occurrence rate for each failure code.

[0841] Through this, users can check the statistical results of the failure over a period of time.

[0842]

[0843] Figure 69 is a drawing explaining a monitoring screen for a failure processing situation of the present invention.

[0844] This drawing illustrates a fault handling status monitoring screen provided by the fault notification module. The user interface providing unit described above can provide a fault handling status monitoring screen like this drawing to the user.

[0845] The fault handling status monitoring screen may include a list of faults according to fault type classification.

[0846] Fault types can include Application Type, Data Type, Mapping Type, Messaging Type, Security Type, and System Type. The list of faults contained within a fault type can be classified based on the fault's processing status. For example, the processing status can be classified as ERROR CLOSE, ERROR OPEN, or ERROR PENDING.

[0847] In one embodiment, a user may select a list of faults whose current processing status is ERROR OPEN among the first fault type (e.g., Messaging) among the fault types. Accordingly, the fault notification module may output a list of faults whose fault type is Messaging and whose current processing status is ERROR OPEN. At this time, the list of faults may include a fault code, fault type, status, fault occurrence time, interface name, transmitting system, receiving system, fault details, and fault level.

[0848] A user can select at least one fault from the list of faults and change the fault handling details. The fault handling details may include the processing status, fault content, and action details. Accordingly, the user can input, edit, and search the fault handling details for the first through nth faults.

[0849]

[0850] Figure 70 is a flowchart disclosing an interface management method of the present invention.

[0851] In one embodiment, the interface management method may provide a failure handling guide based on failure information about the detected failure when a failure of the computing system is detected (S1010).

[0852] In one embodiment, the interface management method can determine whether a failure has been detected through an AI module when a failure is detected. For details, refer to the details described above in FIG. 65.

[0853] Additionally, the interface management method can provide a fault handling guide based on fault information. The fault handling guide can include a hit rate for fault-responsive actions. Furthermore, the fault handling guide can include a fault search function and an API linkage service function.

[0854] In one embodiment, the interface management method can handle a failure based on a failure handling guide (S1020).

[0855] In one embodiment, the interface management method can handle failures based on a failure handling guide provided through the AI ​​module. Furthermore, in another embodiment, the user can directly handle failures based on the failure handling guide. To this end, the user can check the details of measures taken for previously occurring failures through the failure search function.

[0856] In one embodiment, the interface management method can register the action details of the processed fault and the evaluation details of the fault handling guide (S1030).

[0857] In one embodiment, the interface governance platform may process a failure based on a failure handling guide provided through an AI module, and register the actions taken for the processed failure and the evaluation details of the failure handling guide. For example, the evaluation details of the failure handling guide may include a survey content such as, "When the first failure action was performed for the first failure, the first failure was resolved 100%." ​​In one embodiment, the interface management method may update the failure handling guide for the failure based on the actions taken for the processed failure and the evaluation details of the failure handling guide. For example, the interface management method may provide the first failure action as the failure handling guide when the first failure occurs, with the existing hit rate of the first failure action for the first failure being 100%. However, the AI ​​module may actually receive a survey content such as, "None of the failures were resolved" as a result of performing the first failure action for the first failure. At this point, the AI ​​module can lower the accuracy of the first action for the first failure to 50%. This can of course vary based on the size of the population.

[0858] In one embodiment, the interface management method may group or index at least one of the failure information, the failure handling guide, the action taken for the failure, and the evaluation history of the failure handling guide by failure type.

[0859]

[0860] Figure 71 is a drawing disclosing an example of an interface governance system according to an embodiment providing an integrated solution linkage service.

[0861] In the illustrated example, the interface governance system (10000) may include an interface monitoring module. The interface monitoring module may include a reference information management module (1100) and a development automation module (1400). While the modules related to the present invention will be described herein, reference will be made to the embodiment of FIG. 2 described above for other components.

[0862] The development automation module (1400) can perform integration with the integrated solution to extract at least one object for each interface service component of the integrated solution. An embodiment performing integration with the integrated solution is described in detail below. In one embodiment, at least one object may be referred to as interface service component information or a term having an equivalent technical meaning thereto. In one embodiment, the development automation module (1400) can convert the object for the extracted interface service component into a standardized format and store it in the interface information storage of the reference information management module (1100).

[0863] In one embodiment, the development automation module (1400) can perform transitions between integrated solutions by converting objects for interface service components. In one embodiment, the development automation module (1400) can migrate objects for interface service components for reuse in integrated solution upgrades. Therefore, according to the present invention, development productivity and quality can be improved when performing transitions and upgrades of integrated solutions.

[0864] In one embodiment, the automation module (1400) can perform tests in conjunction with the integrated solution. In one embodiment, verification tests can be performed by comparing end-to-end input / output messages in the integrated solution with end-to-end input / output messages in the converted or upgraded target integrated solution based on objects for interface service components. Detailed embodiments thereof are described below. Therefore, according to the present invention, human error can be prevented through service automation, automation registration, and test automation linkage based on objects for interface service components.

[0865] In this example, the interface governance platform (10000) may be connected to an external cloud system or an on-premise system via an API or the like. In one embodiment, the interface governance platform (10000) may be controlled and managed by a control system (100). The control system (100) may include a computer server (110) having at least one processor and a storage or database (120), which may be used to control and manage the interface governance platform (10000). For further details, please refer to the descriptions given in FIGS. 1 to 3 .

[0866]

[0867] Figure 72 is a drawing disclosing another example of an interface governance system according to an embodiment providing an integrated solution linkage service.

[0868] In one embodiment, the interface governance system (10000) may include a reference information management module (1100) and a development automation module (1400). At this time, the components included in the reference information management module (1100) and the development automation module (1400) are distinguished to explain the functions performed by the reference information management module (1100) and the development automation module (1400), and are not limited to the names of the components.

[0869] The development automation module (1400) may include a component information extraction unit (1403), a solution conversion unit (1404), a solution upgrade unit (1405), and a solution testing unit (1406).

[0870] The component information extraction unit (1403) can access at least one object of an interface service component within the repository of the integrated solution. In one embodiment, target information for an interface service component may include a message structure, a user-developed function, connection adapter information, data conversion rules, and log data. For more information, please refer to the above description.

[0871] In one embodiment, the component information extraction unit (1403) may perform external access integration of the integrated solution. In one embodiment, the component information extraction unit (1403) may directly access a repository within the integrated solution. In one embodiment, the component information extraction unit (1403) may perform integration with the integrated solution through an API provided by the integrated solution. In one embodiment, the component information extraction unit (1403) may perform integration with the integrated solution through a log collection agent included in the integrated solution.

[0872] Additionally, the component information extraction unit (1403) can extract objects of interface service components from the linked integrated solution. In one embodiment, the objects of the interface service components can be extracted in a format corresponding to the type of the integrated solution. Additionally, the component information extraction unit (1403) can convert the extracted objects of the interface service components into a standardized format and store them in the interface information storage (1110) of the reference information management module (1100).

[0873] The solution conversion unit (1404) can perform conversion between integrated solutions by converting at least one object for the interface service component according to the format of the target integrated solution. In one embodiment, the solution conversion unit (1404) can perform service automation for the target integrated solution using the at least one converted object. A detailed embodiment of this is described below.

[0874] The solution upgrade unit (1405) can perform an upgrade of the integrated solution by migrating at least one object for the interface service component from the integrated solution to the upgraded target integrated solution. In one embodiment, the solution upgrade unit (1405) can link the automated registration of the interface service component through the above-described migration. A detailed embodiment of this is described below.

[0875] The solution test unit (1406) can perform integrated solution linkage testing based on test data according to the integrated solution, based on at least one object for the interface service component. Here, the integrated solution being tested may include at least one of a converted integrated solution or an upgraded integrated solution. In one embodiment, the solution test unit (1406) can perform the linkage testing through comparative verification between log data and test data.

[0876]

[0877] Figure 73 is a flowchart disclosing an example of an interface management method according to an embodiment performing a transition between integrated solutions.

[0878] At least one object for an interface service component of an integrated solution is acquired (S1110). In one embodiment, the object of the interface service component may be converted into a standardized format. In one embodiment, the object of the interface service component may be acquired from a standardized and stored interface information repository.

[0879] At least one object for an interface service component is converted according to the format of the target integration solution (S1120). In one embodiment, the format of the target integration solution may include at least one of the format, protocol, or form of the integration solution. For example, an object for an interface service component of a web method-based integration solution may be extracted and converted into the format of an SAP PO-based integration solution. In one embodiment, at least one converted object may be automatically registered for the target integration solution.

[0880] A linkage service for the target integrated solution is provided based on at least one converted object (S1130). In one embodiment, the linkage service for the converted target integrated solution can be performed by converting an object of an interface service component according to the integrated solution. In one embodiment, the at least one converted object can be used for test verification of the corresponding integrated solution. For this, please refer to the details described above in FIG. 72.

[0881]

[0882] Figure 74 is a flowchart disclosing an example of an interface management method according to an embodiment performing an upgrade of an integrated solution.

[0883] At least one object for an interface service component of an integrated solution is acquired (S1210). In one embodiment, the object of the interface service component may be converted into a standardized format. In one embodiment, the object of the interface service component may be acquired from a standardized and stored interface information repository.

[0884] At least one object for the interface service component is migrated from the integrated solution to the upgraded target integrated solution (S1220). In one embodiment, the object for the interface service component of the integrated solution before the upgrade can be used for the same target information of the upgraded target integrated solution. In other words, the object for the interface service component can be moved from the integrated solution to the target integrated solution. In one embodiment, at least one migrated object can be automatically registered for the upgraded integrated solution.

[0885] At least one object provides a linkage service for the target integrated solution to which it has been migrated (S1230). In one embodiment, at least one object for the interface service component can be reused in the target integrated solution to which it has been upgraded. In one embodiment, at least one migrated object can be used as connection information for the corresponding integrated solution. In one embodiment, at least one migrated object can be used for test verification of the corresponding integrated solution. For this, please refer to the details described above in FIG. 72.

[0886]

[0887] Figure 75 is a flowchart disclosing an example of an interface management method according to an embodiment providing an integrated solution linkage service.

[0888] At least one object for the interface service component of the integrated solution is acquired (S1310). In one embodiment, the object of the interface service component may be converted into a standardized format. For this, refer to the description above in FIG. 72.

[0889] A linkage service for the integrated solution is provided based on at least one object for the interface service component (S1320). In one embodiment, at least one object for the interface service component may be converted according to the format of the target integrated solution, and a linkage service for the target integrated solution may be provided based on at least one converted object.

[0890] In one embodiment, at least one object for an interface service component may be migrated from an integrated solution to a target integrated solution that has been upgraded, and a linkage service may be provided for the target integrated solution to which at least one object has been migrated.

[0891] In one embodiment, test data for an integrated solution may be generated based on at least one object for an interface service component, and interface verification testing for the integrated solution may be performed based on the test data. For details, refer to the descriptions in FIGS. 71 and 72 .

[0892]

[0893] Figure 76 is a diagram disclosing an example of an interface governance system according to an embodiment managing a distributed interface solution.

[0894] In the illustrated example, the interface governance system (10000) according to the embodiment can receive monitoring data for the computing system from a distributed agent adapter (10) that provides a distributed interface solution different from the interface provided by the integrated solution installed in at least one computing system among an on-premise computing system or a cloud computing system.

[0895] The distributed agent adapter (10) can have different software (S / W) and hardware (H / W) architecture configurations depending on the transaction volume and the number of target computing systems, and can operate as an agent or hub depending on the support scale. For this, please refer to the contents described above in Fig. 4.

[0896] In one embodiment, when a distributed agent adapter (10) is installed in an on-premise computing system (indicated by A in this drawing), it can provide a hub technology that can link and integrate multiple computing systems.

[0897] In one embodiment, the distributed agent adapter (10) can transmit a message received from an on-premise computing system to an integrated solution installed in a cloud computing system (indicated by B in this drawing). In one embodiment, the distributed agent adapter (10) can transmit a message received from an integrated solution installed in a cloud computing system to an on-premise computing system (indicated by C in this drawing).

[0898] In one embodiment, the distributed agent adapter (10) can transmit messages between on-premise computing systems that are linked with an integration solution installed in a cloud computing system (represented by D in this drawing). According to the present invention, the distributed agent adapter (10) can include various adapters that integrate computing systems with heterogeneous protocols. For example, the adapter can include a JDBC adapter for connecting to a DBMS system, a FILE adapter for connecting to an FTP server, an RFC adapter for connecting to an SAP system, and other HTTP / SOAP adapters. In addition, the distributed agent adapter (10) can provide additional custom adapters to replace adapters that the integration solution does not support or that have limitations. This will be described in detail below.

[0899] In one embodiment, the distributed agent adapter (10) may support an XML-SQL structure for data transmitted for linkage between the integrated solution and the DBMS target system. For example, if the integrated solution supports an XML-SQL structure, the distributed agent adapter (10) may also support an XML-SQL structure, thereby enabling interoperability or role switching between the two without additional interface modifications.

[0900] According to the present invention, the distributed agent adapter (10) can provide an adapter not provided by an integrated solution installed in at least one computing system, either an on-premise computing system or a cloud computing system. In one embodiment, the distributed agent adapter (10) can supplement the standard adapter function by converting non-standard protocols and data formats that cannot be processed through the standards provided by the integrated solution.

[0901] As exemplified, the distributed agent adapter (10) can be installed in a distributed manner on each system, thereby isolating some of the adapter functions of the integrated solution, thereby reducing the load on processing data from various interfaces and processing events or log data that occur, and can have the effect of distributing actual resources.

[0902] According to the present invention, the distributed agent adapter (10) minimizes delay speed by compressing transmission data in a physical long-distance network section between the integrated solution and the distributed agent adapter (10), shortens the data conversion process, maximizes performance by processing data input / output reflecting the characteristics of the computing system, and can efficiently process large amounts of data.

[0903] Additionally, the distributed agent adapter (10) can perform load balancing by distributing resources by separating the adapter linked to the target computing system separately from the integrated solution.

[0904] In addition, the distributed agent adapter (10) can perform security authentication and encryption of transmitted data between the integrated solution and the distributed agent adapter (10), thereby acting as a secure connection proxy for linking with a cloud service.

[0905] In one embodiment, the interface governance platform (10000) can monitor at least one computing system using monitoring data. In one embodiment, the interface governance platform (10000) can manage the status of an installed distributed agent adapter (10) and can also register the distributed agent adapter (10) with a cloud computing system or an on-premise computing system.

[0906] In one embodiment, the interface governance system (10000) may include a log collection module (2100) and a control module (2200). While the modules related to the present invention will be described herein, reference will be made to the embodiment of FIG. 2 described above for other components.

[0907] The log collection module (2100) can receive monitoring data for a computing system from a distributed agent adapter that provides a communication protocol not provided by an integrated solution installed in at least one computing system among an on-premise computing system or a cloud computing system.

[0908] The control module (2200) can perform computing system monitoring using monitoring data.

[0909]

[0910] FIG. 77 is a diagram disclosing another example of an interface governance system according to an embodiment managing a distributed interface solution.

[0911] In one embodiment, the interface governance system (10000) may include a log collection module (2100) and a control module (2200). At this time, the components included in the log collection module (2100) and the control module (2200) are distinguished to explain the functions performed by the log collection module (2100) and the control module (2200), and are not limited to the names of the components.

[0912] The log collection module (2100) can receive monitoring data from the distributed agent adapter.

[0913] The control module (2200) may include a message monitoring module (2213) and a service management module (2214).

[0914] The message monitoring module (2213) can monitor monitoring data received from the distributed agent adapter. In one embodiment, the message monitoring module (2213) can monitor at least one of aggregate information, statistical information, and distribution information of log data included in the monitoring data.

[0915] The service management module (2214) can monitor registration information, management information, and service status information for the distributed agent adapter. Here, the service status information can include status information on whether the distributed interface solution provided by the distributed agent adapter is operating normally.

[0916] In one embodiment, the service management module (2214) may monitor screen linkage information. For example, the service management module (2214) may link at least one of the management screen and the monitoring screen of the distributed agent adapter.

[0917] In this example, the interface governance platform (10000) may be connected to an external cloud system or an on-premise system via an API or the like. In one embodiment, the interface governance platform (10000) may be controlled and managed by a control system (100). The control system (100) may include a computer server (110) having at least one processor and a storage or database (120), which may be used to control and manage the interface governance platform (10000). For further details, please refer to the descriptions given in FIGS. 1 to 3 .

[0918]

[0919] FIG. 78 is a drawing disclosing an example of a distributed agent adapter providing a distributed interface solution according to an embodiment.

[0920] In the illustrated example, the distributed agent adapter (10) may include a sender adapter and a receiver adapter that send and receive messages to and from at least one computing system among an on-premise computing system and a cloud computing system based on a distributed interface solution.

[0921] In one embodiment, the distributed agent adapter (10) may include at least one of a protocol adapter that converts a communication protocol not provided by the integrated solution (23), a format conversion adapter that converts a data format not provided by the integrated solution (23), and an additional adapter that provides additional functions other than the adapter provided by the integrated solution (23). For example, the protocols and data formats provided by the distributed agent adapter (10) may include, but are not limited to, HTTP, SOAP, RFC, FILE, and DBMS, and may support various types of protocols and data formats.

[0922] Additionally, in one embodiment, the distributed agent adapter (10) may include a control server that performs a distributed interface solution. In this case, the control server may perform at least one of a service management function, an adapter configuration function, a scheduling function, a monitoring function, and a security management function.

[0923] In one embodiment, the service management function may provide an I / F service linked to the integrated solution (20). In addition, the service management function may perform creation, registration, and matching of adapters and adapter resources. In one embodiment, the adapter configuration function may set properties for each adapter. In one embodiment, the scheduling function may perform polling and scheduling for services of the adapter and distributed interface solution. In one embodiment, the monitoring function may monitor at least one of statistical information, aggregated information, and log data for monitoring data. In one embodiment, the security management function may set certificates and security information based on the linkage with the integrated solution (23).

[0924] In one embodiment, the control server provides an open API and can perform solution management functions based on the open API. For example, the control server can transmit monitoring data to the interface governance platform (10000) using the open API. According to the present invention, the performance and functional aspects of the integrated solution (23) can be supplemented through the distributed agent adapter (10).

[0925]

[0926] Figure 79 is a drawing disclosing an example of a standalone configuration of a distributed agent adapter according to an embodiment.

[0927] In the illustrated example, the distributed agent adapter (10) can operate as an agent when the transaction volume is less than a threshold or when interoperating with a single computing system. In this case, the distributed agent adapter (10) can support the linkage supplementation (e.g., function, supplementation) of a single target computing system in a standalone configuration.

[0928] In one embodiment, the distributed agent adapter (10) may be constructed as a single server in a standalone configuration when configuring hardware (H / W). In one embodiment, the distributed agent adapter (10) may be configured with one AP and one control server.

[0929] For example, if the distributed agent adapter (10) is configured as a standalone, the distributed agent adapter (10) may include at least one of Zookeeper, an adapter, a secure proxy, a control panel, and a metric exporter.

[0930] In this case, ZooKeeper can perform coordination for the distributed interface solution. Furthermore, the adapter can send and receive messages with at least one computing system, either an on-premise computing system or a cloud computing system. The security proxy performs a secure connection for linking with the integrated solution and can maintain security by encrypting and decrypting data and controlling internal and external data access. The control panel can include a processor that controls the operation of the distributed agent adapter (10). The metric exporter can collect metrics from the target computing system and transmit them to an endpoint on the other end (e.g., an interface governance system (10000)).

[0931]

[0932] FIG. 80 is a diagram disclosing an example of an HA configuration of a distributed agent adapter according to an embodiment.

[0933] In the illustrated example, the distributed agent adapter (10) can act as a hub when the transaction volume exceeds a threshold and is linked to multiple computing systems. In this case, the distributed agent adapter (10) can support dynamic and horizontal expansion by linking multiple target computing systems in an HA (High Availability) configuration.

[0934] In one embodiment, the distributed agent adapter (10) may be configured with hardware (H / W) allocated to each server role in an HA configuration. In addition, the distributed agent adapter (10) may be configured with multiple APs and one control server.

[0935] For example, if the distributed agent adapter (10) is configured as HA, the AP of the distributed agent adapter (10) may include at least one of a zookeeper, an adapter, and a security proxy. In addition, the control server of the distributed agent adapter (10) may include at least one of a zookeeper, a control panel, and a metric exporter.

[0936] In one embodiment, a distributed agent adapter (10) configured with HA can be assigned a large transaction per AP unit by a load balancer.

[0937]

[0938] Figure 81 is a flowchart disclosing an example of an interface management method according to an embodiment providing an integrated solution linkage service.

[0939] Monitoring data for a computing system is received from a distributed agent adapter that provides a distributed interface solution different from the interface provided by an integrated solution installed on at least one computing system, either an on-premise computing system or a cloud computing system (S1410). In one embodiment, the distributed agent adapter can transmit messages between a first computing system and a second computing system that are linked to the integrated solution.

[0940] In one embodiment, the distributed interface solution may perform at least one of a protocol adapter function that converts a communication protocol not provided by the integrated solution, a format conversion adapter function that converts a data format not provided by the integrated solution, and an additional adapter function that provides additional functionality other than the adapter provided by the integrated solution.

[0941] In one embodiment, the distributed interface solution may receive a message from at least one of the first computing system or the second computing system, encrypt the received message according to a security policy between the distributed agent adapter and the integrated solution, and transmit the encrypted message to the integrated solution. That is, according to the present invention, a message may be encrypted and transmitted through the distributed interface solution of the distributed agent adapter, which acts as a security proxy.

[0942] In one embodiment, the interface management method may receive monitoring data for the transmission of the message or the reception of the message from the distributed agent adapter.

[0943] In one embodiment, the distributed interface solution may receive a message containing encoded first data from the integrated solution, decrypt the encoded message, and transmit second data generated by decrypting the message to at least one of the first computing system and the second computing system. That is, according to the present invention, the distributed interface solution of the distributed agent adapter may receive a message containing compressed data from the integrated solution, decrypt the message, and transmit it to the computing system, thereby reducing network latency.

[0944] In one embodiment, the distributed interface solution may execute various functions of a distributed agent adapter.

[0945] In one embodiment, the interface management method may receive monitoring data regarding the encoding or decoding of the message from the distributed agent adapter. For details, refer to the contents described above in FIGS. 76 to 78.

[0946] The received monitoring data is used to monitor at least one computing system (S1420). In one embodiment, the monitoring data may include at least one of registration information for the distributed agent adapter, management information, service status information for the distributed agent adapter, log data, and screen linkage information. For more information, please refer to the details described above in FIG. 78.

Claims

1. Step of registering interface-related information related to the application solution of the computing system to the interface governance platform; A step of receiving data related to the interface from the computing system through the interface governance platform; wherein the data related to the above interface includes log data; and A step of monitoring data related to the received interface or managing the computing system based on the registered interface related information; Including, The above monitoring or management steps are: A step of generating work-related interface monitoring information from the log data based on pre-stored interface-related reference information; and A step of providing the above work-related interface monitoring information through a user interface; Including, How to manage interfaces.

2. In paragraph 1, The above monitoring or management steps are: A step of registering reference information of an interface related to an application solution of the above computing system; A step of generating interface identification information based on the reference information of the above interface; and A step of providing a definition document for constructing the above interface; Including, How to manage interfaces.

3. In paragraph 1, The above monitoring or management steps are: A step of providing a user interface (UI) for managing an interface related to an application solution of the computing system; A step for verifying the authority of a user accessing the above user interface; and A step of requesting development of the interface according to the interface application request of the above user; Including, How to manage interfaces.

4. In paragraph 1, The above monitoring or management steps are: A step for providing a screen for creating a mapping definition for interface creation based on the reference information of the saved interface; and A step of generating the interface based on the above mapping definition and the above reference information; Including, How to manage interfaces.

5. In paragraph 1, The above receiving step is, A step of obtaining collector setting information set by user input; and A step of receiving log data for at least one step included in an interface-related process of an integrated solution using a selected log collector based on the acquired collector setting information; Including, The above monitoring or management steps are: A step for performing computing system monitoring using the above collected log data; Including, How to manage interfaces.

6. In paragraph 1, The above monitoring or management steps are: A step of generating at least one of monitoring information or management setting information corresponding to a business manager based on the above log data; and A step of providing at least one of the monitoring information or management setting information through a user interface; Including, How to manage interfaces.

7. In paragraph 1, The above monitoring or management steps are: A step of detecting a failure of at least one of the computing system or interface from the log data based on predefined failure determination criteria information; and A step of providing at least one of failure information or failure action guide according to the detected failure; Including, How to manage interfaces.

8. In paragraph 1, The above monitoring or management steps are: A step of detecting a failure occurring through an interface of the above computing system; A step of applying preset notification rules and templates to the detected fault; and Step for sending a notification for a failure to which the above-mentioned preset notification rules and templates are applied; Including, How to manage interfaces.

9. In paragraph 1, The above monitoring or management steps are: A step for providing a failure handling guide based on failure information about the detected failure when a failure of the computing system is detected; A step for processing the above-mentioned fault based on the above-mentioned fault processing guide; and A step for registering the details of the measures taken for the above-mentioned processed obstacle and the evaluation details of the above-mentioned obstacle processing guide; Including, How to manage interfaces.

10. In paragraph 1, The above monitoring or management steps are: A step of obtaining at least one object for an interface service component of the integrated solution; and A step of providing a linkage service for the integrated solution based on at least one object for the above interface service component; Including, How to manage interfaces.

11. In paragraph 1, The above receiving step is, A step of receiving monitoring data for a computing system from a distributed agent adapter providing a distributed interface solution different from the interface provided by an integrated solution installed on at least one computing system among an on-premise computing system and a cloud computing system; Including, The above monitoring or management steps are: A step of monitoring the at least one computing system using the received monitoring data; Including, Here, the distributed agent adapter transmits messages between the first computing system and the second computing system that are linked with the integrated solution. How to manage interfaces.

12. A database that stores data; and Including a processor for processing the above data, The above processor, Register interface-related information related to application solutions of computing systems to the interface governance platform, Through the above interface governance platform, data related to the above interface is received from the above computing system, Here, data related to the above interface includes log data, Based on pre-stored interface-related reference information, business-related interface monitoring information is generated from the log data, Providing the above work-related interface monitoring information through the user interface, Interface governance system.

13. Register interface-related information related to the application solution of the computing system on the interface governance platform, Through the above interface governance platform, data related to the above interface is received from the above computing system, Here, data related to the above interface includes log data, Based on pre-stored interface-related reference information, business-related interface monitoring information is generated from the log data, A storage medium storing a program executable by a computer that manages an interface, the program performing the step of providing the above-mentioned work-related interface monitoring information through a user interface.

Images