About Using the Content Service Platform As an E-form Repository
E-form integration requires communication with a webMethods Content Service Platform (CSP) repository configured with an e‑form templates folder as well as content folders containing e-form instances. webMethods Content Service Platform must have network access to Software AG Designer and the webMethods run-time components (Integration Server, Process Engine, and Task Engine).
Document types with e-form templates must be stored in the folder
Software AG_directory /CSP/system/templates.
Document types with e-form instances can be stored in any folder (node) in the repository.
After you set up a CSP repository, you must configure one or more CSP environments in
My webMethods and deploy these environments to the
Integration Server host(s) where e-form enabled processes will be running (see
Configuring and Deploying a webMethods
Content Service Platform Environment).
By deploying a CSP environment, you are specifying the CSP 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 CSP 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
Content Service Platform continuously monitors this folder for the creation of or modifications to 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 a webMethods
Content Service Platform Environment.
