What's New in EAP 7?: Undertow Web Server

What's new in EAP 7?
If you are arriving from a JBoss EAP 6 environment you will be eager to
know about the highlights of the new platform. Broadly speaking, the
changes encompass both the server administration area and the Java
Enterprise APIs that can help to provide applications on it. We will start by
introducing the new administrative features and then we will briefly mention
the API highlights.
The administrative features are described as follows:
Undertow web server: JBoss Web has for quite a long time been the
face of the web application server. Although compatible with
Servlet/JSP Specifications it has kept the long-term legacy with Tomcat.
The new Undertow web server has been built from scratch using the
best-of-breed Java IO API. Some of its core features include nonblocking
NIO based APIs, a lightweight and fully embeddable
architecture based on pluggable handlers, and support for WebSockets,
including JSR-356 and the HTTP Upgrade mechanism. Besides this,
Undertow is capable of working as a reverse proxy or load balancer for a
clustered application server, opening the door to the full JBoss clustering
platform.
Simpler server management: Thanks to the HTTP upgrade mechanism

available in Undertow, now you can reduce the number of ports in the
default installation to just two:
* 8080 for applications with JNDI and EJB multiplexed
* 9990 for management, for both HTTP/JSON and native API
Support for HTTP/2: The new web server architecture supports the
new version of the HTTP protocol, named HTTP/2. HTTP/2 aims to
reduce latency and make efficient use of the TCP connection by means
of binary framing, request/response multiplexing, header compression
(HPACK) and more.
New life cycle modes: It is now possible to suspend and resume the
execution of the application server. This allows active
sessions/requests/in-flight-txs to complete and can be used for a
graceful server shutdown scenario.
Enhanced server management: The administration web console has

been revamped with a new graphical layout and new availabilities such
as the Datasource wizard that will let you quickly create database
connections with a few touches.
ArtemisMQ Messaging Broker: In the new server version, the

messaging broker has changed to ArtemisMQ which is directly derived
from the former HornetQ. Former HornetQ clients will be supported out
of the box, while offering compatibility to Apache's ActiveMQ 5.0
clients as well.
ORB Switch: The new version of the application server has switched to
OpenJDK ORB which provides better interoperability with other
vendors compared with the earlier JacORB implementation.
The Java EE 7 API highlights are related to the the Java EE 7 (JSR 342)
specification is an umbrella specification which encompasses 33 single
specifications. There have been brand new technologies and
improvements of existing ones.
Here is a short list of Java EE 7 drivers:
JSR-352 batch applications for the Java platform, featuring a new API
for an XML-based job specification language and a runtime API.
JSR-236 concurrency utilities for JavaEE, providing a simple and
standard API for using multiple threads from Java Enterprise
components.
JSR-353 Java API for JSON Processing (JSON-P). This API can be
used to parse, transform, and query JSON data.
JSR-356 WebSockets support, featuring a full-duplex communication
channel between the client and the server by means of simple
annotations and life cycle callbacks.
Besides the new additions, some updates have been released to existing
services. The most notable ones are as follows:
JSR-345, which includes EJB 3.2, plus Interceptors 1.2 and Annotations
1.2
JSR-340, featuring Servlet 3.1: non-blocking I/O, HTTP upgrade, and so
on
JSR-342, including the JMS 2.0 API that delivers a JMSContext
resource as a wrapper for JMS resources
JSR-344 JSF 2.2: HTML 5, FaceFlows, Stateless views, Resource lib
*** Default Protocol used by Jboss’s are Http, Https, and Ajp
** Overview of deployments **
Deployment of Application (as WAR, EAR, JAR)
Java applications can categorize at least three types of application: --
Java Archive, Web Archive, and Enterprise Archive.
Each of the previously mentioned application types have their own specific
extensions that are just for a readable purpose:
.jar - Java Archive
.war - Web Archive
. ear - Enterprise Archive
As a matter of fact, all of them are essentially ZIP archive files.
EAR File (Enterprise Archive)

-: Deploying using the CLI: -
To deploy your application using the CLI, do as follows:
[root@dev jboss-eap-7.0] # ./bin/jboss-cli.sh
You are disconnected at the moment. Type 'connect' to connect to

the server or 'help' for the list of supported commands.
[disconnected /] connect 192.168.59.103:9990
[standalone@192.168.59.103:9990 /] deploy /opt/rh/jbosshelloworld.war
-: Verify of Deployment: -
# deployment-info --name=jbosshelloworld.war
***undeploy your application, you can use the undeploy command, as Follows:
# undeploy jbosshelloworld.war
@If you don't know the exact name of your application, you can list the
applications available to undeploy, as follows:
# undeploy -l
@ In case you just want to disable an application, for example, due to
maintenance, you can do as follows:
# undeploy jboss-helloworld.war --keep-content
@ Check the deployment status by invoking the deployment-info command:
[standalone@192.168.59.103:9990 /] deployment-info -- name=jbosshelloworld.war
@You can effectively enable your application using the deploy command
followed by the name of the deployment, as follows:
[standalone@192.168.59.103:9990 /] deploy --name=jbosshelloworld.war
@ In case you prefer the web console, deployment is very easy @
Deploying using the web console:-
@log in into the web console (http://localhost:8080/console),

click on the Deployments tab and you should see a page similar to the
following:
Standalone Deployment (Figure-A)
Just press the blue Add button to add a new application as deployment. The
page should pop up the following interface:
Figure-B
By choosing Upload a new deployment and clicking the Next button, the
deployment wizard should prompt you to select the file you want to upload,
from the local filesystem, by pressing the Browse button.
Once you have selected the bundle, click the Next button, as follows:
Standalone - Browsing for the bundle to upload
Next, the wizard shows you a summary of your deployment before

confirmation, as depicted in the screenshot that follows:
Standalone - Completing the deployment upload wizard
As you can see, you can make your deployment available or not by checking
and unchecking the Enable flag.
You can confirm and terminate the deployment task by clicking the
Finish button.
Once done, your deployment appears in the list of deployments. Click on it to
see its details, as follows:
Standalone - Deployment overview

By clicking on your deployment, you should have noticed a drop-down menu
which lets you View, Disable, Replace, and Remove your applications, as
shown in the screenshot as follows:
Standalone - List of commands for deployments

@ Process to deploy Application Deployment in Domain Made @
Managing EAP in Domain Mode:-
Requirement: -
At least 2 Physical Server Required Recommended 3 for better High-Availability
1. Act as a Domain Controller for Centralized Management of Application and all
slave host associated with it

What's New in EAP 7?: Undertow Web Server

Uploaded by

Copyright:

Available Formats

What's New in EAP 7?: Undertow Web Server

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

What's New in EAP 7?: Undertow Web Server

Uploaded by

Copyright:

Available Formats

What's new in EAP 7?

Simpler server management: Thanks to the HTTP upgrade mechanism

Enhanced server management: The administration web console has

ArtemisMQ Messaging Broker: In the new server version, the

EAR File (Enterprise Archive)

[root@dev jboss-eap-7.0] # ./bin/jboss-cli.sh

You are disconnected at the moment. Type 'connect' to connect to

[disconnected /] connect 192.168.59.103:9990

[standalone@192.168.59.103:9990 /] deploy /opt/rh/jbosshelloworld.war

# undeploy jboss-helloworld.war --keep-content

@ Check the deployment status by invoking the deployment-info command:

[standalone@192.168.59.103:9990 /] deployment-info -- name=jbosshelloworld.war

[standalone@192.168.59.103:9990 /] deploy --name=jbosshelloworld.war

@ In case you prefer the web console, deployment is very easy @

Deploying using the web console:-

@log in into the web console (http://localhost:8080/console),

Standalone Deployment (Figure-A)

Standalone - Browsing for the bundle to upload

Next, the wizard shows you a summary of your deployment before

Standalone - Deployment overview

Standalone - List of commands for deployments

You might also like

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.