CN112202854B - Joint debugging method, device, equipment and medium - Google Patents
Joint debugging method, device, equipment and medium Download PDFInfo
- Publication number
- CN112202854B CN112202854B CN202010981186.9A CN202010981186A CN112202854B CN 112202854 B CN112202854 B CN 112202854B CN 202010981186 A CN202010981186 A CN 202010981186A CN 112202854 B CN112202854 B CN 112202854B
- Authority
- CN
- China
- Prior art keywords
- joint debugging
- target system
- joint
- request
- debugging
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/2866—Architectures; Arrangements
- H04L67/30—Profiles
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L61/00—Network arrangements, protocols or services for addressing or naming
- H04L61/45—Network directories; Name-to-address mapping
- H04L61/4505—Network directories; Name-to-address mapping using standardised directories; using standardised directory access protocols
- H04L61/4511—Network directories; Name-to-address mapping using standardised directories; using standardised directory access protocols using domain name system [DNS]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/02—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Debugging And Monitoring (AREA)
Abstract
The embodiment of the disclosure relates to a joint debugging method, device, equipment and medium, and relates to the field of cloud computing. The method is applied to a first joint debugging client and comprises the following steps: receiving a joint debugging request of a joint debugging source system of a local machine, wherein the joint debugging request comprises a domain name of a joint debugging target system, and the number of the joint debugging target systems is at least one; and forwarding the joint debugging request to the joint debugging target system for joint debugging based on a pre-configured joint debugging forwarding rule and the domain name of the joint debugging target system. By adopting the technical scheme, the joint debugging source system can simply and quickly forward the joint debugging request to the joint debugging target system through the first joint debugging client arranged by the local machine to realize joint debugging, and compared with the prior art, the acquisition of related information and the modification of system files during joint debugging at each time can be avoided, so that the workload is saved, and the joint debugging efficiency between the systems is improved.
Description
Technical Field
The present disclosure relates to the field of computer technologies, and in particular, to a joint debugging method, apparatus, device, and medium.
Background
In the prior art, in a scenario where multiple systems are dependent on each other, one system may generally request to implement in a Transmission Control Protocol (TCP) or hypertext Transfer Protocol (HTTP) manner in order to perform functional docking with another system.
In order to implement a correct request between two systems, it is usually necessary to modify relevant information in a configuration file of one system, such as an IP Address (Internet Protocol Address) and a port of the request. Before joint debugging is carried out between systems each time, related information of the other party needs to be acquired and configuration files need to be updated, and the process is complicated. And if one system is a front-end system, cross-domain problems may still exist, extra modification of system (Hosts) files or forwarding of requests by using a proxy mode are needed, and the workload is increased.
Disclosure of Invention
To solve the above technical problem or at least partially solve the above technical problem, the present disclosure provides a joint debugging method, apparatus, device, and medium.
The embodiment of the disclosure provides a joint debugging method, which is applied to a first joint debugging client and comprises the following steps:
receiving a joint debugging request of a joint debugging source system of a local machine, wherein the joint debugging request comprises a domain name of a joint debugging target system, and the number of the joint debugging target systems is at least one;
and forwarding the joint debugging request to the joint debugging target system for joint debugging based on a pre-configured joint debugging forwarding rule and the domain name of the joint debugging target system.
The embodiment of the present disclosure further provides a joint debugging device, where the device is configured at a first joint debugging client, and the device includes:
the joint debugging request receiving module is used for receiving a joint debugging request of a joint debugging source system of the local machine, wherein the joint debugging request comprises a domain name of a joint debugging target system, and the number of the joint debugging target systems is at least one;
and the joint debugging module is used for forwarding the joint debugging request to the joint debugging target system for joint debugging based on a pre-configured joint debugging forwarding rule and the domain name of the joint debugging target system.
An embodiment of the present disclosure further provides an electronic device, which includes: a processor; a memory for storing the processor-executable instructions; the processor is used for reading the executable instructions from the memory and executing the instructions to realize the joint debugging method provided by the embodiment of the disclosure.
The embodiment of the disclosure also provides a computer-readable storage medium, which stores a computer program for executing the joint debugging method provided by the embodiment of the disclosure.
Compared with the prior art, the technical scheme provided by the embodiment of the disclosure has the following advantages: according to the joint debugging scheme provided by the embodiment of the disclosure, a first joint debugging client receives a joint debugging request of a joint debugging source system of a local machine, wherein the joint debugging request comprises a domain name of a joint debugging target system, and the number of the joint debugging target systems is at least one; and forwarding the joint debugging request to a joint debugging target system for joint debugging based on a pre-configured joint debugging forwarding rule and the domain name of the joint debugging target system. By adopting the technical scheme, the joint debugging source system can simply and quickly forward the joint debugging request to the joint debugging target system through the first joint debugging client arranged by the local computer to realize joint debugging.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present disclosure and together with the description, serve to explain the principles of the disclosure.
In order to more clearly illustrate the embodiments or technical solutions in the prior art of the present disclosure, the drawings used in the description of the embodiments or prior art will be briefly described below, and it is obvious for those skilled in the art that other drawings can be obtained according to the drawings without inventive exercise.
Fig. 1 is a schematic flow chart of a joint debugging method according to an embodiment of the present disclosure;
fig. 2 is a schematic flow chart of another joint debugging method provided in the embodiment of the present disclosure;
fig. 3 is a functional schematic diagram of a joint debugging client according to an embodiment of the present disclosure;
fig. 4 is a schematic structural diagram of a joint debugging apparatus according to an embodiment of the present disclosure;
fig. 5 is a schematic structural diagram of an electronic device according to an embodiment of the present disclosure.
Detailed Description
In order that the above objects, features and advantages of the present disclosure may be more clearly understood, aspects of the present disclosure will be further described below. It should be noted that the embodiments and features of the embodiments of the present disclosure may be combined with each other without conflict.
In the following description, numerous specific details are set forth in order to provide a thorough understanding of the present disclosure, but the present disclosure may be practiced in other ways than those described herein; it is to be understood that the embodiments disclosed in the specification are only a few embodiments of the present disclosure, and not all embodiments.
In the prior art, in a scenario where multiple systems are dependent on each other, one system may generally request to implement in a Transmission Control Protocol (TCP) or hypertext Transfer Protocol (HTTP) manner in order to perform functional docking with another system. For example, after the a system developer develops the function, the B system is usually requested to perform joint debugging with the function developed by the B system developer, in order to correctly request to the B system, the relevant information requested in the configuration file, such as the IP address and the port number, usually needs to be modified, and the relevant information to the B system needs to be queried before each joint debugging, and then is used to update the configuration file; if the system A is a front-end Web page, the problem of cross-domain is still existed, the system B cannot be directly requested in an IP mode, and the system file needs to be additionally modified.
The existing joint debugging mode has the following defects: each time of local joint debugging, the related information of the other party needs to be inquired, and the local configuration file is modified, so that the process is complicated; the front-end project may have a cross-domain problem, and system files need to be additionally modified; when a front-end system and a back-end service are jointly dispatched, in order to solve the problem that a cross-domain front end needs to use the same domain name to access the back-end service, a port cannot be used under the normal condition, and at this time, the back-end service needs to forward a request of the port to a correct port in a proxy mode, for example, the back-end service is realized by using a Nginx service, which is very troublesome. In order to solve the above problem, an embodiment of the present disclosure provides a joint debugging method.
Fig. 1 is a schematic flow chart of a joint debugging method provided in an embodiment of the present disclosure, which may be executed by a joint debugging apparatus, where the apparatus may be implemented by software and/or hardware, and may be generally integrated in an electronic device. As shown in fig. 1, the method is applied to a first joint debugging client, and includes:
The joint debugging client is added in the embodiment of the disclosure and is used for realizing the joint debugging between different systems in the development process, the joint debugging client is simple to install and use, only one service needs to be started, and a corresponding server is not needed. The first joint debugging client and the joint debugging source system are configured in the same host.
The joint debugging source system and the joint debugging target system may be two systems which need to perform interactive testing (i.e. joint debugging) in the development process, or may also be two subsystems which need to perform joint debugging in one large system, the systems are a general name, and the specific type, function and number of the systems are not limited in the embodiment of the present disclosure, and for example, the systems may include a front-end application program, a background server, and the like. The joint debugging source system and the joint debugging target system are relative concepts, and a host where the joint debugging target system is located can be provided with a corresponding second joint debugging client so as to realize joint debugging with other systems.
Specifically, the first joint debugging client may receive a joint debugging request sent by a joint debugging source system of the local computer, where the joint debugging request includes a domain name of a joint debugging target system, and the number of the joint debugging target systems is not limited in this embodiment of the present disclosure, that is, the number of the systems performing joint debugging with the joint debugging source system may be multiple.
And 102, forwarding the joint debugging request to a joint debugging target system for joint debugging based on a pre-configured joint debugging forwarding rule and a domain name of the joint debugging target system.
The joint debugging forwarding rule is a forwarding rule based on a port forwarding technology, and different operating systems, such as Mac, Window, Linux and the like, support the port forwarding technology. Port forwarding (Port forwarding) is a method used by Secure Shell (SSH) network secure communications. The joint debugging client in the embodiment of the disclosure can pre-configure the joint debugging forwarding rule of the joint debugging target system to realize joint debugging.
In the embodiment of the present disclosure, before receiving the joint debugging request of the local joint debugging source system, the method further includes: receiving identification information and a domain name of a joint debugging target system sent by a joint debugging source system of a local machine; and starting the joint debugging target system based on the identification information of the joint debugging target system, and configuring joint debugging forwarding rules based on the domain name of the joint debugging target system. The identification information of the joint debugging target system may be a random code generated by a second joint debugging client corresponding to the joint debugging target system during installation, and is used for representing the joint debugging target system. The domain name of the joint debugging target system is one kind of request information, the request information of the joint debugging target system may include a domain name, a port number, an IP address, and the like, and the request information may be obtained by scanning the first joint debugging client in advance.
A development user of the joint debugging source system can acquire identification information of a joint debugging target system on line and determine a domain name of the joint debugging target system needing joint debugging according to actual conditions, and then the identification information and the domain name can be sent to a first joint debugging client of the joint debugging client by performing operations such as input or selection on a front-end page provided by the joint debugging client; the first joint debugging client can remotely start the joint debugging target system based on the identification information so as to enable the joint debugging target system to enter a joint debugging state, can search and determine a corresponding port number and an IP address in a configuration file based on the domain name of the joint debugging target system, can configure a joint debugging forwarding rule based on the port number and the IP address by adopting a port forwarding technology, and the joint debugging forwarding rule can be used for forwarding a request of a joint debugging source system for the domain name of the joint debugging target system to the joint debugging target system.
Specifically, the step of forwarding the joint debugging request to the joint debugging target system for joint debugging based on a pre-configured joint debugging forwarding rule and a domain name of the joint debugging target system comprises the following steps: inquiring in a configuration file based on the domain name of the joint debugging target system, and determining the IP address of the joint debugging target system; and forwarding the joint debugging request to a port where the port number of the joint debugging target system is located based on the IP address of the joint debugging target system and the joint debugging forwarding rule, and performing joint debugging. The configuration file may be a Hosts file, a system file without an extension, and may be used to store a mapping relationship between a domain name and an IP address.
The first joint debugging client stores the mapping relation between the domain name and the IP address of the joint debugging target system in the configuration file in advance, can determine the corresponding IP address based on the domain name of the joint debugging target system, and forwards the joint debugging request to the port corresponding to the port number of the joint debugging target system based on the IP address to carry out joint debugging.
According to the joint debugging scheme provided by the embodiment of the disclosure, a first joint debugging client receives a joint debugging request of a joint debugging source system of a local machine, wherein the joint debugging request comprises a domain name of a joint debugging target system, and the number of the joint debugging target systems is at least one; and forwarding the joint debugging request to a joint debugging target system for joint debugging based on a pre-configured joint debugging forwarding rule and the domain name of the joint debugging target system. By adopting the technical scheme, the joint debugging source system can simply and quickly forward the joint debugging request to the joint debugging target system through the joint debugging client side arranged by the local machine to realize joint debugging, and compared with the prior art, the acquisition of related information and the modification of system files during joint debugging at each time can be avoided, so that the workload is saved, and the joint debugging efficiency between the systems is improved.
In some embodiments, before receiving the joint debugging request of the local joint debugging source system, the method may further include: scanning the local area network to which the local area network belongs according to a set time interval, and determining second joint debugging clients on an external host, wherein the number of the second joint debugging clients is at least one; and acquiring request information of the joint debugging target system issued by a second joint debugging client, and storing the request information of the joint debugging target system in a configuration file, wherein the second joint debugging client and the joint debugging target system are configured in the same host. The set time interval may be set according to actual conditions, and for example, the set time interval may be 10 s. The external host refers to other hosts except the host where the joint debugging source system is located, the second joint debugging client is a joint debugging client installed on the external host, and one external host can be configured with the second joint debugging client and a joint debugging target system.
In the embodiment of the disclosure, when two systems operate in one local area network, joint debugging can be realized. After the first joint debugging client is started, the local area network to which the first joint debugging client belongs can be scanned according to a set time interval so as to determine second joint debugging clients on a plurality of external hosts, and request information of a plurality of joint debugging target systems issued by the second joint debugging clients is obtained and then stored in a configuration file. The joint debugging target system is a system which runs in a local area network with the joint debugging source system and can perform joint debugging with the joint debugging source system, and the number of the joint debugging target systems may change along with time, so that the joint debugging target system needs to be updated by scanning regularly.
In some embodiments, scanning the local area network to which the local area network belongs at a set time interval, and determining the second connection client on the external host includes: and carrying out starting detection and function detection on the joint debugging fixed port on an external host in the local area network, and determining a second joint debugging client side which passes the detection. The joint debugging fixed port is a fixed port started after the joint debugging client is started, joint debugging fixed ports in the joint debugging clients installed on the host where each system is located are the same, namely the joint debugging fixed ports in the first joint debugging client and the second joint debugging client are the same, and the joint debugging fixed port can be set according to actual conditions, for example, the joint debugging fixed port is 9240.
The scanning mode of the first joint debugging client terminal scanning the local area network is realized by scanning the IP network segment of the whole local area network, when a host corresponding to an available IP address is scanned, the joint debugging fixed port of each IP address of the network segment is tried to be connected, whether the joint debugging fixed port is started or not can be detected through a Telnet command, if the connection is available, the host is indicated to start the joint debugging fixed port, and the second joint debugging client terminal can be installed; and then, function detection can be carried out, specifically, a detection (Check) interface exposed by the client corresponding to the joint debugging fixed port can be requested in an http mode, if the return result of the detection interface is successful in verification, the host is indicated to be provided with a second joint debugging client, wherein the detection (Check) interface is an interface for returning a health state. The verification method may be to determine whether a code of the returned value is equal to success (success), and if so, the verification is successful; otherwise, the verification fails. The available IP address is that the IP address can be ping-through, if the IP address does not have a corresponding host, then ping will fail, and if the IP address can be ping-through, it indicates that the IP address has a corresponding alive host.
After the first joint debugging client determines the second joint debugging client which passes the detection, All request information of the joint debugging target system issued by the second joint debugging client can be acquired through the specified interface exposed by the first joint debugging client, wherein the specified interface can be a 'get All Service' interface.
In the above embodiment, the first joint debugging client corresponding to the joint debugging source system may determine other second joint debugging clients in the local area network to which the first joint debugging client belongs in advance through timing scanning, and further obtain and store the request information of the multiple joint debugging target systems issued by the second joint debugging client, so that the required information may be provided for the subsequent joint debugging source system as an active party for joint debugging of any one joint debugging target system, and the related information does not need to be obtained every time of joint debugging, thereby saving workload.
In some embodiments, before receiving the joint debugging request of the local joint debugging source system, the method may further include: and pushing the request information of at least one joint debugging source system of the local machine to a second joint debugging client on an external host in the local area network to which the local machine belongs. The local machine can run at least one joint debugging source system, and the request information of each joint debugging source system can be issued to the local area network through a first joint debugging client on the local machine, so that a second joint debugging client on an external host can store the request information.
The request information of the joint debugging source system and the joint debugging target system can comprise related information such as name, IP address, domain name and port number.
The first joint debugging client can issue request information of a plurality of joint debugging source systems operated by the first joint debugging client to other second joint debugging clients, so that joint debugging target systems corresponding to the second joint debugging clients can be used as an active party to realize joint debugging with the joint debugging source systems.
In the embodiment of the disclosure, the joint debugging client is installed in the host where each system is located, and the joint debugging client can actively release the information of the system in the host and also can acquire the information of the systems in other external hosts, so that mutual confirmation of the two systems before joint debugging is not needed every time, the workload is greatly saved, and the joint debugging efficiency is improved.
Fig. 2 is a schematic flow chart of another joint debugging method provided in the embodiment of the present disclosure, and the embodiment further specifically describes the joint debugging method based on the above embodiment. As shown in fig. 2, the method is applied to a first joint debugging client, and includes:
The joint debugging request comprises the domain name of a joint debugging target system, and the number of the joint debugging target systems is at least one.
And step 204, inquiring in a configuration file based on the domain name of the joint debugging target system, and determining the IP address of the joint debugging target system.
And step 205, forwarding the joint debugging request to a port where the port number of the joint debugging target system is located based on the IP address of the joint debugging target system and the joint debugging forwarding rule, and performing joint debugging.
For example, when the joint debugging source system a needs to be jointly debugged with the joint debugging target system B, a development user of the joint debugging source system a may obtain a random code of a second joint debugging client in the joint debugging target system B on line, the joint debugging source system a may enable the joint debugging target system B through the first joint debugging client, and a domain name "aaa.bb.com" of the joint debugging target system B needs to be provided when the joint debugging source system a is enabled.
After receiving the domain name "aaa.bb.com" of the joint debugging target system B sent by the joint debugging source system a, the first joint debugging client may obtain the IP address "10.1.1.10" corresponding to the domain name from the configuration file according to the domain name, and then configure a joint debugging forwarding rule on the host of the joint debugging source system a, where the joint debugging forwarding rule has an effect of: all requests with the IP address "10.1.1.10" sent by the joint debugging source system a are forwarded to the 8080 port of the host of the joint debugging target system B, and the 8080 port is the port of the joint debugging target system B. Optionally, the first joint debugging client does not obtain the corresponding IP address from the configuration file according to the domain name, and then the IP address "10.1.1.10" corresponding to the domain name "aaa.bb.com" may be added to the configuration file, and the mapping relationship is configured.
When the joint debugging source system a sends out a request for the domain name "aaa.bb.com", since the first joint debugging client has stored and established a mapping relationship between the domain name "aaa.bb.com" and the IP address "10.1.1.10", the host of the joint debugging source system a can forcibly forward all the requests for the domain name "aaa.bb.com" to the host of the joint debugging target system B, thus realizing joint debugging.
In some embodiments, before receiving the joint debugging request of the local joint debugging source system, the method may further include: scanning a local area network to which the local area network belongs according to a set time interval, and determining second joint debugging clients on an external host, wherein the number of the second joint debugging clients is at least one; and acquiring request information of a joint debugging target system issued by the second joint debugging client, and storing the request information of the joint debugging target system in a configuration file, wherein the second joint debugging client and the joint debugging target system are configured in the same host. Wherein, the scanning the local area network to which the local area network belongs according to the set time interval and determining the second connection client on the external host may include: and carrying out starting detection and function detection on the joint debugging fixed port on the external host in the local area network, and determining a second joint debugging client end which passes the detection. In some embodiments, before receiving the joint debugging request of the local joint debugging source system, the method may further include: and pushing the request information of at least one joint debugging source system of the local machine to a second joint client on an external host in the local area network.
For example, the first joint debugging client may scan the entire lan segment at regular time to discover other second joint debugging clients and obtain request information of the joint debugging target system issued by the discovered second joint debugging clients, where the scanning is implemented by scanning the IP segment of the entire lan.
And assuming that the host IP address of the first joint debugging client is "192.168.0.10", the local computer currently runs a joint debugging source system, the port of which is 8080, and assuming that the actual domain name of this joint debugging source system in the test environment is "aaa.bb.com", the domain name of the joint debugging source system is also registered here as "aaa.bb.com", the first joint debugging client may obtain the above request information of the local joint debugging source system based on manual input, and the request information may include a name, a port, a domain name and an IP address. The first syndication client may store the request information of the syndication source system in a configuration file while notifying the other second syndication clients. The way other second connected clients are notified is pushed by scanning the hosts of all network segments once.
In the embodiment of the disclosure, the joint debugging client may operate in a page-providing manner, and is mainly used by the development user to publish own system-related information, enable systems of other development users to perform joint debugging and acquire system-related information of other development users, and all operations of the development users may be stored in the configuration file. The configuration file may store all configuration information in json, for example, the target structure of the configuration file may be:
the timing task is used for scanning the systems on all IP network segments at fixed time, updating an available system list in time, and storing a scanning result in a configuration file with a scanning interval of 10 s. Scanning and checking all the enabled remote systems, checking the state of the remote systems, and automatically deleting the remote systems if the offline time exceeds a set time, wherein the set time can be 10 minutes.
Illustratively, fig. 3 is a schematic functional diagram of a joint debugging client according to an embodiment of the present disclosure, where the joint debugging client may provide a Web configuration page to a development user to implement its function. Referring to fig. 3, the joint debugging client may have three functions: releasing local system information; starting other systems, and configuring joint debugging forwarding rules by adopting a port forwarding technology; the local area network to which the local area network belongs is scanned regularly to obtain other system information, and the local system information and the other system information can be stored in a configuration file for use in configuring the joint debugging forwarding rule and executing the joint debugging forwarding.
Optionally, the joint debugging client may add a step of verifying the enabled joint debugging forwarding rule when starting and closing, and modify the joint debugging forwarding rule table. The joint transferring rule is set when the system of other developers is remotely started, and if the joint transferring client is accidentally closed due to an abnormal condition, the transferring or routing may be abnormal, so that the system of the developers is always accessed, and the access is abnormal. In order to avoid such a situation, when the joint debugging client is started and closed, whether the currently started joint debugging forwarding rule can be matched with the rule configured in the joint debugging forwarding rule table is checked, if not, correction is needed, and the correction method comprises the following steps: on one hand, redundant joint key forwarding rules need to be deleted, and on the other hand, the missing joint key forwarding rules need to be added.
The joint debugging scheme provided by the embodiment of the disclosure mainly aims to solve the problem that complicated operations such as frequent modification of configuration files, service restarting and the like are required when local joint debugging is developed by multiple systems, provides a method for switching environments by one key without restarting the service, and facilitates developers to realize function joint debugging more conveniently. The method can solve the problem of local joint debugging of the application and can also be used for environment switching during development. The disclosed embodiments have the following advantages: 1. the joint debugging client can automatically agent the port, IP address and domain name of the system and can directly access by using the domain name or the IP address, developers do not need to start other services, the joint debugging client is particularly suitable for the scene of joint debugging of a front-end application program and a rear-end server, the developers do not need to modify the joint debugging port, IP address and domain name, and the request can be automatically proxied and forwarded. 2. The joint debugging client can switch the system of mapping the domain name to any developer at any time, and the two parties do not need to restart the service. 3. The installation and use of the joint debugging client are simple, and only one service needs to be started. 4. The joint debugging client has the capability of automatically discovering other joint debugging clients in the local area network, and is convenient to use.
According to the joint debugging scheme provided by the embodiment of the invention, a first joint debugging client receives identification information and a domain name of a joint debugging target system sent by a joint debugging source system of a local machine, starts the joint debugging target system based on the identification information of the joint debugging target system, configures a joint debugging forwarding rule based on the domain name of the joint debugging target system, receives a joint debugging request of the joint debugging source system of the local machine, inquires in a configuration file based on the domain name of the joint debugging target system, determines an IP address of the joint debugging target system, forwards the joint debugging request to a port where a port number of the joint debugging target system is located based on the IP address of the joint debugging target system and the joint debugging forwarding rule, and conducts joint debugging. By adopting the technical scheme, the joint debugging source system can simply and quickly forward the joint debugging request to the joint debugging target system through the first joint debugging client arranged by the local computer to realize joint debugging.
Fig. 4 is a schematic structural diagram of a joint debugging apparatus provided in an embodiment of the present disclosure, where the apparatus may be implemented by software and/or hardware, and may be generally integrated in an electronic device, and may perform joint debugging between multiple systems by executing a joint debugging method. As shown in fig. 4, the apparatus is configured at the first joint debugging client, and includes:
a joint debugging request receiving module 301, configured to receive a joint debugging request of a joint debugging source system of a local computer, where the joint debugging request includes a domain name of a joint debugging target system, and the number of the joint debugging target systems is at least one;
and the joint debugging module 302 is configured to forward the joint debugging request to the joint debugging target system for joint debugging based on a pre-configured joint debugging forwarding rule and the domain name of the joint debugging target system.
According to the joint debugging scheme provided by the embodiment of the disclosure, a first joint debugging client receives a joint debugging request of a joint debugging source system of a local machine, wherein the joint debugging request comprises a domain name of a joint debugging target system, and the number of the joint debugging target systems is at least one; and forwarding the joint debugging request to a joint debugging target system for joint debugging based on a pre-configured joint debugging forwarding rule and the domain name of the joint debugging target system. By adopting the technical scheme, the joint debugging source system can simply and quickly forward the joint debugging request to the joint debugging target system through the first joint debugging client arranged by the local machine to realize joint debugging, and compared with the prior art, the acquisition of related information and the modification of system files during joint debugging at each time can be avoided, so that the workload is saved, and the joint debugging efficiency between the systems is improved.
Optionally, the apparatus further includes a rule configuration module, configured to: before receiving a joint debugging request of a local joint debugging source system,
receiving identification information and a domain name of a joint debugging target system sent by a joint debugging source system of a local machine;
and starting the joint debugging target system based on the identification information of the joint debugging target system, and configuring the joint debugging forwarding rule based on the domain name of the joint debugging target system.
Optionally, the joint debugging module 301 is specifically configured to:
inquiring in a configuration file based on the domain name of the joint debugging target system, and determining the IP address of the joint debugging target system;
and forwarding the joint debugging request to a port where the port number of the joint debugging target system is located based on the IP address of the joint debugging target system and the joint debugging forwarding rule, and performing joint debugging.
Optionally, the apparatus further includes a joint debugging target system information obtaining module, specifically configured to: before receiving a joint debugging request of a local joint debugging source system,
scanning a local area network to which the local area network belongs according to a set time interval, and determining second joint debugging clients on an external host, wherein the number of the second joint debugging clients is at least one;
and acquiring request information of a joint debugging target system issued by the second joint debugging client, and storing the request information of the joint debugging target system in a configuration file, wherein the second joint debugging client and the joint debugging target system are configured in the same host.
Optionally, the joint debugging target system information obtaining module is specifically configured to:
and carrying out the starting detection and the function detection of the joint debugging fixed port on the external host in the local area network, and determining a second joint debugging client side which passes the detection.
Optionally, the apparatus further includes a joint debugging source system information publishing module, specifically configured to: before receiving a joint debugging request of a local joint debugging source system,
and pushing the request information of at least one joint debugging source system of the local machine to a second joint debugging client on an external host in the local area network to which the local machine belongs.
Optionally, the request information includes a name, an IP address, a domain name, and a port number.
The joint debugging device provided by the embodiment of the disclosure can execute the joint debugging method provided by any embodiment of the disclosure, and has corresponding functional modules and beneficial effects of the execution method.
Fig. 5 is a schematic structural diagram of an electronic device according to an embodiment of the present disclosure. As shown in fig. 5, the electronic device 400 includes one or more processors 401 and memory 402.
The processor 401 may be a Central Processing Unit (CPU) or other form of processing unit having data processing capabilities and/or instruction execution capabilities, and may control other components in the electronic device 400 to perform desired functions.
In one example, the electronic device 400 may further include: an input device 403 and an output device 404, which are interconnected by a bus system and/or other form of connection mechanism (not shown).
The input device 403 may also include, for example, a keyboard, a mouse, and the like.
The output device 404 may output various information to the outside, including the determined distance information, direction information, and the like. The output devices 404 may include, for example, a display, speakers, a printer, and a communication network and its connected remote output devices, among others.
Of course, for simplicity, only some of the components of the electronic device 400 relevant to the present disclosure are shown in fig. 5, omitting components such as buses, input/output interfaces, and the like. In addition, electronic device 400 may include any other suitable components depending on the particular application.
In addition to the above methods and apparatus, embodiments of the present disclosure may also be a computer program product comprising computer program instructions that, when executed by a processor, cause the processor to perform the joint debugging method provided by embodiments of the present disclosure.
The computer program product may write program code for carrying out operations for embodiments of the present disclosure in any combination of one or more programming languages, including an object oriented programming language such as Java, C + + or the like and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user's computing device, partly on the user's device, as a stand-alone software package, partly on the user's computing device and partly on a remote computing device, or entirely on the remote computing device or server.
Furthermore, embodiments of the present disclosure may also be a computer-readable storage medium having stored thereon computer program instructions that, when executed by a processor, cause the processor to perform the joint debugging method provided by the embodiments of the present disclosure.
The computer-readable storage medium may take any combination of one or more readable media. The readable medium may be a readable signal medium or a readable storage medium. A readable storage medium may include, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or a combination of any of the foregoing. More specific examples (a non-exhaustive list) of the readable storage medium include: an electrical connection having one or more wires, a portable disk, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.
It is noted that, in this document, relational terms such as "first" and "second," and the like, may be used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Also, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other identical elements in a process, method, article, or apparatus that comprises the element.
The foregoing are merely exemplary embodiments of the present disclosure, which enable those skilled in the art to understand or practice the present disclosure. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other embodiments without departing from the spirit or scope of the disclosure. Thus, the present disclosure is not intended to be limited to the embodiments shown herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.
Claims (9)
1. A joint debugging method is applied to a first joint debugging client and comprises the following steps:
receiving a joint debugging request of a joint debugging source system of a local machine, wherein the joint debugging request comprises a domain name of a joint debugging target system, the number of the joint debugging target systems is at least one, and the first joint debugging client and the joint debugging source system are configured in the same host machine;
based on a pre-configured joint debugging forwarding rule and the domain name of the joint debugging target system, forwarding the joint debugging request to the joint debugging target system for joint debugging;
the step of forwarding the joint debugging request to the joint debugging target system for joint debugging based on a pre-configured joint debugging forwarding rule and the domain name of the joint debugging target system comprises the following steps:
inquiring in a configuration file based on the domain name of the joint debugging target system, and determining the IP address of the joint debugging target system;
forwarding the joint debugging request to a port where a port number of the joint debugging target system is located based on the IP address of the joint debugging target system and the joint debugging forwarding rule, and performing joint debugging;
the joint debugging forwarding rule is configured by adopting a port forwarding technology based on the port number and the IP address of the joint debugging target system, and the joint debugging forwarding rule is used for forwarding all requests of the joint debugging source system to the IP address of the joint debugging target system to the port corresponding to the port number of the joint debugging target system.
2. The method of claim 1, wherein prior to receiving the joint request from the native joint debugging source system, further comprising:
receiving identification information and a domain name of a joint debugging target system sent by a joint debugging source system of a local machine;
and starting the joint debugging target system based on the identification information of the joint debugging target system, and configuring the joint debugging forwarding rule based on the domain name of the joint debugging target system.
3. The method of claim 1, wherein prior to receiving the joint request from the native joint debugging source system, further comprising:
scanning a local area network to which the local area network belongs according to a set time interval, and determining second joint debugging clients on an external host, wherein the number of the second joint debugging clients is at least one;
and acquiring request information of a joint debugging target system issued by the second joint debugging client, and storing the request information of the joint debugging target system in a configuration file, wherein the second joint debugging client and the joint debugging target system are configured in the same host.
4. The method of claim 3, wherein the scanning the local area network to determine the second connection client on the external host at the set time interval comprises:
and carrying out starting detection and function detection on the joint debugging fixed port on the external host in the local area network, and determining a second joint debugging client end which passes the detection.
5. The method of claim 1, wherein prior to receiving the joint request from the native joint debugging source system, further comprising:
and pushing the request information of at least one joint debugging source system of the local machine to a second joint debugging client on an external host in the local area network to which the local machine belongs.
6. The method according to claim 3 or 5, wherein the request information comprises a name, an IP address, a domain name and a port number.
7. A joint debugging device configured at a first joint debugging client, comprising:
the joint debugging request receiving module is used for receiving a joint debugging request of a joint debugging source system of the local machine, wherein the joint debugging request comprises a domain name of a joint debugging target system, the number of the joint debugging target systems is at least one, and the first joint debugging client and the joint debugging source system are configured in the same host;
the joint debugging module is used for forwarding the joint debugging request to the joint debugging target system for joint debugging based on a pre-configured joint debugging forwarding rule and the domain name of the joint debugging target system;
the joint debugging module is specifically used for:
inquiring in a configuration file based on the domain name of the joint debugging target system, and determining the IP address of the joint debugging target system;
forwarding the joint debugging request to a port where a port number of the joint debugging target system is located based on the IP address of the joint debugging target system and the joint debugging forwarding rule, and performing joint debugging;
the joint debugging forwarding rule is configured by adopting a port forwarding technology based on the port number and the IP address of the joint debugging target system, and the joint debugging forwarding rule is used for forwarding all requests of the joint debugging source system to the IP address of the joint debugging target system to the port corresponding to the port number of the joint debugging target system.
8. An electronic device, characterized in that the electronic device comprises:
a processor;
a memory for storing the processor-executable instructions;
the processor is used for reading the executable instructions from the memory and executing the instructions to realize the joint debugging method of any one of the claims 1-6.
9. A computer-readable storage medium, characterized in that the storage medium stores a computer program for executing the joint debugging method according to any of the preceding claims 1-6.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010981186.9A CN112202854B (en) | 2020-09-17 | 2020-09-17 | Joint debugging method, device, equipment and medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010981186.9A CN112202854B (en) | 2020-09-17 | 2020-09-17 | Joint debugging method, device, equipment and medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112202854A CN112202854A (en) | 2021-01-08 |
| CN112202854B true CN112202854B (en) | 2022-08-02 |
Family
ID=74015420
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010981186.9A Active CN112202854B (en) | 2020-09-17 | 2020-09-17 | Joint debugging method, device, equipment and medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112202854B (en) |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108390944A (en) * | 2018-03-28 | 2018-08-10 | 北京小米移动软件有限公司 | Information interacting method and device |
| CN109639788A (en) * | 2018-12-05 | 2019-04-16 | 苏州思必驰信息科技有限公司 | Cross-domain name joint debugging method and system for voice dialogue platform |
| CN109714446A (en) * | 2018-12-20 | 2019-05-03 | 全链通有限公司 | Domain name analytic method, equipment, system and storage medium |
| CN110427324A (en) * | 2019-07-30 | 2019-11-08 | 中国工商银行股份有限公司 | Joint debugging system, joint debugging method, computer equipment and storage medium |
| CN110430288A (en) * | 2019-09-16 | 2019-11-08 | 腾讯科技（深圳）有限公司 | Node visit method, apparatus, computer equipment and storage medium |
| CN110519395A (en) * | 2019-09-16 | 2019-11-29 | 北京思维造物信息科技股份有限公司 | Service request processing method, device, computer equipment and storage medium |
| CN110602182A (en) * | 2019-08-27 | 2019-12-20 | 深圳前海达闼云端智能科技有限公司 | Service scheduling method, device and system, global load balancer and client |
Family Cites Families (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20150052258A1 (en) * | 2014-09-29 | 2015-02-19 | Weaved, Inc. | Direct map proxy system and protocol |
| US7930429B2 (en) * | 2008-12-18 | 2011-04-19 | At&T Intellectual Property I, Lp | System and method for obtaining content from a content delivery network |
| GB2494027B (en) * | 2011-08-25 | 2014-05-21 | Ibm | A computer-implemented method enabling a web application to call at least one native function of a mobile device |
| CN106899621B (en) * | 2015-12-17 | 2019-06-14 | 中国联合网络通信集团有限公司 | A kind of scheduling system and method |
| CN111641728A (en) * | 2020-05-16 | 2020-09-08 | 中信银行股份有限公司 | Calling method and device based on distributed system |
-
2020
- 2020-09-17 CN CN202010981186.9A patent/CN112202854B/en active Active
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108390944A (en) * | 2018-03-28 | 2018-08-10 | 北京小米移动软件有限公司 | Information interacting method and device |
| CN109639788A (en) * | 2018-12-05 | 2019-04-16 | 苏州思必驰信息科技有限公司 | Cross-domain name joint debugging method and system for voice dialogue platform |
| CN109714446A (en) * | 2018-12-20 | 2019-05-03 | 全链通有限公司 | Domain name analytic method, equipment, system and storage medium |
| CN110427324A (en) * | 2019-07-30 | 2019-11-08 | 中国工商银行股份有限公司 | Joint debugging system, joint debugging method, computer equipment and storage medium |
| CN110602182A (en) * | 2019-08-27 | 2019-12-20 | 深圳前海达闼云端智能科技有限公司 | Service scheduling method, device and system, global load balancer and client |
| CN110430288A (en) * | 2019-09-16 | 2019-11-08 | 腾讯科技（深圳）有限公司 | Node visit method, apparatus, computer equipment and storage medium |
| CN110519395A (en) * | 2019-09-16 | 2019-11-29 | 北京思维造物信息科技股份有限公司 | Service request processing method, device, computer equipment and storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112202854A (en) | 2021-01-08 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN112637346B (en) | Proxy method, proxy device, proxy server and storage medium | |
| US9883002B2 (en) | Method and system for accessing website | |
| US9146731B2 (en) | Information processing apparatus, relay server, information relay method, non-transitory computer-readable medium storing information relay program, and communication system | |
| WO2017097123A1 (en) | Access request conversion method and device | |
| US11201792B2 (en) | Management system and control method | |
| US8024430B2 (en) | System and method for installing software | |
| US20090007152A1 (en) | Management of external hardware appliances in a distributed operating system | |
| CN111510330B (en) | Interface management device, method and storage medium | |
| US10324766B1 (en) | Task profile collection | |
| CN114489622A (en) | Js application, electronic device, and storage medium | |
| CN114374669A (en) | VPN client proxy DNS analysis method and system | |
| CN112671574B (en) | Front-end and back-end joint debugging method and device, proxy equipment and storage medium | |
| US20210390064A1 (en) | Tracking movements of enrolled peripheral devices | |
| CN113268254A (en) | Cluster system installation method and device, electronic equipment and storage medium | |
| CN112202854B (en) | Joint debugging method, device, equipment and medium | |
| CN112491940B (en) | Request forwarding method and device of proxy server, storage medium and electronic equipment | |
| WO2018081963A1 (en) | Method and device for dns resolution and network system | |
| CN109375946B (en) | Method and system for managing component package of node package manager | |
| CN114301872B (en) | Domain name based access method and device, electronic equipment and storage medium | |
| CN115150464B (en) | Application proxy method, device, equipment and medium | |
| CN111367921A (en) | Data object refreshing method and device | |
| JP2001202316A (en) | Device, system and method for processing information and storage medium | |
| JP5464449B2 (en) | Method for detecting inconsistency between processing units considering reboot due to failure, shared apparatus, and cluster system | |
| CN113271326A (en) | Network protocol address scheduling method and device and electronic equipment | |
| US10523630B2 (en) | Information processing apparatus, storage medium, and control method |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |