JDE 9.1 Q&A

JDE tool system overview

1.To run the logic and present the user interface, HTML Server accesses the Serial Objects tables, which contain the metadata for same (specs). A JNI-based generation process creates these Serialized Objects (F989998/F989999) from the TAM-formatted data in the JD Edwards EnterpriseOne metadata tables (F987*). The Serialized Objects are suitable for manipulation by Java code.

2.The first page is a sign-in page. The user credentials are passed by HTML Server to the Security Server (which resides on the Enterprise Server) and authenticates them.

3.Application logic is coded in Event Rules (ER), a JD Edwards EnterpriseOne proprietary development language.This code takes the form of metadata called specifications (specs) which is read and interpreted by a JVM running on the HTML Server server in the web application server framework. ER code also makes some direct access to the JD Edwards EnterpriseOne Business data in the course of running application logic.

4.All UBEs and most Business Functions run on the Enterprise Server. Only a few small, simple BSFNs (about two dozen) run on HTML Server as Java code plug-ins for performance reasons. The results are passed back to the machine running the HTML Server instance.

5.Deployment server can only by Windows OS, accomplishes these tasks regardless of which platforms the JD Edwards EnterpriseOne components run on.

6.

QA:

1. Security Sever not connect to DB directly ? if so, where to store user security information?

2. Server manager and SAW difference?

3.Data Access Driver & Data Access Server

4.