1

Application Server:-
Application Server is a container which complies with run time environment of
J2EE applications with J2EE specifications
Web server:-
Web Server is a Container, its functionality is to handle HTTP request and serve
HTML pages, it is used for accessing the web page

WebSphere Application Server

WebSphere Application Server provides the environment to run your
Web-enabled e-business applications.
An application server functions as Web Middleware or a middle tier in a three-tier
e-business environment.

Three –Tier e-business environment

• The first tier is the HTTP server that handles requests from the browser client
• The third tier is the business database (for example, DB2 UDB for iSeries) and
the business logic (for example, traditional business applications, such as order
processing).

The middle tier is WebSphere Application Server, which provides a framework for a
consistent and architected link between the HTTP requests and the business data and
logic.

Some Important Containers in WAS:-

Web container:-
Manages the execution of
1. JSP page(Java Server pages)
2. Servlet components
 2

3.
Enterprise JavaBeans (EJB) container:-
• Provides a run-time environment for enterprise beans within the
application server
SIP Container:-
• Session Initiation Protocol (SIP) is used to establish and manage
multimedia IP sessions
Portlet Container:-
• The portlet container is the runtime environment for portlets using the
JSR (Java Specification Requests) 168 Portlet Specifications, in which
portlets are instantiated, used, and finally destroyed.(Like JSP)
Embedded http server:-
• It is inbuilt in Application server. It is embedded with admin console.
• It is independent with all web containers
J2C container:-
• A J2C container contains connection factories that represent backend resources; it
also manages access to these resources via a connection manager associated with
each connection

WebSphere Application Server ND V6.1 Package:

V6.1 extends the application server to allow it to

• Run Portlets applications
• Session Initiation Protocol (SIP) applications

Session Initiation Protocol (SIP) is used to establish and manage multimedia

IP sessions.

This package includes two tools

• Application Server Toolkit- The toolkit is suitable for J2EE application
development as well as the assembly and deployment of J2EE applications
AST toolkit also provides tools for the development, assembly, and
deployment of SIP and portlet applications.
• Package includes a trial version of Rational Application Developer (RAD)
RAD supports the development, assembly, and deployment of J2EE 1.4
applications.
Web servers supported by WebSphere Application Server V6.1
• Apache HTTP Server 2.0.54
• IBM HTTP Server for WebSphere Application Server V6.0.2 & V 6.1
• IIS (Internet Information Services) V 5.0 & 6.0
• Lotus® Domino® Enterprise Server
• Sun Java System Web Server
 3

Database servers supported by WebSphere Application Server V6.1

• IBM DB2
• Cloudscape
• Oracle
• Sybase
• Microsoft SQL Server
• Informix®
• IMS™
• WebSphere Information Integrator

Directory servers supported by WebSphere Application Server V6.1

LDAP servers that WebSphere Application Server 6.1 supports
• -IBM Tivoli Directory Server
• -Lotus Domino Enterprise Server
• -Sun ONE™ Directory Server
• -Windows Active Directory
• Novell eDirectory

Java Management Extensions (JMX)

• JMX is a framework that provides a standard way of exposing Java resources

The JMX framework allows a provider to implement functions, such as listing the
configuration settings, and allows users to edit the settings

JMX connectors: -
1. SOAP (Simple Object Access Protocol) Port# 8880),
2. RMI (Remote Method Invocation)

MBean:-
-MBeans- (managed beans) is java object that represents a manageable resource,
such as application, a service, a component or a device
-MBeans-Java Object
-Resources are managed by JMX MBeans
-MBean used to communicate the XML repository to update the configuration.

JMX  MBeans  Resource

Master repository:-
Master repository located on the deployment manager installation contains the
serverindex.xml file for each node

The deployment manager reads this file on startup to determine the host name and IP port
of each node agent’s NODE_DISCOVERY_ADDRESS.

File synchronization:-
 4

Node agent checks with the deployment manager to see if any files that apply to
the node have been updated in the master repository.
New or updated files are sent to the node, while any deleted files are also deleted
from the node.

Plug-in

• An HTTP request from a Web browser enters the Web server and is then
redirected to the application server. This redirection is performed by the
WebSphere plug-in.
• WebSphere plug-in as an “agent” redirecting HTTP requests from the Web server
to the application server using the HTTP protocol

HttpTransport
• Its job is to accept the HTTP request from the plug-in, and then forward it to the
web container.

Plugin-cfg.xml: This is Web Sphere’s plug-in configuration file and contains

information about which URLs should be serviced by WebSphere.

<Config>
<Log LogLevel="Error" Name="<WAS_HOME>\logs\http_plugin.log"/>
<VirtualHostGroup Name="default_host">
<VirtualHost Name="*:80"/>
</VirtualHostGroup>
<ServerCluster Name="MyCluster">
<Server Name="CL1">
<Transport Hostname="SHARAD" Port="9080" Protocol="http"/>
</Server>
</ServerCluster>
<UriGroup Name="MyURIs">
<Uri Name="/MyPath/*"/>
</UriGroup>
 5

<Route ServerCluster="MyCluster"
UriGroup="MyURIs" VirtualHostGroup="default_host"/>
</Config>
Step 1: HTTP request enters the plug-in, http://www.xyz.com/MyPath/MyPage
Step 2: Plug-in breaks down the URL into 2 parts:
1st, www.xyz.com:80 is the hostname or the Virtual Host, and
2nd, /MyPath/MyPage is the URI
Step 3: Find a Route in plugin-cfg.xml that will service this Virtual Host and URI
Step 4: Compare the Virtual Host of the request with all Virtual Hosts defined in the
VirtualHostGroup of the Route
Step 5: Compare the URI of request with all the URIs defined in the UriGroup of the
Route. (Start with 1st URI)
Step 6: Route selected. WebSphere will handle the request.

profile Set of files that represent a web sphere application server

configuration or Core product files are shared among runtime
component defined by these profiles
 6

Node Corresponds to a physical computer system with a distinct

IP, the node name is usually the same as the host name of the
computer

Cell Cell is a physical collection of Nodes

Node group Group of nodes with same set of configuration in same O/s

Core group Configuration information of specific JVM belonging to a

node group.
Node agent Node agent is a federated dmgr it communication bridge b/w
dmgr and App srvr.

Profiles in WAS ND v 6.1:-

1. Cell
2. Application Server
3. Deployment Manager
4. Custom

JDBC: - Java Database Connectivity

An application programming interface (API) for connecting Java programs to the data
in a relational database. With this API, you can encode data requests in Structured
Query Language (SQL) that JDBC then passes to the database manager for
interpretation and processing.

JDBC Resource:-

1. JDBC Providers
The JDBC provider object encapsulates the specific JDBC driver implementation
class for access to the specific vendor database of your environment
• Database Type
• Provider Type
• Implementation Type- Connection Pool data source or XA data source
• Database Class path-Driver path

2. Data Source- A data source supplies the physical connections between the application
server and the database.
• Basic Data Source Information:- Data Source Name & JNDI Name
 7

• JDBC Provider
• DB specific properties for Data Source-DB name, Driver Type ,Server name
Types of Drivers:-
Type 1:- ODBC Driver
Type 2:- Driver requires DB client loaded on each client machine
Type 3:- Pure Java Driver-Without firewall (JDBCDB middleware  different
databases)
Type 4: Direct-to-Database Pure Java Driver-With firewall

Need to mention the JNDI name while installing EJB application

i.e., Target JNDI reference
JNDI: -
• Java Naming and Directory interface
• Naming services provide name-to-object mappings
• JNDI is a user registry for all java components like ejb, text, and jms.

JMS- Java Message Service

A programming interface that connects Java programs to middleware messaging

applications, for example, WebSphere MQ.
1. Service Integration-
Bus: - (SIB)
• A service integration bus supports applications using message-based and service-
oriented architectures.
• A bus is a group of interconnected servers and clusters that have been added as
members of the bus.
• Applications connect to a bus at one of the messaging engines associated with its
bus members
Bus Members:-
• Bus members are the servers, WebSphere MQ servers and clusters that have
been added to the bus.( Choose the server, cluster or WebSphere MQ server to
add to the bus Msg store)
Message Engines:-
• Manages messaging resources for a bus member
Application messaging engine service integration bus
• Applications are connected to a messaging engine when accessing a service
integration bus
Designation:-
• Msg type (Queue, Type, Alias, Foreign)
• Queue Identifier
• Assign the queue to a bus member that will store and process the messages for
the queue.

2. Resources:-
• JMS providers:- It provides J2EE connection factories to create connections for
JMS destinations
 8

• QCF:-Queue connection factory is used to create connections to the associated

JMS provider of the JMS queue destinations, for point-to-point messaging.
• Queue: - A JMS queue is used as a destination for point-to-point messaging.
• Activation specifications:- associated with one or more message-driven beans
to receive messages
-MDBs "listen" on a specific JMS destination, when a message arrives on
the destination, that message is delivered to the MDB
-JNDI name (AS) & Destination JNDI name. (Queue)
3. Binding Listeners for MDB - Need to Mention Activation Specifications JNDI name
while Installing Application.

Sequence of starting & stopping various instances:-

1. Strart the node agent
2. Start the server
3. Start the dmgr
4. Start the Appache

Client container and UTC:-

Client container and UTC are used to test EJB directly up to method level.

Administration:-
1. Admin console
Admin Console  embedded http server JMX repository
3. WSADMIN JMX Repository (SOAP protocol , 8880)

Clusters

Group of application servers for load balancing and high availability

Horizontally clustered environments & vertically clustered environments

• Horizontal clustering: - A horizontally clustered environment contains multiple
physical machines (nodes)
• Vertical clustering : - A vertically clustered environment contains multiple
application server instances hosted on the same physical machine (node)

Work load Policy:-

1. Random
2. Random prefer local
3. Round Robin (Default)
4. Round robin preferred local

Session management in Cluster:-

Session data is saved in a distributed environment to over come session failure.
1. Shared session Data Base
2. Memory to memory replication (SIP uses only m2m) – short lived session
 9

Memory-to-memory replication:-

Memory-to-memory session replication is the session replication to another WebSphere

Application Server.

The WebSphere Application Server instance in which the session is currently processed
is referred to as the owner of the session. If the current owner server instance of the
session fails, then the WebSphere Application Server plug-in routes the requests to
another appropriate server in the cluster. In a peer-to-peer cluster, the hot failover feature
causes the plug-in to failover to a server that already contains the backup copy of the
session, avoiding the overhead of session retrieval from another server containing the
backup. In a client/server cluster, the server retrieves the session from a server that has
the backup copy of the session. The server now becomes the owner of the session and
affinity is now maintained to this server.

Three possible modes to run

• Server mode: Only store backup copies of other WebSphere Application Server
sessions and not to send out copies of any session created in that particular server

• Client mode: Only broadcast or send out copies of the sessions it owns and not to
receive backup copies of sessions from other servers

• Both mode: Simultaneously broadcast or send out copies of the sessions it owns
and act as a backup table for sessions owned by other WebSphere Application
Server instances.

Shared session Data Base:- Session info stored in external DB-Specifies that the
session management facility stores session information in the data source specified by the
data source connection settings. Click Database to change these data source settings.

SOAP-Simple Object Access Protocol-SOAP is a simple XML-based protocol to

let applications exchange information over HTTP.

SOA:- Service Oriented Architecture -architecture for the development of loosely

coupled distributed applications. In fact service-oriented architecture is collection of
many services in the network. These services communicate with each other and the
communications involves data exchange & even service coordination.
 10

A service is a function or some processing logic or business processing that is well-

defined, self-contained, and does not depend on the context or state of other services.
Example of Services are Loan Processing Services, which can be self-contained unit for
process the Loan Applications. Other example may be Weather Services, which can be
used to get the weather information. Any application on the network can use the service
of the Weather Service to get the weather information.