Select Dynamic field

JD Edwards EnterpriseOne Use Case


JD Edwards customers are digitally transforming their organizations by leveraging UX One User Experience, Mobile Applications, and Orchestrator. This is a business use case.

TECHNOLOGY:  JD Edwards 9.1 and above

INDUSTRY:  All

COMPONENTS:  Orchestrator, AIS (Application Interface Services), JD Edwards, and Scheduler

What is Orchestrator?
Orchestrator is an IOT web application based on AIS that can transform external data into JD Edwards business processes. Using Orchestrator a customer can automate costly timing tasks and can be used as an interface between IoT and JD Edwards applications. Orchestrator can work also as an alert engine and as an integration platform for external services.

Business Problem — Sometimes, JDE Administrators need to restart or pause the Scheduler. When the Scheduler is down, the UBE´s (Universal Batch Engines) can not be processed. We need an automated way to monitor the Scheduler service if it goes down for this or any other reason and here is where Orchestrator comes into play. Orchestrator can monitor and alert the Scheduler service and prevent the UBEs to stop running.

Objective — Prevent the UBEs to stop running because the Scheduler service went down for any reason.

How to do it: Use Orchestrator to build an orchestration to validate the correct functioning of the Scheduler service. If the service is down or paused an orchestration can alert the Scheduler service is not running and the CNC administrator can validate the issue to put the service up again. The Orchestrator provides a proactive way to the CNC administrator to monitor the Scheduler service and to increase the availability of the JD Edwards services.

Fig 1: The orchestration that monitors the Scheduler service. If the service is down, it shows a task that alerts the CNC administrator about the issue. If the service is Up, the orchestration ends.

Fig 2: Here is a notification sent by the orchestration showing the Scheduler service is down. The CNC administrator will receive these alerts and take action.

Outcome: We combined all the steps into a single orchestration that can run a query to get the status of the Scheduler service. The process runs every 15 minutes using the AIS Scheduler. The orchestration is checking the status of the Scheduler service. If the service is up, the orchestration waits for the next 15 minutes to run the next validation. If the service is down, an alert pops up into the customer JD Edwards portal and an email is sent to our help desk (help@allari.com) to create a ticket automatically to the CNC team who can validate the issue proactively.

This is a very helpful way to use Orchestrator as a monitor tool within JD Edwards. This can improve the CNC administration to be a more efficient, simple, and proactive administration. If you are unfamiliar with Orchestrator or curious about how it can be applied to your environment, here in Allari we can help you to build and manage Orchestrator for you. Please look for us and we can set a meeting to get into your specific needs. We are deeply connected to the Oracle DX team and can set up a collaborative call to get your questions answered.

Let's discuss how you can leverage automation to implement efficiencies at your organization. 

Job Scheduler Monitoring

February 9, 2022

>