Running versions in parallel for migration

In migration scenarios, having two versions of AppMon running at the same time is not supported. The standard migration procedure can be found here. The content of this page is meant as an aid for experts.

Some components and connections in AppMon may result in potential pitfalls. To avoid some of these, consider:

  • Licensing allows for some flexibility allowing running versions in parallel (three-day grace period or three-week trial).

  • Be sure to configure different ports for different version AppMon components to run in parallel and start / stop them at the right time.

  • Same major version non-Webstart Clients: If you want to connect an old version Client to an old version Server again, answer No when it asks if it should update itself on connection to a new version Server.

  • If you allow the update of the non-Webstart Client, it no longer connects to the older Server. To resolve this issue, use the Web Start Client to connect to the old Server or run / install a same old version Client.

  • You cannot use the same Performance Warehouse database with two different Versions, thus you have to:

    • At some point disconnect the old version (only upgrades are possible) and connect the new version, or
    • Create a separate database with a different name, but then you do not have access to the data in the other database.
  • Do not connect an older Server to the same Performance Warehouse DB once you connected the new version Server (and thus updated the DB).

Multiple collectors on the same host

If you run more than one Collector version or instance on the same machine, verify that in their respective collector.config.xml files, on the collectorconfig XML element, they still have:

  • unique ports (agentport attribute) assigned on which they listen for Agents
  • unique name attributes
  • serveraddress and serverport still indicate the correct Server information.