Biztalk Functoid

The orchestration engine saves the state of a running orchestration instance at various points. If it needs to rehydrate the orchestration instance, start up from a controlled shutdown, or recover from an unexpected shutdown, it will run the orchestration instance from the last persistence point, as though nothing else had occurred

☛ 1. Different Stages in Receive and Send Pipelines.

☛ 2. How to develop a Custom Pipeline Component ?

☛ 3. What are the various interfaces implemented for General, Disassemble/Assemble components ?

☛ 4. How do you promote a property in pipelines ?

☛ 5. How do you debug a Pipeline ?

☛ 6. How do you validate an XML in a pipeline ?

Structure

Custom functiods can be integrated into a solution using two ways (in both BizTalk.BaseFunctoid is derived):

☛ Directly by using inline code

☛ Indirectly by reference to a method in a class library deployed into the global assembly cache.

There are 9 categories available in Toolbox viz.,

☛ Advanced

☛ Conversion

☛ Cumulative

☛ Database

☛ Date and Time

☛ Logical

☛ Mathematical

☛ Scientific

☛ String

Below scenarios can tempt developer to create custom functoid:

☛ When there is no out of box functoids which can be used to complete the logic.

☛ When the number of functoids used to implement the logic goes on increasing and becomes difficult to follow and manage.

Biztalk provides you with a really smart routing feature that allows the engine to decide where to send which message. For example, If you receive a message with the EmployeePaySlip schema, and it has the approved flag to true, it should be redirected to the Finance system Orchestration for making the payments and to the HR system Orchestration for keeping the records. This built in intelligence for the Biztalk engine allows it to route the messages simply based on some content within the messages.

Custom code or custom scripts can be added .

When a message is received, or else when a timeout has expired, the orchestration engine can be automatically triggered to rehydrate the instance – it is at this point that the orchestration engine loads the saved instance of the orchestration into memory, restores the state, and runs its from the point it left off.