I think the problem here is that the TWS and Gateway installers now include their own ‘hidden’ copy of Java, this being an Oracle Java that I pretty much guaranteed to work well with that particular version of TWS/Gateway. The rationale for this is that a) it means the user doesn’t have to take the trouble to install and maintain a suitable Java version; and b) this should reduce support problems for IB because in theory the user will not accidentally use an incompatible Java version.

?

Now, the actual Java compiled class files, being pure Java, are I believe identical on all platforms for TWS and Gateway, and should run with any Java VM. So in theory you should be able to install TWS/Gateway on another machine (Ubuntu perhaps or even Windows) and then just copy the relevant jar files over to the ARM machine. You’d then need to install a suitable Java on the ARM machine: I don’t know whether Oracle produce a Java version for the ARM architecture, but if they don’t you might be able to find another implementation. Ah, I’ve just discovered that indeed Oracle do support ARM.

?

Once you’ve got the JAR files and the Java runtime in place, it should just be a matter of using an appropriate Java command with the correct arguments to start the thing off. I can help with that because that’s exactly what IBC/IBController do under the covers.

?

So if you think this might be an avenue worth pursuing, then please let me know and get Oracle Java installed . I’ll then post the details of which jar files to copy, and the appropriate Java command (I can’t be bothered to go and look this up unless you’re actually going to use it).

?

Needless to say, there’s no guarantee this will work, but there’s also no obvious reason why it won’t.

?

Richard

?

?

?