jaketux8 / jboss_eap

Ansible role to install JBoss EAP

Ansible JBoss EAP Role

A role to install JBoss Enterprise Application Platform on RHEL7. Intended to be used with JBoss Middleware Playbooks

Transfer Method

This role supports a few different mechanism for transferring the product zip files to the target host. These are documented on the main playbooks README, as the methods are supported across a variety of roles.

Dependencies

• java
• unzip

Our playbooks provide these dependencies in a common role, but this there is no explicitly ansible dependency to allow end users more options.

JBoss Instance Customization

JBoss instances can be customized on a per host/group basis by modifying the jboss_instance property. By default, a single standalone instance is deployed with HTTP and Management interfaces exposed to all interfaces.

jboss_instances:
  - name: standalone

There are several ways in which you can customize the JBoss instances as described below.

• Create a single instance called standalone which does not publicly expose the Management interface

jboss_instances:
  - name: standalone
    bind_management_address: 127.0.0.1

• Create multiple instances on the same machine with a port offset of 100

jboss_instances:
  - name: node1
  - name: node2
    port_offset: 100

Example Playbooks

• JBoss EAP 7.1 on RHEL 7

License

LICENSE

Authors Information

• Andrew Block
• Albert Wong
• Justin Holmes
• Kamesh Sampath