About the Operation of CSP Content Listeners
When you configure a receive step in a business process model to use an IS document type created from a Content Service Platform (CSP) document type, you specify the following information:
The name of the CSP document type being used with the receive step.
The location of the folder where the monitored CSP document type exists.
After you build and upload a CSP-enabled business process, the
Content Service Platform uses a content listener to continuously monitor the designated repository location for the creation, modification, deactivation, or deletion of the specified CSP document type. For information about creating content listeners, see
Creating a Content Listener.
The content listener is enabled when the process model is enabled. Detection of a monitored event causes Process Engine to start a new instance of the CSP-enabled business process.
After the business process starts, a flow service begins the process of converting the specified CSP document type into the correct IS document type, according to the relationship defined when the CSP document type was initially imported. The resulting IS document type is then passed to the receive step.
If a content listener is not running, no new processes instances will be started even if a CSP document type is created or modified in the monitored folder.
Be aware of the following key points:
Use caution if you configure two or more process models to use the same content listener. For more information, see
Deployment Considerations.
If the monitored CSP repository server stops running, or if network connectivity to the repository server is lost, the content listener will be unable to detect document type events and business processes will not be started.
