Administer the Liberty profile manually
The server.xml file is the primary configuration file for the server. The bootstrap.properties file specifies properties that need to be available before the main configuration is processed. If you update bootstrap.properties, restart the server for the changes to take effect. The only required element in server.xml is a server definition. We can specify overrides and additions. For example, to change the transaction timeout value...
<transactions timeout="30" />
Some attributes can have multiple values. For example...
<server> <featureManager> <feature>servlet-3.0</feature> <feature>localConnector-1.0</feature> </featureManager> </server>
The contents of server.xml can be brief. For example, here is a complete server configuration to run a web application:
<server> <featureManager> <feature>servlet_3.0</feature> </featureManager> <application name="snoop" location="/mywebapps/snoop" id="snoop" type="war"/> </server>
Subtopics
- Customize the Liberty profile environment
- Administer the Liberty profile from the command prompt
- Add and remove Liberty features
- Use include elements, variables, and Ref tags in configuration files
- Control dynamic updates
- Configure class loaders and libraries for Java EE applications
- Configure a web server plug-in
- Configure session persistence
- Configure ManagedExecutorService instances
- Configure thread context service instances
- Configure managed scheduled executors
- Configure managed thread factories
- Access local and JMX REST connectors
- Establishing a JMX MBean Liberty server connection
- Configure binary logging in the Liberty Profile
- Administer the transaction service
- Administer data access resources
- Administer web applications
Parent topic: Administer the Liberty profileConcepts:
Server configuration
Administer the Liberty profile using developer tools
Edit the Liberty profile configuration using developer tools
Displaying the server configuration in a merged view