Cleo Integration Cloud - Cloud Edition compared to the Private Cloud Edition (aka Cleo Harmony) provides many of the same functionalities. However, there are some key differences that current Cleo Harmony customers will experience when they migrate to Cleo Integration Cloud (CIC) - Cloud Edition. This article outlines those differences.
Cleo Harmony protocol host and mailbox become CIC protocol connection endpoints
AS2, FTP, and SFTP protocol hosts and mailboxes are refactored in CIC as AS2, FTP, and SFTP endpoints, respectively. The most common and applicable protocol settings are available in CIC. Multiple mailboxes within a host become multiple endpoints.
CIC also provides an Email endpoint as a replacement for the Cleo Harmony SMTP client and server. However, this is not a direct migration like AS2, FTP, and SFTP endpoints. Where Cleo Harmony provided its own SMTP domain and account, in CIC the customer must provide their own email account for exchanging documents with a trading partner over email and the Email endpoint is configured to use that account.
Cleo Harmony user host and mailbox become CIC Partner Mailbox endpoints
Cleo Harmony user hosts and mailboxes become Partner Mailbox endpoints when migrated to CIC. If there are multiple users, each user becomes a separate Partner Mailbox endpoint. LDAP or any custom authenticators for these users are not supported in the Cloud Edition.
User access through FTP, SFTP, and Cleo Portal connections is available the same in CIC as in Cleo Harmony. However, keep in mind the partner mailbox user namespace is global across all customers in the Cloud Edition (i.e. usernames are required to be unique CIC wide).
Cleo Harmony certificates become CIC signing/encryption certificates (endpoint) or trusted certificates (tenant)
Unlike on-premise Cleo Harmony, CIC does not have a centralized certificate manager. Certificates migrated from an on-premise Harmony are one of the following:
- Signing/encryption certificates or keys explicitly configured in an endpoint: Certificates and keys can be imported and exported directly through the certificate fields in an endpoint. These certificates and keys can be reused in other endpoints if necessary (for instance, as a user certificate/private key).
- Trusted certificates stored at the tenant level: There is not yet a management UI for trusted certificates in the current version of CIC. However, untrusted trading partner server certificates can be trusted by running a dataflow and adding trust through the resulting job.
Cleo Harmony host/mailbox actions become CIC data flows
Cleo Harmony actions become CIC data flows. Data flows consist of a source and destination endpoint, which can be any of the endpoint types listed above plus a Transformation or File System endpoint.
In CIC, the integration between the Protocol Engine and the Integration Engine is direct rather than via a shared folder. This allows for the entire lifecycle of inbound and outbound payloads to be tracked more efficiently and effectively. Jobs are created with each occurrence of an integration, and so runtime log messages are available through the job.
Remaining on-premise integrations
If there remains a need to integrate with a local file system, a headless, lightweight on-premise CIC Agent can be deployed from CIC.
To establish an endpoint on a local system, you first create an Access Point (which includes installing the CIC Agent), and then create a File System endpoint pointed at a specific directory. Local shares can also be accessed as long as the user account running the agent service has the appropriate permission.