Logo
Windows XP
Windows Vista
Windows 7
Windows Azure
Windows Server
Windows Phone
EPL Standings
 
 
Windows Server

BizTalk 2010 Recipes : Administration and Operations - Resubmitting Messages

5/18/2011 6:18:43 PM

1. Problem

Your integration solution has encountered an error, and you need to resubmit the messages that have been affected by the fault.

2. Solution

The BizTalk Administrator Console allows you to resume service instances and resubmit their associated messages. You can locate the suspended service instance (which will contain the suspended message) that you need to resume and then choose to resume it, as follows:

  1. Open the BizTalk Administration Console.

  2. Expand the BizTalk Server Administration folder in the left pane, and select your BizTalk group. This opens the Group Hub page.

  3. Click the Resumable link in the Suspended Items section. This launches a query window displaying all suspended service instances in your BizTalk environment that can be resumed.

  4. If you are unsure if a particular suspended service instance contains the message you need to resubmit, right-click the instance record in the results pane, and select Show Messages. This displays a list of messages referenced by the service instance, allowing you to drill down further into the message details and interrogate the actual message, its context, and the flow the message took prior to suspension.

  5. When you have located the service instance you need to resume, right-click the record in the results pane, and select Resume Instance, as shown in Figure 1. In addition to resuming single suspended service instances, you can also resume multiple instances by holding down the Ctrl key and selecting multiple rows in the results pane. To resume all instances, right-click the header record in the results pane, and select Resume Instances.

    Figure 1. Resuming a single suspended instance

3. How It Works

BizTalk errors can be caused by a number of faults, including hardware or network failure or errors during pipeline or adapter processing. When errors occur in your integration solutions, BizTalk typically suspends the service instance that encountered the error. Services are areas of BizTalk processing—such as orchestration, messaging, or adapter—and service instances are specific instances of the orchestration, messaging, or adapter component. A service instance may contain one or more suspended messages. BizTalk differentiates between two basic types of suspension events: resumable (the service instance can be restarted) and nonresumable (the instance cannot be restarted).

Finding the service instance that contains the message you want to resubmit is critical. A number of methods for searching for suspended instances are provided by BizTalk. If you know that you must resubmit a message that was suspended in a specific orchestration, a quick way to search for service instances is to click on the Grouped by Service Name link on the Group Hub page, as shown in Figure 2.

Figure 2. Viewing service instances

In addition to resuming services instances normally, you can also resume service instances in debug mode. Resuming in debug mode will restart the service instance at the last successful persistence point prior to the error.

BizTalk also provides Windows Management Instrumentation (WMI) methods for resubmitting suspended service instances, such as MSBTS_ServiceInstance.Resume and MSBTS_HostQueue.ResumeServiceInstancesByID.

Finally, messages can be manually resubmitted. This process involves finding a particular service instance or message via the BizTalk Administrator Console, saving the message data, and using a resubmit mechanism (such as ports or administrative tools) to resend the message through BizTalk. To save a message, right-click the record (in the BizTalk Administrator Console), and select the option for saving the tracked message(s). While this method is generally more time consuming and task intensive, it can be particularly helpful when the error is such that it would be significantly difficult to successfully resume a suspended service instance. You should consider the following when manually resubmitting messages:

  • Security, with regards to encryption and authentication

  • Data privacy and protection for sensitive information

  • User error if data is manipulated

Top Search -----------------
- Windows Server 2008 R2 : Work with RAID Volumes - Understand RAID Levels & Implement RAID
- Windows Server 2008 R2 Administration : Managing Printers with the Print Management Console
- Configuring Email Settings in Windows Small Business Server 2011
- Windows Server 2008 R2 : Configuring Folder Security, Access, and Replication - Implement Permissions
- Monitoring Exchange Server 2010 : Monitoring Mail Flow
- Windows Server 2008 R2 :Task Scheduler
- Windows Server 2008 R2 : File Server Resource Manager
- Windows Server 2008 R2 : Installing DFS
- Exchange Server 2010 : Managing Anti-Spam and Antivirus Countermeasures
- Windows Server 2008 R2 : Configuring Folder Security, Access, and Replication - Share Folders
Other -----------------
- BizTalk 2010 Recipes : Administration and Operations - Troubleshooting Suspended Services
- SharePoint 2010 PerformancePoint Services : Maintaining a PPS Deployment - Migrating from PPS 2007
- SharePoint 2010 PerformancePoint Services : Maintaining a PPS Deployment - Managing PPS
- SharePoint 2010 PerformancePoint Services : Maintaining a PPS Deployment - Planning for High Availability
- Backing Up the Windows Server 2008 R2 Environment : Windows Server Backup Overview & Using Windows Server Backup
- Backing Up the Windows Server 2008 R2 Environment : Creating the Disaster Recovery Solution
- Backing Up the Windows Server 2008 R2 Environment : Understanding Your Backup and Recovery Needs and Options
- Active Directory Domain Services 2008 : Manage the Active Directory Domain Services Schema - Deactivate Classes
- Active Directory Domain Services 2008 : Manage the Active Directory Domain Services Schema - Create Classes
- Active Directory Domain Services 2008 : Configuring Attributes Not to Be Indexed for Containerized Searches & Configure Attribute Range
 
 
Most view of day
- Windows Server 2008 Server Core : Compressing Data with the Compact Utility
- Manage the Active Directory Domain Services Schema : Remove Attributes from the Index
- Add an InfoPath Form Web Part to a SharePoint Web Part Page
- Microsoft Systems Management Server 2003 : Defining Parent-Child Relationships (part 2) - Installing the Secondary Site Locally from the SMS CD
- Windows Server 2003 : Analyzing Traffic Using Network Monitor (part 1)
- BizTalk 2009 : Host Integration Server 2009 - Planning Your Host Integration Server Topology
- Using Windows Live Programs (part 2) - Using Windows Live Mail
Top 10
- Windows Server 2008 R2 high-availability and recovery features : Installing and Administering Failover Clustering (part 8) - Administering a Failover Cluster
- Windows Server 2008 R2 high-availability and recovery features : Installing and Administering Failover Clustering (part 7) - Create shared folder on cluster, Testing Failover of Cluster
- Windows Server 2008 R2 high-availability and recovery features : Installing and Administering Failover Clustering (part 6) - Add primary storage to cluster, Configure service or application
- Windows Server 2008 R2 high-availability and recovery features : Installing and Administering Failover Clustering (part 5) - Creating a new Failover Cluster
- Windows Server 2008 R2 high-availability and recovery features : Installing and Administering Failover Clustering (part 4) - Verifying cluster configuration using the Cluster Validation Wizard
- Windows Server 2008 R2 high-availability and recovery features : Installing and Administering Failover Clustering (part 3) - Connecting cluster nodes to shared storage
- Windows Server 2008 R2 high-availability and recovery features : Installing and Administering Failover Clustering (part 2) - Adding Failover Clustering feature
- Windows Server 2008 R2 high-availability and recovery features : Installing and Administering Failover Clustering (part 1) - Failover Clustering prerequisites
- Working in the Background : WORKING WITH THE NETWORK LIST MANAGER
- Working in the Background : IMPLEMENTING APPLICATION RESTART AND RECOVERY
Windows XP
Windows Vista
Windows 7
Windows Azure
Windows Server
Windows Phone
2015 Camaro