The HAL management console is part of every WildFly and JBoss EAP installation. To get started simply fire up your browser and open http://localhost:9990.
Besides that you can run the console on its own aka standalone mode. HAL is a RIA with no server side dependencies. When run on its own, HAL will show a dialog when it’s started. You have to provide the URL of the management endpoint you want to connect to. This is typically the one which uses port 9990. You can add as many endpoints as you want. They’re stored in the browser local storage and survive a browser restart.
If you want to skip the connection dialog and connect to a previously defined endpoint, use the
connect request parameter. If the console runs on port 9090, you’d use an URL like http://localhost:9090/?connect=Development.
The standalone mode allows you to manage different WildFly and / or JBoss EAP instances using the same console. Furthermore you can always use the latest HAL version.
There are different ways to use the standalone mode. All of them require to configure the allowed origins of the http(s) management endpoint:
/host=master/core-service=management/management-interface=http-interface:list-add(name=allowed-origins,value=<url>) reload --host=master
The URL depends on how you launch the console. You can choose between one of the following options:
hal-standalone.jar starts an Undertow server at http://localhost:9090. You can specify a different port as command line parameter:
- Add http://localhost:9090 as allowed origin
java -jar hal-standalone-<version>.jar [port]
- Open http://localhost:9090
- Add http://localhost:3000 as allowed origin
npm install hal-console
[PORT=dddd] node hal-console
The latest console version is also available at GitHub:
GitHub pages are served from https so you need to secure the management interface as well. Please note that if you’re using a self signed key store you might need to open the local management endpoint in the browser and accept the unsafe certificate once, before you can use it with HAL.