Side-by-side component installation

Overview

Side-by-side installation usually means having different versions of the same application on the same operating system or virtual machine coexisting in different directory structures. See below for the exact rules applying to AppMon.

Similar:
Many applications, such as text editors and spreadsheets, consist only of one component, or at least appear as such. However, database management systems (DBMS) already consist of at least two perceptible components ‐ back and front end.

The AppMon Server, Collector, Agent, and Clients components need to work together. It is recommended that you use the very same version and build number for all components. Dynatrace puts great effort into ensuring compatibility across versions in upgrade situations. Build- and revision-level update distribution is handled automatically by default. AppMon build-level updates are automatically propagated from the Server to the Clients and Collectors and from the Collectors to all Agents except non-bootstrap Agents which are denied update at Client startup. Other updates apply after component and application restart.

Different:
Most applications need to be shut down to be updated or patched in the same directory structure through an installer. However, AppMon updates are applied through the Client to a running Server. For changes to apply, restart components and any applications that have an injected Agent with a pending update. See Product Updates for more information.

*NIX

You can install whole AppMon suites or single components as needed using java -jar <path>/<installer>.jar.

Windows

Because the Windows registry requires GUIDs for installations, there are limitations to what can be done. This is also why there are instances, so you can run several Collectors on the same Windows machine if configured with different ports.

Side-by-side installation

You can install different versions of AppMon (major and minor version) side-by-side in different directory structures because they have different GUIDs.

Any configurations and data you want to keep must be migrated, Careful configuration is needed. See the Upgrade and Migration Guide to learn more.

Component installation

  • Use the 64-bit full installation package. This determines if the Server or Collector run with a 32-bit or 64-bit JRE, but you still get the other-bitness Agent bootstrappers and DLLs to instrument any-bitness applications.
  • If you already installed a component with a special installer such as the Agent, and you want to add a component where there is no special installer for Windows, then uninstall the special installation and install all the desired components with a custom install of the full Windows .msi. If you then want to add or remove components, just run the full installer again and modify the installation.
Example:

You installed a Java Agent with the Windows All Agents installation package. To add a Collector on the same machine, uninstall the Agent package and do a custom install with the full installer for the Java Agent and the Collector.

To add a .NET Agent, run the full installer again and modify the installation.

The following matrix shows which installer packages of the same release can and cannot be installed when the other is already on the Windows machine.

Full x-64 Collector Collector x-64 Agent Client Client x-64
Full x-64 s x a x x
Collector s s Yes Yes Yes
Collector x-64 x s Yes Yes Yes
Agent a Yes Yes Yes Yes
Client x Yes Yes Yes x
Client x-64 x Yes Yes Yes x

Legend:
s = conflicts with service
a = conflicts with agents
x = not applicable