Endpoints are listeners triggered on events. They enable integration requirements where the system needs to consume and execute a specific logic (encapsulated in a service) when an event is triggered. Each endpoint has a lifecycle bound to the package it resides in.
TORO Integrate ships with endpoint types that support events triggered from various sources:
- File changes in the local file system
- File changes in an FTP server
- Incoming email messages
- Incoming XMPP messages via Jabber
- Published JMS messages
- Changes in an RSS feed
The platform also provides auxiliary endpoints for:
- Exposing services as virtual directories
- Resuming or re-executing failed integration
- Adding an alias on long URLs
Continue on the next pages to see a more detailed guide for each endpoint type.
An endpoint's status indicates its current state and behavior. It only changes when an endpoint is started or stopped. Depending on the current status of an endpoint, some actions may or may not be performed. For instance, configuring an endpoint's properties or deleting it is not possible unless the endpoint is stopped.
There are five possible endpoint statuses:
The status of endpoints that are not running. In this state, an endpoint will not listen for events.
The status of endpoints that are currently running. In this state, an endpoint will listen for events and will act as configured once an event is intercepted.
The status of endpoints that have managed to start-up but encountered non-fatal errors.
The status of endpoints that have completely failed to start-up because of fatal errors.
The status of endpoints whose states are unknown; if an endpoint has this as its status, it most likely means that the
EndpointManagerhas failed to set the status properly.
An endpoint's state cannot be set manually; its value solely depends on what the