Install multiple versions of API Gateway Policy Manager on the same Windows machine

Products

• CA API Gateway

Issue/Introduction

The multiple supported versions of Layer 7 Gateway may need its own particular versions of Policy Manager. For an implementation that is going through the upgrade cycle, there are time one would need multiple versions of Policy Manager installed on the same machine. In addition, different versions of Policy Manager may also need its own version of JRE/JDK.

Environment

Reelase: 11.x
Component: API Gateway Policy Manager on Windows

Resolution

First, on a Windows machine, please make sure to run the installer as an "administrator" to avoid file permissions issue.

During the run of an installer, please make sure that you provided different folders for different versions of the Policy Manager installer so that they do not attempt to overwrite an existing file installed previously.

At the success run of the installer, you will have a subdirectory for each version. To start the Policy Manager of a particular version, go to the folder that have the version installed. Start the "Layer7 API Gateway Policy Manager.exe" under that subdirectory. The policy manager should start and have its version/build number appear on its Windows title.

By navagating through the "Help\About\Info", it will show the java.vendor and java.vm.version to show you the version of the Java it is using.

Interestingly, the above procedure did not mention anything about an installation of a JRE/JDK. It is because the Windows version installer actually install a jre folder under whether it installs the other files. As a result, Policy Manager 11.1.1.18484 actually used java 17.0.10+7 while Policy Manager 11.0.00.14811 used jave 11.0.15+10.

Note that other unix-like installer may not carry its own jre.