About Monitoring E-form Listeners
When you configure a receive step in a business process model to use an IS document type created from an e-form instance, you specify two pieces of information:
The name of the e-form being used with the receive step.
The location of the instances folder where new instances of the e-form will be delivered.
When the process model is generated, the Process Engine creates a listener component that monitors the named instances folder for the arrival of a new instance of the named e-form. That listener component is enabled when the process model is enabled.
When the listener detects the arrival of a new instance, a flow service begins the process of converting the e-form into the correct IS document type, according to the relationship defined when the e-form template was initially imported. The resulting IS document type is then passed to the receive step.
If the listener component is not running, no new processes instances will be started even if e-form instances are arriving in the monitored folder.
Be aware of the following key points:
Do not configure two or more process models to monitor the same instances folder. There must be a one-to-one relationship between an instance folder and a single listener component.
If the repository server on which the monitored listener folder is located stops running, or if network connectivity to the repository server is lost, the listener component will stop running and must be restarted manually from the
Process Engine dashboard; for more information, see
Monitoring and Starting E-form
Listeners.
If you are using
My webMethods Server as a repository, and an e-form instance is delivered into a monitored instances folder when
My webMethods Server is not running (for example, by WebDAV connection), the e-form instance will not trigger the monitoring process when the listener component is restarted.