Introduction to z/OS Basics

Chapter 14 WebSphere Application Server

WebSphere Application Server on z/OS

(Based on Version 5)

© 2006 IBM Corporation

 Chapter 14 WebSphere Application Server

Chapter objectives

Be able to:
 List the six qualities of the J2EE Application
model
 Give three reasons for running WebSphere
Application Server under z/OS
 Name three connectors to CICS, DB2, and
IMS

2 © 2006 IBM Corporation

 Chapter 14 WebSphere Application Server

Key terms in this chapter

 cell  J2EE
 CR  SR
 CGI  cluster
 EIS  node
 JMX

3 © 2006 IBM Corporation

 Chapter 14 WebSphere Application Server

Introduction to Web applications on z/OS

 Past:
– Many applications are tied to z/OS (CICS, DB2)
– New developments made on other platforms
 Now:
– Integrate both on z/OS

4 © 2006 IBM Corporation

 Chapter 14 WebSphere Application Server

Extending the web server

The Application Server has been thought of as an extension to

a Web server, consisting of 2 main components
A plugin for the Web server (HTTP Server) that will pass the
request to the actual Application Server.
and
The Application Server itself

HTTP Server Some Application

Servers have
built-in HTTP
support
Application Server

Web server plugin

5 © 2006 IBM Corporation

 Chapter 14 WebSphere Application Server

J2EE Application Model in z/OS

Same as on other platforms, following SDK:
 Functional
 Reliable
 Usable
 Efficient
 Maintainable
 Portable

6 © 2006 IBM Corporation

 Chapter 14 WebSphere Application Server

Running WebSphere Application Server for z/OS

 Basics of WebSphere on z/OS
 Consolidation of workloads
 WebSphere for z/OS Security
 Continuous availability
 Performance

7 © 2006 IBM Corporation

 Chapter 14 WebSphere Application Server

What is an Application Server

8 © 2006 IBM Corporation

 Chapter 14 WebSphere Application Server

J2EE Applications execute in

MVS Address Space(s)

9 © 2006 IBM Corporation

 Chapter 14 WebSphere Application Server

Java Virtual Machine in z/OS

bytecodes

z/OS
Java application

Address Java
Space
Virtual
Machine bytecodes Unicode
JVM
Shared Java code C statements

ASCII
Language Environment Shared C code
This layer has
the calls to the
platform specific C runtime library
SAF z/OS UNIX DFSMS code
net (C code) awt

WLM
HFS
ZFS
RACF SMH UNIX
MVS
Dataset System EBCDIC
DB Services
RRS
sockets X11
Posix interface
C runtime library

10 © 2006 IBM Corporation

 Chapter 14 WebSphere Application Server

JVM in z/OS LE
Process

LE
Java
Threads
Enclave
Java
Threads
Java C/C++ main
Heap Threads routine
Java
Threads
Java
Threads
Subroutine
Java
Threads
LE Heap
Storage
Thread stack JVM Enclave
Runtime specific
data area data
Thread stack
System
System Data shared
System
Thread
Thread
Thread between
enclaves
Method area JVM

Java program Java program and JVM executing in a

executing in a JVM z/OS LE Environment

11 © 2006 IBM Corporation

 Chapter 14 WebSphere Application Server

Enterprise Application Packaging

J2EE
Application Application
DD
Installed .EAR file
RAR

EJB Web Client

Module Module Module
.JAR file .WAR file .JAR file

Enterprise EJB HTML, Web Client Client

Servlet JSP
Bean DD GIF, etc. DD Class DD

DD = Deployment Descriptor

12 © 2006 IBM Corporation

 Chapter 14 WebSphere Application Server

J2EE Enterprise Application Architecture

1. 2.

3.

5.
4.

13 © 2006 IBM Corporation

 Chapter 14 WebSphere Application Server

WebSphere Application Server for z/OS

Organization based on concepts:
 Servers
 Nodes (and Node Agents): a logical grouping of
WebSphere-managed servers
 Cells: a grouping of Nodes

Within the address spaces, concept of CONTAINER

14 © 2006 IBM Corporation

 Chapter 14 WebSphere Application Server

Basic Model

Server
Web
browser HTTP Application Application
client Server server database

Admin
UI

15 © 2006 IBM Corporation

 Chapter 14 WebSphere Application Server

WebSphere Application Server for z/OS

 Conform Software Development Kit (SDK)
 Interoperates with other subsystems

SR
Application
Server = CR
Instance

CR = Controller Region
SR = Servant Region

16 © 2006 IBM Corporation

 Chapter 14 WebSphere Application Server

What is a “Standalone” Server

A "Standalone Server" is just that -- a single application server that is not
part of a Deployment Manager's cell. The name is a bit misleading
because in truth it's also a node and a cell:

Single
Because it's a application
cell, it has a server
There are things it can do and not do:
Daemon
Do
Use Admin Console
Install/run applications
Daemon Server Connect to data resources
CR CR SR Use for messaging

Not Do
Add more servers
Span MVS images
A cell, but not A node, but not Cluster
an ND cell a "managed"
Start/stop server from Admin

It's a very handy configuration for testing and development purposes ...

17 © 2006 IBM Corporation

 Chapter 14 WebSphere Application Server

WebSphere Base Application Server

18 © 2006 IBM Corporation

 Chapter 14 WebSphere Application Server

Administering a Base Application Server

Collection of:
Servlets
MVS System or LPAR Administration JSPs
Application HTML pages
GIF/JPG images
Cell EAR

Node Server
Daemon

CR CR A
SR
Standard
HTTP Web
Browser

Files (XML, properties HFS

and application) held in
the HFS structure

Important!
The administrative application
requires that only one "servant"
! (server region) is spawned. This is
due to sharing and locking issues. Administrative application
installed using batch process.
Thereafter, applications installed
using graphical interface of
administrative program

19 © 2006 IBM Corporation

 Chapter 14 WebSphere Application Server

Address Space Relationships

20 © 2006 IBM Corporation

 Chapter 14 WebSphere Application Server

HFS under the Base Application Server Node

21 © 2006 IBM Corporation

 Chapter 14 WebSphere Application Server

Small, Separate Environments

You can create as many of these things as you like, and they can be 100%
operationally and administratively isolated from one another:
MVS Image

Development
Even though they're on the
Daemon Server "Fred" same MVS image, their
CR CR SR
environments are separate
from one another:
Separate Mount Point and HFS
Isolation Separate JCL procedures
Development Separate TCP ports
"Mary"
Daemon Server Separate Admin Consoles
CR CR SR Separate Userids / Passwords
Start/Stop servers independently

Isolation

Functional This is one of the primary

Daemon Server Test Team
benefits of creating
CR CR SR
Standalone Servers

There's another ...

22 © 2006 IBM Corporation

 Chapter 14 WebSphere Application Server

23 © 2006 IBM Corporation

 Chapter 14 WebSphere Application Server

24 © 2006 IBM Corporation

 Chapter 14 WebSphere Application Server

New Administrative Console Look and Feel

25 © 2006 IBM Corporation

 Chapter 14 WebSphere Application Server

HFS under a Base Application Server Node

26 © 2006 IBM Corporation

 Chapter 14 WebSphere Application Server

Run customized Jobs to create Base App Server

27 © 2006 IBM Corporation

 Chapter 14 WebSphere Application Server

Creating First Base Application Server Node

28 © 2006 IBM Corporation

 Chapter 14 WebSphere Application Server

Base App Server Dialog Main Panel

----------------- WebSphere for z/OS Customization ------------------
Option ===> Appl: GA

Configure base Application Server node

Use this dialog to define WebSphere for z/OS variables and generate
customization jobs for your installation. Specify an option and press ENTER.

HLQ for WebSphere product data sets: WASV5GA

1 Allocate target data sets. The data sets will contain the WebSphere
customization jobs and data generated by the dialog.

2 Define variables. Define your installation-specific information for

WebSphere customization.

3 Generate customization jobs. Validate your customization variables

and generate jobs and instructions.

4 View instructions. View the generated customization instructions.

Options for WebSphere for z/OS Customization Variables

S Save customization variables. Save your WebSphere customization

variables in a data set for later use.

L Load customization variables. Load your WebSphere customization

variables from a data set.

29 © 2006 IBM Corporation

 Chapter 14 WebSphere Application Server

Single copy of JCL for Multiple Servers

//V5ACR PROC ENV=CU1X.NU1.SU1,Z=V5ACRZ V5ACR
// SET ROOT='/etc/wasv5'

//BBOCTL EXEC PGM=BBOCTL,REGION=0M,

// PARM='TRAP(ON,NOSPIE),ENVAR("_EDC_UMASK_DFLT=007") /'
//*
//BBOENV DD DDs
PATH='&ROOT/&ENV/was.env' V5ACRZ
//* Output
//*
// INCLUDE MEMBER=&Z
//CEEDUMP DD SYSOUT=*,SPIN=UNALLOC,FREE=CLOSE
//SYSOUT DD SYSOUT=*,SPIN=UNALLOC,FREE=CLOSE
//SYSPRINT DD SYSOUT=*,SPIN=UNALLOC,FREE=CLOSE
//*
//*Steplib Setup
//*
//STEPLIB DD DISP=SHR,DSN=WASV5GA.SBBOLD2
// DD DISP=SHR,DSN=WASV5GA.SBBOLOAD

30 © 2006 IBM Corporation

 Chapter 14 WebSphere Application Server

What was Generated by the Dialog?

 WASZOS.INSTALL.CNTL (FB)  WASZOS.INSTALL.DATA (VB)
–Installation Jobs EXECs
–Server runtime procedures Configuration files
–Misc. jobs & utilities
–Instructions

BBOCBRAJ
BBOCBRAK

BBOCTI00 Input
BBODEFR BBOSSINS
BBOCCINS
} step by step
instructions members
BBODMCCB
BBOERRLG BBOWCPY1 BBOWBMPT
BBOWBOWN BBOWSCMD
BBOINST
BBOWCPY2 BBOWBRAC BBOWSECA
BBOWCEA1 BBOWSEIA
BBOIPCSP
BBOWCTR BBOWCOPY BBOWSERA
BBOMCFG
BBOWCPYC BBOWSOAS
BBOWC2J BBOWCPYD BBOWUUID
BBOMCFGU
BBOWC2N BBOWCPYM BBOWVAA1
BBOMCFG2
BBOWC2JS BBOWVAA2
BBOMSGC
BBOWIAPP BBOWC2NS BBOWVAA3
BBOWE2AS BBOWVIHA
*BBOMSMF BBOWIVT BBOWNODA BBOWWAPA
BBOPROG
BBORRS BBOWTR BBOWSAAS

BBORRSLS BBOW5SH
BBOSCHED
BBOSSINS BBO5ACR
31 © 2006 IBM Corporation
BBO5ACRZ
 Chapter 14 WebSphere Application Server

Introducing the Deployment Manager

The Deployment Manager is a special kind of application server instance. The
administrative application runs in the Deployment Manager:
MVS System or LPAR MVS System or LPAR

DM

CR A
SR Browser

Server_A Server_C

CR SR CR SR

Server_B Server_D

CR SR CR SR

SYSA CF SYSB

HFS HFS

Before the Deployment Manager can manage application servers, those

application servers need to be grouped into something called "Nodes" ...

32 © 2006 IBM Corporation

 Chapter 14 WebSphere Application Server

Deployment Manager Node and Address Space Relationship

33 © 2006 IBM Corporation

 Chapter 14 WebSphere Application Server

WAS Network Deployment Overview

34 © 2006 IBM Corporation

 Chapter 14 WebSphere Application Server

35 © 2006 IBM Corporation

 Chapter 14 WebSphere Application Server

WebSphere on z/OS - continuous availability

• Vertical and Horizontal Cluster
MVS System or LPAR MVS System or LPAR
Servers are
clustered through
Daemon Daemon
Cell A CF
the administrative
interface.
CR CR
Any given server
may be a member
DM Node of only one cluster
at a time
CR A You can not have
Server_C be a
member of two
different clusters,
for example.
Node Agent Node Node Agent Node
Hybrid of vertical
and horizontal is
CR "Vertical" CR
permitted
Cluster
Two or more
servers in the
Server A Server D
same system
or LPAR
CR SR CR SR

Server B Server E

CR SR CR SR "Horizontal"
Cluster
Two or more
servers across
Server C Server F multiple nodes
(or systems)
CR SR CR SR

36 © 2006 IBM Corporation

 Chapter 14 WebSphere Application Server
WAS Cluster Load Balancing

37 © 2006 IBM Corporation

 Chapter 14 WebSphere Application Server

38 © 2006 IBM Corporation

 Chapter 14 WebSphere Application Server

Add Servers Through Admin Console

The Admin Console -- which runs in the Deployment Manager -- is used to
create server. DMGR instructs Node Agent to build server in config HFS.

"New"
Button

Pulldown list of nodes

will include those
"Managed Nodes"
you've already built

And then you'll have to do a little "MVS System Programmer work" to put
down some security stuff. We'll show you how that's all done later.

39 © 2006 IBM Corporation

 Chapter 14 WebSphere Application Server

Running WAS on z/OS - Performance

WebSphere uses three distinct functions of WLM:

 Routing
 Queuing
 Prioritizing

40 © 2006 IBM Corporation

 Chapter 14 WebSphere Application Server

Why WLM . . .
WebSphere Application
SR6
Server Instance
SR5
6 Service Classes:
6
SR4
1 5 SC=CB05
SR3
4 SC=CB04
SC=CB04
2 SR2
SR2

CR 3 SC=CB03
SC=CB03
SR1
5
IIOP
IIOP 2 SC=CB02

6 HTTP
HTTP 1 SC=IWEB01
SC=IWEB01
Mimimum = 1
SC=CB01
SC=CB01
3 Maximum >= 6

41 © 2006 IBM Corporation

 Chapter 14 WebSphere Application Server

Establish Service Level Objectives for different departments

42 © 2006 IBM Corporation

 Chapter 14 WebSphere Application Server

Application Environments

43 © 2006 IBM Corporation

 Chapter 14 WebSphere Application Server

WAS’ Enclave Characteristics

44 © 2006 IBM Corporation

 Chapter 14 WebSphere Application Server

Sample J C L

JTA OTS

45 © 2006 IBM Corporation

 Chapter 14 WebSphere Application Server

SDSF display ‘DA’

46 © 2006 IBM Corporation

 Chapter 14 WebSphere Application Server

Websphere - R R S / XA
OTS is the Object Transaction Service
- Provides the framework to run transactions on a single server, or across
multiple servers.
- It is designed to be interoperable with other OTS components.
- Provides very few applicaion level APIs accessible from J2EE components.
- Our OTS implementation is z/OS specific and lives entirely in native code.
- For more details about what OTS is, see the 3.x and 4.x STE resentations.
JTA is the Java Transaction API
- For WebSphere on z/OS, JTA sits "on top of" OTS.
- It is part of the J2EE specification, and as a result, supports the UserTransaction
API for J2EE applications, and other SPIs used by the EJB Container.
- Since JTA is java-specific, our java implementation lives mostly in java.
JTA is modeled on the XA Specification
- XA is an X/Open Group specification which describes how a resource should
communicate with a transaction manager. It's standardized through ISO.
- JTA includes a mapping of the XA specification (but not a full mapping).
- XA support is new for z/OS in 5.0
RRS is a z/OS specific transaction manager
- RRS can be though of as an entity which manages resources in a z/OS-specific way.
- RRS does not support the XA protocol, but does share some similarities which allow us
to merge both RRS and XA resources together in the same transaction.

47 © 2006 IBM Corporation

 Chapter 14 WebSphere Application Server

Intelligent Workload Management

48 © 2006 IBM Corporation

 Chapter 14 WebSphere Application Server

zSeries Differentiation with WAS on Z

49 © 2006 IBM Corporation

 Chapter 14 WebSphere Application Server

Web Servers in v6

 Web servers can now be defined in a WebSphere Application

Server topology

 Allows association of the application to one or more defined Web servers

– This allows generation of custom plug-in configuration files for a specific
Web server

 Allows administration of the web server via the admin console

50 © 2006 IBM Corporation

 Chapter 14 WebSphere Application Server

Integrated Performance Viewer

51 © 2006 IBM Corporation

 Chapter 14 WebSphere Application Server

wsadmin: How does it work?

 wsadmin acts as an interface to MBeans (JMX management objects)

 Objects perform different operations

– AdminConfig
– AdminApp
– AdminControl
– AdminTask MBean
ask
– Help
innApp
T MBean
d mmi
A d
 Separation between AdminConfig MBean
Script wsadmin
Configuration and AdminControl
He
Control lp MBean

MBean

52 © 2006 IBM Corporation

 Chapter 14 WebSphere Application Server

wsadmin Examples
 Installing an application
– Using jacl
• wsadmin.sh –c “$AdminApp install /tmp/MyApp.ear {-appname
MyApp}”
– Using Jython
• wsadmin.sh –lang jython –c “$AdminApp.install
(‘/tmp/MyApp.ear’,’ [-appname MyApp]’ )”
 Running scripts
– Running a jacl script
• wsadmin.sh –f appinst.jacl
– Running a jython script
• wsadmin.sh –lang jython –f appinst.py

53 © 2006 IBM Corporation

 Chapter 14 WebSphere Application Server

Application Server Configuration on z/OS

• Base Server Node
Cell

Location Service Daemon z/OS functions

(BBODMNB) UNIX System Services
TCP/IP
FTP
Controller RRS
Workload Management
Language Environment
Security Server
ARM
Application server node IMS/TM
CICS/TS
MQ
J2EE scalable
application server
(server1) JMS HTTP
server internal
transport
v5 run-time
environment

Controller Servant

HTTP server

54 © 2006 IBM Corporation

 Chapter 14 WebSphere Application Server

Application Server Configuration on z/OS

• Network Deployment Manager
Cell

Location Service Node 2: Application server z/OS functions

Daemon
UNIX System
(BBODMNB)
Node agent JMS server Services
(BBON001) (BBOJ001) TCP/IP
FTP
Controller RRS
Controller Controller Workload
Management
Language
Environment
Security Server
Node 1: Deployment manager ARM
J2EE scalable IMS/TM
application server HTTP
(server1) CICS/TS
Deployment manager internal MQ
(BBODMGR) transport

v5 run-time
environment
Controller Controller Servants

55 © 2006 IBM Corporation

 Chapter 14 WebSphere Application Server

Connectors for Enterprise Information Systems

Some considerations:
 Expensive
 Must be secured
 Need to perform well
 Must be monitorable
 Methods needed
 Quality of devices

56 © 2006 IBM Corporation

 Chapter 14 WebSphere Application Server

Mainframe Connectors

 CICS Transaction Gateway

 IMS Connect
 DB2 JDBC

57 © 2006 IBM Corporation

 Chapter 14 WebSphere Application Server

Basic Architecture of an connector to an EIS

z/OS

WebSphere RACF RRS

Application Server

Server A

RA C EIS/DB

memory
to
memory

C=connector
RA=resource adapter

58 © 2006 IBM Corporation

 Chapter 14 WebSphere Application Server

59 © 2006 IBM Corporation

 Chapter 14 WebSphere Application Server

60 © 2006 IBM Corporation

 Chapter 14 WebSphere Application Server

61 © 2006 IBM Corporation

 Chapter 14 WebSphere Application Server

62 © 2006 IBM Corporation

 Chapter 14 WebSphere Application Server

63 © 2006 IBM Corporation

 Chapter 14 WebSphere Application Server

64 © 2006 IBM Corporation

 Chapter 14 WebSphere Application Server

WebSphere on z/OS - continuous availability

• WebSphere with Sysplex Distributor
SYSPLEX

z/OS cluster

RACF RRS
WebSphere
Application Server

Connection
RA Address EIS/DB
space

TCP/IP

memory
to
SD memory

RACF RRS
WebSphere
Application Server

Connection
RA Address EIS/DB
space

z/OS

65 © 2006 IBM Corporation

 Chapter 14 WebSphere Application Server

66 © 2006 IBM Corporation

 Chapter 14 WebSphere Application Server

67 © 2006 IBM Corporation

 Chapter 14 WebSphere Application Server

68 © 2006 IBM Corporation

 Chapter 14 WebSphere Application Server

JDBC Drivers

69 © 2006 IBM Corporation

 Chapter 14 WebSphere Application Server

JDBC Drivers for zOS

70 © 2006 IBM Corporation

 Chapter 14 WebSphere Application Server

Connectivity for a Local DB2

71 © 2006 IBM Corporation

 Chapter 14 WebSphere Application Server

Connectivity for a Remote DB2

72 © 2006 IBM Corporation

 Chapter 14 WebSphere Application Server

Local T2 Connection / Remote T4 Connection

73 © 2006 IBM Corporation

 Chapter 14 WebSphere Application Server

Connectivity Options

74 © 2006 IBM Corporation

 Chapter 14 WebSphere Application Server

VSAM Connector for z/OS Puts VSAM Data into the WebSphere Picture
Tier-0: Tier-1: Tier-2: Tier-3:
Client-Side Server-Side Server-Side Server-Side
Presentation Presentation Business Logic Data Logic

Client Container Servlet Container EJB Container

JSP EJB
HTTP / HTTPS

RMI / IIOP
Servlet VSAM

JDBC
DATA
RMI/IIOP

RMI/IIOP

RMI/IIOP
Java Java Java
JDBC

JDBC

JDBC
JNDI

JNDI

JNDI
JTA

JTA

JTA
Mail Mail Mail
JAF JAF JAF Data
System
J2EE Server Core J2EE Server Core J2EE Server Core

Enterprise Archive (EAR)

Client JAR Web Archive (WAR) EJB JAR
EJB EJB
JSP Servlet JSP Servlet EJB EJB EJB EJB

Class Class JSP Servlet JSP Servlet

EJB EJB

Class
Class Class Class

75 © 2006 IBM Corporation

 Chapter 14 WebSphere Application Server

76 © 2006 IBM Corporation

 Chapter 14 WebSphere Application Server

77 © 2006 IBM Corporation

 Chapter 14 WebSphere Application Server

78 © 2006 IBM Corporation

 Chapter 14 WebSphere Application Server

79 © 2006 IBM Corporation

 Chapter 14 WebSphere Application Server

Summary

 In this chapter, you learned to:

– List the six qualities of the J2EE Application model
– List three reasons for running WebSphere Application
Server under z/OS
– Name three connectors to CICS, DB2, and IMS

80 © 2006 IBM Corporation