IBM® WebSphere® Everyplace® Deployment for Windows and Linux Version 6Web Container and Web Applications
IBM® WebSphere® Everyplace® Deployment for Windows and Linux Version 6 Web Container and Web Applications
This presentation explains the Web Container and Web Applications supported by IBM WebSphere Everyplace Deployment for Windows and Linux Version 6.
Goals
Goals Understand the Web Container and Web Applications provided by IBM WebSphere Everyplace Deployment for Windows and Linux Version 6
The goal of this presentation is to understand the Web Container and Web Applications supported by IBM WebSphere Everyplace Deployment for Windows and Linux Version 6.
Agenda
Agenda Web Container and Web Applications Application Capabilities Web Application Infrastructure Plug-in Descriptions Web Applications Web Container Description Web Container Configuration Web Container Serviceability Web Container SSL
The agenda of this presentation is to explain the Web Application capabilities the client platform provides to you, the infrastructure and plug-ins that enable these capabilities, and details about the Web Applications and Web Container supported by IBM WebSphere Everyplace Deployment for Windows and Linux Version 6.
Section
Section Web Container and Web Applications
So, let’s describe more details about the Web Container and Web Applications.
Application Capabilities
Application Capabilities “Simple” HTTP applications using OSGi HTTP Service Lightweight HTTP 1.0 Server with Servlet 2.1 implementation J2EE Style Web Applications using Web Container Supports Servlet 2.3 & JSP 1.2 Supports Servlet 2.4 & JSP 2.0 Supports Struts Must include Struts jars in Web Application Supports Java Server Faces (JSF) and JSP Standard Tag Libraries (JSTL) The client now provides JSF and JSTL jars as shared components to reduce memory requirements Legacy JSF applications may include the required JSF jars Servlet 2.4 JSP 2.0 Web Container OSGi HttpService
IBM WebSphere Everyplace Deployment for Windows and Linux Version 6 provides two methods to enable content serving via an HTTP Server – a basic, lightweight HTTP server and a Web Container. The basic Web Server model is the HttpService, which is an implementation of the OSGi specification for HttpService. The HttpService implements an HTTP 1.0 Web server with a Servlet 2.1 engine. The HttpService provides a complete implementation of the Servlet 2.1 specification. The HTTP Service enables other bundles to dynamically register and unregister servlets and other static resources such as GIF files. You can register HTML files, GIF files, class files, or any resources found via a URL. The Web Container provides the ability to run web applications serving content via servlets and JSPs. The Web container supports Servlet 2.4 and JSP 2.0 web applications as well as Servlet 2.3 and JSP 1.2 web applications. You can also develop and deploy Struts applications; however, the Struts runtime is not included in the client platform so you must include the Struts JARs in your Web application. You can also develop and deploy applications that use Java Server Faces (JSF) and JSP Standard Tag Libraries (JSTL). The runtime for both are now included in the client platform as shared components to reduce memory requirements so there is no need for you to include these JARs in your Web application. However, if you previously created JSF applications with these JARs to run on WCTME-EO 5.8.1, you may continue to do so and run these applications on the client platform.
Web Application Infrastructure
com.ibm.pvc.ras com.ibm.pvc.servlet.jsf Web Application Infrastructure com.ibm.osg.servlet com.ibm.pvc.servlet.jsp.jstl com.ibm.pvc.servlet.jsp org.apache.commons.el com.ibm.pvc.webhttpservice com.ibm.pvc.webcontainer com.ibm.osg.webapp org.osgi.service.webapplication com.ibm.pvc.servlet com.ibm.osg.service.http Compatibility for previous releases com.ibm.pvc.sharedbundle Installed with Minimal Install Optional Installed with Full Install Servlet 2.4 JSP 2.0 Web Container OSGi HttpService
This slide shows the Web Application infrastructure on the client platform, including the plug-ins (components) installed with the Minimal Install of the client platform and the additional plug-ins installed with the Full Install of the client platform. The Minimal Install provides the HttpService and Web Container to support Web applications. The Full Install adds support for Java Server Faces (JSF), JSP Standard Tag Libraries (JSTL) and the Expression Language Interpreter.
Plug-in Descriptions
Plug-in Descriptions Plug-in ID Description com.ibm.pvc.servlet Servlet APIs com.ibm.pvc.servlet.jsp JSP APIs com.ibm.pvc.servlet.jsp.jstl JSTL (JSP Standard Tag Library) implementation com.ibm.pvc.servlet.jsf JSF (JavaServer Faces) implementation org.osgi.service.webapplication OSGi Web Application Service com.ibm.pvc.httpservice OSGi HTTP Service com.ibm.pvc.webhttpservice OSGi HTTP Service for Web Container com.ibm.pvc.webcontainer Web Container com.ibm.pvc.ras Logging/Tracing APIs used by Web Container com.ibm.pvc.sharedbundle HttpSettingListener Interface org.apache.commons.el JSP 2.0 Expression Language Interpreter Servlet 2.4 JSP 2.0 Web Container OSGi HttpService
Here is the description of the plug-ins shown on the previous slide.
Web Applications
Web Applications Web Applications are standard OSGi bundles JSP content within Web Applications must be pre-compiled Toolkit Export wizards perform processing wab command line tool performs processing J2EE WAR files not directly supported – can preprocess using wab tool Servlet 2.4 JSP 2.0 Web Container
Since components in the client platform run as OSGi bundles, a Web application targeting the client platform is packaged and deployed as a Web Application Bundle or WAB. J2EE Web Archive (WAR) files cannot run directly on the client platform. Within the Rational Software Development Platform, the IBM WebSphere Everyplace Client Toolkit Version 6 Export wizards pre-compile the JSP content into the WAB so this processing does not occur when running the Web application on the client platform. When using other J2EE Web tools, you can export your Web applications into a standard WAR file and then use the WAB command line tool provided by IBM WebSphere Everyplace Deployment for Windows and Linux Version 6 to convert the WAR to a WAB, which pre-compiles the JSP content into the WAB.
Web Container Configuration
Web Container Configuration Configured via Java System Properties or Configuration Admin Can specify port to listen on (com.ibm.pvc.webcontainer.port property) 0 = dynamic port selection by web container n = use specified port number non-existent = does not listen on any port Can specify IP address to listen on (com.ibm.pvc.webcontainer.http.address property) default is localhost (can’t connect from another system) ALL = listen on all IP addresses Full list documented in System Administrator’s Guide and also Developer’s Guide Servlet 2.4 JSP 2.0 Web Container
Web Container Configuration
Web Container Configuration Locating web container configuration information in runtime Start platform with the console Locate the com.ibm.pvc.webcontainer bundle and note its id bundle osgi> b 46 update@/C:/Program Files/IBM/WED/rcp/eclipse/plugins/com.ibm.pvc.webcontainer_1.0.0.20050912/ [46] Id=46, Status=ACTIVE Data Root=C:\Documents and Settings\brianlil\IBM\RCP\1126979698778\brianlil\.config\org.eclip se.osgi\bundles\46\data Registered Services {org.osgi.service.cm.ManagedService}={http.redirectPort=-1, http.address=localhost, service.id=41, http.maxThreads=20, service.pid=com.ibm.pvc.webcontainer, http.timeout=60000, http.port=1489, http.maxKeepAliveRequests=50, http.scheme=http, http.maxKeepAliveTimeout=20000, http.minThreads=4, service.vendor=IBM, http.maxKeepAliveConnections=20} Servlet 2.4 JSP 2.0 Web Container
Web Container SSL
Web Container SSL Enabling SSL Set up keystore and truststore files Create SSL configuration file Specify the SSL configuration file (com.ibm.pvc.webcontainer.ssl.configfile property) Specify the port to use for SSL (com.ibm.pvc.webcontainer.port.secure property) same rules as HTTP port Web Container reads SSL configuration file and rewrites webcontainer.properties file Keystore and Truststore passwords obfuscated Servlet 2.4 JSP 2.0 Web Container
Web Container Serviceability
Web Container Serviceability WebContainer has tracing facilities Update trace.properties in com.ibm.pvc.ras plugin Change logredirector.level setting to capture trace output Documented in Application Developer’s Guide Servlet 2.4 JSP 2.0 Web Container
Slide 13
Trademarks, Copyrights, and Disclaimers The following terms are trademarks or registered trademarks of International Business Machines Corporation in the United States, other countries, or both: IBM CICS IMS MQSeries Tivoli IBM(logo) Cloudscape Informix OS/390 WebSphere e(logo)business DB2 iSeries OS/400 xSeries AIX DB2 Universal Database Lotus pSeries zSeries Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both. Microsoft, Windows, Windows NT, and the Windows logo are registered trademarks of Microsoft Corporation in the United States, other countries, or both. Intel, ActionMedia, LANDesk, MMX, Pentium and ProShare are trademarks of Intel Corporation in the United States, other countries, or both. UNIX is a registered trademark of The Open Group in the United States and other countries. Linux is a registered trademark of Linus Torvalds. Other company, product and service names may be trademarks or service marks of others. Product data has been reviewed for accuracy as of the date of initial publication. Product data is subject to change without notice. This document could include technical inaccuracies or typographical errors. IBM may make improvements and/or changes in the product(s) and/or program(s) described herein at any time without notice. Any statements regarding IBM's future direction and intent are subject to change or withdrawal without notice, and represent goals and objectives only. References in this document to IBM products, programs, or services does not imply that IBM intends to make such products, programs or services available in all countries in which IBM operates or does business. Any reference to an IBM Program Product in this document is not intended to state or imply that only that program product may be used. Any functionally equivalent program, that does not infringe IBM's intellectual property rights, may be used instead. Information is provided "AS IS" without warranty of any kind. THE INFORMATION PROVIDED IN THIS DOCUMENT IS DISTRIBUTED "AS IS" WITHOUT ANY WARRANTY, EITHER EXPRESS OR IMPLIED. IBM EXPRESSLY DISCLAIMS ANY WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NONINFRINGEMENT. IBM shall have no responsibility to update this information. IBM products are warranted, if at all, according to the terms and conditions of the agreements (e.g., IBM Customer Agreement, Statement of Limited Warranty, International Program License Agreement, etc.) under which they are provided. Information concerning non-IBM products was obtained from the suppliers of those products, their published announcements or other publicly available sources. IBM has not tested those products in connection with this publication and cannot confirm the accuracy of performance, compatibility or any other claims related to non-IBM products. IBM makes no representations or warranties, express or implied, regarding non-IBM products and services. The provision of the information contained herein is not intended to, and does not, grant any right or license under any IBM patents or copyrights. Inquiries regarding patent or copyright licenses should be made, in writing, to: IBM Director of Licensing IBM Corporation North Castle Drive Armonk, NY 10504-1785 U.S.A. Performance is based on measurements and projections using standard IBM benchmarks in a controlled environment. All customer examples described are presented as illustrations of how those customers have used IBM products and the results they may have achieved. The actual throughput or performance that any user will experience will vary depending upon considerations such as the amount of multiprogramming in the user's job stream, the I/O configuration, the storage configuration, and the workload processed. Therefore, no assurance can be given that an individual user will achieve throughput or performance improvements equivalent to the ratios stated here. © Copyright International Business Machines Corporation 2005. All rights reserved. Note to U.S. Government Users - Documentation related to restricted rights-Use, duplication or disclosure is subject to restrictions set forth in GSA ADP Schedule Contract and IBM Corp. Template Revision: 9/28/2005 5:50 PM