FileCatalyst Direct as “Building Blocks”

posted in: Blogs, FileCatalyst | 0

FileCatalyst Direct is marketed primarily as our point-to-point file transfer system. At its most basic level, the solution requires server-side installation (FileCatalyst Direct Server), and a connection from a client option. On the client side, you don’t even need installation—options like our Web Applets don’t need anything from the client except an internet connection and a browser.

Another purpose is to augment existing FileCatalyst Webmail or FileCatalyst Workflow deployments. Adding a FileCatalyst Direct Server is one of two ways to enable our UDP-based acceleration, and having multiple FileCatalyst Servers allows for increased scalability as well.

But a third way to approach FileCatalyst Direct is to use it as a set of “Building Blocks” for a file transfer solution. Here are a few ways that people use FileCatalyst Direct as Building Blocks. Naturally, this isn’t exhaustive… once you start combining the various tools (adding a Direct Server and a HotFolder solution to your Workflow deployment, for example) the possibilities grow exponentially:

  1. Web Applets:
    • Adding with default GUI: You might already have a web-based application in place, but wish to augment it with file transfer that goes beyond HTTP/FTP. Adding our applets with default GUI is the quickest way to bring accelerated file transfer to your application. Configuration can be dynamically set on the fly with Javascript, PHP, ColdFusion, or other web languages.
    • Adding with Javascript API: When a more custom solution is needed, you can build your own look and feel, and call FileCatalyst events with Javascript functions. Javascript plays nicely with other web technologies, as well.
  2. Command Line:
    • Trigger from Application: Many programming languages are able to ouput commands to the console. If you can output to the command line, you can initiate a FileCatalyst-accelerated transfer.
    • Trigger from Script: You might already have existing scripts that use some sort of command-line FTP transfer. Replace the FTP commands with FileCatalyst commands to accelerate the scripted transfers.
  3. SDK:
    • Our SDK needs pages of description, but suffice it to say that any SDK has as its sole intention the ability to expose functionality to developers. We provide a native Java API, as well as ways to develop in .NET. The Javascript API and CLI are already mentioned above, and is also part of the SDK. Bottom line: if you are programming in Java or one of several other languages, there is a way to initiate FileCatalyst transfers.

The point being: if you have been looking at Direct as only an “out of the box” point-to-point solution, you’re missing the real strength of the product, which is its flexibility. No imperative to use only one particular file transfer system when you can essentially create your own!