Its underlying JDE CNC architecture provides the flexibility needed to scale the system to meet these unique business requirements. Understanding and supporting such a feature-rich, complex, and scalable application can be a daunting task. In many cases, companies require a JD Edwards Managed Services provider to assist them with their JD Edwards CNC requirements.
In this article, we'll provide you with a high-level overview of CNC JD Edwards terms for the non-tech savvy! We'll even cover all the acronyms that you hear from your JDE CNC administrators, so you'll be prepared the next time you speak to them!
So, what is JDE CNC? Let's dive into the details. First, JD Edwards CNC stands for Configurable Network Computing.
Configurable Network Computing (CNC) is the engine that allows JD Edwards to work on a wide variety of hardware, operating systems, databases, and other platforms. JD Edwards EnterpriseOne is architected to insulate the application from the underlying technology, and CNC is the glue that connects the two.
Hardware: Intel, IBM iSeries/Power, HP, Oracle Solaris/SPARC
O/S: Windows, IBM i/AIX, Solaris, Unix, Linux
Database: Oracle, SQL Server, and IBM DB2
Web Server: Oracle WebLogic, Oracle Application Server, or IBM WebSphere
There are many possible servers in the JD Edwards CNC architecture. Each configuration will be dependent on the requirements for that specific JD Edwards EnterpriseOne configuration. The main servers in the JDE CNC architecture include:
Enterprise Server
Web Server
Database Server
Deployment Server
Some other servers include the Transaction Server, AIS Server, BI publisher Server, Mobile Server, and more.
The JD Edwards Enterprise Server is often referred to as the logic server, where the application runs. It contains executable objects and can scale to include multiple servers where necessary. It also performs other functions such as security, batch processing (UBEs), interoperability, and more.
The JD Edwards Web Server is the presentation or user interface layer for the application and what your browser connects to. It is often referred to as the HTML Server or the Java Application Server (JAS).
The JDE Database Server is where the business and system data used by the JD Edwards application is stored. It also hosts the database management software. It can be scaled to include multiple servers.
The JD Edwards Deployment Server is the source of all your application code, including patches, package builds in files, and databases. Packages are built and deployed on the deployment server to deliver code to the end-user.
JD Edwards Server Manager is a tool used by a JDE CNC administrator to monitor and control servers, view logs, manage software releases/tools upgrades, install HTML instances, and more. It is commonly installed on the deployment server but can be set up on its own server.
There are two middleware components in the JDE CNC architecture, including JDENET and JDEBASE. This middleware allows JD Edwards to communicate across distributed computing environments. JDENET handles the communication between the presentation layer and the JD internal Edwards application, while JDEBASE provides support for a variety of third-party SQL databases.
An environment is a collection of pointers that indicate the location of objects including the database, logic server, and code set. Simply put, an environment defines where is the data, what machine will process the logic, and what directory contains that object being processed. Examples of environments include JD – Pristine, DV – Development, TS – Dev Test, PY – Prototype, PD – Production, etc.
A path code is a set of pointers to objects in CNC JD Edwards that define the environment and keep track of those objects and their location in the system. There are multiple path codes in a typical JDE setup, including ones for Development, Prototype, Pristine, Production, etc. Some examples include DV920, PD920, PY920, etc. Path codes include objects for applications, tables, reports, business functions, new versions, data structures, and more.
The Object Configuration Manager (OCM) is the mapping tool used to define your environments and path codes. It defines exactly where the data is, where the objects are, and where they should be processed.
The Object Management Workbench (OMW) is the change management tool for the CNC JD Edwards administrator. All changes for JD Edwards objects, menus, etc., are done in the OMW through the context of projects. Objects are placed in projects, which put the code in other environments for testing. It can also create tables and indexes, copy tables, compare code between environments, and more.
JD Edwards problem tracking system calls a request a Software Action Request (SAR). Formerly called Bug Requests, a SAR is a request to change a JDE object(s), including bug fixes, customer requests, and requests for additional functionality. SARs are sent to Oracle’s development group to create fixes. The fixes can be applied and delivered in a tools release or an ESU by your JD Edwards CNC administrator.
Oracle delivers SARs to clients in the form of Electronic Software Updates (ESUs) and tools releases. An ESU can include one or more SARs. ESUs can be one-offs, baseline, or prerequisites. A baseline can be done individually, while a prerequisite will require other ESUs to be applied first. Either can have hundreds of SARs and objects in them. An update includes all ESUs since the initial release of the major JDE version that you are using.
An Application Software Update (ASU) is a collection of objects focused on an enhancement(s) for a specific functional area of EnterpriseOne applications. They can also be from a third party to enable new functionality.
A Service Request (SR) is how you report bugs through the My Oracle Support portal. In the portal, you can also see the status of bug fixes, get JD Edwards CNC documentation, and more. You must be current on Oracle support to have access to this information.
JD Edwards has an application and technology layer with tools releases relating to the technology. It does not relate to business processes or logic. Every 6-12 months, a new tools release is delivered with enhancements, updates, patching, platform certifications, and user experience enhancements as well for JDE CNC.
Recently, JD Edwards has started delivering product innovations incrementally on a timely and continuous basis without having to wait for a major JDE upgrade, called Continous Innovation. Typically, major upgrades are costly, require significant resources, and can cause potential disruption to the business. The incremental enhancements with the continuous innovation model are much easier to consume as well as provide quicker ROI. Most importantly, you still get to decide when and which ones to apply for JD Edwards EnterpriseOne CNC.
Based on customer feedback, JD Edwards announced a new naming methodology for releases that includes both tools and application enhancements that is more in line with industry trends. The first release under the new naming convention is JD Edwards Release 22.
Multiple foundations (multi-foundations) allow you to run two or more JDE tools releases concurrently so you can test tools releases in lower environments before moving into production in a controlled rollout of new functionality. Multi-foundations can all be configured through Server Manager. So, how can you handle your JDE CNC Support?
Do you have questions about JD Edwards Configurable Network Computing (CNC) or need help with JD Edwards Managed Services? To learn more about our JDE support plans, please reach out to GSI today.