ASM and MS Soa using wsHttpBinding?

We are currently building a SOA infrastructure using an F5 ASM to sit between the users and presentation layer and the presentation layer and business layer.

 

The developers want to use MS wsHttpBinding for communication between the presentation layer and business layer.

 

The following service protocols are supported by the wsHttpBinding and WCF (Windows Communication Foundation):

 

•HTTP 1.1

 

HTTP and HTTPS transport.

 

•MTOM

 

Message Transmission Optimisation Mechanism.

 

•WSDL 1.1

 

Web Services Description Language is used to describe services.

 

•WS-Policy and WS-Policy 1.5

 

WS-Policy provides a flexible and extensible grammar for expressing the capabilities, requirements, and general characteristics of entities in an XML Web services-based system.

 

•WS-PolicyAttachment

 

WS-PolicyAttachment is used to attach policy expressions at various scopes in Web Services Description Language (WSDL).

 

•WS-MetadataExchange

 

WS-MetadataExchange is used to retrieve XML Schema, WSDL, and WS-Policy.

 

•SOAP 1.2

 

SOAP Version 1.2 provides the definition of the XML-based information which can be used for exchanging structured and typed information between peers in a decentralized, distributed environment.

 

•WS-Addressing 2005/08

 

The wsHttpBinding implements the World Wide Web Consortium (W3C) WS-Addressing recommendation to enable asynchronous messaging, message correlation, and transport-neutral addressing mechanisms.

 

•WSS SOAP Message Security 1.0

 

A standard set of SOAP extensions that can be used when building web services to implement message content integrity and confidentiality.

 

•WSS SOAP Message Security UsernameToken Profile 1.1

 

Used to allow a service consumer to supply a username and optional password to authenticate that identity to the service producer.

 

•WSS SOAP Message Security X.509 Certificate Token Profile 1.1

 

Used for authentication and message protection when “Certificate” authentication is configured to be used.

 

•WSS SOAP Message Security Kerberos Token Profile 1.1

 

Used for authentication and message protection when “Windows” authentication is configured to be used.

 

•WS-Trust and WS-SecureConversation

 

Used to provide a secure session which may include one or more messages.

 

•WS-ReliableMessaging

 

Used to identify, track and manage the reliable delivery of messages between a source and destination in the presence of software component, system or network failures.

 

•WS-AtomicTransaction

 

Used to support an atomic transactions including multiple services.

 

•WS-Coordination

 

The base protocol for supporting distributed transactions.

 

Does this work with the ASM or what’s the recommended communication between the presentation layer and business layer? (It is also my understanding that most of the communication will use SOAP.)

 

 

Best Regards

 

Martin Forest