Ce contenu n'est pas disponible dans la langue sélectionnée.
Chapter 5. Validating the deployment
After you successfully run the playbook, the JBoss Web Server collection automatically installs Red Hat JBoss Web Server on your target hosts. If you have added customized tasks to the playbook, Ansible also automatically deploys any JBoss Web Server applications on your targets hosts, as appropriate. You can optionally check the status of JBoss Web Server by using the systemctl command on the target host or by using the curl command on a remote host.
Prerequisites
- You have run the playbook.
Procedure
Optional: On the JBoss Web Server host, enter the following command as the root user:
# systemctl status <service_name>In the preceding command, replace <service_name> with the correct service name for your JBoss Web Server installation. The default service name is
tomcat. For more information about setting up a service name, see Automating the integration of JBoss Web Server withsystemd.NoteThis step requires that JBoss Web Server is integrated with
systemd.Optional: On a remote host, enter the following command as the root user:
# curl http://<target_host>:8080/In the preceding command, replace <target_host> with the IP address or host name of the JBoss Web Server host that you want to access. The preceding command assumes that the JBoss Web Server is accessible through the default port
8080and that the target firewall and network allow remote access to the port.
The JBoss Web Server collection also includes a validate.yml playbook in the playbooks folder. You can run the validate.yml playbook if you want the JBoss Web Server collection to perform automated validation checks. For more information about the validate.yml playbook, refer to the information page for the jws_validation role in Ansible automation hub.
Additional resources
