RTE to Azure - the great escape

Want to get your RTE messages into Azure Service Bus easily?  Of course you do.  Then you have complete control to write some cool code in Azure, that perhaps calls some orchestrations and then fires off some powerApps or does nice workflow - because sorry...  JDE does not do that too well.

What is an RTE?  Real Time Event, built in events in JDE that fire off when a condition occurs, like RTABOUT - Real Time Address Book Out - WOW.  Fires when there is an add or change to an AN8 entry...  Double wow.

You can get these going pretty quickly, but then what?  You are probably already bored.  But what if you created some Azure Message Queues, and then attached some code to them, even did some nice dashboards with Azure Monitor - you'd know how often things are changing and what time - that is cool too - like BAM.

The hard bit, is you might need to come to ask and purchase our EA that will sit and listen to your RTE queues and then shoot the messages off to your Azure.  You could send them to us and we can do all of your integrations for you (to be honest).

The weblogic screen looks a bit like below.  You can start and stop.  Because messages are guaranteed, this is a robust solution.  You can pause the queues, you have complete control of the downstream functionality.  This is really nice.

Another design advantage is this can be highly available. So you can have this running on multiple RTE servers that are active.  If JD Edwards does what it is supposed to do (doesn't it always) you could have multiple RTE servers, multiple listeners and this software will pull from the RTE server that actually got the message (they do fight sometimes).

There is a really simple config file to map JDE RTE queues to Azure Queues

This is a monitor that can show you the messages getting to Azure - now you need to start coding!

All done.  Reach out if you are interested in getting involved.  This is a pretty cool piece of tech to enabled more native integration to JD Edwards using Azure Service Bus.  This could also be used to talk directly to SQS in AWS if you like - you only need to ask.