WildFly Unzip Installation: Difference between revisions
No edit summary |
|||
| Line 15: | Line 15: | ||
Unzip in place ''as the user intended to run the server''. For example, if the application server will be run by an "eap" user, become that user and extract under that user's identity. If there are no sufficient permissions on the parent directory, temporarily lessen the permission during the unzip operation, then restore more restrictive permissions on the parent folder. | Unzip in place ''as the user intended to run the server''. For example, if the application server will be run by an "eap" user, become that user and extract under that user's identity. If there are no sufficient permissions on the parent directory, temporarily lessen the permission during the unzip operation, then restore more restrictive permissions on the parent folder. | ||
==Unzip== | |||
<pre> | |||
unzip .../jboss-eap-6.4.0.zip | |||
</pre> | |||
The operation will create a <tt>./jboss-eap-6.4</tt> directory. | |||
Revision as of 23:55, 11 February 2016
Internal
Overview
This document describes the WildFly "manual" installation procedure. It consists in unzipping a release zip file and configuring the deployment. It applies to both standalone and domain mode for WildFly and EAP releases. Additional configuration such as enabling SSL, adding data sources, adding HA to the domain controller, etc. can be performed after the installation. The examples below mention "jboss", as the procedure was applied to an EAP installation.
Extract Release from ZIP File
Extraction User
Unzip in place as the user intended to run the server. For example, if the application server will be run by an "eap" user, become that user and extract under that user's identity. If there are no sufficient permissions on the parent directory, temporarily lessen the permission during the unzip operation, then restore more restrictive permissions on the parent folder.
Unzip
unzip .../jboss-eap-6.4.0.zip
The operation will create a ./jboss-eap-6.4 directory.