WebSphere Application Server Community Edition v1.0 Overview

1
WebSphere Application Server Community Edition
v1.0 Overview

• Adopting the Community Edition of WAS

2
Agenda

• What is WAS-Community Edition?
• Supported Platforms
• Support
• Installation
• Administration
• Application Deployment
• Sources of Further Information

3
The Middleware Game is Changing
Innovation in technology and in business models
continues to keep the enterprise application
server market competitive and expanding, despite
growing commoditization of basic J2EE application
servers. New players continue to emerge to offer
alternatives and to aim at the leaders'
weaknesses. Gartner Magic Quadrant for
Enterprise Application Servers, 2Q05
Forrester has found that availability of
high-quality professional support is the major
barrier to widespread adoption of open source
projects. Forrester, September 2004
After a period of testing by early adopters,
firms are beginning to use open source software
. in critical projects Forrester, Nov 2004
New license revenue is no longer the singular
measure of success and influence in the
Enterprise Application Server market. Gartner,
2005
Supported open source products provide a third
choice between freeware and more robust
products IDC
Customers have begun to evaluate and deploy
Supported Open Source Middleware for certain
projects
4
IBMs Strategic Direction in the Open Source
Application Server Market

• New developers, partners customers who do not
  need more than supported Open Source they seek a
  subscription-based model that represents revenue
  IBM was not previously able to address

Address a new set of customers
Leading to IBM Cross-sell Upsell Opportunities
in the Future
Some new developers, partners customers that
will naturally grow across the IBM portfolio
value proposition in the future
5
IBM Addresses Open Source Middleware Market
Momentum

• Acquisition of Gluecode Software May 2005
• Capitalize on the market shift, contribute to the
  energy and momentum

IBM makes a major commitment to Apache Geronimo
as the Open Source Application Server of the
future

• Announced worldwide IBM Support for Apache
  Geronimo offering
• Contributed Plug-in Management Console
  technology
• Achieves major milestones industry
  participation increasing

IBM introduces WebSphere Application Server
Community Edition

• A lightweight J2EE application server built on
  Apache Geronimo technology
• Announced worldwide IBM Support for WebSphere
  Application Server Community Edition offerings

6
What is WebSphere Application Server Community
Edition?

• A lightweight J2EE application server built on
  Apache Geronimo technology

No UpfrontCosts
World-class Support (optional,fee-based)
7
Key Customer Benefits

• World-class support Choice of 3 support levels
  from basic to 24x7
• Get started with no upfront costs Download and
  show tangible results quickly
• Pre-integrated to save you time and money
  Includes all the baseline components for you to
  develop and deploy your application quickly
• Customize to tailor to your needs Extend with
  additional features or remove unnecessary
  components to streamline footprint
• Path to advanced capabilities Access other
  middleware products from the IBM WebSphere family
  as your needs grow

8
WebSphere Application Server Family
Proven performance/ scalability, enterprise wide
deployment, functional depth, robustness
WebSphere Application Server for zOS
WebSphere Extended Deployment
WebSphere Application Server Network Deployment
Customer Needs
WebSphere Application Server
WebSphere Application Server - Express
Reduced acquisition costs Rapidly develop
deploy departmental apps, small footprint..
WebSphere Application Server Community Edition
Built on a common codebase
Built on open source technology
High transaction volumes, High Availability,
Advanced Web Services Optimized resource
utilization
Basic security, easy administration and
deployment of single application, low transaction
volumes
Capabilities
9
WebSphere Application Server Community Edition
Key Features

• J2EE 1.4 Compatible
• Leverages Apache Geronimo for support of J2EE
  specifications
• Certified on the IBM 1.4.2 JDK
• Database Support
• Integrated IBM Cloudscape database supported for
  development and production
• IBM DB2, MySQL, MS SQL Server and Oracle
• Full Eclipse web tools support
• Eclipse plug-in for creating, deploying, and
  debugging applications
• Runtime customization
• Architecture enables runtime customization to
  save systems resources and improve performance
• Centralized configuration and control
• Easy-to-use administrative console technology
  preview for managing monitoring the application
  server and related resources
• Small Footprint 60MB download
• Easy access - downloadable in minutes

10
Optional Fee-based IBM Support Offerings
11
IBM Services Offerings for WebSphere Application
Server Community Edition

• Architecture and Design Review
• Review current application/middleware
  architecture and make recommendations on
  enhancements
• Migration planning and implementation assistance
• Provide migration assistance from planning to
  code manipulation to move applications from
  competitive platforms (JBoss, Tomcat, BEA) to
  WebSphere Application Server Community Edition,
  or to migrate WebSphere Application Server
  Community Edition applications to the WebSphere
  platform
• Application Building engagement
• Focused on building and deploying applications to
  solve specific customer problems

12
Why Choose WebSphere Application Community
Edition ?

• IBMs Strategic Commitment to Open Source,
  Apache Geronimo and WebSphere Application Server
  Community Edition
• True Open Community of Apache Geronimo community
  with broad industry participation IBMs first
  mover advantage
• Vendor Stability of IBM our Partners
• Trusted Support and Service from IBM our
  Partners
• Future Migration to the IBM Software Portfolio
  as needs grow
• WebSphere Application Server Market Share
  Addresses customers seeking to align with their
  WebSphere investments
• Cost Trusted support from IBM our Partners for
  less than competitors for comparable support
  offerings

13
Installation

• Varies with platform and whether the included IBM
  JRE is to be used.
• Go to the IBM web site and download.
• Easiest way to get to this is via
  http//www.gluecode.com
• Official link is
• http//www-128.ibm.com/developerworks/downloads/ws
  /wasce
• Select your target platform
• We recommend taking the IBM 1.4.2SR3 JRE packaged
  version
• Avoids complexities of having EXACTLY the right
  version of the Sun JRE (i.e. 1.4.2_09) and
  managing the numerous current patches to it
• REALLY sensitive to the version of the JRE
  installed!!!!!!
• Dont forget the web server plug-in from Apache!

14
Installation (2)
15
Installation (3)
wasce_setup-1.0.0.1.bin Linux32/Intel 38MB
wasce_setup-1.0.0.1.exe Win32/Intel 40MB
wasce_ibm142jre_setup-1.0.0.1.tar Linux32/Intel
76MB IBM JRE
wasce_ibm142jre_setup-1.0.0.1.zip Win32/Intel
78MB IBM JRE
Eclipse v3.1.1 Plug-In for this release of WASCE
Only (6MB) - Not for RAD!
Sample J2EE Applications (2MB)
Documentation (2MB)
16
Installation (4)

• For Windows ZIP and Linux TAR files
• Unzip/tar xvf the files
• Run the IBM 1.4.2 SR3 JRE Setup
• MSI-based InstallShield installation on Windows
• InstallShield installer on Linux
• Run the WASCE Setup - the same as the procedure
  for the versions without the JRE
• Windows WASCE Setup - MSI-based InstallShield
  installation
• Linux WASCE Setup - Complex InstallShield Shell
  Scripts
• Possible these can be made to work on unsupported
  platforms
• Rename to .sh, amend the scripts, etc
• Alternatively, copy the WAS CE Java code and just
  run it by hand!

17
Installation (5) - Windows JRE

• No need to make this the System JRE
• Advantages to making it separate for use just by
  WAS CE, i.e. no requirement to patch it for use
  by other applications

18
Installation (6)

• Although Free the software is still licensed.
• The AppServer requires 57.6MB only - Much less
  than WAS!!!

Installs in C\Program Files\IBM\WebSphere\AppServ
erCommunityEdition by default
19
Installation (7) - Windows Problem

• Beware - a connection to a domain controller is
  required for the installation due to test of the
  machine account rights. Error 1789.

20
Installation (8) - Linux Scripts
21
Installation (9) - Linux Problem

• Expect to see this if you havent used the IBM
  JRE or been VERY careful with the Sun JRE!

This application requires a Java Run Time
Environment (JRE) to run. Searching for one on
your computer was not successful. Please use the
command line switch -isjavahome to specify a
valid JRE. For more help use the option
-ishelp.
22
Installation Directories (1)

• After installation, C\Program
  Files\IBM\WebSphere\AppServerCommunityEdition
  contains
• bin Contains executables for starting and
  stopping the application server, for managing and
  deploying to it, and the glue executable for the
  server itself.
• config-store Contains libraries and components
  that make up the application server bundle, and
  the adminconsole application code. Also contains
  applications deployed onto the application server
  under a set of numbered sub-directories.
• doc Contains the XML files, under the plan
  sub-directory, that contain the core
  configuration and JMX bean configuration for the
  application server.
• graphics Contains the bitmaps and icons used by
  the tooling.

23
Installation Directories (2)

• lib Contains the JAR files for the application
  server components
• license Contains text files for the license for
  the application server.
• repository Contains application server
  components in the form of Java Archive (JAR) and
  Resource Archive (RAR) files. The RAR files are
  configured and used for external connectivity.
• schema Contains the XML Schema and DTD files
  for validating the environment and applications
  against the J2EE standards.
• var Contains log files, configuration property
  files, and runtime environments for components of
  the application server. The runtime environments
  may consist of flat files containing data, XML
  files, or even serialised Java objects. This
  subdirectory must be secured so only
  administrative access is allowed.
• _uninst Contains executables and configuration
  for uninstallation

24
Installation Directories (3)

• var subdirectory contains the following
  subdirectories
• activemq for the ActiveMQ message queuing support
• catalina for the Apache Tomcat JSP and servlet
  engine support
• config for the configuration of Apache Tomcat and
  the server environment
• derby for the built in Java-based database
  management system (apache Derby, based on IBM
  Cloudscape) and its system database
• log for the application server log, deployer log,
  and the logging properties.
• security for the user information configuration
  and keystore
• txlog for the application server transaction logs.

25
Web Server Plug-In

• Tomcat often used for static pages, but a web
  server can be used
• Supports load balancing and failover
• Uses AJP13 TCP protocol to communicate HTTP
  information between the plug-in and the
  application server
• Use mod_jk Apache Tomcat connector
• Download the C source and compile it
• Configure workers.properties file
• Contains protocol, caching, and IP information
• Documentation is at http//tomcat.apache.org/conn
  ectors-doc/
• Get from the Apache Tomcat site
  http//tomcat.apache.org/
• Also change the web server configuration and
  maybe Tomcat

26
Ports
27
Starting the App Server (1)

• Windows
• Use the Start the Server icon on the Start
  Menu
• Under All Programs-IBM WebSphere-Applicatio
  n Server Community Edition
• Or use startup.bat or startserver.exe under
  bin
• Add startserver.exe to the startup group for
  production
• Linux
• Use startServer.sh
• Can start the server with a single application
  only
• java -jar server.jar application_name

28
Starting the App Server (2)

• Fairly familiar - similar to WAS!

29
Administration (1)

• Uses a WAS-like admin console
• Has a different layout so takes getting used to
• URL is http//localhost8080/console/portal/server
  /server_info
• or http//localhost8080/console
• Can use Windows Start Menu Icon
• All Programs-IBM WebSphere-Application
  Server Community Edition-Administrative
  Console
• Logon for the first time with User id system
  and password manager

30
Administration (2)
31
Administration (3)
Server config and control
Status information
Services (i.e. JMS, Mail, DB, etc)
Application configuration
Security configuration
32
Administration (4) - Databases
Setting up database connectivity, such as for
entity beans, is very similar to that in WAS.
Select Database Pools to set up JDBC Services
33
Deployment (1)

• Most annoying part of using WAS-CE.
• Uses an EAR file
• A lot of the time requires an XML plan file
• Works without it using defaults more than the
  docs suggest
• WHY!!!!!!
• Docs suggest Deployment Descriptor is
  insufficient

34
Deployment (2)
Applications can be stopped and started
independently of the server
Installed applications and their status
EAR File
PLAN File
35
Deployment (3) - Command Line

• Use deploy.bat batch file or deploy.sh
• Thin wrapper for deployer.jar
• Found under the bin directory
• Allows applications to be deployed, undeployed,
  redeployed, or started and stopped individually.
• Syntax is
• deploy command user USERID password PASSWORD
  file planxml
• Applications deployed under config-store
  directory
• Subdirectory named after a generated number to
  separate the applications from each other.

36
Deployment (4) - Command Line

• For example,
• deploy deploy uuser system password manager
  c\myejb.ear myplan.xml
• Deploys the application myejb and starts it
  running.
• Use distribute rather than deploy to not
  start the app
• Note that for a simple application the myplan.xml
  file, i.e. the deployment plan, can be omitted.
• Server must be running unless distribute is
  used
• User will be prompted for a username and password
• Status of the deployment will be displayed.

37
Deployment (5) - Plans

• Different types of plans for EAR, WAR, RAR,
  EJB-Jar, etc deployment archives
• Hangover from Apache Geronimo
• Often just contains the name of the application -
  so WHY!!!!!
• Beware reusing the name in plan for more than one
  application
• Duplicates some of the standard Deployment
  Descriptor information
• Plans can be deployed separately or in the
  archive file

38
Deployment (6) - Plans

• xmlnshttp//geronimo.apache.org/xml/ns/web
• xmlnsnaming"http//geronimo.apache.org/xml/ns/
  naming"
• configId"HelloApp"
• /simpledemo

WebApp WAS CE Module Name
WebApp Context Root - Duplicates information in
web.xml
Web Application Plan
39
Deployment (7) - Plans

• /ns/j2ee/application"
• configId"myear"
• myweb.war
• /xml/ns/web"
• configId"Web" parentId"myear"
• myejb.jar
• /xml/ns/openejb-jar"
• configId"myejb"
• parentId"Web"
• mysession
  
• ejb/mysession-name

Duplicates the Deployment Descriptor information!
40
Architecture

• Every manageable component is a GBean
• includes core services (i.e. ActiveMQ, OpenEJB)
• A GBean is a Geronimo Bean
• Shows the Apache Geronimo heritage
• Each GBean has an XML deployment plan
• Think JMX!
• Application Server configuration process changes
  the deployment plan XML files

41
Additional Resources

• WAS CE Documentation
• http//publib.boulder.ibm.com/wasce/V1.0/
• WAS CE DeveloperWorks
• http//www.ibm.com/developerworks/downloads/ws/was
  ce/?S_TACT105AGX67S_CMPEMAIL
• Apache Geronimo
• http//geronimo.apache.org