ESB Toolkit Tip #19 Use the ESB Portal in BizTalk360 to manage ESB Exceptions

When a transformation or routing process fails, the ESB creates an exception message and submits it through a direct-bound port to the Message Box database. The ESB also implements a send port named ALL.Exceptions that subscribes to and retrieves exception messages and publishes them to the ESB Management Portal.
The ESB Management Portal that ships with the ESB Toolkit is a sample website and is not really intended for production environments. Installation can also be quite difficult because the sample depends on many other components that must be installed first before the ESB Management Portal can be installed and there is not much documentation about it. Because of the installation difficulties there are quite some blogs created on how to install the Portal and there are also many questions about it in the BizTalk ESB Toolkit forum.
Another option is to access the ESB exception data directly via BizTalk360. In that case you only have to do one simple configuration in the BizTalk360 settings and you can avoid using different portals and tools to access your data, BizTalk360 consolidates everything in one place, making you productive.
 

BizTalk360 Settings

You first have to configure the ESB Portal Settings in BizTalk360 before you can use the ESB Portal.
 
Click on the Settings icon to go to the BizTalk360 Settings.
 
Click in the Menu on “ESB Portal Settings” to configure the ESB Exception database connection string.

 

Using the ESB Portal

Click in the Menu on “ESB Exceptions” to go to the ESB Exception Management.
 
Select an Exception and click on the properties button in order to see detailed information.

 

Conclusion

The ESB Portal in BizTalk360 works very well. Almost no configuration, the navigation is clear, it’s fast and the design is pretty. It would be nice that you could also edit and resubmit the fault message but the company stated that they are bringing a lot of new features as part of future release like Edit, Resubmit, Bulk Resubmit and more!

You can download it here:
BizTalk360 Free Trial

BizTalk Server 2013: Step-by-Step to implement Unit Testing in Schemas and Maps

BizTalk Server 2013: Step-by-Step to implement Unit Testing in Schemas and Maps

To implement BizTalk Server 2013 unit test within Visual Studio 2012 to test Schemas and Map we need to: Open your BizTalk Project in Visual Studio.NET 2012, in this sample: “UnitTestingFeatureWithMaps.sln” In Solution Explorer, right-click in the BizTalk Server project, in this sample “UnitTestingFeatureWithMaps”, and then click Properties. In Project Designer, click the Deployment property […]
Blog Post by: Sandro Pereira

BizTalk Innovation Day Norway 2014 | September 25, 2014 – Oslo, Norway

BizTalk Innovation Day Norway 2014 | September 25, 2014 – Oslo, Norway

Great news for the BizTalk community, for the third time the BizTalkCrew (Steef-Jan Wiggers, Tord Glad Nordahl, Nino Crudele, Saravana Kumar and me) are hosting the BizTalk Innovation Day, an one-day event focused purely on Microsoft BizTalk Server/BizTalk Services and related topics, in Norway! The two previous BizTalk Innovation Day editions in Norway were carried […]
Blog Post by: Sandro Pereira

ESB Toolkit Tip #18 Use the BTDF-SSO Resolver to dynamically resolve settings via SSO

When you set an endpoint in an Itinerary with the STATIC Resolver you store that endpoint location in the Itinerary. In ESB Toolkit Tip #6 I showed that in larger environments where you have a lot of services you can use Sentinet from Nevatech to store and manage the web services and use the Sentinet SOA Repository Resolver to dynamically get the endpoint of the Services. But what if you want to route the message to a MSMQ or for example a folder? In that case you can use the BTDF-SSO Resolver from the Deployment Framework for BizTalk (BTDF).
The Deployment Framework for BizTalk makes it easy for you to centrally manage all of the variables (connection strings, user names, passwords, file paths, URL’s, etc.) and store them in SSO. At runtime you can use the BTDF-SSO Resolver to resolve the settings from SSO.

 

Deploy Configuration Settings into SSO

To deploy configuration settings into SSO, edit your Deployment Framework for BizTalk project file (.btdfproj) as follows:

1. Set the IncludeSSO property to true.
 
2. Ensure that you have a PropsFromEnvSettings ItemGroup containing SsoAppUserGroup and SsoAppAdminGroup.
 
3. Ensure that the Excel settings spreadsheet contains SsoAppUserGroup and SsoAppAdminGroup settings and add custom settings.

 

Using the BTDF ESB Resolver

To use the BTDF-SSO Resolver in an Itinerary:

1. Ensure that the BTDF-SSO Resolver is added to the esb.config.
 
2. Create or edit an itinerary in the Itinerary Designer and, on an itinerary service object, add or edit a Resolver.
 
3. Choose "Deployment Framework for BizTalk SSO Resolver Extension" as the Resolver Implementation.
 
4. Fill in the AffiliateAppName, Transport Location and Transport Type fields.

 

Testing

Once the BizTalk Project with the SSO settings and the Itinerary is deployed with the Deployment Framework for BizTalk, the itinerary is ready to be tested.

1. Check if the settings of the BizTalk application are deployed to SSO with the SSOSettingsEditor tool.
 
2. Sent a message to BizTalk and run DebugView to watch the trace output of the BTDF-SSO Resolver.
 

 

See Also

For more information on the BTDF-SSO Resolver see:

What’s the future of application integration? I’m heading to Europe to talk about it!

What’s the future of application integration? I’m heading to Europe to talk about it!

We’re in the midst of such an interesting period of technology change. There are new concepts for delivering services (e.g. DevOps), new hosts for running applications (e.g. cloud), lots of new devices generating data (e.g. Internet of Things), and more. How does all this impact an organization’s application integration strategy? Next month, I’m traveling through […]
Blog Post by: Richard Seroter