Copyright © Cloud Software Group, Inc. All Rights Reserved


Chapter 5 Statistics and Variables : Runtime Context Variables

Runtime Context Variables
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 frequency in seconds. Default frequency of 30 seconds will be used if a value less than 30 is specified.
Comma separated list of context URLs to be ignored by archive detection mechanism.
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.
Client key store file for connecting to the JBoss MBean server when TWO_WAY_SSL_ENABLED is true
Client key store password for connecting to the JBoss MBean server when TWO_WAY_SSL_ENABLED is true
Client trust store password used when connecting to the JBoss MBean server
Port for multicast socket on which HA-JNDI listens for auto-discovery requests from clients
Hostname for multicast socket on which HA-JNDI listens for auto-discovery requests from clients
HSQLDB_DS_XML_hypersonic_socket_PORT (JBoss EAP 5.0 only)
Initial context factory to create the JMX connection; must support JNDI access over HTTP
JBOSSMQ_SERVICE_XML_InvocationLayer_PORT (JBoss EAP 5.0 only)
JBOSS_JGROUPS_UDP_BIND_PORT (JBoss EAP 5.1.1 only)
Socket Naming service uses to receive RMI requests from client proxies
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.
REMOTING_BISOCKET_SERVICE_XML_messaging_2x_netty-port
REMOTING_BISOCKET_SERVICE_XML_messaging_2x_netty-ssl-port
TRANSACTION_JBOSS_BEANS_XML_transactionStatusManager_PORT
Colon-separated list of package prefixes to use when loading in URL context factories. Change only if you are an advanced user and you know what you are doing
Whether or not to verify successful deployment of J2EE archives. This must be set to true for archive ordering.
The following variables are also available 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 frequency in seconds. Default frequency of 30 seconds will be used if a value less than 30 is specified.
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.
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
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