Jboss 5 runtime for openesb

Build from source code

The source code of the runtime is here.

The required software:

Maven 3.0.3
Java 1.6+

The runtime of the OpenESB on JBoss must first be built using maven.

You have to add to the config.xml file in the conf directory of your maven installation :

        <repository>
          <id>openesb-snapshot</id>
          <url>http://build.open-esb.net:8081/nexus/content/repositories/openesb-snapshot/</url>
          <releases>
            <enabled>true</enabled>
          </releases>
          <snapshots>
            <enabled>true</enabled>
          </snapshots>
        </repository>
        <repository>
          <id>openesb-release</id>
          <url>http://build.open-esb.net:8081/nexus/content/repositories/openesb-release/</url>
          <releases>
            <enabled>true</enabled>
          </releases>
          <snapshots>
            <enabled>true</enabled>
          </snapshots>
        </repository>

Building the OpenESB on JBoss project will produce the following artifact: packaging\jboss-dist\bld\openesb-jboss5-dist-1.1-distribution.zip

Getting the binary from the jenkins build

The source code can be found here.

The run-time is built nightly here and the binary can be downloaded here.

Installing the Runtime

Installation steps

After exploding that zip file, perform the following steps:

Step	Description
1	Copy the jboss5-jbi-install folder to the root of the JBoss installation (e.g.: jboss-5.1.0.GA)
2	modify the bi/run.sh or bin.run.bat to add the following line JAVA_OPTS="$JAVA_OPTS -Djmx.invoke.getters=true -Djava.util.logging.manager=java.util.logging.LogManager -Djava.util.logging.config.file=$JBOSS_HOME/server/default/conf/logger.properties"
3	Add the file logger.properties tout de directory server/default/conf under the JBoss Installation
4	Copy the openesb-jboss5-deployer.jar file to the deployers directory of the JBoss server instance (e.g.: jboss-5.1.0.GA\server\default\deployers)
5	Copy the openesb-jboss5.sar file to the deploy directory of the JBoss instance (e.g.: jboss-5.1.0.GA\server\default\deploy)
6	Create the following directories under the JBoss server instance (e.g.: jboss-5.1.0.GA\server\default): jbi/autoinstall jbi/autodeploy
7	Start up JBoss. Once JBoss has started, move the JBI shared lib components (e.g.: encoderlib.jar, wsdlextlib.jar, wsdlsl.jar) the to jbi/autoinstall directory. Example JBoss log output after installing the shared libs: 07:51:38,729 INFO [management] Installing shared library sun-encoder-library to target default. 07:51:38,789 INFO [framework] JBIFW1300: Shared Library sun-encoder-library has been installed. 07:51:39,279 INFO [management] Installing shared library sun-wsdl-ext-library to target default. 07:51:39,349 INFO [framework] JBIFW1300: Shared Library sun-wsdl-ext-library has been installed. 07:51:39,579 INFO [management] Installing shared library sun-wsdl-library to target default. 07:51:39,639 INFO [framework] JBIFW1300: Shared Library sun-wsdl-library has been installed.
8	Move the rest of the BC and SE jars to jbi/autoinstall, one by one; if there are any interdependencies between the JBI components, the components without dependencies should be moved to the jbi/autoinstall directory first. Once all of the JBI components are installed, JBI SAs can be installed by moving them into the jbi/autodeploy directory

logger.properties

# Properties file which configures the operation of the JDK 
# logging facility.
# The system will look for this config file, first using 
# a System property specified at startup: 
# 
# >java -Djava.util.logging.config.file=myLoggingConfigFilePath 
# 
# If this property is not specified, then the config file is 
# retrieved from its default location at: 
# 
# JDK_HOME/jre/lib/logging.properties
# Global logging properties. 
# ------------------------------------------ 
# The set of handlers to be loaded upon startup. 
# Comma-separated list of class names. 
# (? LogManager docs say no comma here, but JDK example has comma.) 
handlers=java.util.logging.FileHandler, java.util.logging.ConsoleHandler
# Default global logging level. 
# Loggers and Handlers may override this level 
.level=INFO
# Handlers 
# -----------------------------------------
# --- ConsoleHandler --- 
# Override of global logging level 
java.util.logging.ConsoleHandler.level=FINE
java.util.logging.ConsoleHandler.formatter=java.util.logging.SimpleFormatter
# Loggers 
# ------------------------------------------ 
# Loggers are usually attached to packages. 
# Here, the level for each package is specified. 
# The global level is used by default, so levels 
# specified here simply act as an override. 
com.sun.jbi.level=FINE
com.sun.jbi.framework.level=FINE

Components to install

see Common Installation Steps

To use Modern version of sl4j (1.6.x)

When using Pojose component in conjunction with spring framework (3.2;x) for example, it cannot work as Jboss 5 comes with sl4j-jboss-logging bridge on 1.5.8 version of sl4j.

To avoid this problem here are the steps to apply :

Step	Description
1	Remove file jboss-5.1.0.GA/common/lib/slf4j-api.jar
2	Remove file jboss-5.1.0.GA/common/lib/slf4j-jboss-logging.jar
3	Download and install latest sl4j jar http://repo1.maven.org/maven2/org/slf4j/slf4j-api/1.7.5/slf4j-api-1.7.5.jar in jboss-5.1.0.GA/common/lib directory
4	Download and install jboss logging sl4j bridge we rebuild from source code here http://build.open-esb.net:8080/jenkins/view/JBoss/job/slf4j-jboss-logging/lastSuccessfulBuild/artifact/target/slf4j-jboss-logging-1.1.0.Final-SNAPSHOT.jar in jboss-5.1.0.GA/common/lib directory

Installing the Netbeans Plugin

The source code for the plugin is here, the jenkins build and the nbm to install.

JBoss 5.1.0 GA