WebSphere Application Server 6.

1 Administration

What is WAS and its Overview Position in 3-tier architecture Opportunity/Demand for WAS Admin in the market

 Provides the infrastructure for running applications that run your business. Common environment and programming model for your applications. Platform for developing and Deploying web services and SOA based apps IBM WebSphere is architected to enable you to build business-critical applications for the Web WebSphere includes a wide range of products that help you develop and serve Web applications. They are designed to make it easier for clients to build, deploy, and manage dynamic Web sites more productively

Packaging WebSphere Application Server - Express V6 WebSphere Application Server V6.1 WebSphere Application Server Network Deployment V6

Standalone Server Architecture Overview

Distributed Server Overview

Differences b/n WAS 5,6.0 and 6.1

WAS 5 : J2EE 1.2/1.3 support JDK 1.3 support Web Services based on Apache engine

WAS 6.0: J2EE 1.2/1.3/1.4 support JDK 1.4 support (JDK 1.4.2) Web Services based on J2EE 1.4 High Availability Manager Java Based Messaging Engine EJB 2.1, JMS 1.1, JCA 1.5, Servlet 2.4, and JSP 2.0 Supports Java Server Faces (JSF) Creates Archive of the existing WAS configurations and the archive can be used to create new configurations. Profiles and all profiles use same WebSphere binaries (Less storage) Node groups Service integration functionality provides both message-oriented and service Oriented applications WAS 6.1: J2EE 1.2/1.3/1.4 support JDK 5.0 support JSF-a framework for Web applications Integrated Console Security changes Secure and Scalable runtime

WebSphere Application Server - Express V6.0 Single Server environment.( No Clustering or multi server management) J2EE 1.4 support Medium-sized business Limited to 2 CPUs WebSphere Application Server V6.1 (Base) Slightly differs in packaging and licensing Contains Application Server toolkit Includes a trial version of Rational Application Developer Unlimited CPUs WebSphere Application Server Network Deployment V6 Extends Base version Clustering capabilities and Failover support Distributed Administration Edge Components which provide high performance and availability (Caching Proxy and Load Balancer) HA for distributed configurations Large Enterprise applications Scalability, Availability and Performance Web Server plug-in supports weighted WLM

WAS 6.1 ND Installation

Hardware Requirements Minimum requirements are: . Minimum 512 MB memory; 1 GB recommended . CD-ROM drive for installation .AIX: .RS/6000 workstation or RS/6000 SP Frame at 375 MHz or faster .Minimum 970 MB free disk space for installation (includes SDK) . Linux on Intel: .Intel x86 processor at 500 MHz or faster .Minimum 995 MB free disk space for installation (includes SDK) . Linux on zSeries and S/390: .G5, G6 or better processor .Minimum 995 MB free disk space for installation .Sun Solaris: .Sun SPARC workstation at 440 MHz, or faster .Minimum 1000 MB free disk space for installation (includes SDK) .Windows 2000 and Windows 2003: .Intel Pentium processor at 500 MHz, or faster .Minimum 990 MB free disk space for installation (includes SDK) .HP-UX: .PS-RISC at 440 MHz or faster .Minimum 1100 MB free disk space for installation (includes SDK)

Software Requirements
Operating Systems AIX Windows Sun Solaris HP-UX Linux z/OS Supported WebServers Apache IBM HTTP Server Internet Information Server Sun One WebServer Lotus Domino Databases IBM DB2 Oracle Sybase SQL Informix

 Installation Overview The WebSphere installation separates the core product binary data from the configuration data that is created as the application server runtime environment is customized Can have multiple sets of customized runtime environments Each environment is known as a profile Profiles share product binaries Need to create profiles after installation of product binaries Profile Creation Wizard is launched as part of the install Easier than multiple installations Less disk space Product update is simplified

Creating Profiles Profile is the runtime configuration for the application server WebSphere provide multiple ways of creating profiles Profile Creation Wizard 1) Start menu (Windows only) 2) Launched after installation from install wizard 3) Launch via command line tool pctWindows <was_root>\bin\ProfileManagement\pmt.bat Similar command exists for UNIX platform (GUI Based pop-up) 4) Wizard in first steps console 5)Manually via the manageprofiles.bat command line tool <was_root>\bin\manageprofiles.bat Note : In 6.0 wasprofile.bat is the command line tool for profile creation

Return Codes After installation (Supported only in Linux and Unix and not in Windows) WebSphere Application Server uses return codes to indicate the results of an installation operation: 0 Success 1 Failed 2 Partial success 3 Reserved 4 License not accepted 5 PrereqCheck failed 6 Upgrade not supported

Default WAS Root Installation Directories

/usr/IBM/WebSphere/AppServer - AIX /opt/IBM/WebSphere/AppServer - HPUX,Linux,Solaris C:\Program Files\IBM\WebSphere\AppServer - Windows

Managing Profile Configurations

Back up Profile Configuration
<profile_home>/bin/backupConfig.bat <backup file> <options>

Restore Profile Configuration

<profile_home>/bin/restoreConfig.bat <backup file> <options>

Uninstallation
GUI Silent
<WAS_Root>\uninstall>uninstall.exe -silent -OPT removeProfilesOnUninstall="true"

Fix Packs Installation

The SDK, Java technology edition, in the java/jre directory JAR files in the app_server_root/lib directory Scripts in the app_server_root/bin directory Profile templates

Update installer is used for installing fix packs and interim fixes. GUI

Silent
<InstallerBinaries>/<UpdateInstaller>install.exe options responsefile.updiinstaller.txt silent Fix Pack installation GUI using update installer silent <UpdateInstaller>update.bat options <path to responsefile> silent

Application Server
The application server is the primary runtime component in all configurations and it is where an application executes. In the Express and Base configurations, each application server functions as a separate entity. There is no workload distribution or common administration among application servers. With Network Deployment, you can build a distributed server environment consisting of multiple application servers maintained from a central administration point. In a distributed server environment, you can cluster application servers for workload distribution

Node, Node Agent and Cell A node is a logical grouping of server processes managed by WebSphere and that share common configuration . A node is associated with one physical installation of WebSphere Application Server. In a stand-alone application server configuration, there is only one node. With Network Deployment, you can configure multiple nodes to manage from one common administration server. Node Agent In these centralized management configurations, each node has a node agent that works with a deployment manager to manage administration processes

Cell A cell is a grouping of nodes into a single administrative domain. In the Base and Express configurations, a cell contains one node. In express and Base the configuration files for each server are stored and maintained individually. In a distributed server configuration, a cell can consist of multiple nodes which are all administered from a single point. The configuration and application files for all nodes in the cell are centralized into a cell master configuration repository.

Node Groups A node group is a grouping of nodes within a cell that have similar capabilities A node group validates that the node is capable of performing certain functions before allowing those functions A default node group called DefaultNodeGroup is automatically created for you when the deployment manager is created A node group establishes a boundary for cluster creation. All cluster members must be on nodes that are members of the same node group

Enterprise application installation

Installation Tasks
Configure the application environment as required Variables,virtual hosts,classpath,security etc. Configure application resources JDBC provider,datasources,JMS resources,SIBus etc. Install application Manage Static Content Files served by WebServer,not in EAR file Leave static content in EAR file

Starting an application
Starting an application server starts applications mapped to the server Order in which applications are started depends on the startup order Applications with lowest value are started first Applications with same value are not started in no particular order

Application Auto Start

Determines whether the application starts automatically when the server starts Default is to keep application started

Updating applications
Replace an entire application (.ear file). Replace, add, or remove a single module (.war, EJB .jar, .rar file). Replace, add, or remove a single file. Replace, add and remove multiple files by uploading a compressed file describing the actions to take.

Rollout Update does the following for each cluster member in sequence: 1. Saves the updated application configuration.
2. Stops all cluster members on a given node. 3. Updates the application on the node by synchronizing the configuration. 4. Restarts the stopped cluster members on that node.

Accessing Sample Applications http://localhost:9080/PlantsByWebSphere/ http://localhost:9080/WSsamples

 IBM HTTP Server

The following are the supported Web servers for WebSphere Application Server V6.1: Apache HTTP Server Domino Web Server IBM HTTP Server Microsoft Internet Information Services Sun Java System Web Server (formerly Sun ONE and iPlanet)

Generating Heap Dumps

Heap dump is in .phd format (Portable Heap Dump) IBM Heap Dump is created in <profile_root> directory when an out of Memory Exception error is thrown. Can be disabled with an environment variable HEAPDUMP_OUTOFMEMORY=false Enable Heap Dump IBM_HEAPDUMP=true IBM_JAVA_HEAPDUMP_TEXT=true Kill -3 <PID> -- generates Heap Dump