Jboss basic training presentation

1. JBoss Application Server - Introduction

2. CONTACT
 For any training and consulting requirements please
feel free to get in touch with us
 Anand : + 91 9000204154
 Faisal : +91 9000633263
Now lets get started with the boss.. 

3.  What is JBoss
 JBoss Architecture
 JBoss Internals
 JBoss Installation
 Directory Structure
 Jboss Enterprise Application Platform
 Starting / Stopping the server
 Jboss Administration Console.
 JMX Console
 Twiddle Utility
 QA Session
Road Map

4.  Open source implementation of the Java EE suite of services
 Great deal of customization due to modularization of the services like.
• Enterprise JavaBeans (EJB)
• Java Persistence API (JPA)
• Java Messaging Service (JMS)
• Java Transaction Service/Java Transaction API (JTS/JTA)
• Servlets and Java Server Pages (JSP)
• Java Naming and Directory Interface (JNDI)
 Community JBoss Application Server and JBoss Enterprise Application
Platform.
JBoss Introduction

5.  Developed by JBoss Inc. now a Red Hat division.
 JBoss AS 4.0, a Java EE 1.4 features embedded apache tomcat.
 JBoss AS 4.2 also functions as a Java EE 1.4 but deploys EJB 3.0 by default
 JBoss AS 5.1, released as of 2009, operates as a Java EE 5 application
server built on top of a new JBoss micro container.
 JBoss AS 6.0, an unofficial implementation of Java EE 6, was released on
December 28, 2010. JBoss AS 6 does not support the full Java EE 6 stack
 JBoss AS 7, the current stable release, was released on July 12, 2011.
JBoss Server : History

6. JBoss Server : History

7. Community JBoss Application Server
 Development process allows for rapid innovation.
 Best suited for early to advanced prototyping and development
 http://www.jboss.org/jbossas/downloads/
 http://docs.jboss.org/jbossas/docs/Installation_And_Getting_Started_Guide/5/ht
ml/index.html
JBoss Enterprise Application Platform:
 Integrates JBoss Application Server, with JBoss Hibernate, JBoss Seam, and
other leading open source Java technologies from JBoss.org into a complete,
simple enterprise solution for Java applications.
 Integrated, tested and certified Enterprise Platforms.
 Evaluation copy : http://www.jboss.com/downloads/
 http://docs.redhat.com/docs/en-
US/JBoss_Enterprise_Application_Platform/5/html/Installation_Guide/Introductio
n.html

8.  Jboss Microcontroller : POJO based kernel ,wires all the services. Core of the server.
 Fully-certified Java EE 5 implementation.
 Full support for EJB 3.0
 JBoss Messaging is a high performance JMS provider, rewrite of JBossMQ.
 JBossCache enhancing the performance for caching the data. Comes in two flavors.
 A traditional tree-structured node-based cache
 PojoCache, an in-memory, transactional, and replicated cache system that allows
users to operate on simple POJOs transparently without active user management
of either replication or persistency aspects.
 JBossWS is the web services stack for JBoss 5 providing Java EE compatible web
services,
 JBoss Transactions is the default transaction manager for JBoss 5.
 JBoss Web is the Web container in JBoss 5, an implementation based on Apache Tomcat
that includes the Apache Portable Runtime (APR).
 JBoss Security has been updated to support pluggable authorization models including
SAML, XACML and federation
JBoss EAP

10. JBoss Architecture

11.  Crux of Jboss, which is the foundation architecture into which you can plug only the
services that your application needs, thus you can run as many or as few services that you
want, which can reduce the footprint thus consuming less memory and resources, it also
can help in reducing security risks.
 You can use bean configuration files in the server/xxx/conf directory to configure the
MicroContainer.
 Jboss 5.0 still provides few services based on JMX (Java Management eXtensions) to
access the MBeans.
 JMX Service is defined by JMX kernel is server/xxx/conf/jboss-service.xml, some Mbeans
defined are below.
• The logging Service
• The Thread Pool - used to supply threads to run various services
• The Java Naming and Directory Interface - JNDI
• Various MBeans for managing security - includes JAAS
• Various MBeans related to accessing JMX services
• Various MBeans related to the remoting service
JBoss Micro Container

12. Pre-Requisites
• Enterprise Application Platform 5 requires a Java 6 JDK or JRE.
Installation Methods.
 ZIP download: Enterprise Application Platform 5 requires a Java 6 JDK or JRE.:
The ZIP installation method is the easiest and quickest if you are familiar with
JBoss technologies, or if you are looking for a light-weight method for testing or
development. This method requires some post-installation configuration.
 RPM installation: It is suitable for production deployment on Red Hat Enterprise
Linux systems. RPM installation leverages the benefits of RPM for updating,
system management, and integration with administration tools.
 Graphical Installer: The graphical installer simplifies the installation and
configuration process. In addition to installing the base files, the installer offers
automation of optional component installation, and basic out-of-the-box security
configuration.
Installation

13. Steps
 Download the software from RedHat site. (Evaluation Copy)
Application Platform <release> Binary Installer
 https://access.redhat.com/downloads/evals
 Execute the command java -jar jboss-eap-installer-<release>.jar
 Specify the installation directory
 Select the packages you would like to install
 For ex. WebServices stack
 Specify the JMX Security
 Install the native libraries
 Perform the post installation activities like securing the JMX console, Admin Console etc.
Graphical Installation

14.  Bin: Contains all the scripts to start the server, installing the server as a Service.
 Client: Contains all the client specific jar files.
 Common: Contains the jar files that are common to all the server profiles.
 Docs: Contains the documents and examples.
 Lib: Contains the library files.
 Server: Contains server configurations. By default the Jboss installation contains the below
server configurations.
 Minimal: Has a minimal configuration—the bare minimum services required to start
JBoss. There is no web container, no EJB or JMS support.
 Default : Contains a default set of services. It has the most frequently used services
required to deploy a Java EE application. Does not include the JAXR service, the IIOP
service, or any of the clustering services.
 All: Starts all the available services. This includes the RMI/IIOP and clustering
services, which are not loaded in the default configuration.
 Standard : JavaEE 5 certified configuration of services.
 Web: Lightweight web container oriented profile that previews the JavaEE 6 web
profile.
 Production: Configuration optimized for production environments.
JBoss Server Structure – Directories.

15. JBoss Native Components
 Incorporates native operating system components and connectors
 Higher server performance, as native operating system code becomes available for the server to optimize
tasks.
 Apache Portable Runtime (APR) provides superior scalability, performance, and improved integration
with native server technologies
 OpenSSL implements the Secure Sockets Layer (SSL) and Transport Layer Security (TLS) protocols and
includes a basic cryptographic library.
 Tomcat Native (TC-Native) is a Java Native Interface (JNI) that provides much of Tomcat's core
functionality in native code rather than Java. This allows for an overall increase in the speed of a server.
 mod_jk connects the Tomcat JSP container to the Apache webserver, providing load-balancing.
 mod_cluster is an httpd-based load balancer. In contrast to mod_jk, mod_cluster creates a feedback loop
between the proxy server and the worker nodes, enabling intelligent load distribution and routing within a
load-balancing cluster.
 ISAPI is a connector for the Microsoft IIS web server.
 HornetQ a JMS messaging provider which provides high performance

16. Server Profile Directory Structure
 Conf :Contains the bootstrap.xml bootstrap descriptor file for a given server configuration.
This defines the core microcontainer beans.
 Data: Used by services that want to store content in the file system. It holds persistent data
for services intended to survive a server restart.
 Deploy: Contains the hot-deployable services (those which can be added to or removed
from the running server). You deploy your application code by placing application packages
(JAR, WAR and EAR files) in the deploy directory. The directory is constantly scanned for
updates, and any modified components will be re-deployed automatically.
 Lib: Contains library files specific to the server configuration. All JARs in this directory are
loaded into the shared classpath at startup. Jars common across the serverconfigurations
are now located in <JBoss_Home>/common/lib.
 Log: This is where the log files are written. JBoss uses the Jakarta log4j package for
logging.This may be overridden through the conf/jbosslog4j.xml configuration file.
 tmp Used for temporary storage by JBoss services. The deployer, for example, expands
application archives in this director
 Work: Directory is used by Tomcat for compilation of JSP

17. Starting the Server:
 Move to JBOSS_DIST/jboss-as/bin directory and execute the run.bat (for Windows) or
run.sh (for Linux) script, as appropriate for your operating system.
 $JBOSS_HOME/bin/run.bat
 Note: Below are the default settings.
 The server is bound to 127.0.0.1 for security reasons. To enable remote access by binding
JBoss services to a particular interface, simply run jboss with the -b option.
 $JBOSS_HOME/bin/run.bat –b
 The server runs on port 8080 and to change the settings, we can run it as below.
 $JBOSS_HOME/bin/ run -Djboss.service.binding.set=ports-01
 Specify alternate server profile.
 $JBOSS_HOME/bin/ run –c <alternate-server-profile>
Stopping the server:
 You can run the shutdown script to shutdown the server.
 $JBOSS_HOME/bin/shutdown.sh
JBoss Server Start / Stop.

18.  JBOSS_HOME URL: file:/H:/jboss-6.0.0.Final/
 Bootstrap: $JBOSS_HOMEserver/default/conf/bootstrap.xml
 Common Base: $JBOSS_HOMEcommon/
 Common Library: $JBOSS_HOMEcommon/lib/
 Server Name: default
 Server Base: $JBOSS_HOMEserver/
 Server Library: $JBOSS_HOMEserver/default/lib/
 Server Config: $JBOSS_HOMEserver/default/conf/
 Server Home: $JBOSS_HOMEserver/default/
 Server Data: $JBOSS_HOMEserver/default/data/
 Server Log: $JBOSS_HOMEserver/default/log/
 Server Temp: $JBOSS_HOMEserver/default/tmp/
JBoss server- Default

19. JBoss Default Ports
Port Description Location
1099 JNDI server/default/conf/jboss-service.xml
1100 HAJNDI for clustering server/all/deploy/cluster-service.xml
8083 WebService for downloading RMI classes server/default/conf/jboss-service.xml
4444 RMI/JRMP Invoker, invokes JMX services server/default/conf/jboss-service.xml
4445 RMI/JRMPHA Invoker, invokes clustered JMX services server/all/deploy/cluster-service.xml
3528 CORBA ORB server/all/conf/jacorb.properties
8089 JMS RMI InvocationLayer server/default/deploy/jms/rmi-il-service.xml
8090 JMS OIL InvocationLayer server/default/deploy/jms/oil-service.xml
8091 JMS UIL InvocationLayer server/default/deploy/jms/uil-service.xml
8092 JMS OIL2 InvocationLayer server/default/deploy/jms/oil2-service.xml
8093 JMS UIL2 InvocationLayer server/default/deploy/jms/uil2-service.xml
1701 Hypersonic Database server/default/deploy/hsqldb-ds.xml
8080 WebServer (Tomcat/Jetty)
server/default/deploy/jbossweb-
tomcat41.sar/META-INF/jboss-service.xml

20.  Start automatically when you boot a Windows host computer
 JBoss AS comes with Windows service executable as part of Jboss Native library that can
run JBoss Application Server as service.
 The service executable jbosssvc.exe transforms run.bat and shutdown.bat batch scripts
to services. This means that any change made to those scripts will be used both in
service and command line mode.
 http://www.jboss.org/jbossweb/install/service.html
JBoss as Windows Service

21. Lab - 1
 Installing the Jboss App. Server.
 Exploring the directory structure.
 Starting and stopping the server.
 Changing the default ports.
 Binding to different IP interfaces.
Lab – 2
 Exploring the memory arguments.
 Changing the default memory argument values
Lab – 3
 JBoss as windows service
Labs

22.  Included from Jboss 5.1.0 distribution list onwards.
 Uses the Embedded Jopr (As it runs as a part of Jboss Admin Server).
 Console web application runs “on-demand” and is deployed only when the request is
made.
You can disable the “on-demand” deployment with the below parameter.
-Djboss.as.deployment.ondemand=false
 Default username / password is admin/ admin defined in the below file.
server/configuration/conf/props/jmx-console-users.properties
 Change/ update the roles by editing the below file.
server/configuration/conf/props/jmx-console-roles.properties
JBoss Administration Console

23. JBoss Administration Console - Continued
The Admin Console is secured by the JAAS security domain jmx-console .
Enabling Authentication on the Admin Console
 In this web.xml file:JBOSS_HOME/server/PROFILE/deploy/management/console-
mgr.sar/web-console.war/WEB-INF/web.xml ensure the following
security-constraint fragment is uncommented
Enabling Security Domain on the Admin Console
 In this jboss web.xml file:
JBOSS_HOME/server/PROFILE/deploy/management/console-
mgr.sar/web.console.war/WEB-INF/jboss-web.xml
ensure the following fragment is included.
<jboss-web>
<security-domain>java:/jaas/jmx-console</security-domain>
</jboss-web>

24. Features:
 Provides an overview of the server configuration
 Configuring the ports using the Service Binding Manager.
 Deploy, Re-deploy, Undeploy and control the applications.
 Configure, manage JMS resources
 Configure, manage connection factories.
 Add, remove, configure and control the Data Sources.
 Gather metrics related to the EAP instances, JMS Queues, Topics, Data Sources
JBoss Admin Console - Continued

25.  It’s a JBoss Management Console which provides a raw view of the JMX MBeans which
make up the server. They can provide a lot of information about the running server and
allow you to modify its configuration, start and stop components and so on.
Things we can do with JMX Console.
 Display the JNDI tree : Lists the JNDI object bound using service=JNDIView
 Generate a thread dump: Capture the thread dumps using jboss.system:type=ServerInfo
Mbean
 Display the memory pool usage : Using the jboss.system:type=ServerInfo mbean
 Manage the deployment scanner: Enable/ Disable the Hot Deployment scanner.
 Redeploy an application
 Shut down JBoss
 Note: Any changes made by using the JMX console are not persistent, this means when
JBoss is restarted all changes are lost, MBeans do not change the XML files.
JBoss JMX Console

26.  JMX: Its Java Management Extension allows to integrate modules, containers, and plug-
ins. These components are collectively called Mbeans.
 Command line tool that allows for interaction with a remote JMX server instance.
 Executed by Twiddle.sh / twiddle.bat under the $JBOSS_HOME/bin folder.
 twiddle.bat –h
 usage: twiddle [options] <command> [command_arguments]
 Connecting to a remote server using twiddle.
 twiddle.bat -s localhost:1099 serverinfo –d
 jboss
 List the Mbeans that can be accessed.
 twiddle.bat -s localhost:1099 serverinfo –l
 References:
 http://docs.jboss.org/jbossas/jboss4guide/r1/html/ch2.chapter.html
JBoss Twiddle Utility

27. JBoss Logging
 In JBoss log4j is used for logging.
 Controlled by <server-profile>/conf/jboss-log4j.xml file.
 Defines different appenders, message format, log levels etc.
 By default, JBoss produces output to both the console and a log file (log/server.log).
 Console default level is INFO.
 No default log level for server log, so everything is logged (DEBUG).
 Different log levels TRACE, DEBUG, INFO, WARN, ERROR and FATAL.
 run.bat -Djboss.server.log.threshold=DEBUG
 You can have specific logging for different sub systems by modifying the appenders
defined in the file.
<appender name="FILE" class="org.jboss.logging.appender.DailyRollingFileAppender">
<errorHandler class="org.jboss.logging.util.OnlyOnceErrorHandler"/>
<!-- <param name="File" value="${jboss.server.log.dir}/server.log"/> -->
<param name="File" value="C:/server.log"/>
<param name="Append" value="true"/>

28. Lab - 4
 Exploring the Admin console and JMX console.
 Checking the services
Lab – 5
 Exploring the Twiddle utility.
 Examples to getting Server Information, Global JNDI Information,Jboss Logging
Information,Thread Pool information:
Lab – 6
 Understanding the logging feature.
 Changing the default logging level.
Labs