- About XNAT
- News & Events
- XNAT Marketplace
- Contact Us
Most modern browsers have ceased support for Java Applets. We recommend using the Desktop Upload Assistant for uploads in place of the Upload Applet. The XNAT download applet has been removed from the code base and replaced with a ZIP downloader. The following documentation has been preserved for archival reasons.
XNAT uses applets for a number of functions, mostly involving transferring data between the XNAT server and client applications. Signed and secure Java applets have a lots of capabilities that are required for managing DICOM data between the server and client, but they also have some unfortunate issues that can cause them to function improperly or not function at all depending on how your system is configured. Differences in browser, Java plugin version, and client operating system further complicates diagnosis of applet issues. This troubleshooting guide is intended to help you identify common issues that can be easily resolved and, in more complex cases, gather information that the XNAT team can use to help you diagnose the root problem.
Unlike most browser plugins, the Java plugin has its own control panel that you have to access outside of the browser. How you access this control panel depends on what operating system you're on and what version of the Java plugin you have installed.
On Windows platforms, the Java control panel is accessible through the main Windows Control Panel:
On OS X, the Java control panel is accessible through the System Preferences application:
On Linux, the control panel is accessed through the installed JRE or JVM:
The first steps in understanding issues related to applet functionality are pretty easy:
The applet cache is a mechanism by which the Java plugin increases performance. Once downloaded, Java libraries are saved in the cache to be used in subsequent calls to the applet. In theory, new versions of those libraries should replace the cached versions, but this doesn't always work properly. To ensure that you're getting the latest version of the libraries and clear out any possibly corrupted or invalid code, you can forcibly clear the Java applet cache.
If clearing the cache does not solve your applet execution problem, debug and trace logging can help give the XNAT support staff and development team better insight as to the particular issue occurring on your client.
You can view the log and trace data generated by turning on debug and trace logging by going to the log files that are written out to the system. This can often be difficult to locate, however, and varies greatly by operating system. An easier way to view the debug and trace logging is to show the Java plugin console when the plugin starts up. This provides the ability to view the logs as they're generated in real time.
Once you reload the applet, the console should open up simultaneously (or even a little before!). Once you've recreated any problems in the applet execution, you can just click the Copy button on the Java plugin console to copy all of the log data out, then paste it into a text file, email, or data transfer web site such as pastebin.
The console can become very annoying very quickly when you're not debugging. To turn it off, just follow the same procedure, but click Hide console instead.