Icon

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

Overview

Name

MSBuild Tasks Library for dynaTrace 2.6

Version

1.0

dynaTrace Diagnostics Version

2.6

Author

dynaTrace software

License

dynaTrace BSD

Support

Supported

Download

dynaTrace_DTBuildTasks_v1.0.zip

Description

The Download Package includes an .NET Library that implements several tasks to be used by MSBuild scripts.

Following tasks can be executed:

  • Start, Stop or Restart the dynaTrace Server
  • Start and Stop Session Recording
  • Change Active Configuration

This library makes use of the .NET Command Library.

Installation

  1. Save the attached file locally to the computer where the dynaTrace Diagnostics Client is installed.
  2. Unzip the file.
  3. Copy the two extracted dlls to a directory where it can be picked up by MSBuild when executing your build scripts
  4. View the extracted msbuild_sample.xml file. It shows how you can register the new build tasks in your MSBuild scripts

Usage

You have to register the new Build Tasks with the UseTask configuration entry in your build scripts like this:

Each task can now be used in your targets. Following properties are available for the different tasks:

StartSessionRecordingTask

  • ProfileName: (mandatoy) - specifies the System Profile you want to start recording on 
  • RecordSessionName: (optional) - allows you to define the name of the recorded session
  • dtVersion: (optional) - this is the dynaTrace Client Version that you want to use. In case multiple versions of dynaTrace are installed you use this to connect to the correct version
  • dtInstallDir: (optional) - this is the dynaTrace Client Installation directory. If not specified the value is read from the registry
  • ServerName: (optional) - the dynaTrace Server Hostname to connect to. Default: localhost
  • Username: (optional) - the username to connect to the dynaTrace Server. Default: admin
  • Password (optional) - the password to connect to the dynaTrace Server. Default: admin

StopSessionRecordingTask

  • ProfileName: (mandatory)
  • dtVersion, dtInstallDir, ServerName, Username, Password: see description of StartSessionRecording

SetActiveConfigurationTask

  • ConfigurationName: (mandatory) - configuration name to switch to
  • ProfileName: (mandatory) - System Profile where you want to switch the active configuration
  • dtVersion, dtInstallDir, ServerName, Username, Password: see description of StartSessionRecording

ServerServiceTask

  • ServiceCommand: (mandatory). Allows one of the following values: startup, restart, shutdown
  • dtVersion, dtInstallDir, ServerName, Username, Password: see description of StartSessionRecording

ConfigureApplicationTask

  • Executable: (mandatory). Defines the full path to the executable you want to configure, e.g.: C:\MySample\MyApp.exe
  • Active: (mandatory). True or False. Allows to switch a configuration active or inactive
  • AgentName: (optional). Name of the Agent. Default: name of the executable file, e.g.: MyApp.exe
  • CommandLine: (optional). Command Line that must match the process. Default: empty==any command line value
  • ServerName: (optional). dynaTrace Servername to let the Agent connect to. Default: localhost
  • ServerPort: (optional). dynaTrace server port to let the Agent connect to. Default: 9998
  • LogFile: (optional). location where to store Agent logfile
  • LogLevelLife: (optional). LogLevel for the Log File. Possible Values: LOG_NONE, LOG_SEVERE, LOG_WARNING, LOG_INFO, LOG_FINE, LOG_FINER, LOG_FINEST. Default: LOG_NONE
  • LogLevelConsole: (optional). LogLevel for Console Loggin. Default: LOG_INFO

Internals

The Library uses the dtdcmd.jar file that is installed with the dynaTraceClient. The majority of the build tasks therefore calls the dtdcmd.jar file via command line - based on the properties and parameters that you have specified. For every dtdcmd.jar execution the library creates an EventLog Entry with detailed information about the command line arguments that were passed. This should help with troubleshooting.

The task ConfigureApplicationTask needs write access to the HKLM Registry on your local machine. In case your user does not have the appropriate access rights you will run into errors.

Sample MSBuild Script

The download package includes a sample msbuild file. Check it out for a reference

An additional sample can be seen here: VSTS Sample Test Project

Attachments

  File Modified
ZIP Archive dynaTrace_DTBuildTasks_v1.0.zip MSBuild Tasks Aug 11, 2008 by Andreas Grabner


  • No labels