Process Starters
Some activities are used to start a process when an event occurs. For example, in the File palette, there is an activity named File Poller. This activity detects changes in a specified file and starts a process when the change occurs. This kind of activity is known as a process starter. When a process starter is placed into a process definition, it replaces the default Start activity, and becomes the first activity in the process.
You can only have one process starter in a process definition. You will receive a warning if you attempt to add more than one process starter to a process definition. The following table describes the available process starters.
When you deploy your project, you can place processes with different process starters on different machines. For example, you may wish to place all processes with a Receive Mail process starter on the same machine as the mail server so that the processes can poll the mail server more efficiently. For more information about deployment and specifying where process starters run, see
.
Palette |
Process Starter |
Starts a process when... |
ActiveEnterprise Adapter |
Adapter Subscriber Adapter Request-Response Server |
A message or a request from an adapter is received. |
File |
File Poller |
The specified file is created, changed, or deleted. |
General Activities |
Timer |
The specified time interval occurs. You can start processes for one-time events or schedule processes to start on recurring time intervals. |
Receive Notification |
A corresponding Notify activity has executed. |
|
HTTP |
HTTP Receiver |
An HTTP request is received. |
JMS |
JMS Queue Receiver JMS Topic Subscriber |
Either a JMS queue or topic message is received. |
|
Receive Mail |
Mail for the specified user is received by the mail server. |
Rendezvous |
Rendezvous Subscriber |
A TIBCO Rendezvous message is received. |
SOAP |
SOAP Event Source |
A SOAP web services request is received. |