BizTalk Server has many artifacts such as send ports, send port groups, receive locations, parties, and orchestrations. Of the artifacts, send ports, send port groups, and orchestrations have a state, which determines whether the artifact can process messages.
We have four variants with messages received by adapter :
1). After Subscriber is Enlisted and Started, the messages come to the Message box and then routed to the Subscriber.
2). After Subscriber is Enlisted but not Started yet, the messages are waiting inside Message box in the Suspended (Resumable) state. When Subscriber is started, those messages go out from Message box to this Subscriber.
3). If the Subscriber is not Enlisted, and the message type in well-known by BizTalk, we'll get error
Description:
The Messaging engine failed to process a message submitted by adapter:{adapter details}. Details:Could not find a matching subscription for the message. This error occurs if the subscribed orchestration schedule or send port has not been started, or if some of the message properties necessary for subscription evaluation have not been promoted. Please refer to Health and Activity Tracking tool for more detailed information on this failure
It means the message was recognized by BizTalk, because BizTalk knows of its type. But there is no one subscription to this message.
UnEnlist:- Remove subscription information from Message Box.
Stop:-Will not Remove Subscription information form message box but the port or orchestration will not process(send) messages.
Enlist:-Write Subscription information into message Box(Bound).
Start:-Process(send) messages.
Don't confuse with Stop and Enlist
the "Stop" changes the state from "Started" to "Stopped/Enlisted".
the Enlist will move from Unenlisted to "Stopped/Enlisted" state.
Ex:
you have a mailbox at the local post office. When you go out of town on vacation, you drop from the "Started" to the "Enlisted" state. They hold your mail for you, and when you return, they give you the box full of mail. When you move out of town (or are tired of all the junk mail), you "Stop" your mail and they post master marks it as undeliverable.
We have four variants with messages received by adapter :
1). After Subscriber is Enlisted and Started, the messages come to the Message box and then routed to the Subscriber.
2). After Subscriber is Enlisted but not Started yet, the messages are waiting inside Message box in the Suspended (Resumable) state. When Subscriber is started, those messages go out from Message box to this Subscriber.
3). If the Subscriber is not Enlisted, and the message type in well-known by BizTalk, we'll get error
Description:
The Messaging engine failed to process a message submitted by adapter:{adapter details}. Details:Could not find a matching subscription for the message. This error occurs if the subscribed orchestration schedule or send port has not been started, or if some of the message properties necessary for subscription evaluation have not been promoted. Please refer to Health and Activity Tracking tool for more detailed information on this failure
It means the message was recognized by BizTalk, because BizTalk knows of its type. But there is no one subscription to this message.
UnEnlist:- Remove subscription information from Message Box.
Stop:-Will not Remove Subscription information form message box but the port or orchestration will not process(send) messages.
Enlist:-Write Subscription information into message Box(Bound).
Start:-Process(send) messages.
Don't confuse with Stop and Enlist
the "Stop" changes the state from "Started" to "Stopped/Enlisted".
the Enlist will move from Unenlisted to "Stopped/Enlisted" state.
Ex:
you have a mailbox at the local post office. When you go out of town on vacation, you drop from the "Started" to the "Enlisted" state. They hold your mail for you, and when you return, they give you the box full of mail. When you move out of town (or are tired of all the junk mail), you "Stop" your mail and they post master marks it as undeliverable.
No comments:
Post a Comment