Send Port Group Category
Understanding Send Port Groups Monitoring
Send Port Groups enable fan-out messaging in BizTalk—a single message published to the MessageBox can be delivered to multiple destinations simultaneously. Each Send Port Group contains multiple Send Ports that all subscribe to the same message, creating redundant deliveries or distributing workload across endpoints.
Why Send Port Groups monitoring is critical:
- Silent partial failures – If a Send Port Group is stopped or unenlisted, none of its member Send Ports process messages, even if individual Send Ports are started. All deliveries fail silently. Example: Order notification needs to reach both warehouse (File), shipping provider (SFTP), and CRM (HTTP). If Send Port Group stops, all three deliveries fail.
- Routing failures multiply – A Send Port Group with no matching subscription causes routing failure suspended instances just like individual Send Ports. But the impact is multiplied—messages intended for 5 destinations all suspend simultaneously.
- Business continuity risk – Send Port Groups are often used for critical multi-channel notifications (order confirmations via email + SMS + webhook). If group stops, customers receive zero notifications across all channels.
- Compliance violations – Regulatory filings often require delivery to multiple agencies simultaneously. Stopped Send Port Group means none of the required filings occur, creating compliance gaps.
- Operational complexity – Send Port Groups have two-layer state management: group state (started/stopped/enlisted/unenlisted) AND individual Send Port states. A started group with stopped member ports still fails to deliver.
- Subscription conflicts – Multiple Send Port Groups subscribing to same message types create duplicate fan-out scenarios (message delivered 2x, 3x, etc.), overwhelming downstream systems.
Common scenarios requiring Send Port Group monitoring:
- No subscriber found – Send Port Group filter doesn't match promoted properties; all messages suspend with routing failure
- Enlisted but stopped – Group subscribes but doesn't activate member Send Ports; messages accumulate in MessageBox without delivery
- Member port failures – Individual Send Ports within group fail (adapter errors, credential expiration, endpoint down) but group appears healthy
- Accidental stops – Developer stops group during testing and forgets to restart; production multi-channel deliveries cease
- Filter configuration errors – Bad Boolean logic in group filter (AND vs OR precedence) causes unexpected subscription behavior
Nodinite BizTalk Monitoring Agent empowers you to monitor BizTalk Send Port Groups from all BizTalk Applications. The agent automatically detects and manages new or removed Send Port Groups, ensuring your monitoring is always up to date.
- Send Port Groups in BizTalk appear in Nodinite as Resources using the Send Port Group name.
- Nodinite mirrors the Application structure, providing a 1:1 mapping with BizTalk Applications.
- Send Port Groups are grouped by the Category Send Port Group for streamlined management.
Here's an example of a Monitor View filtered by the 'Send Port Group' category.
Note
All User operations within Nodinite are Log Audited, supporting your security and corporate governance compliance policies.
What are the key features for Monitoring BizTalk Server Send Ports?
- Remote Actions – Execute powerful remote actions directly from Nodinite
- State Evaluation – Monitor and evaluate the real-time run-time state of Send Port Groups
What is evaluated for BizTalk Send Ports?
The table below explains the different evaluated states for any Send Port Group:
| State | Status | Description | Actions | |
|---|---|---|---|---|
| Unavailable | Resource not available | Evaluation of the 'BizTalk Send Port Group' is not possible due to network or security-related problems | Review prerequisites | |
| Error | Unenlisted | An Unenlisted Send Port Group renders as state 'Error' | Start Enlist | |
| Warning | Enlisted/Stopped | Send Port Group is enlisted/stopped and does not process (send) messages | Start Unenlist | |
| OK | Enabled and running | Send Port Group is operational, and no other problems are detected | Details Tracking |
Tip
You can reconfigure the evaluated state using the Expected State feature on every Resource within Nodinite.
Actions
The following Remote Actions are available for the Send Port Group Category:
Send Port Group Actions Menu in Nodinite Web Client.
- Start – Start sending messages (also enlists the send port)
- Stop – Stop sending messages
- Enlist – Start subscribing for messages to send when started
- Unenlist – Stop the port and stop subscribing
- Tracking – Change Tracking Settings
- Details – Display detailed information about the Send Port Group.
Details
Click the Details menu item to open a modal with essential information about the selected Send Port Group.
Details modal for Send Port Group in Nodinite Web Client.
On this page, you can change the Description. Remember to click the Save button to persist your changes.
Filter Send Port Groups
The BizTalk Monitoring Agent supports filtering unwanted resources. See Configuration for details.
Tip
Use the filter feature to remove temporary Send Port Groups that should not be part of your business-critical monitoring with Nodinite.
For information about subscription filters on Send Port Groups, visit the Send Port Details user guide.
Next Step
Add or manage a Monitoring Agent Configuration
Configuration
Details
Start
Stop
Enlist
Unenlist
Tracking