My webMethods Server—You can use My webMethods Server as your e-form repository for storing e-form templates and e-form instances through a JSR-170 interface.

My webMethods—You must use the Central Configuration interface in My webMethods to configure and deploy e-form environment definitions. If you implement e-form enabled task applications, users will interact with the tasks in My webMethods; if you have implemented the ability to do so, they can download and upload e-form documents from within the task user interface.

Software AG Designer—You use Software AG Designer to import an e-form template and create a corresponding IS document type from it. You then use this IS document type to create e-form enabled business process models as well as e-form enabled task applications. You can also create e-form enabled CAF portlet applications in Designer.

Integration Server/Process Engine—You use the Integration Server/ Process Engine as the run-time environment for webMethods business processes. The Integration Server host is the target for your deployed e-form environment definition, and the Process Engine monitors the e-form instance folder defined in the environment for the arrival of new e-form instances, which can be used to start a corresponding business process.

webMethods Task Engine—If you have implemented e-form enabled task applications, the Task Engine manages these tasks and the e-form business data associated with the task. If you implement the ability to download an e-form from an e-form enabled task instance running in My webMethods, the Task Engine formats the e-form business data for downloading using the associated template, and, after uploading, modifies and saves the task business data with the modified data from the uploaded e-form.