Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP

Loading…

Bz1025766: Replace JBoss server with JBoss EAP server #866

Merged
merged 1 commit into from

1 participant

@sgilda
Owner

No description provided.

@sgilda sgilda merged commit bb90516 into from
@sgilda sgilda deleted the branch
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Commits on Mar 3, 2014
  1. @sgilda
This page is out of date. Refresh to see the latest.
Showing with 351 additions and 351 deletions.
  1. +1 −1  README.md
  2. +3 −3 bean-validation/README.md
  3. +4 −4 bmt/README.md
  4. +4 −4 cdi-alternative/README.md
  5. +4 −4 cdi-decorator/README.md
  6. +4 −4 cdi-injection/README.md
  7. +5 −5 cdi-interceptors/README.md
  8. +3 −3 cdi-portable-extension/README.md
  9. +4 −4 cdi-stereotype/README.md
  10. +3 −3 cdi-veto/README.md
  11. +3 −3 cluster-ha-singleton/README.md
  12. +5 −5 cmt/README.md
  13. +4 −4 ejb-asynchronous/README.md
  14. +4 −4 ejb-in-ear/README.md
  15. +5 −5 ejb-in-war/README.md
  16. +3 −3 ejb-multi-server/README.md
  17. +5 −5 ejb-remote/README.md
  18. +12 −12 ejb-security-interceptors/README.md
  19. +4 −4 ejb-security/README.md
  20. +4 −4 ejb-throws-exception/README.md
  21. +6 −6 ejb-timer/README.md
  22. +4 −4 forge-from-scratch/README.md
  23. +4 −4 greeter/README.md
  24. +2 −2 h2-console/README.md
  25. +11 −11 helloworld-jms/README.md
  26. +5 −5 helloworld-mbean/README.md
  27. +6 −6 helloworld-mdb/README.md
  28. +3 −3 helloworld-mdb/src/main/java/org/jboss/as/quickstarts/servlet/HelloWorldMDBServletClient.java
  29. +5 −5 helloworld-osgi/README.md
  30. +4 −4 helloworld-rs/README.md
  31. +4 −4 helloworld-singleton/README.md
  32. +5 −5 helloworld-ws/README.md
  33. +4 −4 helloworld/README.md
  34. +4 −4 hibernate3/README.md
  35. +4 −4 hibernate4/README.md
  36. +10 −10 hornetq-clustering/README.md
  37. +4 −4 inter-app/README.md
  38. +1 −1  jax-rs-client/README.md
  39. +9 −9 jta-crash-rec/README.md
  40. +9 −9 jts-distributed-crash-rec/README.md
  41. +15 −15 jts/README.md
  42. +5 −5 kitchensink-ear/README.md
  43. +5 −5 kitchensink-jsp/README.md
  44. +5 −5 kitchensink-ml-ear/README.md
  45. +5 −5 kitchensink-ml/README.md
  46. +5 −5 kitchensink/README.md
  47. +4 −4 log4j/README.md
  48. +6 −6 logging-tools/README.md
  49. +9 −9 logging/README.md
  50. +4 −4 mail/README.md
  51. +4 −4 numberguess/README.md
  52. +4 −4 payment-cdi-event/README.md
  53. +10 −10 picketlink-sts/README.md
  54. +4 −4 servlet-async/README.md
  55. +4 −4 servlet-filterlistener/README.md
  56. +9 −9 servlet-security-genericheader-auth/README.md
  57. +10 −10 servlet-security/README.md
  58. +4 −4 shopping-cart/README.md
  59. +5 −5 tasks-jsf/README.md
  60. +4 −4 tasks-rs/README.md
  61. +3 −3 tasks/README.md
  62. +4 −4 temperature-converter/README.md
  63. +7 −7 template/README.md
  64. +6 −6 wicket-ear/README.md
  65. +6 −6 wicket-war/README.md
  66. +2 −2 wsat-simple/README.md
  67. +1 −1  wsat-simple/src/main/java/org/jboss/as/quickstarts/wsat/simple/servlet/WSATSimpleServletClient.java
  68. +2 −2 wsba-coordinator-completion-simple/README.md
  69. +2 −2 wsba-participant-completion-simple/README.md
  70. +4 −4 xml-dom4j/README.md
  71. +5 −5 xml-jaxp/README.md
View
2  README.md
@@ -54,7 +54,7 @@ The applications these projects produce are designed to be run on Red Hat JBoss
To run these quickstarts with the provided build scripts, you need the following:
-1. Java 1.6, to run JBoss AS and Maven. You can choose from the following:
+1. Java 1.6, to run JBoss EAP and Maven. You can choose from the following:
* OpenJDK
* Oracle Java SE
* Oracle JRockit
View
6 bean-validation/README.md
@@ -31,10 +31,10 @@ Configure Maven
If you have not yet done so, you must [Configure Maven](https://github.com/jboss-developer/jboss-developer-shared-resources/blob/master/guides/CONFIGURE_MAVEN.md#configure-maven-to-build-and-deploy-the-quickstarts) before testing the quickstarts.
-Start the JBoss Server
+Start the JBoss EAP Server
-------------------------
-1. Open a command prompt and navigate to the root of the JBoss server directory.
+1. Open a command prompt and navigate to the root of the JBoss EAP directory.
2. The following shows the command line to start the server:
For Linux: JBOSS_HOME/bin/standalone.sh
@@ -48,7 +48,7 @@ This quickstart provides Arquillian tests. By default, these tests are configure
_NOTE: The following commands assume you have configured your Maven user settings. If you have not, you must include Maven setting arguments on the command line. See [Run the Arquillian Tests](https://github.com/jboss-developer/jboss-developer-shared-resources/blob/master/guides/RUN_ARQUILLIAN_TESTS.md#run-the-arquillian-tests) for complete instructions and additional options._
-1. Make sure you have started the JBoss Server as described above.
+1. Make sure you have started the JBoss EAP server as described above.
2. Open a command prompt and navigate to the root directory of this quickstart.
3. Type the following command to run the test goal with the following profile activated:
View
8 bmt/README.md
@@ -40,10 +40,10 @@ Configure Maven
If you have not yet done so, you must [Configure Maven](https://github.com/jboss-developer/jboss-developer-shared-resources/blob/master/guides/CONFIGURE_MAVEN.md#configure-maven-to-build-and-deploy-the-quickstarts) before testing the quickstarts.
-Start the JBoss Server
+Start the JBoss EAP Server
-------------------------
-1. Open a command prompt and navigate to the root of the JBoss server directory.
+1. Open a command prompt and navigate to the root of the JBoss EAP directory.
2. The following shows the command line to start the server:
For Linux: JBOSS_HOME/bin/standalone.sh
@@ -55,7 +55,7 @@ Build and Deploy the Quickstart
_NOTE: The following build command assumes you have configured your Maven user settings. If you have not, you must include Maven setting arguments on the command line. See [Build and Deploy the Quickstarts](../README.md#build-and-deploy-the-quickstarts) for complete instructions and additional options._
-1. Make sure you have started the JBoss Server as described above.
+1. Make sure you have started the JBoss EAP server as described above.
2. Open a command prompt and navigate to the root directory of this quickstart.
3. Type this command to build and deploy the archive:
@@ -86,7 +86,7 @@ _Note:_ You will see the following warning in the server log. You can ignore thi
Undeploy the Archive
--------------------
-1. Make sure you have started the JBoss Server as described above.
+1. Make sure you have started the JBoss EAP server as described above.
2. Open a command prompt and navigate to the root directory of this quickstart.
3. When you are finished testing, type this command to undeploy the archive:
View
8 cdi-alternative/README.md
@@ -39,10 +39,10 @@ Configure Maven
If you have not yet done so, you must [Configure Maven](https://github.com/jboss-developer/jboss-developer-shared-resources/blob/master/guides/CONFIGURE_MAVEN.md#configure-maven-to-build-and-deploy-the-quickstarts) before testing the quickstarts.
-Start the JBoss Server
+Start the JBoss EAP Server
-------------------------
-1. Open a command prompt and navigate to the root of the JBoss server directory.
+1. Open a command prompt and navigate to the root of the JBoss EAP directory.
2. The following shows the command line to start the server:
For Linux: JBOSS_HOME/bin/standalone.sh
@@ -54,7 +54,7 @@ Build and Deploy the Quickstart
_NOTE: The following build command assumes you have configured your Maven user settings. If you have not, you must include Maven setting arguments on the command line. See [Build and Deploy the Quickstarts](../README.md#build-and-deploy-the-quickstarts) for complete instructions and additional options._
-1. Make sure you have started the JBoss Server as described above.
+1. Make sure you have started the JBoss EAP server as described above.
2. Open a command prompt and navigate to the root directory of this quickstart.
3. Type this command to build and deploy the archive:
@@ -79,7 +79,7 @@ comment the '<alternatives>' block in the WEB-INF/beans.xml file and redeploy th
Undeploy the Archive
--------------------
-1. Make sure you have started the JBoss Server as described above.
+1. Make sure you have started the JBoss EAP server as described above.
2. Open a command prompt and navigate to the root directory of this quickstart.
3. When you are finished testing, type this command to undeploy the archive:
View
8 cdi-decorator/README.md
@@ -31,10 +31,10 @@ Configure Maven
If you have not yet done so, you must [Configure Maven](https://github.com/jboss-developer/jboss-developer-shared-resources/blob/master/guides/CONFIGURE_MAVEN.md#configure-maven-to-build-and-deploy-the-quickstarts) before testing the quickstarts.
-Start the JBoss Server
+Start the JBoss EAP Server
-------------------------
-1. Open a command prompt and navigate to the root of the JBoss server directory.
+1. Open a command prompt and navigate to the root of the JBoss EAP directory.
2. The following shows the command line to start the server:
For Linux: JBOSS_HOME/bin/standalone.sh
@@ -46,7 +46,7 @@ Build and Deploy the Quickstart
_NOTE: The following build command assumes you have configured your Maven user settings. If you have not, you must include Maven setting arguments on the command line. See [Build and Deploy the Quickstarts](../README.md#build-and-deploy-the-quickstarts) for complete instructions and additional options._
-1. Make sure you have started the JBoss Server as described above.
+1. Make sure you have started the JBoss EAP server as described above.
2. Open a command prompt and navigate to the root directory of this quickstart.
3. Type this command to build and deploy the archive:
@@ -74,7 +74,7 @@ comment the 'decorators' block in the WEB-INF/beans.xml file and redeploy the qu
Undeploy the Archive
--------------------
-1. Make sure you have started the JBoss Server as described above.
+1. Make sure you have started the JBoss EAP server as described above.
2. Open a command prompt and navigate to the root directory of this quickstart.
3. When you are finished testing, type this command to undeploy the archive:
View
8 cdi-injection/README.md
@@ -28,10 +28,10 @@ Configure Maven
If you have not yet done so, you must [Configure Maven](https://github.com/jboss-developer/jboss-developer-shared-resources/blob/master/guides/CONFIGURE_MAVEN.md#configure-maven-to-build-and-deploy-the-quickstarts) before testing the quickstarts.
-Start the JBoss Server
+Start the JBoss EAP Server
-------------------------
-1. Open a command prompt and navigate to the root of the JBoss server directory.
+1. Open a command prompt and navigate to the root of the JBoss EAP directory.
2. The following shows the command line to start the server:
For Linux: JBOSS_HOME/bin/standalone.sh
@@ -43,7 +43,7 @@ Build and Deploy the Quickstart
_NOTE: The following build command assumes you have configured your Maven user settings. If you have not, you must include Maven setting arguments on the command line. See [Build and Deploy the Quickstarts](../README.md#build-and-deploy-the-quickstarts) for complete instructions and additional options._
-1. Make sure you have started the JBoss Server as described above.
+1. Make sure you have started the JBoss EAP server as described above.
2. Open a command prompt and navigate to the root directory of this quickstart.
3. Type this command to build and deploy the archive:
@@ -61,7 +61,7 @@ The application will be running at the following URL <http://localhost:8080/jbos
Undeploy the Archive
--------------------
-1. Make sure you have started the JBoss Server as described above.
+1. Make sure you have started the JBoss EAP server as described above.
2. Open a command prompt and navigate to the root directory of this quickstart.
3. When you are finished testing, type this command to undeploy the archive:
View
10 cdi-interceptors/README.md
@@ -29,10 +29,10 @@ Configure Maven
If you have not yet done so, you must [Configure Maven](https://github.com/jboss-developer/jboss-developer-shared-resources/blob/master/guides/CONFIGURE_MAVEN.md#configure-maven-to-build-and-deploy-the-quickstarts) before testing the quickstarts.
-Start the JBoss Server
+Start the JBoss EAP Server
-------------------------
-1. Open a command prompt and navigate to the root of the JBoss server directory.
+1. Open a command prompt and navigate to the root of the JBoss EAP directory.
2. The following shows the command line to start the server:
For Linux: JBOSS_HOME/bin/standalone.sh
@@ -44,7 +44,7 @@ Build and Deploy the Quickstart
_NOTE: The following build command assumes you have configured your Maven user settings. If you have not, you must include Maven setting arguments on the command line. See [Build and Deploy the Quickstarts](../README.md#build-and-deploy-the-quickstarts) for complete instructions and additional options._
-1. Make sure you have started the JBoss Server as described above.
+1. Make sure you have started the JBoss EAP server as described above.
2. Open a command prompt and navigate to the root directory of this quickstart.
3. Type this command to build and deploy the archive:
@@ -81,7 +81,7 @@ _Note:_ You will see the following warnings and errors in the server log. Hibern
Undeploy the Archive
--------------------
-1. Make sure you have started the JBoss Server as described above.
+1. Make sure you have started the JBoss EAP server as described above.
2. Open a command prompt and navigate to the root directory of this quickstart.
3. When you are finished testing, type this command to undeploy the archive:
@@ -95,7 +95,7 @@ This quickstart provides Arquillian tests. By default, these tests are configure
_NOTE: The following commands assume you have configured your Maven user settings. If you have not, you must include Maven setting arguments on the command line. See [Run the Arquillian Tests](https://github.com/jboss-developer/jboss-developer-shared-resources/blob/master/guides/RUN_ARQUILLIAN_TESTS.md#run-the-arquillian-tests) for complete instructions and additional options._
-1. Make sure you have started the JBoss Server as described above.
+1. Make sure you have started the JBoss EAP server as described above.
2. Open a command prompt and navigate to the root directory of this quickstart.
3. Type the following command to run the test goal with the following profile activated:
View
6 cdi-portable-extension/README.md
@@ -41,10 +41,10 @@ Contributor: You can copy or link to the Maven configuration information in the
If you have not yet done so, you must [Configure Maven](https://github.com/jboss-developer/jboss-developer-shared-resources/blob/master/guides/CONFIGURE_MAVEN.md#configure-maven-to-build-and-deploy-the-quickstarts) before testing the quickstarts.
-Start the JBoss Server
+Start the JBoss EAP Server
-------------------------
-1. Open a command prompt and navigate to the root of the JBoss server directory.
+1. Open a command prompt and navigate to the root of the JBoss EAP directory.
2. The following shows the command line to start the server:
For Linux: JBOSS_HOME/bin/standalone.sh
@@ -58,7 +58,7 @@ This quickstart provides Arquillian tests. By default, these tests are configure
_NOTE: The following commands assume you have configured your Maven user settings. If you have not, you must include Maven setting arguments on the command line. See [Run the Arquillian Tests](https://github.com/jboss-developer/jboss-developer-shared-resources/blob/master/guides/RUN_ARQUILLIAN_TESTS.md#run-the-arquillian-tests) for complete instructions and additional options._
-1. Make sure you have started the JBoss Server as described above.
+1. Make sure you have started the JBoss EAP server as described above.
2. Open a command prompt and navigate to the root directory of this quickstart.
3. Type the following command to run the test goal with the following profile activated:
View
8 cdi-stereotype/README.md
@@ -34,10 +34,10 @@ Configure Maven
If you have not yet done so, you must [Configure Maven](https://github.com/jboss-developer/jboss-developer-shared-resources/blob/master/guides/CONFIGURE_MAVEN.md#configure-maven-to-build-and-deploy-the-quickstarts) before testing the quickstarts.
-Start the JBoss Server
+Start the JBoss EAP Server
-------------------------
-1. Open a command prompt and navigate to the root of the JBoss server directory.
+1. Open a command prompt and navigate to the root of the JBoss EAP directory.
2. The following shows the command line to start the server:
For Linux: JBOSS_HOME/bin/standalone.sh
@@ -49,7 +49,7 @@ Build and Deploy the Quickstart
_NOTE: The following build command assumes you have configured your Maven user settings. If you have not, you must include Maven setting arguments on the command line. See [Build and Deploy the Quickstarts](../README.md#build-and-deploy-the-quickstarts) for complete instructions and additional options._
-1. Make sure you have started the JBoss Server as described above.
+1. Make sure you have started the JBoss EAP server as described above.
2. Open a command prompt and navigate to the root directory of this quickstart.
3. Type this command to build and deploy the archive:
@@ -87,7 +87,7 @@ _Note:_ You will see the following warnings and errors in the server log. Hibern
Undeploy the Archive
--------------------
-1. Make sure you have started the JBoss Server as described above.
+1. Make sure you have started the JBoss EAP server as described above.
2. Open a command prompt and navigate to the root directory of this quickstart.
3. When you are finished testing, type this command to undeploy the archive:
View
6 cdi-veto/README.md
@@ -40,10 +40,10 @@ Configure Maven
If you have not yet done so, you must [Configure Maven](https://github.com/jboss-developer/jboss-developer-shared-resources/blob/master/guides/CONFIGURE_MAVEN.md#configure-maven-to-build-and-deploy-the-quickstarts) before testing the quickstarts.
-Start the JBoss Server
+Start the JBoss EAP Server
-------------------------
-1. Open a command prompt and navigate to the root of the JBoss server directory.
+1. Open a command prompt and navigate to the root of the JBoss EAP directory.
2. The following shows the command line to start the server:
For Linux: JBOSS_HOME/bin/standalone.sh
@@ -57,7 +57,7 @@ This quickstart provides Arquillian tests. By default, these tests are configure
_NOTE: The following commands assume you have configured your Maven user settings. If you have not, you must include Maven setting arguments on the command line. See [Run the Arquillian Tests](https://github.com/jboss-developer/jboss-developer-shared-resources/blob/master/guides/RUN_ARQUILLIAN_TESTS.md#run-the-arquillian-tests) for complete instructions and additional options._
-1. Make sure you have started the JBoss Server as described above.
+1. Make sure you have started the JBoss EAP server as described above.
2. Open a command prompt and navigate to the root directory of this quickstart.
3. Type the following command to run the test goal with the following profile activated:
View
6 cluster-ha-singleton/README.md
@@ -40,7 +40,7 @@ You can copy or link to the Maven configuration information in the README file i
If you have not yet done so, you must [Configure Maven](https://github.com/jboss-developer/jboss-developer-shared-resources/blob/master/guides/CONFIGURE_MAVEN.md#configure-maven-to-build-and-deploy-the-quickstarts) before testing the quickstarts.
-Start the JBoss Server with a HA profile
+Start the JBoss EAP Server with a HA profile
-------------------------
If you run a non HA profile the singleton service will not start correctly. To run the example one instance must be started, to see the singleton behaviour at minimum two instances
@@ -55,7 +55,7 @@ Build and Deploy the Quickstart
_NOTE: The following build command assumes you have configured your Maven user settings. If you have not, you must include Maven setting arguments on the command line. See [Build and Deploy the Quickstarts](../README.md#build-and-deploy-the-quickstarts) for complete instructions and additional options._
-1. Make sure you have started the JBoss Server as described above.
+1. Make sure you have started the JBoss EAP server as described above.
2. Open a command prompt and navigate to the root directory of this quickstart.
3. Type this command to build and deploy the archive:
@@ -101,7 +101,7 @@ Check the timer
Undeploy the Archive
--------------------
-1. Make sure you have started the JBoss Server as described above.
+1. Make sure you have started the JBoss EAP server as described above.
2. Open a command prompt and navigate to the root directory of this quickstart.
3. When you are finished testing, type this command to undeploy the archive:
View
10 cmt/README.md
@@ -67,13 +67,13 @@ _Note_: For the purpose of this quickstart, replace the word `QUICKSTART_DATABAS
1. Be sure to start the PostgreSQL database. Unless you have set up the database to automatically start as a service, you must repeat the instructions "Start the database server" for your operating system every time you reboot your machine.
2. Follow the instructions to [Add the PostgreSQL Module to the JBoss EAP Server](https://github.com/jboss-developer/jboss-developer-shared-resources/blob/master/guides/CONFIGURE_POSTGRESQL.md#add-the-postgresql-module-to-the-jboss-eap-server).
-3. Follow the instructions to [Configure the PostgreSQL Driver in the JBoss Server](https://github.com/jboss-developer/jboss-developer-shared-resources/blob/master/guides/CONFIGURE_POSTGRESQL.md#configure-the-postgresql-driver-in-the-jboss-server).
+3. Follow the instructions to [Configure the PostgreSQL Driver in the JBoss EAP Server](https://github.com/jboss-developer/jboss-developer-shared-resources/blob/master/guides/CONFIGURE_POSTGRESQL.md#configure-the-postgresql-driver-in-the-jboss-eap-server).
-Start the JBoss Server with the Full Profile
+Start the JBoss EAP Server with the Full Profile
---------------
-1. Open a command prompt and navigate to the root of the JBoss server directory.
+1. Open a command prompt and navigate to the root of the JBoss EAP directory.
2. The following shows the command line to start the server with the full profile:
For Linux: JBOSS_HOME/bin/standalone.sh -c standalone-full.xml
@@ -86,7 +86,7 @@ Build and Deploy the Quickstart
_NOTE: The following build command assumes you have configured your Maven user settings. If you have not, you must include Maven setting arguments on the command line. See [Build and Deploy the Quickstarts](../README.md#build-and-deploy-the-quickstarts) for complete instructions and additional options._
-1. Make sure you have started the JBoss Server with the PostgreSQL driver
+1. Make sure you have started the JBoss EAP server with the PostgreSQL driver
2. Open a command prompt and navigate to the root directory of this quickstart.
3. Type this command to build and deploy the archive:
@@ -123,7 +123,7 @@ _Note:_ You will see the following errors in the server log. Hibernate attempts
Undeploy the Archive
--------------------
-1. Make sure you have started the JBoss Server as described above.
+1. Make sure you have started the JBoss EAP server as described above.
2. Open a command prompt and navigate to the root directory of this quickstart.
3. When you are finished testing, type this command to undeploy the archive:
View
8 ejb-asynchronous/README.md
@@ -38,10 +38,10 @@ If you have not yet done so, you must [Configure Maven](https://github.com/jboss
-Start the JBoss Server
+Start the JBoss EAP Server
-------------------------
-1. Open a command prompt and navigate to the root of the JBoss server directory.
+1. Open a command prompt and navigate to the root of the JBoss EAP directory.
2. The following shows the command line to start the server:
For Linux: JBOSS_HOME/bin/standalone.sh
@@ -53,7 +53,7 @@ Build and Deploy the Quickstart
_NOTE: The following build command assumes you have configured your Maven user settings. If you have not, you must include Maven setting arguments on the command line. See [Build and Deploy the Quickstarts](../README.md#build-and-deploy-the-quickstarts) for complete instructions and additional options._
-1. Make sure you have started the JBoss Server as described above.
+1. Make sure you have started the JBoss EAP server as described above.
2. Open a command prompt and navigate to the root directory of this quickstart.
3. Type this command to build and deploy the archive:
@@ -98,7 +98,7 @@ _NOTE: In EAP 6.2, you may see the following errors in the server log after the
Undeploy the Archive
--------------------
-1. Make sure you have started the JBoss Server as described above.
+1. Make sure you have started the JBoss EAP server as described above.
2. Open a command prompt and navigate to the root directory of this quickstart.
3. When you are finished testing, type this command to undeploy the archive:
View
8 ejb-in-ear/README.md
@@ -46,10 +46,10 @@ Configure Maven
If you have not yet done so, you must [Configure Maven](https://github.com/jboss-developer/jboss-developer-shared-resources/blob/master/guides/CONFIGURE_MAVEN.md#configure-maven-to-build-and-deploy-the-quickstarts) before testing the quickstarts.
-Start the JBoss Server
+Start the JBoss EAP Server
-------------------------
-1. Open a command prompt and navigate to the root of the JBoss server directory.
+1. Open a command prompt and navigate to the root of the JBoss EAP directory.
2. The following shows the command line to start the server:
For Linux: JBOSS_HOME/bin/standalone.sh
@@ -61,7 +61,7 @@ Build and Deploy the Quickstart
_NOTE: The following build command assumes you have configured your Maven user settings. If you have not, you must include Maven setting arguments on the command line. See [Build and Deploy the Quickstarts](../README.md#build-and-deploy-the-quickstarts) for complete instructions and additional options._
-1. Make sure you have started the JBoss Server as described above.
+1. Make sure you have started the JBoss EAP server as described above.
2. Open a command prompt and navigate to the root directory of this quickstart.
3. Type this command to build and deploy the archive:
@@ -82,7 +82,7 @@ Enter a name in the input field and click the _Greet_ button to see the response
Undeploy the Archive
--------------------
-1. Make sure you have started the JBoss Server as described above.
+1. Make sure you have started the JBoss EAP server as described above.
2. Open a command prompt and navigate to the root directory of this quickstart.
3. When you are finished testing, type this command to undeploy the archive:
View
10 ejb-in-war/README.md
@@ -35,10 +35,10 @@ Configure Maven
If you have not yet done so, you must [Configure Maven](https://github.com/jboss-developer/jboss-developer-shared-resources/blob/master/guides/CONFIGURE_MAVEN.md#configure-maven-to-build-and-deploy-the-quickstarts) before testing the quickstarts.
-Start the JBoss Server
+Start the JBoss EAP Server
-------------------------
-1. Open a command prompt and navigate to the root of the JBoss server directory.
+1. Open a command prompt and navigate to the root of the JBoss EAP directory.
2. The following shows the command line to start the server:
For Linux: JBOSS_HOME/bin/standalone.sh
@@ -50,7 +50,7 @@ Build and Deploy the Quickstart
_NOTE: The following build command assumes you have configured your Maven user settings. If you have not, you must include Maven setting arguments on the command line. See [Build and Deploy the Quickstarts](../README.md#build-and-deploy-the-quickstarts) for complete instructions and additional options._
-1. Make sure you have started the JBoss Server as described above.
+1. Make sure you have started the JBoss EAP server as described above.
2. Open a command prompt and navigate to the root directory of this quickstart.
3. Type this command to build and deploy the archive:
@@ -68,7 +68,7 @@ The application will be running at the following URL <http://localhost:8080/jbos
Undeploy the Archive
--------------------
-1. Make sure you have started the JBoss Server as described above.
+1. Make sure you have started the JBoss EAP server as described above.
2. Open a command prompt and navigate to the root directory of this quickstart.
3. When you are finished testing, type this command to undeploy the archive:
@@ -82,7 +82,7 @@ This quickstart provides Arquillian tests. By default, these tests are configure
_NOTE: The following commands assume you have configured your Maven user settings. If you have not, you must include Maven setting arguments on the command line. See [Run the Arquillian Tests](https://github.com/jboss-developer/jboss-developer-shared-resources/blob/master/guides/RUN_ARQUILLIAN_TESTS.md#run-the-arquillian-tests) for complete instructions and additional options._
-1. Make sure you have started the JBoss Server as described above.
+1. Make sure you have started the JBoss EAP server as described above.
2. Open a command prompt and navigate to the root directory of this quickstart.
3. Type the following command to run the test goal with the following profile activated:
View
6 ejb-multi-server/README.md
@@ -92,7 +92,7 @@ You configure the domain server by running JBoss CLI commands. For your convenie
JBOSS_HOME/domain/configuration/host.xml
* After you have completed testing and undeployed this quickstart, you can replace these files to restore the server to its original configuration.
4. Start the JBoss EAP server
- * Open a command prompt and navigate to the root of the server directory.
+ * Open a command prompt and navigate to the root of the EAP directory.
* Start the server using the following command:
bin/domain.sh
@@ -216,7 +216,7 @@ Build and Deploy the Quickstart
_NOTE: The following build command assumes you have configured your Maven user settings. If you have not, you must include Maven setting arguments on the command line. See [Build and Deploy the Quickstarts](../README.md#buildanddeploy) for complete instructions and additional options._
-1. Make sure you have started and configured the JBoss Server successful as described above.
+1. Make sure you have started and configured the JBoss EAP server successfully as described above.
2. Open a command prompt and navigate to the root directory of this quickstart.
3. Type this command to build the artifacts:
@@ -323,7 +323,7 @@ _NOTE : A new feature in EAP 6.1 or later will deny the invocation of unsecured
Undeploy the Archives
--------------------
-1. Make sure you have started the JBoss Server as described above.
+1. Make sure you have started the JBoss EAP server as described above.
2. Open a command prompt and navigate to the root directory of this quickstart.
3. When you are finished testing, type this command to undeploy the archive:
View
10 ejb-remote/README.md
@@ -39,10 +39,10 @@ Configure Maven
If you have not yet done so, you must [Configure Maven](https://github.com/jboss-developer/jboss-developer-shared-resources/blob/master/guides/CONFIGURE_MAVEN.md#configure-maven-to-build-and-deploy-the-quickstarts) before testing the quickstarts.
-Start the JBoss Server
+Start the JBoss EAP Server
-------------------------
-1. Open a command prompt and navigate to the root of the JBoss server directory.
+1. Open a command prompt and navigate to the root of the JBoss EAP directory.
2. The following shows the command line to start the server:
For Linux: JBOSS_HOME/bin/standalone.sh
@@ -54,7 +54,7 @@ Build and Deploy the Quickstart
Since this quickstart builds two separate components, you can not use the standard *Build and Deploy* commands used by most of the other quickstarts. You must follow these steps to build, deploy, and run this quickstart.
-1. Make sure you have started the JBoss server. See the instructions in the previous section.
+1. Make sure you have started the JBoss EAP server. See the instructions in the previous section.
2. Open a command prompt and navigate to the ejb-remote quickstart directory
3. Build and install the server side component:
* Navigate to the server-side subdirectory:
@@ -63,7 +63,7 @@ Since this quickstart builds two separate components, you can not use the standa
* Build the EJB and client interfaces JARs and install them in your local Maven repository.
mvn clean install
- * Deploy the EJB JAR to your server. This maven goal will deploy `server-side/target/jboss-ejb-remote-server-side.jar`. You can check the JBoss server console to see information messages regarding the deployment.
+ * Deploy the EJB JAR to your server. This maven goal will deploy `server-side/target/jboss-ejb-remote-server-side.jar`. You can check the JBoss EAP server console to see information messages regarding the deployment.
mvn jboss-as:deploy
4. Build and run the client application
@@ -144,7 +144,7 @@ The remote client application can also be built as a standalone executable JAR w
Undeploy the Archive
--------------------
-To undeploy the server side component from the JBoss server:
+To undeploy the server side component from the JBoss EAP server:
1. Navigate to the server-side subdirectory:
View
24 ejb-security-interceptors/README.md
@@ -86,7 +86,7 @@ It is recommended that you test this approach in a separate and clean environmen
Add the Application Users
---------------
-This quickstart uses secured management interfaces and is built around the default `ApplicationRealm` as configured in the JBoss EAP server distribution. You must create the following application users to access the running application:
+This quickstart uses secured management interfaces and is built around the default `ApplicationRealm` as configured in the JBoss EAP distribution. You must create the following application users to access the running application:
| **UserName** | **Realm** | **Password** | **Roles** |
|:-----------|:-----------|:-----------|:-----------|
@@ -117,7 +117,7 @@ If you prefer, you can use the add-user utility interactively.
For an example of how to use the add-user utility, see instructions in the root README file located here: [Add an Application User](https://github.com/jboss-developer/jboss-developer-shared-resources/blob/master/guides/CREATE_USERS.md#add-an-application-user).
-Configure the JBoss Server
+Configure the JBoss EAP Server
---------------------------
These steps assume you are running the server in standalone mode and using the default standalone.xml supplied with the distribution.
@@ -125,11 +125,11 @@ These steps assume you are running the server in standalone mode and using the d
You configure the security domain by running JBoss CLI commands. For your convenience, this quickstart batches the commands into a `configure-security-domain.cli` script provided in the root directory of this quickstart.
1. Before you begin, back up your server configuration file
- * If it is running, stop the JBoss server.
+ * If it is running, stop the JBoss EAP server.
* Backup the file: `JBOSS_HOME/standalone/configuration/standalone.xml`
* After you have completed testing this quickstart, you can replace this file to restore the server to its original configuration.
-2. Start the JBoss server by typing the following:
+2. Start the JBoss EAP server by typing the following:
For Linux: JBOSS_HOME/bin/standalone.sh
For Windows: JBOSS_HOME\bin\standalone.bat
@@ -157,7 +157,7 @@ You should see the following result when you run the script:
Review the Modified Server Configuration
-----------------------------------
-If you want to review and understand newly added XML configuration, stop the JBoss server and open the `JBOSS_HOME/standalone/configuration/standalone.xml` file.
+If you want to review and understand newly added XML configuration, stop the JBoss EAP server and open the `JBOSS_HOME/standalone/configuration/standalone.xml` file.
1. The following `quickstart-domain` security-domain was added to the `security` subsystem.
@@ -225,10 +225,10 @@ If you want to review and understand newly added XML configuration, stop the JBo
-Start the JBoss Server
+Start the JBoss EAP Server
-------------------------
-1. Open a command prompt and navigate to the root of the JBoss server directory.
+1. Open a command prompt and navigate to the root of the JBoss EAP directory.
2. The following shows the command line to start the server:
For Linux: JBOSS_HOME/bin/standalone.sh
@@ -240,7 +240,7 @@ Build and Deploy the Quickstart
_NOTE: The following build command assumes you have configured your Maven user settings. If you have not, you must include Maven setting arguments on the command line. See [Build and Deploy the Quickstarts](../README.md#build-and-deploy-the-quickstarts) for complete instructions and additional options._
-1. Make sure you have started the JBoss Server as described above.
+1. Make sure you have started the JBoss EAP server as described above.
2. Open a command prompt and navigate to the root directory of this quickstart.
3. Type this command to build and deploy the archive:
@@ -399,7 +399,7 @@ When you run the `mvn exec:exec` command, you see the following output.
Investigate the Server Console Output
----------------------------
-Look at the JBoss Application Server console or Server log and you should see exceptions (the stacktraces were not included here) in the log like the following:
+Look at the JBoss EAP server console or log and you should see exceptions (the stacktraces were not included here) in the log like the following:
09:16:01,133 ERROR [org.jboss.as.ejb3.invocation] (EJB default - 6) JBAS014134: EJB Invocation failed on component SecuredEJB for method public abstract boolean org.jboss.as.quickstarts.ejb_security_interceptors.SecuredEJBRemote.roleOneMethod(): javax.ejb.EJBAccessException: JBAS014502: Invocation on method: public abstract boolean org.jboss.as.quickstarts.ejb_security_interceptors.SecuredEJBRemote.roleOneMethod() of bean: SecuredEJB is not allowed
09:16:01,198 ERROR [org.jboss.as.ejb3.invocation] (EJB default - 9) JBAS014134: EJB Invocation failed on component SecuredEJB for method public abstract boolean org.jboss.as.quickstarts.ejb_security_interceptors.SecuredEJBRemote.roleTwoMethod(): javax.ejb.EJBAccessException: JBAS014502: Invocation on method: public abstract boolean org.jboss.as.quickstarts.ejb_security_interceptors.SecuredEJBRemote.roleTwoMethod() of bean: SecuredEJB is not allowed
@@ -424,7 +424,7 @@ Look at the JBoss Application Server console or Server log and you should see ex
Undeploy the Archive
--------------------
-1. Make sure you have started the JBoss Server as described above.
+1. Make sure you have started the JBoss EAP server as described above.
2. Open a command prompt and navigate to the root directory of this quickstart.
3. When you are finished testing, type this command to undeploy the archive:
@@ -438,7 +438,7 @@ You can remove the security domain configuration by running the `remove-securit
### Remove the Security Domain Configuration by Running the JBoss CLI Script
-1. Start the JBoss server by typing the following:
+1. Start the JBoss EAP server by typing the following:
For Linux: JBOSS_HOME_SERVER_1/bin/standalone.sh
For Windows: JBOSS_HOME_SERVER_1\bin\standalone.bat
@@ -456,7 +456,7 @@ This script removes the `test` queue from the `messaging` subsystem in the serve
### Remove the Security Domain Configuration Manually
-1. If it is running, stop the JBoss server.
+1. If it is running, stop the JBoss EAP server.
2. Replace the `JBOSS_HOME/standalone/configuration/standalone.xml` file with the back-up copy of the file.
View
8 ejb-security/README.md
@@ -76,10 +76,10 @@ If you prefer, you can use the add-user utility interactively.
For an example of how to use the add-user utility, see instructions in the root README file located here: [Add an Application User](https://github.com/jboss-developer/jboss-developer-shared-resources/blob/master/guides/CREATE_USERS.md#add-an-application-user).
-Start the JBoss Server
+Start the JBoss EAP Server
-------------------------
-1. Open a command prompt and navigate to the root of the JBoss server directory.
+1. Open a command prompt and navigate to the root of the JBoss EAP directory.
2. The following shows the command line to start the server:
For Linux: JBOSS_HOME/bin/standalone.sh
@@ -91,7 +91,7 @@ Build and Deploy the Quickstart
_NOTE: The following build command assumes you have configured your Maven user settings. If you have not, you must include Maven setting arguments on the command line. See [Build and Deploy the Quickstarts](../README.md#build-and-deploy-the-quickstarts) for complete instructions and additional options._
-1. Make sure you have started the JBoss Server as described above.
+1. Make sure you have started the JBoss EAP server as described above.
2. Open a command prompt and navigate to the root directory of this quickstart.
3. Type this command to build and deploy the archive:
@@ -138,7 +138,7 @@ When you access the application, you are presented with a browser login challeng
Undeploy the Archive
--------------------
-1. Make sure you have started the JBoss Server as described above.
+1. Make sure you have started the JBoss EAP server as described above.
2. Open a command prompt and navigate to the root directory of this quickstart.
3. When you are finished testing, type this command to undeploy the archive:
View
8 ejb-throws-exception/README.md
@@ -48,10 +48,10 @@ Configure Maven
If you have not yet done so, you must [Configure Maven](https://github.com/jboss-developer/jboss-developer-shared-resources/blob/master/guides/CONFIGURE_MAVEN.md#configure-maven-to-build-and-deploy-the-quickstarts) before testing the quickstarts.
-Start the JBoss Server
+Start the JBoss EAP Server
-------------------------
-1. Open a command prompt and navigate to the root of the JBoss server directory.
+1. Open a command prompt and navigate to the root of the JBoss EAP directory.
2. The following shows the command line to start the server:
For Linux: JBOSS_HOME/bin/standalone.sh
@@ -63,7 +63,7 @@ Build and Deploy the Quickstart
_NOTE: The following build command assumes you have configured your Maven user settings. If you have not, you must include Maven setting arguments on the command line. See [Build and Deploy the Quickstarts](../README.md#build-and-deploy-the-quickstarts) for complete instructions and additional options._
-1. Make sure you have started the JBoss Server as described above.
+1. Make sure you have started the JBoss EAP server as described above.
2. Open a command prompt and navigate to the root directory of this quickstart.
3. Type this command to build and deploy the archive:
@@ -88,7 +88,7 @@ If the `Name` input text box is empty, then the `Response` output text will disp
Undeploy the Archive
--------------------
-1. Make sure you have started the JBoss Server as described above.
+1. Make sure you have started the JBoss EAP server as described above.
2. Open a command prompt and navigate to the root directory of this quickstart.
3. When you are finished testing, type this command to undeploy the archive:
View
12 ejb-timer/README.md
@@ -3,7 +3,7 @@ ejb-timer: EJB Timers example - @Schedule and @Timeout
Author: Ondrej Zizka <ozizka@redhat.com>
Level: Beginner
Technologies: EJB 3.1 Timer
-Summary: Demonstrates how to use EJB 3.1 Timer (@Schedule and @Timeout) with the JBoss AS server.
+Summary: Demonstrates how to use EJB 3.1 Timer (@Schedule and @Timeout) with JBoss EAP.
Target Product: EAP
Product Versions: EAP 6.1, EAP 6.2
Source: <https://github.com/jboss-developer/jboss-eap-quickstarts/>
@@ -11,7 +11,7 @@ Source: <https://github.com/jboss-developer/jboss-eap-quickstarts/>
What is it?
-----------
-Demonstrates how to use EJB 3.1 Timer (@Schedule and @Timeout) with the JBoss AS server.
+Demonstrates how to use EJB 3.1 Timer (@Schedule and @Timeout) with JBoss EAP.
Features used:
@@ -34,10 +34,10 @@ Configure Maven
If you have not yet done so, you must [Configure Maven](https://github.com/jboss-developer/jboss-developer-shared-resources/blob/master/guides/CONFIGURE_MAVEN.md#configure-maven-to-build-and-deploy-the-quickstarts) before testing the quickstarts.
-Start the JBoss Server
+Start the JBoss EAP Server
-------------------------
-1. Open a command prompt and navigate to the root of the JBoss server directory.
+1. Open a command prompt and navigate to the root of the JBoss EAP directory.
2. The following shows the command line to start the server:
For Linux: JBOSS_HOME/bin/standalone.sh
@@ -49,7 +49,7 @@ Build and Deploy the Quickstart
_NOTE: The following build command assumes you have configured your Maven user settings. If you have not, you must include Maven setting arguments on the command line. See [Build and Deploy the Quickstarts](../README.md#buildanddeploy) for complete instructions and additional options._
-1. Make sure you have started the JBoss Application Server as described above.
+1. Make sure you have started the JBoss EAP server as described above.
2. Open a command prompt and navigate to the root directory of this quickstart.
3. Type this command to build and deploy the archive:
@@ -81,7 +81,7 @@ There are pre-created threads in thread pool, and they are rotated. Hence the ch
Undeploy the Archive
--------------------
-1. Make sure you have started the JBoss Server as described above.
+1. Make sure you have started the JBoss EAP server as described above.
2. Open a command prompt and navigate to the root directory of this quickstart.
3. When you are finished testing, type this command to undeploy the archive:
View
8 forge-from-scratch/README.md
@@ -74,10 +74,10 @@ Configure Maven
If you have not yet done so, you must [Configure Maven](https://github.com/jboss-developer/jboss-developer-shared-resources/blob/master/guides/CONFIGURE_MAVEN.md#configure-maven-to-build-and-deploy-the-quickstarts) before testing the quickstarts.
-Start the JBoss Server
+Start the JBoss EAP Server
-------------------------
-1. Open a command prompt and navigate to the root of the JBoss server directory.
+1. Open a command prompt and navigate to the root of the JBoss EAP directory.
2. The following shows the command line to start the server:
For Linux: JBOSS_HOME/bin/standalone.sh
@@ -87,7 +87,7 @@ Start the JBoss Server
Deploy and test the newly generated application
---------------------------
-Make sure you have started the JBoss server. See the instructions in the previous section.
+Make sure you have started the JBoss EAP server. See the instructions in the previous section.
1. Build the application:
@@ -113,7 +113,7 @@ Make sure you have started the JBoss server. See the instructions in the previou
Be sure to replace `YOUR_PROJECT_NAME` with the name of the project you chose when running the script.
-6. When you are ready to undeploy from JBoss AS, run this command:
+6. When you are ready to undeploy from JBoss EAP, run this command:
forge> as7 undeploy
View
8 greeter/README.md
@@ -42,10 +42,10 @@ Configure Maven
If you have not yet done so, you must [Configure Maven](https://github.com/jboss-developer/jboss-developer-shared-resources/blob/master/guides/CONFIGURE_MAVEN.md#configure-maven-to-build-and-deploy-the-quickstarts) before testing the quickstarts.
-Start the JBoss Server
+Start the JBoss EAP Server
-------------------------
-1. Open a command prompt and navigate to the root of the JBoss server directory.
+1. Open a command prompt and navigate to the root of the JBoss EAP directory.
2. The following shows the command line to start the server:
For Linux: JBOSS_HOME/bin/standalone.sh
@@ -57,7 +57,7 @@ Build and Deploy the Quickstart
_NOTE: The following build command assumes you have configured your Maven user settings. If you have not, you must include Maven setting arguments on the command line. See [Build and Deploy the Quickstarts](../README.md#build-and-deploy-the-quickstarts) for complete instructions and additional options._
-1. Make sure you have started the JBoss Server as described above.
+1. Make sure you have started the JBoss EAP server as described above.
2. Open a command prompt and navigate to the root directory of this quickstart.
3. Type this command to build and deploy the archive:
@@ -75,7 +75,7 @@ The application will be running at the following URL: <http://localhost:8080/jbo
Undeploy the Archive
--------------------
-1. Make sure you have started the JBoss Server as described above.
+1. Make sure you have started the JBoss EAP server as described above.
2. Open a command prompt and navigate to the root directory of this quickstart.
3. When you are finished testing, type this command to undeploy the archive:
View
4 h2-console/README.md
@@ -3,7 +3,7 @@ h2-console: Example Using the H2 Console with JBoss
Author: Pete Muir
Level: Beginner
Technologies: H2
-Summary: Shows how to use the H2 console with JBoss AS
+Summary: Shows how to use the H2 console with JBoss EAP
Target Product: EAP
Product Versions: EAP 6.1, EAP 6.2
Source: <https://github.com/jboss-developer/jboss-eap-quickstarts/>
@@ -11,7 +11,7 @@ Source: <https://github.com/jboss-developer/jboss-eap-quickstarts/>
What is it?
-----------
-JBoss AS bundles H2 as an in-memory, in-process database. H2 is written in Java so can run on any platform JBoss AS runs.
+JBoss EAP bundles H2 as an in-memory, in-process database. H2 is written in Java so can run on any platform JBoss EAP runs.
This is quickstart shows you how to use the H2 console with Red Hat JBoss Enterprise Application Platform. It uses the `greeter` quickstart as a GUI for entering data.
View
22 helloworld-jms/README.md
@@ -15,9 +15,9 @@ This quickstart demonstrates the use of external JMS clients with Red Hat JBoss
It contains the following:
-1. A message producer that sends messages to a JMS destination deployed to a JBoss server.
+1. A message producer that sends messages to a JMS destination deployed to a JBoss EAP server.
-2. A message consumer that receives message from a JMS destination deployed to a JBoss server.
+2. A message consumer that receives message from a JMS destination deployed to a JBoss EAP server.
System requirements
@@ -52,16 +52,16 @@ If you prefer, you can use the add-user utility interactively.
For an example of how to use the add-user utility, see instructions in the root README file located here: [Add an Application User](https://github.com/jboss-developer/jboss-developer-shared-resources/blob/master/guides/CREATE_USERS.md#add-an-application-user).
-Configure the JBoss Server
+Configure the JBoss EAP Server
---------------------------
You configure the the JMS `test` queue by running JBoss CLI commands. For your convenience, this quickstart batches the commands into a `configure-jms.cli` script provided in the root directory of this quickstart.
1. Before you begin, back up your server configuration file
- * If it is running, stop the JBoss server.
+ * If it is running, stop the JBoss EAP server.
* Backup the file: `JBOSS_HOME/standalone/configuration/standalone-full.xml`
* After you have completed testing this quickstart, you can replace this file to restore the server to its original configuration.
-2. Start the JBoss server by typing the following:
+2. 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
@@ -81,7 +81,7 @@ You should see the following result when you run the script:
Review the Modified Server Configuration
-----------------------------------
-If you want to review and understand newly added XML configuration, stop the JBoss server and open the `JBOSS_HOME/standalone/configuration/standalone-full.xml` file.
+If you want to review and understand newly added XML configuration, stop the JBoss EAP server and open the `JBOSS_HOME/standalone/configuration/standalone-full.xml` file.
The following `testQueue` jms-queue was configured in a new `<jms-destinations>` element under the hornetq-server section of the `messaging` subsystem.
@@ -93,10 +93,10 @@ The following `testQueue` jms-queue was configured in a new `<jms-destinations>`
</jms-destinations>
-Start the JBoss Server with the Full Profile
+Start the JBoss EAP Server with the Full Profile
---------------
-1. Open a command prompt and navigate to the root of the JBoss server directory.
+1. Open a command prompt and navigate to the root of the JBoss EAP directory.
2. The following shows the command line to start the server with the full profile:
For Linux: JBOSS_HOME/bin/standalone.sh -c standalone-full.xml
@@ -108,7 +108,7 @@ Build and Execute the Quickstart
To run the quickstart from the command line:
-1. Make sure you have started the JBoss server. See the instructions in the previous section.
+1. Make sure you have started the JBoss EAP server. See the instructions in the previous section.
2. Open a command prompt and navigate to the root of the helloworld-jms quickstart directory:
@@ -198,7 +198,7 @@ You can remove the JMS configuration by running the `remove-jms.cli` script pro
### Remove the JMS Configuration by Running the JBoss CLI Script
-1. Start the JBoss server by typing the following:
+1. 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
@@ -213,7 +213,7 @@ This script removes the `test` queue from the `messaging` subsystem in the serve
### Remove the JMS Configuration Manually
-1. If it is running, stop the JBoss server.
+1. If it is running, stop the JBoss EAP server.
2. Replace the `JBOSS_HOME/standalone/configuration/standalone-full.xml` file with the back-up copy of the file.
View
10 helloworld-mbean/README.md
@@ -37,10 +37,10 @@ Configure Maven
If you have not yet done so, you must [Configure Maven](https://github.com/jboss-developer/jboss-developer-shared-resources/blob/master/guides/CONFIGURE_MAVEN.md#configure-maven-to-build-and-deploy-the-quickstarts) before testing the quickstarts.
-Start the JBoss Server
+Start the JBoss EAP Server
-------------------------
-1. Open a command prompt and navigate to the root of the JBoss server directory.
+1. Open a command prompt and navigate to the root of the JBoss EAP directory.
2. The following shows the command line to start the server:
For Linux: JBOSS_HOME/bin/standalone.sh
@@ -52,7 +52,7 @@ Build and Deploy the Quickstart
_NOTE: The following build command assumes you have configured your Maven user settings. If you have not, you must include Maven setting arguments on the command line. See [Build and Deploy the Quickstarts](../README.md#buildanddeploy) for complete instructions and additional options._
-1. Make sure you have started the JBoss Server as described above.
+1. Make sure you have started the JBoss EAP server as described above.
2. Open a command propmt and navigate to the root directory of this quickstart.
3. Type this command to build and deploy the archive:
@@ -70,7 +70,7 @@ The following sections describe how to use 'JConsole' to inspect and test the MB
Start JConsole
--------------
-To connect to the JBoss server using jconsole, open a command prompt and type the following command :
+To connect to the JBoss EAP server using jconsole, open a command prompt and type the following command :
For Linux: JDK_HOME/bin/jconsole
For Windows: JDK_HOME\bin\jconsole.exe
@@ -97,7 +97,7 @@ You can use JConsole to inspect and use the MBeans :
Undeploy the Archive
--------------------
-1. Make sure you have started the JBoss Server as described above.
+1. Make sure you have started the JBoss EAP server as described above.
2. Open a command prompt and navigate to the root directory of this quickstart.
3. When you are finished testing, type this command to undeploy the archive:
View
12 helloworld-mdb/README.md
@@ -33,10 +33,10 @@ Configure Maven
If you have not yet done so, you must [Configure Maven](https://github.com/jboss-developer/jboss-developer-shared-resources/blob/master/guides/CONFIGURE_MAVEN.md#configure-maven-to-build-and-deploy-the-quickstarts) before testing the quickstarts.
-Start the JBoss Server with the Full Profile
+Start the JBoss EAP Server with the Full Profile
---------------
-1. Open a command prompt and navigate to the root of the JBoss server directory.
+1. Open a command prompt and navigate to the root of the JBoss EAP directory.
2. The following shows the command line to start the server with the full profile:
For Linux: JBOSS_HOME/bin/standalone.sh -c standalone-full.xml
@@ -48,13 +48,13 @@ Build and Deploy the Quickstart
_NOTE: The following build command assumes you have configured your Maven user settings. If you have not, you must include Maven setting arguments on the command line. See [Build and Deploy the Quickstarts](../README.md#build-and-deploy-the-quickstarts) for complete instructions and additional options._
-1. Make sure you have started the JBoss Server as described above.
+1. Make sure you have started the JBoss EAP server as described above.
2. Open a command prompt and navigate to the root directory of this quickstart.
3. Type this command to build and deploy the archive:
mvn clean install jboss-as:deploy
-4. This will deploy `target/jboss-helloworld-mdb.war` to the running instance of the server. Look at the JBoss Application Server console or Server log and you should see log messages corresponding to the deployment of the message-driven beans and the JMS destinations:
+4. This will deploy `target/jboss-helloworld-mdb.war` to the running instance of the server. Look at the JBoss EAP console or Server log and you should see log messages corresponding to the deployment of the message-driven beans and the JMS destinations:
14:11:01,020 INFO org.hornetq.core.server.impl.HornetQServerImpl trying to deploy queue jms.queue.HELLOWORLDMDBQueue
14:11:01,029 INFO org.jboss.as.messaging JBAS011601: Bound messaging object to jndi name java:/queue/HELLOWORLDMDBQueue
@@ -73,7 +73,7 @@ To send messages to the topic, use the following URL: <http://localhost:8080/jbo
Investigate the Server Console Output
-------------------------
-Look at the JBoss Application Server console or Server log and you should see log messages like the following:
+Look at the JBoss EAP console or Server log and you should see log messages like the following:
17:51:52,122 INFO [class org.jboss.as.quickstarts.mdb.HelloWorldQueueMDB] (Thread-1 (HornetQ-client-global-threads-26912020)) Received Message from queue: This is message 1
17:51:52,123 INFO [class org.jboss.as.quickstarts.mdb.HelloWorldQueueMDB] (Thread-11 (HornetQ-client-global-threads-26912020)) Received Message from queue: This is message 2
@@ -85,7 +85,7 @@ Look at the JBoss Application Server console or Server log and you should see lo
Undeploy the Archive
--------------------
-1. Make sure you have started the JBoss Server as described above.
+1. Make sure you have started the JBoss EAP server as described above.
2. Open a command prompt and navigate to the root directory of this quickstart.
3. When you are finished testing, type this command to undeploy the archive:
View
6 helloworld-mdb/src/main/java/org/jboss/as/quickstarts/servlet/HelloWorldMDBServletClient.java
@@ -69,7 +69,7 @@ protected void doGet(HttpServletRequest req, HttpServletResponse resp) throws Se
resp.setContentType("text/html");
PrintWriter out = resp.getWriter();
Connection connection = null;
- out.write("<h1>Quickstart: This example demonstrates the use of <strong>JMS 1.1</strong> and <strong>EJB 3.1 Message-Driven Bean</strong> in JBoss Enterprise Application 6.</h1>");
+ out.write("<h1>Quickstart: This example demonstrates the use of <strong>JMS 1.1</strong> and <strong>EJB 3.1 Message-Driven Bean</strong> in JBoss Enterprise Application Platform 6.</h1>");
try {
Destination destination;
if (req.getParameterMap().keySet().contains("topic")) {
@@ -89,13 +89,13 @@ protected void doGet(HttpServletRequest req, HttpServletResponse resp) throws Se
messageProducer.send(message);
out.write("Message (" + i + "): " + message.getText() + "</br>");
}
- out.write("<p><i>Go to your JBoss Application Server console or Server log to see the result of messages processing</i></p>");
+ out.write("<p><i>Go to your JBoss EAP server console or log to see the result of messages processing</i></p>");
} catch (JMSException e) {
e.printStackTrace();
out.write("<h2>A problem occurred during the delivery of this message</h2>");
out.write("</br>");
- out.write("<p><i>Go your the JBoss Application Server console or Server log to see the error stack trace</i></p>");
+ out.write("<p><i>Go your the JBoss EAP server console or log to see the error stack trace</i></p>");
} finally {
if (connection != null) {
try {
View
10 helloworld-osgi/README.md
@@ -30,10 +30,10 @@ Configure Maven
If you have not yet done so, you must [Configure Maven](https://github.com/jboss-developer/jboss-developer-shared-resources/blob/master/guides/CONFIGURE_MAVEN.md#configure-maven-to-build-and-deploy-the-quickstarts) before testing the quickstarts.
-Start the JBoss Server with the OSGi Profile
+Start the JBoss EAP Server with the OSGi Profile
-------------------------
-1. Open a command prompt and navigate to the root of the JBoss server directory.
+1. Open a command prompt and navigate to the root of the JBoss EAP directory.
2. The following shows the command line to start the server with the OSGi profile:
For Linux: JBOSS_HOME/bin/standalone.sh -c standalone-osgi.xml
@@ -45,7 +45,7 @@ Build and Deploy the Quickstart
_NOTE: The following build command assumes you have configured your Maven user settings. If you have not, you must include Maven setting arguments on the command line. See [Build and Deploy the Quickstarts](../README.md#build-and-deploy-the-quickstarts) for complete instructions and additional options._
-1. Make sure you have started the JBoss Server as described above.
+1. Make sure you have started the JBoss EAP server as described above.
2. Open a command prompt and navigate to the root directory of this quickstart.
3. Type this command to build and deploy the archive:
@@ -57,7 +57,7 @@ _NOTE: The following build command assumes you have configured your Maven user s
Investigate the Server Console Output
-------------------------
-Look in the JBoss Application Server console or Server log and you should see the following message:
+Look in the JBoss EAP server console or log and you should see the following message:
`Hello World!!`
@@ -65,7 +65,7 @@ Look in the JBoss Application Server console or Server log and you should see th
Undeploy the Archive
--------------------
-1. Make sure you have started the JBoss Server as described above.
+1. Make sure you have started the JBoss EAP server as described above.
2. Open a command prompt and navigate to the root directory of this quickstart.
3. When you are finished testing, type this command to undeploy the archive:
View
8 helloworld-rs/README.md
@@ -28,10 +28,10 @@ Configure Maven
If you have not yet done so, you must [Configure Maven](https://github.com/jboss-developer/jboss-developer-shared-resources/blob/master/guides/CONFIGURE_MAVEN.md#configure-maven-to-build-and-deploy-the-quickstarts) before testing the quickstarts.
-Start the JBoss Server
+Start the JBoss EAP Server
-------------------------
-1. Open a command prompt and navigate to the root of the JBoss server directory.
+1. Open a command prompt and navigate to the root of the JBoss EAP directory.
2. The following shows the command line to start the server:
For Linux: JBOSS_HOME/bin/standalone.sh
@@ -43,7 +43,7 @@ Build and Deploy the Quickstart
_NOTE: The following build command assumes you have configured your Maven user settings. If you have not, you must include Maven setting arguments on the command line. See [Build and Deploy the Quickstarts](../README.md#build-and-deploy-the-quickstarts) for complete instructions and additional options._
-1. Make sure you have started the JBoss Server as described above.
+1. Make sure you have started the JBoss EAP server as described above.
2. Open a command prompt and navigate to the root directory of this quickstart.
3. Type this command to build and deploy the archive:
@@ -65,7 +65,7 @@ The *JSON* content can be viewed by accessing this URL: <http://localhost:8080/j
Undeploy the Archive
--------------------
-1. Make sure you have started the JBoss Server as described above.
+1. Make sure you have started the JBoss EAP server as described above.
2. Open a command prompt and navigate to the root directory of this quickstart.
3. When you are finished testing, type this command to undeploy the archive:
View
8 helloworld-singleton/README.md
@@ -27,10 +27,10 @@ Configure Maven
If you have not yet done so, you must [Configure Maven](https://github.com/jboss-developer/jboss-developer-shared-resources/blob/master/guides/CONFIGURE_MAVEN.md#configure-maven-to-build-and-deploy-the-quickstarts) before testing the quickstarts.
-Start the JBoss Server
+Start the JBoss EAP Server
-------------------------
-1. Open a command prompt and navigate to the root of the JBoss server directory.
+1. Open a command prompt and navigate to the root of the JBoss EAP directory.
2. The following shows the command line to start the server:
For Linux: JBOSS_HOME/bin/standalone.sh
@@ -42,7 +42,7 @@ Build and Deploy the Quickstart
_NOTE: The following build command assumes you have configured your Maven user settings. If you have not, you must include Maven setting arguments on the command line. See [Build and Deploy the Quickstarts](../README.md#build-and-deploy-the-quickstarts) for complete instructions and additional options._
-1. Make sure you have started the JBoss Server as described above.
+1. Make sure you have started the JBoss EAP server as described above.
2. Open a command prompt and navigate to the root directory of this quickstart.
3. Type this command to build and deploy the archive:
@@ -66,7 +66,7 @@ To test the singleton bean, click on either "Increment A" or "Increment B". The
Undeploy the Archive
--------------------
-1. Make sure you have started the JBoss Server as described above.
+1. Make sure you have started the JBoss EAP server as described above.
2. Open a command prompt and navigate to the root directory of this quickstart.
3. When you are finished testing, type this command to undeploy the archive:
View
10 helloworld-ws/README.md
@@ -27,10 +27,10 @@ Configure Maven
If you have not yet done so, you must [Configure Maven](https://github.com/jboss-developer/jboss-developer-shared-resources/blob/master/guides/CONFIGURE_MAVEN.md#configure-maven-to-build-and-deploy-the-quickstarts) before testing the quickstarts.
-Start the JBoss Server
+Start the JBoss EAP Server
----------------------
-1. Open a command prompt and navigate to the root of the JBoss server directory.
+1. Open a command prompt and navigate to the root of the JBoss EAP directory.
2. The following shows the command line to start the server:
For Linux: JBOSS_HOME/bin/standalone.sh
@@ -42,7 +42,7 @@ Build and Deploy the Quickstart
_NOTE: The following build command assumes you have configured your Maven user settings. If you have not, you must include Maven setting arguments on the command line. See [Build and Deploy the Quickstarts](../README.md#build-and-deploy-the-quickstarts) for complete instructions and additional options._
-1. Make sure you have started the JBoss Server as described above.
+1. Make sure you have started the JBoss EAP server as described above.
2. Open a command prompt and navigate to the root directory of this quickstart.
3. Type this command to build and deploy the archive:
@@ -59,7 +59,7 @@ You can check that the Web Service is running and deployed correctly by accessin
Undeploy the Archive
--------------------
-1. Make sure you have started the JBoss Server as described above.
+1. Make sure you have started the JBoss EAP server as described above.
2. Open a command prompt and navigate to the root directory of this quickstart.
3. When you are finished testing, type this command to undeploy the archive:
@@ -73,7 +73,7 @@ This quickstart provides Arquillian tests. By default, these tests are configure
_NOTE: The following commands assume you have configured your Maven user settings. If you have not, you must include Maven setting arguments on the command line. See [Run the Arquillian Tests](https://github.com/jboss-developer/jboss-developer-shared-resources/blob/master/guides/RUN_ARQUILLIAN_TESTS.md#run-the-arquillian-tests) for complete instructions and additional options._
-1. Make sure you have started the JBoss Server as described above.
+1. Make sure you have started the JBoss EAP server as described above.
2. Open a command prompt and navigate to the root directory of this quickstart.
3. Type the following command to run the test goal with the following profile activated:
View
8 helloworld/README.md
@@ -28,10 +28,10 @@ Configure Maven
If you have not yet done so, you must [Configure Maven](https://github.com/jboss-developer/jboss-developer-shared-resources/blob/master/guides/CONFIGURE_MAVEN.md#configure-maven-to-build-and-deploy-the-quickstarts) before testing the quickstarts.
-Start the JBoss Server
+Start the JBoss EAP Server
-------------------------
-1. Open a command prompt and navigate to the root of the JBoss server directory.
+1. Open a command prompt and navigate to the root of the JBoss EAP directory.
2. The following shows the command line to start the server:
For Linux: JBOSS_HOME/bin/standalone.sh
@@ -43,7 +43,7 @@ Build and Deploy the Quickstart
_NOTE: The following build command assumes you have configured your Maven user settings. If you have not, you must include Maven setting arguments on the command line. See [Build and Deploy the Quickstarts](../README.md#build-and-deploy-the-quickstarts) for complete instructions and additional options._
-1. Make sure you have started the JBoss Server as described above.
+1. Make sure you have started the JBoss EAP server as described above.
2. Open a command prompt and navigate to the root directory of this quickstart.
3. Type this command to build and deploy the archive:
@@ -61,7 +61,7 @@ The application will be running at the following URL: <http://localhost:8080/jbo
Undeploy the Archive
--------------------
-1. Make sure you have started the JBoss Server as described above.
+1. Make sure you have started the JBoss EAP server as described above.
2. Open a command prompt and navigate to the root directory of this quickstart.
3. When you are finished testing, type this command to undeploy the archive:
View
8 hibernate3/README.md
@@ -40,10 +40,10 @@ Configure Maven
If you have not yet done so, you must [Configure Maven](https://github.com/jboss-developer/jboss-developer-shared-resources/blob/master/guides/CONFIGURE_MAVEN.md#configure-maven-to-build-and-deploy-the-quickstarts) before testing the quickstarts.
-Start the JBoss Server
+Start the JBoss EAP Server
-------------------------
-1. Open a command prompt and navigate to the root of the JBoss server directory.
+1. Open a command prompt and navigate to the root of the JBoss EAP directory.
2. The following shows the command line to start the server:
For Linux: JBOSS_HOME/bin/standalone.sh
@@ -55,7 +55,7 @@ Build and Deploy the Quickstart
_NOTE: The following build command assumes you have configured your Maven user settings. If you have not, you must include Maven setting arguments on the command line. See [Build and Deploy the Quickstarts](../README.md#build-and-deploy-the-quickstarts) for complete instructions and additional options._
-1. Make sure you have started the JBoss Server as described above.
+1. Make sure you have started the JBoss EAP server as described above.
2. Open a command prompt and navigate to the root directory of this quickstart.
3. Type this command to build and deploy the archive:
@@ -73,7 +73,7 @@ The application will be running at the following URL: <http://localhost:8080/jbo
Undeploy the Archive
--------------------
-1. Make sure you have started the JBoss Server as described above.
+1. Make sure you have started the JBoss EAP server as described above.
2. Open a command prompt and navigate to the root directory of this quickstart.
3. When you are finished testing, type this command to undeploy the archive:
View
8 hibernate4/README.md
@@ -61,10 +61,10 @@ For example:
Please note that if you are working with Hibernate 3, the process is different. You will need to bundle the jars since JBoss EAP 6 does not ship with Hibernate 3. Refer to the `hibernate3` quickstart for details on how to bundle the JARs.
-Start the JBoss Server
+Start the JBoss EAP Server
-------------------------
-1. Open a command prompt and navigate to the root of the JBoss server directory.
+1. Open a command prompt and navigate to the root of the JBoss EAP directory.
2. The following shows the command line to start the server:
For Linux: JBOSS_HOME/bin/standalone.sh
@@ -76,7 +76,7 @@ Build and Deploy the Quickstart
_NOTE: The following build command assumes you have configured your Maven user settings. If you have not, you must include Maven setting arguments on the command line. See [Build and Deploy the Quickstarts](../README.md#build-and-deploy-the-quickstarts) for complete instructions and additional options._
-1. Make sure you have started the JBoss Server as described above.
+1. Make sure you have started the JBoss EAP server as described above.
2. Open a command prompt and navigate to the root directory of this quickstart.
3. Type this command to build and deploy the archive:
@@ -102,7 +102,7 @@ _Note:_ You will see the following warning in the server log. You can ignore thi
Undeploy the Archive
--------------------
-1. Make sure you have started the JBoss Server as described above.
+1. Make sure you have started the JBoss EAP server as described above.
2. Open a command prompt and navigate to the root directory of this quickstart.
3. When you are finished testing, type this command to undeploy the archive:
View
20 hornetq-clustering/README.md
@@ -47,7 +47,7 @@ You can choose to deploy and run this quickstart in a managed domain or on a sta
_NOTE - Before you begin:_
-1. If it is running, stop the JBoss server.
+1. If it is running, stop the JBoss EAP server.
2. If you plan to test using a standalone server, backup the file:
@@ -67,7 +67,7 @@ After you have completed testing this quickstart, you can replace these files to
You configure the server by running the install-domain.cli script provided in the root directory of this quickstart.
#### Start the server in domain mode.
-1. Open a command prompt and navigate to the root of the JBoss server directory.
+1. Open a command prompt and navigate to the root of the JBoss EAP directory.
2. The following shows the command line to start the server in domain mode:
For Linux: JBOSS_HOME/bin/domain.sh
@@ -104,7 +104,7 @@ Since both application servers must be configured in the same way, you must conf
#### Start the Server in Standalone Mode using the Full HA Profile.
-1. Open a command prompt and navigate to the root of the JBoss server directory.
+1. Open a command prompt and navigate to the root of the JBoss EAP directory.
2. The following shows the command line to start the server with the full-ha profile. This profile supports clustering/HA
For Linux: JBOSS_HOME/bin/standalone.sh -c standalone-full-ha.xml
@@ -128,12 +128,12 @@ Since both application servers must be configured in the same way, you must conf
You should see "outcome" => "success" for all of the commands.
-#### Clone the JBOSS_HOME Directory
+#### Clone the JBoss EAP Directory
-After you have successfully configured the server, you must make a copy of this JBoss directory structure to use for the second server.
+After you have successfully configured the server, you must make a copy of this JBoss EAP directory structure to use for the second server.
1. Stop the server.
-2. Make a copy of this JBoss directory structure to use for the second server.
+2. Make a copy of this JBoss EAP directory structure to use for the second server.
3. Remove the following directories from the cloned instance:
JBOSS_HOME_SERVER_2/standalone/data/messagingbindings
@@ -176,7 +176,7 @@ To send messages to the topic, use the following URL: <http://localhost:8080/jbo
Investigate the Server Console Output
-------------------------
-Look at the JBoss Application Server console or Server log and you should see log messages like the following:
+Look at the JBoss EAP server console or log and you should see log messages like the following:
[Server:jdf-hornetqcluster-node1] 16:34:41,165 INFO [class org.jboss.as.quickstarts.mdb.HelloWorldQueueMDB] (Thread-8 (HornetQ-client-global-threads-1067469862)) Received Message from queue: This is message 1
[Server:jdf-hornetqcluster-node1] 16:34:41,274 INFO [class org.jboss.as.quickstarts.mdb.HelloWorldQueueMDB] (Thread-8 (HornetQ-client-global-threads-1067469862)) Received Message from queue: This is message 3
@@ -193,7 +193,7 @@ When you are finished testing, use the following instructions to undeploy the qu
### Undeploy the quickstart in Domain Mode
-1. Make sure you have started the JBoss Server in domain mode as described above.
+1. Make sure you have started the JBoss EAP server in domain mode as described above.
3. Open a command prompt, navigate to the root directory of this quickstart, and run the following command to undeploy the helloworld-mdb quickstart:
JBOSS_HOME/bin/jboss-cli.sh --connect --file=undeploy-domain.cli
@@ -201,7 +201,7 @@ When you are finished testing, use the following instructions to undeploy the qu
### Undeploy the quickstart in Standalone Mode
-1. Make sure you have started the JBoss Server in standalone mode as described above.
+1. Make sure you have started the JBoss EAP server in standalone mode as described above.
3. Open a command prompt, navigate to the root directory of this quickstart, and run the following command to undeploy the helloworld-mdb quickstart:
JBOSS_HOME/bin/jboss-cli.sh --connect --file=undeploy-standalone.cli
@@ -268,7 +268,7 @@ This script removes the server configuration that was done by the `install-stand
The batch executed successfully.
-### Delete the Cloned Standalone Server Directory
+### Delete the Cloned Standalone JBoss EAP Directory
1. If it is running, stop the second instance of the JBoss EAP server.
2. Delete the cloned directory.
View
8 inter-app/README.md
@@ -35,10 +35,10 @@ Configure Maven
If you have not yet done so, you must [Configure Maven](https://github.com/jboss-developer/jboss-developer-shared-resources/blob/master/guides/CONFIGURE_MAVEN.md#configure-maven-to-build-and-deploy-the-quickstarts) before testing the quickstarts.
-Start the JBoss Server
+Start the JBoss EAP Server
-------------------------
-1. Open a command prompt and navigate to the root of the JBoss server directory.
+1. Open a command prompt and navigate to the root of the JBoss EAP directory.
2. The following shows the command line to start the server:
For Linux: JBOSS_HOME/bin/standalone.sh
@@ -50,7 +50,7 @@ Build and Deploy the Quickstart
_NOTE: The following build command assumes you have configured your Maven user settings. If you have not, you must include Maven setting arguments on the command line. See [Build and Deploy the Quickstarts](../README.md#build-and-deploy-the-quickstarts) for complete instructions and additional options._
-1. Make sure you have started the JBoss Server as described above.
+1. Make sure you have started the JBoss EAP server as described above.
2. Open a command prompt and navigate to the root directory of this quickstart.
3. Type this command to build and deploy the archive:
@@ -72,7 +72,7 @@ You are presented with a form that allows you to set the value on the bean in th
Undeploy the Archive
--------------------
-1. Make sure you have started the JBoss Server as described above.
+1. Make sure you have started the JBoss EAP server as described above.
2. Open a command prompt and navigate to the root directory of this quickstart.
3. When you are finished testing, type this command to undeploy the archive:
View
2  jax-rs-client/README.md
@@ -51,7 +51,7 @@ This quickstart provides Arquillian tests.
_NOTE: The following commands assume you have configured your Maven user settings. If you have not, you must include Maven setting arguments on the command line. See [Run the Arquillian Tests](https://github.com/jboss-developer/jboss-developer-shared-resources/blob/master/guides/RUN_ARQUILLIAN_TESTS.md#run-the-arquillian-tests) for complete instructions and additional options._
-1. Make sure you have started the JBoss Server as described above.
+1. Make sure you have started the JBoss EAP server as described above.
2. Make sure the `helloworld-rs` quickstart has been deployed on the server as noted in the **Prerequisites** section above.
3. Open a command prompt and navigate to the root directory of this quickstart.
4. Type the following command to run the test goal with the following profile activated:
View
18 jta-crash-rec/README.md
@@ -22,7 +22,7 @@ This quickstart shows how to atomically update multiple resources within one tra
The relational database table in this example contains two columns that represent a "key" / "value" pair. The application presents an HTML form containing two input text boxes and allows you to create, update, delete or list these pairs. When you add or update a "key" / "value" pair, the quickstart starts a transaction, updates the database table, produces a JMS message containing the update, and then commits the transaction. If all goes well, eventually the consumer gets the message and generates a database update, setting the "value" corresponding to the "key" to something that indicates it was changed by the message consumer.
-In this example, you halt the JBoss server in the middle of an XA transaction after the database modification has been committed, but before the JMS producer is committed. You can verify that the transaction was started, then restart the JBoss EAP server to complete the transaction. You then verify that everything is in a consistent state.
+In this example, you halt the JBoss EAP server in the middle of an XA transaction after the database modification has been committed, but before the JMS producer is committed. You can verify that the transaction was started, then restart the JBoss EAP server to complete the transaction. You then verify that everything is in a consistent state.
JBoss EAP ships with H2, an in-memory database written in Java. In this example, we use H2 for the database. Although H2 XA support is not recommended for production systems, the example does illustrate the general steps you need to perform for any datasource vendor. This example provides its own H2 XA datasource configuration. It is defined in the `jta-crash-rec-ds.xml` file in the WEB-INF folder of the WAR archive.
@@ -51,10 +51,10 @@ This quickstart uses _Byteman_ to help demonstrate crash recovery. You can find
Follow the instructions here to download and configure _Byteman_: [Download and Configure Byteman](https://github.com/jboss-developer/jboss-developer-shared-resources/blob/master/guides/CONFIGURE_BYTEMAN.md#download-and-configure-byteman)
-Configure the JBoss server
+Configure the JBoss EAP Server
---------------------------
-_NOTE_: The _Byteman_ scripts only work in JTA mode. They do not work in JTS mode. If you have configured the server for a quickstart that uses JTS, you must follow the quickstart instructions to remove the JTS configuration from the JBoss server before making the following changes. Otherwise _Byteman_ will not halt the server.
+_NOTE_: The _Byteman_ scripts only work in JTA mode. They do not work in JTS mode. If you have configured the server for a quickstart that uses JTS, you must follow the quickstart instructions to remove the JTS configuration from the JBoss EAP server before making the following changes. Otherwise _Byteman_ will not halt the server.
Start the JBoss EAP Server
@@ -74,7 +74,7 @@ Build and Deploy the Quickstart
_NOTE: The following build command assumes you have configured your Maven user settings. If you have not, you must include Maven setting arguments on the command line. See [Build and Deploy the Quickstarts](../README.md#build-and-deploy-the-quickstarts) for complete instructions and additional options._
-1. Make sure you have started the JBoss Server as described above.
+1. Make sure you have started the JBoss EAP server as described above.
2. Open a command prompt and navigate to the root directory of this quickstart.
3. Type this command to build and deploy the archive:
@@ -102,7 +102,7 @@ Test the application
* The added complexity is to cope with failures, especially failures that occur during phase 2. Some failure modes require cooperation between the application server and the resources in order to guarantee that any pending changes are recovered.
4. To demonstrate XA recovery, you must enable the Byteman tool to terminate the application server while _phase 2_ is running as follows:
- * Stop the JBoss server.
+ * Stop the JBoss EAP server.
* Follow the instructions here to clear the transaction objectstore remaining from any previous tests: [Clear the Transaction ObjectStore](https://github.com/jboss-developer/jboss-developer-shared-resources/blob/master/guides/CONFIGURE_BYTEMAN.md#clear-the-transaction-objectstore)
* The following line of text must be appended to the server configuration file using the instructions located here: [Use Byteman to Halt the Application](https://github.com/jboss-developer/jboss-developer-shared-resources/blob/master/guides/CONFIGURE_BYTEMAN.md#use-byteman-to-halt-the-application)
@@ -148,14 +148,14 @@ Test the application
* [Disable the Byteman script](https://github.com/jboss-developer/jboss-developer-shared-resources/blob/master/guides/CONFIGURE_BYTEMAN.md#disable-the-byteman-script) by restoring the backup server configuration file.
* [Start the JBoss EAP server](#start-the-jboss-eap-server) as instructed above.
* Load the web interface to the application
- * By the time the JBoss server is ready, the transaction should have recovered.
- * A message is printed on the JBoss server console when the consumer has completed the update. Look for a line that reads 'JTA Crash Record Quickstart: key value pair updated via JMS'.
+ * By the time the JBoss EAP server is ready, the transaction should have recovered.
+ * A message is printed on the JBoss EAP server console when the consumer has completed the update. Look for a line that reads 'JTA Crash Record Quickstart: key value pair updated via JMS'.
* Check that the row you inserted in step 4 now contains the text *"updated via JMS"*, showing that the JMS message was recovered successfully. Use the application URL to perform this check.
* You will most likely see the following message on the console.
ARJUNA016038: No XAResource to recover ... eis_name=...JTACrashRecQuickstartDS during recovery
- This is normal. What actually happened is that the first resource (JTACrashRecQuickstartDS) committed before the JBoss server was halted in step 5. The transaction logs are only updated/deleted after the outcome of the transaction is determined. If the transaction manager did update the log as each participant (database and JMS queue) completed then throughput would suffer. Notice you do not get a similar message for the JMS resource since that is the resource that recovered and the log record was updated to reflect this change. You need to manually remove the record for the first participant if you know which one is which or, if you are using the community version of the JBoss server, then you can also inspect the transaction logs using a JMX browser. For the demo it is simplest to delete the records from the file system, however, *be wary of doing this on a production system*.
+ This is normal. What actually happened is that the first resource (JTACrashRecQuickstartDS) committed before the JBoss EAP server was halted in step 5. The transaction logs are only updated/deleted after the outcome of the transaction is determined. If the transaction manager did update the log as each participant (database and JMS queue) completed then throughput would suffer. Notice you do not get a similar message for the JMS resource since that is the resource that recovered and the log record was updated to reflect this change. You need to manually remove the record for the first participant if you know which one is which or, if you are using the community version of the JBoss EAP server, then you can also inspect the transaction logs using a JMX browser. For the demo it is simplest to delete the records from the file system, however, *be wary of doing this on a production system*.
7. Do NOT forget to [Disable the Byteman script](https://github.com/jboss-developer/jboss-developer-shared-resources/blob/master/guides/CONFIGURE_BYTEMAN.md#disable-the-byteman-script) by restoring the backup server configuration file. The Byteman rule must be removed to ensure that your application server will be able to commit 2PC transactions!
@@ -170,7 +170,7 @@ _Note:_ You will see the following warning in the server log. You can ignore thi
Undeploy the Archive
--------------------
-1. Make sure you have started the JBoss Server as described above.
+1. Make sure you have started the JBoss EAP server as described above.
2. Open a command prompt and navigate to the root directory of this quickstart.
3. When you are finished testing, type this command to undeploy the archive:
View
18 jts-distributed-crash-rec/README.md
@@ -22,12 +22,12 @@ Apart from that, this quickstart works the same as the `jts` quickstart and if t
As an overview, the sequence of events to expect:
-1. Configure and start two JBoss servers.
+1. Configure and start two JBoss EAP servers.
2. Build and deploy the two application components.
3. Open a web browser and attempt to invoice two customers as with the `jts` quickstart.
-4. JBoss server 1 will run through a two-phase commit (2PC), preparing the resources in JBoss server 1 and JBoss server 2. JBoss server 1 will then crash before it can call commit.
+4. JBoss EAP server 1 will run through a two-phase commit (2PC), preparing the resources in JBoss EAP server 1 and JBoss EAP server 2. JBoss EAP server 1 will then crash before it can call commit.
5. The user is invited to inspect the content of the transaction objectstore.
-6. JBoss server 1 should be restarted. It will then recover the "invoices" delivered to the MDBs, just as it does in the _jts_ quickstart
+6. JBoss EAP server 1 should be restarted. It will then recover the "invoices" delivered to the MDBs, just as it does in the _jts_ quickstart
System requirements
@@ -70,8 +70,8 @@ Test the Application
1. If you have not yet done so, configure the two application servers and deploy the `jts` quickstart. Follow the instructions in the [jts README](../jts/README.md) file.
-2. Configure _Byteman_ to halt JBoss server 1
- * Stop both JBoss servers.
+2. Configure _Byteman_ to halt JBoss EAP server 1
+ * Stop both JBoss EAP servers.
* Follow the instructions here to clear the transaction objectstore remaining from any previous tests: [Clear the Transaction ObjectStore](https://github.com/jboss-developer/jboss-developer-shared-resources/blob/master/guides/CONFIGURE_BYTEMAN.md#clear-the-transaction-objectstore)
* The following 2 lines of text must be appended to the server configuration file for server 1 only using the instructions located here: [Use Byteman to Halt the Application](https://github.com/jboss-developer/jboss-developer-shared-resources/blob/master/guides/CONFIGURE_BYTEMAN.md#use-byteman-to-halt-the-application)
@@ -85,7 +85,7 @@ Test the Application
JAVA_OPTS=%JAVA_OPTS% -javaagent:C:BYTEMAN_HOME\lib\byteman.jar=script:C:\QUICKSTART_HOME\jts-distributed-crash-rec\byteman-scripts\failAfterPrepare.btm %JAVA_OPTS%
JAVA_OPTS=%JAVA_OPTS% -Dorg.jboss.byteman.transform.all -Djboss.modules.system.pkgs=org.jboss.byteman -Dorg.jboss.byteman.verbose=true
-3. Start both of the JBoss servers
+3. Start both of the JBoss EAP servers
If you are using Linux:
@@ -109,7 +109,7 @@ Test the Application
15:46:55,667 INFO [stdout] (http-localhost-127.0.0.1-8080-1) Installed rule using default helper : Fail 2PC after prepare
15:46:55,668 INFO [stdout] (http-localhost-127.0.0.1-8080-1) Fail 2PC after prepare execute
15:46:55,669 INFO [stdout] (http-localhost-127.0.0.1-8080-1) rule.debug{Fail 2PC after prepare} : !!!killing JVM!!!
- * NOTE: Until you restart JBoss server 1, you will see several error messages in JBoss server 2. These are to be expected:
+ * NOTE: Until you restart JBoss EAP server 1, you will see several error messages in JBoss EAP server 2. These are to be expected:
15:46:55,044 INFO [org.jboss.ejb.client] (RequestProcessor-10) JBoss EJB Client version 1.0.0.Beta12
15:49:06,579 WARN [com.arjuna.ats.jts] (Periodic Recovery) ARJUNA022167: Got TRANSIENT from ORB for tx 0:ffffc0a8013c:-2eb1158b:4f280ce3:1a, unable determine status, will retry later
@@ -171,7 +171,7 @@ Test the Application
12:09:38,697 INFO [org.jboss.ejb.client] (RequestProcessor-10) JBoss EJB Client version 1.0.0.Beta11
12:09:39,204 INFO [class org.jboss.as.quickstarts.cmt.jts.mdb.HelloWorldMDB] (Thread-3 (group:HornetQ-client-global-threads-649946595)) Received Message: Created invoice for customer named: Tom
- * NOTE: You will also get several stack traces in JBoss server 1 console during recovery, these are to be expected as not all resources are available at all stages of recovery.
+ * NOTE: You will also get several stack traces in JBoss EAP server 1 console during recovery, these are to be expected as not all resources are available at all stages of recovery.
15:55:41,706 WARN [com.arjuna.ats.jts] (Thread-84) ARJUNA022223: ExtendedResourceRecord.topLevelCommit caught exception: org.omg.CORBA.OBJECT_NOT_EXIST: Server-side Exception: unknown oid
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) [:1.6.0_22]
@@ -216,7 +216,7 @@ Test the Application
at com.arjuna.ats.internal.jts.recovery.transactions.TopLevelTransactionRecoveryModule.periodicWorkSecondPass(TopLevelTransactionRecoveryModule.java:81) [jbossjts-4.16.1.Final.jar:]
at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.doWorkInternal(PeriodicRecovery.java:789) [jbossjts-4.16.1.Final.jar:]
at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.run(PeriodicRecovery.java:371) [jbossjts-4.16.1.Final.jar:]
- * The easiest way to check when JBoss server 1 is recovered is to look in the object store and check that all the records are now cleaned up. The records that should be cleared are the ones in the defaultStore/CosTransactions/XAResourceRecord and defaultStore/StateManager/BasicAction/TwoPhaseCoordinator/ArjunaTransactionImple.
+ * The easiest way to check when JBoss EAP server 1 is recovered is to look in the object store and check that all the records are now cleaned up. The records that should be cleared are the ones in the defaultStore/CosTransactions/XAResourceRecord and defaultStore/StateManager/BasicAction/TwoPhaseCoordinator/ArjunaTransactionImple.
* Records will remain in defaultStore/Recovery/FactoryContact and defaultStore/RecoveryCoordinator and that is to be expected. Run:
tree server*/standalone/data/tx-object-store
View
30 jts/README.md
@@ -73,10 +73,10 @@ _Note_: For the purpose of this quickstart, replace the word `QUICKSTART_DATABAS
Be sure to start the PostgreSQL database. Unless you have set up the database to automatically start as a service, you must repeat the instructions "Start the database server" for your operating system every time you reboot your machine.
-Wait until later in these instructions to add the PostgreSQL module and driver configuration to the first JBoss server.
+Wait until later in these instructions to add the PostgreSQL module and driver configuration to the first JBoss EAP server.
-Configure the JBoss Servers
+Configure the JBoss EAP Servers
---------------------------
For this example, you will need two instances of the application server, with a subtle startup configuration difference. Application server 2 must be started up with a port offset parameter provided to the startup script as "-Djboss.socket.binding.port-offset=100".
@@ -88,10 +88,10 @@ Since both application servers must be configured in the same way, you must conf
You configure the security domain by running JBoss CLI commands. For your convenience, this quickstart batches the commands into a `configure-transactions.cli` script provided in the root directory of this quickstart.
1. Before you begin, back up your server configuration file
- * If it is running, stop the JBoss server.
+ * If it is running, stop the JBoss EAP server.
* Backup the file: `JBOSS_HOME/standalone/configuration/standalone-full.xml`
* After you have completed testing this quickstart, you can replace this file to restore the server to its original configuration.
-2. Start the JBoss server with the full profile, passing a unique node ID by typing the following command. Be sure to replace `UNIQUE_NODE_ID_1` with a node identifier that is unique to both servers.
+2. Start the JBoss EAP server with the full profile, passing a unique node ID by typing the following command. Be sure to replace `UNIQUE_NODE_ID_1` with a node identifier that is unique to both servers.
For Linux: JBOSS_HOME/bin/standalone.sh -c standalone-full.xml -Djboss.tx.node.id=UNIQUE_NODE_ID_1
For Windows: JBOSS_HOME\bin\standalone.bat -c standalone-full.xml -Djboss.tx.node.id=UNIQUE_NODE_ID_1
@@ -109,12 +109,12 @@ You configure the security domain by running JBoss CLI commands. For your conven
The batch executed successfully.
{"outcome" => "success"}
-_NOTE:_ When you have completed testing this quickstart, it is important to [Remove the JTS Configuration from the JBoss Server](#remove-the-jts-configuration-from-the-jboss-server).
+_NOTE:_ When you have completed testing this quickstart, it is important to [Remove the JTS Configuration from the JBoss EAP Server](#remove-the-jts-configuration-from-the-jboss-eap-server).
### Review the Modified Server Configuration
-If you want to review and understand newly added XML configuration, stop the JBoss server and open the `JBOSS_HOME/standalone/configuration/standalone-full.xml` file.
+If you want to review and understand newly added XML configuration, stop the JBoss EAP server and open the `JBOSS_HOME/standalone/configuration/standalone-full.xml` file.
1. The orb initializers `transactions` attribute is changed from "spec" to "on" in the `jacorb` subsystem to enable JTS. A naming root is also added to the subsystem.
@@ -138,11 +138,11 @@ If you want to review and understand newly added XML configuration, stop the JBo
<jts/>
</subsystem>
-_NOTE:_ When you have completed testing this quickstart, it is important to [Remove the JTS Configuration from the JBoss Server](#remove-the-jts-configuration-from-the-jboss-server).
+_NOTE:_ When you have completed testing this quickstart, it is important to [Remove the JTS Configuration from the JBoss EAP Server](#remove-the-jts-configuration-from-the-jboss-eap-server).
### Clone the JBOSS_HOME Directory
-Make a copy of this JBoss directory structure to use for the second server.
+Make a copy of this JBoss EAP directory structure to use for the second server.
### Configure Server1 to use PostgreSQL
@@ -150,10 +150,10 @@ Application server 1 must be now configured to use PostgreSQL.
1. Be sure to start the PostgreSQL database. Unless you have set up the database to automatically start as a service, you must repeat the instructions "Start the database server" for your operating system every time you reboot your machine.
2. Follow the instructions to [Add the PostgreSQL Module to the JBoss EAP Server](https://github.com/jboss-developer/jboss-developer-shared-resources/blob/master/guides/CONFIGURE_POSTGRESQL.md#add-the-postgresql-module-to-the-jboss-eap-server) to the server 1 install only.
-3. Follow the instructions to [Configure the PostgreSQL Driver in the JBoss Server](https://github.com/jboss-developer/jboss-developer-shared-resources/blob/master/guides/CONFIGURE_POSTGRESQL.md#configure-the-postgresql-driver-in-the-jboss-server) for the server 1 configuration.
+3. Follow the instructions to [Configure the PostgreSQL Driver in the JBoss EAP Server](https://github.com/jboss-developer/jboss-developer-shared-resources/blob/master/guides/CONFIGURE_POSTGRESQL.md#configure-the-postgresql-driver-in-the-jboss-eap-server) for the server 1 configuration.
-Start the JBoss Servers
+Start the JBoss EAP Servers
-------------------------
Start the the two JBoss EAP servers with the full profile, passing a unique node ID by typing the following command. You must pass a socket binding port offset on the command to start the second server. Be sure to replace `UNIQUE_NODE_ID` with a node identifier that is unique to both servers.
@@ -175,7 +175,7 @@ Build and Deploy the Quickstart
Since this quickstart builds two separate components, you can not use the standard *Build and Deploy* commands used by most of the other quickstarts. You must follow these steps to build, deploy, and run this quickstart.
-1. Make sure you have started the JBoss server with the PostgreSQL driver
+1. Make sure you have started the JBoss EAP server with the PostgreSQL driver
2. Open a command prompt and navigate to the root directory of this quickstart.
3. Type this command to build and deploy the archive:
@@ -206,14 +206,14 @@ The web page will also change and show you the new list of customers.
Undeploy the Archive
--------------------
-1. Make sure you have started the JBoss Server as described above.
+1. Make sure you have started the JBoss EAP server as described above.
2. Open a command prompt and navigate to the root directory of this quickstart.
3. When you are finished testing, type this command to undeploy the archive:
mvn package jboss-as:undeploy
-Remove the JTS Configuration from the JBoss Server
+Remove the JTS Configuration from the JBoss EAP Server
---------------------------
You must remove the JTS server configuration you did during setup because it interferes with the JTA quickstarts.
@@ -222,7 +222,7 @@ You can modify the server configuration by running the `remove-jts-transactions.
### Remove the JTS Server Configuration by Running the JBoss CLI Script
-1. Start the JBoss server with the full profile.
+1. Start the JBoss EAP server with the full profile.
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
@@ -241,7 +241,7 @@ This script removes the `test` queue from the `messaging` subsystem in the serve
### Remove the JTS Server Configuration using the JBoss CLI Tool
-1. Start the JBoss server with the full profile.
+1. Start the JBoss EAP server with the full profile.
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
View
10 kitchensink-ear/README.md
@@ -31,10 +31,10 @@ Configure Maven
If you have not yet done so, you must [Configure Maven](https://github.com/jboss-developer/jboss-developer-shared-resources/blob/master/guides/CONFIGURE_MAVEN.md#configure-maven-to-build-and-deploy-the-quickstarts) before testing the quickstarts.
-Start the JBoss Server
+Start the JBoss EAP Server
-------------------------
-1. Open a command prompt and navigate to the root of the JBoss server directory.
+1. Open a command prompt and navigate to the root of the JBoss EAP directory.
2. The following shows the command line to start the server:
For Linux: JBOSS_HOME/bin/standalone.sh
@@ -46,7 +46,7 @@ Build and Deploy the Quickstart
_NOTE: The following build command assumes you have configured your Maven user settings. If you have not, you must include Maven setting arguments on the command line. See [Build and Deploy the Quickstarts](../README.md#build-and-deploy-the-quickstarts) for complete instructions and additional options._
-1. Make sure you have started the JBoss Server as described above.
+1. Make sure you have started the JBoss EAP server as described above.
2. Open a command prompt and navigate to the root directory of this quickstart.
3. Type this command to build and deploy the archive:
@@ -71,7 +71,7 @@ The application will be running at the following URL: <http://localhost:8080/jbo
Undeploy the Archive
--------------------
-1. Make sure you have started the JBoss Server as described above.
+1. Make sure you have started the JBoss EAP server as described above.
2. Open a command prompt and navigate to the root directory of this quickstart.
3. When you are finished testing, type this command to undeploy the archive:
@@ -85,7 +85,7 @@ This quickstart provides Arquillian tests. By default, these tests are configure
_NOTE: The following commands assume you have configured your Maven user settings. If you have not, you must include Maven setting arguments on the command line. See [Run the Arquillian Tests](https://github.com/jboss-developer/jboss-developer-shared-resources/blob/master/guides/RUN_ARQUILLIAN_TESTS.md#run-the-arquillian-tests) for complete instructions and additional options._
-1. Make sure you have started the JBoss Server as described above.
+1. Make sure you have started the JBoss EAP server as described above.
2. Open a command prompt and navigate to the root directory of this quickstart.
3. Type the following command to run the test goal with the following profile activated:
View
10 kitchensink-jsp/README.md
@@ -32,10 +32,10 @@ Configure Maven
If you have not yet done so, you must [Configure Maven](https://github.com/jboss-developer/jboss-developer-shared-resources/blob/master/guides/CONFIGURE_MAVEN.md#configure-maven-to-build-and-deploy-the-quickstarts) before testing the quickstarts.
-Start the JBoss Server
+Start the JBoss EAP Server
-------------------------
-1. Open a command prompt and navigate to the root of the JBoss server directory.
+1. Open a command prompt and navigate to the root of the JBoss EAP directory.
2. The following shows the command line to start the server:
For Linux: JBOSS_HOME/bin/standalone.sh
@@ -47,7 +47,7 @@ Build and Deploy the Quickstart
_NOTE: The following build command assumes you have configured your Maven user settings. If you have not, you must include Maven setting arguments on the command line. See [Build and Deploy the Quickstarts](../README.md#build-and-deploy-the-quickstarts) for complete instructions and additional options._
-1. Make sure you have started the JBoss Server as described above.
+1. Make sure you have started the JBoss EAP server as described above.
2. Open a command prompt and navigate to the root directory of this quickstart.
3. Type this command to build and deploy the archive:
@@ -75,7 +75,7 @@ _Note:_ You will see the following warnings and errors in the server log. Hibern
Undeploy the Archive
--------------------
-1. Make sure you have started the JBoss Server as described above.
+1. Make sure you have started the JBoss EAP server as described above.
2. Open a command prompt and navigate to the root directory of this quickstart.
3. When you are finished testing, type this command to undeploy the archive:
@@ -89,7 +89,7 @@ This quickstart provides Arquillian tests. By default, these tests are configure
_NOTE: The following commands assume you have configured your Maven user settings. If you have not, you must include Maven setting arguments on the command line. See [Run the Arquillian Tests](https://github.com/jboss-developer/jboss-developer-shared-resources/blob/master/guides/RUN_ARQUILLIAN_TESTS.md#run-the-arquillian-tests) for complete instructions and additional options._
-1. Make sure you have started the JBoss Server as described above.
+1. Make sure you have started the JBoss EAP server as described above.
2. Open a command prompt and navigate to the root directory of this quickstart.
3. Type the following command to run the test goal with the following profile activated:
View
10 kitchensink-ml-ear/README.md
@@ -107,10 +107,10 @@ Configure Maven
If you have not yet done so, you must [Configure Maven](https://github.com/jboss-developer/jboss-developer-shared-resources/blob/master/guides/CONFIGURE_MAVEN.md#configure-maven-to-build-and-deploy-the-quickstarts) before testing the quickstarts.
-Start the JBoss Server
+Start the JBoss EAP Server
-------------------------
-1. Open a command prompt and navigate to the root of the JBoss server directory.
+1. Open a command prompt and navigate to the root of the JBoss EAP directory.
2. The following shows the command line to start the server:
For Linux: JBOSS_HOME/bin/standalone.sh
@@ -122,7 +122,7 @@ Build and Deploy the Quickstart
_NOTE: The following build command assumes you have configured your Maven user settings. If you have not, you must include Maven setting arguments on the command line. See [Build and Deploy the Quickstarts](../README.md#build-and-deploy-the-quickstarts) for complete instructions and additional options._
-1. Make sure you have started the JBoss Server as described above.
+1. Make sure you have started the JBoss EAP server as described above.
2. Open a command prompt and navigate to the root directory of this quickstart.
3. Type this command to build and deploy the archive:
@@ -159,7 +159,7 @@ _Note:_ You will see the following warnings and errors in the server log. Hibern
Undeploy the Archive
--------------------
-1. Make sure you have started the JBoss Server as described above.
+1. Make sure you have started the JBoss EAP server as described above.
2. Open a command prompt and navigate to the root directory of this quickstart.
3. When you are finished testing, type this command to undeploy the archive:
@@ -173,7 +173,7 @@ This quickstart provides Arquillian tests. By default, these tests are configure
_NOTE: The following commands assume you have configured your Maven user settings. If you have not, you must include Maven setting arguments on the command line. See [Run the Arquillian Tests](https://github.com/jboss-developer/jboss-developer-shared-resources/blob/master/guides/RUN_ARQUILLIAN_TESTS.md#run-the-arquillian-tests) for complete instructions and additional options._
-1. Make sure you have started the JBoss Server as described above.
+1. Make sure you have started the JBoss EAP server as described above.
2. Open a command prompt and navigate to the root directory of this quickstart.
3. Type the following command to run the test goal with the following profile activated: