Ellucian Colleague Ethos Connector Overview

Modified on Mon, 30 Sep at 12:39 PM

Ocelot Logo

Ellucian Colleague Ethos Connector Overview

Introduction

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 connector. 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.

Implementation Steps

Below we outline the implementation steps required for full Ellucian Ethos Connector as compared to Ocelot’s approach, showing which steps do not need to be performed.

Implementation Step	Ellucian Ethos	Ocelot
Install/configure Colleague WebAPI	X	X
Open Firewall Ports	X	X
Clean Colleague data	X	X
Maintain Colleague indexing	X	X
Create GUIDs	X	X
Setup Colleague Integration Parameters (CDIP)	X	X
Create Colleague Users for API requests	X	X
Create Colleague Admin User for Publishing Notifications	X	X
Create Colleague User for Warm Up Script	X	X
Setup Colleague in Ethos Connector	X	not needed
Specify EMS Settings in Colleague	X	not needed
Configure ISO Codes	X	not needed
Install Ellucian Messaging Service	X	not needed
Configuring RabbitMQ	X	not needed
Configure EDX: subscribers and triggers	X	not needed
Install Ellucian Message Adapter	X	not needed
Configure Tomcat/WebLogic server	X	not needed
Schedule Warm Up Script	X	X

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.