mafriedel

Have you tried something like this: wildfly::jgroups::stack::tcpping { 'TCPPING': initial_hosts => '192.168.56.101[7600],192.168.56.103[7600]', num_initial_members => 2 } It works in EAP7 (not sure what wildfly version that is the equivalent to),...

I got it working the way you did. Thank you.

Without a Vault being defined the read-attribute results in: [[email protected]:9993 /] /core-service=management/ldap-connection=ad_ldap_connection:read-attribute(name=search-credential) { "outcome" => "success", "result" => "bRarm8e0/)R1[eW" }

Gave up on the wildfly::datasources::datasource since it no longer works with EAP 7.1. Solution for others interested is below. wildfly::deployment { 'db2jcc4.jar': source => 'http://artifacts/support/db2jcc4.jar', } $parameters = [ '--name=DB2T...

Although this works like crap if you ever want to change parameters, so it's not really a solution, more of a stopgap.