Red Hat JBoss Enterprise Application Platform (EAP) Quickstarts

Summary: The quickstarts demonstrate Java EE 6 and a few additional technologies from the JBoss stack. They provide small, specific, working examples that can be used as a reference for your own project.

Introduction

These quickstarts run on Red Hat JBoss Enterprise Application Platform 6.1 or later. We recommend using the JBoss EAP ZIP file. This version uses the correct dependencies and ensures you test and compile against your runtime environment.

Be sure to read this entire document before you attempt to work with the quickstarts. It contains the following information:

Available Quickstarts: List of the available quickstarts and details about each one.
Suggested Approach to the Quickstarts: A suggested approach on how to work with the quickstarts.
System Requirements: List of software required to run the quickstarts.
Configure Maven: How to configure the Maven repository for use by the quickstarts.
Run the Quickstarts: General instructions for building, deploying, and running the quickstarts.
Run the Arquillian Tests: How to run the Arquillian tests provided by some of the quickstarts.
Optional Components: How to install and configure optional components required by some of the quickstarts.

Available Quickstarts

The list of all currently available quickstarts can be found here: http://site-jdf.rhcloud.com/quickstarts/get-started/. The table lists each quickstart name, the technologies it demonstrates, gives a brief description of the quickstart, and the level of experience required to set it up. For more detailed information about a quickstart, click on the quickstart name.

Some quickstarts are designed to enhance or extend other quickstarts. These are noted in the Prerequisites column. If a quickstart lists prerequisites, those must be installed or deployed before working with the quickstart.

Quickstarts with tutorials in the Get Started Developing Applications are noted with two asterisks ( ** ) following the quickstart name.

Note: Some of these quickstart use the H2 database included with JBoss EAP 6. It is a lightweight, relational example datasource that is used for examples only. It is not robust or scalable and should NOT be used in a production environment!

[TOC-quickstart]

Suggested Approach to the Quickstarts

We suggest you approach the quickstarts as follows:

Regardless of your level of expertise, we suggest you start with the helloworld quickstart. It is the simplest example and is an easy way to prove your server is configured and started correctly.
If you are a beginner or new to JBoss, start with the quickstarts labeled Beginner, then try those marked as Intermediate. When you are comfortable with those, move on to the Advanced quickstarts.
Some quickstarts are based upon other quickstarts but have expanded capabilities and functionality. If a prerequisite quickstart is listed, be sure to deploy and test it before looking at the expanded version.

System Requirements

The applications these projects produce are designed to be run on Red Hat JBoss Enterprise Application Platform 6.1 or later.

To run these quickstarts with the provided build scripts, you need the following:

Java 1.6, to run JBoss AS and Maven. You can choose from the following:
- OpenJDK
- Oracle Java SE
- Oracle JRockit
Maven 3.0.0 or newer, to build and deploy the examples
- If you have not yet installed Maven, see the Maven Getting Started Guide for details.
- If you have installed Maven, you can check the version by typing the following in a command line:
```
  mvn --version 
```
The JBoss EAP distribution ZIP.
- For information on how to install and run JBoss, refer to the product documentation.
You can also use JBoss Developer Studio or Eclipse to run the quickstarts.

Configure Maven

Configure Maven to Build and Deploy the Quickstarts

The quickstarts use artifacts located in the JBoss Developer repository. You must configure Maven to use that repository before you build and deploy the quickstarts.

Note: If you do not wish to configure the Maven settings, you must pass the configuration setting on every Maven command as follows: -s QUICKSTART_HOME/settings.xml

Locate the Maven install directory for your operating system. It is usually installed in ${user.home}/.m2/.

     For Linux or Mac:   ~/.m2/
     For Windows: \Documents and Settings\USER_NAME\.m2\  -or-  \Users\USER_NAME\.m2\

If you have an existing settings.xml file, rename it so you can restore it later.

     For Linux or Mac:  mv ~/.m2/settings.xml ~/.m2/settings-backup.xml
     For Windows: ren "\Documents and Settings\USER_NAME\.m2\settings.xml" settings-backup.xml
             -or- ren "\Users\USER_NAME\.m2\settings.xml" settings-backup.xml

If you have an existing repository/ directory, rename it so you can restore it later. For example

     For Linux or Mac:  mv ~/.m2/repository/ ~/.m2/repository-backup/
     For Windows: ren "\Documents and Settings\USER_NAME\.m2\repository\" repository-backup
             -or- ren "\Users\USER_NAME\.m2\repository\" repository-backup

Copy the settings.xml file from the root of the quickstarts directory to your Maven install directory.

     For Linux or Mac:  cp QUICKSTART_HOME/settings.xml  ~/.m2/settings.xml
     For Windows: copy QUICKSTART_HOME/settings.xml \Documents and Settings\USER_NAME\.m2\settings.xml 
             -or- copy QUICKSTART_HOME/settings.xml \Users\USER_NAME\.m2\settings.xml

Restore Your Maven Configuration When You Finish Testing the Quickstarts

Locate the Maven install directory for your operating system. It is usually installed in ${user.home}/.m2/.

     For Linux or Mac:   ~/.m2/
     For Windows: \Documents and Settings\USER_NAME\.m2\  -or-  \Users\USER_NAME\.m2\

Restore the settings.xml file/

     For Linux or Mac:  mv ~/.m2/settings-backup.xml ~/.m2/settings.xml
     For Windows: ren "\Documents and Settings\USER_NAME\.m2\settings-backup.xml" settings.xml
             -or- ren "\Users\USER_NAME\.m2\settings-backup.xml" settings.xml

Restore the repository/ directory

     For Linux or Mac:  mv ~/.m2/repository-backup/ ~/.m2/repository/
     For Windows: ren "\Documents and Settings\USER_NAME\.m2\repository-backup\" repository
             -or- ren "\Users\USER_NAME\.m2\repository\" repository-backup

Maven Profiles

Profiles are used by Maven to customize the build environment. The pom.xml in the root of the quickstart directory defines the following profiles:

The default profile defines the list of modules or quickstarts that require nothing but JBoss Enterprise Application Platform.
The requires-postgres profile lists the quickstarts that require PostgreSQL to be running when the quickstart is deployed.
The complex-dependency profile lists quickstarts that require manual configuration that can not be automated.
The requires-full profile lists quickstarts the require you start the JBoss server using the full profile.
The requires-xts profile lists quickstarts the require you start the JBoss server using the xts profile.
The non-maven profile lists quickstarts that do not require Maven, for example, quickstarts that depend on deployment of other quickstarts or those that use other Frameworks such as Forge.

Run the Quickstarts

The root folder of each individual quickstart contains a README file with specific details on how to build and run the example. In most cases you do the following:

Start the JBoss server
Build and deploy the quickstarts

Start the JBoss Server

Before you deploy a quickstart, in most cases you need a running JBoss EAP server. A few of the Arquillian tests do not require a running server. This will be noted in the README for that quickstart.

The JBoss server can be started a few different ways.

Start the Default JBoss Server: This is the default configuration. It defines minimal subsystems and services.
Start the JBoss Server with the full profile: This profile configures many of the commonly used subsystems and services.
Start the JBoss Server with a custom configuration: Custom configuration parameters can be specified on the command line when starting the server.

The README for each quickstart will specify which configuration is required to run the example.

Start the Default JBoss Server

To start JBoss EAP:

Open a command line and navigate to the root of the JBoss server directory.

The following shows the command line to start the JBoss server:

 For Linux:   JBOSS_HOME/bin/standalone.sh
 For Windows: JBOSS_HOME\bin\standalone.bat

Start the JBoss Server with the Full Profile

To start JBoss EAP with the Full Profile:

Open a command line and navigate to the root of the JBoss server directory.

The following shows the command line to start the JBoss server with the full profile:

 For Linux:   JBOSS_HOME/bin/standalone.sh -c standalone-full.xml
 For Windows: JBOSS_HOME\bin\standalone.bat -c standalone-full.xml

Start the JBoss Server with Custom Configuration Options

To start JBoss EAP with custom configuration options:

Open a command line and navigate to the root of the JBoss server directory.
The following shows the command line to start the JBoss server. Replace the CUSTOM_OPTIONS with the custom optional parameters specified in the quickstart.
```
 For Linux:   JBOSS_HOME/bin/standalone.sh CUSTOM_OPTIONS
 For Windows: JBOSS_HOME\bin\standalone.bat CUSTOM_OPTIONS
```

Build and Deploy the Quickstarts

See the README file in each individual quickstart folder for specific details and information on how to run and access the example.

Build the Quickstart Archive

In some cases, you may want to build the application to test for compile errors or view the contents of the archive.

Open a command line and navigate to the root directory of the quickstart you want to build.
Use this command if you only want to build the archive, but not deploy it:
```
     mvn clean install
```

Build and Deploy the Quickstart Archive

Make sure you start the JBoss server as described in the README.
Open a command line and navigate to the root directory of the quickstart you want to run.
Use this command to build and deploy the archive:
```
     mvn clean install jboss-as:deploy
```

Undeploy an Archive

The command to undeploy the quickstart is simply:

    mvn jboss-as:undeploy

Verify the Quickstarts Build with One Command

You can verify the quickstarts build using one command. However, quickstarts that have complex dependencies must be skipped. For example, the jax-rs-client quickstart is a RESTEasy client that depends on the deployment of the helloworld-rs quickstart. As noted above, the root pom.xml file defines a complex-dependencies profile to exclude these quickstarts from the root build process.

To build the quickstarts:

Do not start the JBoss server.
Open a command line and navigate to the root directory of the quickstarts.
Use this command to build the quickstarts that do not have complex dependencies:
```
     mvn clean install '-Pdefault,!complex-dependencies'
```

Note: If you see a java.lang.OutOfMemoryError: PermGen space error when you run this command, increase the memory by typing the following command for your operating system, then try the above command again.

    For Linux:   export MAVEN_OPTS="-Xmx512m -XX:MaxPermSize=128m"
    For Windows: SET MAVEN_OPTS="-Xmx512m -XX:MaxPermSize=128m"

Undeploy the Deployed Quickstarts with One Command

To undeploy the quickstarts from the root of the quickstart folder, you must pass the argument -fae (fail at end) on the command line. This allows the command to continue past quickstarts that fail due to complex dependencies and quickstarts that only have Arquillian tests and do not deploy archives to the server.

You can undeploy quickstarts using the following procedure:

Start the JBoss server.
Open a command line and navigate to the root directory of the quickstarts.
Use this command to undeploy any deployed quickstarts:
```
     mvn jboss-as:undeploy -fae
```

To undeploy any quickstarts that fail due to complex dependencies, follow the undeploy procedure described in the quickstart's README file.

Run the Arquillian Tests

Some of the quickstarts provide Arquillian tests. By default, these tests are configured to be skipped, as Arquillian tests an application on a real server, not just in a mocked environment.

You can either start the server yourself or let Arquillian manage its lifecycle during the testing. The individual quickstart README should tell you what to expect in the console output and the server log when you run the test.

Test the quickstart on a remote server
- Arquillian's remote container adapter expects a JBoss server instance to be already started prior to the test execution. You must Start the JBoss server as described in the quickstart README file.
- If you need to run the tests on a JBoss server running on a machine other than localhost, you can configure this, along with other options, in the src/test/resources/arquillian.xml file using the following properties:
```
  <container qualifier="jboss" default="true">
      <configuration>
          <property name="managementAddress">myhost.example.com</property>
          <property name="managementPort">9999</property>
          <property name="username">customAdminUser</property>
          <property name="password">myPassword</property>
      </configuration>
  </container>    
```
- Run the test goal with the following profile activated:
```
  mvn clean test -Parq-jbossas-remote     
```
Test the quickstart on a managed server

Arquillian's managed container adapter requires that your server is not running as it will start the container for you. However, you must first let it know where to find the JBoss server directory. The simplest way to do this is to set the JBOSS_HOME environment variable to the full path to your JBoss server directory. Alternatively, you can set the path in the jbossHome property in the Arquillian configuration file.
- Open the src/test/resources/arquillian.xml file located in the quickstart directory.
- Find the configuration for the JBoss container. It should look like this:
```
  
  <container qualifier="jboss" default="true">
      
      
      
      
  </container>           
```
- Uncomment the configuration element, find the jbossHome property and replace the "/path/to/jboss/as" value with the actual path to your JBoss EAP server.
- Run the test goal with the following profile activated:
```
  mvn clean test -Parq-jbossas-managed
```

Use JBoss Developer Studio or Eclipse to Run the Quickstarts

You can also deploy the quickstarts from Eclipse using JBoss tools. For more information on how to set up Maven and the JBoss tools, refer to the JBoss Enterprise Application Platform Development Guide or Get Started Developing Applications.

Optional Components

The following components are needed for only a small subset of the quickstarts. Do not install or configure them unless the quickstart requires it.

Add a User: Add a Management or Application user for the quickstarts that run in a secured mode.
Install and Configure the PostgreSQL Database: The PostgreSQL database is used for the distributed transaction quickstarts.
Install and Configure Byteman: This tool is used to demonstrate crash recovery for distributed transaction quickstarts.

Add a Management or Application User

By default, JBoss EAP is now distributed with security enabled for the management interfaces. A few of the quickstarts use these management interfaces and require that you create a management or application user to access the running application. A script is provided in the JBOSS_HOME/bin directory for that purpose.

The following procedures describe how to add a user with the appropriate permissions to run the quickstarts that depend on them.

Add a Management User

Open a command line

Type the command for your operating system

 For Linux:   JBOSS_HOME/bin/add-user.sh
 For Windows: JBOSS_HOME\bin\add-user.bat

You should see the following response:

 What type of user do you wish to add? 

 a) Management User (mgmt-users.properties) 
 b) Application User (application-users.properties)
 (a):

At the prompt, press enter to use the default Management User

You should see the following response:
```
 Enter the details of the new user to add.
 Realm (ManagementRealm) : 
```
If the quickstart README specifies a realm, type it here. Otherwise, press enter to use the default ManagementRealm.

When prompted, enter the following

 Username : admin
 Password : (choose a password for the admin user)

Repeat the password

Choose yes for the remaining promts.

Add an Application User

Open a command line

Type the command for your operating system

 For Linux:   JBOSS_HOME/bin/add-user.sh
 For Windows: JBOSS_HOME\bin\add-user.bat

You should see the following response:

 What type of user do you wish to add? 

 a) Management User (mgmt-users.properties) 
 b) Application User (application-users.properties)
 (a):

At the prompt, type: b

You should see the following response:
```
 Enter the details of the new user to add.
 Realm (ApplicationRealm) : 
```
If the quickstart README specifies a realm, type it here. Otherwise, press enter to use the default ApplicationRealm.
When prompted, enter the the Username and Passord. If the quickstart README specifies a Username and Password, enter them here. Otherwise, use the default Username quickstartUser and Password quickstartPwd1!.
```
 Username : quickstartUser
 Password : quickstartPwd1!
```
At the next prompt, you will be asked "What roles do you want this user to belong to?". If the quickstart README specifies a role to use, enter that here. Otherwise, type the role: guest

Install and Configure the PostgreSQL Database

Some of the quickstarts require the PostgreSQL database. This section describes how to install and configure the database for use with these quickstarts.

Download and Install PostgreSQL

The following is a brief overview of how to install PostgreSQL version 9.2. If you install a later version, be sure to modify the version when you issue the commands below. More detailed instructions for installing and starting PostgreSQL can be found on the internet.

Note: Although the database only needs to be installed once, to help partition each quickstart we recommend using a separate database per quickstart. Where you see QUICKSTART_DATABASENAME, you should replace that with the name provided in the particular quickstart's README

Linux Instructions

Use the following steps to install and configure PostgreSQL on Linux. You can download the PDF installation guide here: http://yum.postgresql.org/files/PostgreSQL-RPM-Installation-PGDG.pdf

Install PostgreSQL
- The yum install instructions for PostgreSQL can be found here: http://yum.postgresql.org/howtoyum.php/
- Download the repository RPM from here: http://yum.postgresql.org/repopackages.php/
- To install PostgreSQL, in a command line type sudo rpm -ivh RPM_FILE_NAME, where RPM_FILE_NAME is the name of the downloaded repository RPM file, for example:
```
  sudo rpm -ivh pgdg-fedora92-9.2-5.noarch.rpm
```
- Edit your distributions package manager definitions to exclude PostgreSQL. See the "important note" on http://yum.postgresql.org/howtoyum.php/ for details on how to exclude install-and-configure-the-postgresql-database packages from the repository of the distribution.
- Install postgresql92 and postgres92-server by typing the following in a command line:
```
  sudo yum install postgresql92 postgresql92-server
```
Set a password for the postgres user
- In a command line, login as root and set the postgres password by typing the following commands:
```
  su
  passwd postgres
```
- Choose a password
Configure the test database
- In a command line, login as the postgres user, navigate to the postgres directory, and initialize the database by typing:
```
  su postgres
  cd /usr/pgsql-9.2/bin/
  ./initdb -D /var/lib/pgsql/9.2/data
```
- Modify the /var/lib/pgsql/9.2/data/pg_hba.conf file to set the authentication scheme to password for tcp connections. Modify the line following the IPv4 local connections: change trust to to password. The line should look like this:
```
  host    all    all    127.0.0.1/32    password
```
- Modify the /var/lib/pgsql/9.2/data/postgresql.conf file to allow prepared transactions and reduce the maximum number of connections
```
  max_prepared_transactions = 10
  max_connections = 10
```
Start the database server
- In the same command line, type the following:
```
  ./postgres -D /var/lib/pgsql/9.2/data
```
- Note, this command does not release the command line. In the next step you need to open a new command line.
Create a database for the quickstart (as noted above, replace QUICKSTART_DATABASENAME with the name provided in the particular quickstart)
- Open a new command line and login again as the postgres user, navigate to the postgres directory, and create the database by typing the following:
```
  su postgres
  cd /usr/pgsql-9.2/bin/
  ./createdb QUICKSTART_DATABASENAME
```

Mac OS X Instructions

The following are the steps to install and start PostgreSQL on Mac OS X. Note that this guide covers only 'One click installer' option.

Install PostgreSQL using Mac OS X One click installer: http://www.postgresql.org/download/macosx/
Allow prepared transactions:
```
 sudo su - postgres
```
- Edit /Library/PostgreSQL/9.2/data/postgresql.conf to allow prepared transactions
```
  max_prepared_transactions = 10
```

Start the database server

 cd /Library/PostgreSQL/9.2/bin
 ./pg_ctl -D ../data restart

Create a database for the quickstart (as noted above, replace QUICKSTART_DATABASENAME with the name provided in the particular quickstart)
```
 ./createdb QUICKSTART_DATABASENAME
```

Verify that everything works. As the postgres user using the password you specified in Step 1, type the following:

cd /Library/PostgreSQL/9.2/bin
./psql -U postgres

At the prompt

start transaction;
select 1;
prepare transaction 'foobar';
commit prepared 'foobar';

Windows Instructions

Use the following steps to install and configure PostgreSQL on Windows:

Install PostgreSQL using the Windows installer: http://www.postgresql.org/download/windows/
Enable password authentication and configure PostgreSQL to allow prepared transactions
- Modify the C:\Program Files\PostgreSQL\9.2\data\pg_hba.conf file to set the authentication scheme to password for tcp connections. Modify the line following the IPv4 local connections: change trust to to password. The line should look like this:
```
  host    all    all    127.0.0.1/32    password`
```
- Modify the C:\Program Files\PostgreSQL\9.2\data\postgresql.conf file to allow prepared transactions and reduce the maximum number of connections:
```
  max_prepared_transactions = 10
  max_connections = 10
```
Start the database server
- Choose Start -> All Programs -> PostgreSQL 9.2\pgAdmin III
- Server Groups -> Servers (1) -> PostgreSQL 9.2 (localhost:5432)
- Right click -> Stop Service
- Right click -> Start Service
Create a database for the quickstart (as noted above, replace QUICKSTART_DATABASENAME with the name provided in the particular quickstart) * Open a command line
```
   cd C:\Program Files\PostgreSQL\9.2\bin\
   createdb.exe -U postgres QUICKSTART_DATABASENAME
```

Create a Database User

Make sure the PostgreSQL bin directory is in your PATH.
- Open a command line and change to the root directory psql
- If you see an error that 'psql' is not a recognized command, you need to add the PostgreSQL bin directory to your PATH environment variable.
As the postgres user, start the PostgreSQL interactive terminal by typing the following command:
```
psql -U postgres
```
Create the user sa with password sa and all privileges on the database by typing the following commands (as noted above, replace QUICKSTART_DATABASENAME with the name provided in the particular quickstart):
```
create user sa with password 'sa';
grant all privileges on database "QUICKSTART_DATABASENAME" to sa;
\q
```
Test the connection to the database using the TCP connection as user 'sa'. This validates that the change to pg_hba.conf was made correctly:
```
psql -h 127.0.0.1 -U sa QUICKSTART_DATABASENAME
```

Add the PostgreSQL Module to the JBoss server

Create the following directory structure: JBOSS_HOME/modules/org/postgresql/main
Download the JBDC driver from http://jdbc.postgresql.org/download.html and copy it into the directory you created in the previous step.

In the same directory, create a file named module.xml. Copy the following contents into the file:

 <?xml version="1.0" encoding="UTF-8"?>
 <module xmlns="urn:jboss:module:1.0" name="org.postgresql">
     <resources>
         <resource-root path="postgresql-9.2-1002.jdbc4.jar"/>
     </resources>
     <dependencies>
         <module name="javax.api"/>
         <module name="javax.transaction.api"/>
     </dependencies>
 </module>

Add the PostgreSQL Driver Configuration to the JBoss server

You can configure the driver by running the configure-postgresql.cli script provided in the root directory of the quickstarts, by using the JBoss CLI interactively, or by manually editing the configuration file.

NOTE - Before you begin:

If it is running, stop the JBoss EAP server.
Backup the file: JBOSS_HOME/standalone/configuration/standalone-full.xml
After you have completed testing the quickstarts, you can replace this file to restore the server to its original configuration.

Configure the Driver By Running the JBoss CLI Script

Start the JBoss EAP server by typing the following:

 For Linux:  JBOSS_HOME_SERVER_1/bin/standalone.sh -c standalone-full.xml
 For Windows:  JBOSS_HOME_SERVER_1\bin\standalone.bat -c standalone-full.xml

Open a new command line, navigate to the root directory of the quickstarts, and run the following command, replacing JBOSS_HOME with the path to your server:
```
 JBOSS_HOME/bin/jboss-cli.sh --connect --file=configure-postgresql.cli 
```

This script adds the PostgreSQL driver to the datasources subsystem in the server configuration. You should see the following result when you run the script:

    #1 /subsystem=datasources/jdbc-driver=postgresql:add(driver-name=postgresql,driver-module-name=org.postgresql,driver-xa-datasource-class-name=org.postgresql.xa.PGXADataSource)
    The batch executed successfully.
    {"outcome" => "success"}

Configure the Driver Using the JBoss CLI Interactively

Start the JBoss EAP server by typing the following:

 For Linux:  JBOSS_HOME_SERVER_1/bin/standalone.sh -c standalone-full.xml
 For Windows:  JBOSS_HOME_SERVER_1\bin\standalone.bat -c standalone-full.xml

To start the JBoss CLI tool, open a new command line, navigate to the JBOSS_HOME directory, and type the following:
```
 For Linux: bin/jboss-cli.sh --connect
 For Windows: bin\jboss-cli.bat --connect
```

At the prompt, type the following:

 [standalone@localhost:9999 /] /subsystem=datasources/jdbc-driver=postgresql:add(driver-name=postgresql,driver-module-name=org.postgresql,driver-xa-datasource-class-name=org.postgresql.xa.PGXADataSource)

Tell the server to reload the configuration:
```
  [standalone@localhost:9999 /] :reload
```

Configure the Driver By Manually Editing the Configuration File

If it is running, stop the JBoss EAP server.
Backup the file: JBOSS_HOME/standalone/configuration/standalone-full.xml
Open the JBOSS_HOME/standalone/configuration/standalone-full.xml file in an editor and locate the subsystem urn:jboss:domain:datasources:1.0.

Add the following driver to the <drivers> section that subsystem. You may need to merge with other drivers in that section:

<driver name="postgresql" module="org.postgresql">
    <xa-datasource-class>org.postgresql.xa.PGXADataSource</xa-datasource-class>
</driver>

Remove the PostgreSQL Configuration

When you are done testing the quickstarts, you can remove the PostgreSQL configuration by running the remove-postgresql.cli script provided in the root directory of the quickstarts or by manually restoring the back-up copy the configuration file.

Remove the PostgreSQL Configuration by Running the JBoss CLI Script

Start the JBoss EAP server by typing the following:

 For Linux:  JBOSS_HOME_SERVER_1/bin/standalone.sh -c standalone-full.xml
 For Windows:  JBOSS_HOME_SERVER_1\bin\standalone.bat -c standalone-full.xml

Open a new command line, navigate to the root directory of this quickstart, and run the following command, replacing JBOSS_HOME with the path to your server:
```
 JBOSS_HOME/bin/jboss-cli.sh --connect --file=remove-postgresql.cli 
```

This script removes PostgreSQL from the datasources subsystem in the server configuration. You should see the following result when you run the script:

    #1 /subsystem=datasources/jdbc-driver=postgresql:remove
    The batch executed successfully.
    {"outcome" => "success"}

Remove the PostgreSQL Configuration Manually

If it is running, stop the JBoss EAP server.
Replace the JBOSS_HOME/standalone/configuration/standalone-full.xml file with the back-up copy of the file.

Important Quickstart Testing Information

The installation of PostgreSQL is a one time procedure. However, unless you have set up the database to automatically start as a service, you must repeat the instructions "Start the database server" above for your operating system every time you reboot your machine.

Install and Configure Byteman

Byteman is used by a few of the quickstarts to demonstrate distributed transaction processing and crash recovery.

What is It?

Byteman is a tool which simplifies tracing and testing of Java programs. Byteman allows you to insert extra Java code into your application, either as it is loaded during JVM startup or after it has already started running. This code can be used to trace what the application is doing and to monitor and debug deployments to be sure it is operating correctly. You can also use Byteman to inject faults or synchronization code when testing your application. A few of the quickstarts use Byteman to halt an application server in the middle of a distributed transaction to demonstrate crash recovery.

Download and Configure Byteman

Download Byteman from http://www.jboss.org/byteman/downloads/
Extract the ZIP file to a directory of your choice.
By default, the Byteman download provides unrestricted permissions to others which can cause a problem when running Ruby commands for the OpenShift quickstarts. To restrict the permissions to others, open a command line and type the followinge:
```
 cd byteman-download-2.0.0/
 chmod -R o-rwx byteman-download-2.0.0/
```

Halt the Application Using Byteman

NOTE: The Byteman scripts only work in JTA mode. They do not work in JTS mode. If you have configured the server for a JTS quickstart, you must follow the instructions to Remove the JTS Configuration from the JBoss server before making the following changes. Otherwise Byteman will not halt the server.

When instructed to use Byteman to halt the application, perform the following steps:

Find the appropriate configuration file for your operating system in the list below.

 For Linux: JBOSS_HOME/bin/standalone.conf 
 For Windows: JBOSS_HOME\bin\standalone.conf.bat

Important: Make a backup copy of this file before making any modifications.
The quickstart README should specify the text you need to append to the server configuration file.
Open the configuration file and append the text specified by the quickstart to the end of the file. Make sure to replace the file paths with the correct location of your quickstarts and the Byteman download.

The following is an example of of the configuration changes needed for the jta-crash-rec quickstart:

For Linux, open the JBOSS_HOME/bin/standalone.conf file and append the following line:

 JAVA_OPTS="-javaagent:/PATH_TO_BYTEMAN_DOWNLOAD/lib/byteman.jar=script:/PATH_TO_QUICKSTARTS/jta-crash-rec/src/main/scripts/xa.btm ${JAVA_OPTS}"

For Windows, open the JBOSS_HOME\bin\standalone.conf.bat file and append the following line:

 SET "JAVA_OPTS=%JAVA_OPTS% -javaagent:C:PATH_TO_BYTEMAN_DOWNLOAD\lib\byteman.jar=script:C:\PATH_TO_QUICKSTARTS\jta-crash-rec\src\main\scripts\xa.btm %JAVA_OPTS%"

Disable the Byteman Script

When you are done testing the quickstart, remember to restore the configuration file with the backup copy you made in step 2 above.

Name		Name	Last commit message	Last commit date
Latest commit History 1,391 Commits
bean-validation		bean-validation
bmt		bmt
cdi-alternative		cdi-alternative
cdi-decorator		cdi-decorator
cdi-injection		cdi-injection
cdi-interceptors		cdi-interceptors
cdi-portable-extension		cdi-portable-extension
cdi-stereotype		cdi-stereotype
cdi-veto		cdi-veto
cluster-ha-singleton		cluster-ha-singleton
cmt		cmt
dist		dist
ejb-asynchronous		ejb-asynchronous
ejb-in-ear		ejb-in-ear
ejb-in-war		ejb-in-war
ejb-multi-server		ejb-multi-server
ejb-remote		ejb-remote
ejb-security-interceptors		ejb-security-interceptors
ejb-security		ejb-security
ejb-throws-exception		ejb-throws-exception
ejb-timer		ejb-timer
forge-from-scratch		forge-from-scratch
greeter		greeter
guide		guide
h2-console		h2-console
helloworld-jms		helloworld-jms
helloworld-mbean		helloworld-mbean
helloworld-mdb		helloworld-mdb
helloworld-osgi		helloworld-osgi
helloworld-rs		helloworld-rs
helloworld-singleton		helloworld-singleton
helloworld-ws		helloworld-ws
helloworld		helloworld
hibernate3		hibernate3
hibernate4		hibernate4
hornetq-clustering		hornetq-clustering
inter-app		inter-app
jax-rs-client		jax-rs-client
jta-crash-rec		jta-crash-rec
jts-distributed-crash-rec		jts-distributed-crash-rec
jts		jts
kitchensink-ear		kitchensink-ear
kitchensink-jsp		kitchensink-jsp
kitchensink-ml-ear		kitchensink-ml-ear
kitchensink-ml		kitchensink-ml
kitchensink		kitchensink
log4j		log4j
logging-tools		logging-tools
logging		logging
mail		mail
numberguess		numberguess
payment-cdi-event		payment-cdi-event
picketlink-sts		picketlink-sts
servlet-async		servlet-async
servlet-filterlistener		servlet-filterlistener
servlet-security-genericheader-auth		servlet-security-genericheader-auth
servlet-security		servlet-security
shopping-cart		shopping-cart
tasks-jsf		tasks-jsf
tasks-rs		tasks-rs
tasks		tasks
temperature-converter		temperature-converter
template		template
wicket-ear		wicket-ear
wicket-war		wicket-war
wsat-simple		wsat-simple
wsba-coordinator-completion-simple		wsba-coordinator-completion-simple
wsba-participant-completion-simple		wsba-participant-completion-simple
xml-dom4j		xml-dom4j
xml-jaxp		xml-jaxp
.gitignore		.gitignore
.quickstarts_ignore		.quickstarts_ignore
CONTRIBUTING.md		CONTRIBUTING.md
LICENSE.txt		LICENSE.txt
README.md		README.md
RELEASE_PROCEDURE.md		RELEASE_PROCEDURE.md
configure-postgresql.cli		configure-postgresql.cli
contributor-settings.xml		contributor-settings.xml
pom.xml		pom.xml
remove-postgresql.cli		remove-postgresql.cli
settings.xml		settings.xml

License

hhovsepy/jboss-eap-quickstarts

Folders and files

Latest commit

History

Repository files navigation

Red Hat JBoss Enterprise Application Platform (EAP) Quickstarts

Introduction

Available Quickstarts

Suggested Approach to the Quickstarts

System Requirements

Configure Maven

Configure Maven to Build and Deploy the Quickstarts

Restore Your Maven Configuration When You Finish Testing the Quickstarts

Maven Profiles

Run the Quickstarts

Start the JBoss Server

Start the Default JBoss Server

Start the JBoss Server with the Full Profile

Start the JBoss Server with Custom Configuration Options

Build and Deploy the Quickstarts

Build the Quickstart Archive

Build and Deploy the Quickstart Archive

Undeploy an Archive

Verify the Quickstarts Build with One Command

Undeploy the Deployed Quickstarts with One Command

Run the Arquillian Tests

Use JBoss Developer Studio or Eclipse to Run the Quickstarts

Optional Components

Add a Management or Application User

Add a Management User

Add an Application User

Install and Configure the PostgreSQL Database

Download and Install PostgreSQL

Linux Instructions

Mac OS X Instructions

Windows Instructions

Create a Database User

Add the PostgreSQL Module to the JBoss server

Add the PostgreSQL Driver Configuration to the JBoss server

Configure the Driver By Running the JBoss CLI Script

Configure the Driver Using the JBoss CLI Interactively

Configure the Driver By Manually Editing the Configuration File

Remove the PostgreSQL Configuration

Remove the PostgreSQL Configuration by Running the JBoss CLI Script

Remove the PostgreSQL Configuration Manually

Important Quickstart Testing Information

Install and Configure Byteman

What is It?

Download and Configure Byteman

Halt the Application Using Byteman

Disable the Byteman Script

About

Resources

License

Stars

Watchers

Forks

Releases

Packages 0

Packages