Logo
programming4us
programming4us
programming4us
programming4us
Home
programming4us
XP
programming4us
Windows Vista
programming4us
Windows 7
programming4us
Windows Azure
programming4us
Windows Server
programming4us
Windows Phone
 
Windows Server

BizTalk 2010 Recipes : Administration and Operations - Resuming Inbound Message Processing

- Free product key for windows 10
- Free Product Key for Microsoft office 365
- Malwarebytes Premium 3.7.1 Serial Keys (LifeTime) 2019
5/21/2011 3:52:38 PM

1. Problem

BizTalk has encountered an error and suspended the processing of an inbound message. You need to fix the error and resume message processing to receive it successfully.

2. Solution

This example demonstrates the resumable inbound message-processing capabilities of BizTalk. BizTalk initially receives a message that has no recipients. In the publish/subscribe architecture of the MessageBox, the error message will indicate that BizTalk cannot find a subscriber to the message. After creating the appropriate subscription, this example resumes processing and successfully delivers the message.

Begin by creating the receive port and receive location that will accept the message:

  1. Open the BizTalk Server Administration Console.

  2. Right-click the Receive Ports folder under an application, and select New => One-Way Receive Port from the context menu.

  3. Enter SuspendedMessagesExampleIn for the name of the new receive port.

  4. Add a receive location to the receive port, using the default PassThroughReceive pipeline.

  5. Using the File transport type, specify C:\SuspendedMessagesExample\In as the receive folder. Create the folder if necessary.

  6. Grant the BizTalk Application Users group full control to the C:\SuspendedMessagesExample folder.

  7. Enable the receive location.

BizTalk can now receive messages, but the administrator has not specified where BizTalk should deliver the messages. BizTalk will raise an error to the event log and suspend messages received through the SuspendedMessagesExampleIn receive port. Follow these steps:

  1. Place an XML file in the C:\SuspendedMessagesExample\In folder.

  2. In the left tree view of the BizTalk Server Administration Console, click the BizTalk Group to show the Group Hub page. Press the F5 key to refresh the Group Overview page. Note that you will be able to see the count of suspended messages, as shown in Figure 1.

    Figure 1. Suspended message counts in the Group Hub page
  3. Click the Suspended Service Instances link to open the Suspended tab. The Suspended tab will display all resumable suspended service instances, as shown in Figure 2.

    Figure 2. Resumable service instance

Now that there is a suspended message in BizTalk, create a send port to deliver the message and resume message processing:

  1. Create a new static one-way send port in the same BizTalk application as the receive port was created in.

  2. Enter SuspendedMessagesExampleOut for the name of the send port, and configure the File adapter to deliver messages to the C:\SuspendedMessagesExample\Out folder. Create the folder if necessary. Use the default PassThruTransmit send pipeline.

  3. In the left pane of the SuspendedMessagesExampleOut – Send Port Properties dialog box, select Filters.

  4. Define a filter where BTS.ReceivePortName equals SuspendedMessagesExampleIn, as shown in Figure 3. This will create a subscription for all messages received through the SuspendedMessagesExampleIn receive port.

    Figure 3. Defining a message subscription
  5. Enlist and start the SuspendedMessagesExampleOut send port.

  6. On the Group Hub page, return to the Suspended tab.

  7. Select the Suspended (Resumable) query results to display the suspended SuspendedMessagesExampleIn service instance.

  8. Right-click the suspended service instance, and select Resume Instance from the context menu. Click Yes when prompted to confirm. If the Resume Instance option is not available, verify that the selected service instance's status is Suspended (Resumable) under the query results.

  9. Verify that BizTalk successfully delivered the XML message to the C:\SuspendedMessagesExample\Out folder.

3. How It Works

BizTalk supports resumable inbound interchange processing. It suspends the message while receiving it, and the administrator can resume the message after fixing the configuration error. The BizTalk administrator can perform extensive troubleshooting to identify the cause of a suspended message. Double-clicking the Suspended (resumable) service instance shown in Figure 10-25 opens a Service Details dialog box containing detailed information about the suspended message. The Error Information tab, shown in Figure 4, displays detailed error information indicating that the message was suspended because BizTalk could not identify a subscriber.

Figure 4. Viewing error information

The Messages tab displays all the messages in the suspended service instance. Double-clicking a message opens the Message Details dialog box. Select Context in the left pane of the Message Details dialog box to display the message's context properties, as shown in Figure 5. BizTalk can use the Promoted context properties to identify the subscriber of a message.

Figure 5. Message context properties

Back on the Suspended tab of the Group Hub page, the BizTalk administrator can right-click a suspended message and navigate the Troubleshoot Routing Failure submenu to identify the cause of a routing failure.

Although most suspended messages in BizTalk are resumable, in some situations, BizTalk cannot resume message processing. One example is when BizTalk uses order delivery messages in the same order BizTalk receives them. In this situation, resuming a message would also deliver it out of order, so BizTalk prevents resuming the message.

Other -----------------
- BizTalk 2010 Recipes : Administration and Operations - Throttle Orchestration Memory Usage
- Exchange Server 2010 : Managing Logging (part 4) - Specifying Diagnostic Logging Levels & Managing Message Tracking
- Exchange Server 2010 : Managing Logging (part 3) - Managing Administrator Audit Logging & Managing Routing Table Logging
- Exchange Server 2010 : Managing Logging (part 2) - Managing Agent Logging & Managing Exchange Store Logging
- Exchange Server 2010 : Managing Logging (part 1) - Managing Connectivity Logging & Managing Protocol Logging
- Windows Server 2003 : Implementing a DNS Name Resolution Strategy
- Windows Server 2003 : Designing a DNS Namespace
- Windows Server 2003 : Determining Name Resolution Requirements
- SharePoint 2010 Central Administration Backup and Restore : Backup,Restore Prerequisites and Considerations
- SharePoint 2010 : An Overview of Backup and Restore Capabilities (part 2) - Granular Backup & Configuration-Only Backup
 
 
Top 10
- Microsoft Visio 2013 : Adding Structure to Your Diagrams - Finding containers and lists in Visio (part 2) - Wireframes,Legends
- Microsoft Visio 2013 : Adding Structure to Your Diagrams - Finding containers and lists in Visio (part 1) - Swimlanes
- Microsoft Visio 2013 : Adding Structure to Your Diagrams - Formatting and sizing lists
- Microsoft Visio 2013 : Adding Structure to Your Diagrams - Adding shapes to lists
- Microsoft Visio 2013 : Adding Structure to Your Diagrams - Sizing containers
- Microsoft Access 2010 : Control Properties and Why to Use Them (part 3) - The Other Properties of a Control
- Microsoft Access 2010 : Control Properties and Why to Use Them (part 2) - The Data Properties of a Control
- Microsoft Access 2010 : Control Properties and Why to Use Them (part 1) - The Format Properties of a Control
- Microsoft Access 2010 : Form Properties and Why Should You Use Them - Working with the Properties Window
- Microsoft Visio 2013 : Using the Organization Chart Wizard with new data
 
programming4us
Windows Vista
programming4us
Windows 7
programming4us
Windows Azure
programming4us
Windows Server