Click File → Import to open the Import wizard.

Expand Maven, select Existing Maven Projects and click Next.

In the Root Directory field, enter the path to the TicketMonster source code. Alternatively, click Browse to navigate to the source code location. The Import Maven Project wizard recursively searches the path for a pom.xml file. The pom.xml file identifies the project as a Maven project. The file is listed under Projects once it is found.

Figure 1. pom.xml File Listed in the Projects Pane

Click Finish. When the import process is complete, the project is listed in the Project Explorer view.

In the Project Explorer view, right-click ticket-monster and click Run As → Run on Server.

Under How do you want to select the server?, ensure Choose an existing server is selected.

In the Server table, expand localhost, select jboss-eap-version where version denotes the JBoss EAP version, and click Next.

Figure 2. JBoss EAP 6.x Server Selected

Ensure ticket-monster is listed in the Configured column and click Finish. The Console view automatically becomes the view in focus and displays the output from the JBoss EAP server. Once deploying is complete, the web application opens in the default system web browser.

Figure 3. ticket-monster Listed in the Configured Column

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

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

Make sure you have started the JBoss Server as described above.

Type this command to build and deploy the archive into a running server instance.

mvn clean package jboss-as:deploy

mvn clean package jboss-as:deploy -s TICKETMONSTER_MAVEN_PROJECT_ROOT/settings.xml

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

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

Install the MySQL JBDC driver as a new JBoss module.

Register the MySQL datasource used by the application. Edit the server configuration file (standalone.xml), to add the datasource definition:

<datasources>
   <datasource jndi-name="java:jboss/datasources/TicketMonsterMySQLDS" pool-name="MySQLDS">
      <connection-url>jdbc:mysql://localhost:3306/ticketmonster</connection-url>
      <driver>com.mysql</driver>
      <transaction-isolation>TRANSACTION_READ_COMMITTED</transaction-isolation>
      <pool>
        <min-pool-size>10</min-pool-size>
        <max-pool-size>100</max-pool-size>
        <prefill>true</prefill>
      </pool>
      <security>
        <user-name>test</user-name>
        <password>test</password>
      </security>
      <statement>
        <prepared-statement-cache-size>32</prepared-statement-cache-size>
        <share-prepared-statements/>
      </statement>
    </datasource>
    <drivers>
      <driver name="com.mysql" module="com.mysql">
	  	<driver-class>com.mysql.jdbc.Driver</driver-class>
        <xa-datasource-class>com.mysql.jdbc.jdbc2.optional.MysqlXADataSource</xa-datasource-class>
      </driver>
    </drivers>
</datasources>

Build and deploy the application, using the mysql profile defined in the project POM :

Install the PostgreSQL JBDC driver as a new JBoss module.

Register the PostgreSQL datasource used by the application. Edit the server configuration file (standalone.xml), to add the datasource definition:

<datasources>
   <datasource jndi-name="java:jboss/datasources/TicketMonsterPostgreSQLDS" pool-name="PostgreSQLDS">
      <connection-url>jdbc:postgresql://localhost:5432/ticketmonster</connection-url>
      <driver>org.postgresql</driver>
      <transaction-isolation>TRANSACTION_READ_COMMITTED</transaction-isolation>
      <pool>
        <min-pool-size>10</min-pool-size>
        <max-pool-size>100</max-pool-size>
        <prefill>true</prefill>
      </pool>
      <security>
        <user-name>test</user-name>
        <password>test</password>
      </security>
      <statement>
        <prepared-statement-cache-size>32</prepared-statement-cache-size>
        <share-prepared-statements/>
      </statement>
    </datasource>
    <drivers>
      <driver name="org.postgresql" module="org.postgresql">
        <xa-datasource-class>org.postgresql.xa.PGXADataSource</xa-datasource-class>
      </driver>
    </drivers>
</datasources>

Build and deploy the application, using the postgresql profile defined in the project POM :