Ansible collections

WildFly server configuration with Ansible collection for JCliff, Part 3

WildFly server configuration with Ansible collection for JCliff, Part 3

Welcome to the final installment in this three-part series about using Ansible Collection for JCliff to manage WildFly or Red Hat JBoss Enterprise Application Platform (JBoss EAP) instances. Previously, we’ve discussed installing and configuring the JCliff Ansible collection and using its basic features. In this article, we discuss advanced options available with the project’s latest release. Without further ado, let’s dive in!

Continue reading WildFly server configuration with Ansible collection for JCliff, Part 3

Share
WildFly server configuration with Ansible collection for JCliff, Part 1

WildFly server configuration with Ansible collection for JCliff, Part 1

This three-part series guides you through using Ansible to fine-tune a WildFly or Red Hat JBoss Enterprise Application Platform (JBoss EAP) server configuration. We will use the most recently released version of the Ansible collection for JCliff to extend Ansible’s capabilities. The JCliff collection supports configuring several of the application server subsystems directly from Ansible.

In Part 1, we will mostly focus on the groundwork and discuss all the steps required to be able to use JCliff within Ansible. Once properly installed, we’ll use JCliff to configure WildFly’s system_props subsystem, which lets us declare system variables in WildFly’s server configuration. Once we have that foundation in place, we’ll begin exploring more interesting configurations in Part 2 and Part 3.

Note: See the Ansible documentation for more about Ansible collections.

Continue reading “WildFly server configuration with Ansible collection for JCliff, Part 1”

Share