Demystifying Direct Bound Ports – Part 5

Dynamic Direct Bound Ports A dynamic port allows you to set the address of the logical port to a URI so that at runtime the message can be routed to the correct service to handle the request and the service can then send to the indicated endpoint.  In BizTalk Server 2006 the same can be…


Demystifying Direct Bound Ports – Part 4

Self-Correlating Direct Bound Ports Self-Correlating direct bound ports are self referential (i.e. the address property includes the service instance identifier of the orchestration) providing the capability of getting messages back to a particular orchestration instance without using a correlation set. To configure a self-correlating direct bound port select ‘Self Correlating’ as the ‘Partner Orchestration Port’….


Demystifying Direct Bound Ports – Part 3

Partner Direct Bound Ports Partner direct bound ports provide the capability of having inter-orchestration communication via ports.  To configure a partner direct bound port you must choose the orchestration and port for the ‘Partner Orchestration Port’ property.  When configuring the two partner ports you must have one side select the orchestration.port it will communicate with…


Demystifying Direct Bound Ports – Part 2

Message Box Direct Bound Ports Message box direct bound ports, as its name implies, allows you to drop messages directly into the message box without an explicit recipient and it allows you to subscribe to messages, not from any particular sender, which meet certain criteria.  To configure a message box direct bound port set the…


Demystifying Direct Bound Ports – Part 1

Direct Bound Ports In BizTalk Server 2004/2006 orchestrations can have direct bound ports.  Direct bound ports are logical one-way or two-way ports in your orchestration that are not explicitly bound to physical ports that allow you to have different communication patterns amongst your services.  To create a direct bound port select the binding of the…