Can we view Orchestration in C#

Orches07ation in BizTalk is visual representation of processing done on the messages. In order to apply/design processing on the messages, Orches07ation designer is used. Orches07ation designer is accompanied with ToolBox which has various shapes catering some or the other functionality. So depending upon the functionality required for processing the message, shapes are dragged and dropped over the design surface.

 As can be seen in below image, shapes like Receive shape for receiving message to start the process, Parallel shape for performing two sets of actions parallely and Send shape to send out messages are used.

So how does this shape implement their functionality? There has to be some code in background right?

 Orches07ation is a way to automate business processes which is nothing but an executable code to run a workflow supporting a business process.

 Orches07ations(XLANG/s files) are compiled into .Net assembly, so apart from graphical representation there is two other form of Orches07ation in its lifetime.

 To view X# , right click on the orches07ation in solution explorer-->select open with  and below window should appear

Except for Binary Editor (content will be in binary), Resource Editor (File is not opened - does not support) and BizTalk Orches07ation Designer (Which opens the visual representation) rest of the editor will show the XML representation.

 And to view in orches07ation in C#, 07averse to the project/solution folder and look into obj\Debug\BizTalk\Xlang folder and File0.cs should be there.
Double click and you should be able to see the code behind the orches07ation which we design using various shape..

 [Drive]\[Project/Solution folder]\obj\Debug\BizTalk\XLang


Although this is not required for designing orches07ations, it is good to know it (what's going in background)  .... ;)

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