Copyright © Cloud Software Group, Inc. All Rights Reserved |
The following is a comprehensive list of all runtime context variables used by the JBoss EAP Enabler.The first table contains JBoss EAP 5.0 and 5.1 runtime context variables, while the second contains variables for JBoss EAP 6.0:
The amount of time in seconds to allow for each archive deployment to finish in standalone mode. Only valid if VERIFY_ARCHIVE_DEPLOYMENT_SUCCESS is true. Archive detection will be enabled if this variable is set to true. Archive detection frequency in seconds. Default frequency of 30 seconds will be used if a value less than 30 is specified. Set to true to have JBoss bind to all available local IP addresses. Directories/files excluded from capture. Generally useful to exclude are log file directories, tmp directories, etc. Directories that need to be captured. Generally these directories contain configuration, applications, etc. The bind address for the management interface. This can optionally be set to 0.0.0.0 to bind to all local addresses, or to ${JBOSS_BIND_ADDRESS} to use the same address as the public interface, as specified by ${LISTEN_ADDRESS_NET_MASK}. Note that doing so will allow the management interface to be accessible from other network locations, which may entail a security risk. Unique name for the JBoss node, used when clustering is enabled. A comma delimited list of net masks in CIDR notation. The first IP address found that matches one of the net masks is used as the listen address. Private key entry’s alias in the server key store, see JBoss bug JBPAPP6-789 Server key store file location for incoming SSL connections Server trust store file location for outgoing SSL connections How often in milliseconds to check if the server has started Whether or not to verify successful deployment of J2EE archives. This must be set to true for archive ordering.
Copyright © Cloud Software Group, Inc. All Rights Reserved |