Chapter 1. Introduction

Table of Contents

1.1. Overview
1.2. System Concepts and Roles
1.3. Architecture and Components
1.3.1. Client Layer
1.3.2. WAS Middleware Layer
1.3.3. Source Layer
1.4. Interoperable Modules
1.5. Editions

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.

JEUS(Java Enterprise User Solution) 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

Java EE

JEUS conforms to Oracle's Java Enterprise Edition specification, and is Java EE 6 certified. JEUS supports all of the listed technologies in the following quote 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 JavaBeans™ (EJBs™), JavaServer Pages™ (JSPs™), Java Servlets, the Java Naming and Directory Interface™ (JNDI™), the Java Transaction API (JTA), CORBA, and the JDBC™ data access API."

The following table lists the Java EE features that are implemented in JEUS 7. For more information on the Java EE specification, refer to http://www.oracle.com/technetwork/java/javaee/tech/index.html.

SpecJEUS 7
J2EEJava EE 6
WebServerWebtoB 4.1
HTTP1.0/1.1
CGI1.1
PHP3.x/4.x/5.x
SSL/ssl3/tls1
EJB (Enterprise Java Beans)3.1
RMI-IIOPSupported
JAF (JavaBeans Activation Framework)1.1
EJB to CORBA Mapping1.1
JCA (Java EE Connector Architecture)1.6
JMS (Java Message Service API)1.1
Common Annotations for the Java Platform1.1
JPA (Java Persistence API)2.0
JavaMail API1.4
JTA (Java Transaction API)1.1
JTS (Java Transaction Service)1.0
JNDI (Java Naming and Directory Interface)1.2.1
CDI (Contexts and Dependency Injection for Java. Web Beans)1.0
Bean Validation1.0
Managed Beans1.0
Interceptors1.1
JSP2.2
Servlet3.0
JSF (JavaServer Faces)2.0
JSTL1.2
XSLT1.0
JDBC4.0
IBM MQSupported
Sonic MQSupported
J2EE Management1.1
J2EE Deployment API1.2
JAAS1.0.1
JACC1.3
JASPIC1.0
Implementing Enterprise Web Services1.3
WS-I Basic Profile1.1
WS-Security1.1
WS-Reliable Messaging1.1
WS-Transaction1.0
WS-Addressing1.0
SOAP1.1/1.2
WSDL1.1
Web Service Metadata2.1
SAAJ1.3
UDDI2.0/3.0
JAX-RPC1.1
JAX-WS2.2
JAX-RS1.1
JAXR1.0
JAXB2.2
JAXP(included in Java SE 6)
WS-Policy1.0
WS-Security Policy1.2
WS-Trust1.3
WS-Secure Conversation1.3
WS-Policy Attachment1.5
StAX (Streaming API for XML)(included in Java SE 6)
OTSSupported
Java IDL APISupported
IDE ToolNot Supported
GUI ToolNot Supported
Web ToolWebAdmin
Monitoring ToolConsole Tool, WebAdmin
JDK6.0(certified)

Note

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.

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.


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, and the mainframe gateway (Host-Link) provides connection between a mainframe system and TP-Monitor.

Each layer is explained in more detail in the following.

The JEUS WAS layer in [Figure 1.2] is showing JEUS 7. The following are the components of JEUS 7.

  • 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.

    ServiceDescription
    Domain ConfigurationManages domain configurations.
    Application ManagementManages domain applications.
    AdministrationCentrally monitors and controls all domain servers, services, applications, and resources by using WebAdmin and jeusadmin.
  • JEUS Managed Server(MS)

    This contains several types of engines configured within a JEUS system. There are the following four engine types.

    Engine / ServiceDescription
    EJB EngineRuns EJB 3.0 applications.
    Servlet EngineWeb container that handles both JSP/Servlet applications and static contents like HTML.
    JMS EngineSupports JMS structures.
    Web Services EngineJEUS Web server that acts as the front end of the servlet engine.
    JNDI ServiceNaming system.
    Security ServiceHandles authentication and authority.
    JTAProvides complete transactions for various applications running on Web application servers.
    SchedulerSupports timers that trigger an event at a predefined time.
    Session ManagerReliably stores client session information when clustering is needed.
    JDBCConfigurable database connection pool.
    LoggingStores and records jobs that have been executed on JEUS.
    JMXAllows NMS/JMX clients to manage JEUS.
    JCAJCA stands for Java EE Connector Architecture. JCA allows any legacy EAI (Enterprise Application Integration) solution to integrate with a legacy EIS if the EAI solution supports JCA.

  • WebtoB (or Apache) Web Server

    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 Administration Tools

    The following two main management tools are available for use.

    ToolDescription
    WebAdminWeb 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.

Source LayerDescription
DatabaseCan be accessed by JEUS through JDBC.
Directory ServiceJNDI is used to access services like LDAP.
Other Java EE ServerJEUS interoperates with Java EE Servers from other vendors.
Tmax ServerTmaxSoft's TP-monitor. WebT API library is used to access JEUS or Tmax.
ORBCan be referenced by using IIOP (Internet Inter-ORB Protocol).
MainframeAccessed by using Host-Link or Java EE connector products.
Legacy EISSupports JCA and interoperates with JEUS.

Interoperability refers to the ability of two or more systems (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 fully supports communication protocols and technologies such as Web services, JBuilder Bridge, JNLP, and RMI-IIOP. The following are the modules provided for JEUS interoperability.

ModuleDescription
RMI-IIOPRMI technology that uses IIOP (Internet Inter-ORB Protocol) and enables distributed CORBA computing jobs in Java.
JEUSInteroperates with other vendors' Web applications and services.
WebTProvides a connection between TP-Monitor and JEUS.
Host-LinkAdapter module that enables clients to use services that are running on an EIS.
JCAEnables JEUS and JEUS clients to virtually interoperate with any legacy EIS.

The following table shows the main features of each JEUS 7 edition.

EditionMain Features
JEUS Base Edition
  • JEUS Server

  • JEUS Web Server

  • Servlet 3.0

  • JSP 2.2

  • JSF 2.0

  • JSTL 1.2

  • Security

  • JDBC connection pooling

  • XML Utility

  • JNDI

  • JMX

  • WebAdmin

  • JEUS node clustering

JEUS Base Plus Edition
  • Base Edition

  • Session clustering

JEUS Standard Edition
  • Base Edition

  • EJB 3.1

  • JMS 1.1

  • 2 Phase-Commit Supported JTA

  • JCA 1.6

  • SNMP

  • Web service

JEUS Enterprise Edition
  • JEUS Standard Edition

  • Session clustering

  • JMS clustering

JEUS Developer Edition
  • JEUS Enterprise Edition

  • Maximum of 5 Clients via HTTP

Note

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 Developer Edition license by default.