Icon

Comments have been closed on this page. Please use AppMon & UEM Plugins forum for questions about this plugin.

The dynaTrace FastPack for Microsoft BizTalk Server enables faster performance analysis of BizTalk Environments by providing pre-configured Dashboards, System Profile, Sensor Packs, and Monitor Plugin for BizTalk.

FastPack Details

Name

Microsoft BizTalk FastPack

Version

5.0

dynaTrace Version

>= 6.1

Author

version 5.x dynaTrace software (sergio.hinojosa@dynatrace.com)
version 4.x dynaTrace software (andreas.grabner@dynatrace.com)

License

dynaTrace BSD

Support

Not Supported

Source Code

https://github.com/Dynatrace/Dynatrace-BizTalk-FastPack

Download

1.- v 5.0 BizTalk Monitors Fastpack
2.- v 5.0 BizTalk Profile Fastpack

older versions
----------------

BizTalk Monitor Plugin  (for version 3.x)
v 3.0: BizTalk FastPack Package
v 3.1: BizTalk FastPack Plugin
v 4.0: BizTalk FastPack Plugin (includes Monitor Plugin)

Dynatrace FastPack for Microsoft BizTalk Server

The dynaTrace FastPack for Microsoft BizTalk Server enables faster performance analysis of BizTalk Environments by providing pre-configured Dashboards, Monitors, System Profile and Sensor Packs for BizTalk.
 

 

Overview

The dynaTrace FastPack for BizTalk contains everything to get started with analyzing your BizTalk Environment

  • A system profile with pre-configured Monitors, Sensor Rules and Agent Mappings
  • A set of dashboards to Analyze the Messages performance, Message Box, Orchestrations, Documents, Adapters and Pipeline Performance
  • A set of BizTalk Monitoring plugins to monitor BizTalk specific Performance Counters

 

Installation

  1. Download the latest release of the BizTalk Monitors FastPack and the BizTalk Profile and Dashboard Fastpack.

  2. In the Dynatrace Client, go to Tools -> Manage Plugins and click "Install Plugin"
    1. Select the BizTalk Monitors Fastpack .DTP and allow it to install.
    2. Select the BizTalk Profile and Dashboards .DTP and allow it to install.

That's it, you have now installed a set of Monitors and a System Profile with Dashboards for your BizTalk Environment. Now you only need to spefify your BizTalk Servers you want to monitor and map the Agents.

 

Configuration

BizTalk Processes

Configure your BizTalk Host Instance processes with the .NET Agent configuration Tool (BTSNTSvc.exe). In the System Profile there is an Tier Mapping for Applications deployed in IIS. If you want to monitor them as well, just configure your IIS Web Server to map the BizTalk System Profile.

Once you have maped the BizTalk processes you want to monitor, restart your BizTalk Host Instances via the BizTalk Administration Console.

Verify that the BizTalk Host Instances get correctly assigned to the imported BizTalk System Profile. In the Dynatrace Client go to Status Overview > Agents Overview. If they are mapped correctly, you'll be able to see PurePaths once you put messages through your BizTalk Orchestration.

Monitors configuration

Once you have the Processes mapped to the System Profile, you'll automatically get the Hosts where your BizTalk Instances are running. The Monitors installed in the first step, will retrieve Performance Counters from your BizTalk Instances.

  1. In the Dynatrace Client go and click on edit in the BizTalk System Profile.
  2. Click in Monitors
    • You will see 3 different preconfigured monitors.These are described in Monitors
  3. For each Monitor click on Edit
    1. Configure the Performance Counter Instance under Settings. The 3 different monitors will collect information from 3 different PerfMon Instances at 3 different Levels: BizTalk Application, MessageBox and Host.
    2. Select the Hosts to monitor under Hosts.

Monitors

The monitors collect Performance Counters from 3 different instances which are defined at 3 different levels: BizTalk Application, MessageBox and Host.

BizTalk MessageBox Performance Monitor (General Counters)

  • Collects information about the MessageBox like Purge Jobs and Spool Size

  • The PerfMon instance is "BizTalkMessageBoxName:HostName"

BizTalk MessageBox Performance Monitor (Host Counters)

  • Collects information about the Host Queue

  • The PerfMon instance is "BizTalkServerApplicationName:BizTalkMessageBoxName:HostName"

BizTalk Windows Performance Monitor

  • Collects information about Orchestration, Message Performance, Adapters running in each instance.
  • The PerfMon instance is "BizTalkServerApplicationName" which per Default is "BizTalkServerApplication"


For more information about Hosts and System Monitors visit Monitors in the Dynatrace Community.

 

Dashboards

The following Dashboards will be installed in the System Profile.

BizTalk Performance Dashboard

 

This dashboard provides helps identifying performance problems in the overall message processing infrastructure of BizTalk. It monitors the Windows Performance Counters of BizTalk and alerts on problems that impact the Host throttling such as

  • High message delivery rate
  • High database size
  • High in-process message queue
  • ...

This dashboard gives a high-level performance overview of the most critical component in BizTalk - which is the MessageBox, the Message Box Host queue and the message processing. It also shows the message delivery delay such as pending messages, active publishing delay and active send messages.

BizTalk Documents and Pipelines Dashboard

This dashboard provides an insight in the messaging performance counters displaying the processed documents by the BizTalk server. The default pipelines will be detected with a business transaction and will be automatically plotted as well as the different orchestrations being processed by BizTalk server. The slowest Pipelines and Orchestrations as well as the most used ones will filtered and shown in a business transaction dashlet. For correlating infrastructure issues with the amount of processed documents, at the bottom of the dashboard, the active threads, handles, read bytes and written bytes by the host will be displayed.

BizTalk Orchestration Engine Dashboard

The Orchestration Engine dashboard shows rerformance counters about the orchestration health, the transactional scopes and the pending work. A timeline displays the amount of orchestration and transactional metrics per second such as orchestration created, dehydrated, rehydrated, completed and so fort. The Dyhadration threshold, dynadrations in progress as well as the allocated memory and amount of database transactions will be measured and displayed. The slowest Pipelines and Orchestrations as well as the most used ones will filtered and shown in a business transaction dashlet.

BizTalk Adapters Dashboard

The Adapters dashboard displays the performance counters for the most common adapters such as File, HTTP and SOAP for the received and sent messages. An alert (lock failure / sec) will be triggered when the BizTalk server starts locking messages for their processing. This usually happens when being under load. The handle count and current CPU load helps identifying problems related to the infrastructure.

BizTalk Architect Dashboard

This dashboard provides helps to architecs to identify problems related to:

  • Memory Usage and Garbage Collector Activity
  • Exceptions that are thrown within the BizTalk Orchestration
  • Database and Web Service activity
  • Reponse Time Hotspots among all the transactions and instances of the BizTalk Servers.
  • API Breakdown with the distribution of cpu, sync and wait.
  • Transaction layer breakdown and execution count

The dashboard also shows a performance breakdown into the individual components within BizTalk like BizTalk Core Components, XLANG, Web Services, ...

BizTalk Deep Analysis Dashboard

This dashboards is composed by the following dashlets:

  • Transaction flow
  • API breakdown
  • Methods
  • Method Hotspots

This dashboard will help developers understand the called methods and indentify the hotspots inside the BizTalk Server such as code running inside the XLANG BTX Engine. The MessageBox is in the transaction flow exposed as an external call with the help of a method sensor. This method is called when the XLANGStore commits it’s work and sends the message to the COM module, which then commits the message in the database.

 

Database Agent

The Dynatrace Database Agent is a must complementary for performance analysis with BizTalk. BizTalk relies heavily in the database of the MessageBox. The messaging and orchestration engine will store and handle the lifecycle of every message in the MessageBox. This is normally a Microsoft SQL Database.

The Database agent configuration is really simple and can be done within a minute. Nothing needs to be installed in the database, this is just a JDBC connection that is configured through the dynatrace client. Just select the messagebox database, with a user and password and that's it, you are ready to go.

The Database Agent will get you great insight into the Database so you can correlate all the retrieved information such as total and active sessions, batch requests per seconds, amount of SQL compilations and recompilations, CPU usage, Disk I/O, slow queries, locks and tablespaces. For more information about how to leverage with the database agent, just watch the great Online Perf Clinic – Database Diagnostics Use Cases with Dynatrace from Andy on our YouTube Chanel or check our APM Blog for blogs like this sql server plan blog from Sonja.

 

Problems? Questions? Suggestions?

Additional Resources

Blogs

Dynatrace AppMon Documentation

BizTalk Performance Counters

Contribution

Feel free to contribute any changes on Github

  1. Anonymous (login to see details)

    Do we plan to develop a release for DT 5.6?  When I did the import on the system profile, the migration from this one to 5.6 it asked to change a lot of the sensor rules.

    Also, are the sensor packs needed for 5.6?

    1. Anonymous (login to see details)

      Hi Jeff. Good Points. I think most of the Sensor Rules are no longer needed because we have Auto Sensors now. Our colleague Jari worked on the FastPack this week as he needed it. I will ask him if he updated the version so that we can upload it for 5.6.

  2. Anonymous (login to see details)

    Hi Jeff,

    Let me know if you find out anything for this. I experienced the same behavior on 5.5 and we think we have a majority covered, but i'm not a biztalk expert and it would be great to get a proper sensor pack that only insturments the important methods and let our auto-sensors do the rest.

    Thanks

  3. Anonymous (login to see details)

    If there is an updated version I would like to get my hands on it as well.

    1. Anonymous (login to see details)

      Hi Jeremy. There is no more recent version than the one on this page. So - give it a try

  4. Anonymous (login to see details)

    In order to use this FastPack do you need to use a Collector installed on Windows or can it be used with a Linux Collector?  Just wonder since it uses Windows Performance counters.

    1. Anonymous (login to see details)

      Although the monitor plugin is running from the Collector, it is requesting the Windows Performance Counters from the machine that BizTalk is running on i.e. a Windows machine. What the monitor is doing should not be affected by the OS it is running from.

  5. Anonymous (login to see details)

    Hi, Our Biztalk guys are wanting to know if Dynatrace can monitor Biztalk 2013 R2.  We are on DT 6.1 currently.   They are having a lot of misc problems with Biztalk and need some help! 

     

    Thanks!

    1. Anonymous (login to see details)

      So you can apply this monitor and get high level metrics.

      OR

      You can install IIS and .NET agents onto BizTalk. BizTalk 2013 I believe is completely IIS and .NET, some of the older versions of BizTalk used to have proprietary components as well.

  6. Anonymous (login to see details)

    Hi All,

    Does this Fastpack work on AppMon 6.3?

    Thanks!

    1. Anonymous (login to see details)

      I just tried it on 6.3.3 and it installed correctly. it comes with a pre-configured system profile which includes some BTs and Measures as well as the dashboards shown on that page!

  7. Anonymous (login to see details)

    That's great!

    Thank you very much Andreas for your prompt answer!

  8. Anonymous (login to see details)

    Hi,

    It says that the bundle is invalid when I try to install it. The I look at the dtserver logs and it says:

    2016-08-26 11:48:42 WARNING [DeploymentManager] Invalid or unsupported plugin type 'invalidBundle' found in file 'BizTalk_Profile_v.5.dtp'. Installation canceled.

    How can I fix that?

    Thanks.

     

    Eddy

     

     

    1. Anonymous (login to see details)

      Hi Eddy,

      I tried to install version 5.0 of the fastpack but I get the same error as you. Looks like there is a problem with the dtp-file.

      I have contacted Sergio who has written version 5.0 of the plugin but he is on holiday till September 5th.

      For now you can download version 4.0 of the BizTalk Plugin

      Ingo

       

      1. Anonymous (login to see details)

        Thanks for the update Ingo.

        Eddy

        1. Anonymous (login to see details)

          Hi Eddy

          sorry for the late reply. It appears that when the DTP files were uploaded/copyed into the release directory in GitHub, the files were truncated to 53Kb. I just copyed the original ones (from the bin directory in GitHub) again to the release directory. The download & installation should by fine now. Give it a try and let me know if everything went ok.

          Best

          Sergio

           

  9. Anonymous (login to see details)

    Hi guys,

    One more question. When installing version 4.0, I see it comes with 3 Biztalk  sensor packs (Biztalk, Biztalk Debug and Biztalk XML Debug), but they are not placed. However, it comes with two sensor groups (Biztalk Entry Points and Biztalk_AG), which are placed. I had a look at the Biztalk sensor pack under the sensor packs in the server settings to see what methods are instrumented and compared them with Biztalk entry points and Biztalk_AG and they are quite different. Is there any reason why Biztalk sensor pack is not placed? Was it for old versions of dynatrace that did not have auto sensors and the Biztalk and Biztalk_AG replace them? Not sure if I have to place the Biztalk one to get more visibility.

    Thanks.

    Eddy

    1. Anonymous (login to see details)

      Hi Eddy

      yes, you are right. Version 4 (and older) of this plugin was made a few years ago and are based in older versions of Dynatrace. The out of the box visibility for uninstrumented methods has improved a lot since then. When updating this plugin I cleaned some of the sensor groups and unplaced sensors. I tested this release with BizTalk 2013 R2 and added two more monitors in order to get the perfmon counters for adapters, orchestration, messaging and the message box (see the latest Performance Counters for the BizTalk Server). I hope this helps you and you get the visibility and insights that you are looking for. You can always capture any missing information. Microsoft describes the implemented classes and interfaces for the BizTalk Services like the BTXEngine which helps to capture the desired information. And last but not least, don't forget to give it a try to the Database Agent to complement the visibility of the Message Box.

      Best

      Sergio

  10. Anonymous (login to see details)

    Hi Sergio,

    Thanks a lot! It installed correctly.

    Cheers.

    Eddy

     

  11. Anonymous (login to see details)

    Hi Sergio,

     

    We are installing this plugin and BizTalk_Monitors_v.5.dtp installed properly but we are getting error for BizTalk_Profile_v.5.dtp. Please find the logs from the server.

    2016-12-20 15:50:27 WARNING [DeploymentManager] Internal Error: Failed to deploy plugin installation file 'BizTalk_Profile_v.5.dtp' - ignoring installation file: com.dynatrace.diagnostics.server.deployment.DeploymentManager b:829 java.io.IOException: Failed to load Dashboard from file '/apps/dynatrace-6.2/server/deployment/BizTalk_FastPack_1.0.1.0/dashboards/BizTalk Adapter Monitor.dashboard.xml'         at com.dynatrace.diagnostics.sdk.dashboard.internal.DashboardConfigManager.loadDashboardConfigurationFromFile(SourceFile:669)         at com.dynatrace.diagnostics.server.deployment.DeploymentManager.a(SourceFile:1538)         at com.dynatrace.diagnostics.server.deployment.DeploymentManager.b(SourceFile:767)         at com.dynatrace.diagnostics.server.deployment.DeploymentManager.a(SourceFile:119)         at com.dynatrace.diagnostics.server.deployment.DeploymentManager$4.work(SourceFile:591)         at com.dynatrace.diagnostics.server.deployment.PluginInstallationCallable.call(SourceFile:56)         at com.dynatrace.diagnostics.server.deployment.PluginInstallationCallable.call(SourceFile:20)         at java.util.concurrent.FutureTask.run(FutureTask.java:262)         at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)         at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)         at java.lang.Thread.run(Thread.java:745) Caused by: com.dynatrace.diagnostics.util.modern.MaximalVersionMismatchException: Version mismatch: Version '6.3.5.1050' is not supported. The highest supported version is '6.2.8.1019'.         at com.dynatrace.diagnostics.util.modern.JDomHelper.loadDocument(JDomHelper.java:217)         at com.dynatrace.diagnostics.sdk.memento.XMLMementoSerializer.deserialize(SourceFile:102)         at com.dynatrace.diagnostics.sdk.memento.XMLMementoSerializer.deserialize(SourceFile:67)         at com.dynatrace.diagnostics.sdk.dashboard.internal.DashboardConfigManager.loadDashboardConfigurationFromFile(SourceFile:616)         ... 10 more

     

    1. Anonymous (login to see details)

      Hello Mukesh,

      in BizTalk_Monitors_v.5.dtp file are the Monitors plugin that polls the information (PefMons) from BizTalk. In the BizTalk_Profile_v.5.dtp  is a System Profile, the Dashboards, and the Monitors configurations. From the log I can see that your dynatrace server supports a highest of 6.2.8 and the dashboards were made with version 6.3.5. If you can update to 6.3 or even better, 6.5 then that's the way to go. There's a ton of new functionality and cool features since 6.2.

      In some spare time I'll try to modify the Dashboards so that the backwards compatibility goes until 6.1. and check them in into Github.

      Best

      Sergio