Table of Contents
This chapter describes the basics of JEUS and Java EE specification. It also explains the concepts of a JEUS system, its components, and features of each edition.
Java Enterprise User Solution (JEUS) provides a platform for the development, operation, and execution of applications in a Web environment. It also supports Java-based Web application services and their management. JEUS provides a platform and the following components that are required to execute Java EE applications.
EJB containers
Web containers (JSPs/Servlet engines)
Security modules
Naming servers
Transaction managers
JDBC connection pools
Session managers
JEUS conforms to Oracle's Java Enterprise Edition specification, and is Java EE 7 certified.
JEUS supports all of the listed technologies in the following quotes from Oracle website.
"The Java Platform, Enterprise Edition (Java EE) defines the standard for developing multitier enterprise applications. The Java EE platform simplifies enterprise applications by basing them on standardized, modular components, by providing a complete set of services to those components, and by handling many details of application behavior automatically, without complex programming."
"The primary technologies in Java EE are: Enterprise JavaBeansTM (EJBsTM), JavaServer PagesTM (JSPsTM), Java Servlets, the Java Naming and Directory InterfaceTM (JNDITM), the Java Transaction API (JTA), CORBA, and the JDBCTM data access API."
For more information about Java EE, refer to Oracle website. (http://www.oracle.com/technetwork/java/javaee/overview/index.html)
The following table lists the Java EE features that are implemented in JEUS 8.
Spec | JEUS 8 |
---|---|
J2EE | Java EE 7 |
WebServer | WebtoB 5.0 |
HTTP | 1.0/1.1/2.0 |
CGI | 1.1 |
PHP | 3.x/4.x/5.x |
SSL | /ssl3/tls1 |
WebSocket | 1.0 |
Java API for JSON Processing | |
Batch Application for the Java Platform | |
Concurrency Utilities for Java EE | 1.0 |
EJB | 3.2 |
RMI-IIOP | Supported |
JAF | 1.1 |
EJB to CORBA Mapping | 1.1 |
JCA | 1.7 |
JMS | 2.0 |
Common Annotations for the Java Platform | 1.2 |
JPA | 2.1 |
JavaMail API | 1.5 |
JTA | 1.2 |
JTS | 1.0 |
JNDI | 1.2.1 |
CDI | 1.1 |
Bean Validation | 1.1 |
Managed Beans | 1.0 |
Interceptors | 1.2 |
JSP | 2.3 |
Servlet | 3.1 |
JSF | 2.2 |
JSTL | 1.2 |
XSLT | 1.0 |
JDBC | 4.0 |
IBM MQ | Supported |
Sonic MQ | Supported |
J2EE Management | 1.1 |
J2EE Deployment API | 1.2 |
JAAS | 1.0.1 |
JACC | 1.5 |
JASPIC | 1.1 |
JAXP | (Included in JDK 7) |
StAX | (Included in JDK 7) |
JAXB | 2.2 |
SAAJ | 1.3 |
Implementing Enterprise Web Services | 1.3 |
Web Service Metadata | 2.1 |
JAX-RPC | 1.1 |
JAX-WS | 2.2 |
JAX-RS | 2.0 |
JAXR | 1.0 |
UDDI | 2.0/3.0 |
SOAP | 1.1/1.2 |
WSDL | 1.1 |
WS-I Basic Profile | 1.1 |
WS-Policy | 1.5 |
WS-Policy Attachment | 1.5 |
WS-Addressing | 1.0 |
WS-Security | 1.1 |
WS-Security Policy | 1.2 |
WS-Trust | 1.4 |
WS-Secure Conversation | 1.4 |
WS-Reliable Messaging | 1.2 |
WS-AtomicTransaction | 1.2 |
WS-Coordination | 1.2 |
OTS | Supported |
Java IDL API | Supported |
IDE Tool | Not supported |
GUI Tool | Not supported |
Web Tool | WebAdmin |
Monitoring Tool | Console Tool, WebAdmin |
JDK | 7 (Certified) |
1. For more information about the specifications, refer to http://www.oracle.com/technetwork/java/javaee/tech/index.html.
2. Some editions of JEUS may not implement all of the features. For more information, refer to the documents for each JEUS edition.
The following figure shows how JEUS integrates with other Web servers or DBMSs to provide enterprise application solutions.
The following are the four layers shown in the previous figure.
Consists of Java applications and native applications. End users use various clients to access WAS services, and the clients use various protocols to access WAS services.
Consists of Web server and protocols used by clients and WAS. This layer deals with static contents and load balancing.
Consists of Java-based middleware and deals with requests from the Web and client layers.
Consists of data and existing legacy services. WAS interoperates with legacy services through various mechanisms such as JDBC, directory services, and Java EE connector.
JEUS is made up of various components. These components operate differently depending on which communication technologies they use to communicate with clients, data storage devices, and JEUS, as shown in the following figure ([Figure 1.2]).
The client layer in the previous figure shows a diverse set of client applications and communication protocols. The source layer shows various types of data storage devices. The WAS middleware layer contains JEUS and Web server. The Web server connects with client applications and is tightly coupled with the Web application server. The Web gateway (WebT) connects the Web application server to the TP-Monitor (Tmax server), and the mainframe gateway (Host-Link) provides connection between a mainframe system and TP-Monitor.
Each layer (Client Layer, WAS Middleware Layer, Source Layer) is explained in more detail in the following sections.
The client layer consists of remote and local applications that use JEUS.
It contains the following components.
The JEUS WAS layer in [Figure 1.2] corresponds to JEUS 8. Its components are as follows:
JEUS Domain Administration Server(DAS)
Each domain must have a special server called a Domain Administration Server (hereafter DAS). The configurations that define the relationship between servers of a domain, and applications and resources in the domain are centrally managed by DAS. DAS controls and monitors servers by communicating with the management tools, WebAdmin and jeusadmin.
An MS contains several types of engines configured within a JEUS system. There are the following four engine types.
The Web server transfers static contents such as HTML and dynamic contents such as CGI. It acts as the front end of the servlet engine. WebtoB is available in two versions, WebtoB, which completely supports all Web server features, and JEUS Web Server, which partially supports the features.
JEUS Web server comes with JEUS but not with WebtoB. As an alternative, open-source web server Apache may be used with JEUS.
The following two main management tools are available for use.
Tool | Description |
---|---|
WebAdmin | Web tool that can be used in a Web browser to manage JEUS components and to package and configure applications. |
Console Tool (jeusadmin) | Enables console access to the features available from GUI. This is used when GUI is unavailable. |
The source layer shown in [Figure 1.2] shows the back-end resources and data storage used by JEUS system. The following are the components.
Interoperability refers to the ability of two or more systems, such as computers, communication devices, networks, software, and other information technology components, to interact with one another and exchange data according to a prescribed method in order to achieve predictable results (ISO ITC-215).
JEUS supports communication protocols and technologies such as Web services, JBuilder Bridge, JNLP, and RMI-IIOP.
The following are the modules provided for JEUS interoperability.
The following table shows the main features of each JEUS 8 edition.
Edition | Main Features |
---|---|
JEUS Standard Edition |
|
JEUS Enterprise Edition |
|
JEUS Cloud Edition |
|
All features of the previous table are covered in the JEUS manuals. Refer to this table to check whether the features described in each guide are available for use. JEUS includes a Trial license by default.