Red Hat JBoss Developer Studio

7.0
Installation Guide

Information for users installing JBoss Developer Studio

Red Hat Documentation Team

Red Hat JBoss Developer Studio 7.0 Installation Guide

Information for users installing JBoss Developer Studio

Red Hat Do cumentatio n Team

Legal Notice

Copyright 2013 Red Hat, Inc.

T his document is licensed by Red Hat under the Creative Commons Attribution-ShareAlike 3.0 Unported
License. If you distribute this document, or a modified version of it, you must provide attribution to Red
Hat, Inc. and provide a link to the original. If the document is modified, all Red Hat trademarks must be
removed.

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

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

Linux is the registered trademark of Linus T orvalds in the United States and other countries.

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

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

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

Node.js is an official trademark of Joyent. Red Hat Software Collections is not formally related to or
endorsed by the official Joyent Node.js open source or commercial project.

T he OpenStack Word Mark and OpenStack Logo are either registered trademarks/service marks or
trademarks/service marks of the OpenStack Foundation, in the United States and other countries and
are used with the OpenStack Foundation's permission. We are not affiliated with, endorsed or
sponsored by the OpenStack Foundation, or the OpenStack community.

All other trademarks are the property of their respective owners.

Abstract
T his document details how to install and set up JBoss Developer Studio.
 Table of Contents

Table of Contents

.Preface
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3. . . . . . . . . .
1. Document Conventions 3
1.1. T ypographic Conventions 3
1.2. Pull-quote Conventions 4
1.3. Notes and Warnings 5
2. Getting Help and Giving Feedback 5
2.1. Do You Need Help? 5
2.2. Give us Feedback 6

.Chapter
. . . . . . . . 1.
. . .Introduction
. . . . . . . . . . . . .to
. . .Red
. . . . Hat
. . . . JBoss
. . . . . . . Developer
. . . . . . . . . . . Studio
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7. . . . . . . . . .
1.1. About Red Hat JBoss Developer Studio 7
1.2. Use Cases of JBoss Developer Studio 7

.Chapter
. . . . . . . . 2.
. . .System
. . . . . . . .Requirements
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9. . . . . . . . . .
2.1. System Requirements Overview 9
2.2. Supported Operating Systems and Architectures 9
2.3. Computer Memory 9
2.4. Compatible Java Developer Kits 10

.Chapter
. . . . . . . . 3.
. . .Install
. . . . . . .JBoss
. . . . . . Developer
. . . . . . . . . . . .Studio
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
............
3.1. Install Options 11
3.2. Install JBoss Developer Studio 11
3.3. Install JBoss Developer Studio BYOE 16

.Chapter
........4. ...Set
. . . . Preferences
. . . . . . . . . . . . . on
. . . First
. . . . . .Launch
. . . . . . . .after
. . . . . Installing
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
............
4.1. Preferences Options 22
4.2. Select a Workspace Location 22
4.3. Set Usage Reporting 23
4.4. Define Servers for Application Servers Found by Runtime Detection 24
4.5. Set the Perspective to JBoss 25

.Chapter
. . . . . . . . 5.
. . .Upgrade
. . . . . . . . . from
. . . . . Previous
. . . . . . . . . .Versions
. . . . . . . . . of
. . .JBoss
. . . . . . .Developer
. . . . . . . . . . .Studio
. . . . . . . . . . . . . . . . . . . . . . . . 27
............
5.1. Upgrade Methods 27
5.2. Upgrade JBoss Developer Studio 27
5.3. Upgrade JBoss Developer Studio BYOE 27

.Chapter
. . . . . . . . 6.
. . .Uninstall
. . . . . . . . . JBoss
. . . . . . . Developer
. . . . . . . . . . . Studio
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
............
6.1. Uninstall Methods 28
6.2. Uninstall JBoss Developer Studio 28
6.3. Uninstall JBoss Developer Studio BYOE 28

.Java
. . . . .Developer
. . . . . . . . . . .Kits
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .32
...........
A.1. Determine Default Java Developer Kit of the System 32
A.2. Install a Java Developer Kit 33

. . . . . . . . . .History
Revision . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .35
...........

1
 Red Hat JBoss D eveloper Studio 7.0 Installation Guide

2
 Preface

Preface

1. Document Conventions
T his manual uses several conventions to highlight certain words and phrases and draw attention to
specific pieces of information.

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

1.1. Typographic Conventions

Four typographic conventions are used to call attention to specific words and phrases. T hese
conventions, 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 highlight
keys and key combinations. For example:

T o see the contents of the file m y_next_bestselling_novel in your current working

directory, enter the cat m y_next_bestselling_novel command at the shell prompt
and press Enter to execute the command.

T he 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 Ctrl+Alt+F2 to switch to a virtual terminal.

T he first example highlights a particular key to press. T he 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 m ono-spaced bold. For example:

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

Proportional Bold

T his 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 Mouse
Preferences. In the Buttons tab, select the Left-handed m ouse check box and click
Close to switch the primary mouse button from the left to the right (making the mouse
suitable for use in the left hand).

T o insert a special character into a gedit file, choose Applications Accessories

3
 Red Hat JBoss D eveloper Studio 7.0 Installation Guide

Character Map from the main menu bar. Next, choose Search Find from the
Character Map menu bar, type the name of the character in the Search field and click
Next. T he character you sought will be highlighted in the Character T able. Double-click
this highlighted character to place it in the T ext to copy field and then click the Copy
button. Now switch back to your document and choose Edit Paste from the gedit menu
bar.

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

Mono-spaced Bold Italic or Proportional Bold Italic

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

T o connect to a remote machine using ssh, type ssh username@ domain.name at a shell
prompt. If the remote machine is exam ple.com and your username on that machine is
john, type ssh john@ exam ple.com .

T he m ount -o rem ount file-system command remounts the named file system. For
example, to remount the /hom e file system, the command is m ount -o rem ount /hom e.

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

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

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

Publican is a DocBook publishing system.

1.2. Pull-quote Conventions

T erminal output and source code listings are set off visually from the surrounding text.

Output sent to a terminal is set in m ono-spaced rom an 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 m ono-spaced rom an but add syntax highlighting as follows:

4
 Preface

package org.jboss.book.jca.ex1;

import javax.naming.InitialContext;

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 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. 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 Hat Customer
Portal at http://access.redhat.com. T hrough 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
 Red Hat JBoss D eveloper Studio 7.0 Installation Guide

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. Give us Feedback

If you find a typographical error, or know how this guide can be improved, we would love to hear from
you. Submit a report in Bugzilla against the product Red Hat JBoss Developer Studio and the
component docum entation. T he following link will take you to a pre-filled bug report for this product:
https://bugzilla.redhat.com/.

Fill out the following template in Bugzilla's Description field. Be as specific as possible when
describing 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.

6
 Chapter 1. Introduction to Red Hat JBoss D eveloper Studio

Chapter 1. Introduction to Red Hat JBoss Developer Studio

1.1. About Red Hat JBoss Developer Studio

Red Hat JBoss Developer Studio is a set of Eclipse-based development tools. It contains plug-ins that
integrate with Eclipse to extend the existing functionality of the integrated development environment
(IDE).

JBoss Developer Studio is designed to increase your productivity when developing applications. You can
focus on building, testing and deploying your applications because JBoss application development tools
are integrated in one IDE. Furthermore, JBoss Developer Studio has many unique features to assist your
application development:

Develop new applications using the wizards and project examples of JBoss Central.
Add powerful functionality to applications with minimal effort using Forge T ools.
Build web interfaces with ease using the visual editing and drag-and-drop utilities of Visual Web
T ools and Mobile Web T ools.
Experience browsers automatically refreshing in response to modified application resources with
LiveReload T ools.
Incorporate JSF, Seam, JAX-RS, Hibernate, CDI and other popular APIs into applications with
simplicity using the tool-driven interface.
Preview and test mobile web applications on a variety of simulation mobile devices using
BrowserSim.
Deploy applications to JBoss runtime servers and the cloud using JBoss Server T ools and
OpenShift T ools.

JBoss Developer Studio comes built around Eclipse and packaged with all of the necessary
dependencies and third-party plug-ins for simplified installing. For developers already running Eclipse,
JBoss Developer Studio can also be installed through Eclipse Marketplace. For distinction, this latter
JBoss Developer Studio installation is called JBoss Developer Studio BYOE (Bring Your Own Eclipse).

Report a bug

1.2. Use Cases of JBoss Developer Studio

JBoss Developer Studio assists JEE developers by integrating JBoss technology and APIs in a single
development environment. Here are a few ways that JBoss Developer Studio makes the work of a
developer easier:

Web applications
JBoss Central provides wizards that generate skeleton and sample projects, enabling you to
focus on developing the functionality of your applications. T he wizards create web applications
based on different APIs and technologies, showing the usage and advantages of each.
JBoss Developer Studio also offers project file templates in a range of popular programming
languages, including HT ML, XHT ML, and JSF.

Palettes in JBoss Developer Studio give access to the core elements of the JSF, Richfaces and
Seam APIs, for use in developing the user interfaces of your applications. Elements of these
APIs can be dragged and dropped directly into your project so that you can create richer user
interfaces quickly. Visual Web T ools offers graphical and source viewing of files and defaults to
dedicated editors for different file types. JBoss Developer Studio supports the Java EE 6
specification and provides tools for JAX-RS, Hibernate, and CDI APIs so you can develop the

7
 Red Hat JBoss D eveloper Studio 7.0 Installation Guide

server-side components of your application effortlessly.

LiveReload T ools automatically refreshes browsers of local or deployed applications as you

modify project resources to save you from needing to manually refresh. You can even
experience automatic refreshing when viewing applications in browsers on external and mobile
devices, with application web addresses easy to navigate to with QR codes.

Web applications optimized for mobile devices

Mobile Web T ools provides support for HT ML5 and jQuery Mobile to enable you to create web
applications optimized across desktop and mobile clients. T he HT ML5 Project wizard in JBoss
Central generates a sample application using HT ML5 and jQuery Mobile technologies and,
together with HT ML5 and jQuery Mobile project file templates, helps you to get up and running
with these APIs and technologies quickly. HT ML5 and jQuery Mobile widgets can be dragged
from the Mobile Web palette into your project files and, in conjunction with the widget wizards,
enable you to effortlessly develop customized user interfaces for your mobile web applications.

BrowserSim allows you to view your web applications on a variety of simulated mobile devices
so that you can ensure they will be correctly formatted. LiveReload also extends to BrowserSim
allowing you to experience automatic browser refreshing as you develop your mobile web
applications. T he integration of Firebug Lite and Weinre capabilities with BrowserSim assists
you to inspect the page source of web pages with familiar tools.

Applications for cloud deployment

OpenShift T ools deploys your applications directly to the cloud on the Red Hat OpenShift
platform. You can create and manage your OpenShift account and manage the deployment of
applications in your OpenShift domain from within the IDE. In addition to using the OpenShift
Application wizard to create new applications for deployment to OpenShift, OpenShift T ools can
import applications already deployed on OpenShift so that you can further develop them and
manage their deployment from the comfort of the IDE.

Report a bug

8
 Chapter 2. System Requirements

Chapter 2. System Requirements

2.1. System Requirements Overview

T he aim of this section is familiarize you with the system requirements necessary for
JBoss Developer Studio to function optimally:

A variety of operating system and architecture combinations are generally supported but some tools
have additional requirements.
A minimum amount of RAM and hard disk space are required to install and run
JBoss Developer Studio.
A variety of operating systems and Java developer kit combinations are supported.

Report a bug

2.2. Supported Operating Systems and Architectures

JBoss Developer Studio 7.0 is supported on the operating systems listed in the table below.

T able 2.1. Supported Operating Systems

Operating System Chip Architecture

Red Hat Enterprise Linux 6 x86, x86_64
Microsoft Windows XP, Windows 7 and Windows 8 x86, x86_64
OS X Lion (10.7) and OS X Mountain Lion (10.8) x86_64
Fedora 18 and Fedora 19 x86, x86_64
Ubuntu 12.04.2 LT S and Ubuntu 13.04 x86, x86_64

As JBoss Developer Studio 7.0 is based on Eclipse Kepler (4.3), the system requirements of Eclipse
Kepler also apply to JBoss Developer Studio 7.0. For example, GT K is required as the windowing
system on Linux distributions, Win32 on Microsoft Windows operating systems and Cocoa on OS X
operating systems. For more information about Eclipse Kepler system requirements see
http://www.eclipse.org/eclipse/development/readme_eclipse_4.3.html on the Eclipse website.

T he Visual Page Editor of JBoss Developer Studio 7.0 has additional system requirements and
restrictions:

T he visual component of the Visual Page Editor, which depends on XULRunner, does not operate in
the 64-bit version of JBoss Developer Studio on OS X and Microsoft Windows operating systems. T o
work around this restriction, you must install a 32-bit version of JBoss Developer Studio with a 32-bit
Java developer kit on 64-bit OS X and Microsoft Windows operating systems.

Report a bug

2.3. Computer Memory

T o install and run JBoss Developer Studio 7.0, the following memory requirements are recommended:

4 GB RAM
1.5 GB of hard disk space

9
 Red Hat JBoss D eveloper Studio 7.0 Installation Guide

T he minimum memory requirements are 2 GB RAM and 750 MB of hard disk space.

Report a bug

2.4. Compatible Java Developer Kits

JBoss Developer Studio 7.0 requires a Java developer kit of version 1.6 or newer. T his release of
JBoss Developer Studio is supported on the operating system and Java developer kit combinations
listed in the table below.

T able 2.2. Supported Combinations of Operating Systems and Java Developer Kits

Operating System Java Developer Kit

Red Hat Enterprise Linux 6 OpenJDK 1.6, OpenJDK 1.7, Oracle JDK 1.6 and
Oracle JDK 1.7
Microsoft Windows XP Oracle JDK 1.6
Microsoft Window 7 and Windows 8 Oracle JDK 1.6 and Oracle JDK 1.7
OS X Lion (10.7) and OS X Mountain Lion (10.8) Apple JDK 1.6 and Oracle JDK 1.7 (64-bit only)
Fedora 18 and Fedora 19 OpenJDK 1.6 and OpenJDK 1.7
Ubuntu 12.04.2 LT S and Ubuntu 13.04 OpenJDK 1.6 and OpenJDK 1.7

Before installing JBoss Developer Studio you must identify which Java developer kit you have installed. If
it is not listed above, you must install a compatible one before proceeding.

Important

You must use a 32-bit Java developer kit to install a 32-bit version of JBoss Developer Studio and
a 64-bit Java developer kit to install a 64-bit version of JBoss Developer Studio.

See Also:

Appendix A, Java Developer Kits

Report a bug

10
 Chapter 3. Install JBoss D eveloper Studio

Chapter 3. Install JBoss Developer Studio

3.1. Install Options

JBoss Developer Studio can be installed in a number of different ways.

You can install JBoss Developer Studio, packaged with Eclipse and dependent third-party plug-ins, with
a universal installer for all operating systems.

Alternatively, if you already have Eclipse on your system you may prefer to install
JBoss Developer Studio BYOE. T his option installs JBoss Developer Studio in Eclipse.

Report a bug

3.2. Install JBoss Developer Studio

A universal installer .jar file is provided for installing JBoss Developer Studio and it is available from
the Customer Service Portal.

Alternatively, the source code is also available as a .zip file at the same location. You can use this
source code to build the universal installer yourself and then use that to install JBoss Developer Studio.
Maven must be installed to build the universal installer from the source code.

Both options are detailed in the procedure below.

Procedure 3.1. Install with the Universal Installer

1. Log in to the Customer Portal at https://access.redhat.com.

2. From the menu bar click Downloads.
3. Under Red Hat JBoss Middleware, click Download Software.

Figure 3.1. Download Red Hat JBoss Middleware Software on the Customer Portal

4. Under Software Downloads, select the following options:

From the Product list, select JBoss Developer Studio.
From the Version list, select 7.0.x.

11
 Red Hat JBoss D eveloper Studio 7.0 Installation Guide

Figure 3.2. JBoss Developer Studio Downloads Listed on the Customer Portal

5. Complete the appropriate step for your chosen install option:

A. For installing from the provided universal installer, from the table click Download for the Red
Hat JBoss Developer Studio 7.0.x Stand Alone Universal Binary download
file. T his downloads the universal installer .jar file.
B. For installing from a source-built universal installer, follow these steps:
a. From the table, click Download for the Red Hat JBoss Developer Studio 7.0.x
Source Code download file. T his downloads the sources .zip file.
b. On the command line, navigate to path/to/.zip and enter

unzip jbdevstudio-product-sources-7.0.x.build_version.zip

where x.build_version is substituted to match the name of the downloaded file. T he

archive is extracted to a devstudio directory.
c. T o build the universal installer, on the command line navigate to devstudio/product
and enter

mvn clean install

Building takes some time to complete, after which the universal installer .jar file is
located in installer/target/.
6. On the command line, navigate to path/to/.jar and enter

12
 Chapter 3. Install JBoss D eveloper Studio

java -jar jbdevstudio-product-universal-7.0.x.build_version.jar

where x.build_version is substituted to match the name of the .jar file.

Note

T o start the installer, you may be able to double-click the .jar file.

7. When the Installer window opens, click Next.

8. After reading and agreeing to the terms of the End User License Agreement, click I accept the
term s of this license agreem ent and click Next.
9. In the Select the installation path field, type the path where you want
JBoss Developer Studio to be installed or click Browse to navigate to the desired location. When
the Select the installation path field shows the correct path, click Next. When you are
prompted about the specified location being created or overwritten, review the message and, if
satisfied, click OK.

Figure 3.3. Installation Step 3: Select T arget Folder

10. In the Select Java VM step, Default Java VM is automatically selected. Ensure that the
disabled text field contains the path of the Java developer kit you want to use. T his is based on
the default Java developer kit of your system. T o change the specified Java developer kit, click
Specific Java VM and type the path of the Java developer kit in the text field or use the
Browse button to locate the Java developer kit. When the text field shows the correct Java
developer kit path, click Next.

13
 Red Hat JBoss D eveloper Studio 7.0 Installation Guide

Figure 3.4 . Installation Step 4 : Select Java VM

Important

You must specify a Java developer kit with a 32-bit JRE to install a 32-bit version of
JBoss Developer Studio and a 64-bit JRE to install a 64-bit version of
JBoss Developer Studio. T o change the bit version of the Java developer kit to be used for
installing JBoss Developer Studio, complete the appropriate step for your operating system:
On OS X operating systems, from the Installation type list click the appropriate
bit version.
On Linux distributions and Microsoft Windows operating systems, in the text field type
the path to the appropriate bit version of the Java developer kit.

11. T o make use of automatic runtime detection for finding application servers, click Add. In the
Location field, type the path from which recursive scanning for application servers is to
commence or click Browse to navigate to the location:
T o detect a specific application server, select the install directory for that application server.
T o detect multiple application servers, select a directory higher up the directory tree.
Alternatively, this can be achieved by adding multiple locations for scanning.
T o scan the specified path for new application servers each time JBoss Developer Studio starts,
select the Scan every start check box. Click OK to close the Add Location window and
click Next.

14
 Chapter 3. Install JBoss D eveloper Studio

Figure 3.5. Add Location Window for Runtime Detection

12. Review the details in the Summary Information window and, if they are correct, click Next.
13. Installation commences. When the Pack installation progress bar shows Finished,
click Next.

Figure 3.6. Installation Step 7: Installation Progress in Finished State

14. T o create shortcuts for starting JBoss Developer Studio, select the Create shortcuts in
the Start-Menu and Create additional shortcut on the desktop check boxes and
click Next.
15. T he installation process is now complete. T o automatically start JBoss Developer Studio when the
Installer window closes, select the Run JBoss Developer Studio after
installation check box. Click Done to close the Installer window.

15
 Red Hat JBoss D eveloper Studio 7.0 Installation Guide

Important

Linux distributions have a maximum number of files that a process can have open at one time. If
this maximum number of files is set too low, JBoss Developer Studio will not start. You must open
the /etc/security/lim its.conf file and ensure that the soft nofile and hard nofile
variables have values of 9216 at a minimum. If the variables have smaller values, the values
must be increased to 9216. If the variables are not specified, the following lines must be added to
the file:

* soft nofile 9216

* hard nofile 9216

Report a bug

3.3. Install JBoss Developer Studio BYOE

You can obtain JBoss Developer Studio BYOE from Eclipse Marketplace or use the .zip file available
from the Red Hat JBoss Developer Studio Update website. T he latter option provisions for online and
offline installation modes; Eclipse can install directly from the online .zip file or you can download the
.zip file first and then Eclipse can install from this local copy.

Select one of the procedures below, which will guide you through the JBoss Developer Studio BYOE
installation process.

Procedure 3.2. Install from Eclipse Marketplace

1. Start Eclipse Kepler.

2. Click HelpEclipse Marketplace.
3. In the Find field of the Search tab, enter JBoss Developer Studio.
4. Locate Red Hat JBoss Developer Studio (Kepler) and click Install.

16
 Chapter 3. Install JBoss D eveloper Studio

Figure 3.7. Install JBoss Developer Studio BYOE via Eclipse Marketplace

5. Ensure the Red Hat JBoss Developer Studio (Kepler) check box is selected and click
Confirm >.

17
 Red Hat JBoss D eveloper Studio 7.0 Installation Guide

Figure 3.8. Confirm Selected Features Window

6. After reading and agreeing to the licenses, click I accept the term s of the license
agreem ents and click Finish.

Figure 3.9. Review Licenses Window

7. During the installation process you may receive warnings about installing unsigned content. If this
is the case, review the details of the content and if satisfied click OK to continue with the
installation.

18
 Chapter 3. Install JBoss D eveloper Studio

Figure 3.10. Warning Prompt for Installing Unsigned Content

8. Once installing is complete, you are prompted to restart Eclipse. Click Yes to restart now and No if
you need to save any unsaved changes to open projects. Note that IDE changes do not take
effect until Eclipse is restarted.

Procedure 3.3. Install from Update Z IP File

Note

T o install JBoss Developer Studio BYOE in offline mode, you must go to

https://devstudio.jboss.com/updates/7.0/ and download the update .zip file before proceeding.

1. Start Eclipse Kepler.

2. Click HelpInstall New Software.
3. Complete the appropriate step for your chosen install mode:
A. For online mode, in the Work with field enter
https://devstudio.jboss.com /updates/7.0/.

Figure 3.11. Work from an Online Website

B. For offline mode, in the Work with field enter the path of the update .zip file. Alternatively,
click Add and click Archive to locate the file.

Figure 3.12. work from a Local Copy of the Update .zip File

19
 Red Hat JBoss D eveloper Studio 7.0 Installation Guide

4. From the table of components, select JBoss Developer Studio 7.0 - Bring Your Own
Eclipse and click Next.

Figure 3.13. Available Software Window Listing JBoss Developer Studio 7.0 - Bring
Your Own Eclipse

5. Review the details of the component to be installed and click Next.

6. After reading and agreeing to the licenses, click I accept the term s of the license
agreem ents and click Finish.

20
 Chapter 3. Install JBoss D eveloper Studio

Figure 3.14 . Review Licenses Window

7. During the installation process you may receive warnings about installing unsigned content. If this
is the case, review the details of the content and if satisfied click OK to continue with the
installation.

Figure 3.15. Warning Prompt for Installing Unsigned Content

8. Once installing is complete, you are prompted to restart Eclipse. Click Yes to restart now and No if
you need to save any unsaved changes to open projects. Note that IDE changes do not take
effect until Eclipse is restarted.

Report a bug

21
 Red Hat JBoss D eveloper Studio 7.0 Installation Guide

Chapter 4. Set Preferences on First Launch after Installing

4.1. Preferences Options

T he aim of this section is to guide you in setting preferences for the JBoss Developer Studio features
encountered on the first IDE start after installing:

Select a workspace for your projects

Choose whether to enable JBoss Developer Studio to collect usage information for compiling
product-wide statistics
Decide whether to define servers for application servers that runtime detection found on IDE start
Activate the JBoss perspective to provide easy access to common tabs, menus and toolbars for
working with JBoss technologies

Report a bug

4.2. Select a Workspace Location

When the IDE starts, you are asked to choose the workspace folder for the session. T he workspace is
where your projects are stored.

Figure 4 .1. Select a Workspace Window

T o set the workspace location, follow these steps:

1. In the Workspace field, type the path for a new or existing workspace or use Browse to navigate
to the workspace location.
2. If you do not want to be asked to choose a workspace folder each time the IDE starts, select the
Use this as the default and do not ask again check box.

22
 Chapter 4. Set Preferences on First Launch after Installing

3. Click OK.

T he workspace location prompting behavior can be altered at any time by clicking

WindowPreferences. Expand GeneralStartup and Shutdown and select Workspaces.
Select or clear the Prom pt for workspace on startup check box to alter the behavior as
appropriate.

Report a bug

4.3. Set Usage Reporting

JBoss Developer Studio has usage reporting. At the first start of the IDE after installing, you are asked if
you allow the collection of anonymous usage statistics by JBoss Developer Studio.

Figure 4 .2. Prompt for Anonymous Usage Statistics

T he information collected enables Red Hat to understand how and where JBoss Developer Studio is
being used. Specifically, information about operating systems and system display resolution assists in
continually improving JBoss Developer Studio.

T he following information is collected:

Version of JBoss Developer Studio

Installed components of JBoss Developer Studio
JBoss Central enabled
Origin of Eclipse product
Version of Eclipse
Operating system
Operating system version
Linux distribution and version, if appropriate
Screen colors
Screen resolution
Version of Java
Internet connection type
Location (continent, country, city) and language
User type (new or returning)
Number of times JBoss Developer Studio has been started
Date of first usage reported

23
 Red Hat JBoss D eveloper Studio 7.0 Installation Guide

Date of last usage reported

Date of current usage reported

If enabled, the usage reporting plug-in uses Google Analytics to track data as though you visited a page
under https://devstudio.jboss.com/usage.

T o agree to this anonymous information being collected, click Yes when prompted.

T he usage reporting behavior can be changed at any time by clicking WindowPreferences. Expand
JBoss T ools and select Usage Reporting. Select or clear the Please allow Red Hat Inc.
to receive anonym ous usage statistics for this JBoss Developer Studio
installation check box to alter the behavior as appropriate.

Report a bug

4.4. Define Servers for Application Servers Found by Runtime

Detection
If you set up runtime detection during the installation process, at the first start if the IDE you are
prompted with the results of the runtime detection scan. Depending on whether any application servers
are found, follow the appropriate step:

If no new application servers are found or you do not wish to create server runtime environments,
click Cancel.

Figure 4 .3. No New Application Servers Found by Runtime Detection

If new application servers are found, you can generate server runtime environments for them. Select
the check boxes of the application servers for which you want to generate server runtime
environments and click OK.

24
 Chapter 4. Set Preferences on First Launch after Installing

Figure 4 .4 . One New Application Server Found by Runtime Detection

Note

If you have not set up runtime detection during the installation process or you installed JBoss
Developer Studio BYOE, you can set up runtime detection in Preferences under JBoss
T oolsJBoss Runtim e Detection.

Report a bug

4.5. Set the Perspective to JBoss

JBoss Developer Studio has JBoss perspective. T his displays tabs, toolbars and menu items most often
used by developers using JBoss. T hese include Project Explorer, Palette, Servers and OpenShift
Explorer.

If you start JBoss Developer Studio, this perspective is set as the default and it is automatically
displayed.

If you start Eclipse, this perspective is not automatically displayed. T o show the JBoss perspective, click
the JBoss icon . Alternatively, click WindowOpen PerspectiveOther, select JBoss and
click OK.

T o set the JBoss perspective as the default perspective, click WindowPreferences. Expand
General and select Perspectives. From the Available perspectives list, select JBoss and
click Make Default. Click Apply and click OK to close the Preferences window.

25
 Red Hat JBoss D eveloper Studio 7.0 Installation Guide

Figure 4 .5. Make JBoss the Default Perspective in the Preferences Window

Report a bug

26
 Chapter 5. Upgrade from Previous Versions of JBoss D eveloper Studio

Chapter 5. Upgrade from Previous Versions of JBoss

Developer Studio

5.1. Upgrade Methods

T he method for upgrading JBoss Developer Studio depends on whether you are using
JBoss Developer Studio or JBoss Developer Studio BYOE.

Warning

Before upgrading, you are advised to back up your workspace. In addition to your project files,
your workspace contains meta-data about customized setting and preferences for
JBoss Developer Studio or Eclipse. T o back up your workspace, either copy the workspace
directory to a backup location or save it as a compressed file.

Report a bug

5.2. Upgrade JBoss Developer Studio

It is not possible to upgrade an existing JBoss Developer Studio installation to JBoss Developer Studio
7.0 because they are based on different versions of Eclipse. For example, JBoss Developer Studio 6.0 is
based on Eclipse Juno (4.2) but JBoss Developer Studio 7.0 is based on Eclipse Kepler (4.3).

T o use JBoss Developer Studio 7.0, you must download and run the universal installer available from
the Customer Portal at https://access.redhat.com.

Note

You can use different versions of JBoss Developer Studio alongside each other by installing them
in different directories.

Report a bug

5.3. Upgrade JBoss Developer Studio BYOE

It is not possible to upgrade an existing JBoss Developer Studio BYOE to JBoss Developer Studio 7.0
BYOE because they support different versions of Eclipse. For example, JBoss Developer Studio 6.0
BYOE supports Eclipse Juno (4.2) but JBoss Developer Studio 7.0 BYOE supports Eclipse Kepler (4.3).

T o use JBoss Developer Studio 7.0 BYOE, you must upgrade to Eclipse Kepler and install
JBoss Developer Studio 7.0 BYOE from Eclipse Marketplace.

Report a bug

27
 Red Hat JBoss D eveloper Studio 7.0 Installation Guide

Chapter 6. Uninstall JBoss Developer Studio

6.1. Uninstall Methods

T here are two uninstall methods for JBoss Developer Studio. T he method you use depends on whether
you are using JBoss Developer Studio or JBoss Developer Studio BYOE.

Report a bug

6.2. Uninstall JBoss Developer Studio

Procedure 6.1. Uninstall with the Uninstaller

1. Ensure JBoss Developer Studio is not running.

2. On the command line, navigate to path/to/JBoss Developer Studio/Uninstaller.
3. On the command line, enter

java -jar uninstaller.jar

Note

Alternatively, to start the uninstaller you may be able to double-click the

uninstaller.jar file.

4. T o remove the entire JBoss Developer Studio installation directory, select the Force the
deletion check box. If this is not selected, JBoss Developer Studio is uninstalled but some files
are left behind in the installation directory.
5. Click Uninstall.
6. Once the progress bar shows Finished, click Quit to close the Uninstaller window.

Figure 6.1. Uninstaller in Finished State

Report a bug

6.3. Uninstall JBoss Developer Studio BYOE

JBoss Developer Studio BYOE can be uninstalled with the procedure below regardless of whether it was
installed via Eclipse Marketplace or the update .zip file.

28
 Chapter 6. Uninstall JBoss D eveloper Studio

Procedure 6.2. Uninstall via Eclipse Marketplace

1. Start Eclipse Kepler.

2. Click HelpEclipse Marketplace.
3. In the Find field of the Search tab, enter JBoss Developer Studio.
4. Locate Red Hat JBoss Developer Studio (Kepler) and click Uninstall.

29
 Red Hat JBoss D eveloper Studio 7.0 Installation Guide

Figure 6.2. Uninstall JBoss Developer Studio via Eclipse Marketplace

5. Ensure the Red Hat JBoss Developer Studio (Kepler) check box is selected and click
Confirm >.

30
 Chapter 6. Uninstall JBoss D eveloper Studio

6. Ensure the Red Hat JBoss Developer Studio (Kepler) check box is selected and click
Finish.

Figure 6.3. Confirm Selected Features Window

7. Once installing is complete, you are prompted to restart Eclipse. Click Yes to restart immediately
and No if you need to save any unsaved changes to open projects. Note that IDE changes do not
take effect until Eclipse is restarted.

Report a bug

31
 Red Hat JBoss D eveloper Studio 7.0 Installation Guide

Java Developer Kits

It is important to use a Java developer kit that is supported by this release of JBoss Developer Studio.
T he aim of this section is to assist you to do the following:

Determine the Java developer kit used by your system

Install a supported Java developer kit

Report a bug

A.1. Determine Default Java Developer Kit of the System

T o determine if your system has a Java developer kit set up for use and the version, follow the
procedure below which is suitable for all operating systems.

Procedure A.1. Determine Default Java Developer Kit of the System

1. On the command line, enter javac -version. T he output shows the version of the Java
compiler being used as the default of the system and indicates that the system has a Java
developer kit set up for use.

Important

If a message to the effect of javac not found is returned, the system does not have a
Java compiler set up for use. T his indicates that either the system does not have a Java
developer kit installed or that the installed Java developer kit is not set up for use.

2. On the command line, enter java -version. T he output preceding Runtim e Environm ent
identifies which Java distribution is being used as the default Java runtime environment (JRE) and
the output after java version identifies the version number of the JRE.

Important

If the version numbers of the Java compiler and JRE are different, the system is using a
Java compiler and JRE from different Java distributions as the default. T his should be
rectified so that the Java compiler and JRE are from the same Java developer kit.

Sample output for various Java developer kits is displayed below.

32
 Java D eveloper Kits

Example A.1. Sample Output from Identifying the Default Java Developer Kit of the
System

Output for OpenJDK Java developer kit 1.7.0:

$ javac -version
javac 1.7.0_09
$ java -version
java version "1.7.0_09-icedtea"
OpenJDK Runtime Environment (fedora-2.3.5.fc17-x86_64)
OpenJDK 64-Bit Server VM (build 23.2-b09, mixed mode)

Output for Oracle JDK 1.6.0:

$ javac -version
javac 1.6.0_38
$ java -version
java version "1.6.0_38"
Java(TM) SE Runtime Environment (build 1.6.0_38-b05)
Java HotSpot(TM) 64-Bit Server VM (build 20.13-b02, mixed mode)

Output for OpenJDK JRE 1.7.0 (no Java compiler):

$ javac -version
bash: /usr/bin/javac: No such file or directory
$ java -version
java version "1.7.0_09-icedtea"
OpenJDK Runtime Environment (fedora-2.3.5.fc17-x86_64)
OpenJDK Server VM (build 23.2-b09, mixed mode)

Report a bug

A.2. Install a Java Developer Kit

T he procedures given here guide you through how to install a new Java developer kit, either OpenJDK
or Oracle.

Important

Each Java developer kit has its own system requirements and these must be checked before
starting the installation process.

Procedure A.2. Install a OpenJDK Java developer kit

Complete the appropriate step for your operating system:

A. For Red Hat Enterprise Linux and Fedora, on the command line enter

sudo yum install java-1.7.0-openjdk-devel

B. For Ubuntu, on the command line enter

33
 Red Hat JBoss D eveloper Studio 7.0 Installation Guide

Procedure A.3. Install a Oracle JDK

1. T o download a JDK, go to http://www.oracle.com/technetwork/java/javase/downloads/index.html on

the Oracle website. Identify the Java SE version you want and follow the instructions to download
the appropriate file for your operating system and architecture.

Note

For Linux distributions, both a .rpm and a .tar.gz file will be available for download.
Installing with an RPM binary (.rpm ) file requires root access but the archive binary
(tar.gz) file can be installed by all users.

2. T o install the JDK from the downloaded file, complete the appropriate steps for your operating
system:
A. For Linux distributions and the .tar.gz file:
a. Move the .tar.gz file to the directory where you want to install the JDK. For example,
Java distributions are typically stored in /usr/java/.
b. On the command line, navigate to the location of the .tar.gz file and enter

tar zxvf jdk-<version>-linux-<architecture>.tar.gz

replacing <version> and <architecture> as appropriate.

c. Once complete, the .tar.gz file can be deleted to save disk space.
B. For Linux distributions and the .rpm file:
a. On the command line, navigate to the location of the .rpm file and enter

sudo rpm -ivh jdk-<version>-linux-<architecture>.rpm

replacing <version> and <architecture> as appropriate.

b. Once complete, the .rpm file can be deleted to save disk space.
C. For OS X operating systems:
a. Double-click the .dm g file.
b. In the open Finder window, double-click the package icon and follow the installer
instructions.
c. Once complete, the .dm g file can be deleted to save disk space.
D. For Microsoft Windows operating systems:
a. Double-click the .exe and follow the installer instructions.
b. Once complete, the .exe file can be deleted to save disk space.

Report a bug

34
 Revision History

Revision History
Revision 7.0.0-15.4 00 2013-10-31 Rdiger Landmann
Rebuild with publican 4.0.0

Revision 7.0.0-15 Wed Sep 04 2013 Michelle Murray

T OOLSDOC-358: Updated product download instructions following Customer Portal change

Revision 7.0.0-14 T hu Aug 15 2013 Michelle Murray

T OOLSDOC-382: Rebuilt for the Customer Portal, content unchanged

Revision 7.0.0-13 T hu Aug 01 2013 Michelle Murray

T OOLSDOC-380: Applied more edits for technical review

Revision 7.0.0-12 Wed Jul 31 2013 Michelle Murray

T OOLSDOC-380: Applied edits for technical review

Revision 7.0.0-11 T ue Jul 30 2013 Michelle Murray

T OOLSDOC-348: Added screen captures

Revision 7.0.0-10 Wed Jul 24 2013 Michelle Murray

T OOLSDOC-377: Added Java developer kit appendix

Revision 7.0.0-9 T hu Jul 11 2013 Michelle Murray

T OOLSDOC-364: Added install in offline mode with .zip file

Revision 7.0.0-8 T hu Jul 11 2013 Michelle Murray

T OOLSDOC-368: Removed QE remark tags and Beta2 identifier

Revision 7.0.0-7 Fri Jun 28 2013 Michelle Murray

Added Beta2 identifier to title

Revision 7.0.0-6 Wed Jun 26 2013 Michelle Murray

JBQA-8087: Incorporated QE feedback for Beta2

Revision 7.0.0-5 Fri Jun 7 2013 Michelle Murray

T OOLSDOC-354: Implemented brand change

Revision 7.0.0-4 T hu Jun 6 2013 Michelle Murray

T OOLSDOC-352: Added build from source

Revision 7.0.0-3 T ue Jun 4 2013 Michelle Murray

T OOLSDOC-328: Implemented product name change

Revision 7.0.0-2 T hu May 2 2013 Michelle Murray

T OOLSDOC-314: Added immediate launch after install

Revision 7.0.0-1 Wed Mar 6 2013 Michelle Murray

First draft

35
 Red Hat JBoss D eveloper Studio 7.0 Installation Guide

36