BiztalkOrcProfiler Wiki & Documentation Rss Feed

Updated Wiki: Home

santoshbenjamin — Mon, 29 Mar 2010 21:21:32 GMT

Notes

This tool makes use of the common BizTalk OM Library so if you run into any issues with the core, or wish to debug and/or make changes, you need to get that library as well (although the PDB's are included here in the source tree to help with debugging)

Current Release

The current release is v1.2 which is a point release making the 64 bit support now fully available (this was always available as a Planned release but now its been formally made available)

Roadmap

Point releases will be made as frequently as possible to fix reported bugs but no big functionality changes can be expected. Instead we are working on a new tool that will combine this Profiler with the Documenter (as they share a number of common services including the Analysis OM). It is hard to work on two tools (actually 4 -if you take Profiler, Documenter and OM as separate projects) at the same time so please bear with us if we dont get fixes released frequently.

Screenshots

The image below shows a sample of the coverage summary, at a glance you can see the percentage of overall coverage acheived upon an individual orchestration, if all of the shapes are touched as part of your orchestration then you will acheive 100% coverage, common reasons for not covering all shapes with an orchestration are not running tests that stress the error paths of your solution. This coverage summary also provides you metrics around execution duration of your orchestration easily identifying orchestrations that take a long time to execute.

The image below shows the orchestration coverage in detail, shapes highlighted in green have been executed as part of your last test pass and any shapes not executed will be highlighted in red. This enables you to easily understand what parts of your solution have been tested and which parts have not and adjust your testing as necessary.

As part of the profiler report you can see the "Top 10 Least Successsfull" shapes and the "Top 10 Longest Running" shapes, understanding where time is being spent inside your orchestration is key to effective performance testing and has been proven on a number of instances to pinpoint poor orchestration design and coding which when resolved has dramatically increased overall performance. The key is to understanding exactly where time is being spent and this tool offers a no-code view into your running system.

Updated Wiki: Home

santoshbenjamin — Sun, 28 Mar 2010 21:51:22 GMT

Notes

Roadmap

A point release is forthcoming which will support running in 64 bit systems.

Point releases will be made as frequently as possible to fix reported bugs but no big functionality changes can be expected. Instead we are working on a new tool that will combine this Profiler with the Documenter (as they share a number of common services including the Analysis OM). It is hard to work on two tools (actually 4 -if you take Profiler, Documenter and OM as separate projects) at the same time so please bear with us if we dont get fixes released frequently.

Screenshots

Updated Wiki: Home

santoshbenjamin — Fri, 19 Mar 2010 09:18:13 GMT

Notes

Screenshots

UPDATED WIKI: Home

darrenj — Mon, 02 Jul 2007 09:50:20 GMT

Project Description
Creates CHM report files illustrating the level of coverage for specified BizTalk orchestrations. This tool can be run to gain a consolidated view of orchestration tracking data for a specified period of time to help developers get an idea of how their orchestrations are being processed and how much coverage they are getting in their testing. In addition to simple coverage information the data presented helps to identify latency and code path exceptions by highlighting long running and error prone orchestration shapes which is key to effective performance testing.

The image below shows a sample of the coverage summary, at a glance you can see the percentage of overall coverage acheived upon an individual orchestration, if all of the shapes are touched as part of your orchestration then you will acheive 100% coverage, common reasons for not covering all shapes with an orchestration are not running tests that stress the error paths of your solution. This coverage summary also provides you metrics around execution duration of your orchestration easily identifying orchestrations that take a long time to execute.

The image below shows the orchestration coverage in detail, shapes highlighted in green have been executed as part of your last test pass and any shapes not executed will be highlighted in red. This enables you to easily understand what parts of your solution have been tested and which parts have not and adjust your testing as necessary.

As part of the profiler report you can see the "Top 10 Least Successsfull" shapes and the "Top 10 Longest Running" shapes, understanding where time is being spent inside your orchestration is key to effective performance testing and has been proven on a number of instances to pinpoint poor orchestration design and coding which when resolved has dramatically increased overall performance. The key is to understanding exactly where time is being spent and this tool offers a no-code view into your running system.

UPDATED WIKI: Home

darrenj — Mon, 02 Jul 2007 09:17:09 GMT

News
Frequently Asked Questions (FAQ)
Project information (the text from your project description, for example)
Project documentation
Development methodologies
Release process
Current issues

UPDATED WIKI: Home

darrenj — Mon, 02 Jul 2007 09:16:35 GMT

News
Frequently Asked Questions (FAQ)
Project information (the text from your project description, for example)
Project documentation
Development methodologies
Release process
Current issues

UPDATED WIKI: Home

darrenj — Mon, 02 Jul 2007 09:10:12 GMT

News
Frequently Asked Questions (FAQ)
Project information (the text from your project description, for example)
Project documentation
Development methodologies
Release process
Current issues

UPDATED WIKI: Home

darrenj — Mon, 02 Jul 2007 09:09:52 GMT

News
Frequently Asked Questions (FAQ)
Project information (the text from your project description, for example)
Project documentation
Development methodologies
Release process
Current issues

UPDATED WIKI: Home

darrenj — Sun, 01 Apr 2007 19:11:07 GMT

News
Frequently Asked Questions (FAQ)
Project information (the text from your project description, for example)
Project documentation
Development methodologies
Release process
Current issues