Websphere Application Server: Much more than Open Source


Published on

This presentation was given by Ishad M. Barot, Client Technical Professional, India(West) during Impact India 2012 on the 1st of June at Mumbai. It focuses on how businesses can save time and efforts using the WebSphere Application Server. WAS is much more than just being Open Source

Published in: Technology
  • Be the first to comment

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • http://www.freakonomics.com/
  • Licensed components for WAS Base: http://www-03.ibm.com/software/sla/sladb.nsf/lilookup/528E9221E0D1DF35002574BF0060E084?opendocument&li_select=CA2FDAD7AC1A2DC7002574BF0060E068Licensed components for WAS ND: http://www-03.ibm.com/software/sla/sladb.nsf/lilookup/73A19EC3265C0245852578690036E698?opendocument&li_select=E2E8EF2D66B931AA852578690036E685* - Java for Business: http://www.sun.com/software/javaforbusiness/getit.jsp – Oracle charges depending on the company size. For a small company the cost starts at $50K per year, for larger companies could be hundreds of thousands of dollars per year. One might argue that RHEL comes with the Apache OpenJDK included, however there are number of JIRA records on JBoss website that indicate security issues when using JBoss and JON with OpenJDK. IBM internal testing also shows that OpenJDK with JBoss has scalability issues – such as lack of ability to transfer large multi-megabyte SOAP XML messages using JAXWS implementation in JBoss (requests never finish).** - increase in hardware requirements is due to the slower performance of JBoss AS*** - WSMQ Extended Transactional Client is required for JBoss to support XA with remote WSMQ servers while this capability is included with WAS JMS provider out of the boxWebSphere includes free licenses of the following componentsWebSphere Edge Components: Load BalancerIP level workload management software that provides scalability and availability through server clustering and failover. Often used as a less expensive alternative to hardware load balancersWebSphere Edge Components: Caching Proxy Enhance user response time and off-load the app server JVMs by caching static and dynamic content, such as whole or fragments of Servlets and JSPs output, SOAP/HTTP web services DB2 databaseLimited for use for HTTP session persistence onlyTivoli DirectoryProduction grade LDAP serverJDKSupported version of the IBM JVM to run all of the Java applicationsWebSphere MQ Extended Transactional ClientUsed to support XA transactions to remote WebSphere MQ serversIBM HTTP Server (HIS)IHS is based on Apache web server (RedHat Linux includes supported Apache version)
  • These tests show single JVM scalability. With JBoss it is possible to slightly improve the vertical scaling by adding 2nd, 3rd or 4th JVM to run on a machine, however this significantly complicates administration as you now need to manage that many more resources as independent instances, have more overhead for memory, CPU, etc.
  • http://openjdk.java.net/groups/hotspot/docs/RuntimeOverview.htmlAverage SPECjbb performance of IBM submissions is 35% higher than HotSpot
  • Some of this info can be found here: http://www14.software.ibm.com/webapp/wsbroker/redirect?version=matt&product=was-nd-iseries&topic=cwsv_topologyFor ODR information, please refer to the WAS v8.5 infocenter
  • CSS: As a administrator, I want the WebSphere application server to mitigate common memory leaks that occur when stopping an application to avoid running out of memory because of those leaks.CSS: As an administrator, I want the ability to prevent leaks, receive leak warnings and get heap/system dumps when leaking applications are stoppedCSS: As an administrator I want  to use an MBean to display a list of previously stopped and/or restarted applications that have leaks and fix these leaks
  • 50 MB with no features“Footprint” is the Working Set i.e. total physical memory (RAM) used by the process.
  • Consider the implications and liabilities for a $1 vs. $1,000,000 transferThe implementation of the transaction can be done as a set of SQL statements in a stored procedure, JDBC code in Java, EJB code, BPEL flow, MS .NET, JMS, Web Services, etc. Implementations details do not matter a long as ACID properties of the transaction are maintained even during the events of hardware or power failures of all of the systems involved.There are patterns that allow to break one large transaction into many asynchronous steps, but eventually there must be a mechanism to ensure the reliable delivery and avoid duplication of messages in a long running asynchronous system.
  • Websphere Application Server: Much more than Open Source

    1. 1. So Much More Than Open Source: SaveCosts & Efforts with WebSphere ApplicationServerIrshad M. BarotClient Technical Professional – India (West)
    2. 2. Open Source Application Server landscape • Full Java EE 5 application server • Under Red Hat, no longer supports OSS directly. Instead they provide support for their commercial distribution called JBoss Enterprise Application Platform (EAP). • Open Source JBoss Community - self maintained and supported • Driven by developer loyalty, but 95% of R&D is funded by Red Hat. • Servlet container only - Java EE 6 Web Profile. Free OSS with Apache license • Developers like small memory and disk footprint, lightweight – fast restart • Tomcat is typically supported internally, but 3rd party support is available • Formerly Sun’s Java EE app server. • it is lightweight, has quick startup time and at the leading edge of the Java EE specs • No longer strategic for Oracle as it was for Sun 2
    3. 3. IBM contributions to Open Source go back 15+ years 1999 - 2001 2002 - 2003 2004 - 2006 2007 - today IBM forms Linux  Linux contributions to  IBM and Novell/SUSE achieve  IBM leads Open AJAX initiative and Technology Center scalability (8-way+), security milestone (EAL4+ and COE announces partnership with the reliability (stress compliance) Dojo Foundation Leads Apache testing, defect mgmt, projects Xerces doc)  Leads Apache Tuscany project (XML4J), Xalan,  Eclipse Foundation, Inc. becomes SOAP  Leads Apache independent - IBM contributes UML2,  Contributes code for security projects: Web Voice Tools, Aperi, COSMOS, Ajax management to Eclipse Higgins Creates OSI-approved Services (WSIF and Toolkit Framework  IBM contributes to Apache Lucene IBM Public License WSIL), Pluto (Portlet project and announces OmniFind API) and WSRP4J  Globus Toolkit 4 is WS-I compliant Yahoo! Edition Strategic participation (Remote Portal) in Mozilla  Pledged 500 patents to open source  IBM joins OpenOffice.org  Leads Eclipse IBM becomes projects GEF  IBM joins Open Health Tools, founding member of  Partner with Zend PHP moving code for medical record (editing), EMF OSDL (modeling), XSD management from Eclipse OHF  IBM enhances Apache partnership Founder of Eclipse.org (XML Schema), - Contributes Derby database  Contributes Open Services for ALM and Eclipse Hyades (testing), – Jazz REST Services samples Visual Editor, AspectJ, - Contributes voice recognition Consortium - Supports Geronimo J2EE project Equinox rich client  IBM creates ODF Toolkit Union - Acquires Gluecode for skills Creates internal  Contributes Lotus Notes/Domino bazaar using OSS  Globus Toolkit contributions for  IBM contributes accessibility code to app templates to OpenNTF.org methodology Firefox OGSA, OGSI  Incubates Apache Wink (JAX-RS) More than 1000 IBM developers IBM leads 80+ OSS projects IBM contributes to 150+ involved in OSS projects OSS projects
    4. 4. WebSphere takes advantage of the OpenSourceWebSphere Application Server 8.5 includes all or parts of over 70 Open Source projects Apache Aries
    5. 5. WebSphere Application Infrastructure Public cloud WebSphere Application WebSphere Application enablement Accelerator for Hybrid Networks Accelerator for Public NetworksPrivate cloud IBM Workload Deployer v3 (Images, Topologies, Patterns) enablement Mobile IBM Worklight server (Mobile device support: Apple, Android, etc.) Extreme WebSphere eXtreme Scale v7.1 WAS v8.5 batch support transactions DataPower XC10 Autonomics WebSphere Virtual Enterprise v7 (now part of WAS ND v8.5)and elasticity Feature Packs Foundation WebSphere Application Server v8.5 (Express, Base, ND, HV) JVM IBM JVM v1.6 or v1.7
    6. 6. Red Hat Application Infrastructure: lacksvision & reach No Application Acceleration No Application Acceleration for Hybrid Networks for Public Networks No Edge Appliance Alpha version of OpenShift No intelligent management capability No batch support  JBoss Infinispan (beta) No cache appliance Missing some of the Feature Pack capabilities  JBoss Application Server (EAP) 5.x  3rd party JVM (OpenJDK, Oracle JVM, etc.)
    7. 7. Which IBM product competes with JBoss AS? Mobile, Portlet, etc. Batch, OSGi, SIP, WAS Base WAS ND (or Express) JBoss Full JEEProgramming style Servlet/JSP Tomcat (PHP, Groovy, COBOL) Non-Java Small Medium Large Extra-Large Size of the environment and QoS
    8. 8. Red Hat JBoss Community vs. Enterprise JBoss Enterprise products are for Enterprise Developers who are building production applications and need:  Enterprise quality support from Red Hat during development and/or production with guaranteed SLAs  Pre-integrated and tested software thats certified multiple JVMs and Operating Systems  Continuous updates and patches to resolve security, performance, and stability issues  Notifications about security issues and advice on how to resolve them  Training and consulting services Free and Open Source Free and Open Source
    9. 9. 10%the hidden cost of software
    10. 10. Software license & subscription costs Gartner research note G00165072, March 2009: “Products available for• Cost of selection of the vendor software free (such as open• Requirements analysis and capture cost source), or those that• Developer, admin and end-user training cost are a "same cost" swap• Application design and development costs out, can cost more during• Cost of integration with other systems three- to five-year• Quality, user acceptance and other testing costs period than a first-time• Deployment cost commercial purchase• Operational support cost costing thousands of• Application enhancements and bug fixes cost dollars. To understand• Runtime price/performance analysis cost operation life cycle• Hardware and networking costs costs, a number of key• Product upgrades cost inputs are necessary to• SLA penalties• Downtime costs (planned and unplanned) provide a more realistic• Removal and disposal costs assessment of the total• Self-support costs costs of management• Cost of risks products.”
    11. 11. License cost comparison of additionalcomponents for App Server WAS WAS ND JBoss AS Management and monitoring Included Included $280 / core / year (JBoss JON) JON configuration DBMS n/a n/a ~ $3,750 / CPU / year (PostgreSQL) Hardware for the JON database n/a n/a ~ $10,000 + support (3rd party) Load Balancer Extra $ Included ~ $20,000 / device + support (3rd party) Dynamic content caching proxy Extra $ Included $5,000 / server / year (JBoss EWS)Page fragment & POJO caching Included Included ~ $1,000 / server / year (3rd party)HTTPSession persistence DBMS Included Included ~ $3,750 / CPU / year (PostgreSQL) LDAP Included Included ~ $9,000 / server / year (3rd party) JDK Included Included ~ $5,000 / core + support (3rd party*) XA integration with WSMQ Included Included ~ $7,500+ / CPU + support (IBM***) HTTP Server Included Included $2,500 / server / year (JBoss EWS) App Server Hardware $X $X $X + 60% (due to lower performance)
    12. 12. License + support cost over 5 years per server WAS WAS WAS WAS Base WAS Base WAS# of usersCores per Cores per IBM PVU IBM PVU SocketsServers Processor type Processor type Express Express Express min(PVU or JBoss EAP JBoss EAP Express min(PVU or metric metricsocket socket (users) (users) (PVU) (PVU) socket) socket) 0 104 Nehalem EX (2 socket) (2 socket) 2 10 Nehalem EX 70 70 na na na $180,000 $180,000 $243,438 na $243,438 0 84 Nehalem EX (2 socket) (2 socket) 2 8 Nehalem EX 70 70 na na na $180,000 $180,000 $190,000 na $190,000 0 64 Nehalem EX (2 socket) (2 socket) 2 6 Nehalem EX 70 70 na na na $180,000 $180,000 $160,315 na $160,315 0 104 Nehalem EX (4 socket) (4 100 4 10 Nehalem EX socket) 100 na na na $360,000 $360,000 $486,877 na $486,877 0 84 Nehalem EX (4 socket) (4 100 4 8 Nehalem EX socket) 100 na na na $360,000 $360,000 $380,000 na $380,000 0 64 Nehalem EX (4 socket) (4 100 4 6 Nehalem EX socket) 100 na na na $360,000 $360,000 $296,877 na $296,877 0 64 Nehalem EP 2 6 Nehalem EP 70 70 na na na $180,000 $180,000 $160,315 na $160,315 0 24 Intel Pre-Nehalem 1 2 Intel Pre-Nehalem 50 $4,406 50 $17,604 $4,406 $17,604 $35,460 $35,460 $53,438 $53,438 0 24 HP Itanium Itanium 1 2 HP 100 $4,406 100 $35,208 $4,406 $35,208 $70,920 $70,920 $53,438 $53,438 0 164 Sparc T3 Sparc T3 2 16 70 70 na na na $180,000 $180,000 $380,000 na $380,000 0 84 Power 7 (710, 740, (710, 740, etc) 70 2 8 Power 7 etc) 70 na na na $180,000 $180,000 $190,000 na $190,000 0 84 Power 7 (750, 755)(750, 755) 4 8 Power 7 100 100 na na na $360,000 $360,000 $380,000 na $380,000 0 24 Power 6 (520,JS12, (520,JS12, etc.) 80 2 2 Power 6 etc.) 80 $4,406 $56,333 $4,406 $56,333 $113,472 $113,472 $53,438 $53,438 0 24 Power 6 (550 and6 (550 and up) $4,406 2 2 Power up) 120 120 $84,499 $4,406 $84,499 $170,208 $170,208 $53,438 $53,438 0 84 Power 7 (770, 780)(770, 780) 8 8 Power 7 120 120 na na na $2,723,328 $760,000 $760,000 na $2,723,328 0 14 Systemz10Systemz10 1 1 120 $4,406 120 $21,125 $4,406 $21,125 $42,552 $42,552 $53,438 $53,438 0 14 Single coreSingle core (all) 1 1 (all) 100 $4,406 100 $17,604 $4,406 $17,604 $35,460 $35,460 $53,438 $53,438 In most cases WAS Express or Base license + support cost over 5 years is lower than that of JBoss.
    13. 13. TCO study: WAS vs. JBoss EAP v5 over five years Hands-on analysis of capabilities revealed that JBoss is 49% more expensive than WebSphereSource: Based on the study by Summa Technologies, December 2010
    14. 14. WAS development environment choicesFREE WebSphere Developer Tools for EclipseFREE WebSphere Application Server for Developers Available at no charge for the developer desktop/laptop (optional support is $949* per year)FREE WAS (and other IBM software) on IBM SmartCloud or Amazon EC2 ISVs and SIs can use IBM software for development, test, POC and demos. Software is free, only pay for machine time per hour (starting from 20 cents per hour)FREE WAS with Rational Application Developer Includes WAS and Portal test servers at no additional cost. RAD Standard costs $2,060* per developer, full RAD costs $4,860* per developer with first year of support included. Floating user license is also available (i.e. concurrent user license)FREE RAD with WebSphere Application Server Tools Editions Additional 3% on the cost of WAS or WAS ND provide unlimited licenses of RAD and WAS Developer Tools for Eclipse, which can be used only in support of the purchased production servers
    15. 15. WAS v8 is JEE6 certified since June 2011Enhanced developer productivity, user experiences, performance & integration:• Enterprise JavaBeans (EJB) 3.1:  Java API for RESTful Web Services (JAX- Enhanced developer productivity through RS) 1.1: Deliver better user experiences faster simplification including testing outside of the through integrated Web 2.0 prog model support application server, new timer support &  JavaServer Faces (JSF) 2.0: Enhanced async enhancements developer productivity & end user experience• Contexts and Dependency Injection for through annotations & Facelets support Java (CDI) 1.0: Faster time to value  Bean Validation 1.0: Improved developer through tighter and simpler integration productivity through declarative means for between Web & business logic tiers describing validation constraints for data• Java Persistence API (JPA) 2.0: Enhanced  Java Architecture for XML Binding (JAXB) developer ease of use & app performance 2.2: Improved performance via new default through improved locking, mapping support marshalling optimizations & dynamic query construction  Enterprise Web Services 1.3: Improved• Java Servlet 3.0: Enhanced time to value integration and reuse support through annotations and ease of integrating  Java API for XML-Based Web Services third party presentation frameworks (JAX-WS) 2.2: Developer productivity and security enhancements
    16. 16. IBM WebSphere 11 years of performance leadershipIBM WAS track record• Held the most records in ECPerf SPECjEnterprise2010• FIRST to publish SPECj2001• FIRST to publish SPECj2002 IBM: 524• FIRST and ONLY company to publish SPECj2002 Distributed Oracle: 452• FIRST to publish SPECj2004 – Was the only vendor to publish for over 13 months JBoss: 0 (never published) – Held #1 spot for most of the time EjOPS per second per processor core• FIRST to publish SPECjEnterprise2010• LOWEST cost per transaction 1. WAS V8.5 on Westmere-EP 2. WLS 10.3.5 on Westmere-EP• BEST performance per core
    17. 17. WebSphere release-to-release performance
    18. 18. WebSphere has superior vertical scaling when compared to JBossApplication Server:•IBM x3550 M2, Intel Xeon X5570 @ 2.93 GHz, 2x4 cores x 2 threads,114 GB RAM, RHEL 5.5 (64 bit)•IBM WebSphere 7 (64 bit) / JBoss EAP 5.0.1+Sun JDK (64 bit)•Apache Day TraderDatabase Server:•IBM x3755 MC1, AMD Opteron 8360SE @ 2.0 GHz, 4x4 cores, 15 GB RAM, RHEL 5.5 (64 bit)•IBM DB2 9.7 Source: IBM SWG CPO, December 2010
    19. 19. IBM J9 JVM competitive advantages IBM J9 Hot Spot, OpenJDK Fast garbage collection for large heap sizes (>4GB) - -Xgcpolicy:balanced Yes No System class data sharing for reduced memory footprint and faster startup Yes Client onlyApplication class data sharing for smaller memory footprint and faster startup Yes No Avoid JVM restarts due to the PermGen filling up Yes No Compressed 64-bit references (for faster runtime and smaller memory) Yes Recent Troubleshooting tools for JVM (heap dump, garbage analyzer, etc.) Yes No Faster performance per core Yes No*
    20. 20. Intelligent Management Extending QoS through autonomic computing Application Health Dynamic Edition Management Clustering Management Self-Protecting Self-Optimizing Self-Managing Self-HealingStockTrading 1.0 Finance 3.0 StockTrading 2.0 Finance 4.0 StockTrading 3.0 Intelligent Routing
    21. 21. Intelligent routing - new ODR capability fromWVE (now WASND) WASND F5 + JBossSLA enforcement. Prioritizes requests based on service policies and current Yes No capacity and conditionsEnables dynamic clusters of application servers to scale load when needed Yes No based on service policies Application edition-aware routing. Yes No Continuous availability during updates CPU and heap overload protection Yes No Dynamically recognizes when routing information changes Yes No (e.g. app/ server/node add/remove/change) Dynamically adjusts server weights Yes No based upon servers current resources and response times Performs HTTP session re-balancing Yes No Reacts to server starts and stops without retries Yes No Load balances or fails over between clusters Yes Yes in the same or different cells Supports content-based routing rules Yes Yes Static file serving and in-memory and disk page caching Yes* No* - WASND ships with (1) Proxy Server and (2) DMZ Secure Proxy and (3) IBM HTTP Server
    22. 22. Application Edition Management Applications can be upgraded without incurring outages  Upgrade Applications without interruption to end users  Concurrently run multiple editions of an applications •Automatically route users to a specific application  Multiple editions can be activated for extended periods of time  Rollout policies to switch from one edition to another without service loss  Easily update OS or WebSphere without incurring down time  Easy-to-use edition control center in admin console, plus full scripting support Validation Rollout Concurrent Mode Policies Activation22
    23. 23. Dynamic Clustering Proactively provision and start or stop application servers based on workload demands to meet Service Level Agreements  Associate service policies with your applications •Let WebSphere manage to the service goals  Programmatically respond to spikes in demand •Add or reduce application server instances as appropriate  Automatically recover from infrastructure problems  Includes automatic start and stop of cluster members based on load for MQ-driven applications  Decrease administrative overhead required to monitor and diagnose performance issues23
    24. 24. Lazy Application Start• Dynamic Clusters support a min and max number of running cluster members• If the “stop all instances” option is enabled, the min is 0, which means: The application may not be running in the pool anywhere When a request is received, a cluster member is started When the application goes idle all clusters members are stopped This allows low volume applications to be available without consuming resources. A customizable On Demand Router error page with meta-refresh provides a user-friendly customer experience
    25. 25. Overload ProtectionMaximum heaputilizationprotects againstOutOfMemoryexceptionsMaximum CPUutilizationprotectsagainst variousfailures whichoccur whenCPU isconsumedRejects excesstraffic withoutaffinity whenoverload occurs
    26. 26. Memory leak detection Protection in WAS Reduce possibilities Get enough info. List stopped of memory leak in if leak is detected apps that have your applications to help fix my app memory leaks WebSphere Application Server V8.5: • Ability to mitigate memory leak when stopping apps • Ability to prevent leaks, receive leak warnings and get heap/system dumps • MBean to list stopped apps that have memory leaks26
    27. 27. Health Management – Health Policies Helps mitigate common health problems before outages occur Health policies can be defined for common server health conditions When a health policys condition is true, corrective action execute automatically or require approval • Notify administrator (send email or SNMP trap) • Capture diagnostics (generate heap dump, java core) • Restart server Excessive response time means you are monitoring what matters most: your customers experience! Application server restarts are done in a way that prevent outages and service policy Health Conditions violations • Excessive request timeouts: % of timed out requests Each health policy can be in supervise or • Excessive response time: average response time automatic mode. Supervise mode is like • Excessive garbage collection: % of time spent in GCs training wheels to allow you to verify that a health policy does what you want before • Excessive memory: % of maximum JVM heap size making it automatic. • Age-based: amount of time server has been running • Memory leak: JVM heap size after garbage collection • Storm drain: significant drop in response time • Workload: total number of requests
    28. 28. WAS v8.5: Introduces the Lightweight Liberty” Profile A highly composable, dynamic Server profile Dynamic Server Profile Developer First Focus Not static like Web Profile – Simplified, shareable server config (like a determines by app at a fine- dev. artifact). One XML file or several to grained level simplify sharing & reuse of configIncredibly fast: Small Download:start times: < 5 secs < 50MBLightweight runtime Dynamic RuntimeSmall memory footprint: Adding features & updating WAS v8.5 configs does not require(60MB for TradeLite) Liberty Profile server restart Integrated Tooling Integration with ND Job Mgr Powerful tools. Simple Optionally manage server Eclipse feature lifecycle through ND Job Mgr Unzip Install & Deploy Popular Platforms Fidelity to full profile WAS IM or unzip to install. Unzip Adds MAC OS for Same reliable containers & QOS deploy of server + app + config development (easy migration from dev to ops)
    29. 29. How do Red Hat customers really use JBossAS in production?• Less than 5% of JBoss customers use clustering – Must tolerate lower quality of services ($$$) – Or use 3rd party tools to achieve high availability ($$$) and• Most JBoss customers purchase 3rd party management tools, monitoring tools, configuration management tools, performance profilers, etc. – 3rd party tools require license and support payments ($$$) – 3rd party tools are not always in synch with the desired version of JBoss ($$$) – 3rd party vendor viability poses risks ($$$) and• Most JBoss customers invest significant staff time to build home grown scripting frameworks for JBoss management (a combination of shell scripting and generation of JBoss XML files using XSLT, Java or other template mechanism) – Cost to develop, debug, maintain such scripts can be significant ($$$) – New versions of JBoss (major or minor) are not 100% backwards compatible, causing significant rework of home grown scripts and tools ($$$)• WAS ND provides all needed administrative tools out of the box at no extra cost
    30. 30. Documentation – order of magnitude difference in quality JBoss docs – limited and inconsistent, lags in time JBoss wikis – lots of old confusing info User forums – no longer monitored by developersInfoCenter – world class, up to dateRedbooks – unique and comprehensivedeveloperWorks - implementation tipsISA – electronic support search tool3rd party – sites, blogs, etc.User forums – self help
    31. 31. The saga of a one million dollars Failure Remote cloud (future) Account 1 Account 1 balance = $1M balance = $1M Failure Failure Credit Card System Failure Failure Account 1 Account 1balance = $1M balance = $1M Account 1 Internet Banking System Audit Log balance = $1M Failure Failure Failure Types of failures: 1. Power outage Transaction: Transfer $1M Failure 2. Network error or outage 1. Check funds availability in Account1 3. Software failure (OS, DBMS, etc.) 2. Withdraw funds from the Account1 4. Hardware failure 3. Debit funds to the Account2 5. Human error 4. Update related systems with the right information 6. Application error 5. Write into the audit log for security and compliance reasons 7. DoS or other attack 8. Combination of any of the above Failure Failure Failure Failure Account 1 Account 2 Initial state: balance = $1M balance = $0 Account 1 Account 2 Possible outcome 1: balance = $0M balance = $0M Account 1 Account 2 Possible outcome 2: balance = $1M balance = $1M Account 1 Account 2 Desired outcome 3: balance = $0M balance = $1M
    32. 32. Highly available transaction log• Provides Failover of In-flight 2 PC transactions• WAS-ND Can Be Configured to Store Transaction Logs For Each Server on a NAS (Network Attached Storage) or Shared File System – Allows All Peers to See All Transaction Logs – Automatic HAManager Recovery requires that the distributed file in use provide the necessary file locking semantics• When a WAS-ND cluster Member Fails, a Peer is Elected to Recover the Transaction Log From the Failed Server – In Doubt Transactions From a Failed Server Are Recovered Very Quickly – Significantly Faster Than Hardware Clustering • Recovery Can Take Minutes • Requires OS Clustering & Shared Disk – Recovery in a few seconds • Design Criteria < 1 sec.• Not Enabled By Default For a Cluster – Enable failover of transaction log recovery• JBoss does not provide transaction log failover
    33. 33. Security issues with JBoss• No role-based administrative security (“Who can do what?”)• No resource scope separation for admin users (“Who can manage what?”)• Clustered configuration is insecure – Can lead to ad hoc clusters and unexpected downtime, unauthorized instances can join the cluster and hijack workload – Must have file system level access to all servers, which is often not an option in secure environmentsThese issues result in increased administration costs when using JBossbecause of lost productivity. These issues increase risks to the organizationdue to loss/theft of data or loss of business due to unplanned downtime.
    34. 34. FREE WebSphere Migration Toolkit (Eclipse plugin) Oracle WebLogic OC4J• Migrate WebSphere applications from older (OAS) releases to WAS v7.0, v8.0 or v8.5 – Migrate applications from v5.1, v6.0, v6.1, v7.0 and v8.0 WAS Tomcat JBoss• Migrate From Oracle (WebLogic & OracleAS), v5, v6, JBoss or Tomcat to WebSphere Faster/Easier v7, v8 – Migrate applications 2x as fast – Migrate web services 3x as fast• The tool programmatically scans customer applications and identifies the changes required – In many cases the tool is capable of making the application change itself, in other cases it provides WebSphere Migration Toolkit guidance on how to make the required change – Generate reports to assess the migration task• Ease the migration process and speed time to value with this Free toolkit WebSphere Application Server v7, v8, v8.5 Now easier then ever before to migrate your applications to WebSphere Application Server
    35. 35. Thank You