Home About Courses Schedule Services Webinars Contact Search

CICS Transaction Server Setup of WAS Liberty Profile


Duration: 1 day

Method: Instructor-led. Hands-on Exercises.

Price: $600.00

Course Code: CI5075


This course will be of interest to CICS system administration and technical support personnel. It does include some hands-on work in the basic setup of WAS LP under CICS TS.


You have been working in CICS TS administration for a while now, but have never implemented any of the newer modernization features. This course is ideal for you. We will cover what WebSphere Application Server Liberty Profile is to mainframe modernization, plus its setup and use within your CICS TS regions. First we will cover just what WAS LP contains and its purpose in the realm of application deployment. Next we will get into the details of the various configuration files and their location within the CICS product install. Not to worry if you have never used UNIX System Services, we plan to provide the necessary basics for you to work with USS. Then we will cover the configuration options and potential impact on your environment. We then proceed to startup CICS with the basic WAS LP server enabled, includes configuration of application deployment facilities. Then we move to using z/OS Explorer to deploy a predefined application. Finally we will cover some basic performance and problem resolution topics. All-in-all one complete day effort to implement Liberty profile.


Upon successful completion of this course, the student will be able to:

  • Understand the components of WAS LP.
  • Determine what it might take to implement WAS LP at your site.
  • Implement the base WAS LP in our test CICS TS environments.
  • Gain some basic knowledge about how your developers will deploy their applications.


Your current CICS TS system administration experience, plus a little of the current terminology.


  • I. WebSphere Application Server Liberty Profile Overview – This section provides a brief overview of the current WAS LP product and features.
    • What is WebSphere Application Server Liberty Profile?
    • What is contained in the basic product supplied with CICS TS.
    • What are the other features that can be configured into WAS LP while under CICS TS.
  • II. Making CICS regions ready to accept and configure WAS LP – This section covers the items you need to setup or verify before you configure and bring up WAS LP for the first time.
    • Necessary updates and additions to the CICS JCL and system initialization parameters
    • Necessary zFS file system requirements
    • Necessary TCPIP updates
    • Necessary security updates
    • Setting up the LE environment options
    • Setting up the JVM environment options
  • III. WebSphere Application Server Liberty Profile Configuration – This section provides a look into the variables and resources necessary to bring up the server for the first time.
    • Setting up the WAS LP profile options
    • Necessary updates to the USS profile
    • Defining the JVMSERVER resource to CICS TS
    • Defining BUNDLE resources to CICS TS
    • Bring up WAS LP for the first time and verify its implementation
    • A look at server.xml and adding features
    • Configure the web server plug-in and verify its operation
  • IV. z/OS Explorer and working with WAS LP – This section provides a look into using z/OS Explorer to deploy applications into WAS LP running under CICS TS.
    • Configure z/OS Explorer for connection and use with the mainframe environment
    • Setup and deploy the sample CICS application through z/OS Explorer
    • Test the deployed application through WAS LP
  • V. Basic performance and problem resolution – This section provides a look into some basic performance tuning options as well as some basic problem resolution options.
    • CICS TS options affecting performance
    • JDBC and z/OS performance options
    • Symptoms and actions for problem resolution
    • Message and log file importance to debugging
    • JVM dumps and traces
    • Debugging tools available for use with the JVM