The FileCatalyst Direct Client Applications

FileCatalyst Direct includes a range of client options, which you may pick and choose from in order to accomodate different purposes within your organization:

  • HotFolder
    is a desktop application that is installed at the client side. With HotFolder, set up one or more “watched” folders, which transfer new or changed files automatically. HotFolder has rich filtering and bandwidth scheduling capabilities, along with a number of other tools to fully control your file transfer.
  • Java Applets
    allow you to embed accelerated file transfer into any webpage, resulting in a zero-installation experience for the end-user. Build a new file transfer web portal, or add the applets to an existing one. The Java Applets also appear in our FileCatalyst Webmail and FileCatalyst Workflow web applications.
    • 2-Way Applet: resembles an FTP client, with remote and local listings and options
    • Upload Applet: used when only uploading is required, or when upload events trigger the next step of a web application
    • Download Applet: used for download-only transactions, or when download events trigger a subsequent step in a web application
    • JavaScript API: build your own web based components for transferring files. Add accelerated file transfer functionality to your exisitng Flex, Flash or Sliverlight web components.
  • Command Line Interface
    can be triggered using scripts or by applications built in languages other than Java. If your existing process already uses command-line FTP, upgrade it with accelerated FileCatalyst transfers.
  • FileCatalyst SDK
    is available in Java, C# and JavaScript. Use the Client API to build an accelerated file transfer application or component. Use the Server API to build an interface for controlling the server. The Client API also includes a .NET wrapper and a JavaScript API for file transfers initiated via the web browser.
  • HTTP Tunneling Servlet
    provides HTTP failover and tunneling service for any FileCatalyst/FTP/FTPS server on your network. Due to restrictive firewalls or proxy servers, some clients might only be able to connect via HTTP to your servers. The servlet will run in any Java Application Server including: Tomcat, Jetty, Websphere and GlassFish.

Products