Demystifying Direct Bound Ports – Part 6

Dynamic Direct Bound Port Clarification There seems to have been some confusion generated by readers trying to implement dynamic direct bound ports that I wanted to clarify.  A dynamic direct bound port is merely a direct bound port whose address is set at runtime.  It is not a dynamic send port.  Dynamic send ports allow…


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…


Get Connected to Free Product Support and Tremendous Online Collaboration

Have you ever wanted to speak to Microsoft developers of a specific feature of BizTalk Server? I am sure your answer was “Yes let me at them”, so the Business Process Integration Division is extending an invitation to all customers to join our key feature developers, program managers, and testers in the following newsgroups:  microsoft.public.biztalk.accelerator.forsuppliers microsoft.public.biztalk.newuser…


Low-latency scenarios that use two-way (solicit-response) HTTP send ports.

HttpOutCompleteSize This setting controls the size of the batch of messages that is returned from the HTTP send adapter.  The default value for this is 5.  If the buffer is not full and there are outstanding responses then the adapter will wait for 1 second until it commits the batch.  For low-latency scenarios this should…


An orchestration pattern that can hog the master message box CPU

Overview We had a customer scenario such that when a complex business process was executed at the rate of 1 request per second the CPU utilization of the SQL Server hosting the master message box quickly grew up to 100% sustained.  Having the master message box’s CPU utilization so high is not desirable as it…


Welcome to my blog

I suppose I should give a little background on myself before I start blogging to give my posts some context.  Before Microsoft I was designing and developing parts of foreign exchange transaction systems for Reuters.  I started at Microsoft about 7 years ago as a software design engineer on Windows working on the index server.  I…