Due to security guidelines for downloaded files on certain MacOS platforms, few steps have to be executed in order to get the inspectIT UI (RCP) running.
Please note that:
|
By default, MacOS marks all downloaded files, which can be executed, as unsecure and adds a quarantine flag that prevents the access to it. Unfortunately, all plugins used by the inspectIT UI are shipped as Jar files which will be classified as unsecure. Due to this, the inspectIT UI is not able to load the required bundles and the start will fail.
The quarantine flag can be removed from the inspectIT files by executing the following command:
xattr -r -d com.apple.quarantine /path/to/inspectIT.app |
Since version 1.8.3 the inspectIT UI is shipped with a run.sh
file which contains all the necessary commands to remove the quarantine flag and allows to start the inspectIT UI in an easy way.
This step is only necessary for versions prior 1.8.3. |
The inspectIT UI (prior version 1.8) comes with its own JRE which can cause problems or prevent the startup of the inspectIT UI in the latest MacOS version.
In order to get the it running, the shipped JRE has to be removed. This can be achieved by the following steps:
Note: When removing the shipped JRE a Java runtime environment has to be installed on the host system in order to use the inspectIT UI.