I am reposting this question from 11/26/2004 - did not get any responses...

Any idea what legal values of this variable might be.  I want to set the nam
e
of the pipeline for a dynamic file send port.  A search on the help refresh
shows nothing on this word "SendPipelineConfig" nor "BTS.SendPipelineConfig"
.

I want to do something like this:
mymsg(BTS.SendPipelineConfig) = "xxxx"
but what the heck is legal for "xxxx"?
Is it the pipeline name?  Fully qualified assembly name?
Why aren't these BTS. variables documents?  or are they?

Thanks,
Neal Walters
http://Biztalk-Training.com - Free Biztalk 2004 Demos

[ Post a follow-up to this message ]

Hello.

I think I looked into this a while back.  I saw the name as the fully
qualified namespace name, but I did not think I was able to set this propert
y
inside the Orchestration.  I think the pipeline is associated with a Port an
d
it can not be set dynamically.

As an alternative, have you looked into using Role Links?  This would allow
for multiple send ports and pipelines.  Or, some stages of the pipelines
allow for a first match processing.  Many this would allow a single pipeline
to process different types of messages?  Just some thoughts…

Hope this helps.

Stephen W. Thomas
http://www.geekswithblogs.net/sthomas




"Neal Walters" wrote:

> I am reposting this question from 11/26/2004 - did not get any responses..
.
>
> Any idea what legal values of this variable might be.  I want to set the n
ame
> of the pipeline for a dynamic file send port.  A search on the help refres
h
> shows nothing on this word "SendPipelineConfig" nor "BTS.SendPipelineConfi
g".
>
> I want to do something like this:
>   mymsg(BTS.SendPipelineConfig) = "xxxx"
> but what the heck is legal for "xxxx"?
> Is it the pipeline name?  Fully qualified assembly name?
> Why aren't these BTS. variables documents?  or are they?
>
> Thanks,
> Neal Walters
> http://Biztalk-Training.com - Free Biztalk 2004 Demos
>
>
>

[ Post a follow-up to this message ]

Right, the pipeline is associated statically even with the dynamic send
ports.

However you can control configuration of some pipeline components
dynamically from orchestration. For example to configure XML and Flat File
assemblers you can use the properties from the XMLNORM namespace. The
product documentation has description of those properties
(http://msdn.microsoft.com/library/d...n-us/sdk/htm/eb
iz_prog_pipe_izmc.asp).


--------------------
>Thread-Topic: Setting send pipeline of dynamic port in orchestration
>thread-index: AcThUrG6qE/x0YCwQbO0OiQpp27Fng==
>X-WBNR-Posting-Host: 162.136.192.1
>From: "examnotes"
<StephenWThomas@discussions.microsoft.com>
>References:  <AE7267DA-AB86-4759-AE4B-FC8D6DFC9932@microsoft.com>
>Subject: RE: Setting send pipeline of dynamic port in orchestration
>Date: Mon, 13 Dec 2004 12:31:15 -0800
>Lines: 40
>Message-ID: <FD4A304F-7A96-4622-A3FC-C70C79FF21AB@microsoft.com>
>MIME-Version: 1.0
>Content-Type: text/plain;
>	charset="Utf-8"
>Content-Transfer-Encoding: 8bit
>X-Newsreader: Microsoft CDO for Windows 2000
>Content-Class: urn:content-classes:message
>Importance: normal
>Priority: normal
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
>Newsgroups: microsoft.public.biztalk.orchestration
>NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.1.29
>Path:
cpmsftngxa10.phx.gbl!TK2MSFTNGXS01.phx.gbl!cpmsftngxa06.phx.gbl!TK2MSFTNGP08
.phx.gbl!TK2MSFTNGXA03.phx.gbl
>Xref: cpmsftngxa10.phx.gbl microsoft.public.biztalk.orchestration:9345
>X-Tomcat-NG: microsoft.public.biztalk.orchestration
>
>Hello.
>
>I think I looked into this a while back.  I saw the name as the fully
>qualified namespace name, but I did not think I was able to set this
property
>inside the Orchestration.  I think the pipeline is associated with a Port
and
>it can not be set dynamically.
>
>As an alternative, have you looked into using Role Links?  This would
allow
>for multiple send ports and pipelines.  Or, some stages of the pipelines
>allow for a first match processing.  Many this would allow a single
pipeline
>to process different types of messages?  Just some thoughts…
>
>Hope this helps.
>
>Stephen W. Thomas
>http://www.geekswithblogs.net/sthomas
>
>
>
>
>"Neal Walters" wrote:
> 
responses...[vbcol=seagreen] 
name[vbcol=seagreen] 
refresh[vbcol=seagreen] 
"BTS.SendPipelineConfig".[vbcol=seagreen] 
>

This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm

Note:  For the benefit of the community-at-large, all responses to this
message are best directed to the newsgroup/thread from which they
originated.

[ Post a follow-up to this message ]

Thanks, but here's my problem.  I have some two transmits that are failing i
f
I do not make the dynamic port a "pass thru" (one of them is an STMP email).

Since the ports are dynamic, everytime I recompile the orchestration, the
dynamic ports are rebuilt with the default values; thus after every single
recompile and deploy, I have to remember to change the two dynamic ports fro
m
XmlReceive back to PassThrough.  If a new programmer comes along, he or she
will also run into the same problem and spend probably way too much time
debugging...

Any ideas?

Thanks,
Neal Walters
http://Biztalk-Training.com - Free Biztalk 2004 Videos

[ Post a follow-up to this message ]

Did you know that you could specify the pipeline for the dynamic port in a
port configuration property directly in orchestration? This way every time
you recompile and re-deploy your orchestration the correct pipeline will be
used and you would not have to go to BTS explorer to re-set it.


--------------------
>Thread-Topic: Setting send pipeline of dynamic port in orchestration
>thread-index: AcTiFj+b8x9j2QDPTa66i0FgQebnWQ==
>X-WBNR-Posting-Host: 66.21.4.50
>From: examnotes <NealWalters@discussions.microsoft.com>
>References:  <AE7267DA-AB86-4759-AE4B-FC8D6DFC9932@microsoft.com>
<FD4A304F-7A96-4622-A3FC-C70C79FF21AB@microsoft.com>
<dz3b0QY4EHA.3984@cpmsftngxa10.phx.gbl>
>Subject: RE: Setting send pipeline of dynamic port in orchestration
>Date: Tue, 14 Dec 2004 11:51:05 -0800
>Lines: 16
>Message-ID: <FA2BABDF-E4E3-4A7C-BFD4-9EF8BB1BD90E@microsoft.com>
>MIME-Version: 1.0
>Content-Type: text/plain;
>	charset="Utf-8"
>Content-Transfer-Encoding: 7bit
>X-Newsreader: Microsoft CDO for Windows 2000
>Content-Class: urn:content-classes:message
>Importance: normal
>Priority: normal
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
>Newsgroups: microsoft.public.biztalk.orchestration
>NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.1.29
>Path: cpmsftngxa10.phx.gbl!TK2MSFTNGXA03.phx.gbl
>Xref: cpmsftngxa10.phx.gbl microsoft.public.biztalk.orchestration:9353
>X-Tomcat-NG: microsoft.public.biztalk.orchestration
>
>Thanks, but here's my problem.  I have some two transmits that are failing
if
>I do not make the dynamic port a "pass thru" (one of them is an STMP
email).
>
>Since the ports are dynamic, everytime I recompile the orchestration, the
>dynamic ports are rebuilt with the default values; thus after every single
>recompile and deploy, I have to remember to change the two dynamic ports
from
>XmlReceive back to PassThrough.  If a new programmer comes along, he or
she
>will also run into the same problem and spend probably way too much time
>debugging...
>
>Any ideas?
>
>Thanks,
>Neal Walters
>http://Biztalk-Training.com - Free Biztalk 2004 Videos
>
>

This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm

Note:  For the benefit of the community-at-large, all responses to this
message are best directed to the newsgroup/thread from which they
originated.

[ Post a follow-up to this message ]