wrapper.java.command=java
One of the things that installer does is add Java to $PATH.
One thing I should mention. This client launcher is not on the same machine as the gateway, if that matters.
It only matters in that you need to install this version of Java on whatever machine the Client Launcher is on.
If your Ignition Gateway is currently working and you don't need to change its Java version then don't make changes there.
1 Like
Does changing ignition.conf require me to restart the gateway?
Yes, but you nothing you've said so far explains why you're modifying ignition.conf. This was originally about the launchers. Are you trying to change the version of Java for that Gateway as well?
No, but the ignition.conf file is currently specifying the java path instead of using the environment variable.
Who cares? Why are you changing something? Is your Gateway not working?
the gateway is fine. I can't get a new client to launch on this PC
Ok, stop what you're doing and listen to me. I'm going to repeat what I've already told you, but whatever.
Go to the computer where you can't launch a Client Launcher. Remove any existing versions of Java. Download the Azul JDK 8 MSI installer and install it.
1 Like
Make sure that the OpenJDK install Kevin found for you is the only java installed on that PC (the client PC).
Edit: What Kevin just said.
This topic highlights a fundamental requirement of running old software: you usually also have to run old versions of some or all of its dependencies. If you choose to not upgrade Ignition due to $, be prepared to not upgrade the rest of the system. Yes, that is tricky when facing Windows' constant need for defensive updates. Factor that latter hazard into your business case.
Thank you. I was also working with a client who's IT security is extremely tight and they were hoping it would work on the latest version.
Hoping that the Client Launcher would work on the latest version of Java?
Yeah... "extremely tight" security, but running 10+ year old unsupported software.
2 Likes