Level 2.3 CBT Course on Websphere Architecture and Deployment-Final

7/28/2019 Level 2.3 CBT Course on Websphere Architecture and Deployment-Final

1/50

Oct 13 2008 TPG Confidential1

Technology Practices GroupJava Competency Framework

"Incubate, Nurture and Deploy Technology Experts

Innovate, Build and Deliver Technology Solutions


2/50


Document Details

Business Unit BFSI

Group Technology Practices Group

Practice Java Practice

Sub-Practices

Initiative Competency Framework

Competency Level 2.3 [Level 4]

Experience Level 2-3 years

Pre-Requisite Java, J2EE, Web App Server internals

Version 1.0

Author TPG Java Practice

Total number of slides 50

Duration of learning 3 days


3/50


Revision History

Version

(x.yy)Date of

RevisionDescription of Change Reason for

ChangeAffected

SectionsApproved By

1.001.10

Sep 2007Dec 2008

Initial VersionContent Refresh Re-Format


4/50


Objective

** Please read the objective of this content clearly **

This presentation is essentially to set the context oflearning on Websphere appl icat ion server arch itectu reand deploym ent. The content deals with the coverage(both depth and width applicable) forWebsphereappl icat ion s erver archi tecture and deploymentin aconcise format, providing an overview of the elements thatmakes up this 2.3 [Level 4].

While this content provides with a high levelunderstanding of the topic to the level of depth that isexpected at 2.3 [Level 4], it is highly recommended tohave a detailed in depth learning using the resourcesmentioned in the Additional Resources section.


5/50


Table of Contents

Chapter 1 : Introduction Chapter 2 : Compatibility matrix Chapter 3 : Capabilities & Integration Chapter 4 : Concepts, Planning & Design Chapter 5 : Key features since v7.0

Chapter 6 : Deployment Chapter 7 : Best practice Chapter 8: Typical Topology Chapter 9 : Server administration Chapter 10 : Other features


6/50


Chapter 1 : Introduction

WebSphere is IBM's integration softwareplatform.

It includes the entire middleware

infrastructure -- such as servers, services,and tools--needed to write, run, and monitor24x7 industrial-strength, on demand Web

applications and cross-platform, cross-product solutions.

WebSphere provides reliable, flexible, and

robust integration software.


7/50Oct 13 2008 TPG Confidential7

Introduction (cont)

WebSphere Application Server is the base forthe infrastructure; everything else runs on topof it.

It supports SOA and non-SOA environments. WebSphere Process Server, which is based

on WebSphere Application Server, and

WebSphere Enterprise Service Bus, providethe foundation for service-oriented architected(SOA), modular applications.



Introduction (cont)

Collectively, they support the use ofbusiness rules to drive applications thatsupport business processes.

High performance environments also useWebSphere Extended Deployment as partof their base infrastructure. Other

WebSphere products provide a widevariety of additional services, as describedbelow.



Chapter 2: Compatibility matrix



Chapter 3: Capabilities & Integration

You can use WebSphere to build andmonitor an infrastructure to support your ondemand business, and to build and extend

applications that run on that infrastructure.



Capabilities & Integration (cont)

IBM providesextensive tools andfacilities, based on

industry openstandards such J2EEand Eclipse, to help

you build, run,manage, and optimizeyour WebSphereapplications.


12/50Oct 13 2008TPG Confidential 12

Chapter 4 : Concepts, Planning & Design

The majorconcepts of WebSphere are: Profiles

Stand-alone application servers

Nodes, node groups, and node agents

Cells

Deployment manager

Administrative agent

Job manager

Web Servers, Proxy Servers, Generic Servers

Business level applications

Centralized installation manager

Intelligent runtime provisioning


13/50Oct 13 2008 TPG Confidential

13

Concepts, Planning & Design (cont)

A nodeis an administrative grouping ofapplication servers for configuration andoperational management within one

operating system instance. Each node has a node agentthat works

with the deployment manager to manage

administration processes. A node groupis a grouping of nodes

within a cell that have similar capabilities.



14




15


A cellis a grouping of nodes into a singleadministrative domain.

In the Base and Express configurations, a

cell contains one node and that nodecontains one server.

The following are the some design

consideration for WebSphere deployment: Scalability

Caching



16


High Availability Load-balancing and fail-over

Disaster recovery

Security Application deployment

Servicability



17

The server environments are classified as: Single cell configurations

Multiple cell configuration

Mixed node versions in a cell Flexible management.

Clusters A cluster is a collection of servers

managed together. Clusters behave as a single application server

entity to accomplish a job by parallel

processing.




18

Chapter 5 : Key features since v7.0

Features added since WAS v7.0: Rational Application Developer Assembly &

Deploy v7.5

Rational Application Developer for WebSphereSoftware v7.5

Portlet application support enhancement

Session Initiation Protocol (SIP) support

IBM Software Developer Kit (SDK) for Java 6support

Enterprise JavaBeans (EJB) thin client


19/50


Key features since v7.0 (cont)

Just in time deployment for EJB 3.0 module. WebSphere Business Level Application.


20/50


Chapter 6 : Deployment

Recommendedtest

environment:


21/50


Deployment (cont)

Following are items to consider when youplan for additional resources.


22/50


Deployment (cont)

Basic deployment architecture


23/50


Deployment (cont)

Basic deployment


24/50


Deployment (cont)

Basic Deployment

Used in environment where

Down time is not critical

Typically used in Development/Testingenvironment


25/50


Deployment (cont)

Network Deployment

Supports multiple server instances

Supports clustering

Failover can be handled ensuring availability

Complements Load balancing hence easyscalability

Centralized administration of multiple serverinstances in the cell


26/50


Deployment (cont)

Network deployment architecture


27/50


Deployment (cont)

Network deployment


28/50


Deployment (cont)

Network Deployment usage Down time is critical

Typically in production environment

Allows the user to use the server even when anew version of the application is being rolled out

Application need to be scaled

Can distribute an application across

geographies to reduce the risk


29/50


Chapter 7: Best practices

User load and High availability requirementscan be handled through

Vertical Scaling

Horizontal Scaling

Vertical scaling

Adding more hardware to the same machinefor efficient usage of system resources

Increasing number of server instances tohandle user requests

Represents a single point of failure


30/50


Best practices (cont)

Horizontal scaling Preferred topology for High availability and load

balancing

Refers to addition of more systems

To distribute load

Ensuring high availability

Reduce single point of failure

Network deployment architecture isbeneficial in server administration andmonitoring of horizontally scaledapplication


31/50


Best practices (cont)

In a Horizontal clustered environmentWebsphere deploys application to one nodeat a time in the cell before moving to nextnode

During such roll out, use of ripple start isadvised, this ensures server in a cell isrestarted automatically one after another

thus ensuring high availability. Care must be taken when ripple start is

used in a 2 server environment and theretry interval set.


32/50


Chapter 8 : Typical Topology

CELL

Websphere

Websphere

Websphere

Websphere

SYSTEM1Loadbalancer

Webserver(example: apache)

Webserver(example: apache) SYSTEM2

DB

Backup

database


33/50


Chapter 9 : Server administration

Basicand Networkservers can be administeredthrough

Commands

Shell scripts or batch files based on the OS Can only perform a subset of administration tasks

Admin Console

User Interface based server administration

JMX Using JMX (Java Management extension)

Custom built administration through a program


34/50


Server administration (cont)

Configuration files

Configuration is stored in XML files, these filescan be modified for server administration

Scripting client

A command line interface for administration


35/50



Commands Server provides set of commands to start/stop/deploy/monitor

the server instance

startServer.sh server1

starts server1 instance

stopServer.shserver1

Stops server1 instance

startNode (stopNode) Starts a node

startManager (stopManager)

Starts deployment Manager


36/50



serverStatus Verifies server status to indicate whether server

is dead or alive

addNode, removeNode and syncNode

Used for node related operations

dumpNameSpace.sh

Dumps the JNDI tree.

Useful for debugging when an application is notable to recognize a resource configured in JNDIunder Cell/Node/server level


37/50



Key folders in a server installation $USER_INSTALL_ROOT/installedApps

File system location for a deployed .ear

$USER_INSTALL_ROOT/logs//

Log file location for a server

$WAS_HOME/bin

Location for the server scripts


38/50



Admin Console:Console Deployment Admin console is an

inbuilt web application In Network deployment

Admin console is hostedon deployment manager Console is accessible as

long as the deploymentmanager is running

In Stand alone, the

console runs inapplication server Admin console cannot

be accessed if theserver is stopped


39/50



Console Deployment: Have the deployable

ear ready

Logon to the adminconsole

ChooseApplications>>

Enterprise Applicationsfrom left menu

Choose installto installa new application

Select an ear path fromthe local folder.

Admin consoledeployment involvesuploading an ear to theserver using web basedconsole, hence earshould be picked fromthe local folder path


40/50



Console Deployment

Virtual hostconfigurationenables a systemto resemble

multiple hosts Virtual host are

created throughdifferent DNSname alias

Different

applications can behosted on differentvirtual hosts tomake use ofavailable resources


41/50



ConsoleDeployment

Choose clusterand servers fordeployment


42/50



ConsoleDeployment

Click on Savemaster configuration

updates the Cellconfiguration

Synchronizes allthe nodes in thecell


43/50



JMX based administration Java standard for administration

JMX includes:

MBean, which wraps around a manageableresource

Mbean server, registry to lookup Mbean

Protocol to connect to a MBeanServer

Client program can access MBeanServer usingSOAP or RMI-IIOP


44/50



In Basic deployment, administering clientdirectly connects to the server.

MBeans for all servers are visible through

Node agent MBeans across different nodes are visible at

Deployment manager level

Client program can get access to the serverthrough anAdminClientObject


45/50



Configuration files Configurations are stored in XML file

XML files are placed under$USER_INSTALL_ROOT/config directory

An change made to the configuration xml at thecell level updates the Node as well

Key configuration files

security.xml virtualhosts.xml

resources.xml

variables.xml


46/50



Each node has an correspondingsubdirectory and holds the configurationspecific to the Node

Deployed applications are placed underapplications directory

Each of the deployed application containsdeployment.xmlwith deployment

configuration details


47/50



Scripting Client Non graphical command line interface

Supports Jacl and Jython languages

Easy for automation of server administration in Interactive mode

Batch mode

Command mode

wsadmin acts as the core component ofscripting client.


48/50


Chapter 10 : Other features

Apart from the regular J2EE services,some of the other services provided byWebsphere include:

Performance Monitoring Interface (PMI) PMI collects performance related data on runtime

Runtime data can be retrieved using JMX client

integrated Tivoli performance viewer


49/50


Other features (cont)

Session sharing

A session can be shared between webapplications assembled with in an enterpriseapplication. In other words, if an EARcontains more than one web application(WAR), session attributes can be sharedbetween the WARs


50/50

Additional Resources

SL # Topic Element Resource Location/Link Remarks

1 WebSphere introduction http://www.ibm.com/developerworks/websphere/newto/ Chapter 1. Introduction

2Capabilities &integration

http://www.ibm.com/developerworks/websphere/newto/#dowith

Chapter 3. Capabilities &Integration

3Concepts, Planning &

Designhttp://www.redbooks.ibm.com/redpieces/pdfs/sg247708.pdf Chapter 4: Concepts
http://www.ibm.com/developerworks/websphere/newto/http://www.ibm.com/developerworks/websphere/newto/http://www.ibm.com/developerworks/websphere/newto/http://www.redbooks.ibm.com/redpieces/pdfs/sg247708.pdfhttp://www.redbooks.ibm.com/redpieces/pdfs/sg247708.pdfhttp://www.redbooks.ibm.com/redpieces/pdfs/sg247708.pdfhttp://www.redbooks.ibm.com/redpieces/pdfs/sg247708.pdfhttp://www.ibm.com/developerworks/websphere/newto/http://www.ibm.com/developerworks/websphere/newto/http://www.ibm.com/developerworks/websphere/newto/

Documents

Level 2.3 CBT Course on Websphere Architecture and Deployment-Final