Creating Microsoft .NET transport configurations
You can manually create a Microsoft .NET transport configuration
to describe the transport settings for service requests that use the Windows Communication Foundation
(WCF) protocol.
Before you begin
If you are using SOAP security, ensure that the environment is configured with the correct libraries and configuration files.
Certificates and libraries required by the Microsoft client proxy must be installed on the computer, including Microsoft .NET libraries.
You must link a modified version of the Microsoft client proxy configuration file of the WCF service (by default client.exe.config) to the Microsoft .NET transport configuration. You must rename the file to soaclient.exe.config and edit it as described in the following procedure.
Tip: You can create a Microsoft .NET transport configuration automatically by importing
the Microsoft .NET WSDL
file. In this case, you must still manually edit the Microsoft .NET transport configuration
to point to the modified soaclient.exe.config file as described in the following procedure. For more information,
see Sending service requests with WSDL files
About this task
- BasicHttpBinding
- WsHttpBinding
- NetMsMqBinding for 1-way calls only
- WSFederationHttpBinding
- WS2007FederationHttpBinding
- NetTcpBinding
- Custom bindings that do not integrate custom extensions in the channel, serialization of the message, transport, and security
Note: The following WCF services are not supported:
- Transaction and scopes
- Duplex mode requests, such as callbacks or 2-way services based on the Microsoft Message Queuing (MS-MQ) transport
To use Generic
Service Client with IBM Appscan to test a WCF application, add the following code to the WCF
configuration
file:
<system.diagnostics> <trace autoflush="true" />
<sources> <source name="System.Net"
maxdatasize="1048576"><listeners><add
name="System.Net"/></listeners></source> <source
name="System.Net.Cache"><listeners><add
name="System.Net"/></listeners></source> <source
name="System.Net.Http"><listeners><add name="System.Net
"/></listeners></source> <source
name="System.Net.Sockets"><listeners><add
name="System.Net"/></listeners></source> <source
name="System.Net.WebSockets"><listeners><add
name="System.Net"/></listeners></source> </sources>
<sharedListeners> <add
name="System.Net"
type="IBM.ServiceModel.Soa.Extension.tools.TrafficTraceListener,
Soa-Behavior-Library"
initializeData="" />
</sharedListeners> <switches> <add name="System.Net"
value="All"/> <add name="System.Net.Cache"
value="All"/> <add name="System.Net.Http"
value="All"/> <add name="System.Net.Sockets"
value="All"/> <add name="System.Net.WebSockets"
value="All"/> </switches></system.diagnostics>
IBM
Appscan expects only HTTP requests in WCF. The following HTTP bindings are supported:
- BasicHttpBinding
- Custombinding above standard httpTransport
- WsHttpBinding
- WsFederationHttpBinding
- WS2007FederationHttpBinding
- Action value ( mandatory )
- Reply Action value ( mandatory )
- Protection level