IBM BPM, V8.0.1, All platforms > Create processes in IBM Process Designer > Modeling processes > Integrating with Enterprise Content Management (ECM) systems > Inbound events from Enterprise Content Management systems
Performing modeling tasks for inbound events
To receive information about inbound content events that originate from changes to documents or folders on Enterprise Content Management (ECM) servers, you need to use Process Designer to perform the modeling tasks of creating and configuring components that can detect and respond to the content events.
The following components are created as a result of performing the modeling tasks:
- An event subscription for the process application
- An attached service for the event subscription that will invoke the Content undercover agent (UCA)
- A Content UCA to trigger a content event
- A content event for the business process definition (BPD), such as a content Start or Intermediate event, which will catch or throw interactions with an ECM server.
Although information about creating the required components is found in the modeling topics below, it is generally recommended created all of the components at the same time by following the instructions in the topic Subscribing to document events: the end-to-end approach. This is a simpler approach than creating each component separately on a stand-alone basis and it automatically creates some resources that you would otherwise need to create manually.
- Subscribing to document and folder events: the end-to-end approach
To detect and respond to document and folder events that are produced when content changes occur on an Enterprise Content Management (ECM) server, you need to create several components in Process Designer. Using the end-to-end approach described in this topic, you will find that creating the required components is more automated and less complex than creating them one at a time on a stand-alone basis.- Create event subscriptions
In Process Designer, you can create and configure an event subscription for a process application, which is used to obtain information about document and folder events that occur on an Enterprise Content Management (ECM) server.- Content event types
When you configure an event subscription in Process Designer, you must specify the type of content event that you want to receive when a specific content change occurs on an Enterprise Content Management (ECM) server.For example, if you want an event to be received when a user creates a document on an ECM server, you would select the Created event type.
- Create attached services
To enable an event subscription to respond to events from your Enterprise Content Management server, you need to create an attached service that can be used to invoke a Content UCA.- Create an undercover agent for a content event
To obtain information about document or folder events on an Enterprise Content Management (ECM) server, create and configure a Content UCA that works with your event subscription. A Content UCA is used to initiate a BPM Start or Intermediate event when specific content changes occur on an ECM server. It is conceptually similar to a Message UCA, but it has a specialized Content marker to differentiate it from a Message marker.- Adding a content event to a BPD
In a BPD, a content event is used to catch or throw interactions with an enterprise content management (ECM) system. You can add one of several types of content events, such as a Start event, Intermediate event, Boundary event, or Event Subprocess Start event.- The ECMContentEvent business object
The ECMContentEvent business object is included in the Content Management toolkit, which is used to gain access to Enterprise Content Management (ECM) types and services. The resources of the toolkit are required to allow a business process developed in Process Designer to work with an Enterprise Content Management system. The ECMContentEvent business object is used to pass generic ECM event data to an event subscription service and Content UCA. The business object is passed unchanged as BPMN event data into the process if it is not modified, mapped, or replaced by the service or UCA.