Export (0) Print
Expand All

How to Configure an SB-Messaging Receive Location

[Unless specifically noted, the content in this topic applies to BizTalk Server 2013 and 2013 R2.]

This section provides information on how to configure an SB-Messaging Receive Location using the BizTalk Server Administration Console.

noteNote
Before completing the following procedure you must have already added a one-way receive port. For more information, see How to Create a Receive Port.

To configure an SB-Messaging receive location

  1. In the BizTalk Server Administration console, expand BizTalk Server Administration, expand BizTalk Group, expand Applications, and then expand the application under you want to create a receive location.

  2. In the left pane, click the Receive Ports node and in the right pane, right-click the receive port with which you want to associate the new receive location, and then click Properties.

  3. In the left pane of the Receive Port Properties dialog box, select Receive Locations, and in the right pane click New to create a new receive location.

  4. In the Receive Location Properties dialog box, in the Transport section, select SB-Messaging from the Type drop-down list, and then click Configure to configure the transport properties for the receive location.

  5. In the SB-Messaging Transport Properties dialog box, in the General tab, do the following:

     

    Use this To do this

    Queue or Subscription URL

    Specify the URL where the Service Bus queue is deployed. Typically the URL is in the following format:

    sb://<namespace>.servicebus.windows.net/<queue_name>
    

    Open Timeout

    Specifies a time span value that indicates the time for a channel open operation to complete.

    Default value: 1 minute

    Close Timeout

    Specifies a time span value that indicates the time for a channel close operation to complete.

    Default value: 1 minute

    Receive timeout

    Specifies a time span value that indicates the time for a receive operation to complete.

    Default value: 10 minutes

    Prefetch count

    Specifies the number of messages that are received simultaneously from the Service Bus Queue or a topic. Prefetching enables the queue or subscription client to load additional messages from the service when it performs a receive operation. The client stores these messages in a local cache. The size of the cache is determined by the value for the Prefetch Count property you specify here.

    For more information, refer to the section “Prefetching” at http://msdn.microsoft.com/library/windowsazure/hh528527.aspx

    Default value: -1

    Use Session

    Select this check box to use a Service Bus session to receive messages from a queue or a subscription.

  6. In the Authentication tab, do the following:

     

    Use this To do this

    Access Control Service

    Select this to use ACS for authentication and provide the following values:

    • Specify the Service Bus Access Control Service STS URI. Typically the URI is in the following format:

      https://<namespace>-sb.accesscontrol.windows.net/
      
    • Specify the issuer name for the Service Bus namespace.

    • Specifies the issuer key for the Service Bus namespace.

    Shared Access Signature (applicable to BizTalk Server 2013 R2 only)

    Select this to use Shared Access Signature (SAS) for authentication, and provide the SAS key name and key value.

  7. In the Properties tab, in the Namespace for Brokered Message Properties field, specify the namespace that the adapter uses to write the brokered message properties as message context properties on the message received by BizTalk Server. Additionally, if you want to promote the brokered message properties, select the Promote Brokered Message Properties check box.

  8. Click OK.

  9. Enter the appropriate values in the Receive Location Properties dialog box to complete the configuration of the receive location and click OK to save settings. For information about the Receive Locations Properties dialog box, see How to Create a Receive Location.

See Also

© 2014 Microsoft Corporation. All rights reserved.

Community Additions

ADD
Show:
© 2014 Microsoft