In the Cleo Integration Cloud (CIC), an Endpoint represents a source or destination for data you want to move. For instance, you create Endpoints for each of your customers, partners, and back-end systems that you want to integrate with. An Endpoint is defined within CIC, but the actual data source resides outside of CIC. You can create different types of endpoints, including AS2, SFTP, and FTP, depending on what protocol you intend for the endpoint to either send or receive data over.
There is a special type of Endpoint, called Transformation, used only to transfer data in to and out of the CIC Integration Engine. You do not need to create this Endpoint. The CIC Cockpit comes preconfigured with the Transformation Endpoint ready to use.
Using Cloud Monitors and Adapters
In the CIC Studio, there are two objects that allow you to connect to a specific endpoint, thereby providing the means of connecting to the CIC and allowing data to flow to and from the actual integrations built in the Studio. These objects are the Cloud Monitor and Cloud Adapter.
- A Cloud Monitor waits for incoming payloads and launches an Event to execute Business Process(es) to process the incoming payloads. In this way, Cloud Monitors are similar to other monitors in Clarify. However, in the case of CIC Studio, Cloud Monitors monitor Endpoints created in Cleo Integration Cloud rather than the file system (File Monitor) or databases (Database Monitor). For more details, see Cloud Monitors.
- A Cloud Adapter is responsible for ensuring files coming out of the transformation engine are sent to their final destination Endpoint. For more details, See Cloud Adapters.
You can connect CIC to an existing on-premise or private cloud database or to the CIC database. Either type of connection allows you to use the database as a Data Source in your integrations.