Ocelot interfaces access Ellucian Colleague using Ethos API endpoints, but we do so by directly accessing these via a Colleague WebAPI instance hosted by your college, not the Ellucian Cloud.
Why do we do this? Many Colleague clients have not implemented full Ethos integration. By accessing your Colleague WebAPI directly, we reduce the setup and implementation timeline required for Ethos to work. Additionally, there is some slight performance improvement because requests don’t have to traverse the Ellucian Cloud before being transmitted to your WebAPI instance.
If your college already has Ethos setup and configured for Colleague, this approach will still work.
Below we outline the implementation steps required for full Ellucian Ethos Integration as compared to Ocelot’s approach, showing which steps do not need to be performed.
Thus, many of the Ellucian Ethos implementation steps for Colleague can be skipped saving time whilst still providing the functionality that Ethos affords for Colleague connectivity.