Note : I created this is a post almost 2 years ago but never published it here. Screenshots are not from the latest Orchestrator Studio but the methodology is the same.
I’ll start this new year with a Technical Post : we had yesterday the first 2018 Technical Task Force webinar; the topic was “Orchestrator and AIS Server”. You can find the presentation here : JDE_E1_Tech_Task_Force-JDE_Orchestrator&AIS_Enhancements
One of the Use Case described yesterday was “Irrigation Automation” with the following scenario:
You have configured your AIS Server with https, created orchestrations as “micro-services” ready to be consumed by your mobile application, Oracle JET application, … and you are now wondering about authentication ?
With the latest Tools releases you now have multiple options for this:
Basic authentication, username/password and PS Token authentication are fairly easy to use and I won’t talk about it in this post. You can check directly the Oracle doc : https://docs.
I started using Oracle Always Free Cloud Services as soon as Oracle released them in September (in fact, even a few hours before Larry’s announcement during his keynote at OpenWorld). It gave me the possibility to re-architecture and expand my dev/lab environments, by taking advantage of those Always Free services:
**2 Autonomous Transaction Processing Databases **(with 1 OCPU and 20 Gb Storage)
1 for JD Edwards database 1 for storing JSON data using Simple Oracle Document Access (SODA) - see Oracle As Document Store **2 Compute VMs **(with 1/8 OCPU and 1 GB memory)
The last Orchestrator 7.0.0 brings real enhancements for JD Edwards automation and integration.
I’ve been working a lot with this version in the past few months, in France, UK and Ireland, during our Citizen Developer/Orchestrator workshops sessions and I must say I really enjoy this latest version which is now ready to be used intensively in Production environments:
Orchestrator Monitor: You can now monitor your orchestrations and notifications using the new Orchestrator Health and Exception Monitoring: Error Handling: you can set up error handling for individual orchestration steps.
