AMI Device Event messages are going to SGG-D3-EVENT destination instead of SGG-D3-CIM-Event Destination
(Doc ID 2504089.1)
Last updated on OCTOBER 11, 2022
Applies to:Oracle Utilities Smart Grid Gateway - Version 188.8.131.52.0 to 184.108.40.206.0 [Release 2.2 to 2.3]
Information in this document applies to any platform.
AMI Device Event messages are going to SGG-D3-Event destination instead of SGG-D3-CIM-Event Destination. This is causing the CIM Events to go to the wrong JMS Queue.
1. Customer has customized the CIM Events to send events to a different queue then regular LG Events.
To recreate this we must Setup a new JMS Queues in Weblogic to process CIM Events. For testing we added CIMDestinationQueue-D3 manually.
2.Open up the OSB Service Bus Console
3.Go to the SGG-D3-CIM-EVENT-CM->Business Service->DestinationBusinessService.
4.Under the Transport Tab point the Endpoint URI to this new JMS Queue.1.For testing stop processing payload files, make sure the queues for CIM Events and Events are empty, and pause consumption on these queues to see where the messages are being sent to.2.Drop a CIM Event payload.3.Look for the CIM Events in the queue that “CIMDestinationQueue-D3” JMS queue.4.No Messages are in this queue.
5.Now look at the Queue that the SGG-D3-Event’s are pointed to, you will see the CIM Event’s in this queue.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document