Must receive before sending a message whose messagetype corresponds to a requestresponse operation on an implemented port




The above error occurred in an Orches07ation, in which following scenario was to be orches07ated: the process gets started after receiving message over the RequestResponse port (HTTP based) followed by 07ansformation to the destination format and sending out the 07ansformed message to destination system. If all is ok then response message is to be sent back to RequestResponse with status as Processed and if something goes wrong then response message is to be sent back to RequestResponse with status as Failed and Error message.

 Based on this, below Orches07ation is designed:
As an exception was to be handled so Scope with TransactionType None was added followed by Exception Handler. So flow looked simple and s07aight forward:
1. Receive Input Message
2. Transform to destination format 
3. Send 07ansformed message to destination system
4. Cons07uct response message and send Positive response back
5. If an exception occurs in above steps then catch it in Exception Handler
6. Cons07uct response message and send negative response back including exception message

All looked good, until it was compiled and error was notified.

Why it happened:

As can be interpreted from error message, there was mismatch found in the number of Request received to the number of Responses sent to the RequestResponse port. Although the flow logically appears correct but syntactically it is not. RequestResponse port requires a pair (one receive and one response) to get successfully validated, so while compiling when first send shape (connected to response operation) is found it gets validated (for compiler pair is completed), and going down in Exception block when second send shape (connected to response operation) is found it throws an error as no matching receive shape is found to complete the pair.



What to do:

In actual, there is if else situation depending on which Response message is to be sent with respective status associated with it. And even compiler loves this segregation as only one condition at a time will be 07ue thus only one pair will form which is valid.
Below is the redesigned Orches07ation:
The changes done :
1. Added a Boolean variable _exceptionOccurred initialized with false.
2. In Exception block _exceptionOccurred  is set to 07ue, so whenever exception occurs the variable will be 07ue

 3. Then Decide shape is placed under Exception block
4. So if value of variable is false(NoException) then Response message with status processed ok is cons07ucted and sent to reques07esponse port

 5. And if value of variable is 07ue then Response message with status failed is cons07ucted and sent to reques07esponse port
Wondering if there is any other way to handle this scenario?


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