properties not being promoted

Trickymonk

I am struggling with promoted properties. I have 2 input schemas that I have
promoted (Quick Promotion) 2 properties from (1 from each). The property
schema was created with these properties listed. I rebuilt and deployed. I
have send ports that I'm trying to set filters on using these properties.
Both send ports are in a single send port group. I've managed to discover
that I have to set the filter on the send port group and not the individual
send ports since their filters will be ignored otherwise (is this correct?).
I've also set every receive location I have to the XMLReceive pipeline and my
send ports are set to XMLTransmit. Additionally, I set the PropertySchemaBase
to 'MessageDataPropertyBase' for each of the promoted fields in the property
schema (since they were both blank to begin with). Yet when I try routing on
my promoted properties I get: The published message could not be routed
because no subscribers were found....
Upon inspecting the message content of the failed message (using BT Admin) I
do NOT see my promoted properties. What am I missing?

Jan Eliasen

On Thu, 29 Nov 2007 07:00:01 -0800, Trickymonk
<> wrote:

>I am struggling with promoted properties. I have 2 input schemas that I have
>promoted (Quick Promotion) 2 properties from (1 from each). The property
>schema was created with these properties listed. I rebuilt and deployed. I
>have send ports that I'm trying to set filters on using these properties.
>Both send ports are in a single send port group. I've managed to discover
>that I have to set the filter on the send port group and not the individual
>send ports since their filters will be ignored otherwise (is this correct?).
Yes, that is correct. Sort of... When binding a send port group to an
orchestration, the message is sent from the orchestration through all
the send ports no matter what individual filter they have. But you can
still have filters on them, since they also act as a stand alone send
port. So you can have a send port that outputs toa f ile folder and
have the send port as a part of a send port group. You can then set
the filter to be BTS.ReceivePortName=="MyReceivePort". This way,
everything that comes in through that port AND everything that is sent
to the send port group goes through this send port.

>I've also set every receive location I have to the XMLReceive pipeline and my
>send ports are set to XMLTransmit. Additionally, I set the PropertySchemaBase
>to 'MessageDataPropertyBase' for each of the promoted fields in the property
>schema (since they were both blank to begin with). Yet when I try routing on
>my promoted properties I get: The published message could not be routed
>because no subscribers were found....
>Upon inspecting the message content of the failed message (using BT Admin) I
>do NOT see my promoted properties. What am I missing?
Sounds fishy. Have you restartet the host instance?

--
eliasen, representing himself and not the company he works for.

Private blog:

Private email:

Trickymonk

> Yes, that is correct. Sort of... When binding a send port group to an
> orchestration, the message is sent from the orchestration through all
> the send ports no matter what individual filter they have. But you can
> still have filters on them, since they also act as a stand alone send
> port. So you can have a send port that outputs toa f ile folder and
> have the send port as a part of a send port group. You can then set
> the filter to be BTS.ReceivePortName=="MyReceivePort". This way,
> everything that comes in through that port AND everything that is sent
> to the send port group goes through this send port.

Perhaps this is part of my issue. The send ports themselves have no filters.
The send port group has the filter BTS.ReceivePortName=="MyReceivePort" - so
both send ports receive the message. I have then been adding my promoted
properties to this filter. Both send ports DO output to a file folder. Would
it be better to remove the group and set each send port's filter individually?

> Sounds fishy. Have you restartet the host instance?
I have, several times. I've redeployed several times. The promoted
properties are available in the filter dropdown, they just don't appear in
the list of properties in the failed message. I'm using BTS2006 BTW.

"Jan Eliasen" wrote:

> On Thu, 29 Nov 2007 07:00:01 -0800, Trickymonk
> <> wrote:
>
> >I am struggling with promoted properties. I have 2 input schemas that I have
> >promoted (Quick Promotion) 2 properties from (1 from each). The property
> >schema was created with these properties listed. I rebuilt and deployed. I
> >have send ports that I'm trying to set filters on using these properties.
> >Both send ports are in a single send port group. I've managed to discover
> >that I have to set the filter on the send port group and not the individual
> >send ports since their filters will be ignored otherwise (is this correct?).
> Yes, that is correct. Sort of... When binding a send port group to an
> orchestration, the message is sent from the orchestration through all
> the send ports no matter what individual filter they have. But you can
> still have filters on them, since they also act as a stand alone send
> port. So you can have a send port that outputs toa f ile folder and
> have the send port as a part of a send port group. You can then set
> the filter to be BTS.ReceivePortName=="MyReceivePort". This way,
> everything that comes in through that port AND everything that is sent
> to the send port group goes through this send port.
>
> >I've also set every receive location I have to the XMLReceive pipeline and my
> >send ports are set to XMLTransmit. Additionally, I set the PropertySchemaBase
> >to 'MessageDataPropertyBase' for each of the promoted fields in the property
> >schema (since they were both blank to begin with). Yet when I try routing on
> >my promoted properties I get: The published message could not be routed
> >because no subscribers were found....
> >Upon inspecting the message content of the failed message (using BT Admin) I
> >do NOT see my promoted properties. What am I missing?
> Sounds fishy. Have you restartet the host instance?
>
> --
> eliasen, representing himself and not the company he works for.
>
> Private blog:
>
> Private email:
>

Trickymonk

I am at a complete dead end on this. I tried pulling one of the send ports
out of the send group and assigning the receive port and promoted property
filters to it, but then that send port didn't get any messages routed to it
(even though it subscribed to the same receive filter as the group).

Do the send ports have to be directly bound to an orchestration to use
promoted properties? I have a receive port/location that picks up XML files
from a file folder. My send port group (the one I've been trying to add my
promoted property filter to)then subscribes to this through the
BTS.ReceivePortName filter. One of the send ports in the group then places
the file in another folder where a receive location within my orchestration
picks it up.

Any help is greatly appreciated!

"Trickymonk" wrote:

> I am struggling with promoted properties. I have 2 input schemas that I have
> promoted (Quick Promotion) 2 properties from (1 from each). The property
> schema was created with these properties listed. I rebuilt and deployed. I
> have send ports that I'm trying to set filters on using these properties.
> Both send ports are in a single send port group. I've managed to discover
> that I have to set the filter on the send port group and not the individual
> send ports since their filters will be ignored otherwise (is this correct?).
> I've also set every receive location I have to the XMLReceive pipeline and my
> send ports are set to XMLTransmit. Additionally, I set the PropertySchemaBase
> to 'MessageDataPropertyBase' for each of the promoted fields in the property
> schema (since they were both blank to begin with). Yet when I try routing on
> my promoted properties I get: The published message could not be routed
> because no subscribers were found....
> Upon inspecting the message content of the failed message (using BT Admin) I
> do NOT see my promoted properties. What am I missing?

Jan Eliasen

On Thu, 29 Nov 2007 07:00:01 -0800, Trickymonk
<> wrote:

>I am struggling with promoted properties. I have 2 input schemas that I have
>promoted (Quick Promotion) 2 properties from (1 from each). The property
>schema was created with these properties listed. I rebuilt and deployed. I
>have send ports that I'm trying to set filters on using these properties.
>Both send ports are in a single send port group. I've managed to discover
>that I have to set the filter on the send port group and not the individual
>send ports since their filters will be ignored otherwise (is this correct?).
Yes, that is correct. Sort of... When binding a send port group to an
orchestration, the message is sent from the orchestration through all
the send ports no matter what individual filter they have. But you can
still have filters on them, since they also act as a stand alone send
port. So you can have a send port that outputs toa f ile folder and
have the send port as a part of a send port group. You can then set
the filter to be BTS.ReceivePortName=="MyReceivePort". This way,
everything that comes in through that port AND everything that is sent
to the send port group goes through this send port.

>I've also set every receive location I have to the XMLReceive pipeline and my
>send ports are set to XMLTransmit. Additionally, I set the PropertySchemaBase
>to 'MessageDataPropertyBase' for each of the promoted fields in the property
>schema (since they were both blank to begin with). Yet when I try routing on
>my promoted properties I get: The published message could not be routed
>because no subscribers were found....
>Upon inspecting the message content of the failed message (using BT Admin) I
>do NOT see my promoted properties. What am I missing?
Sounds fishy. Have you restartet the host instance?

--
eliasen, representing himself and not the company he works for.

Private blog:

Private email:

Trickymonk

> Yes, that is correct. Sort of... When binding a send port group to an
> orchestration, the message is sent from the orchestration through all
> the send ports no matter what individual filter they have. But you can
> still have filters on them, since they also act as a stand alone send
> port. So you can have a send port that outputs toa f ile folder and
> have the send port as a part of a send port group. You can then set
> the filter to be BTS.ReceivePortName=="MyReceivePort". This way,
> everything that comes in through that port AND everything that is sent
> to the send port group goes through this send port.

Perhaps this is part of my issue. The send ports themselves have no filters.
The send port group has the filter BTS.ReceivePortName=="MyReceivePort" - so
both send ports receive the message. I have then been adding my promoted
properties to this filter. Both send ports DO output to a file folder. Would
it be better to remove the group and set each send port's filter individually?

> Sounds fishy. Have you restartet the host instance?
I have, several times. I've redeployed several times. The promoted
properties are available in the filter dropdown, they just don't appear in
the list of properties in the failed message. I'm using BTS2006 BTW.

"Jan Eliasen" wrote:

> On Thu, 29 Nov 2007 07:00:01 -0800, Trickymonk
> <> wrote:
>
> >I am struggling with promoted properties. I have 2 input schemas that I have
> >promoted (Quick Promotion) 2 properties from (1 from each). The property
> >schema was created with these properties listed. I rebuilt and deployed. I
> >have send ports that I'm trying to set filters on using these properties.
> >Both send ports are in a single send port group. I've managed to discover
> >that I have to set the filter on the send port group and not the individual
> >send ports since their filters will be ignored otherwise (is this correct?).
> Yes, that is correct. Sort of... When binding a send port group to an
> orchestration, the message is sent from the orchestration through all
> the send ports no matter what individual filter they have. But you can
> still have filters on them, since they also act as a stand alone send
> port. So you can have a send port that outputs toa f ile folder and
> have the send port as a part of a send port group. You can then set
> the filter to be BTS.ReceivePortName=="MyReceivePort". This way,
> everything that comes in through that port AND everything that is sent
> to the send port group goes through this send port.
>
> >I've also set every receive location I have to the XMLReceive pipeline and my
> >send ports are set to XMLTransmit. Additionally, I set the PropertySchemaBase
> >to 'MessageDataPropertyBase' for each of the promoted fields in the property
> >schema (since they were both blank to begin with). Yet when I try routing on
> >my promoted properties I get: The published message could not be routed
> >because no subscribers were found....
> >Upon inspecting the message content of the failed message (using BT Admin) I
> >do NOT see my promoted properties. What am I missing?
> Sounds fishy. Have you restartet the host instance?
>
> --
> eliasen, representing himself and not the company he works for.
>
> Private blog:
>
> Private email:
>

Trickymonk

I am at a complete dead end on this. I tried pulling one of the send ports
out of the send group and assigning the receive port and promoted property
filters to it, but then that send port didn't get any messages routed to it
(even though it subscribed to the same receive filter as the group).

Do the send ports have to be directly bound to an orchestration to use
promoted properties? I have a receive port/location that picks up XML files
from a file folder. My send port group (the one I've been trying to add my
promoted property filter to)then subscribes to this through the
BTS.ReceivePortName filter. One of the send ports in the group then places
the file in another folder where a receive location within my orchestration
picks it up.

Any help is greatly appreciated!

"Trickymonk" wrote:

> I am struggling with promoted properties. I have 2 input schemas that I have
> promoted (Quick Promotion) 2 properties from (1 from each). The property
> schema was created with these properties listed. I rebuilt and deployed. I
> have send ports that I'm trying to set filters on using these properties.
> Both send ports are in a single send port group. I've managed to discover
> that I have to set the filter on the send port group and not the individual
> send ports since their filters will be ignored otherwise (is this correct?).
> I've also set every receive location I have to the XMLReceive pipeline and my
> send ports are set to XMLTransmit. Additionally, I set the PropertySchemaBase
> to 'MessageDataPropertyBase' for each of the promoted fields in the property
> schema (since they were both blank to begin with). Yet when I try routing on
> my promoted properties I get: The published message could not be routed
> because no subscribers were found....
> Upon inspecting the message content of the failed message (using BT Admin) I
> do NOT see my promoted properties. What am I missing?

Jan Eliasen

On Fri, 30 Nov 2007 14:19:07 -0800, Trickymonk
<> wrote:

>Do the send ports have to be directly bound to an orchestration to use
>promoted properties? I have a receive port/location that picks up XML files
>from a file folder. My send port group (the one I've been trying to add my
>promoted property filter to)then subscribes to this through the
>BTS.ReceivePortName filter. One of the send ports in the group then places
>the file in another folder where a receive location within my orchestration
>picks it up.
Well...

This is starting to be a bit tricky.

Let me just make sure I understand the issue:
You have promoted properties from your schemas, but when you view the
messages in HAT, they do not appear to have the properties in the
context, right?

If you unenelist the send ports, the messages will definately fail,
because of no subscribers. Take a look at the non-resumable message
that can be found in group hub page. The resumable one doesn't have
the properties promoted yet. But the non-resumable one should have.
This is just to make sure that you looked at the right message.

Also, note that the filters in the send ports do not support writing
BTS.ReceivePortName== "theportname" - I mean - you are not supposed to
write the quotes in the value-field. This is only for when entering
filters on reeive shapes inside an orchestration.

--
eliasen, representing himself and not the company he works for.

Private blog:

Private email:

Trickymonk

I have 2 schemas that correspond to XML files I receive from 2 external
sources. These files are picked up by 2 separate receive ports (both set to
XML receive). I have 4 send ports in 2 send port groups (2 in each group)
that subscribe to these receive ports (and no, I don't have quotes around the
value for BTS.ReceivePortName). I am trying to place the promoted properties
filter on these send port groups. These send ports place the files in a file
directory where they are picked up by a receive port bound to an
orchestration. The orchestration decides what type of message it is and uses
the appropriate map to convert to a flat file/csv schema for output. I use
another send port bound to the orchestration to place the output csv files in
a file directory where they are picked up by a non-BizTalk external process.

The only place I am looking for the promoted values is in the non-resumable
messages on the group hub page. Whenever I insert the filter for the promoted
values, messages start failing. When I look at the context for the
non-resumable messages I do not see the promoted values. How do I view the
messages in HAT?

"Jan Eliasen" wrote:

> On Fri, 30 Nov 2007 14:19:07 -0800, Trickymonk
> <> wrote:
>
> >Do the send ports have to be directly bound to an orchestration to use
> >promoted properties? I have a receive port/location that picks up XML files
> >from a file folder. My send port group (the one I've been trying to add my
> >promoted property filter to)then subscribes to this through the
> >BTS.ReceivePortName filter. One of the send ports in the group then places
> >the file in another folder where a receive location within my orchestration
> >picks it up.
> Well...
>
> This is starting to be a bit tricky.
>
> Let me just make sure I understand the issue:
> You have promoted properties from your schemas, but when you view the
> messages in HAT, they do not appear to have the properties in the
> context, right?
>
> If you unenelist the send ports, the messages will definately fail,
> because of no subscribers. Take a look at the non-resumable message
> that can be found in group hub page. The resumable one doesn't have
> the properties promoted yet. But the non-resumable one should have.
> This is just to make sure that you looked at the right message.
>
> Also, note that the filters in the send ports do not support writing
> BTS.ReceivePortName== "theportname" - I mean - you are not supposed to
> write the quotes in the value-field. This is only for when entering
> filters on reeive shapes inside an orchestration.
>
> --
> eliasen, representing himself and not the company he works for.
>
> Private blog:
>
> Private email:
>

Jan Eliasen

On Mon, 3 Dec 2007 06:35:00 -0800, Trickymonk
<> wrote:

>I have 2 schemas that correspond to XML files I receive from 2 external
>sources. These files are picked up by 2 separate receive ports (both set to
>XML receive). I have 4 send ports in 2 send port groups (2 in each group)
>that subscribe to these receive ports (and no, I don't have quotes around the
>value for BTS.ReceivePortName). I am trying to place the promoted properties
>filter on these send port groups. These send ports place the files in a file
>directory where they are picked up by a receive port bound to an
>orchestration. The orchestration decides what type of message it is and uses
>the appropriate map to convert to a flat file/csv schema for output. I use
>another send port bound to the orchestration to place the output csv files in
>a file directory where they are picked up by a non-BizTalk external process.
>
>The only place I am looking for the promoted values is in the non-resumable
>messages on the group hub page. Whenever I insert the filter for the promoted
>values, messages start failing. When I look at the context for the
>non-resumable messages I do not see the promoted values. How do I view the
>messages in HAT?
Sorry about the late answer...

You don't see them in HAT if they are suspended. They will stay in the
MessageBox until they are terminated or completed.

Anyway, it is difficult to come up with answers... Can you export an
MSI of your solution and send to me? I will import it and take a look
at it.

--
eliasen, representing himself and not the company he works for.

Private blog:

Private email: