WebSphere Liberty is a Java EE application server built on open source Open Liberty. It uses OSGi services to manage components and provide a dynamic runtime environment. The Liberty kernel launches the OSGi framework which loads configured features as OSGi bundles. Features provide programming models and services for applications. Liberty is lightweight, dynamic, and easy to use making it suitable for cloud applications and microservices.

1. WebSphere
Liberty

2. Agenda
Introduction
Architecture
Installation
Program

3. Introduction
IBM WebSphere Liberty is a Java EE application server.
Designed for cloud-native applications and microservices.
Liberty Server (WAS) performs the role of a web
application server.
It is the flagship product within IBM's WebSphere software
suite.
Liberty profile is a dynamic profile of WAS which enables
the WAS server to deploy only required custom features
Developers can choose required features based on business
requirement and push it to the server.

4. Why
WebSphere
Liberty?

5. ARCHITECTURE
 WebSphere Liberty is a fast, dynamic, and easy-to-use Java application
server, built on the open source Open Liberty project.
 WebSphere Liberty is a highly composable and dynamic runtime environment.
OSGi services are used to manage component lifecycles, and the injection of
dependencies and configuration.
 The server process contains a single JVM, the Liberty kernel, and any number
of optional features. The feature code and most of the kernel code runs as
OSGi bundles within an OSGi framework.
 Features provide the programming models and services that are required by
applications.

6. Architecture

7. THE KERNEL LAUNCHER
BOOTSTRAPS THE SYSTEM
AND STARTS THE OSGI
FRAMEWORK.
THE CONFIGURATION IS
PARSED, AND THEN THE
CONFIGURED FEATURES ARE
LOADED BY THE FEATURE
MANAGER.
THE KERNEL EXTENSIVELY
USES OSGI SERVICES TO
PROVIDE A HIGHLY DYNAMIC
RUNTIME ENVIRONMENT.
THE FILE MONITOR SERVICE
DETECTS APPLICATION AND
CONFIGURATION FILE
CHANGES, AND THE
LOGGING SERVICE WRITES
MESSAGES AND DEBUG
INFORMATION TO THE
LOCAL FILE SYSTEM.

8.  As the flowing diagram shows,
the kernel includes a feature
manager, a file monitor, a
logging service, and OSGi
resources for configuration
administration and for working
with declarative services.

9.  Features are specified in the system configuration files that are the
server.xml file and any other included files.
 The server configuration files populate the OSGi Configuration Admin
service, which injects the feature configuration into the feature manager
service.
 The feature manager maps each feature name to a list of bundles that
provide the feature.
 The bundles are installed into the OSGi framework and started.
 The feature manager responds to configuration changes by dynamically
adding and removing features while the server is running.

10. Installation
Add Add the WebSphere Development tools (WDT) to Eclipse
.
Download
and install
Download and install Eclipse 4.5(Oxygen) for Java EE
Developers. This is the Integrated Development
Environment (IDE) you will be using to develop your
enterprise applications.
Download
and install
Download and install a Java Development Kit (JDK).
This is required to develop Java apps. Java EE 7 is the
latest supported version, so it is recommended that you
use JDK 7.1 or 7

11.  Fill the destination path with
where you would like your
liberty installation path to be
located
 Check ‘Download and install a
new runtime environment from
ibm.com:‘, and then select the
latest version of the WAS Liberty
Runtime. Click Next.

12. Project
creation
Go to new->Dynamic Web Project
add project name and finish it
Go to project->Java Resources->src-
>right click->new->class name -
>next->edit URL Mappings->finish
Edited the java file to print
message.

13. Sample Program

16. Reasons to Choose Liberty
•Smaller, simpler, faster to set up
•Effortless to have common development and production
runtimes
•More accommodating and adjustable to install, update
and manage
•packaged server ‘master image’ deployments are popular
•Composable, right-sized runtimes
•More choice of deployment environments
•Bluemix, other PaaS, containers
•Liberty on z/OS has higher throughput, lower resource
use
•Servers (all editions) can be centrally handled (albeit not
clustered)
•Earlier support of new technology through continuous
delivery
•Easier version to version migration once using Liberty
•Greater management scale with collectives than cells

20. Thank You