• Print
  • Share


  • Updated on 01 May 2018
  • 1 minute to read
  • Contributors

Microsoft BizTalk Server is a widely used integration product in the market. It comes with a variety of inbuilt features to help organizations ease their integration challenges. Once the BizTalk applications are built and deployed into production environments (or any controlled environments like UAT, SIT etc), BizTalk administrators and support people need to actively manage them on a day to day basis. On a regular basis they will perform activities like keeping an eye on the instances suspending, state of the receive locations, send ports, host instances etc, perform some activities on the artifacts like starting host instance, stopping send port etc. BizTalk Server by default comes with a tool called "BizTalk Administration Console" (let's call it for short as BAC) to perform all these operational activities. Even though BAC is very powerful, it possesses a lot of gaps. First, it's not web-based, the operational security model is very weak, these are only a few of the weaknesses.

This section will cover the topics:

  • Challenges faced by BizTalk Server administrators - Explaining potential gaps in the BizTalk Server Administration Console (BAC) when it comes to managing BizTalk Server environments.
  • How BizTalk360 helps BizTalk Server customers to address all the challenges around BizTalk security and audit, for their BizTalk environment(s).
  • BizTalk Server Operation Security
  • Real-time scenarios
Was this article helpful?