Authentication Options for a Receive Port
Keep messages if authentication fails. If this option is selected, the receive port will check
message credentials using Party resolution and keep the message in the suspended queue if authentication fails.
the persistence points in the orchestrations
End of a transactional scope (atomic or long running)
At the execution of other orchestrations through the Start Orchestration shape
At the Send shape (except in an atomic transaction)
At the end of the orchestration
Apart from that, the engine might decide to persist the orchestration in the following cases -
When an Orchestration Instance is suspended
When the system shutdowns in a controlled manner
When the engine determines it wants to dehydrate
When an orchestration instance is finished
Consuming webservices from within BizTalk
http://blogs.msdn.com/sanket/archive/2007/03/31/consuming-webservices-from-within-biztalk.aspx
with authentication
Filter Expression in Receive Shape
schema versioning
biz group
group hub
for resumable instances
port binding
self-correlating
BAM:
steps
BRE:
Monday, November 19, 2007
Saturday, November 17, 2007
biztalk patterns
Parallel Receive
Condition: you wait for all the messages to come into your business process before the processing starts. Example: If you need to process something after receiving quotation (message) from all your manufacturers.
Key steps in your orchestration
* Drop Parallel action with 2 or more Receive shapes in the beginning.
* Activate = True in all the receive shapes
* Initializing Correlation Sets = "somecorrelationset" in all the receive shapes. (You need to define a correlation set with an element unique across all the messages you receive).
Sequential Receive
Condition: Either you receive same type or different type of message one after the other; you need to wait until you receive some kind of control message to say "That's the end", or keep receiving n number of messages.
Key steps in your orchestration
* Set Activate = True in the first Receive Shape, Initializing Correlation Sets = somecorrelationset (You need to define a correlation set with an element unique across all the messages you receive).
* Set Activate = False in the following receive shapes, Following Correlation Sets = somecorrelationset, and
* Put a Loop across Receive shape. Terminate the loop based on your condition either after receiving n number of messages or after receiving the control message.
Condition: you wait for all the messages to come into your business process before the processing starts. Example: If you need to process something after receiving quotation (message) from all your manufacturers.
Key steps in your orchestration
* Drop Parallel action with 2 or more Receive shapes in the beginning.
* Activate = True in all the receive shapes
* Initializing Correlation Sets = "somecorrelationset" in all the receive shapes. (You need to define a correlation set with an element unique across all the messages you receive).
Sequential Receive
Condition: Either you receive same type or different type of message one after the other; you need to wait until you receive some kind of control message to say "That's the end", or keep receiving n number of messages.
Key steps in your orchestration
* Set Activate = True in the first Receive Shape, Initializing Correlation Sets = somecorrelationset (You need to define a correlation set with an element unique across all the messages you receive).
* Set Activate = False in the following receive shapes, Following Correlation Sets = somecorrelationset, and
* Put a Loop across Receive shape. Terminate the loop based on your condition either after receiving n number of messages or after receiving the control message.
Subscribe to:
Posts (Atom)
