WildFly Unzip Installation

Internal

• WildFly Installation

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.

Create a Symbolic Link

ln -s ./jboss-eap-6.4 jboss

Optional for a Standalone Installation

If you perform a standalone installation you can remove the domain subdirectory to reduce the clutter and confusion. You won't need it.

Optional on a Host Controller and/or Domain Controller

This applies when we install a host controller and when the host controller is also the domain controller: the standalone directory can be removed.

cd jboss
rm -r standalone
cd bin
rm standalone *

Optional on a non-Windows Machine

The *.bat files from bin can be removed.

cd jboss/bin
rm *.bat

Post-Install Configuration

Post-Install Configuration User

Perform all post-install configuration operations as the JBoss runtime user.

Unset the JBOSS_HOME Environment Variable

If the JBOSS_HOME value is accidentally set to point to another WildFly deployment, it will interfere with the next steps, so it is best if you unset it.

Security

Add a management user, conventionally named admin. Note that this user does not represent the identity used by a subordinate host controller to connect to the domain controller, that will be configured later. The procedure is described here:

Adding a User to the Management Realm

Network

Configure the bind addresses for management and public interfaces. The bind address of the management interface can be set externally with jboss.bind.address.management system property. The bind address of the public interface can be set externally with jboss.bind.address system property.

Note that in domain mode, host controllers connect to the domain controller's management interface to get domain configuration, so the domain controller management functions have to be externally accessible over the management interface, hence the management interface has to be visible on the management (internal) network. A subordinate host controller does not have to expose its management interface. The public interface must be configured on all hosts and accessible externally, provided that the server instances must be available externally.

Standalone Node

Set 'jboss.bind.address' as described here

Subordinate Host Controller

Will be described in detail in the Subordinate Host Controller Configuration section below.

Domain Controller

Will be described in detail in the Domain Controller Configuration section below.

Extra Standalone Configuration

Some of the standalone-*.xml files can be removed if you know that you are not going to use those profiles.

Domain Controller Configuration

WildFly Domain Controller Post-Install Configuration

Start WildFly as a Service on Linux

Subordinate Host Controller Configuration

The domain controller must be fully operational when configuring subordinated host controllers, since we need to interact with the domain controller during the subordinated host controller installation (create users, etc.)

Subordinate WildFly Host Controller Post-Install Configuration

Start WildFly as a Service on Linux

Start WildFly as a Service on Linux

Return Here

TODO

• Re-create the 2 + 1 EAP environment from scratch, verify the procedure (and update it), and then document it in the em Manual.

em create --ami_id ami-775e4f16 --group sg-3b64b65c --storage-size 10 dc01
em create --ami_id ami-775e4f16 --group sg-3b64b65c --storage-size 10 n01
em create --ami_id ami-775e4f16 --group sg-3b64b65c --storage-size 10 n02
em overlay eap-dc dc01
em start d01
em overlay eap-node n01
em overlay eap-node n02
# reboot everything, the nodes should connect.

• Update the EC2 environment diagram with the new names.

!!!Smoke Tests

jboss-host-controller start

Verify that $JBOSS_HOME/domain/log is created and it is owned by the user supposed to run JBoss.

Verify that $JBOSS_HOME/domain/servers contains directories corresponding to the servers declared in Template:Host.xml.

grep java 

Optionally, add this to the JBoss account:

grep java 

Look for "Process Controller", "Host Controller" and the "Server: ..."

For each server, cat {{$JBOSS_HOME/domain/servers/<server-name>/log/server.log}} and make sure the server started with no errors.

grep ERROR

cat server.log

You should get zero errors and warnings.

Repeat the same operations after reboot.

Verify cluster topology with the CLI: [JBoss7 CLI Navigate Domain Topology]

Verify cluster topology with the management console: [JBoss7 Management Console#NavigateDomainTopology].