Only send an email to the credit department if the filename contains the word “EXPORT” and and ends with .txt.
We cannot put *EXPORT*.txt in the Receive Location, because there are other files coming in with different patterns.
Question: How would you do that in BizTalk?
BizTalk has filters on the send ports. So in theory, you could filter on the filename. But guess what?
There is no operator for “contains”, or “matches”, or any RegEx (Regular Expressions).
The image below shows the field we would use: FILE.ReceivedFileName, but there is no operator that helps solve this problem.
On the ReceivePort, I created my own custom pipeline component, did the matching myself, and promoted fields if the results were true. The admin/developer can identify the name of the promoted field as one of the values in my Pipeline Component. He also provides the filemask he wants to match.
The receive port pipeline configuration is shown below.
I created a Property Schema that corresponds:
Then in the SendPort, I can test the promoted fields that were promoted by that Receive Pipeline component.
The underlying connection was closed: The connection was closed unexpectedly.
I’m sure there are numerous reasons for this error, but here’s one I encountered today.
First the background. We have BizTalk server connecting to an internal Open/AS2 server running on Linux. That Linux server was re-installed on a Virtual Machine; and I had agreed with the Linux guy to change the AS2-ID (defined in the Trading Parties) from BiztalkTest to BizTalkProd. However, he didn’t make the change on his side.
So when he looked at the logs, he could see that it was receiving data, but as he described it “the server didn’t know what to do with it.” That means, it didn’t generate the MDN and send it back to BizTalk.
I had defined my SendPort was a two-way (Static Solicit-Reponse) and was using content-based routing. So we sent the message to the AS2 server, and didn’t get a response back, giving the “underlying connection closed unexpectedly” error.