Escolar Documentos
Profissional Documentos
Cultura Documentos
Works 6
Installation Guide
Legal Notice
Copyright 2014 Red Hat, Inc..
T his document is licensed by Red Hat under the Creative Commons Attribution-ShareAlike 3.0 Unported
License. If you distribute this document, or a modified version of it, you must provide attribution to Red
Hat, Inc. and provide a link to the original. If the document is modified, all Red Hat trademarks must be
removed.
Red Hat, as the licensor of this document, waives the right to enforce, and agrees not to assert, Section
4d of CC-BY-SA to the fullest extent permitted by applicable law.
Red Hat, Red Hat Enterprise Linux, the Shadowman logo, JBoss, MetaMatrix, Fedora, the Infinity Logo,
and RHCE are trademarks of Red Hat, Inc., registered in the United States and other countries.
Linux is the registered trademark of Linus T orvalds in the United States and other countries.
Java is a registered trademark of Oracle and/or its affiliates.
XFS is a trademark of Silicon Graphics International Corp. or its subsidiaries in the United States
and/or other countries.
MySQL is a registered trademark of MySQL AB in the United States, the European Union and other
countries.
Node.js is an official trademark of Joyent. Red Hat Software Collections is not formally related to or
endorsed by the official Joyent Node.js open source or commercial project.
T he OpenStack Word Mark and OpenStack Logo are either registered trademarks/service marks or
trademarks/service marks of the OpenStack Foundation, in the United States and other countries and
are used with the OpenStack Foundation's permission. We are not affiliated with, endorsed or
sponsored by the OpenStack Foundation, or the OpenStack community.
All other trademarks are the property of their respective owners.
Abstract
T his guide teaches you how to install the Red Hat JBoss Fuse Service Works product.
T able of Contents
Table of Contents
.Preface
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4. . . . . . . . .
1. Document Conventions
4
1.1. T ypographic Conventions
4
1.2. Pull-quote Conventions
5
1.3. Notes and Warnings
6
2. Getting Help and Giving Feedback
6
2.1. Do You Need Help?
6
2.2. We Need Feedback!
7
. .art
P
. . .I.. Basic
. . . . . .Installation
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8. . . . . . . . .
. .hapter
C
. . . . . . 1.
. . Preface
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9. . . . . . . . .
1.1. What is Red Hat JBoss Fuse Service Works?
9
1.2. Core Capabilities
9
1.3. System Integration
9
1.4. Core and Components
10
1.5. Components of Red Hat JBoss Fuse Service Works
10
1.6. Red Hat JBoss Fuse Service Works Features
11
1.7. Integration Use Case
11
1.8. Back Up Your Data
12
1.9. Red Hat Documentation Site
12
. .hapter
C
. . . . . . 2.
. . Prerequisites
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
..........
2.1. Prerequisites for Installing Red Hat JBoss Fuse Service Works
13
2.1.1. Prerequisites for Installing Red Hat JBoss Fuse Service Works
13
2.1.2. Java Virtual Machine
13
2.1.3. Install JBoss Enterprise Application
13
2.1.4. Install Open JDK on Red Hat Linux
14
2.1.5. Install Maven
14
2.1.6. Install JBoss Developer Studio
16
2.1.7. Install JBoss Developer Studio Integration Stack
19
. .hapter
C
. . . . . . 3.
. . Maven
. . . . . . .Repositories
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
..........
3.1. About Maven
21
3.2. About T he Provided Maven Repositories
21
3.3. Configuring Maven to Use the File System Repositories
21
3.4. Configuring Maven to Use the Online Repositories
25
3.5. Dependency Management
28
. .art
P
. . .II.. .Basic
. . . . . Installation
. . . . . . . . . . .and
. . . .Operation
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
..........
. .hapter
C
. . . . . . 4. . .Download
. . . . . . . . .the
. . . Product
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
..........
4 .1. Red Hat Customer Portal
31
4 .2. Packages Available for Download
31
4 .3. Javadocs
31
4 .4. Download Files From the Red Hat Customer Portal
31
4 .5. Checksum Validation
32
4 .6. Verify the Downloaded File
32
4 .7. Red Hat Documentation Site
33
. .hapter
C
. . . . . . 5.
..T
. .he
. . JBoss
. . . . . . Fuse
. . . . . Service
. . . . . . . .Works
. . . . . .Installer
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
..........
5.1. Installing JBoss Fuse Service Works by GUI
34
5.1.1. Additional Configuration Options
36
5.2. Installing JBoss Fuse Service Works by Script
36
5.2.1. Supplying Passwords to the Installation Script
37
. .hapter
C
. . . . . . 6.
. . Starting
. . . . . . . . and
. . . . Stopping
. . . . . . . . .the
. . . Application
. . . . . . . . . . .Server
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
..........
1
T able of Contents
. .hapter
C
. . . . . . 14
. . .. .Configuring
. . . . . . . . . . .S-RAMP
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
..........
14.1. Download, Install and Configure S-RAMP
66
14.2. Verify S-RAMP Installation
67
. .art
P
. . .IV.
. . Advanced
. . . . . . . . . .Use
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
..........
. .hapter
C
. . . . . . 15.
. . . .Starting
. . . . . . . Red
. . . . Hat
. . . . JBoss
. . . . . . Fuse
. . . . .Service
. . . . . . . Works
. . . . . . in
. . an
. . . Enterprise
. . . . . . . . . . Environment
.......................
15.1. Introduction
70 70
15.2. Specify the Network Interface
70
.Security
. . . . . . . Considerations
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
..........
A.1. Secure Ways of Running Red Hat JBoss Fuse Service Works
72
. . . . . . . . .History
Revision
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
..........
Preface
1. Document Conventions
T his manual uses several conventions to highlight certain words and phrases and draw attention to
specific pieces of information.
In PDF and paper editions, this manual uses typefaces drawn from the Liberation Fonts set. T he Liberation
Fonts set is also used in HT ML editions if the set is installed on your system. If not, alternative but
equivalent typefaces are displayed. Note: Red Hat Enterprise Linux 5 and later include the Liberation Fonts
set by default.
Preface
T o insert a special character into a gedit file, choose Applications Accessories
Character Map from the main menu bar. Next, choose Search Find from the
Character Map menu bar, type the name of the character in the Search field and click
Next. T he character you sought will be highlighted in the Character T able. Double-click
this highlighted character to place it in the T ext to copy field and then click the Copy
button. Now switch back to your document and choose Edit Paste from the gedit menu
bar.
T he above text includes application names; system-wide menu names and items; application-specific
menu names; and buttons and text found within a GUI interface, all presented in proportional bold and all
distinguishable by context.
Mono-spaced Bold Italic or Proportional Bold Italic
Whether mono-spaced bold or proportional bold, the addition of italics indicates replaceable or variable
text. Italics denotes text you do not input literally or displayed text that changes depending on
circumstance. For example:
T o connect to a remote machine using ssh, type ssh username@ domain.name at a shell
prompt. If the remote machine is exam ple.com and your username on that machine is john,
type ssh john@ exam ple.com .
T he m ount -o rem ount file-system command remounts the named file system. For
example, to remount the /hom e file system, the command is m ount -o rem ount /hom e.
T o see the version of a currently installed package, use the rpm -q package command. It
will return a result as follows: package-version-release.
Note the words in bold italics above: username, domain.name, file-system, package, version and release.
Each word is a placeholder, either for text you enter when issuing a command or for text displayed by the
system.
Aside from standard usage for presenting the title of a work, italics denotes the first use of a new and
important term. For example:
Publican is a DocBook publishing system.
Desktop
Desktop1
documentation
downloads
drafts
images
mss
notes
photos
scripts
stuff
svgs
svn
Source-code listings are also set in m ono-spaced rom an but add syntax highlighting as follows:
static int kvm_vm_ioctl_deassign_device(struct kvm *kvm,
struct kvm_assigned_pci_dev *assigned_dev)
{
int r = 0;
struct kvm_assigned_dev_kernel *match;
mutex_lock(&kvm->lock);
match = kvm_find_assigned_dev(&kvm->arch.assigned_dev_head,
Note
Notes are tips, shortcuts or alternative approaches to the task at hand. Ignoring a note should have
no negative consequences, but you might miss out on a trick that makes your life easier.
Important
Important boxes detail things that are easily missed: configuration changes that only apply to the
current session, or services that need restarting before an update will apply. Ignoring a box labeled
Important will not cause data loss but may cause irritation and frustration.
Warning
Warnings should not be ignored. Ignoring warnings will most likely cause data loss.
Preface
C hapter 1. Preface
Chapter 1. Preface
1.1. What is Red Hat JBoss Fuse Service Works?
Red Hat JBoss Fuse Service Works is a platform for developing enterprise application integration (EAI)
and service-oriented architecture (SOA) solutions. It consists of a service component framework, business
rules/complex event processing, life-cycle governance, runtime governance and process automation. It is
built on the same core as JBoss Fuse with enterprise messaging, Camel and CXF so, therefore, users can
use it to design, deploy, integrate and orchestrate business services.
Report a bug
10
C hapter 1. Preface
Encapsulate business rules as decision services using the JBoss Rules component in
SwitchYard. Each service has a well defined contract with protocol binding details and marshaling
details abstracted away by SwitchYard.
Smooks
T his transformation engine can be used in conjunction with Red Hat JBoss Fuse Service Works
to process messages.
Business Process Execution Language (BPEL)
You can use web services to orchestrate business rules using this language. It is included with
Red Hat JBoss Fuse Service Works for the execution of business process instructions.
JBoss Rules
T his is the rules engine that is packaged with Red Hat JBoss Fuse Service Works. It can infer
data from the messages it receives to determine which actions need to be performed.
T esting
Comprehensive unit test support is provided to allow you to test services as you develop them.
Report a bug
11
12
C hapter 2. Prerequisites
Chapter 2. Prerequisites
2.1. Prerequisites for Installing Red Hat JBoss Fuse Service Works
2.1.1. Prerequisites for Installing Red Hat JBoss Fuse Service Works
In order to install and run Red Hat JBoss Fuse Service Works, you must already have the following items
on your computer:
A supported Java Virtual Machine
A supported Java Development Kit (for running the quickstarts)
A supported database server (needed to run the JBoss Server)
Apache Maven (needed to run the Database Schema Configuration T ool and deploy the SwitchYard
quickstart examples)
An archiving tool (to extract the contents of compressed files)
JBoss Developer Studio 7 or later (obtain it from the Red Hat Customer Portal at
https://access.redhat.com/home)
Red Hat tests and certifies Red Hat JBoss Fuse Service Works against several different hardware
platforms, Java Virtual Machines, operating systems and databases. T his is an ongoing process and the
list of supported environments is always growing. Find the list of currently-supported environments at
https://access.redhat.com/site/articles/626513.
Report a bug
13
In a Microsoft Windows environment, right-click the file and select Extract All.
Result
JBoss Enterprise Application Platform 6 has been installed successfully. T he directory created by
extracting the Z ip archive is the top-level directory for the server.
Report a bug
a. As a root user, run the alternatives command for java: /usr/sbin/alternatives -config java
b. Select /usr/lib/jvm /jre-1.7.0-openjdk/bin/java .
c. Apply the same for javac: /usr/sbin/alternatives --config javac
d. Select /usr/lib/jvm /java-1.7.0-openjdk/bin/java.
Result
Open JDK is installed successfully on your machine.
Report a bug
14
C hapter 2. Prerequisites
b. Choose the compiled zip archive link as per your operating system and save the zip file.
2. Install and configure Maven.
A. Red Hat Enterprise Linux
a. Extract the zip file to the directory where you wish to install Maven. T hese instructions
assume that you have chosen /usr/local/apache-m aven/apache-m aven-3.0.5.
b. Open command line terminal.
c. Add the M2_HOME environment variable by entering the following command:
$ export M2_HOME=/usr/local/apache-m aven/apache-m aven-3.0.5
d. Add the M2 environment variable by entering the following command:
$ export M2=$M2_HOME/bin
e. Optional: Add the MAVEN_OPT S environment variable to specify JVM properties by
entering the following command:
$ export MAVEN_OPT S="-Xm s256m -Xm x512m "
You can use this environment variable to supply extra options to Maven.
f. Add M2 environment variable to your path by entering the following command:
$ export PAT H=$M2:$PAT H
g. Make sure that JAVA_HOME is set to the location of your JDK:
$ export JAVA_HOME=/usr/java/jdk1.5.0-02
Make sure that $JAVA_HOME/bin is in your PAT H environment variable.
h. Run the following command to verify that Maven is installed successfully on your machine:
$ m vn --version
B. Microsoft Windows
a. Extract the zip file to the directory where you wish to install Maven. T hese instructions
assume that you have chosen C:\Program Files\Apache Software Foundation.
T he subdirectory apache-m aven-3.0.5 will be created from the archive.
b. Press Start+Pause|Break. T he System Properties dialog box is displayed.
c. Click the Advanced tab and then click the Environm ent Variables button.
d. Under System Variables, select Path.
e. Click Edit and add the two Maven paths using a semi-colon to separate each entry.
Add the M2_HOME variable and set the path to C:\Program Files\Apache
Software Foundation\apache-m aven-3.0.5.
Add the M2 variable and set the value to %M2_HOME%\bin.
f. Update or create the Path environment variable:
15
Figure 2.1. Download Red Hat JBoss Middleware Software on the Customer Portal
4. Under Software Downloads, select the following options:
From the Product list, select JBoss Developer Studio.
From the Version list, select 7.1.x.
5.
For the JBoss Developer Studio universal installer, click Download for the Red Hat JBoss
Developer Studio 7.1.x Stand Alone Universal Binary download file.
For the JBoss Developer Studio and JBoss EAP universal installer, click Download for the Red
Hat JBoss Developer Studio 7.1.x Universal Binary with JBoss EAP download
file.
T his downloads a universal installer .jar file.
16
C hapter 2. Prerequisites
java -jar jbdevstudio-product-universal-version.jar
Note
Alternatively, to start the installer you may be able to double-click the .jar file.
7. When the Installer window opens, click Next.
8. After reading and agreeing to the terms of the End User License Agreement, click I accept the
term s of this license agreem ent and click Next.
9. In the Select the installation path field, type the path where you want
JBoss Developer Studio to be installed or click Browse to navigate to the location. When the
Select the installation path field shows the correct path, click Next. When you are
prompted about the specified location being created or overwritten, review the message and, if
satisfied, click OK or Yes as appropriate.
17
Important
You must specify a Java developer kit with a 32-bit JRE to install a 32-bit version of
JBoss Developer Studio and a 64-bit JRE to install a 64-bit version of
JBoss Developer Studio. T o change the bit version of the Java developer kit to be used for
installing JBoss Developer Studio, complete the appropriate step for your operating system:
On OS X operating systems, from the Installation type list click the appropriate bit
version.
On Linux distributions and Microsoft Windows operating systems, in the text field type the
path to the appropriate bit version of the Java developer kit.
18
C hapter 2. Prerequisites
Important
Linux distributions have a maximum number of files that a process can have open at one time. If this
maximum number of files is set too low, JBoss Developer Studio will not start. You must open the
/etc/security/lim its.conf file and ensure that the soft nofile and hard nofile
variables have values of 9216 at a minimum. If the variables have smaller values, the values must
be increased to 9216. If the variables are not specified, the following lines must be added to the file:
* soft nofile 9216
* hard nofile 9216
Report a bug
19
20
Important
T he set of online remote repositories is a technology preview source of components. As such, it is
not in scope of patching and is supported only for use in development environment. Using the set of
online repositories in production environment is a potential source of security vulnerabilities and is
therefore not a supported use case. For more information see
https://access.redhat.com/site/maven-repository.
Report a bug
Procedure 3.1.
1. Download the following Z IP archives containing the required repositories:
http://maven.repository.redhat.com/techpreview/fsw6/6.0.0/fsw-6.0.0.GA-redhat-2-repository.zip
http://maven.repository.redhat.com/techpreview/eap6/6.1.1/jboss-eap-6.1.1-maven-repository.zip
Alternatively, the Z IP archives can also be downloaded from http://access.redhat.com/jbossnetwork/.
2. Unzip the downloaded Z IP files into an arbitrary location in a local file system.
3. Add entries for the unzipped repositories to Maven's settings.xm l file. T he following code
sample contains a profile with the repositories and an activation entry for the profile:
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<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/xsd/settings-1.0.0.xsd">
<localRepository/>
<profiles>
<!-- Profile with local repositories required by Fuse Service Works -->
<profile>
<id>fsw-local-repos</id>
<repositories>
<repository>
<id>fsw-6.0.0.GA-redhat-2-repository</id>
<name>FSW 6.0.0.GA Repository</name>
<url>file://<!-- path to the repository -->/fsw-6.0.0.GA-redhat-2repository</url>
<layout>default</layout>
<releases>
<enabled>true</enabled>
<updatePolicy>never</updatePolicy>
</releases>
<snapshots>
<enabled>false</enabled>
<updatePolicy>never</updatePolicy>
</snapshots>
</repository>
<repository>
<id>jboss-eap-6.1.1.GA-maven-repository</id>
<name>EAP 6.1.1.GA Repository</name>
<url>file://<!-- path to the repository -->/jboss-eap-6.1.1.GAmaven-repository</url>
<layout>default</layout>
<releases>
<enabled>true</enabled>
<updatePolicy>never</updatePolicy>
</releases>
<snapshots>
<enabled>false</enabled>
<updatePolicy>never</updatePolicy>
</snapshots>
</repository>
</repositories>
<pluginRepositories>
<pluginRepository>
<id>fsw-6.0.0.GA-redhat-2-repository</id>
<name>FSW 6.0.0.GA Repository</name>
22
4. If you modified the settings.xm l file while JBoss Developer Studio was running, you must refresh
Maven settings in the IDE. From the menu, choose Window Preferences. In the Preferences
Window, expand Maven and choose User Settings. Click the Update Settings button to
refresh the Maven user settings in JBoss Developer Studio.
23
24
Important
If your cached local Maven repository contains outdated artifacts, you may encounter one of the
following Maven errors when you build or deploy your project:
Missing artifact ARTIFACT_NAME
[ERROR] Failed to execute goal on project PROJECT_NAME; Could not resolve dependencies
for PROJECT_NAME
T o resolve the issue, delete the cached local repository the ~/.m 2/repository/ directory on
Linux or the %SystemDrive%\Users\USERNAME\.m 2\repository\ directory on Windows. T his
will force Maven to download correct versions of required artifacts when performing the next build.
Report a bug
25
2. If you modified the settings.xm l file while JBoss Developer Studio was running, you must refresh
Maven settings in the IDE. From the menu, choose Window Preferences. In the Preferences
Window, expand Maven and choose User Settings. Click the Update Settings button to
refresh the Maven user settings in JBoss Developer Studio.
26
27
Important
If your cached local Maven repository contains outdated artifacts, you may encounter one of the
following Maven errors when you build or deploy your project:
Missing artifact ARTIFACT_NAME
[ERROR] Failed to execute goal on project PROJECT_NAME; Could not resolve dependencies
for PROJECT_NAME
T o resolve the issue, delete the cached local repository the ~/.m 2/repository/ directory on
Linux or the %SystemDrive%\Users\USERNAME\.m 2\repository\ directory on Windows. T his
will force Maven to download correct versions of required artifacts during the next build.
Report a bug
28
Report a bug
29
30
Description
Report a bug
4.3. Javadocs
Javadocs are automatically-generated documentation for Java APIs. T hey are created from the comments
developers add to source code as they write it. Javadocs have become the de facto standard way of
documenting Java APIs.
Report a bug
Procedure 4 .1. Log in and Download Files from the Red Hat Customer Portal
1. Browse to https://access.redhat.com and click the Log in link in the top right corner. Enter your
credentials and click Log In.
31
32
33
3. You are presented with the End User License Agreement. If you agree with the terms, select I
accept the term s of this license agreem ent and then select Next to continue.
4. You are prompted for the location in which you want to install JBoss Fuse Service Works. Specify a
location and select Next. You will be notified that an instance of JBoss EAP will be placed in the
chosen location. Select OK to proceed.
Warning
A warning message is displayed if the directory already exists. Red Hat does not recommend
installing over the top of an existing installation. However, if you wish to proceed, select Yes
to continue.
5. You are prompted for the installation packs to install. Select Next to continue with the default
options.
Note
Depending on your deployment, you can select packs other than the default options. For
example, if you do not wish to install every pack, you could select SwitchYard and Run-T ime
Governance Client only, for a basic installation.
6. You are prompted to create an administrative user. Once created, this user will be added to the
ManagementRealm and can be used to access the Management Console and other applications
secured using ManagementRealm. Enter the new username and password in the appropriate fields
and select Next.
34
Note
If you choose to skip the maven repository setup, you will be asked to confirm this decision.
Select Yes to continue.
9. You are prompted to configure the SAML keystore. It is used by a Java KeyStore to sign
authentication tokens. Enter the SAML keystore password and select Next.
10. You are then prompted to enable the Java Security Manager. It enforces access rules at the JVM
runtime based on one or more security polices. Enable the Java Security Manager and select Next.
11. At this point you are asked to choose between the default or advanced configuration. Select the
default configuration for a basic configuration, and select Next to continue.
12. You are prompted to configure the password vault. Enter the Vault keystore password in the
appropriate fields and select Next.
13. You are presented with a screen specifying default database settings. Change the username and
password to something secure and select Next.
14. You are presented with a list of packages that will be installed. Select Next to proceed.
15. T he installation will commence. A status bar for each component will display its progress. Once this
is complete, select Next.
16. Additional processing of tasks will commence. When the status bar indicates this has been
completed, select Next.
17. T he console displays a message to let you know that the application has been successfully
installed. Also, it offers you a list of URLs for accessing the Administration and BPEL Consoles, SRAMP and DT Gov User Interfaces and Gadget Server.
If you want to repeat the same installation on other machines, select Generate installation
script and properties file and choose a location and filename for the script.
18. Select Done.
Result
T he basic installation is complete.
Note
When running the installer on Windows, you may be asked to provide administrator credentials
during installation.
35
Procedure 5.3.
1. You can change the installation directory by editing the script and modifying the value specified
within the <installpath> element.
36
Note
You can specify either a full directory path or a path relative to the directory in which you run
the script.
Warning
Red Hat does not support installing over an existing instance of Fuse Service Works.
T herefore be sure to select a new or empty directory.
2. Run the script using the following command, replacing 6.0.0.GA-redhat-4 for the version you
downloaded if required:
java -jar jboss-fsw-installer-6.0.0.GA-redhat-4.jar InstallConfigRecord.xml
T he script runs and prompts you to provide Governance, SAML keystore, and Vault keystore
passwords, as shown below:
[ Starting automated installation ]
Read pack list from xml definition.
Try to add to selection [Name: Red Hat JBoss Enterprise Application Platform
and Index: 0]
Try to add to selection [Name: Red Hat JBoss Fuse Service Works and Index: 1]
Try to add to selection [Name: Switchyard quickstarts and Index: 2]
Try to remove from selection [Name: RT-Gov Client-only and Index: 3]
Try to add to selection [Name: RT-Gov Server+Client and Index: 4]
Try to add to selection [Name: RTGov Server quickstarts and Index: 5]
Try to add to selection [Name: DT-Gov run-time and Index: 6]
Try to add to selection [Name: DT-Gov quickstarts and Index: 7]
Try to add to selection [Name: S-RAMP run-time and Index: 8]
Try to add to selection [Name: S-RAMP quickstarts and Index: 9]
Try to add to selection [Name: Red Hat JBoss Fuse Service Works quickstarts and
Index: 10]
Modify pack selection.
Pack [Name: RT-Gov Client-only and Index: 3] removed from selection.
Governance password:
Confirm Governance password:
SAML keystore password:
Re-enter SAML keystore password:
Vault keystore password:
Re-enter vault keystore password:
Report a bug
37
You can also supply them directly on the command line as key/value pairs by using the -variables
option:
java -jar jboss-fsw-installer-6.0.0.GA-redhat-4.jar InstallConfigRecord.xml variables KEY_1=VALUE_1 KEY_2=VALUE_2 ...
Warning
Red Hat recommends you remove plaintext passwords from the .variables file after installation
to avoid compromise.
Report a bug
38
Note
For more information about starting and stopping JBoss Enterprise Application Platform using
alternative and more advanced methods, see the Red Hat JBoss Enterprise Application Platform
Administration and Configuration Guide.
Report a bug
39
40
Note
Each quickstart has different requirements. T hese are documented in their individual readm e.txt
files.
Report a bug
Note
Make sure that you run the following command to verify that Maven is installed successfully on
your machine:m vn --version
Note
Make sure that you select the remote-invoker quickstart and then execute m vn clean
install command.
Result
T he quickstarts compile and are ready for use.
Report a bug
41
Note
You can find additional quickstarts by going to the quickstarts directory.
Report a bug
42
43
Result
T he Remote Invoker quickstart is ready for use.
Report a bug
Result
T he Remote Invoker quickstart is deployed successfully by Maven.
Report a bug
3. On a separate terminal, run the following command to send a request message to the service:
mvn exec:java
Result
T he RemoteInvoker serves as a remote invocation client for SwitchYard services and send messages
successfully.
Report a bug
44
Result
T he Remote Invoker quickstart is undeployed successfully.
Report a bug
45
46
C hapter 8. Validating Your Red Hat JBoss Fuse Service Works Installation
8.2. Validate Your Red Hat JBoss Fuse Service Works Installation
Procedure 8.1. T ask
1. Navigate to the EAP home directory and open the standalone/log/server.log file.
2. Check to see if there is ERROR dialogue in the log. If there is no ERROR text, it means your
installation has been completed successfully. If there is, it means the installation was unsuccessful
and you should try downloading and installing the file again.
Report a bug
Description
EAP
Switchyard
Camel
Riftsaw
Drools Expert
Smooks
47
Description
Modeshape
ActiveMQ
Apache CXF
Report a bug
48
Description
collectionEnabled
ActivityServerLogger.maxT hreads
ActivityServerLogger.durationBetweenFailureRepor
ts
ActivityServerLogger.activityListQueueSize
ActivityServerLogger.freeActivityListQueueSize
49
Description
BatchedActivityUnitLogger.maxUnitCount,
BatchedActivityUnitLogger.maxT imeInterval
infinispan.container
Report a bug
Description
MVELSeverityAnalyzer.scriptLocation
Report a bug
Description
REST ActivityServer.serverURL
REST ActivityServer.serverUsername
REST ActivityServer.serverPassword
Report a bug
9.6. Database
T he installer sets up the datasources for Runtime-T ime Governance, jBPM, SRAMP, BPEL (Riftsaw), and
Gadget Server. T he datasources can be configured in
$JBOSS_HOME/standalone/configuration/standalone.xm l.
Report a bug
9.7. Caching
T he EPN and Active Collection mechanisms both have the ability to make use of caching provided by
Infinispan. When running the Red Hat JBoss Fuse Service Works in clustered mode (that is, with
standalone-full-ha.xm l), it provides a default clustered cache container, which is referenced in the
infinispan.container property in the overlord-rtgov.properties file.
50
Note
T o make sure the individual named caches are clustered correctly, it is necessary to add an entry
for each cache into the standalone-full-ha.xm l file.
For more information on Infinispan configuration, refer JBoss Enterprise Application Platform 6.1
Development Guide.
Report a bug
Report a bug
51
If the configuration file does not exists, you can create the file and modify. T he Design-T ime Governance
will automatically identify this file during the server startup. You can set the location of the configuration file
by accessing the following Java system property:
governance.file.name
Report a bug
You can set the location of the configuration file by accessing the following Java system property:
dtgov-ui.config.file.name
Report a bug
52
Note
T he Design-T ime Governance back-end and the Design-T ime Governance User Interface each
have their own separate configuration. T his is because the back-end and User Interface are
separate applications that can be independently deployed.
Design-T ime Governance Back-End Configuration Properties
# # S-RAMP Connection details
sramp.repo.url
sramp.repo.auth.provider
sramp.repo.user
sramp.repo.password
sramp.repo.validating
sramp.repo.auth.saml.issuer
sramp.repo.auth.saml.service
# Location of the DTGov WAR
governance.url
# Frequency with which to poll S-RAMP for query matches
governance.query.interval
# Location in JNDI of the email service
governance.jndi.email.reference
# "From" information to use when sending email (domain and address)
governance.email.domain
governance.email.from
# RHQ connection info
rhq.rest.user
rhq.rest.password
rhq.base.url
# BPM connection info
governance.bpm.user
governance.bpm.password
governance.bpm.url
# JAAS user used to invoke DTGov provided services
governance.user
governance.password
# Deployment targets configured for the DTGov deployment service
governance.targets
# Mapping of S-RAMP query to governance workflow
governance.queries
# Location of the DTGov UI
dtgov.ui.url
# S-RAMP
s-ramp-wagon
dtgov.s-ramp-wagon.snapshots
dtgov.s-ramp-wagon.releases
# DTGov Workflow maven info
dtgov.workflows.group
dtgov.workflows.name
dtgov.workflows.version
dtgov.workflows.package
53
54
T he above configuration uses BASIC authentication when connecting to the S-RAMP repository. It
connects to S-RAMP on localhost (port 8080).
User Interface Configuration Example
Here is an example of the User Interface configuration:
dtgov-ui.s-ramp.atom-api.endpoint=http://localhost:8080/s-ramp-server
dtgov-ui.s-ramp.atomapi.authentication.provider=org.overlord.dtgov.ui.server.services.sramp.SAMLBearerTok
enAuthenticationProvider
dtgov-ui.s-ramp.atom-api.authentication.saml.issuer=/dtgov-ui
dtgov-ui.s-ramp.atom-api.authentication.saml.service=/s-ramp-server
dtgov-ui.s-ramp.atom-api.validating=true
T he above configuration connects to S-RAMP on localhost (port 8080) and uses SAML bearer token
authentication.
Report a bug
55
2. Ensure that the server is up and running, and deploy the "SimpleReleaseProcess" sample workflow
to the server by running the following command:
mvn -s local-settings.xml deploy
Report a bug
56
Note
HT T P communication with JBoss EAP 6 is considered to be remote access, even if the traffic
originates on the localhost. T herefore, you must create at least one user in order to be able to use
the management console. If you attempt to access the management console before adding a user,
you will receive an error because it does not even deploy until the user is added.
Procedure 11.1. Create the Initial Administrative User for the Remote Management Interfaces
1. Invoke the add-user.sh or add-user.bat script.
Change to the EAP_HOME/bin/ directory. Invoke the appropriate script for your operating system.
Red Hat Enterprise Linux
[user@host bin]$ ./add-user.sh
57
8. You can suppress the normal output of the add-user script by passing the --silent parameter.
T his applies only if the minimum parameters if usernam e and password have been specified.
Error messages will still be shown.
Result
Any users you add are activated within the security realms you have specified. Users active within the
Managem entRealm realm are able to manage JBoss EAP 6 from remote systems.
Report a bug
Argument Value
Description
-a
N/A
-dc
DOMAIN_CONFIGURATION_DI
RECTORY
58
Argument Value
Description
-sc
SERVER_CONFIGURATION_DI
RECTORY
-up
USER_PROPERTIES_FILE
GROUP_LIST
GROUP_PROPERTIES_FILE
PASSWORD
--userproperties
-g
--group
-gp
--groupproperties
-p
--password
USER_NAME
REALM_NAME
N/A
N/A
--user
-r
--realm
-s
--silent
-h
--help
Report a bug
59
Note
T he add-user command is intended to operate on existing properties files. Any alternate
properties files specified in command line arguments must exist or you will see the following error:
JBAS015234: No appusers.properties files found
Report a bug
60
C hapter 12. Configuring Red Hat JBoss Fuse Service Works to Run as a Background Service
61
If everything has gone correctly, you should get a green [OK]. If you get an error, check the error
logs and make sure your paths are correct in the configuration file.
6. Make the service start automatically when you restart your server.
T o add the service to the list of services which start automatically when your server restarts, issue
the following command.
[user@host init.d]$ sudo chkconfig jboss-as-standalone.sh on
Result
JBoss FSW starts automatically when the Red Hat Enterprise Linux reaches its default run-level, and
stops automatically when the operating system goes through its shutdown routine.
Report a bug
62
C hapter 13. Configuring Red Hat JBoss Fuse Service Works to Run in a Clustered Environment
Note
T he SwitchYard registry is a runtime registry and not a publication registry. T he state of services
within the registry is tied directly to the current state of services deployed within a cluster.
Report a bug
63
When the instances are up, you can deploy applications independently to each instance. A homogeneous
cluster(a cluster of identical machines) consists of identical applications deployed on each node. However,
a heterogeneous cluster consists of different applications and services deployed on each instance. T o
verify the cluster setup, deploy a consumer application to one instance and a provider application to
another.
Report a bug
Note
By default, SwitchYard uses the default cache in the cluster cache container which comes predefined in the standalone-ha.xm l file.
You can control the services in the application that can be published in the cluster's runtime registry and
the references that can be resolved by clustered services.
T o enable a service to be published in the cluster's runtime registry, promote the service in the application
and add a <binding.sca> with clustering enabled to it.
<sca:service name="Goodbye" promote="GoodbyeBean/Goodbye">
<sca:interface.java interface="com.example.Goodbye"/>
<sca:binding.sca sy:clustered="true"/>
</sca:service>
T o invoke a service in a cluster, promote the reference and add an SCA binding with clustering enabled.
<sca:reference name="Goodbye" multiplicity="0..1" promote="GreetingBean/Goodbye">
<sca:interface.java interface="com.example.Goodbye"/>
<sca:binding.sca sy:clustered="true"
</sca:reference>
Report a bug
64
C hapter 13. Configuring Red Hat JBoss Fuse Service Works to Run in a Clustered Environment
When you start the server using the HA profile, run-time governance is automatically clustered based on
the clustered infinispan, hornetq, and a shared database. S-RAMP only requires a shared database.
T here is no dependency between run-time governance and S-RAMP as they are installed and configured
independently.
In a clustered environment, it is recommended to have a dedicated run-time governance server, separate
from the execution servers that hosts the run-time governance server. In this case, all servers connect to
this server via the run-time governance client. Depending upon the load of the run-time governance server,
it may also be necessary to set up a cluster of governance servers as well. If you have a cluster of runtime governance servers, then they only need to connect to the same database instance. However, it is
possible to also configure each run-time governance server to have its own SRAMP database. T he FSW
installer configures all components to use the same database by default. So run-time governance and SRAMP share the same database instance, however this is not mandatory.
Report a bug
65
T his command first downloads jBPM, REST Easy and ModeShape from sourceforge. T he downloads
are stored in the jbpm5 directory. In the same directory, it creates a jbpm-installer directory with jBPM
and a sub-directory containing the application server jboss-as-7.1.1.Final. T he application
server saves ModeShape and REST Easy as modules.
3. Configure S-RAMP
Run the following command:
ant configure
T his command adds some S-RAMP specific services to jBPM. It deploys the s-ram pserver.war, the s-ram p-ui.war and the governance.war. It then points jBPM to obtain its
workflow data from the S-RAMP repository, rather than BRMS or Drools-Guvnor. At this point, you
need to populate the S-RAMP repository with some initial data. T o achieve this, the repository needs
to be up and running.
a. Start the JBoss application server by running the following command:
ant start
b. If your system supports the tail command, you can run the following command:
ant tail
T his monitors the startup process. It is ready as soon as you see the following in the
application server console output:
[exec] 12:00:13,905 INFO [org.jboss.as.server] (DeploymentScanner-threads
- 2) JBAS018559: Deployed "s-ramp-ui.war"
[exec] 12:00:13,910 INFO [org.jboss.as.server] (DeploymentScanner-threads
66
"s-ramp-server.war"
[org.jboss.as.server] (DeploymentScanner-threads
"s-ramp-governance.war"
[org.jboss.as.server] (DeploymentScanner-threads
"jbpm-human-task-war.war"
[org.jboss.as.server] (DeploymentScanner-threads
"jbpm-gwt-console.war"
[org.jboss.as.server] (DeploymentScanner-threads
"jbpm-gwt-console-server.war"
[org.jboss.as.server] (DeploymentScanner-threads
"jbpm-form-builder.war"
[org.jboss.as.server] (DeploymentScanner-threads
"drools-guvnor.war"
[org.jboss.as.server] (DeploymentScanner-threads
"designer.war"
*******************************************************************
***
_____
______ ___ ___ ________
/ ___|
| ___ \/ _ \| \/ | ___ \
\ `--. ______| |_/ / /_\ \ . . | |_/ /
`--. \______|
/| _ | |\/| | __/
/\__/ /
| |\ \| | | | | | | |
\____/
\_| \_\_| |_|_| |_|_|
JBoss S-RAMP Kurt Stam and Eric Wittmann, Licensed under the
Apache License, V2.0, Copyright 2012
*******************************************************************
***
s-ramp>
67
When you press the return key, the cursor goes from red to green.
b. Browse the artifacts in the repository by runninf the following query:
s-ramp> s-ramp:query /s-ramp
Report a bug
68
69
Warning
If you expose the management interfaces to other network interfaces which are accessible from
remote hosts, be aware of the security implications. Most of the time, it is not advisable to provide
remote access to the management interfaces.
Report a bug
70
C hapter 15. Starting Red Hat JBoss Fuse Service Works in an Enterprise Environment
Example 15.4 . Bind the public interface to all network interfaces.
EAP_HOME/bin/domain.sh -b 0.0.0.0
It is possible to edit your XML configuration file directly, to change the default bind addresses. However, if
you do this, you will no longer be able to use the -bcommand-line switch to specify an IP address at runtime, so this is not recommended. If you do decide to do this, be sure to stop JBoss EAP 6 completely
before editing the XML file.
Report a bug
71
Security Considerations
A.1. Secure Ways of Running Red Hat JBoss Fuse Service Works
Enabling the Java Security Manager (JSM) to sandbox the evaluation of MVEL may introduce a
performance hit in high load environments. Following are some secure ways of running Red Hat JBoss
Fuse Service Works:
If you run Red Hat JBoss Fuse Service Works without Run-T ime Governance, you can disable JSM as
it does not introduce MVEL security risks.
If you need Run-T ime Governance in high performance environment, Red Hat recommends running
Run-T ime Governance in a separate JVM. T he JVM instance running Run-T ime Governance must
have JSM enabled, whereas other application server instances can run without JSM.
If you are working on testing and development environments without high loads, it is okay to run one
JVM with the server, Run-T ime Governance, and JSM enabled as the performance hit is not dramatic.
Warning
Red Hat does not recommend running the server with Run-T ime Governance enabled and JSM
disabled in one JVM instance, as this is not secure.
Report a bug
72
Revision History
Revision History
Revision 6.0.0-4 5
Mon Jul 14 2014
B Long
Built from Content Specification: 22586, Revision: 684216 by belong
73