CNC Team and System Automation Enhancements
If you’re a “normal” person, you need to be warned I’m about to go all “tech guy” on you. You can skip to the takeaway at the end of this section. If you’re still reading this and have ignored my warnings, let’s drill down into some arguably exciting changes.
Batch processes (UBE and reports) continue to be a core component of JDE and critical for the majority of business processes. With Tools 9.2.5, JD Edwards has improved the scalability, flexibility, and availability of UBE batches with Virtual Batch Queues (VBQ). If you’re anything like me, your first thought is going to be “hooray!”
VBQs will enable E1 to meet modern Cloud Elasticity needs for batch processing. How you ask? It’s now possible to use a Virtual Hostname configured within a JDE app “tying” multiple E1 batch servers.
It sounds to me like JDE specific-application-layer-load-balancing but again, another welcomed addition.
A few more points on VBQs:
Enables users to maximize the system resources by having their UBEs processed by any available batch server from the batch server cluster dynamically.
Allows scaling of E1 batch processing by allowing users to bring up or down virtual machines and have them simply work as part of the batch processing solution.
An enterprise server can be easily removed or replaced from the JDE environment without having to change OCM mappings for jobs processed on other servers.
An enterprise server can be removed from the environment without having to re-route UBEs that are waiting to be processed.
Overall, this feature provides elasticity for batch servers, high availability, improved performance, and creates features that will allow JDE to stay relevant for years to come. Is Oracle just trying to modernize, or are we going to see JDE as a SaaS offering? Time will tell.
Development Client Simplification
If you have never built a thick client, it’s a time-intensive process that requires anywhere between 4-8 hours or more depending on a multitude of factors. It was complex and due to several requirements, simply cloning the thick client was not an option.
Oracle has made improvements in the JDE client architecture to simplify development clients by removing the need for the local database. In lieu of the database, new tables were created in Central Objects to store user specs. This enhancement also:
Reduces time & effort for development client installations.
Reduces storage & memory requirements on client machines.
Reduces I/O & network traffic during many activities.
Speeds up the client package build process.
Enables automated backup of development work.
Overall, these enhancements save hours of administration time, improve the user experience, and makes the tech team happy. They reduce the burden of repeatable, mundane, and time-intensive tasks which saves money and allows us to focus on higher-value work.
Web-Based Package Build and Deployment
At last, we can build, assemble, and deploy packages from the web! More specifically, the key system administration applications for package assembly, build, and deployment can be run through the JDE web. On the surface, this may not sound like a big deal, but it is. Historically, these apps were only accessible through the development client which tends to be slow and kills efficacy.
Enabling these applications through the web also creates opportunities for automating, scheduling package builds, and sending notifications through orchestrations.
Automated Troubleshooting for Kernel Failures
Tools 9.2.5 expedites the troubleshooting process for kernel failures, making the life of the CNC administration team less complicated. This enhancement identifies the cause of the kernel failure and sends notifications to the appropriate parties so that corrective actions can be taken. The information includes kernel failures, log file, and call stack which helps to streamline the resolution process and reduces working time with Oracle Support. The takeaway here seems that there is a reoccurring trend of automation.
Web-Enabled Object Management Workbench
With an early version of the JDE 9.2 Tools Oracle released, for the Web Object Management Workbench (OMW), we were only able to work with User Defined Objects (UDOs). Starting with JDE tools 9.2.5, Web OMW has been enhanced to support the management of standard development objects. Developers, testers, and administrators can now promote objects through a browser-based application within the E1 web-user interface.
UDO Dependencies for ORCH
With this feature, you can view information about all dependent components for orchestrations and notifications such as orchestrations, form requests, rules, notifications, and so on. In other words, this is Cross Reference (XREF) for UDO objects.