It is possible to have multiple different versions of DevOps Test Performance (DTP) on the same machine.

Note: This is not an officially supported setup. If you try it and run into an issue, you may be asked to revert to a supported configuration for debugging.

The key requirement when running multiple DTP installations in parallel is to ensure that their footprints do not overlap. This means:

• Each installation must be in a separate directory path.
• Configuration files, log files, ports, and runtime environments must be isolated from one another.
• No two instances should attempt to use the same system resources, such as ports or temporary file locations.

Following these guidelines helps avoid conflicts and ensures that each DTP instance runs independently without affecting the others.

Note: This is not possible with DevOps Test UI as some necessary file paths are hard-coded in the product.

To run multiple versions of DTP in parallel, you’ll need to manage three key steps:

1.      Setting up multiple IBM Installation Manager (IM) instances

2.      Installing each DTP version in its own location

3.      Configuring how each DTP version is launched and maintained

Managing IBM Installation Manager

The first step is to prepare separate instances of IBM Installation Manager; each tailored to a specific version of DTP.

Important: This doesn’t mean installing IBM Installation Manager multiple times. You will use the same IM executable but launch it with different parameters, so each version operates independently.

Example Setup:

I like to keep my instances organized by placing shortcuts on my desktop—one for each DTP version I am managing. For example:

• DTP 10.1.2 → C:\DTP_IMs\10.1.2\
• DTP 10.1.3 → C:\DTP_IMs\10.1.3\
• DTP 10.5.0 → C:\DTP_IMs\10.5\

Each of these shortcuts points to the same IBMIM executable, but with a unique -dataLocation.

How to Create Custom IM Shortcuts:

1. Right-click on an existing IBM Installation Manager shortcut and select Properties.
2. Modify the Target field like this: C:\Program Files\IBM\Installation Manager\eclipse\IBMIM.exe" -dataLocation C:\DTP_IMs\10.5\

3. Repeat this for each DTP version you plan to install, using different folder names for each -dataLocation.
   
   

This keeps each instance of Installation Manager completely isolated from the others.

Installing DTP

Once you have set up a separate IM instance, use it to install the corresponding version of DTP.

You can install multiple versions this way—I have personally managed over 20 versions in parallel without conflict.

Things to Remember During Installation:

When stepping through the Install wizard, make sure to specify unique paths in the following locations:

a) Shared Resources Directory

For example:

C:\Program Files\DTP_1105\IBMIMShared

The default path is:

b) Installation Directory

Again, use a versioned path to keep everything clean and separate:

C:\Program Files\DTP_1105\

The default location is:

Tip: Stick to a consistent naming scheme—it will save you a lot of guesswork later.

Complete the wizard, and you now have that version of DTP installed in isolation.

Running DTP Versions

Once multiple versions are installed, you might notice a small limitation that the Start Menu will only show one entry under:

Start Menu > DevOps Test > DevOps Test Performance

This entry points to the most recently installed version.

Better Approach: Use Custom Desktop Shortcuts

To run different DTP versions easily, create separate desktop shortcuts for each one. Then:

1. Right-click the shortcut → Properties
2. Update the Target field to point to that version’s eclipse.exe
3. Set the Start in field to the correct install directory. For example:

• • • Target:

"C:\Program Files\DTP_1050\eclipse.exe"

• • • Start in:

C:\Program Files\DTP_1050\

Repeat this for each version, and you are ready to launch any version of DTP with a single click—without affecting the others.

Running multiple versions of DTP in parallel is not something officially supported by Product Support Team, but it is doable with a bit of setup. The key is isolation—keeping directories, configurations, and resources separate at every step.

If you're a tester, developer, or support engineer managing multiple versions for different projects or clients, this workflow can save you hours of uninstall/reinstall cycles or help you run two versions simultaneously. Here are some other tips and tricks to make it easier.