Unit 1 - Installation and basic configuration of JBoss Enterprise Application Platform (EAP).
Students learn about the hardware and software required to run JBoss
products. Students will also learn how to determine which software
versions to use and about the interdependencies of supporting software.
Technologies covered: Java, JBoss EAP, JMX
Lab:
Install JBoss Enterprise Application Platform. Also install JBoss Admin
Console as a front-end GUI for management and control.
Unit 2 - Deploying enterprise applications to JBoss EAP.
In this unit, Students learn what defines an enterprise application,
how to deploy it to JBoss EAP, and what types of supporting components
are needed. Students also learn what deployable packages exist and the
structure of package internals.
Lab: Verify that your application is deployed. Use JBoss Admin Console to deploy packages.
Unit 3 - Monitoring and controlling JBoss EAP.
Students will learn what tools are available to monitor JBoss EAP
installations, how to configure those tools, and what information they
offer. The student will be introduced to the JBoss Admin Console and
will experience how it can be used to monitor and manage applications
deployed to the application server.
Labs:
Monitoring the application server with Jconsole. Using JBoss Admin
Console to monitor datasources, Enterprise Java Beans, web servers, and
other application components.
Unit 4 - Connecting to JBoss EAP.
In this unit, students learns what connections are available and can
provide access to JBoss components. The student will be exposed to web
protocols such as HTTP, and secure socket layer (SSL) via HTTP/S.
Various services, such as Java Naming and Directory Interface and Java
Messaging Service, will be introduced and discussed. The
vulnerabilities of these choices will be introduced, with best
practices around how to protect the appropriate ports.
Technologies: HTTP, SSL, AJP, JNDI, JMS
Labs: Protect incoming ports from denial-of-service (DOS) attacks
Unit 5 - Securing applications with JBoss solutions.
Students will gain an understanding of the various forms security takes
within an enterprise system and how they are best used. They will learn
to slim down their EAP installation to trim away any unnecessary
services or applications and about application-level security and how
encryption can be implemented. A discussion of the pros and cons of
container-managed security is included.
Labs:
Secure the system by insuring that no unnecessary connections are
possible. Use an LDAP server (Red Hat Data Server) to authentication of
user logins.
Unit 6 - Troubleshooting applications on JBoss EAP.
In this unit, the student will learn about the tools available to help
understand and identify potential application problems as they arise.
Best practices in response to such situations will be introduced.
Database bottlenecks, memory management issues, garbage collection, and
other performance-stealing problems will be covered.
Lab: Identify a performance bottleneck in the installed application and decide how to resolve the performance issue.
Unit 7 - Clustering applications with JBoss EAP.
Students will learn how to deploy a clustered application into a tuned
and clustered production environment. The unit asks students to tie
together previous learnings to deploy and configure a potentially
complex solution.
Lab:
Verify that the provided applications are fully configured for the
production environment (datasources, deployment descriptors, etc.).
Unit 8 - Optimizing applications for JBoss EAP.
In this unit, students will learn how to load-balance the embedded web
server in JBoss. They will also learn about best methods for fail-over
and session state management in the application server using caching
technologies. After configuring an application for deployment to the
load-balanced server, the student will learn how to tune
request-handling parameters for optimum scalability.
Labs:
Cluster a web-based application with JBoss. Start two clustered
instances of JBoss, then deploy the application to the cluster, and
watch what happens when the serving node crashes.