WFLY-13464 Change server startup documentation to reference local ins…

…tallation and standalone-microprofile.xml
wildfly · May 14, 2020 · 577e63d · 577e63d
1 parent 3ff06c4
commit 577e63d
Showing 1 changed file with 4 additions and 17 deletions.
diff --git a/microprofile-openapi/README.adoc b/microprofile-openapi/README.adoc
@@ -20,28 +20,15 @@ To complete this guide, you will need:
 * JDK 1.8+ installed with `JAVA_HOME` configured appropriately
 * Apache Maven 3.5.3+
 
+include::../shared-doc/use-of-jboss-home-name.adoc[leveloffset=+1]
+
 == Steps
 
-. Start a {productName} instance.
+. Start a {productName} instance using the microprofile profile.
 +
 [source, shell]
 ----
-$ mvn wildfly:run &
-----
-
-. Add support for MicroProfile OpenAPI by adding the requisite extension and subsystem.
-+
-[source, shell]
-----
-$ mvn wildfly:execute-commands -Dwildfly.commands=/extension=org.wildfly.extension.microprofile.openapi-smallrye:add
-$ mvn wildfly:execute-commands -Dwildfly.commands=/subsystem=microprofile-openapi-smallrye:add
-----
-
-. Since the MicroProfile OpenAPI subsystem modifies {productName}'s deployment chain, the server needs to be reloaded.
-+
-[source, shell]
-----
-$ mvn wildfly:shutdown -Dwildfly.reload=true
+$ {jbossHomeName}/bin/standalone.sh --server-config=standalone-microprofile.xml &
 ----
 
 . Build and deploy the sample application to {productName}.