How to Update the Remote Admin JAR files in FileCatalyst Central
Posted by , Last modified by on 10 November 2016 05:00 PM


This article describes how to update the .jar files in FileCatalyst Central to remedy the Java Application Blocked message that Administrators receive when trying to launch the Remote Admin Applet in Central.

The Java message or pop-up is generated from a failed check for a security certificate. Our web based Java Applets and Applications are signed for 2 years from the date of the build. For the purposes of this article, any FileCatalyst Application connecting to FileCatalyst Central is referred to as a node.


FileCatalyst Central v3.6 and older.


  1. Determine what version of the .jar files you need for the nodes that are connecting to the FileCatalyst Central deployment. In Windows, look in the \FileCatalyst Central\www\Web Console\<client application> for all connected applications. Each folder in this directory will reference the version of FileCatalyst Application that Central has communicated with.  Or look in the nodes section in FileCatalyst Central.
  2. Shut down the FileCatalyst Central service.
  3. Rename the old applets to something different. Change the extension of the current .jar file to .jar.old. For example, the file FileCatalystHotFolderAdminApplet.jar would be renamed to FileCatalystHotFolderAdminApplet.jar.old. See the addendum at the bottom of the page.
  4. Download the appropriate version of the applets that you need from You will need to obtain the user-name and password to this location by logging into your account at
  5. Transfer the files to the appropriate directory for the version of the application you require from #2 above.
  6. Rename the new files and remove the build version portion of the name, for example, v3.5_build9_AppletLoader.jar to AppletLoader.jar.
  7. Replace the current AppletLoader.jar file from the \FileCatalyst Central\www\Web Console\lib with the AppletLoader.jar file from the previous step.
  8. Clear the Java cache from the system that is accessing the respective Remote Admins. This step has to be performed on all computers that use FileCatalyst Central. Go to for a detailed guide.
  9. Reopen the browser and clear your browser cache Ctrl-Shift-Delete (Windows) or Command-Shift-Delete (Mac)
  10. Restart the FileCatalyst Central service, this may take a few seconds.
  11. Log into Central as normal and test the Remote Admin Applets from the Nodes page.


Default location and names of the Applets.

  • FileCatalyst Central
    Be aware this is different than the AppletLoader.jar files contained in the application location.

    • Location: \FileCatalyst Central\www\Web Console\lib\
    • Filename: AppletLoader.jar

  • FileCatalyst Server

    • Location: \FileCatalyst Central\www\Web Console\FCServer\Default\ 
      Each build within this location is contained in a seperate folder.

    • Filenames: AppletLoader.jar and FileCatalystServerAdminApplet

  • FileCatalyst Hotfolder

    • Location: \FileCatalyst Central\www\Web Console\HotFolder\
      Each build within this location is contained in a separate folder.

    • Filenames: FileAppletLoader.jar and FileCatalystHotFolderAdminApplet.jar

Comments (0)