Stop action for Orchestration
Discover how you can quickly and securely stop BizTalk Server Orchestrations using the intuitive Nodinite Web Client. Take full control of your integration landscape with just a few clicks!
Animated walkthrough: Stop sets the Started Orchestration to Enlisted (Warning), and Start brings it back to OK.
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 Stop selected BizTalk Server Orchestrations.
After you stop a BizTalk Server Orchestration, you can later Start it to resume message routing and orchestration processing. For details on starting an orchestration, see How to Start a Orchestration.
Warning
A stopped Orchestration still subscribes to messages. They queue until you Start it again. Only Unenlist removes the subscriptions.
New 6.4.2 Stop keeps the Orchestration enlisted. Before BizTalk Monitoring Agent 6.4.2, Stop unenlisted the Orchestration, the same as Unenlist: the Orchestration went to Error, and messages that arrived while it was stopped failed routing.
Stop
Nodinite offers several convenient ways to Stop Orchestrations:
- Use the Stop action from the Action button menu (as described below)
- Click the Stop button in the Details modal
- Leverage the Auto Healing feature for automated control—use with care!
To Stop a BizTalk Orchestration, press the Action button menu item on the selected row in the list of BizTalk Server Orchestrations:
Stop Orchestration button menu item in Nodinite Web Client.
You will be prompted to confirm the Stop operation in the Execute action? dialog.
Confirmation dialog for stopping an Orchestration.
Once confirmed, the Action dialog shows the answer of the agent to the User, Orchestration '(name)' set to Enlisted:
Success message when the operation completes.
If the operation fails, the Action dialog shows a short message that ends with See diagnostics for details (CorrelationId: …). See Why can't I Stop my Orchestration?.
When the Orchestration is stopped, it is evaluated as being in the Warning state (Enlisted state):
Orchestration in Warning (Enlisted) state after being stopped.
Auto Healing
Nodinite can automatically issue the Stop command for you. This is detailed in the Auto Healing user guide. Use this feature to keep selected BizTalk Server Orchestrations in their intended run-time state—ensuring compliance and reducing manual intervention.
Tip
Using Auto Healing helps maintain your BizTalk environment in its intended state.
Frequently asked questions
Find more solutions and FAQs for the Nodinite BizTalk Monitoring Agent in the Troubleshooting user guide.
Why can't I Stop my Orchestration?
The service account running the BizTalk Monitoring Agent must be a member of BizTalk Server Administrators. Please review the prerequisites.
If BizTalk refuses the change, the Action dialog shows There is a problem to execute operation for '(name)' in category 'Orchestration'. … See diagnostics for details (CorrelationId: …). 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.
Next Steps
Start
Enlist
Unenlist
Tracking
Details