Re: Acks and Nacks over Request-Response port

Supplementary questions - I have Orchestrations that subscribe to a few
accepted message types. How can I subscribe to messages which turn out not
to
belong to any of these but flow through the same receive port?

With regards to this, you can have a send port subscribe to messages that do
not get picked up from the orchestration. By having a filter that has a
statement that looks like: BTS.MessageType != xyz and BTS.MessageType !=abc,
and BTS.ReceivePortName = "MY ReceivePort"

This will send anything that is NOT of these particular message types to the
send port, very useful for filtering out stuff you do not support. You DO
need to ensure that the schema for ALL messages you are receiving exists in
BizTalk, even if you do not use them. As BizTalk will need to match the
message type so the filter works.


"CodeDigger" <CodeDigger@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:AC476AB7-2198-494F-B108-A0618B90BA80@xxxxxxxxxxxxxxxx
Our Biztalk installation is on a remote box and hence the protocol is
Http.
Hence to send back Acks or Nacks to the message sending party, we have
configured 2-way Request-Response ports (the senders URI may vary).

In this scenario I need to send Acks or Nacks if the message was bad
/transmission did not succeed/wrong message type/bad message part/etc.

I have read Kevin Smith's blog entry on Acks or Nacks for one-way ports

http://blogs.msdn.com/kevinsmi/archive/2004/07/03/172574.aspx

Also tried out the sample from Stephen w Thomas.
http://www.geekswithblogs.net/sthomas/archive/2004/08/02/9234.aspx

However these both work with one-way ports and file adapters where the
send
URI is known. How can I effect this for a 2-way Request-Response port?

Supplementary questions - I have Orchestrations that subscribe to a few
accepted message types. How can I subscribe to messages which turn out not
to
belong to any of these but flow through the same receive port?


.

Relevant Pages

  • Re: Problem with web services
    ... message types are different. ... Verify the type of the message sent and the type accepted by the port are ... target namespace of the schema itself. ... Then I implemented the methods in an ASP.net web service asmx file. ...
    (microsoft.public.biztalk.general)
  • Send Port Order of Operations - Document Mapping Error
    ... I have a scenario where I have an orchestration (used as a convoy to ... message types to be handled by the same orchestration both inbound and ... logical send port to the physical send port. ... I have configured multiple maps to be applied (so that each ...
    (microsoft.public.biztalk.general)
  • RE: one message type = one receive location = one orchestration ?
    ... Disabling schema verification is only required if each schema is not ... Do you need to map each message on the Receive Port? ... Receive ports can support multiple maps. ... > need to be invoked for different message types. ...
    (microsoft.public.biztalk.general)
  • Send Port Order of Operations - Document Mapping Error 2
    ... adding a second receive port/location and send port which picks up the ... configured on the send port which is tied to the orchestration. ... not the same (as the map is correctly applied during the second send ... message types to be handled by the same orchestration both inbound and ...
    (microsoft.public.biztalk.general)
  • Re: Problem connecting send to port for SQL insert
    ... I was able to connect the Send and the Port and build. ... used the automatically created multipart message types for the ... I don't understand why VS needs to create an orchestration for what seems ...
    (microsoft.public.biztalk.general)
Loading