Skip to Content.
Sympa Menu

grouper-users - RE: [grouper-users] sending messages to AWS SQS

Subject: Grouper Users - Open Discussion List

List archive

RE: [grouper-users] sending messages to AWS SQS


Chronological Thread 
  • From: "Hyzer, Chris" <>
  • To: Ben Beecher <>, Vivek Sachdeva <>
  • Cc: " Mailing List" <>
  • Subject: RE: [grouper-users] sending messages to AWS SQS
  • Date: Wed, 20 Nov 2019 14:42:07 +0000
  • Arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=isc.upenn.edu; dmarc=pass action=none header.from=isc.upenn.edu; dkim=pass header.d=isc.upenn.edu; arc=none
  • Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=bAux8NalxMs5YNS1Suy47ysPpGEMYOILh2a7kfXrGSs=; b=HvbHERiLeQcHMkifsXW6YcUGQz57lth3/1SLA28ruWQfrvQzZt6672yaz3+kPTJoQGZ2hURHjncta34X1dIKl+TYAxwz6P0nBVnIsGXDOTvPZxWQ39rxpnyNJU6R8SCpw/vLgejLh0FQaz56tFDoW2soYMt83ry30SnIlxLN/2O3oi5353sS1dmhkNn1nPQMNwsMWdm+TgM0ebfjUx0vmdIgQoWIHdMq5kk700NLjKLRczRQD3aAZUNgRuy1kV7EXkRF1D0RhIt5c+CcXr8AGwh1+1jZbpx9YE2VtpZb9ugpoDiw7RVujqeKLs1I18yBGPHOq14FDb4M+dwQANf4yQ==
  • Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=bNKhgkXOGstUCxbUMmaA58/c1uObrVfpq3QCIF/dVCl4E2Zl7097Y14sk5H8e+5kaR2KmBFkN284Ju2NmBklRtgqefcKsX1mjMtmmJ9WsVsX5NmUGgXgn2+9cZTY0xNxUHBDQg11g+iWB90g8Dd2wPPULMv7v1Kc8AUCddyhKuvPDm3/VVzAV4rrgC/QK6i5NZdUEljt9jzUbeEHlx2apRyTEjzl6ctsofufBQF4q1c2tzKTH6VKT6nVQplAiC0rXAdvZkwSMoy7/WNEyspkstLtLtI+B0hs5TNLKYEriG4irWmUM+4ZzNxUUNwYtwNEgHiEzRBcyiF3wJvptAhC3A==

Did you set these in grouper.client.properties?

 

 

# sqs settings

grouper.messaging.system.awsSystem.accessKey = 

 

grouper.messaging.system.awsSystem.secretKey = 

 

 

changeLog.consumer.changeLogMessagingSample.queueOrTopicName = queue name in sqs?  Not sure
changeLog.consumer.changeLogMessagingSample.messageQueueType = queue

Don’t use these

grouper.messaging.system.awsSystem.defaultSystemName = grouper_memberships

grouper.messaging.system.awsSystem.defaultPageSize = 5
grouper.messaging.system.awsSystem.maxPageSize = 10

 

Please try that and send all sanitized configs you are using and the log messages

 

thanks

 

From: <> On Behalf Of Ben Beecher
Sent: Wednesday, November 20, 2019 9:30 AM
To: Vivek Sachdeva <>
Cc: Mailing List <>
Subject: Re: [grouper-users] sending messages to AWS SQS

 

Vivek,

Thanks for the quick response.

I didn't add these properties
changeLog.consumer.changeLogMessagingSample.class = edu.internet2.middleware.grouper.changeLog.ChangeLogConsumerToMessage
changeLog.consumer.changeLogMessagingSample.quartzCron =
changeLog.consumer.changeLogMessagingSample.messagingSystemName = grouperBuiltinMessaging
changeLog.consumer.changeLogMessagingSample.queueOrTopicName = sampleChangeLogMessagingQueue
changeLog.consumer.changeLogMessagingSample.messageQueueType = queue

because I thought they applied only to built-in messaging. If I were to
add these to grouper-loader.properties what would I use for "name of the consumer"?

this one is probably not needed because the AWS SQS doc says
"We don't support creating the queues. Setting autoCreateObjects property to true will do nothing."
loader.messaging.settings.autocreate.objects = true

Do I need these as well (for printing out messages)?
messaging.listener.messagingListenerChangeLogConsumerPrint.class = edu.internet2.middleware.grouper.messaging.MessagingListenerToChangeLogConsumer
messaging.listener.messagingListenerChangeLogConsumerPrint.changeLogConsumerClass = edu.internet2.middleware.grouper.changeLog.consumer.PrintTest
messaging.listener.messagingListenerChangeLogConsumerPrint.quartzCron = 0 * * * * ?
messaging.listener.messagingListenerChangeLogConsumerPrint.messagingSystemName = grouperBuiltinMessaging
messaging.listener.messagingListenerChangeLogConsumerPrint.queueName = sampleChangeLogMessagingQueue


I added these properties (from the AWS SQS doc) to grouper.client.properties

grouper.messaging.system.awsSystem.name = grouper_memberships
grouper.messaging.system.awsSystem.class = edu.internet2.middleware.grouperMessagingAWS.GrouperMessagingSqsSystem
grouper.messaging.system.awsSystem.defaultPageSize = 5
grouper.messaging.system.awsSystem.maxPageSize = 10
grouper.messaging.system.awsSystem.defaultSystemName = grouper_memberships


I added this to grouper-loader.properties

changeLog.consumer.esb.publisher.messagingSystemName = grouper_memberships

Ben

 

On Tue, Nov 19, 2019 at 7:58 PM Vivek Sachdeva <> wrote:

Hi Ben,

 

Can you please share the configuration you have for messaging? Specifically, what are the values you are using for the properties listed on https://spaces.at.internet2.edu/display/Grouper/Grouper+messaging+send+receive+change+log+adapter+example and https://spaces.at.internet2.edu/display/Grouper/Grouper+Messaging+with+AWS+SQS

 

No need to share aws access key and secret key here in the thread.

 

Thanks,

Vivek

 

On Tue, Nov 19, 2019 at 3:04 PM Ben Beecher <> wrote:

I installed the messaging module for AWS SQS in Grouper 2.4 and I updated our properties files with info about our message queue. There are no messages in the queue. How can I tell Grouper to create a message for every change in the change log?

 

Ben




Archive powered by MHonArc 2.6.19.

Top of Page