This chapter provides sample instructions for deploying Virtualize Server to WildFly. See UpgradingVirtualize Server for WildFly Deployments for instructions on updating Virtualize Server.
- Download WildFly 10.1 or higher for your platform from http://wildfly.org/.
- Extract the downloaded WildFly file to a location of your choice (<WILDFLY_HOME>) and remove the <WILDFLY_HOME>/welcome-content directory.
- 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.
- 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.
- (Optional) To deploy the WAR file over SSL, configure the port for HTTPS as described in step 7. No additional configuration is required.
- Extract the contents of the WAR file into <UNZIPPED_SOAVIRT_WAR>.
- Open the <UNZIPPED_SOAVIRT_WAR>/WEB-INF/config.properties configuration file and specify the following (see Configuring Virtualize Server for details):
- Ports used by WildFly, e.g.,
server.port.http=8080
orserver.port.https=8443
. The ports specified in config.properties must match the ports specified in the WildFly configuration. - License.
- Workspace.
- Ports used by WildFly, e.g.,
- Compress the contents of the <UNZIPPED_SOAVIRT_WAR> back into the WAR and deploy it using one of the following methods:
- Web interface:
- Go to http://localhost:9990/ and click the Deployments tab.
- Click Add and use the wizard to deploy the WAR file.
- CLI console:
- Start <WILDFLY_HOME>/bin/jboss-cli.bat and run the following command:
[standalone@localhost:9990 /] deploy <WAR>
- Start <WILDFLY_HOME>/bin/jboss-cli.bat and run the following command:
- Web interface:
- 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"/> </host> </server>