BizTalk Server Orchestration - RE: BizTalk 2004: Dynamic Port Binding - Filename and Path - Macros

This is Interesting: Free IT Magazines  
Home > Archive > BizTalk Server Orchestration > August 2004 > RE: BizTalk 2004: Dynamic Port Binding - Filename and Path - Macros





You are viewing an archived Text-only version of the thread. To view this thread in it's original format and/or if you want to reply to this thread please [click here]

Author RE: BizTalk 2004: Dynamic Port Binding - Filename and Path - Macros
Neal Walters

2004-08-11, 5:52 pm

Below is from a prior post with some of my own additions, it assumes you are
using orchestration:

In your orchestration (this solution does require Orchestration) set the
FILE.ReceiveFileName to what you want the file
name to be in a Message Assignment Shape after you create the outbound
message:

InvoiceMessage(FILE.ReceivedFileName) = "Test12345.xml" 'This could be more
complicated (see below).

in your send port under FILE Transport Properties

File name: %SourceFileName%

Hope this helps you.

This trick was from Microsoft Community Orchestration, answer posted by Bill
Chesnut. Above from Post from Microsoft Newsgroup 6/13/2004.

Following additional examples by Neal Walters:

I recently did a demo of this in class and it was remarkable easy.
I was receive a "StubbornPO" and converting it to an 'EasyPO" using a
Transform shape (map). I added a Message-Assignment shape after the
Transform and added the following line of code:

mEasyPO(FILE.ReceivedFileName) = mEasyPO.PONumber + ".xml";

Note that "PONumber" was a distinguished field in my schema.

I suppose if you wanted to further add the %MessageID%.xml in the send port,
you could leave the ".xml" out in the orchestration code above (you probably
don't want two .xml's in your filename).

I did prefix the message with additional text and the additional text got
added just fine in front of the "FILE.ReceivedFileName". So for example in
my send port I set filename = "OrchLargePO_%SourceFileName%" and since my PO
number was "STU-002" the ultimate filename was "OrchLargePO_STU-002.xml".

Later I will see what effect this has on HAT and tracking.

Neal Walters
http://Biztalk-Training.com

Sponsored Links






Free braindumps | Software forum | Database administration forum

Copyright 2003 - 2008 webservertalk.com