Appendix A. Reference information for getting started with JBoss EAP
You can use the arguments, attributes, and default socket binding to help you get started with using JBoss EAP. For example, you can use arguments to set an alternative configuration to a default JBoss EAP standalone server. This helps configure the server to meet your needs.
A.1. Server runtime arguments and switches
On standalone servers and servers in a managed domain, you can use specific server runtime arguments with an application’s startup script. The script can start a server with alternative configurations to those defined in the standalone.xml
, domain.xml
, and host.xml
configuration files. Alternative configurations might include starting the server with an alternative socket bindings set or a secondary configuration.
Before you start the server, you can access the available parameters list by issuing the help switch, -h
or --help
, in your terminal.
Argument or switch | Server type | Description |
---|---|---|
| Standalone |
Sets the server’s running type to |
| Domain |
Sets the host controller’s running type to |
| Standalone, Domain |
Sets system property |
| Standalone, Domain |
Sets system property |
| Domain | Keep a copy of the persistent domain configuration even if this host is not the domain controller. |
| Standalone |
Name of the server configuration file to use. The default is |
| Domain |
Name of the server configuration file to use. The default is |
| Domain | If the host is not the domain controller and cannot contact the domain controller at boot, then you must boot by using a locally cached copy of the domain configuration. |
| Standalone | Activate debug mode with an optional argument to specify the port. Argument only works if the launch script supports the argument. |
| Standalone, Domain | Sets a system property. |
| Domain |
Name of the server configuration file to use. Defaults as |
| Standalone |
The location of the Git repository that is used to manage and persist server configuration data. This can be |
| Standalone | The branch or tag name in the Git repository to use. You must name an existing branch or tag name as it will not be created if it does not exist. If you use a tag name, you put the repository in a detached HEAD state, meaning future commits are not attached to any branches. Tag names are read-only and are normally used when you need to replicate a configuration across several nodes. |
| Standalone |
The URL to an Elytron configuration file that contains the credentials the server uses when it connects to a remote Git repository. You can use the argument when your remote Git repository requires authentication. Elytron does not support SSH. Elytron supports only default SSH authentication by using private keys without a password. You cannot use the argument with a |
| Standalone, Domain | Display the help message and exit the help index. |
| Domain |
Name of the host configuration file to use. Defaults as |
| Domain | Address on which the host controller can listen for communication from the process controller. |
| Domain | Port on which the host controller can listen for communication from the process controller. |
| Domain |
Sets system property |
| Domain |
Sets system property |
| Standalone |
Name of the server configuration file to use. Argument differs from |
| Domain |
Name of the domain configuration file to use. Argument differs from |
| Domain |
Name of the host configuration file to use. Argument differs from |
| Standalone, Domain | Load system properties from the given URL. |
| Domain | Address on which the process controller listens for communication from processes it controls. |
| Domain | Port on which the process controller listens for communication from processes it controls. |
| Standalone | Sets a security property. |
| Standalone, Domain | Runs the server with a security manager installed. |
| Standalone |
Name of the server configuration file to use. Defaults as |
| Standalone |
Sets the start mode of the server. You cannot use the argument with the
|
| Standalone, Domain |
Sets system property |
| Standalone, Domain | Display the application server version and exit. |
JBoss EAP sets its included configuration files to handle the behavior of the switches. For example, -b
and -u
. If you change your configuration files to no longer use the system property controlled by the switch then adding the system property to the start command does not work.
A.2. Add-user arguments
You can use arguments with the add-user.sh
script or the add-user.bat
script to configure how these scripts add new users to a properties file for authentication purposes.
Command line argument | Description |
---|---|
| Creates a user in the application realm. If you do not create a user in the application realm then the script creates a user in the management realm by default. |
|
The domain configuration directory that contains the properties files. If you omit the argument then the script sets |
|
An alternative standalone server configuration directory that contains properties files. If you omit the argument then the script sets |
|
The name of the alternative user properties file. You can set an absolute path for the file or specify a file name by using the argument with an |
| A comma-separated list of groups to assign to a user. |
|
The name of the alternative group properties file. You can set an absolute path for the file or specify a file name by using the argument with an |
| The password of the user. |
| The name of the user. User names can only contain the following characters, in any number and in any order:
|
|
The name of the realm used to secure the management interfaces. If omitted, the default is |
|
Run the |
| Enable the user. |
| Disable the user. |
| Automatically confirm warning in interactive mode. |
|
Display usage information for the |
| Print the secret value in non-interactive mode. |
A.3. Interface attributes
You can use interface attributes to configure a JBoss EAP interface.
Attribute names in the table display in the order JBoss EAP lists them in its management model. See the schema definition file located at EAP_HOME/docs/schema/wildfly-config_5_0.xsd
to view the elements as they appear in the XML. XML element listings must differ from those displayed in the management model.
Interface attribute | Description |
---|---|
| Specifies that an interface must meet at least one, but not necessarily all, of the selected nested set of criteria. |
| Empty attribute that binds a wildcard address to sockets that use an interface. The attribute has the following configuration options:
|
| Specifies either an IP address in IPv6 or IPv4 dotted decimal notation or a host name resolved to an IP address. |
| Empty attribute that specifies criteria for whether or not an interface includes a link-local address. |
| Empty attribute that specifies criteria for whether or not an interface identifies as a loopback interface. |
|
A loopback address that might not have been configured on the machine’s loopback interface. Attribute differs from |
| Empty attribute that specifies criteria for whether or not an interface supports multicast. |
| The name of the interface. |
|
The name of a network interface, such as |
| A regular expression that matches the names of the network interfaces available on a machine to an acceptable interface. |
| Attribute that indicates the selection criteria that an interface must not meet. |
| Empty attribute that specifies criteria for whether or not an interface identifies as a point-to-point interface. |
| Empty attribute that specifies criteria for whether or not an interface contains a publicly routable address. |
| Empty attribute that specifies criteria for whether or not an interface contains a site-local address. |
|
Specifies a network IP address and the number of bits in the address' network prefix, which is written in slash notation ,such as |
| Empty attribute that specifies criteria for whether or not an interface locates as up. |
| Empty attribute that specifies criteria for whether or not an interface contains identifies as a virtual interface. |
A.4. Socket binding attributes
You can use socket binding attributes to configure the socket binding for your JBoss EAP server.
Specific attributes exist for the following types of socket bindings:
- Inbound socket bindings
- Remote outbound socket bindings
- Local outbound socket bindings
Attribute names in the table display in the order JBoss EAP lists them in its management model. See the schema definition file located at EAP_HOME/docs/schema/wildfly-config_5_0.xsd
to view the elements as they appear in the XML. XML element listings must differ from those displayed in the management model.
Attribute | Description |
---|---|
|
Specifies the client mappings for an inbound socket binding. A client that connects to an inbound socket must use the destination address specified in the mapping. This address matches the outbound interface. By using the |
| Use the attribute to determine if the port value must remain fixed. You can use the attribute even if you applied numeric offsets to the other sockets in the socket group. |
|
An attribute that sets the name of the interface to which the socket binds. You can also use the attribute to set the interface that multicast sockets must listen. If you do not define a declared interface, then the attribute uses the |
| Multicast address on which the socket receives multicast traffic. If you do not specify a value for the attribute, then you do not configure the socket to receive multicast functionality. |
|
Port on which the socket receives multicast traffic. You must configure the attribute if you configured the |
| You must set a name of the socket. A service requiring access to the socket configuration information cannot use the name to find the socket. |
|
Number of the port to which the socket binds. You must override the attribute value if you configured servers to apply a |
Attribute | Description |
---|---|
| Determines whether the port value must remain fixed, even if you applied numeric offsets to the other outbound sockets in a socket group. |
| The host name or IP address of the remote destination to which an outbound socket connects. |
| The port number of the remote destination to which an outbound socket connects. |
| The name of the interface that JBoss EAP uses for the source address of the outbound socket. |
| The port number that JBoss EAP uses as the source port of the outbound socket. |
Attribute | Description |
---|---|
| Determines whether the port value must remain fixed, even if you applied numeric offsets to the other outbound sockets in the socket group. |
| The name of the local socket binding that JBoss EAP uses to determine the port for the connecting outbound socket. |
| The name of the interface that JBoss EAP uses for the source address of the outbound socket. |
| The port number that JBoss EAP uses as the source port of the outbound socket. |
A.5. Default socket bindings
You can set default socket bindings for each socket binding group.
The following five types of default socket bindings exist for JBoss EAP:
-
standard-sockets
-
ha-sockets
-
full-sockets
-
full-ha-sockets
-
load-balancer-sockets
Socket Binding | Port | Description |
---|---|---|
|
| Apache JServ Protocol. Used for HTTP clustering and load balancing. |
|
| The default port for deployed web applications. |
|
| SSL-encrypted connection between deployed web applications and clients. |
|
| Used for HTTP communication with the management layer. |
|
| Used for HTTPS communication with the management layer. |
|
| The JTA transaction recovery manager. |
|
| The JTA / JTS transaction manager. |
Socket Binding | Port | Multicast Port | Description |
---|---|---|---|
|
| Apache JServ Protocol. Used for HTTP clustering and load balancing. | |
|
| The default port for deployed web applications. | |
|
| SSL-encrypted connection between deployed web applications and clients. | |
|
| Multicast. Used to discover initial membership in a HA cluster. | |
|
| Unicast peer discovery in HA clusters using TCP. | |
|
|
| Multicast peer discovery in HA clusters using UDP. |
|
| Used for HTTP communication with the management layer. | |
|
| Used for HTTPS communication with the management layer. | |
|
| Multicast port for communication between JBoss EAP and the HTTP load balancer. | |
|
| The JTA transaction recovery manager. | |
|
| The JTA / JTS transaction manager. |
Socket Binding | Port | Description |
---|---|---|
|
| Apache JServ Protocol. Used for HTTP clustering and load balancing. |
|
| The default port for deployed web applications. |
|
| SSL-encrypted connection between deployed web applications and clients. |
|
| CORBA services for JTS transactions and other ORB-dependent services. |
|
| SSL-encrypted CORBA services. |
|
| Used for HTTP communication with the management layer. |
|
| Used for HTTPS communication with the management layer. |
|
| The JTA transaction recovery manager. |
|
| The JTA / JTS transaction manager. |
Name | Port | Multicast Port | Description |
---|---|---|---|
|
| Apache JServ Protocol. Used for HTTP clustering and load balancing. | |
|
| The default port for deployed web applications. | |
|
| SSL-encrypted connection between deployed web applications and clients. | |
|
| CORBA services for JTS transactions and other ORB-dependent services. | |
|
| SSL-encrypted CORBA services. | |
|
| Multicast. Used to discover initial membership in a HA cluster. | |
|
| Unicast peer discovery in HA clusters using TCP. | |
|
|
| Multicast peer discovery in HA clusters using UDP. |
|
| Used for HTTP communication with the management layer. | |
|
| Used for HTTPS communication with the management layer. | |
|
| Multicast port for communication between JBoss EAP and the HTTP load balancer. | |
|
| The JTA transaction recovery manager. | |
|
| The JTA / JTS transaction manager. |
Name | Port | Multicast Port | Description |
---|---|---|---|
|
| The default port for deployed web applications. | |
|
| SSL-encrypted connection between deployed web applications and clients. | |
|
| Used for HTTP communication with the management layer. | |
|
| Used for HTTPS communication with the management layer. | |
|
| The port for the Mod-Cluster Management Protocol (MCMP) connection to transmit lifecycle events. | |
|
| Multicast port for communication between JBoss EAP and the HTTP load balancer. |
Revised on 2022-12-16 12:18:13 UTC