New Intelligent Management Features of the WebSphere Web Server Plugin

Transcription

1 New Intelligent Management Features of the WebSphere Web Server Plugin Keith Smith, STSM, DataPower Edge, WebSphere VE, Resiliency IBM Session Number Here

2 Please Note IBM s statements regarding its plans, directions, and intent are subject to change or withdrawal without notice at IBM s sole discretion. Information regarding potential future products is intended to outline our general product direction and it should not be relied on in making a purchasing decision. The information mentioned regarding potential future products is not a commitment, promise, or legal obligation to deliver any material, code or functionality. Information about potential future products may not be incorporated into any contract. The development, release, and timing of any future features or functionality described for our products remains at our sole discretion. Performance is based on measurements and projections using standard IBM benchmarks in a controlled environment. The actual throughput or performance that any user will experience will vary depending upon many factors, including 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 results similar to those stated here.

3 Agenda On Demand Router (ODR) Overview ODR Strategies and Topologies WebSphere Web Server Plugin Intelligent Management Features Overview Configuring Intelligent Management Understanding How It Works Not Yet

4 On Demand Router (ODR) Overview ODR is a java-based HTTP & SIP proxy built on the WebSphere run-time ODR is a new server type, but is not an application server ODR is cluster-able and administer-able, like an application server ODR is an intelligent router which is central to providing Intelligent Management features such as: editions, health policies, traffic shaping, service policies, etc

5 Yesterday's WebSphere ODR Strategy Today's Standard Topology WebServer Tier Goal was to: Make ODR DMZ-ready Implement all Web server features in ODR Replace Web server with ODR ODR Tier AppServer Tier Used-To-Be Tomorrow's Topology ODR Tier AppServer Tier

6 Yesterday's WebSphere ODR Strategy (continued) Advantages Re-use of java runtime components between java ODR and application server Scalability because of efficient thread usage Disadvantages Implementing all web server features is a moving target and costly Replacing the web server is unreasonable Since the web server is most often still required, the additional tier increases complexity, maintenance, and TCO and is less resilient

7 Yesterday's DataPower ODR Strategy Re-implement ODR features in C for the DataPower appliance, known as the AO option ( Optimization) Disadvantages: Error prone, or just didn't work quite the same, perhaps with slightly different semantics Always a few steps behind from a feature perspective Costly for IBM to develope DataPower /AO re-implements ODR AppServer Tier

8 Today's Unified ODR Strategy ODRLIB is a common C library which is used by both: 1)DataPower physical and virtual appliances; and 2)WebSphere web server plugin for Apache/IHS DataPower w/ ODRLIB ODRLIB WebSphere Connector AppServer Tier ODRLIB is the single strategic webbased connector to the WebSphere Server IHS/Apache w/ ODRLIB AppServer Tier

9 Today's Unified ODR Strategy (continued) Advantages 1) With a single shared implementation: Increased quality/resilience Faster delivery of new features Ease of migration between offerings Functional equivalence between DataPower (DP) and IHS/Apache 2) For the DataPower topology: The premier WebSphere connector Will include all ODR features + DP DataPower w/ ODRLIB ODRLIB AppServer Tier 3) For the IHS/Apache topology: Easily pick-n-choose Intelligent Management features with no topology change Less to learn in order to use the Intelligent Management features Simpler topology to size, test, maintain, and debug leading to decreased TCO and increased resilience Decreased latency due to one less hop IHS/Apache w/ ODRLIB AppServer Tier

10 Intelligent Management Features Overview WebSphere Web Server Plugin for Apache/IHS 1) Automatic routing The web server plugin automatically discovers and recognizes all changes which affect routing: server/cluster create/start/stop/delete, application install/start/stop/uninstall, virtual host updates, session affinity configuration changes, dynamic server weight changes, etc. 2) edition routing Validation mode, application edition routing rules, continuous availability during atomic/group hard/soft rollout, concurrent editions 3) edition caching Plugin's ESI (Edge Side Include) cache is edition-aware

11 Intelligent Management Features Overview 4) Health policies The plugin supports ODR-related health policies: Excessive Response Time Excessive Request Timeout 5) Dynamic clusters APC ( Placement Controller) dynamically starts/stops servers to meet demand with APC.predictor=CPU. Plugin automatically routes appropriately. 6) Node and server maintenance mode When a node or server is placed into maintenance mode, the plugin automatically routes appropriately

12 Intelligent Management Features Overview 7) Multi-cell routing A single plugin automatically routes to different applications in multiple cells Routing to the same application in multiple cells is not yet supported, which requires ODR routing rule support 8) WLOR (Weighted Least Outstanding) load balancing Evens out response times due to dynamically changing weights Quick to send less traffic to slow or hung servers 9) Per-request conditional trace 10) Retrieve plugin routing info via Apache's mod-status Available in JSON format for consumption by monitoring tools 11) Highly-available REST-based control connection to WebSphere DMZ-friendly; no application to install or additional configuration required; REST-based service automatically available in WAS 855 dmgr and nodeagent; plugin fails over when needed.

13 Configuring Intelligent Management for IHS/Apache From the WebSphere administrative console or via scripting: 1) Create an Apache or IHS web server on a managed or unmanaged node (as usual) 2) Enable the Intelligent Management feature for the web server. > Server Types > Web servers Select a web server Select Intelligent Management under Additional Properties Select the Enable check box 3) Optionally add additional cells A web server is managed from a single cell, but that web server can route to multiple cells. Adding additional cells allows the web server to route to multiple cells. 4) Generate and propagate the plugin (as usual)

14 Configuring Intelligent Management for Apache/IHS Enable Intelligent Management for this Web server Add other cells to which this Web server will route

15 Plugin-cfg.xml example New IM Stanza Cell 1 connectors There is a single control connection per cell, but with failover. A REST service runs in the dmgr and each node agent for high availability. Cell 2 connectors All of the routing information is obtained dynamically, so there is no application or application server information in the plugincfg.xml.

16 Per-request conditional trace Enable trace for only requests which match the specified condition Fine-grained trace enablement; both hierarchichal and levelbased Allows selective trace enablement for problem determination (e.g. why is it breaking affinity?)

17 Intelligent Management Routing Info To view via mod-status: Returns JSON format for easy consumption by monitoring tools Types of information returned: Clusters and servers Connector groups show status of the control connection to the REST service

18 Intelligent Management in Apache/IHS's Multi-Process Model IM Daemon Process IM REST service Cluster Cell 1 Parent Listener Process Child Worker Process #1 Child Worker Process #N IM REST service Cluster Cell N Legend: HTTP request traffic: Unix Domain socket: REST:

19 ODR Features Not Yet Supported by WebSphere Plugin ) ODR routing rules No load balancing or failover between cells 2) CPU or memory overload protection 3) Request prioritization No queueing and re-ordering of requests based on service policies 4) Highly available deployment manager

20 We love your Feedback! Don t forget to submit your Impact session and speaker feedback! Your feedback is very important to us we use it to improve next year s conference Go to the Impact 2013 SmartSite ( Use the session ID number to locate the session Click the Take Survey link Submit your feedback

21

22 Legal Disclaimer IBM Corporation All Rights Reserved. The information contained in this publication is provided for informational purposes only. While efforts were made to verify the completeness and accuracy of the information contained in this publication, it is provided AS IS without warranty of any kind, express or implied. In addition, this information is based on IBM s current product plans and strategy, which are subject to change by IBM without notice. IBM shall not be responsible for any damages arising out of the use of, or otherwise related to, this publication or any other materials. Nothing contained in this publication is intended to, nor shall have the effect of, creating any warranties or representations from IBM or its suppliers or licensors, or altering the terms and conditions of the applicable license agreement governing the use of IBM software. References in this presentation to IBM products, programs, or services do not imply that they will be available in all countries in which IBM operates. Product release dates and/or capabilities referenced in this presentation may change at any time at IBM s sole discretion based on market opportunities or other factors, and are not intended to be a commitment to future product or feature availability in any way. Nothing contained in these materials is intended to, nor shall have the effect of, stating or implying that any activities undertaken by you will result in any specific sales, revenue growth or other results. If the text contains performance statistics or references to benchmarks, insert the following language; otherwise delete: Performance is based on measurements and projections using standard IBM benchmarks in a controlled environment. The actual throughput or performance that any user will experience will vary depending upon many factors, including 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 results similar to those stated here. If the text includes any customer examples, please confirm we have prior written approval from such customer and insert the following language; otherwise delete: All customer examples described are presented as illustrations of how those customers have used IBM products and the results they may have achieved. Actual environmental costs and performance characteristics may vary by customer. Please review text for proper trademark attribution of IBM products. At first use, each product name must be the full name and include appropriate trademark symbols (e.g., IBM Lotus Sametime Unyte ). Subsequent references can drop IBM but should include the proper branding (e.g., Lotus Sametime Gateway, or WebSphere Server). Please refer to for guidance on which trademarks require the or symbol. Do not use abbreviations for IBM product names in your presentation. All product names must be used as adjectives rather than nouns. Please list all of the trademarks that you use in your presentation as follows; delete any not included in your presentation. IBM, the IBM logo, Lotus, Lotus Notes, Notes, Domino, Quickr, Sametime, WebSphere, UC2, PartnerWorld and Lotusphere are trademarks of International Business Machines Corporation in the United States, other countries, or both. Unyte is a trademark of WebDialogs, Inc., in the United States, other countries, or both. If you reference Adobe in the text, please mark the first use and include the following; otherwise delete: Adobe, the Adobe logo, PostScript, and the PostScript logo are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States, and/or other countries. If you reference Java in the text, please mark the first use and include the following; otherwise delete: Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both. If you reference Microsoft and/or Windows in the text, please mark the first use and include the following, as applicable; otherwise delete: Microsoft and Windows are trademarks of Microsoft Corporation in the United States, other countries, or both. If you reference Intel and/or any of the following Intel products in the text, please mark the first use and include those that you use as follows; otherwise delete: Intel, Intel Centrino, Celeron, Intel Xeon, Intel SpeedStep, Itanium, and Pentium are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries. If you reference UNIX in the text, please mark the first use and include the following; otherwise delete: UNIX is a registered trademark of The Open Group in the United States and other countries. If you reference Linux in your presentation, please mark the first use and include the following; otherwise delete: Linux is a registered trademark of Linus Torvalds in the United States, other countries, or both. Other company, product, or service names may be trademarks or service marks of others. If the text/graphics include screenshots, no actual IBM employee names may be used (even your own), if your screenshots include fictitious company names (e.g., Renovations, Zeta Bank, Acme) please update and insert the following; otherwise delete: All references to [insert fictitious company name] refer to a fictitious company and are used for illustration purposes only.