Grouper Developers Forum

[Chris Hyzer <>]

The messaging interface we are looking at is very simple, so it will not be 
difficult to add more implementations if someone needs them, especially if 
the provisioning components use those interfaces and not a vendor specific 
messaging technology.

Thanks,
Chris

-----Original Message-----
From: 

 
[mailto:]
 On Behalf Of Waldbieser, Carl
Sent: Tuesday, January 27, 2015 10:02 AM
To: 

Subject: [grouper-dev] Grouper Messaging connector question


On the "Post PSP Provisioning" page [1] it looks like the current thinking is 
that Grouper will be able to target messaging middleware that can then 
forward the events on to software that does the actual provisioning.  In the 
last minutes email that went out I noticed this:

  "Grouper will ship with provisioning connectors to internal, AWS and 
ActiveMQ".

For the ActiveMQ item-- is Grouper going to be targetting a protocol like 
AMQP[2] or STOMP[3]?  I realize it may be too early for a definitive answer, 
but I am curious as to whether support for ActiveMQ is going to translate 
into support for any messaging system that supports a given protocol (e.g. 
similar to how LDAP and HTTP servers are fairly interchangable) or if there 
are idiosyncrasies particular to each messaging platform that need to be 
addressed by Grouper (closer to how the RDBMS landscape looks today).

Thanks,
Carl Waldbieser
ITS System Programmer
Lafayette College


[1] https://spaces.internet2.edu/display/Grouper/Grouper+Messaging+System
[2] http://www.amqp.org/
[3] http://stomp.github.io/