WebSphere Application Server

architecture: Stand-alone

© Copyright IBM Corporation 2016

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
 Unit objectives
• Describe a typical e-business application architecture
• Describe the architectural differences between WebSphere Application
Server packages
• Describe what is running in a WebSphere Application Server node
• Describe the architectural implications of the web server plug-in
• Describe the use of Java Database Connectivity (JDBC) providers and
data sources

WebSphere Application Server architecture: Stand-alone © Copyright IBM Corporation 2016

 Topics
• Architecture runtime
• Architecture administration
• Profiles

WebSphere Application Server architecture: Stand-alone © Copyright IBM Corporation 2016

 Architecture runtime

© Copyright IBM Corporation 2016

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
 Version 9 packaging

WebSphere Application Server ND

Clustering Node agent Deployment manager

Intelligent Management Web Services Gateway

WebSphere Application Server Traditional

Web-based admin Web services

EJB container Messaging

Web container JDK

PMEs

WebSphere Application Server architecture: Stand-alone © Copyright IBM Corporation 2016

 WebSphere Application Server basics
• WebSphere Application Server
▪ Is a platform on which Java based business applications run
▪ Is an implementation of the Java Platform, Enterprise Edition (Java EE)
specification
▪ Provides services (database connectivity, threading, workload management)
that the business applications can use

Application

Application Server

Hardware, operating system, database,

network, storage

WebSphere Application Server architecture: Stand-alone © Copyright IBM Corporation 2016

 WebSphere architecture runtime (1 of 10)

Browser

Legend HTTP or HTTPS RMI/IIOP SOAP JDBC

WebSphere Application Server architecture: Stand-alone © Copyright IBM Corporation 2016
 WebSphere architecture runtime (2 of 10)

Browser

HTTP or
HTTPS
HTTP
server

Legend HTTP or HTTPS RMI/IIOP SOAP JDBC

WebSphere Application Server architecture: Stand-alone © Copyright IBM Corporation 2016
 WebSphere architecture runtime (3 of 10)
Application Server
Browser
Web container

Embedded HTTP
Servlets
HTTP
Server
server JSP
Plug-in

Plug-in
configuration
file

Legend HTTP or HTTPS RMI/IIOP SOAP JDBC

WebSphere Application Server architecture: Stand-alone © Copyright IBM Corporation 2016
 WebSphere architecture runtime (4 of 10)
Application Server
Browser
Web container EJB container

Embedded HTTP
Servlets
HTTP EJB
Server
server JSP
Plug-in

Plug-in
configuration
file

Legend HTTP or HTTPS RMI/IIOP SOAP JDBC

WebSphere Application Server architecture: Stand-alone © Copyright IBM Corporation 2016
 WebSphere architecture runtime (5 of 10)
Application Server
Browser
Web container EJB container

Embedded HTTP
Servlets
HTTP EJB
Server
server JSP
Plug-in

Plug-in Application
configuration data
file

Legend HTTP or HTTPS RMI/IIOP SOAP JDBC

WebSphere Application Server architecture: Stand-alone © Copyright IBM Corporation 2016
 WebSphere architecture runtime (6 of 10)
Application Server
Browser
Web container EJB container

Embedded HTTP
Servlets
HTTP EJB
Server
server JSP
Plug-in
Web services Messaging
Plug-in engine engine Application
configuration data
file
Dynamic cache JMX

Data replication Security

Name server Other services

Legend HTTP or HTTPS RMI/IIOP SOAP JDBC

WebSphere Application Server architecture: Stand-alone © Copyright IBM Corporation 2016
 WebSphere architecture runtime (7 of 10)
Application Server
Browser
Web container EJB container

Embedded HTTP
Servlets
HTTP EJB
Server
server JSP
Plug-in
Web services Messaging
Plug-in engine engine Application
configuration data
file
Dynamic cache JMX

Data replication Security

Name server Other services

Legend HTTP or HTTPS RMI/IIOP SOAP JDBC

WebSphere Application Server architecture: Stand-alone © Copyright IBM Corporation 2016
 WebSphere architecture runtime (8 of 10)
Java
Application Server client
Browser
Web container EJB container

Embedded HTTP
Servlets
HTTP EJB
Server
server JSP
Plug-in
Web services Messaging
Plug-in engine engine Application
configuration data
file
Dynamic cache JMX

Data replication Security

Name server Other services

Legend HTTP or HTTPS RMI/IIOP SOAP JDBC

WebSphere Application Server architecture: Stand-alone © Copyright IBM Corporation 2016
 WebSphere architecture runtime (9 of 10)
Java
Application Server client
Browser
Web container EJB container

Embedded HTTP
Servlets
HTTP EJB
Server
server JSP
Plug-in
Web services Messaging
Plug-in engine engine Application
configuration data
file
Dynamic cache JMX

Data replication Security

Name server Other services

Web
services
client

Legend HTTP or HTTPS RMI/IIOP SOAP JDBC

WebSphere Application Server architecture: Stand-alone © Copyright IBM Corporation 2016
 WebSphere architecture runtime (10 of 10)
Java
Application Server client
Browser
Web container EJB container

Embedded HTTP
Servlets
HTTP EJB
Server
server JSP
Plug-in
Web services Messaging
Plug-in engine engine Application
configuration data
file
Dynamic cache JMX

Data replication Security

Name server Other services

Web JMS
services client
client

Legend HTTP or HTTPS RMI/IIOP SOAP JDBC JMS

WebSphere Application Server architecture: Stand-alone © Copyright IBM Corporation 2016
 JDBC providers
• Provide the JDBC driver implementation for database access
▪ Type 2 JDBC drivers (thick): Require 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 by
using its native protocol
• XA drivers support transaction recovery

Client node

JNDI Connection JDBC Database Database

pool client server
JDBC driver
Data source

WebSphere Application Server architecture: Stand-alone © Copyright IBM Corporation 2016

 Data sources
• Data sources can improve performance and portability for database access
▪ Standard and XA data sources
• Two parts provide connection pooling:
▪ J2C connection manager
▪ Relational resource adapter
• Connection factories are similar to data sources
▪ Typically connect to external resources that are not databases
• WebSphere Application Server Version 4.0 data sources are deprecated in
Version 9
Relational resource
adapter
Application

Data source
or Connection
Database
connection pool
factory

J2C connection
manager
WebSphere Application Server architecture: Stand-alone © Copyright IBM Corporation 2016
 Administration architecture

© Copyright IBM Corporation 2016

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
 WebSphere administration architecture (1 of 4)
Application Server

Web container EJB container

Servlets

Embedded HTTP
JSP pages EJB
Server

Web services Messaging

engine engine

Dynamic cache JMX

Data replication Security

Name server Other services

WebSphere Application Server architecture: Stand-alone © Copyright IBM Corporation 2016

 WebSphere administration architecture (2 of 4)
Application Server

Web container EJB container

Admin

Embedded HTTP
Servlets service
JSP EJB
Server Admin
Admin
MBeans
application

Web services Messaging

engine engine

Dynamic cache JMX

Data replication Security

Name server Other services

XML
configuration
files
WebSphere Application Server architecture: Stand-alone © Copyright IBM Corporation 2016
 WebSphere administration architecture (3 of 4)
Application Server
Web-based
administrative
console Web container EJB container
Admin

Embedded HTTP
Servlets service
JSP EJB
Server Admin
Admin
MBeans
application

Web services Messaging

engine engine

Dynamic cache JMX

Data replication Security

Name server Other services

XML
configuration
Legend HTTP or HTTPS RMI/IIOP SOAP/HTTP File I/O files
WebSphere Application Server architecture: Stand-alone © Copyright IBM Corporation 2016
 WebSphere administration architecture (4 of 4)
Application Server
Web-based
administrative
console Web container EJB container
Admin

Embedded HTTP
Servlets service
JSP EJB
Server Admin
Admin
MBeans
application

Web services
Messaging
engine engine
wsadmin
command-line Dynamic cache JMX
client
Data replication Security

C:\> wsadmin
Name server Other services

XML
configuration
Legend HTTP or HTTPS RMI/IIOP SOAP/HTTP File I/O files
WebSphere Application Server architecture: Stand-alone © Copyright IBM Corporation 2016
 Profiles

© Copyright IBM Corporation 2016

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
 WebSphere profile overview
Profiles are sets of files that represent a
WebSphere Application Server configuration

WebSphere Application Server files are split

into two categories: WebSphere
• Product files product files
(binary files)
▪ Set of shared read-only static files or
product binary files
▪ Shared among any instances of the
WebSphere Application Server product
Profile files
 DmgrProfile
• Profiles (configuration files)  profile1
 profile2
▪ Set of user-customizable data files
▪ Files include WebSphere configuration,
installed applications, resource adapters,
properties, and log files

WebSphere Application Server architecture: Stand-alone © Copyright IBM Corporation 2016

 WebSphere profile benefits
• Benefits of profiles:
▪ Each profile uses the same product files
▪ Simpler than multiple WebSphere installations
▪ Less disk space
▪ Simplifies application of product updates
profile1 profile2

WebSphere Application Server architecture: Stand-alone © Copyright IBM Corporation 2016

 Managing profiles
2

Profiles are managed through one of the tools provided:

1. Profile Management Tool
• Accessed through the WebSphere Customization Toolbox
• Gathers user input and starts the manageprofiles
command-line tool to create the profiles
2. manageprofiles script
• Command-line interface for profile management functions
WebSphere Application Server architecture: Stand-alone © Copyright IBM Corporation 2016
 Profile types
• Cell
▪ Deployment manager with a federated application server
• Management
▪ Administrative agent
▪ Deployment manager
▪ Job manager
• Application server
▪ Stand-alone
• Custom profile
▪ Federated node
(no application server)
• Secure proxy

WebSphere Application Server architecture: Stand-alone © Copyright IBM Corporation 2016

 Unit summary
• Describe a typical e-business application architecture
• Describe the architectural differences between WebSphere Application
Server packages
• Describe what is running in a WebSphere Application Server node
• Describe the architectural implications of the web server plug-in
• Describe the use of Java Database Connectivity (JDBC) providers and
data sources

WebSphere Application Server architecture: Stand-alone © Copyright IBM Corporation 2016

 Review questions
1. Which one of the following components provides an
environment for running servlets?
A. Client module
B. Web container
C. EJB module

2. Which type of JDBC driver is considered a “thick” driver?

A. Type 2
B. Type 3
C. Type 4

3. Which of the following are components contained within

the JVM of the application?
A. HTTP Server plug-in
B. Embedded HTTP Server
C. DB2 database

WebSphere Application Server architecture: Stand-alone © Copyright IBM Corporation 2016

 Review answers
1. Which one of the following components provides an
environment for running servlets?
A. Client module
B. Web container
C. EJB module
The answer is B.
2. Which type of JDBC driver is considered a “thick” driver?
A. Type 2
B. Type 3
C. Type 4
The answer is A.
3. Which of the following are components contained within
the JVM of the application?
A. HTTP Server plug-in
B. Embedded HTTP Server
C. DB2 database
The answer is B.
WebSphere Application Server architecture: Stand-alone © Copyright IBM Corporation 2016
 Exercise: Profile creation

© Copyright IBM Corporation 2016

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
 Exercise objectives
After completing this exercise, you should be able to:
• Use the Profile Management Tool to create a profile
• Verify the profile creation

WebSphere Application Server architecture: Stand-alone © Copyright IBM Corporation 2016