CN110147397B - System docking method, device, management system, terminal equipment and storage medium - Google Patents
System docking method, device, management system, terminal equipment and storage medium Download PDFInfo
- Publication number
- CN110147397B CN110147397B CN201910283811.XA CN201910283811A CN110147397B CN 110147397 B CN110147397 B CN 110147397B CN 201910283811 A CN201910283811 A CN 201910283811A CN 110147397 B CN110147397 B CN 110147397B
- Authority
- CN
- China
- Prior art keywords
- service
- source system
- service data
- data
- acquisition mode
- 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
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/25—Integrating or interfacing systems involving database management systems
Abstract
The embodiment of the application is applicable to the technical field of computers, and discloses a system docking method, a device, a management system, terminal equipment and a computer readable storage medium, wherein the method comprises the following steps: the third party system acquires service data from the source system through a non-service interface mode; the third party system analyzes the service data and determines a service flow; and the third party system executes corresponding business operation on the target system through a non-business interface mode according to the business flow and the business data. According to the embodiment of the application, the third party system is introduced, the third party system obtains service data from the source system in a non-service interface mode, analyzes the service data to determine a service flow, executes corresponding service operation on the target system in the non-service interface mode based on the service data and the service flow, does not need to develop a system or open an interface, does not need to modify or develop a program to realize system butt joint between the source system and the target system, reduces the butt joint difficulty, and improves the butt joint efficiency and the system stability.
Description
Technical Field
The application belongs to the technical field of computers, and particularly relates to a system docking method, a system docking device, a management system, terminal equipment and a computer readable storage medium.
Background
Currently, there is a data transmission requirement or a service operation requirement between two systems in one unit or between two systems in different units, and the systems need to perform system docking when data is transmitted or service operation is performed between the systems.
The traditional system docking mode is that two sides of the system agree on an interface mode and an interface method, and the two sides or one side of the system reserves or opens an interface to realize the system docking through developing a program or modifying the program. Common interfacing means include, for example, web Service, http API, DLL, etc. The Web Service docking mode specifically comprises the following steps: the target system develops a section of Web Service program and declares the interface definition to the source system; the source system increases the interface call to the destination system, both systems follow the Web Service standard. The http API docking mode specifically comprises the following steps: the destination system develops an http program as part of the system and declares the interface definition to the source system. The source system increases the call to the interface and both systems use http.
Obviously, the system interfacing mode in the existing stage needs to develop a system interface, and needs to modify programs on two sides or one side of the system, so that support for the interface is increased or call for the interface is increased. Development or modification of the docking program, definition and development of the interface, and the like are generally difficult, and the time is long. In addition, the interface or the interface calling program opened by the system can bring unstable hidden trouble to the system. In summary, the existing system docking mode has the problems of high docking difficulty, low docking efficiency and low system stability.
Disclosure of Invention
In view of this, the embodiments of the present application provide a system docking method, device, management system, terminal device, and computer readable storage medium, so as to solve the problems of greater docking difficulty, lower docking efficiency, and lower system stability in the existing system docking manner.
A first aspect of an embodiment of the present application provides a system docking management system, including a source system, a third party system communicatively connected to the source system, and a destination system communicatively connected to the third party system;
the third party system is used for acquiring service data from the source system in a non-service interface mode; analyzing the service data to determine a service flow; according to the service flow and the service data, corresponding service operation is executed on the target system in a non-service interface mode;
the source system is a party initiating service operation in the system docking, and the destination system is a party receiving service operation in the system docking.
A second aspect of the embodiments of the present application provides a system docking method, which is applied to the third party system in the system docking management system described in the first aspect, and includes:
acquiring service data from a source system through a non-service interface mode;
analyzing the service data to determine a service flow;
and executing corresponding business operation on the target system in a non-business interface mode according to the business flow and the business data.
With reference to the second aspect, in a possible implementation manner, the acquiring service data from the source system through a non-service interface manner includes:
determining a corresponding target acquisition mode from preset acquisition modes according to the type of the source system;
and acquiring the service data from the source system in the target acquisition mode.
With reference to the second aspect, in a possible implementation manner, the determining, according to a type of the source system, a corresponding target acquisition manner from preset acquisition manners includes:
when the source system is a browser-based system, the corresponding target acquisition mode is a first target acquisition mode;
when the source system is a system running based on a database, the corresponding target acquisition mode is a second target acquisition mode;
when the source system is a Windows program, the corresponding target acquisition mode is a second target acquisition mode;
the preset acquisition modes comprise a first target acquisition mode, a second target acquisition mode and a third target acquisition mode.
With reference to the second aspect, in a possible implementation manner, the acquiring, by the target acquiring manner, the service data from the source system includes:
operating a browser of the source system to open a corresponding page of the source system based on the Selenium software;
acquiring an operation object in a browser of the source system through xPath;
extracting the service data according to the operation object; or alternatively
The service data are obtained by running SQL sentences without editing rights in a database of the source system; or alternatively
Operating the source system to switch to the front end of the window through Windows API;
and activating an editing window through the Windows operation message, and acquiring the service data.
With reference to the second aspect, in a possible implementation manner, when the destination system is a browser-based system, the executing, according to the service flow and the service data, a corresponding service operation on the destination system through a non-service interface manner includes:
operating a browser of the target system to open a business operation page based on the Selenium software;
acquiring an operation object in a browser of the source system through xPath;
and operating the operation object in the browser of the source system according to the service data and the service flow.
A third aspect of the embodiments of the present application provides a system docking device, which is integrated in the system docking management system described in the first aspect, and includes:
the service data acquisition module is used for acquiring service data from the source system in a non-service interface mode;
the flow determining module is used for analyzing the service data and determining a service flow;
and the operation module is used for executing corresponding service operation on the target system in a non-service interface mode according to the service flow and the service data.
With reference to the third aspect, in a possible implementation manner, the service data acquisition module includes:
the acquisition mode determining unit is used for determining a corresponding target acquisition mode from preset acquisition modes according to the type of the source system;
and the acquisition unit is used for acquiring the service data from the source system in the target acquisition mode.
A fourth aspect of the embodiments of the present application provides a terminal device comprising a memory, a processor and a computer program stored in the memory and executable on the processor, the processor implementing the steps of the method according to any one of the second aspects above when the computer program is executed.
A fifth aspect of embodiments of the present application is a computer-readable storage medium storing a computer program which, when executed by a processor, implements the steps of the method according to any of the second aspects.
Compared with the prior art, the embodiment of the application has the beneficial effects that:
according to the embodiment of the application, the third party system is introduced, the third party system obtains service data from the source system in a non-service interface mode, analyzes the service data to determine a service flow, executes corresponding service operation on the target system in the non-service interface mode based on the service data and the service flow, does not need to develop a system or open an interface, does not need to modify or develop a program to realize system butt joint between the source system and the target system, reduces the butt joint difficulty, and improves the butt joint efficiency and the system stability.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings that are required for the embodiments or the description of the prior art will be briefly described below, it being obvious that the drawings in the following description are only some embodiments of the present application, and that other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.
Fig. 1 is a schematic block diagram of a system docking management system according to an embodiment of the present application;
FIG. 2 is a schematic block diagram of a system docking method according to an embodiment of the present disclosure;
fig. 3 is a schematic flow block diagram of a service data acquisition process provided in an embodiment of the present application;
FIG. 4 is a schematic block diagram of a third party system operation destination system according to an embodiment of the present application;
FIG. 5 is a schematic block diagram of a system docking device according to an embodiment of the present disclosure;
fig. 6 is a schematic diagram of a terminal device provided in an embodiment of the present application.
Detailed Description
In the following description, for purposes of explanation and not limitation, specific details are set forth, such as particular system configurations, techniques, etc. in order to provide a thorough understanding of the embodiments of the present application. It will be apparent, however, to one skilled in the art that the present application may be practiced in other embodiments that depart from these specific details. In other instances, detailed descriptions of well-known systems, devices, circuits, and methods are omitted so as not to obscure the description of the present application with unnecessary detail.
In order to illustrate the technical solutions described in the present application, the following description is made by specific examples.
Example 1
Referring to fig. 1, a schematic block diagram of a system docking management system according to an embodiment of the present application may include a source system 11, a third party system 12 communicatively connected to the source system, and a destination system 13 communicatively connected to the third party system.
The source system refers to a party initiating service operation in the system docking, and the destination system refers to a party receiving service operation in the system docking. I.e. the source system and the destination system are names used to characterize both systems in the system docking. The type of source and destination systems may be arbitrary.
The third party system can be used for acquiring service data from the source system through a non-service interface mode; analyzing service data and determining a service flow; and executing corresponding service operation on the target system in a non-service interface mode according to the service flow and the service data. The third party system is established, the third party system obtains service data from the source system in a mode of not depending on the service interface, and the process customization is carried out according to the service data, so that the target system is operated, and the system butt joint is realized.
In a specific application, the third party system may be a system independent of the source system and the destination system, or may be a subsystem subordinate to the source system or the destination system, i.e. the third party system and the source system may be packaged into the same system, or the third party system and the destination system may be packaged into the same system.
Therefore, by introducing the third system, system development or an open interface is not needed, and system docking is realized without modifying or developing a program, so that docking difficulty is reduced, and docking efficiency and system stability are improved.
Example two
Referring to fig. 2, a schematic flow chart diagram of a system docking method according to an embodiment of the present application is provided, and the method may be specifically applied to a third party system in the system docking management system in the first embodiment, and the method may include the following steps:
step S201, service data is acquired from a source system through a non-service interface mode.
The service data may refer to data that needs to be transmitted from the source system to the destination system, or may refer to corresponding data that is required by the source system to operate the destination system. In other words, data transfer refers to, but is not limited to, data transfer traffic or operation traffic between the source system and the destination system: the destination system receives the data in the source system, and the operation service refers to the operation of the source system, the flow, the clicking of a button or a link, the entry of a text in an input box and the like in a software interface of the destination system. According to different services, the third party system can acquire corresponding service data from the source system.
The non-service interface mode is a data acquisition mode, and the data acquisition mode enables the third system not to pass through a service interface between the systems, can acquire service data from the source system, and can operate the target system according to the service data. The data interaction between the third party system and the source system and the destination system can realize the system butt joint without a service interface, namely, the third party system is established and the service interface is not relied on.
The types of the source systems are different, and the non-business interface modes are correspondingly different, namely the data acquisition modes are correspondingly different. The third party system is preset with a data acquisition mode, which can automatically adapt to a corresponding data acquisition mode according to different source systems, and then acquire service data from the source systems according to the adapted data acquisition mode.
In some embodiments, referring to fig. 3, which is a schematic flow diagram of a service data acquisition process provided in an embodiment of the present application, the specific process of acquiring service data from a source system through a non-service interface manner may include:
step 301, determining a corresponding target acquisition mode from preset acquisition modes according to the type of the source system.
It should be noted that the source system may be a system running based on a browser, a system running based on a database, or a Windows program. And the third party system automatically adapts to a corresponding target acquisition mode from the preset acquisition modes according to the source system. The preset acquisition mode is a non-business interface data acquisition mode.
Further, the determining, according to the type of the source system, the corresponding target acquisition mode from the preset acquisition modes may include: when the source system is a browser-based system, the corresponding target acquisition mode is a first target acquisition mode; when the source system is a system running based on a database, the corresponding target acquisition mode is a second target acquisition mode; when the source system is a Windows program, the corresponding target acquisition mode is a second target acquisition mode; the preset acquisition modes comprise a first target acquisition mode, a second target acquisition mode and a third target acquisition mode.
The first target acquisition mode may specifically be: based on the Selenium and xPath, the third party system operates the browser to obtain data from the source system. The second target acquisition mode may specifically be: and the third party system runs SQL sentences without editing rights in the database of the source system to acquire service data. The third target acquisition mode may specifically be: the third party system operates the source system through the Windows API and obtains the service data from the source system based on the keyboard message or the mouse message.
Step S302, service data is acquired from a source system in a target acquisition mode.
Specifically, after the third party system automatically adapts to the target acquisition mode according to the source system, service data is acquired from the source data through the target acquisition mode. The process of acquiring the service data will be correspondingly different according to the different target acquisition modes.
Further, when the target acquisition mode is the first target acquisition mode, the process of acquiring the service data from the source system by using the target acquisition mode may specifically include: based on the Selenium software, a browser of the source system is operated to open a corresponding page of the source system; acquiring an operation object in a browser of a source system through xPath; and extracting service data according to the operation object.
Among them, selenium is a tool software for Web application testing. The selenum can operate the browser as if the real user were operating. The browsers they support include, but are not limited to IE, firefox, chrome and the like. Its main functions may include: testing compatibility with a browser, testing system functions, etc.
xPath (XML Path Language) is an XML path language, which is a language used to determine the location of a portion of an XML document. xPath is based on an XML tree structure, providing the ability to find nodes in a data structure tree, which is part of the W3C standard.
Specifically, the Selenium software is run on the third party system, the third party system can operate the browser on the source system, open the corresponding page, then acquire the operation object in the browser through the xPath, and then extract the corresponding service data based on the browser operation object. By means of the Selenium+xPath mode, data interaction between the source system and the third party system is not dependent on interfaces, development or interface development is not needed, and data interaction is carried out by modifying or developing programs and the like.
When the target acquisition mode is the second target acquisition mode, the process of acquiring the service data from the source system by using the target acquisition mode may specifically include: and acquiring service data by running SQL sentences without editing rights in a database of the source system. The SQL is a structured query language and is used for data access, data query, update and management of a relational database system.
SQL statements can degrade the security of the system if data editing rights are provided externally. The SQL statement does not have editing authority, so that the safety of the system can be further improved.
When the target acquisition mode is the third target acquisition mode, the process of acquiring the service data from the source system by using the target acquisition mode may specifically include: switching to the front end of the window through the Windows API operation source system; and activating the editing window through the Windows operation message, and acquiring service data.
Specifically, the third party system switches to the front end of the window through Windows API operation source system, then activates the editing window through Windows operation information such as keyboard information or mouse information and obtains data, which includes using clicking or double clicking to activate the editing window, and using keyboard information to send control+C to copy data.
Note that the Windows API called here is an interface of the bottom layer of the Windows system, and is different from a service interface developed or reserved for realizing system interfacing.
After the service data of the source system is acquired, the third party system can perform flow customization according to the data, namely determining whether to open a desired operation page of the destination system or operate different operation objects.
Step S202, analyzing the business data and determining the business flow.
Step 203, corresponding business operation is executed to the destination system through a non-business interface mode according to the business flow and the business data.
It should be noted that, the data interaction between the third party system and the destination system is realized by a non-service interface mode, that is, the corresponding service operation can be realized between the third party system and the destination system without a service interface. Of course, the types of the destination systems are different, and the non-business interface data interaction modes between the third party system and the destination systems are correspondingly different.
Specifically, the third party system performs an operation or analysis on the acquired service data to determine whether the executed service flow, for example, data transfer, or operation of a different object on the destination system, or the like. After determining the next service flow to be executed, corresponding service operations can be executed according to the service flow and the service data. For example, if the business process is a text entry process, entering corresponding information in a text box; if the business process is a button or link, clicking on the corresponding operation object.
In some embodiments, when the destination system is a system running based on a browser, referring to the flow schematic block diagram of the third party system operating the destination system shown in fig. 4, the process of executing, according to the service flow and the service data, the corresponding service operation on the destination system by using the non-service interface manner may include:
step S401, based on the Selenium software, a browser of an operation destination system opens a business operation page.
Step S402, obtaining an operation object in a browser of a source system through xPath.
Step S403, according to the business data and the business flow, operating the operation object in the browser of the source system.
Specifically, when the target system is a browser-based system, running the Selenium software in a third-party system, and opening a browser in the target system to open a corresponding operation page; and then acquiring an operation object in the browser through the xPath, and operating the operation object in the browser to realize system docking. By means of the Selenium+xPath mode, data interaction between the target system and the third party system is not dependent on interfaces, development or development of interfaces is not needed, and data interaction is carried out by modifying or developing programs and the like.
It can be seen that the third party system obtains service data from the source system, and the destination system is operated according to the service data, so that service interfaces are not required to be reserved or developed between the source system and the destination system, between the third party system and the source system and between the third party system and the destination system, corresponding programs are modified or developed, the system docking difficulty is reduced, the system docking efficiency is improved, the system does not develop interfaces or interface calling programs, the hidden danger of instability of the system is reduced, and the stability is higher.
It should be understood that the sequence number of each step in the foregoing embodiment does not mean that the execution sequence of each process should be determined by the function and the internal logic of each process, and should not limit the implementation process of the embodiment of the present application in any way.
Example III
Referring to fig. 5, a schematic block diagram of a system docking device provided in an embodiment of the present application, which is integrated in the third party system in the system docking management system of the first aspect, may include:
a service data obtaining module 51, configured to obtain service data from the source system through a non-service interface manner;
the flow determining module 52 is configured to analyze the service data and determine a service flow;
and the operation module 53 is configured to execute corresponding service operations on the destination system through a non-service interface mode according to the service flow and the service data.
In a possible implementation manner, the service data obtaining module may include:
the acquisition mode determining unit is used for determining a corresponding target acquisition mode from preset acquisition modes according to the type of the source system;
and the acquisition unit is used for acquiring the service data from the source system in a target acquisition mode.
In one possible implementation, the acquisition mode determining unit is specifically configured to: when the source system is a browser-based system, the corresponding target acquisition mode is a first target acquisition mode; when the source system is a system running based on a database, the corresponding target acquisition mode is a second target acquisition mode; when the source system is a Windows program, the corresponding target acquisition mode is a second target acquisition mode; the preset acquisition modes comprise a first target acquisition mode, a second target acquisition mode and a third target acquisition mode.
In a possible implementation manner, the acquiring unit is specifically configured to: based on the Selenium software, a browser of the source system is operated to open a corresponding page of the source system; acquiring an operation object in a browser of a source system through xPath; extracting service data according to the operation object; or the SQL statement without editing authority is operated in the database of the source system to acquire service data; or switching the source system to the front end of the window through Windows API operation; and activating the editing window through the Windows operation message, and acquiring service data.
In one possible implementation, when the target system is a browser-based system, the operation module may include:
the first operation unit is used for operating a browser of the target system to open a business operation page based on the Selenium software;
an operation object obtaining unit, configured to obtain an operation object in a browser of a source system through xPath;
and the second operation unit is used for operating the operation object in the browser of the source system according to the service data and the service flow.
It should be noted that, the device provided in the embodiment of the present application corresponds to the system docking method provided in the second embodiment, and the relevant or corresponding description is referred to in the corresponding content above, and is not limited herein.
Therefore, by introducing the third system, system development or an open interface is not needed, and system docking is realized without modifying or developing a program, so that docking difficulty is reduced, and docking efficiency and system stability are improved.
Example IV
Fig. 6 is a schematic diagram of a terminal device according to an embodiment of the present application. As shown in fig. 6, the terminal device 6 of this embodiment includes: a processor 60, a memory 61 and a computer program 62 stored in said memory 61 and executable on said processor 60. The processor 60, when executing the computer program 62, implements the steps of the various system docking method embodiments described above, such as steps S201 to S203 shown in fig. 2. Alternatively, the processor 60, when executing the computer program 62, performs the functions of the modules or units of the apparatus embodiments described above, such as the functions of the modules 51 to 53 shown in fig. 5.
By way of example, the computer program 62 may be divided into one or more modules or units, which are stored in the memory 61 and executed by the processor 60 to complete the present application. The one or more modules or units may be a series of computer program instruction segments capable of performing specific functions for describing the execution of the computer program 62 in the terminal device 6. For example, the computer program 62 may be divided into a service data acquisition module, a flow determination module, and an operation module, each of which specifically functions as follows:
the service data acquisition module is used for acquiring service data from the source system in a non-service interface mode; the flow determining module is used for analyzing the service data and determining the service flow; and the operation module is used for executing corresponding service operation on the target system in a non-service interface mode according to the service flow and the service data.
The terminal device 6 may be a computing device such as a desktop computer, a notebook computer, a palm computer, a cloud server, etc. The terminal device may include, but is not limited to, a processor 60, a memory 61. It will be appreciated by those skilled in the art that fig. 6 is merely an example of the terminal device 6 and does not constitute a limitation of the terminal device 6, and may include more or less components than illustrated, or may combine certain components, or different components, e.g., the terminal device may further include an input-output device, a network access device, a bus, etc.
The processor 60 may be a central processing unit (Central Processing Unit, CPU), other general purpose processors, digital signal processors (Digital Signal Processor, DSP), application specific integrated circuits (Application Specific Integrated Circuit, ASIC), off-the-shelf programmable gate arrays (Field-Programmable Gate Array, FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, or the like. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.
The memory 61 may be an internal storage unit of the terminal device 6, such as a hard disk or a memory of the terminal device 6. The memory 61 may be an external storage device of the terminal device 6, such as a plug-in hard disk, a Smart Media Card (SMC), a Secure Digital (SD) Card, a Flash memory Card (Flash Card) or the like, which are provided on the terminal device 6. Further, the memory 61 may also include both an internal storage unit and an external storage device of the terminal device 6. The memory 61 is used for storing the computer program and other programs and data required by the terminal device. The memory 61 may also be used for temporarily storing data that has been output or is to be output.
It will be apparent to those skilled in the art that, for convenience and brevity of description, only the above-described division of the functional units and modules is illustrated, and in practical application, the above-described functional distribution may be performed by different functional units and modules according to needs, i.e. the internal structure of the apparatus is divided into different functional units or modules to perform all or part of the above-described functions. The functional units and modules in the embodiment may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit, where the integrated units may be implemented in a form of hardware or a form of a software functional unit. In addition, specific names of the functional units and modules are only for convenience of distinguishing from each other, and are not used for limiting the protection scope of the present application. The specific working process of the units and modules in the above system may refer to the corresponding process in the foregoing method embodiment, which is not described herein again.
In the foregoing embodiments, the descriptions of the embodiments are emphasized, and in part, not described or illustrated in any particular embodiment, reference is made to the related descriptions of other embodiments.
Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.
In the embodiments provided in the present application, it should be understood that the disclosed apparatus, terminal device and method may be implemented in other manners. For example, the apparatus, terminal device embodiments described above are merely illustrative, e.g., the division of the modules or units is merely a logical function division, and there may be additional divisions in actual implementation, e.g., multiple units or components may be combined or integrated into another system, or some features may be omitted, or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection via interfaces, devices or units, which may be in electrical, mechanical or other forms.
The units described as separate units may or may not be physically separate, and units shown as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.
In addition, each functional unit in each embodiment of the present application may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit. The integrated units may be implemented in hardware or in software functional units.
The integrated modules or units, if implemented in the form of software functional units and sold or used as stand-alone products, may be stored in a computer readable storage medium. Based on such understanding, the present application may implement all or part of the flow of the method of the above embodiment, or may be implemented by a computer program to instruct related hardware, where the computer program may be stored in a computer readable storage medium, and when the computer program is executed by a processor, the computer program may implement the steps of each method embodiment described above. Wherein the computer program comprises computer program code which may be in source code form, object code form, executable file or some intermediate form etc. The computer readable medium may include: any entity or device capable of carrying the computer program code, a recording medium, a U disk, a removable hard disk, a magnetic disk, an optical disk, a computer Memory, a Read-Only Memory (ROM), a random access Memory (RAM, random Access Memory), an electrical carrier signal, a telecommunications signal, a software distribution medium, and so forth. It should be noted that the computer readable medium contains content that can be appropriately scaled according to the requirements of jurisdictions in which such content is subject to legislation and patent practice, such as in certain jurisdictions in which such content is subject to legislation and patent practice, the computer readable medium does not include electrical carrier signals and telecommunication signals.
The above embodiments are only for illustrating the technical solution of the present application, and are not limiting; although the present application has been described in detail with reference to the foregoing embodiments, it should be understood by those of ordinary skill in the art that: the technical scheme described in the foregoing embodiments can be modified or some technical features thereof can be replaced by equivalents; such modifications and substitutions do not depart from the spirit and scope of the technical solutions of the embodiments of the present application, and are intended to be included in the scope of the present application.
Claims (10)
1. The system docking management system is characterized by comprising a source system, a third party system in communication connection with the source system and a destination system in communication connection with the third party system;
the third party system is used for acquiring service data from the source system in a non-service interface mode; analyzing the service data to determine a service flow; according to the service flow and the service data, corresponding service operation is executed on the target system in a non-service interface mode;
the source system is a party initiating service operation in system docking, and the destination system is a party receiving service operation in system docking;
the third party system is a system independent of the source system and the destination system or a subsystem subordinate to the source system or the destination system;
the non-business interface mode is a data acquisition mode, and the third party system is preset with the data acquisition mode; the third party system is specifically configured to: and according to the type of the source system, adapting a corresponding data acquisition mode, and acquiring the service data from the source system according to the corresponding data acquisition mode.
2. A system docking method applied to the third party system in the system docking management system of claim 1, comprising:
acquiring service data from a source system through a non-service interface mode;
analyzing the service data to determine a service flow;
and executing corresponding business operation on the target system in a non-business interface mode according to the business flow and the business data.
3. The method of claim 2, wherein the obtaining service data from the source system via the non-service interface comprises:
determining a corresponding target acquisition mode from preset acquisition modes according to the type of the source system;
and acquiring the service data from the source system in the target acquisition mode.
4. The method of claim 3, wherein determining a corresponding target acquisition mode from among preset acquisition modes according to the type of the source system comprises:
when the source system is a browser-based system, the corresponding target acquisition mode is a first target acquisition mode;
when the source system is a system running based on a database, the corresponding target acquisition mode is a second target acquisition mode;
when the source system is a Windows program, the corresponding target acquisition mode is a third target acquisition mode;
the preset acquisition modes comprise the first target acquisition mode, the second target acquisition mode and the third target acquisition mode.
5. The method of claim 4, wherein said obtaining said traffic data from said source system by said target obtaining means comprises:
operating a browser of the source system to open a corresponding page of the source system based on the Selenium software;
acquiring an operation object in a browser of the source system through xPath;
extracting the service data according to the operation object; or alternatively
The service data are obtained by running SQL sentences without editing rights in a database of the source system; or alternatively
Operating the source system to switch to the front end of the window through Windows API;
and activating an editing window through the Windows operation message, and acquiring the service data.
6. The method of claim 5, wherein when the destination system is a browser-based system, the performing, according to the service flow and the service data, the corresponding service operation on the destination system through a non-service interface manner includes:
operating a browser of the target system to open a business operation page based on the Selenium software;
acquiring an operation object in a browser of the source system through xPath;
and operating the operation object in the browser of the source system according to the service data and the service flow.
7. A system docking device, a third party system integrated in the system docking management system of claim 1, comprising:
the service data acquisition module is used for acquiring service data from the source system in a non-service interface mode;
the flow determining module is used for analyzing the service data and determining a service flow;
and the operation module is used for executing corresponding service operation on the target system in a non-service interface mode according to the service flow and the service data.
8. The apparatus of claim 7, wherein the traffic data acquisition module comprises:
the acquisition mode determining unit is used for determining a corresponding target acquisition mode from preset acquisition modes according to the type of the source system;
and the acquisition unit is used for acquiring the service data from the source system in the target acquisition mode.
9. A terminal device comprising a memory, a processor and a computer program stored in the memory and executable on the processor, characterized in that the processor implements the steps of the method according to any of claims 2 to 6 when the computer program is executed.
10. A computer readable storage medium storing a computer program, characterized in that the computer program when executed by a processor implements the steps of the method according to any one of claims 2 to 6.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910283811.XA CN110147397B (en) | 2019-04-10 | 2019-04-10 | System docking method, device, management system, terminal equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910283811.XA CN110147397B (en) | 2019-04-10 | 2019-04-10 | System docking method, device, management system, terminal equipment and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN110147397A CN110147397A (en) | 2019-08-20 |
| CN110147397B true CN110147397B (en) | 2023-06-20 |
Family
ID=67588964
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910283811.XA Active CN110147397B (en) | 2019-04-10 | 2019-04-10 | System docking method, device, management system, terminal equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110147397B (en) |
Families Citing this family (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111124365A (en) * | 2019-12-20 | 2020-05-08 | 中国建设银行股份有限公司 | RPA demand collection method and device |
| CN111177836B (en) * | 2019-12-30 | 2023-10-03 | 上海利策科技股份有限公司 | Ocean engineering design data acquisition method, system, medium and equipment |
| CN112612624A (en) * | 2020-12-25 | 2021-04-06 | 金蝶软件（中国）有限公司 | Data interaction method and device between systems, computer equipment and storage medium |
| CN113010240B (en) * | 2021-03-29 | 2024-02-02 | 北京金山云网络技术有限公司 | Data acquisition method, system, electronic equipment and storage medium |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104899015A (en) * | 2014-03-07 | 2015-09-09 | 上海高达星软件系统有限公司 | Service component management system and method thereof |
| WO2017109791A1 (en) * | 2015-12-22 | 2017-06-29 | Tangirala Srinivas | A system and method for building enterprise applications |
Family Cites Families (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US9182951B1 (en) * | 2013-10-04 | 2015-11-10 | Progress Software Corporation | Multi-ecosystem application platform as a service (aPaaS) |
| CN109471740A (en) * | 2018-10-31 | 2019-03-15 | 深圳智链物联科技有限公司 | Built-in system and third party system software interconnection method, device and terminal device |
-
2019
- 2019-04-10 CN CN201910283811.XA patent/CN110147397B/en active Active
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104899015A (en) * | 2014-03-07 | 2015-09-09 | 上海高达星软件系统有限公司 | Service component management system and method thereof |
| WO2017109791A1 (en) * | 2015-12-22 | 2017-06-29 | Tangirala Srinivas | A system and method for building enterprise applications |
Also Published As
| Publication number | Publication date |
|---|---|
| CN110147397A (en) | 2019-08-20 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110147397B (en) | System docking method, device, management system, terminal equipment and storage medium | |
| CN111026470B (en) | System and method for verification and conversion of input data | |
| WO2021017735A1 (en) | Smart contract formal verification method, electronic apparatus and storage medium | |
| CN108255837B (en) | SQL parser and method | |
| US20180089314A1 (en) | Messaging digest | |
| US20220138074A1 (en) | Method, electronic device and computer program product for processing data | |
| CN111708753A (en) | Method, device and equipment for evaluating database migration and computer storage medium | |
| EP4092538A1 (en) | Method and apparatus for testing electronic map, and electronic device and storage medium | |
| KR20210125448A (en) | Data annotation method, apparatus, electronic equipment and storage medium | |
| CN113656124A (en) | Login page generation method and device | |
| CN113806522A (en) | Abstract generation method, device, equipment and storage medium | |
| CN113204695A (en) | Website identification method and device | |
| CN108768742B (en) | Network construction method and device, electronic equipment and storage medium | |
| CN110764624A (en) | Method and device for customizing numeric keyboard for internet finance and electronic equipment | |
| CN115640279A (en) | Method and device for constructing data blood relationship | |
| CN114443990A (en) | URL (Uniform resource locator) normalization method and device | |
| CN113138767A (en) | Code language conversion method, device, electronic equipment and storage medium | |
| CN113362111A (en) | Content sending method and device and electronic equipment | |
| CN116775030B (en) | Method and device for creating security baseline | |
| CN110858240A (en) | Front-end module loading method and device | |
| CN115563183B (en) | Query method, query device and program product | |
| CN112287097B (en) | Method and device for analyzing markup language text, storage medium and electronic equipment | |
| CN116400962A (en) | Instruction processing method, apparatus and computer program product | |
| CN113110873A (en) | Method and apparatus for unifying system coding specifications | |
| CN114817058A (en) | Concurrent risk detection method and device, electronic equipment and storage medium |
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 |