Set up the Webstart Client

The AppMon Webstart Client is a fully functional AppMon Client that uses the Java Web Start Technology to minimize administrative effort. To access the AppMon Webstart Client, you open a link in a web browser. You don't install an AppMon Client on the local machine. When the AppMon Server updates, all AppMon Webstart Clients update automatically at start up. The Webstart Client can only connect to a single AppMon Server at a time. Consequently, the Add Dynatrace Server button does not appear in the Client's Settings > Dynatrace Client dialog box.

How does it work?

By default, the AppMon Server ships with an AppMon Webstart plugin. The AppMon Server uses the plugin to display a download link on the Server home page. The default HTTP settings are at https://<servername>:8021.

The link Webstart client references a JNLP file that you need to open with a Java Web Start Launcher. The Java Web Start Launcher downloads all required resources and starts up the Webstart Client. The Java Network Launching Protocol (JNLP) is specified in JSR 056 by the Java Community Process.

Launch the Webstart Client from the AppMon Server home page
Launch the Webstart Client from the AppMon Server home page
Launch the Webstart Client from the AppMon Web menu
Launch the Webstart Client from the AppMon Web menu


See system requirements for AppMon 2017 May, AppMon 2018 April or AppMon 2018 October.

Run the client using webstart

Open a web browser, navigate to https://<servername>:8021/webstart/Client/client.jnlp. The browser may ask for confirmation to run client.jnlp file.

Run the client using JNLP file

If your browser does not support webstart, you can save the JNLP file, and use it to launch the client. Refer to Java documentation for the detailed instructions.


The default installation is pre-configured so the AppMon Webstart Client is immediately available.

  • Enable Webstart: Enables or disables the AppMon Webstart Client.
  • VM Arguments: Shows the JVM arguments used by the AppMon Webstart Client. Due to security restrictions in the Oracle Java Runtime environment this settings cannot be edited.
  • Default Connection Settings: Specifies the default Connectivity settings of AppMon Webstart Clients.

Working directory

Webstart Client can connect to its host server only. This is the only difference from a locally installed Client, which supports connections to multiple servers. Additionally, configuration files of the Webstart Client are stored in server-based working directories to prevent incompatibility issues.

The working directory of Webstart Clients is /.dynaTrace/Dynatrace Webstart Client <servername>. You can find it in the user working directory of your system.

The user working directory depends on the operating system:

  • Windows: /Users/<username>/.dynaTrace/Dynatrace Webstart Client <servername>.
  • Linux: The main working directory is hidden in /home/<username>/.dynaTrace/Dynatrace Webstart Client <servername> and you must enable hidden system folders to display in your file browser.

Migration of stored sessions and dashboards

Follow these steps to migrate locally Stored Sessions such as PurePath sessions or memory dumps from an older AppMon Webstart Client:

  1. Run the older AppMon Webstart Client first.
  2. Export all necessary AppMon stored sessions.
  3. Run the newer AppMon Webstart Client.
  4. Import the AppMon stored sessions.

Follow these steps to migrate dashboards:

  1. Run the older AppMon Webstart Client first.
  2. Store all necessary dashboards at an AppMon Server.
  3. Run the newer AppMon Webstart Client.
  4. Open dashboards from the AppMon Server.
  5. Optionally, store dashboards locally.

Webstart Client kiosk mode

Go to https://<servername>:8021 with your web browser. Under Administration you find the Kiosk mode link to launch the Webstart Client in kiosk mode. The default interval of dashboard switches is 30 seconds. You can customize the interval by applying for instance a 10 sec interval argument in the Webstart launch URL:


Webstart Client URL equivalent to command line arguments

The following is a locally installed Client's command line argument example in Client Commandline Arguments:

<DT_HOME>/dtclient -dashboard "online://<servername>/Incident Dashboard?filter=tf:Last7d"

The Webstart Client URL equivalent:


After the basic Webstart URL http://<servername>:8021/webstart/Client/client.jnlp, the query starts with the usual ? and the arguments are separated by &. The space in Incident dashboard is escaped with a + and can also be escaped with %23. Refer to > HTML URL Encoding Reference for a complete table.


In the online:// argument, you must use the AppMon Server's name, which is typically the lowercased host name and not localhost.

With the additional argument=-reuse, the dashboard opens in a running Client.


The following example only works if you define a PurePath Comparison dashboard and two stored sessions. The & is for argument separation and the source. The compare part uses the same character, and must be escaped with %26.


See Client Commandline Arguments and REST Filters for more argument descriptions.

Frequently asked questions