Other E-form Template Storage Options
In addition to storing an e-form template in a content repository, it is possible to use the following storage options:
You can store e-form templates in a standard file system location, with the following requirements:
During design time, the location must accessible from the location where your
Software AG Designer instance is running. Designer provides a file system browse feature so you can locate and select an e-form template in the file system for importation as an IS document type or as business data for a task.
During run time, the location must be accessible from your
Task Engine host if you implement the ability to download an e-form from an e-form enabled task instance interface running in
My webMethods. The
Task Engine formats the e-form business data using the associated template for downloading.
You can avoid this requirement by attaching a copy of the e-form template to an e-form enabled task application at design time. For more information, see the webMethods BPM Task Development Help.
E-form templates can also be stored on a web server and made available with standard http access (the web server must be available to Designer at design time and to the
Task Engine at run time).
Note:
You cannot use a file system location for the instances folder; the instances folder must always be located in My webMethods Server configured as a JSR-170 repository with network access to the run-time components.