Configurable Network Computing: Difference between revisions

Content deleted Content added
A misspelled word
Spelling corrections
Line 4:
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, 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/LlinuxLinux, or System i), or the [[Oracle database|Oracle]] Transaction Server.<ref>http://www.astradyne-uk.com/manuals/ir019510.pdf JD Edwards OneWorld Xe Implementation on IBM iSeries Servers</ref>
 
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.
Line 92:
 
==CNC training==
Because of the scope of the CNC functionality, the CNC function requires intensive training.<ref>[http://www.jdetips.com/WorkshopCatalog.asp JD Edwards Training Catalog for World and EnterpriseOne Clients from JDEtips<!-- Bot generated title -->]</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 techotechno-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>[http://www.coursemonster.co.uk/course/16265/]</ref>
* System Fundamentals – An introductory top-down look at the CNC architecture