Configurable Network Computing: Difference between revisions

Revision as of 16:36, 9 August 2007

Revision as of 16:36, 9 August 2007

Line 4:

In this specialized architecture, a company's JDEdwards [[business software]](JDE)applications run in such as way as to be transparently insulated from both the [[database]] where the business data is stored as well as from the client [[computer]]'s underlying [[operating system]]. 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.

In what has been known traditionally as [[client-server environments]] 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 for communication of and JDEBASE Database Middleware

==JDENET and JDEBASE Middleware==