Grouper Users - Open Discussion List

[Rob Hebron <>]

Chris is right: it should work with the config he suggests.

ESB events are simply JSON representations of change log events. 
Properties are filled for events where they are available in 
edu.internet2.middleware.grouper.changeLog.ChangeLogLabels for that 
event - no more or added and none are removed. On a GROUP_ADD event (for 
example) the group name is got via ChangeLogLabels.GROUP_ADD.name, so 
this it appears in this property in the JSON doc. I'll review the 
documentation to check whether this is clear.

Rob

On 10/03/11 06:03, Chris Hyzer wrote:
> Im going through the code and see that for group events, the groupName 
> property isn't set, it's the name event...
>
> So...  try changing it to:
>
> ((event.eventType eq 'GROUP_DELETE' ||
>    event.eventType eq 'GROUP_ADD')&&
>       event.name =~ '^nyu\:apps\:atlas\:.*$')
> || ((event.eventType eq 'MEMBERSHIP_DELETE' ||
>    event.eventType eq 'MEMBERSHIP_ADD')
>    &&  event.groupName =~ '^nyu\:apps\:atlas\:.*$'))
>
> Thanks,
> Chris
>
> -----Original Message-----
> From: 
>
>  
> [mailto:]
>  On Behalf Of Erik Froese
> Sent: Wednesday, March 09, 2011 5:31 PM
> To: 
>
> Subject: [grouper-users] Re: XMPP notification filter to include GROUP_ADD 
> and GROUP_DELETE
>
> I just saw this in the grouper-loader logs.
>
> 2011-03-09 17:25:17,698: [main] WARN
> GrouperLoaderType.retrieveGroups(2675) -  - Group type grouperLoader
> does not exist, so no loader jobs about groups will be scheduled
>
> Could that be the problem? Would I need to set the group type for all
> of the groups I'd like to be notified about?
>
> Erik
>
> On Wed, Mar 9, 2011 at 5:04 PM, Erik 
> Froese<>
>   wrote:
> > Hey,
> >
> > I'm trying to use the XMPP/ESB component to send group and membership
> > events via XMPP. So far the membership events are sent but not the
> > group add/delete events.
> >
> > Here's the filter I'm using (broken up for readability)
> >
> > (event.eventType eq 'GROUP_DELETE' ||
> > event.eventType eq 'GROUP_ADD' ||
> > event.eventType eq 'MEMBERSHIP_DELETE' ||
> > event.eventType eq 'MEMBERSHIP_ADD')
> > &&  event.groupName =~ '^nyu\:apps\:atlas\:.*$'
> >
> > I cranked up the logging on the EsbConsumer class to DEBUG.
> >
> > Here's the excerpt from the log.
> > 2011-03-09 16:58:00,055: [DefaultQuartzScheduler_Worker-6] DEBUG
> > EsbConsumer.processChangeLogEntries(56) -  - Processing event number
> > 241
> > 2011-03-09 16:58:00,055: [DefaultQuartzScheduler_Worker-6] DEBUG
> > EsbConsumer.processChangeLogEntries(79) -  - Event is GROUP_DELETE
> > 2011-03-09 16:58:00,056: [DefaultQuartzScheduler_Worker-6] DEBUG
> > EsbConsumer.addSubjectAttributes(536) -  - Adding subject attributes
> > to event
> > 2011-03-09 16:58:00,059: [DefaultQuartzScheduler_Worker-6] DEBUG
> > EsbConsumer.processChangeLogEntries(453) -  - Event 241 does not match
> > consumer filter (event.eventType eq 'GROUP_DELETE' || event.eventType
> > eq 'GROUP_ADD' || event.eventType eq 'MEMBERSHIP_DELETE' ||
> > event.eventType eq 'MEMBERSHIP_ADD')&&  event.groupName =~
> > '^nyu\:apps\:atlas\:.*$'
> >
> > The group was in the nyu:apps:atlas stem and membership events for
> > that group were previously sent.
> >
> > Am I missing something?
> >
> > Erik