PageRenderTime 64ms CodeModel.GetById 21ms RepoModel.GetById 0ms app.codeStats 1ms

/controller/src/main/resources/org/jboss/as/controller/descriptions/common/LocalDescriptions.properties

https://github.com/dbuos/wildfly
Properties File | 470 lines | 433 code | 23 blank | 14 comment | 0 complexity | ef3878ec2ad9cc3669ba23ccf6fec9b7 MD5 | raw file
Possible License(s): Apache-2.0

Large files files are truncated, but you can click here to view the full file

  1. # Common attributes
  2. namespaces=Map of namespaces used in the configuration XML document, where keys are namespace prefixes and values are schema URIs.
  3. namespaces.add-namespace=Adds a namespace prefix mapping to the namespaces attribute's map.
  4. namespaces.add-namespace.namespace=The prefix of the namespace to add
  5. namespaces.add-namespace.uri=The schema uri of the namespace to add.
  6. namespaces.remove-namespace=Removes a namespace prefix mapping from the namespaces attribute's map.
  7. namespaces.remove-namespace.namespace=The prefix of the namespace to remove.
  8. schema-locations=Map of locations of XML schemas used in the configuration XML document, where keys are schema URIs and values are locations where the schema can be found.
  9. schema-locations.add-schema-location=Adds a schema location mapping to the schema-locations attribute's map.
  10. schema-locations.add-schema-location.uri=The uri of the schema location to add
  11. schema-locations.add-schema-location.schema-location=The location where the added schema can be found.
  12. schema-locations.remove-schema-location=Removes a schema location mapping from the schema-locations attribute's map.
  13. schema-locations.remove-schema-location.uri=The URI of the schema location to remove.
  14. # Management
  15. core.management=The management services used to control a standalone server or a host's host controller in a management domain.
  16. core.management.security-realms=The security realms available for control access to the management services.
  17. core.management.security-realm=A security realm that can be associated with a management interface and used to control access to the management services.
  18. core.management.security-realm.add=Adds a security realm that can be associated with a management interface and used to control access to the management services.
  19. core.management.security-realm.map-groups-to-roles=After a users group membership has been loaded should a 1:1 relationship be assumed regarding group to role mapping.
  20. core.management.security-realm.remove=Removes a security realm that can be associated with a management interface and used to control access to the management services.
  21. core.management.security-realm.plug-in=An extension to the security realm allowing additional authentication / authorization modules to be loaded.
  22. core.management.security-realm.plug-in.add=Add a plug-in to the security realm.
  23. core.management.security-realm.plug-in.remove=Remove a plug-in from the security realm.
  24. core.management.security-realm.property=A property within a security realm resource.
  25. core.management.security-realm.property.add=Add a property definition.
  26. core.management.security-realm.property.remove=Remove the property definition.
  27. core.management.security-realm.property.name=The name of the property.
  28. core.management.security-realm.property.value=The optional value of the property.
  29. core.management.security-realm.server-identity=Configuration of the identities that represent the server.
  30. core.management.security-realm.server-identity.secret=Configuration of the secret/password-based identity of a server or host controller.
  31. core.management.security-realm.server-identity.secret.add=Adds a secret/password-based identity for a server or host controller.
  32. core.management.security-realm.server-identity.secret.remove=Removes a Adds a secret/password-based identity for a server or host controller.
  33. core.management.security-realm.server-identity.secret.value=The secret / password - Base64 Encoded.
  34. core.management.security-realm.server-identity.ssl=Configuration of the SSL identity of a server or host controller.
  35. core.management.security-realm.server-identity.ssl.add=Adds the SSL identity of a server or host controller.
  36. core.management.security-realm.server-identity.ssl.remove=Removes the SSL identity of a server or host controller.
  37. core.management.security-realm.server-identity.ssl.protocol=The protocol to use when creating the SSLContext.
  38. core.management.security-realm.server-identity.ssl.alias=The alias of the entry to use from the keystore.
  39. core.management.security-realm.server-identity.ssl.key-password=The password to obtain the key from the keystore.
  40. core.management.security-realm.server-identity.ssl.keystore-password=The password to open the keystore.
  41. core.management.security-realm.server-identity.ssl.keystore-path=The path of the keystore.
  42. core.management.security-realm.server-identity.ssl.keystore-relative-to=The name of another previously named path, or of one of the standard paths provided by the system. If 'relative-to' is provided, the value of the 'path' attribute is treated as relative to the path specified by this attribute.
  43. core.management.security-realm.authentication=Configuration of the server side authentication mechanisms. Optionally one truststore can be defined and one username/password based store can be defined. Authentication will first attempt to use the truststore and if this is not available will fall back to the username/password authentication. If none of these are specified the only available mechanism will be the local mechanism for the Native interface and the HTTP interface will not be accessible.
  44. core.management.security-realm.authentication.truststore=Configuration of a keystore to use to create a trust manager to verify clients.
  45. core.management.security-realm.authentication.truststore.add=Adds a keystore to use to create a trust manager to verify clients.
  46. core.management.security-realm.authentication.truststore.remove=Removes a keystore to use to create a trust manager to verify clients.
  47. core.management.security-realm.authentication.truststore.keystore-password=The password to open the keystore.
  48. core.management.security-realm.authentication.truststore.keystore-path=The path of the keystore.
  49. core.management.security-realm.authentication.truststore.keystore-relative-to=The name of another previously named path, or of one of the standard paths provided by the system. If 'relative-to' is provided, the value of the 'path' attribute is treated as relative to the path specified by this attribute.
  50. core.management.security-realm.authentication.jaas=Configuration to use a JAAS LoginContext to authenticate the users.
  51. core.management.security-realm.authentication.jaas.add=Adds a configuration to use JAAS for authentication.
  52. core.management.security-realm.authentication.jaas.remove=Removes a configuration to use JAAS for authentication.
  53. core.management.security-realm.authentication.jaas.name=The name of the JAAS configuration to use.
  54. core.management.security-realm.authentication.ldap=Configuration to use LDAP as the user repository.
  55. core.management.security-realm.authentication.ldap.add=Adds a configuration to use LDAP as the user repository.
  56. core.management.security-realm.authentication.ldap.remove=Removes a configuration to use LDAP as the user repository.
  57. core.management.security-realm.authentication.ldap.connection=The name of the connection to use to connect to LDAP.
  58. core.management.security-realm.authentication.ldap.base-dn=The base distinguished name to commence the search for the user.
  59. core.management.security-realm.authentication.ldap.recursive=Whether the search should be recursive.
  60. core.management.security-realm.authentication.ldap.user-dn=The name of the attribute which is the user's distinguished name.
  61. core.management.security-realm.authentication.ldap.allow-empty-passwords=Should empty passwords be accepted from the user being authenticated.
  62. core.management.security-realm.authentication.ldap.username-attribute=The name of the attribute to search for the user. This filter will then perform a simple search where the username entered by the user matches the attribute specified here.
  63. core.management.security-realm.authentication.ldap.advanced-filter=The fully defined filter to be used to search for the user based on their entered user ID. The filter should contain a variable in the form {0} - this will be replaced with the username supplied by the user.
  64. core.management.security-realm.authentication.local=Configuration of the local authentication mechanism.
  65. core.management.security-realm.authentication.local.add=Adds a configuration to use the JBOSS-LOCAL-USER mechanism for authentication.
  66. core.management.security-realm.authentication.local.remove=Removes a configuration to use JBOSS-LOCAL-USER for authentication.
  67. core.management.security-realm.authentication.local.default-user=The name of the default user to assume if no user specified by the remote client.
  68. core.management.security-realm.authentication.local.allowed-users=The comma separated list of users that will be accepted using the JBOSS-LOCAL-USER mechanism or '*' to accept all. If specified the default-user is always assumed allowed.
  69. core.management.security-realm.authentication.plug-in=Configuration of a user store plug-in for use by the realm.
  70. core.management.security-realm.authentication.plug-in.add=Add the plug-in definition.
  71. core.management.security-realm.authentication.plug-in.remove=Remove the plug-in definition.
  72. core.management.security-realm.authentication.plug-in.name=The short name of the plug-in (as registered) to use.
  73. core.management.security-realm.authentication.plug-in.mechanism=Allow the mechanism this plug-in is compatible with to be overridden from DIGEST.
  74. core.management.security-realm.authentication.plug-in.property=A configuration property to be made available to the plug-in.
  75. core.management.security-realm.authentication.properties=Configuration to use a list users stored within a properties file as the user repository. The entries within the properties file are username={credentials} with each user being specified on it's own line.
  76. core.management.security-realm.authentication.properties.add=Adds a configuration to use a list users stored within a properties file as the user repository.
  77. core.management.security-realm.authentication.properties.remove=Removes a configuration to use a list users stored within a properties file as the user repository.
  78. core.management.security-realm.authentication.properties.path=The path of the properties file containing the users.
  79. core.management.security-realm.authentication.properties.relative-to=The name of another previously named path, or of one of the standard paths provided by the system. If 'relative-to' is provided, the value of the 'path' attribute is treated as relative to the path specified by this attribute.
  80. core.management.security-realm.authentication.properties.plain-text=Are the credentials within the properties file stored in plain text. If not the credential is expected to be the hex encoded Digest hash of 'username : realm : password'.
  81. core.management.security-realm.authentication.xml=Configuration to use a list users stored directly within the standalone.xml or host.xml configuration file as the user repository.
  82. core.management.security-realm.authentication.xml.add=Adds a configuration to use a list users stored directly within the standalone.xml or host.xml configuration file as the user repository.
  83. core.management.security-realm.authentication.xml.remove=Removes a configuration to use a list users stored directly within the standalone.xml or host.xml configuration file as the user repository.
  84. core.management.security-realm.authentication.xml.user=An authorized user.
  85. core.management.security-realm.authentication.xml.user.add=Adds an authorized user.
  86. core.management.security-realm.authentication.xml.user.remove=Removes an authorized user.
  87. core.management.security-realm.authentication.xml.user.password=The user's password.
  88. core.management.security-realm.authorization=Configuration server side for loading additional user information such as roles to be used for subsequent authorization checks.
  89. core.management.security-realm.authorization.properties=Configuration to use properties file to load a users roles. The entries within the properties file are username={roles} where roles is a comma separated list of users roles.
  90. core.management.security-realm.authorization.properties.add=Adds a configuration to use a properties file to load a users roles.
  91. core.management.security-realm.authorization.properties.remove=Removes a configuration to use a properties file to load a users roles.
  92. core.management.security-realm.authorization.properties.path=The path of the properties file containing the users roles.
  93. core.management.security-realm.authorization.properties.relative-to=The name of another previously named path, or of one of the standard paths provided by the system. If 'relative-to' is provided, the value of the 'path' attribute is treated as relative to the path specified by this attribute.
  94. core.management.security-realm.authorization.plug-in=Configuration of a user store plug-in for use by the realm.
  95. core.management.security-realm.authorization.plug-in.add=Add the plug-in definition.
  96. core.management.security-realm.authorization.plug-in.remove=Remove the plug-in definition.
  97. core.management.security-realm.authorization.plug-in.name=The short name of the plug-in (as registered) to use.
  98. core.management.security-realm.authorization.plug-in.property=A configuration property to be made available to the plug-in.
  99. core.management.security-realm.authorization.ldap=Configuration to use LDAP as the user repository.
  100. core.management.security-realm.authorization.ldap.add=Adds a configuration to use LDAP as the user repository.
  101. core.management.security-realm.authorization.ldap.remove=Removes a configuration to use LDAP as the user repository.
  102. core.management.security-realm.authorization.ldap.connection=The name of the connection to use to connect to LDAP.
  103. core.management.security-realm.authorization.ldap.username-to-dn=User search configuration where the username is already a distinguished name.
  104. core.management.security-realm.authorization.ldap.user-search.username-to-dn=User search configuration where the username is already a distinguished name.
  105. core.management.security-realm.authorization.ldap.user-search.username-to-dn.add=Add a username to dn fiter.
  106. core.management.security-realm.authorization.ldap.user-search.username-to-dn.remove=Remove a username to dn fiter.
  107. core.management.security-realm.authorization.ldap.user-search.username-to-dn.force=Authentication may have already converted the username to a distingushed name, force this to occur again before loading groups.
  108. core.management.security-realm.authorization.ldap.username-filter=A simple filter configuration to identify the users distinguished name from their username.
  109. core.management.security-realm.authorization.ldap.user-search.username-filter.add=Add username fiter.
  110. core.management.security-realm.authorization.ldap.user-search.username-filter.remove=Add username fiter.
  111. core.management.security-realm.authorization.ldap.user-search.username-filter=A simple filter configuration to identify the users distinguished name from their username.
  112. core.management.security-realm.authorization.ldap.user-search.username-filter.force=Authentication may have already converted the username to a distingushed name, force this to occur again before loading groups.
  113. core.management.security-realm.authorization.ldap.user-search.username-filter.base-dn=The starting point of the search for the user.
  114. core.management.security-realm.authorization.ldap.user-search.username-filter.recursive=Should levels below the starting point be recursively searched?
  115. core.management.security-realm.authorization.ldap.user-search.username-filter.user-dn-attribute=The attribute on the user entry that contains their distinguished name.
  116. core.management.security-realm.authorization.ldap.user-search.username-filter.attribute=The attribute on the user entry that is their username.
  117. core.management.security-realm.authorization.ldap.advanced-filter=An advanced filter configuration to identify the users distinguished name from the username.
  118. core.management.security-realm.authorization.ldap.user-search.advanced-filter.add=Add an advanced fiter.
  119. core.management.security-realm.authorization.ldap.user-search.advanced-filter.remove=Add an advanced fiter.
  120. core.management.security-realm.authorization.ldap.user-search.advanced-filter=An advanced filter configuration to identify the users distinguished name from the username.
  121. core.management.security-realm.authorization.ldap.user-search.advanced-filter.force=Authentication may have already converted the username to a distingushed name, force this to occur again before loading groups.
  122. core.management.security-realm.authorization.ldap.user-search.advanced-filter.base-dn=The starting point of the search for the user.
  123. core.management.security-realm.authorization.ldap.user-search.advanced-filter.recursive=Should levels below the starting point be recursively searched?
  124. core.management.security-realm.authorization.ldap.user-search.advanced-filter.user-dn-attribute=The attribute on the user entry that contains their distinguished name.
  125. core.management.security-realm.authorization.ldap.user-search.advanced-filter.filter=The filter to use for the LDAP search.
  126. core.management.security-realm.authorization.ldap.group-to-principal=A group search where the group entry contains an attribute referencing it's members.
  127. core.management.security-realm.authorization.ldap.group-search.group-to-principal=A group search where the group entry contains an attribute referencing it's members.
  128. core.management.security-realm.authorization.ldap.group-search=The configuration to search for a users groups.
  129. core.management.security-realm.authorization.ldap.group-search.group-to-principal.add=Add the group to principal mapping
  130. core.management.security-realm.authorization.ldap.group-search.group-to-principal.remove=Remove the group to principal mapping
  131. core.management.security-realm.authorization.ldap.group-search.group-to-principal.group-name=An enumeration to identify if groups should be referenced using a simple name or their distinguished name.
  132. core.management.security-realm.authorization.ldap.group-search.group-to-principal.iterative=Should further searches be performed to identify groups that the groups identified are a member of?
  133. core.management.security-realm.authorization.ldap.group-search.group-to-principal.group-dn-attribute=Which attribute on a group entry is it's distingushed name.
  134. core.management.security-realm.authorization.ldap.group-search.group-to-principal.group-name-attribute=Which attribute on a group entry is it's simple name.
  135. core.management.security-realm.authorization.ldap.group-search.group-to-principal.search-by=Should searches be performed using simple names or distinguished names?
  136. core.management.security-realm.authorization.ldap.group-search.group-to-principal.base-dn=The starting point of the search for the group.
  137. core.management.security-realm.authorization.ldap.group-search.group-to-principal.recursive=Should levels below the starting point be recursively searched?
  138. core.management.security-realm.authorization.ldap.group-search.group-to-principal.principal-attribute=The attribute on the group entry that references the principal.
  139. core.management.security-realm.authorization.ldap.principal-to-group=A group search where the principal entries contain an attribute referencing the groups that they are a member of.
  140. core.management.security-realm.authorization.ldap.group-search.principal-to-group.add=Add the principal to group mapping.
  141. core.management.security-realm.authorization.ldap.group-search.principal-to-group.remove=Remove the principal to group mapping.
  142. core.management.security-realm.authorization.ldap.group-search.principal-to-group=A group search where the principal entries contain an attribute referencing the groups that they are a member of.
  143. core.management.security-realm.authorization.ldap.group-search.principal-to-group.group-name=An enumeration to identify if groups should be referenced using a simple name or their distinguished name.
  144. core.management.security-realm.authorization.ldap.group-search.principal-to-group.iterative=Should further searches be performed to identify groups that the groups identified are a member of?
  145. core.management.security-realm.authorization.ldap.group-search.principal-to-group.group-dn-attribute=Which attribute on a group entry is it's distingushed name.
  146. core.management.security-realm.authorization.ldap.group-search.principal-to-group.group-name-attribute=Which attribute on a group entry is it's simple name.
  147. core.management.security-realm.authorization.ldap.group-search.principal-to-group.search-by=Should searches be performed using simple names or distinguished names?
  148. core.management.security-realm.authorization.ldap.group-search.principal-to-group.group-attribute=The attribute on the principal which references the group the principal is a member of.
  149. core.management.ldap-connections=Configurations of connection factories that can be used by a security realm to access LDAP servers as a source of authentication and authorization information.
  150. core.management.ldap-connection=A connection factory that can be used by a security realm to access an LDAP server as a source of authentication and authorization information.
  151. core.management.ldap-connection.add=Adds a connection factory that can be used by a security realm to access an LDAP server as a source of authentication and authorization information.
  152. core.management.ldap-connection.remove=Removes a connection factory that was usable by a security realm to access an LDAP server as a source of authentication and authorization information.
  153. core.management.ldap-connection.url=The URL to use to connect to the LDAP server.
  154. core.management.ldap-connection.search-dn=The distinguished name to use when connecting to the LDAP server to perform searches.
  155. core.management.ldap-connection.search-credential=The credential to use when connecting to perform a search.
  156. core.management.ldap-connection.security-realm=The security realm to reference to obtain a configured SSLContext to use when establishing the connection.
  157. core.management.ldap-connection.initial-context-factory=The initial context factory to establish the LdapContext.
  158. core.management.ldap-connection.property=A custom property to use when establishing the LDAP connection.
  159. core.management.ldap-connection.property.add=Add a custom property to use when establishing an LDAP connection.
  160. core.management.ldap-connection.property.remove=Remove a custom property defined on an LDAP connection.
  161. core.management.ldap-connection.property.value=The value of the custom property.
  162. core.management.management-interface=Interfaces exposed by the management services to allow external callers to perform management tasks.
  163. core.management.native-interface=Configuration of the server's native management interface
  164. core.management.native-interface.add=Adds the configuration of the server's native management interface
  165. core.management.native-interface.interface=Network interface on which the server's socket for native management communication should be opened. Must be 'undefined' if the 'socket-binding' attribute is set.
  166. core.management.native-interface.port=Port on which the server's socket for native management communication should be opened. Must be 'undefined' if the 'socket-binding' attribute is set.
  167. core.management.native-interface.security-realm=The security realm to use for the native management interface.
  168. core.management.native-interface.socket-binding=The name of the socket binding configuration to use for the native management interface's socket.
  169. core.management.native-remoting-interface=Configuration of the server's native management interface using a connector from the remoting subsystem.
  170. core.management.native-remoting-interface.add=Adds the configuration of the server's native management interface using a connector from the remoting subsystem.
  171. core.management.http-interface=Configuration of the server's HTTP management interface
  172. core.management.http-interface.add=Adds the configuration of the server's HTTP management interface
  173. core.management.http-interface.interface=Network interface on which the server's socket for HTTP management communication should be opened.
  174. core.management.http-interface.port=Port on which the server's socket for HTTP management communication should be opened.
  175. # whoami operation
  176. core.management.whoami=Returns the identity of the currently authenticated user.
  177. core.management.whoami.verbose=If set to true whoami also returns the users roles.
  178. core.management.whoami.reply=The identify of the authenticated user and their roles if requested.
  179. # Extensions
  180. extension=A module that extends the standard capabilities of a domain or a standalone server.
  181. extension.module=The name of the module.
  182. extension.add=Adds an extension.
  183. extension.remove=Removes an extension.
  184. extension.subsystem=A subsystem provided by the extension. What is provided here is information about the xml schema and management interface provided by the subsystem, not the configuration of the subsystem itself.
  185. extension.subsystem.xml-namespaces=A list of URIs for the XML namespaces supported by the subsystem's XML parser. May be empty if the extension did not clearly associate an XML namespace with a particular subsystem.
  186. extension.subsystem.management-major-version=Major version of the subsystem's management interface. May be undefined if the subsystem does not currently provide a versioned management interface.
  187. extension.subsystem.management-minor-version=Minor version of the subsystem's management interface. May be undefined if the subsystem does not currently provide a versioned management interface.
  188. extension.subsystem.management-micro-version=Micro version of the subsystem's management interface. May be undefined if the subsystem does not currently provide a versioned management interface.
  189. # Paths
  190. named_path=A named filesystem path, but without a requirement to specify the actual path. If no actual path is specified, acts as a placeholder in the model (e.g. at the domain level) until a fully specified path definition is applied at a lower level (e.g. at the host level, where available addresses are known.)
  191. named_path.name=The name of the path. Cannot be one of the standard fixed paths provided by the system: <ul><li>jboss.home - the root directory of the JBoss AS distribution</li><li>user.home - user's home directory</li><li>user.dir - user's current working directory</li><li>java.home - java installation directory</li><li>jboss.server.base.dir - root directory for an individual server instance</li></ul> Note that the system provides other standard paths that can be overridden by declaring them in the configuration file. See the 'relative-to' attribute documentation for a complete list of standard paths.
  192. named_path.path=The actual filesystem path. Treated as an absolute path, unless the 'relative-to' attribute is specified, in which case the value is treated as relative to that path. <p>If treated as an absolute path, the actual runtime pathname specified by the value of this attribute will be determined as follows: </p>If this value is already absolute, then the value is directly used. Otherwise the runtime pathname is resolved in a system-dependent way. On UNIX systems, a relative pathname is made absolute by resolving it against the current user directory. On Microsoft Windows systems, a relative pathname is made absolute by resolving it against the current directory of the drive named by the pathname, if any; if not, it is resolved against the current user directory.
  193. named_path.relative-to=The name of another previously named path, or of one of the standard paths provided by the system. If 'relative-to' is provided, the value of the 'path' attribute is treated as relative to the path specified by this attribute. The standard paths provided by the system include:<ul><li>jboss.home - the root directory of the JBoss AS distribution</li><li>user.home - user's home directory</li><li>user.dir - user's current working directory</li><li>java.home - java installation directory</li><li>jboss.server.base.dir - root directory for an individual server instance</li><li>jboss.server.data.dir - directory the server will use for persistent data file storage</li><li>jboss.server.log.dir - directory the server will use for log file storage</li><li>jboss.server.tmp.dir - directory the server will use for temporary file storage</li><li>jboss.domain.servers.dir - directory under which a host controller will create the working area for individual server instances</li></ul>
  194. named_path.read-only=True if added by the system, false if configured by user. If true, the path cannot be removed or modified.
  195. named_path.add=Add a new path.
  196. named_path.add.path=The value of the path's 'path' attribute
  197. named_path.add.relative-to=The value of the path's 'relative-to' attribute
  198. named_path.remove=Remove a path
  199. path.resolve-path=Resolves a relative path of a previously named paths or one of the standard paths provided by the system.
  200. path.resolve-path.relative-to-only=Indicates whether only the relative-to attribute should be resolved or the full path should be resolved. The default is false meaning the entire path will be resolved.
  201. path.resolve-path.reply=The resolved path from the relative path attribute.
  202. specified_path=A named filesystem path.
  203. specified_path.name=The name of the path. Cannot be one of the standard fixed paths provided by the system: <ul><li>jboss.home - the root directory of the JBoss AS distribution</li><li>user.home - user's home directory</li><li>user.dir - user's current working directory</li><li>java.home - java installation directory</li><li>jboss.server.base.dir - root directory for an individual server instance</li></ul> Note that the system provides other standard paths that can be overridden by declaring them in the configuration file. See the 'relative-to' attribute documentation for a complete list of standard paths.
  204. specified_path.path=The actual filesystem path. Treated as an absolute path, unless the 'relative-to' attribute is specified, in which case the value is treated as relative to that path. <p>If treated as an absolute path, the actual runtime pathname specified by the value of this attribute will be determined as follows: </p>If this value is already absolute, then the value is directly used. Otherwise the runtime pathname is resolved in a system-dependent way. On UNIX systems, a relative pathname is made absolute by resolving it against the current user directory. On Microsoft Windows systems, a relative pathname is made absolute by resolving it against the current directory of the drive named by the pathname, if any; if not, it is resolved against the current user directory.
  205. specified_path.relative-to=The name of another previously named path, or of one of the standard paths provided by the system. If 'relative-to' is provided, the value of the 'path' attribute is treated as relative to the path specified by this attribute. The standard paths provided by the system include:<ul><li>jboss.home - the root directory of the JBoss AS distribution</li><li>user.home - user's home directory</li><li>user.dir - user's current working directory</li><li>java.home - java installation directory</li><li>jboss.server.base.dir - root directory for an individual server instance</li><li>jboss.server.data.dir - directory the server will use for persistent data file storage</li><li>jboss.server.log.dir - directory the server will use for log file storage</li><li>jboss.server.tmp.dir - directory the server will use for temporary file storage</li><li>jboss.domain.servers.dir - directory under which a host controller will create the working area for individual server instances</li></ul>
  206. specified_path.read-only=True if added by the system, false if configured by user. If true, the path cannot be removed or modified.
  207. specified_path.add=Add a new path.
  208. specified_path.add.path=The value of the path's 'path' attribute
  209. specified_path.add.relative-to=The value of the path's 'relative-to' attribute
  210. specified_path.remove=Remove a path
  211. # Interfaces
  212. named_interface=A named network interface, but without any required criteria for determining the IP address to associate with that interface. If no IP address selection criteria are defined, acts as a placeholder in the model (e.g. at the domain level) until a fully specified interface definition is applied at a lower level (e.g. at the host level, where available addresses are known.)
  213. specified_interface=A named network interface, along with required criteria for determining the IP address to associate with that interface.
  214. interface=Interface definition
  215. interface.name=The name of the interface.
  216. interface.criteria=Deprecated. A set of criteria that can be used at runtime to determine what IP address to use for an interface.
  217. interface.add=Add a new interface specification.
  218. interface.add.criteria=Deprecated.
  219. interface.remove=Remove an interface specification.
  220. interface.any-address=Attribute indicating that sockets using this interface should be bound to a wildcard address. The IPv6 wildcard address (::) will be used unless the java.net.preferIpV4Stack system property is set to true, in which case the IPv4 wildcard address (0.0.0.0) will be used. If a socket is bound to an IPv6 anylocal address on a dual-stack machine, it can accept both IPv6 and IPv4 traffic; if it is bound to an IPv4 (IPv4-mapped) anylocal address, it can only accept IPv4 traffic.
  221. interface.any-ipv4-address=Attribute indicating that sockets using this interface should be bound to the IPv4 wildcard address (0.0.0.0).
  222. interface.any-ipv4-address.deprecated=In the absence of -Djava.net.preferIPv4Stack=true, the JVM cannot be instructed to bind a socket to all IPv4 addresses, but only to IPv4 addresses, so the intended semantic cannot be obtained via this setting alone. Since using any-address and setting -Djava.net.preferIPv4Stack=true provides the same effect, this any-ipv4-address attribute will be removed in a future release
  223. interface.any-ipv6-address=Attribute indicating that sockets using this interface should be bound to the IPv6 wildcard address (::).
  224. interface.any-ipv6-address.deprecated=The name of this attribute implies sockets will be reachable only via IPv6 addresses and not via IPv4, but this is not the case. Since using any-address provides the same effect, this any-ipv6-address will be removed in a future release.
  225. interface.inet-address=Attribute indicating that part of the selection criteria for choosing an IP address for this interface should be whether or not the address matches the given value. Value is either a IP address in IPv6 or IPv4 dotted decimal notation, or a hostname that can be resolved to an IP address. An 'undefined' value means this attribute is not relevant to the IP address selection.
  226. interface.link-local-address=Attribute indicating that part of the selection criteria for choosing an IP address for this interface should be whether or not the address is link-local. An 'undefined' or 'false' value means this attribute is not relevant to the IP address selection.
  227. interface.loopback=Attribute indicating that part of the selection criteria for choosing an IP address for this interface should be whether or not it is a loopback address. An 'undefined' or 'false' value means this attribute is not relevant to the IP address selection.
  228. interface.loopback-address=Attribute indicating that the IP address for this interface should be the given value, if a loopback interface exists on the machine. A 'loopback address' may not actually be configured on the machine's loopback interface. Differs from inet-address in that the given value will be used even if no NIC can be found that has the IP specified address associated with it. An 'undefined' or 'false' value means this attribute is not relevant to the IP address selection.
  229. interface.multicast=Attribute indicating that part of the selection criteria for choosing an IP address for this interface should be whether or not its network interface supports multicast. An 'undefined' or 'false' value means this attribute is not relevant to the IP address selection.
  230. interface.nic=Attribute indicating that part of the selection criteria for choosing an IP address for this interface should be whether its network interface has the given name. The name of a network interface (e.g. eth0, eth1, lo). An 'undefined' value means this attribute is not relevant to the IP address selection.
  231. interface.nic-match=Attribute indicating that part of the selection criteria for choosing an IP address for this interface should be whether its network interface has a name that matches the given regular expression. Value is a regular expression against which the names of the network interfaces available on the machine can be matched to find an acceptable interface. An 'undefined' value means this attribute is not relevant to the IP address selection.
  232. interface.point-to-point=Attribute indicating that part of the selection criteria for choosing an IP address for this interface should be whether or not its network interface is a point-to-point interface. An 'undefined' or 'false' value means this attribute is not relevant to the IP address selection
  233. interface.public-address=Attribute indicating that part of the selection criteria for choosing an IP address for this interface should be whether or not it is a publicly routable address. An 'undefined' or 'false' value means this attribute is not relevant to the IP address selection
  234. interface.resolved-address=Attribute showing the resolved ip address for this interface.
  235. interface.site-local-address=Attribute indicating that part of the selection criteria for choosing an IP address for this interface should be whether or it is a site-local address. An 'undefined' or 'false' value means this attribute is not relevant to the IP address selection
  236. interface.subnet-match=Attribute indicating that part of the selection criteria for choosing an IP address for this interface should be 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' network prefix, written in "slash notation"; e.g. "192.168.0.0/16". An 'undefined' value means this attribute is not relevant to the IP address selection.
  237. interface.up=Attribute indicating that part of the selection criteria for choosing an IP address for this interface should be whether its network interface is currently up. An 'undefined' or 'false' value means this attribute is not relevant to the IP address selection
  238. interface.virtual=Attribute indicating that part of the selection criteria for choosing an IP address for this interface should be whether its network interface is a virtual interface. An 'undefined' or 'false' value means this attribute is not relevant to the IP address selection
  239. interface.not=Attribute indicating that part of the selection criteria for choosing an IP address for this interface should be that the IP address *does not* meet any of a nested set of criteria. The value of the attribute is a set of criteria (e.g. 'loopback') whose normal meaning is reversed. An 'undefined' value means this attribute is not relevant to the IP address selection.
  240. interface.any=Attribute indicating that part of the selection criteria for choosing an IP address for this interface should be that the IP address meets at least one of a nested set of criteria, but not necessarily all of the nested criteria. The value of the attribute is a set of criteria. An 'undefined' value means this attribute is not relevant to the IP address selection.
  241. interface.resolve-internet-address.any=any
  242. interface.resolve-internet-address.not=Not
  243. interface.resolve-internet-address.any-address=Any address
  244. interface.resolve-internet-address.any-ipv4-address=Any IPv4 address
  245. interface.resolve-internet-address.any-ipv6-address=Any IPv6 address
  246. interface.resolve-internet-address.any-ipv4-address.deprecated=Use any-address
  247. interface.resolve-internet-address.any-ipv6-address.deprecated=Use any-address
  248. interface.resolve-internet-address.inet-address=Inet address
  249. interface.resolve-internet-address.link-local-address=Link local address
  250. interface.resolve-internet-address.loopback=Loopback
  251. interface.resolve-internet-address.loopback-address=Loopback address
  252. interface.resolve-internet-address.multicast=Multicast
  253. interface.resolve-internet-address.nic=NIC
  254. interface.resolve-internet-address.nic-match=NIC match
  255. interface.resolve-internet-address.point-to-point=Point to point
  256. interface.resolve-internet-address.public-address=Public address
  257. interface.resolve-internet-address.site-local-address=Site local address
  258. interface.resolve-internet-address.subnet-match=Subnet match
  259. interface.resolve-internet-address.up=Up
  260. interface.resolve-internet-address.virtual=Virtual
  261. interface.resolve-internet-address.reply=The IP address string in textual presentation.
  262. interface.not.any-address=Any address
  263. interface.not.any-ipv4-address=Any IPv4 address
  264. interface.not.any-ipv6-address=Any IPv6 address
  265. interface.not.any-ipv4-address.deprecated=Use any-address
  266. interface.not.any-ipv6-address.deprecated=Use any-address
  267. interface.not.inet-address=Inet address
  268. interface.not.link-local-address=Link local address
  269. interface.not.loopback=Loopback
  270. interface.not.loopback-address=Loopback address
  271. interface.not.multicast=Multicast
  272. interface.not.nic=NIC
  273. interface.not.nic-match=NIC match
  274. interface.not.point-to-point=Point to point
  275. interface.not.public-address=Public address
  276. interface.not.site-local-address=Site local address
  277. interface.not.subnet-match=Subnet match
  278. interface.not.up=Up
  279. interface.not.virtual=Virtual
  280. interface.any.any-address=Any address
  281. interface.any.any-ipv4-address=Any IPv4 address
  282. interface.any.any-ipv6-address=Any IPv6 address
  283. interface.any.any-ipv4-address.deprecated=Use any-address
  284. interface.any.any-ipv6-address.deprecated=Use any-address
  285. interface.any.inet-address=Inet address
  286. interface.any.link-local-address=Link local address
  287. interface.any.loopback=Loopback
  288. interface.any.loopback-address=Loopback address
  289. interface.any.multicast=Multicast
  290. interface.any.nic=NIC
  291. interface.any.nic-match=NIC match
  292. interface.any.point-to-point=Point to point
  293. interface.any.public-address=Public address
  294. interface.any.site-local-address=Site local address
  295. interface.any.subnet-match=Subnet match
  296. interface.any.up=Up
  297. interface.any.virtual=Virtual
  298. # Sockets
  299. socket-binding-group=Contains a list of socket configurations.
  300. socket-binding-group.name=The name of the socket binding group.
  301. socket-binding-group.default-interface=Name of an interface that should be used as the interface for any sockets that do not explicitly declare one.
  302. socket-binding-group.socket-binding=The individual socket configurations.
  303. socket-binding-group.port-offset=Increment to apply to the base port values defined in the socket bindings to derive the runtime values to use on this server.
  304. socket-binding-group.includes=A list of socket binding group names whose bindings are to be included in this socket-binding-group. This binding group's default interface will be applied to any included bindings that do not specify an interface.
  305. socket-binding-group.add=Adds a socket binding group.
  306. socket-binding-group.remove=Removes a socket binding group.
  307. socket-binding-group.include.add=Adds a socket binding group to the socket binding group's 'includes' attribute.
  308. socket-binding-group.include.add.include=The name of the socket binding group to include.
  309. socket-binding-group.include.remove=Removes a socket binding group from the socket binding group's 'includes' attribute.
  310. socket-binding-group.include.remove.include=The name of the socket binding group to no longer include.
  311. socket-binding=Configuration information for a socket.
  312. socket-binding.name=The name of the socket. Services which need to access the socket configuration information will find it using this name.
  313. socket-binding.interface=Name of the interface to which the socket should be bound, or, for multicast sockets, the interface on which it should listen. This should be one of the declared interfaces.
  314. socket-binding.port=Number of the port to which the socket should be bound.
  315. socket-binding.fixed-port=Whether the port value should remain fixed even if numeric offsets are applied to the other sockets in the socket group.
  316. socket-binding.multicast-address=Multicast address on which the socket should receive multicast traffic. If unspecified, the socket will not be configured to receive multicast.
  317. socket-binding.multicast-port=Port on which the socket should receive multicast traffic. Must be configured if 'multicast-address' is configured.
  318. socket-binding.add=Adds a socket binding configuration to the group.
  319. socket-binding.remove=Removes a socket binding configuration from the group.
  320. socket-binding.bound=Whether an actual socket using this socket binding configuration has been bound.
  321. socket-binding.bound-address=The address to which the actual socket using this socket binding configuration has been bound, or undefined if no socket has been bound.
  322. socket-binding.bound-port=The port to which the actual socket using this socket binding configuration has been bound, or undefined if no socket has been bound.
  323. socket-binding.client-mappings=Specifies zero or more client mappings for this socket binding. A client connecting to this socket should use the destination address specified in the mapping that matches its desired outbound interface. This allows for advanced network topologies that use either network address translation, or have bindings on multiple network interfaces to function. Each mapping should be evaluated in declared order, with the first successful match used to determine the destination.
  324. socket-binding.client-mappings.source-network=Source network the client connection binds on. This value is in the form of ip/netmask. A client should match this value against the desired client host network interface, and if matched the client should connect to the corresponding destination values. If omitted this mapping should match any interface.
  325. socket-binding.client-mappings.destination-address=The destination address that a client should connect to if the source-network matches. This value can either be a hostname or an ip address.
  326. socket-binding.client-mappings.destination-port=The destination port that a client should connect to if the source-network matches. If omitted this mapping will reuse the effective socket binding port.
  327. socket-binding-group.remote-destination-outbound-socket-binding=Configuration information for a, remote destination, outbound socket binding.
  328. socket-binding-group.local-destination-outbound-socket-binding=Configuration information for a, local destination, outbound socket binding.
  329. remote-destination-outbound-socket-binding=Configuration information for a remote destination outbound socket binding.
  330. remote-destination-outbound-socket-binding.name=Name of the outbound socket binding. Services which need to access the socket configuration information will find it using this name.
  331. remote-destination-outbound-socket-binding.source-interface=The name of the interface which will be used for the source address of the outbound socket.
  332. remote-destination-outbound-socket-binding.source-port=The port number which will be used as the source port of the outbound socket.
  333. remote-destination-outbound-socket-binding.host=The host name or the IP address of the remote destination to which this outbound socket will connect.
  334. remote-destination-outbound-socket-binding.port=The port number of the remote destination to which the outbound socket should connect.
  335. remote-destination-outbound-socket-binding.add=Adds a remote destination outbound socket binding to a socket binding group
  336. remote-destination-outbound-socket-binding.remove=Removes a remote destination outbound socket binding from a socket binding group
  337. remote-destination-outbound-socket-binding.fixed-source-port=Whether the port value should remain fixed even if numeric offsets are applied to the other outbound sockets in the socket group.
  338. local-destination-outbound-socket-binding=Configuration information for a local destination outbound socket binding.
  339. local-destination-outbound-socket-binding.name=Name of the outbound socket binding. Services which need to access the socket configuration information will find it using this name.
  340. local-destination-outbound-socket-binding.source-interface=The name of the interface which will be used for the source address of the outbound socket.
  341. local-destination-outbound-socket-binding.source-port=The port number which will be used as the source port of the outbound socket.
  342. local-destination-outbound-socket-binding.socket-binding-ref=The name of the local socket-binding which will be used to determine the port to which this outbound socket connects.
  343. local-destination-outbound-socket-binding.add=Adds a local destination outbound socket binding to a socket binding group
  344. local-destination-outbound-socket-binding.remove=Removes a local destination outbound socket binding from a socket binding group
  345. local-destination-outbound-socket-binding.fixed-source-port=Whether the port value should remain fixed even if numeric offsets are applied to the other outbound sockets in the socket group.
  346. # Subsystem
  347. subsystem.describe=Outputs the subsystem as a list of operations that can be executed to create the original model
  348. # Global operations
  349. global.read-attribute=Gets the value of an attribute for the selected resource
  350. global.read-attribute.name=The name of the attribute to get the value for under the selected resource
  351. global.read-attribute.include-defaults=Boolean to enable/disable default reading. In case it is set to false only attribute set by user are returned ignoring undefined.
  352. global.read-attribute.reply=The value of the attribute. The type will be that of the attribute found
  353. global.read-children-names=Gets the names of all children under the selected resource with the given type
  354. global.read-children-names.child-type=The name of the node under which to get the children names
  355. global.read-children-names.reply=The children names
  356. global.read-children-types=Gets the type n

Large files files are truncated, but you can click here to view the full file