Webform Server relies on two central components: a portlet or servlet, and a Translator. The Translator also contains a Shared File Cache subcomponent. The following diagram shows how these components are set up in a typical installation:
The portlet/servlet is installed on the application server. You can install the Translator on any computer that the application server can communicate with. Finally, you may also have a form repository or a form application from which the portlet or servlet retrieves XFDL forms.
The components perform the following functions:
Parent topic: Webform Server technical overview
- Portlet/Servlet — The portlet or servlet controls the form application, and processes all incoming and outgoing forms. It passes forms to the Translator for conversion, and may communicate with other applications or rely on a form repository. You must write the portlet or servlet yourself, and therefore it is unique to each form application. Webform Server provides a Framework that includes methods for doing this, as well as a sample servlet and sample portlet for your reference.
- Translator — The Translator converts forms between XFDL and HTML. When converting a form to HTML, the Translator stores the original XFDL in a Shared File Cache and saves some metadata about the form in an access control list. When converting a form back to XFDL, the Translator retrieves the original form from the Shared File Cache and transfers the data from the submitted HTML form.
- XFDL Form Repository/Application — This optional component may be a collection of XFDL forms that users may work with, or an application that will return XFDL forms.
- ACDB — The access control database, which processes and monitors active forms.