Chapter 3. Enabling automated deployments of JBoss Web Server The JBoss Web Server collection provides a comprehensive set of variables and default values that you can manually update to match your setup requirements. These variable settings provide all the information that the JBoss Web Server collection requires to complete an automated and customized installation of Red Hat JBoss Web Server on your target hosts. For a full list of variables that the JBoss Web Server collection provides, see the information page for the jws role in Ansible automation hub . The information page for the jws role lists the names, descriptions, and default values for all the variables that you can define. Note You can define variables in multiple ways. By default, the JBoss Web Server collection includes an example playbook.yml file that links to a vars.yml file in the same playbooks folder. For illustrative purposes, the instructions in this section describe how to define variables in the vars.yml file that the collection provides. You can use a different way to define variables if you prefer. You can define variables to automate the following tasks: Install JBoss Web Server from archive files that you can choose to download either automatically or manually from the Red Hat Customer Portal . Install JBoss Web Server from RPM packages . Ensure that a supported JDK version is installed on your target hosts . Ensure that a product user account and group are created on your target hosts . Integrate JBoss Web Server with systemd . Configure the JBoss Web Server installation . You can also automate the deployment of web applications by adding customized tasks to the playbook, as described in Enabling the automated deployment of JBoss Web Server applications on your target hosts . 3.1. Enablement of automated installations of JBoss Web Server from archive files By default, the JBoss Web Server collection is configured to install Red Hat JBoss Web Server on each target host from product archive files. Depending on your setup requirements, you can enable the JBoss Web Server collection to install a base product release, product patch updates, or both simultaneously from archive files. You can choose to download the archive files manually from the Red Hat Customer Portal or enable the JBoss Web Server collection to download the archive files automatically. 3.1.1. Enabling the automated installation of a JBoss Web Server base release You can enable the JBoss Web Server collection to install the base release of a specified JBoss Web Server version from product archive files. A base release is the initial release of a specific product version (for example, 6.0.0 is the base release of version 6.0). The JBoss Web Server collection requires that local copies of the appropriate archive files are available on your Ansible control node. If copies of the archive files are not already on your system, you can set variables to specify Red Hat service account credentials to permit automatic file downloads from the Red Hat Customer Portal. Alternatively, you can download the archive files manually. Prerequisites You have installed the JBoss Web Server collection . If copies of the JBoss Web Server archive files are already on your system, you have copied these archive files to your Ansible control node. If you want the JBoss Web Server collection to download archive files automatically from the Red Hat Customer Portal, you have created a Red Hat service account. Note Service accounts enable you to securely and automatically connect and authenticate services or applications without requiring end-user credentials or direct interaction. To create a service account, log in to the Service Accounts page in the Red Hat Hybrid Cloud Console, and click Create service account . If you prefer to download the archive files manually, you have downloaded the appropriate archive files to your Ansible control node. For more information, see the Red Hat JBoss Web Server Installation Guide . Note If you manually download the archive files, you do not need to extract these files on your Ansible control node. In this situation, the JBoss Web Server collection extracts the archive files automatically. Procedure On your Ansible control node, open the vars.yml file. To specify the JBoss Web Server version that you want to install, set the jws_version variable to the appropriate base release. For example: Note Ensure that the value you specify for the jws_version variable matches the version of the product archive files that you want to install. For example, to install the archive files for JBoss Web Server 6.0, specify a value of 6.0.0 . By default, the JBoss Web Server collection is configured to install both the main application server archive and the native archive for the product version that you specify. If you set the jws_native variable to False , the JBoss Web Server collection cannot install the native archive, which causes issues for features such as SELinux policies that require the installation of a native archive file. If you do not specify credentials for automatic file downloads as described in Step 3 , ensure that you have copied the archive files for the specified product version to your Ansible control node. In this situation, ensure that the copied native archive file matches the operating system version that is installed on your target hosts. If copies of the JBoss Web Server archive files do not exist on your Ansible control, the collection contacts the Red Hat Customer Portal by default to download the archive files automatically. To ensure successful contact with the Red Hat Customer Portal, set the rhn_username and rhn_password variables to specify your Red Hat service account credentials. For example: In the preceding example, replace <client_ID> and <client_secret> with the client ID and secret that are associated with your Red Hat service account. Note By default, the collection automatically determines which native archive file matches the operating system version that is installed on your target hosts. If copies of the appropriate archive files already exist on your Ansible control node, the collection does not download these archive files again. If you prefer to download the archive files manually or you have already obtained these files in some other way, you can enforce a fully offline installation. For more information about enforcing offline installations, see Enabling the automated installation of JBoss Web Server product patch updates . If you changed the names of the downloaded archive files on your Ansible control node, set the zipfile_name and jws_native_zipfile variables to specify the files that you want to install. For example: In the preceding example, replace <application_server_file> and <native_file> with the appropriate archive file names. Note If you did not change the file names, you do not need to set the zipfile_name and jws_native_zipfile variables. The JBoss Web Server collection uses the value of the jws_version variable to determine the default file names automatically. Save your changes to the vars.yml file. By setting these variables, as appropriate, you enable the JBoss Web Server collection to install the base product release automatically on your target hosts when you subsequently run the playbook. 3.1.2. Enabling the automated installation of JBoss Web Server patch updates If product patch updates are available for the JBoss Web Server version that is being installed, you can also enable the JBoss Web Server collection to install these patch updates from archive files. Depending on your requirements, you can enable the JBoss Web Server collection to install either the latest available patch or a specified patch release. You can use the same steps to enable the automated installation of patch updates regardless of whether you want to install these updates at the same time as the base release or later. The JBoss Web Server collection requires that local copies of the appropriate archive files are available on your Ansible control node. If copies of the archive files are not already on your system, you can set variables to specify Red Hat service account credentials to permit automatic file downloads from the Red Hat Customer Portal. Alternatively, you can download the archive files manually. Note Patch updates are cumulative, which means that each patch update automatically includes any earlier patch releases that are available for the same product version. For example, a 6.0.2 patch update would include the 6.0.1 release, a 6.0.3 patch update would include the 6.0.1 and 6.0.2 releases, and so on. Important You cannot use cumulative patch updates to install the base ( X.X. 0) release of a product version. For example, a 6.0.2 patch would include the 6.0.1 release but cannot install the base 6.0.0 release. In this situation, you must ensure that the base release of the appropriate product version (for example, 6.0.0) is also installed either at the same time or previously. Prerequisites You have installed the JBoss Web Server collection . If copies of the archive files for the patch update that you want to install are already on your system, you have copied these archive files to your Ansible control node. If you want the JBoss Web Server collection to download archive files automatically from the Red Hat Customer Portal, you have created a Red Hat service account. Note Service accounts enable you to securely and automatically connect and authenticate services or applications without requiring end-user credentials or direct interaction. To create a service account, log in to the Service Accounts page in the Red Hat Hybrid Cloud Console, and click Create service account . If you prefer to download the archive files manually, you have downloaded the appropriate archive files to your Ansible control node. For more information, see the Red Hat JBoss Web Server Installation Guide . Note Because patch updates are cumulative, you only need to download the archive files for the patch release that you want to install. You do not need to download any patch updates. If you manually download the archive files, you do not need to extract these files on your Ansible control node. In this situation, the JBoss Web Server collection extracts the archive files automatically. Procedure On your Ansible control node, open the vars.yml file. Set the jws_apply_patches variable to True . For example: Note Ensure that the jws_version variable is set to the base release for the appropriate product version (for example, 6.0.0 ). The JBoss Web Server collection is configured to install the latest patch update by default. The collection contacts the Red Hat Customer Portal to determine the correct patch to install. If you want the collection to install a specified patch release rather than the latest patch update, set the jws_patch_version variable to the patch release that you want to install. For example: Based on the preceding example, the collection installs the cumulative 6.0.2 patch only, even if later patches are also available. When the jws_apply_patches variable is set to True , the JBoss Web Server collection contacts the Red Hat Customer Portal by default to check if new patch updates are available. The collection also downloads patch updates, if necessary. To ensure successful contact with the Red Hat Customer Portal, set the rhn_username and rhn_password variables to specify your Red Hat service account credentials. For example: In the preceding example, replace <client_ID> and <client_secret> with the client ID and secret that are associated with your Red Hat service account. Note By default, the collection automatically determines which native archive file matches the operating system version that is installed on your target hosts. If copies of the appropriate archive files already exist on your Ansible control node, the collection does not download these archive files again. If the jws_patch_version variable is set to a specific patch release, the collection downloads the specified patch release only, even if later patches are also available. If you prefer to download the archive files manually or you have already obtained these files in some other way, you can enforce a fully offline installation as described in Step 5 . If you want to enforce a fully offline installation and prevent the collection from contacting the Red Hat Customer Portal, set the jws_offline_install variable to True . For example: Note The jws_offline_install variable is useful if your Ansible control node does not have internet access or you want the collection to avoid contacting the Red Hat Customer Portal for file downloads. In this situation, you must set the jws_patch_version variable to the patch release you want to install. Ensure that you have copied the archive files for the appropriate patch update to your Ansible control node. In this situation, ensure that the copied native archive file matches the operating system version that is installed on your target hosts. If you set the jws_offline_install variable to True , the collection does not attempt to contact the Red Hat Customer Portal, even if you have also set the rhn_username and rhn_password variables to permit automatic file downloads. Save your changes to the vars.yml file. By setting these variables, as appropriate, you enable the JBoss Web Server collection to install the product patch updates automatically on your target hosts when you subsequently run the playbook. 3.2. Enabling the automated installation of JBoss Web Server from RPM packages You can enable the JBoss Web Server collection to install Red Hat JBoss Web Server on each target host from RPM packages. In this situation, the JBoss Web Server collection automatically obtains the RPM packages directly from Red Hat. Note When you enable the RPM installation method, the JBoss Web Server collection installs the latest RPM packages for the specified major version of JBoss Web Server, including any minor version and patch updates. Prerequisites Your system is compliant with Red Hat Enterprise Linux package requirements . You have registered your system with Red Hat Subscription Management and subscribed to the relevant Content Delivery Network (CDN) repositories . You have installed the JBoss Web Server collection . Procedure On your Ansible control node, open the vars.yml file. To specify the JBoss Web Server version that you want to install, set the jws_version variable to the appropriate major product version. For example: Note In this situation, the JBoss Web Server collection checks the first digit in the specified value to determine the major product version that you want to install. For example, if you want the collection to install the latest available RPM packages for JBoss Web Server 6, you can specify a value of 6.0.0 . Regardless of the minor version and release number that you specify (for example, 0.0 ), the collection installs the packages for the latest minor version and patch release of the specified major version. To enable installation from RPM packages, set the jws_install_method variable to rpm . For example: Save your changes to the vars.yml file. By setting these variables, you enable the JBoss Web Server collection to obtain and automatically install the RPM packages for the specified product version on your target hosts when you subsequently run the playbook. Note If you enable the installation of RPM packages for JBoss Web Server 6.0, the collection installs JBoss Web Server in the /opt/rh/jws6/root/usr/share/tomcat directory. If you want to use a different installation directory, you can manually create a symbolic link to /opt/rh/jws6/root/usr/share/tomcat on each target host. 3.3. Ensuring that a JDK is installed on the target hosts JBoss Web Server requires that a Java Development Kit (JDK) is already installed as a prerequisite on your target hosts to ensure that JBoss Web Server operates successfully. A JDK includes a Java Runtime Environment (JRE) and Java Virtual Machine (JVM), which must be available on any host where you want to run JBoss Web Server. For a full list of JDK versions that JBoss Web Server supports, see JBoss Web Server 6 Supported Configurations . By default, the JBoss Web Server collection does not install a JDK automatically, based on the assumption that you have already installed a supported JDK on the target hosts. However, for the sake of convenience, you can configure the JBoss Web Server collection to install a supported version of Red Hat build of OpenJDK automatically on each target host. Consider the following guidelines for installing a JDK when you use the JBoss Web Server collection: If you want to install a supported version of Red Hat build of OpenJDK on your target hosts, you can set the jws_java_version variable to the appropriate JDK version (for example, 11 or 17 ). The JBoss Web Server collection automatically installs the specified Red Hat build of OpenJDK version on each target host when you subsequently run the playbook. If you want to install a supported version of IBM JDK or Oracle JDK, you must install the JDK manually on each target host or you can automate this process by using your own playbook. For more information about manually installing a version of IBM JDK or Oracle JDK, see the Red Hat JBoss Web Server Installation Guide . In this situation, you do not need to set a variable. If you already have a supported JDK installed on your target hosts, you do not need to set a variable. Note Use the following procedure if you want to enable the JBoss Web Server collection to install Red Hat build of OpenJDK on target hosts where a supported JDK is not already installed. Prerequisites You have installed the JBoss Web Server collection . Procedure On your Ansible control node, open the vars.yml file. Set the jws_java_version variable to the appropriate OpenJDK version that you want to install. For example: Based on the preceding example, the JBoss Web Server collection automatically installs Red Hat build of OpenJDK 11 on each target host when you run the playbook. Note Alternatively, if you want the JBoss Web Server collection to install Red Hat build of OpenJDK version 17, set the jws_java_version variable to 17 . Save your changes to the vars.yml file. 3.4. Ensuring that a product user and group are created on the target hosts JBoss Web Server requires that a product user account and user group are already created as a prerequisite on your target hosts. By default, the JBoss Web Server collection handles this requirement by creating a tomcat user account and a tomcat group automatically on each target host. However, if you want the JBoss Web Server collection to create a different user account and group, you can modify the behavior of the JBoss Web Server collection to match your setup requirements. The product user account is also assigned ownership of the Tomcat directories to run the Tomcat service. Note Use the following procedure if you want to enable the JBoss Web Server collection to create a different user account and group rather than the tomcat default values. Prerequisites You have installed the JBoss Web Server collection . Procedure On your Ansible control node, open the vars.yml file. Set the jws_user and jws_group variables to the appropriate product user name and group name that you want to create. For example: Based on the preceding example, the JBoss Web Server collection automatically creates a myuser user account and group instead of creating the default tomcat user account and group. Save your changes to the vars.yml file. 3.5. Enabling the automated integration of JBoss Web Server with systemd You can optionally enable the JBoss Web Server collection to set up JBoss Web Server as a service that a system daemon can manage. By default, the JBoss Web Server collection is not configured to integrate JBoss Web Server with a system daemon. If you enable this feature, the JBoss Web Server collection sets up JBoss Web Server as a jws6‐tomcat service automatically on each target host. However, if you want to use a different service name, you can modify the behavior of the JBoss Web Server collection to match your setup requirements. When you integrate JBoss Web Server with a system daemon, the system daemon can automatically start the JBoss Web Server services at system startup. The system daemon also provides functions to start, stop, and check the status of the product. The default system daemon is systemd . Note This configuration task is optional but recommended. Prerequisites You have installed the JBoss Web Server collection . Procedure On your Ansible control node, open the vars.yml file. To enable integration with systemd , set the jws_systemd_enabled variable to True . For example: If you want JBoss Web Server to use a service name other than jws6‐tomcat , set the jws_service_name variable to the appropriate value. For example: Based on the preceding example, the JBoss Web Server collection sets up the product as a jws service on each target host when you run the playbook. Note If you do not set the jws_service_name variable, the JBoss Web Server collection sets up the product as a jws6‐tomcat service automatically. If you did not enable the automated installation of Red Hat build of OpenJDK, also set the jws_java_home variable to specify the full path to the JDK that is installed on your target hosts. For example: Note To ensure successful integration with systemd , if you do not enable the automated installation of Red Hat build of OpenJDK, you must set the jws_java_home variable. This step is not required if you enable the automated installation of Red Hat build of OpenJDK, as described in Ensuring that a JDK is installed on the target hosts . Save your changes to the vars.yml file. 3.6. Enablement of automated JBoss Web Server configuration tasks The JBoss Web Server collection provides a comprehensive set of variables to enable the automated configuration of a JBoss Web Server installation. By default, the JBoss Web Server collection configures JBoss Web Server to listen for nonsecure HTTP connections on port 8080 . Other product features such as the following are disabled by default: Support for secure HTTPS connections Mod_cluster support for load-balancing HTTP server requests to the JBoss Web Server back end The password vault for storing sensitive data in an encrypted Java keystore To enable a wider set of product features, you can define variables to modify the behavior of the JBoss Web Server collection to match your setup requirements. Note The following subsections describe only a subset of the automated configuration updates that the JBoss Web Server collection can perform. These example updates focus on enabling support for HTTPS connections, enabling mod_cluster support, and enabling the password vault. For a full list of variables that the JBoss Web Server collection provides, refer to the information page for the jws role in Ansible automation hub . For more information about configuring and using JBoss Web Server features, refer to the Red Hat JBoss Web Server documentation page . 3.6.1. Enabling the automated configuration of HTTPS support in JBoss Web Server You can configure JBoss Web Server to support secure encrypted connections between web clients and the web server over the HTTPS protocol. Consider the following guidelines for enabling HTTPS support when you use the JBoss Web Server collection: If you want to enable HTTPS support, you must ensure that a Java keystore exists on each target host before you subsequently run the playbook. The JBoss Web Server collection does not provide or create a Java keystore automatically. In this situation, you must create a new keystore on your target hosts or copy an existing keystore file to each target host, as described in Step 1 of the following procedure. To enable HTTPS support, you can set a jws_listen_https_enabled variable to True . When you enable HTTPS support, the JBoss Web Server collection updates the server.xml file on each target host with the appropriate path and password settings for the Java keystore. By default, the JBoss Web Server collection configures these path and password settings in the server.xml file with values of /etc/ssl/keystore.jks and changeit , respectively. However, if you want to use a different keystore path or keystore password, you can modify the behavior of the JBoss Web Server collection to match your setup requirements. Prerequisites You have installed the JBoss Web Server collection . Procedure If you want to create a Java keystore, perform the following steps: Log in to the target host where you want to create the keystore. Note Ensure that a JDK is already installed and the JAVA_HOME variable is already set on the target host. To create the keystore, enter the following command: In the preceding command, replace <path_to_keystore> with the full path to the keystore file that you want to create. If you do not specify the -keystore option, the command creates the keystore file in some default location that depends on the version of the JDK you have installed. For example, if you are using Red Hat build of OpenJDK, the default location for the keystore is /etc/ssl/keystore.jks . The preceding command generates a keystore file that contains a pair of public and private keys and a single self-signed certificate for server authentication. The key pair and self-signed certificate are stored in a single keystore entry that is identified by the -alias option (for example, tomcat ). When the keytool command prompts you for the following information, enter the appropriate values for your setup: Keystore password (by default, changeit ) General information about the certificate Key password for the certificate (by default, the keystore password) Note Alternatively, rather than create a new keystore, you can use the Linux scp command to copy an existing keystore file between different hosts. To enable support for HTTPS connections, perform the following steps: On your Ansible control node , open the vars.yml file. Set the jws_listen_https_enabled variable to True . For example: If the Java keystore on each target host is located in a path other than /etc/ssl/keystore.jks , set the jws_listen_https_keystore_file variable to the appropriate value. For example: In the preceding example, replace <keystore_path> with the full path to the keystore file that is on each target host. Note If you do not set the jws_listen_https_keystore_file variable, the JBoss Web Server collection automatically configures the certificateKeystoreFile setting in the server.xml file with a value of /etc/ssl/keystore.jks . If the Java keystore on each target host uses a password other than changeit , set the jws_listen_https_keystore_password variable to the appropriate value. For example: In the preceding example, replace <keystore_password> with the correct password for the Java keystore that is on each target host. Note If you do not set the jws_listen_https_keystore_password variable, the JBoss Web Server collection automatically configures the certificateKeystorePassword setting in the server.xml with a value of changeit . Save your changes to the vars.yml file. 3.6.2. Enabling the automated configuration of mod_cluster support in JBoss Web Server The mod_cluster connector is a reduced-configuration and intelligent solution for load-balancing Apache HTTP Server requests to the JBoss Web Server back end. The mod_cluster connector also provides features such as real-time load-balancing calculations, application life-cycle control, automatic proxy discovery, and multiple protocol support. To enable mod_cluster support, you can define variables to enable the mod_cluster listener and specify IP address and port values for the mod_cluster instance. Prerequisites You have installed the JBoss Web Server collection . Procedure On your Ansible control node, open the vars.yml file. To enable the mod_cluster listener, set the jws_modcluster_enabled variable to True . For example: To specify the IP address and port of the mod_cluster instance, set the jws_modcluster_ip and jws_modcluster_port variables to the appropriate values. The default IP address is 127.0.0.1 . The default port is 6666 . For example: In the preceding example, replace <ip_address> with the appropriate bind address for the mod_cluster instance on the target host, and replace <port> with the appropriate port that the mod_cluster instance uses to listen for incoming requests. Save your changes to the vars.yml file. For more information about using mod_cluster , see the HTTP Connectors and Load Balancing Guide . 3.6.3. Enabling the automated configuration of the password vault in JBoss Web Server You can use the password vault for JBoss Web Server to mask passwords and other sensitive strings, and to store sensitive information in an encrypted Java keystore. When you use the password vault, you can stop storing clear-text passwords in your JBoss Web Server configuration files. JBoss Web Server can use the password vault to search for passwords and other sensitive strings from a keystore. To enable password vault, you can set a series of variables that enable you to specify various files and configuration settings that the password vault uses. Prerequisites You have installed the JBoss Web Server collection . You have created the required vault.keystore , VAULT.dat , and vault.properties files. For more information about creating these files, refer to the Red Hat JBoss Web Server Installation Guide . Procedure On your Ansible control node, open the vars.yml file. To specify the paths to the vault.keystore , VAULT.dat , and vault.properties files that you created as part of the prerequisite step, set the following variables to the appropriate values. For example: In the preceding example, ensure that you specify the correct paths that you configured as part of the prerequisite step. To enable the password vault feature, set the jws_tomcat_vault_enabled variable to True . For example: To specify the keystore alias, keystore password, iteration count, and salt values that you configured for the password vault, set the following variables to the appropriate values. For example: In the preceding example, ensure that you specify the appropriate values that you configured as part of the prerequisite step. Save your changes to the vars.yml file. For more information about using the password vault, refer to the Red Hat JBoss Web Server Installation Guide . 3.6.4. SELinux policies for JBoss Web Server You can use Security-Enhanced Linux (SELinux) policies to define access controls for JBoss Web Server. These policies are a set of rules that determine access rights to the product. The SELinux policies feature is enabled by default. When JBoss Web Server is being installed from archive files, the SELinux policies feature requires that the native archive file for the specified product version is also installed. By default, the JBoss Web Server collection is configured to install the native archive file that matches the operating system version on your target hosts. 3.7. Enabling the automated deployment of JBoss Web Server applications on your target hosts You can also automate the deployment of web applications on your target JBoss Web Server hosts by adding customized tasks to the playbook. This requires that you place the application .war file in the appropriate directory. If you want to deploy a new or updated application when JBoss Web Server is already running, the JBoss Web Server collection provides a handler to restart the web server when the application is deployed. Note The following procedure assumes that you have created a custom playbook. Prerequisites You have installed the JBoss Web Server collection . You are familar with general Ansible concepts and creating Ansible playbooks. For more information, see the Ansible documentation . Procedure On your Ansible control node, open your custom playbook. In the tasks: section of the playbook, add a task to deploy the appropriate web application. For example: In the preceding example, replace <url_path> and <app_name> with the correct path and .war file name for the application that you want to deploy. Save your changes to the playbook. Additional resources Files modules Net Tools modules

Commands:
[...] jws_version: 6.0.0
[...] rhn_username: <client_ID> rhn_password: <client_secret>
[...] zipfile_name: <application_server_file> jws_native_zipfile: <native_file>
[...] jws_version: 6.0.0 [...] jws_apply_patches: True
[...] jws_apply_patches: True jws_patch_version: 6.0.2
[...] rhn_username: <client_ID> rhn_password: <client_secret>
[...] jws_offline_install: True
[...] jws_version: 6.0.0
[...] jws_install_method: rpm
[...] jws_java_version: 11
[...] jws_user: myuser jws_group: myuser
[...] jws_systemd_enabled: True
[...] jws_service_name: jws
[...] jws_java_home: <JAVA_HOME path>
USDJAVA_HOME/bin/keytool -genkeypair -alias tomcat -keyalg RSA -keystore <path_to_keystore>
[...] jws_listen_https_enabled: True
[...] jws_listen_https_keystore_file: <keystore_path>
[...] jws_listen_https_keystore_password: <keystore_password>
[...] jws_modcluster_enabled: True
[...] jws_modcluster_ip: <ip_address> jws_modcluster_port: <port>
[...] jws_vault_name: ./vault_files/vault.keystore jws_vault_data: ./vault_files/VAULT.dat jws_vault_properties: ./vault_files/vault.properties
[...] jws_tomcat_vault_enabled: True
[...] jws_tomcat_vault_alias: <keystore_alias> jws_tomcat_vault_storepass: <keystore_password> jws_tomcat_vault_iteration: <iteration_count> jws_tomcat_vault_salt: <salt>
[...] tasks: [...] - name: "Deploy demo webapp" ansible.builtin.get_url: url: 'https:// <url_path> / <app_name> .war' dest: "{{ jws_home }}/webapps/ <app_name> .war" [...]