Architecture
JD Edwards (JDE) EnterpriseOne supports multiple deployment architectures, including two-tier and three-tier configurations. Here’s how the two-tier architecture, Business Services (BSSV), and REST services fit into the JDE ecosystem.
JDE Two-Tier Architecture In a two-tier setup, JDE EnterpriseOne runs as a client-server application where the fat client (Windows-based) directly communicates with the database server.
graph TD
A[Fat Client - Windows] --> B[Database Server - JDE]
A -.-> C[User Interface & Business Logic]
B -.-> D[Database - JDE Tables]Components: Fat Client (Windows) Runs JD Edwards EnterpriseOne client tools and applications. Includes business logic and user interface. Communicates directly with the database. Database Server Stores all JD Edwards data, tables, and metadata. The fat client executes business logic locally but retrieves/stores data from the database. Limitations: Requires client installation on every user's machine. Lacks scalability compared to three-tier architecture. Not suitable for web-based or distributed environments.
JDE Three-Tier Architecture
JD Edwards (JDE) Three-Tier Architecture, the system is divided into three main layers:
Client Layer (Presentation Layer)
This is the user interface where users interact with the system. It can be a fat client, a web client, or a mobile interface. Application Layer (Business Logic Layer)
This layer includes the application server, which hosts the JD Edwards EnterpriseOne application and business logic. This is where the majority of the processing happens, and it communicates with both the database and external systems. Database Layer (Data Layer)
This layer stores all the JDE data in databases. It includes the JDE tables, data, and associated database management systems (DBMS).
JDE Business Services (BSSV) Business Services Server (BSSV) is JDE’s web service layer that allows external applications to interact with JD Edwards via SOAP-based web services.
graph TD
A[User Client Web/Fat Client] --> B[Application Server JDE E1]
B --> C[Business Services Layer BSSV]
C --> D[Database Server JDE]
B -.-> E[Business Logic & APIs]
D -.-> F[Database JDE Tables]Hosted on an Application Server. Uses Java-based Business Services (BSSV) to expose JDE functions as web services. Runs separately from the main EnterpriseOne application server. JD Edwards Business Functions (BSFN)
Core JDE business logic that BSSV calls via JDE APIs. External Applications
ERPs, third-party applications, or web portals can call BSSV services using SOAP requests. Advantages: Enables integration with external systems. Supports enterprise service-oriented architecture (SOA). Provides a standardized way to access JDE functionality. JDE REST Services JD Edwards also supports RESTful APIs, introduced in later versions as an alternative to BSSV.
Features: Lightweight & Fast: REST services are JSON-based and more efficient than SOAP-based BSSV. Built-in JDE Orchestrator: JD Edwards Orchestrator provides a graphical way to create REST services using JDE applications. Authentication & Security: Uses standard security methods (e.g., OAuth, JWT, basic authentication). Common Use Cases: Mobile and web applications. Integration with cloud platforms. Automating JDE tasks via Orchestrations. Comparison: BSSV vs. REST Services Feature BSSV (SOAP) REST Services Protocol SOAP/XML REST/JSON Speed Slower due to XML overhead Faster due to lightweight JSON Complexity Requires Java development Orchestrator simplifies creation Use Cases Legacy integrations, enterprise apps Web, mobile, cloud integrations Deployment Requires WebLogic/WebSphere Built into JDE Orchestrator Conclusion Two-tier JDE: Legacy architecture where fat clients connect directly to the database. BSSV: SOAP-based web services for integrating JDE with other enterprise systems. REST Services: Modern JSON-based APIs using JDE Orchestrator for seamless integration with web and cloud applications. For modern implementations, REST services via Orchestrator are preferred over BSSV due to their simplicity, speed, and cloud compatibility. However, BSSV is still used in many legacy integrations.