Pull request Compare This branch is 96 commits behind jboss-developer:2.7.0.Final-with-tutorials.
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
..
Failed to load latest commit information.
.settings
patches
src
README.md
admin_layer.fsh
pom.xml
update_import_sql.pl

README.md

TicketMonster - a JBoss example

TicketMonster is an online ticketing demo application that gets you started with JBoss technologies, in particular the JBoss Developer Framework, and helps you learn and evaluate them.

Here are a few instructions for building and running it. You can learn more about the example from the tutorial.

Updating the Performance dates

NOTE: This step is optional. It is necessary only if you want to update the dates of the Performances in the import.sql script in an automated manner. Updating the performance dates ensure that they are always set to some timestamp in the future, and ensures that all performances are visible in the Monitor section of the TicketMonster application.

  1. Run the update_import_sql Perl script. You'll need the DateTime, DateTime::Format::Strptime and Tie::File Perl modules. These are usually available by default in your Perl installation.

    $ perl update_import_sql.pl src/main/resources/import.sql
    

Generating the administration site

NOTE: This step is optional. The administration site is already present in the source code. If you want to regenerate it from Forge, and apply the changes outlined in the tutorial, you may continue to follow the steps outlined here. Otherwise, you can skip this step and proceed to build TicketMonster.

Before building and running TicketMonster, you must generate the administration site with Forge.

  1. Ensure that you have JBoss Forge installed. The current version of TicketMonster supports version 1.4.4.Final or higher of JBoss Forge.

  2. Start JBoss Forge

    $ forge
    
  3. Verify that the Forge plugin is installed by running

    $ forge list-plugins
    

    and verifying that org.jboss.forge.angularjs-scaffoldx-plugin is in the returned list.

    The version of the installed plugin must be 1.0.4.Final or higher. The version is present in the output of this command and it appears like so: org.jboss.forge.angularjs-scaffoldx-plugin:1.4.3.Final:1.0.4.Final-0b904c70-87c2-4ed9-9ec4-4868bfc02214. The plugin version is the second version string (1.0.4.Final) listed in the output; the first version string (1.4.3.Final) is the Forge API version used by the plugin.

  4. If the outcome of the previous step was that the AngularJS plugin was not installed, do that now

    $ forge install-plugin angularjs
    
  5. From the JBoss Forge prompt, execute the script for generating the administration site

    $ run admin_layer.fsh
    

Steps 3 and 4 need to be performed only once - after the plugin has been installed, it will be available on any subsequent runs of Forge.

On step 5, answer yes to all the the questions concerning patches. Deployment to JBoss EAP 6.2 is optional.

Building TicketMonster

TicketMonster can be built from Maven, by runnning the following Maven command:

mvn clean package

Building TicketMonster with tests

If you want to run the Arquillian tests as part of the build, you can enable one of the two available Arquillian profiles.

For running the tests in an already running application server instance, use the arq-jbossas-remote profile.

mvn clean package -Parq-jbossas-remote

If you want the test runner to start an application server instance, use the arq-jbossas-managed profile. You must set up the JBOSS_HOME property to point to the server location, or update the src/main/test/resources/arquillian.xml file.

mvn clean package -Parq-jbossas-managed

Building TicketMonster with Postgresql (for OpenShift)

If you intend to deploy into OpenShift, you can use the postgresql-openshift profile

mvn clean package -Ppostgresql-openshift

Running TicketMonster

You can run TicketMonster into a local JBoss EAP 6.2 instance or on OpenShift.

Running TicketMonster locally

Start JBoss Enterprise Application Platform 6.2

  1. Open a command line and navigate to the root of the JBoss server directory.
  2. The following shows the command line to start the server with the web profile:

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

Deploy TicketMonster

  1. Make sure you have started the JBoss Server as described above.
  2. Type this command to build and deploy the archive into a running server instance.

    mvn clean package jboss-as:deploy
    

    (You can use the arq-jbossas-remote profile for running tests as well)

  3. This will deploy target/ticket-monster.war to the running instance of the server.

  4. Now you can see the application running at http://localhost:8080/ticket-monster

Running TicketMonster in OpenShift

Create an OpenShift project

  1. Make sure that you have an OpenShift domain and you have created an application using the jbosseap-6 cartridge (for more details, get started here). If you want to use PostgreSQL, add the postgresql-8.4 cartridge too.
  2. Ensure that the Git repository of the project is checked out.

Building and deploying

  1. Build TicketMonster using either:

    • the default profile (with H2 database support)

      mvn clean package   
      
    • the postgresql-openshift profile (with PostgreSQL support) if the PostgreSQL cartrdige is enabled in OpenShift.

      mvn clean package -Ppostgresql-openshift
      
  2. Copy the target/ticket-monster.warfile in the OpenShift Git repository(located at <root-of-openshift-application-git-repository>).

    cp target/ticket-monster.war <root-of-openshift-application-git-repository>/deployments/ROOT.war
    
  3. Navigate to <root-of-openshift-application-git-repository> folder

  4. Remove the existing src folder and pom.xml file.

    git rm -r src
    git rm pom.xml
    
  5. Add the copied file to the repository, commit and push to Openshift

    git add deployments/ROOT.war
    git commit -m "Deploy TicketMonster"
    git push
    
  6. Now you can see the application running at http://<app-name>-<domain-name>.rhcloud.com

NOTE: this version of TicketMonster uses the binary deployment style.