Welcome to:

WebSphere Application Server

Architectural Components
Unit Objectives
After completing this unit, you should be able to:
•Review the architectural components of WebSphere
Application Server
•Describe JCA, JDBC Providers, Data sources and
Persistence manager
•Describe the role of Virtual Hosts
•Describe WebSphere Application Server’s Security Services
implementation
•Describe how JMX supports distributed administration
•Describe Web Services, Web Services Gateway and the
UDDI Registry
Runtime Architecture for Network Deployment
Node
Web Browser Application Server JVM
Client
Web Container
HTTP Server
Embedded Web
WebSphere
Load Balancer HTTP Server Modules
Plug-in

Application EAR
Client Container EJB Container
EJB
Java
Modules
Application Admin
Service
J2C Container
Resource Application
Admin
wsadmin Adapter Database
Console Modules

Deployment Manager Name Service (JNDI) Session Management Session

Database
Admin
Security Service
Application
Admin
Name
Service
Service File Transfer JMS Server JMS Service
Admin
(JNDI) Application Service

Node
Node Agent Name Service (JNDI)
Admin
Service Configuration
Master (XML Files)
Configuration
(XML Files)
Java Connection Architecture (JCA)

J2EE Server Runtime

Resource Adapter EIS
J2EE
for the EIS CICS
Component (CICS)

Common
J2EE Client Resource Adapter EIS
Component for the EIS IMS
Interface
(IMS)
API

J2EE
Component Resource Adapter
for the EIS SAP
EIS
Included with WebSphere (SAP)

Provided by EIS vendor

or Third Party vendor
JDBC Providers
•Provide the JDBC driver implementation for database access
–Type 2 JDBC Drivers (Thick)
•Requires the database client software on the client node to connect to
the database server
–Type 3 JDBC Drivers (Net protocol)
•Require server side code to map net protocol to native database
–Type 4 JDBC Drivers (Native protocol)
•Connect directly to the database using its native protocol
•XA Drivers support transaction recovery

Client Node

JNDI Connection
Connection
Pool
Pool
JDBC Database
Database
Client
JDBC Driver Server
DataSource
Data Sources
•Data Sources can improve performance and portability for
database access
–Standard and XA data sources
–V4.0 data sources supported for J2EE 1.2 and EJB 1.1
–V5.0 data sources for EJB 2.0 and Servlet 2.3 applications
•V5.0 Connection pooling is provided by two parts:
–J2C connection manager
–Relational resource adapter
Relational Resource
Adapter
Application

Datasource
Connection
Connection
Pool
Pool
Connection Database
Factory

J2C Connection
Manager
Persistence Manager
•Support EJB 2.0 Container Managed Persistence (CMP)
requirements
–New EJB 2.0 CMP persistence model
–Abstract persistence schema
–Relationships
–Dependent values
–EJB QL Query
•Support for extended persistence options
–Inheritance
–Data caching
–Advanced locking and pre-fetch mechanisms
•Provide architectural foundation for supporting different back-
ends
–JDBC
–SQLJ
–Non-relational adapters
Persistence Manager – Architecture
•Uses JCA under the covers
–Extends the range of potential data sources beyond JDBC
–Support for different back-end mechanisms
•Relies on "concrete bean" to provide implementation of data
access requests
–Generated by deployment tools

Abstract
Concrete BMP JDBC
CMP
Bean Bean applications
Bean Container
J2C CCI

JCA Persistence
Manager
Resource
Adapter
JDBC Adapter SQLJ Adapter

Enterprise Only
EIS (CICS, IMS, ...)
Possible future implementations
RDB
Persistence Manager - Caching
•Improve the scalability and performance of CMP beans
•Caching Mechanisms
–Data cache
•Holds the actual data entries
•Supports findByPrimaryKey-methods and EJB hydration
–Association cache
•Describes the associations (i.e., the composition structure) between the
data entries
•Supports foreign key based finder
Container
methods that are generated for
relationship traversal
•Caching mechanisms at the Core
basis of "value add" features Persistence
Manager
Cache Dynamic
Query
–Access intent
•WebSphere Application Server
–Dynamic Query, Adapter
Dynamic Access Intent...
•WebSphere Enterprise
Datastore Connection
Manager
Name Service
•Provides a JNDI name space
•Registers all EJB and J2EE resources (example: JDBC
Providers, JMS, J2C, URL and JavaMail) that are hosted by
the application server
•There is one name server per application server
Node 3

Deployment Manager
lookup
JNDI Client 9809 Name space

lookup
lookup

Node 1 Node 2
Node Agent Node Agent

2809 Name space Name space 2809

Application Server Application Server Application Server

9810 Name space Name space 9811 9810 Name space

Security Services
•Each application server JVM hosts a number of security
services
•The services use security settings held in the configuration
repository
•Provides authentication and authorization functions
Virtual Hosts
•Configuration that enables a host machine to resemble
multiple host machines
–Allows one machine to support multiple applications
–Associated with the cell not an single node
–Enables plug-in to route requests to the correct servers
•Each virtual host has a logical name and:
–One or more host aliases
•Each alias is a host name and port combination (allows wildcards)
•For example: *:80, *:443, *:9080, *:9090
–MIME type mappings
•There are two default virtual hosts
–default_host - used for accessing the default applications
•example: http://localhost:9080/snoop
–admin_host - used for accessing the administrative console
•example: http://localhost:9090/admin
JMX - Java Management Extensions
•Framework oriented at the management of applications and
resources
•Your application or resources can be "exposed" to remote
and local management tools
•Framework allows a provider to implement functions such as:
–listing configuration settings
–editing of configuration settings
•Also allows management applications to monitor events such
as:
–startup of an application server
–shutdown of an enterprise application
•Architectural importance
–Deployment Manager, Node Agent and Managed Servers
are built on this framework
WebSphere Application Server JMX Big Picture
Clients, Multi-cell
management and other EMS
Node 1

Deployment Manager

MBean JMX Configuration

Server Connector Repository Service
MBeans Master Admin
MBean MBean MBeans Repository
Proxy Proxy XML
es files
n od
r
o the
To Node Agent

MBean JMX
Server Connector Configuration
Distribution Service
MBeans
MBean MBean MBeans
er Proxy Proxy
oth ion
To licat
app vers
s er Application Server

MBean JMX EAR

Server Connector files Local Node
Repository
MBeans XML
files
MBeans
Edge Components
•WebSphere Application Server Network Deployment contains the
following Edge Component functionality:
– Load Balancer
– Caching Proxy
•Edge Components install separately from WebSphere Application
Server
•Load Balancer is responsible for balancing the load across multiple
servers that can be within either Local Area Network or Wide Area
Network
•Caching Proxy’s purpose is to reduce network congestion within an
Enterprise by offloading security / content delivery from Web servers
and Application Servers

Cluster of Load
Clients Balanced Servers
Load
Balancer
Web Services Engine
•Web Services Engine is actually the implementation of many APIs for
additional services.
•“It” does not stand by itself as a separate viable component
•Web Services are provided as a set of APIs in cooperation with J2EE
applications
•The following specifications are implemented:
– SOAP (Simple Object Access Protocol)
– WSDL (Web Services Description Language)
– UDDI (Universal Description, Discovery and Integration)
– WSIF (Web Services Invocation Framework)

UDDI Registry

Service bindingTemplate
Type

Service Interface
Web Service
Definition WSDL
Application
Document
UDDI Registry
•The registry is essential for Web services brokering
•Contains a “list” of services that are available
•The registry enables an enterprise to run its own “private”
Web services broker or provide Web services to the world
outside the enterprise
•The WebSphere 5.0 UDDI Registry is installed as a web
application, package in a .EAR file

UDDI Registry

Service Type Registrations

Business Registrations
Web Services Gateway
•Middleware that helps bridge the gap between Internet and Intranet environments
during Web service invocations

•Built upon WSDL and WSIF

– A deployed WSDL file describes how the gateway should access the Web
service
– WSIF defines how the WSDL file is deployed, either to a UDDI Registry or URL

•Requests that pass through the Gateway can be sent to

– Java classes
– EJBs
– SOAP server
– SOAP/JMS server
Internet Target
Public Service
UDDI
external Gateway internal
(GW) WSDL WSDL
Unit Summary
•Reviewed the architectural components of WebSphere
Application Server
•Described JCA, JDBC Providers, Data sources and
Persistence manager
•Described the role of Virtual Hosts
•Described WebSphere Application Server’s Security Services
implementation
•Described how JMX supports distributed administration
•Described Web Services, Web Services Gateway and the
UDDI Registry