2 Base Components

This chapter contains the following topics:

2.1 Enterprise Server

This section discusses these topics:

  • Overview of Enterprise Server

  • Enterprise Server Architecture

  • Enterprise Server Certified Platforms

  • Additional References

2.1.1 Overview of Enterprise Server

The JD Edwards EnterpriseOne Enterprise Server is a critical component of the EnterpriseOne architecture. It validates users (Security Server), runs Business Logic (Logic Server) and Batch processing (UBE's), Interoperability Logic (XML requests), Embedded BI, and many other critical functions for EnterpriseOne.

Using Object Configuration Manager (OCM), it is possible to create separate Enterprise Server instances to distribute workload or work type (Batch Server, Interactive Server, XML Server, JDBNet server, etc.), but each Enterprise Server instance is capable of doing all types of work if so desired and configured.

OCM can also be used to map third-party (e.g. Vertex, PC Miler) interface logic to an Enterprise Server where these products are installed, while most of the Interactive and Batch logic runs on larger server-class machines.

Enterprise Servers can be set up so that they trust each other from a Security perspective. This allows a central Security Server that can authenticate E1 Users, while their activities can run on other Enterprise Server instances.

2.1.2 Enterprise Server Architecture

Figure 2-1 Enterprise Server Architecture

Description of Figure 2-1 follows
Description of "Figure 2-1 Enterprise Server Architecture"

The Enterprise Server is the central hub that receives requests from multiple clients as well as other Enterprise Server Instances. It communicates with the database for transactional processing and can be clustered for failover and hot-swap capabilities.

2.1.3 Enterprise Server Certified Platforms

Enterprise Server is certified to run on the following platforms:

  • Linux / x86-64

  • Oracle Solaris / SPARC

  • Microsoft Windows /x86-64

  • HP-UX / Itanium

  • IBM AIX /Power

  • IBM i/Power

2.1.4 Additional References

Product = JD Edwards EnterpriseOne Enterprise Server

2.2 HTML Server

This section discusses these topics:

  • Overview of HTML Server

  • HTML Server Architecture

  • HTML Server Certified Platforms

  • Additional References

2.2.1 Overview of HTML Server

The HTML Server component of the JD Edwards EnterpriseOne architecture is largely a presentation/user interface layer. It is one module of the JD Edwards EnterpriseOne web client solution architecture. The HTML Server also executes some Java processing; therefore, it is sometimes referred to as the Java Application Server (JAS). The terms HTML Server and JAS are synonymous.

The web client solution consists of the following:

HTTP server

This makes the web client available via a TCP/IP port. The JD Edwards interactive applications are presented to the user via an html interface accessed through a port on an http server. Examples include Oracle HTTP Server, IBM HTTP Server, and Microsoft Internet Information Services (IIS).

Java J2EE runtime environment

This is the Java-based web application server. JD Edwards web applications are hosted in the framework of a J2EE web application server, such as Oracle WebLogic Server or IBM WebSphere Application Server.

The J2EE environment is a web server plug-in for running Java servlets, JSBs and EJBs. HTML Server is running on top the J2EE environment and manifests itself as one or more Java Virtual Machines (JVMs). This is a runtime process which runs the java-based code, which generates the HTML pages presented to the user and runs a portion of the application logic. 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.

HTML Server

The role of HTML Server itself is to build the HTML, which presents the applications to the user. It also retrieves the other components necessary, such as .jpg graphics and JavaScript files which run some application logic on the browser.

The user logs into a known URL which points to the HTML Server instance in question. The URL contains a specific path on the machine hosting the J2EE instance as well as the http port pointing to that instance. 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.

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.

ER code in turn makes calls to Business Functions, which are written in ANSI C. Business Functions do not run in the HTML Server environment (Java-based), but are passed to the Enterprise Server (C-based). 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.

Finally, some logic actually runs on the browser itself in the form of javascript code. The .js executables are downloaded as part of the HTML stream.

The JD Edwards EnterpriseOne Enterprise Server and Database must be installed and ready to use before HTML Server is installed for production. HTML Server does not replace the Enterprise Server's functionality. All UBEs and most Business Functions run on the Enterprise Server.

2.2.2 HTML Server Architecture

Figure 2-2 HTML Server Architecture

Description of Figure 2-2 follows
Description of "Figure 2-2 HTML Server Architecture"

2.2.3 HTML Server Certified Platforms

HTML Server is certified to run on the following platforms (operating systems and web application servers):

  • Linux/x86-64

  • Oracle Solaris/SPARC

  • Microsoft Windows/x86-64

  • HP-UX/Itanium

  • IBM AIX/Power

  • IBM i/Power

  • Oracle WebLogic Server

  • IBM WebSphere Application Server

2.3 Database Server

This section discusses these topics:

  • Overview of the Database Server

  • Database Server Architecture

  • Database Server Certified Platforms

  • Additional References

2.3.1 Overview of the Database Server

The Database Server is the generic term given to the server and the database management software that provides the storage of data used for the EnterpriseOne application. There can be multiple database sources serving the JD Edwards EnterpriseOne architecture. The database management software stores data in tables that are accessed by the application.

There are four different database management software systems that are supported by the JD Edwards EnterpriseOne application:

  • Oracle Database

  • Microsoft SQL Server

  • IBM DB2

  • IBM DB2 for Linux, Unix, and Windows (JD Edwards EnterpriseOne supports IBM DB2 only on AIX and Windows)

2.3.2 Database Server Architecture

Figure 2-3 Database Server Architecture

Description of Figure 2-3 follows
Description of "Figure 2-3 Database Server Architecture"

The EnterpriseOne Database serves as the repository of all of the tables used by the EnterpriseOne application.

2.3.3 Database Server Certified Platform

  • Oracle Database on linux/x86-64; Oracle Solaris/SPARC; Microsoft Windows/x86-64; IBM AIX/Power; HP-UX/Itanium

  • Microsoft SQL Server on Microsoft Windows/x86-64

  • IBM DB2 on IBMi, IBM AIX/Power, and Microsoft Windows/x86-64

2.3.4 Additional References

Product = JD Edwards EnterpriseOne Database Server