- 3 minutes to read

Enlist action for Orchestrations

Discover how Nodinite empowers you to Enlist BizTalk Server Orchestrations quickly and efficiently using the intuitive Web Client or the powerful auto-healing feature. Streamline orchestration management and ensure your environment is always ready for business.

Unenlist and then Enlist an Orchestration from a Monitor View, animated walkthrough (6.4.2)
Animated walkthrough: from Enlisted (Warning), Unenlist turns the Orchestration Error, and Enlist brings it back to Enlisted (Warning); messages queue up until it is started.

From Monitor Views where you have access and where BizTalk Orchestrations are included and Remote Actions are allowed, you can use the Nodinite Web Client to Enlist selected BizTalk Server Orchestrations.

An Enlisted Orchestration can be Unenlisted, Stopped, or Started. There is no need to use the BizTalk Server Administration Console (MMC) for this administrative task.

Warning

Enlisting a BizTalk Orchestration means it will subscribe (stockpile) messages, but no message processing occurs until you start the Orchestration.

How do I Enlist an Orchestration?

To Enlist Orchestrations, you have several options with Nodinite:

  • Use the Action button menu item Enlist (as described on this page)
  • Use the Enlist button available from within the Details modal
  • Use the Auto healing feature – use with care!

To Enlist a BizTalk Server Orchestration, press the Action button menu item on the selected row and select Enlist:

Action menu of an Orchestration with the Enlist menu item (7.12)
Enlist Orchestration button menu item.

The user will be prompted to confirm the Enlist operation in the Execute action? dialog:
Execute action? confirmation for Enlist on the Orchestration Lab.Orders.i0100_Started (7.12)
Confirmation dialog when enlisting an Orchestration.

Then, the Action dialog shows the answer of the agent, Orchestration '(name)' set to Enlisted:
Action dialog with Orchestration Lab.Orders.i0100_Started set to Enlisted (7.12)
This image shows a successful enlist operation.

Note

A Stopped Orchestration is the same state as an Enlisted Orchestration.

If BizTalk refuses the Enlist, for example because no host is assigned, the Action dialog shows a short message with a CorrelationId instead. See Why can't I Enlist my Orchestration?

If Enlisted, the BizTalk Server Orchestration will be evaluated as being in the Warning state:
Enlisted Orchestration in Warning state with the Log Text Orchestration is enlisted/Stopped (7.12)
This image shows an Orchestration in the Enlisted (Warning) state.

Auto Healing

Nodinite can automatically issue the Enlist, Start, Stop, or Unenlist command for you. Learn more in the Auto Healing user guide. This feature helps keep selected BizTalk Server Orchestrations in the intended run-time state.

Tip

Using Auto Healing keeps your BizTalk environment in its intended state.


Frequently asked questions

Find additional solutions to common problems and the FAQ for the Nodinite BizTalk Monitoring Agent in the Troubleshooting user guide.

Why can't I Enlist my Orchestration?

  • The Orchestration must be in one of the following states:
    • Unenlisted
    • Started (in which case the Enlist operation is also a Stop operation)

Make sure to configure the Orchestrations first.

  • Bindings must be properly configured:

    • Host assigned
    • Port bindings set if applicable

    New 6.4.2 An Orchestration that is not bound shows a Log Text that names what is missing. See What is evaluated for BizTalk Orchestrations?

A refused action shows There is a problem to execute operation for '(name)' in category 'Orchestration'. … See diagnostics for details (CorrelationId: …), here for a refused Start:
Action dialog after a refused action on Lab.Orders.i0100_OrderFlow, with a CorrelationId and no BizTalk details (6.4.2)
Failed operation example: BizTalk's reason is in the agent's diagnostic files.

New 6.4.2 BizTalk's own reason is written only to the agent's diagnostic files, under that CorrelationId; search the files for it. The agent rolls the refused change back, so BizTalk management keeps working.

The Nodinite BizTalk Monitoring Agent cannot enlist Orchestrations that you cannot enlist from the BizTalk Server MMC either.

Note

Test the enlist operation from the BizTalk Server MMC if the operation fails using Nodinite.

Next Steps

Start
Stop
Unenlist
Details
Tracking

Monitor Views
Remote Actions