Grouped under the same project for ease of management

grouped under the same project for ease of management and to avoid name conflicts with
resources from other projects.
Run time (WebSphere Liberty profile)
The run time includes the bin , lib , and lafiles binary files.
Liberty_server
The Liberty_server directory contains the following server definitions:
– A self-contained directory that includes the server.env file, the jvm.options file, the
server.xml file, and other configuration files and working directories.
– A template directory that contains just the server.xml file and other configuration files.
This directory allows one set of configuration files to be standardized and referred to
from multiple server instances.
– A localized directory that contains only the server.env file, the jvm.options file, the
working directory, and a pointer to a template directory. The localization directory
contains only host-specific information:
• Host name
• The location of the SDK
• A pointer to the server template directory
• The location of the application or applications
Application_binary
The Application_binary is an archive or a directory that contains the application. This
archive or directory might or might not be deployed to a Liberty profile server.
SDK
The Java software development kit is used to run the Liberty profile servers.
A Liberty profile image is an archive file that contains one or more types of resources of the
Liberty profile environment, depending on the topology that is deployed. You can extract them
manually or can use an extraction tool to deploy the file to one or more systems. Alternatively,
you can use the job manager to deploy these images.
In WebSphere Application Server V8.5, the job manager can be used to perform these
functions:
Package the Liberty profile runtime environments, configurations, and applications
Distribute and deploy a Liberty profile server and applications
Start embedded profile packages
For more information about managing the Liberty profile with a job manager, see 8.3.3,
“Liberty profiles managed by a job manager” on page 214.

Chapter 4. An overview of the Liberty profile
111
4.7.1 Example topology 1
Figure 4-4 illustrates a self-contained topology in which the compressed file contains the
following resources:
A Liberty profile run time, which is shown as WLP in Figure 4-4 on page 111
An SDK
A Liberty profile server
An application
Figure 4-4 Self-contained topology 1
4.7.2 Example topology 2
Figure 4-5 illustrates a self-contained topology in which the compressed file contains the
following components:
A Liberty profile run time
A Liberty profile server
An application
The SDK is preinstalled on each host.
Figure 4-5 Self-contained topology 2
WLP
SDK
Server
Application
Deploy
WLP
Server
Application
Deploy
SDK

112
WebSphere Application Server V8.5 Concepts, Planning, and Design Guide
4.7.3 Example topology 3
Figure 4-6 illustrates a shared topology that involves installation of multiple compressed files.