Administering Liberty

A server configuration consists of a server.xml file, a file, and any optional files that are included by the two main configuration files. You can use WebSphere® Application Server Developer Tools for Eclipse or a text editor to edit the configuration files. There is no administrative console for Liberty, but you can use Admin Center to administer Liberty servers and applications and other resources from a web browser on a smartphone, tablet, or computer.

About this task

Liberty is configured by exception. The runtime environment operates from a set of built-in configuration default settings, and you only need to specify configuration that overrides those default settings. You do this by editing either the server.xml file or another XML file that is included in server.xml at run time.

Features are the units of functionality by which you control the pieces of the runtime environment that are loaded into a particular server. They are the primary mechanism that makes the server composable. The list of features that you specify in the server configuration provides a functional server.

When you first install and start the server, a feature manager and a default server configuration are available:
  • By default, a server contains the jsp-2.2 feature, to support servlet and JSP applications. You can use the feature manager to add the features that you need.
  • Server configuration is by exception. When you specify the features that you need, the default configuration of those features provides a rich environment that is designed to cover most common requirements, therefore you only need to specify changes from the default configuration.

You can organize Liberty servers into collectives to administer multiple Liberty servers at a time efficiently and accurately. For information about collectives, see Setting up the server-management environment for Liberty by using collectives.