Skip to main content

Techdocs Library > White papers >

Liberty z/OS Review of "Good Practices"



Document Author:

Don Bagwell


Document ID:

WP102687


Doc. Organization:

Advanced Technical Sales


Document Revised:

01/16/2017


Product(s) covered:

WebSphere Application Server for z/OS







Abstract: Liberty is an application server runtime that is very flexible in how you can use it. It can be configured from a simple single-server, or it can be configured into a cross-platform, multi-server collective.

The goal of this material is to provide a "framework" of understanding how Liberty, and Liberty z/OS specifically, operates and can be used. Included in this framework is a set of "good practice" recommendations to help you get the most out of Liberty z/OS.
Overview and Key Concepts
    Liberty z/OS Key Concepts -- this deck is optional, depending on your starting knowledge of Liberty and Liberty z/OS. The purpose of this deck is to lay the foundation for some key concepts that play a central role in the more detailed good practices that follow.
    Good Practices Overview -- this deck provides a high-level view of Liberty z/OS and some of the good practices that have emerged from real-world use of Liberty z/OS.
Topology Design
    The goal of this unit is to review different approaches to server topology design.

Security Overview
    Security is always an important topic, and that is true with Liberty z/OS as well.

    In this unit we focus on three layers of security: file system security; z/OS server security; and Java application-layer security. We cover recommended good practices, and provide an understanding how z/OS Security Access Facility (SAF, the security interface provided with z/OS, behind which a security product such as IBM RACF runs) is used with Liberty z/OS.

Applications and Application Deployment
    The application programming interfaces (APIs) of Liberty are common and consistent across all the platforms supported by Liberty.

    In this unit we look at how applications are deployed to Liberty, and we look at the considerations for moving an application from WAS traditional to Liberty.

Collectives
    Collectives are a way of organizing individual Liberty servers into a logical collection for the purposes of administration and management.
    In this unit we review how collectives are constructed, and how z/OS SAF can be used for the security that operates under a collective.
    Note: this unit is still under construction. Check back for updates.

Operations, Monitoring, and Problem Determination
    Once you have Liberty z/OS servers created and running, you will want to operate them effectively, monitor them, and perform problem determination when issues arise.

    This unit is designed to provide a framework of understanding around how these are performed.
    Note: some sections this unit are still under construction. Check back for updates.

Other Resources

Credits
    The material here is the result of the efforts of many people: Jim Mulvey, David Follis, Mike Stephen, Jeff Mierzejewski, Keith Jabcuga, Gary Picher, Tim Kaczynski, Kevin Senior, Edward McCarthy.

    Please report any errors in the charts or speaker notes to dbagwell@us.ibm.com.



Classification:

Software

Category:

Planning and Design




Platform(s):

IBM System z Family

S/W Pillar(s):

IBM System z Software; WebSphere

O/S:

z/OS

Keywords:

Liberty z/OS Good Practices

The Techdocs Library
Is this your first visit to Techdocs (the Technical Sales Library)?

Learn more


Techdocs QuickSearch

: