JBoss Enterprise Application Platform 6 Installation Guide en US

JBoss EnterpriseApplication Platform 6

Installation GuideFor Use with JBoss Enterprise Application Platform 6

Sande Gilda

Eamon Logue

Darrin Mison

David Ryan

Misty Stanley-Jones

Tom Wells

Installation Guide

JBoss Enterprise Application Platform 6 Installation GuideFor Use with JBoss Enterprise Application Platform 6Edition 2

Author Sande GildaAuthor Eamon LogueAuthor Darrin MisonAuthor David RyanAuthor Misty Stanley-JonesAuthor Tom Wells

Copyright © 2012 Red Hat, Inc..

The text of and illustrations in this document are licensed by Red Hat under a Creative CommonsAttribution–Share Alike 3.0 Unported license ("CC-BY-SA"). An explanation of CC-BY-SA is availableat http://creativecommons.org/licenses/by-sa/3.0/. In accordance with CC-BY-SA, if you distribute thisdocument or an adaptation of it, you must provide the URL for the original version.

Red Hat, as the licensor of this document, waives the right to enforce, and agrees not to assert,Section 4d of CC-BY-SA to the fullest extent permitted by applicable law.

Red Hat, Red Hat Enterprise Linux, the Shadowman logo, JBoss, MetaMatrix, Fedora, the InfinityLogo, and RHCE are trademarks of Red Hat, Inc., registered in the United States and other countries.

Linux® is the registered trademark of Linus Torvalds in the United States and other countries.

Java® is a registered trademark of Oracle and/or its affiliates.

XFS® is a trademark of Silicon Graphics International Corp. or its subsidiaries in the United Statesand/or other countries.

MySQL® is a registered trademark of MySQL AB in the United States, the European Union and othercountries.

All other trademarks are the property of their respective owners.

This book is a guide to the installation of JBoss Enterprise Application Platform 6 and its patchreleases.

http://creativecommons.org/licenses/by-sa/3.0/

iii

Preface v1. Document Conventions ................................................................................................... v

1.1. Typographic Conventions ...................................................................................... v1.2. Pull-quote Conventions ........................................................................................ vi1.3. Notes and Warnings ............................................................................................ vii

2. Getting Help and Giving Feedback ................................................................................. vii2.1. Do You Need Help? ............................................................................................ vii2.2. Give us Feedback .............................................................................................. viii

1. JBoss Enterprise Application Platform 6 11.1. Introducing JBoss Enterprise Application Platform 6 ....................................................... 1

1.1.1. Introducing JBoss Enterprise Application Platform 6 ............................................. 11.1.2. New and Changed Features in JBoss Enterprise Application Platform 6 ................. 1

1.2. Downloading JBoss Enterprise Application Platform 6 .................................................... 21.2.1. Download JBoss Enterprise Application Platform 6 .............................................. 21.2.2. Available Downloads for JBoss Enterprise Application Platform 6 .......................... 21.2.3. About the Red Hat Customer Portal ................................................................... 4

1.3. Preparing to Install JBoss Enterprise Application Platform 6 ............................................ 51.3.1. Installation Prerequisites for JBoss Enterprise Application Platform 6 ..................... 51.3.2. Java Environments Supported By JBoss Enterprise Application Platform 6 ............ 51.3.3. Install OpenJDK on Red Hat Enterprise Linux ..................................................... 5

1.4. Installing JBoss Enterprise Application Platform 6 .......................................................... 71.4.1. Installation Methods for JBoss Enterprise Application Platform 6 ........................... 71.4.2. Install JBoss Enterprise Application Platform 6 Using the Installer Method .............. 81.4.3. Install JBoss Enterprise Application Platform 6 Using the ZIP Download ................ 91.4.4. Install JBoss Enterprise Application Platform 6 using the Red Hat Network(RPM installation) ...................................................................................................... 101.4.5. Installation Structure and Details ...................................................................... 11

1.5. Running JBoss Enterprise Application Platform 6 as a Service ...................................... 131.5.1. Run JBoss Enterprise Application Platform 6 as an Operating System Service ...... 131.5.2. Install JBoss Enterprise Application Platform as a Service in Red Hat EnterpriseLinux ........................................................................................................................ 131.5.3. Install JBoss Enterprise Application Platform 6 as a Service in MicrosoftWindows ................................................................................................................... 15

1.6. Getting Started with JBoss Enterprise Application Platform 6 ......................................... 161.6.1. Add the Initial User for the Management Interfaces ............................................ 161.6.2. Start JBoss Enterprise Application Platform 6 .................................................... 181.6.3. Start JBoss Enterprise Application Platform 6 as a Managed Domain .................. 191.6.4. Start JBoss Enterprise Application Platform 6 as a Standalone Server ................. 191.6.5. Running JBoss Enterprise Application Platform 6 as a Service ............................ 20

1.6.5.1. Run JBoss Enterprise Application Platform 6 as an Operating SystemService ............................................................................................................. 201.6.5.2. Install JBoss Enterprise Application Platform as a Service in Red HatEnterprise Linux ................................................................................................ 201.6.5.3. Install JBoss Enterprise Application Platform 6 as a Service in MicrosoftWindows ........................................................................................................... 22

1.6.6. Test the Installation .......................................................................................... 231.6.7. Network Ports Used By JBoss Enterprise Application Platform 6 ......................... 241.6.8. Configure Network Firewalls to Work with JBoss Enterprise Application Platform6 .............................................................................................................................. 261.6.9. Default User Security Configuration .................................................................. 29

1.7. Uninstalling JBoss Enterprise Application Platform 6 ..................................................... 301.7.1. Uninstall JBoss Enterprise Application Platform 6 .............................................. 301.7.2. Uninstall JBoss Enterprise Application Platform 6 From a Zip Installation ............. 30

Installation Guide

iv

1.7.3. Uninstall JBoss Enterprise Application Platform 6 From a Graphical Installation .... 311.7.4. Uninstall JBoss Enterprise Application Platform 6 From an RPM Installation ......... 31

A. Revision History 33

v

Preface

1. Document ConventionsThis manual uses several conventions to highlight certain words and phrases and draw attention tospecific pieces of information.

In PDF and paper editions, this manual uses typefaces drawn from the Liberation Fonts1 set. TheLiberation Fonts set is also used in HTML editions if the set is installed on your system. If not,alternative but equivalent typefaces are displayed. Note: Red Hat Enterprise Linux 5 and later includesthe Liberation Fonts set by default.

1.1. Typographic ConventionsFour typographic conventions are used to call attention to specific words and phrases. Theseconventions, and the circumstances they apply to, are as follows.

Mono-spaced Bold

Used to highlight system input, including shell commands, file names and paths. Also used to highlightkeycaps and key combinations. For example:

To see the contents of the file my_next_bestselling_novel in your currentworking directory, enter the cat my_next_bestselling_novel command at theshell prompt and press Enter to execute the command.

The above includes a file name, a shell command and a keycap, all presented in mono-spaced boldand all distinguishable thanks to context.

Key combinations can be distinguished from keycaps by the hyphen connecting each part of a keycombination. For example:

Press Enter to execute the command.

Press Ctrl+Alt+F2 to switch to the first virtual terminal. Press Ctrl+Alt+F1 toreturn to your X-Windows session.

The first paragraph highlights the particular keycap to press. The second highlights two keycombinations (each a set of three keycaps with each set pressed simultaneously).

If source code is discussed, class names, methods, functions, variable names and returned valuesmentioned within a paragraph will be presented as above, in mono-spaced bold. For example:

File-related classes include filesystem for file systems, file for files, and dir fordirectories. Each class has its own associated set of permissions.

Proportional Bold

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 sub-menu titles. For example:

Choose System → Preferences → Mouse from the main menu bar to launch MousePreferences. In the Buttons tab, click the Left-handed mouse check box and click

1 https://fedorahosted.org/liberation-fonts/

https://fedorahosted.org/liberation-fonts/

https://fedorahosted.org/liberation-fonts/

Preface

vi

Close to switch the primary mouse button from the left to the right (making the mousesuitable for use in the left hand).

To insert a special character into a gedit file, choose Applications → Accessories→ Character Map from the main menu bar. Next, choose Search → Find… from theCharacter Map menu bar, type the name of the character in the Search field and clickNext. The character you sought will be highlighted in the Character Table. Double-click this highlighted character to place it in the Text to copy field and then click the

Copy button. Now switch back to your document and choose Edit → Paste from thegedit menu bar.

The above text includes application names; system-wide menu names and items; application-specificmenu names; and buttons and text found within a GUI interface, all presented in proportional bold andall distinguishable by context.

Mono-spaced Bold Italic or Proportional Bold Italic

Whether mono-spaced bold or proportional bold, the addition of italics indicates replaceable orvariable text. Italics denotes text you do not input literally or displayed text that changes depending oncircumstance. For example:

To connect to a remote machine using ssh, type ssh [email protected] ata shell prompt. If the remote machine is example.com and your username on thatmachine is john, type ssh [email protected].

The mount -o remount file-system command remounts the named filesystem. For example, to remount the /home file system, the command is mount -oremount /home.

To see the version of a currently installed package, use the rpm -q packagecommand. It will return a result as follows: package-version-release.

Note the words in bold italics above — username, domain.name, file-system, package, version andrelease. Each word is a placeholder, either for text you enter when issuing a command or for textdisplayed by the system.

Aside from standard usage for presenting the title of a work, italics denotes the first use of a new andimportant term. For example:

Publican is a DocBook publishing system.

1.2. Pull-quote ConventionsTerminal output and source code listings are set off visually from the surrounding text.

Output sent to a terminal is set in mono-spaced roman and presented thus:

books Desktop documentation drafts mss photos stuff svnbooks_tests Desktop1 downloads images notes scripts svgs

Source-code listings are also set in mono-spaced roman but add syntax highlighting as follows:

package org.jboss.book.jca.ex1;

import javax.naming.InitialContext;

Notes and Warnings

vii

public class ExClient{ public static void main(String args[]) throws Exception { InitialContext iniCtx = new InitialContext(); Object ref = iniCtx.lookup("EchoBean"); EchoHome home = (EchoHome) ref; Echo echo = home.create();

System.out.println("Created Echo");

System.out.println("Echo.echo('Hello') = " + echo.echo("Hello")); }}

1.3. Notes and WarningsFinally, 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 shouldhave 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 tothe current session, or services that need restarting before an update will apply. Ignoring a boxlabeled '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. Getting Help and Giving Feedback

2.1. Do You Need Help?

If you experience difficulty with a procedure described in this documentation, visit the Red HatCustomer 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).

http://access.redhat.com

Preface

viii

• access other product documentation.

Red Hat also hosts a large number of electronic mailing lists for discussion of Red Hat software andtechnology. 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. Give us Feedback

If you find a typographical error, or know how this guide can be improved, we would love to hear fromyou. Submit a report in Bugzilla against the product JBoss Enterprise Application Platformand the component documentation. The following link will take you to a pre-filled bug report for thisproduct: https://bugzilla.redhat.com/.

Fill out the following template in Bugzilla's Description field. Be as specific as possible whendescribing the issue; this will help ensure that we can fix it quickly.

Document URL:

Section Number and Name:

Describe the issue:

Suggestions for improvement:

Additional information:

Be sure to give us your name so that you can receive full credit for reporting the issue.

https://www.redhat.com/mailman/listinfo

https://www.redhat.com/mailman/listinfo

Chapter 1.

1

JBoss Enterprise Application Platform6

1.1. Introducing JBoss Enterprise Application Platform 6

1.1.1. Introducing JBoss Enterprise Application Platform 6JBoss Enterprise Application Platform 6 is a middleware platform built on open standards, andcompliant with Java EE. It integrates JBoss Application Server 7 with high-availability clustering,powerful messaging, distributed caching, and other technologies to create a stable, scalable, andfast platform. In addition, it also includes APIs and development frameworks you can use to developsecure, powerful, and scalable Java EE applications quickly.

Report a bug1

1.1.2. New and Changed Features in JBoss Enterprise ApplicationPlatform 6• JBoss Enterprise Application Platform 6 is a certified implementation of the Java Enterprise Edition

6 Full Profile and Web Profile specifications.

• A Managed Domain provides centralized management of multiple server instances and physicalhosts, while a Standalone Server allows for a single server instance.

• Configurations, deployments, socket bindings, modules, extensions, and system properties can allbe managed per server group.

• The Management Console and Management CLI are brand new interfaces for managing yourdomain or standalone JBoss Enterprise Application Platform 6 instance. There is no longer anyneed to edit XML configuration files by hand. The Management CLI even offers batch mode, so thatyou can script and automate management tasks.

• Application security, including security domains, are managed centrally for simplified configuration.

• The directory layout of JBoss Enterprise Application Platform 6 has been simplified. The modules/directory now contains the application server modules, instead of using common and server-specific lib/ directories. The domain/ and standalone/ directories contain the artifacts andconfiguration files for domain and standalone deployments.

• The classloading mechanism has been made completely modular, so that modules are loaded andunloaded on demand. This provides performance and security benefits, as well as very fast start-upand restart times.

1 https://bugzilla.redhat.com/enter_bug.cgi?cf_environment=Instance+Name%3A+Not+Defined%0ABuild%3A+CSProcessor+Builder+Version+1.5%0ABuild+Filter%3A+null%0ABuild+Name%3A+%0ABuild+Date%3A+31-07-2012+11%3A58%3A00&cf_build_id=228-155458+31+Jul+2012+11%3A58+en-US&assigned_to=misty%40redhat.com&product=JBoss+Enterprise+Application+Platform+6&component=documentation&version=6.0&keywords=Documentation

https://bugzilla.redhat.com/enter_bug.cgi?cf_environment=Instance+Name%3A+Not+Defined%0ABuild%3A+CSProcessor+Builder+Version+1.5%0ABuild+Filter%3A+null%0ABuild+Name%3A+%0ABuild+Date%3A+31-07-2012+11%3A58%3A00&cf_build_id=228-155458+31+Jul+2012+11%3A58+en-US&assigned_to=misty%40redhat.com&product=JBoss+Enterprise+Application+Platform+6&component=documentation&version=6.0&keywords=Documentation






Chapter 1. JBoss Enterprise Application Platform 6

2

• Datasource management is streamlined. Database drivers can be deployed just like other services.In addition, datasources are created and managed directly in the Management Console orManagement CLI.

• JBoss Enterprise Application Platform 6 starts and stops very quickly, which is especially beneficialto developers. It uses fewer resources and is extremely efficient in its use of system resources.

Report a bug2

1.2. Downloading JBoss Enterprise Application Platform 6

1.2.1. Download JBoss Enterprise Application Platform 6

1. Log into the Customer Service Portal at http://access.redhat.com.

2. Click the Downloads link, and browse to JBoss Enterprise Middleware.

3. Select Enterprise Application Platform.

4. Locate the appropriate version, platform, file type (Zip archive, RPM, or native installation file) andsystem architecture (32-bit or 64-bit), and click the Download link.

5. Download any supplemental packages you need, such as the Quickstarts, Maven Repository,HTTP Connectors, or Native binaries.

ResultThe JBoss Enterprise Application Platform 6 file that you selected is downloaded to your computer,along with any supplemental downloads you have selected.

Report a bug3

1.2.2. Available Downloads for JBoss Enterprise ApplicationPlatform 6JBoss Enterprise Application Platform 6 includes a number of different installation types andoptional 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 onlyappropriate for certain operating systems or architectures, and thus are only available for thosespecific variations.

2 https://bugzilla.redhat.com/enter_bug.cgi?cf_environment=Instance+Name%3A+Not+Defined%0ABuild%3A+CSProcessor+Builder+Version+1.5%0ABuild+Filter%3A+null%0ABuild+Name%3A+%0ABuild+Date%3A+31-07-2012+11%3A58%3A00&cf_build_id=229-164507+31+Jul+2012+11%3A58+en-US&assigned_to=misty%40redhat.com&product=JBoss+Enterprise+Application+Platform+6&component=documentation&version=6.0&keywords=Documentation3 https://bugzilla.redhat.com/enter_bug.cgi?cf_environment=Instance+Name%3A+Not+Defined%0ABuild%3A+CSProcessor+Builder+Version+1.5%0ABuild+Filter%3A+null%0ABuild+Name%3A+%0ABuild+Date%3A+31-07-2012+11%3A58%3A00&cf_build_id=40-155458+31+Jul+2012+11%3A58+en-US&assigned_to=dryan%40redhat.com&product=JBoss+Enterprise+Application+Platform+6&component=documentation&version=6.0&keywords=Documentation



https://bugzilla.redhat.com/enter_bug.cgi?cf_environment=Instance+Name%3A+Not+Defined%0ABuild%3A+CSProcessor+Builder+Version+1.5%0ABuild+Filter%3A+null%0ABuild+Name%3A+%0ABuild+Date%3A+31-07-2012+11%3A58%3A00&cf_build_id=40-155458+31+Jul+2012+11%3A58+en-US&assigned_to=dryan%40redhat.com&product=JBoss+Enterprise+Application+Platform+6&component=documentation&version=6.0&keywords=Documentation

https://access.redhat.com/

https://access.redhat.com/











Available Downloads for JBoss Enterprise Application Platform 6

3

Table 1.1. Available Downloads for JBoss Enterprise Application Platform 6

Name Description Operating Systems

Apache HTTP Server A stand-alone Apache HTTPserver instance for eachsupported operating systemand architecture. This HTTPserver has been tested andverified to work with JBossEnterprise Application Platform6.

Red Hat Enterprise Linux 5,Red Hat Enterprise Linux 6,Microsoft Windows Server2008, Solaris 10 and 11

Native Components Components which have beencompiled to be optimized for aspecific platform. For instance,DLLs are provided for MicrosoftWindows Server environments.In some cases, the nativecomponents may provideperformance improvements.


Native Utilities Utilities specific to eachsupported operating systemand architecture, such asscripts and utilities for installingJBoss Enterprise ApplicationPlatform as a service inyour operating system andgenerating SSL encryptionkeys and certificates.


Webserver Connector Natives Pre-compiled modules forApache, Microsoft, andNetscape HTTPD servers, forHTTP load balancing and high-availability capabilities. Thesebinaries are extensively testedand known to work well withJBoss Enterprise ApplicationPlatform 6.


Javadocs Documentation for all publicAPIs exposed by JBossEnterprise Application Platform6. You can install these intoyour local HTTP server or IDE,or can view them on your localmachine.

Platform-independent

Installer Java graphical installer forJBoss Enterprise ApplicationPlatform 6


Maven Repository A Maven repository whichyou can download andmake available in your localdevelopment environment,and which contains artifacts



4

Name Description Operating Systemscommon to applicationsbuilt upon JBoss EnterpriseApplication Platform 6.

Quickstarts Example applications to helpyou get started developingJava EE 6 applications withAPIs supplied with JBossEnterprise Application Platform6.


Source Code The Java source code forJBoss Enterprise ApplicationPlatform 6, provided so thatyou can recompile it in yourown environment or audit ityourself.


Application Platform The ZIP installation packagewhich can be installed and runon every supported platform.This is the most common wayto install JBoss EnterpriseApplication Platform 6.


Note - RPM Installation The RPM installation method'sdownloads are not availableon the Customer Portal, but viathe Red Hat Network (RHN).To install JBoss EnterpriseApplication Platform 6 via RPM,refer to the following topic:Section 1.4.4, “Install JBossEnterprise Application Platform6 using the Red Hat Network(RPM installation)”

Red Hat Enterprise Linux 5,Red Hat Enterprise Linux 6

Report a bug4

1.2.3. About the Red Hat Customer PortalThe Red Hat Customer Portal is a website where Red Hat customers download officially-supportedsoftware, manage entitlements and support contracts, contact Global Support services, andfile bugs against Red Hat products. The web address to access the Customer Portal is https://access.redhat.com.



https://access.redhat.com

https://access.redhat.com






Preparing to Install JBoss Enterprise Application Platform 6

5

Report a bug5

1.3. Preparing to Install JBoss Enterprise ApplicationPlatform 6

1.3.1. Installation Prerequisites for JBoss Enterprise ApplicationPlatform 6Before you can install JBoss Enterprise Application Platform 6, you need to meet the followingrequirements:

• Set up an account on the Red Hat Customer Portal at http://access.redhat.com. Refer toSection 1.2.3, “About the Red Hat Customer Portal”

• Review and make sure your computer uses a supported configuration, according to http://www.jboss.com/products/platforms/application/supportedconfigurations/.

Report a bug6

1.3.2. Java Environments Supported By JBoss EnterpriseApplication Platform 6JBoss Enterprise Application Platform 6 requires Java 6 or Java 7. The list of supportedJava environments can be found at http://www.jboss.com/products/platforms/application/supportedconfigurations/. A Java Development Kit (JDK) is required for development, and a JavaRuntime Environment (JRE) is required to run JBoss Enterprise Application Platform.

Report a bug7

1.3.3. Install OpenJDK on Red Hat Enterprise Linux

IntroductionOpenJDK is one of many Java Development Kits (JDKs) supported in Red Hat Enterprise Linuxfor use with JBoss enterprise products. This task shows you how to install OpenJDK in Red HatEnterprise Linux, and how to configure your system to use it as the default JDK.

5 https://bugzilla.redhat.com/enter_bug.cgi?cf_environment=Instance+Name%3A+Not+Defined%0ABuild%3A+CSProcessor+Builder+Version+1.5%0ABuild+Filter%3A+null%0ABuild+Name%3A+%0ABuild+Date%3A+31-07-2012+11%3A58%3A00&cf_build_id=254-155458+31+Jul+2012+11%3A58+en-US&assigned_to=misty%40redhat.com&product=JBoss+Enterprise+Application+Platform+6&component=documentation&version=6.0&keywords=Documentation6 https://bugzilla.redhat.com/enter_bug.cgi?cf_environment=Instance+Name%3A+Not+Defined%0ABuild%3A+CSProcessor+Builder+Version+1.5%0ABuild+Filter%3A+null%0ABuild+Name%3A+%0ABuild+Date%3A+31-07-2012+11%3A58%3A00&cf_build_id=234-155458+31+Jul+2012+11%3A58+en-US&assigned_to=misty%40redhat.com&product=JBoss+Enterprise+Application+Platform+6&component=documentation&version=6.0&keywords=Documentation7 https://bugzilla.redhat.com/enter_bug.cgi?cf_environment=Instance+Name%3A+Not+Defined%0ABuild%3A+CSProcessor+Builder+Version+1.5%0ABuild+Filter%3A+null%0ABuild+Name%3A+%0ABuild+Date%3A+31-07-2012+11%3A58%3A00&cf_build_id=300-155458+31+Jul+2012+11%3A58+en-US&assigned_to=misty%40redhat.com&product=JBoss+Enterprise+Application+Platform+6&component=documentation&version=6.0&keywords=Documentation



http://www.jboss.com/products/platforms/application/supportedconfigurations/






















6

Note

It is possible to install multiple JDKs on a single system.

Task PrerequisitesYou must meet the following conditions before continuing with this task:

• You must be running Red Hat Enterprise Linux 6. OpenJDK is not available or supported for RedHat Enterprise Linux 5 at this time.

• The server running Red Hat Enterprise Linux 6 must be registered with RHN and subscribed tothe base channel. Refer to the Package Management section of the Red Hat Enterprise Linux6 Deployment Guide on http://access.redhat.com/knowledge/docs/ for more information aboutmanaging subscriptions and entitlements on Red Hat Enterprise Linux systems.

1. Install the OpenJDK RPM.There are two different ways to install an RPM, depending on whether you have used acommand-line interface (CLI) or a Graphical User Interface (GUI).

From the CLIAfter logging in with administrator access, run one of the following two commands:

OpenJDK 6yum install java-1.6.0-openjdk-devel

OpenJDK 7yum install java-1.7.0-openjdk-devel

From a GUIa. In Gnome, select Administration from the System menu, and click Add / Remove

Software.

b. Search for openjdk and choose the java-1.6.0-openjdk-devel option forOpenJDK 6 or the java-1.7.0-openjdk-devel option for OpenJDK 7.

c. Click Apply to install the selected packages and dependencies.

d. When prompted, enter the administrator password to install the packages.

2. Optional: Set the JAVA_HOME environment variable.Some applications such as Apache Maven and Apache Ant require you to set the JAVA_HOMEenvironment variable. If you need to do this, follow these steps.

a. Determine the correct value for JAVA_HOME. Red Hat Enterprise Linux installs OpenJDK1.6 into either /usr/lib/jvm/java-1.6.0-openjdk-1.6.0.0/ or /usr/lib/jvm/java-1.6.0-openjdk-1.6.0.0.x86_64/, depending on whether your system is a 32-bitor 64-bit architecture. The JAVA_HOME should point to the directory containing a bin/javaexecutable.

b. As the user who will use OpenJDK, open the shell configuration file. For the Bash shell, thisfile is /home/username/.bashrc.

http://access.redhat.com/knowledge/docs/

Installing JBoss Enterprise Application Platform 6

7

c. At the bottom of the file, type the following line, replacing the hypothetical path with the actualpath to use on your own system: export JAVA_HOME="/path/to/java/home"

d. Save the file, and log out of and back into your session.

3. Switch between different OpenJDK versions using the alternatives utility.Red Hat Enterprise Linux includes a utility called alternatives, which lets you change thedefault version for applications which allow multiple versions to be installed. OpenJDK is one suchapplication.

To use the alternatives utility, perform the following steps. Note that setting the environmentvariables overrides the behavior of the alternatives command. For instance, if you use ascript which manually sets $JAVA_HOME and $JAVA variables to a different JDK from the onespecified by the alternatives command, the environment variables will override the command.

• Log in as the root user, or prefix the commands below with the sudo command.

• The alternatives command is not installed by default, but may already be installed on yoursystem. If not, install the alternatives package by running the following command:

yum install alternatives

• Issue the following command:

/usr/sbin/alternatives --config java

• Follow the prompts that follow to set the default version of OpenJDK.

Result:OpenJDK is installed on your server and available for your use. If necessarily, the JAVA_HOMEenvironment variable has been specified as well. If necessary, the default OpenJDK for your systemhas been set using the alternatives utility.

Report a bug8

1.4. Installing JBoss Enterprise Application Platform 6

1.4.1. Installation Methods for JBoss Enterprise ApplicationPlatform 6The installation choices for JBoss Enterprise Application Platform 6 include an RPM repository, a JARinstaller or the extraction of a ZIP archive.









8

You can use the RPM installer if you have a compatible operating system, or the Zip file if you wouldlike to extract the server manually. The installer file is available to assist new users in the configurationand startup process, which also creates an XML installation script to automate the installation processfor other or future installations.

Report a bug9

1.4.2. Install JBoss Enterprise Application Platform 6 Using theInstaller Method

SummaryThe JBoss Enterprise Application Platform 6 installer offers multiple methods for installation. Choosefrom either the standard Graphical User Interface (GUI) installation, or a Command Line Interface(CLI) mode with the console parameter. An Automatic Installation mode enables you to generate anXML file of your selected installation settings to assist in future installations.

Prerequisites• Section 1.2.1, “Download JBoss Enterprise Application Platform 6”

Procedure 1.1. Task• Install JBoss Enterprise Application Platform 6

Choose your installation preference.

GUI Installationa. Launch the GUI installer with the following Java command.

java -jar jboss-eap-6.0.0-installer.jar

b. Follow the installation prompts. At the end of installation, an XML file of the installationcan be generated, for future use with the Automatic Installation feature.

Console Installationa. Launch the console installer with the following Java command.

java -jar jboss-eap-6.0.0-installer.jar -console

b. Follow the installation text prompts. At the end of the installation, an XML file of theinstallation can be generated, for use with the automatic installation feature.

Automatic Installationa. If you have created a previous installation instance, you will have generated an

automatic installation XML script. You can use this file to run the automatic installationoption.

b. Launch the automatic installer with the following Java command.








Install JBoss Enterprise Application Platform 6 Using the ZIP Download

9

java -jar jboss-eap-6.0.0-installer.jar NameOfXML.xml

c. Installation will complete according to the values in the XML file.

ResultThe installation is complete.

Report a bug10

1.4.3. Install JBoss Enterprise Application Platform 6 Using the ZIPDownload

SummaryThe Zip file installation method is appropriate for all support operating systems.

PrerequisitesBefore you can install JBoss Enterprise Application Platform 6, you need to download the Zip archivefrom the Red Hat Customer Service Portal.

Procedure 1.2. Task1. Move the Zip archive to the desired location.

Move the Zip file to the server and directory where you want to install JBoss EnterpriseApplication Platform 6. The directory should be accessible by the user who will start and stop theserver.

2. Use an appropriate application to extract the Zip archive.In Linux, the command to extract a Zip archive is typically called unzip. In a Microsoft Windowsenvironment, right-click the file and select Extract All.

ResultThe directory created by extracting the Zip archive is the top-level directory for JBoss EnterpriseApplication Platform 6. This is typically referred to as EAP_HOME. If you ever decide to move yourinstallation, you can move this directory to another directory or another server.

Report a bug11

10 https://bugzilla.redhat.com/enter_bug.cgi?cf_environment=Instance+Name%3A+Not+Defined%0ABuild%3A+CSProcessor+Builder+Version+1.5%0ABuild+Filter%3A+null%0ABuild+Name%3A+%0ABuild+Date%3A+31-07-2012+11%3A58%3A00&cf_build_id=6893-168380+31+Jul+2012+11%3A58+en-US&assigned_to=dryan%40redhat.com&product=JBoss+Enterprise+Application+Platform+6&component=documentation&version=6.0&keywords=Documentation11 https://bugzilla.redhat.com/enter_bug.cgi?cf_environment=Instance+Name%3A+Not+Defined%0ABuild%3A+CSProcessor+Builder+Version+1.5%0ABuild+Filter%3A+null%0ABuild+Name%3A+%0ABuild+Date%3A+31-07-2012+11%3A58%3A00&cf_build_id=252-155458+31+Jul+2012+11%3A58+en-US&assigned_to=misty%40redhat.com&product=JBoss+Enterprise+Application+Platform+6&component=documentation&version=6.0&keywords=Documentation














10

1.4.4. Install JBoss Enterprise Application Platform 6 using the RedHat Network (RPM installation)

SummaryThe RPM package method of installing JBoss Enterprise Application Platform 6 is appropriate for RedHat Enterprise Linux 6. The recommended installation method is to use the Red Hat Network (RHN) tomanage your server subscriptions and channels.

PrerequisitesIf you are installing an RPM package by using YUM to access the Red Hat Network, you will first needto add your server to the JBoss Enterprise Application Platform 6 channel on the RHNwebsite at http://rhn.redhat.com. You will also be required to log in to your server as the root user.Please note that the RPM package method is only appropriate for Red Hat Enterprise Linux 6.

Procedure 1.3. TaskAccess and install the RPM package by using the YUM install via the Red Hat Network.

1. Install the RPM package by using YUM and the Red Hat NetworkYou can use YUM to install the default JBoss Enterprise Application Platform 6 group package byusing the groupinstall command.

[user@host ~]$ yum groupinstall jboss-eap6

The jbossas-hornetq-native package is included as a method of implementing highavailability in JBoss Enterprise Application Platform 6 and is activated by default.

2. Set the EAP_HOME environment variable to /usr/share/jbossas/.Use the following command to set the EAP_HOME environment variable to /usr/share/jbossas/ if you use the Bash shell. The command may be different if you use a different shell.

export EAP_HOME=/usr/share/jbossas

To make the change persistent, add the command to the end of the .bashrc in the homedirectory of the user running JBoss Enterprise Application Platform.

3. Configure additional options.Several options are available to be configured using the /etc/sysconfig/jbossas/ file. Referto this file for the configuration options. Note that the order and precedence of these options isimportant, so do not change the order of the options in the file.

ResultThe installation is complete.

Report a bug12

12 https://bugzilla.redhat.com/enter_bug.cgi?cf_environment=Instance+Name%3A+Not+Defined%0ABuild%3A+CSProcessor+Builder+Version+1.5%0ABuild+Filter%3A+null%0ABuild+Name%3A+%0ABuild+Date%3A+31-07-2012+11%3A58%3A00&cf_build_id=250-166462+31+Jul+2012+11%3A58+en-

http://rhn.redhat.com





Installation Structure and Details

11

1.4.5. Installation Structure and DetailsJBoss Enterprise Application Platform 6 includes a simplified directory structure, compared to previousversions. Following is a listing of the directory structure, and a description of what the directorycontains.

Table 1.2. Top-level directories and files

Name Purpose

appclient/ Contains configuration details for the applicationclient container.

bin/ Contains start-up scripts for JBoss EnterpriseApplication Platform 6 on Red Hat EnterpriseLinux and Microsoft Windows.

bundles/ Contains OSGi bundles which pertain to JBossEnterprise Application Platform 6 internalfunctionality.

docs/ License files, schemas, and examples.

domain/ Configuration files, deployment content, andwritable areas used when JBoss EnterpriseApplication Platform 6 runs as a manageddomain.

modules/ Modules which are dynamically loaded by JBossEnterprise Application Platform 6 when servicesrequest them.

standalone/ Configuration files, deployment content, andwritable areas used when JBoss EnterpriseApplication Platform 6 runs as a standaloneserver.

welcome-content/ Contains content used by the Welcome webapplication which is available on port 8080 of adefault installation.

jboss-modules.jar The bootstrapping mechanism which loadsmodules.

Table 1.3. Directories within the domain/ directory

Name Purpose

configuration/ Configuration files for the managed domain.These files are modified by the ManagementConsole and Management CLI, and are notmeant to be edited directly.

data/ Information about deployed services. Servicesare deployed using the Management Consoleand Management CLI, rather than by adeployment scanner. Therefore, do not placefiles in this directory manually.

US&assigned_to=misty%40redhat.com&product=JBoss+Enterprise+Application+Platform+6&component=documentation&version=6.0&keywords=Documentation




12

Name Purpose

log/ Contains the run-time log files for the hostand process controllers which run on the localinstance.

servers/ Contains the equivalent data/, log/, andtmp/ directories for each server instance ina domain, which contain similar data to thesame directories within the top-level domain/directory.

tmp/ Contains temporary data such as files pertainingto the shared-key mechanism used by theManagement CLI to authenticate local users tothe managed domain.

Table 1.4. Directories within the standalone/ directory

Name Purpose

configuration/ Configuration files for the standalone server.These files are modified by the ManagementConsole and Management CLI, and are notmeant to be edited directly.

deployments/ Information about deployed services. Thestandalone server does include a deploymentscanner, so you can place archives in thisdirectory to be deployed. However, therecommended approach is to managedeployments using the Management Console orManagement CLI.

lib/ External libraries which pertain to a standaloneserver mode. Empty by default.

tmp/ Contains temporary data such as files pertainingto the shared-key mechanism used by theManagement CLI to authenticate local users tothe server.

Report a bug13








Running JBoss Enterprise Application Platform 6 as a Service

13

1.5. Running JBoss Enterprise Application Platform 6 as aService

1.5.1. Run JBoss Enterprise Application Platform 6 as an OperatingSystem ServiceJBoss Enterprise Application Platform 6 can be configured to run as a service, allowing you to starta Managed Domain or Standalone Server configuration at system runtime, and allowing the serverinstance to continue to run when you log out of your local system.

• Section 1.5.2, “Install JBoss Enterprise Application Platform as a Service in Red Hat EnterpriseLinux”

• Section 1.5.3, “Install JBoss Enterprise Application Platform 6 as a Service in Microsoft Windows”

Report a bug14

1.5.2. Install JBoss Enterprise Application Platform as a Service inRed Hat Enterprise Linux

SummaryThis task installs JBoss Enterprise Application Platform 6 as a service on Red Hat Enterprise Linux.

PrerequisitesYou need administrator access to complete this task.

Procedure 1.4. Task1. Copy the start-up script to the /etc/init.d/ directory

The start-up script is a different file, depending on whether you use a Managed Domain orStandalone Server.

Standalone Server

cp EAP_HOME/bin/standalone.sh /etc/init.d/

Managed Domain

cp EAP_HOME/bin/domain.sh /etc/init.d/









14

2. Define $JBOSS_HOME in the /etc/init.d/standalone.sh or /etc/init.d/domain.shscript.Edit the /etc/init.d/standalone.sh or /etc/init.d/domain.sh script to set theJBOSS_HOME variable. This will override the logic in previous parts of the script, which sets$JBOSS_HOME programmatically.

a. Locate the following section:

# Setup JBOSS_HOME if [ "x$JBOSS_HOME" = "x" ]; then # get the full path (without any relative bits) JBOSS_HOME=`cd $DIRNAME/..; pwd` fi export JBOSS_HOME

b. Edit the line that reads export JBOSS_HOME to point to the installation directory for JBossEnterprise Application Platform 6. This should be the top-level directory, which contains abin/ directory.

export JBOSS_HOME=/path/to/installation/

3. Provide run-level, startup and shutdown priorities to the initialization subsystem of RedHat Enterprise Linux.Edit the /etc/init.d/standalone.sh or /etc/init.d/domain.sh script to include run-level, startup, and shutdown priority information for chkconfig. Add these three lines below thefirst line of the script, which reads #!/bin/sh.

#chkconfig: 2345 95 20#description: JBoss AS 7#processname: standalone.sh

4. Add the start-up script as a service.Add the new standalone.sh or domain.sh service to the chkconfig service managementcommand.

chkconfig --add standalone.sh

chkconfig --add domain.sh

ResultJBoss Enterprise Application Platform 6 starts automatically when the Red Hat Enterprise Linuxreaches its default run-level, and stops automatically when the operating system goes through itsshutdown routine.

Report a bug15








Install JBoss Enterprise Application Platform 6 as a Service in Microsoft Windows

15

1.5.3. Install JBoss Enterprise Application Platform 6 as a Service inMicrosoft Windows

SummaryThis task installs JBoss Enterprise Application Platform 6 as a service on Microsoft Windows.


Procedure 1.5. Task1. Download the Native Utilities package for your architecture.

32-bit, 64-bit, and Itanium 64-bit packages are available from the Red Hat Customer Portalat http://access.redhat.com. For more information on downloading software from the Red HatCustomer Portal, refer here: Section 1.2.2, “Available Downloads for JBoss Enterprise ApplicationPlatform 6”

2. Unzip the downloaded archive.Unzip the archive into a new folder.

Result: The modules\native\bin\ folder is created.The modules\native\bin\ folder contains the files you need to install JBoss EnterpriseApplication Platform 6 as a service. These services are part of Procrun, which is a series ofwrapper scripts provided by Apache Commons. To learn more about Procrun and its syntax, referto the following link: http://commons.apache.org/daemon/procrun.html.

3. Run the modules\sbin\prunsrv.exe executable.

prunsrv.exe install path_to_startup_script

ResultThe service is installed. JBoss Enterprise Application Platform 6 is listed in the Services appletservices.msc.

4. Manage your service.Use the modules\bin\prunmgr.exe executable to manage, edit, add, or delete services. Thefollowing command-line options are supported:

• run

• service

• start

• stop

• update

• install

• delete

• pause [seconds]


http://commons.apache.org/daemon/procrun.html


16

• version

• help

The general syntax is:

prunmgr.exe command service_name

ResultYou can use the net service command at the command line, or the services.msc applet, tostart, stop, and manage automatic start-up of JBoss Enterprise Application Platform 6 in MicrosoftWindows Server.

Report a bug16

1.6. Getting Started with JBoss Enterprise ApplicationPlatform 6

1.6.1. Add the Initial User for the Management Interfaces

OverviewThe management interfaces in JBoss Enterprise Application Platform 6 are secured by default, andthere is no default user. This is a security precaution, to prevent security breaches from remotesystems due to simple configuration errors. Local non-HTTP access is protected by a SASLmechanism, with a negotiation happening between the client and server each time the client connectsfor the first time from the localhost.

This task describes how to create the initial administrative user, which can use the web-basedManagement Console and remote instances of the Management CLI to configure and administerJBoss Enterprise Application Platform 6 from remote systems. For more information about the defaultsecurity configuration, refer to Section 1.6.9, “Default User Security Configuration”.








Add the Initial User for the Management Interfaces

17

Note

HTTP communication with JBoss Enterprise Application Platform 6 is considered to be remoteaccess, even if the traffic originates on the localhost. Therefore, you must create at least one userin order to be able to use the management console. If you attempt to access the managementconsole before adding a user, you will receive an error because it does not even deploy until theuser is added.

Procedure 1.6. Task1. Invoke the add-user.sh or add-user.bat script.

Change to the EAP_HOME/bin/ directory. Invoke the appropriate script for your operatingsystem.

Red Hat Enterprise Linux

[user@host bin]$ ./add-user.sh

Microsoft Windows Server

C:\bin> add-user.bat

2. Choose to add a Management user.Select option a to add a Management user. This user is added to the ManagementRealmand is authorized to perform management operations using the web-based ManagementConsole or command-line based Management CLI. The other choice, b, adds a user to theApplicationRealm, and provides no particular permissions. That realm is provided for use withapplications.

3. Choose the realm for the user.The next prompt refers to the realm where the user will be added. For a user withpermissions to manage JBoss Enterprise Application Platform 6, choose the default, which isManagementRealm.

4. Enter the desired username and password.When prompted, enter the security realm, username and password. Pressing ENTER selectsthe default realm of ManagementRealm, which allows the user to administer JBoss EnterpriseApplication Platform 6 using the management interfaces. You must add at least one user to thisrealm. You are prompted to confirm the information. If you are satisfied, type yes .

5. Choose whether the user represents a remote JBoss Enterprise Application Platform 6server instance.Besides administrators, the other type of user which occasionally needs to be added to JBossEnterprise Application Platform 6 in the ManagementRealm is a user representing anotherinstance of JBoss Enterprise Application Platform 6, which needs to be able to authenticate tojoin a cluster as a member. The next prompt allows you to designate your added user for thispurpose. If you select yes, you will be given a hashed secret value, representing the user'spassword, which would need to be added to a different configuration file. For the purposes of thistask, answer no to this question.


18

6. Enter additional users.You can enter additional users if desired, by repeating the procedure. You can also add them atany time on a running system. Instead of choosing the default security realm, you can add usersto other realms to fine-tune their authorizations.

7. Create users non-interactively.You can create users non-interactively, by passing in each parameter at the command line. Thisapproach is not recommended on shared systems, because the passwords will be visible in logand history files. The syntax for the command, using the management realm, is:

[user@host bin]$ ./add-user.sh username password

To use the application realm, use the -a parameter.

[user@host bin]$ ./add-user.sh -a username password

ResultAny users you add are activated within the security realms you have specified. Users active within theManagementRealm realm are able to manage JBoss Enterprise Application Platform 6 from remotesystems.

Report a bug17

1.6.2. Start JBoss Enterprise Application Platform 6

TaskStart JBoss Enterprise Application Platform 6 in one of the following ways:

• Section 1.6.3, “Start JBoss Enterprise Application Platform 6 as a Managed Domain”

• Section 1.6.4, “Start JBoss Enterprise Application Platform 6 as a Standalone Server”

• Section 1.6.5.1, “Run JBoss Enterprise Application Platform 6 as an Operating System Service”

Report a bug18

17 https://bugzilla.redhat.com/enter_bug.cgi?cf_environment=Instance+Name%3A+Not+Defined%0ABuild%3A+CSProcessor+Builder+Version+1.5%0ABuild+Filter%3A+null%0ABuild+Name%3A+%0ABuild+Date%3A+31-07-2012+11%3A58%3A00&cf_build_id=5750-150354+31+Jul+2012+11%3A58+en-US&assigned_to=misty%40redhat.com&product=JBoss+Enterprise+Application+Platform+6&component=documentation&version=6.0&keywords=Documentation18 https://bugzilla.redhat.com/enter_bug.cgi?cf_environment=Instance+Name%3A+Not+Defined%0ABuild%3A+CSProcessor+Builder+Version+1.5%0ABuild+Filter%3A+null%0ABuild+Name%3A+%0ABuild+Date%3A+31-07-2012+11%3A58%3A00&cf_build_id=4598-155458+31+Jul+2012+11%3A58+en-US&assigned_to=twells%40redhat.com&product=JBoss+Enterprise+Application+Platform+6&component=documentation&version=6.0&keywords=Documentation


https://bugzilla.redhat.com/enter_bug.cgi?cf_environment=Instance+Name%3A+Not+Defined%0ABuild%3A+CSProcessor+Builder+Version+1.5%0ABuild+Filter%3A+null%0ABuild+Name%3A+%0ABuild+Date%3A+31-07-2012+11%3A58%3A00&cf_build_id=4598-155458+31+Jul+2012+11%3A58+en-US&assigned_to=twells%40redhat.com&product=JBoss+Enterprise+Application+Platform+6&component=documentation&version=6.0&keywords=Documentation











Start JBoss Enterprise Application Platform 6 as a Managed Domain

19

1.6.3. Start JBoss Enterprise Application Platform 6 as a ManagedDomain

1. Start JBoss Enterprise Application Platform 6 as a managed domain in Red Hat EnterpriseLinux.Run the command: EAP_HOME/bin/domain.sh

2. Start JBoss Enterprise Application Platform 6 as a managed domain in Microsoft WindowsServerRun the command: EAP_HOME\bin\domain.bat

3. Optional: Pass additional parameters to the start-up scriptFor a list of parameters you can pass to the start-up script, use the -h parameter.

Result:The JBoss Enterprise Application Platform 6 Managed Domain instance starts.

Report a bug19

1.6.4. Start JBoss Enterprise Application Platform 6 as a StandaloneServer

1. Start JBoss Enterprise Application Platform 6 in as a standalone server in Red HatEnterprise Linux.Run the command: EAP_HOME/bin/standalone.sh

2. Start Jboss Enterprise Application Platform 6 in as a standalone server in MicrosoftWindows Server.Run the command: EAP_HOME\bin\standalone.bat

3. Optional: Specify additional parameters.To print a list of additional parameters to pass to the start-up scripts, use the -h parameter.

ResultThe JBoss Enterprise Application Platform 6 Standalone Server instance starts.

Report a bug20

19 https://bugzilla.redhat.com/enter_bug.cgi?cf_environment=Instance+Name%3A+Not+Defined%0ABuild%3A+CSProcessor+Builder+Version+1.5%0ABuild+Filter%3A+null%0ABuild+Name%3A+%0ABuild+Date%3A+31-07-2012+11%3A58%3A00&cf_build_id=43-155458+31+Jul+2012+11%3A58+en-US&assigned_to=misty%40redhat.com&product=JBoss+Enterprise+Application+Platform+6&component=documentation&version=6.0&keywords=Documentation20 https://bugzilla.redhat.com/enter_bug.cgi?cf_environment=Instance+Name%3A+Not+Defined%0ABuild%3A+CSProcessor+Builder+Version+1.5%0ABuild+Filter%3A+null%0ABuild+Name%3A+%0ABuild+Date%3A+31-07-2012+11%3A58%3A00&cf_build_id=42-155458+31+Jul+2012+11%3A58+en-US&assigned_to=misty%40redhat.com&product=JBoss+Enterprise+Application+Platform+6&component=documentation&version=6.0&keywords=Documentation














20

1.6.5. Running JBoss Enterprise Application Platform 6 as a Service

1.6.5.1. Run JBoss Enterprise Application Platform 6 as an OperatingSystem ServiceJBoss Enterprise Application Platform 6 can be configured to run as a service, allowing you to starta Managed Domain or Standalone Server configuration at system runtime, and allowing the serverinstance to continue to run when you log out of your local system.

• Section 1.6.5.2, “Install JBoss Enterprise Application Platform as a Service in Red Hat EnterpriseLinux”

• Section 1.6.5.3, “Install JBoss Enterprise Application Platform 6 as a Service in Microsoft Windows”

Report a bug21

1.6.5.2. Install JBoss Enterprise Application Platform as a Service in RedHat Enterprise Linux

SummaryThis task installs JBoss Enterprise Application Platform 6 as a service on Red Hat Enterprise Linux.


Procedure 1.7. Task1. Copy the start-up script to the /etc/init.d/ directory

The start-up script is a different file, depending on whether you use a Managed Domain orStandalone Server.

Standalone Server

cp EAP_HOME/bin/standalone.sh /etc/init.d/

Managed Domain

cp EAP_HOME/bin/domain.sh /etc/init.d/

2. Define $JBOSS_HOME in the /etc/init.d/standalone.sh or /etc/init.d/domain.shscript.Edit the /etc/init.d/standalone.sh or /etc/init.d/domain.sh script to set theJBOSS_HOME variable. This will override the logic in previous parts of the script, which sets$JBOSS_HOME programmatically.








Running JBoss Enterprise Application Platform 6 as a Service

21

a. Locate the following section:

# Setup JBOSS_HOME if [ "x$JBOSS_HOME" = "x" ]; then # get the full path (without any relative bits) JBOSS_HOME=`cd $DIRNAME/..; pwd` fi export JBOSS_HOME

b. Edit the line that reads export JBOSS_HOME to point to the installation directory for JBossEnterprise Application Platform 6. This should be the top-level directory, which contains abin/ directory.

export JBOSS_HOME=/path/to/installation/

3. Provide run-level, startup and shutdown priorities to the initialization subsystem of RedHat Enterprise Linux.Edit the /etc/init.d/standalone.sh or /etc/init.d/domain.sh script to include run-level, startup, and shutdown priority information for chkconfig. Add these three lines below thefirst line of the script, which reads #!/bin/sh.

#chkconfig: 2345 95 20#description: JBoss AS 7#processname: standalone.sh

4. Add the start-up script as a service.Add the new standalone.sh or domain.sh service to the chkconfig service managementcommand.

chkconfig --add standalone.sh

chkconfig --add domain.sh

ResultJBoss Enterprise Application Platform 6 starts automatically when the Red Hat Enterprise Linuxreaches its default run-level, and stops automatically when the operating system goes through itsshutdown routine.

Report a bug22









22

1.6.5.3. Install JBoss Enterprise Application Platform 6 as a Service inMicrosoft Windows

SummaryThis task installs JBoss Enterprise Application Platform 6 as a service on Microsoft Windows.


Procedure 1.8. Task1. Download the Native Utilities package for your architecture.

32-bit, 64-bit, and Itanium 64-bit packages are available from the Red Hat Customer Portalat http://access.redhat.com. For more information on downloading software from the Red HatCustomer Portal, refer here: Section 1.2.2, “Available Downloads for JBoss Enterprise ApplicationPlatform 6”

2. Unzip the downloaded archive.Unzip the archive into a new folder.

Result: The modules\native\bin\ folder is created.The modules\native\bin\ folder contains the files you need to install JBoss EnterpriseApplication Platform 6 as a service. These services are part of Procrun, which is a series ofwrapper scripts provided by Apache Commons. To learn more about Procrun and its syntax, referto the following link: http://commons.apache.org/daemon/procrun.html.

3. Run the modules\sbin\prunsrv.exe executable.

prunsrv.exe install path_to_startup_script

ResultThe service is installed. JBoss Enterprise Application Platform 6 is listed in the Services appletservices.msc.

4. Manage your service.Use the modules\bin\prunmgr.exe executable to manage, edit, add, or delete services. Thefollowing command-line options are supported:

• run

• service

• start

• stop

• update

• install

• delete

• pause [seconds]


http://commons.apache.org/daemon/procrun.html

Test the Installation

23

• version

• help

The general syntax is:

prunmgr.exe command service_name

ResultYou can use the net service command at the command line, or the services.msc applet, tostart, stop, and manage automatic start-up of JBoss Enterprise Application Platform 6 in MicrosoftWindows Server.

Report a bug23

1.6.6. Test the Installation

Task Prerequisites• Section 1.6.2, “Start JBoss Enterprise Application Platform 6”

• The necessary network ports must be open. Refer to Section 1.6.7, “Network Ports Used By JBossEnterprise Application Platform 6” and Section 1.6.8, “Configure Network Firewalls to Work withJBoss Enterprise Application Platform 6”.

1. Look for error messages in the log files.After you start the server, view the log files in EAP_HOME/domain/log/ or EAP_HOME/standalone/log/.

Result:If the server started properly, there will be no errors, and you will see output similar to thefollowing:

Example 1.1. Example of a successful start-up

[Server:server-two] 15:47:44,372 INFO [org.jboss.as] (MSC service thread 1-3) JBoss AS 7.0.0.Final" started in 4227ms - Started 114 of 162 services (48 services are passive or on-demand)

In a managed domain, you see a similar message for each locally-run server.









24

2. Browse to the Management Console.If the installation worked properly and your server is running, you should be able toaccess the Management Console by pointing your web browser at an address similar tohttp://YOUR_SERVER:9990/, replacing YOUR_SERVER with a valid value.

Result:The front page of the Management Console appears.

Result:The Management Console is a deployable service. If you are able to reach it after starting the server,your installation is working properly and is able to deploy services.

Report a bug24

1.6.7. Network Ports Used By JBoss Enterprise Application Platform6The ports used by the JBoss Enterprise Application Platform 6 default configuration depend on severalfactors:

• Whether you use a Managed Domain or Standalone Server configuration.

• Whether your server groups use one of the default socket binding groups, or a custom group.

• The requirements of your individual deployments.

Numerical port offsets

A numerical port offset can be configured, to alleviate port conflicts when you run multiple serverson the same physical server. If your server uses a numerical port offset, add the offset to thedefault port number for its server group's socket binding group. For instance, if the HTTP port ofthe socket binding group is 8080, and your server uses a port offset of 100, its HTTP port is 8180.

Unless otherwise stated, the ports use the TCP protocol.

The default socket binding groups• full-ha-sockets

• full-sockets

• ha-sockets

• standard-sockets








Network Ports Used By JBoss Enterprise Application Platform 6

25

Table 1.5. Reference of the default socket bindings

Name Port MulicastPort

Description full-ha-sockets

full-sockets

ha-socket

standard-socket

ajp 8009 Apache JServProtocol. Used forHTTP clustering andload balancing.

Yes Yes Yes Yes

http 8080 The default portfor deployed webapplications.

Yes Yes Yes Yes

https 8443 SSL-encryptedconnection betweendeployed webapplications andclients.

Yes Yes Yes Yes

jacorb 3528 CORBA servicesfor JTS transactionsand other ORB-dependent services.

Yes Yes No No

jacorb-ssl

3529 SSL-encryptedCORBA services.

Yes Yes No No

jgroups-diagnostics

7500 Multicast. Used forpeer discovery inHA clusters.

Yes No Yes No

jgroups-mping

45700 Multicast. Usedto discover initialmembership in a HAcluster.

Yes No Yes No

jgroups-tcp

7600 Unicast peerdiscovery in HAclusters using TCP.

Yes No Yes No

jgroups-tcp-fd

57600 Used for HA failuredetection over TCP.

Yes No Yes No

jgroups-udp

55200 45688 Unicast peerdiscovery in HAclusters using UDP.

Yes No Yes No

jgroups-udp-fd

54200 Used for HA failuredetection over UDP.

Yes No Yes No

messaging5445 JMS service. Yes Yes No No

messaging-group

Referenced byHornetQ JMSbroadcast anddiscovery groups.

Yes Yes No No

messaging-throughput

5455 Used by JMSRemoting.

Yes Yes No No

mod_cluster 23364 Multicast port forcommunicationbetween the

Yes No Yes No


26

Name Port MulicastPort

Description full-ha-sockets

full-sockets

ha-socket

standard-socket

JBoss EnterpriseApplication Platformand the HTTP loadbalancer.

osgi-http

8090 Used by internalcomponents whichuse the OSGisubsystem.

Yes Yes Yes Yes

remoting 4447 Used for remoteEJB invocation.

Yes Yes Yes Yes

txn-recovery-environment

4712 The JTA transactionrecovery manager.

Yes Yes Yes Yes

txn-status-manager

4713 The JTA / JTStransation manager.

Yes Yes Yes Yes

Management PortsIn addition to the socket binding groups, each host controller opens two more ports for managementpurposes:

• 9990 - The Web Management Console port

• 9999 - The port used by the Management Console and Management API

Report a bug25

1.6.8. Configure Network Firewalls to Work with JBoss EnterpriseApplication Platform 6

OverviewMost production environments use firewalls as part of an overall network security strategy. If youneed multiple server instances to communicate with each other or with external services such as webservers or databases, your firewall needs to take this into account. A well-managed firewall only opensthe ports which are necessary to operation, and limits access to the ports to specific IP addresses,subnets, and network protocols.

A full discussion of firewalls is out of the scope of this documentation.








Configure Network Firewalls to Work with JBoss Enterprise Application Platform 6

27

Prerequisites• Determine the ports you need to open. Refer to Section 1.6.7, “Network Ports Used By JBoss

Enterprise Application Platform 6” to determine the list of ports for your situation.

• An understanding of your firewall software is required. This procedure uses the system-config-firewall command in Red Hat Enterprise Linux 6. Microsoft Windows Server includes a built-infirewall, and several third-party firewall solutions are available for each platform.

AssumptionsThis procedure configures a firewall in an environment with the following assumptions:

• The operating system is Red Hat Enterprise Linux 6.

• JBoss Enterprise Application Platform 6 runs on host 10.1.1.2. Optionally, the server has its ownfirewall.

• The network firewall server runs on host 10.1.1.1 on interface eth0, and has an externalinterface eth1.

• You want traffic on port 5445 (a port used by JMS) forwarded to JBoss Enterprise ApplicationPlatform 6. No other traffic should be allowed through the network firewall.

Procedure 1.9. Task1. Log into the Management Console.

Log into the Management Console. By default, it runs on http://localhost:9990/console/.

2. Managed Domain: Determine the socket binding group your server group uses.Each server group uses a socket binding group, which is a collection of socket bindings. A socketbinding is a name-value pair of port name and number.

To determine which socket binding group your server groups, click the Server Groups label atthe top right side of the screen. Then click the name of your server group in the Available servergroup configurations table. The Server attributes area at the bottom of the screen is populatedwith the profile and socket binding group used by the server group.

3. Determine the socket bindings used by the socket binding group.Click the Profiles label at the top right of the Management Console. At the left-hand side of thescreen, a series of menus is shown. The bottom menu heading is General Configuration. Clickthe Socket Binding Groups item below this heading. The Socket Binding Declarations screenappears. Initially, the standard-sockets group is shown. You can choose a different group byselecting it from the combo box on the right-hand side.

Note

If you use a standalone server, it has only one socket binding group.

The list of socket names and ports is shown, six values per page. You can go through the pagesby using the arrow navigation below the table.

4. Determine the ports you need to open.Depending on the function of the particular port and the needs of your environment, some of theports may need to be accessible across your firewall. If you are unsure of the purpose of a socket

http://localhost:9990/console/


28

binding, refer to Section 1.6.7, “Network Ports Used By JBoss Enterprise Application Platform 6”for a list of the default socket bindings and their purposes.

5. Configure your firewall to forward traffic to JBoss Enterprise Application Platform 6.Perform these steps to configure your network firewall to allow traffic on the desired port.

a. Log into your firewall machine and access a command prompt, as the root user.

b. Issue the command system-config-firewall to launch the firewall configuration utility. AGUI or command-line utility launches, depending on the way you are logged into the firewallsystem. This task makes the assumption that you are logged in via SSH and using thecommand-line interface.

c. Use the TAB key on your keyboard to navigate to the Customize button, and press theENTER key. The Trusted Services screen appears.

d. Do not change any values, but use the TAB key to navigate to the Forward button, and pressENTER to advanced to the next screen. The Other Ports screen appears.

e. Use the TAB key to navigate to the <Add> button, and press ENTER. The Port and Protocolscreen appears.

f. Enter 5445 in the Port / Port Range field, then use the TAB key to move to the Protocolfield, and enter tcp. Use the TAB key to navigate to the OK button, and press ENTER.

g. Use the TAB key to navigate to the Forward button until you reach the Port Forwardingscreen.

h. Use the TAB key to navigate to the <Add> button, and press the ENTER key.

i. Fill in the following values to set up port forwarding for port 5445.

• Source interface: eth1

• Protocol: tcp

• Port / Port Range: 5445

• Destination IP address: 10.1.1.2

• Port / Port Range: 5445

Use the TAB key to navigate to the OK button, and press ENTER.

j. Use the TAB key to navigate to the Close button, and press ENTER.

k. Use the TAB key to navigate to the OK button, and press ENTER. To apply the changes, readthe warning and click Yes.

6. Configure a firewall on your JBoss Enterprise Application Platform 6 host.Some organizations choose to configure a firewall on the JBoss Enterprise Application Platform6 server itself, and close all ports that are not necessary for its operation. Consult Section 1.6.7,“Network Ports Used By JBoss Enterprise Application Platform 6” and determine which portsto open, then close the rest. The default configuration of Red Hat Enterprise Linux 6 closes allports except 22 (used for Secure Shell (SSH) and 5353 (used for multicast DNS). While youare configuring ports, make sure you have physical access to your server so that you do notinadvertently lock yourself out.

Default User Security Configuration

29

ResultYour firewall is configured to forward traffic to your internal JBoss Enterprise Application Platform 6server in the way you specified in your firewall configuration. If you chose to enable a firewall on yourserver, all ports are closed except the ones needed to run your applications.

Report a bug26

1.6.9. Default User Security Configuration

IntroductionAll management interfaces in JBoss Enterprise Application Platform 6 are secured by default. Thissecurity takes two different forms:

• Local interfaces are secured by a SASL contract between local clients and the server they connectto. This security mechanism is based on the client's ability to access the local filesystem. This isbecause access to the local filesystem would allow the client to add a user or otherwise changethe configuration to thwart other security mechanisms. This adheres to the principle that if physicalaccess to the filesystem is achieved, other security mechanisms are superfluous. The mechanismhappens in four steps:

Note

HTTP access is considered to be remote, even if you connect to the localhost using HTTP.

1. The client sends a message to the server which includes a request to authenticate with the localSASL mechanism.

2. The server generates a one-time token, writes it to a unique file, and sends a message to theclient with the full path of the file.

3. The client reads the token from the file and sends it to the server, verifying that it has localaccess to the filesystem.

4. The server verifies the token and then deletes the file.

• Remote clients, including local HTTP clients, use realm-based security. The default realm withthe permissions to configure the JBoss Enterprise Application Platform 6 remotely using themanagement interfaces is ManagementRealm. A script is provided which allows you to add usersto this realm (or realms you create). For more information on adding users, refer to the GettingStarted chapter of the Installation guide for JBoss Enterprise Application Platform 6. For eachuser, the username, a hashed password, and the realm are stored in a file. The file is in a differentlocation if the JBoss Enterprise Application Platform 6 is configured as a managed domain or astandalone server.









30

Managed domain

EAP_HOME/domain/configuration/mgmt-users.properties

Standalone server

EAP_HOME/standalone/configuration/mgmt-users.properties

Even though the contents of the mgmt-users.properties are masked, the file should still betreated as a sensitive file. It is recommended that it be set to the file mode of 600, which gives noaccess other than read and write access by the file owner.

Report a bug27

1.7. Uninstalling JBoss Enterprise Application Platform 6

1.7.1. Uninstall JBoss Enterprise Application Platform 6

Task SummaryThe exact steps for uninstalling JBoss Enterprise Application Server 6 depend on how it was installed.

• Section 1.7.2, “Uninstall JBoss Enterprise Application Platform 6 From a Zip Installation”

• Section 1.7.3, “Uninstall JBoss Enterprise Application Platform 6 From a Graphical Installation”

• Section 1.7.4, “Uninstall JBoss Enterprise Application Platform 6 From an RPM Installation”

Report a bug28

1.7.2. Uninstall JBoss Enterprise Application Platform 6 From a ZipInstallation

1. Log into the server.Log into your server as a user who has write access to the JBoss Enterprise Application Platform6 installation directory.














Uninstall JBoss Enterprise Application Platform 6 From a Graphical Installation

31

2. Remove the installation directory.JBoss Enterprise Application Platform 6 installs in a single directory when you use the Zipinstallation method. Delete the installation directory to uninstall JBoss Enterprise ApplicationPlatform 6.

3. Optional: Remove any initialization scripts you created.If you created initialization scripts or other scripts which depended upon JBoss EnterpriseApplication Platform 6 being installed on your computer, remove them.

4. Optional: Microsoft Windows: Remove JBoss Enterprise Application Platform 6 from yourServices.To remove the JBoss Enterprise Application Platform 6 service, run the following command at acommand prompt, as an administrative user: sc delete "JBEAP6SVC".

Result:JBoss Enterprise Application Platform 6 is uninstalled from your server.

Report a bug29

1.7.3. Uninstall JBoss Enterprise Application Platform 6 From aGraphical Installation1. Navigate to the EAP_HOME/Uninstaller/ directory on the server.

During the installation of JBoss Enterprise Application Platform 6, a directory called EAP_HOME/Uninstaller/ was created. This directory contains a file called uninstaller.jar.

2. Run the java -jar uninstaller.jar command.This command uninstalls JBoss Enterprise Application Platform 6.

Result:JBoss Enterprise Application Platform 6 is uninstalled from your server.

Report a bug30

1.7.4. Uninstall JBoss Enterprise Application Platform 6 From anRPM Installation1. Log into the server.

Log into the server where JBoss Enterprise Application Platform 6 is installed and gain rootaccess.















32

2. Optional: Create a list of files and directories created by the RPM installation.To create a list of files and directories created by the RPM installation, run the command rpm -ql jboss-eap6 > /tmp/jbeap6.txt. The reason to do this step is because removing theRPM may not remove all of these files and directories from your system. You may need to removesome of them by hand.

3. Remove the package with the yum command.Use the YUM groupremove command to remove the jboss-eap6 group.

yum groupremove jboss-eap6

4. Optional: Check for and remove files or directories that were not removed by the yumgroupremove command.Check the list of files and directories created by the rpm -ql command above. Remove any thatwere not removed automatically.

ResultJBoss Enterprise Application Platform 6 is uninstalled from your server.

Report a bug31








33

Appendix A. Revision HistoryRevision 1.0-0 Wed Jun 20 2012 Tom Wells [email protected]

First edition of the JBoss Enterprise Application Platform 6 Installation Guide.

mailto: [email protected]

34

Documents

JBoss Enterprise Application Platform 6 Installation Guide en US