Chapter 4. An overview of the Liberty profile 95
For more information, see the WebSphere Application Server V8.5 Information Center at:
4.2 Installing the Liberty profile
You can use any of the following methods to install the Liberty profile:
Extracting an archive file that contains the distribution image to a local folder
Using Installation Manager
Installing the Liberty profile developer tools
For more information about installing the Liberty profile, see 9.8, “Planning for the Liberty
profile” on page 268.
4.3 Configuring the Liberty profile
The Liberty profile configuration operates from a set of built-in configuration defaults. You can
specify only the required changes for your environment by using a simple XML format. This
section provides details about how to configure the Liberty profile.
4.3.1 Liberty profile configuration characteristics
The Liberty profile configuration has the following characteristics:
The persistent configuration has these characteristics:
– Described in XML files
– Small, easy to back up, and easy to copy to another system
– Human readable and editable in a text editor
– Shareable with the entire application development team
– Composed such that features can add configurations to the system easily
The runtime configuration has these characteristics:
– Injected into the owning components on an update
– Dynamically composable so that configuration for features can be added to or removed
from the system easily
– Supports zero cost migration between releases
Configuration used by components is dynamically responsive to updates and forgiving.
Missing values are assumed and unrecognized properties are ignored.
4.3.2 Simplified configuration
A Liberty profile server configuration consists of a bootstrap.properties file, a server.xml
file and any (optional) files that are included by these files. The bootstrap.properties file
specifies properties that need to be available before the main configuration is processed.
These properties are kept to a minimum. The server.xml file is the primary configuration file
for the server, and the file that users work with the most.