The Console, as well as the JMX and JBossWS consoles, are deployed "on-demand" by default. This means that the consoles are deployed when the user requests access. This deferred deployment strategy minimizes the overall server boot time. This feature can be disabled, however, by passing the following property to the server start command:

/run.sh -Djboss.as.deployment.ondemand=false

Once the server is started, simply point your browser of choice to:

http://localhost:8080/admin-console

JBoss AS binds its services to localhost (127.0.0.1) by default, instead of binding to all available interfaces (0.0.0.0). This was primarily done for security reasons because of concerns of users going to production without having secured their servers properly. To enable remote access by binding JBoss services to a particular interface, simply start the JBoss AS server with the -b option. To bind to all available interfaces and re-enable the legacy behaviour use -b 0.0.0.0. If the server is started with the -b option, you will have to alter the URL accordingly.

This will bring you to the JBoss AS Administration Console Login page. Login credentials are the same as used for the JMX console. A default user/password combination, admin/admin, is provided for out-of-box access. You can change/update the usernames/passwords for the configured security domain by editing the corresponding credential files:

server/configuration/conf/props/jmx-console-users.properties

Similarly, you can change/update roles for the configured security domains by editing corresponding credential files:

server/configuration/conf/props/jmx-console-roles.properties

For more information on modifying user credentials, refer to the Secure the JMX Console wiki.

Click the Login button using the default user provided or your customized administrative login.