OpenKit for Real User Monitoring is the replacement solution which allows you to get Real User Insight for additional Digital Touch points like Java/.NET Rich Clients, PoS-Systems, ATMs,... Currently we are running an early access program covering Java and .NET based end-point implementations. If you are interested please contact email@example.com, firstname.lastname@example.org or email@example.com. We will help you getting started.
Thanks for all your feedback on this project!
This is an experimental prototype bringing UEM features to your Java/.NET Rich Client Applications. It allows tracing activites in WinForms/WPF/SWT/AWT Clients in a similar way as Native Mobile Applications
This prototype uses the same protocol as the Mobile ADK. It requires the following steps to work
a) You need to change the source code of your rich client application to call the ADK functions
b) You need User Experience Management either on a Java Application or Web Server Enabled
c) You need a UEM License as these Rich Clients will be identified as Visits that create Page Actions.
This is an experimental release. Use at your own risk. Do not use in production.
Rich Client UEM ADK
dynaTrace 5.0, 5.5, 6.0, 6.1
Dynatrace Center of Excellence
Sample Session with .NET Rich Client UEM Visit
Download a sample easyTravel WinForms Application. It will connect to easyTravel Business Backend Web Services running on localhost. It uses the RichClientADK to connect to a Web Server Agent on http://localhost:8079. Best is to launch one of the easyTravel UEM Scenarios.
Here are some images that show the Sample Application, Code Snippets and captured PurePaths:
Upon close of the application a message box will show the captured log output of the ADK. Remember - this is a sample application
Using the ADK on your Application
Have a look at the sample project. Download
Step 1: Initialize ADK
Before using the ADK it needs to be initialized. The Startup method will launch a background worker thread that will later be used to send data to the configured monitorSignalURL. This call MUST BE made before making any other calls to the ADK
Here is a sample call to the Startup method:
void Startup(string monitorSignalURL, string applicationId, string deviceType, string manifacturer, string userlanguage, string connectionType)
Step 2: Create Actions
A new action will start a new Page Action which will measure the time between creating the action and calling the method Leave() on it.
Action Enter(string name)
It is also possible to have child actions. Simply call EnterChildAction on an Action object.
Step 3: Tag Web Service Calls
When an application makes Web Service calls or regular HTTP Web Requests they can be tagged so that the captured server-side PurePaths will be linked to the Page Action.
void RichClientADK.TagHeaderBehavior(Action parentAction)
void TagWebRequest(HttpWebRequest request, Action parentAction)
Step 4: Log context information
Additonal to monitoring actions it is possible to log additional context information on page actions. In the current version of the ADK we allow to report a string value.
void ReportEvent(string name)
Step 5: Shutdown ADK
Before the application stops it is required to shutdown the ADK. This allows the ADK implementation to send any unsent monitoring data and also gracefully stop the background worker thread
Start by downloading the AWT Sample Application: AWT_RichClient-UEM-ADK-Demo-src.zip
Using the ADK on your own application
Step 1: Initialilze ADK
The initialize method will register an AWT Event Queue Handler. The handler will then create a page action for the most common window, mouse and keyboard events