FileCatalyst® SDK

FileCatalyst SDK gives licensees the option to build the core FileCatalyst technology into their existing applications. This allows developers to create tailored applications with enhanced file transfer capabilities. FileCatalyst currently has two methods of integration: a Java API, and a SOAP / Web Services API.

FileCatalyst Java API

The Java API is the engine that drives all other FileCatalyst client applications, including the Hot Folder, Applets, and Command Line Interface. Using the API, you will be able to write your own FileCatalyst client applications, or integrate FileCatalyst transfers into your existing Java-based applications with very little effort.

FileCatalyst SOAP / Web Services API

The SOAP API sits on top of the Java API, providing a Web Services interface to initiate, as well as control and monitoring of FileCatalyst transfers. This is useful for integration using languages other than Java, or for integration into SOA-based applications.

The Web Services module is based on Apache Savan/Axis2, and provides publisher/subscriber functionality with full support for WS-Eventing. This means you do not have to poll the server for status updates. Simply subscribe to updates and they are sent automatically.

The Web Services engine runs alongside FileCatalyst Server, allowing transfer of files from one FileCatalyst Server to another. It can be installed either standalone or as a web application for deployment on a servlet container (such as Tomcat) or J2EE server (such as IBM's WebSphere).