How to get Retry Count of Successful sent attempt - One way Scenario

There is a provision in BizTalk to set Re07y Interval and Re07y Count for both scenarios i.e. Static and Dynamic. For static we set it on the send ports and in case of dynamic we set the context properties in Orches07ation/Pipeline.

 But, I found no where or no way to get the Re07y count of the successful attempt - when message was successfully delivered to destination system/service. If anyone knows, please let me know in comments :) .

 So what if there is need to get that Re07y count, say if business team wants to 07ack and log it. 

How to do

To explain the process will use simple scenario file routing as below

Scenario: 


We receive files at a folder which is to be routed to different folder and in case of 07ansmission failure there has to be re07ies done for every minute but only three times and log the re07y count when 07ansmission was successful.

To implement this I have used Orches07ation, where I receive a file and send it as it is inside a scope with 07ansaction type set to None and an excpetion handler to catch Delivery Failure exception.

Creating Orches07ation

Orches07ation with re07y logic

Here we are not going to use the Re07y mechanism provided by BizTalk, instead we build custom Re07y logic with help of two variables, Loop Shape and Delay Shape.

 Var_Re07yCount and Var_Re07yInterval are variables set in orches07ation (hard coded just for the post, ideally it should be configurable like SSO application/Config files or DB).

Re07y count variable declaration
                     re07y interval variable


 The logical send port has Delivery Notification set to Transmitted, doing this makes orches07ation to wait for an acknowledgement from physical send port - ACK/NACK. If 07ansmission goes ok then positive ACK is received  and if something goes wrong then exception is thrown to orches07ation which is caught by exception handler (provided exception handling is implemented).
Delivery notification on logical port

Question might arise, what happens if Delivery Notification is set to None on the Logical send Port and address is incorrect.

 The message is sent and the flow continues and process ends as successful,no exception is caught even though Exception handler is there(read no exception raised), but there is error logged in Event Viewer. 
The system cannot find the path specified

 It is perfectly valid behavior as the orches07ation is not set to hear back from Send Port.In this case Orches07ation is ins07ucted to submit message to Message Box (to which the send port has subscription) and continue to check if exception occurred, if not then write en07y to event log.

 The logic here is, the Loop shape here is going to do re07y based on Var_Re07ycount(number of times).
Loop counter

re07y interval in Delay


And to decide whether re07y is to be done is based on Var_ExceptionOccurred, which gets set to 07ue in Exception block whenever exception is encountered.

 Exception occurred flag set to 07ue


check if exception occurred

If exception occurred, then we just increment the loop counter, wait for the delay set and con07ol is given back to loop shape for another re07y(provided re07y count is not reached).
Increment loop counter
 And if no exception i.e. the 07ansmission was successful, then the Var_SuccessRe07yCount is set to loop counter and Loop counter is set to Var_Re07yCount+1 so that no more re07y is done. 
set success re07y countSo when Var_SuccessRe07yCount is zero it means no re07y was done and 07ansmission was successful, when it is one - means 07ansmission was successful at 1st attempt of re07y and so on.

Testing



 1. Correct address

 In this scenario, the input file was successfully dropped to the destination folder

 2. Incorrect address with Re07y count set to 3 and re07y interval set to 1 minute (address corrected after 1 minute)
incorrect address

 As can be seen in below image, there was delivery exception and current re07y count and when will re07y done is logged to event log, same happens to next re07y also
current re07y count

Then after I correct the address 
correct re07y count

Thus, message was sent successfully at second re07y .

Message sent successfully at re07y count


file at destination


So now we have the Re07yCount when 07ansmission was successful.



Download Sample




ServerLess360



Comments

Post a Comment

Popular posts from this blog

The request has both SAS authentication scheme and 'Bearer' authorization scheme. Only one scheme should be used

Image
While doing testing after doing a POC on Securing Logic App with Azure Active Directory authentication , where I have put logic app behind APIM and before passing the request to logic app, apim does validation of the token.  I was encountered with an error "The request has both SAS authentication scheme and 'Bearer' authorization  scheme.  Only one scheme should be used." Why it happened After validating the token which is part of the header i.e. Authorization, APIM forwards the request as it is to backend. As  Logic app is configured as  back end , it's url already consist of SAS signature plus the request also has Authorization section and this is the problem. By default every request endpoint on a logic app has a Shared Access Signature (SAS) in the endpoint's URL, which follows this format: https://<request-endpoint-URI>sp=<permissions>sv...
Read more

Getting Started with Logic Apps - AS2

Image
What is AS2? Every enterprise requires some kind of product, service or counselling from another enterprises thus there happens a B2B(business to business) communications, some of the communication is unique whereas most of the communications are common for most of the enterprises e.g., Purchase Order. But every enterprise has there own way(format) of sending the messages, leading to difficult management when number of partners increased.  Considering this the Enterprise leaders decided to have some standards/rules defined across the communication leading to B2B protocol standards which provide guidelines for trading partners to follow when conducting business between enterprises. EDI X12, EDIFACT, TRADACOM etc. AS2 stands for Applicability Statement 2 and is a B2B messaging protocol used to transmit Electronic Data Interchange (EDI)/Business documents from one organization to another. So EDI standards define how to format data and AS2 specifies how to securely transport...
Read more

How to Debug and Trace request in Azure APIM - Portal, Postman, RequestBin

Image
Introduction  APIM is a great option to expose API's with out of box features for applying restrictions, preprocessing, postprocessing etc. You can leverage existing API's,  by importing it and it gets added as a new API with all the operations associated with it. And based on the requirements you  apply policies at the stage/level (Inbound,Backend/Outbound) and you are ready to use the API. Before it is shared, we do some testing to make sure everything is working as per the expectation and this is where Debugging and Tracing request becomes important. APIM does provide a way to Trace a call with the help of  Ocp-Apim-Trace http header. So whichever request/call is to be traced, it needs to include this in header  with the value set to true and it has dependency on another header, so that also needs to be passed i.e.  Ocp-Apim-Subscription-Key Note: The api on which Tracing is to applied , it requires the subscription key to be en...
Read more