hal / core

Management console for WildFly 12 and below

⚠ Maintenance Version

This repository is the maintenance codebase of the HAL managament console for WildFly 12 and below. For the most recent version, please use https://github.com/hal/console

---

The WildFly Web Management Interface

Prerequisites

• JDK 8
• WildFly 8+

In order to work on the console you a need running WildFly instance on your local host. You can download it here:

http://www.wildfly.org/downloads/

You can run WildFly in either the 'domain' or 'standalone' mode.

Running in hosted mode

1. Make sure WildFly is started
2. Make sure you build the top level module first (mvn -Pdev clean install).
3. cd 'build/app'

Start the GWT shell with

mvn gwt:<run|debug>

When the hosted browser is started, it's enough to hit the 'refresh' button to recompile and verify changes. You can get the OOPHM Plugin, required for attaching your browser to the hosted mode execution here: http://www.gwtproject.org/missing-plugin/

NOTE: you need to add user with WildFly add-user script. NOTE2: firefox on linux should use version 24 or minor, because gwt plugin doesn't work with recent firefox versions.

Running in web mode

cd build/app
mvn package

Produces a war file in target/*-resources.jar, which needs to be deployed as a WildFly Module.

EAP Build Profile

To run a customised EAP build (L&F) follow these steps:

1. Create a dedicated version number (i.e. 1.0.0.EAP.CR2)

2. Rebuild with the EAP profile enabled:

    mvn -Peap clean install
   

Development Profile

Due to the increased number of permutations (additional languages) the full compile times have increased quiet drastically. To work around this problem during development, we've added a development build profile that restricts the languages to english and the browser permutations to firefox:

1. Build

    mvn -Pdev clean install
   

2. Run hosted mode

    cd 'build/app'
    mvn -Pdev gwt:run
   

Bind Address

In some cases you may want to bind both the AS and the hosted mode to a specific address. A typical scenario is running a different OS (i.e Windows) in a virtual machine. To make such a setup work you need to bind the hosted mode environment and the application server to a specific inet address that can be access from the virtual machine:

1. start the AS on a specific address:

    ./bin/standalone.sh -Djboss.bind.address=192.168.2.126 -Djboss.bind.address.management=192.168.2.126
   

2. launch hosted mode on a specific address:

    mvn clean -Dgwt.bindAddress=192.168.2.126 gwt:run
   

Problems?

Please post any questions to the wildfly mailing list: [email protected]

Or ping us on IRC

freenode.net#wildfly-management

Have fun.

core's Issues

Unable to set filename for logging file handler in UI

I am unable to set the filename of a file handler or periodic file handler in the UI:

In the standalone.xml file I am able to actually configure a file like that:

            <periodic-rotating-file-handler name="FILE" autoflush="true">
                <formatter>
                    <named-formatter name="PATTERN"/>
                </formatter>
                <file relative-to="jboss.server.log.dir" path="server.log"/>
                <suffix value=".yyyy-MM-dd"/>
                <append value="true"/>
            </periodic-rotating-file-handler>

In the XML the suffix attribute looks pretty similar to file and is shown in the UI.
So I went through the source code starting from src.main.java.org.jboss.as.console.client.shared.subsys.logger.HandlerView, but I was not able to track the issue down further than that.

Expected behavior: A field to enter the filename should show up under attributes in the UI.
Used version: WildFly 9.0.1

Wrong status code of HTTP response on GWT debug

I found difference in behavior of DMR in GWT debug from behavior in compiled form, when code in HAL try to read not existing attribute or attribute of not existing node:

// reading not existing attribute of /
ModelNode operation = new ModelNode();
operation.get(ADDRESS).set(new ModelNode());
operation.get(NAME).set("notexisting");
operation.get(OP).set(READ_ATTRIBUTE_OPERATION);

dispatcher.execute(new DMRAction(operation), new LoggingCallback<DMRResponse>() {
    public void onSuccess(DMRResponse response) {
        ModelNode outcome = response.get().get(ModelDescriptionConstants.OUTCOME);
        if(outcome.asString().equals(ModelDescriptionConstants.SUCCESS)){
            // ...
        }else{
            // **This will be executed in GWT debug mode**
        }
    }
    public void onFailure(Throwable caught) {
        // **This will be executed in production**
    }
});

Root of the problem is in statusCode of HTTP response - in production is 500, but in GWT debug is 200:

core/dmr/src/main/java/org/jboss/dmr/client/dispatch/impl/DMRHandler.java

Line 219 in c615533

if (200 == statusCode)

But I dont know where this can be repaired.