About the E-form Repository
E-form integration requires communication with My webMethods Server as a JSR-170 repository containing an instances folder and, if desired, a templates folder. When configured as a JSR-170 repository, My webMethods Server must have network access to Software AG Designer and the webMethods run-time components (Integration Server, Process Engine, and Task Engine).
Templates and instances must be maintained in separate folders in the e-form repository. After you set up an e-form repository, you must configure one or more e-form environments in My webMethods and deploy these environments to the Integration Server host(s) where e-form enabled processes will be running.
By deploying an e-form environment, you are specifying the repository location of your e-form templates and e-form instances to the various components, so the templates and instances can be retrieved as needed during design time and run-time activities:
During design time activities with
Software AG Designer, the deployed e-form environment enables you to locate and select an e-form template for importation as an IS document type or as business data for a task.
During run-time activity, the deployed environment identifies the e-form instance folder; the
Process Engine continuously monitors this folder for the arrival of new instances of an e-form to start a new business process.
Also during run time, if you implement the ability to download/upload an e-form from a task instance running in
My webMethods, the
Task Engine must have access to the e-form template location.
For more information about creating and deploying an e-form environment, see
Configuring and Deploying an E-form Environment.
