Home
Welcome to Cleo Clarify v5
Cleo Clarify supports every phase of business integration – building, integrating, and maintaining – in one simplified, streamlined product. An individual may create, test, and deploy integration processes from beginning to end, or Clarify can be used by teams with multiple participants and roles – including business analysts, developers, and IT operations personnel.
Designing Integration Solutions
This set of comprehensive topics describe the available resources, tools, and processes used to transform data as part of an integration solution.
Sending and Receiving the Data
This set of topics describe how to use objects to input and output data.
Web Services
Web Service objects are used to create, configure, and set up different resources needed to subscribe to a local or remote service, expose a service to remote clients, and manage the flow and manipulation of your data as either a service provider, consumer, or both.
Secure Authorization of Web Service Requests using a Clarify Server Vault
The latest Clarify server contains an authorization vault, which provides a secure storage location for API keys, tokens, username and passwords, headers, and other info used to authorize calls to external Web Services. This information can be maintained in one secure location, but accessed from multiple server environments and from different users.
Before you begin: Add User Profile with Vault Permissions
Cleo strongly recommends creating a User Profile with Vault permissions before setting up and using vaults between your Clarify servers. While the default server user profile (ebiadmin) contains the same permissions necessary for using the vault, there is a strong possibility of server errors and server session id conflicts if using that default user profile with Auth Vaults.

Before you begin: Add User Profile with Vault Permissions

Cleo strongly recommends creating a User Profile with Vault permissions before setting up and using vaults between your Clarify servers. While the default server user profile (ebiadmin) contains the same permissions necessary for using the vault, there is a strong possibility of server errors and server session id conflicts if using that default user profile with Auth Vaults.

System Administrators can create a User Profile from the Access Control view in the Admin Console. Please refer to the Access Control procedures for more information.

Required permission: Access Content in Vault

This provides the user with the ability to create, delete, and update auth info inside a vault entry. This does not allow for the changing of Alias or Environment.