The flexibility of the J.D. Edwards architecture does confuse things a bit...
As with all applications, you need Database, Business Logic, and Presentation layers. Here are some sample configurations and comments:
1) Enterprise Server (DB, BL)
Windows Client (PRES, BL)
This is a basic...
1) The JDE product formerly called "Integration for Microsoft" is now called "Adapter for MSMQ". The messages it handles are (I=inbound to OW, O=outbound from OW, M=MBF call, Z=Z file):
a. Sales Order Create (I, M)
b. Sales Order Cancel (I, M)
c. Sales Order...
Take a look at the J.D. Edwards Server Administration Workbench (SAW). The original Windows application version is pretty weak, but the new version included in later service packs is getting quite good. It is Web Based, so it requires some set up if you are not using the Web Client. There is...
1) JDE has done and published studies on bandwidth utilization for Win32 clients, Win32 clients with MBFs mapped to the server, Citrix, RDP, Java Client (deprecated), and Web Client. These studies compare client to server bandwidth utilization, server to client bandwidth utilization, and round...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.