 Hello and welcome to getting up to speed with Ansible Automation Platform. This tutorial demonstrates and guides you to the process of preparing a local machine with the necessary tooling and then deploying an instance of Wildfly. First, let's get Ansible installed on the local machine, a local machine from which we would like to push the configurations to the managed nodes. The managed nodes are the ones we would like to configure and they can be defined under inventory. So I have installed the Ansible on my local machine. Let me quickly check the version of the Ansible installed. We can see Ansible code 2.12.3 is installed. Ansible collections are the distribution format for Ansible content that can include playbook, roles, modules and plugins. For this tutorial, we are using our Wildfly collection. In this tutorial, we are also using execution environment and the Ansible navigator utility to perform the automation and provisioning of Wildfly instance. I have Ansible navigator installed on my local machine. If you have not installed the Ansible and the Ansible navigator on your local machine, please refer to the tutorial. Now that we have Ansible and Ansible navigator installed, let's quickly check the default collections that come with the Ansible navigator. So we can look for the collections here. So these are the collections that come by default through Ansible navigator. So for this tutorial, we are using an execution environment. So we are using an execution environment image that is provided by Red Hat. This execution environment image has all the collections that are available through our Ansible team. So let's take a quick look on the collections that are available through this image. So we can see the different collections that are available through our team. And for this particular tutorial, we would be using middleware underscore automation.wildfly collection. Now that we have all the things set up on the local machine, let's start looking into setting up an inventory. So we need to create an inventory file and we need a VM where we would like to deploy our Wildfly instance. So I have a real egg VM. We need the IP address to the instance and the login information for Ansible to access the VM. In this tutorial, we are using SSL keys instead of passwords. So these keys are created on the controller node and we would provide the path of the private key in the inventory file. So let's create the inventory file. If you see here, this is the host and this is the IP address of the host and the Ansible user is root and this is the path to my private key. And let's also take a look on the playbook. So in this playbook, we can see we are installing under slash OPT. The install name is Wildfly. We are installing 26.0.0. Final version and we can see we are using middleware underscore automation.wildfly collection. We are using the Wildfly install rule to install the Wildfly and we are using the Wildfly underscore system D rule to set up the system D configurations or the JDBC driver configurations. So let's also take a quick look on the VM, which the real 8 VM. So let's now SSH into the VM. So let's confirm it's a real 8 VM. And let's also see the reports that are enabled on this VM. I have subscribed this VM to the customer portal and I have the default real 8 reports enabled. So we can see the base OS RPM repo and the AppStream RPM repo for real 8 are enabled. This should be good to go. So now let's run the playbook to deploy the Wildfly instance. So as I said before, we are using the Ansible navigator and we are passing the execution environment image provided by the Red Hat team and we are running the playbook and we are passing the inventory file and let's start. So this will take a few seconds to pull up the inventory and once it's there, it installs JDK and it will download all the required things and it will download the Wildfly instance, copy the instance, copy the zip file to the VM and then it will install and set things up. So let's now wait to get it complete. We can see it's copied and the installation is trying to install. And once the installation is complete, it's trying to set up the system MD or JDBC driver and it's done. So now the playbook execution is done. Now our next step is to wait for if the instance is deployed properly and the ports are accessible now. Now let's access our VM and let's do a help check. We can see the outcome is true and the value is running. It seems to be fine. Now let's also see if the service is running, the Wildfly service. You can see the service is active and running without any issues. We can also use a validate.yml that's available in the tutorial. It does the same thing. You can use the playbook instead. On conclusion, we saw in this tutorial how to provision an instance of Wildfly using the Ansible collection for Wildfly. We can also deploy JBoss EAP instead of open source Wildfly with the same collection. If you are using on the production environment, I would highly recommend to use the EAP collection that is available on the Ansible Automation Hub. I can quickly show you that as well. This is our EAP collection which is available on the Automation Hub. Once again, thank you for watching the tutorial. Bye for now.