Accessing the admin console
Accessing the admin console
It’s time to update your bookmarks. JBoss AS 7, by default, does not use anymore port 8080 to serve the admin console. You can access it at the http://localhost:9990/console as configured in your standalone.xml
<socket-binding name=”management-http” interface=”management”
Once logged in with your account you will land on the main application window which, in the standalone mode contains two main tabs: The first one, Profile, can be used to model the application server configuration as illustrated by the following screenshot:
On the other hand, the Runtime tab, can be used to manage deployments, as we have learnt in before tutorials. In the next section we will show how easy can be configuring server profiles using the Web admin console:
Configuring server profiles
The server profile configuration is located in the left area of the Web application. When running in standalone mode, it can be located under the “Profile” label. When running domain mode, you will need to navigate through the “Profiles” tab and choose one through the “Profile” combo box.
Expanding the Profile label, you can see a set of subsystems which can be configured through the Web interface.
In before tutorials, Configuring the Application Server, and Chapter 3, Configuring the Enterprise Server, of this book, we showed how to configure these resources using the main configuration file. If you are the kind of system administrator who prefers windows, icons, menus, and pointers (WIMP) interfaces, then the next sections are for
you. The configuration of resources, when using the Web console, is pretty intuitive, so we will just cover the following handy topics:
- Configuring datasources
- Configuring JMS resources
- Configuring Socket Binding groups
Clicking on the Datasources link, you will switch the main panel to the Datasource Configurations panel. This panel contains two upper tabs for configuring Datasources and XADatasources. Let’s see what the first tab contains:
In the middle of the panel, you can find out the list of configured datasources. The actions that can be started, are located in the upper right area of the screen, where you can create a new one by clicking on the Add button. In the same part of the screen you can delete a Datasource definition. On the other hand, in the lower part of the GUI you
can choose to Edit / Disable / Test a Datasource).
Editing or deleting an existing datasource is a straightforward task, which can be executed with as little as a button click. The same can be said about enabling and disabling the selected datasource. Here, we will rather show how to add a new datasource to your Profile configuration, which requires a few simple steps to be completed.
Once you have clicked on the New Datasource button, a three-steps wizard will guide you through the creation of the datasource. Let’s configure a sample MySQL datasource for this purpose. The first information required will be the datasource name and its JNDI binding. Leaving the Enabled check-box on, will make the datasource enabled (default).
The next step will be selecting the proper JDBC driver for your datasource. Provided that you have successfully installed a JDBC driver on your AS, you will should have it listed as an available driver:
Choose the MySQL JDBC driver and in the next (last) step you will be required to enter the JDBC URL of the datasource along with the Username and Password credentials.
Clicking Done completes the wizard and you will be redirected to the main panel, where the new datasource is now enlisted and enabled for use by your applications
Creating a new XA datasource
As we have shown in the Command Line Interface section, an XA datasource requires your JDBC URL to be entered as XA property, in just the same way. Thus, the datasource JNDI naming and driver selection stays the same as for non-XA datasources. In the next screenshot, we illustrate the last two steps needed to complete the XA datasource creation: