locked
Why Receive port have Receive locations but Send port dont have send location?? RRS feed

  • Question

  • I have small query...I know the difference between the Receive and send port but the doubt is...

    Why Receive port have Receive locations but Send port dont have send location??
    Tuesday, November 3, 2009 7:43 AM

Answers

  • Hi,

    I think this has mainly to do with the way the two (receive ports and send ports) are internally used and instantiated by BizTalk.

    If you're looking for a way to use multiple send ports for one operation you could try a send port group. Although there are a lot of small differences you could compare the concept of a receive port with multiple receive locations to the concept of a send port group with multiple send ports.

    Beware that you can set a filter on both the send port group and send port. Filters with send port groups can be a little tricky so be sure to test this thoroughly.


    HTH, Randal van Splunteren - http://biztalkmessages.vansplunteren.net - Please mark as answered if this answers your question.
    Tuesday, November 3, 2009 8:10 AM
    Moderator
  • Hi,

    In one single Receive Port we can add multiple locations. Hence we have recv location. While sending if you want to pass the message to be broadcasted we can go for send group. if we are going to send the msg to one location we need not have a send location separately.


    Vijaykishan | http://v2attechhorizon.blogspot.com | Please mark this as answer if it helps
    Tuesday, November 3, 2009 8:14 AM
  • This is by BizTalk design and if we look it with respect to the working of how the messages flow in and out of BizTalk we can easily understand the difference. In the orchestration design when we use logical receive port we assume that it will be connected to a physical receive port when we deploy and configure it in the admin console. However at that time we know that a message of type (X) will be received in the orchestration regardless of the location. When we try to configure the receive port we can have multiple locations from where we can get that message of type (X) for e.g. from a file or ftp location.

    Similarly from the perspective of send ports logically for an opertion within the orchestration we can assume that we may send the message to one or more locations. While the send port can only have one location bound to it. Send ports can be grouped together where a single message can be broadcasted to all the send ports based on the filters on the send ports and send port group. All the send ports can be bound to different locations.

    Receive ports can also be thought as publishers and they can publish the message (X) received from any location to the message box. While send ports and send port groups are subscribers.

    Abdul Rafay http://abdulrafaysbiztalk.wordpress.com/ Please mark this as answer if it helps
    Tuesday, November 3, 2009 8:47 AM

All replies

  • Hi,

    I think this has mainly to do with the way the two (receive ports and send ports) are internally used and instantiated by BizTalk.

    If you're looking for a way to use multiple send ports for one operation you could try a send port group. Although there are a lot of small differences you could compare the concept of a receive port with multiple receive locations to the concept of a send port group with multiple send ports.

    Beware that you can set a filter on both the send port group and send port. Filters with send port groups can be a little tricky so be sure to test this thoroughly.


    HTH, Randal van Splunteren - http://biztalkmessages.vansplunteren.net - Please mark as answered if this answers your question.
    Tuesday, November 3, 2009 8:10 AM
    Moderator
  • Hi,

    In one single Receive Port we can add multiple locations. Hence we have recv location. While sending if you want to pass the message to be broadcasted we can go for send group. if we are going to send the msg to one location we need not have a send location separately.


    Vijaykishan | http://v2attechhorizon.blogspot.com | Please mark this as answer if it helps
    Tuesday, November 3, 2009 8:14 AM
  • This is by BizTalk design and if we look it with respect to the working of how the messages flow in and out of BizTalk we can easily understand the difference. In the orchestration design when we use logical receive port we assume that it will be connected to a physical receive port when we deploy and configure it in the admin console. However at that time we know that a message of type (X) will be received in the orchestration regardless of the location. When we try to configure the receive port we can have multiple locations from where we can get that message of type (X) for e.g. from a file or ftp location.

    Similarly from the perspective of send ports logically for an opertion within the orchestration we can assume that we may send the message to one or more locations. While the send port can only have one location bound to it. Send ports can be grouped together where a single message can be broadcasted to all the send ports based on the filters on the send ports and send port group. All the send ports can be bound to different locations.

    Receive ports can also be thought as publishers and they can publish the message (X) received from any location to the message box. While send ports and send port groups are subscribers.

    Abdul Rafay http://abdulrafaysbiztalk.wordpress.com/ Please mark this as answer if it helps
    Tuesday, November 3, 2009 8:47 AM