Date post: | 22-Dec-2015 |
Category: |
Documents |
View: | 221 times |
Download: | 2 times |
Introduction to z/OS Basics
© 2006 IBM Corporation
Chapter 14 WebSphere Application Server
WebSphere Application Server on z/OS(Based on Version 5)
Chapter 14 WebSphere Application Server
© 2006 IBM Corporation2
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
Chapter 14 WebSphere Application Server
© 2006 IBM Corporation3
Key terms in this chapter
cell
CR
CGI
EIS
JMX
J2EE
SR
cluster
node
Chapter 14 WebSphere Application Server
© 2006 IBM Corporation4
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
Chapter 14 WebSphere Application Server
© 2006 IBM Corporation5
Extending the web server
HTTP Server
Web server plugin
Application Server
Some Application Servers have built-in HTTP support
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. andThe Application Server itself
Chapter 14 WebSphere Application Server
© 2006 IBM Corporation6
J2EE Application Model in z/OS
Same as on other platforms, following SDK:
Functional
Reliable
Usable
Efficient
Maintainable
Portable
Chapter 14 WebSphere Application Server
© 2006 IBM Corporation7
Running WebSphere Application Server for z/OS
Basics of WebSphere on z/OS
Consolidation of workloads
WebSphere for z/OS Security
Continuous availability
Performance
Chapter 14 WebSphere Application Server
© 2006 IBM Corporation8
What is an Application Server
Chapter 14 WebSphere Application Server
© 2006 IBM Corporation9
J2EE Applications execute in MVS Address Space(s)
Chapter 14 WebSphere Application Server
© 2006 IBM Corporation10
platform specificcode
(C code)
Shared C code
Java application
Shared Java code
awt
Posix interfaceC runtime library
X11
net
sockets
bytecodes
bytecodes
This layer has the calls to theC runtime library
C statements
Unicode
ASCII
EBCDIC
JavaVirtual
Machine
UNIXSystemServices
SAF DFSMS
AddressSpace
z/OS
SMH
WLM
RRS
HFS
MVSDataset
ZFS
DB
z/OS UNIX
Language Environment
RACF
JVM
Java Virtual Machine in z/OS
Chapter 14 WebSphere Application Server
© 2006 IBM Corporation11
Heap
JVM
Runtime data area
Method area
Thread stack
Thread stack
Java program and JVM executing in a z/OS LE Environment
Java program executing in a JVM
Process
Enclave specificdata
Data sharedbetween enclaves
System Thread
System Thread
System Thread
JVM
LE Enclave
C/C++ main routine
Subroutine
LE Heap Storage
JavaThreadsJava
ThreadsJavaThreads
JavaThreadsJava
ThreadsJavaThreads
JVM in z/OS LE
Chapter 14 WebSphere Application Server
© 2006 IBM Corporation12
Enterprise Application Packaging
EJB DD
Web DD
Client DD
HTML, GIF, etc.
Application DD
Enterprise Bean
Client ClassServlet JSP
EJB Module .JAR file
Web Module
.WAR file
Client Module .JAR file
DD = Deployment Descriptor
J2EE Application
.EAR fileInstalledRAR
Chapter 14 WebSphere Application Server
© 2006 IBM Corporation13
J2EE Enterprise Application Architecture
1. 2.
3.
4.
5.
Chapter 14 WebSphere Application Server
© 2006 IBM Corporation14
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
Chapter 14 WebSphere Application Server
© 2006 IBM Corporation15
HTTP Server
Application database
Application server
Admin UI
Web browser
client
Server
Basic Model
Chapter 14 WebSphere Application Server
© 2006 IBM Corporation16
WebSphere Application Server for z/OS
Conform Software Development Kit (SDK)
Interoperates with other subsystems
CR = Controller RegionSR = Servant Region
ApplicationServer =Instance
CR
SR
Chapter 14 WebSphere Application Server
© 2006 IBM Corporation17
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:
CR SR
Server
CR
Daemon
Single application
server
A node, but not a "managed"
A cell, but not an ND cell
Because it's a cell, it has a
Daemon
There are things it can do and not do:
DoUse Admin ConsoleInstall/run applicationsConnect to data resourcesUse for messaging
Not DoAdd more serversSpan MVS imagesClusterStart/stop server from Admin
It's a very handy configuration for testing and development purposes ...
What is a “Standalone” Server
Chapter 14 WebSphere Application Server
© 2006 IBM Corporation18
WebSphere Base Application Server
Chapter 14 WebSphere Application Server
© 2006 IBM Corporation19
Administrative application installed using batch process. Thereafter, applications installed using graphical interface of administrative program
MVS System or LPAR
Daemon
CR
Node
Cell
Server
CR SRA
Administration Application
EAR
Collection of:ServletsJSPsHTML pagesGIF/JPG images
Files (XML, properties and application) held in
the HFS structure
HFS
Standard Web
BrowserHTTP
The administrative application requires that only one "servant"
(server region) is spawned. This is due to sharing and locking issues.
Important!
!
Administering a Base Application Server
Chapter 14 WebSphere Application Server
© 2006 IBM Corporation20
Address Space Relationships
Chapter 14 WebSphere Application Server
© 2006 IBM Corporation21
HFS under the Base Application Server Node
Chapter 14 WebSphere Application Server
© 2006 IBM Corporation22
You can create as many of these things as you like, and they can be 100% operationally and administratively isolated from one another:
CR SR
Server
CR
Daemon
CR SR
Server
CR
Daemon
CR SR
Server
CR
Daemon
MVS Image
Development"Fred"
Development"Mary"
Functional Test Team
Even though they're on the same MVS image, their environments are separate from one another:
Separate Mount Point and HFS
Separate JCL procedures
Separate TCP ports
Separate Admin Consoles
Separate Userids / Passwords
Start/Stop servers independently
Isolation
Isolation
This is one of the primary benefits of creating Standalone Servers
There's another ...
Small, Separate Environments
Chapter 14 WebSphere Application Server
© 2006 IBM Corporation23
Chapter 14 WebSphere Application Server
© 2006 IBM Corporation24
Chapter 14 WebSphere Application Server
© 2006 IBM Corporation25
New Administrative Console Look and Feel
Chapter 14 WebSphere Application Server
© 2006 IBM Corporation26
HFS under a Base Application Server Node
Chapter 14 WebSphere Application Server
© 2006 IBM Corporation27
Run customized Jobs to create Base App Server
Chapter 14 WebSphere Application Server
© 2006 IBM Corporation28
Creating First Base Application Server Node
Chapter 14 WebSphere Application Server
© 2006 IBM Corporation29
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.
Chapter 14 WebSphere Application Server
© 2006 IBM Corporation30
Single copy of JCL for Multiple Servers
//V5ACR PROC ENV=CU1X.NU1.SU1,Z=V5ACRZ // SET ROOT='/etc/wasv5' //BBOCTL EXEC PGM=BBOCTL,REGION=0M, // PARM='TRAP(ON,NOSPIE),ENVAR("_EDC_UMASK_DFLT=007") /' //BBOENV DD PATH='&ROOT/&ENV/was.env' // INCLUDE MEMBER=&Z
//* //* Output DDs //* //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
V5ACR
V5ACRZ
Chapter 14 WebSphere Application Server
© 2006 IBM Corporation31
What was Generated by the Dialog? WASZOS.INSTALL.CNTL (FB)
–Installation Jobs
–Server runtime procedures
–Misc. jobs & utilities
–Instructions
WASZOS.INSTALL.DATA (VB)EXECsConfiguration files
BBOCBRAJ BBOCBRAK BBOCTI00 BBODEFR BBODMCCB BBOERRLG BBOINST BBOIPCSP BBOMCFG BBOMCFGU BBOMCFG2 BBOMSGC BBOMSMF BBOPROG BBORRS BBORRSLSBBOSCHED BBOSSINS BBOTCPIP BBOUNIN BBOWCFRM BBOWCHFS
BBOWCPY1 BBOWCPY2 BBOWCTR BBOWC2J BBOWC2N BBOWIAPP BBOWIVT BBOWTR BBOW5SH BBO5ACR BBO5ACRZ BBO5ASR BBO5ASRZBBO5DMN BBO5DMNZ
BBOWBMPTBBOWBOWNBBOWBRACBBOWCEA1BBOWCOPYBBOWCPYCBBOWCPYDBBOWCPYMBBOWC2JSBBOWC2NSBBOWE2ASBBOWNODABBOWSAAS
BBOWSCMDBBOWSECABBOWSEIABBOWSERABBOWSOASBBOWUUIDBBOWVAA1BBOWVAA2BBOWVAA3BBOWVIHABBOWWAPA
BBOSSINSBBOCCINS}
step by stepinstructions
*
Input members
Chapter 14 WebSphere Application Server
© 2006 IBM Corporation32
Server_A
CR SR
Server_B
CR SR
Server_C
CR SR
Server_D
CR SR
SYSA SYSBCF
MVS System or LPAR MVS System or LPAR
HFSHFS
The Deployment Manager is a special kind of application server instance. The administrative application runs in the Deployment Manager:
DM
CR SRA Browser
Before the Deployment Manager can manage application servers, those application servers need to be grouped into something called "Nodes" ...
Introducing the Deployment Manager
Chapter 14 WebSphere Application Server
© 2006 IBM Corporation33
Deployment Manager Node and Address Space Relationship
Chapter 14 WebSphere Application Server
© 2006 IBM Corporation34
WAS Network Deployment Overview
Chapter 14 WebSphere Application Server
© 2006 IBM Corporation35
Chapter 14 WebSphere Application Server
© 2006 IBM Corporation36
WebSphere on z/OS - continuous availability• Vertical and Horizontal Cluster
MVS System or LPARMVS System or LPAR
"Vertical"Cluster Two or moreservers in thesame systemor LPAR
DM
CR AA
Node Agent
CR
CR SR
Server A
CR SR
Server B
Node
Node
CR SR
Server C
Daemon
CR
Daemon
CR
Node Agent
CR
CR SR
Server D
CR SR
Server E
Node
CR SR
Server F
Cell A CF
"Horizontal" Cluster Two or moreservers across multiple nodes (or systems)
Servers are clustered through the administrative interface.
Any given server may be a member of only one cluster at a time
You can not have Server_C be a member of two different clusters, for example.
Hybrid of vertical and horizontal is permitted
Chapter 14 WebSphere Application Server
© 2006 IBM Corporation37
WAS Cluster Load Balancing
Chapter 14 WebSphere Application Server
© 2006 IBM Corporation38
Chapter 14 WebSphere Application Server
© 2006 IBM Corporation39
Add Servers Through Admin ConsoleThe 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.
Chapter 14 WebSphere Application Server
© 2006 IBM Corporation40
Running WAS on z/OS - Performance
WebSphere uses three distinct functions of WLM:
Routing
Queuing
Prioritizing
Chapter 14 WebSphere Application Server
© 2006 IBM Corporation41
Why WLM . . .
2
1
3
4
6
5
WebSphere ApplicationServer Instance
IIOPIIOP
CR
HTTPHTTP
SR1SR1
SC=CB01SC=CB01
1
SR2SR2
SC=IWEB01SC=IWEB01
2
SR3SR3
SC=CB02SC=CB02
3
SR4SR4
SC=CB03SC=CB03
4
SR5SR5
SC=CB04SC=CB04
5
SR6SR6
SC=CB05SC=CB05
6
Mimimum = 1
Maximum >= 6
6 Service Classes:
Chapter 14 WebSphere Application Server
© 2006 IBM Corporation42
Establish Service Level Objectives for different departments
Chapter 14 WebSphere Application Server
© 2006 IBM Corporation43
Application Environments
Chapter 14 WebSphere Application Server
© 2006 IBM Corporation44
WAS’ Enclave Characteristics
Chapter 14 WebSphere Application Server
© 2006 IBM Corporation45
JTA OTS
Sample J C L
Chapter 14 WebSphere Application Server
© 2006 IBM Corporation46
SDSF display ‘DA’
Chapter 14 WebSphere Application Server
© 2006 IBM Corporation47
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.
Chapter 14 WebSphere Application Server
© 2006 IBM Corporation48
Intelligent Workload Management
Chapter 14 WebSphere Application Server
© 2006 IBM Corporation49
zSeries Differentiation with WAS on Z
Chapter 14 WebSphere Application Server
© 2006 IBM Corporation50
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
Chapter 14 WebSphere Application Server
© 2006 IBM Corporation51
Integrated Performance Viewer
Chapter 14 WebSphere Application Server
© 2006 IBM Corporation52
wsadmin: How does it work? wsadmin acts as an interface to MBeans (JMX management objects)
Objects perform different operations– AdminConfig– AdminApp – AdminControl– AdminTask – Help
Separation between
Configuration and
Control
wsadmin
MBean
MBean
MBean
Help
AdminApp
AdminConfig
AdminControlMBean
ScriptScript
MBean
AdminT
ask
Chapter 14 WebSphere Application Server
© 2006 IBM Corporation53
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
Chapter 14 WebSphere Application Server
© 2006 IBM Corporation54
Application Server Configuration on z/OS• Base Server Node
Location Service Daemon(BBODMNB)
Controller
Application server node
Cell
J2EE scalable application server (server1) JMS
server
HTTPinternal
transport
Controller Servant
v5 run-timeenvironment
HTTP server
z/OS functionsUNIX System ServicesTCP/IPFTPRRSWorkload ManagementLanguage EnvironmentSecurity ServerARMIMS/TMCICS/TSMQ
Chapter 14 WebSphere Application Server
© 2006 IBM Corporation55
Application Server Configuration on z/OS• Network Deployment Manager
Cell
Location Service Daemon(BBODMNB)
Controller
z/OS functionsUNIX System ServicesTCP/IPFTPRRSWorkload ManagementLanguage EnvironmentSecurity ServerARMIMS/TMCICS/TSMQ
Node 1: Deployment manager
Deployment manager(BBODMGR)
Controller
Node 2: Application server
Node agent(BBON001)
Controller
JMS server(BBOJ001)
Controller
J2EE scalable application server (server1)
Controller Servants
HTTPinternal
transport
v5 run-timeenvironment
Chapter 14 WebSphere Application Server
© 2006 IBM Corporation56
Connectors for Enterprise Information Systems
Some considerations:
Expensive
Must be secured
Need to perform well
Must be monitorable
Methods needed
Quality of devices
Chapter 14 WebSphere Application Server
© 2006 IBM Corporation57
Mainframe Connectors
CICS Transaction Gateway
IMS Connect
DB2 JDBC
Chapter 14 WebSphere Application Server
© 2006 IBM Corporation58
Basic Architecture of an connector to an EIS
WebSphereApplication Server
Server A
RA EIS/DB
RACF RRS
z/OS
C
memory to
memory
C=connectorRA=resource adapter
Chapter 14 WebSphere Application Server
© 2006 IBM Corporation59
Chapter 14 WebSphere Application Server
© 2006 IBM Corporation60
Chapter 14 WebSphere Application Server
© 2006 IBM Corporation61
Chapter 14 WebSphere Application Server
© 2006 IBM Corporation62
Chapter 14 WebSphere Application Server
© 2006 IBM Corporation63
Chapter 14 WebSphere Application Server
© 2006 IBM Corporation64
Chapter 14 WebSphere Application Server
© 2006 IBM Corporation65
WebSphere on z/OS - continuous availability • WebSphere with Sysplex Distributor
WebSphereApplication Server
RARAConnection
Addressspace
EIS/DB
RACF RRS
WebSphereApplication Server
RARAConnection
Addressspace
EIS/DB
RACF RRS
clusterz/OS
z/OS
SDSD
SYSPLEX
TCP/IP
memoryto
memory
Chapter 14 WebSphere Application Server
© 2006 IBM Corporation66
Chapter 14 WebSphere Application Server
© 2006 IBM Corporation67
Chapter 14 WebSphere Application Server
© 2006 IBM Corporation68
Chapter 14 WebSphere Application Server
© 2006 IBM Corporation69
JDBC Drivers
Chapter 14 WebSphere Application Server
© 2006 IBM Corporation70
JDBC Drivers for zOS
Chapter 14 WebSphere Application Server
© 2006 IBM Corporation71
Connectivity for a Local DB2
Chapter 14 WebSphere Application Server
© 2006 IBM Corporation72
Connectivity for a Remote DB2
Chapter 14 WebSphere Application Server
© 2006 IBM Corporation73
Local T2 Connection / Remote T4 Connection
Chapter 14 WebSphere Application Server
© 2006 IBM Corporation74
Connectivity Options
Chapter 14 WebSphere Application Server
© 2006 IBM Corporation75
EJBEJB
Servlet Container EJB Container
ServletServlet
JSPJSP
Data System
J2EE Server Core
Enterprise Archive (EAR)
JN
DI
JTA
RM
I/IIOP
JD
BC
JavaMail
JAF
JN
DI
JTA
RM
I/IIOP
JD
BC
JavaMail
JAF
HT
TP
/ HT
TP
S
RM
I / IIOP
Tier-1: Server-Side Presentation
Tier-0: Client-Side
Presentation
Tier-2: Server-Side
Business Logic J
DB
C
Tier-3: Server-Side Data Logic
J2EE Server Core
JN
DI
JTA
RM
I/IIOP
JD
BC
JavaMail
JAF
Client Container
J2EE Server Core
EJB JAREJB
EJBEJB
EJBEJB
EJB EJBEJB
Web Archive (WAR)JSPJSP ServletServlet JSPJSP ServletServlet
Client JAR
ClassClass ClassClass ClassClass
VSAMDATA
VSAM Connector for z/OS Puts VSAM Data into the WebSphere Picture
Chapter 14 WebSphere Application Server
© 2006 IBM Corporation76
Chapter 14 WebSphere Application Server
© 2006 IBM Corporation77
Chapter 14 WebSphere Application Server
© 2006 IBM Corporation78
Chapter 14 WebSphere Application Server
© 2006 IBM Corporation79
Chapter 14 WebSphere Application Server
© 2006 IBM Corporation80
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