Our Luminis setup has the message gateway(LMG) that would normally accept these events configured for local network access only. We would have to open a hole in our firewall to allow outside network access which would allow anyone using AWS to attempt to connect to it. This *should* be okay, but I guess we are a bit paranoid. AWS has lots of customers.
Additionally, we have a second student system that is not banner(or peoplesoft, not a major vendor even) that syncs to canvas and that may potentially need to support grade push later on. So in both the data sync to canvas(users,courses,enrollments,etc.) and the grade push, we would have ended up with one using LMG and one custom. If we have to write custom anyway, just use it for both was our thinking.
Our java app uses .properties to configure each data source, both for data sync to canvas as well as grade posting. So it can support several datasources. For example:
config.1.name=Banner
config.1.jdbc.url=...........
config.1.datasource.sql.user=select distinct * from.........
config.1.datasource.sql.course=select distinct ............
config.1.datasource.sql.section=select distinct ...........
config.1.datasource.sql.enrollment=select * from .........
config.1.datasource.sql.gradesync_proc=ZUAH_PUSH_ONE_GRADE(?,?,?,?,?,?)
config.2.name=XYZ
config.2.jdbc.url=...........
config.2.datasource.sql.user=select distinct * from.........
config.2.datasource.sql.course=select distinct ............
config.2.datasource.sql.section=select distinct ...........
config.2.datasource.sql.enrollment=select * from ........
config.3......
This discussion post is outdated and has been archived. Please use the Community question forums and official documentation for the most current and accurate information.