y - Net Developer

amrameshreddy.blog.comDurability of the message once it has been sent or system availability is not part of theWS-RM specification or currently available in WCF. 27 A suggestion on how to approach thedurability and system availability aspect, which is out of the scope of the WS-RM specification,has been to leverage MSMQ in conjunction with reliable sessions, but that doesn’t address thecross-platform issues. However, by using gateway technologies such as Host IntegrationServer (HIS) or other MSMQ to IBM MQSeries bridges, it is possible. But again, the limitationson the stack from each vendor on each side of the channel come into play. So, unless you havean extensible stack and you’re prepared to develop customized bindings on the receiving end,the current shipping limitation is WCF in conjunction with MSMQ.Network availability is addressed by dealing with timeouts on acknowledgments. Inactivitytimeout settings, when exceeded without acknowledgment, will result in failure. Therefore,if a session is interrupted by an unreliable network connection, the WCF stack and any WS-RMimplementation that supports AtLeastOnce or ExactlyOne will raise a fault.WS-ReliableMessaging ExampleYou’ll now look at the WsReliableMessaging sample that’s part of the Chapter 13 downloadablesamples. Using the MTOM sample as a base, we’ve modified the bindings to indicate that werequire reliable sessions on the service interface. Using the WCF Service Configuration Editor(SvcConfigEditor.exe) that’s part of the Windows SDK (select Tools ➤ WCF SvcConfigEditor inVisual Studio), you can modify the App.config file for the WcfHost application in the sample, asshown in Figure 13-6.ramrameshreddyramrameshreddyFigure 13-6. Enabling WS-ReliableMessaging on WcfHostCHAPTER 13 ■ IMPLEMENTING SOA INTEROPERABILITY 41927. http://specs.xmlsoap.org/ws/2005/02/rm/