Grouper Developers Forum

["Michael R. Gettes" <>]

and getting things into grouper - we are developing a reverse process via AMQ 
as well.  yes, we know there are grouper-ws, but there are a variety of 
reasons for using AMQ for delivery, mostly because integrating via JMS and 
the async mechanism is more appropriate - like with OIM.  As noted, dreaming 
up the messages is the central issue.  I regret that with our first version 
of GAP we did not version stamp the messages - which is kinda important to do 
to evolve things smoothly.

/mrg

On Aug 14, 2014, at 2:13 PM, Steven Carmody 
<>
 wrote:

> On 8/14/14 11:32 AM, Michael R. Gettes wrote:
>> Thanks Tom… I do appreciate your comments.
>> 
> 
> Tom -- what's the process for starting the v2.3 provisioning discussion ? 
> Are you collecting use cases ?
> 
>> 
>> I have expressed my comments on the spaces page about provisioning and I
>> am working with DaveL to help in learning about AMQ.  I do take the
>> perspective of the grouper team should include AMQ and concentrate on
>> providing appropriate tools for getting grouper messages to AMQ,
>> possibly in various forms.
> 
> There seems to be a growing number of sites that are using AMQ (or a 
> similar system) as part of their provisioning. Here at Brown we're 
> wondering if there's now enough experience to begin a discussion about 
> standardizing some of the messages, and including a few "standard" 
> connectors with a Grouper distribution ? Currently, only sites with some 
> available programming cycles can adopt this approach; standardization might 
> make adoption easier for additional sites.
> 
> Yes, I know standardization is hard. But, perhaps we can find the common 
> 80% ?
> 
> Michael calls out "getting grouper messages to AMQ". I'd add that its just 
> as important to think about msgs that get data into Grouper (real time 
> updates from ERP systems).
> 
> 
>