Grouper Users - Open Discussion List

[Keith Hazelton <>]

JBoss FUSE Supports AMQP 1.0 while both MuleSoft and WSO2 support AMQP 0.9.1, 
not 1.0, so it's good that Grouper supports both ActiveMQ (AMQP 1.0) and 
RabbitMQ (AMQP 0.9.1) for interoperation across (and between) the major 
Integration as a service vendors.   --Keith

-----Original Message-----
From: Keith Hazelton 
Sent: Monday, August 7, 2017 12:27 PM
To: TIER-API 
<>;
 grouper-users 
<>
Subject: RE: [tier-api] grouper rabbitmq messaging

None taken, Chris.

In my mind, you already support a broad enough swath of clients. The question 
gets simpler now: Which client should TIER use In situations where we get to 
choose, such as for our own demos, integrations and reference 
implementations.  

Adopting campuses may opt for any of the supported clients for their own 
integrations between local services and Grouper messaging. That kind of 
approach makes sense to me.

             --Keith

-----Original Message-----
From: Hyzer, Chris 
[mailto:]
 
Sent: Monday, August 7, 2017 12:17 PM
To: Keith Hazelton 
<>;
 TIER-API 
<>;
 grouper-users 
<>
Subject: RE: [tier-api] grouper rabbitmq messaging

Im happy to do whatever Java messenging client someone wants me to.  Right 
now we have built-in, rabbitmq, activemq, and aws.  Is there another amqp 
server that someone is using that is not on that list that they will do 
grouper messenging with and is there a generic ampq java client that someone 
knows works with it and others?  Honestly, its not a lot of effort to 
implement the messenging interface with a specific client and I don't want to 
spend too much time figuring out why a generic client doesn't work or lose 
features that are specific to a messenging system.  Ok?  :)   Anyways, im 
happier with specific experience with clients and not wikis about how things 
should work in an ideal world if that makes sense :)  (no offense)

Thanks
Chris

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

 
[mailto:]
 On Behalf Of Keith Hazelton
Sent: Monday, August 07, 2017 1:12 PM
To: TIER-API 
<>;
 grouper-users 
<>
Subject: [grouper-users] RE: [tier-api] grouper rabbitmq messaging

AMQP and reference implementations are on the agenda for Wednesday's TIER 
API/Registry WG call.  See 
https://docs.google.com/document/d/1iVRCLNVZSbrfpPLYIy1f1-N82XvkeOHlhxJKfgoUoaQ/edit
 

             --Keith

-----Original Message-----
From: Keith Hazelton 
Sent: Monday, August 7, 2017 11:09 AM
To: TIER-API 
<>;
 grouper-users 
<>
Subject: RE: [tier-api] grouper rabbitmq messaging

The more I read, the more I think we have to do an evaluation of options 
here.  See, e.g. https://jira.spring.io/browse/AMQP-662 

                   --Keith

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

 
[mailto:]
 On Behalf Of Keith Hazelton
Sent: Monday, August 7, 2017 10:59 AM
To: TIER-API 
<>;
 grouper-users 
<>
Subject: RE: [tier-api] grouper rabbitmq messaging

Note for Spring users: Spring-jms supports AMQP 1.0, while Spring-amqp 
supports AMQP 0.9.  See stackoverflow message from last week:   
https://stackoverflow.com/questions/45461589/can-spring-amqp-connect-and-process-messages-from-amqp1-0-brokers/45462037#45462037
 

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

 
[mailto:]
 On Behalf Of Keith Hazelton
Sent: Monday, August 7, 2017 10:52 AM
To: Eszes, Gabor 
<>;
 Gettes, Michael 
<>;
 Chris Hyzer 
<>
Cc: TIER-API 
<>;
 grouper-users 
<>
Subject: [grouper-users] RE: [tier-api] grouper rabbitmq messaging

RabbitMQ does have a plug-in for AMQP 1.0 
(https://github.com/rabbitmq/rabbitmq-amqp1.0/blob/rabbitmq_v3_6_10/README.md 
).  Chris, what do you think? It would be much better to be on AMQP 1.0 if 
feasible.

           --Keith

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

 
[mailto:]
 On Behalf Of Eszes, Gabor
Sent: Monday, August 7, 2017 10:46 AM
To: Gettes, Michael 
<>;
 Chris Hyzer 
<>
Cc: TIER-API 
<>;
 grouper-users 
<>
Subject: [grouper-users] Re: [tier-api] grouper rabbitmq messaging

The reason the product keeps being specified is because the Wiki page for 
'Grouper Messaging with RabbitMQ' [1] talks about an integration which uses 
amqp-client-4.0.2.jar by RabbitMQ [2], which implements the AMQP 0.9.1 
protocol [3]. Although RabbitMQ promulgated the AMQP spec first, the later 
version AMQP 1.0 is not compatible, and that's the version that has seen 
adoption in other messaging products. Therefore, this Grouper integration is 
indeed compatible with RabbitMQ, but essentially no other messaging product, 
making the distinction important.

[1] 
https://spaces.internet2.edu/display/Grouper/Grouper+Messaging+with+RabbitMQ
[2] https://github.com/rabbitmq/rabbitmq-java-client/tree/v4.0.2/
[3] https://www.rabbitmq.com/api-guide.html


________________________________________
From: 

 
<>
 on behalf of Gettes, Michael 
<>
Sent: Monday, August 7, 2017 8:30 AM
To: Chris Hyzer
Cc: TIER-API; grouper-users
Subject: [grouper-users] Re: [tier-api] grouper rabbitmq messaging

I am excited about this capability.  From the conversations I have 
participated this work was supposed to be about supporting the AMQP protocol 
and not specifying the product - RabbitMQ.  AMQP is supported by nearly all 
the popular messaging products.  I think it would be wise to go with AMQP 
support for Grouper and not specify the product.

/mrg