TWI836263B - Interface control system and method - Google Patents

Abstract

An interface control system including multiple software interfaces and a monitoring device is disclosed. The software interfaces are configured to transmit data to multiple software systems; the monitoring device is coupled to the software interfaces to: receive address information and a detection frequency, and perform error detection on a detected interface of the software interfaces according to the detection frequency, where the detected interface corresponds to the address information; and when determining that the detected interface is in an abnormal state, the detected interface is restarted according to an configuration file corresponding to the detected interface. In addition, an interface control system is also disclosed herein.

Description

Interface control system and method

The present disclosure relates to an interface control system and method.

In the process of software system integration, it is often encountered that the software interface stops responding due to massive amounts of basic data opened at the beginning of the period or improper writing of custom service applications, which not only makes all integrated functions unusable, but also affects the work of users. Therefore, how to prevent all integrated functions from being unusable and affecting the work of users is a problem that technical personnel in this field are eager to solve.

The interface control system disclosed in the present invention includes a plurality of software interfaces and a monitoring device. The software interfaces are used to transmit data to a plurality of software systems; the monitoring device is coupled to the software interfaces to: receive address information and a detection cycle, and perform error detection on a detected interface among the software interfaces according to the detection cycle, wherein the detected interface corresponds to the address information; and when the detected interface is determined to be in an abnormal state, the detected interface is restarted according to an interface configuration file corresponding to the detected interface.

Another aspect of the present disclosure discloses an interface control method, including: receiving address information and a detection cycle by a monitoring device, and performing error detection on a detected interface among multiple software interfaces according to the detection cycle, wherein the detected interface corresponds to the address information, wherein the software interfaces transmit data with multiple software systems, wherein the address information includes an interface name, a host address and an interface URL of the detected interface; and when the monitoring device determines that the detected interface is in an abnormal state, the monitoring device restarts the detected interface according to an interface configuration file corresponding to the detected interface.

The following disclosure provides many different embodiments or examples for implementing various features of the present disclosure. Particular illustrations of components and arrangements are used in the following discussion to simplify the present disclosure. Any examples discussed are for illustrative purposes only and do not limit in any way the scope and significance of this disclosure or its examples. Where appropriate, the same reference numbers are used in the drawings and corresponding text to represent the same or similar elements.

Please refer to FIG. 1 , which is a schematic diagram of an interface control system 100 according to an embodiment of the present disclosure. The interface control system 100 includes a plurality of software interfaces 110(1)~110(N) and a monitoring device 120, where N is any positive integer and is not particularly limited. The plurality of software interfaces 110 are respectively coupled to the plurality of software systems SP(1)~SP(N), and the monitoring device 120 is coupled to the software interfaces 110(1)~110(N).

In some embodiments, the interface control system 100 can be established by a computer, a server or a processing center.

In some embodiments, the software interfaces 110(1)~110(N) may be application programming interfaces or human-computer interaction interfaces, where the application programming interfaces may be, for example, Enterprise Process Management (EPM) interfaces or customer relationship management interfaces. (Customer Relationship Management, CRM) interface, Easy Flow GP interface, T100 interface or interconnection middle platform interface, etc. In addition, the software systems SP(1)~SP(N) may be any software applications or systems (eg, enterprise resource planning (Enterprise resource planning, ERP) system).

In some embodiments, the monitoring device 120 may be composed of electronic units such as a processing unit and a memory unit, wherein the processing unit may be implemented by a processor, a central processing unit or a computing unit, and the memory unit may be implemented using a memory, a flash memory, a read-only memory, a hard disk or any equivalent storage component.

In some embodiments, the monitoring device 120 is not limited to including a memory unit and a processing unit. The monitoring device 120 may further include other components required for operation and application. For example, the monitoring device 120 may further include an output interface (for example, using Display panels that display information), input interfaces (such as touch panels, keyboards, microphones, scanners or flash memory readers) and communication circuits (such as WiFi communication modules, Bluetooth communication modules, wireless telecommunications networks communication module, etc.).

In some embodiments, the monitoring device 120 is used to run the transceiver module 1201 and the detection module 1202 based on corresponding software/firmware instruction programs. The transceiver module 1201 is used for data transmission, and the detection module 1202 is used for error detection on the software interfaces 110(1)~110(N).

In some embodiments, the interface control system 100 further includes a user interface 130 and an alarm device 140. The user interface 130 is used to perform human-computer interaction with the user, and the alarm device 140 is used to notify the user that an interface error has occurred (for example, sending an alarm message to the user device used by the user to notify that an interface error has occurred).

Please also refer to FIG. 2 , which is a schematic diagram of an interface control method 200 according to an embodiment of the present disclosure. The interface control system 100 shown in FIG. 1 can be used to execute the interface control method 200 in FIG. 2 .

As shown in Figure 2, first, in step S210, the address information and the detection period are received, and error detection is performed on the tested interface among the multiple software interfaces according to the detection period, where the tested interface corresponds to the address information. In some embodiments, the address information includes the interface name, host address, and interface URL of the interface being inspected. The interface under test is one of the software interfaces 110(1)~110(N) to be error-detected, and the one of the software interfaces 110(1)~110(N) can be preset by the user. The interface name is the name of the interface under inspection. The host address (Host ID) is the address of one of the network hosts in the software systems SP(1)~SP(N) that is coupled to the interface under inspection. The interface URL (URL) is the URL of one of the software interfaces 110(1)~110(N) that is coupled to the inspected interface. The detection cycle includes the time stamp of the interface to be tested (for example, 12 a.m. on Monday of the first week of each month), and the time stamp can also be preset by the user. The detailed steps of step S210 in some embodiments will be further explained with specific examples later.

Then, in step S220, when it is determined that the tested interface is in an abnormal state, the tested interface is restarted according to the interface configuration file corresponding to the tested interface. In some embodiments, the abnormal state can be various software interface errors such as script errors, resource access errors, or system connection errors. The interface configuration file is a configuration file used to set the tested interface. The detailed steps of step S220 in some embodiments will be further explained in conjunction with specific examples.

In other words, in step S210, error detection is first performed on the interface under test. In step S220, it is determined whether to restart the tested interface based on the detection result.

Please refer to FIG. 3 , which is a flowchart showing detailed steps S211 to S212 of step S210 and detailed steps S221 to S222 of step S220 in some embodiments.

As shown in Figures 1 to 3, in step S211, the address information and detection period are set through the user interface 130. In some embodiments, the user interface 130 includes a graphical interface corresponding to the address information and a graphical interface corresponding to the detection period. In this way, users can input address information and detection periods respectively through these graphical interfaces. In some embodiments, the user interface 130 is further used to set the user's notification email address.

In step S212, the detection module 1202 performs error detection on the tested interface corresponding to the address information among the multiple software interfaces according to the detection cycle. In some embodiments, the transceiver module 1201 receives the address information and the detection period through the user interface 130 . In some embodiments, after setting the address information and detection period through the user interface 130, the detection module 1202 periodically performs the detection based on the set address information according to the timestamp in the set detection period. interface for error detection.

In some embodiments, after the notification mail address is set through the user interface 130, the detection module 1202 receives the notification mail address from the user interface 130 via the transceiver module 1201, and notifies the user of the detection result of the error detection according to the notification mail address, wherein the detection result includes the host address of the detected interface, the interface name and the interface status, wherein the interface status indicates an abnormal state or a normal state. In some embodiments, the transceiver module 1201 transmits the detection result to the mailbox of the user's notification mail address according to the return detection cycle, wherein the return detection cycle can be pre-stored in the monitoring device 120 (for example, it is set when the monitoring device 120 is shipped from the factory).

It is worth noting that although a single interface under inspection is taken as an example here, the present invention can also set multiple interfaces under inspection directly through address information, so as to perform error detection on these interfaces under inspection in subsequent steps. In addition, the notification email address may also include email addresses corresponding to multiple users, and the detection results may be used to notify these users.

Please also refer to FIG. 4 , which illustrates a schematic diagram of the graphical interface 400 in the user interface 130 according to some embodiments of this disclosure document.

As shown in FIG. 4 , the graphical interface 400 has an input interface corresponding to the address information and the notification mail address, so that the user can input the address information corresponding to the inspected interface. In addition, the input interface includes a field 410 for the interface name, a field 420 for the host address, a field 430 for the interface URL, a field 440 for the user name, and a field 450 for the notification mail address.

In this embodiment, the data entered by the user in field 410 are "interconnected middleware", "T100", "Easy Flow GP (EFGP)", "business process management (BPM)", and "customer relationship management (CRM)". The data entered by the user in field 420 are "10.20.86.123", "10.40.40.18", "10.20.9.142", "10.40.40.232", and "10.20.9.26". The data entered by the user in field 430 are "10.20.86.123.9999/IntegrationEntry?WSDL", "10.40.40.18/wt10dev/ws/r/awsp900?WSDL", "10.20.9.142/NaNaWeb/services/CrossIntegrationEFGP", "10.40.40.232/CRMINTService", and "10.20.9.26/NaNaWeb". The data entered by the user in field 440 are "02013" and "01275", where "02013" is the user's user name. The data entered by the user in field 450 are "abbylin@digiwin.com" and "lilan.chen@digiwin.com", where "abbylin@digiwin.com" is the user's notification email address.

Please also refer to FIG. 5 , which illustrates a schematic diagram of the graphical interface 500 in the user interface 130 according to some embodiments of this disclosure document.

As shown in FIG. 5 , the graphical interface 500 has an input interface corresponding to the detection period for the user to input a time stamp corresponding to the interface being tested. In addition, this input interface includes a field 510 for the month, a field 520 for the week, a field 530 for Sunday to Saturday, a field 540 for the time and period, and a field 550 for special instructions. Field 510 includes subfields corresponding to "monthly" and "monthly". Field 520 includes subfields corresponding to "weekly" and "weekly". Field 530 includes subfields corresponding to "weekly", "day", "optional" and "daily". Field 540 includes subfields corresponding to "specified execution time" and "specified cycle period." With this, the user can set the timestamp in fields 510~550.

Please also refer to FIG. 6 , which illustrates a schematic diagram of a graphical interface 600 in detection results according to some embodiments of this disclosure document.

As shown in Figure 6, the graphical interface 600 has an output interface corresponding to the detection results for the user to view the status of the currently tested interface. In addition, the output interface includes a field 610 for the interface name, a field 620 for the host address, a field 630 for the interface status, and a field 640 for the detection time. Through this, the user can know from the output interface whether the interface status of the inspected interface is normal or abnormal (for example, a tick icon indicates normal status, and a cross icon indicates abnormal status), and the user can also obtain Know the detection time of the interface under inspection.

In this embodiment, the user can know from the fields 610 and 630 in the output interface that the BPM interface, CRM interface, T100 interface and interconnection middle platform interface are all in normal status, while the EFGP interface is in abnormal status, and from the output interface Field 640 in can tell that the detection time of the tested interface is "14:58:54 on December 9, 2020".

As shown in FIGS. 1 to 3, in step S221, the detection circuit 1202 determines whether the detected interface is in an abnormal state. If the detected interface is not in an abnormal state, the process returns to step S212, and steps S212 and S221 are repeated to continuously perform abnormal detection on the detected interface. In some embodiments, the detection module 1202 performs error detection on the detected interface to determine whether various software interface errors such as script errors, resource access errors, or system connection errors occur.

If the interface under inspection is in an abnormal state, step S222 is entered. In step S222, the warning information is sent through the warning circuit 140. In some embodiments, the alert circuit 140 generates alert information based on the interface being checked, and notifies the user that an interface error has occurred based on the notification email address. Specifically, when the detection circuit 1202 determines that there is an abnormal state, the warning circuit 140 immediately sends a packet containing warning information to the mailbox of the user's notification email address to notify the user that an interface error has occurred.

In step S223, the detected interface is restarted by the detection module 1202. In some embodiments, the detection module 1202 transmits a configuration file request corresponding to the detected interface to the management server (not shown) of the management software system SP(1)~SP(N) via the transceiver module 1201. In response to the configuration file request, the management server returns the configuration file of the detected interface to the detection module 1202 via the transceiver module 1201. In this way, the detection module 1202 resets the detected interface by various setting parameters in the configuration file to restart it.

To sum up, the interface control system and method provided by the present invention allow each user to input various interfaces to be tested and the detection cycle at one time and quickly through its user interface, so as to perform error detection on the interfaces to be tested. In addition, the detection results can be notified to each user, and if an error occurs on the checked interface, each user can be notified immediately to restart the checked interface where the error occurred. In this way, the stability of the integrated operation can be improved, and through a one-time setting method, the self-detection, exception notification and self-restart of the interface can be achieved, thereby producing the effects of early warning and self-healing mechanisms. This can solve the customer operation problems that were caused in the past when integration interface anomalies seriously affected user operations, but could only be traced afterwards.

Although specific embodiments of the present disclosure have been disclosed with respect to the above-mentioned embodiments, these embodiments are not intended to limit the present disclosure. Various substitutions and improvements can be performed in the present disclosure by a person skilled in the art without departing from the principles and spirit of the present disclosure. Therefore, the scope of protection of the present disclosure is determined by the scope of the attached patent application.

100: Interface control system SP(1)~SP(N): Software system 110(1)~110(N): Software interface 120: Monitoring device 130: User interface 140: Alarm circuit 1201: Transceiver module 1202: Detection module 200: Interface control method S210~S220, S211~S212, S221~S223: Steps 400, 500, 600: Graphical interface 410~450, 510~550, 610~640: Fields

FIG. 1 is a schematic diagram of an interface control system according to one embodiment of the present disclosure. FIG. 2 is a schematic diagram of an interface control method according to one embodiment of the present disclosure. FIG. 3 is a flow chart of detailed steps of the interface control method in some embodiments. FIG. 4 is a schematic diagram of a graphical interface in a user interface according to some embodiments of the present disclosure. FIG. 5 is a schematic diagram of a graphical interface in a user interface according to some embodiments of the present disclosure. FIG. 6 is a schematic diagram of a graphical interface in a detection result according to some embodiments of the present disclosure.

100:Interface control system

SP(1)~SP(N): software system

110(1)~110(N): Software interface

120:Monitoring device

130: User interface

140: Warning circuit

1201: transceiver module

1202: Detection module

Claims (10)

An interface control system includes: a plurality of software interfaces for transmitting data to a plurality of software systems, wherein each of the software interfaces is an application program interface; a monitoring device coupled to the software interfaces for: receiving a preset address information and a detection cycle to set a detected interface from the software interfaces according to the address information, and performing error detection on the detected interface according to the detection cycle to detect whether a script error, a resource access error or a fault occurs in the detected interface The abnormal state of system connection error, wherein the address information includes an interface name, a host address and an interface URL of the detected interface, wherein the host address of the detected interface is the address of the network host of one of the software systems coupled to the detected interface, wherein the interface URL is the URL of the one of the software interfaces coupled to the detected interface; and when the detected interface is determined to be in the abnormal state, the detected interface is restarted according to an interface configuration file corresponding to the detected interface. The interface control system as described in claim 1, wherein the monitoring device is further used to: receive a notification email address, and notify a user of a detection result of the error detection based on the notification email address, wherein the detection The result includes the host address of the tested interface, the interface name, and the interface status, where the interface status indicates the abnormal state or normal state. The interface control system as described in claim 2 further includes: a user interface for the user to input the address information, the notification email address and the detection period. The interface control system as described in claim 3 further includes: an alarm device coupled to the monitoring device, wherein when the monitoring device determines that the detected interface is in the abnormal state, an alarm message is generated according to the detected interface, and the user is notified of an interface error according to the notification mail address. The interface control system as described in claim 1, wherein the software interfaces include an enterprise process management interface, a customer relationship management interface, Easy Flow GP interface, T100 interface and interconnection middle platform interface. An interface control method includes: receiving preset address information and a detection period through a monitoring device, setting a tested interface from a plurality of software interfaces according to the address information, and setting the interface according to the detection period. The inspected interface performs error detection to detect whether the inspected interface has an abnormal state such as a script error, a resource access error or a system connection error. These software interfaces transmit data with multiple software systems, and among these software interfaces Each of them is an application programming interface, wherein the address information includes an interface name, a host address and an interface URL of the inspected interface, wherein the host address of the inspected interface is one of the software systems associated with the interface. the address of one of the network hosts to which the interface under examination is coupled, The interface URL is the URL of one of the software interfaces that is coupled to the tested interface; and when the monitored interface is judged to be in an abnormal state by the monitoring device, the monitoring device is configured according to the An interface profile corresponding to the inspected interface restarts the inspected interface. The interface control method as described in claim 6 further includes: receiving a notification email address through the monitoring device, and notifying a user of a detection result of the error detection based on the notification email address, wherein the detection The result includes the host address of the tested interface, the interface name, and the interface status, where the interface status indicates the abnormal state or normal state. The interface control method as described in claim 7 further includes: providing a user interface for the user to input the address information, the notification email address, and the detection cycle. The interface control method as described in claim 8 further includes: when the monitoring device determines that the detected interface is in the abnormal state, a warning device coupled to the monitoring device generates a warning message according to the detected interface, and notifies the user that an interface error has occurred according to the notification mail address. The interface control method as described in request item 6, wherein these The software interface includes an enterprise process management interface, a customer relationship management interface, Easy Flow GP interface, T100 interface and interconnection middle platform interface.

Images