이 콘텐츠는 선택한 언어로 제공되지 않습니다.
Chapter 3. Configuration of HawtIO
HawtIO consists of two main components: The server runtime and client console.
The server runtime is the Java backend that runs on the server side, and the client console is the JavaScript frontend that is deployed and runs on the browser.
Therefore, two types of configuration are provided for HawtIO:
HawtIO and its plugins can configure their behaviours through System properties.
- Configuration properties - The server runtime configuration
- hawtconfig.json - The client console configuration
3.1. Configuration properties 링크 복사링크가 클립보드에 복사되었습니다!
The HawtIO server runtime and its plugins can configure their behaviours through System properties.
The following table lists the configuration properties for the HawtIO core system and various plugins.
For the configuration properties related to security and authentication, refer to Security.
| System | Default | Description |
|---|---|---|
| hawtio.disableProxy | false | With this property set to true, ProxyServlet (/hawtio/proxy/*) can be disabled. This makes the Connect plugin unavailable, which means HawtIO can no longer connect to remote JVMs, but sometimes users might want to do so because of security if the Connect plugin is not used. |
| hawtio.localAddressProbing | true | Whether local address probing for proxy allowlist is enabled or not upon startup. Set this property to false to disable it. |
| hawtio.proxyAllowlist | localhost, 127.0.0.1 | Comma-separated allowlist for target hosts that Connect plugin can connect to via ProxyServlet. All hosts not listed in this allowlist are denied to connect for security reasons. This option can be set to * to allow all hosts. Prefixing an element of the list with "r:" allows to define a regex (example: localhost,r:myserver[0-9]+.mydomain.com) |
| hawtio.redirect.scheme | The scheme is to redirect the URL to the login page when authentication is required. | |
| hawtio.sessionTimeout | The maximum time interval, in seconds, that the servlet container will keep this session open between client accesses. If this option is not configured, then HawtIO uses the default session timeout of the servlet container. |
3.2. Quarkus 링크 복사링크가 클립보드에 복사되었습니다!
For Quarkus, all those properties are configurable in application.properties or application.yaml with the quarkus.hawtio prefix.
For example:
quarkus.hawtio.disableProxy = true
quarkus.hawtio.disableProxy = true
3.3. Spring Boot 링크 복사링크가 클립보드에 복사되었습니다!
For Spring Boot, all those properties are configurable in application.properties or application.yaml as is.
For example:
hawtio.disableProxy = true
hawtio.disableProxy = true
3.4. Configuring Jolokia through system properties 링크 복사링크가 클립보드에 복사되었습니다!
The Jolokia agent is deployed automatically with io.hawt.web.JolokiaConfiguredAgentServlet that extends Jolokia native org.jolokia.http.AgentServlet class, defined in hawtio-war/WEB-INF/web.xml.
If you want to customize the Jolokia Servlet with the configuration parameters that are defined in the Jolokia documentation, you can pass them as System properties prefixed with jolokia.
For example:
jolokia.policyLocation = file:///opt/hawtio/my-jolokia-access.xml
jolokia.policyLocation = file:///opt/hawtio/my-jolokia-access.xml
3.5. Custom branding configuration of HawtIO 링크 복사링크가 클립보드에 복사되었습니다!
The hawtconfig.json is the entrypoint JSON file for configuring the frontend console of HawtIO. It can be used to customise the various parts of the console: the branding, styles and basic UI parts such as the login page and about modal, as well as the console-specific behaviours of some of the HawtIO plugins.
Here is an example file of hawtconfig.json:
Example hawtconfig.json:
3.5.1. Configuration options in hawtconfig.json 링크 복사링크가 클립보드에 복사되었습니다!
At the top level of hawtconfig.json the following options are currently provided:
Top-level configuration options
| Option | Descriptiom |
|---|---|
|
| The branding options for the console. |
|
| The login page configuration. |
|
| The about modal configuration. |
|
| The list of plugins that should be hidden from the console. |
|
| The JMX plugin configuration. |
|
| The HawtIO Online configuration. |
3.5.1.1. Branding 링크 복사링크가 클립보드에 복사되었습니다!
The branding configuration provides the options to customise the console’s branding, such as the application name, logos, styles and favicon.
Branding configuration options
| Option | Default | Description |
|---|---|---|
|
|
| Customise the application name of the console. The name is used in the browser title header and optionally in the header of the console page. |
|
|
| Show the application name in the header of the console page. |
|
|
| Use the URL to substitute the application logo. |
|
|
| Use the URL to substitute the company logo. |
|
| Provide the custom CSS to apply to the console. | |
|
| Use the URL to substitute the favicon. |
Here is how the branding configuration looks in hawtconfig.json:
3.5.1.2. Login 링크 복사링크가 클립보드에 복사되었습니다!
The login configuration provides the options to customise the information displayed in the HawtIO login page.
Login configuration options
| Option | Default | Description |
|---|---|---|
|
| Set the text displayed in the login page. | |
|
| [ ] |
Provide the links at the bottom of the login page. The value should be an array of objects with |
Here is how the login configuration looks in hawtconfig.json:
3.5.1.3. About 링크 복사링크가 클립보드에 복사되었습니다!
The about configuration provides the options to customise the information displayed in the HawtIO About modal.
About configuration options
| Option | Default | Description |
|---|---|---|
|
|
| Customise the title of the About modal. |
|
| Provide the description text to the About modal. | |
|
|
| Use the URL to substitute the logo image in the About modal. |
|
| [ ] |
Provide the information of names and versions about the additional components used in the console. The value should be an array of objects with |
|
| Set the copyright information in the About modal. |
Here is how the about configuration looks in hawtconfig.json:
3.5.1.4. Disabled routes 링크 복사링크가 클립보드에 복사되었습니다!
The disabledRoutes configuration provides the option to hide the plugins from the console.
The value of the option should be an array of strings that represent the paths of the plugins that should be hidden.
Here is how the disabledRoutes configuration looks in hawtconfig.json:
"disabledRoutes": [ "/disabled" ]
"disabledRoutes": [
"/disabled"
]
3.5.1.5. JMX plugin 링크 복사링크가 클립보드에 복사되었습니다!
The JMX plugin is customisable via the jmx configuration in hawtconfig.json.
By default HawtIO loads all MBeans into the workspace via the JMX plugin. Sometimes your custom HawtIO console might want to load only a portion of MBeans to reduce the load on the application. The jmx configuration provides an option to limit the MBeans to be loaded into the workspace.
JMX plugin configuration options
| Option | Default | Description |
|---|---|---|
|
| Specify the list of MBean domains and object names that should be loaded to the JMX plugin workspace. |
This option can either disable workspace completely by setting false, or specify an array of MBean paths in the form of:
<domain>/<prop1>=<value1>,<prop2>=<value2>,...
<domain>/<prop1>=<value1>,<prop2>=<value2>,...
to fine-tune which MBeans to load into workspace.
Disabling workspace should also deactivate all the plugins that depend on MBeans provided by workspace.
Here is how the jmx configuration looks in hawtconfig.json:
3.5.1.6. HawtIO Online 링크 복사링크가 클립보드에 복사되었습니다!
The frontend aspects of HawtIO Online can be configured via the online configuration in hawtconfig.json.
HawtIO Online configuration options
| Option | Default | Description |
|---|---|---|
|
|
Set the selector used to watch for projects. It is only applicable when the HawtIO deployment type is equal to | |
|
|
Configure the OpenShift Web console link. A link is added to the application menu when the HawtIO deployment is equal to |
ConsoleLink configuration options
| Option | Default | Description |
|---|---|---|
|
| Set the text display for the link. | |
|
|
Set the section of the application menu in which the link should appear. It is only applicable when the HawtIO deployment type is equal to | |
|
|
Set the path, relative to the HawtIO status URL, for the icon used in front of the link in the application menu. It is only applicable when the |
Here is how the HawtIO online configuration looks in hawtconfig.json:
3.5.2. Deploying hawtconfig.json 링크 복사링크가 클립보드에 복사되었습니다!
3.5.2.1. Quarkus 링크 복사링크가 클립보드에 복사되었습니다!
For a Quarkus application, the hawtconfig.json file, as well as the other companion static resources such as CSS files and images, should be placed under META-INF/resources/hawtio in the src/main/resources directory of the project.
You can find an example Quarkus project here.
3.5.2.2. Spring Boot 링크 복사링크가 클립보드에 복사되었습니다!
For a Spring Boot application, the hawtconfig.json file, as well as the other companion static resources such as CSS files and images, should be placed under hawtio-static in the src/main/resources directory of the project.
You can find an example Spring Boot project here.
3.5.3. Customising from plugins 링크 복사링크가 클립보드에 복사되었습니다!
While plugins cannot directly provide the hawtconfig.json file itself for the console, they can customise the configuration after the file is loaded from the main console application.
The @hawtio/react NPM package provides the configManager API. You can use this API in the plugin’s index.ts to customise the configuration of hawtconfig.json during the loading of the plugin.
Here is an example of how you can customise the hawtconfig.json configuration from a plugin:
You can find an example WAR plugin project here.