Home > BizTalk Server, ESB Toolkit > ESB Management Portal Customization

ESB Management Portal Customization


The ESB Management Portal that ships with the ESB Toolkit is a sample site and is intended as a starting point for building your own portal for exception management and beyond.

This view of the portal is something that is often overlooked with the assumption made that it is a production ready component of the ESB Toolkit.

To make the most out of the portal it should be customized to suit the needs of your client or enterprise.

Resubmitting XML

The first customization required is to facilitate the resubmission of failed XML messages. “Out-of-the-box” fault messages are logged with a content type of “text/plain”. This results in only HTTP On-Ramps being visible in the resubmission location drop-down list.

To resolve this modify the usp_insert_Message stored procedure in the EsbExceptionDb as follows

IF (@ContentType = 'text/plain' AND LEFT(@MessageData,1) = '<')
BEGIN
  SET @ContentType = 'text/xml'
END

This will set the content type of all XML fault messages received to “text/xml” resulting in the WCF and SOAP On-Ramps being visible in the resubmission location drop-down list.

While there are many customizations that should be applied to the portal this is the main one to make if you require the ability to resubmit XML messages, which I am certain the majority of users will want.

References

MSDN Forum post by MikeGBUK

Advertisements
  1. March 25, 2012 at 06:23

    Good post Colin. Another customization that goes hand in hand with this is to potentially relax the HTTP restrictions on characters such as XML tags in the resubmitted request messages, take a look at http://adventuresinsidethemessagebox.wordpress.com/2012/03/25/a-potentially-dangerous-request-form-value-was-detected-from-the-client-on-trying-to-resubmit-a-message-in-the-esb-portal/.

    Let me know if you have found a better way to get around this problem 🙂

    • March 25, 2012 at 21:41

      Thanks for the reminder Johann. You can also receive this error when viewing XML fault messages on the portal. I will update the post to reference that.

  1. March 25, 2012 at 06:19

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: