Page tree

Skip to end of metadata
Go to start of metadata

This chapter provides sample instructions for deploying the WAR file to WildFly. See Upgrading for WildFly Deployments for instructions on updating to a new version of the SOAtest and Virtualize Server.

  1. Download WildFly 10.1 or higher for your platform from
  2. Extract the downloaded WildFly file to a location of your choice (<WILDFLY_HOME>) and remove the <WILDFLY_HOME>/welcome-content directory.
  3. Start WildFly according to your preference (see the WildFly documentation for start-up options). For example, run the <WILDFLY_HOME>/bin/standalone.bat script to start the standalone server using the default configuration.
  4. Go to http://localhost:9990/ and follow the instructions for configuring WildFly to manage deployments. You may need to add a WildFly user with administrative access.
  5. (Optional) To deploy the WAR file over SSL, configure the port for HTTPS as described in step 7. No additional configuration is required.
  6. Extract the contents of the WAR file into <UNZIPPED_SOAVIRT_WAR>.
  7. Open the <UNZIPPED_SOAVIRT_WAR>/WEB-INF/ configuration file and specify the following (see Server Configuration for details):
    • Ports used by WildFly, e.g., server.port.http=8080 or server.port.https=8443. The ports specified in must match the ports specified in the WildFly configuration.
    • License.
    • Workspace.
  8. Compress the contents of the <UNZIPPED_SOAVIRT_WAR> back into the WAR and deploy it using one of the following methods:
    • Web interface:
      1. Go to http://localhost:9990/ and click the Deployments tab.
      2. Click Add and use the wizard to deploy the WAR file.
    • CLI console:
      1. Start <WILDFLY_HOME>/bin/jboss-cli.bat and run the following command:

        [[email protected]:9990 /] deploy <WAR>
  9. Browse to http://localhost:8080/ (adjust the port if needed). If the following message appears, then the application was installed correctly:

There are no deployments on this server. Cannot respond to this request: /.

Increasing the POST Size Limit 

If you have tests larger than 10 MB, you should increase the POST size limit by adding a max-post-size attribute in the <WILDFLY_HOME>/standalone/configuration/standalone.xml configuration file. The following example demonstrates how to add this attribute for both HTTP and HTTPS:

<server name="default-server">
                <http-listener name="default" max-post-size="25485760" socket-binding="http" redirect-socket="https" enable-http2="true"/>
                <https-listener name="https" max-post-size="25485760" socket-binding="https" security-realm="ApplicationRealm" enable-http2="true"/>
                <host name="default-host" alias="localhost">
                    <location name="/" handler="welcome-content"/>
                    <filter-ref name="server-header"/>
                    <filter-ref name="x-powered-by-header"/>
  • No labels