JBOSS Admin-JBOSS Application Server

Uninstall JBoss

Defining the Environment Variables

To deploy a Web application in JBoss- Jetty, set the environment variables to enable access to the executables, such as the javac compiler, ANT tool, and JBoss script files. To define environment variables:

Set the JBOSS_HOME environment variable to the path to JBoss installation directory using the command:

JBOSS_HOME=/usr/java/jboss-3.2.1
Export the JBOSS_HOME environment variable using the command:

export JBOSS_HOME
Set JAVA_HOME environment variable to the J2SDK installation directory using the command:

JAVA_HOME=/usr/java/j2sdk1.4.1_01
Export the JAVA_HOME environment variable using the command:

export JAVA_HOME
Set the ANT_HOME environment variable to the ANT installation directory using the command:

ANT_HOME= /usr/java/ant1.5.3.1
Export ANT_HOME using the command:

export ANT_HOME
Set the PATH environment variable using the command:

PATH=$JBOSS/bin:$JAVA_HOME/bin:$ANT_HOME/bin:.:
Export the PATH environment variable using the command:

export PATH
Set the CLASSPATH environment variable using the command:

CLASSPATH=$JBOSS_HOME/server/default/lib/javax.servlet.jar:.:
Export the CLASSPATH environment variable using the command:

export CLASSPATH

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

Deployers on Jboss Application server:

Deployment:  Deployments on JBoss

 Java EE Deployment Lifecycle

Development and Deployment Lifecycle:

1.Design static content (HTML, CSS, GIF, JPG, etc.)
2.Develop dynamic content (Servlets, JSPs, and other Java components like EJBs)
3.Write deployment descriptors (e.g. web.xml, application.xml, ejb-jar.xml, etc.) for components
4.Assemble components into deployable packages (e.g. WAR, JAR, EAR, etc.)
5.Provide all resources that the components require (e.g DBCP, Mail sessions, message queues, etc.)
6.Deploy packages (e.g. WAR, JAR, EAR, etc.) on the Java EE application server
7.Manage Java EE applications on the server

2. Deployment Descriptors

Give the containers instructions on how to use and manage deployed Java EE components

1. Security
2. Transactions
3. Persistence

Declarative customization (XML-based)
Enables portability of Java EE components

Note:
J2EE 1.3 and JBoss pre 5.x deployment descriptors are defined by XML DTD documents. These can be found in $JBOSS_HOME/docs/dtd/ directory. As of J2EE 1.4 and JBoss 5.x, deployment descriptors are defined by XML Schema (XSD) documents. These can be found in $JBOSS_HOME/docs/schema/ directory.

3. Deployment on JBoss AS

Deployment is a two-step process

1.First we notify JBoss that of the application we want to deploy by copying it to ${jboss.server.home.url}/deploy/ or any of its subdirectories
2. Then, JBoss performs the necessary steps to make that application ready for our use

Undeployment on Jboss As
Undeployment is also a two-step process

1.First we notify JBoss that of the application we want to undeploy by removing it from${jboss.server.home.url}/deploy/ directory
2.Then, JBoss performs the necessary steps to stop the application and unload its resources.

Alternatively, applications can be deployed/undeployed/and re-deployed viajboss.system:service=MainDeployer JMX MBean (more on this later).
This mechanism also support remote management of JBoss deployments.Supports deployment dependencies

 Hot-deployment vs. cold-deployment

Archived components are uncompressed (a.k.a. exploded) under${jboss.server.temp.dir}/deploy/
JBoss deletes (or at least it is supposed to delete) ${jboss.server.temp.dir}/deploy/deployments upon restart
It is recommended to deploy applications already uncompressed (exploded) for to avoid the overhead of uncompression, and provide easy access to deployment descriptors and JSP files
The deployed components are automatically redeployed if their deployment descriptors are modified while JBoss AS is running
JBoss supports nested deployments (e.g. WAR under EAR) regardless of whether they are compressed into archives or deployed uncompressed
With clustering enabled, JBoss AS also supports farmed deployment – that is, pushing applications across the entire cluster when deployed on any single member of that cluster
JBoss supports JSR-88 (Java EE application deployment spec) but
There are no tools that make this kind of deployment easy – requires writing code
The resulting deployments go into the tmp/ directory – making redeployments harder

4. Deployers on JBoss AS

JBoss has an extensible deployment architecture that allows components to be easily integrated into the core JBoss Microcontainer
Deployers for: WARs, EARs, EJBs, JAR libraries, RARs, SARs, XML-based services, HARs, Aspects, Client, BeanShell scripts
The deployers are deployed themselves as *.deployer or *-deployer-beans.xml  under ${jboss.server.home.url}/deployers/ directory

4.1. Type of Deployers

Web – handles web application archives as .war files with descriptors WEB-INF/web.xml, WEB- INF/jboss-web.xml (optional), and WEB-INF/context.xml (optional)

EAR – handles enterprise application archives as .ear files with descriptors META-INF/application.xml and META-INF/jboss-app.xml (optional)

EJB – handles Enterprise Java Bean archives as .jar files with descriptors META-INF/ejb-jar.xml and META-INF/jboss.xml (optional)

RAR – handles JCA resource archives as .rar files with a descriptor META-INF/ra.xml
SAR – handles JBoss MBean service archives either as .sar files with a META-INF/jboss-service.xml descriptor, or as stand alone *-service.xml files

Web Service – handles JBoss Web Services as *.wsr files
POJO – handles plain old java objects deployed as *-jboss-beans.xml files that register with JBoss Microcontainer
XML – handles arbitrary .xml files that are converted into SARs (e.g. *-ds.xml get deployed as data sources)
HAR – handles Hibernate archives as .har files with a META-INF/hibernate-service.xmldescriptor
Aspect – handles aspect archives either as .aop files with a META-INF/jboss-aop.xmldescriptor or as stand-alone *-aop.xml files
Client – handles Java EE application client resources as .jar files with META-INF/application-client.xml and META-INF/jboss-client.xml (optional) descriptors
BeanShell – handles bean shell scripts as .bsh files that represent MBeans
Zip – handles arbitrary .zip archives that are examined for that actual deployment type based on the internal deployment descriptors

JBoss Administration Console

Included from Jboss 5.1.0 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.

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>

Features:

1.  Provides an overview of the server configuration.
2.  Configuring the ports using the Service Binding Manager.
3.  Deploy, Re-deploy, Undeploy and control the applications.
4.  Configure, manage JMS resources.
5.  Configure, manage connection factories.
6.  Add, remove, configure and control the Data Sources.
7. Gather metrics related to the EAP instances, JMS Queues, Topics, Data Sources

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.

1.  Display the JNDI tree : Lists the JNDI object bound using service=JNDIView
2.  Generate a thread dump: Capture the thread dumps using jboss.system:type=ServerInfoMbean
3. Display the memory pool usage : Using the jboss.system:type=ServerInfo mbean
4. Manage the deployment scanner: Enable/ Disable the Hot Deployment scanner.
5. Redeploy an application
6. Shut down JBoss

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

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

<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”/>

JBOSS 6  

Different Way to deploy Jboss 7 Application Server

src=”http://rmohan.com/wp-content/uploads/2014/11/deploy-022.png” alt=”deploy 022″ width=”948″ height=”651″ />