Share via


Announcing: BizTalk Server 2004 Configuration Management Report Generator w/SQL Reporting Services support

Any of this sound familiar to you?

  • I wish I could report on the relationship between my BizTalk Server components easily. I have an orchestration connecting to three receive ports but it isn’t simple to see how it all hangs together.

  • I wish I could understand the impact of making a change to one of the BizTalk Server components such as this schema I want to update. I need a list of which maps and orchestrations use that schema.

  • I wish I could print-out a BizTalk Server Configuration for a functional specification, operational documentation etc.

The BizTalk Server 2004 Configuration Management Report Generator supports all of these scenarios and more by saving BizTalk Server configuration information to XML and more importantly making it visible in SQL Server Reporting Services through a custom data extension component. Check out an example report here.

With SQL Reporting Services you get hosted reports, export to a variety of formats such as pdf and excel, and lots of built in design capabilities. Of course every BizTalk Server 2004 requires SQL Server 2000 so you already have access to SQL Reporting Services.

The BizTalk Server 2004 Configuration Management Report Generator is a sample and includes the full-source code to all components. Thanks to Jonathan Moons for his work on this sample. Download it here.

Comments

  • Anonymous
    May 18, 2004
    Hi Scott ,
    This is real Product (Tool) integration ! I think other reports would be an option too such as reports on the Tracking Database (HAT) or Reports on the PrimaryImport / Star Database (BAM) is interesting in any format you like depending of the wishes of your customer. By the way this could also be done with the older versions of BizTalk Server :-).
  • Anonymous
    May 18, 2004
    BizTalk Server 2004 CM Reports using SQL Server Reporting Services
  • Anonymous
    June 17, 2009
    PingBack from http://thebasketballhoop.info/story.php?id=2189