CN105471968B - A kind of method for interchanging data, system and data platform server - Google Patents
A kind of method for interchanging data, system and data platform server Download PDFInfo
- Publication number
- CN105471968B CN105471968B CN201510792194.8A CN201510792194A CN105471968B CN 105471968 B CN105471968 B CN 105471968B CN 201510792194 A CN201510792194 A CN 201510792194A CN 105471968 B CN105471968 B CN 105471968B
- Authority
- CN
- China
- Prior art keywords
- data
- server
- client
- service
- data exchange
- 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 69
- 238000013497 data interchange Methods 0.000 claims abstract 2
- 238000006243 chemical reaction Methods 0.000 claims description 14
- 238000013480 data collection Methods 0.000 claims description 7
- 238000012545 processing Methods 0.000 claims description 7
- 238000012795 verification Methods 0.000 claims description 7
- 230000004044 response Effects 0.000 claims description 5
- 238000004891 communication Methods 0.000 claims description 4
- 238000013481 data capture Methods 0.000 abstract 2
- 238000003032 molecular docking Methods 0.000 description 12
- 238000010586 diagram Methods 0.000 description 6
- 230000006870 function Effects 0.000 description 5
- 230000002159 abnormal effect Effects 0.000 description 4
- 230000008901 benefit Effects 0.000 description 3
- 230000008569 process Effects 0.000 description 3
- 230000005856 abnormality Effects 0.000 description 2
- 238000004590 computer program Methods 0.000 description 2
- 238000012423 maintenance Methods 0.000 description 2
- 238000012549 training Methods 0.000 description 2
- 239000012190 activator Substances 0.000 description 1
- 230000005540 biological transmission Effects 0.000 description 1
- 230000008859 change Effects 0.000 description 1
- 239000003795 chemical substances by application Substances 0.000 description 1
- 125000004122 cyclic group Chemical group 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 238000011161 development 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/50—Network services
- H04L67/56—Provisioning of proxy services
- H04L67/565—Conversion or adaptation of application format or content
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/02—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
-
- 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/50—Network services
- H04L67/55—Push-based network 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/50—Network services
- H04L67/56—Provisioning of proxy services
- H04L67/59—Providing operational support to end devices by off-loading in the network or by emulation, e.g. when they are unavailable
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The invention discloses a kind of method for interchanging data, this method executes in data interchange platform, including：The data exchange request that dispatch server is sent is received, customer ID and service name are parsed from data exchange request；According to the customer ID parsed, obtain interface network address, data output format information and the data exchange agreement of client server, data capture logic and interface method title are obtained according to the service name parsed, and is data exchange interface by interface network address and interface method name combination；The business datum of client server is obtained from data platform server according to the data capture logic got, and Data Format Transform is carried out to the business datum got according to the data output format information got；Using the data exchange agreement got, the business datum after Data Format Transform is pushed to the data exchange interface of client server.The invention also discloses a kind of data exchange system and data platform servers.
Description
Technical Field
The present invention relates to the field of data communications, and in particular, to a data exchange method, system, and data platform server.
Background
In some transactional websites, a data platform server needs to exchange data with client servers of multiple clients. For example, a user places an order on a certain automobile transaction website, and the website needs to summarize order data of each client (manufacturer) and send the summarized order data to a client server of the corresponding manufacturer, and accordingly, the client server also returns information such as the processing condition of the manufacturer on the order. The client servers of each manufacturer have different data interfaces, and the used data exchange protocols, the received data output formats and the like may be different.
For this reason, in the prior art, a single-protocol service type data exchange platform is generally adopted to realize data exchange with a client server. By "single protocol" is meant that the data exchange protocol with a certain client server is fixed; by "service type" is meant that one service corresponds to one client and one service needs to be developed for each client. The data exchange platform realizes data exchange between a server and a client by using webservices, and generates an agent class proxylent at the client through a webservices tool to access services provided by the server.
And at the server, realizing cyclic data exchange through the windows timing task, for example, calling a service every 5 minutes by the windows timing task, performing data exchange between the client program and the server through the webservices protocol until the data exchange is finished, disconnecting the server and the client, and waiting for the next scheduling after 5 minutes.
The prior art has the following disadvantages:
(1) since the proxy class of Webservcies is generated by the tool before the program is compiled, it is difficult to change the program once it is compiled, unless it is recompiled.
(2) New services need to be redeveloped and deployed for different customers, increasing development and maintenance costs.
(3) The windows timing task scheduler can bring single point of service deployment, if the machine for deploying the service is abnormal and cannot be accessed or started, almost no other scheme except restarting the computer is available, and the method is unacceptable for the service requiring 7 x 24.
Disclosure of Invention
In view of the above, the present invention has been made to provide a data exchange method, system and data platform server that overcome the above problems or at least partially solve the above problems.
According to one aspect of the invention, a data exchange method is provided, which is executed in a data platform server, wherein the data platform server can exchange data with a client server under the scheduling of a scheduling server; the data platform server stores the client identification and the associated configuration information, the service name and the associated data acquisition logic; the configuration information comprises an interface network address of the client server, data output format information, a data exchange protocol, a service name and a related interface method name; the data exchange method comprises the following steps: receiving a data exchange request sent by a scheduling server, and analyzing a client identifier and a service name from the data exchange request; acquiring an interface network address, data output format information and a data exchange protocol of a client server according to the analyzed client identifier, acquiring data acquisition logic and an interface method name according to the analyzed service name, and combining the interface network address and the interface method name into a data exchange interface; acquiring service data of a client server from a data platform server according to the acquired data acquisition logic, and performing data format conversion on the acquired service data according to the acquired data output format information; and pushing the service data after the data format conversion to the data exchange interface of the client server by adopting the acquired data exchange protocol.
Optionally, in the data exchange method according to the present invention, the configuration information further includes a data platform identifier and associated authentication code information; the data exchange method further comprises the following steps: and the data platform server sends the data platform identification and the authentication code information to the client server so that the client server can carry out identity verification on the data platform server.
Optionally, the data exchange method according to the present invention further includes: and acquiring response data of the client server from the data exchange interface.
Optionally, in the data exchange method according to the present invention, the data exchange protocol includes: webservices protocol and http protocol.
Optionally, in the data exchange method according to the present invention, the client identifier and the associated configuration information are stored in a data table manner or in a JSON format in the data platform server.
According to another aspect of the present invention, there is provided a data platform server, communicatively connected to a scheduling server and a client server, capable of exchanging data with the client server under the scheduling of the scheduling server, the data platform server comprising: a storage unit adapted to store a customer identification and associated configuration information, as well as a service name and associated data collection logic; the configuration information comprises an interface network address of the client server, data output format information, a data exchange protocol, a service name and a related interface method name; the receiving unit is suitable for receiving a data exchange request sent by the scheduling server and analyzing a client identifier and a service name from the data exchange request; the processing unit is suitable for acquiring an interface network address, data output format information and a data exchange protocol of the client server according to the analyzed client identifier, acquiring a data acquisition logic and an interface method name according to the analyzed service name, and combining the interface network address and the interface method name into a data exchange interface; the acquisition unit is suitable for acquiring the service data of the client server from the data platform server according to the acquired data acquisition logic and performing data format conversion on the acquired service data according to the acquired data output format information; and the switching unit is suitable for pushing the service data after the data format conversion to the data switching interface of the client server by adopting the acquired data switching protocol.
According to a further aspect of the present invention, there is provided a data exchange system comprising a scheduling server and one or more of the above data platform servers, wherein the data platform server is communicatively connected to one or more client servers and is capable of exchanging data with the client servers under the scheduling of the scheduling server
According to the data exchange scheme, the requirement of new data docking is met through the configuration file, new docking clients or functions are added, only the configuration information of the clients needs to be added in the configuration file, and redevelopment, debugging and online are not needed. Compared with the prior art that new codes are developed to meet the requirement of new data docking, the cost of data docking is effectively reduced, and non-technical workers can complete data docking tasks through simple training.
Furthermore, through distributed deployment of the data platform servers, once one of the servers is found to be abnormal, the scheduling server can switch the service to the other server to operate, the influence of sudden abnormality of the single server is avoided, and the stability of the service is improved.
The foregoing description is only an overview of the technical solutions of the present invention, and the embodiments of the present invention are described below in order to make the technical means of the present invention more clearly understood and to make the above and other objects, features, and advantages of the present invention more clearly understandable.
Drawings
Various other advantages and benefits will become apparent to those of ordinary skill in the art upon reading the following detailed description of the preferred embodiments. The drawings are only for purposes of illustrating the preferred embodiments and are not to be construed as limiting the invention. Also, like reference numerals are used to refer to like parts throughout the drawings. In the drawings:
FIG. 1 shows a block diagram of a data exchange system according to one embodiment of the present invention;
FIG. 2 shows a flow diagram of a data exchange method according to one embodiment of the invention; and
FIG. 3 shows a block diagram of a data platform server according to one embodiment of the present invention.
Detailed Description
Exemplary embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. While exemplary embodiments of the present disclosure are shown in the drawings, it should be understood that the present disclosure may be embodied in various forms and should not be limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the disclosure to those skilled in the art.
Fig. 1 shows a block diagram of a data exchange system according to one embodiment of the invention. Referring to fig. 1, the data exchange system includes a scheduling server and one or more data platform servers, wherein the data platform servers are communicatively connected to one or more client servers and can exchange data with the client servers under the scheduling of the scheduling server.
In the embodiment of the invention, distributed deployment can be realized by deploying a plurality of data platform servers, and each data platform server is independent. The data platform server 1 and the data platform server 2 and the other data platform servers may all do the same task, and any one data platform server may be replaced by another data platform server. For example, if the data platform server 1 is abnormal, the scheduling server may select the data platform server 2 to complete the task instead. In addition, the deployment location of the data platform server can be any region, so that the 7 x 24 hour service capacity is guaranteed.
In an embodiment of the present invention, a data platform server stores therein a client identifier and associated configuration information, as well as a service name and associated data collection logic. The configuration information includes the interface network address of the client server, data output format information, data exchange protocol, and service name and associated interface method name. Further, the configuration information may further include a data platform identifier and associated authentication code information. Wherein, the information can be stored in each data platform server.
The information, such as the client identification and associated configuration information, is stored in the data platform server in a data table manner or in a JSON format. For example, the following data table is stored in the data platform server:
InterfaceConnectInfo (partner Table)
| Column name | Type (B) | Description of the invention |
| ID | Int | Self-adding column unique identifier |
| TargetType | Varchar(10) | Partner vendor id |
| TargetName | Nvarchar(50) | Partner vendor name |
TABLE 1
| ID | TargetType | TargetName |
| 1 | 0x1423b11f | Qichen (Chinese character of 'Qi' -shaped tablet) |
| 2 | 0xfd4124df | Guangdong notebook |
TABLE 2
Table 2 is a detailed content of table 1, where TargetType is a client identifier (partner id), and the partner id of the broad book is 0xfd4124df, for example.
InterfaceServiceConfig (manufacturer interface service configuration table)
| Column name | Type (B) | Description of the invention |
| ID | Int | Self-adding column unique identifier |
| ServiceUrl | Varchar(100) | Vendor interface network address |
| TargetType | Varchar(10) | Partner vendor id |
| MediaId | Varchar(50) | Collaborative media id |
| Token | Varchar(50) | Manufacturer-supplied encrypted token |
TABLE 3
TABLE 4
Table 4 is the specific content of table 3, where the network address of the ServiceUrl vendor interface, the MediaId is the unique identifier of the data platform server in the vendor system (i.e. the data platform identifier), and the Token authentication code is the identifier for the vendor to verify whether the data platform server is authorized to access the client server of the vendor.
(III) InterfaceServiceDetailConfig (manufacturer detailed service configuration Table)
| Column name | Type (B) | Description of the invention |
| ID | Int | Self-adding column unique identifier |
| OutputValue | Varchar(500) | Formatting the final output |
| OutputFormat | Varchar(1000) | Format of output content |
| MethodName | Varchar(50) | Manufacturer side interface method name |
| FunctionEnName | Varchar(50) | English name of method |
| TargetType | Varchar(10) | Manufacturer identification |
TABLE 5
TABLE 6
Table 6 is the specific contents of table 5, and is used to describe the data format pushed to the vendor server and the interface name provided by the vendor, and generate an accessible address (data interface) depending on the combination of the ServiceUrl field of the vendor interface service configuration table and the MethodName, for example:
http://10.10.10.120:8100/interface/SendCommonLeads
the OutputValue and OutputFormat are output data format information, and are formatting of output parameters, for example, the GENDER attribute of the original data in the data platform server is 0 or 1, and the client server needs to be male or female, so that the data platform server will replace the attribute GENDER of 0 to male and 1 to female before pushing the data to the client server.
Fig. 2 shows a flow diagram of a data exchange method according to an embodiment of the invention. The data exchange method is performed in the data platform server shown in fig. 1. Referring to fig. 2, the data exchange method starts at step S202.
In step S202, the data platform server receives the data exchange request sent by the scheduling server, and parses the client identifier and the service name from the data exchange request. The data platform server can provide a service entrance in an http form, and by deploying an IIS (Internet Information Services) on Windows and then establishing a Web site on the IIS, the data platform server provides an interface for the scheduling server to perform service scheduling in the form of the Web site. Specific IIS scheduling may refer to microsoft related documentation.
When a certain client server needs to exchange data with a data platform server, a scheduling server selects one data platform server from a plurality of data platform servers, and sends a data exchange request (http request) to the data platform server in an http mode, wherein the http request carries a client identifier and a service name. The client server corresponding to the client identifier is a client server with which the data platform server needs to exchange data; the data platform server can provide different types of data exchange services, for example, order service, vehicle type service, vehicle series service, general service, and the like, each data exchange service corresponds to different data acquisition logics, and each data acquisition logic can acquire corresponding service data in the data platform server and send the service data to the client server.
For example, if the service name is Order, the representative needs to send Order data, and the data collection logic (service logic) corresponding to the service name is to collect Order data. One service logic can be used by multiple merchants (corresponding to multiple customer servers) together, and only the order data of corresponding customers are collected according to different customer identifications.
The data platform server monitors a data exchange request (http request) in the network, and in the embodiment of the invention, the format of parameters transmitted by the http request is as follows:
{ "actionType": trigger "," executorald ": number", "logId": number "," method ": autohome.Cooperator.Server.WebAPI. vendor name.service name", "param": cooperation id "};
for example:
{"actionType":"trigger","executorId":110,"logId":1000,"method":"AutoHome.Cooperator.Server.WebAPI.Kia.Order","param":"0xfd4124df"}；
wherein,
actionType: the name of a scheduler triggering service in a scheduling server, trigger is the triggering service, and stop is the stopping service;
execlutorId: identification id for scheduling service to execute the service
logic: scheduling service to execute log id of this service
A method: service method name provided by data exchange platform
param: the parameters passed in by the scheduling service, vendor Cooperation id (i.e., customer identification)
The data platform server may parse out the customer identification and the service name, which in this example is denoted as "0 xfd4124 df", the service name is "Order", i.e., Order service.
In step S204, the data platform server obtains the interface network address, the data output format information, and the data exchange protocol of the client server according to the parsed client identifier, obtains the data acquisition logic and the interface method name according to the parsed service name, and combines the interface network address and the interface method name into the data exchange interface.
As previously described, the data platform server has stored therein a customer identification and associated configuration information, as well as a service name and associated data collection logic. In the embodiment of the invention, each client has a unique client identifier, and each client identifier corresponds to one piece of configuration information. The configuration information includes the interface network address of the client server, data output format information, data exchange protocol, and service name and associated interface method name (for a certain client server, different service names correspond to different interface method names). Wherein the client server can accept a plurality of data exchange services and the client server provides different interface method names for different data exchange services.
In addition, the data platform server can provide different kinds of data exchange services, and each kind of data exchange service corresponds to different data acquisition logics. Therefore, the data platform server also stores the corresponding relationship between the service name and the data acquisition logic, that is, different service names correspond to different data acquisition logics. In particular, the data collection logic may be implemented in computer code, e.g., as a class (class) in a programming-oriented language.
Thus, the data platform server can obtain corresponding configuration information according to the analyzed client identifier, wherein the configuration information comprises an interface network address, data output format information and a data exchange protocol; according to the analyzed service name, data acquisition logic can be acquired; according to the client identification and the service name, the interface method name of the client server can be obtained. Thus, the data exchange interface of the client server can be obtained by combining the interface network address and the interface method name. In this example, the interface network address of the client server is: http://10.10.10.120: 8100/interface/; the interface method name is: sendcommonleads, which are combined to obtain a data exchange interface for the client server to receive order service: http://10.10.10.120: 8100/interface/SendcommonLeads.
In step S206, the data platform server obtains the service data of the client server from the data platform server according to the obtained data acquisition logic, and performs data format conversion on the obtained service data according to the obtained data output format information. As mentioned above, the data platform server may provide different types of data exchange services, for example, order service, vehicle type service, vehicle series service, general service, etc., each data exchange service corresponds to different data acquisition logics, and each data acquisition logic may acquire corresponding service data in the data platform server and send the service data to the client server. Before the service data is sent to the client server, the data format conversion should be performed to convert the service data into the data format required by the client server, and the conversion method can be obtained from the configuration information (data output format information) of the client.
In step S208, the data platform server uses the acquired data exchange protocol to push the service data after data format conversion to the data exchange interface of the client server. The data exchange protocol may be webservices protocol or http protocol. According to the embodiment of the invention, the data exchange protocol can be easily switched in the data exchange process, and the data platform server can automatically switch to the corresponding protocol for data exchange as long as the protocol type is modified in the configuration information, so that the cost of system maintenance caused by protocol switching is reduced.
For example, if the adopted data exchange protocol is webservices protocol, a webservices proxy class is first generated through serviceUrl, and information in the configuration information is called through reflection, and exemplary codes are as follows:
var instance＝Activator.CreateInstance(proxyClassType)；
var methodinfo＝proxyClassType.GetMethod("SendSeries")；
methodinfo.Invoke(instance,jsonData)；
the above code means that the proxy method of the client is acquired, and then the method is executed to push the vehicle series data to the client.
For example, if the data exchange protocol used is http protocol, it is necessary to push data to the address specified by url by using POST method of http protocol as follows.
For example: http://127.0.0.1:8081/MediaInterface/Service/Sendseries
According to another embodiment of the present invention, in the correspondence relationship between the client identifier and the configuration information stored in the data platform server, the configuration information further includes the data platform identifier and the associated authentication code information, so that, in step S208, before the data platform server performs data exchange with the client server, the data platform server further sends the data platform identifier and the authentication code information to the client server, and the client server performs identity verification on the data platform server according to the information sent by the data platform, the identity verification is passed, the data platform server is allowed to access the data exchange interface of the client server, the identity verification is not passed, and the data exchange interface of the data platform server client server is not allowed.
After receiving the pushed service data, the client server may send a message of successful reception to the data platform server. In addition, after the client server performs required processing according to the service data, the processing result can be returned to the data platform server, that is, the data platform server can also obtain the response data of the client server from the data exchange interface of the client server.
For example, the webservice will return true through the called function to confirm that the communication is successful, and exemplary codes are as follows:
var ret＝bmwServices.SendSeries(list)；
the ret is a return value, and whether the transmission is successful or not can be determined by judging whether the ret is true or not, wherein true is successful and false is failure.
http will judge whether the attribute status in the returned json is true to judge whether the sending is successful, true is successful, false is failure, and the exemplary code is as follows:
var ret＝HttpRequest.Post(list)；
ret＝{"status":"true"}
FIG. 3 shows a block diagram of a data platform server according to one embodiment of the present invention. The data platform server is in communication connection with the scheduling server and the client server and can exchange data with the client server under the scheduling of the scheduling server.
Referring to fig. 3, the data platform server includes a storage unit 310, a receiving unit 320, a processing unit 330, an obtaining unit 340 and a switching unit 350, and its operation principle is as follows:
the storage unit 310 stores therein the customer identification and associated configuration information, as well as the service name and associated data collection logic; the configuration information includes the interface network address of the client server, data output format information, data exchange protocol, and service name and associated interface method name. When a new docking client is added, the configuration information of the client may be added and stored in the storage unit 310; alternatively, when an existing client needs to add a new docking function, the configuration information of the client stored in the storage unit 310 may also be modified.
The receiving unit 320 receives the data exchange request sent by the scheduling server, and parses the client identifier and the service name from the data exchange request.
The processing unit 330 obtains the interface network address, the data output format information and the data exchange protocol of the client server from the storage unit 310 according to the parsed client identifier, obtains the data acquisition logic and the interface method name from the storage unit 310 according to the parsed service name, and combines the interface network address and the interface method name into the data exchange interface.
The obtaining unit 340 obtains the service data of the client server from the data platform server according to the obtained data acquisition logic, and performs data format conversion on the obtained service data according to the obtained data output format information.
The switching unit 350 uses the obtained data exchange protocol to push the service data after data format conversion to the data exchange interface of the client server. Wherein the data exchange protocol can be webservices protocol and http protocol. In addition, the configuration information may further include a data platform identifier and associated authentication code information, and accordingly, the switching unit 350 further sends the data platform identifier and the authentication code information to the client server, so that the client server performs identity verification on the data platform server.
Further, the switching unit 350 may also obtain response data of the client server from the data exchange interface of the client server.
According to the data exchange scheme of the embodiment of the invention, the requirement of new data docking is completed through the configuration file, new docking clients or functions are added, only the configuration information of the clients needs to be added in the configuration file, and redevelopment, debugging and online are not needed. Compared with the prior art that new codes are developed to meet the requirement of new data docking, the cost of data docking is effectively reduced, and non-technical workers can complete data docking tasks through simple training.
By the distributed deployment of the data platform servers, once one of the servers is found to be abnormal, the scheduling server can switch the service to the other server to operate, the influence of the sudden abnormality of the single server is avoided, and the stability of the service is improved.
The algorithms and displays presented herein are not inherently related to any particular computer, virtual machine, or other apparatus. Various general purpose systems may also be used with the teachings herein. The required structure for constructing such a system will be apparent from the description above. Moreover, the present invention is not directed to any particular programming language. It is appreciated that a variety of programming languages may be used to implement the teachings of the present invention as described herein, and any descriptions of specific languages are provided above to disclose the best mode of the invention.
In the description provided herein, numerous specific details are set forth. It is understood, however, that embodiments of the invention may be practiced without these specific details. In some instances, well-known methods, structures and techniques have not been shown in detail in order not to obscure an understanding of this description.
Similarly, it should be appreciated that in the foregoing description of exemplary embodiments of the invention, various features of the invention are sometimes grouped together in a single embodiment, figure, or description thereof for the purpose of streamlining the disclosure and aiding in the understanding of one or more of the various inventive aspects. However, the disclosed method should not be interpreted as reflecting an intention that: that the invention as claimed requires more features than are expressly recited in each claim. Rather, as the following claims reflect, inventive aspects lie in less than all features of a single foregoing disclosed embodiment. Thus, the claims following the detailed description are hereby expressly incorporated into this detailed description, with each claim standing on its own as a separate embodiment of this invention.
Those skilled in the art will appreciate that the modules in the device in an embodiment may be adaptively changed and disposed in one or more devices different from the embodiment. The modules or units or components of the embodiments may be combined into one module or unit or component, and furthermore they may be divided into a plurality of sub-modules or sub-units or sub-components. All of the features disclosed in this specification (including any accompanying claims, abstract and drawings), and all of the processes or elements of any method or apparatus so disclosed, may be combined in any combination, except combinations where at least some of such features and/or processes or elements are mutually exclusive. Each feature disclosed in this specification (including any accompanying claims, abstract and drawings) may be replaced by alternative features serving the same, equivalent or similar purpose, unless expressly stated otherwise.
Furthermore, those skilled in the art will appreciate that while some embodiments described herein include some features included in other embodiments, rather than other features, combinations of features of different embodiments are meant to be within the scope of the invention and form different embodiments. For example, in the following claims, any of the claimed embodiments may be used in any combination.
The various component embodiments of the invention may be implemented in hardware, or in software modules running on one or more processors, or in a combination thereof. Those skilled in the art will appreciate that a microprocessor or Digital Signal Processor (DSP) may be used in practice to implement some or all of the functions of some or all of the components in a data platform server according to embodiments of the present invention. The present invention may also be embodied as apparatus or device programs (e.g., computer programs and computer program products) for performing a portion or all of the methods described herein. Such programs implementing the present invention may be stored on computer-readable media or may be in the form of one or more signals. Such a signal may be downloaded from an internet website or provided on a carrier signal or in any other form.
It should be noted that the above-mentioned embodiments illustrate rather than limit the invention, and that those skilled in the art will be able to design alternative embodiments without departing from the scope of the appended claims. In the claims, any reference signs placed between parentheses shall not be construed as limiting the claim. The word "comprising" does not exclude the presence of elements or steps not listed in a claim. The word "a" or "an" preceding an element does not exclude the presence of a plurality of such elements. The invention may be implemented by means of hardware comprising several distinct elements, and by means of a suitably programmed computer. In the unit claims enumerating several means, several of these means may be embodied by one and the same item of hardware. The usage of the words first, second and third, etcetera do not indicate any ordering. These words may be interpreted as names.
Claims (10)
1. A data exchange method is executed in a data platform server, the data platform server can exchange data with a client server under the scheduling of a scheduling server, wherein the data platform server provides different types of data exchange services, each type of data exchange service corresponds to different data acquisition logics, and each type of data acquisition logic can acquire corresponding service data in the data platform server and send the service data to the client server; the data platform server stores the client identification and the associated configuration information, the service name and the associated data acquisition logic; the configuration information comprises an interface network address of the client server, data output format information, a data exchange protocol, a service name and a related interface method name; the data exchange method comprises the following steps:
receiving a data exchange request sent by a scheduling server, and analyzing a client identifier and a service name from the data exchange request;
acquiring an interface network address, data output format information and a data exchange protocol of a client server according to the analyzed client identifier, acquiring data acquisition logic and an interface method name according to the analyzed service name, and combining the interface network address and the interface method name into a data exchange interface;
acquiring service data of a client server from a data platform server according to the acquired data acquisition logic, and performing data format conversion on the acquired service data according to the acquired data output format information; and
and pushing the service data after the data format conversion to the data exchange interface of the client server by adopting the acquired data exchange protocol.
2. The data exchange method of claim 1, wherein the configuration information further includes data platform identification and associated authentication code information;
the data exchange method further comprises the following steps: and the data platform server sends the data platform identification and the authentication code information to the client server so that the client server can carry out identity verification on the data platform server.
3. The data exchange method according to claim 1 or 2, further comprising: and acquiring response data of the client server from the data exchange interface.
4. The data exchange method of claim 1, wherein the data exchange protocol comprises: webservices protocol and http protocol.
5. The data exchange method of claim 1, wherein the client identification and associated configuration information are stored in a data table manner or in a JSON format in a data platform server.
6. A data platform server, with dispatch server and customer server communication connection, can carry on the data interchange with the customer server under the dispatch of the dispatch server, wherein the data platform server provides the data exchange service of different kinds, each kind of data exchange service corresponds to different data acquisition logics, each kind of data acquisition logics will gather the corresponding business datum in the data platform server and send to the customer server, the data platform server includes:
a storage unit adapted to store a customer identification and associated configuration information, as well as a service name and associated data collection logic; the configuration information comprises an interface network address of the client server, data output format information, a data exchange protocol, a service name and a related interface method name;
the receiving unit is suitable for receiving a data exchange request sent by the scheduling server and analyzing a client identifier and a service name from the data exchange request;
the processing unit is suitable for acquiring an interface network address, data output format information and a data exchange protocol of the client server according to the analyzed client identifier, acquiring a data acquisition logic and an interface method name according to the analyzed service name, and combining the interface network address and the interface method name into a data exchange interface;
the acquisition unit is suitable for acquiring the service data of the client server from the data platform server according to the acquired data acquisition logic and performing data format conversion on the acquired service data according to the acquired data output format information; and
and the switching unit is suitable for pushing the service data after the data format conversion to the data switching interface of the client server by adopting the acquired data switching protocol.
7. The data platform server of claim 6, wherein the configuration information further includes data platform identification and associated authentication code information;
the switching unit is further adapted to: and sending the data platform identification and the authentication code information to the client server so that the client server can carry out identity verification on the data platform server.
8. The data platform server of claim 6 or 7, wherein the switching unit is further adapted to: and acquiring response data of the client server from the data exchange interface.
9. The data platform server of claim 6, wherein the data exchange protocol comprises: webservices protocol and http protocol.
10. A data exchange system comprising a dispatch server and one or more data platform servers as claimed in any one of claims 6 to 9, wherein the data platform servers are communicatively connected to one or more client servers and are capable of exchanging data with the client servers under the dispatch of the dispatch server.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201510792194.8A CN105471968B (en) | 2015-11-17 | 2015-11-17 | A kind of method for interchanging data, system and data platform server |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201510792194.8A CN105471968B (en) | 2015-11-17 | 2015-11-17 | A kind of method for interchanging data, system and data platform server |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN105471968A CN105471968A (en) | 2016-04-06 |
| CN105471968B true CN105471968B (en) | 2018-09-21 |
Family
ID=55609231
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201510792194.8A Active CN105471968B (en) | 2015-11-17 | 2015-11-17 | A kind of method for interchanging data, system and data platform server |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN105471968B (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110321380A (en) * | 2019-07-09 | 2019-10-11 | 北京外研讯飞教育科技有限公司 | A kind of method for interchanging data, apparatus and system |
Families Citing this family (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105897783B (en) * | 2016-07-01 | 2018-11-27 | 中国联合网络通信有限公司重庆市分公司 | It is a kind of controllably can pipe sensitive data switching technology implementation method |
| CN106850596B (en) * | 2017-01-16 | 2020-08-04 | 北京市天元网络技术股份有限公司 | Data acquisition system and method |
| CN107729345B (en) * | 2017-07-27 | 2020-08-18 | 深圳壹账通智能科技有限公司 | Website data processing method and device, website data processing platform and storage medium |
| CN109063040B (en) * | 2018-07-17 | 2020-07-07 | 清华大学 | Client program data acquisition method and system |
| CN109639763B (en) * | 2018-11-12 | 2021-06-08 | 武汉虹信技术服务有限责任公司 | Remote centralized acquisition system and method for identity card information |
| CN111031029A (en) * | 2019-12-09 | 2020-04-17 | 广东电网有限责任公司 | Work order and power failure data interaction device supporting multi-protocol conversion |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1437810A (en) * | 2000-03-10 | 2003-08-20 | 黎明网络有限公司 | An information switch |
| CN101631093A (en) * | 2009-08-28 | 2010-01-20 | 中国电信股份有限公司 | Method and system for realizing real-time data exchange interface |
| CN104320396A (en) * | 2014-10-28 | 2015-01-28 | 用友优普信息技术有限公司 | Data interaction device and method |
| CN104967650A (en) * | 2015-02-06 | 2015-10-07 | 北京海涛国际旅行社有限公司 | Third-party e-commerce platform unified releasing method |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US8959188B2 (en) * | 2008-10-01 | 2015-02-17 | Nokia Corporation | Method, system, and apparatus for configuring network accounts on devices for use therewith |
-
2015
- 2015-11-17 CN CN201510792194.8A patent/CN105471968B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1437810A (en) * | 2000-03-10 | 2003-08-20 | 黎明网络有限公司 | An information switch |
| CN101631093A (en) * | 2009-08-28 | 2010-01-20 | 中国电信股份有限公司 | Method and system for realizing real-time data exchange interface |
| CN104320396A (en) * | 2014-10-28 | 2015-01-28 | 用友优普信息技术有限公司 | Data interaction device and method |
| CN104967650A (en) * | 2015-02-06 | 2015-10-07 | 北京海涛国际旅行社有限公司 | Third-party e-commerce platform unified releasing method |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110321380A (en) * | 2019-07-09 | 2019-10-11 | 北京外研讯飞教育科技有限公司 | A kind of method for interchanging data, apparatus and system |
Also Published As
| Publication number | Publication date |
|---|---|
| CN105471968A (en) | 2016-04-06 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN105471968B (en) | A kind of method for interchanging data, system and data platform server | |
| CN104580406B (en) | A kind of method and apparatus of synchronous logging state | |
| CN103001815B (en) | The acquisition methods of test data, Apparatus and system | |
| CN107920094B (en) | Data acquisition method and device, server and network equipment | |
| CN105610819B (en) | The method and apparatus of the query service of server info are provided | |
| CN110377590B (en) | Data acquisition system and method based on Internet of things and computer readable storage medium | |
| CN104980421B (en) | Batch request processing method and system | |
| CN111737270A (en) | Data processing method and system, computer system and computer readable medium | |
| CN106056437A (en) | Order management method and system | |
| CN108173839B (en) | Authority management method and system | |
| US10009220B2 (en) | In-vehicle information system and information processing method thereof | |
| CN104753909A (en) | Updated information authentication method, device and system | |
| CN116523457A (en) | Workflow processing method, device, equipment and storage medium based on business process | |
| CN105955838A (en) | System halt reason check method and device | |
| CN109862074B (en) | Data acquisition method and device, readable medium and electronic equipment | |
| CN113691618B (en) | Message notification method, device, message center and storage medium | |
| CN113542416B (en) | Message receiving and sending method and device | |
| CN115951923B (en) | Subscription event management method, display system, device and storage medium | |
| CN111447273A (en) | Cloud processing system and data processing method based on cloud processing system | |
| CN116776912A (en) | Store detection processing method, device, system and computing equipment | |
| CN110881030A (en) | Logstack-based method and device for recording operation logs of web service administrator | |
| CN110875832A (en) | Abnormal service monitoring method, device and system and computer readable storage medium | |
| CN114968822A (en) | Interface testing method and device, computer equipment and storage medium | |
| CN112559278B (en) | Method and device for acquiring operation data | |
| CN112487323A (en) | Webpage experimental method and server |
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 |