Guided creation of a System Profile

Manage System Profile with the (Add Tier) wizard

Depending on your entry point, you have slightly different ways to manage or create a System Profile:

  • In the AppMon Client´s Tools > Create System Profile menu, you enter the wizard and name a System Profile in step 1.
  • From the AppMon Start Center, you begin at Step 2 since you already created or selected a System Profile there. At the right top of the window, click the Create button.
  • Through the Add Tier button in the Configuration panel, add to the active System Profile (shown in the breadcrumbs - here: 'easyTravel' in the first screenshot) or - in a new installation when there is only an AppMon Self-Monitoring profile - a new System Profile is created, implicitly named Monitoring.
  • From the Add buttons in the Application Environment Configuration Dialog, add a new tier configuration to the active System Profile (shown in the breadcrumbs - here: 'Monitoring' in the last screenshot).

The whole process has up to seven basic steps.

Step 1: Select a System Profile, or Create a new System Profile

Specify the name of the new System Profile, or edit an existing one when you enter the wizard from Tools > Create System Profile.

Step 2: Add a new tier. Select the technology of new tier

A new Agent Group is created for each tier. See the Agent Groups later by double-clicking the newly created System Profile in the Cockpits sidebar.

Step 3: Define technology details of new tier

Depending on the technology of the tier, specify the location and the technology details of the tier. The definition steps vary depending on the selected technology (Java/.NET/Native). For Java this includes the specification of the used JDK/JRE version.

Step 4 (Remote machines only): Install the Agent

Download the appropriate Agent version from the Dynatrace Community. The installation steps vary depending on the selected technology (Java/.NET/Native).

Step 5: Integrate the Agent into the SUD

Configure the SUD to have an Agent integrated. The integration steps vary depending on the selected technology (Java/.NET/Native).

For example, in Java this includes placing specific command line parameters into the startup scripts of the SUD, while in .NET this is done using the Agent Configuration Tool.

Note

The provided agent string for Java-based SUDs is optimized to be used in startup scripts or in a command line. To use the agent string in Eclipse-based .ini files, the double quotes (") must be removed.

Step 6: Manually restart components

The manual restart page indicates which components to restart before the agents can send data.

Usually this is just the process for the just-created configuration. However, Windows systems for web servers and IIS require two or even three restart steps.

Web server on Windows systems:

  1. Restart the AppMon Web Server Agent Service through the Windows Services.
  2. Restart the web server.

IIS:

  1. Restart the AppMon Web Server Agent Service through the Windows Services.
  2. Restart/Recycle your IIS Application Pool through the IIS Manager.
  3. Access your application's web site through the browser (ensures that, for example, ASP.NET is loaded).

Step 7: Summary of System Profile

In the summary, you can add additional tiers (start again at Step 2) if the wizard was not started with the Application Environment Configuration dialog box.

Step 8: Check the newly created profile

Double-click the newly created System Profile in the Cockpits sidebar and check the Agent Groups / tiers.