Red Hat 6.3 JBoss Enterprise Application Platform Installation Guide
Below you will find brief information for JBoss Enterprise Application Platform 6.3. JBoss Enterprise Application Platform 6.3 is a middleware platform built on open standards and compliant with the Java Enterprise Edition 6 specification. It integrates JBoss Application Server 7 with high-availability clustering, messaging, distributed caching, and other technologies. This platform includes a new, modular structure that allows service enabling only when required, improving start-up speed. The Management Console and Management Command Line Interface make editing XML configuration files unnecessary and add the ability to script and automate tasks.
advertisement
JBoss Enterprise Application
Platform 6.3
Installation Guide
For use with Red Hat JBoss Enterprise Application Platform 6
Red Hat Customer Content Services
JBoss Enterprise Application Platform 6.3 Installation Guide
For use with Red Hat JBoss Enterprise Application Platform 6
Legal Notice
Co pyright © 20 14 Red Hat, Inc..
This do cument is licensed by Red Hat under the
Creative Co mmo ns Attributio n-ShareAlike 3.0
Unpo rted License
. If yo u distribute this do cument, o r a mo dified versio n o f it, yo u must pro vide attributio n to Red Hat, Inc. and pro vide a link to the o riginal. If the do cument is mo dified, all Red
Hat trademarks must be remo ved.
Red Hat, as the licenso r o f this do cument, waives the right to enfo rce, and agrees no t to assert,
Sectio n 4 d o f CC-BY-SA to the fullest extent permitted by applicable law.
Red Hat, Red Hat Enterprise Linux, the Shado wman lo go , JBo ss, MetaMatrix, Fedo ra, the Infinity
Lo go , and RHCE are trademarks o f Red Hat, Inc., registered in the United States and o ther co untries.
Linux ® is the registered trademark o f Linus To rvalds in the United States and o ther co untries.
Java ® is a registered trademark o f Oracle and/o r its affiliates.
XFS ® is a trademark o f Silico n Graphics Internatio nal Co rp. o r its subsidiaries in the United
States and/o r o ther co untries.
MySQL ® is a registered trademark o f MySQL AB in the United States, the Euro pean Unio n and o ther co untries.
No de.js ® is an o fficial trademark o f Jo yent. Red Hat So ftware Co llectio ns is no t fo rmally related to o r endo rsed by the o fficial Jo yent No de.js o pen so urce o r co mmercial pro ject.
The OpenStack ® Wo rd Mark and OpenStack Lo go are either registered trademarks/service marks o r trademarks/service marks o f the OpenStack Fo undatio n, in the United States and o ther co untries and are used with the OpenStack Fo undatio n's permissio n. We are no t affiliated with, endo rsed o r spo nso red by the OpenStack Fo undatio n, o r the OpenStack co mmunity.
All o ther trademarks are the pro perty o f their respective o wners.
Abstract
This bo o k is a guide to the installatio n o f Red Hat JBo ss Enterprise Applicatio n Platfo rm 6 and its patch releases.
T able of Cont ent s
1.1. Typ o g rap hic Co nventio ns
1.2. Pull-q uo te Co nventio ns
2. G etting Help and G iving Feed b ack
Table of Contents
1.1. Ab o ut Red Hat JBo ss Enterp rise Ap p licatio n Platfo rm 6
1.2. Features o f JBo ss EAP 6
2.1. Ab o ut the Red Hat Custo mer Po rtal
3.1. JBo ss EAP 6 Installatio n Prereq uisites
10
4.1. JBo ss EAP 6 Installatio n Metho d s
4.2.1. Do wnlo ad JBo ss EAP 6 (Zip Installatio n)
4.2.2. Install JBo ss EAP 6 (ZIP Installatio n)
4.2.3. Uninstall JBo ss EAP 6 (Zip Installatio n)
4.3.1. Do wnlo ad JBo ss EAP 6 (Installer)
4.3.2. Run the JBo ss EAP Installatio n Pro g ram
4.3.3. Uninstall JBo ss EAP 6 (Installer)
11
11
11
12
13
13
13
14
17
4.4. G rap hical RPM Installatio n
4.4.1. Install JBo ss EAP 6 (G rap hical RPM Installatio n)
4.5. Text-b ased RPM Installatio n
4.5.1. Install JBo ss EAP 6 (Text-b ased RPM Installatio n)
4.6 . Auto mated Installatio n
18
18
19
19
20
4.6 .1. Install Multip le Instances o f JBo ss EAP 6 (Installer)
20
4.7. Auto mated Installatio n Ap p ro aches
4.7.1. Ab o ut Auto mated Installatio n Ap p ro aches
21
21
4.8 . Installing Native Co mp o nents and Utilities
4.8 .1. Install Native Co mp o nents and Native Utilities (Zip , Installer)
4.8 .2. Install Native Co mp o nents and Native Utilities (RPM Installatio n)
4.9 . Service Co nfig uratio n
4.9 .1. Co nfig ure JBo ss EAP 6 as a Service in Red Hat Enterp rise Linux (RPM Metho d )
4.9 .2. Co nfig ure JBo ss EAP 6 as a Service in Red Hat Enterp rise Linux (Zip , Installer)
4.9 .3. Co nfig ure JBo ss EAP 6 as a Service in Micro so ft Wind o ws Server (Zip , Installer)
22
22
23
23
24
25
25
26
29
5.1. Ab o ut Patches and Up g rad es
5.2. Patching JBo ss EAP 6
32
32
1
5
6
5
5
3
3
4
7
7
9
JBoss Ent erprise Applicat ion Plat form 6 .3 Inst allat ion G uide
5.2.1. Ab o ut Patching Mechanisms
5.2.2. Patching a Zip /Installer Installatio n
5.2.2.1. The Patch Manag ement System
5.2.2.2. Installing Patches in Zip Fo rm Using the Patch Manag ement System
5.2.2.3. Ro llb ack the Ap p licatio n o f a Patch in Zip Fo rm Using the Patch Manag ement System
32
32
33
33
34
5.2.3. Patching an RPM Installatio n
5.2.4. Sub scrib e to Patch Mailing Lists
5.2.5. Severity and Imp act Rating o f JBo ss Security Patches
5.3. Up g rad ing JBo ss EAP 6
5.3.1. Up g rad e the JBo ss EAP 6 ZIP Installatio n
5.3.2. Up g rad e the JBo ss EAP 6 RPM Installatio n
5.3.3. Up g rad e JBo ss EAP Cluster fro m 6 .2 to 6 .3
36
38
39
40
41
41
42
43
A.1. Availab le Do wnlo ad s fo r JBo ss EAP 6
A.2. Directo ry Structure o f JBo ss EAP 6
A.3. RPM Packag e List fo r JBo ss EAP 6
A.4. RPM Installatio n Co nfig uratio n Files fo r JBo ss EAP 6
45
46
48
49
B.2. End User License Ag reement
B.4. Select the Packs to Install
B.5. Ad ministrative User Creatio n
B.6 . Q uickstart Installatio n
B.7. Maven Rep o sito ry Setup
B.9 . Custo m So cket Bind ing s fo r Stand alo ne Co nfig uratio ns
B.10 . Custo m So cket Bind ing s fo r Do main Co nfig uratio ns
B.12. Co nfig ure Lo g g ing Levels
B.13. Co nfig ure Runtime Enviro nment
B.14. Passwo rd Vault Co nfig uratio n
B.15. Co nfig ure SSL Security
B.17. Infinisp an Co nfig uratio n
B.18 . Security Do main Co nfig uratio n
B.21. Review Installatio n Co mp o nents
B.22. Installatio n Pro g ress
B.23. Installatio n Pro cessing Finished
B.25. G enerate Install Scrip t
70
71
73
74
75
56
57
6 0
6 4
6 9
53
54
55
51
51
52
8 2
8 3
8 4
8 5
76
77
79
8 0
8 1
2
Preface
Preface
1. Document Convent ions
This manual uses several conventions to highlight certain words and phrases and draw attention to specific pieces of information.
1.1. T ypographic Convent ions
Four typographic conventions are used to call attention to specific words and phrases. These conventions, and the circumstances they apply to, are as follows.
Mo no -spaced Bo l d
Used to highlight system input, including shell commands, file names and paths. Also used to highlight keys and key combinations. For example:
To see the contents of the file my_next_bestsel l i ng _no vel in your current working directory, enter the cat my_next_bestsel l i ng _no vel command at the shell prompt and press Enter to execute the command.
The above includes a file name, a shell command and a key, all presented in mono-spaced bold and all distinguishable thanks to context.
Key combinations can be distinguished from an individual key by the plus sign that connects each part of a key combination. For example:
Press Enter to execute the command.
Press C trl +Al t+F2 to switch to a virtual terminal.
The first example highlights a particular key to press. The second example highlights a key combination: a set of three keys pressed simultaneously.
If source code is discussed, class names, methods, functions, variable names and returned values mentioned within a paragraph will be presented as above, in mo no -spaced bo l d . For example:
File-related classes include fi l esystem for file systems, fi l e for files, and d i r for directories. Each class has its own associated set of permissions.
Pro p o rt io n al Bo ld
This denotes words or phrases encountered on a system, including application names; dialog-box text; labeled buttons; check-box and radio-button labels; menu titles and submenu titles. For example:
Choose Syst em → Pref eren ces → Mo u se from the main menu bar to launch
Mo u se Pref eren ces. In the Butto ns tab, select the Left-hand ed mo use check box and click C l o se to switch the primary mouse button from the left to the right
(making the mouse suitable for use in the left hand).
To insert a special character into a g ed it file, choose Ap p licat io n s →
Accesso ries → Ch aract er Map from the main menu bar. Next, choose Search →
Fin d … from the Ch aract er Map menu bar, type the name of the character in the
Search field and click Next. The character you sought will be highlighted in the
3
JBoss Ent erprise Applicat ion Plat form 6 .3 Inst allat ion G uide
C haracter T abl e. Double-click this highlighted character to place it in the T ext
to co py field and then click the C o py button. Now switch back to your document and choose Ed it → Past e from the g ed it menu bar.
The 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:
To connect to a remote machine using ssh, type ssh username@ domain.name at a shell prompt. If the remote machine is exampl e. co m and your username on that machine is john, type ssh jo hn@ exampl e. co m.
The mo unt -o remo unt file-system command remounts the named file system.
For example, to remount the /ho me file system, the command is mo unt -o remo unt
/ho me.
To 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.
1.2. Pull-quot e Convent ions
Terminal output and source code listings are set off visually from the surrounding text.
Output sent to a terminal is set in mo no -spaced ro man and presented thus: books Desktop documentation drafts mss photos stuff svn books_tests Desktop1 downloads images notes scripts svgs
Source-code listings are also set in mo no -spaced ro man 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,
assigned_dev->assigned_dev_id);
if (!match) {
printk(KERN_INFO
"%s: device hasn't been assigned
4
Preface
before, "
"so cannot be deassigned \n " , __func__);
r = -EINVAL;
goto out;
}
kvm_deassign_device(kvm, match);
kvm_free_assigned_device(kvm, match);
out:
mutex_unlock(& kvm->lock);
return r;
}
1.3. Not es and Warnings
Finally, we use three visual styles to draw attention to information that might otherwise be overlooked.
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.
2. Get t ing Help and Giving Feedback
2.1. Do You Need Help?
If you experience difficulty with a procedure described in this documentation, visit the Red Hat
Customer Portal at http://access.redhat.com
. Through the customer portal, you can: search or browse through a knowledgebase of technical support articles about Red Hat products.
submit a support case to Red Hat Global Support Services (GSS).
access other product documentation.
5
JBoss Ent erprise Applicat ion Plat form 6 .3 Inst allat ion G uide
Red Hat also hosts a large number of electronic mailing lists for discussion of Red Hat software and technology. You can find a list of publicly available mailing lists at https://www.redhat.com/mailman/listinfo . Click on the name of any mailing list to subscribe to that list or to access the list archives.
2.2. We Need Feedback!
If you find a typographical error in this manual, or if you have thought of a way to make this manual better, we would love to hear from you! Please submit a report in Bugzilla: http://bugzilla.redhat.com/ against the product JBo ss En t erp rise Ap p licat io n Plat f o rm.
When submitting a bug report, be sure to mention the manual's identifier: Installation_Guide
If you have a suggestion for improving the documentation, try to be as specific as possible when describing it. If you have found an error, please include the section number and some of the surrounding text so we can find it easily.
6
Chapt er 1 . Product O verview
Chapter 1. Product Overview
1.1. About Red Hat JBoss Ent erprise Applicat ion Plat form 6
Red Hat JBoss Enterprise Application Platform 6 (JBoss EAP 6) is a middleware platform built on open standards and compliant with the Java Enterprise Edition 6 specification. It integrates JBoss
Application Server 7 with high-availability clustering, messaging, distributed caching, and other technologies.
JBoss EAP 6 includes a new, modular structure that allows service enabling only when required, improving start-up speed.
The Management Console and Management Command Line Interface make editing XML configuration files unnecessary and add the ability to script and automate tasks.
In addition, JBoss EAP 6 includes APIs and development frameworks for quickly developing secure and scalable Java EE applications.
Report a bug
1.2. Feat ures of JBoss EAP 6
T ab le 1.1. JBo ss EAP 6 .3.0 Feat u res
Feat u re
Java Certification
Managed Domain
Management Console and Management CLI
Simplified directory layout
Descrip t io n
Java Enterprise Edition 6 Full Profile and Web
Profile certified.
Centralized management of multiple server instances and physical hosts, while a standalone server allows for a single server instance.
Per-server group management of configuration, deployment, socket bindings, modules, extensions and system properties.
Centralized and simplified management of application security (including security domains).
New domain or standalone server management interfaces. XML configuration file editing is no longer required. The Management CLI also includes a batch mode that can script and automate management tasks.
The mo d ul es directory now contains all application server modules. The common and server-specific l i b directories are deprecated.
The d o mai n and stand al o ne directories contain the artifacts and configuration files for domain and standalone deployments respectively.
7
JBoss Ent erprise Applicat ion Plat form 6 .3 Inst allat ion G uide
Feat u re
Modular classloading mechanism
Streamlined Data source management
Reduced and more efficient resource use.
Descrip t io n
Modules are loaded and unloaded on demand.
This improves performance, has security benefits and reduces start-up and restart times.
Database drivers are deployed just like other services. In addition, datasources are created and managed directly in the Management
Console or Management CLI.
JBoss EAP 6 uses fewer system resources and uses them more efficiently than previous versions. Among other benefits, JBoss EAP 6 starts and stops faster than JBoss EAP 5.
Report a bug
8
Chapt er 2 . Int roduct ion
Chapter 2. Introduction
2.1. About t he Red Hat Cust omer Port al
The Red Hat Customer Portal is the centralized platform for Red Hat knowledge and subscription resources. Use the Red Hat Customer Portal to do the following:
Manage and maintain Red Hat entitlements and support contracts.
Download officially-supported software.
Access product documentation and the Red Hat Knowledgebase.
Contact Global Support Services.
File bugs against Red Hat products.
The Customer Portal is available here: https://access.redhat.com
.
Report a bug
9
JBoss Ent erprise Applicat ion Plat form 6 .3 Inst allat ion G uide
Chapter 3. System Requirements
3.1. JBoss EAP 6 Inst allat ion Prerequisit es
Each installation process for JBoss EAP 6 has a number of prerequisites. This section covers the common requirements, as well as those that are installation specific.
Co mmo n Prereq u isit es
Set up an account on the Red Hat Customer Portal at https://access.redhat.com
. For more information, refer here:
Section 2.1, “ About the Red Hat Customer Portal”
.
Review the supported configurations and ensure your system is supportable: https://access.redhat.com/site/articles/111663 .
Ensure that your system is up to date with Red Hat issued updates and errata.
Z IP/In st aller Prereq u isit es
Administration privileges for the installation directory.
Ensure that the chosen JDK has been extracted (or installed). Refer to the JDK's documentation for information on how to do this.
On Microsoft Windows Server, ensure that the JAVA_HOME and PATH environment variables have been set, otherwise shortcuts will not work.
On Hewlett-Packard HP-UX, ensure that an unzi p utility has been installed.
RPM Prereq u isit es
Register the server on the Red Hat Network.
Subscribe to the R ed Hat Enterpri se Li nux Server base software channel appropriate to your Red Hat Enterprise Linux version.
Subscribe to the JBo ss Appl i cati o n P l atfo rm fo r Server sub-channel, in the JBo ss
Enterpri se P l atfo rm group.
On Red Hat Enterprise Linux 5, JDK 6 must be installed, even if JDK 7 only is to be used. On Red
Hat Enterprise Linux 6 and higher, only a JDK 7 is required. This can be obtained by subscribing to the suppl ementary software channel for your Red Hat Enterprise Linux installation. For example; the channel for Red Hat Enterprise Linux version 6 installed on i386 architecture is
rhel -i 386 -server-suppl ementary-6 .
p p c6 4 Prereq u isit es
On Red Hat Enterprise Linux 6, subscribe to the rhel -ppc6 4 -server-o pti o nal -6 channel.
On Red Hat Enterprise Linux 7, subscribe to the rhel -7-server-o pti o nal -rpms-7Server repository.
Report a bug
10
Chapt er 4 . Inst all Inst ruct ions
Chapter 4. Install Instructions
4 .1. JBoss EAP 6 Inst allat ion Met hods
There are several different ways to install JBoss EAP 6. Each method is best used in certain situations. This topic provides a brief overview for each type of installation, and links to the sections that cover the relevant installation processes.
T ab le 4 .1. In st allat io n Met h o d s
Met h o d
Z ip Installation
JAR Installer
RPM Installation
Descrip t io n
The Z ip archive is suitable for installation on all supported operating systems. This process should be used if you wish to extract the instance manually.
The JAR installer can be run in a console, or as a graphical wizard. Both options provide step-by-step instructions for installing and configuring the server instance. Additional setup, including the Quickstarts and Maven Repository, is also possible with the installer. This is the preferred way to install
JBoss EAP 6 on all supported platforms.
JBoss EAP 6 can be installed with the supported RPM package graphical installer, or with a command-line interface.
This method is suitable for supported installations of Red
Hat Enterprise Linux 5 and 6.
In st ru ct io n s
Section 4.2.2, “ Install JBoss
Section 4.4.1, “ Install JBoss
Section 4.5.1, “ Install JBoss
Report a bug
4 .2. Zip Inst allat ion
4 .2.1. Download JBoss EAP 6 (Zip Inst allat ion)
Prereq u isit es:
Section 3.1, “ JBoss EAP 6 Installation Prerequisites”
Su mmary
The JBoss EAP 6 Z IP file is available from the Red Hat Customer Portal. The Z IP file installation is platform-independent. This topic covers the steps to download the archive.
11
JBoss Ent erprise Applicat ion Plat form 6 .3 Inst allat ion G uide
Pro ced u re 4 .1. Do wn lo ad t h e Z IP f ile
1. Open a browser and log into the Customer Portal at https://access.redhat.com
.
2. Click Do wn lo ad s.
3. Click R ed Hat JBo ss Enterpri se Appl i cati o n P l atfo rm in the P ro d uct
D o wnl o ad s list.
4. Select the correct JBoss EAP version from the Versi o n drop-down menu.
5. Find R ed Hat JBo ss Enterpri se Appl i cati o n P l atfo rm 6 . x.x in the list and click the D o wnl o ad option.
Resu lt
JBoss EAP 6 is now downloaded to your target machine, ready for installation.
Next St ep in Z ip In st allat io n
Section 4.2.2, “ Install JBoss EAP 6 (Z IP Installation)”
Report a bug
4 .2.2. Inst all JBoss EAP 6 (ZIP Inst allat ion)
Previo u s St ep in
Section 4.2.1, “ Download JBoss EAP 6 (Z ip Installation)”
Su mmary
This topic covers the steps to install JBoss EAP 6 using the downloaded Z IP file.
Pro ced u re 4 .2. Z IP File In st allat io n
1. Mo ve t h e Z IP arch ive t o t h e d esired lo cat io n .
Move the Z IP file to the server and directory where you plan to install JBoss EAP 6. The user who will start and stop the server must have read and write access to this directory.
2. Use an ap p ro p riat e ap p licat io n t o ext ract t h e Z IP arch ive t o t h e d esired lo cat io n .
In a Red Hat Enterprise Linux environment, use the unzi p utility to extract the contents of the
Z IP archive.
In a Microsoft Windows environment, right-click the file and select Extract Al l .
In a Hewlett-Packard HP-UX environment, use the unzi p utility to extract the contents of the
Z IP archive.
Resu lt
JBoss EAP 6 has been installed successfully. The directory created by extracting the Z IP archive is the top-level directory for the server. This is referred to as EAP_HOME.
Next St ep in Z ip In st allat io n
12
Chapt er 4 . Inst all Inst ruct ions
Section 4.2.3, “ Uninstall JBoss EAP 6 (Z ip Installation)”
Report a bug
4 .2.3. Uninst all JBoss EAP 6 (Zip Inst allat ion)
Previo u s St ep in
Section 4.2.2, “ Install JBoss EAP 6 (Z IP Installation)”
Prereq u isit es
Backup any modified configuration files and deployments that may be reused in a later instance.
Su mmary
This section covers the steps required to uninstall a Z ip installation of JBoss EAP 6.
Pro ced u re 4 .3. Un in st all JBo ss EAP 6 ( Z ip in st allat io n )
1. Go to the directory where you had extracted the JBoss EAP 6 folder from the Z ip file.
2. Delet e t h e in st allat io n d irect o ry.
JBoss EAP 6 installs in a single directory when you use the Z ip installation method. Delete the installation directory to uninstall JBoss EAP 6.
3. O p t io n al: Delet e an y in it ializ at io n scrip t s yo u creat ed .
If you created initialization scripts or other scripts which depended upon JBoss EAP 6 being installed on your computer, delete them.
Resu lt
JBoss EAP 6 is uninstalled from the server.
Report a bug
4 .3. Inst aller
4 .3.1. Download JBoss EAP 6 (Inst aller)
Prereq u isit es:
Section 3.1, “ JBoss EAP 6 Installation Prerequisites”
Su mmary
The JBoss EAP 6 installer archive is available from the Red Hat Customer Portal. The . jar archive can be used to run either the graphical or text-based installers. The installer is the preferred way to install JBoss EAP 6 on all supported platforms. This topic covers the steps to download the archive.
Pro ced u re 4 .4 . Do wn lo ad t h e In st aller
1. Open a browser and log into the Customer Portal at https://access.redhat.com
.
13
JBoss Ent erprise Applicat ion Plat form 6 .3 Inst allat ion G uide
2. Click Do wn lo ad s.
3. Click R ed Hat JBo ss Enterpri se Appl i cati o n P l atfo rm in the P ro d uct
D o wnl o ad s list.
4. Select the correct JBoss EAP version from the Versi o n drop-down menu.
5. Find R ed Hat JBo ss Enterpri se Appl i cati o n P l atfo rm 6 . x.x Instal l er in the list and click the D o wnl o ad option.
Resu lt
JBoss EAP 6 is now downloaded to your target machine, ready for installation.
Section 4.3.3, “ Uninstall JBoss EAP 6 (Installer)”
Report a bug
4 .3.2. Run t he JBoss EAP Inst allat ion Program
The JBoss EAP installation program can be run in either graphical or text mode. This topic covers the command to run the installation program in graphical mode.
Pro ced u re 4 .5. Ru n t h e JBo ss EAP In st allat io n Pro g ram
1. Open a terminal and navigate to the directory containing the downloaded installation program JAR.
2. Type the following command: java -jar jboss-eap-6.3.0-installer.jar
3. Follow the instructions in the table below.
T ab le 4 .2. JBo ss EAP In st allat io n Pro g ram Screen s
Screen n ame
Wh en it Ap p ears
Always
Always
Always
Always
Descrip t io n
Choose the desired language for the installation program and click O K.
The EULA for RED HAT JBOSS MIDDLEWARE.
Select "I accept the terms of this license agreement", and click Next.
Select the installation path for JBoss EAP and click Next. You are prompted to create the new directory, or, if it exists, to replace the named directory.
Select the packs to install. Required packs are disabled for deselection.
14
Chapt er 4 . Inst all Inst ruct ions
Screen n ame
Wh en it Ap p ears
Always
Always
If you choose to install the quickstart examples
Always
If you choose to configure the custom port bindings for standalone mode
If you choose to configure the custom port bindings for domain mode.
Always
Always
Descrip t io n
Create an administrative user and assign a password. The password must be at least eight characters long, with one alphabetic character, one digit, and one non-alphanumeric character.
Then click Next.
Install the quickstart examples. If you would like to install them, choose Y es and select the installation path. If you do not wish to install them, choose No . Then click Next.
A publicly hosted Maven repository is available for use with the quickstarts. The default selections automatically configure your installation to use this repository. This is the easiest way to run the quickstarts. If you prefer, specify the path to a locally installed repository,
Specify a path if your Maven settings file is not in the default location.
Determine whether the installation will use the default port bindings, configure custom port bindings, or configure port offsets for all default bindings. If you select custom bindings, select whether to configure the ports for standalone mode, domain mode, or both. If you choose to configure port offsets, choose the offset. Then click Next.
Configure the ports and system properties for the various standalone modes, then click Next.
Configure the ports and system properties for the various domain modes, then click Next.
Select the startup option required on completion of the installation process. Then click Next.
Choose Y es to configure log levels, or No to skip this configuration. Then click Next.
Always
If you choose to install password vault in advanced configuration of runtime environment
Choose P erfo rm d efaul t co nfi g urati o n to install the default configuration. Choose
P erfo rm ad vanced co nfi g urati o n to choose from a list of advanced configuration options. Advanced options can also be configured after installation. Then click Next.
Configure a password vault to store all your sensitive passwords in an encrypted keystore and click Next. For more information see:
Administration and Configuration Guide, "Mask the Keystore Password and Initialize the
Password Vault"
15
JBoss Ent erprise Applicat ion Plat form 6 .3 Inst allat ion G uide
Screen n ame
Wh en it Ap p ears
If you choose to enable SSL security in advanced configuration of runtime environment
Descrip t io n
Configure an SSL keystore for securing EAP management interfaces. Then click Next. For more information see: Security Guide, "Generate a SSL Encryption Key and Certificate"
Warning
Red Hat recommends that you explicitly disable SSL in favor of TLSv1.1 or
TLSv1.2 in all affected packages.
If you choose to enable LDAP
Configuration in advanced configuration of runtime environment
If you choose to install
Infinispan cache in advanced configuration of runtime environment
If you choose to add a security domain in advanced configuration of runtime environment
If you choose to install a JDBC driver in advanced configuration of runtime environment
If you choose to install a datasource in advanced configuration of runtime environment
Enable LDAP authentication to use an LDAP directory server as the authentication source for the Management Console, Management CLI or
Management API. When you are done click
Next. For more information see: Administration and Configuration Guide, "Use LDAP to
Authenticate to the Management Interfaces"
Create an Infinispan cache for managing cached data. Give an Infinispan name, configure the other fields and click Next. For more information see: Administration and
Configuration Guide, "Chapter 14 Infinispan"
Configure a security domain to incorporate the services provided by PicketBox to a JBoss EAP server instance. Most of the fields are already populated with default values and do not need modifications. When you are done click Next.
For more information see: Administration and
Configuration Guide, "Security Domains"
Install and setup a JDBC driver to convert your application code to the relevant database language. Choose an appropriate driver from the supported list of drivers which appears in
"Driver Vendor" drop down list. For more information see: Administration and
Configuration Guide, "Chapter 6 Datasource
Management"
Configure a datasource which can be used by applications. Give a datasource name, configure the other fields and click Next. For more information see: Administration and
Configuration Guide, "Datasource
Configuration"
16
Screen n ame
Wh en it Ap p ears
Always
Always
Always
Always
Always
Chapt er 4 . Inst all Inst ruct ions
Descrip t io n
Review your selections and click Next.
When installation progress completes, click
Next.
When processing finishes, click Next.
Choose whether to create shortcuts and how to configure them. Then click Next.
Click G enerate i nstal l ati o n scri pt and
pro perti es fi l e if you want to capture the selected installation options. Then click D o ne.
Installation is now complete.
Resu lt
The installation is complete and JBoss EAP 6 is installed on your target machine.
Report a bug
4 .3.3. Uninst all JBoss EAP 6 (Inst aller)
Previo u s St ep in
Section 4.3.1, “ Download JBoss EAP 6 (Installer)”
Su mmary
This section details the steps required to uninstall an instance of JBoss EAP 6 that was installed using either the graphical or text-based installer.
Pro ced u re 4 .6 . Un in st all JBo ss EAP 6 ( G rap h ical In st allat io n )
1. During the installation of JBoss EAP 6 on the target machine, a directory called
Uni nstal l er was created in the directory where you had installed JBoss EAP 6. This directory contains a file called uni nstal l er. jar. Navigate to this directory in a terminal window.
2. Launch the GUI uninstaller by executing the following command:
java -jar uni nstal l er. jar
3. The execution of the command will launch the graphical uninstaller as shown in the following figure. Select the check box if you want to delete the JBoss EAP 6 installation directory.
17
JBoss Ent erprise Applicat ion Plat form 6 .3 Inst allat ion G uide
Fig u re 4 .1. Un in st all JBo ss EAP 6 u sin g t h e g rap h ical in st aller
4. Press the Un in st all button to start the uninstall process.
5. When the uninstall process is finished, press the Q u it button to exit the uninstaller.
6. After a successful uninstall, you may want to manually remove the Uni nstal l er directory from where you launched the uninstaller.
Pro ced u re 4 .7. T ext - b ased Un in st all Pro cess
1. In a console, navigate to the Uni nstal l er directory created during the installation process.
This can be found one level above EAP_HOME.
2. Launch the Text-based uninstaller by executing the following command:
java -jar uni nstal l er. jar -co nso l e
3. Follow the steps to uninstall JBoss EAP 6.
Resu lt :
JBoss EAP 6 is uninstalled from your server.
Report a bug
4 .4 . Graphical RPM Inst allat ion
4 .4 .1. Inst all JBoss EAP 6 (Graphical RPM Inst allat ion)
Prereq u isit es:
Section 3.1, “ JBoss EAP 6 Installation Prerequisites”
Su mmary
The Graphical RPM package method of installing JBoss EAP 6 is available for Red Hat Enterprise
Linux 5 and Red Hat Enterprise Linux 6. This topic covers the steps required to complete the installation.
18
Chapt er 4 . Inst all Inst ruct ions
Pro ced u re 4 .8. In st all JBo ss EAP 6 ( G rap h ical RPM In st allat io n )
Use PackageKit to graphically install JBoss EAP 6 on your target machine.
1. Lau n ch Packag eKit
PackageKit is an open source package management software installed as part of Red Hat
Enterprise Linux. On the target machine launch PackageKit by selecting Syst em →
Ad min ist rat io n → Ad d /Remo ve So f t ware.
2. Type jboss-eap6 in the search box and then press the Fi nd button. You will be presented with the JBoss EAP
6 package in the result box.
3. Select the JBoss EAP 6 package and press the Appl y button. See figure below.
Fig u re 4 .2. JBo ss EAP 6 Packag eKit In st all
4. Follow the rest of the steps to install JBoss EAP 6 on your target machine.
Resu lt
The installation is complete and JBoss EAP 6 is installed in your target machine.
Report a bug
4 .5. T ext -based RPM Inst allat ion
4 .5.1. Inst all JBoss EAP 6 (T ext -based RPM Inst allat ion)
Prereq u isit es:
19
JBoss Ent erprise Applicat ion Plat form 6 .3 Inst allat ion G uide
Section 3.1, “ JBoss EAP 6 Installation Prerequisites”
Su mmary
The RPM package method of installing JBoss EAP 6 is appropriate for Red Hat Enterprise Linux 5,
Red Hat Enterprise Linux 6, and Red Hat Enterprise Linux 7. This topic covers the steps required to install an instance using the command line.
Pro ced u re 4 .9 . T ext - b ased In st allat io n St ep s
Access and install the RPM package by using the YUM install via the Red Hat Network.
1. In st all t h e RPM p ackag e b y u sin g YUM an d t h e Red Hat Net wo rk
Use YUM to install the default JBoss EAP 6 group package by using the g ro upi nstal l command.
[user@ host ~]$ yum groupinstall jboss-eap6
2. Co n f ig u re in it o p t io n s.
The RPM install contains init scripts for launching the server. The configuration for the init
scripts are contained in several additional files. Refer to Section A.4, “ RPM Installation
Configuration Files for JBoss EAP 6” for details about these files and the options contained
within.
Resu lt
The installation is complete. The default EAP_HOME path for the RPM installation is
Section A.3, “ RPM Package List for JBoss EAP 6” for a complete list
of all the packages installed.
Report a bug
4 .6. Aut omat ed Inst allat ion
4 .6.1. Inst all Mult iple Inst ances of JBoss EAP 6 (Inst aller)
Prereq u isit es
Generate an automatic installation script using the Graphical or Text-based Installer:
. Section 4.3.2, “ Run the JBoss EAP Installation Program”
Su mmary
Multiple identical instances of JBoss EAP 6 can be installed using an automatic installation script, generated during the installation process, using either the Graphical or Text-based installer. This topic covers the steps required to install JBoss EAP 6 using a generated script.
Pro ced u re 4 .10. Au t o mat ed In st allat io n
In a terminal, run the following command to install JBoss EAP 6 using the automatic installation script:
20
java -jar jbo ss-eap-6 . 3. 0 -i nstal l er. jar auto. xml
Chapt er 4 . Inst all Inst ruct ions
Note
When you use the automatic installation script (auto.xml) for automated installation the installer by default will generate a prompt for entering all passwords.
Resu lt
An identical instance of JBoss EAP 6 has been installed, based on the automatic installation script.
Report a bug
4 .6.2. Use Aut omat ic Inst allat ion Script (aut o.xml) from Different Sources for
Inst alling JBoss EAP 6
The installer can use the automatic installation script (auto . xml ) from any of the network locations irrespective of where it is being run. Thus the installer (jbo ss-eap-6 . 3. 0 -i nstal l er. jar) and the automatic installation script (auto . xml ) can be located on different machines. This topic covers the steps to install JBoss EAP 6.3 automatically from a different network location.
In a terminal type either of the following commands to specify the automatic installation script
(present at a different network location) to your current network location: java -jar jbo ss-eap-6 . 3. 0 -i nstal l er. jar http://network-host/auto.xml
(For HTTP) java -jar jbo ss-eap-6 . 3. 0 -i nstal l er. jar ftp://network-host/auto.xml
(For FTP)
Resu lt
JBoss EAP 6 is installed on your machine.
Report a bug
4 .7. Aut omat ed Inst allat ion Approaches
4 .7.1. About Aut omat ed Inst allat ion Approaches
Prereq u isit es
Run the installer and generate an automatic installation script using Graphical or Text-based installer:
Section 4.3.2, “ Run the JBoss EAP Installation Program”
Su mmary
You may use two approaches to install JBoss EAP 6 automatically using the automatic installation script generated by the installer:
21
JBoss Ent erprise Applicat ion Plat form 6 .3 Inst allat ion G uide
The first approach is to specify all the key/password values needed for automatic installation in the automatic installation variable file
The second approach is to specify the key/password values during install time
Report a bug
4 .7.2. Inst all JBoss EAP 6 by Pre-set t ing t he Key/Password Values in t he
Aut omat ic Inst allat ion Variable File
Use the following procedure for automatically installing JBoss EAP 6 by pre-setting the key/password values in the automatic installation variable file.
Pro ced u re 4 .11.
1. En t er key valu es in variab le f ile
JBoss EAP 6 installer creates an automatic installation script and an automatic installation variable file. The automatic installation variable file contains a list of keys/password parameters needed for automatic installation. To enter key values open the automatic installation variable file. Fill in a valid key/password value against each key parameter. For example: adminPassword = password#2 vault.keystorepwd = vaultkeystorepw ssl.password = user12345
2. Ru n t h e in st aller wit h t h e variab lef ile f ilen ame arg u men t t o b eg in au t o mat ed
in st allat io n
You can begin fully automated EAP installation by running the installer with variablefile
auto . xml . vari abl efi l e argument. This argument supplies the variable file key/password values (step 1) to the installer.To begin fully automated installation open a terminal and enter the following command with relevant filenames: java -jar jbo ss-eap-6 . 3. 0 -i nstal l er. jar auto . xml -variablefile
auto . xml . vari abl efi l e
Resu lt
JBoss EAP 6 is installed on your machine.
Report a bug
4 .7.3. Inst all JBoss EAP 6 aut omat ically by Specifying t he Key
Values/Passwords During Inst all T ime
Use the following procedure for automatically installing JBoss EAP 6.3 by specifying the key values/passwords during install time.
Pro ced u re 4 .12.
Ru n t h e in st aller wit h variab les arg u men t
You can initiate automated installation by running the installer with variables argument and then
22
Chapt er 4 . Inst all Inst ruct ions
specifying a variable list. This variables argument will help you define variables along with the key/password values during install time. To initiate the installation process open a terminal and enter the following command with relevant filenames: java -jar jbo ss-eap-6 . 3. 0 -i nstal l er. jar auto . xml -variables adminPassword=password#2,vault.keystorepwd=vaultkeystorepw,ssl.password
=user12345
Note
It is important to specify the variable names (adminPassword, keystorepwd and ssl.password) without any empty space for successful installation.
Report a bug
4 .8. Inst alling Nat ive Component s and Ut ilit ies
Native Components are optional components which have been compiled to be optimized for a specific operating system and architecture. In some cases, using the native components may provide performance improvements. Native Components include native support for HornetQ (AIO), and the
Guide.
Native Utilities are optional utilities specific to each supported operating system and architecture.
These include scripts and utilities for installing JBoss EAP 6 as a service in your operating system, and generating SSL encryption keys and certificates.
In addition to Native Components and Native Utilities, Webserver Connector Natives are used for load balancing and clustering. See the Administration and Configuration Guide to configure Webserver
Connector Natives.
Report a bug
4 .8.1. Inst all Nat ive Component s and Nat ive Ut ilit ies (Zip, Inst aller)
Prereq u isit es
Install JBoss EAP 6 using the Z ip installation, Graphical Installer, or Text-based Installer:
Section 4.2.2, “ Install JBoss EAP 6 (Z IP Installation)” .
Section 4.3.2, “ Run the JBoss EAP Installation Program”
Access to the Management CLI or the Management Console for the JBoss EAP 6 server. Refer to
Launch the Management CLI or Log in to the Management Console in the Administration and
Configuration Guide.
For Native Components:
In Red Hat Enterprise Linux 6 and 7 environments, ensure that the Apache Portability Runtime
(APR) and OpenSSL libraries are installed. If you intend to use the Tomcat Native Library which is part of the JBoss EAP Native Components, the operating system package to mcatjss must be removed before installation.
23
JBoss Ent erprise Applicat ion Plat form 6 .3 Inst allat ion G uide
In a HP-UX environment, OpenSSL must be installed.
Pro ced u re 4 .13. Do wn lo ad an d In st all Nat ive Co mp o n en t s
1. Download the Native Components package for your operating system and architecture from the Red Hat Customer Portal. You can download the packages from the same location
specified in Section 4.2.1, “ Download JBoss EAP 6 (Z ip Installation)” .
2. Extract the downloaded Native Components zip archive over your JBoss EAP 6 installation.
You can verify a successful extraction by checking if there is a new folder for your operating system and architecture in
EAP_HOME/mo d ul es/system/l ayers/base/o rg /jbo ss/as/web/mai n/l i b/.
3. Using the Management CLI, activate the native components for the web subsystem with the following command:
[standalone@ localhost:9999 /] /subsystem= web: wri te-
attri bute(name= nati ve,val ue= true)
4. Restart the JBoss EAP 6 server to apply the changes.
Pro ced u re 4 .14 . Do wn lo ad an d In st all Nat ive Ut ilit ies
1. Download the Native Utilities package for your operating system and architecture from the
Red Hat Customer Portal. You can download the packages from the same location specified
in Section 4.2.1, “ Download JBoss EAP 6 (Z ip Installation)” .
2. Extract the downloaded Native Components zip archive over your JBoss EAP 6 installation.
You can verify a successful extraction by checking if there is nati ve directory in
EAP_HOME/mo d ul es/system/l ayers/base/.
3. Refer to procedures in the JBoss EAP documentation suite and on the Red Hat Customer
Portal to configure specific native utilities features.
Report a bug
4 .8.2. Inst all Nat ive Component s and Nat ive Ut ilit ies (RPM Inst allat ion)
You can use the RPM installation method to install native components, utilities and all the corresponding dependencies only if you have installed EAP using RPM installation method. The
RPM package method of installing natives is appropriate for Red Hat Enterprise Linux 5, 6 and 7.
This topic covers the steps required to install the native components and utilities using the command line.
Prereq u isit es
Section 3.1, “ JBoss EAP 6 Installation Prerequisites”
Pro ced u re 4 .15. In st all Nat ive Co mp o n en t s an d Nat ive Ut ilit ies
1. In st all n at ive co mp o n en t s an d u t ilit ies
To install native components and utilities in Red Hat Enterprise Linux 5, 6 and 7 (with their dependencies) run the following command using your administration account replacing
package_name with name of the native component which you need to install:
24
Chapt er 4 . Inst all Inst ruct ions
yum install package_name
You can install these native components: mo d _cl uster-nati ve, mo d _jk, mo d _rt,
mo d _snmp, apache-co mmo ns-d aemo n-jsvc-eap6 , httpd , httpd -d evel , jbo ssas-
ho rnetq -nati ve, jbo ssas-jbo ssweb-nati ve.
Important
The native components jbo ssas-ho rnetq -nati ve and jbo ssas-jbo ssweb-
nati ve are installed by default when you run the yum g ro upi nstal l jbo ss-eap6
command to install JBoss EAP 6 group package. If you have used Section 4.4.1,
“ Install JBoss EAP 6 (Graphical RPM Installation)” or
Section 4.5.1, “ Install JBoss EAP
6 (Text-based RPM Installation)” for JBoss EAP 6 installation you need not install
jbo ssas-ho rnetq -nati ve and jbo ssas-jbo ssweb-nati ve.
Note
It is important to give the correct package name in order to install a specific native component. Package names are case sensitive. In Red Hat Enterprise Linux 7 the name of the httpd package is httpd 22. Therefore the package httpd must be replaced with
httpd 22 when you run yum i nstal l package_name command for installing
Apache HTTP server in Red Hat Enterprise Linux 7.
2. Rest art t h e server
Restart the JBoss EAP 6 server to apply the changes
Report a bug
4 .9. Service Configurat ion
4 .9.1. Configure JBoss EAP 6 as a Service in Red Hat Ent erprise Linux (RPM
Met hod)
Prereq u isit es
Install JBoss EAP 6 using the RPM Method (Graphical or Text Based).
Section 4.4.1, “ Install JBoss EAP 6 (Graphical RPM Installation)”
Section 4.5.1, “ Install JBoss EAP 6 (Text-based RPM Installation)”
Administrator privileges on the server are required.
Su mmary
Use the following procedure to install JBoss EAP 6 as a service on Red Hat Enterprise Linux when the installation has been done using the RHN (RPM) method.
25
JBoss Ent erprise Applicat ion Plat form 6 .3 Inst allat ion G uide
Pro ced u re 4 .16 . Co n f ig u re JBo ss EAP 6 as a Service u sin g t h e RPM Met h o d in Red Hat
En t erp rise Lin u x
1. In st all JBo ss EAP 6
Install JBoss EAP 6 via the RPM method using one of the steps listed in the prerequisite sections listed above.
2. En ab le t h e service
The RPM install method for JBoss EAP 6 installs the requisite service files in their correct locations. All you need to do to set it up as service is issue the following command: chkconfig jbossas on
To set it up as a service in domain mode, issue the following command: chkconfig jbossas-domain on
Resu lt
JBoss EAP 6 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
4 .9.2. Configure JBoss EAP 6 as a Service in Red Hat Ent erprise Linux (Zip,
Inst aller)
Prereq u isit es
Install JBoss EAP 6 using the Z ip installation, Graphical Installer, or Text-based Installer:
Section 4.2.2, “ Install JBoss EAP 6 (Z IP Installation)” .
Section 4.3.2, “ Run the JBoss EAP Installation Program” .
Administrator privileges on the server are required.
Su mmary
Use the following procedure to install JBoss EAP 6 as a service on Red Hat Enterprise Linux when the installation has been done with either the zip, text, or graphical methods. This process does not apply when the installation has been done using the RHN (RPM) method.
Pro ced u re 4 .17. Set Up t h e Service
Note
The steps below describe running JBoss EAP 6 as a service in standalone mode. In order to run JBoss EAP 6 as a service in domain mode, use the same steps but replace jbo ss-as-
stand al o ne. sh with jbo ss-as-d o mai n. sh.
26
Chapt er 4 . Inst all Inst ruct ions
1. Lo cat e t h e st art - u p scrip t an d co n f ig u rat io n f ile
The start-up script and an associated configuration file are located in the
EAP_HOME/bi n/i ni t. d / directory. Open the configuration file jbo ss-as. co nf to edit it.
2. Cu st o miz e t h e st art - u p o p t io n s in t h e jbo ss-as. co nf f ile
There are several options within the jbo ss-as. co nf file. At the minimum, specify the correct values for JBO SS_HO ME and the JBO SS_USER variables. If these variables are absent, add them.
3. Co p y f iles in t o syst em d irect o ries a. Copy the modified configuration file to the /etc/jbo ss-as directory.
[user@ ho st i ni t. d ]$ sud o mkd i r /etc/jbo ss-as
[user@ ho st i ni t. d ]$ sud o cp jbo ss-as. co nf /etc/jbo ss-as/ b. Copy the start-up script to the /etc/i ni t. d directory.
[user@ ho st i ni t. d ]$ sud o cp jbo ss-as-stand al o ne. sh
/etc/i ni t. d
4. Ad d t h e st art - u p scrip t as a service.
Add the new jbo ss-as-stand al o ne. sh service to list of automatically started services, using the chkco nfi g service management command.
[user@ ho st i ni t. d ]$ sud o chkco nfi g --ad d jbo ss-as-stand al o ne. sh
5. St art t h e service.
Test that the service has been installed correctly by using one of the following commands for
Red Hat Enterprise Linux.
A. For Red Hat Enterprise Linux 5 and 6:
[user@ ho st bi n]$ sud o servi ce jbo ss-as-stand al o ne. sh start
B. For Red Hat Enterprise Linux 7:
[user@ ho st bi n]$ sud o servi ce jbo ss-as-stand al o ne start
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.
Note
The green [OK] does not appear for Red Hat Enterprise Linux 7.
27
JBoss Ent erprise Applicat ion Plat form 6 .3 Inst allat ion G uide
6. Make t h e service st art au t o mat ically wh en yo u rest art yo u r server.
To add the service to the list of services which start automatically when your server restarts, issue the following command.
[user@ ho st i ni t. d ]$ sud o chkco nfi g jbo ss-as-stand al o ne. sh o n
Resu lt
JBoss EAP 6 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.
Pro ced u re 4 .18. Un in st all t h e JBo ss EAP 6 service f ro m Red Hat En t erp rise Lin u x
Note
The steps below describe uninstalling the JBoss EAP 6 service in standalone mode. In order to uninstall the JBoss EAP 6 service in domain mode, use the same steps but replace jbo ss-
as-stand al o ne. sh with jbo ss-as-d o mai n. sh.
1. If the service is running, first open a terminal and stop the service by executing the sto p command with the name of the service:
sud o servi ce jbo ss-as-stand al o ne. sh sto p
2. Remove JBoss EAP from the list of services:
sud o chkco nfi g --d el jbo ss-as-stand al o ne. sh
3. Remove the system directory files.
a. Remove the service start-up script:
sud o rm /etc/i ni t. d /jbo ss-as-stand al o ne. sh
b. Remove the service configuration file:
sud o rm /etc/jbo ss-as/jbo ss-as. co nf
Important
/etc/jbo ss-as is not a standard system directory. Only if there are no other files being used there, also remove the directory itself:
sud o rm -rf /etc/jbo ss-as/
Resu lt
28
Chapt er 4 . Inst all Inst ruct ions
JBoss EAP 6 service is uninstalled from the server.
Report a bug
4 .9.3. Configure JBoss EAP 6 as a Service in Microsoft Windows Server (Zip,
Inst aller)
Prereq u isit es
Install JBoss EAP 6 using the Z ip installation, Graphical Installer, or Text-based Installer:
Section 4.2.2, “ Install JBoss EAP 6 (Z IP Installation)” .
Section 4.3.2, “ Run the JBoss EAP Installation Program”
Administrator privileges on the server are required.
The JAVA_HO ME system environment variable must be set.
The JBoss EAP 6 server instance must not be running.
Important
When setting system environment variables, using the set command at a Windows Server command prompt will not permanently set the environment variable. You must use either the
setx command, or the System interface in the C o ntro l P anel .
Su mmary
Use the following procedures to configure JBoss EAP 6 as a service on Microsoft Windows Server.
Pro ced u re 4 .19 . Co n f ig u re a Service f o r JBo ss EAP 6 in Micro so f t Win d o ws Server
1. Creat e syst em en viro n men t variab les
Create two system environment variables:
JBO SS_HO ME pointing to the JBoss EAP 6 installation directory.
NO P AUSE= 1
2. If n o t alread y co n f ig u red , d o wn lo ad an d ext ract t h e Nat ive Ut ilit ies p ackag e f o r
yo u r arch it ect u re
If the Native Utilities for Windows Server package has not been installed as part of the JBoss
EAP 6 installation, download the relevant 32-bit or 64-bit package from the Red Hat Customer
Portal at https://access.redhat.com
. Extract the Native Utilities zip archive over the JBoss EAP
6 installation.
This will result in a nati ve directory in the following location in the JBoss EAP 6 installation:
EAP_HOME\mo d ul es\system\l ayers\base\
3. In st all t h e service
29
JBoss Ent erprise Applicat ion Plat form 6 .3 Inst allat ion G uide
Open a terminal, and change directories to
EAP_HOME\mo d ul es\system\l ayers\base\nati ve\sbi n
A new service can be created with the servi ce i nstal l command, with the available options shown in the following table.
T ab le 4 .3. servi ce i nstal l o p t io n s
Arg u men t o r
Swit ch
/controller
HOST:PORT
/host
[DOMAIN_HOST]
/loglevel LEVEL
/name
SERVICE_NAME
/desc
"DESCRIPTION"
/serviceuser
DOMAIN\USERNAME
/servicepass
PASSWORD
/jbossuser
USERNAME
/jbosspass
PASSWORD
Descrip t io n
The host and port of the management interface. If omitted, the default is l o cal ho st: 9 9 9 9 .
Indicates that domain mode is to be used, optionally specifying the name of the domain controller. If the domain controller name is omitted, the default name is master.
The log level for the service, either: ER R O R , INFO , WAR N or D EBUG .
If omitted, the default is INFO
The name of the service to be created, must not contain spaces. If omitted, the default is JBo ssEAP 6
The description of the service. If omitted, the default is "JBo ss
Enterpri se Appl i cati o n P l atfo rm 6 "
Specifies the name of the account under which the service will run.
Use an account name in the format of DOMAIN\USERNAME. If omitted, the service runs as the Local System account.
Password for /serviceuser account.
Optional, the JBoss EAP 6 username to use for the shutdown command.
Password for /jbossuser account, required if /jbossuser is specified.
Below are basic examples of an i nstal l command to create a new service in either standalone or domain mode. Execute the following command, adjusting the log level for the service as required:
A. Standalone mode:
servi ce. bat i nstal l /l o g l evel INFO
B. Domain mode:
If you are not using the default master for your JBoss EAP 6 domain controller, replace
master with the correct host name or alias of the JBoss EAP 6 domain controller.
servi ce. bat i nstal l /ho st master /l o g l evel INFO
A new Windows service will be created with name JBo ssEAP 6 .
4. Verif y t h e n ew service in t h e Services co n so le
Execute the following command in a terminal to open the Windows Services console:
servi ces. msc
30
Chapt er 4 . Inst all Inst ruct ions
If the default service name was used, in the list of Windows services, the new service will have the display name: JBo ss Enterpri se Appl i cati o n P l atfo rm 6 . From the Services console you can start and stop the service, as well change its settings on how and when it starts.
5. St art in g an d st o p p in g t h e JBo ss EAP 6 service f ro m a t ermin al
To start the service from a terminal, use the following command, changing the service name if necessary:
net start JBossEAP6
To stop the service from a terminal, use the following command, changing the service name if necessary:
net sto p JBossEAP6
Resu lt
A JBoss EAP 6 service is configured in Microsoft Windows Server.
Pro ced u re 4 .20. Un in st all t h e JBo ss EAP 6 service f ro m Micro so f t Win d o ws Server
If the service is running, first open a terminal and stop the service by executing the net sto p command with the name of the service:
net sto p JBossEAP6
In a terminal, change directories to
EAP_HOME\mo d ul es\system\l ayers\base\nati ve\sbi n and execute the following command:
servi ce uni nstal l
Resu lt
The JBoss EAP 6 service has been removed from Microsoft Windows Server.
Report a bug
31
JBoss Ent erprise Applicat ion Plat form 6 .3 Inst allat ion G uide
Chapter 5. Patching and Upgrading JBoss EAP 6
5.1. About Pat ches and Upgrades
Patching in JBoss EAP 6 applies updates which are made available to a specific minor version of
JBoss EAP 6, for example JBoss EAP 6.2. Patches can contain individual or cumulative updates.
Upgrading is the process of moving to a newer major version (for example, from 5.0 to 6.0) or newer minor version (for example, from 6.1 to 6.2), and cannot be done via patching.
See Also :
Section 5.2, “ Patching JBoss EAP 6”
Section 5.3, “ Upgrading JBoss EAP 6”
Report a bug
5.2. Pat ching JBoss EAP 6
5.2.1. About Pat ching Mechanisms
JBoss patches are distributed in two forms: zip (for all products) and RPM (for a subset of products).
Important
A JBoss product installation must always only be updated using one patch method: either zip or RPM patches. Only security and cumulative patches will be available via RPM, and customers using an RPM installation will not be able to update using zip patches.
JBoss patches can be either an asynchronous update, or a planned update:
Asynchronous updates: individual patches which are released outside the normal update cycle of the existing product. These may include security patches, as well as other individual patches provided by Red Hat Global Support Services (GSS) to fix specific issues.
Planned updates: These include cumulative patches, as well as micro, minor or major upgrades of an existing product. Cumulative patches include all previously developed updates for that version of the product.
Deciding whether a patch is released as part of a planned update or an asynchronous update depends on the severity of the issue being fixed. An issue of low impact is typically deferred, and is resolved in the next cumulative patch or minor release of the affected product. Issues of moderate or higher impact are typically addressed in order of importance as an asynchronous update to the affected product, and contain a fix for only a specific issue.
Security updates for JBoss products are provided by an erratum (for both zip and RPM methods).
The erratum encapsulates a list of the resolved flaws, their severity ratings, the affected products, textual description of the flaws, and a reference to the patches. Bug fix updates are not announced via an erratum.
32
Chapt er 5. Pat ching and Upgrading JBoss EAP 6
Important
It is important to note that after a patch has been applied, the jars picked up at runtime are picked up from the
EAP_HOME/mo d ul es/system/l ayers/base/. o verl ays/$P AT C H_ID /$MO D ULE
directory. The original files are left in
EAP_HOME/mo d ul es/system/l ayers/base/$MO D ULE. The patching mechanism cripples the original jar files for security reasons. This means that if you apply a patch which updates a module, the original module's jar files are altered to be unusable. If the patch is rolled back, the original files will be reverted back to a usable state. This also means that the proper
rollback procedure must be used to rollback any applied patch. See Section 5.2.2.3,
“ Rollback the Application of a Patch in Z ip Form Using the Patch Management System” for the
proper rollback procedure.
Impact Rating of JBoss Security Patches”
Red Hat maintains a mailing list for notifying subscribers about security related flaws. See
Section 5.2.4, “ Subscribe to Patch Mailing Lists”
Report a bug
5.2.2. Pat ching a Zip/Inst aller Inst allat ion
5 .2 .2 .1 . T he Pat ch Manage m e nt Syst e m
The JBoss EAP 6 patch management system is used to apply downloaded zip patches to a single
JBoss EAP 6 server. It can be accessed either through the Management CLI by using the patch command, or through the Management Console. The patch management system cannot be used to automatically patch JBoss EAP 6 server instances across a managed domain, but individual server instances in a managed domain can be patched independently.
Important
JBoss EAP 6 server instances which have been installed using the RPM method cannot be
updated using the patch management system. Refer to Section 5.2.3, “ Patching an RPM
Installation” to update RPM-installed JBoss EAP 6 servers.
Note
The patch management system can only be used with patches produced for versions of JBoss
EAP 6.2 and later. For patches for versions of JBoss EAP prior to 6.2, you should instead refer to the relevant version's documentation available at https://access.redhat.com/site/documentation/ .
In addition to applying patches, the patch management system can provide basic information on the state of installed patches, and also provides a way to immediately rollback the application of a patch.
When applying or rolling back a patch, the patch management system will check the modules and
33
JBoss Ent erprise Applicat ion Plat form 6 .3 Inst allat ion G uide
other miscellaneous files that it is changing for any user modifications. If a user modification is detected, and a conflict-handling switch has not been specified, the patch management system will abort the operation and warn that there is a conflict. The warning will include a list of the modules and other files that are in conflict. To complete the operation, it must be retried with a switch specifying how to resolve the conflict: either to preserve the user modifications, or to override them.
The table below lists the arguments and switches for the Management CLI patch command.
T ab le 5.1. patch Co mman d Arg u men t s an d Swit ch es
Arg u men t o r Swit ch appl y
--o verri d e-al l
--o verri d e-mo d ul es
--o verri d e= path(,path)
--preserve= path(,path)
--ho st= HOST_NAME i nfo hi sto ry ro l l back
--patch-i d = PATCH_ID
--reset-co nfi g urati o n= TRUE| FALSE
--ro l l back-to
Descrip t io n
Applies a patch.
If there is a conflict, the patch operation overrides any user modifications.
If there is a conflict as a result of any modified modules, this switch overrides those modifications with the contents of the patch operation.
For specified miscellaneous files only, this will override the conflicting modified files with the files in the patch operation.
For specified miscellaneous files only, this will preserve the conflicting modified files.
Available in domain mode, this specifies the host that the patch operation will be performed on.
Returns information on currently installed patches.
Returns information on the patching history.
Rollsback the application of a patch.
Required for rollback, the ID of the patch to rollback.
Required for rollback, this specifies whether to restore the server configuration files as part of the rollback operation.
If the patch to rollback is an individual (one-off) patch, using this argument specifies that the rollback operation will also rollback all other one-off patches that have been applied on top of the specified patch.
Report a bug
5 .2 .2 .2 . Inst alling Pat che s in Zip Fo rm Using t he Pat ch Manage m e nt Syst e m
Prereq u isit es:
Section 3.1, “ JBoss EAP 6 Installation Prerequisites”
Su mmary
Patches that are in the zip format can be installed using the JBoss EAP 6 patch management system via either the Management CLI or the Management Console.
34
Chapt er 5. Pat ching and Upgrading JBoss EAP 6
Important
The patch management system is a feature that was added in JBoss EAP 6.2. For versions of
JBoss EAP prior to 6.2, the process to install patches in zip form is different, and you should instead refer to the relevant version's documentation available at https://access.redhat.com/site/documentation/ .
Prereq u isit es
Valid access and subscription to the Red Hat Customer Portal.
A current subscription to a JBoss product installed in zip format.
Access to the Management CLI or the Management Console for the JBoss EAP 6 server to be updated. Refer to Launch the Management CLI or Log in to the Management Console in the
Administration and Configuration Guide.
Warning
Before installing a patch, you should backup your JBoss product along with all customized configuration files.
Pro ced u re 5.1. Ap p ly a z ip p at ch t o a JBo ss EAP 6 server in st an ce u sin g t h e
Man ag emen t CLI
1. Download the patch zip file from the Customer Portal at https://access.redhat.com/downloads/
2. From the Management CLI, apply the patch with the following command including the appropriate path to the patch file:
[standalone@ localhost:9999 /] patch appl y /path/to/downloaded-
patch.zip
The patch tool will warn if there are any conflicts in attempting the apply the patch. Refer to
Section 5.2.2.1, “ The Patch Management System”
for available patch command switches to re-run the command to resolve any conflicts.
3. Restart the JBoss EAP 6 server for the patch to take effect:
[standalone@ localhost:9999 /] shutd o wn --restart= true
Pro ced u re 5.2. Ap p ly a z ip p at ch t o a JBo ss EAP 6 server in st an ce u sin g t h e
Man ag emen t Co n so le
1. Download the patch zip file from the Customer Portal at https://access.redhat.com/downloads/
2. In the Management Console:
A. For a standalone server: click on the R unti me tab at the top of the screen, then click
P atch Manag ement.
35
JBoss Ent erprise Applicat ion Plat form 6 .3 Inst allat ion G uide
B. For a managed domain: click on the D o mai n tab at the top of the screen, select the host you want to patch from the Ho st drop-down menu, then click P atch Manag ement.
3. Click Appl y a New P atch.
a. If you are patching a managed domain host, on the next screen select whether to shutdown the servers on the host, and click Next.
4. Click the Bro wse button, select the downloaded patch you want to apply, and then click
Next.
a. If there are any conflicts in attempting to apply the patch, a warning will be displayed.
Click Vi ew erro r d etai l s to see the detail of the conflicts. If there is a conflict, you can either cancel the operation, or select the O verri d e al l co nfl i cts check box and click Next. Overriding conflicts will result in the content of the patch overriding any user modifications.
5. After the patch has been successfully applied, select whether to restart the JBoss EAP 6 server now for the patch to take effect, and click Fi ni sh.
Resu lt
The JBoss EAP 6 server instance is patched with the latest update.
Report a bug
5 .2 .2 .3. Ro llback t he Applicat io n o f a Pat ch in Zip Fo rm Using t he Pat ch
Manage m e nt Syst e m
Su mmary
The JBoss EAP 6 patch management system can be used to rollback the application of a previously applied zip patch, via either the Management CLI or the Management Console.
Warning
Rolling back the application of a patch using the patch management system is not intended as a general uninstall functionality. It is only intended to be used immediately after the application of a patch which had undesirable consequences.
Important
The patch management system is a feature that was added in JBoss EAP 6.2. For versions of
JBoss EAP prior to 6.2, the process to rollback patches in zip form is different, and you should instead refer to the relevant version's documentation available at https://access.redhat.com/site/documentation/ .
Prereq u isit es
A patch that was previously applied using the JBoss EAP 6 patch management system.
36
Chapt er 5. Pat ching and Upgrading JBoss EAP 6
Access to the Management CLI or the Management Console for the JBoss EAP 6 server. Refer to
Launch the Management CLI or Log in to the Management Console in the Administration and
Configuration Guide.
Warning
When following either procedure, use caution when specifying the value of the R eset
C o nfi g urati o n option:
If set to T R UE, the patch rollback process will also rollback the JBoss EAP 6 server configuration files to their pre-patch state. Any changes that were made to the JBoss EAP 6 server configuration files after the patch was applied will be lost.
If set to FALSE, the server configuration files will not be rolled back. In this situation, it is possible that the server will not start after the rollback, as the patch may have altered configurations, such as namespaces, which may no longer be valid and have to be fixed manually.
Pro ced u re 5.3. Ro llb ack a p at ch f ro m a JBo ss EAP 6 server in st an ce u sin g t h e
Man ag emen t CLI
1. From the Management CLI, use the patch i nfo command to find the ID of the patch that is to be rolled back.
A. For cumulative patches, the patch ID is the value of the first cumul ati ve-patch-i d shown in the patch i nfo output.
B. Individual security or bug fix patch IDs are listed as the value of the first patches shown in the patch i nfo output, with the most recently applied individual patch listed first.
2. From the Management CLI, rollback the patch with the appropriate patch ID from the previous step.
[standalone@ localhost:9999 /] patch ro l l back --patch-i d = PATCH_ID -
-reset-co nfi g urati o n= TRUE
The patch tool will warn if there are any conflicts in attempting the rollback the patch. Refer to
Section 5.2.2.1, “ The Patch Management System”
for available patch command switches to re-run the command to resolve any conflicts.
3. Restart the JBoss EAP 6 server for the patch rollback to take effect:
[standalone@ localhost:9999 /] shutd o wn --restart= true
Pro ced u re 5.4 . Ro llb ack a p at ch f ro m a JBo ss EAP 6 server in st an ce u sin g t h e
Man ag emen t Co n so le
1. In the Management Console:
A. For a standalone server: click on the R unti me tab at the top of the screen, then click
P atch Manag ement.
B. For a managed domain: click on the D o mai n tab at the top of the screen, select the relevant host from the Ho st drop-down menu, then click P atch Manag ement.
37
JBoss Ent erprise Applicat ion Plat form 6 .3 Inst allat ion G uide
2. In the R ecent P atch Hi sto ry table, select the patch that you want to rollback, then click
R o l l back.
a. For a managed domain host, on the next screen select whether to shutdown the servers on the host, and click Next.
3. Choose your options for the rollback process, then click Next.
4. Confirm the options and the patch to be rolled back, then click Next.
a. If the O verri d e al l option was not selected and there are any conflicts in attempting to rollback the patch, a warning will be displayed. Click Vi ew erro r
d etai l s to see the detail of the conflicts. If there is a conflict, you can either cancel the operation, or click C ho o se O pti o ns and try the operation again with the
O verri d e al l check box selected. Overriding conflicts will result in the rollback operation overriding any user modifications.
5. After the patch has been successfully rolled back, select whether to restart the JBoss EAP 6 server now for the changes to take effect, and click Fi ni sh.
Resu lt
The patch, and optionally also the server configuration files, are rolled back on the JBoss EAP 6 server instance.
Report a bug
5.2.3. Pat ching an RPM Inst allat ion
Prereq u isit es:
Section 3.1, “ JBoss EAP 6 Installation Prerequisites”
Su mmary
JBoss patches are distributed in two forms: Z IP (for all products) and RPM (for a subset of products).
This task describes the steps you need to take to install the patches via the RPM format.
Prereq u isit es
A valid subscription to the Red Hat Network.
A current subscription to a JBoss product installed via an RPM package.
Pro ced u re 5.5. Ap p ly a p at ch t o a JBo ss p ro d u ct via t h e RPM met h o d
Security updates for JBoss products are provided by errata (for both zip and RPM methods). The errata encapsulates a list of the resolved flaws, their severity ratings, the affected products, textual description of the flaws, and a reference to the patches.
For RPM distributions of JBoss products, the errata include references to the updated RPM packages. The patch can be installed by using yum.
38
Chapt er 5. Pat ching and Upgrading JBoss EAP 6
Warning
Before installing a patch, you must backup your JBoss product along with all customized configuration files.
1. Get notified about the security patch either via being a subscriber to the JBoss watch mailing list or by browsing the JBoss watch mailing list archives.
2. Read the errata for the security patch and confirm that it applies to a JBoss product in your environment.
3. If the security patch applies to a JBoss product in your environment, then follow the link to download the updated RPM package which is included in the errata.
4. Use
yum upd ate
to install the patch.
Important
When updating an RPM installation, your JBoss product is updated cumulatively with all RPM-released fixes.
Resu lt
The JBoss product is patched with the latest update using the RPM format.
Report a bug
5.2.4 . Subscribe t o Pat ch Mailing List s
Su mmary
The JBoss team at Red Hat maintains a mailing list for security announcements for Red Hat JBoss
Middleware products. This section covers what you need to do to subscribe to this list.
Prereq u isit es
None
Pro ced u re 5.6 . Su b scrib e t o t h e JBo ss Wat ch List
1. Click the following link to go to the JBoss Watch mailing list page: JBoss Watch Mailing List .
2. Enter your email address in the Subscri bi ng to Jbo ss-watch-l i st section.
3. [You may also wish to enter your name and select a password. Doing so is optional but recommended.]
4. Press the Subscri be button to start the subscription process.
39
JBoss Ent erprise Applicat ion Plat form 6 .3 Inst allat ion G uide
5. You can browse the archives of the mailing list by going to: JBoss Watch Mailing List
Archives .
Resu lt
After confirmation of your email address, you will be subscribed to receive security related announcements from the JBoss patch mailing list.
Report a bug
5.2.5. Severit y and Impact Rat ing of JBoss Securit y Pat ches
To communicate the risk of each JBoss security flaw, Red Hat uses a four-point severity scale of low, moderate, important and critical, in addition to Common Vulnerability Scoring System (CVSS) version 2 base scores which can be used to identify the impact of the flaw.
T ab le 5.2. Severit y Rat in g s o f JBo ss Secu rit y Pat ch es
Severit y
Critical
Important
Moderate
Low
Descrip t io n
This rating is given to flaws that could be easily exploited by a remote unauthenticated attacker and lead to system compromise (arbitrary code execution) without requiring user interaction.
These are the types of vulnerabilities that can be exploited by worms. Flaws that require an authenticated remote user, a local user, or an unlikely configuration are not classed as critical impact.
This rating is given to flaws that can easily compromise the confidentiality, integrity, or availability of resources. These are the types of vulnerabilities that allow local users to gain privileges, allow unauthenticated remote users to view resources that should otherwise be protected by authentication, allow authenticated remote users to execute arbitrary code, or allow local or remote users to cause a denial of service.
This rating is given to flaws that may be more difficult to exploit but could still lead to some compromise of the confidentiality, integrity, or availability of resources, under certain circumstances. These are the types of vulnerabilities that could have had a critical impact or important impact but are less easily exploited based on a technical evaluation of the flaw, or affect unlikely configurations.
This rating is given to all other issues that have a security impact. These are the types of vulnerabilities that are believed to require unlikely circumstances to be able to be exploited, or where a successful exploit would give minimal consequences.
4 0
Chapt er 5. Pat ching and Upgrading JBoss EAP 6
The impact component of a CVSS v2 score is based on a combined assessment of three potential impacts: Confidentiality (C), Integrity (I) and Availability (A). Each of these can be rated as None (N),
Partial (P) or Complete (C).
Because the JBoss server process runs as an unprivileged user and is isolated from the host operating system, JBoss security flaws are only rated as having impacts of either None (N) or Partial
(P).
Examp le 5.1. CVSS v2 Imp act Sco re
The example below shows a CVSS v2 impact score, where exploiting the flaw would have no impact on system confidentiality, partial impact on system integrity and complete impact on system availability (that is, the system would become completely unavailable for any use, for example, via a kernel crash).
C : N/I: P /A: C
Combined with the severity rating and the CVSS score, organizations can make informed decisions on the risk each issue places on their unique environment and schedule upgrades accordingly.
For more information about CVSS2, please see: CVSS2 Guide .
Report a bug
5.3. Upgrading JBoss EAP 6
5.3.1. Upgrade t he JBoss EAP 6 ZIP Inst allat ion
Prereq u isit es
Ensure that the base operating system is up to date.
Determine which files have been modified since JBoss EAP 6 was installed.
Back up any modified configuration files, deployments, and all user data.
Section 4.2.1, “ Download JBoss EAP 6 (Z ip Installation)” .
Su mmary
This procedure covers upgrading a JBoss EAP 6 Z IP installation between minor versions (for example, from JBoss EAP 6.1 to 6.2). For installing patches for a specific minor version, refer to the
Patch Installation section. Upgrading to the latest release of JBoss EAP 6 requires some initial work to back up the existing installation.
Warning
For managed domains, the master Host Controller (or Domain Controller) instance should be upgraded first, before each Host Controller is upgraded.
Pro ced u re 5.7. Up g rad e t o t h e lat est JBo ss EAP 6 versio n
4 1
JBoss Ent erprise Applicat ion Plat form 6 .3 Inst allat ion G uide
1. Move the downloaded Z IP archive to the desired location. It is recommended that this is a different location to the existing JBoss EAP 6 installation.
Important
If you wish to install the latest version of JBoss EAP 6 to the same directory location as the existing installation, you will need to move the existing installation to a different location before proceeding. This is to prevent modified configuration files, deployments, and upgrades from being lost.
2. Unzip the archive. This step installs a clean instance of the latest JBoss EAP 6 release.
3. Copy the EAP_HOME/domain/ and EAP_HOME/standalone/ directories from the previous installation over the new installation directories.
Note
New features in the new release, such as new subsystems, may not be activated if configuration files are copied from an older JBoss EAP 6 installation. To use these new features, it is necessary to compare and update the old configuration files with the ones from the new version.
4. Review the changes made to the bi n directory of the previous installation, and make the equivalent modifications to the new directory.
Warning
Files in the bi n directory should not be overwritten by the files from previous versions.
Changes should be made manually.
5. Review the remaining modified files from the previous installation, and move these changes into the new installation. These files may include:
The wel co me-co ntent directory.
Custom modules in the mo d ul es directory.
Custom bundles in the bund l es directory.
6. O p t io n al: If JBoss EAP 6 was previously configured to run as a service, remove the existing service and configure a new service for the upgraded installation.
Resu lt
The JBoss EAP 6 Z IP installation has been successfully upgraded to the latest release.
Report a bug
5.3.2. Upgrade t he JBoss EAP 6 RPM Inst allat ion
Prereq u isit es
4 2
Chapt er 5. Pat ching and Upgrading JBoss EAP 6
Ensure that the base operating system is up to date and that the system is subscribed and enabled to get updates for the Base OS channel.
Ensure that the correct JBoss EAP 6 RHN channel is enabled. For example, on a x86, 64 bit architecture, this will be the JBoss Application Platform (v 6) for 6Server x86_64 channel
(jbapppl atfo rm-6 -x86 _6 4 -server-6 -rpm).
Back up any modified configuration files, deployments, and all user data.
Su mmary
Upgrading to the latest release of JBoss EAP 6 requires some initial work to back up the existing installation. This topic covers upgrading the RPM installation via the Red Hat Network (RHN).
Warning
For managed domains, the master Host Controller (or Domain Controller) instance should be upgraded first, before each Host Controller is upgraded.
Pro ced u re 5.8. Up g rad e t o t h e lat est JBo ss EAP 6 release
1. Run the following command in a terminal to upgrade the installation:
[user@ host] yum update
2. Manually merge each created *. rpmnew file that contains changes into the production configuration files.
Resu lt
JBoss EAP 6 has been successfully upgraded.
Report a bug
5.3.3. Upgrade JBoss EAP Clust er from 6.2 t o 6.3
Prereq u isit es
None
Su mmary
JBoss EAP 6.3 does not support the creation of clusters where the different nodes are made up of different versions of JBoss EAP servers. Thus, a mixed cluster based on different versions is not supported and all nodes within a cluster must be the same version - 6.3.
Warning
The upgrade process for migrating traffic from a 6.2 cluster to a 6.3 cluster is therefore based on transferring all traffic to the 6.3 cluster and then shutting down the servers or nodes in the
6.2 cluster.
4 3
JBoss Ent erprise Applicat ion Plat form 6 .3 Inst allat ion G uide
Pro ced u re 5.9 . Set u p a JBo ss EAP Clu st er in 6 .3
1. Refer to the HTTP Clustering and Load Balancing chapter of the JBoss EAP 6.3 Administration and
Configuration Guide for instructions on how to setup a JBoss EAP cluster in 6.3.
2. Migrate all traffic to this new cluster using the steps outlined in the Migrate Traffic between
Clusters chapter of the JBoss EAP 6.3 Administration and Configuration Guide
Resu lt
Your JBoss EAP 6.2 cluster has been migrated to a cluster based on JBoss EAP 6.3.
Report a bug
4 4
Reference Mat erial
Reference Material
A.1. Available Downloads for JBoss EAP 6
JBoss EAP 6 includes a number of different installation types and optional components, which are available for download on the Red Hat Customer Portal at https://access.redhat.com/ . The following table explains the different options. Some components are only appropriate for certain operating systems or architectures, and thus are only available for those specific variations.
T ab le A.1. Availab le Do wn lo ad s
Name
Apache HTTP Server
Native Components
Native Utilities
Webserver Connector Natives
Javadocs
Descrip t io n
A standalone Apache HTTP server instance for each supported operating system and architecture. This HTTP server has been tested and verified to work with JBoss EAP
6.
Components which have been compiled to be optimized for a specific platform. For instance,
DLLs are provided for Microsoft
Windows Server environments.
In some cases, the native components may provide performance improvements.
Utilities specific to each supported operating system and architecture, such as scripts and utilities for installing JBoss EAP 6 as a service in your operating system and generating SSL encryption keys and certificates.
Pre-compiled modules for
Apache, Microsoft, and Oracle iPlanet web servers, for HTTP load balancing and highavailability capabilities. These binaries are extensively tested and known to work well with
JBoss EAP 6.
Documentation for all public
APIs exposed by JBoss EAP 6.
You can install these into your local HTTP server or IDE, or can view them on your local machine.
O p erat in g Syst ems
Red Hat Enterprise Linux 5, Red
Hat Enterprise Linux 6,
Microsoft Windows Server
2008, Solaris 10 and 11
Red Hat Enterprise Linux 5, Red
Hat Enterprise Linux 6,
Microsoft Windows Server
2008, Solaris 10 and 11,
Hewlett-Packard HP-UX
Red Hat Enterprise Linux 5, Red
Hat Enterprise Linux 6,
Microsoft Windows Server
2008, Solaris 10 and 11,
Hewlett-Packard HP-UX
Red Hat Enterprise Linux 5, Red
Hat Enterprise Linux 6,
Microsoft Windows Server
2008, Solaris 10 and 11,
Hewlett-Packard HP-UX
Platform-independent
4 5
JBoss Ent erprise Applicat ion Plat form 6 .3 Inst allat ion G uide
Name
Installer
Maven Repository
Quickstarts
Source Code
Application Platform
Descrip t io n
Java installer for JBoss EAP 6.
Includes steps to install the
Quickstarts and Maven
Repository.
A Maven repository which you can download and make available in your local development environment, and which contains artifacts common to applications built upon JBoss EAP 6. The Maven repository is also available through the JBoss EAP 6
Installer.
Example applications to help you get started developing
Java EE 6 applications with
APIs supplied with JBoss EAP
6. The Quickstarts are also available through the JBoss
EAP 6 Installer.
The Java source code for
JBoss EAP 6, provided so that you can recompile it in your own environment or audit it yourself.
The Z ip installation package, which can be installed and run on every supported platform.
This is the most common way to install JBoss EAP 6.
O p erat in g Syst ems
Platform-independent
Platform-independent
Platform-independent
Platform-independent
Platform-independent
Important
The RPM installation method's downloads are not available on the Customer Portal, but via the Red Hat Network (RHN).
Report a bug
A.2. Direct ory St ruct ure of JBoss EAP 6
Su mmary
JBoss EAP 6 includes a simplified directory structure, compared to previous versions. This topic contains a listing of the directories, and a description of what each directory contains.
It also includes directory structures of the stand al o ne/ and d o mai n/ folders.
T ab le A.2. T o p - level d irect o ries an d f iles
4 6
Reference Mat erial
Name
appclient/ bin/ bundles/ docs/ domain/ modules/ standalone/ welcome-content/
.installation/
Pu rp o se
Contains configuration details for the application client container.
Contains start-up scripts for JBoss EAP 6 on
Red Hat Enterprise Linux and Microsoft
Windows.
Contains OSGi bundles which pertain to JBoss
EAP 6 internal functionality.
License files, schemas, and examples.
Configuration files, deployment content, and writable areas used when JBoss EAP 6 runs as a managed domain.
Modules which are dynamically loaded by
JBoss EAP 6 when services request them.
Configuration files, deployment content, and writable areas used when JBoss EAP 6 runs as a standalone server.
Contains content used by the Welcome web application which is available on port 8080 of a default installation.
Contains metadata for the patching mechanism.
No modifications are required for the contents of this directory.
The bootstrapping mechanism which loads modules.
Contains license agreement details.
Contains license details.
Contains version details.
jbo ss-mo d ul es. jar
JBo ssEULA. txt
LIC ENSE. txt versi o n. txt
T ab le A.3. Direct o ries wit h in t h e d o mai n/ d irect o ry
Name
configuration/ data/ log/ servers/ tmp/
Pu rp o se
Configuration files for the managed domain.
These files are modified by the Management
Console and Management CLI, and are not meant to be edited directly.
Information about deployed services. Services are deployed using the Management Console and Management CLI, rather than by a deployment scanner. Therefore, do not place files in this directory manually.
Contains the run-time log files for the host and process controllers which run on the local instance.
Contains the equivalent d ata/, l o g /, and
tmp/ directories for each server instance in a domain, which contain similar data to the same directories within the top-level d o mai n/ directory.
Contains temporary data such as files pertaining to the shared-key mechanism used by the Management CLI to authenticate local users to the managed domain.
4 7
JBoss Ent erprise Applicat ion Plat form 6 .3 Inst allat ion G uide
T ab le A.4 . Direct o ries wit h in t h e stand al o ne/ d irect o ry
Name
configuration/ data/ deployments/ lib/ log/ tmp/
Pu rp o se
Configuration files for the standalone server.
These files are modified by the Management
Console and Management CLI, and are not meant to be edited directly.
Information about deployed services. Services are deployed using the Management Console and Management CLI, rather than by a deployment scanner. Therefore, do not place files in this directory manually.
Information about deployed services. The standalone server does include a deployment scanner, so you can place archives in this directory to be deployed. However, the recommended approach is to manage deployments using the Management Console or
Management CLI.
External libraries which pertain to a standalone server mode. Empty by default.
Contains the run-time log files for the host and process controllers which run on the local instance.
Contains temporary data such as files pertaining to the shared-key mechanism used by the Management CLI to authenticate local users to the server.
Report a bug
A.3. RPM Package List for JBoss EAP 6
Su mmary
JBoss EAP 6 is installed on Red Hat Enterprise Linux 6 using the YUM package group JBo ss EAP
6 . That group is made up of the following packages.
T ab le A.5. Packag e List
Packag e
jbossas-appclient jbossas-bundles jbossas-core jbossas-domain jbossas-hornetq-native jbossas-jbossweb-native jbossas-modules-eap jbossas-product-eap jbossas-standalone
Descrip t io n
JEE Application Client Container
OSGi bundles
Core components. This is required for all configurations.
Domain configuration
Container for the JBoss AS HornetQ files
JBoss Enterprise Web Platform
JBoss EAP modules
Product configuration components. This customizes product execution.
Standalone configuration
4 8
Packag e
jbossas-welcome-content-eap
Reference Mat erial
Descrip t io n
Welcome content used in startup messages and console pages
Important
The jbo ssas-ho rnetq -nati ve package is included for high availability in JBoss EAP 6 but it is not activated by default.
Report a bug
A.4 . RPM Inst allat ion Configurat ion Files for JBoss EAP 6
Su mmary
The RPM installation of JBoss EAP 6 includes three additional configuration files to the Z IP installation. These files are used by the service init script to specify the application server's launch environment. One of these files applies to all JBoss EAP 6 instances, while the other two provide overrides for standalone and domain mode servers.
T ab le A.6 . Ad d it io n al RPM Co n f ig u rat io n Files
File Descrip t io n
/etc/jbo ssas/jbo ssas. co nf
This file is read first and applies to all JBoss EAP 6 instances.
/etc/sysco nfi g /jbo ssas
Settings specific to standalone servers. Values specified here will override those in jbossas.conf when running as a standalone server.
/etc/sysco nfi g /jbo ssasd o mai n
Settings specific to domain-mode servers. Values specified here will override those in jbossas.conf when running as a domainmode server.
The following table shows a list of available configuration properties along with their default values.
T ab le A.7. RPM In st allat io n Co n f ig u rat io n Pro p ert ies
Pro p ert y
JBO SS_USER
JBO SS_G R O UP
JBO SS_ST AR T UP _WA
IT
Descrip t io n
The system user account that the JBoss EAP 6 runs as. This user also has ownership of the files.
Default value: jbo ss
The system user group that the JBoss EAP 6 files belong to.
Default value: jbo ss
The number of seconds that the init script will wait until confirming that the server has launched successfully after receiving a start or restart command.
Default value: 6 0
4 9
JBoss Ent erprise Applicat ion Plat form 6 .3 Inst allat ion G uide
Pro p ert y
JBO SS_SHUT D O WN_W
AIT
Descrip t io n
The number of seconds that the init script will wait for the server to shutdown before continuing when it receives a sto p or restart command.
Default value: 20
JBO SS_C O NSO LE_LO
G
JAVA_HO ME
JBO SS_HO ME
JAVAP T H
JBO SSC O NF
JBO SSSH
JBO SS_SER VER _C O N
FIG
JBO SS_HO ST _C O NFI
G
Report a bug
The file that the CONSOLE log handler will be redirected to.
Default value: /var/l o g /jbo ssas/$JBOSSCONF/co nso l e. l o g
The directory where your Java Runtime Environment is installed.
Default value: /usr/l i b/jvm/jre
The directory where the application server files are installed.
Default value: /usr/share/jbo ssas
The path where the Java executable files are installed.
Default value: $JAVA_HOME/bi n
The server mode to launch this server in, stand al o ne or d o mai n.
Default value: stand al o ne or d o mai n depending on server mode.
The script which is used to launch to server.
Default value: $JBO SS_HO ME/bi n/$JBO SSC O NF. sh
The server configuration file to use.
There is no default for this property. Either stand al o ne. xml or
d o mai n. xml can be defined at start.
This property allows a user to specify the host configuration (such as
ho st. xml ). It has no value set as the default.
50
Installer Screenshots
B.1. Language Select ion
Inst aller Screenshot s
Fig u re B.1. JBo ss EAP In st allat io n Pro g ram Lan g u ag e Select io n
Report a bug
B.2. End User License Agreement
51
JBoss Ent erprise Applicat ion Plat form 6 .3 Inst allat ion G uide
Fig u re B.2. JBo ss EAP In st allat io n Pro g ram En d User Licen se Ag reemen t
Report a bug
B.3. Inst allat ion Pat h
52
Inst aller Screenshot s
Fig u re B.3. JBo ss EAP In st allat io n Pro g ram In st allat io n Pat h
Report a bug
B.4 . Select t he Packs t o Inst all
Select or deselect the packs to install. Required packs are disabled for deselection.
53
JBoss Ent erprise Applicat ion Plat form 6 .3 Inst allat ion G uide
Fig u re B.4 . JBo ss EAP In st allat io n Pro g ram Select Packs t o In st all
Report a bug
B.5. Administ rat ive User Creat ion
54
Inst aller Screenshot s
Fig u re B.5. JBo ss EAP In st allat io n Pro g ram Ad min ist rat ive User Creat io n
Report a bug
B.6. Quickst art Inst allat ion
55
JBoss Ent erprise Applicat ion Plat form 6 .3 Inst allat ion G uide
Fig u re B.6 . JBo ss EAP In st allat io n Pro g ram Q u ickst art Set u p
Report a bug
B.7. Maven Reposit ory Set up
56
Inst aller Screenshot s
Fig u re B.7. JBo ss EAP In st allat io n Pro g ram Maven Rep o sit o ry Set u p
Report a bug
B.8. Socket Binding Set up
Determine whether to use the default bindings, or configure custom bindings.
57
JBoss Ent erprise Applicat ion Plat form 6 .3 Inst allat ion G uide
Fig u re B.8. JBo ss EAP In st allat io n Pro g ram Def au lt So cket Bin d in g s
58
Inst aller Screenshot s
Fig u re B.9 . JBo ss EAP In st allat io n Pro g ram Cu st o m Po rt So cket Bin d in g s
59
JBoss Ent erprise Applicat ion Plat form 6 .3 Inst allat ion G uide
Fig u re B.10. JBo ss EAP In st allat io n Pro g ram Co n f ig u re O f f set f o r Def au lt So cket
Bin d in g s
Report a bug
B.9. Cust om Socket Bindings for St andalone Configurat ions
The following sequence of screens appear if you choose to configure custom port bindings for standalone mode.
60
Inst aller Screenshot s
Fig u re B.11. JBo ss EAP In st aller St an d alo n e So cket Bin d in g Co n f ig u rat io n
61
JBoss Ent erprise Applicat ion Plat form 6 .3 Inst allat ion G uide
Fig u re B.12. JBo ss EAP In st aller St an d alo n e HA So cket Bin d in g Co n f ig u rat io n
62
Inst aller Screenshot s
Fig u re B.13. JBo ss EAP In st aller St an d alo n e Fu ll St an d alo n e So cket Bin d in g
Co n f ig u rat io n
63
JBoss Ent erprise Applicat ion Plat form 6 .3 Inst allat ion G uide
Fig u re B.14 . JBo ss EAP In st aller St an d alo n e Fu ll HA St an d alo n e So cket Bin d in g
Co n f ig u rat io n
Report a bug
B.10. Cust om Socket Bindings for Domain Configurat ions
The following sequence of screens appear if you choose to configure custom port bindings for domain mode.
64
Inst aller Screenshot s
Fig u re B.15. JBo ss EAP In st aller Do main Ho st So cket Bin d in g Co n f ig u rat io n
65
JBoss Ent erprise Applicat ion Plat form 6 .3 Inst allat ion G uide
Fig u re B.16 . JBo ss EAP In st aller Def au lt Do main So cket Bin d in g Co n f ig u rat io n
66
Inst aller Screenshot s
Fig u re B.17. JBo ss EAP In st aller HA Do main So cket Bin d in g Co n f ig u rat io n
67
JBoss Ent erprise Applicat ion Plat form 6 .3 Inst allat ion G uide
Fig u re B.18. JBo ss EAP In st aller Fu ll Do main So cket Bin d in g Co n f ig u rat io n
68
Inst aller Screenshot s
Fig u re B.19 . JBo ss EAP In st aller Fu ll HA Do main So cket Bin d in g Co n f ig u rat io n
Report a bug
B.11. Server Launch
69
JBoss Ent erprise Applicat ion Plat form 6 .3 Inst allat ion G uide
Fig u re B.20. JBo ss EAP In st allat io n Pro g ram Server Lau n ch
Report a bug
B.12. Configure Logging Levels
70
Inst aller Screenshot s
Fig u re B.21. JBo ss EAP In st allat io n Pro g ram Co n f ig u re Lo g g in g Levels
Report a bug
B.13. Configure Runt ime Environment
Choose P erfo rm ad vanced co nfi g urati o n to customize installation and configuration of security, caching, LDAP, and datasource options.
71
JBoss Ent erprise Applicat ion Plat form 6 .3 Inst allat ion G uide
Fig u re B.22. JBo ss EAP In st allat io n Pro g ram Co n f ig u re Ru n t ime En viro n men t - Def au lt
72
Inst aller Screenshot s
Fig u re B.23. JBo ss EAP In st allat io n Pro g ram Co n f ig u re Ru n t ime En viro n men t -
Ad van ced
Report a bug
B.14 . Password Vault Configurat ion
73
JBoss Ent erprise Applicat ion Plat form 6 .3 Inst allat ion G uide
Fig u re B.24 . JBo ss EAP In st all Passwo rd Vau lt Co n f ig u rat io n
Report a bug
B.15. Configure SSL Securit y
74
Inst aller Screenshot s
Fig u re B.25. JBo ss EAP In st all Co n f ig u re SSL Secu rit y
Report a bug
B.16. Configure LDAP
75
JBoss Ent erprise Applicat ion Plat form 6 .3 Inst allat ion G uide
Fig u re B.26 . JBo ss EAP In st all LDAP Co n f ig u rat io n
Report a bug
B.17. Infinispan Configurat ion
76
Inst aller Screenshot s
Fig u re B.27. JBo ss EAP In st all In f in isp an Co n f ig u rat io n
Report a bug
B.18. Securit y Domain Configurat ion
77
JBoss Ent erprise Applicat ion Plat form 6 .3 Inst allat ion G uide
78
Inst aller Screenshot s
Fig u re B.28. JBo ss EAP In st all Secu rit y Do main Co n f ig u rat io n
Report a bug
B.19. JDBC Driver Set up
79
JBoss Ent erprise Applicat ion Plat form 6 .3 Inst allat ion G uide
Fig u re B.29 . JBo ss EAP In st all Co n f ig u re a JDBC Driver
Report a bug
B.20. Dat asource Set up
80
Inst aller Screenshot s
Fig u re B.30. JBo ss EAP In st all Dat aso u rce Set u p
Report a bug
B.21. Review Inst allat ion Component s
81
JBoss Ent erprise Applicat ion Plat form 6 .3 Inst allat ion G uide
Fig u re B.31. JBo ss EAP In st allat io n Pro g ram Review Select ed Co mp o n en t s
Report a bug
B.22. Inst allat ion Progress
82
Inst aller Screenshot s
Fig u re B.32. JBo ss EAP In st allat io n Pro g ram Co mp o n en t In st allat io n Pro g ress
Report a bug
B.23. Inst allat ion Processing Finished
83
JBoss Ent erprise Applicat ion Plat form 6 .3 Inst allat ion G uide
Fig u re B.33. JBo ss EAP In st allat io n Pro g ram Pro cessin g Fin ish ed
Report a bug
B.24 . Creat e Short cut s
84
Inst aller Screenshot s
Fig u re B.34 . JBo ss EAP In st aller Creat e Sh o rt cu t s
Report a bug
B.25. Generat e Inst all Script
85
JBoss Ent erprise Applicat ion Plat form 6 .3 Inst allat ion G uide
Fig u re B.35. JBo ss EAP In st allat io n Pro g ram G en erat e In st all Scrip t
Report a bug
86
Revision Hist ory
Revision History
Revisio n 6 .3.0- 50 T u esd ay No vemb er 18 2014 Ru ssell Dicken so n
Red Hat JBoss Enterprise Application Platform 6.3.0 Continuous Release
Revisio n 6 .3.0- 32 Frid ay Au g u st 8 2014 Lu cas Co st i
Red Hat JBoss Enterprise Application Platform 6.3.0 Continuous Release
Revisio n 6 .3.0- 30 Mo n d ay Au g u st 4 2014
Red Hat JBoss Enterprise Application Platform 6.3.0.GA
San d e G ild a
87
advertisement
Key Features
- Java Enterprise Edition 6 certified
- Centralized server management
- Simplified directory layout
- Modular classloading mechanism
- Streamlined datasource management
- Reduced resource use
- Improved performance
