Standalone JBoss Deployment

• Requires Ansible 1.2 or newer
• Expects CentOS/RHEL 6 or 7 hosts

These playbooks deploy a very basic implementation of JBoss Application Server, version 7. To use them, first edit the hosts inventory file to contain the hostnames of the machines on which you want JBoss deployed, and edit the group_vars/all file to set any JBoss configuration parameters you need.

Then run the playbook, like this:

ansible-playbook -i hosts site.yml

When the playbook run completes, you should be able to see the JBoss Application Server running on the ports you chose, on the target machines.

This is a very simple playbook and could serve as a starting point for more complex JBoss-based projects.

Application deployment

The playbook deploy-application.yml may be used to deploy the HelloWorld and Ticket Monster demo applications to JBoss hosts that have been deployed using site.yml, as above.

Run the playbook using:

ansible-playbook -i hosts deploy-application.yml

The HelloWorld application will be available at http://<jboss server>:<http_port>/helloworld

The Ticket Monster application will be available at http://<jboss server>:<http_port>/ticket-monster

Provisioning for Amazon Web Services

A simple playbook is provided, as an example, to provision hosts in preparation for running this JBoss deployment example.

ansible-playbook -i hosts demo-aws-launch.yml

Ideas for Improvement

Here are some ideas for ways that these playbooks could be extended:

• Write a playbook or an Ansible module to configure JBoss users.
• Extend this configuration to multiple application servers fronted by a load balancer or other web server frontend.

We would love to see contributions and improvements, so please fork this repository on GitHub and send us your changes via pull requests.