Client Considerations When Redeploying a Reliable Web Service Interoperability with WebLogic Web Service Reliable Messaging

Using Web Services Reliable Messaging 5-49

5.12 Client Considerations When Redeploying a Reliable Web Service

WebLogic Server supports production redeployment, which means that you can deploy a new version of an updated reliable WebLogic Web service alongside an older version of the same Web service. WebLogic Server automatically manages client connections so that only new client requests are directed to the new version. Clients already connected to the Web service during the redeployment continue to use the older version of the service until they complete their work, at which point WebLogic Server automatically retires the older Web service. If the client is connected to a reliable Web service, its work is considered complete when the existing reliable message sequence is explicitly ended by the client or as a result of a timeout. For additional information about production redeployment and Web service clients, see Client Considerations When Redeploying a Web service in Getting Started With JAX-WS Web Services for Oracle WebLogic Server.

5.13 Interoperability with WebLogic Web Service Reliable Messaging

The WebLogic Web services reliable messaging implementation will interoperate with the Web service reliable messaging implementations provided by the following third-party vendor Web services: IBM and Microsoft .NET. For best practices when interoperating with Microsoft .NET, see Interoperability with Microsoft WCF.NET in Introducing WebLogic Web Services for Oracle WebLogic Server. To enhance interoperability with Oracle SOA services that use Web services reliable messaging, please consider the following interoperability guidelines: ■ Do no use MakeConnection for asynchronous transport, as described in Section 3.6, Using Asynchronous Web Service Clients From Behind a Firewall MakeConnection. Reliable SOA services do not support MakeConnection. ■ Do no use WS-SecureConversation to secure reliable Web services. SOA services do not support the use of Web services reliable messaging and WS-SecureConversation together. ■ For reliable WebLogic Web service clients that are accessing reliable SOA services: – Use synchronous anonymous WS-Addressing ReplyTo EPR request-reply or one-way MEP Message exchange pattern. – Do not use asynchronous non-anonymous WS-Addressing ReplyTo EPR request-reply MEP Message exchange pattern. ■ For reliable SOA clients that are accessing reliable WebLogic Web services, use one of the following: – Synchronous anonymous WS-Addressing ReplyTo EPR request-reply or one-way MEP Message exchange pattern. – Asynchronous non-anonymous WS-Addressing ReplyTo EPR request-reply MEP Message exchange pattern. 5-50 Programming Advanced Features of JAX-WS Web Services for Oracle WebLogic Server 6 Managing Web Service Persistence 6-1 6 Managing Web Service Persistence The following sections describe how to manage Web service persistence. ■ Section 6.1, Overview of Web Service Persistence