Suggestions on implementing a Server/Client based SOAP system
I'm developing a SOAP based server/client, and I'd like some inputs about
developing the application.
The application has mainly three parts:
=> Asynchronous messaging
The system is mainly a "Incident-creating" system, means if any problem is
found on the client side (ABC company) or our side, an "Incident" is
in the Database.
1)If the client created an incident he sends the "Incident"
information to us as a SOAP envelope.
2) If we create an incident, we send the "Incident" information to the
URL as a SOAP message.
Here when the Problem is submitted or Accepted a "Business
sent/received. This Acknowledgement is to ensure that the information
was well formed and had all the mandatory fields required. The
is a Synchronous call.
i) If the client's end-point is not available, we've to retry the
try sending the "Incident" information until the end-point is available.)
3) When we receive any message from the ABC company, we need to queue
any transactions. Once we put the messages into a message queue
should pull out each message, parse the SOAP message and insert the
This is a broad picture of the whole application.
I was thinking to have the following:
1) Client => will create "new Incident" messages and submits the
information to the client's end-point.
2) Server => (ABC co) will use this end-point (our end-point), to submit
any Incident information.
Please let me know your thoughts and also suggest best approaches and
implementing the same.