Configurable Network Computing: Difference between revisions

Revision as of 17:22, 27 July 2023

Latest revision as of 01:00, 14 August 2024

(8 intermediate revisions by 6 users not shown)

Line 1:

{{advert|date=September 2016}}

'''Configurable Network Computing''' or '''CNC''' is [[JD Edwards]]'s (JDE) [[client–server]] proprietary architecture and methodology. Now a division of the [[Oracle Corporation]], Oracle continues to sponsor the ongoing development of the [[JD Edwards]] [[Enterprise Resource Planning]] ([[Enterprise resource planning|ERP]]) system, While highly flexible, the CNC architecture is [[wikt: proprietary|proprietary]] and, as such, it cannot be exported to any other systems. While the CNC architecture's chief 'Claim to fame', insulation of applications from the underlying database and operating systems, were largely superseded by modern web-based technology, nevertheless CNC technology continues to be at the heart of both JD Edwards' One World and Enterprise One architecture and willis planned to play a significant role Oracle's developing ''fusion architecture'' initiative.<ref>[http://www.oracle.com/applications/fusion.html Oracle Fusion Information URL]</ref> While a proprietary architecture, CNC is neither an Oracle nor JDE product offering. The term CNC also refers to the systems analysts who install, maintain, manage and enhance this architecture. CNC's are also one of the three technical areas in the JD Edwards [[Enterprise Resource Planning]] [[Enterprise resource planning|ERP]] which include developer/report writer and functional/business analysts.

==The CNC architecture==

Oracle is continuing to develop the CNC technology and will incorporate key elements of the CNC technology into its Oracle Fusion project which will pull together technologies from JDE, [[PeopleSoft]] and its own application software technologies.

In the CNC architecture, a company's JD Edwards (JDE) [[business software]] applications run transparently insulated from both the [[database]] where the business data is stored as well as from the client [[computer]]'s underlying [[operating system]] and all other intervening JDE business applications servers. In layman's terms, the business programs don't "care" where the data is or which operating system is being used on any of the [[end user]] computers. Neither do the applications servers on which business programs run need to directly "know" what database systems are being called on the data end or back end. The CNC architecture keeps track of this through various database tables that point the business applications to the servers that run or execute the business applications and also include database connection tools called database drivers that tell the system also where the database servers are and what specific databases to do lookups, data inserts and data extracts from. Because of the key nature of the underlying architecture, a sound CNC infrastructure is critical to the success of a JD Edwards OneWorld installation or implementation. The back-end databases that are supported include [[Oracle database]], [[Microsoft SQL Server]], and [[IBM DB2]] databases. The application server can run on [[Microsoft Windows|Windows]] platforms, [[Unix]]/[[Linux]], and the IBM System i (formerly known as iSeries and AS/400). The [[web server]] can be [[IBM WebSphere]] (on Windows, Unix/Linux, or System i) or the [[Oracle Weblogic Server]] (on Windows or Unix/Linux).

In what has been known traditionally as [[client–server]] environments, applications must communicate across a combination of different hardware platforms, operating systems, and databases as including. The CNC architecture uses a layer of software, called [[middleware]], which resides between the platform operating system and the JDE business applications. To accomplish this, JDE provides two types of middleware, JDENET Communication Middleware, and JDEBASE Database Middleware. The JDEBASE middleware communicates with the database through ODBC, JDBC, or SQL*Net.

===Definition and strengths of the CNC Architecture===

According to the JD Edwards document, ''Configurable Network Computing Implementation'', the CNC architecture is defined as follows:

"CNC is the technical architecture for JD Edwards OneWorld and EnterpriseOne software. CNC enables highly configurable, distributed applications to run on a variety of platforms without users or analysts needing to know which platforms or which databases are involved in any given task. CNC insulates the business solution from the underlying technology. Enterprises can grow and adopt new technologies without rewriting applications....(it"{{fact|date=July 2023}}

"Configurable Network is)Computing an application architecture that enables interactive and batch applications, composed of a single code base, to run across a [[Internet protocol suite|TCP/IP network]] of multiple server platforms and SQL databases. The applications consist of reusable business functions and associated data that can be configured across the network dynamically. The overall objective for businesses is to provide a future-proof environment that enables them to change organizational structures, business processes, and technologies independently of each other."<ref>[http://download.oracle.com/docs/cd/B28737_01/jded/acrobat/e1_tools895tcg-b0805.pdf Configurable Network Computing, URL]</ref>

====Multi-foundation capability====

Another strength of JD Edwards is its multi-foundation architecture. This means that one can create separate instances of JDE on different Tools Releases and isolate these releases from each other. This is doneachieved by creating a separate set of system folders for the other foundation. In the main configuration file of the applications or enterprise server, JDE.ini, the incoming and outgoing ports are changed to a different one than the other foundation, so if one foundation had port 6015, then the alternate could use 6016. Also, the client-side tools release folder is installed on the deployment server and the system administrator uses the JDE Planner or installation environment to define another foundation. Subsequent full packages can then be pointed to using this different foundation.

===Weaknesses in the CNC architecture===

====Specifications file corruption with JDE Applications up to 8.12====

Until the advent of EnterpriseOne applications version, 8.12 running on tools release/service pack 8.96, by far the most vulnerable aspect of the CNC technology was that proprietary object specifications had to be copied from the full client up to the applications server in order for a JDE user's data selection and processing options to be run as requested on the server. If those proprietary specifications became corrupted, the batch application object, in turn, on the applications server could become corrupted. A rebuild and redeploy of the object was the only fix. Likewise, if there is some intervening process that corrupts object specifications as they come down to the client PC, the related object could become corrupted and no longer function correctly. Since applications upgrade E812 and Tools Release or systems or foundational service pack, the proprietary specifications have been replaced with XML-based object properties which have proven to be more stable and less prone to corruption. In the fall of 2008, Oracle brought out the E900 applications release and by the fall of 2010, the tools release was up to 8.98.3.3. E900 Update 1, or E901 is the latest release as of fall 2010.

====Specifications portability====

Line 36 ⟶ 38:

==CNC's interface with web-based technologies==

The advent of the [[World Wide Web]] and [[HTML]] technologies have also insulated users and applications from underlying technologies. The CNC architecture combines this with its own architecture through a Java Applications Server (JAS) architecture. The web clients communicate with the CNC architecture via these JAS servers.

===Oracle releases E900 in late 2008 and E910 in 2011===

In the fall of 2008, Oracle brought out the E900 applications release and by the summer of 2011, the tools release was up to 8.98.4.3. In the fall of 2009, E900 Update 1 was released. By the summer of 2011, over 2000 Electronic Software Updates (ESUs) patches were required to bring the E901 release up to the latest code current levels. In the fall of 2010, update 2 was released. In the fall of 2011, Oracle released Applications Release 9.1 and Tools Release 9.1 significantly changing the look and feel of E1.

==JDENET and JDEBASE Middleware==

Line 45 ⟶ 47:

===JDENET===

JDENET is the [[message-oriented middleware]] that connects the generated presentation layer of JDE applications with business function components through a standard JDE applications programming interface, or [[API]] called "jdeCallObject." The JDENET middleware, running within the CNC architecture, supports the configuration of business function components for execution in the heterogeneous distributed computing environment that the CNC architecture support.

===JDEBASE===

Line 56 ⟶ 58:

==What's in a name - CNC==

In recent years, there has been much discussion among the CNC community on the title, "CNC." On many websites including such sites as [[Oracle Corporation|Oracle]] and [[LinkedIn]] people who have worked in the CNC field for many years have proposed a new title to replace the traditional CNC term. One of the most popular is "JD Edwards Systems Architect" or "[[EnterpriseOne]] Architect" even simply "JDE Architect." This seems to be driven by the fact that many senior CNCs become involved in planning and implementing the underlying CNC architecture and that the term CNC really conveys no meaning as to the actual job description. While the discussions go round and round, recruiters who continue to use the CNC job description or dispense with the CNC term may refer to the job as "JD Edwards System Administrator." Unfortunately, this latter term is largely misunderstood by recruiters and IT people unfamiliar with the complexities of a JD Edwards Implementation and have told CNCs that from the title JDE System Administrator, their responsibilities are fairly simple and probably mimic that of an email administrator or operating systems administrator adding/deleting users and resetting user passwords. JD Edwards "Infrastructure Engineer" is often used which better explains the functions that go beyond simple administration. Despite the discussions on the utility of the CNC title, IT seems to return to it as the only industry-wide accepted way to term the job description.

==CNC-related functions==

{{Original research|section|date=August 2024}}

The CNC function entails a number of responsibilities or functions. Large companies may have an entire staff of CNCs, some working on security, others software change management which deploy changes in the JDE ERP system through the various stages of development, testing, and production. Other CNCs will troubleshoot performance issues, others will work on batch process automatization and finally, a Senior CNC will manage the entire group and, in that capacity, will often function as the chief JDE systems architect.

The CNC function entails a number of responsibilities or functions. Large companies may have an entire staff of CNCs, some working on security, others software change management which deploy changes in the JDE ERP system through the various stages of development, testing, and production. Other CNCs will troubleshoot performance issues, others will work on batch process automation and finally, a Senior CNC will manage the entire group and, in that capacity, will often function as the chief JDE systems architect.

===Basic CNC tasks===

Line 94 ⟶ 97:

==CNC training==

{{Original research|section|date=August 2024}}

Because of the scope of the CNC functionality, the CNC function requires intensive training.<ref>{{Cite web |url=http://www.jdetips.com/WorkshopCatalog.asp |title=JD Edwards Training Catalog for World and EnterpriseOne Clients from JDEtips<!-- Bot generated title --> |access-date=2007-09-10 |archive-url=https://web.archive.org/web/20070820153403/http://www.jdetips.com/WorkshopCatalog.asp |archive-date=2007-08-20 |url-status=dead }}</ref> Oracle JD Edwards manages the officially required coursework, but many JDE business partners also offer training. A frequent criticism of CNC training is that far too many trainers and the syllabuses that they employ are so complicated as to be almost indecipherable to an incoming novice. The training is couched in techno-speak: terms such as ''path code'', ''environment'', OCM mappings are bantered about with overlapping and circular explanations that leave novices and introductory CNC students quite confused.{{Citation needed|date=March 2015}} As of 2000, there is no official certification program. A typical list of classes is as follows:

* Common Foundation – The common end-user JDE experience<ref>{{Cite web|url=http://www.coursemonster.co.uk/course/16265/|title = IT Training Courses &#124; IT Certifications &#124; CourseMonster}}</ref>

Line 113 ⟶ 117:

* Development Tools Parts 1 and 2 - The use of the JDE software Report Design Aid, Table Design Aid, and other object development tools

* Optional training - Report writing and other development tools and functional business training (how the business processes affect the design and implementation of JDE ERP)

==Oracle's CNC certification program==

After more than a decade of discussion, Oracle has resurrected a JDE-CNC certification program.

*The certification link is at https://web.archive.org/web/20110929025144/http://education.oracle.com/pls/web_prod-plq-dad/db_pages.getpage?page_id=439

*Exam details are at https://web.archive.org/web/20110929025144/http://education.oracle.com/pls/web_prod-plq-dad/db_pages.getpage?page_id=439

*''' Currently listed CNC Exam topics as of January 2011.'''

'''JDE-CNC Exam topics''' <ref>{{Cite web |url=http://education.oracle.com/pls/web_prod-plq-dad/db_pages.getpage?page_id=41&p_exam_id=1Z0_550#2 |title=Oracle's JD Edwards CNC Certification Program |access-date=2011-01-18 |archive-url=https://web.archive.org/web/20101022071437/http://education.oracle.com/pls/web_prod-plq-dad/db_pages.getpage?page_id=41&p_exam_id=1Z0_550#2 |archive-date=2010-10-22 |url-status=dead }}</ref>

<div style="left; margin:5px;">

{| class="wikitable"

|- style="background:#CCCCCC"

| '''Topic'''||'''Subtopic'''

|-

| style="background:#DDDDDD"| '''CNC Foundation & Terminology'''

|-

| style="background:#DDDDDD"| ||Work with Environments

|-

| style="background:#DDDDDD"| ||Work with Path Codes

|-

| style="background:#DDDDDD"| ||Use Object Management Configuration

|-

| style="background:#DDDDDD"| ||Create Data Sources

|-

| style="background:#DDDDDD"| ||Explain Server Types

|-

| style="background:#DDDDDD"| ||Describe User Overrides

|-

| style="background:#DDDDDD"| ||Work with Printers

|-

| style="background:#DDDDDD"| ||Work with Universal Table Browser / Data Browser

|-

| style="background:#DDDDDD"| ||Creating Scheduled Jobs with Scheduler

|-

| style="background:#DDDDDD"| ||Describe Media Objects

|-

| style="background:#DDDDDD"| ||Work with Server Jobs

|-

| style="background:#DDDDDD"| ||Creating Job Queues

|-

| style="background:#DDDDDD"| ||Managing Cross Reference Information

|-

| style="background:#DDDDDD"| '''Architecture, Performance and Troubleshooting'''

|-

| style="background:#DDDDDD"| ||Explain JDE Middleware

|-

| style="background:#DDDDDD"| ||Explain the Different JDE Platforms

|-

| style="background:#DDDDDD"| ||Explain Oracle VM Templates

|-

| style="background:#DDDDDD"| ||Implementing JDE in a Multi-Foundation Environment

|-

| style="background:#DDDDDD"| ||Describe the JDE Kernels

|-

| style="background:#DDDDDD"| ||Troubleshooting with Server Manager

|-

| style="background:#DDDDDD"| ||Using Resource Manager

|-

| style="background:#DDDDDD"| ||Explain JDE Clustering

|-

| style="background:#DDDDDD"| ||Implementing Single Sign On with JDE

|-

| style="background:#DDDDDD"| ||Explain JDE Data Replication

|-

| style="background:#DDDDDD"| ||Explain JDE Backup Schemas

|-

| style="background:#DDDDDD"| ||Explain JDE Subsystems

|-

| style="background:#DDDDDD"| '''Object Management'''

|-

| style="background:#DDDDDD"| ||Describe Object Storage

|-

| style="background:#DDDDDD"| ||Object Types and Anatomy

|-

| style="background:#DDDDDD"| ||Creating Projects

|-

|

|-

| style="background:#DDDDDD"| ||Object Check Out/In/Get

|-

| style="background:#DDDDDD"| ||Utilizing OMW Tokens

|-

| style="background:#DDDDDD"| ||Defining Promotion/Lifecycle

|-

| style="background:#DDDDDD"| ||Setting up Save/Restore in OMW

|-

| style="background:#DDDDDD"| ||Interpreting OMW Logging

|-

| style="background:#DDDDDD"| ||Setting up Object Management Configuration

|-

| style="background:#DDDDDD"| ||Defining Activity Rules

|-

| style="background:#DDDDDD"| ||Explain Allowed Actions

|-

| style="background:#DDDDDD"| ||Administering Data Dictionary Items

|-

| style="background:#DDDDDD"| ||Describe Vocabulary Overrides

|-

| style="background:#DDDDDD"| '''Package Management'''

|-

| style="background:#DDDDDD"| ||Creating Full Packages

|-

| style="background:#DDDDDD"| ||Creating Update Packages

|-

| style="background:#DDDDDD"| ||Working with Package Features

|-

| style="background:#DDDDDD"| ||Building a Client Package

|-

| style="background:#DDDDDD"| ||Building a Server Package

|-

| style="background:#DDDDDD"| ||Building an Update Package

|-

| style="background:#DDDDDD"| ||Deploying a Full Package

|-

| style="background:#DDDDDD"| ||Deploying an Update Package

|-

| style="background:#DDDDDD"| ||Deploying a Server Package

|-

| style="background:#DDDDDD"| ||Deploying to an HTML Server

|-

| style="background:#DDDDDD"| ||Defining Multi-Tier Deployment

|-

| style="background:#DDDDDD"| ||Explain Business Services Server Deployment

|-

| style="background:#DDDDDD"| ||Working with Package History

|-

| style="background:#DDDDDD"| ||Reviewing Package Build Log Files

|-

| style="background:#DDDDDD"| '''Security'''

|-

| style="background:#DDDDDD"| ||Creating User Profiles

|-

| style="background:#DDDDDD"| ||Working with Roles

|-

| style="background:#DDDDDD"| ||Explain Role Sequencing

|-

| style="background:#DDDDDD"| ||Explain Signon Security

|-

| style="background:#DDDDDD"| ||Administering Passwords

|-

| style="background:#DDDDDD"| ||Working with Security Workbench

|-

| style="background:#DDDDDD"| ||Applying Application Security

|-

| style="background:#DDDDDD"| ||Applying Action Security

|-

| style="background:#DDDDDD"| ||Applying External Application Security

|-

| style="background:#DDDDDD"| ||Applying Exit Security

|-

| style="background:#DDDDDD"| ||Applying Processing Option Security

|-

| style="background:#DDDDDD"| ||Applying Row Security

|-

| style="background:#DDDDDD"| ||Applying Column Security

|-

| style="background:#DDDDDD"| ||Applying Solution Explorer Security

|-

| style="background:#DDDDDD"| ||Applying Tab Security

|-

| style="background:#DDDDDD"| ||Applying Portal Security

|-

| style="background:#DDDDDD"| ||Applying Security Model/Hierarchy

|-

| style="background:#DDDDDD"| ||Applying OMW/OMC Security

|-

| style="background:#DDDDDD"| ||Implementing Database Security

|-

| style="background:#DDDDDD"| ||Implementing Enterprise Server Security

|-

| style="background:#DDDDDD"| ||Implementing HTML Server Security

|-

| style="background:#DDDDDD"| ||Implementing Deployment Server Security

|-

| style="background:#DDDDDD"| ||Implementing Server Manager Security

|-

| style="background:#DDDDDD"| ||Implementing Desktop Security

|-

| style="background:#DDDDDD"| '''Install & Upgrade'''

|-

| style="background:#DDDDDD"| ||Explain Minimal Technical Requirements

|-

| style="background:#DDDDDD"| ||Executing a Deployment Server Installation

|-

| style="background:#DDDDDD"| ||Executing a Platform Pack (Enterprise, Database) Server Installation

|-

| style="background:#DDDDDD"| ||Executing a Server Manager Installation

|-

| style="background:#DDDDDD"| ||Creating an HTML Server Instance

|-

| style="background:#DDDDDD"| ||Creating a Business Services Server Instance

|-

| style="background:#DDDDDD"| ||Creating a Transaction Server Instance

|-

| style="background:#DDDDDD"| ||Installing Portal Server

|-

| style="background:#DDDDDD"| ||Installing a Development Client

|-

| style="background:#DDDDDD"| ||Creating an Installation/Upgrade Plan

|-

| style="background:#DDDDDD"| ||Running the Installation/Upgrade Workbench

|-

| style="background:#DDDDDD"| ||Describe Application Upgrades (ex. Xe->E9.0)

|-

| style="background:#DDDDDD"| ||Describe Electronic Software Updates

|-

| style="background:#DDDDDD"| ||Explain Application Updates (ex. E9.0 Update 3)

|-

| style="background:#DDDDDD"| ||Implementing Tools Updates (ex. 8.98.4)

|-

| style="background:#DDDDDD"| ||Using Change Assistant

|-

| style="background:#DDDDDD"| ||Describe the Post Install/Upgrade Steps

|-

| style="background:#DDDDDD"| ||Installing and Configuring Peoplebooks

|-

| style="background:#DDDDDD"| ||Installing Additional Languages

|-

| style="background:#DDDDDD"| ||Running EnterpriseOne Services

|-

| style="background:#DDDDDD"| ||Executing Porttest

|-

| style="background:#DDDDDD"| ||Implementing Oracle Business Accelerators

|}</div>

==Independent support for JDE CNCs==

Line 352 ⟶ 132:

==External links==

*[http://www.oracle.com/applications/jdedwards-enterprise-one.html JD Edwards on the Oracle Website]

*[https://education.oracle.com/jd-edwards-enterpriseone-configurable-network-computing-92-certified-implementation-specialist/trackp_506 JD Edwards EnterpriseOne Configurable Network Computing 9.2 Certified Implementation Specialist] certification

*[http://www.astradyne-uk.com/manuals/ir019510.pdf JDE OneWorld Xe Implementation on IBM iSeries AS/400 Servers]

*[http://www.jdelist.com a popular free site that has discussion forums on JDE issues including the CNC function]