middleware_automation.jcliff.jcliff module – Manages the configuration of Wildfly / JBoss EAP servers
Note
This module is part of the middleware_automation.jcliff collection (version 0.0.23).
To install it, use: ansible-galaxy collection install middleware_automation.jcliff
.
To use it in a playbook, specify: middleware_automation.jcliff.jcliff
.
Synopsis
Wraps the JCliff Java utility tool in order to support fine grained tuning of Wildfly / JBoss EAP server configuration in Ansible.
Note
This module has a corresponding action plugin.
Parameters
Parameter |
Comments |
---|---|
Wildfly or JBoss EAP Subsystems or configuration component |
|
Datasource configurations. |
|
Datasource SQL query for checking a valid connection. Default: “undefined” |
|
Connection URL. |
|
Name of the driver. |
|
Whether the datasource is enabled. Default: “true” |
|
Datasource idle timeout minutes. Default: “undefined” |
|
JNDI name. |
|
Datasource maximum pool size. Default: “undefined” |
|
Datasource minimum pool size. Default: “undefined” |
|
Datasource name. |
|
Datasource password. |
|
Name of the datasource pool. |
|
Datasource query timeout. Default: “undefined” |
|
Use the Java context. Default: “true” |
|
Datasource user name. |
|
Datasource validate on match. Default: “undefined” |
|
Deployments. |
|
Adds to the repository in a disabled state. Choices:
|
|
Name of the deployment. |
|
Path to the deployment. |
|
Regex pattern to replace the deployment if the value matches the name. |
|
Regex pattern to replace the deployment if the value matches the runtime name. |
|
Runtime of the deployment. |
|
Specifies whether the deployment should be managed. Choices:
|
|
JDBC driver configurations. |
|
Driver class name. Default: “undefined” |
|
Class name for the datasource. Default: “undefined” |
|
Name of the driver module. |
|
Name of the driver. |
|
Class name for the XA datasource. Default: “undefined” |
|
Name of the module slot. Default: “undefined” |
|
Interface. |
|
Sockets using this interface should be bound to a wildcard address Choices:
|
|
Whether or not the address matches the given value |
|
Part of the selection criteria for choosing an IP address for this interface should be whether or not the address is link-local Choices:
|
|
Part of the selection criteria for choosing an IP address for this interface should be whether or not it is a loopback address Choices:
|
|
Value indicating that the IP address for this interface should be the given value, if a loopback interface exists on the machine |
|
Whether or not its network interface supports multicast Choices:
|
|
Name of the interface |
|
Part of the selection criteria for choosing an IP address for this interface should be whether its network interface has the given name |
|
Whether its network interface has a name that matches the given regular expression |
|
Whether or not its network interface is a point-to-point interface Choices:
|
|
Whether or not it is a publicly routable address Choices:
|
|
The resolved ip address for this interface |
|
Whether or it is a site-local address Choices:
|
|
Whether or it the address fits in the given subnet definition. Value is a network IP address and the number of bits in the address |
|
Whether its network interface is currently up Choices:
|
|
Whether its network interface is a virtual interface Choices:
|
|
Keycloak. |
|
List of applications to secure using Keycloak. |
|
Base URL of the Keycloak server. |
|
The secure value for the application. If not provided, it is setup as a public client. |
|
Name of the deployment. |
|
Should only be used during development and NEVER in production as it will disable verification of SSL certificates. Default false. Choices:
|
|
Name of the Keycloak realm. |
|
The client-id of the application. |
|
Ensures that communication to and from the Keycloak server is over HTTPS. Default external. Possible values all external none. |
|
Whether the adapter will look inside the token for application level role mappings for the user. The default value is false. Choices:
|
|
Whether the adapter will verify whether the token contains this client name (resource) as an audience. Default is false. Choices:
|
|
logger. |
|
Replace level with log level that is to be set |
|
Replace name with name of the log category |
|
mail. |
|
Replace from_email with email id. |
|
Set jndi_name, for ex. java:jboss/mail/testSession |
|
Replace name with subject. |
|
Set outbound_socket_binding_ref, for ex. mail-smtp |
|
Set ssl Choices:
|
|
Create messaging activemq. |
|
Configure address setting |
|
Sets the dead-letter-address. |
|
Sets the expiry-address. |
|
Sets max number of delivery attempts. |
|
Enter the details of address setting. |
|
Sets the redelivery-delay. |
|
Configure bridge |
|
discovery group |
|
Logical name of the bridge |
|
queue name |
|
static connectors |
|
Configure connection factory. |
|
Legacy entries |
|
discovery group |
|
Enter the required entries |
|
Logical name of the connection factory |
|
Configure connector. |
|
factory class |
|
Logical name of the connector. |
|
Configure in vm acceptor |
|
Enter the details of in vm acceptor. |
|
Enter the details of server id. |
|
Create JMS queue |
|
Enter if it is durable or not. |
|
Enter the required entries. |
|
headers |
|
Legacy entries |
|
Logical name of the jms queue |
|
seclecor |
|
Configure jms topic. |
|
Enter the required entries. |
|
headers |
|
Legacy entries |
|
Logical name of the jms topic. |
|
Configure pooled connection factory |
|
Enter the details of connector. |
|
Enter the details of discovery. |
|
Enter entries. |
|
Enter the details of pooled connection factory. |
|
Configure remote acceptor |
|
Enter the details of remote acceptor. |
|
Configure remote connector |
|
Enter the details of remote acceptor. |
|
Enter the details of socket binding. |
|
Configure security setting |
|
Consume |
|
create_durable_queue |
|
create_non_durable_queue |
|
delete_durable_queue |
|
delete_non_durable_queue |
|
manage |
|
Logical name of the bridge |
|
enter details to send |
|
Creates and sets messaging-activemq server properties. |
|
Name of property. |
|
Value of property. |
|
Manage Modcluster. |
|
Modcluster proxy. |
|
Whether to enable multicast-based advertise mechanism. Choices:
|
|
If specified, reverse proxy advertisements checksums will be verified using this value as a salt. |
|
Name of socket binding to use for the advertise socket. |
|
If false, the contexts are registered with the reverse proxy as disabled. Choices:
|
|
The name of the balancer on the reverse proxy to register with. |
|
List of contexts to exclude from registration with the reverse proxies. |
|
Whether to enable packet flushing on the reverse proxy. Choices:
|
|
Time to wait before flushing packets on the reverse proxy. |
|
The name of Undertow listener that will be registered with the reverse proxy. |
|
Name of the load balancing group this node belongs to. |
|
Maximum number of failover attempts by reverse proxy when sending the request to the backend server. |
|
Logical name of the modcluster proxy. |
|
Timeout (in seconds) for proxy connections to a node. Time mod_cluster will wait for the back-end response before returning an error. |
|
Number of seconds for which to wait for a pong answer to a ping. |
|
List of reverse proxies for mod_cluster to register with defined by ‘outbound-socket-binding’ in ‘socket-binding-group’. |
|
List of reverse proxies to register with. Format (hostname:port) separated with commas. |
|
Base URL for MCMP requests. |
|
Session draining strategy used during undeployment of a web application. |
|
Simple load provider returns constant pre-configured load balancing factor. |
|
Soft maximum idle connection count for reverse proxy. |
|
Timeout to wait for the reverse proxy to answer a MCMP message. |
|
Reference to the SSLContext to be used by mod_cluster. |
|
Number of seconds a STATUS message is sent from the application server to the proxy. |
|
Indicates whether subsequent requests for a given session should be routed to the same node, if possible. Choices:
|
|
Whether the reverse proxy should run an error in the event that the balancer is unable to route a request to the node to which it is stuck. Choices:
|
|
Whether the reverse proxy should remove session stickiness when the balancer is unable to route a request to the node to which it is stuck. Choices:
|
|
Maximum time to wait for context to process pending requests. |
|
Time to live (in seconds) for idle connections above smax. |
|
Number of seconds to wait for a worker to become available to handle a request. |
|
The deployment scanner is only used in standalone mode. It can be found in standalone.xml. |
|
The name of the scanner. It can be path, relative-to, scan-enabled, scan-interval, auto-deploy-zipped, auto-deploy-exploded, auto-deploy-xml, deployment-timeout |
|
enter the respective value, corresponding to name. https://docs.jboss.org/infinispan/9.4/serverconfigdocs/jboss-as-deployment-scanner_2_0.html |
|
Create Socket bindings. |
|
Remote destination outbound socket binding. |
|
Whether the port value should remain fixed even if numeric offsets are applied to the other outbound sockets in the socket group. Choices:
|
|
The host name or the IP address of the remote destination to which this outbound socket will connect. |
|
Logical name of the remote destination outbound socket configuration that should be used elsewhere in the configuration. |
|
The port number of the remote destination to which the outbound socket should connect. |
|
The name of the interface which will be used for the source address of the outbound socket. |
|
The port number which will be used as the source port of the outbound socket. |
|
Socket bindings. |
|
Logical name of the interface to which a socket based on this configuration should be bound. |
|
If the socket will be used for multicast, the multicast address to use. |
|
If the socket will be used for multicast, the multicast port to use. |
|
Logical name of the socket configuration that should be used elsewhere in the configuration. |
|
Base port to which a socket based on this configuration should be bound. |
|
System properties. |
|
System property name. |
|
System property value. |
|
Setting node-identifier |
|
Node-identifier |
|
enter the respective value, corresponding to name. |
|
Undertow configuration |
|
Configuration |
|
The type of filter to use |
|
List of servers to setup using Undertow |
|
List of hosts for this server |
|
Reference to the filtertype |
|
Gzip filter |
|
Predicate describing relevant requests for filtering |
|
Server name. |
|
Server name. |
|
XA Datasource configurations. |
|
Specifies that connections are validated on a background thread, rather than being validated prior to use. Mutually exclusive to validate-on-match. Choices:
|
|
The background-validation-millis element specifies the amount of time, in milliseconds, that background validation will run. Changing this value require a server restart. |
|
Datasource SQL query for checking a valid connection. Default: “undefined” |
|
Name of the driver. |
|
Whether the datasource is enabled. Default: “true” |
|
Which exception sorter class should be used. Default: “undefined” |
|
JNDI name. |
|
The max-pool-size element specifies the maximum number of connections for a pool. No more connections will be created in each sub-pool |
|
The min-pool-size element specifies the minimum number of connections for a pool. |
|
Datasource name. |
|
Should datasource attempt recovery. Choices:
|
|
Datasource password. |
|
Name of the datasource pool. |
|
The same-rm-override element allows one to unconditionally set whether the javax.transaction.xa.XAResource.isSameRM(XAResource) returns true or false. Choices:
|
|
Use the Java context. Default: “true” |
|
Datasource user name. |
|
An org.jboss.jca.adapters.jdbc.ValidConnectionChecker that provides a SQLException isValidConnection(Connection e) method to validate is a connection is valid. Default: “undefined” |
|
The validate-on-match element indicates whether or not connection level validation should be done when a connection factory attempts to match a managed connection for a given set. Default: “undefined” |
|
The fully qualified name of the javax.sql.XADataSource implementation |
|
Properties for XA datasource |
|
url for this datasource |
|
Debug output. Choices:
|
|
Path to the the Jcliff utility. Default: “/usr/bin/jcliff” |
|
Home directory for the Jcliff utility. Default: “/usr/share/jcliff” |
|
Location of the Java JVM. |
|
Management host. Default: “localhost” |
|
Management password. |
|
Management port. Default: “9990” |
|
Management username. |
|
Set jcliff reconnect delay Default: 30000 |
|
Location of the rules directory on the remote instance. |
|
Name of the rules file. |
|
Directory containing Jcliff rules. Default: “/usr/share/jcliff/rules” |
|
If ‘present’, configurations will be applied to the Wildfly/JBoss EAP server. If ‘absent’, configurations will be removed from the Wildfly/JBoss EAP server - this is NOT implemented yet! Choices:
|
|
Set jcliff timeout (how long a jcliff will allow a query to the server to last) Default: 30000 |
|
Home directory for the Wildfly or JBoss EAP server. |
Examples
- name: Configure Wildfly instance
jcliff:
wfly_home: "/opt/wildfly"
subsystems:
- system_properties:
- name: jcliff.enabled
value: 'enabled.plus'
- datasources:
- name: ExampleDS2
use_java_context: 'true'
jndi_name: java:jboss/datasources/ExampleDS2
connection_url: "jdbc:h2:mem:test2;DB_CLOSE_DELAY=-1;DB_CLOSE_ON_EXIT=FALSE"
driver_name: h2