Server and Web Applications

TFORMer SDK can be used by server applications through a supported programming interface or TFPrint. Select an interface and package that match the server operating system and process architecture. See Windows deployment or Linux deployment for licensing and required files.

Server-Side Output

A server application supplies a form layout and data, selects an output type and destination, and invokes the chosen TFORMer interface. Server-side output does not require a browser-specific client component.

The selected interface determines how form layouts and data are supplied. On Windows, the maintained TFPrint sample loads a stand-alone .tff from an HTTPS URL and imports XML data from a local file. See the TFPrint workflow for the documented URL and local-file combinations.

For the Java/JNI integration model, see the Java guide.

Runtime Account and File Access

Check access using the account that actually runs the service or web application, not only your interactive account. It needs:

• Read access to the selected layout and its external data and image files.
• For file output, permission to create or write files in the selected destination directory.
• A writable temporary directory for operations that create temporary files, such as downloading inputs or extracting archives.

Use only the access needed by the application. Do not assume that a service uses your interactive account's temporary directory or network access.

Direct URL Access

TFORMer SDK supports direct URL access for certain input types. Availability depends on the input type, protocol, and platform. If direct access is unavailable, download the required input files first and use local paths.

When downloading a repository for local use, keep its associated files and relative directory structure together.