Binding an orchestration to multiple receive ports

In the BizTalk Server Management Console, it’s only possible to bind 1 physical Receive Port to 1 logical (Orchestration-)Receive Port.
To bind multiple receive ports to an orchestration, you could follow these steps:

1) Create receive ports with unique and approviate names in the correct biztalk application.

2) Create a new one way port in your orchestration, which can receive messages. As port binding please use “direct”. In this example please make sure, that “Routing between ports will be defined by filter expressions on incoming messages in the Messagebox database” is selected.

3) Create or select your activating Receive Shape and configure the “Filter Expression” by clicking the ellipsis. In the Filter Expression add as many “BTS.ReceivePortName”-properties as Receive Ports you have created eralier. Set the values of the properties to the portnames of the Receive Ports and group each row by “OR”.
The Filter Expression should resemble something like this: (BTS.ReceivePortName == “ReceiveMsgPort1”) (BTS.ReceivePortName == “ReceiveMsgPort2”)

All the messages which originate from the filtered ports will be processed by the Orchestration

Access to a Stored Procedure on a remote SQL Server via Microsoft Biztalk SQL Adapter

If it is neccesary to access a stored procedure on a remote SQL Server by SQL Adapter, you have to activate the DTC Network access in the security options of component services.

Error message: “Transaction could not enlist in the Transaction coordinator”.

Security setting:

Further informations: http://msdn.microsoft.com/en-us/library/aa561924.aspx.

%SourceFileName%

Macro %SourceFileName%

The original filename of a file which has been catched by a receive port can be used again in a send port by using the macro %SourceFileName%. In this way it is possible to move a file from one directory to an another -Ă‚ source filename identical to the destination filename. Also it is possible to send a file via ftp adapter (send direction) to a ftp server, using the same filename. This is needful if your source system (e.g. ERP system) generates a reporting file with a strict filename policy prescribed by owner of the destinate ftp server.