WCF-Custom Transport Properties Dialog Box, Send, General Tab
Use the General tab to configure the endpoint address, the service identity, and the SOAP Action feature for the WCF-Custom send port. The WCF-Custom adapter enables the use of Windows Communication Foundation (WCF) extensibility features. The adapter allows users to select and configure a WCF binding, behavior, and behavior extensions for the receive location and send port.
| Use this | To do this |
|---|---|
| Address (URI) | Required. Specify the fully qualified URI of the destination service for this send port. The available transport scheme for this property is decided by the Binding Type property on the Binding tab. Note: You can also import and export this property through the Import/Export tab. Maximum length: 255 The default is an empty string. |
| Endpoint Identity | Optional. Specify the identity of the service that this send port expects. These settings enable this send port to authenticate the service. In the handshake process between the client and service, the WCF infrastructure will ensure that the identity of the expected service matches the values of this element. The values that can be specified for the Endpoint Identity property differ according to the security configuration. Note: You can also import and export this property through the Import/Export tab. If the send port is configured to use multiple identity types, only the identity type with the lowest number can be exported. For example, if 1. DNS and 4. RSA are both set in the Identity Editor dialog box, only the 1. DNS property is saved by using the Export tab. The default value is cleared. |
| Action | Required. Specify the SOAPAction header field for outgoing messages. This property can also be set through the message context property WCF.Action in a pipeline or orchestration. You can specify this value in two different ways: the single action format and the action mapping format. If you set this property in the single action format- for example, http://contoso.com/Svc/Op1- the SOAPAction header for outgoing messages is always set to the value specified in this property. If you set this property in the action mapping format, the outgoing SOAPAction header is determined by the BTS.Operation context property. For example, if this property is set to the following XML format and the BTS.Operation property is set to Op1, the WCF send adapter uses http://contoso.com/Svc/Op1 for the outgoing SOAPAction header. <BtsActionMapping> <Operation Name="Op1" Action="http://contoso.com/Svc/Op1" /> <Operation Name="Op2" Action="http://contoso.com/Svc/Op2" /> </BtsActionMapping> If outgoing messages comes from an orchestration port, orchestration instances dynamically set the BTS.Operation property with the operation name of the port. If outgoing messages are routed with content-based routing, you can set the BTS.Operation property in pipeline components. Minimum length: 0 Maximum length: 32767 The default is an empty string. |
See Also
How to Configure a WCF-Custom Send Port WCF Adapters Property Schema and Properties The <identity> element Configuring Dynamic Send Ports Using WCF Adapters Context Properties
Feedback
Coming soon: Throughout 2024 we will be phasing out GitHub Issues as the feedback mechanism for content and replacing it with a new feedback system. For more information see: https://aka.ms/ContentUserFeedback.
Submit and view feedback for