Okay, now it's time to install JBoss ESB into the JBoss AS server we installed previously. But, wait. Before we do that, let's examine just what it means to "deploy" JBoss ESB to an application server. "Deploying" something to the application server means putting it in a location where the application server can recognize it, control it, and start the application's lifecycle. Follow these steps to deploy JBoss ESB:
install
directory under the jbossesb-4.10
directory:cd install
deployment.properties-example
in the install directory. Copy this file to a file named deployment.properties
:cp deployment.properties-example deployment.properties
deployment.properties
file. Open up your favorite text editor and define these properties in that file:org.jboss.esb.server.home=/opt/jboss-5.1.0.GA-jdk6 org.jboss.esb.server.config=all
You probably noticed that we just referenced a property named org.jboss.esb.server.config
. What's a server config?
Each JBoss server profile consists of a set of server configurations (to control the level of logging detail, server start up memory requirements, and so on) and the set of services to install. JBoss AS 5.1.0.GA is shipped with these profiles:
all
: starts all available servicesdefault
: a base Java EE serverminimal
: a bare, slimmed down configuration, the minimum for starting the application serverproduction
: a profile designed for use in production environmentsstandard
: a Java EE certified configuration of servicesweb
: a small set of services designed to mimic a web profileWe'll use either the default
or all
profile for most of our work in this book.
all
configuration, just copy its directory tree:cp -pR all all.original
ant
command to deploy JBoss ESB to JBoss AS is very simple:ant deploy
We accomplished two tasks in this section, namely:
ant
later in the book, when we work with the JBoss ESB quickstarts and other example code.But, what exactly does this invocation of ant deploy
actually do? In the context of this installation, just what JBoss ESB bits are installed? The installed JBoss ESB bits are:
server/default/deployers/esb.deployer
: The name is a dead giveaway here. This component enables the server to deploy .esb
archives.server/default/deploy/jbossesb-registry.sar
: This service archive contains ESB's integration to its service registry. A registry is used to look up service endpoints at runtime; a repository is used to store and manage the life cycle of services. We'll describe the registry, how it works, and how you use it in a subsequent chapter.server/default/deploy/jbossesb.esb
: This ESB archive contains internal support for messages and message redelivery.server/default/deploy/jbpm.esb
: This ESB archive contains the JBoss ESB integration to the jBPM Business Process Management system.server/default/deploy/jbrules.esb
: This ESB archive contains the JBoss ESB integration to JBoss Rules for building rules-based services.server/default/deploy/smooks.esb
: This ESB archive contains the JBoss ESB integration to the Smooks message transformation and routing engine.server/default/deploy/soap.esb
: This ESB archive contains the JBoss ESB support for hosting Web Services.server/default/deploy/spring.esb
: This ESB archive contains the JBoss ESB support for applications built with the Spring framework.