Kickstarting Banner Integration deliverables discussion Friday
Thu 9/23/2021 11:34 PM
Matthew Brookover <mbrookov@mines.edu>
I did go ahead a pull up a few notes.
CSP Banner Integration Working Group notes Round 1
Banner Integration Working Group Notes Round 2
We produced this document: Banner Schema Cross Walk. Schema questions started on April 3rd call in CSP Banner Integration Working Group notes and continue throughout all of the meetings.
We also developed a prototype BEIS connector and an Ethos connector. Both pulled records from Banner and dumped them to Rabbit MQ. Later on, we talked about using the REST connector super class in midPoint to connect directly to Ethos.
I noted a few milestones:
May 1st, 2018 call, Mark Bollembach from Ellucian attended — learned a lot about Ethos. Ethos only supports polling, no push model. First discussions about WSO2 and Banner. Robert Ward, University of Michigan Dearborn was using WSO2.
May 10th (CSP F2F meeting) - Igor Frenic (evolveum) attended, lots of discussions about integration between Grouper, midPoint and data getting fed from Banner. Where does policy live? should we use Ethos, BEIS, or JDBC to move data?
Got API keys from Mark for Ellucian Ethos demo environment.
Integration discussions continued for many meetings. Eventually we settled on Grouper hosting policy and midPoint provisioning accounts.
June 12 - practical discussion on deploying midPoint - Oragan state (Andy and Erica) had made a lot of progress on an implementation. also discussed how to use Eclipse to manage configuration files
July 10th, more schema discussions, Started work on Schema Cross Walk based on data from Lafayette, Rice, Oregon State, and Mines. This continued, along with discussions about data base and scripted SQL connectors. There were also questions about Auditing.
Some where along the way, did a demonstration of Ethos feeding a user to midPoint via Rabbit MQ at Global Summit 2018.
September 18th - Igor/Evoveum offered to develop scripted SQL connector for Banner. As I recall, No one had funding to support the project.
A common request: I want a guide that explains how to set up Banner with midPoint and Grouper.
October 2nd, CSP over, meetings stopped.
Thoughts:
Databases allow for a very flexible schema. Databases are fast, allow for updates and reconcilliation. Every school we talked too had a different schema
BEIS narrows down the set of attributes, allows for real time updates, no reconciliation, again flexible schema
Ethos - API has the Ethos schema, same schema for all schools. should be possible to develop a connector that would allow for updates and a full dump for reconciliation, Ethos API can be very slow. According to Mark, 556 interfaces into Ethos API
Flexible schemas make it difficult to write a deployment guide. Ethos can be difficult to deploy, not many schools have Ethos set up. If every school ran Ethos, an Ethos deployment guide would be much simpler to write then a guide for databases or BEIS.
August 6th, 2019 - restarted, new scribing doc - similar discussions on Ethos, Databases, BEIS
September 3rd, 2019, Mark Bollemboch joined meeting, discussions about Ethos continued for a while
September 24th, Asynch connector for midPoint, AMQP
October 15th, 2019, walked throught midPoint complex demo
November 5th, Ehan Kromhout discusses Word Press connector and connector development
January 7th, 2020 REST Connector super class and Ethos discussions
Discussions about both BEIS and Ethos continue
March 3rd, 2020 - Workday
March 10th, detailed discussions of BEP - Banner Enterprise Provisioner - implemented with Rabbit MQ and JSON messages.
April 21st 2020, planning for midPoint Integration Manual
April 28th, 2020, May 12 - Ketih L, connector work, read schema from config file, https://github.com/GRdevOps/midPoint-Connectors/tree/master/rabbitMQ-connector
May 26th, 2020, Ethan, SCIM service, processed 600,000 records in 20 hours
It is getting late… I will continue later
Matt
From: Keith LeValley <klevalley2@davenport.edu> Sent: Wednesday, September 22, 2021 2:33 PM To: Matthew Brookover <mbrookov@mines.edu> Cc: Keith Hazelton <hazelton@internet2.edu>; Ethan Kromhout <ethan@unc.edu> Subject: Re: [External] kickstarting Banner Integration deliverables discussion Friday
KeithH,
If we were going to restart the conversation I would start with a few big picture questions.
How are you getting the data from Banner? Ethos, BEIS, BEP, etc
What does your schema look like? What data do you need from Banner, what data do you need to push to Banner. Is the information available in a single view or are you cobbling together multiple tables
Are you publishing to midpoint or are you routing through Grouper 1st
What are your constraints? Do you have access to BEP, do you need real time sync, do you do year round enrollment or is your enrollment window later summer, early fall
If you turn the above into a decision tree then you start to see how this becomes very messy. How do you provide a solution to govern all the possibilities?
So maybe what would be most useful is to set some limits early on what we are trying to solve. Then once we have a solution then we can work on dealing with other use cases beyond that.
On Wed, Sep 22, 2021 at 11:36 AM Matthew Brookover <mbrookov@mines.edu> wrote:
I will scan through the notes and get back to you.Matt
KeithL, I agree with your conclusion 100%. So let’s spend time Friday coming up with some specific problems in need of solution and then figure out how to chose the first to work on. --KeithH
Keith Hazelton
Wed 9/22/2021 10:22 AM
MattB, KeithL, EthanK, I’ve been reviewing notes on Banner from the Software Integration meetings and could highlight things that we might want to use in developing Banner Integration deliverables. Could one of you scan the Banner Integration meeting notes