Skip to content

PredixDev/rmd-orchestration

Repository files navigation

view javadoc   view github pages

RMD Orchestration- How this works

  • Orchestration, by design, will be listening on a specific queue for a specific TYPE of event. Queue name and the connection to the queue will be established at the deployment time.
  • Once the event is read from the queue, listener with the help of routing rules decide which orchestration to execute based on the event's message content.
  • Predix Orchestration Runtime executes the orchestration, which in turn, can invoke one or more analytics based on the content of message.

Sample FieldChangedEvent json

{
        "fieldChangedList": {
                "fieldChanged": [{
                        "assetList": {
                                "asset": [{
                                        "uri": "/asset/Compressor-CMMS-Compressor-2018",
                                        "assetType": "asset",
                                        "fieldList": {
                                                "field": [{
                                                        "fieldKey": "/asset/assetTag/crank-frame-dischargepressure",
                                                        "fieldValue": "",
                                                        "fieldType": "assetTag",
                                                        "timeChanged": "2012-09-11T07:16:13.000Z"
                                                }]
                                        }
                                }]
                        },
                        "externalAttributeMap": {
                                "entry": [{
                                        "key": "",
                                        "value": ""
                                }]
                        }
                }]
        }
}

Tech Stack

  • Spring
  • SpringBoot
  • SpringTest
  • Maven
  • Rabbit MQ

Microcomponents

More Details

Analytics