Ansible playbook to install Process Automation Manager in multiple flavours.
- Check out the main playbook site.yml for the plays.
- Review the variables in groups_vars to tune the installation.
- Assign hosts to the right group in the hosts inventory file.
ansible-playbook -i hosts site.yml
- JBoss EAP, RHPAM distros and versions are kept in the role's defaults variables.
Once you have the setup up and running, you can import in Central the following project to try it out:
Start and stop the JBoss systemd service:
ansible -i ./hosts managed --become -m service -a "name=jbosseap7 state=stopped"
ansible -i ./hosts managed --become -m service -a "name=jbosseap7 state=started"
Enable DEBUG or change the log level:
ansible -i ./hosts unmanaged -m shell -a "$JBOSS_EAP_HOME/scripts/change-log-level.sh org.kie DEBUG"
ansible -i ./hosts unmanaged -m shell -a "$JBOSS_EAP_HOME/scripts/change-log-level.sh org.eclipse DEBUG"
ansible -i ./hosts central -m shell -a "$JBOSS_EAP_HOME/scripts/change-log-level.sh org.drools DEBUG"
ansible -i ./hosts central -m shell -a "$JBOSS_EAP_HOME/scripts/change-log-level.sh org.guvnor DEBUG"
ansible -i ./hosts central -m shell -a "$JBOSS_EAP_HOME/scripts/change-log-level.sh org.uberfire DEBUG"