After receiving questions about the second part of this blog series, I decided to write this 4th and final part. Just to make things clear on how to use the Message Type and what the adapter does with it.
In the lower part of the referenced blog, you can see the SourceMessageType being just “o” in the monitoring screenshot. Also the XML representation shows the “o”.
If the JSON message doesn’t have a named structure as root, the adapter translates to “o” for JSON objects and “a” for JSON arrays.
I now modified my input data to reflect the Message Type I created in the ESR
When you verify the Message Monitoring again, you can see the Message Type being reflected.
Hope this clarifies…