Seeking asynchronous xml messaging scheme! !! !!

bihailantian

I want to do such a distributed asynchronous xml messaging scheme.
The current idea is: in each region, all applications (including web applications) do not communicate directly, but communicate with the regional integration server; between regions, communicate with each other through the regional integration server. All communication messages are xml data.
The regional integration server wants to receive messages through the web service. The current difficulty is how to solve the problem of message monitoring and automatic forwarding.

crabhero

Throwing bricks hopes to attract jade:
1. Define a unified message (xml) format
2. Register the interface and description information of any app with the center to obtain a unique identifier
3. All applications implement IInterface.Receive (message, purpose unique identifier)
4. Each app implements Receive internally and forwards the message to the destination code

Lightweight implementation, without considering transactions, permissions, security, etc.

bihailantian

Thank you,
1. The exchanged XML format has been determined;
2. The app registration function and permission list mechanism have been set in the regional integration server;
3. In the xml message, it can carry the destination identifier;
The issue is:
1. What kind of delivery is used? All applications here are only web applications.
For example, the regional integration server (ZIS) is also made into a web application, A post to ZIS, ZIS post to B.
But the post has no way to guarantee the security and integrity of the message delivery.
2. With SOAP, webservice can only be received, not actively sent, and there is still a lack of a message monitoring mechanism.
What better solution? ?

crabhero

2. With SOAP, webservice can only be received, not actively sent, and it lacks a message monitoring mechanism.
-------------------------------------------------- ----
The sending is changed to the app to forward the server to the central server, the source can be any piece of code in the app,
The monitoring mechanism can consider that the app provides a webservice interface, and the timing of sending is determined by the central forwarding server, so that there is no app monitoring problem. The central forwarding server provides services such as transaction submission and persistence, that is, all apps call the server The webservice sends data, and the server app calls the app’s webservice accept function to forward the message.

bihailantian

tocrabhero:
I understand what you mean:
Whether it is an application or a regional integration server, it is made into an app+webservice approach:
A. app calls ZIS.webservice to send;
ZIS.app calls B.webservice to implement forwarding.
Maybe I am stupid:)
What I can't figure out is: the data received by ZIS.webservice is stored in the database, how can I tell ZIS.app that there is a message to send?
There is also the transaction commit and persistence you mentioned. I haven't considered it clearly yet. If you can get your advice, it will be very grateful!

chander

Recommend to use MSMQ

tsxshuanger

Is there any custom message processing mechanism besides MSMQ?