Geeks With Blogs
John Watson The Pragmatic Enthusiast BizTalk
BizTalk Project / Assembly Organization Gotcha
I have a real-world experience to share for organizing your BizTalk projects and assemblies. I think the natural tendency is to group “like things” together so if you have an orchestration with a schema or two and a custom pipeline you'd define all these artifacts in the same project. This way they're always kept together in source control, on disk and deployed together. That same “benefit” is also the “gotcha” to watch out for. In my case, the custom pipeline ......

Posted On Friday, May 6, 2005 10:45 AM

Specifying the output filename from a BizTalk orchestration
Once again, I needed a short simple answer but found either examples that didn't match exactly or newsgroup posts that were cryptic. In my case, the target system I was feeding data to required me to specify a filename that included the month and day of posting as well as the next sequential number. Thus the format is MyOutputFile_mmdd-nnn.out where mm is the month, dd is the day and nnn is the next sequential number (in the case of multiple runs during the same day). To do this, within the message ......

Posted On Monday, May 2, 2005 4:40 PM

Changing a VPC Computer Name with BizTalk
Alan Smith asked about the steps to take to change a VPC computer name when distributing the same preloaded VPC image to multiple developers...”We have network problems if two or more images with the same computer name are started with network access (to SourceSafe). So I attempted to change the computer name in an image.” While the BizTalk reload steps are painful, Megan Davis put together notes on sysprepping the VPC image before distributing so that it will do a “mini-install” ......

Posted On Wednesday, April 27, 2005 1:56 PM

New BizTalk Wiki

Aaron Skonnard has started The BizTalk Wiki

Posted On Tuesday, April 26, 2005 8:55 PM

Accessing input queue name in an orchestration

The name of the queue that a message was received on can also be obtained through the message context:

IncomingMsgName(BTS.InboundTransportLocation)

Posted On Wednesday, April 13, 2005 11:12 AM

Accessing input filename in an orchestration
I recently needed to access the incoming filename in an orchestration and found it difficult to find the simple answer. I found a few examples of doing so in a pipeline adapter and a couple of cryptic answers on newsgroups but nothing plain and simple. The incoming filename is made available in the message context and can be accessed via: IncomingMsgName(FILE.Receiv... Hope this helps somebody and saves some time. ......

Posted On Saturday, December 11, 2004 4:39 PM

New BizTalk Deployment with NAnt
Scott has a major update to his award winning BizTalk deployment script.

Posted On Tuesday, December 7, 2004 8:05 PM

Copyright © John Watson | Powered by: GeeksWithBlogs.net | Join free