WildFly is a modern, flexible, lightweight and managed application runtime, which is written in Java and implements the latest standards and technology of the Java Platform Enterprise Edition (Java EE) specification. WildFly is entirely free and open-source, available to be run on multiple platforms.
Among the main features of this application server:- customizable runtime based on the pluggable subsystems, which can be integrated or removed on demand
- Java EE8 support to implement the latest enterprise Java standards in easy to consume framework
- modular approach with an ability to start each service in isolation
-
fast, lightweight and optimized for ultimate performance
2. In the opened environment topology wizard, navigate to the Java tab and select WildFly from the list of available application servers. Then, specify the allocated resources limit using cloudlet sliders, choose a region and edit the name of my environment.
Notes:
- WildFly is not compatible with Java 6 and 7; therefore these versions are not available
- due to the minimal WildFly resources requirements, it is strongly recommended to allocate more than 1 cloudlet for this node. Otherwise, I can experience low server performance and even its failure
- WildFly can be launched in the Standalone mode using the configuration file defined in the STANDALONE_MODE_CONFIG environment variable
- CloudJiffy provides out-of-box support of the WildFly servers Auto-Clustering in the Managed Domain mode via the appropriate switcher in topology wizard
Click the Create button when ready.
3. Wait for a couple of minutes for the environment to be created and click the Open in Browser button next to it.
4. The WildFly default welcome page lists some useful links to help me get started.
In order to access the WildFly Administration Console, click the appropriate link or get the URL from the email (received after server creation) alongside other access credentials. Also, you can establish an SSH connection to your WildFly server and use the WildFly CLI inbuilt utility for managing.Standalone Mode
There are four certified profiles for standalone mode:
- standalone.xml (default) - configurations for Java Enterprise Edition 8 Web with the required technologies
- standalone-full.xml - configurations for Java Enterprise Edition 8 Full with all the EE 8 technologies
- standalone-ha.xml - configurations for Java Enterprise Edition 8 Web with high availability
-
standalone-full-ha.xml - configurations for Java Enterprise Edition 8 Full with high availability
In the case of using the HA configs (the last two options), the jgroups protocol is used for messaging between nodes. It is configured to use the authorization with the MD5 token and asymmetrical encryption by default. Such an implementation prevents non-authorized nodes from being able to join a cluster and non-members from communicating with cluster members.