Send Port Filter on Promoted Property

Home Page Forums BizTalk 2004 – BizTalk 2010 Send Port Filter on Promoted Property

Viewing 1 reply thread
  • Author
    Posts
    • #25076

      Hello,

      I am trying to route the messages based on the content in the messages.
      This is what I have

      1)     
      Schema has a root of “MsgRootTestNew” and 2 elements
      Source, Destination

      2)     
      Source is a promoted (using quick
      promotion)

      3)     
      Added a target namespace of http://Schema.TestSchema root of “MsgRootTestNew” with assembly name of “Schema”

      4)     
      Assigned SN key and deployed
      schema and property schema on to BTS

      5)     
      I have send port with
      transport type of File Port and pipeline as XMLtransmit

      6)     
      I added a filter Schema.Destination == ABC

      7)     
      I drop below test XML,

      <MsgRootTestNew xmlns=”http://Schema.TestSchema”&gt;

       
      <Source>SOmeAPP</Source>

        <Destination>ABC</Destination>

      </MsgRootTestNew>

      8)     
      I get an error

      A
      message received by adapter “FILE” on receive location “POCDynamicRouting_File”
      with URI “C:\POC\PipelineTest\Input\*.xml” is suspended.

       Error details: The published message could not
      be routed because no subscribers were found. This error occurs if the
      subscribing orchestration or send port has not been enlisted, or if some of the
      message properties necessary for subscription evaluation have not been
      promoted. Please use the Biztalk Administration console to troubleshoot this
      failure. 

      If
      I remove the Schema.Destination == ABC 
      and
      set the filter on the BTS.ReceivePortName == MyPortName
      property, Works just fine.

      Any
      thoughts?

      Any help is appreciated..

      Thanks

      Kote

       

       

    • #25077

      Are you using a property schema for promotion or a distinguished field.
      You need to have a property schema with Source and Destination properties defined.
      In your schema promote the Source and Destination fields to the appropriate properties. Do not use distinguished fields as these cannot be used for routing.

      If the message fails with a Routing error then you need to check the message context to see if your “Schema.Destination” property is promoted

      • #25078

        Thanks for the reply.

        Yes, I have created a message schema and a  property Schema in my project. Then I created property promotion by doing quick promotion and verified  that promotion appears in the Property Schema.  Both these schema files were deployed.

        When I see the message context, I do NOT  see Schema.Destination promoted.  

        On the receive side I have a tried both using the XMLReceive and custom pipeline with XML Disassembler defined. 

        I am not using the distinguished fields.  

        Thanks

        Kote

         

        • #25079

          All I can suggest is a rebuild, redeploy and restarting the Host Instances and retesting.

          If this does not work are you able to email me your schema and properties schema to greg.forsythe at gmail.com 

Viewing 1 reply thread
  • The forum ‘BizTalk 2004 – BizTalk 2010’ is closed to new topics and replies.