EuroAP Application Server – Getting to Know the Console

EuroAP Application Server Getting to Know the Console

The application server can be configured and managed in three ways: using the CLI, the HAL graphic console or by making changes directly in the configuration file. In today's article, we will take a short journey around the EuroAP application server web console and get to know the individual tabs of the graphical interface. As an example we will take a console configured in Domain mode. The graphical interface in Standalone mode contains the same tabs, differing only in small details (e.g. there are no Server Groups).

The HAL console in EuroAP application server offers a very pleasant and simple graphical interface, thanks to which we can easily manage our server and configure it.

Using the default configuration, the console can be accessed at localhost: 9990 or 127.0.0.1: 9990. After opening this address in the browser and logging in, the main page will appear:

homepage

As you can see in the above screenshot, we have six different tabs at our disposal:

  • Homepage
  • Deployments
  • Configuration
  • Runtime
  • Patching
  • Access Control.

We will discuss each of them briefly today.

Home

The home page has a shortcut to each section along with short descriptions that are intended to guide the user to the section that may be of interest to them. Let's take a closer look at the other tabs.

Deployments

The Deployments section is designed to intended for managing our Java applications. From this tab we can implement these applications, remove them, view the contents of * .jar and * .war files and many more. The way of implementing the application via the web console is very simple and convenient.

deployments

Just click "Upload new deployment" and then select the program you want to deploy. We can also do it using the drag & drop technique.

deployments

After approval, our product is immediately available at localhost: 8080/helloWorldStatic and ready for operation:

deploymentsConfiguration

From this tab, we have access to the entire system configuration. We can display the configuration of any subsystem and modify it. It is recommended to get familiarized with the individual tabs and find the modules we are interested in. For example, we can configure JDBC Drivers or Datasources for any profile in Domain mode.

configuration

The process of adding a database is simple, and the graphics console will help us get through it in a user-friendly way:

configuration

Runtime

A Domain mode application server consists of at least one Domain Controller, Host Controller, and at least one server group per Host Controller.

The Runtime tab is the central point from which we can manage our infrastructure. This is the right place if you want to add a new server, remove it or just restart after making some configuration modifications.

runtime

The Runtime tab also clearly shows the entire structure of the system. With a large number of hosts and servers this can be very helpful.

Patching

In this section we can manage EuroAP patching.

patching

The Patching tab and its capabilities are described in detail in a separate article: Middleware – how to patch EuroAP Application Server?

Access Control

This panel is used to manage users. From here, we can add and remove them. The Access Control mechanism is based on managing the users by granting them appropriate permissions with the use of Roles.

Roles allow multiple users to share the responsibility of managing the server. Due to "sharing of duties" by managing users, it is easy to distribute responsibility among individuals or groups without granting unnecessary permissions. This guarantees the maximum possible security for servers and data, while providing flexibility in configuration, deployment and management.

 

access_control

Summary

As you can see, the HAL console in EuroAP gives us a lot of possibilities. We can manage virtually every section from this level. The graphical interface is clearly designed, making configuration management by users very easy. Note that modifications directly in the *.xml file can be dangerous, and so are not recommended. Therefore, in case of any uncertainty when using the CLIconsole, we recommend that you use the web console.