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:
- Web Applets:
- 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.
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!