I have developed two custom pipelines that call a custom pipeline component for archiving. Almost all configurations for these components are set in the BizTalk Admin console, but a few are populated with defaults. A user will then come in and overwrite the blank values with their selections.
For one-way receive locations and send ports, these pipelines function properly. If I have a two-way location or port, the design-time properties will be called only on the receive of the receive location and the send of the send port. The second action, sending a response or receiving a response, does not pickup the configurations set in the Admin console. If I attach the debugger and listen for the second action of the location/port, I can see that the property bag’s Load method is called, but all values are null.
Has anyone else experienced this issue or is this an *undocumented feature*? Are there any hotfixes to address this? I am having the same issue on both BizTalk 2006 and 2006 R2. Using the MLLP and SOAP adapters results in the same result.