215:
WS-ReliableMessaging (WS-RM) protocol to transmit the message to the RMD. The RMD delivers the message to the AD. If the RMS cannot transmit the message to the RMD for some reason, it must raise an exception or otherwise indicate to the AS that the message was not transmitted. The AS and RMS may be implemented within the same process space or they may be separate components. Similarly, the AD and RMD may exist within the same process space or they may be separate components.
22:
214:
An
Application Source (AS) wishes to reliably send messages to an Application Destination (AD) over an unreliable infrastructure. To accomplish this, they make use of a Reliable Messaging Source (RMS) and a Reliable Messaging Destination (RMD). The AS sends a message to the RMS. The RMS uses the
218:
The important thing to keep in mind is that the WS-RM specification only deals with the contents and behavior of messages as they appear "on the wire". How messages are sent from the AS to the RMS, how they are delivered from the RMD to the AD, whether messages are persisted on-disk or held in
265:. WS-ReliableMessaging does not define all the features required for a complete messaging solution. WS-ReliableMessaging is a building block that is used in conjunction with other Web Services specifications and application-specific protocols to build a complete messaging solution.
229:
Each message will be delivered to the AD at least once. If a message cannot be delivered, an error must be raised by the RMS and/or the RMD. Messages may be delivered to the AD more than once (i.e. the AD may get duplicate
308:
authored by BEA, IBM, Microsoft, and Tibco. This version of the specification has been implemented by a number of vendors and open source projects. It is sometimes referred to as "WS-ReliableMessaging 1.0" or "WS-RM 1.0".
242:
Each message will be delivered to the AD exactly once. If a message cannot be delivered, an error must be raised by the RMS and/or the RMD. The AD will never get duplicate messages.
295:
248:
Messages will be delivered from the RMD to the AD in the order that they are sent from the AS to the RMS. This assurance can be combined with any of the above assurances.
236:
Each message will be delivered to the AD at most once. Messages might not be delivered to the AD, but the AD will never get duplicate messages.
43:
472:
208:
262:
113:
292:
94:
413:
66:
350:
The version replaces the references to pre-standard versions of WS-Policy with references to the WS-Policy W3C Recommendation (
47:
73:
80:
156:
and in March, 2003 and subsequently refined over the next two years. The
February, 2005 version was submitted to the
277:
attempts to make the case that reliability is not needed at the message level, but required at the business level.
62:
32:
332:
51:
36:
387:
336:
328:
447:
355:
317:
168:
157:
137:
between distributed applications in the presence of software component, system, or network failures.
359:
347:
320:
452:
305:
87:
188:
134:
164:
was approved as an OASIS Standard on June 14, 2007, and v1.2 was approved on
February 2, 2009.
160:
Web
Services Reliable Exchange (WS-RX) Technical Committee in June of that year. The resulting
192:
286:
457:
196:
299:
313:
430:
172:
274:
466:
407:
392:
180:
222:
The WS-RM protocol defines and supports a number of
Delivery Assurances. These are:
207:
425:
351:
199:. Most of these vendors now also support the WS-ReliableMessaging specification.
219:
memory, etc.; none of these considerations are part of the WS-RM specification.
141:
21:
377:
161:
382:
365:
All three specifications were approved as OASIS Standards on
February 2, 2009.
397:
145:
342:
All three specifications were approved as OASIS Standards on June 14, 2007.
331:
is the product of the above-mentioned WS-RX TC. It is accompanied by the
176:
402:
153:
258:
130:
184:
149:
15:
206:
321:
Web
Services Reliable Exchange (WS-RX) Technical Committee
354:) and fixes some minor errors. It is accompanied by the
175:) that was supported by a coalition of vendors; namely
257:
WS-ReliableMessaging uses the extensibility model of
458:An Introduction to Web Services Reliable Messaging
8:
302:authored by BEA, IBM, Microsoft, and Tibco.
289:authored by BEA, IBM, Microsoft, and Tibco.
50:. Unsourced material may be challenged and
140:The original specification was written by
114:Learn how and when to remove this message
448:WS-ReliableMessaging 1.1 OASIS Standard
312:This specification and its companion
7:
372:WS-ReliableMessaging Implementations
48:adding citations to reliable sources
323:for standardization in June, 2005.
14:
129:describes a protocol that allows
414:Windows Communication Foundation
20:
171:produced a competing standard (
167:Prior to WS-ReliableMessaging,
1:
453:WS-ReliableMessaging 200502
306:WS-ReliableMessaging 200502
293:WS-ReliableMessaging 200403
287:WS-ReliableMessaging 200303
489:
473:Web service specifications
162:WS-ReliableMessaging 1.1
348:WS-ReliableMessaging 1.2
329:WS-ReliableMessaging 1.1
203:Reliable Messaging Model
253:Composable Architecture
316:were submitted to the
211:
63:"WS-ReliableMessaging"
360:WS-MakeConnection 1.1
337:WS-MakeConnection 1.0
210:
127:WS-ReliableMessaging
44:improve this article
314:WS-RM Policy 200502
298:2008-05-17 at the
212:
189:Oracle Corporation
135:reliably delivered
193:Progress Software
124:
123:
116:
98:
480:
378:Apache Sandesha2
362:specifications.
356:WS-RM Policy 1.2
339:specifications.
333:WS-RM Policy 1.1
197:Sun Microsystems
119:
112:
108:
105:
99:
97:
56:
24:
16:
488:
487:
483:
482:
481:
479:
478:
477:
463:
462:
444:
439:
422:
388:WebLogic Server
374:
300:Wayback Machine
283:
271:
255:
205:
133:messages to be
120:
109:
103:
100:
57:
55:
41:
25:
12:
11:
5:
486:
484:
476:
475:
465:
464:
461:
460:
455:
450:
443:
442:External links
440:
438:
435:
434:
433:
431:WS-Reliability
428:
421:
418:
417:
416:
410:
405:
400:
395:
390:
385:
380:
373:
370:
369:
368:
367:
366:
345:
344:
343:
326:
325:
324:
303:
290:
282:
279:
270:
267:
254:
251:
250:
249:
246:
243:
240:
237:
234:
231:
227:
204:
201:
173:WS-Reliability
122:
121:
28:
26:
19:
13:
10:
9:
6:
4:
3:
2:
485:
474:
471:
470:
468:
459:
456:
454:
451:
449:
446:
445:
441:
436:
432:
429:
427:
424:
423:
419:
415:
411:
409:
408:SAP NetWeaver
406:
404:
401:
399:
396:
394:
393:IBM WebSphere
391:
389:
386:
384:
381:
379:
376:
375:
371:
364:
363:
361:
357:
353:
352:WS-Policy 1.5
349:
346:
341:
340:
338:
334:
330:
327:
322:
319:
315:
311:
310:
307:
304:
301:
297:
294:
291:
288:
285:
284:
280:
278:
276:
268:
266:
264:
260:
252:
247:
244:
241:
238:
235:
232:
228:
225:
224:
223:
220:
216:
209:
202:
200:
198:
194:
190:
186:
182:
178:
174:
170:
165:
163:
159:
155:
151:
147:
143:
138:
136:
132:
128:
118:
115:
107:
96:
93:
89:
86:
82:
79:
75:
72:
68:
65: –
64:
60:
59:Find sources:
53:
49:
45:
39:
38:
34:
29:This article
27:
23:
18:
17:
426:Web Services
272:
256:
221:
217:
213:
166:
139:
126:
125:
110:
101:
91:
84:
77:
70:
58:
42:Please help
30:
239:ExactlyOnce
226:AtLeastOnce
142:BEA Systems
437:References
412:Microsoft
383:Apache CXF
233:AtMostOnce
230:messages).
104:March 2022
74:newspapers
398:GlassFish
269:Criticism
146:Microsoft
31:does not
467:Category
420:See also
296:Archived
281:History
275:article
245:InOrder
181:Hitachi
177:Fujitsu
88:scholar
52:removed
37:sources
195:, and
152:, and
90:
83:
76:
69:
61:
403:gSOAP
318:OASIS
273:This
169:OASIS
158:OASIS
154:Tibco
95:JSTOR
81:books
358:and
335:and
263:WSDL
261:and
259:SOAP
131:SOAP
67:news
35:any
33:cite
185:NEC
150:IBM
46:by
469::
191:,
187:,
183:,
179:,
148:,
144:,
117:)
111:(
106:)
102:(
92:·
85:·
78:·
71:·
54:.
40:.
Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.
