JBoss 5.1 - Chapter 01 - Installing Core Components

From Training Material
Jump to navigation Jump to search
Title
Installing Core Components
Author
Bernard Szlachta (NobleProg Ltd)

Finding Help ⌘

Installing the Java environment ⌘

Oracle JKD ⌘

There are following methods of intallling JDK on the machine:

  • Subscribe to Supplementary Server channel + yum install java-1.6.0-sun-devel
  • Manual download (rpm)
  • Manual download (sh)

Manual Download (rpm) ⌘

1. Step 1: Download jdk-6u45-linux-i586-rpm.bin and save it in /opt

2. Step 2

cd /opt
./jdk-6u45-linux-i586-rpm.bin

3. Step 3

rpm -i jdk-6u45-linux-i586.rpm
echo JAVA_HOME

OpenJDK ⌘

yum install java-1.6.0-openjdk
/usr/sbin/alternatives --config java
java -version
java version "1.6.0_24"
OpenJDK Runtime Environment (IcedTea6 1.11.11) (rhel-1.40.1.11.11.el5_9-i386)
OpenJDK Client VM (build 20.0-b12, mixed mode)

Swiching between alternatives ⌘

/usr/sbin/alternatives --config java

Installing JBoss AS ⌘

Ways of installing Jboss 5 on Red Hat Enterprise Linux

  • zip installation
  • part of JBoss Enterprise Application Platform 5
    • zip
    • rpm
  • shipped with multiple products (e.g. jBPM)

Installing from zip ⌘

Open Source ⌘

unzip jboss-5.1.0.GA-jdk6.zip
cd jboss-5.1.0.GA/bin

Jboss EAP 5.1.2 ⌘

Setting up Variables

You can add it either to /etc/profile or .bashrc

export JBOSS_HOME=/opt/jboss-5.1.0.GA
export PATH=$PATH:$JBOSS_HOME/bin

Uninstalling JBoss ⌘

  1. Remove the folder
  2. Remove the JBOSS_HOME variable

Testing Server ⌘

./run.sh -b 0.0.0.0
lynx localhost:8080

You may want to disable firewalls as well

/etc/init.d/iptables stop

Enabled Authentication for EAP ⌘

In conf/props/jmx-console-users.properties add appropriate user.

Application server features ⌘

JBoss Microcontainer ⌘

  • http://www.jboss.org/jbossmc
  • next generation POJO based kernel
  • supports an extensible deployment model and advanced dependency relationships.

JBoss EJB3 ⌘

  • implementation of EJB 3.0 spec
  • is a deep overhaul and simplification of the

JBoss Messaging ⌘

  • Default JMS provider in JBoss AS

JBossCache ⌘

Comes in two flavors:

  • A traditional tree-structured node-based cache
  • a 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 ⌘

  • web services stack providing Java EE compatible web services,

JAX-WS-2.0

JBoss Transactions ⌘

  • default transaction manager JBoss Transactions

JBoss Web ⌘

  • Web container
  • based on Tomcat
  • includes the Apache Portable Runtime (APR) and Tomcat native technologies to achieve scalability and performance characteristics that match and exceed the Apache Http server.

JBoss Security ⌘

  • pluggable authorization models including SAML, XACML and federation.

Creating a custom server configuration ⌘

Existing Configurations ⌘

Module minimal web default standard all
Microcontainer Y Y Y Y Y
Naming service Y Y Y Y Y
Log4j Y Y Y Y Y
Deployment scanner Y Y Y Y Y
JPA Y Y Y Y
EJB container Y Y Y
JCA support Y Y Y Y
JMS Y Y Y
Mail service Y Y Y
HSQL DB Y Y Y Y
JBossWS Y Y Y
XA transactions Y Y Y Y
Monitoring services Y Y Y
Quartz service Y Y Y
Clustering support Y
RMI-IIOP and jUDDI Y Y

Creating own configuration ⌘

  1. Copy configuration closest to your needs
  2. Rename the folder to match your configuration name (e.g. prod)
  3. Remove or add components, change the configuration
  4. Run server with -c paramter
run.sh -c prod

https://community.jboss.org/wiki/JBoss5xTuningSlimming

Exercise ⌘

Add JMS to your custom' configuration based on the web

hint:

  • deployers/messaging-definitions-jboss-beans.xml
  • deploy/messaging
  • deploy/jms-ra.rar