WebSphere Application

Server architecture –
stand-alone

© Copyright IBM Corporation 2013

Course materials may not be reproduced in whole or in part without the prior written permission of IBM. 8.0
Unit objectives
After completing this unit, you should be able to:
• 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

© Copyright IBM Corporation 2013

Topics
• Architecture runtime
• Architecture administration
• Profiles

© Copyright IBM Corporation 2013

 Architecture runtime

© Copyright IBM Corporation 2013

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

WebSphere Application Server Network Deployment

Clustering Node agent Deployment manager

Intelligent Management Web Services Gateway

WebSphere Application Server

and
WebSphere Application Server Express (up to two processors)

Web-based admin Web services

EJB container Messaging

Web container JDK

PMEs

© Copyright IBM Corporation 2013

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

© Copyright IBM Corporation 2013

WebSphere architecture runtime (1 of 10)

Browser

Legend HTTP/S RMI/IIOP SOAP JDBC © Copyright IBM Corporation 2013

WebSphere architecture runtime (2 of 10)

Browser

HTTP(S)

HTTP
server

Legend HTTP/S RMI/IIOP SOAP JDBC © Copyright IBM Corporation 2013

 WebSphere architecture runtime (3 of 10)
Application Server
Browser
Web container

Embedded HTTP
Servlets
HTTP
server Server JSPs
Plug-in

Plug-in
configuration
file

Legend HTTP/S RMI/IIOP SOAP JDBC © Copyright IBM Corporation 2013

 WebSphere architecture runtime (4 of 10)
Application Server
Browser
Web container EJB container

Embedded HTTP
Servlets
HTTP
Server
EJBs
server JSPs
Plug-in

Plug-in
configuration
file

Legend HTTP/S RMI/IIOP SOAP JDBC © Copyright IBM Corporation 2013

 WebSphere architecture runtime (5 of 10)
Application Server
Browser
Web container EJB container

Embedded HTTP
Servlets
HTTP
Server
EJBs
server JSPs
Plug-in

Plug-in Application
configuration data
file

Legend HTTP/S RMI/IIOP SOAP JDBC © Copyright IBM Corporation 2013

 WebSphere architecture runtime (6 of 10)
Application Server
Browser
Web container EJB container

Embedded HTTP
Servlets
HTTP
Server
EJBs
server JSPs
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/S RMI/IIOP SOAP JDBC © Copyright IBM Corporation 2013

 WebSphere architecture runtime (7 of 10)
Application Server
Browser
Web container EJB container

Embedded HTTP
Servlets
HTTP
Server
EJBs
server JSPs
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/S RMI/IIOP SOAP JDBC © Copyright IBM Corporation 2013

 WebSphere architecture runtime (8 of 10)
Java
Application Server client
Browser
Web container EJB container

Embedded HTTP
Servlets
HTTP
Server
EJBs
server JSPs
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/S RMI/IIOP SOAP JDBC © Copyright IBM Corporation 2013

 WebSphere architecture runtime (9 of 10)
Java
Application Server client
Browser
Web container EJB container

Embedded HTTP
Servlets
HTTP
Server
EJBs
server JSPs
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/S RMI/IIOP SOAP JDBC © Copyright IBM Corporation 2013

 WebSphere architecture runtime (10 of 10)
Java
Application Server client
Browser
Web container EJB container

Embedded HTTP
Servlets
HTTP
Server
EJBs
server JSPs
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/S RMI/IIOP SOAP JDBC JMS

© Copyright IBM Corporation 2013
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
pool JDBC Database
Database
client
JDBC driver server
Data source

© Copyright IBM Corporation 2013

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
Relational resource
adapter
Application

Data source
or Connection Database
Connection pool
factory

J2C
connection
manager © Copyright IBM Corporation 2013
 Architecture administration

© Copyright IBM Corporation 2013

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

Web container EJB container

Embedded HTTP
Servlets
EJBs
JSPs
Server

Web services Messaging

engine engine

Dynamic cache JMX

Data replication Security

Name server Other services

© Copyright IBM Corporation 2013

WebSphere architecture administration (2 of 4)
Application Server

Web container EJB container

Admin

Embedded HTTP
Servlets service
Server JSPs EJBs
Admin
Admin
MBeans
application

Web services Messaging

engine engine

Dynamic cache JMX

Data replication Security

Name server Other services

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

Embedded HTTP
Servlets service
Server JSPs EJBs
Admin
Admin
MBeans
application

Web services Messaging

engine engine

Dynamic cache JMX

Data replication Security

Name server Other services

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

Embedded HTTP
Servlets service
Server JSPs EJBs
Admin
Admin
MBeans
application

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

C:\> wsadmin
Name server Other services

XML
Legend HTTP/S RMI/IIOP SOAP/HTTP File I/O configuration
files
© Copyright IBM Corporation 2013
 Profiles

© Copyright IBM Corporation 2013

Course materials may not be reproduced in whole or in part without the prior written permission of IBM. 8.0
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 Profile files
Application Server product  DmgrProfile
 profile1
 profile2
• Profiles (configuration files)
– Set of user-customizable data files
– Files include WebSphere configuration, installed
applications, resource adapters, properties, and
log files
© Copyright IBM Corporation 2013
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

© Copyright IBM Corporation 2013

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

© Copyright IBM Corporation 2013

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

© Copyright IBM Corporation 2013

Unit summary
Having completed this unit, you should be able to:
• 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

© Copyright IBM Corporation 2013