1. JBoss Administration Server Introduction
WeblogicWonders

2. Jboss Enterprise Application Platform Starting / Stopping the server
Road Map
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

3. JBoss Introduction
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 JavaServer Pages (JSP)
Java Naming and Directory Interface (JNDI)
Advanced and fully extensible, cross component model, aspect integration, server runtime environment
Community Jboss Application Server and Jboss Enterprise Application Platform.
JBoss strategy for making available the various EE services as independent projects.
Note: Each service is hot-deployed as a component running on top of a very compact core called JBoss Microcontainer which is based on JMX Mbeans.
WeblogicWonders

4. JBoss Server : History Developed by Jboss Inc, now a RedHat 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 microcontainer.
JBoss AS 6.0, an unofficial implementation of Java EE 6, was released on December 28, 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.
WeblogicWonders

5. Community Jboss Application Server:
Used by developers to test and integrate middleware capabilities.
Best suited for early to advanced prototyping and development
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 :
US/JBoss_Enterprise_Application_Platform/5/html/Installation_Guide/Introduction .html
Community Jboss Server:
Development process allows for rapid innovation.
Jboss Enterprise Application Platform:
Includes patches, updates, SLA-based support, multi-year maintenance policies, and Red Hat Open Source Assurance.
Best of both worlds - rapid innovation, with long-term stability, supportability and maintainability.
WeblogicWonders

6. Jboss EAP – Core components
Jboss Microcontroller : POJO based kernel ,wires all the services. Core of the server.
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
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
Fully-certified Java EE 5 implementation.
Jboss Cache
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.
WeblogicWonders

7. JBoss MicroContainer
Crux of Jboss, which is the foundation architecture into which you can plug only the services that your application needs
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 
Reduce the footprint thus consuming less memory and resources, it also can help in reducing security risks.
Wires the POJO services
WeblogicWonders

8. Jboss Architecture

9. Pre-Requisites Installation Methods. Installation
Enterprise Application Platform 5 requires a Java 6 JDK or JRE.
Installation Methods.
ZIP download: Extract the ZIP folder. Faster way.
RPM installation: Suitable for production deployment on Red Hat Enterprise Linux system
Graphical Installer: In addition to installing the base files, the installer offers automation of optional component installation, and basic out-of-the-box security configuration
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. Does not include native libraries.
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.
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. 
WeblogicWonders

10. Graphical Installation
Steps
Download the software from RedHat site. (Evaluation Copy)
Application Platform <release> Binary Installer
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.

11. Jboss Server Structure – Directories.
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.
Native : Contains the native libraries
Server: Contains server configurations. By default the Jboss installation contains the below server configurations.
Minimal:
Default :
All:
Standard :
Web:
Production:
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.
WeblogicWonders

12. 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)
OpenSSL for implementing SSL and TLS
Tomcat Native (TC-Native)
mod_jk connects the Tomcat JSP container to the Apache webserver, providing load-balancing.
mod_cluster is an httpd-based load balancer.
ISAPI is a connector for the Microsoft IIS web server.
HornetQ a JMS messaging provider which provides high performance 
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 
WeblogicWonders

13. 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, applications
Lib: Contains library files specific to the server configuration.
Log: This is where the log files are written
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
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
WeblogicWonders

14. JBoss server Start / Stop.
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 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
WeblogicWonders

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

16. JBoss Default Ports
WeblogicWonders

17. Jboss as Windows Service
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.
WeblogicWonders

18. Labs Lab - 1 Installation and exploring the directory structure.
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
WeblogicWonders

19. JBoss Administration Console
Included from Jboss distribution list onwards.
Uses the Embedded Jopr (As it runs as a part of Jboss Admin Server).
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
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
WeblogicWonders

20. 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>
WeblogicWonders

21. Jboss Admin Console - Continued
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
WeblogicWonders

22. JBoss JMX Console
It’s a JBoss Management Console which provides a raw view of the JMX MBeans which make up the server.
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
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.
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.
WeblogicWonders

23. Jboss Web Console Features: Jboss Management console.
Comprehensive insight about the Jboss
$SERVER-PROFILE\deploy\management\console-mgr.sar\web-console.war
$SERVER-PROFILE\deploy\management\console-mgr.sar\web-console.war\WEB- INF\classes\
web-console-users.properties
web-console-roles.properties
By default, user credentials are blocked to avoid the default password attack
WeblogicWonders

24. Jboss Twiddle Utility
JMX: Its Java Management Extension allows to integrate modules, containers, and plug-ins. These components are collectively called Mbeans.
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:
Command line tool that allows for interaction with a remote JMX server instance.
WeblogicWonders

25. 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"/>
WeblogicWonders

26. Labs Lab - 4 Exploring the Admin console and JMX console. Lab – 5
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.
WeblogicWonders

27. Q - A