Currently, when using the API of Integrity (using the mskclient.jar as a library for all needed functions to communicate with the server) to connect to a server using a local integration point, the api will automatically start the client (assuming that `setAutoStartIntegrityClient`is called with `true` as the first parameter) which is set in the PATH environment variable at the first position. That, in general, works great, but is a problem when more than one client is installed on one machine and both are used to run a specific Java code using the MKS Api against a specific server (e.g. 10.8 and 10.9 as installed version).
A workaround would be, to adjust the PATH variable whenever I need to start another Integrity client. Unfortunately, this requires an ugly wrapper script for any Java code, which should be executed, to set adjust the PATH variable in this context only, or administrator permissions on a Windows machine to change it globally. Both ways aren't a real solution.