CN115225476B - Transmission method and device based on SOA architecture integrated deployment - Google Patents
Transmission method and device based on SOA architecture integrated deployment Download PDFInfo
- Publication number
- CN115225476B CN115225476B CN202210807671.3A CN202210807671A CN115225476B CN 115225476 B CN115225476 B CN 115225476B CN 202210807671 A CN202210807671 A CN 202210807671A CN 115225476 B CN115225476 B CN 115225476B
- Authority
- CN
- China
- Prior art keywords
- data
- context
- interface
- resturl
- servicecode
- 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
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/10—Protocols in which an application is distributed across nodes in the network
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/0876—Aspects of the degree of configuration automation
- H04L41/0879—Manual configuration through operator
-
- 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/2866—Architectures; Arrangements
- H04L67/30—Profiles
- H04L67/306—User profiles
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D30/00—Reducing energy consumption in communication networks
- Y02D30/50—Reducing energy consumption in communication networks in wire-line communication networks, e.g. low power modes or reduced link rate
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Automation & Control Theory (AREA)
- Communication Control (AREA)
- Information Transfer Between Computers (AREA)
Abstract
The invention relates to the technical field of information, and provides a transmission method and device based on SOA architecture integrated deployment. The method aims to solve the problem of lateral expansion of one-to-one protocol in the integrated deployment-distributed deployment process. The method comprises the steps of managing the RestUrl and the RestOperationType of the Servicecode, configuring the RestUrl and the RestOperationType into a serviceUrl. Properties file directly through manual operation, then analyzing the file, reading data of the serviceUrl. Properties file, and inputting the data into a context ContextConstants; the information stored in the context ContextConstants is taken out from the context ContextConstants, the obtained Servicecode is stored in the httpBody, the RestUrl is stored in the httpHead, and the stored httpHead and httpBody data are sent to the appointed address through the means of the Restful protocol.
Description
Technical Field
The invention relates to the technical field of information, and provides a transmission method and device based on SOA architecture integrated deployment.
Background
SOA, service OrientedArchitecture (service oriented architecture), deployment, combination and use of services are performed by applying the loosely coupled coarse strength to the network according to requirements. The service layer is the basis of the SOA and can be directly called by the application, so that the artificial dependence of interaction with software in the system is effectively controlled.
In terms of an SOA integrated deployment architecture, front-end service-protocol-back-end service is deployed in a one-to-one protocol transport architecture during deployment.
In terms of the distributed deployment architecture, each newly added service is newly added with a new URL address.
The distributed service which is expanded by the integrated deployment architecture based on the single address can only be bound by a single protocol, and the problem of the lateral expansion of the protocol can occur, namely, a back-end distributed service is added, and the application of the integrated architecture needs to be bound by adding a new protocol.
In the aspect of data transmission, the Restful protocol is expanded by the HTTP protocol, and the request mode is directly contained in the HttpHead of the protocol so as to be convenient for the processing of a server, thereby simplifying the data transmission mode.
Therefore, all interfaces needing a pair of multiple modes are managed and configured in a file configuration mode, and the existing protocol is replaced by a Restful protocol, so that only one Restful protocol can be established, and the problem of one-to-one protocol lateral expansion of integrated service access distributed service under an SOA architecture is solved.
Disclosure of Invention
The invention aims to solve the problem of transverse expansion of one-to-one protocol in the integrated deployment-distributed deployment process. From the viewpoint of implementation, the invention can realize the one-to-one mode instead of the one-to-many mode by overcoming three problems of configuration management of multiple URL addresses, reading URL configuration entry context transmission and Restful protocol data transmission.
In order to realize the technical scheme, the invention adopts the following technical means:
a transmission method based on SOA architecture integrated deployment comprises the following steps:
step 1, managing an integrated-distributed interface by means of manual management configuration, configuring interface code data ServiceCode, interface address data RestUrl and interface request mode data RestOperationType of the interface into a serviceUrl.properties file directly through manual operation, then analyzing the file, reading data of the serviceUrl.properties file to obtain interface ServiceCode, an interface transmission address RestUrl and an interface transmission mode RestOperationType, obtaining corresponding final data, storing the final data into a context ContextConstants, namely storing obtained values corresponding to ServiceCode, restUrl and RestOperationType into the context ContextConstant;
and 2, taking out the information stored in the context ContextConstants from the context ContextConstants, storing the final data of the obtained ServiceNode into the HttpBody of the Restful protocol, storing the final data of the obtained restUrl into the httphole of the Restful protocol as a transmitted designated address, and transmitting the stored httphole and HttpBody data to the designated address by means of the Restful protocol.
In the above technical solution, step 1 specifically includes the following steps:
step 1.1, independently establishing a configuration file serviceUrl.
Step 1.2, manually managing the interfaces, and manually using ServiceCode: the form of RestUrl+RestOperationType is configured into a serviceUrl. Prproperties file;
step 1.3, reading configuration files serviceUrl.properties, storing a service interface ServiceCode into a context ContextConstans, and carrying out context identification and transmission in the whole flow by the ServiceCode in the context;
step 1.4, reading configuration files serviceUrl.properties, storing the RestUrl information of a service interface ServiceCode into a context ContextConstants, and carrying out context identification in the context by using the RestUrl and transmitting the information in the whole flow;
step 1.5, reading configuration files, serviceUrl.properties, storing the RestOperationType of the service interface ServiceCode into the context ContextConstants, carrying out context identification by using the RestOperationType and transmitting in the whole flow, wherein the RestOperationType defaults to be post.
In the above technical solution, step 2 specifically includes the following steps:
step 2.1, establishing a Restful protocol through codes, and preparing a protocol transmission data flow;
step 2.2, obtaining corresponding final data from the context ContextConstants through Servicecode, restUrl and RestOperationType information;
step 2.3, storing the final data of the obtained ServiceNode into HttpBody of the Restful protocol to prepare for data transmission;
step 2.4, storing the obtained final data of the RestUrl as a transmitted designated address into a Restful protocol httpHead, and preparing for data transmission;
step 2.5, judging the obtained RestOperationType final data, judging whether the data are post, get, delete, put, if not, returning an exception and not sending the data, if so, storing the data in httpHead as a specified request mode of a protocol, and preparing for data transmission;
and 2.6, carrying out data transmission on the stored HttpHead and HttpBody data through a link method of an HTTP request server in a Restful protocol, and then waiting for data return by the Restful protocol.
And 2.7, ending the data transmission flow of the protocol.
The invention also provides a transmission device based on SOA architecture integrated deployment, which comprises:
and (3) a configuration module: the method comprises the steps of managing an integrated-distributed interface through a manual management configuration means, configuring interface code data ServiceCode, interface address data RestUrl and interface request mode data RestOperationType of the interface into a serviceUrl. Properties file directly through manual operation, then analyzing the file, reading data of the serviceUrl. Properties file, obtaining the interface ServiceCode, an interface transmission address RestUrl and an interface transmission mode RestOperationType, obtaining corresponding final data, and storing the final data into a context ContextConstants;
and an analysis module: the information stored in the context ContextConstants is taken out from the context ContextConstants, the final data of the obtained ServiceNode is stored in the HttpBody of the Restful protocol, the final data of the obtained restUrl is stored in the Restful protocol httpHead as a sending designated address, and the stored HttpBody and HttpBody data are sent to the designated address by means of the Restful protocol.
In the above technical solution, the implementation of the configuration module specifically includes the following steps:
step 1.1, independently establishing a configuration file serviceUrl.
Step 1.2, manually managing the interfaces, and manually using ServiceCode: the form of RestUrl+RestOperationType is configured into a serviceUrl. Prproperties file;
step 1.3, reading configuration files serviceUrl.properties, storing a service interface ServiceCode into a context ContextConstans, and carrying out context identification and transmission in the whole flow by the ServiceCode in the context;
step 1.4, reading configuration files serviceUrl.properties, storing the RestUrl information of a service interface ServiceCode into a context ContextConstants, and carrying out context identification in the context by using the RestUrl and transmitting the information in the whole flow;
step 1.5, reading configuration files, serviceUrl.properties, storing the RestOperationType of the service interface ServiceCode into the context ContextConstants, carrying out context identification by using the RestOperationType and transmitting in the whole flow, wherein the RestOperationType defaults to be post.
In the above technical solution, the implementation of the parsing module specifically includes the following steps:
step 2.1, establishing a Restful protocol through codes, and preparing a protocol transmission data flow;
step 2.2, obtaining corresponding final data from the context ContextConstants through Servicecode, restUrl and RestOperationType information;
step 2.3, storing the final data of the obtained ServiceNode into HttpBody of the Restful protocol to prepare for data transmission;
step 2.4, storing the obtained final data of the RestUrl as a transmitted designated address into a Restful protocol httpHead, and preparing for data transmission;
step 2.5, judging the obtained RestOperationType final data, judging whether the data are post, get, delete, put, if not, returning an exception and not sending the data, if so, storing the data in httpHead as a specified request mode of a protocol, and preparing for data transmission;
and 2.6, carrying out data transmission on the stored HttpHead and HttpBody data through a link method of an HTTP request server in a Restful protocol, and then waiting for data return by the Restful protocol.
And 2.7, ending the data transmission flow of the protocol.
Because the invention adopts the technical scheme, the invention has the following beneficial effects:
the protocol bottom layer of the Restful is defined as an HTTP protocol, and the Restful has the advantage of directly expanding an interface of a native HTTP protocol;
2. the interface transverse expansion difficulty of the integrated service request distribution service under the SOA architecture is reduced;
3. because post, get, delete, put parameters can be carried in the head defined by the Restful specification, the corresponding interface operation can be directly carried out by using the additional conditions, the subsequent post, get, delete, put operation and the like are simplified, and the method has the advantages that the complexity of the interface can be simplified by directly taking the carried parameters as data to be used as operations of clicking, acquiring, deleting and pushing;
4. the url and request method unique to the interface of the newly added serviceUrl/properties individual management interface is used for the configuration management of the transverse expansion interface-protocol-interface;
5. and a Restful protocol is introduced, and the interface carries out data transmission by using the Restful protocol, so that the problem of difficult transverse expansion of a common protocol transmission mode is solved.
Drawings
FIG. 1 is a flow chart of a configuration and parsing module
FIG. 2 is a flow chart of the Rest protocol data transmission
Detailed Description
Hereinafter, embodiments of the present invention will be described in detail. While the invention will be described and illustrated in conjunction with certain specific embodiments, it will be understood that it is not intended to limit the invention to these embodiments alone. On the contrary, the invention is intended to cover modifications and equivalent arrangements included within the scope of the appended claims.
In addition, numerous specific details are set forth in the following description in order to provide a better illustration of the invention. It will be understood by those skilled in the art that the present invention may be practiced without these specific details.
A transmission method based on SOA architecture integrated deployment comprises the following steps:
step 1, managing an integrated-distributed interface by means of manual management configuration, configuring interface code data ServiceCode, interface address data RestUrl and interface request mode data RestOperationType of the interface into a serviceUrl.properties file directly through manual operation, then analyzing the file, reading data of the serviceUrl.properties file to obtain interface ServiceCode, an interface transmission address RestUrl and an interface transmission mode RestOperationType, obtaining corresponding final data, storing the final data into a context ContextConstants, namely storing obtained values corresponding to ServiceCode, restUrl and RestOperationType into the context ContextConstant;
and 2, taking out the information stored in the context ContextConstants from the context ContextConstants, storing the final data of the obtained ServiceNode into the HttpBody of the Restful protocol, storing the final data of the obtained restUrl into the httphole of the Restful protocol as a transmitted designated address, and transmitting the stored httphole and HttpBody data to the designated address by means of the Restful protocol.
In the above technical solution, step 1 specifically includes the following steps:
step 1.1, independently establishing a configuration file serviceUrl.
Step 1.2, manually managing the interfaces, and manually using ServiceCode: the form of RestUrl+RestOperationType is configured into a serviceUrl. Prproperties file;
step 1.3, reading configuration files serviceUrl.properties, storing a service interface ServiceCode into a context ContextConstans, and carrying out context identification and transmission in the whole flow by the ServiceCode in the context;
step 1.4, reading configuration files serviceUrl.properties, storing the RestUrl information of a service interface ServiceCode into a context ContextConstants, and carrying out context identification in the context by using the RestUrl and transmitting the information in the whole flow;
step 1.5, reading configuration files, serviceUrl.properties, storing the RestOperationType of the service interface ServiceCode into the context ContextConstants, carrying out context identification by using the RestOperationType and transmitting in the whole flow, wherein the RestOperationType defaults to be post.
In the above technical solution, step 2 specifically includes the following steps:
step 2.1, establishing a Restful protocol through codes, and preparing a protocol transmission data flow;
step 2.2, obtaining corresponding final data from the context ContextConstants through Servicecode, restUrl and RestOperationType information;
step 2.3, storing the final data of the obtained ServiceNode into HttpBody of the Restful protocol to prepare for data transmission;
step 2.4, storing the obtained final data of the RestUrl as a transmitted designated address into a Restful protocol httpHead, and preparing for data transmission;
step 2.5, judging the obtained RestOperationType final data, judging whether the data are post, get, delete, put, if not, returning an exception and not sending the data, if so, storing the data in httpHead as a specified request mode of a protocol, and preparing for data transmission;
and 2.6, carrying out data transmission on the stored HttpHead and HttpBody data through a link method of an HTTP request server in a Restful protocol, and then waiting for data return by the Restful protocol.
And 2.7, ending the data transmission flow of the protocol.
The invention also provides a transmission device based on SOA architecture integrated deployment, which comprises:
and (3) a configuration module: the method comprises the steps of managing an integrated-distributed interface through a manual management configuration means, configuring interface code data ServiceCode, interface address data RestUrl and interface request mode data RestOperationType of the interface into a serviceUrl. Properties file directly through manual operation, then analyzing the file, reading data of the serviceUrl. Properties file, obtaining the interface ServiceCode, an interface transmission address RestUrl and an interface transmission mode RestOperationType, obtaining corresponding final data, and storing the final data into a context ContextConstants;
and an analysis module: the information stored in the context ContextConstants is taken out from the context ContextConstants, the final data of the obtained ServiceNode is stored in the HttpBody of the Restful protocol, the final data of the obtained restUrl is stored in the Restful protocol httpHead as a sending designated address, and the stored HttpBody and HttpBody data are sent to the designated address by means of the Restful protocol.
In the above technical solution, the implementation of the configuration module specifically includes the following steps:
step 1.1, independently establishing a configuration file serviceUrl.
Step 1.2, manually managing the interfaces, and manually using ServiceCode: the form of RestUrl+RestOperationType is configured into a serviceUrl. Prproperties file;
step 1.3, reading configuration files serviceUrl.properties, storing a service interface ServiceCode into a context ContextConstans, and carrying out context identification and transmission in the whole flow by the ServiceCode in the context;
step 1.4, reading configuration files serviceUrl.properties, storing the RestUrl information of a service interface ServiceCode into a context ContextConstants, and carrying out context identification in the context by using the RestUrl and transmitting the information in the whole flow;
step 1.5, reading configuration files, serviceUrl.properties, storing the RestOperationType of the service interface ServiceCode into the context ContextConstants, carrying out context identification by using the RestOperationType and transmitting in the whole flow, wherein the RestOperationType defaults to be post.
In the above technical solution, the implementation of the parsing module specifically includes the following steps:
step 2.1, establishing a Restful protocol through codes, and preparing a protocol transmission data flow;
step 2.2, obtaining corresponding final data from the context ContextConstants through Servicecode, restUrl and RestOperationType information;
step 2.3, storing the final data of the obtained ServiceNode into HttpBody of the Restful protocol to prepare for data transmission;
step 2.4, storing the obtained final data of the RestUrl as a transmitted designated address into a Restful protocol httpHead, and preparing for data transmission;
step 2.5, judging the obtained RestOperationType final data, judging whether the data are post, get, delete, put, if not, returning an exception and not sending the data, if so, storing the data in httpHead as a specified request mode of a protocol, and preparing for data transmission;
and 2.6, carrying out data transmission on the stored HttpHead and HttpBody data through a link method of an HTTP request server in a Restful protocol, and then waiting for data return by the Restful protocol.
And 2.7, ending the data transmission flow of the protocol.
The invention manages the RestUrl and RestOperationType of the Servicecode, and adds the serviceUrl. And finally, the configuration management of the transverse expansion interface-protocol-interface is realized by the mode of carrying out configuration management on the file.
And storing the obtained corresponding values of ServiceCode, restUrl and RestOperationType into the context ContextConstant by reading the configured serviceUrl.
And finally, the data is transmitted to the server by taking out from the context ContextConstat and storing the data into HttpHead and HttpBody of the Restful protocol.
Description of the preferred embodiments
The distributed providing interface addresses are respectively:
user newly added interface URL/insert UserData
User revision interface URL/updateUserData
User deletion interface URL/deleteUserData
The integrated application is deployed as follows
1. Managing the three interfaces;
1-1 management setting ServiceCode
The user newly added interface is UserInsert
User revision interface is UserUpdate
The user deletion interface is userdeete
1-2 management setting RestUrl
The user newly added interface is URL/insert UserData
User revising interface to URL/updateUserData
The user deleting interface is URL/deleteUserData
1-3 management setting RestOperationType
The user newly added interface can set the request mode as post
The user revision interface can set the request mode as put
The user deletion interface can set the request mode as delete
2. Configuration of interfaces after having been managed into serviceUrl
2-1 adding a serviceUrl. Properties (if there is a current serviceUrl. Properties file then directly adding, if there is no then adding)
2-2 arrange the above rules to configure interface data into serviceUrl. Properties file according to servicecode= "restUrl" + "restoperation type
New user interface
UserInsert=”URL/insertUserData”+”post”;
User revision interface
UserUpdate=”URL/updateUserData”+”put”;
User delete interface
UserDelete=”URL/deleteUserData”+”delete”;
3. The above procedure automatically reads ServiceCode, restUrl, restOperationType the final data into the context ContextConstants in the order of Servicecode= "RestUrl" + "RestOperationType";
4. application of automatically creating a Restful protocol for data transmission (and judging whether the current functional module has the Restful protocol or not, if not, creating the Restful protocol)
5. The above procedure automatically reads ServiceCode, restUrl, restOperationType of ContextConstants in the context
5-1, automatically storing the read Servicecode data into the HttpBody for transmission;
5-2, automatically storing the RestUrl data read by the computer into HttpHead to prepare for transmission;
5-3, automatically storing the RestOperationType data read in the HttpHead to prepare for transmission;
the restful protocol starts to request distributed services according to HTTP requests and waits for data to return according to httphole+httpbody data.
Claims (4)
1. The transmission method based on the SOA architecture integrated deployment is characterized by comprising the following steps:
step 1, managing an integrated-distributed interface by means of manual management configuration, configuring interface code data ServiceCode, interface address data RestUrl and interface request mode data RestOperationType of the interface into a serviceUrl.properties file directly through manual operation, then analyzing the file, reading data of the serviceUrl.properties file to obtain interface ServiceCode, an interface transmission address RestUrl and an interface transmission mode RestOperationType, obtaining corresponding final data, storing the final data into a context ContextConstants, namely storing obtained values corresponding to ServiceCode, restUrl and RestOperationType into the context ContextConstants;
step 2, the information stored in the context ContextConstants is taken out from the context ContextConstants, the final data of the obtained ServiceNode is stored in the HttpBody of the Restful protocol, the final data of the obtained restUrl is stored in the httphole of the Restful protocol as a transmitted appointed address, and the stored httphole and the HttpBbody data are transmitted to the appointed address by means of the Restful protocol;
the step 2 specifically comprises the following steps:
step 2.1, establishing a Restful protocol through codes, and preparing a protocol transmission data flow;
step 2.2, obtaining corresponding final data from the context ContextConstants through Servicecode, restUrl and RestOperationType information;
step 2.3, storing the final data of the obtained ServiceNode into HttpBody of the Restful protocol to prepare for data transmission;
step 2.4, storing the obtained final data of the RestUrl as a transmitted designated address into a Restful protocol httpHead, and preparing for data transmission;
step 2.5, judging the obtained RestOperationType final data, judging whether the data are post, get, delete, put, if not, returning an exception and not sending the data, if so, storing the data in httpHead as a specified request mode of a protocol, and preparing for data transmission;
step 2.6, the stored httphole and HttpBody data are transmitted through a link method of an HTTP request server in a Restful protocol, and then the Restful protocol waits for data return;
and 2.7, ending the data transmission flow of the protocol.
2. The transmission method based on the integrated deployment of the SOA architecture according to claim 1, wherein the step 1 specifically includes the following steps:
step 1.1, independently establishing a configuration file serviceUrl.
Step 1.2, manually managing the interfaces, and manually using ServiceCode: the form of RestUrl+RestOperationType is configured into a serviceUrl.
Step 1.3, reading configuration files serviceUrl.properties, storing a service interface ServiceCode into a context ContextConstants, and carrying out context identification and transmission in the whole flow by the ServiceCode in the context;
step 1.4, reading configuration files serviceUrl.properties, storing the RestUrl information of a service interface ServiceCode into a context ContextConstants, and carrying out context identification in the context by using the RestUrl and transmitting the information in the whole flow;
step 1.5, reading configuration files, serviceUrl.properties, storing the RestOperationType of the service interface ServiceCode into the context ContextConstants, carrying out context identification by using the RestOperationType and transmitting in the whole flow, wherein the RestOperationType defaults to be post.
3. An SOA architecture integrated deployment-based transmission device, comprising:
and (3) a configuration module: the method comprises the steps of managing an integrated-distributed interface through a manual management configuration means, configuring interface code data Servicecode, interface address data RestUrl and interface request mode data RestOperationType of the interface into a serviceUrl. Properties file directly through manual operation, then analyzing the file, reading data of the serviceUrl. Properties file, obtaining interface Servicecode, an interface transmission address RestUrl and an interface transmission mode RestOperationType, obtaining corresponding final data, storing the final data into a context ContextConstants, namely storing corresponding values of ServiceCode, restUrl and RestOperationType into the context ContextConstants;
and an analysis module: the method comprises the steps of taking information stored in a context ContextConstants out of the context ContextConstants, storing final data of the obtained ServiceNode into HttpBody of a Restful protocol, storing the final data of the obtained restUrl into a Restful protocol httpHead as a transmitted designated address, and transmitting the stored HttpHead and HttpBody data to the designated address by means of the Restful protocol;
the analysis module comprises the following steps:
step 2.1, establishing a Restful protocol through codes, and preparing a protocol transmission data flow;
step 2.2, obtaining corresponding final data from the context ContextConstants through Servicecode, restUrl and RestOperationType information;
step 2.3, storing the final data of the obtained ServiceNode into HttpBody of the Restful protocol to prepare for data transmission;
step 2.4, storing the obtained final data of the RestUrl as a transmitted designated address into a Restful protocol httpHead, and preparing for data transmission;
step 2.5, judging the obtained RestOperationType final data, judging whether the data are post, get, delete, put, if not, returning an exception and not sending the data, if so, storing the data in httpHead as a specified request mode of a protocol, and preparing for data transmission;
step 2.6, the stored httphole and HttpBody data are transmitted through a link method of an HTTP request server in a Restful protocol, and then the Restful protocol waits for data return;
and 2.7, ending the data transmission flow of the protocol.
4. The transmission device based on SOA architecture integrated deployment according to claim 3, wherein the configuration module implementation specifically includes the following steps:
step 1.1, independently establishing a configuration file serviceUrl.
Step 1.2, manually managing the interfaces, and manually using ServiceCode: the form of RestUrl+RestOperationType is configured into a serviceUrl.
Step 1.3, reading configuration files serviceUrl.properties, storing a service interface ServiceCode into a context ContextConstants, and carrying out context identification and transmission in the whole flow by the ServiceCode in the context;
step 1.4, reading configuration files serviceUrl.properties, storing the RestUrl information of a service interface ServiceCode into a context ContextConstants, and carrying out context identification in the context by using the RestUrl and transmitting the information in the whole flow;
step 1.5, reading configuration files, serviceUrl.properties, storing the RestOperationType of the service interface ServiceCode into the context ContextConstants, carrying out context identification by using the RestOperationType and transmitting in the whole flow, wherein the RestOperationType defaults to be post.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210807671.3A CN115225476B (en) | 2022-07-08 | 2022-07-08 | Transmission method and device based on SOA architecture integrated deployment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210807671.3A CN115225476B (en) | 2022-07-08 | 2022-07-08 | Transmission method and device based on SOA architecture integrated deployment |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN115225476A CN115225476A (en) | 2022-10-21 |
| CN115225476B true CN115225476B (en) | 2023-08-11 |
Family
ID=83609121
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202210807671.3A Active CN115225476B (en) | 2022-07-08 | 2022-07-08 | Transmission method and device based on SOA architecture integrated deployment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN115225476B (en) |
Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2011150645A1 (en) * | 2010-12-20 | 2011-12-08 | 华为技术有限公司 | Method for scheduling web hosting service, method for processing application access, apparatus and system thereof |
| CN104660575A (en) * | 2013-11-25 | 2015-05-27 | 上海益尚信息科技有限公司 | Novel data transmission method for maintaining sub-system binding of NAT address base station in SIP network system |
| WO2015176519A1 (en) * | 2014-05-21 | 2015-11-26 | 华南理工大学 | Distributed collaborative method for improving application efficiency of web browser |
| WO2019075317A1 (en) * | 2017-10-12 | 2019-04-18 | Convida Wireless, Llc | Interworking service for the restful internet of things |
| CN111787031A (en) * | 2020-08-03 | 2020-10-16 | 南京信息职业技术学院 | Method for sending control instruction of Internet of things equipment based on distributed technology |
| CN111988171A (en) * | 2020-08-12 | 2020-11-24 | 北京大学 | Method, proxy server and system for calling SOAP Web service based on RESTful style request |
| CN112039969A (en) * | 2020-08-26 | 2020-12-04 | 浪潮云信息技术股份公司 | AWS 3 URL uploading method based on Redis distributed lock development |
| CN113031979A (en) * | 2021-05-26 | 2021-06-25 | 武汉众邦银行股份有限公司 | Galaxy-based framework configuration separation device and implementation method |
-
2022
- 2022-07-08 CN CN202210807671.3A patent/CN115225476B/en active Active
Patent Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2011150645A1 (en) * | 2010-12-20 | 2011-12-08 | 华为技术有限公司 | Method for scheduling web hosting service, method for processing application access, apparatus and system thereof |
| CN104660575A (en) * | 2013-11-25 | 2015-05-27 | 上海益尚信息科技有限公司 | Novel data transmission method for maintaining sub-system binding of NAT address base station in SIP network system |
| WO2015176519A1 (en) * | 2014-05-21 | 2015-11-26 | 华南理工大学 | Distributed collaborative method for improving application efficiency of web browser |
| WO2019075317A1 (en) * | 2017-10-12 | 2019-04-18 | Convida Wireless, Llc | Interworking service for the restful internet of things |
| CN111787031A (en) * | 2020-08-03 | 2020-10-16 | 南京信息职业技术学院 | Method for sending control instruction of Internet of things equipment based on distributed technology |
| CN111988171A (en) * | 2020-08-12 | 2020-11-24 | 北京大学 | Method, proxy server and system for calling SOAP Web service based on RESTful style request |
| CN112039969A (en) * | 2020-08-26 | 2020-12-04 | 浪潮云信息技术股份公司 | AWS 3 URL uploading method based on Redis distributed lock development |
| CN113031979A (en) * | 2021-05-26 | 2021-06-25 | 武汉众邦银行股份有限公司 | Galaxy-based framework configuration separation device and implementation method |
Also Published As
| Publication number | Publication date |
|---|---|
| CN115225476A (en) | 2022-10-21 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN100423610C (en) | User identifying module service and method and system for using personalized tailered issuing | |
| CN100555944C (en) | Utilize the method for GPRS technical management and shared mobile communication terminal | |
| CN103729189B (en) | Broadcasting method for converting protocol based on LUA, system, terminal | |
| EA002411B1 (en) | System and method for using a workspace data manager to access, manipulate and synchronize network data | |
| US20030157933A1 (en) | Multicast address allocation apparatus, information distribution apparatus, information distribution system | |
| CN104050525B (en) | Information processing equipment, information processing method and distribution system | |
| CN101963909B (en) | Information processing apparatus, workflow system and workflow management method | |
| CN106257868B (en) | Configuration data pushing method and device | |
| JP2006014319A (en) | Apparatus and system for executing document scanning jobs that are intended for remote work station through using wireless interconnection between work station and scanner facility | |
| CN100363890C (en) | System and method for synchronously renewing file of remote computer | |
| US20070070977A1 (en) | Method for delivering data resources | |
| CN101951576B (en) | Method for implementing USSD (Unstructured Supplementary Service Data) application service and USSD centre | |
| US20090265466A1 (en) | Data providing system, data providing method, server, network system, and program | |
| CN1623150A (en) | Providing information for mobile user | |
| CN115225476B (en) | Transmission method and device based on SOA architecture integrated deployment | |
| CN103368897A (en) | Method, device and system for transmitting application program | |
| JP2002049637A (en) | Database management method, device and recording medium | |
| JPH11272471A (en) | Software distribution system and recording medium stored with program used for the same | |
| CN107885604A (en) | Method and device, computer equipment and the storage medium of communications between heterogeneous systems | |
| US8762837B1 (en) | System and methodology for the storage and manipulation of documents | |
| JP2004078535A (en) | Exclusive control device, method, and program | |
| CN1773984A (en) | Method for promoting transaction of mobile communication value-added service | |
| JP2003085073A (en) | File download support file server, file download support download terminal, file download support method, file download support program and recording medium with the program recorded | |
| CN118210480B (en) | System and method for realizing general form under micro-service scene | |
| JP3937374B2 (en) | Data object storage method and data object storage device |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |