Scribd
Upload
41 views14 pages

WebSphere 101

Uploaded by

ckdxxnr
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
41 views14 pages

WebSphere 101

Uploaded by

ckdxxnr
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 14

WebSphere

Application Server
 Overview of key concepts, terminology and technologies
 What an “Application Server” is
 Java and the role of open standards
 Review of the kinds of applications WebSphere can and can not
run
 Review of the notion of a “three tier” architecture -- very common
with WebSphere
Key Concepts, Terminology
and Technologies
 We’ll start by clearing up a point of confusion about the term “WebSphere.”
 “WebSphere” is a Brand; “WebSphere Application Server” a Product
 Probably close to 100 products that carry the “WebSphere” brand name
 WebSphere Adapters
 WebSphere Application Server
 Branch Transformation Toolkit for WebSphere Studio
 WebSphere Business Events
 WebSphere Business Integration Server
 :
 :
 WebSphere Virtual Enterprise
 WebSphere Voice Response for AIX
 WebSphere Voice Server
 What An “Application Server” Provides
 WebSphere Application Server is an “application server” … but what is that?

 Purpose is to provide pre-packaged application support stuff so developers can focus on


the main business task. No more re-inventing the wheel.
 Agreed-to Standards: Rules and regulations agreed to by the players in an industry that will
allow the different offerings to work better together.
 Otherwise we’d have islands of proprietary technology and difficulty interconnecting
 Java and the Java Virtual Machine (JVM)
 Java is a programming language; the JVM is what the Java programs runs in. It’s what
shields the Java program from the specifics of the platform.
Different Kinds of Java Programs
 WebSphere Application Server can host -- or “run” or “support” --several different kinds of
application -- all written in Java
 Web Application: An application that’s accessed with a browser. This typically consists of
static files (HTML, JPG/GIF), and Java programs that generate dynamic output:
 Servlets -- Java program that contains logic to do things like perform calculations, access
data, and format a reply
 JSPs -- stands for Java Server Pages, it’s a way to create a dynamic web page that can be
populated with dynamic content
 EJB Application: Stands for “Enterprise Java Bean,” it’s a more sophisticated application
that’s intended for high-end applications. Two flavors:
 Session Beans -- meant to hold the logic of the application
 Entity Beans -- meant to represent data as an “object” Many EJB applications are made
up of just session beans -- easier.
 POJO : Stands for “Plain Old Java Object.” It is the simplest form of a Java program. (POJO
commonly applies to the EJB 3.0 environment and Java Batch environment)
 Data Connectivity -- JDBC, JCA and JMS
 All three are open standard specifications for access different kinds of data. Key is that they
provide a defined, standardized interface to “hide” the actual data system where data is held:
 Relational Databases
 DB2, Oracle, Informix, Sybase, etc.
 JDBC = Java Data Base Connectivity
 Standard: a defined set of APIs that are converted to the specific commands needed for the
backend DB by the vendor supplied code
 Non-Relational Databases
 CICS, IMS, SAP, PeopleSoft, etc.
 JCA = Java Connector Architecture
 Standard: a defined set of APIs that are converted to the specific commands needed for the
backend data store by the vendor supplied code
 Messaging Providers
 MQ as provider, or WebSphere built-in messaging
 JMS = Java Messaging Service
 Standard: a defined set of APIs for applications to send and receive messaging. The actual
carrier of the messages can be MQ or the built-in system of WebSphere.
Typical “Three-Tier” Application Design
High Level Overview of WebSphere
Application Server
 The idea of a framework that provides common services, and the notion of a Java Virtual
Machine:
Schematic Diagram of WebSphere Application server
1.Server is Started
 This native code is what establishes the lower-level
“plumbing” and allows for the invocation of the Java
environment
2.Java Runtime Established, including JVM
 Once the native base is ready, it establishes Java
runtime environment and launches the JVM
3.WebSphere Java Components Loaded into JVM
 With the JVM launched, WebSphere Application
Server can now load the Java components that make
up the Java EE environment
 This is the “framework” we mentioned earlier
 This is why WebSphere Application Server is more than
just a JVM.
4.Your Applications Loaded and Started
 If they’re deployed in the server and configured to
start automatically, WebSphere will do that for you.

You might also like