Installation on JBoss EAP
Install JBoss Fuse 6.2.1 on JBoss EAP 6.4
Copyright © 2011-2015 Red Hat, Inc. and/or its affiliates.
Abstract
Chapter 1. Installation Guide Overview
Structure of Red Hat JBoss Fuse 6.2.1
Table 1.1.
| JBoss Fuse Version | Components | Prequisites |
|---|---|---|
| JBoss Fuse on Karaf |
jboss-fuse-karaf-6.2.1.redhat-XXX
jboss-fuse-full-update-6.2.1
Optional packages:
|
JBoss Fuse 6.2.0 for update package
|
|
JBoss Fuse on JBoss EAP
|
jboss-fuse-eap-6.2.1
Optional packages:
| JBoss EAP 6.4 |
Contents of JBoss Fuse Packages
The packages for JBoss Fuse contain discrete sets of functionality. The base package for the chosen platform is mandatory but the additional packages are optional.
| Pack name | Contents |
|---|---|
|
jboss-fuse-karaf-6.2.1.redhat-XXX or
jboss-fuse-full-update-6.2.1
|
|
|
JBoss Fuse on JBoss EAP
|
|
| Integration Pack | Contains quickstarts to enable integration of JBoss Fuse components with other modules that are not part of this JBoss Fuse release. |
| JON Pack | Red Hat JBoss Operations Network |
Chapter 2. Read Me
2.1. Back Up Your Data
2.2. Red Hat Documentation Site
2.3. EAP_HOME
EAP_HOME refers to the root directory of the Red Hat JBoss Enterprise Application Platform installation on which JBoss Fuse is deployed.
2.4. MODE
MODE refers to the mode that your instance of JBoss EAP is running in. MODE will either be standalone or domain. For more information about MODE see JBoss EAP Operating Modes. Substitute either standalone or domain whenever you see MODE in a file path in this documentation.
Chapter 3. Install JBoss Fuse on JBoss EAP
Prerequisites
Install JBoss Fuse using Installer
- Download Red Hat JBoss Fuse 6.2.1 on EAP Installer to a temporary location on your file system.
- Navigate to $EAP_HOME of a clean instance of JBoss EAP.
- Run the installer with the following command:
java -jar temporary location/fuse-eap-installer-6.2.1.redhat-084.jar
Chapter 4. Monitor Fuse Resources
Abstract
4.1. Installation Procedure
Fuse Plugin Pack for JBoss ON 3.3:
- Navigate to the Red Hat Software Downloads page on the Red Hat Customer Portal.
- Select JBoss ON for Fuse under Management in the sidebar menu (or using the drop-down menu for the Products field).
- Make sure
3.3appears in the Version drop-down list on the Software Downloads page. - Click Download next to Fuse Plugin Pack for Red Hat JBoss Operations Network 3.3 .
- Unzip the plugin package (
jon-plugin-pack-fuse-3.3.0.GA.zip) into a temporary directory (for example,/installDir/server/). - Install the jar files in one of two ways:
- Hot DeployCopy the unpacked jar files into the JBoss Operations Network's
/installDir/server/plugins/directory. For details, see the JBoss Operations Network Installation Guide. - JON Server UIFor details, see the JBoss Operations Network Installation Guide, or watch the video Installing JBoss Operations Network - Part 4, Installing JON Agent Plugins.
Chapter 5. Start and Stop the Application Server
5.1. Start JBoss EAP 6
Summary
This topic covers the steps to start JBoss EAP 6.4.
Procedure 5.1. Start the Platform Service as a Standalone Server
For Red Hat Enterprise Linux.
Run the command: EAP_HOME/bin/standalone.shFor Microsoft Windows Server.
Run the command: EAP_HOME\bin\standalone.batOptional: Specify additional parameters.
To print a list of additional parameters to pass to the start-up scripts, use the-hparameter.
Procedure 5.2. Start the Platform Service as a Domain Server
For Red Hat Enterprise Linux.
Run the command: EAP_HOME/bin/domain.shFor Microsoft Windows Server.
Run the command: EAP_HOME\bin\domain.batOptional: Specify additional parameters.
To print a list of additional parameters to pass to the start-up scripts, use the-hparameter.
5.2. Stop JBoss EAP 6.4
Stop JBoss EAPl using the Management CLI.
- Run the EAP_HOME/bin/jboss-cli.sh command to launch the Management CLI.
$ EAP_HOME/bin/jboss-cli.sh
- Run the connect command to connect to the server.
[disconnected /] connect
- Run the shutdown command to stop the server.
[standalone@localhost:9999 /] shutdown
- Run the quit command to close the Management CLI.
[standalone@localhost:9999 /] quit
Stop JBoss Enterprise Application Platform in terminal window.
Navigate to the terminal where JBoss EAP is running. Press Ctrl+C.
Chapter 6. Maven Repositories
6.1. About Maven
http:// when located on an HTTP server, or file:// when located on a file server. The default repository is the public remote Maven 2 Central Repository.
settings.xml file. You can either configure global Maven settings in the M2_HOME/conf/settings.xml file, or user-level settings in the USER_HOME/.m2/settings.xml file.
6.2. About The Provided Maven Repositories
settings.xml file during installation, Maven is already configured to use the online repositories. If you did not provide the location during installation, you need to configure Maven manually by following the procedure in Section 6.3, “Configure Maven to Use the Online Repositories” .
6.3. Configure Maven to Use the Online Repositories
settings.xml file during installation, Maven is already configured to use the online repositories. If you did not provide the location during installation, you need to configure Maven manually by following the procedure in Section 6.3, “Configure Maven to Use the Online Repositories”.
Procedure 6.1. Configuring Maven to Use the Online Repositories
- Add entries for the online repositories to Maven's
settings.xmlfile as in the code sample below:<settings xmlns="http://maven.apache.org/SETTINGS/1.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/SETTINGS/1.0.0 http://maven.apache.org/xsd/settings-1.0.0.xsd"> <profiles> <!-- Profile with online repositories required by Fuse --> <profile> <id>fsw-online-repos</id> <repositories> <repository> <id>jboss-ga-repository</id> <url>http://maven.repository.redhat.com/techpreview/all</url> <releases> <enabled>true</enabled> </releases> <snapshots> <enabled>false</enabled> </snapshots> </repository> <repository> <id>jboss-public-repository</id> <url>http://repository.jboss.org/nexus/content/repositories/public/</url> <releases> <enabled>true</enabled> </releases> <snapshots> <enabled>false</enabled> </snapshots> </repository> <repository> <id>jboss-fuse-public-repository</id> <url>https://repo.fusesource.com/nexus/content/groups/public/</url> <releases> <enabled>true</enabled> </releases> <snapshots> <enabled>false</enabled> </snapshots> </repository> </repositories> <pluginRepositories> <pluginRepository> <id>jboss-ga-plugin-repository</id> <url>http://maven.repository.redhat.com/techpreview/all</url> <releases> <enabled>true</enabled> </releases> <snapshots> <enabled>false</enabled> </snapshots> </pluginRepository> <pluginRepository> <id>jboss-public-plugin-repository</id> <url>http://repository.jboss.org/nexus/content/repositories/public/</url> <releases> <enabled>true</enabled> </releases> <snapshots> <enabled>false</enabled> </snapshots> </pluginRepository> <pluginRepository> <id>jboss-fuse-public-plugin-repository</id> <url>https://repo.fusesource.com/nexus/content/groups/public/</url> <releases> <enabled>true</enabled> </releases> <snapshots> <enabled>false</enabled> </snapshots> </pluginRepository> </pluginRepositories> </profile> </profiles> <activeProfiles> <!-- Activation of the Fuse profile --> <activeProfile>fsw-online-repos</activeProfile> </activeProfiles> </settings> - If you modified the
settings.xmlfile while JBoss Developer Studio was running, you must refresh Maven settings in the IDE. From the menu, choose → . In the Preferences Window, expand Maven and choose User Settings. Click the button to refresh the Maven user settings in JBoss Developer Studio.Figure 6.1. Update Maven User Settings

[D]
Result
Maven has been configured to use the online repositories provided for Red Hat JBoss Fuse.
- Missing artifact ARTIFACT_NAME
- [ERROR] Failed to execute goal on project PROJECT_NAME; Could not resolve dependencies for PROJECT_NAME
~/.m2/repository/ directory on Linux or the %SystemDrive%\Users\USERNAME\.m2\repository\ directory on Windows. This will force Maven to download correct versions of required artifacts during the next build.
6.4. Dependency Management
pom.xml file. Adding the BOM and parent will ensure that correct versions of plug-ins and transitive dependencies from the provided Maven repositories are included in the project.
pom.xml file:
org.jboss.fuse.bom:jboss-fuse-parent:6.2.1.redhat-084
dependencyManagement section:
org.jboss.fuse.bom:jboss-fuse-parent:6.2.1.redhat-084
<parent>
<groupId>org.jboss.fuse.bom</groupId>
<artifactId>jboss-fuse-parent</artifactId>
<version>6.2.1.redhat-084</version>
</parent>
...
<dependencyManagement>
<dependencies>
<dependency>
<groupId>org.jboss.fuse.bom</groupId>
<artifactId>jboss-fuse-parent</artifactId>
<version>6.2.1.redhat-084</version>
<type>pom</type>
<scope>import</scope>
</dependency>
</dependencies>
</dependencyManagement>Chapter 7. Install Red Hat JBoss Development Tools
7.1. Install Red Hat JBoss Developer Studio
7.2. Install Red Hat JBoss Developer Studio Integration Stack
Appendix A. Prerequisite Software
A.1. Install OpenJDK on Red Hat Linux
- Subscribe to the Base Channel Obtain the OpenJDK from the RHN base channel. (Your installation of Red Hat Enterprise Linux is subscribed to this channel by default.)
- Install the Package. Use the yum utility to install OpenJDK: yum install java-1.7.0-openjdk-devel
- Verify that OpenJDK is now your system default. You can ensure the correct JDK is set as the system default by following the steps below.
- As a root user, run the alternatives command for java: /usr/sbin/alternatives --config java
- Select
/usr/lib/jvm /jre-1.7.0-openjdk/bin/java. - Apply the same for javac:
/usr/sbin/alternatives --config javac - Select
/usr/lib/jvm /java-1.7.0-openjdk/bin/javac.
Result
OpenJDK is installed successfully on your machine.
A.2. Install Maven
Prerequisites
The following software must be installed:
- An archiving tool for extracting the contents of compressed files.
- OpenJDK.
Procedure A.1. Install Maven
Download Maven.
- Enter http://maven.apache.org/download.cgi in the address bar of a browser.
- Download
apache-maven-3.0.5ZIP file and save it to your hard drive.
Install and configure Maven.
On Red Hat Enterprise Linux
- Extract the ZIP archive to the directory where you wish to install Maven.
- Open a terminal.
- Add the M2_HOME environment variable by entering the following command:
export M2_HOME=/usr/local/apache-maven/apache-maven-3.0.x
- Add the M2 environment variable by entering the following command:
export M2=$M2_HOME/bin
- Add the M2 environment variable to your path by entering the following command:
export PATH=$M2:$PATH
- Make sure that JAVA_HOME is set to the location of your JDK. For example:
export JAVA_HOME=/usr/lib/jvm/java-1.7.0-openjdk.x86_64
- Make sure that $JAVA_HOME/bin is in your PATH environment variable.
- Run the following command to verify that Maven is installed successfully on your machine:
mvn --version
On Microsoft Windows
- Extract the ZIP archive to the directory where you wish to install Maven. The subdirectory
apache-maven-3.0.xis created from the archive. - Press Start+Pause|Break. The System Properties dialog box is displayed.
- Click the Advanced tab and click Environment Variables.
- Under System Variables, select Path.
- Click Edit and add the two Maven paths using a semicolon to separate each entry.
- Add the M2_HOME variable and set the path to
C:\Program Files\Apache Software Foundation\apache-maven-3.0.X. - Add the M2 variable and set the value to %M2_HOME%\bin.
- Update or create the Path environment variable:
- Add the %M2% variable to allow Maven to be executed from the command line.
- Add the variable %JAVA_HOME%\bin to set the path to the correct Java installation.
- Click OK to close all the dialog boxes including the System Properties dialog box.
- Open Windows command prompt and run the following command to verify that Maven is installed successfully on your machine:
mvn --version
Result
Maven is successfully installed and configured on your machine.
Appendix B. Verify Your Red Hat JBoss Fuse Installation
- If no error was reported, you can verify the installation by performing the following steps:
- Start the JBoss EAP server by running standalone.sh command
- Open the
server.logfile to check if any error messages have been logged and that SwitchYard (and other component subsystems) have loaded correctly - Navigate to the Management Console (http://localhost:9990/) check that you can see the SwitchYard Runtime properties.
- Compile, deploy and run a quickstart application.
Legal Notice
Trademark Disclaimer
