CN106453213B - Call method and device between a kind of system - Google Patents
Call method and device between a kind of system Download PDFInfo
- Publication number
- CN106453213B CN106453213B CN201510491365.3A CN201510491365A CN106453213B CN 106453213 B CN106453213 B CN 106453213B CN 201510491365 A CN201510491365 A CN 201510491365A CN 106453213 B CN106453213 B CN 106453213B
- Authority
- CN
- China
- Prior art keywords
- application system
- context information
- parameter object
- method parameter
- rpc
- 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
- 238000000034 method Methods 0.000 title claims abstract description 226
- 238000012545 processing Methods 0.000 claims abstract description 65
- 239000002131 composite material Substances 0.000 claims description 17
- 230000005540 biological transmission Effects 0.000 claims description 5
- 230000002159 abnormal effect Effects 0.000 claims 8
- 238000005516 engineering process Methods 0.000 abstract description 3
- 238000010586 diagram Methods 0.000 description 14
- 238000004590 computer program Methods 0.000 description 7
- 238000012986 modification Methods 0.000 description 5
- 230000004048 modification Effects 0.000 description 5
- 230000008569 process Effects 0.000 description 5
- 230000006870 function Effects 0.000 description 4
- 230000004075 alteration Effects 0.000 description 1
- 238000004891 communication Methods 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 239000000284 extract Substances 0.000 description 1
- 238000004519 manufacturing process Methods 0.000 description 1
- 230000007246 mechanism Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 238000012546 transfer Methods 0.000 description 1
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/01—Protocols
- H04L67/133—Protocols for remote procedure calls [RPC]
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/54—Interprogram communication
- G06F9/547—Remote procedure calls [RPC]; Web services
-
- 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/10—Protocols in which an application is distributed across nodes in the network
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Computer And Data Communications (AREA)
- Stored Programmes (AREA)
Abstract
This application involves call method and devices between field of computer technology more particularly to a kind of system to improve the problem location efficiency under distributed multisystem framework to realize under the premise of not introducing the third party systems such as messaging bus.Call method includes: that the first application system is determining that being based on remote procedure call protocol RPC frame is that first application system method parameter object to be transmitted configures contextual information when needing to call the second application system between system provided by the embodiments of the present application；After first application system carries out serializing processing based on contextual information of the RPC frame to the method parameter object and configuration, it is transferred to the second application system.
Description
Technical Field
The present application relates to the field of computer technologies, and in particular, to a method and an apparatus for intersystem call.
Background
In an Information Technology (IT) system of a large enterprise or an internet large system architecture, a large system is often required to be deployed into a distributed multi-system architecture based on requirements of system expansibility and stability.
In a distributed multi-system architecture, based on the requirement of service logic, interface data communication between different application systems needs to be realized based on a Remote Procedure Call Protocol (RPC). When a service request needs to be completed by matching a plurality of application systems, each level of application system can process the transmitted method parameter object according to the own requirements, and transmit the processed method parameter object to the next level of application system for continuous processing. It can be seen that the method parameter object received by the last stage application system is data after multi-stage processing, if a problem occurs in the data (for example, a certain attribute is missing or does not conform to format convention), when problem location is required, the problem location can be performed only from bottom to top, and the location efficiency is low.
In order to avoid tracing and positioning the first-level and the second-level of the application system, a scheme is provided, a transfer service is provided through a third-party system such as a message bus, when the next-level application system is called, a calling method and a transferred method parameter object are sent to the message bus, the message bus acquires and records context information corresponding to the transferred method parameter object based on the calling method, and the next-level application system can acquire the context information corresponding to the transferred method parameter object through the message bus.
Disclosure of Invention
The embodiment of the application provides an intersystem calling method, which is used for improving the problem positioning efficiency under a distributed multi-system architecture on the premise of not introducing a third-party system such as a message bus.
The embodiment of the application provides an intersystem calling method, which comprises the following steps:
when the first application system determines that a second application system needs to be called, context information is configured for a method parameter object to be transmitted by the first application system based on a remote procedure call protocol (RPC) framework;
and the first application system serializes the parameter object and the configured context information based on the RPC framework and transmits the serialized parameter object and the configured context information to the second application system.
Optionally, the configuring, by the first application system, context information for the method parameter object to be transmitted by the first application system based on the RPC framework includes:
and the first application system configures context information for the method parameter object after detecting that the method parameter object has a context information configuration indication identifier through an RPC frame.
Optionally, the first application system serializes the parameter object and the configured context information based on an RPC framework, and includes:
creating a composite object containing the method parameter object and the configured context information, and carrying out serialization processing on the created composite object; or,
and respectively carrying out serialization processing on the method parameter object and the configured context information.
Optionally, the context information comprises one or more of the following information:
name of the first application system, server IP address of the first application system, class name called, method name.
Another embodiment of the present application provides an inter-system call method, including:
the second application system carries out deserialization processing on the serialized method parameter object and the context information transmitted by the first application system based on a remote procedure call protocol (RPC) framework;
and the second application system calls the deserialized method parameter object based on the RPC framework and stores the deserialized context information.
Optionally, the second application system performs deserialization processing on the serialized method parameter object and the context information transmitted by the first application system based on the RPC framework, including:
performing deserialization processing on the serialized composite object containing the method parameter object and the context information; or,
and performing deserialization processing on the serialized method parameter object and the serialized context information respectively.
Optionally, the second application system, based on the RPC framework, after performing a method call on the deserialized method parameter object and storing the deserialized context information, further includes:
when the third application system is determined to be called, configuring context information for a method parameter object to be transmitted, which is obtained after the second application system is called by a method, based on an RPC (remote procedure call) frame;
and on the basis of an RPC (remote procedure call) framework, serializing the method parameter object to be transmitted of the second application system, the context information configured for the method parameter object to be transmitted and the context information sent by the first application system, and then transmitting the serialized context information to the third application system.
Optionally, the second application system, based on the RPC framework, after performing a method call on the deserialized method parameter object and storing the deserialized context information, further includes:
and after receiving a query request aiming at the context information, extracting and feeding back the stored context information.
An embodiment of the present application provides an intersystem call apparatus, including:
the configuration module is used for configuring context information for the method parameter object to be transmitted of the first application system based on a remote procedure call protocol (RPC) framework when the second application system is determined to be called;
and the transmission module is used for transmitting the parameter object and the configured context information to a second application system after the parameter object and the configured context information are serialized on the basis of the RPC framework.
Another embodiment of the present application provides an inter-system call apparatus, including:
the processing module is used for performing deserialization processing on the serialized method parameter object and the context information transmitted by the first application system based on a remote procedure call protocol (RPC) framework;
and the execution module is used for calling the method of the deserialized method parameter object based on the RPC framework and storing the deserialized context information.
In the embodiment of the application, when a second application system is called through an RPC framework of a first application system, context information is configured for a transferred method parameter object, and the configured context information and the transferred method parameter object are serialized and then transmitted to the second application system. Therefore, each level of application system can increase the context information corresponding to the transmitted method parameter object when the application system carries out the serialization processing of the method parameter object based on the RPC frame; therefore, the information of the whole calling link corresponding to the finally output method parameter object is recorded in the context information stored in the last-stage application system, namely the bottom-layer application system, so that the problem positioning efficiency under the distributed multi-system architecture can be improved on the premise of not introducing third-party systems such as a message bus and the like.
Drawings
Fig. 1 is a flowchart of an inter-system call method according to an embodiment of the present application;
fig. 2 is a flowchart of an inter-system calling method according to a second embodiment of the present application;
fig. 3 is a flowchart of an intersystem call method provided in the third embodiment of the present application;
FIG. 4 is a schematic diagram of inter-system calls;
fig. 5 is a schematic structural diagram of an inter-system call device according to a fourth embodiment of the present application;
fig. 6 is a schematic structural diagram of an inter-system call device according to a fifth embodiment of the present application.
Detailed Description
The basic idea of the embodiment of the application is as follows: and expanding an RPC frame for inter-system call, and adding context information during serialization processing. Specifically, when a second application system is called through an RPC framework of a first application system, context information is configured for the transferred method parameter object, and the configured context information and the transferred method parameter object are serialized and then transmitted to the second application system. Therefore, each level of application system can increase the context information corresponding to the transmitted method parameter object when the application system carries out the serialization processing of the method parameter object based on the RPC frame; therefore, the information of the whole calling link corresponding to the finally output method parameter object is recorded in the context information stored in the last-stage application system, namely the bottom-layer application system, so that the problem positioning efficiency under the distributed multi-system architecture can be improved on the premise of not introducing third-party systems such as a message bus and the like.
The embodiments of the present application will be described in further detail with reference to the drawings attached hereto.
Example one
As shown in fig. 1, a flowchart of an inter-system call method provided in an embodiment of the present application includes the following steps:
s101: when the first application system determines that the second application system needs to be called, context information is configured for the method parameter object to be transmitted by the first application system based on a remote procedure call protocol (RPC) framework.
In the service processing related to multi-system call, after the first application system completes service logic processing, a method parameter object obtained after processing needs to be transferred to the second application system for processing continuously, that is, a request for calling the second application system is sent to an RPC frame of the second application system through the RPC frame of the first application system, so as to call a service method of the second application system for continuous service logic processing.
Here, the context information may include one or more of the following information:
name of the first application system, server IP address of the first application system, class name called, method name.
Through the context information configured by the first application system, the method calling process responsible for the first application system in the whole calling link of the method parameter object can be tracked.
S102: and the first application system serializes the parameter object and the configured context information based on the RPC framework and transmits the serialized parameter object and the configured context information to the second application system.
In this step, the RPC framework of the first application system serializes the context information and the method parameter object to be transferred, and then transmits the serialized context information and the method parameter object to the next-stage application system. In fact, the serialization processing mechanism of the RPC call is utilized, and the addition of the context information is completed in the serialization processing process.
S103: and the second application system carries out deserialization processing on the serialized method parameter object and the context information transmitted by the first application system based on a remote procedure call protocol (RPC) framework.
Here, the RPC framework of the second application system performs deserialization processing on the received serialized method parameter object and context information to obtain the original method parameter object and context information.
S104: and the second application system carries out method calling based on the deserialized method parameter object and stores the deserialized context information.
The second application system calls a service method based on the deserialized method parameter object to process the service logic of the second application system; and storing the deserialized context information, wherein the stored context information can be used for continuing to be transmitted to a next-level application system or used for inquiring.
Example two
As shown in fig. 2, a flowchart of an inter-system call method provided in the second embodiment of the present application includes the following steps:
s201: when the first application system needs to call the second application system, whether a method parameter object to be transmitted has a context information configuration indication mark is detected through an RPC frame, if so, S203 is entered, and if not, S202 is entered.
In specific implementation, which classes, methods, attributes and the like need to be configured with context information may be preset, and a context information configuration indication identifier, such as @ HoldContext, is added at a set position such as a name of the class/method/attribute where the context information needs to be configured; after the service logic processing is performed to obtain the relevant method parameter object, it is usually searched whether a set position of the class/method/attribute corresponding to the method parameter object has a context information configuration indication identifier to determine whether the context information corresponding to the method parameter object needs to be configured.
S202: the first application system is based on the RPC framework, and transmits the parameter object to be transmitted to the second application system after serialization processing.
Here, if the method parameter object to be transmitted does not need to be configured with context information, the RPC framework of the first application system may directly serialize the method parameter object and transmit the serialized method parameter object to the second application system.
S203: the first application system configures context information for the method parameter object based on an RPC framework, creates a composite object containing the method parameter object and the configured context information, and transmits the created composite object to a second application system after serialization processing; or, the parameter object and the configured context information are respectively serialized and then transmitted to a second application system.
Here, the RPC framework of the first application system may perform the serialization processing on the method parameter object and the configured context information as a composite object, or may perform the serialization processing on the two objects separately.
S204: the second application system performs deserialization processing on the serialized composite object containing the method parameter object and the context information based on the RPC framework; or performing deserialization processing on the serialized method parameter object and the serialized context information respectively.
Corresponding to S203, when performing deserialization, the RPC framework of the second application system may perform deserialization on a composite object of the method parameter object and the context information, or may perform deserialization on two objects of the method parameter object and the context information, respectively.
S205: and the second application system calls the deserialized method parameter object based on the RPC framework and stores the deserialized context information.
Here, the RPC framework of the second application system calls a service method based on the deserialized method parameter object, and the second application system performs the processing of its own service logic; and the RPC framework of the second application system stores the deserialized context information, and the stored context information can be used for continuing to be transmitted to the next-level application system or used for querying. Specifically, if the second application system is not the application system at the bottom layer of the current service, the second application system serializes the method parameter object obtained after the service logic is performed and the context information corresponding to the method parameter object and the previously received context information and transmits the serialized context information to the next-stage application system based on the RPC framework. If the second application system is the lowest application system of the current service, the context information can be saved for subsequent query. This idea will be further described in example three.
EXAMPLE III
As shown in fig. 3, which is a flowchart of an inter-system call method provided in a third embodiment of the present application, fig. 4 is a schematic diagram of an inter-system call corresponding to the third embodiment, where the third embodiment includes the following steps:
s301: when the first application system determines that the second application system needs to be called, context information is configured for the method parameter object to be transmitted by the first application system based on the RPC framework.
As shown in fig. 4, firstly, a developer may add a context information configuration indication identifier, such as @ HoldContext, to a set location of a class/attribute/method or the like that needs to maintain a context through a development interface of the first application system.
After receiving an instruction for calling a second application system, an RPC frame of the first application system detects whether a set position corresponding to a method parameter object to be transmitted has a corresponding context information configuration indication mark, and if so, configures context information for the method parameter object to be transmitted.
S302: and the first application system serializes the parameter object and the configured context information based on the RPC framework and transmits the serialized parameter object and the configured context information to the second application system.
As shown in fig. 4, after the RPC framework of the first application system serializes the method parameter object to be transmitted and the configured context information, the serialized method parameter object and the configured context information are transmitted to the RPC framework of the second application system, that is, the second application system continues processing.
S303: the second application system carries out deserialization processing on the serialized method parameter object and the context information transmitted by the first application system based on the RPC framework; and carrying out method calling based on the deserialized method parameter object, and storing the deserialized context information.
As shown in fig. 4, the RPC framework of the second application system performs deserialization processing on the received listed method parameter object and context information; and the RPC framework of the second application system calls the service method based on the deserialized method parameter object, and the second application system performs self service logic processing based on the called service method.
S304: and when the second application system determines that a third application system needs to be called, configuring context information for the method parameter object to be transmitted, which is obtained after the second application system carries out method calling, based on the RPC framework.
S305: the second application system carries out serialization processing on the method parameter object to be transmitted of the second application system, the context information configured for the method parameter object to be transmitted and the context information sent by the first application system based on the RPC framework, and then transmits the method parameter object to a third application system.
As shown in fig. 4, after receiving an instruction for calling a third application system, the RPC framework of the second application system configures context information for a method parameter object to be transmitted, which is obtained after a service method is called, and transmits the method parameter object, the configured context information, and previous context information to the third application system after performing serialization processing.
S306: the third application system carries out deserialization processing on the serialized method parameter object and the context information transmitted by the second application system based on the RPC framework; and carrying out method calling based on the deserialized method parameter object, and storing the deserialized context information.
As shown in fig. 4, the RPC framework of the third application system performs deserialization processing on the received serialized information, and stores all the deserialized context information; and (3) using the deserialized method parameter object to call a service method, and performing self service logic processing (such as risk identification service logic processing) by the third application system based on the called service method.
And the RPC frame of the third application system provides a context information service interface, after receiving a context information query request aiming at any method parameter object, queries a call link corresponding to the method parameter object based on the RPC frame, and extracts context information corresponding to each method parameter object on the call link.
Based on the same inventive concept, the embodiment of the present application further provides an inter-system calling device corresponding to the inter-system calling method, and as the principle of the device for solving the problem is similar to the inter-system calling method in the embodiment of the present application, the implementation of the device may refer to the implementation of the method, and repeated details are not repeated.
Example four
As shown in fig. 5, a schematic structural diagram of an inter-system call device provided in the fourth embodiment of the present application includes:
a configuration module 51, configured to configure context information for a method parameter object to be transmitted by the first application system based on a remote procedure call protocol (RPC) framework when it is determined that the second application system needs to be called;
and the transmission module 52 is configured to perform serialization processing on the parameter object and the configured context information based on the RPC framework, and then transmit the serialized parameter object and the configured context information to the second application system.
Optionally, the configuration module 51 is specifically configured to:
and configuring context information for the method parameter object after detecting that the method parameter object has a context information configuration indication mark through an RPC frame.
Optionally, the transmission module 52 is specifically configured to:
creating a composite object containing the method parameter object and the configured context information, and carrying out serialization processing on the created composite object; or,
and respectively carrying out serialization processing on the method parameter object and the configured context information.
Optionally, the context information comprises one or more of the following information:
name of the first application system, server IP address of the first application system, class name called, method name.
EXAMPLE five
As shown in fig. 6, a schematic structural diagram of an inter-system call device provided in the fifth embodiment of the present application includes:
the processing module 61 is configured to perform deserialization processing on the serialized method parameter object and the context information transmitted by the first application system based on a remote procedure call protocol (RPC) framework;
and the execution module 62 is configured to perform method call on the deserialized method parameter object based on the RPC framework, and store the deserialized context information.
Optionally, the processing module 61 is specifically configured to:
performing deserialization processing on the serialized composite object containing the method parameter object and the context information; or,
and performing deserialization processing on the serialized method parameter object and the serialized context information respectively.
Optionally, the executing module 62 is further configured to:
when the third application system is determined to be called, configuring context information for a method parameter object to be transmitted, which is obtained after the second application system is called by a method, based on an RPC (remote procedure call) frame; and on the basis of an RPC (remote procedure call) framework, serializing the method parameter object to be transmitted of the second application system, the context information configured for the method parameter object to be transmitted and the context information sent by the first application system, and then transmitting the serialized context information to the third application system.
Optionally, the executing module 62 is further configured to:
and after receiving a query request aiming at the context information, extracting and feeding back the stored context information.
As will be appreciated by one skilled in the art, embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
The present application is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the application. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
While the preferred embodiments of the present application have been described, additional variations and modifications in those embodiments may occur to those skilled in the art once they learn of the basic inventive concepts. Therefore, it is intended that the appended claims be interpreted as including preferred embodiments and all alterations and modifications as fall within the scope of the application.
It will be apparent to those skilled in the art that various changes and modifications may be made in the present application without departing from the spirit and scope of the application. Thus, if such modifications and variations of the present application fall within the scope of the claims of the present application and their equivalents, the present application is intended to include such modifications and variations as well.
Claims (16)
1. An inter-system call method, comprising:
when the first application system determines that a second application system needs to be called, context information is configured for a method parameter object to be transmitted by the first application system based on a remote procedure call protocol (RPC) framework;
the first application system serializes the parameter object and the configured context information based on the RPC framework and then transmits the serialized parameter object and the configured context information to a second application system;
when the second application system is the last-stage application system and the method parameters are found to be abnormal, positioning the initially abnormal application system according to the stored context information; the context information stored in the last level application system records the information of the whole calling link corresponding to the finally output method parameter object.
2. The method of claim 1, wherein the first application system configuring context information for the method parameter object to be transmitted by the first application system based on the RPC framework comprises:
and the first application system configures context information for the method parameter object after detecting that the method parameter object has a context information configuration indication identifier through an RPC frame.
3. The method of claim 1, wherein the first application system serializes the method parameter objects and configured context information based on an RPC framework, comprising:
creating a composite object containing the method parameter object and the configured context information, and carrying out serialization processing on the created composite object; or,
and respectively carrying out serialization processing on the method parameter object and the configured context information.
4. A method according to any one of claims 1 to 3, wherein the context information comprises one or more of:
name of the first application system, server IP address of the first application system, class name called, method name.
5. An inter-system call method, comprising:
the second application system carries out deserialization processing on the serialized method parameter object and the context information transmitted by the first application system based on a remote procedure call protocol (RPC) framework;
the second application system calls the deserialized method parameter object based on the RPC framework and stores the deserialized context information;
when the second application system is the last-stage application system and the method parameters are found to be abnormal, positioning the initially abnormal application system according to the stored context information; the context information stored in the last level application system records the information of the whole calling link corresponding to the finally output method parameter object.
6. The method of claim 5, wherein the second application system deserializing the serialized method parameter object and context information transmitted by the first application system based on the RPC framework comprises:
performing deserialization processing on the serialized composite object containing the method parameter object and the context information; or,
and performing deserialization processing on the serialized method parameter object and the serialized context information respectively.
7. The method of claim 5 or 6, wherein after the second application system makes a method call to the deserialized method parameter object based on the RPC framework and saves the deserialized context information, the method further comprises:
when the third application system is determined to be called, configuring context information for a method parameter object to be transmitted, which is obtained after the second application system is called by a method, based on an RPC (remote procedure call) frame;
and on the basis of an RPC (remote procedure call) framework, serializing the method parameter object to be transmitted of the second application system, the context information configured for the method parameter object to be transmitted and the context information sent by the first application system, and then transmitting the serialized context information to the third application system.
8. The method of claim 5 or 6, wherein after the second application system makes a method call to the deserialized method parameter object based on the RPC framework and saves the deserialized context information, the method further comprises:
and after receiving a query request aiming at the context information, extracting and feeding back the stored context information.
9. An inter-system call apparatus, comprising:
the configuration module is used for configuring context information for a method parameter object to be transmitted by the first application system based on a remote procedure call protocol (RPC) framework when the first application system determines that the second application system needs to be called;
the transmission module is used for serializing the parameter object and the configured context information based on the RPC framework and then transmitting the serialized parameter object and the configured context information to a second application system; when the second application system is the last-stage application system and the method parameters are found to be abnormal, positioning the initially abnormal application system according to the stored context information; the context information stored in the last level application system records the information of the whole calling link corresponding to the finally output method parameter object.
10. The apparatus of claim 9, wherein the configuration module is specifically configured to:
and configuring context information for the method parameter object after detecting that the method parameter object has a context information configuration indication mark through an RPC frame.
11. The apparatus of claim 9, wherein the transmission module is specifically configured to:
creating a composite object containing the method parameter object and the configured context information, and carrying out serialization processing on the created composite object; or,
and respectively carrying out serialization processing on the method parameter object and the configured context information.
12. An apparatus as claimed in any one of claims 9 to 11, wherein the context information comprises one or more of: name of the first application system, server IP address of the first application system, class name called, method name.
13. An inter-system call apparatus, comprising:
the processing module is used for the second application system to perform deserialization processing on the serialized method parameter object and the context information transmitted by the first application system based on a remote procedure call protocol (RPC) framework;
the execution module is used for calling the method of the deserialized method parameter object based on the RPC frame and storing the deserialized context information; when the second application system is the last-stage application system and the method parameters are found to be abnormal, positioning the initially abnormal application system according to the stored context information; the context information stored in the last level application system records the information of the whole calling link corresponding to the finally output method parameter object.
14. The apparatus of claim 13, wherein the processing module is specifically configured to:
performing deserialization processing on the serialized composite object containing the method parameter object and the context information; or,
and performing deserialization processing on the serialized method parameter object and the serialized context information respectively.
15. The apparatus of claim 13 or 14, wherein the execution module is further to:
when the third application system is determined to be called, configuring context information for a method parameter object to be transmitted, which is obtained after the second application system is called by a method, based on an RPC (remote procedure call) frame; and on the basis of an RPC (remote procedure call) framework, serializing the method parameter object to be transmitted of the second application system, the context information configured for the method parameter object to be transmitted and the context information sent by the first application system, and then transmitting the serialized context information to the third application system.
16. The apparatus of claim 13 or 14, wherein the execution module is further to:
and after receiving a query request aiming at the context information, extracting and feeding back the stored context information.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201510491365.3A CN106453213B (en) | 2015-08-11 | 2015-08-11 | Call method and device between a kind of system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201510491365.3A CN106453213B (en) | 2015-08-11 | 2015-08-11 | Call method and device between a kind of system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN106453213A CN106453213A (en) | 2017-02-22 |
| CN106453213B true CN106453213B (en) | 2019-09-17 |
Family
ID=58093444
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201510491365.3A Active CN106453213B (en) | 2015-08-11 | 2015-08-11 | Call method and device between a kind of system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN106453213B (en) |
Families Citing this family (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109460304B (en) * | 2017-09-06 | 2022-06-03 | 阿里巴巴集团控股有限公司 | Cross-application notification display and notification content packaging method and device |
| CN108833500B (en) * | 2018-05-29 | 2021-03-30 | 创新先进技术有限公司 | Service calling method, service providing method, data transmission method and server |
| CN110958218B (en) * | 2019-10-16 | 2022-01-28 | 平安国际智慧城市科技股份有限公司 | Data transmission method based on multi-network communication and related equipment |
| CN114697402B (en) * | 2020-12-29 | 2023-07-14 | 中移物联网有限公司 | Internet of things protocol serialization method and device and electronic equipment |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1852209A (en) * | 2006-05-31 | 2006-10-25 | 北京和利时系统工程股份有限公司 | Remote process transfering method and system in distribution type control system |
| CN101706901A (en) * | 2009-12-01 | 2010-05-12 | 中国建设银行股份有限公司 | Device and method for realizing shielding of different working flow products |
| CN102148698A (en) * | 2010-12-29 | 2011-08-10 | 华为技术有限公司 | Network configuration protocol-based network configuration management method, equipment and system |
| CN102223291A (en) * | 2010-04-14 | 2011-10-19 | 华为技术有限公司 | Method, device and communication system for realizing device access |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US8869176B2 (en) * | 2012-11-09 | 2014-10-21 | Qualcomm Incorporated | Exposing host operating system services to an auxillary processor |
-
2015
- 2015-08-11 CN CN201510491365.3A patent/CN106453213B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1852209A (en) * | 2006-05-31 | 2006-10-25 | 北京和利时系统工程股份有限公司 | Remote process transfering method and system in distribution type control system |
| CN101706901A (en) * | 2009-12-01 | 2010-05-12 | 中国建设银行股份有限公司 | Device and method for realizing shielding of different working flow products |
| CN102223291A (en) * | 2010-04-14 | 2011-10-19 | 华为技术有限公司 | Method, device and communication system for realizing device access |
| CN102148698A (en) * | 2010-12-29 | 2011-08-10 | 华为技术有限公司 | Network configuration protocol-based network configuration management method, equipment and system |
Also Published As
| Publication number | Publication date |
|---|---|
| CN106453213A (en) | 2017-02-22 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN106453213B (en) | Call method and device between a kind of system | |
| US20180359140A1 (en) | Method, device, and system for processing a terminal fault | |
| WO2019144761A1 (en) | Data synchronization method, distributed system and device | |
| CN111404990A (en) | File transmission method, device, client and storage medium | |
| CN112269588B (en) | Algorithm upgrading method, device, terminal and computer readable storage medium | |
| WO2016202000A1 (en) | Differential rollback upgrading method and apparatus | |
| CN109343983B (en) | Information interaction method, device, equipment and storage medium between function modules | |
| CN113656503A (en) | Data synchronization method, device and system and computer readable storage medium | |
| CN110727524A (en) | Method and device for realizing remote procedure call | |
| CN104598266A (en) | Client application service logic updating method and device and equipment | |
| CN111008254A (en) | Object creating method and device, computer equipment and storage medium | |
| CN114676205A (en) | Event information processing method and device | |
| CN114417202A (en) | Artificial intelligence-based mixed page skipping method, device and equipment | |
| CN104484413A (en) | Method and device for obtaining searching results | |
| CN109995548B (en) | Device management method and system, data transmission method and system and terminal device | |
| CN112199443B (en) | Data synchronization method and device, computer equipment and storage medium | |
| CN107577822A (en) | A kind of method of data synchronization, data synchronization unit and mobile terminal | |
| CN110768811B (en) | Method, device and system for updating YANG model file library | |
| CN112035169A (en) | Skip processing method and device, computer equipment and computer readable storage medium | |
| CN106453592B (en) | Asynchronous call processing method, device and distributed system | |
| CN109389271B (en) | Application performance management method and system | |
| CN114221883B (en) | Message testing method, device, server and storage medium | |
| US20110055279A1 (en) | Application server, object management method, and object management program | |
| CN115794927A (en) | Service function expansion method and system | |
| WO2015169053A1 (en) | Packet data processing method, device and system |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant | ||
| TR01 | Transfer of patent right |
Effective date of registration: 20200918 Address after: Cayman Enterprise Centre, 27 Hospital Road, George Town, Grand Cayman Islands Patentee after: Innovative advanced technology Co.,Ltd. Address before: Cayman Enterprise Centre, 27 Hospital Road, George Town, Grand Cayman Islands Patentee before: Advanced innovation technology Co.,Ltd. Effective date of registration: 20200918 Address after: Cayman Enterprise Centre, 27 Hospital Road, George Town, Grand Cayman Islands Patentee after: Advanced innovation technology Co.,Ltd. Address before: Cayman Islands Grand Cayman capital building, a four storey No. 847 mailbox Patentee before: Alibaba Group Holding Ltd. |
|
| TR01 | Transfer of patent right |